Develop Bugs

[Unofficial] TWRP - 2.8.3.0 - Moto 360

Team Win Recovery Project 2.x, or twrp2 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.
Phone look:
Tablet look:
CHANGELOG for 2.8.3.0:
-MTP will now tell the host PC that storage is removed instead of disabling MTP completely
-MTP will now report the correct max file size based on the file system in use to the host PC (may fix transfer of large files)
-Update and improve fix permissions and make fixing contexts optional
-Update SuperSU in TWRP to 2.40 and update install process
-Make TWRP work properly on AArch64 (Nexus 9 is now built in true 64-bit binaries and libraries)
-Attempt to set correct permissions and contexts on all files placed in storage so backups will show in Android
-Fix kernel panic during MTP start on some devices
-Support unicode fonts on devices with True Type Font support
-Fix slider value not showing sometimes (vibration settings page)
-Toggle MTP off during adb sideload to set correct USB IDs
-Reduce library requirements for 5.0 L decrypt
-Other minor fixes and improvements
Note: Starting with TWRP 2.8.2.0 and higher, adb sideload uses a new sideload method originally implemented in AOSP recovery. You will need the latest adb binaries to use sideload in these newer versions of TWRP. The version required is 1.0.32. You can find the version by running "adb version" on your computer. The new sideload feature no longer stores the zip on your device. Instead, a fuse file system is created in RAM and the zip is streamed from your computer. This puts less wear and tear on storage and ensures that large zips will not fill up all of your RAM. The sideload may spit an error on your PC side, but the zip should install just fine on your device.
CHANGELOG for 2.8.2.0:
-Pull in all changes from Android 5.0 lollipop into TWRP
-Add decrypt support for Android 5.0 lollipop encrypted partitions including automatic decrypt when the default_password is in use
-Revert some changes to exFAT that were breaking exFAT support on some devices
-Other minor fixes and updates
Note: At this time we do not have a GUI representation for pattern unlock. You can still decrypt patterns though by translating the pattern dots to numbers. The pattern dots correspond to numbers in the following pattern:
1 2 3
4 5 6
7 8 9
So an upper-case L would translate to a password of 14789 entered on the keyboard. Eventually we plan to add a proper pattern unlock to TWRP but it is a relatively low priority at this point.
CHANGELOG for 2.8.1.0:
-MTP fixes and improvements - you can now copy zips to the root of storage - thanks to _that
-TrueType Font support - optional as it takes up a decent amount of space so may not be available on all devices - thanks to Tassadar
-Temperature support - thanks to bigbiff
-Various other bugfixes and tweaks
CHANGELOG for 2.8.0.1:
-Fix a bug that causes weird graphics glitches and touch issues
CHANGELOG for 2.8.0.0:
-Add MTP support to recovery thanks mostly to bigbiff with a little help from Dees_Troy
-Add command line capabilities - you can now execute various TWRP features via adb instead of the touchscreen
-Add support for color in the console and give error, warning, and highlight lines different colors
-Track backup and restore progress based on file sizes to provide a much more accurate indication of progress
-Improve handling of /misc thanks to mdmower
-Improve setting of time on Qualcomm devices thanks to [NUT]
-Allow using images on slidervalue GUI objects thanks to Tassadar
-Allow using variables and addition and subtraction in variables for easier theming
-Add support for 1440x2560, 280x280, and 320x320 resolutions and update 240x240
-Allow ui.xml file to include additional xml files to help break up the theme and make TWRP easier to maintain
-Other minor fixes and improvements
Over the course of the last year or so, bigbiff has worked to migrate various Java functions from Android's MTP implementation to bring you a fully C++ based MTP implementation that allows you to transfer files to both emulated storage and Micro SD cards. It's confirmed to work on various Nexus devices but we may have to make some changes on other devices to keep Windows happy. Windows is very picky about USB IDs and its drivers. We have tested it on Windows 7 and 8 as well as Ubuntu 14.04 Trusty. MTP is enabled by default, but we do toggle it off and on automatically during certain operations such as if you choose to wipe a storage partition. You can enable or disable MTP under the mount menu in TWRP. For more about what MTP is here.
Note: Due to a weird bug with our MTP setup, you cannot copy a zip file to the root of storage with Windows. You can change the .zip to something else like .txt and then copy it to the root and rename the file back to .zip once it's copied to the device. You can also copy the zip into any subfolder.
Command line support is also now available. You can perform various OpenRecoveryScript commands via the adb shell. Depending on what you are doing you may wish to do a "twrp set tw_mtp_enabled 0" and then reboot to prevent the MTP auto toggle from killing your adb interface. You can use this option to create and restore backups, wipe, install zips, and more. Via adb shell, type twrp followed by a space then enter the OpenRecoveryScript command and hit enter. Find more OpenRecoveryScript commands here.
CHANGELOG for 2.7.1.0:
-Add GUI option to change or repair file systems on individual partitions. The change is destructive so backup your data including internal sdcard first. This option should make it a little easier to migrate a device from ext4 -> f2fs, for instance. You will find this option under Wipe -> Advanced Wipe, then select only one partition and then press the Repair or Change File System button. If a developer has added f2fs support for your device and we don't have it in TWRP, please contact me via PM to arrange for it to be added.
-Various bugfixes to backup and restore
-Improvements to USB storage handling
-Added a class to search for files to make finding the correct brightness file automatic in most cases
-Various other bugfixes and tweaks
DOWNLOAD:
Look in post #2
Most devices can be updated quickly and easily with the TWRP Manager app:
Play Store Link
1) Install TWRP Manager from the Play Store
2) Open TWRP Manager and provide root permissions
3) Hit Advanced->Install Recovery
4) Verify the correct device name on your screen then press Install Recovery if the correct device is showing
OR:
You can find more information and download links on our website!
BUGS:
If you have found a bug, please consider posting it to our github issues log. It's pretty much impossible for us to keep up with the more than 40 threads that we have for the devices that we "directly" support. If you have a significant problem that cannot be answered in this thread, your best bet is to PM me directly, contact us via our website, or find us in our IRC channel below. If you see someone that's struggling, feel free to point it out to us. We need your help to help us keep track of all of our devices! Thanks!
SUPPORT:
This is an unofficial port, if you have issues dont bother them, you bug me.
Live support is available via #twrp on Freenode with your IRC client or just click this link.

Moto 360 Part​
Thread closed so dees_troy can have his official one, go grab that version!!!!!
Download this: 2.8.3.0 with v7 of the 320x290 theme
Put your device into Fastboot mode
Connect to your dongle (here is a guide on that all)
Use the following command "fastboot flash recovery path/to/the/image/you/downloaded.img" without the quotes.
You can either fastboot reboot and then reboot into recovery or fastboot boot the recovery image and have it boot into it.
Flash http://shabbypenguin.com/?developer=Tools&folder=Superuser to gain root
There is no key combo that I've found that would allow directly booting into recovery, so fastboot is still your friend if your rom isnt booting :/.
The gui is offcentered because it is teh smallest one they have and it doesnt match up, the next biggest looked fine except the buttons at teh bottom used to navigate were off screen. I'm pretty terrible with graphics and it would end up worse if i tried, so reach out to twrp themers and the twrp devs to get us a round theme or at the very least a theme that would fit. If you would like to donate in my signature you'll find a magical link that directly supports me being lazy and not finding a real job.
Credits:
My wife for buying me a 360
Hroark for saving the day and helping with TWRP
RootJunky for helping me out with a cable so i could even root and testing
mkaymuzik for working on the 320x290 TWRP theme we will be using
TWRP Team for an amazing recovery.

Ok so in hindsight, this post wasnt needed, so now im going to put my device tree down here because... well i need to have something here right?
Device tree source​
there, now its used... happy now?

Nice Work cant wait to get this installed and the Theme updated

great! Now we need a custom rom

BerndHhn said:
great! Now we need a custom rom
Click to expand...
Click to collapse
Agreed!!!! Has anyone tried flashing this yet?

