Database Develop

[RECOVERY][ROOT]TWRP 3.2.3-1 Galaxy A7 2018/A750

Unofficial release -TWRP recovery for the Galaxy A7 2018 - SM-A750F EXYNOS 7885
{
"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"
}
TWRP 3.2.3-0 Released
Aug 6, 2018
TWRP 3.2.3-0 is out now for most currently supported devices.
What's new in 3.2.3-0:
* Fix automatic installing of OTA zips on encrypted devices
* Remove SuperSU from TWRP
* Support both md5 and md5sum file extensions when doing MD5 checking for zip files
Want to get notifications when we release new versions of TWRP? Install the TWRP app and select your device!
We need your help! The bulk of TWRP work is done by a handful of people on a volunteer basis. We have pushed most of our device files to our github and we have a gerrit instance. If you have the ability, please help us maintain our official devices and/or add your device to our official device list. Thanks in advance!
You can track the progress of builds here
Update 25/12/2018
Beta build released.
Current status - (Tested working)
Treble supported
You flash this at your own risk. Please ensure you have the stock ROM to hand downloaded from SAMMOBILE in case of problems. This will trip the knox counter.
NOTE: ON ANDROID 5.1.1> DEVICES IT IS NECESSARY TO GO TO:
Settings -> Developer Options -> OEM unlocking
AND ENABLE OEM UNLOCK FIRST OR YOU MAY ENCOUNTER 'BLOCKED BY FRP LOCK' WHEN FLASHING.
*****INSTALL INSTRUCTIONS:*****
Flash with ODIN in the AP slot.
1. Put your device in DOWNLOAD mode.
(Hold POWER + VOL DOWN + VOL UP)
2. Load the file below into the AP slot, uncheck AUTO-REBOOT and hit start.
twrp_3.2.3-1_a750_251218
3. After flashing and ODIN reports PASS immediately force reboot to recovery. Do NOT let the device boot to the OS.
You should now see TWRP recovery.
4. Flash the RMM bypass zip
https://forum.xda-developers.com/attachment.php?attachmentid=4481843&d=1524258795
NOTE: FAILURE TO FOLLOW THE STEPS ABOVE IMPLICITLY WILL RESULT IN STOCK RECOVERY REPLACING TWRP AT FIRST BOOT.
5. Reboot to TWRP (Do not boot to the OS yet)
*****OREO ROOT INSTRUCTIONS:*****
NOTE: To mount data it is necessary to first *FORMAT* (not wipe) the /DATA partition using the FORMAT DATA button under the wipe options.
PLEASE NOTE THIS WILL DELETE EVERYTHING ON INTERNAL STORAGE AND FACTORY RESET THE DEVICE, SO BACK UP ANYTHING YOU WISH TO KEEP.
Continue with the instructions below to prevent the data partition becoming re-encrypted.
1. To root I suggest downloading and installing the latest Magisk as this is a currently supported project, SuperSu is no longer getting active development.
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
2. Copy the Magisk zip to a Micro sd card then install with TWRP.
3. Enjoy your rooted device.
DEVICE TREE: soon
PLEASE DO *NOT* DIRECT LINK TO THESE FILES. PLEASE LINK TO THIS POST
Credits: Me, Teamwin, @BlackMesa123 for RMM bypass zip.
Please note I don't own this device and spend a lot of my free time bringing these builds for you to use and benefit from.
FEEDBACK IS APPRECIATED PLEASE.
THANKS.
DONATE ME HERE IF YOU WANT TO BUY ME A BEER OR HIT THE THANKS BUTTON IF I HELPED YOU

158 views, 20 downloads and not one reply.
Smashing guys. :good:

4. перепрограммируйте обходной zip- архив rmm.можно поподробнее?
Mod edit: English please!
Google translation:
4. reprogram the rmm bypass zip archive. can you be more specific?

Odin shows Failed !! Tried 3 Times ? Had to Flash the Firmare Again.
Help !!

notoriouschyld said:
Odin shows Failed !! Tried 3 Times Had to Flash the Firmare Again.
Help !!
Click to expand...
Click to collapse
Sorry about that, build error on my end. Fixed now.

It will not work on SM-A750FNXXU1ARIC?

Sfuj24 said:
It will not work on SM-A750FNXXU1ARIC?
Click to expand...
Click to collapse
Is that a statement or question?

Hey. Does it work well? I wanted to install myself. but it seems to me that this is not a complete instruction. Does OEM unlock need to be enabled?

