Code:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*
*/
Hi,
here you can find my preview version of LineageOS 19.1 for our Samsung Galaxy Note 8.0 devices.
At first I want to thank @rINanDO and @ChronoMonochrome for all your work which helped me a lot.
This is a BETA build, also on the LineageOS side, so don't install it if you want a completley stable rom and don't report my already listet bugs!
Here you can see how far everything is working for now.
Spoiler: Whats working
Boot
Bluetooth
Audio
Graphics
Cameras
Sensors
Wifi
GPS
USB
Video playback (HW/SW)
Tethering via USB, WIFI and Bluetooth
consumerir transmitter
Stylus
RIL
much more...
Spoiler: Whats not working
Random reboots
Encryption
Maybe more
SD-Card can't be formatted as internal storage, this will cause a bootloop
Spoiler: Links
TWRP
N5100 ROM
N5110 ROM
N5120 ROM
ROM Mega
Magisk zip file
Spoiler: Changelog
26.10.2021
30.11.2021
29.12.2021
09.01.2022
14.02.2022
15.02.2022
18.02.2022
07.03.2022
10.03.2022
17.03.2022
25.03.2022
03.04.2022
12.04.2022
10.05.2022
26.06.2022
23.09.2022
25.01.2023
Spoiler: Don't like my boot picture?
If you don't like it, reboot into recovery and type the following command:
adb shell (or use TWRP's terminal)
bash /data/param_restore.sh
reboot
Uploaded a prepared package to build your own boot picture
download
I would recommend to use microG (much faster experience) or open Gapps as soon they are available.
Do you like my work?
Than you can simply hit the thanks button and consider to spend me a coffee or a beer,
I'm doing this in my free time and it also costs a lot of money to buy hardware.
donate
Wanna improve your sound configs, control your charging current and more?
Now you can use my app to access all boeffla configurations, there will follow more functions.
Exynos4 Kernel Manager - Apps on Google Play
This app provides Boeffla sound control and other kernel + charging tweaks
play.google.com
Spoiler: How to install it?
Instructions
Spoiler: microG instructions
Download Magisk 24.1 and flash it via TWRP (yes, flash the APK file), reboot
Open Magisk and update the App (and do a reboot if it's asking)
Enable Zygisk in Magisk
Download and install microG installer in the Magisk manager, reboot
Download and install safetynet-fix in the Magisk manager, reboot
Check with a safetynet checker app and you should pass
XDA:DevDB Information
[ROM][12.x][N5100/N5110/N5120][BETA] LineageOS 19.1, ROM for the Samsung Galaxy Note 8.0
Contributors
html6405
Source Code: https://github.com/html6405
ROM OS Version: 12.x S
ROM Kernel: Linux 3.x
ROM Firmware Required: TWRP 3.5.2
Based On: LineageOS
Selinux: permissive, this only makes sense as soon the ROM is stable.
Version Information
Status: Beta
Created 2021-11-25
Last Updated 2023-01-25
Update 26.11.2021:
N5120: fixed deep sleep bug
fixed sw decoder issue
This update comes via OTA and don't forget, if you're using BitGapps,
reflash them manually after the flash, otherwise you will face a bootloop...
html6405 said:
Update 26.11.2021:
N5120: fixed deep sleep bug
Click to expand...
Click to collapse
Congrats on getting 19.0 up and running! I did notice the initial build had no deep sleep and I was going to report it, but I see you have resolved it now. Which commit on your github fixed the deep sleep? I want to know for learning purposes. NO RUSH for an answer. Thank you.
html6405N5100 (The firmware does not start)
retiredtab said:
Congrats on getting 19.0 up and running! I did notice the initial build had no deep sleep and I was going to report it, but I see you have resolved it now. Which commit on your github fixed the deep sleep? I want to know for learning purposes. NO RUSH for an answer. Thank you.
Click to expand...
Click to collapse
I will push the commit next week.
But it's only a temporyary solution, because of the not working ril so far, there's no deep sleep.
When we remove the radio entries in the device manifest the device will deep sleep.
The real solution will be to find a way of fixing the RIL on A12.
XdaFoxygen said:
html6405N5100 (The firmware does not start)
Click to expand...
Click to collapse
On my n5100 it run's very well, did you install the ROM clean, are you just facing a bootloop?
html6405 said:
On my n5100 it run's very well, did you install the ROM clean, are you just facing a bootloop?
Click to expand...
Click to collapse
Yes, I ran into the Samsung logo hanging on it.
Accidentally the firmware is not for the project treble?
XdaFoxygen said:
Yes, I ran into the Samsung logo hanging on it.
Accidentally the firmware is not for the project treble?
Click to expand...
Click to collapse
You could try to reboot, sometimes it could be that the device doesn't start the first try,
maybe some kind of timing issue in the mounting process.
Treble is disabled at the moment.
html6405 said:
You could try to reboot, sometimes it could be that the device start's the first boot,
maybe some kind of timing issue in the mounting process.
Treble is disabled at the moment.
Click to expand...
Click to collapse
I'm trying to hang on the logo for about 10 minutes and it doesn't go any further ...
oh yes it started although it took a long time (firmware works)
Can I use Open GApps?
Can I install the version of Open GApps from android 11?
334k said:
Can I use Open GApps?
Can I install the version of Open GApps from android 11?
Click to expand...
Click to collapse
No, you have to use gapps made for Android 12.
Update 30.11.2021:
N5100 & N5110: fixed GPS (N5120 should already work)
Enable default power hal for all
This update comes via OTA and don't forget, if you're using BitGapps,
reflash them manually after the flash, otherwise you will face a bootloop...
html6405Thanks for the update, I'm waiting for you to fix everything else.
I watched the app zoom video backwards through the browser. Can't view, message video media player back aborted
Can I edit it to play?
(N5100,Excellent, Rom is very beautiful)
html6405 said:
Code:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*
*/
Hi,
here you can find my preview version of LineageOS 19.0 for our Samsung Galaxy Note 8.0 devices.
At first I want to thank @rINanDO and @ChronoMonochrome for all your work which helped me a lot.
This is a early ALPHA build, also on the LineageOS side, so don't install it if you want a completley stable rom and don't report my already listet bugs!
When you have BitGapps installed, you have to reflash them after every update!
Here you can see how far everything is working for now.
Spoiler: Whats working
Boot
Bluetooth
Audio
Graphics
Cameras
Sensors
Wifi
GPS on N5120
USB
Video playback (HW/SW)
Tethering via USB, WIFI and Bluetooth
consumerir transmitter
Stylus with gestures and hovering icon
sec keyboard dock
RIL on N8000 (mobile connection)
much more...
Spoiler: Whats not working
Video recording with both cameras
GPS
N5120: RIL
Random reboots
Maybe more
SD-Card can't be formatted as internal storage, this will cause a bootloop
Spoiler: Links
TWRP
N5100 ROM
N5110 ROM
N5120 ROM
Magisk zip file
Spoiler: Changelog
26.10.2021
30.11.2021
Spoiler: Don't like my boot picture?
If you don't like it, reboot into recovery and type the following command:
adb shell (or use TWRP's terminal)
bash /data/param_restore.sh
reboot
Uploaded a prepared package to build your own boot picture
download
If you are going to use BitGapps,
here you can download them:
BitGapps, arm, 12
For the others, you can use microG in future.
If you plan to use a sim card in your device, I would recommend to disable the pin code before with another device.
In some cases the sim card becomes unusable while typing in the code.
Do you like my work?
Than you can simply hit the thanks button and consider to spend me a coffee or a beer,
I'm doing this in my free time and it also costs a lot of money to buy hardware.
donate
Spoiler: How to install it?
Instructions
XDA:DevDB Information
[ROM][12.x][N5100/N5110/N5120][BETA] LineageOS 19.0, ROM for the Samsung Galaxy Note 8.0
Contributors
html6405
Source Code: https://github.com/html6405
ROM OS Version: 12.x R
ROM Kernel: Linux 3.x
ROM Firmware Required: TWRP 3.5.2
Based On: LineageOS
Selinux: permissive, this only makes sense as soon the ROM is stable.
Version Information
Status: Alpha
Created 2021-11-25
Last Updated 2021-11-30
Click to expand...
Click to collapse
Is it a good idea trying to flash the device firmware with your costume ROM
Update 29.12.2021:
Synched with latest LineageOS sources
Signed with dev keys (removes the "signed with public keys" warning)
N5120: Fixed RIL, untested by me, because I don't have my device here, would be great if someone could test and report
N5120: It could be that gps crashes with this version, I would recommend to disable it until next build
Made some fixes for encryption ( but still not finished )
Created workaround to fix shutdown / reboot behaviour with Magisk
Fixed video recording with camera's
Fixed Torch (flashlight)
Fixed hardware button gestures control
Fixed GPS week rollover issue
Set swappiness to 60
Can I run it on a GT-N5105?
ertuncb said:
Can I run it on a GT-N5105?
Click to expand...
Click to collapse
Yes, the n5100 version should be compatible.
html6405 said:
Yes, the n5100 version should be compatible.
Click to expand...
Click to collapse
Flashed the lineage-19.0-20211229-HTML6405-n5100.zip. I've been waiting for 30 minutes with the text 'Samsung GALAXY Note 8.0 GT-N5105' on my screen. Any guesses on how long the first boot might take?
ertuncb said:
Flashed the lineage-19.0-20211229-HTML6405-n5100.zip. I've been waiting for 30 minutes with the text 'Samsung GALAXY Note 8.0 GT-N5105' on my screen. Any guesses on how long the first boot might take?
Click to expand...
Click to collapse
Tired of waiting and restarted by holding down the power button. The animation of LineageOS on initial setup appeared for a short while, then the system booted up. However, while trying to enter the settings and adjust the wireless network settings, the system shut down by itself and booted to TWRP. I've rebooted again and now the see the same boot screen text but with "xdadeveloper html640" in the last two lines. Still waiting, nothing happens. Any suggestions? (In between, I also cleaned dalvik cache and data)
Related
SamFail presents...
PartCyborgActiveRom
ARA1
A Rooted Custom Rom
For SM-G892A/U on V1 and V2 Bootloaders
FAQ
What is my Bootloader Revision?
Your bootloader revision is part of the baseband build number of the firmware you are currently running. For example, let's consider this firmware version: G892ASQS2BQL1
Start from the right and count 5 characters back. See that 2? That is the bootloader revision for the firmware that came with this rom. All Samsung firmware follow this formula for all devices.
Using this formula, What is the bootloader version for G892UEU4GHK1?
Answer: Bootloader revision is 4
Updates
Please see below for a a new update to both the V1 and V2 releases.
It is a new BL "part 2" tarball that contains a fix for the issues reported by
many of you with the finger print and other various sensors. It has replaced
the original firmware Part2 link in the following post .
Featured Modifications
Deodexed
Deodexed for all devices.
I found a way that works!
It should continue working as long
as we care about nougat
Xposed Preinstalled
Forget that extra flash, PCR now comes out of the flasher with xposed pre-installed.
NOTE: Xposed Installer may crash on first boot. It will not crash after setup finishes and you reboot
New Custom Boot Animation
Another great one from @rayan-refoua himself.
This one is my favorite so far.
JamesDSP
I added another DSP style audio mod. JamesDSP is similar to V4A in how it operates and what features it has, but it has some really awesome features that have gotten me using it for a while. Specifically it has a better convolver (IRS processing) implementation, and its bass boost is WAY better than v4a. However you can use both at the same time to get the best of both worlds.
ITYBP Modded YouTube
A last minute addition, this is a really nice youtube mod brought to you by XXXXXX ADD SOURCE XXXXX. It features some cool features like native adblocking (no more xposed module), override your max youtube resolution (so you can watch 4k videos on your phone), and, not as important to us, spoofing different device types to get true hdr videos. I have been using it for a while and really like it. A big thanks to them for letting me include it with PCR
Improved Debloating
I did a lot more digging this round, and was able to add back a few things that I had taken out without loading the system more. This rom feels snappier than any before it. As usual, if you find something missing that you want back, pull it from the stock rom and install it in /system.
Improved Battery Life
Thanks to some fine battery sleuthing work by @TheMadScientist, this release comes with a nice big bump in efficiency. With just some very minor tuning using amplify and a service disabler, I can get around 1%/h drain.
Performance Improvements
That increased battery life does not come at the cost of performance. In fact performance is better too. Part of that is due to a large batch of personally tested build.prop tweaks make the ui a lot more responsive. Part of that is the data optimisation scripts that now run at boot to make sure things are cleaned up and in tip top shape. You wont notice those, but they are there doing their thing.
Other Features
- Pre-Rooted with SuperSU installed
- CSC OYN pre-installed. Tested working on several carriers
- RCS and VoLTE icons removed from status bar.
- High quality audio mods, including
- Viper Audio (V4A)
- Dolby Atmos from the Axon 7
- Pandora hifi audio framework
- Native Google Dialer & Contacts support, including local search, spam call blocking
- Oreo 8..1 Emoji Icon Set
- Custom Lockscreen Clock font
- Stock system display fonts replaced with Apple's original San Francisco Font
Special Thanks
- @ahiron and @Zackptg5 for the killer sounds from V4A and Dolby Atmos Mods!
- The Aiur crew for Pandora (now a legacy mod but works great on the s8)
- @syndre for the Google Dialer and Contacts framework mod
- @rayan-refoua for the beautiful Tech Lines Custom boot and shutdown animations!
- Last but not least, my new friend @laura almeida, along with @Razerman amd @ZaneZam for letting me include the iYTBP - injected YouTube Background Playback Mod
- everyone who tested
Warnings/Disclaimers/Known Issues
- 80% Battery life like every other rooted US snapdragon device
- Flashing on a USB 3.0 port will likely cause corruption in your flash that can cause kernel panics, loss of root, and occasionally very strange other errors. If you get something like this, its not the rom its a hardware conflict that can only show up with larger images like are used in SamFail flashing. See the section below on Kernel Panics for more.
- If there is an app or apk from the stock rom that you wish you had installed, the best solution is to extract it from your stock rom image and copy it to the same place in /system using a root file manager. If a large number of people want something back, I will include it in the next version, but by now I think we have covered all those possibilities and now the list will only get shorter. No I will not put Bixby back
SamFail Rooting Process
and Rom Installation
WARNING: THE FOLLOWING WILL ERASE YOUR WHOLE PHONE
If you have a SDCard, remove it from your device. Occasional firmware incidents have wiped SDCards in the past. Better safe than sorry.
Prepare the Following:
- complete stock rom at your bootloader rev in case things dont work
- Everything backed up (see above)
- Both Prince Comsy Odin, and Regular Odin for flashing stock
- A USB 2.0 Port. If you attempt to flash with a USB 3.0 port it may work, but if you get kernel panics, or unexpected bad behavior and/or crashes your usb3 is absolutely to blame. some people get lucky and suceed after a few tries, YMMV. If you can not acquire a machine with a usb2.0 port, get a usb2.0 hub and run your phone into that & that into your machine. Reports are that has made things work for some, but we get few reports back.
[/size]
Steps to Root
1) Download and unzip AP Part 1 and BL Part 2 zip files.
2) Download and unzip Prince Comsey Odin and start it up
3) Reboot device into Download mode, connect to your pc
4) Open Comsy Odin and add ONLY the AP Part1.tar.md5 file. Select the following options only:
- "Auto-Reboot"
- "F-Reset Time"
- "Nand Erase All"
NOTE: Odin will freeze while checking the AP tar.md5 hash.
Be patient, it will come back.
5) Click "Start" and wait for the system.img.ext4 file to flash fully to your device. This will take a while too.
ATTENTION:
When the flash finishes, this is when the SamFail magic happens. Instead of saying "Failed (Auth)" like it should, the device will crash into upload mode with "Unknow Error".
If your device does not do this, and just says "Failed (Auth)" or something similar and stays in download mode, you need to start again from the beginning, but using a different set of ub ports as you have suffered from the usb3 corruption.
When you see the upload mode page, use the 3 button reboot to go back to download mode.
WARNING: When you reboot from upload mode, your phone will show an error instead of download mode.
When you reboot back into download mode, your screen will say that you had a failed update and you need to do emergency repair or take your device to a service center.
Rest assured, your phone is actually in download mode, and Odin will have recognized it and said "Added!" along with the com port lighting up underneath the progress bar.
It is safe to continue
6) Close and re-open Comsy Odin or hit the reset button, and add BL_PartCyborgRom-BootLoopEdition-<version>.tar.md5 to the BL section.
7) Leave the default checkboxes for "F Reset Time" and "Auto Reboot" checked. Click "Start" and flash the BL (part 2) to your device.
8) Wait for the flash to finish . It won't take very long at all all the files are small.
9) When it has finished, Odin will say PASS and your device will reboot into recovery.
Warning: Failure to follow this step could lead to a corrupted instance with no cell coverrage
10) When in recovery issue a factory reset. This ensures that your device has a userdata partition that is valid, and that the csc is processed correctly. Failure to do the reset could cause issues with either.
All done!
Donations/Root Bounty
Pledged a donation for the root bounty? Send it here. Thank you!
IF YOU GET A BOOT LOOP:
If you get a boot loop or your device hangs at boot, try the following:
1) Reboot to recovery and factory reset again.
To get to recovery hold power+vol-down until screen goes black, then wait till upload mode (press power key for 7+ secs) comes up. Then press vol-down+power again and hold it till it reboots and as SOON as the screen goes black switch to holding vol-up+power+bixby. Hold it for 5-7sec then let go and you will wind up in recovery mode.
Kernel Panic, Invalid Argument
Start the process over
Go back to the beginning and do everything again. If it fails in a new way this time, you may have hardware caused corruption, or maybe you missed a step. Change hardware, and keep trying.
Help
If you get stuck, some of us will be here to help. Check out our telegram channel, where people will be around that can help you. Come Check it out.
Enjoy!
XDA:DevDB Information
PartCyborgRom, ROM for the Samsung Galaxy S8
Contributors
partcyborg
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 4.x
Based On: TouchWiz/Samsung Experience
Version Information
Status: Stable
Current Stable Version: BQL1
Stable Release Date: 2017-12-10
Created 2017-12-11
Last Updated 2018-2-10
Downloads
V1 Bootloader Revision
PartCyborgRom.G892A-ARA1.Part1.zip
[Alternate Mirror]
PartCyborgRom.G892A-ARA1.Part1b.zip
[New: Fingerprint/Sensors all working]
V2 Bootloader Revision
PartCyborgRom.G892A-2ARA1.Part1.zip
[Alternate Mirror]
PartCyborgRom.G892A-2ARA1.Part2b.zip
[New: Fingerprint/Sensors all working]
(New!) V3 Bootloader Revision
SM-G892A: PCR_G892A_BLV3.7z
SM-G892U: PCR_G892U_BLV3.7z
Odin
Prince Comsy Odin
One more time
I'm gonna celebrate it
Oh boy I'm first in the thread lol. No bagsssss.
I'm outa thanks for the day but they is comin
How to I know what version of Bootloader I have?
Yu-Ra said:
How to I know what version of Bootloader I have?
Click to expand...
Click to collapse
What is your baseband version
Mine has the u2 in it means I'm v2 look in pic
Can't unzip part 1, re DLed it multiple times can only extract 518mbs then crc error.
Pjs187 said:
Can't unzip part 1, re DLed it multiple times can only extract 518mbs then crc error.
Click to expand...
Click to collapse
I will let him know this was a issue the other day as well
That would be the AP part right
TheMadScientist said:
I will let him know this was a issue the other day as well
That would be the AP part right
Click to expand...
Click to collapse
Yes sir. TY.
Pjs187 said:
Yes sir. TY.
Click to expand...
Click to collapse
He may be busy I dropped him a note It happened a while back while he did the reg s8 betas also something with the zip file is corrupt
The downloads worked for me, no issues. If you're on a tmobile variant this rom will work fine also if you're on BL 1 att you'll be fine not sure about sprint, my fingerprint scanner, iris scanner & face recognition don't work but everything else running perfect.
Purest said:
The downloads worked for me, no issues. If you're on a tmobile variant this rom will work fine also if you're on BL 1 att you'll be fine not sure about sprint, my fingerprint scanner, iris scanner & face recognition don't work but everything else running perfect.
Click to expand...
Click to collapse
Hmmm the download extract was broken for me as well. But should be fixed sometime soon.
TheMadScientist said:
Hmmm the download extract was broken for me as well. But should be fixed sometime soon.
Click to expand...
Click to collapse
What mirror did you use? Some of the mirrors were giving me issues, the Texas mirror was the only one working properly for me.
Purest said:
What mirror did you use? Some of the mirrors were giving me issues, the Texas mirror was the only one working properly for me.
Click to expand...
Click to collapse
Lol that's the one I used
Purest said:
What mirror did you use? Some of the mirrors were giving me issues, the Texas mirror was the only one working properly for me.
Click to expand...
Click to collapse
TheMadScientist said:
Lol that's the one I used
Click to expand...
Click to collapse
Pjs187 said:
Can't unzip part 1, re DLed it multiple times can only extract 518mbs then crc error.
Click to expand...
Click to collapse
Sorry for the trouble folks! The zip extracts fine on my end, so it must be an AFH issue. Ill do what i can as im s paying customer, but we will see. In the meantime, i posted another link under "Alternate Mirror", so download from there if you are having issues.
ill reupload it to afh as well
Bootloader V2 support is now up in the OP!
Hey what version of xposed did you use, note 8 xposed isn't working wondering if you used a modified version or what you might have used?
partcyborg said:
Sorry for the trouble folks! The zip extracts fine on my end, so it must be an AFH issue. Ill do what i can as im s paying customer, but we will see. In the meantime, i posted another link under "Alternate Mirror", so download from there if you are having issues.
ill reupload it to afh as well
Click to expand...
Click to collapse
Awesome work OP thank you very much, got everything up and running now very nice, let me know where to send money for the bounty.
Pjs187 said:
Awesome work OP thank you very much, got everything up and running now very nice, let me know where to send money for the bounty.
Click to expand...
Click to collapse
I knew I forgot something!!!
https://www.paypal.me/partcyborg is the link. I will add it to the op too.
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
Features:
All function in a normal TWRP
Multi-language support
MTP
Backup/Restore
Install guide:
1. Install fastboot tools from google's sdk on your PC
2. Enter fastboot mode
3. Unlock your bootloader
4. Run "fastboot flash recovery imgfilename.img" in command line ( if you want you can go in recovery from bastboot using this command "fastboot boot imgfilename.img" )
5. Reboot and enjoy it
Download:
Official Pace TWRPs
TWRP 3.2.3-6 Pace A1602 Full
TWRP 3.2.3-7 Pace A1612 Full
TWRP 3.2.3-5 Stratos Full
TWRP 3.2.3-5 Verge Full
Source code:
https://github.com/omnirom/android_bootable_recovery
https://github.com/mauronofrio/android_device_huami_huanghe-twrp
https://github.com/mauronofrio/android_device_huami_everest-twrp
https://github.com/mauronofrio/android_device_huami_qogir-twrp
Thanks to @TingyiChen for the base
DONATE LINK
If you want to support the project please consider making a donation, thanks.
Created 2018-11-28
Many thanks!
Can you provide images
tiago199988 said:
Can you provide images
Click to expand...
Click to collapse
and this what is?
mauronofrio said:
Download:
TWRP 3.2.3-3 Pace
Click to expand...
Click to collapse
Would some pictures not be?
Do not use, it ****s up the serial of the watch
1immortal said:
Do not use, it ****s up the serial of the watch
Click to expand...
Click to collapse
Yes unfortunately there was this bug in the older one, with the new one this bug is solved.
Please all use this twrp check if they have the serial number, if you have not it please follow this guide:
https://forum.xda-developers.com/smartwatch/amazfit/guide-restore-null-sn-locked-t3775998
Could I use this recovery image on Stratos CN version (1609)?
Thanks.
Vandriod said:
Could I use this recovery image on Stratos CN version (1609)?
Thanks.
Click to expand...
Click to collapse
Yes
1immortal said:
Do not use, it ****s up the serial of the watch
Click to expand...
Click to collapse
Pace or Stratos ?
---------- Post added at 20:21 ---------- Previous post was at 20:20 ----------
Can we flash SuperSU with this ?
AFAIK We have MIPS ,not arm ,also supersu wasn't ported to Android Wear (If that matters).
The4anoni said:
Pace or Stratos ?
---------- Post added at 20:21 ---------- Previous post was at 20:20 ----------
Can we flash SuperSU with this ?
AFAIK We have MIPS ,not arm ,also supersu wasn't ported to Android Wear (If that matters).
Click to expand...
Click to collapse
The serial problem is solved
mauronofrio said:
The serial problem is solved
Click to expand...
Click to collapse
I know ,but I just want to ask
Thank you for the builds! May I ask why there is a "small" and "full" versions? Both img's have the same size.
Regards
lfom said:
Thank you for the builds! May I ask why there is a "small" and "full" versions? Both img's have the same size.
Regards
Click to expand...
Click to collapse
Full is a full size without corners, the small have corners so it smaller than full img
mauronofrio said:
Full is a full size without corners, the small have corners so it smaller than full img
Click to expand...
Click to collapse
It's related to the screen resolution then, right? OK, I got it.
Once again, thanks a lot for the build. I have installed it on Pace and it seemed to work fine. A few remarks:
1. The identifiers for "device" and "model" are different from the normal firmware, so it's not possible to install stock firmware or OTAs, probably it can be fixed easily:
Code:
getprop("ro.product.device") == "watch"
getprop("ro.build.huami.model") == "A1602"
2. The touchscreen seems to need some calibration, sometimes the button identified as touched isn't the correct one, it's even harder with smaller options.
3. It seems that sometimes the screen doesn't update: after I tap a button, I need to swipe the screen so it is refreshed and you can see the new content. It's kinda dangerous because you can tap somewhere you don't want to when doing this... No idea how this can be improved, tho.
4. After a installing, I could do a backup, etc, but the next reboot the recovery was replaced by the stock one (it shows "No command" after boot). Do you know how to prevent this? Never mind, I found the cause.
Keep it up! Regards.
lfom said:
It's related to the screen resolution then, right? OK, I got it.
Once again, thanks a lot for the build. I have installed it on Pace and it seemed to work fine. A few remarks:
1. The identifiers for "device" and "model" are different from the normal firmware, so it's not possible to install stock firmware or OTAs, probably it can be fixed easily:
Code:
getprop("ro.product.device") == "watch"
getprop("ro.build.huami.model") == "A1602"
2. The touchscreen seems to need some calibration, sometimes the button identified as touched isn't the correct one, it's even harder with smaller options.
3. It seems that sometimes the screen doesn't update: after I tap a button, I need to swipe the screen so it is refreshed and you can see the new content. It's kinda dangerous because you can tap somewhere you don't want to when doing this... No idea how this can be improved, tho.
4. After a installing, I could do a backup, etc, but the next reboot the recovery was replaced by the stock one (it shows "No command" after boot). Do you know how to prevent this? Never mind, I found the cause.
Keep it up! Regards.
Click to expand...
Click to collapse
New twrps pubblished, also verge supported now.
Now you can flash stock roms, for the touch i can't do nothing, is a kernel problem.
mauronofrio said:
New twrps pubblished, also verge supported now.
Now you can flash stock roms, for the touch i can't do nothing, is a kernel problem.
Click to expand...
Click to collapse
I am sorry, but it didn't change anything (I am still getting the same IDs with 3.2.3-5 installed on Pace) . Anyway, Huami updates also check for the installed version signature, so unless there is a way to read device's build.prop during boot, I think it won't work.
Another question: I could not get "show_progress(fraction, time)" to work correctly in any flashing script, it always goes to 100%. It works fine when backuping/restoring tho. Known bug?
Thanks again. Regards.
lfom said:
I am sorry, but it didn't change anything (I am still getting the same IDs with 3.2.3-5 installed on Pace) . Anyway, Huami updates also check for the installed version signature, so unless there is a way to read device's build.prop during boot, I think it won't work.
Another question: I could not get "show_progress(fraction, time)" to work correctly in any flashing script, it always goes to 100%. It works fine when backuping/restoring tho. Known bug?
Thanks again. Regards.
Click to expand...
Click to collapse
Can you share a stock rom zip?
mauronofrio said:
Can you share a stock rom zip?
Click to expand...
Click to collapse
They can be downloaded from Huami's Pan Disk online:
http://bbs.huami.com/thread-4934-1-1.html
I have attached an update.zip script too (delta OTA update).
lfom said:
They can be downloaded from Huami's Pan Disk online:
http://bbs.huami.com/thread-4934-1-1.html
Click to expand...
Click to collapse
I'm unable to download roms from baidu, please reupload one stock rom on another cloud service and give me the link
Update March 23, 2019: I'd like to apologize to everyone. It looks like I am not going to be able to actively keep this thread updated like I used to. I have had too much going on at home an work and it doesn't look like it's going to settle down any time soon. The thread is still usable so I will leave it open for discussion.
Team Win Recovery Project
Code:
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards, fires, rigged elections,
* specks of dusk sitting on cursors, cursors that mock you--waiting for cursor
* revenge, thermonuclear war, or you getting fired because the alarms failed
* and you could not call in.
*
* Please ensure you have an advanced understanding of this device before
* flashing it! YOU are choosing to make these modifications or your own free will.
This is the first official build of TWRP for the Motorola Moto G6 (ALI)!
Notes:
Decryption is finicky: Currently only vold decryption is working. This image must be flashed to properly decrypt. Updates may cause issues with decryption.
If you format data (Not just factory reset) after decrypting you must reboot into recovery and format again.
If you are unable to unlock your phone after restoring a data backup that had a lock code on it (and TWRP is able to decrypt using default password) you'll need remove the '/data/system/locksettings.db' while in TWRP. After that you should be able to reboot into Android and set a lock code. If you cannot then please use this thread as a guide and try again. Bascially you just delete more, however I was able to boot after just deleting the one file with a pattern set (Maybe random luck, maybe not)
If you have any other issues please let me know and I'll work toward fixing them! AS ALWAYS, IT'S YOUR RESPONSIBILITY IF YOU USE THIS SOFTWARE
Known Issues:
I have just noticed some odd behaviour if you input an incorrect decryption password/pattern/etc in twrp. It can cause an issue while entering the lockscreen password/pattern/etc while booting up. Under normal circumstances these two are the same, hence why restoring can also cause a similar issue, though that one is easily fixable. The onIy way to clear the decryption pass is to format. I am unsure at the moment what is causing this, but clearly it has something to do with the decryption. At this time I'd say it'd be best to remove your current lockscreen password/pattern/etc before booting into twrp to avoid this issue. A possible work-around would be to reboot to twrp, enter the correct password, back up your data, format (reboot to twrp and format again), then restore your backup (and possibly need to delete the '/data/system/locksettings.db' file. Your data would still exist that way. I am going to work to fix this asap and maybe see if I can get another build without decryption made for official use for now.
Flashing zips that require BusyBox will not work with the official version right now. I've built an unofficial version to use until a new official build is triggered.
ALI's Changelog: Post #2
Download: twrp.me Download
Unofficial Download (updated more often): twrp-v3.2.3-unofficial-ali-20181110.img
Simple Installation Method:
1) boot to fastboot
2) fastboot flash recovery <twrp-image-name>.img
Other instructions are available on the Official download page. It's up to you to backup your factory recovery first if you wish to have a backup: Post #3
Thanks to the TWRP team and everyone who has put in effort to make these things possible!
@Jleeblanch - Wonderful advice and guidance
@Dadud - testing
@ Everyone at github
@ XDA and the people who provided TWRP compiling threads
If I've forgotten someone who you think needs mention please let me know!
* This page will continue to be edited as more information comes
XDA:DevDB Information
[RECOVERY][OFFICIAL] TWRP v3.2.3 [2018-10-20], Tool/Utility for the Moto G6
Contributors
dejello
Source Code: [url]https://github.com/TeamWin/android_device_motorola_ali[/URL]
Version Information
Status: Stable
Current Stable Version: 3.2.3-0
Stable Release Date: 2018-10-20
Current Beta Version: 3.2.3 Unofficial
Beta Release Date: 2018-11-10
Created 2018-10-21
Last Updated 2018-11-10
Changelogs
TWRP Changelog:
v3.2.3 changelog
ALI's Official Changelog:
v3.2.3-0 (Oct 20, 2018)
- N/A, first build!
ALI's Temp. Unofficial Changelog:
v3.2.3 (Oct 31, 2018) (This log will get moved to official when it gets updated with these changes)
- Stop using toybox (Use busybox!)
- Added vendor image mount point
Factory Backup Information
It's up to you to determine if you want/need a factory recovery image backup before flashing:
To boot twrp first (it will fail decryption, don't worry about it) just do the following while replacing <twrp> with the actual file name.
Code:
fastboot boot <twrp>.img
Then to back up your stock/factory recovery while booted in TWRP do the following.
Code:
adb pull /dev/block/bootdevice/by-name/recovery stockrecovery.img
First [emoji14]
For real tho, nice work and congrats [emoji41]
Woot Woot! Congrats bro?
Lockscreen after restore
Hello, this method (delete lockscreen) after restore backup works for me to ?
Decryption doesn't work for me. XT1925-6 Ali
giant22000 said:
Decryption doesn't work for me. XT1925-6 Ali
Click to expand...
Click to collapse
I'll need more details if I'm to look into it. I also have an xt1925-6. Any logs? What version software are you running? What kind of lock screen are you using (pin, password, pattern, none, etc)? What happened from booting twrp up to the point of decryption failure? The more information I have the better chance I have at rectifying the issue.
[EDIT] I just did some messing around and came across something I hadn't seen before:
I have just noticed some odd behaviour if you input an incorrect decryption password/pattern/etc in twrp. It can cause an issue while entering the lockscreen password/pattern/etc while booting up. Under normal circumstances these two are the same, hence why restoring can also cause a similar issue, though that one is easily fixable. The onIy way to clear the decryption pass is to format. I am unsure at the moment what is causing this, but clearly it has something to do with the decryption. At this time I'd say it'd be best to remove your current lockscreen password/pattern/etc before booting into twrp to avoid this issue. A possible work-around would be to reboot to twrp, enter the correct password, back up your data, format (reboot to twrp and format again), then restore your backup (and possibly need to delete the '/data/system/locksettings.db' file. Your data would still exist that way. I am going to work to fix this asap and maybe see if I can get another build without decryption made for official use for now.
I have added this to the first post.
Damn thanks !
Hi. First thank for the contribution.
I would like to know if someone has the stock twrp, modeled 1925-1. When I modified my stock twrp, I made a back up, but I lost it.
I would like to update my security patch, but I can not because it has modified the twrp.
aaleej0 said:
Hi. First thank for the contribution.
I would like to know if someone has the stock twrp, modeled 1925-1. When I modified my stock twrp, I made a back up, but I lost it.
I would like to update my security patch, but I can not because it has modified the twrp.
Click to expand...
Click to collapse
So I guess I will be the one to say it. I'm giving you one warning about this. It's against forum rules to post on multiple threads with the same subject. I've answered your question on the Ali stock firmware thread also. Please read guides and threads instead of skimming through them because it's been answered multiple times. Next time you do this and post the same thing on multiple threads I will be the one reporting you. Have a good day.
I have added an unofficial build tonight (Oct/31/2018) to fix an issue flashing zips that need busybox (Resurrected Kernel, etc) versus toybox. It also adds a 'vendor image' mount point for use in backups and flashing. Once official gets updated this unofficial build will be removed.
Hello, could you consider supporting the Moto g 6 play xt922-4 I'm welling to help out with logs or anyfile if needed.
jglm4u said:
Hello, could you consider supporting the Moto g 6 play xt922-4 I'm welling to help out with logs or anyfile if needed.
Click to expand...
Click to collapse
There are certain reasons there is no official twrp for our moto g6 play devices yet. Is there issue your having?. Dejello supports the regular g6 and for all intensive purposes I've being doing support for the g6 play.
jglm4u said:
Hello, could you consider supporting the Moto g 6 play xt922-4 I'm welling to help out with logs or anyfile if needed.
Click to expand...
Click to collapse
ninjakira said:
There are certain reasons there is no official twrp for our moto g6 play devices yet. Is there issue your having?. Dejello supports the regular g6 and for all intensive purposes I've being doing support for the g6 play.
Click to expand...
Click to collapse
I don't have access (well, sort of but not really) to a g6 play. My son has one, but it's not unlocked or anything and I won't experiment on his phone without having everything backed up.... Besides, getting the damn thing away from him for extended periods when he isn't in trouble would be something.... I thing it's glued to his face or something.
I am also not up to date on any issues or reasons why twrp isn't official for the g6 play. Be aware that even this version for the g6 has some issues (workarounds are available for everything so you won't lose anything) still.
I've been debating looking into it, but haven't yet for reasons above.
dejello said:
I don't have access (well, sort of but not really) to a g6 play. My son has one, but it's not unlocked or anything and I won't experiment on his phone without having everything backed up.... Besides, getting the damn thing away from him for extended periods when he isn't in trouble would be something.... I thing it's glued to his face or something.
I am also not up to date on any issues or reasons why twrp isn't official for the g6 play. Be aware that even this version for the g6 has some issues (workarounds are available for everything so you won't lose anything) still.
I've been debating looking into it, but haven't yet for reasons above.
Click to expand...
Click to collapse
I just had a good laugh about your son's g6 play being glued to his face ??I could definitely say I don't look at or use my phone as much as the kids now a days and I'm 27 lol I worked ina mall so I seen that alot lmao and what all would you need from someone to attempt an official twrp for it? Ill do my best to provide you with what's needed. The patched twrp for the g6 play should be a good start. I would have already started on it myself but i am not able to get it going because i don't trust my laptop (it came with Vista) and it likes to randomly reboot and all this marvelous stuff lol
ninjakira said:
I just had a good laugh about your son's g6 play being glued to his face ??I could definitely say I don't look at or use my phone as much as the kids now a days and I'm 27 lol I worked ina mall so I seen that alot lmao and what all would you need from someone to attempt an official twrp for it? Ill do my best to provide you with what's needed. The patched twrp for the g6 play should be a good start. I would have already started on it myself but i am not able to get it going because i don't trust my laptop (it came with Vista) and it likes to randomly reboot and all this marvelous stuff lol
Click to expand...
Click to collapse
When I get a chance I can take a look at some things. But looking at github I do see at least one device tree being worked on for jeter
ninjakira said:
I just had a good laugh about your son's g6 play being glued to his face [emoji23][emoji23]I could definitely say I don't look at or use my phone as much as the kids now a days and I'm 27 lol I worked ina mall so I seen that alot lmao and what all would you need from someone to attempt an official twrp for it? Ill do my best to provide you with what's needed. The patched twrp for the g6 play should be a good start. I would have already started on it myself but i am not able to get it going because i don't trust my laptop (it came with Vista) and it likes to randomly reboot and all this marvelous stuff lol
Click to expand...
Click to collapse
I wouldn't trust Windows either. Personally, I'd wipe Windows right off it and run Linux. Linux would breathe new life into a laptop that came with Vista lol.
Jleeblanch said:
I wouldn't trust Windows either. Personally, I'd wipe Windows right off it and run Linux. Linux would breathe new life into a laptop that came with Vista lol.
Click to expand...
Click to collapse
I do have it on dual boot with Ubuntu 18.10 it's Just the the random rebooting is persistent still but yeah I personally use use linux distos over Windows lol. My next paycheck I'm having our local computer store called microcenter help me out with a new laptop at least lol
dejello said:
When I get a chance I can take a look at some things. But looking at github I do see at least one device tree being worked on for jeter
Click to expand...
Click to collapse
I'm not able to send the screenshot of termux so here they are. Recovery is 16 mb
ProtonAOSP
Android 12 ROM
ProtonAOSP is a minimal Android fork (custom ROM) focused on UI/UX and performance, with a touch of privacy.
Screenshots
Screenshots of the latest version
Installation
This ROM is currently distributed as flashable ZIPs. Flash it the same way you would flash ROM ZIPs. Don't forget to wipe all data using "fastboot -w" before booting the ROM.
Features
List of current features, with accompanying screenshots and explanations
Downloads
Downloads and changelogs for all versions
Builds with and without minimal Google services (gapps) included are provided for convenience.
Support
If you have questions or concerns, please read the Frequently Asked Questions before asking. It saves time for everyone involved, especially you, and allows us to provide higher-quality answers for all users.
Website with comprehensive documentation
Join the Telegram group for support and extras
Please consider donating to @kdrag0n to support development if you found this helpful: recurring donation to keep the project alive in the long term or buy him a coffee
Kernel source code
ROM source code
Link to AOSP 11: https://github.com/JarlPenguin/rele...001/aosp_montana-ota-retrofit-eng.kiam001.zip
Has the same bugs as LineageOS 18.1.
AOSP 12 has been dropped in favor of ProtonAOSP.
AOSP 11/12 and ProtonAOSP sources are on my GitHub and should be fully buildable. If not, open an issue here.
а можно просто командами рассписать ?
but can you just write down the commands?
JarlPenguin said:
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
Instructions:
Download the latest super images, build, recovery image and GApps (if you need them)
Flash the downloaded super images and recovery image via fastboot
Boot to recovery
Format system and perform a factory reset
Reboot to recovery
Flash the latest build
Flash GApps and any other necessary add-ons
What's working:
WiFi
Camera and Camcorder
Bluetooth
Fingerprint - Oreo firmware required
OTG
Video Playback
Audio
RIL
VoLTE
You tell me
Known issues:
SELinux: Permissive
You tell me
Not tested:
NFC
GPS
USB tethering/audio
Downloads:
Super images: Here
Builds: Here
Recovery: Here
Google Apps: Here
Reporting Bugs
All bugs should be reported here: Issue Tracker
DO NOT Report bugs if you're running a custom kernel or you installed Xposed
Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
If it is a random reboot, grab /proc/last_kmsg. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
If the problem disappears after running "setenforce 0" from a root shell, grab /data/misc/audit/audit.log
Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. Please also do not report known issues. Any bug not reported in the bug report format below may be ignored.
Code:
What is your--
version:
Download url:
Gapps version:
Did you--
wipe:
restore with titanium backup:
reboot after having the issue:
Are you using--
a task killer:
a non-stock kernel:
other modifications:
Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed:
Thanks to:
@GivFNZ, @Hausemaster, @Rush for testing my builds
@wiktorek140, @karthick mostwanted, @wh0dat, @KalilDev, @AsD Monio, @GoldeneyeS2, @Steve Mathew Joy and @rajatgupta1998 for their hard work on our device sources
LineageOS team
Changelogs:
Code:
2021-10-21:
Fixed Bluetooth.
Fixed FM Radio.
Fixed an issue where the system became unresponsive after enabling and disabling Hotspot and attempting to turn on WiFi.
Fixed GUI glitchiness.
Updated to android-12.0.0_r3 tag.
2021-10-18:
Initial release.
Source code:
Common device tree: https://github.com/JarlPenguin/device_motorola_msm8937-common
Device tree: https://github.com/JarlPenguin/device_motorola_montana
Kernel: https://github.com/LineageOS/android_kernel_motorola_msm8953
Click to expand...
Click to collapse
How to flash super image,,, what is the command?
liony77 said:
а можно просто командами рассписать ?
but can you just write down the commands?
Click to expand...
Click to collapse
SDanger4U said:
How to flash super image,,, what is the command?
Click to expand...
Click to collapse
If you don't understand what and how you need to flash you're better off not installing this ROM. It's not 100% stable either.
everything works wonderfully. does not pass certification
First stable build released. Links and changelog have been updated in the OP.
i did everything in order, but recovery wont boot.
janinetavs said:
i did everything in order, but recovery wont boot.
Click to expand...
Click to collapse
It works only lineage recovery,,,,I tested today,,,but my mobile network not working then I uninstalled it
JarlPenguin said:
First stable build released. Links and changelog have been updated in the OP.
Click to expand...
Click to collapse
Hi,
Hope you are doing well.
Are regular builds (flashable via zip) also planned? For A12
newinnov said:
Hi,
Hope you are doing well.
Are regular builds (flashable via zip) also planned? For A12
Click to expand...
Click to collapse
Once I get time to look into the bugs, yes.
H
Hello everyone, it's been a while since the last update. We've managed to partially fix RIL, while audio is behaving somewhat weirdly. Everything seems to work except for mobile data and VoLTE on the 2nd SIM, while as for audio, system and notification sounds are somewhat delayed. As of right now we don't really know the cause, but we're working on fixing these issues. Also, I've implemented the possibility to relock your bootloader, which is useful for people who would like to run custom ROMs, but with the additional security benefits that a locked bootloader brings.
AOSP 12 has been dropped in favor of ProtonAOSP. First build is available here.
Second build with a quick hotfix is up, I recommend that anyone on version 1 flash this build.
Third release available with some minor fixes and a non-gapps build.
Sorry for saying this But I am a beginner so can you please just explain in a way so that I can understand how to install. P.S. I have already tried via twrp and via adb sideload but it just goes on a loop at the stage where it show the id in yellow colour And yeah I have Latest Lineage os installed.
Sorry again for a silly question
JarlPenguin said:
Third release available with some minor fixes and a non-gapps build.
Click to expand...
Click to collapse
I tried it out, and it worked excellently, except for poor battery life on my device (I'd estimate about half the battery life of stock)
This led me to decide to revert to a backup. (Using the Motorola Software Repair Assistant + backup of data using TWRP)
In doing so, I encountered a major issue: the device can no longer connect to mobile networks (including sms) or gps. Reinstalling the ROM restored this, but even a full reset using the SRA also cannot use these networks.
Any idea what if anything I could do to fix this?
SussyBaka said:
Sorry for saying this But I am a beginner so can you please just explain in a way so that I can understand how to install. P.S. I have already tried via twrp and via adb sideload but it just goes on a loop at the stage where it show the id in yellow colour And yeah I have Latest Lineage os installed.
Sorry again for a silly question
Click to expand...
Click to collapse
I also encountered a fair number of bootloops while installing. I think the installed system should be stock (but I may be wrong), so reinstall stock again first, then flash with TWRP (adb sideload works for me). Then run `fastboot -w` in bootloader before booting the device.
_Kumiho said:
I also encountered a fair number of bootloops while installing. I think the installed system should be stock (but I may be wrong), so reinstall stock again first, then flash with TWRP (adb sideload works for me). Then run `fastboot -w` in bootloader before booting the device.
Click to expand...
Click to collapse
I will give it a try Thanks!!
AOSP 13
This is a moto-common project release under the codename borneo
Code:
/*
* I'm not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed (like it did for me...).
* Please do some research if you have any concerns about features included in the products you find here before flashing it!
* YOU are choosing to make these modifications, and if you point the finger at me for messing up your device, I will laugh at you.
* Your warranty will be void if you tamper with any part of your device / software.
* Same statement for XDA.
*/
What's Moto-Common?
Moto-Common is a set of trees common to every 4.14+ QCOM Motorola device, making it easier to do bringups based on SODP.
What's AOSP?
AOSP is Android as Google publish without other modifications.
Known issues:
You tell me
IF YOU DONT HAVE SLOT B FILLED YOU CAN BRICK
Instructions :
Download the latest build
Reboot to bootloader
Code:
fastboot -w
Code:
fastboot update PACKAGE.zip
You may need to install drivers in device manager after running the last command
Downloads :
Download
Telegram Groups
My chat
Source Code:
https://github.com/moto-common
Changelog:
Jan 25th 2023: Initial release on XDA
Feb 27th 2023: Pushed Feb update
June 19th 2023: Pushed June patch update
Fix fingerprint gestures for egis
Fix color mode listings
Fix aux cameras
Improve memory management
Improve Wi-Fi 5GHz strength
Numerous other changes
Hi I recently installed this as its the only ROM currently available for my phone that I've seen, and I'm just wondering how would someone go about installing gapps?
DefinitelyDetermined said:
Hi I recently installed this as its the only ROM currently available for my phone that I've seen, and I'm just wondering how would someone go about installing gapps?
Click to expand...
Click to collapse
I have no idea , I just build to provide a base for others to work off of mostly.
DefinitelyDetermined said:
Hi I recently installed this as its the only ROM currently available for my phone that I've seen, and I'm just wondering how would someone go about installing gapps?
Click to expand...
Click to collapse
@Electimon
See the following links:
- https://stackoverflow.com/questions/71001696/how-to-include-opengapps-in-aosp-12-build
Use tau instead of sigma for aosp-13 (in the notes at bottom checked answer)\
- https://github.com/opengapps/aosp_build
- https://www.droidwin.com/how-to-download-and-install-android-13-gapps/
Note: Requires a working TWRP
Does this rom bring unlimited google photos???
sdembiske said:
@Electimon
See the following links:
- https://stackoverflow.com/questions/71001696/how-to-include-opengapps-in-aosp-12-build
Use tau instead of sigma for aosp-13 (in the notes at bottom checked answer)\
- https://github.com/opengapps/aosp_build
- https://www.droidwin.com/how-to-download-and-install-android-13-gapps/
Note: Requires a working TWRP
Click to expand...
Click to collapse
Would an outdated twrp version work? There is an unofficial one for Android 11
@Electimon Do you know anything about "range restricted" in Firehose loaders for EDL?
It prevents you from reading (and probably writing?) most partitions in EDL.
If your CID is 0xff or if you have a flag set (which I haven't traced down yet) you can bypass the restriction.
Renate said:
@Electimon Do you know anything about "range restricted" in Firehose loaders for EDL?
It prevents you from reading (and probably writing?) most partitions in EDL.
If your CID is 0xff or if you have a flag set (which I haven't traced down yet) you can bypass the restriction.
Click to expand...
Click to collapse
Yeah thats known, sadly CID partition is signed and the flag is usually burned qfuse in the SoC which is burnt on all retail devices.
Electimon said:
... the flag is usually burned qfuse ...
Click to expand...
Click to collapse
I'm using the Firehose loader size=609,484, MD5=153a904c54963cb21b901b0dd10f0641
I can see that the CID is validated by cert chains.
But I also see lots of stuff like "ssm_flash_cid", "write_cid_store".
I see a bunch of smc (Secure Monitor Calls) and a bunch of SCM (Secure Channel Monitor) calls and functions for reading/writing fuses.
I also see one small function that writes a byte into memory that can disable restrictions.
It seems like a back door, but I haven't seen what activates it.
Would it be possible to use this device tree to make a pixel experience port?
LethalGamer2121 said:
Would it be possible to use this device tree to make a pixel experience port?
Click to expand...
Click to collapse
Yes
Feb 27th 2023: Pushed Feb update
Electimon said:
Feb 27th 2023: Pushed Feb update
Click to expand...
Click to collapse
sound isnt working after update. it started working after i downgraded to the jan release
DefinitelyDetermined said:
sound isnt working after update. it started working after i downgraded to the jan release
Click to expand...
Click to collapse
Thank you for letting me know, it will be fixed soon
DefinitelyDetermined said:
sound isnt working after update. it started working after i downgraded to the jan release
Click to expand...
Click to collapse
Please redownload the same link, ive updated it with the fixed package. Thank you
having an issue where I cant flash it, its saying that it cannot flash
>fastboot update aosp_borneo-img-Feb-Week4.zip-------------------------------- - Pastebin.com
Pastebin.com is the number one paste tool since 2002. Pastebin is a website where you can store text online for a set period of time.
pastebin.com
if you want to reach out to me quickly, DM me on discord, Merith#5829
merith-tk said:
having an issue where I cant flash it, its saying that it cannot flash
>fastboot update aosp_borneo-img-Feb-Week4.zip-------------------------------- - Pastebin.com
Pastebin.com is the number one paste tool since 2002. Pastebin is a website where you can store text online for a set period of time.
pastebin.com
if you want to reach out to me quickly, DM me on discord, Merith#5829
Click to expand...
Click to collapse
Use platform-tools r32, in the latest version google broke fastboot update.
Electimon said:
Use platform-tools r32, in the latest version google broke fastboot update.
Click to expand...
Click to collapse
Small problem, phone has fastbootd, bootloader, recovery, and system (system being rom)
when you tell the phone to boot to fastboot, it goes to fastbootd which does not show up in fastboot.exe's list,
but if I send it to bootloader, it shows up
Edit, Updating drivers fixed it, IOBit Driver notified of out of date driver
Electimon said:
Use platform-tools r32, in the latest version google broke fastboot update.
Click to expand...
Click to collapse
Still broken, just differently
It flashed, rebooted, showed the AOSP android boot animation, rebooted then brought me to stock recovery (TWRP not flashed) saying the system was corrupt and could not boot
Reflashing fixed it but I dont have Cell Service (I have an carrier unlocked device on USC network)
merith-tk said:
Still broken, just differently
It flashed, rebooted, showed the AOSP android boot animation, rebooted then brought me to stock recovery (TWRP not flashed) saying the system was corrupt and could not boot
Reflashing fixed it but I dont have Cell Service (I have an carrier unlocked device on USC network)
Click to expand...
Click to collapse
Wipe data in recovery and let me know if its still an issue