Gotroot said:
Agreed!!!! Has anyone tried flashing this yet?
Click to expand...
Click to collapse
I did ;P

You do it over? Or use app

Gotroot said:
You do it over? Or use app
Click to expand...
Click to collapse
Im not aware of any app that will flash it on a watch.

Would you mind sharing the fastboot or dd cmd ?
---------- Post added at 10:56 PM ---------- Previous post was at 10:51 PM ----------
Or can you use the script posted here and direct it to the img..

shabbypenguin said:
Moto 360 Part​
Download this: https://mega.co.nz/#!UQ4RwahC!AnFEeNBrGob9NuAyne62OXXW0MiaWeV7kpwrbjSIzjM
Put your device into Fastboot mode
Connect to your dongle (here is a guide on that all)
Use the following command "fastboot flash recovery path/to/the/image/you/downloaded.img" without the quotes.
You can either fastboot reboot and then reboot into recovery or fastboot boot the recovery image and have it boot into it.
There is no key combo that I've found that would allow directly booting into recovery, so fastboot is still your friend if your rom isnt booting :/.
The gui is offcentered because it is teh smallest one they have and it doesnt match up, the next biggest looked fine except the buttons at teh bottom used to navigate were off screen. I'm pretty terrible with graphics and it would end up worse if i tried, so reach out to twrp themers and the twrp devs to get us a round theme or at the very least a theme that would fit. If you would like to donate in my signature you'll find a magical link that directly supports me being lazy and not finding a real job.
Credits:
My wife for buying me a 360
Hroark for saving the day and helping with TWRP
RootJunky for helping me out with a cable so i could even root
TWRP Team for an amazing recovery.
Click to expand...
Click to collapse
Gotroot said:
Would you mind sharing the fastboot or dd cmd ?
---------- Post added at 10:56 PM ---------- Previous post was at 10:51 PM ----------
Or can you use the script posted here and direct it to the img..
Click to expand...
Click to collapse

I use fastboot from my apk tool folder so, so move your recovery.img into your fastboot path ..... My command looked like this " fastboot flash recovery recovery.img" and there you go.

@shabbypenguin could you post screenshots of how it look at the moment? Will start working on a design concept (as discussed).
I also need a ramdisk-recovery.img version of the moto360's twrp and witch theme resolution did you use ?

im using 240x240 as it proved to be far more effective than 320x320, http://imgur.com/WV4G7kb

So I got the Lollipop update but I had flashed this recovery and when I go to install the update it boots me into TWRP How should I go about this ? Flash with TWRP? or reflash stock recovery?

NUGZZ420 said:
So I got the Lollipop update but I had flashed this recovery and when I go to install the update it boots me into TWRP How should I go about this ? Flash with TWRP? or reflash stock recovery?
Click to expand...
Click to collapse
Usually you need to be on stock recovery to flash update so I would think wear would be the same. Unless someone makes a flashable zip, in which case twrp would be able to flash it

fakieskr8333 said:
Usually you need to be on stock recovery to flash update so I would think wear would be the same. Unless someone makes a flashable zip, in which case twrp would be able to flash it
Click to expand...
Click to collapse
I figured it out kinda feel dumb for asking now I haven't done a OTA and a grip its always flashing it.

NUGZZ420 said:
I figured it out kinda feel dumb for asking now I haven't done a OTA and a grip its always flashing it.
Click to expand...
Click to collapse
Haha no big deal. I had a total brain fart the other day and had to lookup how to adb reboot. Turns out I forgot I was on a Mac and needed to add ./ to the front. Its funny BC I always use a Mac lol.

Will TWRP reinstall root like it will on phones?
I lost root when upgrading to Lollipop and cannot get it back by using the fastboot boot boot.img command.

abuttino said:
Will TWRP reinstall root like it will on phones?
I lost root when upgrading to Lollipop and cannot get it back by using the fastboot boot boot.img command.
Click to expand...
Click to collapse
yup, best bet is to flash supersu though.
as a progress update:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Is It Possible To Avoid (Red) "Your Device Is Corrupt..." Message Using CM13?

Is It Possible To Avoid (Red) "Your Device Is Corrupt..." Message Using CM13?
I just completed following the directions to install CM13 (Release) on my new Nexus 5X. It seems no matter how I slice the CM13 installation, I always receive this message during bootup...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
CM13 loads fine after receiving this -- however, once I'm in CM I immediately receive the message:
"There's an internal problem with your device. Contact your manufacturer for details."
I was hoping CM13 would sit cleanly on the device without messages like this. Is there a way these messages can go away?
To be clear, the steps I followed were...
1) Opened the box, started the Nexus 5X, enabled to USB \ ADB modes to let me do things , then...
2) Did: adb reboot bootloader
3) Did: fastboot flashing unlock
4) Grabbed the Nexus Factory Image MTC19V (Android 6.0.1) from here. Put this on the device (flash-all.bat) to make sure I'm starting with the OS that the Cyanogenmod documentation references.
5) Rebooted, back into the bootloader.
6) Installed TWRP Recovery (3.0.2-0) onto the device.
7) Went into TWRP.
8) Did an adb push to get CM13 (Release) and Open GApps (ARM64, Android 6.0, nano) onto the device.
9) Did the standard Wipe \ Factory Reset from TWRP.
10) Installed CM13 (Release) + Open GApps back-to-back.
11) Rebooted, then got the above (Red) message-of-death.
I understand this message can be ignored, but it just seems crappy that I'd have to endure it every time (along with the nagging CM13 message) the device boots up.
Any ideas?
Thanks,
Gary

http://forum.xda-developers.com/nexus-5x/themes-apps/bootloader-theme-material-bootloader-t3298420

I appreciate that... but replacing the warning\error screen with a legitimate-looking one is just sort of masking the issue. Can the core problem of the phone needing to display "Your device is corrupt..." be corrected?
- Gary

garybiscuit said:
I appreciate that... but replacing the warning\error screen with a legitimate-looking one is just sort of masking the issue. Can the core problem of the phone needing to display "Your device is corrupt..." be corrected?
Click to expand...
Click to collapse
If you turn off dm-verity integrity checking in the kernel image you won't get the red corrupt message, but you'll instead get the yellow "can't check for corruption" message. That can be masked as noted earlier, but you can't stop the actual 4 second pause or the fact that it is happening without modifying the bootloader. I don't recall anybody working on that. It is likely bootloader is signed, in which case you might need to delve deeper into the phones boot process, probably the qualcomm modules.

I'm not an Android developer, just a (technical) Android enthusiast. I assume to set the dm-verity integrity checking I'd have to recompile the CM13 source code on my own. I'm not really interested in taking it to that level. I'd just have assumed that the CM13 developers would have already solved this particular problem if they're considering their ROM an official release.
But, even if the CM13 kernel could be adjusted to not do this check... wouldn't you still get the "There's an internal problem with your device. Contact your manufacturer for details." message?
In general I'm just shocked that CM13 users (on the Nexus 5X) are okay with these messages. It sort of flies in the face of elegance.
- Gary

garybiscuit said:
I just completed following the directions to install CM13 (Release) on my new Nexus 5X. It seems no matter how I slice the CM13 installation, I always receive this message during bootup...
CM13 loads fine after receiving this -- however, once I'm in CM I immediately receive the message:
"There's an internal problem with your device. Contact your manufacturer for details."
I was hoping CM13 would sit cleanly on the device without messages like this. Is there a way these messages can go away?
To be clear, the steps I followed were...
1) Opened the box, started the Nexus 5X, enabled to USB \ ADB modes to let me do things , then...
2) Did: adb reboot bootloader
3) Did: fastboot flashing unlock
4) Grabbed the Nexus Factory Image MTC19V (Android 6.0.1) from here. Put this on the device (flash-all.bat) to make sure I'm starting with the OS that the Cyanogenmod documentation references.
5) Rebooted, back into the bootloader.
6) Installed TWRP Recovery (3.0.2-0) onto the device.
7) Went into TWRP.
8) Did an adb push to get CM13 (Release) and Open GApps (ARM64, Android 6.0, nano) onto the device.
9) Did the standard Wipe \ Factory Reset from TWRP.
10) Installed CM13 (Release) + Open GApps back-to-back.
11) Rebooted, then got the above (Red) message-of-death.
I understand this message can be ignored, but it just seems crappy that I'd have to endure it every time (along with the nagging CM13 message) the device boots up.
Any ideas?
Thanks,
Gary
Click to expand...
Click to collapse
Flash attached zip.
View attachment Bootloader_fix.zip