powermen27 said:
Hey. Does it work well? I wanted to install myself. but it seems to me that this is not a complete instruction. Does OEM unlock need to be enabled?
Click to expand...
Click to collapse
No matter how complete an instruction is, if you don't bother reading it in the first place it's not going to make any difference.
As clearly posted in the OP:
NOTE: ON ANDROID 5.1.1> DEVICES IT IS NECESSARY TO GO TO:
Settings -> Developer Options -> OEM unlocking
AND ENABLE OEM UNLOCK FIRST OR YOU MAY ENCOUNTER 'BLOCKED BY FRP LOCK' WHEN FLASHING.
Click to expand...
Click to collapse

sorry

ashyx said:
Sorry about that, build error on my end. Fixed now.
Click to expand...
Click to collapse
Tried with the new TWRP.img but I'm having a Bootloop on the Samsung Boot Screen.
Help
Take your Time !!

notoriouschyld said:
Tried with the new TWRP.img but I'm having a Bootloop on the Samsung Boot Screen.
Help
Take your Time !!
Click to expand...
Click to collapse
Can you tell me which firmware build number you are running and if possible a screen shot of your device screen while booted to download mode?

Stuck in bootloop after flashing twrp
A750FXXU1ARK7

A7whatever said:
Stuck in bootloop after flashing twrp
A750FXXU1ARK7
Click to expand...
Click to collapse
Can you try this build, it's built with the kernel from the latest source available - A750FNXXU1ARIC.
Be aware OEM unlock must be enabled and you MUST boot to TWRP immediately after flashing with ODIN. Do not boot to the OS.
In TWRP immediately install Magisk.
https://androidfilehost.com/?fid=11410963190603874542

ashyx said:
Can you try this build, it's built with the kernel from the latest source available - A750FNXXU1ARIC.
Be aware OEM unlock must be enabled and you MUST boot to TWRP immediately after flashing with ODIN. Do not boot to the OS.
In TWRP immediately install Magisk.
Click to expand...
Click to collapse
Same bootloop at the Samsung screen
However i use heimdall not odin so I have to unpack the tar file and flash the recovery image. i also use it to flash the stock recovery and it works perfectly
Does using it make a difference?
Edit: my phone is A750FNXXU1ARK2
A750FXXU1ARK7 Was my build number

A7whatever said:
Same bootloop at the Samsung screen
However i use heimdall not odin so I have to unpack the tar file and flash the recovery image. i also use it to flash the stock recovery and it works perfectly
Does using it make a difference?
Edit: my phone is A750FNXXU1ARK2
A750FXXU1ARK7 Was my build number
Click to expand...
Click to collapse
Can you flash the bootloader from A750FNXXU1ARIC and see if it boots twrp?

ashyx said:
Can you flash the bootloader from A750FNXXU1ARIC and see if it boots twrp?
Click to expand...
Click to collapse
Flashed the old sboot.bin however got the same bootloop

A7whatever said:
Flashed the old sboot.bin however got the same bootloop
Click to expand...
Click to collapse
So just to be clear :
Immediately after flashing twrp you are forcing a boot to recovery directly from ODIN?

ashyx said:
So just to be clear :
Immediately after flashing twrp you are forcing a boot to recovery directly from ODIN?
Click to expand...
Click to collapse
Yes

A7whatever said:
Yes
Click to expand...
Click to collapse
Hmm looks like I'll have to take another look at the twrp config or kernel build.
If I pack the kernel into a boot image would you be willing to test if it boots?

[RECOVERY][UNOFFICIAL] TWRP for Galaxy S10 5G (Snapdragon)

{
"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"
}
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Code:
* Your warranty is now void.
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or your 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.
Supported Models:
Galaxy S10 5G G9770, G977U, G977U1 and G977W.
US/Canada bootloader unlock thread:
here
Download & Guide:
1. Unlock your bootloader.
2. Download S10 5G: beyondxq.
3. Reboot to download mode and flash vbmeta_disabled.tar in AP slot and reboot. Device will reboot to stock recovery mode prompting you to wipe data so wipe data and reboot to download mode again.
4. Put the TWRP tar for your device with Odin in the AP slot and click start.
5. Reboot to recovery via recovery key combo.
6. Disable encryption:
- Go to Advanced > Terminal, type: multidisabler.​If vendor complain about free space left on device, will attempt to resize vendor. and it ask to - Run multidisabler again!.​- Type: multidisabler again. will see - Finished. when done.​7. Go back to Wipe > Format Data > type yes.
8. Reboot to recovery.
9. Flash magisk apk in twrp.
10. Reboot to system, Enjoy.
Note:
Code:
To disable encryption manually:
You need to replace fileencryption=ice with encryptable=ice only in userdata line (maybe rest lines) in vendor/etc/fstab.qcom
To avoid stock recovery restoration manually:
Rename system/recovery-from-boot.p to recovery-from-boot.p.bak
Support:
Live support is available via #twrp on Freenode with your IRC client or just click this link.
Telegram group
Bugs:
- Encryption not fully working.
Thanks:
TWRP team
@Mentalmuso for base device tree
@jesec for unlock guide
@ianmacd for multidisabler
Sources:
Kernel tree
Device tree

