{
"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"
}
Resurrection Remix Q
Code:
[SIZE="4"]/*
* 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.
*/[/SIZE]
Resurrection Remix the ROM has been based on LineageOS, SlimRoms, Omni and original Remix ROM builds, this creates an awesome
combination of performance, customization, power and the most new features, brought directly to your Device.
Many things that in previous versions were tweaked with mods, are now included by default in the ROM so, please enjoy!
Special thanks to the LineageOS team, Omni team, SlimRoms and of course to all the supporters.
Make sure you have a custom recovery installed(TWRP is the preferred recovery)
Download the latest Resurrection Remix Rom & the latest GApps package
Boot into recovery
Perform a FULL factory wipe and wipe/system and dalvik cache as a precaution
Flash ResurrectionRemix Rom
Flash Google Apps package(Optional)
Flash Magisk Root(Optional)
First boot may take up to 10 minutes.
RROSQ-KUNTAO
GApps
Resurrection Remix Source
Device Source
Kernel Source
Vendor Source
XDA Developers
LineageOs Team
AICP
Crdroid
AOSIP
DU
Xtended
Evolution X
Bliss
Omni Team
And Of Course To All The Supporters, Donators And Users
Join our Telegram channel : https://t.me/resurrectionremixchat
If you have a major bug to report that has not been reported already, please take the following steps to report it to us. It will save you, Team Resurrection Remix and me quite some time.
Download the MatLog app from the Play Store.
After downloading the MatLog app, go to the app settings, and change the log level to Debug.
Clear all previous logs and take the exact steps to produce the error you are receiving. As soon as you receive the error (probably a force close), go straight into MatLog and stop the log recording.
Copy and paste the entire log either to Hastebin or Pastebin
Save the log, and copy and paste the link into the thread with a brief description of the error.
Fixed
Good to see RR back in action [emoji846]
Wysłane z mojego Lenovo P2a42 przy użyciu Tapatalka
Just installed RR. Will report in a couple od days. So far no problems with instalation.
Sohit5s said:
Charging led doesn't work.
For notifications it works.
Click to expand...
Click to collapse
RROS-Q has already been released-8.6.3-20201024-kuntao-Unofficial.zip and you have from 20201023. Maybe from October 24 already fixed this case with the led??
Вот здесь..... https://sourceforge.net/projects/roms5/
Does FM radio work?
boris555 said:
RROS-Q has already been released-8.6.3-20201024-kuntao-Unofficial.zip and you have from 20201023. Maybe from October 24 already fixed this case with the led??
Вот здесь..... https://sourceforge.net/projects/roms5/
Click to expand...
Click to collapse
I have report that it works in 23-oct build.
But for me personally it doesn't work.
Sutcliffe9 said:
Does FM radio work?
Click to expand...
Click to collapse
Yes, it works.
Sohit5s said:
I have report that it works in 23-oct build.
But for me personally it doesn't work.
Click to expand...
Click to collapse
It doesn't work for me either.
boris555 said:
RROS-Q has already been released-8.6.3-20201024-kuntao-Unofficial.zip and you have from 20201023. Maybe from October 24 already fixed this case with the led??
Вот здесь..... https://sourceforge.net/projects/roms5/
Click to expand...
Click to collapse
Did u test the 24 Oct build??
Sohit5s said:
Did u test the 24 Oct build??
Click to expand...
Click to collapse
Now installed but only without Gapps. From October 24, it works bro!!! The led responds to USB when the cable cord is connected.
Can you apply for official RR REMIX as an official maintainer?
Skorp Knight said:
Can you apply for official RR REMIX as an official maintainer?
Click to expand...
Click to collapse
No, I won't. That would not make a difference in rom, except for official tag.
lenovo p2 resurrection remix 10 failed to flash
1) Problem:
mishra1320 said:
Please help. I can't flash my Lenovo P2, failing on both images available. What am I doing wrong ?
Click to expand...
Click to collapse
FIX: The problem was in TWRP version, which initially was 3.0.3-0. After I've updated TWRP to twrp-3.4.0-0-kuntao.img - everything went smooooooth !
2) Problem: I had to wipe all my user data because it was on EXT4 and encrypted, so I got error while TWRP was trying to mount /data: "could not mount /data and unable to find crypto footer".
FIX: Change the partition type of /data to f2fs, format it and then wipe everything up again and only after that the installer worked like a charm.
Thank you, Sohit5s, for your great efforts! :good:
I could not even imagine that my Lenovo P2 will run Android 10 with Resurrection Remix in 2020. It is a dream came true!
Okay. I understand..WELL, thanks for this great ROM. MUCH APPRECIATED
unauthorized device attached
Is there any way of getting ADB working on this ROM ?
The problem is that I can't connect Lenovo P2 with RR 8.6.3 by KUNTAO to my notebooks (one with Win7, other with Win10). There is no system pop-up prompt on the phone upon connecting to PC host about allowing USB debugging. There is no option "Revoke USB debugging authorization" under Developer Options.
At the moment I stuck with error:
d:\adb>adb devices
* daemon not running; starting now at tcp:5037
* daemon started successfully
List of devices attached
ZZ223ZZ3ZZ unauthorized
Here's the list of what I tried:
1) change drivers for USB connection - no effect (universal USB drivers, Samsung USB drivers and finally, Lenovo USB drivers from "rescue_and_smart_assistant_v5.3.0.21_signed_setup.exe" package).
2) delete all files in my windows adb profile c:\Users\%username%\.android\adbkey and c:\Users\%username%\.android\adbkey.pub , then plug-in the phone again.
3) i even checked up the content of phone's adb keys directory, located at /data/misc/adb - this directory is always empty no matter what I did to connect the phone to PC host.
Is this a bug or a feature? Is there any way of fixing that ADB unauthorized device error?
Help ?
p.s. I tried to connect my other phone (on Android 10 too) via USB on the same PC host, got the prompt on the phone about trusting, and ADB see the other phone okay:
d:\adb>adb devices
List of devices attached
R38R33DB6FD device
ZZ223ZZ3ZZ unauthorized
mishra1320 said:
Is there any way of getting ADB working on this ROM ?
The problem is that I can't connect Lenovo P2 with RR 8.6.3 by KUNTAO to my notebooks (one with Win7, other with Win10). There is no system pop-up prompt on the phone upon connecting to PC host about allowing USB debugging. There is no option "Revoke USB debugging authorization" under Developer Options.
At the moment I stuck with error:
d:\adb>adb devices
* daemon not running; starting now at tcp:5037
* daemon started successfully
List of devices attached
ZZ223ZZ3ZZ unauthorized
Here's the list of what I tried:
1) change drivers for USB connection - no effect (universal USB drivers, Samsung USB drivers and finally, Lenovo USB drivers from "rescue_and_smart_assistant_v5.3.0.21_signed_setup.exe" package).
2) delete all files in my windows adb profile c:\Users\%username%\.android\adbkey and c:\Users\%username%\.android\adbkey.pub , then plug-in the phone again.
3) i even checked up the content of phone's adb keys directory, located at /data/misc/adb - this directory is always empty no matter what I did to connect the phone to PC host.
Is this a bug or a feature? Is there any way of fixing that ADB unauthorized device error?
Help ?
p.s. I tried to connect my other phone (on Android 10 too) via USB on the same PC host, got the prompt on the phone about trusting, and ADB see the other phone okay:
d:\adb>adb devices
List of devices attached
R38R33DB6FD device
ZZ223ZZ3ZZ unauthorized
Click to expand...
Click to collapse
Install adb drivers for windows
Sohit5s said:
Install adb drivers for windows
Click to expand...
Click to collapse
May I ask you to share what driver version you've been using to connect your Lenovo P2 over adb for windows?
mishra1320 said:
May I ask you to share what driver version you've been using to connect your Lenovo P2 over adb for windows?
Click to expand...
Click to collapse
ADB_DRIVERS
Is VoLTE working?
DS-1 said:
Is VoLTE working?
Click to expand...
Click to collapse
Yes bro.
Related
{
"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"
}
Resurrection Remix P
Code:
[SIZE="4"]/*
* 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.
*/[/SIZE]
Resurrection Remix the ROM has been based on LineageOS, SlimRoms, Omni and original Remix ROM builds, this creates an awesome
combination of performance, customization, power and the most new features, brought directly to your Device.
Many things that in previous versions were tweaked with mods, are now included by default in the ROM so, please enjoy!
Special thanks to the LineageOS team, Omni team, SlimRoms and of course to all the supporters.
Install TWRP Treble custom recovery:
> IMG file is here <
or
> Fastboot auto installation is here <
then
Download the latest Resurrection Remix Rom & the latest GApps package
Boot into recovery
Perform a FULL factory wipe and wipe/system and dalvik cache as a precaution
Flash ResurrectionRemix Rom
Flash Google Apps package(Optional)
Flash Magisk Root(Optional)
First boot may take up to 10 minutes.
For first start, you may have a bug, when you will be restarted in recovery.
Repeat wiping and installing the firmware, download > this file <, boot into TWRP, click the Install button, click the IMG button, select this file and then tick the Boot, swipe to install and reboot into the system (you can also use this instruction to switch SE Linux to permissive mode).
After a successful launch, go back to the recovery and reinstall the firmware.
With any of the following firmware installations, you will no longer need these actions.
ROM Download
GApps
Resurrection Remix Source
Device Source
Kernel Source
Vendor Source
XDA Developers
LineageOs Team
Omni Team
And Of Course To All The Supporters, Donators And Users
If you have a major bug to report that has not been reported already, please take the following steps to report it to us. It will save you, Team Resurrection Remix and me quite some time.
Download the MatLog app from the Play Store.
After downloading the MatLog app, go to the app settings, and change the log level to Debug.
Clear all previous logs and take the exact steps to produce the error you are receiving. As soon as you receive the error (probably a force close), go straight into MatLog and stop the log recording.
Copy and paste the entire log either to Hastebin or Pastebin
Save the log, and copy and paste the link into the thread with a brief description of the error.
Additions:
Alternative CPU modes is > here < (reinstallation is required after each firmware upgrade).
Android 9 has a lot of animation. Which is often undermined, on ours is no longer the most recent memory. Disabling caching is not an option, so go to the developer settings (how to do this, see F.A.Q.) and in all the lines where the animation speed in size 1.0 is mentioned - set the recommended value to 0.5 or NO if you don’t need it at all. In addition, there are many specific animation settings in RR, and these parameters can also affect their speed (for example, accelerate the effect of an old TV more than necessary), keep in mind, experiment. It is possible that replacing standard transitions with those from RR will give the best option and you will not need to change anything in the developer settings.
>>>>>>> Donat Link <<<<<<<
XDA:DevDB Information
[ROM][9.0][OFFICIAL] Resurrection Remix Pie v.7.x.x for Nubia Z9 Max [NX512J], ROM for all devices (see above for details)
Contributors
TTTT555, TTTT555
Source Code: https://github.com/TTTT555/android_device_nubia_nx512j/tree/rr-p
ROM OS Version: 9.x Pie
ROM Kernel: Linux 3.10.x
Version Information
Status: Nightly
Created 2019-06-06
Last Updated 2019-06-06
Z9max NX510J
thanks for your efforts
is it possible to have Android9.0 for Z9max Nx510J,as well?
thanks in advance
amirbahalegharn said:
thanks for your efforts
is it possible to have Android9.0 for Z9max Nx510J,as well?
thanks in advance
Click to expand...
Click to collapse
Only if you find a person who can rebuild the kernel for this device.
Stay in the logo after installing the rom, can't start normally.（Already installed according to theme）
uhjdfhg said:
Stay in the logo after installing the rom, can't start normally.（Already installed according to theme）
Click to expand...
Click to collapse
Same.
I have already used the sp_rr7_boot.img which you've attached in your goole drive document, it still suck in the Nubia logo.
TTTT555 said:
Only if you find a person who can rebuild the kernel for this device.
Click to expand...
Click to collapse
https://github.com/nubia-development/android_kernel_nubia_msm8994
{
"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.
*
* 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.
*/
The Mi Note 10 Lite (toco) has been with us for not that long but has proved to be a pretty awesome device. There is also not much development on the device as at the time of writing this article but @mauronofrio has managed to build a Test-TWRP that you can learn more about HERE. Toco launched with Android 10 out of the box which brings about dynamic partitioning which TWRP has not yet supported. The good thing is that this has not prevented us from being able to tinker with the device once you have the bootloader unlocked. I have managed to set up a GSI on my unit and I will lay out the process I followed here for any other user who want to try.
GSIs Tested
HavocOS v3.7 Link (arm64-A/B) - Credits to @turboxluke - 09/07/2020 with July security patch
HavocOS v3.6 Link (arm64-A/B) - Credits to @turboxluke
AOSP 10.0 v220 Link (arm64-A/B) - Credits to @phhusson
Known Issues
FOD
Bluetooth audio - Fixed on 09/07/2020 - Check the 1st fix in the Fixes section
Let me know in case of other issues arising
Instructions For Flashing:
1. Download GSI with Gapps (Recommended since TWRP is not fully functional)
2. Extract the compressed GSI zip to reveal the *.img file
3. Backup your important data as this process will wipe your data
4. Reboot your Mi Note 1o Lite into bootloader mode
5. Launch a command interface in the folder containing the GSI
Type the commands below in the sequence they are in (NB: Device has to be in bootloader mode)
Code:
fastboot -w
fastboot reboot fastboot
fastboot erase system
fastboot flash system nameofGSI.img
fastboot reboot bootloader
fastboot reboot
6. Set up your device after first-time boot, establish root with Magisk and apply the fixes below
GSI Fixes
1. Audio Stutter Fix
This is the first, simple and MOST RECOMMEDED method to fix Audio Stutter is to navigate to Settings > Phh Treble Settings > Misc features > and tick the "Disable audio effects" option as shown with the attached image. This method will have all the audio working including the Bluetooth Audio. I fiddled with the various options and got to this fix and thank you to @alex.msk-dev for testing to confirm this fix. 09/07/2020
Audio stutter fix Magisk Module @AndroidHQ254 - Flash in Magisk
2. Adaptive brightness fix (Updated on 09/07/2020) @AndroidHQ254 - copy to /system/overlay/ folder and set rw-r-r permisions
3. GSI lag fix @alex.msk-dev - Flash in Magisk
4. GSI_Fix_havoc3.6_toco_v2 | Mirror by @alex.msk-dev (Flash this fix with Magisk on Havoc 3.6 ONLY)
This HavocOS v3.6 Magisk Module fixes;
Add lawnchair (full work 10-Q)
Fixed SafetyNet
Fixed work Gpay
Add aptX and aptXHD
Fix margins and rounding status bar
Delete stock ShadyQuickStep launcher
Add support AOD, 3.5 jack.
Add power_profile
Add native brightness settings
5. ComboFix_GSi_toco070720 by @alex.msk-dev (Flash this fix with Magisk on ANY GSI)
09/07/2020 This GSI Combo Magisk Module fixes;
* add lawnchair (full work 10-Q)
* fixed SafetyNet
* fixed work Gpay
* Add aptX and aptXHD
* Delete stock ShadyQuickStep launcher (HavocOS)
* Add support AOD, 3.5 jack.
* Add power_profile
* Add native brightness settings
Downloads:
Find download links above in the "GSIs Tested" section
Sources:
Overlay
Credits
Alex Msk (alex.msk-dev) @ XDA
Support
Hello, if you like my work, you may support me by donating:
PayPal
XDA:DevDB Information
Android 10 GSI On Mi Note 10 Lite (toco), ROM for the Xiaomi Mi Note 10
Contributors
AndroidHQ254
ROM OS Version: Android 10
ROM Kernel: Linux 4.x
ROM Firmware Required: Clean Stock Firmware
Version Information
Status: Beta
Beta Release Date: 2020-07-01
Created 2020-07-01
Last Updated 2020-07-11
Reserved
Havoc GSI is working on tucana too btw
ItsBen12000 said:
Havoc GSI is working on tucana too btw
Click to expand...
Click to collapse
But the installation method is not similar to that of tucana
@AndroidHQ254 Thank you for this guide, will there be a Bluetooth audio fix from you?
harry0815 said:
@AndroidHQ254 Thank you for this guide, will there be a Bluetooth audio fix from you?
Click to expand...
Click to collapse
I am exploring possible fixes so the one that works will be posted here
Failed
m_a_omar said:
Failed
Click to expand...
Click to collapse
Your image cannot be loaded. Kindly upload a viewable image
Manual not working for me. My bootloader is unlocked and Miui 11.0.10.0(QFNEUXM) software is on the device.
harry0815 said:
Manual not working for me. My bootloader is unlocked and Miui 11.0.10.0(QFNEUXM) software is on the device.
Click to expand...
Click to collapse
Seems you have a driver issue that is why you are stuck at that waiting message. I faced a similar issue and what I did was to disable driver signature enforcement on my Windows 10 and then installing the drivers. You can also substitute the fastboot -w command with going to the stock recovery and performing a factory reset.
Failed (waiting for device) stuck in fastbootd mode only
AndroidHQ254 said:
Seems you have a driver issue that is why you are stuck at that waiting message. I faced a similar issue and what I did was to disable driver signature enforcement on my Windows 10 and then installing the drivers. You can also substitute the fastboot -w command with going to the stock recovery and performing a factory reset.
Click to expand...
Click to collapse
OK Thank you, I now have the HavocOS v.3.6 rom on it, but I can't get it to copy the adaptive brightness fix, I'm using Root Explorer, it has root rights, my device is also rooted, what am I doing wrong?
harry0815 said:
OK Thank you, I now have the HavocOS v.3.6 rom on it, but I can't get it to copy the adaptive brightness fix, I'm using Root Explorer, it has root rights, my device is also rooted, what am I doing wrong?
Click to expand...
Click to collapse
The fix is a Magisk Module so install it in Magisk
m_a_omar said:
Failed (waiting for device) stuck in fastbootd mode only
Click to expand...
Click to collapse
Seems you have a driver issue that is why you are stuck at that waiting message. I faced a similar issue and what I did was to disable driver signature enforcement on my Windows 10 and then installing the drivers.
Post Updated!
09/07/2020 Changelog:
1. Audio stutter fix without breaking Bluetooth Audio or use of a magisk module
2. Updated the overlay - now enable AOD, tweaked auto-brightness values...
2. Lag fix for that extra smooth experience
3. A GSI combo module - Previously it was just for HavocOS
4. Added link for the latest HavocOS v3.7 GSI with the July security patch
@AndroidHQ254
Wow!! Fantasic! In other words..no more bugs apparently?
Yes Bluetooth audio now works really well, thanks to AndroidHQ254:good:
nfraccar said:
@AndroidHQ254
Wow!! Fantasic! In other words..no more bugs apparently?
Click to expand...
Click to collapse
FOD remaining as of now. We hope to get a fix soon too for that
harry0815 said:
Yes Bluetooth audio now works really well, thanks to AndroidHQ254:good:
Click to expand...
Click to collapse
Am happy to know that it is working for you and feel most welcome. Happy to help and contribute where I can
AndroidHQ254 said:
FOD remaining as of now. We hope to get a fix soon too for that
Click to expand...
Click to collapse
Face unlock is there?
Other thing. How did you install magisk?
Did you flash boot twrp then flash magisk after first time installation or..?
{
"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.
*
* 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.
*/
LineageOS is a free, community built, aftermarket firmware distribution of Android 10, which is designed to increase performance and reliability over stock Android for your device.
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. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
Downloads :
SourceForge folder (includes rom, dtbo image, LineageOS recovery image)
Installation :
You MUST have unlocked botloader and android 10 firmware on your phone
1) Flash LineageOS recovery via fastboot
fastboot flash boot <name of the file>
2) Reboot to recovery
3) Perform factory reset
4) Navigate Apply update -> apply from ADB
5) Sideload rom .zip
adb sideload <rom zip name>
6) Reboot recovery (Advanced -> Reboot to recovery)
7) Now you can sideload gapps or magisk if you need them (recovery might give you a warning about flashing unsigned files, just click second option and installation process will continue)
adb sideload <zip name>
8) "Reboot system now"
9) If you have broken wifi/bt flash dtbo image via fastboot linked at this page
fastboot flash dtbo <name of img>
Notes :
- This is personal build for my own usage, I'm just sharing it
Trees :
Common tree: https://github.com/HarukeyUA/android_device_xiaomi_sm6125-common (Thanks @DarkJoker360 @erfanoabdi for their work for sm6125 common tree)
Device tree: https://github.com/HarukeyUA/android_device_xiaomi_laurel_sprout
Kernel: https://github.com/HarukeyUA/android_kernel_xiaomi_laurel_sprout
Vendor: https://github.com/HarukeyUA/proprietary_vendor_xiaomi
Reserved
Hi and thanks for the work. Has it dual app?
OP
New build is up.
Clean flash is highly recommended to avoid any issues.
Changelog:
- LineageOS source sync
- Fixed incall sound in some voip apps (e. g. discord, google duo)
- SELinux enforcing
- New kernel based off android-linux-stable (4.14.212) with LA.UM.8.11.r1-04800-NICOBAR.0 caf tag merged (kernel, audio, wlan)
- Kernel includes BBR tcp algo by default, wireguard, sdfat, exfat support
Link: SourceForge
I will test this rom bro
New build is up.
Changelog:
- Fixed DT2W
- Fixed 4k video recording
- Imported brightness values from bonito (pixel 3a)
- Enabled aod
- Removed xiaomi doze
- Added fod pressed icon from stock
- Kernel: 4.14.213
Link: SourceForge
Kedeck said:
I will test this rom bro
Click to expand...
Click to collapse
We are waiting for your experience/feedback
I will try asap. Feel so good
has anybody feedback? is this suitable for daily use?
Typhoon_Master said:
has anybody feedback? is this suitable for daily use?
Click to expand...
Click to collapse
solid as a rock. fod is a bit buggy, on par with other oss roms. sot 9-10 hours, no gaming. found no bugs or glitches whatsoever. 10/10. this is the best rom for your a3, period.
New build is up.
Changelog:
- LineageOS source sync
- Kernel: 4.14.214
Link: SourceForge
Harukey said:
New build is up.
Changelog:
- LineageOS source sync
- Kernel: 4.14.214
Link: SourceForge
Click to expand...
Click to collapse
Tnx for sharing your personal rom to community
I did the exactly same way described on the main thread to flash the rom on my phone but for some reason I get boot looped every-time, I flashed the recovery, rom, open-gapps and magisk
After selecting Advanced -> Reboot to recovery I got completely black screen, cant get either fastboot or recovery ... MiFlash detects COM3 and tyring to flash gets me error: cannot receive hello packet
luisgerardo01 said:
After selecting Advanced -> Reboot to recovery I got completely black screen, cant get either fastboot or recovery ... MiFlash detects COM3 and tyring to flash gets me error: cannot receive hello packet
Click to expand...
Click to collapse
i am in the same situation. have you resurrected your phone somehow?
*****************************************************************************************
* DISCLAIMER *
* ROMs are published as is, without any guaranty. *
* They are built automaticaly without test. *
* I am not responsable if you phone is bricked, burned or if it speaks french. *
*****************************************************************************************
UNOFFICIAL LineageOS + microG
{
"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"
}
As a LineageOS fan, I realy wanted to see this ROM on Nothing Phone 1.
So I merged some git repos and published the result.
I am not a developer, please do not send bug report or feature request.
ROM customisation :
* microG with related apps included
* Fdroid with privilegied extension preinstalled
* Aurora preinstalled (Aurora Services will come in future builds)
* OTA configured
Many thanks to :
* Lineage OS team
* microG team
* evox for NP1 specific source code
What does not work :
* Bluetooth : ON/OFF switch stay OFF
* Fingerprint : It detect when you put your finger on it but can not "read" it.
* NFC
* Glyph Interface only show batery charge
* SELinux is disabled
* ROM are signed with self-signed certificate
* Low mic sound level
* You tell me
DOWNLOAD : https://los.vosky.fr
Installation :
* Download Lineage recovery : https://los.vosky.fr/builds/full/lineage-20.0-UNOFFICIAL-Spacewar-recovery.img (right-click -> Save-as)
* Boot on it : fastboot boot lineage-20.0-UNOFFICIAL-Spacewar-recovery.img
* Flash ROM with adb : adb sideload lineage-20.0-XXXXYYZZ-UNOFFICIAL-Spacewar.zip
Source code
* Lineage OS : https://github.com/LineageOS
* device tree : https://gitlab.storozhev.net/evox/android_device_nothing_Spacewar
* vendor : https://gitlab.storozhev.net/evox/android_vendor_nothing_Spacewar
* kernel : https://gitlab.storozhev.net/evox/android_kernel_nothing_sm7325
* MicroG : https://github.com/microg
Vosky said:
Installation :
* Download Lineage recovery : https://los.vosky.fr/builds/full/lineage-20.0-UNOFFICIAL-Spacewar-recovery.img
Click to expand...
Click to collapse
not worging
there is something wrong with the download link
Exodusnick said:
not worging
there is something wrong with the download link
Click to expand...
Click to collapse
Right clic on the link > Save as > File is good
Apparently this link open file like a xml file instead download file
Pho3nX said:
Right clic on the link > Save as > File is good
Apparently this link open file like a xml file instead download file
Click to expand...
Click to collapse
Heyy,
how are you, I hope it is going okie
May I ask something, did you try this rom already?
If so, how was your experience with it? Many thanks in advance!
Ofdas23 said:
Heyy,
how are you, I hope it is going okie
May I ask something, did you try this rom already?
If so, how was your experience with it? Many thanks in advance!
Click to expand...
Click to collapse
Hey;
Not tested, i'm actually on Stock NOS 1.5 beta and (for me) i like so much, and i need Google Apps for my work.
I hope someone will feeback this rom, a lot of people searching after a vanilla MicroG Custom from a long time.
Pho3nX said:
Hey;
Not tested, i'm actually on Stock NOS 1.5 beta and (for me) i like so much, and i need Google Apps for my work.
I hope someone will feeback this rom, a lot of people searching after a vanilla MicroG Custom from a long time.
Click to expand...
Click to collapse
I just went back to stock as well, and right now in the progress of updating to 1.5
Thank you, for your reply ^^
You didnt tell me how you are though, mister
Going to test this. Would you like logs or do you have a TG channel?
dememted1 said:
Going to test this. Would you like logs or do you have a TG channel?
Click to expand...
Click to collapse
Nice, Great start. Thanks
Thanks for the latest build 24/12/22
Has anyone got this rom to work??
mollex said:
Can the installation also be done using the "*#*#682#*#*" method?
Click to expand...
Click to collapse
I did not know this method.
Sorry I can't try as I already use the ROM, so Nothing offline update menu is not available.
With your phone app you call *#*#682#*#* and in the folder ota in the root of your phone the correct zip file. For example, I was able to install NOTHING OS 1.5 (NOTHING OS 1.5.zip) over my EEA Full Nothing OS 1.1.7.
Very interested in this. Did anyone get it to work?
I love Lineage, but I would like to have a build without signature spoofing.
MicroG is not a good solution for a daily driver in my opinion.
So, I will wait for a Lineage with GAPs and Glyph support.
I installed this ROM last night and its working great. So far I have noticed no issues. My old phone is Lineage and I don't use Google. I'll continue to test for a couple days and report back here if I notice anything.
Thank you for building this ROM!
I'm using a PIN code but noticed the finger print reader isn't working. I don't care about the Glphys on the back either.
zeekPhotonic said:
I'm using a PIN code but noticed the finger print reader isn't working. I don't care about the Glphys on the back either.
Click to expand...
Click to collapse
Hi, thank you for your feedback.
There is a list of features that do not work in first post.
Please tell us if you see anything else.
sudo fastboot boot lineage-20.0-UNOFFICIAL-Spacewar-recovery.img
creating boot image...
creating boot image - 1167599616 bytes
Sending 'boot.img' (1140234 KB) FAILED (remote: 'Requested download size is more than max allowed')
fastboot: error: Command failed
Edit:
Newest version of platform tools installed
Original cable used (direktly into the usb-c of my mainboard)
The_Toady said:
sudo fastboot boot lineage-20.0-UNOFFICIAL-Spacewar-recovery.img
creating boot image...
creating boot image - 1167599616 bytes
Sending 'boot.img' (1140234 KB) FAILED (remote: 'Requested download size is more than max allowed')
fastboot: error: Command failed
Click to expand...
Click to collapse
Try downloading and using the latest version of platform tools from https://developer.android.com/studio/releases/platform-tools.
OrangeFox 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 recovery
* 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.
*
*/
OrangeFox is FREE SOFTWARE
Supports Treble, Miui, Custom Roms
Downloads: https://www.mediafire.com/folder/rn5f7emnkkm1k/ofox
Notes:
Read very carefully the documentation (Guides, FAQ, etc - linked below), plus the build notes on the download site, before trying anything
INSTALLATION:
0. Backup your ROM, your data, your internal storage, and your settings/apps, to an External storage medium [OPTIONAL]
1. Download the OrangeFox zip file to your device
2. Reboot to your Custom Recovery
3. Flash the OrangeFox zip file as a normal zip
4. The device will automatically reboot into OrangeFox recovery after installation (allow this to happen)
5. Enjoy!
* For a more detailed installation guide, see Installing OrangeFox Recovery.
Guides; Frequently Asked Questions; Installation; Troubleshooting; Sundry Information:
* See https://wiki.orangefox.tech/en/guides/
Credits
* TeamWin - for TWRP
* The OrangeFox Team - for your hard work
* All our testers - for your patience and help
FEATURES:
* Updated with latest TWRP commits
* Built-in support for installing init.d functionality
* Built-in support for installing Magisk
* Flashlight
* Password, torch, led
* Support for Most of the Custom ROMs and the Stock Rom
* Superb new UI and themes
BUGS:
* Needs to wipe data firstly -> reboot to recovery -> then format data
* If your PC not detecting ofox internal storage then
Go to mount select system then turn off and on MPT
OrangeFox, Tool/Utility for the Xiaomi MI A3
Contributors
Ryukendo9
Version Information
Status: Beta
Stable Release Date: 2023-01-19
Created 2023-01-19
Last Updated 2023-01-19
instead of saying "Thanks", Press the ':good: Thanks!' Button.
Hi,
Can I flash all the roms available to this device using this recovery? For example, SparkOS, EvolutionX, LOS etc. which needs to be sideloaded through los recovery...
Shawmik said:
Hi,
Can I flash all the roms available to this device using this recovery? For example, SparkOS, EvolutionX, LOS etc. which needs to be sideloaded through los recovery...
Click to expand...
Click to collapse
Yes u can
It behaves strange in slot A: PC don't see sdcard and reboot options doesn't work. In slot B everything is fine, love it . Do you know what's wrong?
UPD: Now it doesn't want wipe data after reflash on either slot Have to return to losrecovery
demSo said:
It behaves strange in slot A: PC don't see sdcard and reboot options doesn't work. In slot B everything is fine, love it . Do you know what's wrong?
Click to expand...
Click to collapse
Here no issues. Still share the logs . We will look into it. Thx
Is it better than TWRP?
P_ablo24 said:
Is it better than TWRP?
Click to expand...
Click to collapse
That's subjective. U may like twrp , ofx or other. Orangefox have much feature. So, try all other recovery n decide
Ryukendo9 said:
That's subjective. U may like twrp , ofx or other. Orangefox have much feature. So, try all other recovery n decide
Click to expand...
Click to collapse
I have never installed a recovery, I tried 1 year ago and ended up bricking the phone. I managed to unblock it without TEST POINTS. Something quite rare.
P_ablo24 said:
I have never installed a recovery, I tried 1 year ago and ended up bricking the phone. I managed to unblock it without TEST POINTS. Something quite rare.
Click to expand...
Click to collapse
DM me on telegram i will help u there
Ryukendo9 said:
DM me on telegram i will help u there
Click to expand...
Click to collapse
Okay.
Ryukendo9 said:
DM me on telegram i will help u there
Click to expand...
Click to collapse
t.me/P4blo24 is my telegram. I still don't know very well how XDA works.