garybiscuit said:
I'm not an Android developer, just a (technical) Android enthusiast. I assume to set the dm-verity integrity checking I'd have to recompile the CM13 source code on my own.
Click to expand...
Click to collapse
Either flash one of the existing custom kernel/boot images with dm-verity disabled for you or flash SuperSU which will do it on the fly.
It doesn't mean recompiling entire CM13 source. The dm-verity check is an option enabled in the mount tables. Disabling involved unpacking the boot.img into kernel and mini filesystem, editing the mount table to remove the option, then repacking the kernel and mini filesystem. People have already done this for you or you can install SuperSU and it will do it for you.
Keep in mind, this won't get rid of the message or the pause, it'll just change the message from RED corrupt to YELLOW can't check for corruption.
If you don't like either message, best you can do is mask it.
The 4 second pause though will still be there as that would probably require the bootloader itself be modified rather than just the appended images.

glehel said:
Flash attached zip.
View attachment 3809902
Click to expand...
Click to collapse
Thanks here... but what is this .zip and how do I flash it?
- Gary

garybiscuit said:
Thanks here... but what is this .zip and how do I flash it?
- Gary
Click to expand...
Click to collapse
Boot Twrp recovery

garybiscuit said:
Thanks here... but what is this .zip and how do I flash it?
Click to expand...
Click to collapse
It appears to be replacing the RED corrupt image with something more legitimate looking, which, when suggested earlier, is what you didn't want to do.

Yeah... that's just kind of a cludgy workaround in my opinion. Though I appreciate the effort there.

garybiscuit said:
Yeah... that's just kind of a cludgy workaround in my opinion. Though I appreciate the effort there.
Click to expand...
Click to collapse
What did you expect? you open the bootloader, you use a non-factory system. might even with encryption turned off.
A google so declare his displeasure.
https://support.google.com/nexus/answer/6185381?p=verified_boot

I feel like an alternate ROM with the reputation of Cyanogenmod should have the annoyances that subtract from it's seamlessness worked out. That's what I expect.

I had a similar message after an update and found that I forgot to flash vendor.img. I don't use CM, but perhaps you need to fastboot flash vendor vendor.img. If you were only getting the message during the initial boot, before the android logo animation, that would be different, but since you're getting it inside android after the phone boots, this could be the culprit.
dd

garybiscuit said:
I feel like an alternate ROM with the reputation of Cyanogenmod should have the annoyances that subtract from it's seamlessness worked out. That's what I expect.
Click to expand...
Click to collapse
In this "trusted boot" world, CM will probably need to start signing their ROMs, building merkel-trees, and getting their keys distributed with the phone, but I imagine this might be difficult for them to do given the open nature of their builds and the lack of trust.