Changelog:
30.11.2021 - Update to TWRP 3.6.0
- Update multidisabler
27.04.2021 - Update to G977PVPU6FUBH kernel source
31.12.2020 - Update TWRP to 3.5.0
20.11.2020 - Initial Release

You can add the G977P/T to the list as working, confirmed working on my G977T.

Is this still good for android 11?

If you need to download the latest version's twrp, you can do it this link(Download TWRP for beyondx)

G977B supported? Android 11?

Yoonwoo said:
If you need to download the latest version's twrp, you can do it this link(Download TWRP for beyondx)
Click to expand...
Click to collapse
This is the wrong one, this is for exynos, we are dealing with snapdragon here.

razercortex said:
You can add the G977P/T to the list as working, confirmed working on my G977T.
Click to expand...
Click to collapse
Just got my G977P, getting info on how to root Android 11 G977PVPS5EUA4, trying not to brick my device. Any tips on how to do it the safe way? First time trying to root Snapdragon device.

Absolutely! You need to first unlock the bootloader, so go into developer options and enable OEM unlock. After you enable it, reboot to DL mode by volume down + power. Select the power keys that allow for unlock and confirm with the displayed key press. After, follow this thread's guide. Then, download Magisk from the official github, it should be from topjohnwu, it will be in apk format, just rename it to zip. Flash in TWRP and you will be good to go!

razercortex said:
Absolutely! You need to first unlock the bootloader, so go into developer options and enable OEM unlock. After you enable it, reboot to DL mode by volume down + power. Select the power keys that allow for unlock and confirm with the displayed key press. After, follow this thread's guide. Then, download Magisk from the official github, it should be from topjohnwu, it will be in apk format, just rename it to zip. Flash in TWRP and you will be good to go!
Click to expand...
Click to collapse
Thanks! Is it safe to update to latest official software update before installing TWRP?

Yes, it shouldn't matter.

razercortex said:
Yes, it shouldn't matter.
Click to expand...
Click to collapse
Confirmed working on G977P, so fast and easy, thanks for the support!

razercortex said:
You can add the G977P/T to the list as working, confirmed working on my G977T.
Click to expand...
Click to collapse
Man I'm at a loss, I've followed this guide and nothing makes sense in terms of.
I'll get twrp installed just fine but the second i reboot my device it'll either throw me back into twrp or I'll get stuck in "Android is starting" and nothing will happen for hours. I'm on G977p and my bootloader is unlocked

Nexu F said:
Man I'm at a loss, I've followed this guide and nothing makes sense in terms of.
I'll get twrp installed just fine but the second i reboot my device it'll either throw me back into twrp or I'll get stuck in "Android is starting" and nothing will happen for hours. I'm on G977p and my bootloader is unlocked
Click to expand...
Click to collapse
Did you flash vbmeta? Also, starting android for the first time takes a really long time.

razercortex said:
Did you flash vbmeta? Also, starting android for the first time takes a really long time.
Click to expand...
Click to collapse
I did yes. I'll try this doing this guide once more later tonight. Could be quite possible I'm missing a step or didn't pay close attention to one since the others with the same Device on this thread reported a success

razercortex said:
Did you flash vbmeta? Also, starting android for the first time takes a really long time.
Click to expand...
Click to collapse
Any rough idea to how long the starting Android could take before i stop it?

Is the SM-G977N korean model supported
Android 11
Do you know how to access OEM Unlock in development. There is no sign of it on this phone.
Thanks

Any updates for Android 12 G977PVPS8HVE1 for SM-G977P (Sprint)? I can see the official firmware already out, but waiting for working version of TWRP.

Yo, idiot. This guide is for Beyondx not Snapdragon. Misleader.....

[RECOVERY][UNOFFICIAL] TWRP for Galaxy A71 (Snapdragon)

