[ROM] [8.0.0] [yuga] LineageOS 15.0 for Xperia Z (Unofficial) - Xperia Z Android Development

{
"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"
}
Disclaimer:
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. Hard. A lot.
*/
About ROM:
This is Experiemental Build of Android 8.0 Oreo for Sony Xperia Z (C6602, C6603), Based on LineageOS.
Thanks To:
Mardon
What's working:
* ROM is experiemental and is not recommended for daily usage *
* Now we have working Audio *
I have not tested whole rom but everything works fine except:
- Flashlight and Camera
- Adaptive Brightness
Please report any bugs in the comments below!
(Special) Install Instructions for Newbies:
Warning: If you flash ROM first time do it at your own risk, You may brick device.
Before resuming remember these things:
- You can't restore TA codes on a custom ROM, TA codes only work on Stock ROMs, So if you ever reflash Stock ROM you can restore them.
- If you're Windows 8/8.1 or 10 User this Tutorial may not work for you as long as you've done This Tutorial
- Read everything Carefully, I wish you Good Luck
1.0 - Backing up TA Codes
- First you need an unlocked bootloader, But before unlocking it you have to backup DRM keys (Optional)
- Download KingoRoot, Root your device with One-Click-Root and then Download Backup-TA Program from Here
1.1 - Unlock Bootloader
- After you've done that, Unlock your bootloader from Here
1.2 - Preparing Drivers
- After you unlock your bootloader Install Sony Flashtool from Here
- Go to Flashtool Folder then go Drivers folder and select Flashtool-drivers.exe
Check the Fastboot and Flashmode drivers then Scrool down and find Xperia Z SO-02E drivers, Check it and Install them.
1.3 - Installing ADB
- Now it's time to download ADB 15 Seconds Installer from Here
Follow the instructions in the program and Install ADB/Fastboot drivers, then locate "C:/adb" folder and open it.
- Download Latest TWRP 3.1.1 from Here and move into adb folder located in "C:/adb"
- Rename TWRP 3.1.1 file to twrp (If your file extensions are shown twrp.img)
- As long as you can't flash TWRP directly as Recovery you must flash it as boot, Your ROM won't start again so back up everything before restarting to ADB!
- After you back up everything just enable USB debugging in your phone (go Settings/About and press Build Number couple times)
- Press Back button and go to Developer Settings and find USB Debugging, Enable it.
- Now go to "C:/adb" and press and hold SHIFT, Then press RMB (Right Mouse Button) and press open command window here.
- Congratulations! Now you're in adb.
1.4 - Flashing TWRP
- Write next ADB Commands:
adb devices (so you will check your device is detected by ADB or not, If adb shows any number row and then DEVICE its okay, If it doesn't then just write):
adb reboot bootloader (Look at your phone and give permissions of USB Debugging to PC, If phone reboots it means you've done everything correctly, If it doesn't then you did something wrong!)
- Well if the phone rebooted you will see blue led in the top of your phone, That means you're in a bootloader!
Write next commands:
fastboot devices (And check your device is detected by fastboot or not, same thing it will show number row and then FASTBOOT, So you did everything correctly, If it doesn't check your installed drivers, You may have little update from Device Manager so comment down below, If drivers are installed wrong and you don't see device number and FASTBOOT just restart phone and wait for the answer in the comments)
- If you see your device number and FASTBOOT enter next commands:
fastboot flash boot twrp.img
- After you've done that and you see that it has flashed without any Errors write next command:
fastboot reboot
- Now you're in TWRP recovery, Congratulations !!
1.5 - CleanFlashing ROM
- If you backed up everything just see if your computer detects your phone's MTP (media file transfer)
Go to My Computer/Xperia Z and see is there Internal Storage or not
- If There is any Storage that's good so make a Fully Clean Install
- Go back in the main menu of TWRP press Wipe, Advanced Wipe and check: Data, Cache, Dalvik Cache, System and Internal Storage, Then swipe to wipe.
- After you wiped your phone go back to the main menu of TWRP, Enter your internal storage folder from your PC and move ROM, Gapps and Rootkit in there.
- After that Press Install, You'll see lineageos, gapps and rootkit in the TWRP so press lineageos file and swipe to flash.
- Then go back (Don't Reboot) and press gapps file, flash it as you flashed lineageos.
- Go back again and flash Rootkit but when it's finished just press wipe dalvik cache and swipe to wipe it!
- After you've done that press Reboot phone.
- Congratulations!! Wait for 10 minute to boot and enjoy your new Android 8.0.0 Oreo!
1.0-2 - Troubleshooting
- If you want to install any other Custom ROMs just resume this tutorial from ADB (adb reboot bootloader) And do the same.
- If ROM doesn't boot up that means you did something incorrectly, So you have to do next steps:
Long Press Power Button and Volume UP, After it vibrates it will vibrate three more times and then release so your phone will shut down.
Get your USB Cable which's connected to PC and hold Volume UP, then connect USB Cable into phone
- You're in a fastboot, resume tutorial from (fastboot flash boot twrp.img)
- If you flashed ROM again and still doesn't work change your gapps version and download gApps-Pico
- Then it will work 100%, Or you can flash LineageOS14.1 and wait for Stable Oreo build.
- Thank you for attention, do it at your own risk and good luck
Downloads:
MOD EDIT: Download link removed.
Download the gApps (ARM, 8.0, Pico)
Download Rootkit if you want (I've tested Magisk and works fine)
- Links updated & No more error7 in TWRP
Short Install Instructions:
Move the ROM/GAPPS/ROOTKIT on your SDCARD
Flash latest TWRP (If you have old version already reflash it using flash image)
Wipe Cache, Data, Dalvik cache and System
Flash ROM
Flash gApps
Flash Rootkit
Wipe dalvik cache
Reboot!
- First boot may take some time for optimizing apps, bootanimation may have a little lag, be patient and wait.
ROM Information:
ROM Version: 8.x Oreo
ROM Kernel: Linux 3.10.x
Based On: LineageOS
Version Information:
Status: Experiemental
If you like the ROM please hit that Thanks button and give some support

Again hard work on design of topic, i hope you enjoy highlights and green (LOS color) design
So hit that THANKS button <3

#iLiKo said:
Again hard work on design of topic, i hope you enjoy highlights and green (LOS color) design
So hit that THANKS button <3
Click to expand...
Click to collapse
omg I can't believe this @@
thank you so much for your awesome work ^^

with 3.0.2- version of TWRP gave me error 7 and not install me the ROM so it is possible with 3.1.1 version ?

404 not found
Can't find it!
If you are seeing this error page then the file in question has been deleted from the site and servers. Please contact the developer/uploader for a new link to the file.

cyparisss1 said:
with 3.0.2- version of TWRP gave me error 7 and not install me the ROM so it is possible with 3.1.1 version ?
Click to expand...
Click to collapse
Not TWRP problem at all, don't delete rom because mby link got broken, ill help you to fix tommorow, update-script must be changed

Mardon deleted both international testbuilds of lineage15yuga from his account, idk why.
Link of old version:
MOD EDIT: Removed download link

not happen
with version 3.1.1
installing zip file /sdcard/Android 8/lineage-15.*****
checking for digest file....
skipping digest check : no Digest file found
Warning: no file_contexts
E3004: This package is for device: C6602, C6603, C6606, yuga;this device is .
Updater process ended with ERROR: 7
Error installing zip file lineage-15*******
Updating partition details...
....done
my device is 6603 I am sure in that - how to check and set it, may be from the custom roms this information is lost in the phone ?

cyparisss1 said:
with version 3.1.1
installing zip file /sdcard/Android 8/lineage-15.*****
checking for digest file....
skipping digest check : no Digest file found
Warning: no file_contexts
E3004: This package is for device: C6602, C6603, C6606, yuga;this device is .
Updater process ended with ERROR: 7
Error installing zip file lineage-15*******
Updating partition details...
....done
my device is 6603 I am sure in that - how to check and set it, may be from the custom roms this information is lost in the phone ?
Click to expand...
Click to collapse
dude its bugged at update-script so tommorow when i get PC please upload that new ROM somewhere, ill fix it and you and other people can download back, i fixed the link, but its old version without audio..

#iLiKo said:
Mardon deleted both international testbuilds of lineage15yuga from his account, idk why.
Click to expand...
Click to collapse
I can tell you why. Because you posted it without even asking. This happened a month ago too. Please stop that. It is annoying and delays LOS15 for fusion3 because people have to deal with this sh**.

I am using custom rom and my device model is Xperia Z , it is possible to not verify my phone like c6603 and then the installation fails. See on the screen shots

#iLiKo said:
dude its bugged at update-script so tommorow when i get PC please upload that new ROM somewhere, ill fix it and you and other people can download back, i fixed the link, but its old version without audio..
Click to expand...
Click to collapse
welcome my friend, MOD EDIT: Removed download link

NamenIos said:
I can tell you why. Because you posted it without even asking. This happened a month ago too. Please stop that. It is annoying and delays LOS15 for fusion3 because people have to deal with this sh**.
Click to expand...
Click to collapse
ill explain u smth this rom is shared and doesnt require any rights to post on websites, also people must have single oreo rom for this phone to try how its like, plus i made whole tutorial of newbies now i think they wont get in problems, also everyone knowns that this is experimental testbuild, but LOSTEAM still want to share only stable.. i think differently, i think people can see how oreo really is, whats the differences and etc.. by themselves. stop it, im not gonna delete rom again.

cyparisss1 said:
welcome my friend, MOD EDIT: Removed download link
Click to expand...
Click to collapse
new link: MOD EDIT: Removed download link

Bug
Camera not working
Lag ui (recent app)
Error 7 script delete assert line

mohammadnadimi48 said:
Camera not working
Lag ui (recent app)
Error 7 script delete assert line
Click to expand...
Click to collapse
Error 7 has been fixed i think so.
Use new link

Thread closed.
#iLiKo said:
ill explain u smth this rom is shared
Click to expand...
Click to collapse
Yes, you are right here - LineageOS can be built from source.
#iLiKo said:
doesnt require any rights to post on websites
Click to expand...
Click to collapse
Not quite correct - you still need to stick to the XDA rules (see rule 12).
You need to accept the fact that the developers of the ROM don't want to release half-baked builds or unfinished work (even if it's open source). Don't we all want a stable daily driver after all?
Thread closed.

Related

[NEW LAYOUT][ROM] Unofficial CyanogenMod 13.0 for HTC Incredible S [Version 1.2]

CyanogenMod 13.0 for HTC Incredible S​
{
"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"
}
CyanogenMod is a free, community built, aftermarket firmware distribution of Android 6.0, which is designed to increase performance and reliability over stock Android for your device.
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.
*/
About CyanogenMod
CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.
Not Working / Bugs
Some graphical glitches.
Screen Recorder.
Bluetooth switch in settings does not turn on Bluetooth.
How to Install
Make sure you have installed this recovery and switched to the new data layout.
Download the ROM from below
Download GApps from below
Attach the phone to your computer
Copy the ROM to your phone
Copy the GApps to your phone
Boot into recovery
If this is your first time installing this ROM then factory reset the phone from recovery
If you want to upgrade the ROM, flash the new version on top, and only wipe cache and dalvik cache
Go to Install and select the ROM zip file
After ROM has finished installing, flash the GApps
Go to Reboot -> System
Enjoy
Download
CM13.0
Google Apps
XDA:DevDB Information
CyanogenMod 13.0 for HTC Incredible S, ROM for the HTC Incredible S
Contributors
rqmok
Source Code: https://github.com/rqmok/android_device_htc_vivo/tree/cm-13.0
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.0.x
ROM Firmware Required: TWRP 3.x (New Layout)
Based On: CyanogenMod
Version Information
Status: Stable
Current Stable Version: 1.1
Stable Release Date: 2016-07-01
Created 2016-06-22
Last Updated 2016-07-19
Changelog
Version 1.2
- Sync with latest CyanogenMod sources.
- Revert back to older Camera app.
- Revert back to older media HAL.
- Revert back to older vidc drivers.
- Reserve 5MB for PMEM again.
- Add support for hitachi panel (probably doesn't work).
- Clean up and update panel code.
- Increase RAM to 607MB.
- Change GPS AMSS version (GPS still doesn't work).
Version 1.1
- Sync with latest CyanogenMod sources.
- Disable Atlas service to save RAM.
- Cherry-pick some changes for telephony framework.
- Revert back to old bcmdhd code.
- Revert back to old wifi code.
- Increase RAM by 5MB.
Version 1.0
- Initial Release
Reserved
Reserved 2
rqmok said:
Changelog
Version 1.0
- Initial Release
Click to expand...
Click to collapse
Sucsessfuly booted on my IncS! For now, works perfectly! Will be testing it now. Thank you so much!
After succesfull instalation i still have 5.1.1, cm12.
I've tried several times. Switched to new layout, but
- Go to "wipe". & - Press "Format Data". formats only sd card.
prezii said:
After succesfull instalation i still have 5.1.1, cm12.
I've tried several times. Switched to new layout, but
- Go to "wipe". & - Press "Format Data". formats only sd card.
Click to expand...
Click to collapse
"Format Data" is only meant to format sd card. After this, you need to go to Wipe -> Advanced Wipe and then select everything and wipe it. After that, go to Reboot -> Recovery. When you reboot back into recovery, copy cm13 and gapps to the sdcard, and flash them.
If you properly follow the instructions I have provided in the recovery thread and this thread then it is not hard.
Got an "Encryption unsuccessful" message during system load
---
It works! Great job, rqmok!
Good job,keep your work
rqmok said:
"Format Data" is only meant to format sd card. After this, you need to go to Wipe -> Advanced Wipe and then select everything and wipe it. After that, go to Reboot -> Recovery. When you reboot back into recovery, copy cm13 and gapps to the sdcard, and flash them.
If you properly follow the instructions I have provided in the recovery thread and this thread then it is not hard.
Click to expand...
Click to collapse
After flash boot.img 6.0 started. But "encryption unsuccessful" appeared, as above, reset phone is not solution....
dimmonz said:
Got an "Encryption unsuccessful" message during system load
---
It works! Great job, rqmok!
Click to expand...
Click to collapse
Can you please share how you fixed the problem? Did you have to format and wipe everything again?
Encryption Unsuccessful - Reset Phone
Finally successfully installed CyanogenMod 13.0 on HTC Incredible S [Version 1.0]
I was getting same error: Encryption Unsuccessful ..... Reset Phone
What I did was following and was successful. I am sure some of the steps might be unnecessary and be skipped:
1. Inserted SD card (16GB) into laptop deleted all partitions and recreated only one primary partition with format FAT32
2. Reinserted SD card to phone and into twrp recovery mode (ver 3.0.2.0) and performed following operations:
- Format Data
- Advance Wipe - Selected all partitions to wipe.
3. Just to check what has happened to my SD card, I inserted into laptop and checked using "MiniTool Partition Wizard Free". I found SD card had format ext3.
4. While in recovery mode copied CM13 ROM and Gapps to SD card and installed zips.
5. Rebooted to system. Soon after ---- CyanogenMod logo ---- optimizing app 1 of 11 ---- Marshmallow setup screen
Did not had much time to play with but for sure Camera, YouTube & Play Store definitely working.
gosain2000 said:
Finally successfully installed CyanogenMod 13.0 on HTC Incredible S [Version 1.0]
I was getting same error: Encryption Unsuccessful ..... Reset Phone
What I did was following and was successful. I am sure some of the steps might be unnecessary and be skipped:
3. Just to check what has happened to my SD card, I inserted into laptop and checked using "MiniTool Partition Wizard Free". I found SD card had format ext3.
4. While in recovery mode copied CM13 ROM and Gapps to SD card and installed zips.
Did not had much time to play with but for sure Camera, YouTube & Play Store definitely working.
Click to expand...
Click to collapse
How did you copied CM13 in recovery mode? I can't...
prezii said:
How did you copied CM13 in recovery mode? I can't...
Click to expand...
Click to collapse
Make sure you reboot recovery after formatting everything from the recovery.
rqmok said:
Can you please share how you fixed the problem? Did you have to format and wipe everything again?
Click to expand...
Click to collapse
Noticed that sdcard was formatted into FAT during ROM & APPs copying under Windows. Just copied them under linux mint without sdcard formatting.
prezii said:
How did you copied CM13 in recovery mode? I can't...
Click to expand...
Click to collapse
I can't do this too whith usb connection. While
Code:
adb devices
all the way returns that my htc is unauthorised,
Code:
adb push
does not work and i can't beat it. So i just get sdcard out to pc and copied files directly.
Now looking for ROOT...
rqmok said:
Make sure you reboot recovery after formatting everything from the recovery.
Click to expand...
Click to collapse
Again:
Procedure, after flashing TWRP 3.0.2-0 and boot.img.
1. Insert SD card to phone and into twrp recovery mode (ver 3.0.2.0) and performed following operations:
- Format Data
- Advance Wipe - Selected all partitions to wipe.
3. In recovery mode copied CM13 ROM and Gapps to SD card (important: works in win7, doest work in win10!) and installed zips.
5. Rebooted to system. Soon after ---- CyanogenMod logo ---- yes it WORKS!!!! Thanks brothers!!!
Still testing...
CM13 doesn't works without SD card, Encryption problem appeared.
Copy CM13 to SD card in recovery mode
prezii said:
How did you copied CM13 in recovery mode? I can't...
Click to expand...
Click to collapse
In Recovery mode, Under mount you have option to disable/enable MTP. If MTP is enabled you can transfer files to SD Card. However correct drivers is important. You will not see device as a separate drive but under This PC/ My computer.
Further sharing my experience:
I successfully installed CM13 using windows 10, Surface pro 3. There was a time when I could communicate with HTC Incredible S using ADB commands only and not fastboot commands. When HTC is in fastboot mode it uses different driver. After extensive reading on XDA I found that on installing compatible HTC sync drivers, under device manager you would see two separate Sections. Under section Android USB Device will be My HTC and under Portable Devices section would be HTC Incredible S. I use to get Error code 10 when my HTC was in fastboot mode. Once I changed its driver (found on XDA) problem got solved. i.e I could communicate in fastboot mode and in recovery or booted up mode. After this I am working with Windows 10 most of times.
Also use latest version of ADB to use ADB sideload feature.
tell me, do the s-off to do ??
S-off HTC incredible S
raiden.80 said:
tell me, do the s-off to do ??
Click to expand...
Click to collapse
Follow instructions http://forum.xda-developers.com/showthread.php?t=1373697
Download all required software from the links in the thread. It works.
I have just released version 1.1. The changes have been listed, but the biggest change is reverting back to older wifi drivers in the kernel. This should make the wifi connect to the network even faster. Also, it should make wifi more stable.

[Recovery] [V3.0-006] Red Wolf Recovery Project

{
"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"
}
/* Your warranty is now void! I am not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the flashlight failed. Please do some research if you have any concerns about features included in this recovery 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. */
Click to expand...
Click to collapse
Introduction
Red Wolf Recovery is alternatovní recovery based on the source code TWRP.
The main objective of the Red Wolf Recovery is to provide the features that were for some reasonrefusedto add to the official source code Winu Team (besides the maximum utilization of hardware options that device ...).
Hence Recovery supports password protection, since Team Win rejected this method of security because users generally do not read any kind of warning, then it was just a mistake on the part of Team Winu that somebody got into the facility despite a recovery password protected.
For this reason, therefore, I warn that the red wolf is secured in such a way that nobody could get into recovery without the user's password, but no recovery willnot safeguardagainst reinstall the device via Flash or Mi fastboot. So please take a note!
Acknowledgments:
Ray Li: For his help in modifying the source code TWRP.
osm0sis: In the video below scripts which also runs most of the functions recovery.
z31s1g: For the base material. theme.
And all the other developers of the various scripts and installation files as Chanfire,topjohnwu,cofface,etc
Features recovery:
- Brightness can be reduced to a minimum fair value. (TWRP only supports a minimum of 10% Brightness).
- Support for more than 50 sections (including "subsections").
- Possibility of installation of paintings in section Modem and Boot Logos.
- Adjusted ADB - for security reasons already does not start automatically at boot recovery, but now it turns in the recovery
- Recovery allows you to set and remove a password
- Torch phone is now going to turn right in Recovery
- Automatically Block stock recovery
- Recovery contains settings regarding Governor where recovery is currently running. If, therefore, not in a hurry, so just switch to performance and processes such as backup, restore or installation will be up almost 20% faster.
- When you confirm the installation file on the screen appears and warnings checkbox for the finished installation. This recovery will automatically notify the completed installation using the notification LED.
- For safety reasons deactivated TWRP theme engine.
- Official TWRP application was replaced for Snap Camera HDR.
- Access to the folder with zálohama and setting recovery is blocked. Access to these files is only possible from the recovery. (This is only an internal storage)
- The first recovery that is built on OMNI ROM code purely for Kate.
- Folder screenshotama of recovery has been moved to /sdcard/WOLF.res to already screenshots of recovery are not confused with the other screenshotama ..
- Updated Czech translation - Slovak translation can be translated from the strings provided below.
- new terminal supports three commands: unpackbootimg, mkbootimg and zipper (so they may also be retrieved from the script, of course).
- Recovery supports Tap To Wake Engine (dt2w is not supported yet ...)
- Support for "night mode".
- Built AromaFM supports Czech language.
- User can set custom name for the folder backup & ID at the ADB.
- Create backup can also be erased at once (not therefore been deleted one by one as it is in ofiko TWRP).
- Recovery is assembled on AOSP 7.1.2 / TWRP 3.1.1-0 / Omni 7.1.2.
Built-in installation files:
Supers
Magisk
Nitrogen UNROOT
substrates Rescue
Deactivation dm-verity
substrates Rescue Legacy
- Built-in scripts community:
Fix-fp-scanner (script to fix the fingerprint reader if the ROM reports "hardware can not be found")
ramdisk- cleaner (the script automatically cleans content boot from custom kernels and thus need not be renewed when switching to a different kernel stock kernel. However, the script still only supports ElementalX kernel, Radon kernel and Franco kernel.Warning: After cleaning the content boot must just to flash a new kernel - certainly attempt to restart the device to the system !!)
rm-pass(script to remove security currently installed ROM.)
NOS-before-flash-other-kernel(script recently found on 4PDA - deactivates the post-script Nitrogen boot ROM and thus allows better compatibility custom kernel).
Community scripts can thus be understandable added community. If you have your script / tip on a script about it here let me know.
Known Bugs
- The search engine of the camera HDR Snap is momentary assembly inoperable. TWRP still finds the application and if the application is installed TWRP and even prevents installation Snap CAMERA HDR.
The problem is mainly that I do not have complete access to that search engine - probably even if I somehow repaired and recovery will still prefer ofiko TWRP search application. So it probably could not be correct function ofiko TWRP applications not installed. However, definitely I do something in the next builds I make.
Link to download
latest build released: official
https://www.androidfilehost.com/?fid=889764386195913594
Update Changes
Update!
RedWolf-V3.0_006-Kate_Kenzo
Major changes;
- After clicking on the main menu icon coffee displays a new button "folder backups." Here you can now rename your current folder & zálohama or even set a new ID instead of the serial number at the ADB.
- Clicking on the Main Menu button to restore the icon appears at the top "bones". Using this button you can now delete all backups currently displayed. Therefore no longer need to delete one by one separately.
Current info
Version recovery: V3.0
Current build: 006
Number of community scripts: 4
Number of installation files: 6
Date of latest released build: 05-7-2017
Strings of recovery can be download here:
Strings for any translation AromaFM:
Extra Links
https://github.com/omnirom/android_bootable_recovery/commit/ce8f83c48d200106ff61ad530c863b15c16949d9
https://github.com/TeamWin
All Credit to ATG Droid
Source
Ss pls
not in a hurry but will have to remind you that source is not updated.... please add
~peace
AxeCORE said:
Ss pls
Click to expand...
Click to collapse
here!
adithyan25 said:
not in a hurry but will have to remind you that source is not updated.... please add
~peace
Click to expand...
Click to collapse
Visit our Forum - https://androidforum.cz
měj hezký den
Can i flash any rom on this type of recovery ?
xN00Bx said:
here!
Click to expand...
Click to collapse
Flashed just now device is not rebooting to recovery mode at all instead of going to recovery mode device is booting to normal plz check it
Previously i am using zcx twrp from that i have flashed this recovery flashing done successfully no issues about thag
Waiting for solution
cherri said:
Flashed just now device is not rebooting to recovery mode at all instead of going to recovery mode device is booting to normal plz check it
Previously i am using zcx twrp from that i have flashed this recovery flashing done successfully no issues about thag
Waiting for solution
Click to expand...
Click to collapse
+1
filipino guy said:
Can i flash any rom on this type of recovery ?
Click to expand...
Click to collapse
Yes you can flash it on any roms
cherri said:
Flashed just now device is not rebooting to recovery mode at all instead of going to recovery mode device is booting to normal plz check it
Previously i am using zcx twrp from that i have flashed this recovery flashing done successfully no issues about thag
Waiting for solution
Click to expand...
Click to collapse
after flash press reboot to recovery ( if your device booting normally) then press vol plus + power button immediately after the screen goes down while pressing reboot to recovery,
try again master, no problem here!
xN00Bx said:
Yes you can flash it on any roms
after flash press reboot to recovery ( if your device booting normally) then press vol plus + power button immediately after the screen goes down while pressing reboot to recovery,
try again master, no problem here!
Click to expand...
Click to collapse
Yaa now working don't know why it didn't worked at first he he he thank you bro
I am having some weired grains on the screen when reboot to recovery..after a few seconds the grains disappears andt
reboots to system
anandumohan said:
I am having some weired grains on the screen when reboot to recovery..after a few seconds the grains disappears andt
reboots to system
Click to expand...
Click to collapse
Same thing
Recovery was withdrawn because its not yet ready to run on the variant Kenzo fully,
only kate is completely functional!
we will back to you when it's gets fixed
~thanks
Mod Edit
Thread closed at the request of the [OP]
malybru
Senior Moderator

[RECOVERY][UNOFFICIAL][09/20]Red Wolf Recovery Project

{
"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"
}
Code:
/*
* Your warranty is now void.
*
* We're 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.
*
*/
Red Wolf Recovery is custom recovery based on TWRP source code, however some things are working here slightly different then you might expected. The main objective of this project is to provide stable recovery with features which you have never seen before in a recovery and which have not been accepted for adding to the official source code of TWRP. This recovery is also first recovery on the world with password protection.​
Based on TWRP version: 3.2.1
For devices: Z2 PRO, Z2121, Z2_ROW
TREE: https://github.com/mracar07/android_device_zuk_z2_row/tree/RWRecovery
Developers: ATG Droid & dadi11
Thanks: z31s1g (for the base of his theme), Ray Li (For his useful advice in the beginnings), osm0sis (for his image scripts), cosmedd for twrp tree
Features:
Code:
[B]Translated to EN, PL, zh_cn, & CZ [/B]
- Password protection
- Flashlight
- MIUI Incremental OTA Support
- Built-in latest Magisk, SuperSU & AromaFM
- Support two screenshot GUI actions - Power+VolDown to save screenshot in to the internal storage &
Power+VolUp to save screenshot in to the external storage (Will be automatically saved in to the internal in case
that external storage doesn't exist).
- Support automatic reboot after the restore process
- Recovery can automatically modify some props in the ROM directly during the installation
- Some built-in scripts from community
- Tap to wake support
- Advanced deactivation of the stock recovery
- Automatic deactivation of the dm-verity & forced encryption directly during the installation of the ROM
- Recovery can notify you about the completed backup/restore/installation using the notification diode & vibration.
- Support "set on boot" settings.
*[B] Changes for security reasons [/B]*
- ADB isn't starting automatically at the start of the recovery. You have to activate it in recovery
- MTP isn't starting until user enter correct password
- Deactivated support of the custom themes
Some differences to the official version:
Code:
[B][COLOR="red"]- get out of here if you are pirating apps. this recovery is not for you[/COLOR][/B]
- always up-to-date with the latest TWRP changes
- compiled on omnirom-7.1 source
- kernel compiled inline with the recovery
- fixed backup/restore of Firmware
- added F2FS support
- added NTFS support
- added exFAT support
- more languages
- other improvements from Features and Changelog lists
Changelog:
04/09:
Treble Support
In AEX Blue Led of Death fixed
thanks to @cosmedd
Redwolf source updated...
04/09 Second Release:
Slow backup-restoring fixed
04/18:
Renamed from factory to vendor
BUGs:
Only in recovery FLASHLIGHT
Downloads:
Latest build for ZUK Z2 PRO(z2_row):
https://androidfilehost.com/?fid=1322778262904009823
Screenshots:
Warning:
Please remember that recovery with password protection isn't still a full protection for your phone. Red Wolf can only prevent unauthorized access to your device from recovery. But your device can be still reinstalled using fastboot or Miflash.
Donate DEV: paypal.me/mracar07​
Flashed, no problem...excellent development, thank you!
flashed, made backup and restore with it, worked without problems. Thanks!
looks interesting any incompatiblity with roms? is the su included? or just a script to install from path "xyz"? is the kernel change / govenor change permanently or temporary for one boot?
so many questions :fingers-crossed: thx for your work guys
Thanks for your work ,but I met some trouble .I use AEX 5.2 ,try to flash this recovery from twrp. but when I rebot to the RW , I can see RW's first screen ,then LED was blue(900E) .I back to TWRP now. I hope you can fix it.THX
江泽民1926 said:
Thanks for your work ,but I met some trouble .I use AEX 5.2 ,try to flash this recovery from twrp. but when I rebot to the RW , I can see RW's first screen ,then LED was blue(900E) .I back to TWRP now. I hope you can fix it.THX
Click to expand...
Click to collapse
Not have any issiue. Tested and working properly :good:
Does it chinese language supported?I can help you im chinese
江泽民1926 said:
Thanks for your work ,but I met some trouble .I use AEX 5.2 ,try to flash this recovery from twrp. but when I rebot to the RW , I can see RW's first screen ,then LED was blue(900E) .I back to TWRP now. I hope you can fix it.THX
Click to expand...
Click to collapse
me too!
Bave Lee said:
Does it chinese language supported?I can help you im chinese
Click to expand...
Click to collapse
-> "Translated to EN, PL, zh_cn, & CZ "
Great Project! We need a german translation. I can help you. Tell me what can i do. OK, i see we have a german translation. Great work.
江泽民1926 said:
Thanks for your work ,but I met some trouble .I use AEX 5.2 ,try to flash this recovery from twrp. but when I rebot to the RW , I can see RW's first screen ,then LED was blue(900E) .I back to TWRP now. I hope you can fix it.THX
Click to expand...
Click to collapse
Hi, Chairman 江☺I 've encountered the same issue with you, I am currently using MIUI 9 , not sure if I need to clean up the old TWRP files.
Did you flash latest LR.Team TWRP (by wzsx150)?
Updated. 04/09.
for test thanks to @weimerd
04/09 Second Release:
Slow backup-restoring fixed
for test thanks to @weimerd
Thanks man, nice work
Unfortunately not possible to run edl mode . Btw good work and recovery works quite good and fast . Thanks for your work .
mar.ur said:
Unfortunately not possible to run edl mode . Btw good work and recovery works quite good and fast . Thanks for your work .
Click to expand...
Click to collapse
There's no direct button for it within RW Recovery, but it has adb working, so once you're started up in Red Wolf Recovery, just plug into the computer and send it "adb reboot edl" from a terminal. I just tested it and it worked fine.
I'm assuming you have a functional installation of android sdk or platform tools and working USB drivers on a capable computer, otherwise what exactly did you plan on doing with EDL mode anyway?
Terminator.J said:
There's no direct button for it within RW Recovery, but it has adb working, so once you're started up in Red Wolf Recovery, just plug into the computer and send it "adb reboot edl" from a terminal. I just tested it and it worked fine.
I'm assuming you have a functional installation of android sdk or platform tools and working USB drivers on a capable computer, otherwise what exactly did you plan on doing with EDL mode anyway?
Click to expand...
Click to collapse
No possible to run edl mode from system by ADB command . Edl = download and is existing in twrp as I know .
mar.ur said:
No possible to run edl mode from system by ADB command . Edl = download and is existing in twrp as I know .
Click to expand...
Click to collapse
... I"m sorry, I don't know what else to say, other than either you're wrong or there must be something wrong with your computer/phone configuration. I literally just started up in the latest red wolf recovery, connected via USB cable to my computer (Windows 10 laptop), opened an administrative command prompt on the computer, cd to directory I unzipped platform tools to, typed "adb reboot edl", and the phone rebooted into emergency download mode, and ran QFIL, which sees a 9008 mode device ready for flash.
However I did also test from within the recovery itself... going to terminal inside RW recovery and typing "reboot download" did not work, it just restarted normally. That is true. But again, it's not an issue since you have the computer & USB cable there (or else you wouldn't need EDL mode) and can just send the adb command from the computer.
I only reported that is impossible to run edl mode from system by ADB and from twrp by download button .
04/18 UPDATED....
Renamed from factory to vendor

[ROM][UNOFFICIAL][m8qlul] LineageOS 15.1 for HTC One M8s

LineageOS is a free, community built, aftermarket firmware distribution of Android 8.1.0 (Oreo), which is designed to increase performance and reliability over stock Android for your device.
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.
*
*/
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. You will need to provide your own Google Applications package (gapps). LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for Lineage OS is available in the LineageOS Github repo. And if you would like to contribute to Lineage OS, please visit our Gerrit Code Review. Your changelog is whatever was merged into gerrit.
NOTE: This build is unofficial, don't report bugs to the official LineageOS bug tracker.
HOW TO FLASH
Download the ROM from here
Download GAPPS from here
Install TWRP recovery from this thread
Boot to recovery
Wipe Data/Factory reset
Flash LineageOS
Flash GAPPS
Wipe Cache/Dalvik
Boot to system
What works
Audio
Camera
RIL (calls, sms, etc)
GPS
Bluetooth
WiFi
Everything else not listed below
What doesn't work
HDR
WiFi Hotspot
Wireless display
Before asking any question read the FAQ below
Big thanks to @voidzero for letting me use his server to build and for the initial device tree
XDA:DevDB Information
[ROM][UNOFFICIAL][m8qlul] LineageOS 15.1 for HTC One M8s, ROM for the HTC One (M8)
Contributors
root-expert, voidzero
Source Code: https://github.com/M8s-dev/
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 3.10.x
ROM Firmware Required: M firmware base
Version Information
Status: Stable
Beta Release Date: 2018-06-18
Created 2018-06-18
Last Updated 2018-10-27
Changelog
Code:
[B][U]26 October 2018[/U][/B]
* Instagram videos fixed
Code:
[B][U]18 October 2018[/U][/B]
* August/September/October ASB merged
* Use sdFAT instead of exFAT
* Reduce GPS fix time
* Increased speaker volume
* Increased microphone volume
* Increased upper earpiece volume when in-call
* Enabled HDR
* Fixed wakelock
Code:
[B][U]26 July 2018[/U][/B]
* July Android Security updates
* Kernel updated from tag 3.10.49 to tag 3.10.108
* Bluetooth now recognises the correct bt address
* Use low-latency as primary output for notifications and ringtone
* Switched SELinux to enforcing
* When usb composition is on "charge only" adb works
* Enabled audio offloading
* Added the option to disable Double Tap to wake gesture
* Added option to unlock phone with a gesture (you can find it under gestures tab)
* Used newer WiFi configuration files (hope that fixes WiFi problems)
* The name "HTC One M8s" is shown to your pc when connected instead of "Android Phone"
Code:
[B][U]20 June 2018[/U][/B]
[LIST]
[*]Fixed headphones microphone
[/LIST]
Code:
[B][U]18 June 2018[/U][/B]
[LIST]
[*]Initial commit
[/LIST]
Frequently Asked Questions (FAQ)
Q: I flashed the ROM and I'm getting random reboots and crashes
A: Ensure that before flashing this ROM your last stock rom was Android version 6.0. If not follow the instructions on the post below
Q: I found a bug, what should I do?
A: Describe in this thread the issue as best as you can and include steps to reproduce.
Also include a logcat taken the time that the bug happens.
If you had a random reboot don't bother taking a logcat instead pull /sys/fs/pstore/console-ramoops file and atach it to your post.
Q: I want to root this ROM. Should I flash something?
A: Either download su addon from https://download.lineageos.org/extras or flash Magisk.
If you are coming from CM12.1 (Just like I did) then follow these steps
NOTE: If you do not follow these steps, your final Oreo ROM (LOS 15) will crash, you'll suffer randoms reboots and instability problems due to incompatible radio / HTC firmware. This whole update process to Stock 6.0 can take up to 4 hours! So make sure you have the time to do everything correctly, don't cut corners.
I suffered
1. Create a full backup of your ROM using TWRP (v2.8 or v3.0.2.0), Copy your INTERNAL STORAGE and SD Card contents to PC .
During the upgrade from "CM12.1 > 5.0.1 Stock > 6 Stock > LOS 15" you WILL lose your internal data! (because of bootloader relock & unlock again)
2. Relock your bootloader; (Make sure you are using the htc_fastboot.exe)
Turn off phone
Go into bootloader (Hold down VOL DOWN+Power button
Connect USB and enter Fastboot (Should show as FASTBOOT USB)
Open commandprompt;
Code:
htc_fastboot oem lock
The phone should restart and show up as ***RELOCKED***
3. Get your matching RUU from https://ruu.lalleman.net/HTC_M8S(QL_UL)/
If you dont know which RUU to get, follow this thread; https://forum.xda-developers.com/ht...lp-thread-htc-one-m8s-to-stock-howto-t3190238 (M8sQL_UL > Firmware (Expert)>Firmware Crypted (Original HTC))
If you get the "Device halted due to Large Image update fail" error during installation, just try another RUU - but make sure it matches your CID.
I got it working using a "signed" version. The "combined-signed" version did not work for me. Your mileage may very.
Click to expand...
Click to collapse
4. In Android Stock (5.0.1), continue the setup and after that go to: Settings > Software updates (At the bottom) > Check for updates
At first I only got 2 APP updates: "HTC Sense" and some other app (cant remember). Update both apps and reboot.
After a reboot check again for updates. Now you get a ~400Mb update. Download and install.
After the first update check again for updates. Now you get a ~1.23Gb update (Update to Marshmallow, Part 1 of 2). Download and install.
After that check again, and now you'll get a ~700Mb update (Update to Marshmallow, Part 2 of 2.)
That's it for going back to the most recent stock version. You now have Android 6.0 Stock running.
To install TWRP (if you want to flash LOS 15)
1. Unlock your bootloader again.
Go to https://www.htcdev.com/bootloader/ and follow the instructions.
2. Flash TWRP.
Code:
htc_fastboot flash recovery twrp-recovery-image-name-and-version.img
After that:
Wipe Cache/Dalvik, Data and System
Install LOS15
Wipe Dalvik again
Flash Gapps
Wipe Dalvik
Boot
Say thank you to @root-expert for keeping this phone alive with the development and @voidzero for providing the build-environment / mirrors
- Jeroen
Nice job! Great work on the rom and keeping the one m8s alive!
New build up!
Headphones microphone is now fixed.
Grab it as usual from here
-Chris
For the users who want to remove the"root icon" ( the status bar), there is no setting to disable it.
{
"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"
}
To remove it:
Connect your M8s to PC with USB
Open CMD
Code:
adb shell settings get secure icon_blacklist
The output is:
Code:
[COLOR="Red"]rotate,headset[/COLOR]
Now enter the output + su
Code:
adb shell settings put secure icon_blacklist rotate,headset,[COLOR="red"]su[/COLOR]
And after that:
Code:
adb reboot
Now the "#" icon is gone from the status bar.
- Jeroen
My battery time is very bad. Clean install with everything wiped. Rom is slick, clean, easy, snappy. Can't install shortcut for greenify. Xposed installed without problems, pico gapps, I like this rom. Only battery life is bad. I might try reinstalling when I get a chance to see what happens. All in all, slick rom, kudos to Developer !
brunkonjaa said:
My battery time is very bad. Clean install with everything wiped. Rom is slick, clean, easy, snappy. Can't install shortcut for greenify. Xposed installed without problems, pico gapps, I like this rom. Only battery life is bad. I might try reinstalling when I get a chance to see what happens. All in all, slick rom, kudos to Developer !
Click to expand...
Click to collapse
Hello, thanks for flashing. In what way you battery life is bad? When you use it or when it's idle?
I suggest you to run the ROM for 1-2 days and take a look at battery statistics.
-Chris
root-expert said:
Hello, thanks for flashing. In what way you battery life is bad? When you use it or when it's idle?
I suggest you to run the ROM for 1-2 days and take a look at battery statistics.
-Chris
Click to expand...
Click to collapse
I'll run it for a few days and screenshot battery stats. Then I'll reinstall the whole thing and compare new batery stats with old ones. Maybe if I format data prior to flashing things will be different
brunkonjaa said:
I'll run it for a few days and screenshot battery stats. Then I'll reinstall the whole thing and compare new batery stats with old ones. Maybe if I format data prior to flashing things will be different
Click to expand...
Click to collapse
I don't believe you have to do that. The only requirement is that your last stock android version was Android 6.0
Post battery statistics here
After using for about 13hours work Perfect. Ok 1 time i got crash but i try to install a same time 5 apps + download about 2gb for sekund 2 apps + copy via usb to sd some files + copy via usb to internal memory another thing + run google play store update apps just installed :silly: :silly:
But otherwise work realy great wasnt any problems.
Oh one more thing to install rom via TWRP NEEEEEED twrp-3.2.1-0-m8qlul.img at twrp-3.0.2-0-m8ql.img get error 7
Of course except
HDR
Wireless display
SELinux
WiFi hotspot
You tell me...
GeoEgbA said:
After using for about 13hours work Perfect. Ok 1 time i got crash but i try to install a same time 5 apps + download about 2gb for sekund 2 apps + copy via usb to sd some files + copy via usb to internal memory another thing + run google play store update apps just installed :silly: :silly:
But otherwise work realy great wasnt any problems.
Oh one more thing to install rom via TWRP NEEEEEED twrp-3.2.1-0-m8qlul.img at twrp-3.0.2-0-m8ql.img get error 7
Of course except
HDR
Wireless display
SELinux
WiFi hotspot
You tell me...
Click to expand...
Click to collapse
Hello, can you give me the error of twrp? If it is an assert error i'll fix it real quick and upload a new TWRP image.
-Chris
Problem with google play services
Hi
first thank you very much for your great work. :good:
I've got a problem with the Google Play Services / TWRP / GAPPS
Okay first what I've done:
1. followed your steps until installation of gapps
2. recognized the error: Failed to mount '/persist' (GApps: ARM64/8.1/nano)
3. ignored the error
4. system is running without problems
5. try to start play store -> "Google Play Services Has stopped" message continually popping up
Do you have any idea?
Greetings and thank you in advance
root-expert said:
Hello, can you give me the error of twrp? If it is an assert error i'll fix it real quick and upload a new TWRP image.
-Chris
Click to expand...
Click to collapse
Sure give me 5 min
root-expert said:
Hello, can you give me the error of twrp? If it is an assert error i'll fix it real quick and upload a new TWRP image.
-Chris
Click to expand...
Click to collapse
Sure give me 5 min
Click to expand...
Click to collapse
View attachment recovery.log
Try by twrp-3.0.2-0-m8ql.img
View attachment twrp-3.0.2-0-m8ql.zip
GeoEgbA said:
View attachment 4533829
Try by twrp-3.0.2-0-m8ql.img
View attachment 4533830
Click to expand...
Click to collapse
Look again on the flashing instructions. I state you should flash a TWRP recovery from one specific thread. YOu are using outdated recovery. Use the new one and it will fix this error
EDIT: I read agian your initial post, and yes you need the newer recovery to flash the rom and i said i state on flashin instructions
-Chris
monkyMatys said:
Hi
first thank you very much for your great work. :good:
I've got a problem with the Google Play Services / TWRP / GAPPS
Okay first what I've done:
1. followed your steps until installation of gapps
2. recognized the error: Failed to mount '/persist' (GApps: ARM64/8.1/nano)
3. ignored the error
4. system is running without problems
5. try to start play store -> "Google Play Services Has stopped" message continually popping up
Do you have any idea?
Greetings and thank you in advance
Click to expand...
Click to collapse
Hello,
Ensure that you flashed GAPPS straight after flashing the ROM WITHOUT rebooting to system. If you reboot to system and then flash GAPPS you'll have problem and crashes like you do. Also ensure that your previous stock andorid version was android 6.0. If not follow the instructions on this thread to revert back to stock and then try to flash the ROM
-Chris
root-expert said:
Look again on the flashing instructions. I state you should flash a TWRP recovery from one specific thread. YOu are using outdated recovery. Use the new one and it will fix this error
EDIT: I read agian your initial post, and yes you need the newer recovery to flash the rom and i said i state on flashin instructions
-Chris
Click to expand...
Click to collapse
Yes yes that why i wrote that need 3.2.1..0 becouse on 3.0.2.0 get error 7. I flash 3.2.1.0 anf LOS and work great for 15h now sorry for confusion
How long should the first boot take? i followed the instructions, twrp 3.2.1 gave a /persist error but everything else seemed fine. its been 20m and im at the lineage os boot screen.

Development [ROM][13.0] crDroid 9 [OFFICIAL]

{
"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"
}
Code:
*** Disclaimer
I am not responsible for any damage you made to your device
You have been warned
Features:
* Encrypted build
* Vanilla build (no gapps)
* Selinux enforcing and Safety net passes by default
* More info - Click here
First Time Installation:
* Backup before you begin
* Reboot to provided or TWRP based recovery.
* Format Data , even coming from crDroid 8.x
(otherwise you may not able to boot ROM due to encryption complexities)
* Flash ROM via adb sideload
* Flash Nik Gapps core + Gapps Search addon + Google Device Personalization addon via adb sideload
* Reboot and profit!
Update Installation:
* Backup before you begin
* Ensure you are on provided 12/13 recovery
* Use Updater app to download update and flash
(or download update separately and use Updater app with Local update option)
* No need to flash gapps if already flashed.
Download:
Click Here
Known issues:
* None.
Sources:
ROM: https://github.com/crdroidandroid
Device tree: https://github.com/crdroidandroid/android_device_xiaomi_sm6150-common
Visit official website @ crDroid.net
crDroid sweet/sweetin - crDroid Telegram
Donate to help me in development
crDroid Community Telegram
Donate to help CrDroid team pay server costs
Hello, neobuddy89.
I installed the rom this morning.
I encountered only a "bug" (??).
In developer'options, I choose as usual "File transfer" but it is then automatically set to "No data transfer".
Correction isn't urgent. I can use a USB key.
hi,
i flashed last build and touch issue persists on A13 build
But i still stay on
Nice! Thanks a lot!
Very nice ROM, but it has some issues...
- file transfer in developer option doesn't stay how I want (no data transfer)
- doesn't matter what I want to install, I'm out of space... I must uninstall some apps "to free up space"... but I have enough... more than 90GB. I cannot install any of my apps. In rest...looks fine.
Hellera said:
- doesn't matter what I want to install, I'm out of space... I must uninstall some apps "to free up space"... but I have enough... more than 90GB. I cannot install any of my apps. In rest...looks fine.
Click to expand...
Click to collapse
The same issue here. That's why i'll wait for fixed version. Even Gapps installing just some of packages. There is no option to install any .APK file or to install any Google Play's aplication. Cant install magisk too. Always problem with storege.
@Hellera & Can-dlE!
Seems like you guys used incompatible recovery, get latest unofficial TWRP from update group and clean flash it.
mnsiw said:
@Hellera & Can-dlE!
Seems like you guys used incompatible recovery, get latest unofficial TWRP from update group and clean flash it.
Click to expand...
Click to collapse
I clean flashed it in orange fox recovery, latest version., OrangeFox-R12.1_3. Did I do something wrong? Can you provide a specific recovery something else than default one, please? Thank you.
mnsiw said:
@Hellera & Can-dlE!
Seems like you guys used incompatible recovery, get latest unofficial TWRP from update group and clean flash it.
Click to expand...
Click to collapse
I'm on 3.6.2_12-0. Other ROMs working fine, and i cant find any newest TWRP.
Hellera said:
Very nice ROM, but it has some issues...
- file transfer in developer option doesn't stay how I want (no data transfer)
- doesn't matter what I want to install, I'm out of space... I must uninstall some apps "to free up space"... but I have enough... more than 90GB. I cannot install any of my apps. In rest...looks fine.
Click to expand...
Click to collapse
` Can-dlE ! said:
I'm on 3.6.2_12-0. Other ROMs working fine, and i cant find any newest TWRP.
Click to expand...
Click to collapse
I faced similar issues on some TWRP builds and OrangeFox, storage, APK and Play Store related stuff. Since then I'm on 'TWRP-3.6.2-sweet-Nebrassy-13-09-22' and never faced such issue again. This one works perfect except for some Pulkit builds, where you need KewL version of TWRP.
Try twrp-3.7.0_12-0-sweet.img which can be downloaded here.
1) Recovery -> format -> reboot to Recovery (internal storage unreadable)
2) Recovery -> Install crDroidAndroid-13.0-20221108 (from sd card)
-> Install NikGapps-core-arm64-13-20220908-signed.zip
-> Reboot to System
3) Recovery -> Data decrypted
4) Backup/Restore of data in recovery seem to work too.
I find the rom nice, features rich and good/stable to use except mtp (file transfer) doesn't work. To access files in the internal storage, I have to boot to recovery.
jngiag said:
Try twrp-3.7.0_12-0-sweet.img ...
Click to expand...
Click to collapse
Thank you for your explanation.
I followed the same way to install the rom this wednesday morning (see post 2 of this thread), using also the same twrp.
As workaround to the mtp tranfer problem (awaiting for a quick solution), I simply use a USB key instead of rebooting to twrp.
For having used crDroid 8 for a few months as daily driver, I'm now using crDroid 9 in the place in order to ensure continuity : same environment, same developer.
jngiag said:
Try twrp-3.7.0_12-0-sweet.img which can be downloaded here.
1) Recovery -> format -> reboot to Recovery (internal storage unreadable)
2) Recovery -> Install crDroidAndroid-13.0-20221108 (from sd card)
-> Install NikGapps-core-arm64-13-20220908-signed.zip
-> Reboot to System
3) Recovery -> Data decrypted
4) Backup/Restore of data in recovery seem to work too.
I find the rom nice, features rich and good/stable to use except mtp (file transfer) doesn't work. To access files in the internal storage, I have to boot to recovery.
Click to expand...
Click to collapse
Thanks for this, but how can I acces the phone storage or sd card...? Nothing works! File transfer doesn't work, and that's a big problem!
I'm looking forward to flashing A13 once it's more stable. Also, it's the weekend and I don't want to spend the next few days looking at a recovery screen
Hellera said:
Thanks for this, but how can I acces the phone storage or sd card...? Nothing works! File transfer doesn't work, and that's a big problem!
Click to expand...
Click to collapse
Awaiting the correction of the problem "MTP File tranfer", simply act as follows :
connect your phone to your PC with the cable ;
reboot to twrp ;
on your PC, you will find your device and
;
you can then work as with MTP File transfer
cocopipou said:
Awaiting the correction of the problem "MTP File tranfer", simply act as follows :
connect your phone to your PC with the cable ;
reboot to twrp ;
on your PC, you will find your device and View attachment 5758139 ;
you can then work as with MTP File transfer
Click to expand...
Click to collapse
Yes, I know that... but is frustrating to do this everytime when I need access to the phone storage. Thanks anyway!
Maybe the next build will be corrected.
Hellera said:
Yes, I know that... but is frustrating to do this everytime when I need access to the phone storage. Thanks anyway!
Maybe the next build will be corrected.
Click to expand...
Click to collapse
I agree with you, but we have to be patient.
Don't forget that we have the chance having a developer who makes a great work.
It's a first release of crDroid 9.
Before installing this rom, I installed various A13 roms.
None of them had the problem of MTP file transfer but other disadvantages like "No advanced restart", ...
After flashing Magisk in TWRP, launching the Magisk app results in it saying "Downloading" and loading forever.
tomikaka said:
After flashing Magisk in TWRP, launching the Magisk app results in it saying "Downloading" and loading forever.
Click to expand...
Click to collapse
TWRP version? Magisk Version?
` Can-dlE ! said:
The same issue here. That's why i'll wait for fixed version. Even Gapps installing just some of packages. There is no option to install any .APK file or to install any Google Play's aplication. Cant install magisk too. Always problem with storege.
Click to expand...
Click to collapse
for me its all working.

Categories

Resources