[ROM][UNOFFICIAL][N][UsU]CypherOS 4.2 [H815]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This is Cypher. An extension to pure Android. Cypher tries maintain the purity of Android while offering useful features for users. The goal is to give the highest level of performance whilst achieving Simplicity.
Code:
/*
* 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.
*/
**** These builds are for UsU'd devices only ****
UsU? http://bit.do/unlockg4
Get your builds from my leech service
http://leech.binbash.rocks:8008/aoscp/nougat/h815-UsU/
Note: Builds are updated as soon as possible. There is no build cycle.
Information pertaining to your device is displayed accordingly.
The current build is the latest for your device.
Become apart of our G+ community - JOIN
REMINDER
If you're having issues and want to submit a report (Logcat) please make sure you are reporting from the stock kernel, not a modified kernel. Modified kernels can break or fix, even improve things. It depends. I can't get a full clue of the issue when you're not running the original kernel.
Click to expand...
Click to collapse
​
Features:
- Status bar Customization
- Changeable icons
- Quick pulldown
- Smart pulldown
- Notification count
- Clock position
- Seconds in clock
- Date design
- Quick Settings
- Brightness slider
- Brightness icon
- Tile tap customization
- System
- Screenshot partial and full
- Scrolling cache customization
- Power menu customization
- One-handed mode
- Specials
- UsU compatible build so no need for a baseband package to be flashed!
- Using latest TITAN kernel sources
Requirements
Your device need to be unlocked by UsU
Your bootloader stack should be on MM (see FAQ #20 for how to upgrade your bootloader stack)
Latest TWRP - PREVIEW build: click
Clean modem partition (so no UsU baseband flashed) - see Installation topic for details
Installation
If you have ever flashed the UsU baseband package: Clean flash the modem partition in TWRP:
- TWRP flashable N modem (recommended)
Full wipe like described here (click & go to FAQ "#zzz") is highly recommended. DO NOT REPORT ISSUES when you have skipped that step!
Flash AOSCP
Flash GApps (7.1 - ARM64) if you like to use google apps
Flash SuperSU / Magisk if you want root
Boot (will take long on first boot!)
Enjoy
Credits
LineageOS
AICP
PureNexus
AOKP
Dirty Unicorns
Paranoid Android
kessaras
steadfasterX
and more..
Sources
Kernel
device tree

reserved 1

reserved 2

Error Status 7
Using lastest TWRP preview, I get the above error.
I know to fix it I just need to delete the "assert" line in the .zip, but I thought this ROM (UsU's supported) had the model that TWRP show.
I mean, the model according to;
(*) TWRP: LGUSU
(*) ROM (assert): p1, h815, h815_usu & g4 (not 'LGUSU' as shown in TWRP).
Thanks!

the_naxhoo said:
Error Status 7
Using lastest TWRP preview, I get the above error.
I know to fix it I just need to delete the "assert" line in the .zip, but I thought this ROM (UsU's supported) had the model that TWRP show.
I mean, the model according to;
(*) TWRP: LGUSU
(*) ROM (assert): p1, h815, h815_usu & g4 (not 'LGUSU' as shown in TWRP).
Thanks!
Click to expand...
Click to collapse
correct the removal of that line is not needed but i can see that the model detection is wrong on your device.
Please share the recovery log file!
Sent from my LG-H815 using XDA Labs

steadfasterX said:
correct the removal of that line is not needed but i can see that the model detection is wrong on your device.
Please share the recovery log file!
Sent from my LG-H815 using XDA Labs
Click to expand...
Click to collapse
OK. Here is the recovery.log

ROM works great. Very smooth with no bloatware.
Just one problem, when setting the lockscreen type in security it doesn't seem to apply correctly. I have set it to "pattern" but it keeps defaulting back to swipe. I then tried to set it to PIN and it just crashes when I go back into lock screen settings now.

the_naxhoo said:
OK. Here is the recovery.log
Click to expand...
Click to collapse
ok the reason is clear:
download: https://androidfilehost.com/?fid=746010030569958479
extract it
flash in fastboot:
Code:
fastboot flash laf laf_UsU.img
fastboot flash raw_resources rawres_UsU.img
Then boot into TWRP again and share the recovery log again.
Rich Rich said:
ROM works great. Very smooth with no bloatware.
Just one problem, when setting the lockscreen type in security it doesn't seem to apply correctly. I have set it to "pattern" but it keeps defaulting back to swipe. I then tried to set it to PIN and it just crashes when I go back into lock screen settings now.
Click to expand...
Click to collapse
seems to be a known issue for some rare cases.
I cannot reproduce it here it works fine so far.
Have you clean flashed ? Format(!) data as written in the OP?

steadfasterX said:
ok the reason is clear:
download: https://androidfilehost.com/?fid=746010030569958479
extract it
flash in fastboot:
Code:
fastboot flash laf laf_UsU.img
fastboot flash raw_resources rawres_UsU.img
Then boot into TWRP again and share the recovery log again.
Click to expand...
Click to collapse
lol its worked... thx!

steadfasterX said:
seems to be a known issue for some rare cases.
I cannot reproduce it here it works fine so far.
Have you clean flashed ? Format(!) data as written in the OP?
Click to expand...
Click to collapse
Yes, did the "format data" wipe before install.
It may be a slight difference in the way I set the device up. I did select "pattern lock" when I first installed the OS. I noticed this was not working then re-set "pattern lock" in settings a few times but nothing worked. I then tried setting it to "pin lock" and now it just crashes the settings app every time I try to change the security.
It's not a big issue for me as the G4 is just used as a work phone. I'll flash the next build when available and see if that sorts the problem.

Rich Rich said:
Yes, did the "format data" wipe before install.
It may be a slight difference in the way I set the device up. I did select "pattern lock" when I first installed the OS. I noticed this was not working then re-set "pattern lock" in settings a few times but nothing worked. I then tried setting it to "pin lock" and now it just crashes the settings app every time I try to change the security.
It's not a big issue for me as the G4 is just used as a work phone. I'll flash the next build when available and see if that sorts the problem.
Click to expand...
Click to collapse
oh well i have tried PIN only.. sorry havent read carefully. will try the pattern thing..

Hello thanks for all of your efforts I follow your toppic for long time and finally yesterday I unlocked my h815tr device successfully. And I flash the ROM you shared in this topic. All works fine thanks again. I just have a problem about Yahoo mail account. I can't add it to my Gmail app. I enter my mail and password I allow the permissions about mail and at final step screen shows 404 can't found. But I solve this by using Yahoo's mail app. But it would be good if I can use Gmail app. And I realised that if I take a photo and immediately if I tap to photo I took the camera app crash but if I wait few seconds and then if I tap the photo it's all ok. I'm not complaining don't get me wrong, again thank you so much.

Is this ROM support quick charge? Because when I plug to QC adapter, phone says slow charging. Original adapter says slow charging also

emrtnl said:
Is this ROM support quick charge? Because when I plug to QC adapter, phone says slow charging. Original adapter says slow charging also
Click to expand...
Click to collapse
slow charging is everywhere due to power hal and due to our sources.
In the rom to show if its fast normal or slow it needs to read the voltage not the ampere. but in kernel we read no voltage. we only read the ampere.
Totally stupid since its the ampere that matters , but thats how things work there.
EDIT:
i mean it's always showing slow for the reason i explained , but it's not.

kessaras said:
slow charging is everywhere due to power hal and due to our sources.
In the rom to show if its fast normal or slow it needs to read the voltage not the ampere. but in kernel we read no voltage. we only read the ampere.
Totally stupid since its the ampere that matters , but thats how things work there.
EDIT:
i mean it's always showing slow for the reason i explained , but it's not.
Click to expand...
Click to collapse
Thanks for that information. At v29 ROM previously I use I could see quick charging notification, that's why I asked.

emrtnl said:
Thanks for that information. At v29 ROM previously I use I could see quick charging notification, that's why I asked.
Click to expand...
Click to collapse
stock lg stuff handle many things differently from the open source.
but we do not have access there, only LG has.
What we do in this side of development is to work with the open source.
LG rom may read the ampere. Or they may have added a voltage reading. We do not know...

have done all steps but reboot into twrp always (((

floast said:
have done all steps but reboot into twrp always (((
Click to expand...
Click to collapse
I had the same problem.
While in TWRP go to Advanced, then select Terminal
type this command:
Code:
dd if=/dev/zero of=/dev/block/bootdevice/by-name/fota
keep in mind that there's a space before if and before of, like below replaced with underscores:
dd_if=/dev/zero_of=/dev/block/bootdevice/by-name/fota
If you don't get an error, just reboot the phone and it will go into the system.
I found this solution here and adjusted it a bit:
https://forum.xda-developers.com/showthread.php?t=2451696
---------- Post added at 03:24 PM ---------- Previous post was at 03:06 PM ----------
#EDIT: Ok, so funnily enough, me helping the guy above also risked having him screw his mac address up the same way I describe as a separate problem below Looks like we need to adjust he process below to our model:
https://forum.xda-developers.com/showpost.php?p=70474540&postcount=12
Sorry for being clumsily underqualified, everyone.
#EDIT2: A better and easier solution that might work for us:
https://forum.xda-developers.com/lg-g3/development/fix-stuck-custom-recovery-trying-ota-t2907508
And now my own problem. I cannot connect to any WiFi network and noticed that my mac address is 00:00:00:00:00:00.
I stays that way even if I do the whole process again: format data, flash the rom, flash the gapps, flash supersu.
After I reboot into the system and wait for it to initialise and enter the initial phone config, where it asks me to connect to a WiFi network I can see my zeroed out mac address at the bottom. If I try to connect to a 5G wifi network or 2.4G one it says "Connecting" and then just displays "Saved" under the selected network. It doesn't ever connect. I checked one 5G network and two different 2.4G networks, triple-checking the password each time.
In "settings>about phone>status>WiFi MAC address" I also see 00:00:00:00:00:00.
I checked /system/etc/wifi/bcmdhd.cal file and the attribute there seems normal:
Code:
macaddr=00:90:4c:c5:12:38
I've seen in a thread concernig a different phone that some people advise to put the desired mac address into a /system/etc/wifi/.mac_info file and reboot but this doesn't work (might be dumb to even try that but it didn't hurt so I gave it a shot).
I wanted to try working around the issue using a mac address changer app off of Play Store but I can't connect to any Google Account (in the settings or any Google app), even on the cellular data - seems like the authentication looks at my mac and doesn't like it.
I considered finding and sideloading an apk of some mac address changer app, but that's doesn't seem like a viable solution - people say it only works temporarily and I'm not even sure if that will fool Play Store authentication if it really does rely on mac add somehow.
Any ideas where else the system might be pulling that 00:00:00:00:00:00 from or where the mac is missing?
Does fixing the mac issue might also fix the Google Services authentication problem?

Derpthunder said:
I had the same problem.
While in TWRP go to Advanced, then select Terminal
type this command:
keep in mind that there's a space before if and before of, like below replaced with underscores:
dd_if=/dev/zero_of=/dev/block/platform/soc.0/f9824900.sdhci/by-name/fota
Also, the soc.0/f9824900.sdhci/ part might be different in your case. If after typing the above command you'll get an error saying that there's no such file, type these commands:
And it will tell you if you have soc.0 or something else. Then type (if you had something else than soc.0 in the previous step, replace soc.0 with what it told you)
and you'll see what you have instead of f9824900.sdhci
Once you know what you have instead of soc.0/f9824900.sdhci/, just type that command again replacing that section:
If you don't get an error, just reboot the phone and it will go into the system.
I found this solution here and adjusted it a bit:
https://forum.xda-developers.com/showthread.php?t=2451696
Click to expand...
Click to collapse
That's why
/dev/block/bootdevice/by-name/
exists. It's always pointing to the correct SOC path.
Sent from my LG-H815 using XDA Labs

steadfasterX said:
That's why
/dev/block/bootdevice/by-name/
exists. It's always pointing to the correct SOC path.
Sent from my LG-H815 using XDA Labs
Click to expand...
Click to collapse
Thanks, I edited the post to add the correction.
#EDIT: I don't quite remember if I actually overwrote the fota or the misc to get out of booting into TWRP loop. The G2 and G5 threads advise to overwrite the misc and the G3 one to overwrite fota. Is there a difference?
Plus, I added this since it turned out that my mac problem was due to that exact fix I recommended:
Derpthunder said:
#EDIT: Ok, so funnily enough, me helping the guy above also risked having him screw his mac address up the same way I describe as a separate problem below Looks like we need to adjust he process below to our model:
https://forum.xda-developers.com/sho...0&postcount=12
Sorry for being clumsily underqualified, everyone.
#EDIT2: A better and easier solution that might work for us:
https://forum.xda-developers.com/lg-...g-ota-t2907508
Click to expand...
Click to collapse

[ROM][RAV*][SOFIA*][11][UNOFFICIAL] DISCONTINUED

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Havoc-OS 4.x is based on AOSP, inspired by Google Pixel.​Has a refined Material Design 2 UI crafted by @SKULSHADY.​Many useful features that will blow your mind.​All you can dream of and all you'll ever need.​Just flash and enjoy...​
Code:
[SIZE="3"][SIZE="3"][B][U]General:[/B][/U][/SIZE]
Material Design 2 UI
Android R Style Screenrecord Dialog
Rounded UI
Inbuilt GApps (optional)
Face Unlock
Enhanced QS Battery Estimation
Lockscreen Clocks
Font Customisation
Dark Theme Support for AOSP apps
Notification LED Settings
Pixel Lockscreen weather
Signature Spoofing
Micro-G support
Lockscreen charging animation
[SIZE="3"][B][U]Status Bar:[/B][/U][/SIZE]
Clock & Date Settings
Custom Logo
Brightness Control Gesture
Double Tap to Sleep
Network Traffic Indicator Settings
Carrier Label Settings
Battery Icon Style/Percentage Settings
Status Bar Icons Toggle
HD/VoLTE Icon Toggle
4G/LTE Icon Toggle
Data Disable Icon Toggle
Roaming Indicator Toggle
Small Mobile Type Icon Toggle
Bluetooth Battery Status Toggle
[SIZE="3"][B][U]Quick Settings:[/B][/U][/SIZE]
Quick Pulldown
Smart Pulldown
Battery Estimates Toggle
Background Opacity
Background Blur Configuration
Header Image Configuration
QS Customisations
Rows/Column
Tile Title
Vibrate on Touch
Brightness Slider Customization
Brightness Slider On Bottom/Top/Hidden
Auto Brightness Icon
Brightness Control Buttons
QS Footer Customization
Settings Icon
Running Services Icon
Edit Icon
User Switcher Icon
[SIZE="3"][B][U]Ambient Display:[/B][/U][/SIZE]
Show/Hide Battery Level
Ambient Options
Always On
Always On When Charging
Wakeup On New Notifications
Wakeup on New Music (Music Ticker)
Sensor Based Screen Wakeup (Tilt/Hand Wave/Pocket)
Double Tap for Ambient Display
Ambient/Always On Display Brightness Configuration
[SIZE="3"][B][U]Screen:[/B][/U][/SIZE]
Corners Customisation
Rounded Corner Radius
Corner Content Padding
Legacy App Scaling
Force Higher Aspect Ratio for Selected Apps
[SIZE="3"][B][U]Buttons:[/B][/U][/SIZE]
Navigation
Nav Bar Toggle
System Navigation Type
Arrows Keys
Volume Buttons
Swap Keys
Volume Steps
Long Press to Seek Tracks
Keyboard Cursor Control
Volume Rocker Wakeup
Volume keys Answer Call
Power Button
Power Menu Customization
Lockscreen Options
Visibility on the Lockscreen
Reboot
Advanced Reboot
Screenshot Option
Screenrecord
Screen-Off Torch
Double Tap Power Button
Long Press Power Button
Back Gesture
Arrow Animation toggle
Long Swipe Type (Swipe and Hold/Swipe Edge to Edge)
Long Swipe Timeout
Long Left/Right Swipe Action
Haptic Feedback toggle
[SIZE="3"][B][U]Gestures:[/B][/U][/SIZE]
Jump To Camera
System Navigation Settings
Prevent Ringing Gesture
Swipe To Screenshot
Touchscreen Gestures
[SIZE="3"][B][U]Lockscreen:[/B][/U][/SIZE]
Double Tap to Sleep
Media Cover Art
Media Cover Art Blur Level
Music Visualiser
Unlocking
Pocket Detection
Fingerprint
Screen Off FOD
Show Icon
Recognizing Animation
FP Authentication Vibration
FP error Vibration
Elements Customisation
Status Bar
Quick Settings
Lock Icon
Charging Info
[SIZE="3"][B][U]Notifications:[/B][/U][/SIZE]
Flashlight
Blink for incoming call
Blink for Call Waiting
Screen
Edge Lighting Customisation
Status Bar
Heads Up
System
FC Notifications
Misc
Kill App Button
Noisy Notifications
[SIZE="3"][B][U]Animations:[/B][/U][/SIZE]
Animation Duration
System Animation customization
QS Tile Animation Customisation
[SIZE="3"][B][U]Battery Saving:[/B][/U][/SIZE]
Smart Pixels
Suspend Actions
[SIZE="3"][B][U]Miscellaneous:[/B][/U][/SIZE]
Gaming Mode
Wake Up on Charge
Charging Animation
Screenshot Type (Full/Partial)
Adaptive Playback
Playback Timeout (30sec/1min/2min/5min/10min)
[SIZE="3"][B][U]Other Features:[/B][/U][/SIZE]
Vibration & Haptics Customization
LiveDisplay
Notch Hide Settings
Seperate ringtone for SIM1&2
Screen Refresh Rate (For Supported Devices)
ALways On Display
Smart Charging
Theming
Styles and Wallpapers
Dark Theme
Accent Colour
Icon Shape
[SIZE="3"][B][U]QS Tile Shortcuts:[/B][/U][/SIZE]
Heads Up tile
Caffeine tile
CPU info tile
Smart pixel tile
Live Caption
Screenrecord tile
Gaming Mode tile
Screenshot tile
LTE tile
Music Tile
LiveDisplay
Switch Data Card Tile
Reboot Tile
Reading Mode
Gaming Mode
Compass
Sound Search
Compass Tile
[/SIZE]
https://photos.app.goo.gl/WSbmYy7QeB6K9CSn6​
Founder & Lead Developer:​SKULSHADY (Anushek Prasal)​​Support Team:​theo.j22 (Tushar Jain)​​
If you like our work then please consider donating.​PayPal: https://www.paypal.me/ANUSHEK​UPI: [email protected]​Maintainer PayPal: https://www.paypal.me/ANUSHEK
Open GApps: http://opengapps.org
Magisk: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Telegram Support Group: https://t.me/havocofficial
Telegram Announcements Channel: https://t.me/Havoc_OS
Discord Server: https://discord.gg/YfhBCj4[/SIZE][/INDENT]
LineageOS (https://github.com/LineageOS)​Crdroid (https://github.com/crdroidandroid)​Pixel Experience (https://github.com/PixelExperience)​Nitrogen Project (https://github.com/nitrogen-project)​Omnirom (https://github.com/omnirom)​And all the other Developers, Testers, Donators and Users.​
https://github.com/Havoc-OS​https://github.com/Havoc-Devices​
Device Trees: https://git.asineth.gq/android_device_motorola_sofiar/
Vendor Trees: https://git.asineth.gq/android_vendor_motorola_sofiar/
Kernel Trees: https://git.asineth.gq/android_kernel_motorola_trinket/
A million Thank You's to @vache and @asineth for their hard work on the trees used to build, and @Rooted_Ansh and @kgvarunkanth for answering all my noob questions :silly: and @niaboc79 for the inspiration to make my own stuff :good:
Install Steps in Post #2.
Download Links in Post #3.
KNOWN BUGS:
Let me know!

To Install:
1. Extract the zip and open a shell with ADB and fastboot.
2. Reboot your device into fastbootd mode.
Code:
fastboot reboot fastboot
3. Flash boot, system, product, and vbmeta.
Code:
fastboot set_active a
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash product product.img
fastboot flash vbmeta vbmeta.img
4. Wipe userdata.
Code:
fastboot -w
To install via TWRP:
1. Install stock firmware, complete one OTA update, then install TWRP in fastboot.
Code:
fastboot flash recovery TWRP.img
fastboot flash recovery_b TWRP.img
2. Format data in twrp, not wipe, format!
3.1. For GAPPS build, flash the rom, reboot, profit.
3.2. For Vanilla builds (if you want to install your own gapps) flash the rom, reboot to recovery, flash flame gapps basic package, reboot to system. If you dont want gapps, flash the Vanilla rom zip, reboot, profit.
4. If you want magisk, flash it in TWRP after booting the phone to the launcher homescreen once.

ROM Download Links
19-9-20 (Initial) Build - No GApps, Screen Recording Causes Reboot, ADB Broken
https://drive.google.com/file/d/1-ztGP-YYJRzRB8p-bLuMl3YWDw7mawm8/view?usp=sharing
20-9-20 Build - GApps Included, ADB Access Fixed, Screen Recording The Same
https://drive.google.com/file/d/16xXU4gbKOhcsNVOQREidrDeUDrnZN8jC/view?usp=sharing
10-11-20 Build - Updated to 3.11, November security patch. New boot.img included with hotspot fix and twrp decryption support (thanks vache and odin and samuel). GAPPS still included. Clean install recommended.
https://drive.google.com/file/d/1PfPLco3pcfJ-x-uBDuBWVMffY4vySorx/view?usp=sharing
21-11-20 Build - Still 3.11, Nothing new, No GAPPS build.
https://drive.google.com/file/d/1HZg7jNw5COVDiKbCw5Wfpd6OP95eqxNO/view?usp=sharing
22-12-20 Build - Updated to 3.12, December security patch. Added the working screen recorder to system and removed the old broken one.
No Gapps Build
Gapps Included Build
23-6-21 Build - HavocOS 4.6!!!
Fixed screen recorder, fixed screen cast/mirroring (gapps build/vanilla with gapps installed), added Moto Camera 2 and Moto clock widgets, kernel upstreamed to .236 with kcal patches added, color control app added to tweak colour/saturation, June security patch. GAPPS and Vanilla builds, TWRP zips and Fastboot D images.
https://drive.google.com/drive/folders/1zhgC1r-FxnobhCG_CyO7aLbvMz8iiFMh?usp=sharing
07-08-21 build
Havoc-OS v4.8
Rebased to omni device trees.
Kernel upstreamed to 4.14.240
Tap to wake working.
(Stylus model only) Stylus should be working, may need to reopen stylus settings from time to time.
FM radio is BROKEN
Havoc-OS-v4.8 - Stylus Test - Google Drive

Reserved

Thanks for building my one of my old favorites that I used on my old S5 Downloading now. Tried CR and it was nice but no LTE data. Omni had working LTE data so I don't understand why CR wouldn't have.
Anyway, I'll post as soon as I have it going and test a few things. I can test 3g only here at home though.
Thanks again. I was going to try to build this one myself after I get a capable machine. Or maybe a google test drive which is what one guy used to do to build for the S5.
Why Include GAPPS though? Also iif you used your home machine to build what are the specs for your box?
My lappy is about shot and I'm trying to hold out until Black friday, but may just go ahead and get a weaker lappy and build a nice ryzen box for home server use and to learn to build ROMS and kernels.

Tried to flash on top of CR and when I got to product, it failed during the 2nd or 3rd section. I tried doing the product image many times and it failed but didn't say it's ran out of space.
Could that be my issue? I'm the how to for gsi's there are instructions shot what to do if flashing system fails.
Any ideas?
Sent from my Moto G Stylus using XDA Labs

One of the screen shots shows color calibration settings including adjusting saturation. Is that working on this phone? I know it's a kernel issue. If so, I'll install this Rom just for that. Increasing the saturation on an LCD screen makes it so much better. And adjusting the rgb values eliminates burn in.
Thanks!

androiddiego said:
One of the screen shots shows color calibration settings including adjusting saturation. Is that working on this phone? I know it's a kernel issue. If so, I'll install this Rom just for that. Increasing the saturation on an LCD screen makes it so much better. And adjusting the rgb values eliminates burn in.
Thanks!
Click to expand...
Click to collapse
The rgb adjustment is availiable, saturation no. Just the options like stock for boosted or saturated.

can't seem to get it flashed.. error occurs when running "fastboot flash system system.img" all I get is "FAILED to resize partition" any ideas?

MadMan29729 said:
can't seem to get it flashed.. error occurs when running "fastboot flash system system.img" all I get is "FAILED to resize partition" any ideas?
Click to expand...
Click to collapse
I finally got it going on my stylus using big red. So far so awesome but so was CR at this point. This point being living in an area with only 3g and no LTE so I can't test that. I think it's only Verizon where that happens anyway.
So far it seems more similar to Omni (where LTE worked) than CR.
I know that's a little woo-woo.
It could be that I flashed over the stock rom both with Omni and Havoc. I know that even though when flashing images the entire partition is used but other partitions may get written to by the OS that are not wiped with the factory reset. Just shooting from the hip here so tags it with a grain of salt.
Also if you read the thread about flashing GSIs there is a command that is used to resize
Double check but I think the command is.
Edit: I don't know the fancy code tag probably [code. The code words /code]
Anyway here:
fastboot delete-logical-partition product _a(or the letter of the slot you're flashing to) double check the post though to be sure. Even then I'd still verify the command with some quick searching.
I'll figure this stuff out yet.
Sent from my Moto G Stylus using XDA Labs if I was helpful to you hit the thanks button for me I appreciate it.

Vibration/Haptic fixed kernel. Flash in fastboot:
Code:
fastboot flash boot <filename.img>
https://drive.google.com/file/d/1I9gK9qxJJAy5R2cqH7tRZM9OCYE65mmB/view?usp=sharing

You guys may already know but LTE dara works just find with Verizon
It didn't on CR which is the reason for this post, Omni, and Havoc had everything when big red wording except wifi calling which never used to be possible but I think it is after some modification, just gotta find em..
Much appreciation. And thanks to all developers involved.
Edit: I usually have to reboot to get LTE data not sure why and I'm not sure using airplane mode works instead of a reboot in fact I'm pretty sure a reboot is needed. I'm not on the updated kernel BTW.
Sent from my Moto G Stylus using XDA Labs

Junior Member
22 posts
Thanks: 3
I've tried flashing omni multiple times and tried to flash havoc once last night. I finally figured out what the error is:
ok so everything flashes fine but when i run fastboot -w i get:
"erase successful but not automatically formatting..."
Then it goes on to say something about the filesystem being raw.
The only thing I can think of that I've come across after searching is that my adb might need updating. I've been using minimal adb 1.43 because when I try to open adb through platform tools the window will open then immediately close. Will someone tell me what I'm doing wrong or how to run abd.exe from platform tools. I uninstalled minimal adb and made sure platform tools was the only adb version I had on my computer. I also installed the universal adb driver for windows.
*edit*
I figured it out. so i installed the latest version of adb and figured out how to properly open it but it still gave me the same error. so after that error i ran the command fastboot erase userdata, restarted and it booted into havocos just fine!

Quick question:
I flashed HavocOS to my phone but needed to go back to stock. In fastboot though the only files it's letting me flash are boot, system, product, and vbmeta. Any other file I try to flash it gives me an error. I can't remember the exact error because I'm not by my computer but is something along the lines of send successful but writing failed.
I did some searching and people with the same problem solved it by moving it to a USB 2.0 port. I didn't check which USB version I have but I'm fairly sure they're 2.0. and also I didn't think that mattered in my case because why would it let me flash those 4 files (the same type of files I flashed to install havoc) and not any of the other ones. That's why I'm thinking it's not a USB 2.0 issue

Tried flashing this to my Moto G stylus every time I get a error on system and product
---------- Post added at 04:39 PM ---------- Previous post was at 04:38 PM ----------
I keep getting an error on system and product when I flash is can you please help
---------- Post added at 04:46 PM ---------- Previous post was at 04:39 PM ----------
Every time I flash is it get an error on system and product it says bootloader pre something failed
---------- Post added at 04:46 PM ---------- Previous post was at 04:46 PM ----------
I know what it was now bootloader free verification failed on system and product can someone help me

jdg007 said:
Tried flashing this to my Moto G stylus every time I get a error on system and product
---------- Post added at 04:39 PM ---------- Previous post was at 04:38 PM ----------
I keep getting an error on system and product when I flash is can you please help
---------- Post added at 04:46 PM ---------- Previous post was at 04:39 PM ----------
Every time I flash is it get an error on system and product it says bootloader pre something failed
---------- Post added at 04:46 PM ---------- Previous post was at 04:46 PM ----------
I know what it was now bootloader free verification failed on system and product can someone help me
Click to expand...
Click to collapse
You need to be in fastbootd, not fastboot.

bigrooster88 said:
Junior Member
22 posts
Thanks: 3
I've tried flashing omni multiple times and tried to flash havoc once last night. I finally figured out what the error is:
ok so everything flashes fine but when i run fastboot -w i get:
"erase successful but not automatically formatting..."
Then it goes on to say something about the filesystem being raw.
The only thing I can think of that I've come across after searching is that my adb might need updating. I've been using minimal adb 1.43 because when I try to open adb through platform tools the window will open then immediately close. Will someone tell me what I'm doing wrong or how to run abd.exe from platform tools. I uninstalled minimal adb and made sure platform tools was the only adb version I had on my computer. I also installed the universal adb driver for windows.
*edit*
I figured it out. so i installed the latest version of adb and figured out how to properly open it but it still gave me the same error. so after that error i ran the command fastboot erase userdata, restarted and it booted into havocos just fine!
Click to expand...
Click to collapse
mine is doing the same thing, after installing i get that message about filesystem raw and it never boots it just goes to normal fastboot everytime, i tried doing the command fastboot erase userdata, and after reboot it still took me to fastboot mode.. where did i go wrong?

I got the flash itch and installed this on my stylus and my only gripe is I can't use adblocker file via /system/bin adaway is my backup. no issues to report so far.
To install very easy, need CPU,mouse,otg cable,moto stylus
extract ROM zip to any folder you want
delete boot. IMG and replace with op updated fixed boot. IMG
open command prompt and CD to your ROM extracted folder
with updated adb, fast boot exe files,
hold power plus volume down buttons until phone reboots into fastboot mode
Important,,, in command prompt type ,,fastboot reboot fastboot,, hit enter
phone will take 10 seconds to boot into , fastbootd,,
you will see a red menu saying Fastbootd,,
now copy paste the op's install commands
(fastboot set_active a
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash product product.img
fastboot flash vbmeta vbmeta.img)
hit power button when installation is complete.
bam ..
too install gapps I use pico arm 64
after a sucesseful boot up reboot into fastboot via button combination
extract twrp into any folder you want
open command prompt inside twrp folder
type fastboot boot recovery twrp.IMG (name of twrp image)
wait a second once you see the blue moto screen immediately remove cord from phone and input otg cable with mouse ..
phone will be in twrp menu and you can use the mouse to navigare in the menus to install gapps and magisk or all your zips..
bam

any fix for the crash when turning off hotspot?

CorporalCactus said:
mine is doing the same thing, after installing i get that message about filesystem raw and it never boots it just goes to normal fastboot everytime, i tried doing the command fastboot erase userdata, and after reboot it still took me to fastboot mode.. where did i go wrong?
Click to expand...
Click to collapse
Try not erasing or formatting any storage and see what it says. Also what version of adb are you using?
Download from here
https://developer.android.com/studio/releases/platform-tools#downloads
Delete all old adb files and exe's from pc and use the files you just downloaded.
Sorry it took so long for a response I was gone for a few weeks.

Development [ROM][OFFICIAL][13] StatiXOS v6.2 [alioth/aliothin]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
StatiXOS for Redmi K40 | Mi 11X | POCO F3 (alioth/aliothin)​
What is StatiXOS?
StatiXOS is a custom ROM based on the Android Open Source Project aiming to be minimal while providing quality of life improvements and up to date security patches.
Spoiler: Known Issues
Changing the intensity of haptics does not work.
Battery stats in Settings show nothing.
Please report anything else you run into!
Spoiler: Download StatiXOS Here!
Primary
Spoiler: How To Flash
Detailed Flashing instructions in Post #3
Download the fastbootimage zip
Unlock your bootloader, and reboot to bootloader
Type in
Bash:
fastboot format:f2fs --fs-options=casefold,projid
[This will format all of the data in your phone including internal storage (photos, files, everything!)] (Skip this step if you are coming from a previous build)
Connect your phone to PC and type in
Bash:
fastboot update statix_alioth-XXXXXX-13-v6.1-TIRAMISU-img.zip
(XXXXXX denotes the date of the build)
Wait for a while until the flashing process completes, it will reboot your device
Enjoy!
Note: This ROM has GApps!
Spoiler: Stay in touch with our Telegram channels!
Official Releases & Announcements Channel
Android version: 13
Linux Kernel Version: 4.19.157
Source code: GitHub
Kernel Source code: GitHub
Code Review: Gerrit

Changelogs
6 February 2023
Initial build
7 February 2023
February 2023 Security patch
11 February 2023
Fixed missing smartspace.
Fixed camera not working with 3rd party apps.
Some under the hood micro-optimisations on top of android bionic.
23 April 2023
April Security Patch
Upgraded blobs to MIUI 14.x
Better pickup sensor implementation
Multi-Gen LRU enabled by default
Several Battery optimisations
5 May 2023
May Security Patch
Fixed the random reboot issues faced by some users

Detailed Flashing instructions:
NOTE: These instructions are for first time users only! If you are upgrading from previous StatiX Builds, you DO NOT NEED TO FORMAT DATA!
To flash StatixOS, you need these pre-requisites:
A PC with ADB/Fastboot installed
Redmi K40/Mi 11X/POCO F3 device
USB Cable
StatiXOS Build
Backup your internal storage before this process.
This guide assumes you are coming from MIUI 13.x with an unlocked bootloader.
For Windows Users:
Download SDK platform tools for Windows (do not use the latest platform tools, use any older than the r34) and extract it to anywhere you like.
Install ADB/Fastboot Drivers
Assuming you have unlocked bootloader, and enabled Developer Options, navigate to Additional Settings > Developer Options, scroll down to find USB Debugging, and enable it.
Connect your device to PC
From your PC, navigate to the extracted platform-tools
In the folder you need to check if there are some dll files and a few executables (.exe files). We're majorly concerned with adb.exe and fastboot.exe.
Whilst pressing Shift key, Right click in the folder, and there shall be an option to "Open powershell window here" or "Open Command Prompt here"
In the powershell window, type in .\adb.exe devices, now check your phone, there will a window asking to allow connection, allow it on phone. (If you don't do quicky, it may show as unauthorised in the powershell window, which is nothing to be worried about, just repeat the command)
Once the device is authorised, type in .\adb.exe reboot bootloader, your device shall reboot to a FASTBOOT screen, this is the bootloader mode.
Now ensure your drivers are proper. Type in .\fastboot.exe devices. If it shows nothing, it means that your drivers are not proper, google search on how you should fix them as it is out of the scope of this guide. Once you get an output like 2398534953 fastboot, it means that your device is detected.
(You do not have to do this step if you are upgrading from a previous StatiXOS build) In powershell, type in .\fastboot.exe format:f2fs --fs-options=casefold,projid userdata, this will completely wipe your internal storage.
Now, type in .\fastboot.exe update ''path\to\StatiXOS\Build\zip'' (replace path\to\StatiXOS\Build\zip with actual path to the fastboot images zip file) Pro Tip: You can right click and copy the zip and then paste into powershell window. Make sure you paste in between the quotes ' '.
It should show some details and start flashing immediately. It will reboot your device automatically to fastbootd mode in Statix Recovery. DO NOT DISCONNECT THE DEVICE DURING THIS PROCESS!
Wait till the process finishes, it will reboot the device automatically.
That's all! Enjoy StatiX on your device!
For Linux Users:
Install adb and fastboot according to your distro, and install proper udev rules.
Assuming you have unlocked bootloader, and enabled Developer Options, navigate to Additional Settings > Developer Options, scroll down to find USB Debugging, and enable it.
Connect your device to PC
From your PC, open Terminal
In the terminal window, type in adb devices, now check your phone, there will a window asking to allow connection, allow it on phone. (If you don't do quicky, it may show as unauthorised in the powershell window, which is nothing to be worried about)
Once the device is authorised, type in adb reboot bootloader, your device shall reboot to a FASTBOOT screen, this is the bootloader mode.
Type in fastboot devices, you'll get an output like 2398534953 fastboot, it means that your device is detected.
(You do not have to do this step if you are upgrading from a previous StatiXOS build) In powershell, type in fastboot format:f2fs --fs-options=casefold,projid userdata, this will completely wipe your internal storage.
Now, type in fastboot update ''path/to/StatiXOS/Build/zip'' (replace path/to/StatiXOS/Build/zip with actual path to the fastboot images zip file).
It should show some details and start flashing immediately. It will reboot your device automatically to fastbootd mode in Statix Recovery. DO NOT DISCONNECT THE DEVICE DURING THIS PROCESS!
Wait till the process finishes, it will reboot the device automatically.
That's all! Enjoy StatiX on your device!

Wow,
Yet another new rom for our great device,
i will have to give it a try soon,
would it be possible to make a "simple. zip" file that could be installed using TWRP or Orangefox recovery.
NOW FIXED By using Post no. 10
I wish you well with this rom and look forward to future updates
many thanks Murali

johnr64 said:
Wow,
Yet another new rom for our great device,
i will have to give it a try soon,
would it be possible to make a "simple. zip" file that could be installed using TWRP or Orangefox recovery.
I wish you well with this rom and look forward to future updates
many thanks Murali
Click to expand...
Click to collapse
I didn't make a simple zip file as custom recoveries don't support the new emulated storage changes.
Fastboot method is easier and more convenient than AOSP or in fact any recovery method.
Always having a PC is a good thing when flashing a ROM, as you can quickly restore your device to a working state without any worries if your device goes into bootloop (which should not happen with statix).

do you have some screenshots for this on poco f3? please post them

Update!
Changelog:
February 2023 security patch
Download from OP

exodius48 said:
do you have some screenshots for this on poco f3? please post them
Click to expand...
Click to collapse
Screenshots have been attached to OP

m_vaisakh said:
Update!
Changelog:
February 2023 security patch
Download from OP
Click to expand...
Click to collapse
Murali,
Your FAST.

Hi Murali,
I use a small standalone ADB program to install Temporary Recovery.
I have modified it a bit and added some basic adb FastBoot commands,
i have now included your install files as well:
-------------------------- UPDATED ! -------------------------
Now confirmed working
================================================================================
. ---------- Connect your phone to a PC in FASTBOOT mode to use this program ----------
.
.
Select Option:
.=========
.
1) Install TWRP Recovery (Remember to MOUNT SD Card in TWRP, wait 3 seconds and plug in your OTG adaptor)
2) Install OrangeFox Recovery (Remember to MOUNT SD Card in OFRecovery, wait 3 seconds and plug in your OTG adaptor)
3) Fastboot Devices
4) Reboot Bootloader
5) Reboot Recovery
6) Reboot
7) ADB Command line:
8) (WARNING)------------------ Format:f2fs
9) (WARNING)------------------ Install Statix_alioth-XXXX-XXXX XXXX-TIRAMISU-img.zip
10) Exit
.
.
. -To enter FASTBOOT, Power Off your Phone followed by Pressing and holding the Power and Volume down Buttons for 3 seconds,
.
.------------- Please read the INSTALL.txt file ---------------
.
Type option:
================================================================================
Also included in the .7z file are Magisk V25.2 and Migrate-GPE.
Download and unzip:
Statix-XXXX-XXXX-TIRAMISU + TEMP TWRP - OrangeFox (FASTBOOT) V1.0
Download Statix_Alioth-XXXX-XXXX-TIRAMISU, Rename it to rom.zip
and copy into the Statix_Alioth-XXXX-XXXX-TIRAMISU + TWRP - OrangeFox (FASTBOOT) V1.0.7 Folder.
Using this method, it is now easy to install this ROM as Murali explained and add Recovery if needed,
Thank you Murali for all your hard work,
I hope users find this little proggie helpful.

Update!
Hotfix for camera
Changelog:
Fixed missing smartspace.
Fixed camera not working with 3rd party apps.
Some under the hood micro-optimisations on top of android bionic.
Download from OP

m_vaisakh said:
Update!
Hotfix for camera
Changelog:
Fixed missing smartspace.
Fixed camera not working with 3rd party apps.
Some under the hood micro-optimisations on top of android bionic.
Download from
Apps in playstore not updating . always shows try again. Facebook messanger chats not loading .
Click to expand...
Click to collapse

Doesn't look like a statix issue to me. Did you format data using the given commands?

m_vaisakh said:
Doesn't look like a statix issue to me. Did you format data using the given commands?
Click to expand...
Click to collapse
Yes i am from MIUI 13.0.9 and formatted data .facebook messenger chat working fine but play store app updates not working. an now when plugging charger no sign of charging shown in the battery icon though the battery % is increasing. its only me with these problem? please look those.

gulmeli said:
Yes i am from MIUI 13.0.9 and formatted data .facebook messenger chat working fine but play store app updates not working. an now when plugging charger no sign of charging shown in the battery icon though the battery % is increasing. its only me with these problem? please look those.
Click to expand...
Click to collapse
You didn't understand my question. How did you format your data? What commands?
I didn't face any issue as charging indication not showing up, but one of my testers reported it today. I'll look into the issue.

m_vaisakh said:
You didn't understand my question. How did you format your data? What commands?
I didn't face any issue as charging indication not showing up, but one of my testers reported it today. I'll look into the issue.
Click to expand...
Click to collapse
(.\fastboot.exe format:f2fs --fs-options=casefold,projid userdata ) i used this

gulmeli said:
(.\fastboot.exe format:f2fs --fs-options=casefold,projid userdata ) i used this
Click to expand...
Click to collapse
That's correct. None of my testers, or I face the play store issue.
Can you try this?
Open Play Store > Tap on your Account picture in Top Right > Settings > Expand About > tap on Update Play store.
Or if that doesn't work, try rebooting the device once and check if your updates work or not.

m_vaisakh said:
That's correct. None of my testers, or I face the play store issue.
Can you try this?
Open Play Store > Tap on your Account picture in Top Right > Settings > Expand About > tap on Update Play store.
Or if that doesn't work, try rebooting the device once and check if your updates work or not.
Click to expand...
Click to collapse
Thank You Very much. it works fine now thanks again for the beautiful rom for great device.

Hi,
I tried the rom today,
the things i found:-
it seems to take a long time between the Poco F3 Logo and the boot animation,
i wasn`t able to find Face Unlock in the security setting,
Using the "Standalone ADB program" has made a massive difference,
as it simplifies every thing for me.
The rom is good but is in need of some TLC (Tender Loving Care),
I look forward to the next update,
Thank you again for all your hard work

m_vaisakh said:
I didn't make a simple zip file as custom recoveries don't support the new emulated storage changes.
Fastboot method is easier and more convenient than AOSP or in fact any recovery method...
Click to expand...
Click to collapse
I think you could explain also that this ROM uses vendorboot-as-recovery.