{
"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"
}
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Code:
* Your warranty is now void.
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or your 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.
Supported Models:
Galaxy A71 SM-A715F, SM-A715U, SM-A715U1, SM-A715V and SM-A715W.
US/Canada bootloader unlock thread:
here
Download & Guide:
1. Unlock your bootloader.
2. Download A71: a71.
3. Reboot to download mode and flash vbmeta_disabled.tar in AP slot and reboot. Device will reboot to stock recovery mode prompting you to wipe data so wipe data and reboot to download mode again.
4. Put the TWRP tar for your device with Odin in the AP slot and click start.
5. Reboot to recovery via recovery key combo.
6. Disable encryption:
- Go to Advanced > Terminal, type: multidisabler.​If vendor complain about free space left on device, will attempt to resize vendor. and it ask to - Run multidisabler again!.​- Type: multidisabler again. will see - Finished. when done.​7. Go back to Wipe > Format Data > type yes.
8. Reboot to recovery.
9. Flash magisk apk in twrp.
10. Reboot to system, Enjoy.
Note:
To disable encryption manually:
You need to replace fileencryption=ice with encryptable=ice only in userdata line (maybe rest lines) in vendor/etc/fstab.qcom
To avoid stock recovery restoration manually:
Rename system/recovery-from-boot.p to recovery-from-boot.p.bak
Click to expand...
Click to collapse
Support:
Live support is available via #twrp on Freenode with your IRC client or just click this link.
Telegram:
Link
Bugs:
- Encryption not fully working.
Thanks:
TWRP team
@ianmacd for multidisabler
Sources:
Kernel tree
Device tree

Changelog:
GitHub History

after unlock bootloader and root, fingerprint doesnt work.
how to fix it ?
thank you in advance

kevin mitnick said:
after unlock bootloader and root, fingerprint doesnt work.
how to fix it ?
thank you in advance
Click to expand...
Click to collapse
Dont use Ian multidisabler.

afaneh92 said:
Dont use Ian multidisabler.
Click to expand...
Click to collapse
I reflashing rom and reflashing twrp and not used ian multidisabler. but fingerprint still not fixed. please help

kevin mitnick said:
I reflashing rom and reflashing twrp and not used ian multidisabler. but fingerprint still not fixed. please help
Click to expand...
Click to collapse
Try this vbmeta disabler https://drive.google.com/file/d/1-4K--sTHhGY9ekmKd_oiaP0eoGrD4vAf/view?usp=drivesdk

afaneh92 said:
Try this vbmeta disabler https://drive.google.com/file/d/1-4K--sTHhGY9ekmKd_oiaP0eoGrD4vAf/view?usp=drivesdk
Click to expand...
Click to collapse
thank you sir..
I flashed this file, but still ask calibration for finger print and not fixed.

kevin mitnick said:
thank you sir..
I flashed this file, but still ask calibration for finger print and not fixed.
Click to expand...
Click to collapse
So other twrp recoveries are ok?

afaneh92 said:
So other twrp recoveries are ok?
Click to expand...
Click to collapse
I tried your twrp and ian recovery..still same..

Flashing The Twrp on Odin is ok. But when i flash using twrp with zip or img. Always showing in Red error.. reading flashin error..

alpher17 said:
Flashing The Twrp on Odin is ok. But when i flash using twrp with zip or img. Always showing in Red error.. reading flashin error..
Click to expand...
Click to collapse
post recovery log

kevin mitnick said:
I tried your twrp and ian recovery..still same..
Click to expand...
Click to collapse
still working on a fix

Sorry i forgoten my firm version is A715FXXS6BUI1 . Is not supported?

alpher17 said:
Sorry i forgoten my firm version is A715FXXS6BUI1 . Is not supported?
Click to expand...
Click to collapse
should be ok

afaneh92 said:
still working on a fix
Click to expand...
Click to collapse
I bought another a71 mainboard and the problem is still same. finger print need calibration. is that software or hardware problem ? finger print work well before unlock bootloader

kevin mitnick said:
I bought another a71 mainboard and the problem is still same. finger print need calibration. is that software or hardware problem ? finger print work well before unlock bootloader
Click to expand...
Click to collapse
I think disabling encryption broke it. This doesn't effect US devices only international variants on specific models.

afaneh92 said:
I think disabling encryption broke it. This doesn't effect US devices only international variants on specific models.
Click to expand...
Click to collapse
my device is a715fxx.
so, how to fix it ?
please help

kevin mitnick said:
my device is a715fxx.
so, how to fix it ?
please help
Click to expand...
Click to collapse
I cant help you now, as I said above still working on it. dont spam the thread.

@afneh92
afaneh92 said:
I cant help you now, as I said above still working on it. dont spam the thread.
Click to expand...
Click to collapse
Can you help me with something?
I have the TWRP 3.5.1 [ianmacd] recovery installed and a custom Samsung ROM (NcX 3.1.2).
I want to flash the stock firmware via odin to keep the ROM up to date (though without losing data, by flashing the HOME_CSC file).
I'll need to flash TWRP again to install Magisk and Root later via Odin as even though it wont format my data, it will flash on top of my current TWRP.
To install yours, what steps should i follow after i flash the Stock ROM again? (Remember that i wont lose data/need to encrypt the phone again)?

Pupet_Master said:
@afneh92
Can you help me with something?
I have the TWRP 3.5.1 [ianmacd] recovery installed and a custom Samsung ROM (NcX 3.1.2).
I want to flash the stock firmware via odin to keep the ROM up to date (though without losing data, by flashing the HOME_CSC file).
I'll need to flash TWRP again to install Magisk and Root later via Odin as even though it wont format my data, it will flash on top of my current TWRP.
To install yours, what steps should i follow after i flash the Stock ROM again? (Remember that i wont lose data/need to encrypt the phone again)?
Click to expand...
Click to collapse
There is 90% chance to lose data, make data backup move it to PC then try.
Note1: changing vbmeta will lose data so must flash same file.
Note2: if you disabled encryption need to do again.
Ignoring note 1&2 then rebooting to system will lose data

[ROM][11][AOSP] PixelExperience for OnePlus Nord N10 5G [UNOFFICIAL][BILLIE]

{
"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"
}
PixelExperience for OnePlus Nord N10 5G [billie]
What is this?
PixelExperience is an AOSP based ROM, with Google apps included and all Pixel goodies (launcher, wallpapers, icons, fonts, boot animation)
Our mission is to offer the maximum possible stability and security, along with essential and useful features for the proper functioning of the device
Based on Android 11
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.
*/
Whats working?
Wi-Fi
RIL
Mobile data
GPS
Camera
Flashlight
Bluetooth
Fingerprint reader
Face unlock
NFC
Lights
Sound/vibration
Known issues
DT2W
You tell me!
DON'T FLASH GAPPS, THEY'RE ALREADY INCLUDED
ROM: https://www.androidfilehost.com/?fid=2981970449027577418
MD5: 53C4B515DDCC722A59510C161209F916
SHA-1: CCA686001DA7959C0E953D1948FB3626CF66987F
RECOVERY: https://www.androidfilehost.com/?fid=2981970449027577417
MD5: BFE3114F2A966E03CFD0CF6C0040146B
SHA-1: B14B3102C97C15E3C7C045182489514C0827713F
In case you need it for magisk or any other reason, here's the boot image as well:
BOOT IMAGE: https://www.androidfilehost.com/?fid=2981970449027577416
MD5: CFE13188A29FD82AD8134DA706D06730
SHA-1: FC023DEC26372B2F9E8EEF054635561092DCF2EF
INSTRUCTIONS
1. Download the ROM and Recovery image
2. Boot into bootloader/fastboot mode
* adb reboot bootloader
3. Flash the Recovery image
* fastboot flash recovery recovery.img
4. Boot into Recovery
* fastboot reboot-recovery
5. Perform a Factory Reset/Wipe in Recovery
6. Go to Apply Update and choose Apply from ADB
7. Sideload the ROM
* adb sideload rom.zip
Reboot and voila!
Translation
Help with project translation
Stay tuned
Follow us on Telegram​
Contributors @iamsaalim, @kronflux, @billaids
ROM source: https://github.com/PixelExperience
Device sources: https://github.com/kronflux/device_oneplus_billie
Kernel source: https://github.com/danascape/kernel_oneplus_billie
ROM OS Version: 11.x
ROM Kernel: 4.19.125
ROM Firmware Required: OxygenOS 11.x
Based On: AOSP
Version Information
Status: Community Beta
Created 22-01-2022
Last Updated 22-03-2022

Is this an update, and if so do you update through the recovery. Also does updating reset userdata

For some reason adb sideload stops at 47% and I see step 2/2 on my screen. With no indication of it's complete or not. Upon backing out it immediately says complete but doesn't boot, and instead boots into the bootloader

dieudeglace said:
For some reason adb sideload stops at 47% and I see step 2/2 on my screen. With no indication of it's complete or not. Upon backing out it immediately says complete but doesn't boot, and instead boots into the bootloader
Click to expand...
Click to collapse
If it gets to 47% it's finished. (It happens with every recovery and rom for some reason)
It goes right to the bootloader because you have to flash both slots with the rom.
You're halfway there basically.
Use fastboot to switch slots and sideload PE again.
You should be all good to go, just make sure to factory reset after sideloading.

CodeNotSoGenious said:
Is this an update, and if so do you update through the recovery. Also does updating reset userdata
Click to expand...
Click to collapse
It is not an update, you can't go from the previous version of pixel experience to this one.
Unlike the previous version which requires you being on Android 10 before installing pixel experience, you've gotta be on Android 11.
You'd lose user data by having to go back to stock for the Android 11 update (again when unlocking bootloader, and again if you choose to format your device after installing the rom)
It's a bit of time, but the effort is definitely worth it if you have somewhere to store your files momentarily.

ninjasinabag said:
If it gets to 47% it's finished. (It happens with every recovery and rom for some reason)
It goes right to the bootloader because you have to flash both slots with the rom.
You're halfway there basically.
Use fastboot to switch slots and sideload PE again.
You should be all good to go, just make sure to factory reset after sideloading.
Click to expand...
Click to collapse
you are a god send. i thought i was doing something entirely wrong lol

yeah works like a charm now. Deeply appreciate this. Im still new to all this and accidentally bricked my tcl 20 pro 5g a little while ago.

dieudeglace said:
yeah works like a charm now. Deeply appreciate this. Im still new to all this and accidentally bricked my tcl 20 pro 5g a little while ago.
Click to expand...
Click to collapse
Glad to hear you've got it up and running.
Yeah, it's always a coin toss when flashing anymore. Almost always worth it once you get those kinks out.

ninjasinabag said:
It is not an update, you can't go from the previous version of pixel experience to this one.
Unlike the previous version which requires you being on Android 10 before installing pixel experience, you've gotta be on Android 11.
You'd lose user data by having to go back to stock for the Android 11 update (again when unlocking bootloader, and again if you choose to format your device after installing the rom)
It's a bit of time, but the effort is definitely worth it if you have somewhere to store your files momentarily.
Click to expand...
Click to collapse
Thanks, I'll put in some time to flash this!

What's different from the last pixel experience ROM?

CodeNotSoGenious said:
What's different from the last pixel experience ROM?
Click to expand...
Click to collapse
Updated kernel and built officially around Android 11 instead of 10.

ninjasinabag said:
Updated kernel and built officially around Android 11 instead of 10.
Click to expand...
Click to collapse
Appreciate it

Seems I have had one issue so far. Using Android auto and receiving/making calls with people ends up with them not being able to hear me.

dieudeglace said:
Seems I have had one issue so far. Using Android auto and receiving/making calls with people ends up with them not being able to hear me.
Click to expand...
Click to collapse
I'll try and test this myself soon, I haven't been driving much lately so it's a tough thing to test
Make sure you try re-pairing your phone with the vehicle. and by that I mean, entirely delete it from your vehicle as well as delete the pairing in the phone itself. set it up as if it's a new device, and see if that makes a difference

Will try it later to see if it works, otherwise this is a very solid build so thank you for making this!

Now I may habve missed this through the pages but I am getting
"Eackage is for product OnePlusN10 but expected OnePlusNordN10" one device and on laptop cmd it says "failed to read command" is that because I need to flash both slots or is this soem other error?

brncgreen said:
Now I may habve missed this through the pages but I am getting
"Eackage is for product OnePlusN10 but expected OnePlusNordN10" one device and on laptop cmd it says "failed to read command" is that because I need to flash both slots or is this soem other error?
Click to expand...
Click to collapse
Do you happen to be using the metro version of the Nord n10? (Or TMobile since they're basically the same phone.)

ninjasinabag said:
Do you happen to be using the metro version of the Nord n10? (Or TMobile since they're basically the same phone.)
Click to expand...
Click to collapse
I am using t mobile. How ever I did figure it out.... It was ignorant for me to do this but... I didnt realize how PE was suppose to look and when it booted up for the first time I thought it was just stock oneplus OOS.... This time i flashed both a/b and when I booted it was the same thing so I was doing it right all along just failed to realize that it isnt really any different than stock at least from the cosmetic.

Trying to install this but when I get to adb sideload rom.zip (I did rename it after several failed attempts with it's original name). I keep getting
E:\Profile\Desktop>adb sideload rom.zip
loading: 'rom.zip'
* cannot read 'rom.zip' *
Any suggestions?

happened to me. I tried to install over a custom rom that had os11 on it, but it did not like it and kept giving me the same "cannot read" error. I MsM back to stock rom which for me was version 10 at which point I needed to update os to 11 twice to make sure that 11 was on both partitions. After that I unlocked, flashed recovery, reboot recovery, format data, adb sideload rom, then adb sideload partition fix, then reboot to bootloader, fastboot--set-active=a( or b depending on what partition you were on. you want to be on the other partition), boot back into recovery, adb sideload rom again for the different partition, format data again, then reboot. works fine for me.

[ROM][11][AOSP] ArrowOS for OnePlus Nord N10 5G [UNOFFICIAL][BILLIE]

{
"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"
}
ArrowOS​
Code:
/*
* 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.
* It is your fault because you chose to do all the modifications on your device.
* Remember projects like these and the work done on them is a hobby to the
* contributors and the team members, no one is working for you nor is getting paid for it
* have some respect for the work done by them since it is done purely on interest or a hobby
*/
ABOUT
ArrowOS is an Android Open Source Project based Android mobile operating system started with the aim of keeping things simple, clean and neat.
Website: https://arrowos.net
Telegram: Channel
Github: https://github.com/ArrowOS
WHAT WORKS?
Wi-Fi
RIL
Mobile data
GPS
Camera
Flashlight
Bluetooth
Fingerprint reader
Face unlock
NFC
Lights
Sound/vibration
WHAT DOESN'T WORK?
DT2W
You tell me
Be sure to include a log : check how to
DOWNLOADS
ROM [VANILLA]: https://www.androidfilehost.com/?fid=2981970449027577433
MD5: 3BEBDBD50CEF18A0BC7EE4B91FFB4556
SHA-1: 088D01620FAC2198C41BAAB5C4B7373545CE0F1C
ROM [WITH GAPPS]: https://www.androidfilehost.com/?fid=2981970449027577434
MD5: 2CB7B3426A300BB3CC3975936A50B4A3
SHA-1: 8C8DE3CA640C769FEE44A6BA413C28E70DDC430D
*NOTE: ArrowOS Recovery not currently working properly, included PixelExperience recovery in the meantime, which will work fine*
RECOVERY: https://www.androidfilehost.com/?fid=2981970449027577417
MD5: BFE3114F2A966E03CFD0CF6C0040146B
SHA-1: B14B3102C97C15E3C7C045182489514C0827713F
In case you need it for magisk or any other reason, here's the boot image as well:
BOOT IMAGE: https://www.androidfilehost.com/?fid=2981970449027577435
MD5: F1C858AF7E4037098595016570ACF773
SHA-1: 75B9B0337651D09813FBF494715C93AF307953CA
Read our blog article/post about:
* HOW-TO report a bug
* GAPPS and VANILLA variants
Contributors: @iamsaalim, @kronflux
Source Code: https://github.com/ArrowOS
Device Sources: - https://github.com/kronflux/device_oneplus_billie
Kernel Sources: - https://github.com/danascape/kernel_oneplus_sm6350
ROM OS Version: 11.x Android R
Version Information
Status: STABLE
Release Date: 27-01-2022
Last Updated: 21-03-2022
ROM Firmware Required: OxygenOS 11.x
ROM Kernel: 4.19.125

Please provide instructions on how to install it.
Thank you!

I agree with the person above, there should be installation instructions.

Michael0620 said:
I agree with the person above, there should be installation instructions.
Click to expand...
Click to collapse
I agree as well, I wanted to install this on my phone, but I was running into error's.

art2111 said:
Please provide instructions on how to install it.
Thank you!
Click to expand...
Click to collapse
arrow os installation in nord n10 5G with 100% working method

Just wanted to say that I've been having a hell of a time lately getting my N10 5g back up and running properly everything fails in twrp or otherwise. First install attempt with arrow well see for yourself. Works wonderfully so far.

How long should I be watching the boot screen? I have had problems getting almost anything to install on this phone, I though OP was supposed to be more friendly to tinkerers! That being said, Orangefox Recovery installed like a champ, Arrow seemed to flash without any problem, now I'm going on 30min watching the Arrow icon on the boot screen. Am I stuck in a bootloop? There hasn't been any noticeable restarting of the boot screen animation
***Please ignore my question, after watching the install video I realized I was missing a couple crucial steps. Arrow is installed and working perfect!***

Nds99 said:
How long should I be watching the boot screen? I have had problems getting almost anything to install on this phone, I though OP was supposed to be more friendly to tinkerers! That being said, Orangefox Recovery installed like a champ, Arrow seemed to flash without any problem, now I'm going on 30min watching the Arrow icon on the boot screen. Am I stuck in a bootloop? There hasn't been any noticeable restarting of the boot screen animation
***Please ignore my question, after watching the install video I realized I was missing a couple crucial steps. Arrow is installed and working perfect!***
Click to expand...
Click to collapse
hello,can you tell me how stable is this rom?

BloodMist said:
hello,can you tell me how stable is this rom?
Click to expand...
Click to collapse
Only been running for a couple days but I haven't had one single problem out of it.

Honestly, when I get the time I want to install this ROM since I pretty much ripped everything google related out of pixel experience when I realized that I didn't have to.
I might post the step-by-step instructions I followed

Isabelinc said:
Honestly, when I get the time I want to install this ROM since I pretty much ripped everything google related out of pixel experience when I realized that I didn't have to.
I might post the step-by-step instructions I followed
Click to expand...
Click to collapse
Yes please,instructions will be appreciated

BloodMist said:
Yes please,instructions will be appreciated
Click to expand...
Click to collapse
INSTRUCTIONS (leave a like so that more people see this):
So everything is going well but here is how I did it (Note be sure to have a computer with android-tools (for adb and fastboot):
1. make sure your device is unlocked
2. Download your desired version of the rom (Vanilla or GAPPS, I picked Vanilla), the boot image (for rooting with magisk or flashing if you have another rom previously installed), and the recovery image
3. From within your normal rom, make sure adb debugging is enabled then do "adb reboot bootloader"
4. Flash the recovery image with "fastboot flash recovery recovery.img"
5. Perform a system wipe from within the recovery
6. Go to apply update then choose apply from ADB
7. adb sideload rom.zip
8. Voila
With my phone I had to repeat steps 4-7 again in slot a(or b)* and flash the boot image on both slots*
*Enter fastboot mode and enter fastboot --set-active=(a/b)
*fastboot flash boot.img
Side Note: it can be finicky entering fastboot mode so make sure you reboot to a screen that says one plus fastboot mode or something of the sorts

Isabelinc said:
So everything is going well but here is how I did it (Note be sure to have a computer with android-tools (for adb and fastboot):
1. make sure your device is unlocked
2. Download your desired version of the rom (Vanilla or GAPPS, I picked Vanilla), the boot image (for rooting with magisk or flashing if you have another rom previously installed), and the recovery image
3. From within your normal rom, make sure adb debugging is enabled then do "adb reboot bootloader"
4. Flash the recovery image with "fastboot flash recovery recovery.img"
5. Perform a system wipe from within the recovery
6. Go to apply update then choose apply from ADB
7. adb sideload rom.zip
8. Voila
With my phone I had to repeat steps 4-7 again in slot a(or b)* and flash the boot image on both slots*
*Enter fastboot mode and enter fastboot --set-active=(a/b)
*fastboot flash boot.img
Side Note: it can be finicky entering fastboot mode so make sure you reboot to a screen that says one plus fastboot mode or something of the sorts
Click to expand...
Click to collapse
i think i did same,but after flashing recovery and sideloading the rom,i was getting stock rom!
i forgot -set active command and boot image i think lol
thank you!

just installed and works perfectly!
is there any chance i can have stock camera back though?

BloodMist said:
just installed and works perfectly!
is there any chance i can have stock camera back though?
Click to expand...
Click to collapse
Which stock camera app, the one plus camera app or the google one? On the Vanilla version is came with the one plus camera app which I disabled and replaced with SImple Camera.
For the google one, I bet you could find the apk or on the play store/aurora store.
Also I'm glad I was able to help!

Isabelinc said:
Which stock camera app, the one plus camera app or the google one? On the Vanilla version is came with the one plus camera app which I disabled and replaced with SImple Camera.
For the google one, I bet you could find the apk or on the play store/aurora store.
Also I'm glad I was able to help!
Click to expand...
Click to collapse
i mean the Oneplus stock camera one,it would be better with it,any chance i can have it back?
thank you

BloodMist said:
i mean the Oneplus stock camera one,it would be better with it,any chance i can have it back?
thank you
Click to expand...
Click to collapse
Try looking for apk mirrors online of it and see if they work

Isabelinc said:
Try looking for apk mirrors online of it and see if they work
Click to expand...
Click to collapse
no they don't,they crash immediately without warning right when clicked open

BloodMist said:
no they don't,they crash immediately without warning right when clicked open
Click to expand...
Click to collapse
ah rip, well I guess you're going to have to get used to something different

Isabelinc said:
ah rip, well I guess you're going to have to get used to something different
Click to expand...
Click to collapse
there is no way to get stock one back? even with root?