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

[Isabelinc]

there is no way to get stock one back? even with root?

You're going to have to look into it on your own, I'm afraid :\

 

[OdinVex]

@kronflux, Visual Voicemail doesn't appear to be working on my billie8t. The Dialer just shows “Visual Voicemail isn't working, Call voicemail to finish setting it up”. I've done that, made no difference, toggling the feature on/off doesn't enable it either, but I'm on Mint Wireless (an MVNO, which uses TMO, T-Mobile). Maybe something needs tinkering just for TMO-users. Just reporting it in, I'm going to try to grab the TMO apks and figure out what they've done to the standard way of Visual Voicemail grabbing what it needs. VoLTE appears to work (icon can be enabled and looks alive, but Network Cell Info says it's a dud). An extra step was needed to flash to my billie8t (may work on billie8 as well). Flashing the boot image to boot_a and boot_b.

Edit: VoLTE may or may not be working, connection is somewhat buggy on T-Mobile (sometimes calls won't go through until I reboot or airplane-mode it), usually indicative that T-Mobile's crap backend wants those stupid APKs.

 

[jmfixitman]

Man, how do I erase this ROM??? I've tried installing the GAPPS version over the Vanilla, and no go, it says unable to downgrade. Then I tried to format and install TWRP to do a wipe, and the touch controls dont work. I've tried sideloading GAPps and it says no room in partition, try a smaller file. Im using the smallest one!

 

[OdinVex]

Man, how do I erase this ROM??? I've tried installing the GAPPS version over the Vanilla, and no go, it says unable to downgrade. Then I tried to format and install TWRP to do a wipe, and the touch controls dont work. I've tried sideloading GAPps and it says no room in partition, try a smaller file. Im using the smallest one!

You're kinda doing everything wrong, based on what you've mentioned. Since you've probably f***ed it all up at this point, restore with Qualcomm EDL (restores back to stock, remember to keep your unlock_token binary if you ever wish to unlock again!!!). Don't flash from TWRP, TWRP isn't ready for these devices. If you bothered to follow directions you'd know that you can only use Pixel Recovery to format and sideload, remember to do both a and b name-schemes. As for GApps, I used MagiskGApps converted just for testing (careful with this method, never disable the module, or you'll bootloop).

 

[jmfixitman]

Thanks and sorry I miss spoke. I tried to install the Gapps version of arrow on top of the vanilla... It didn't work and that's when I got the cannot downgrade. I tried to install the pixel recovery through the arrow recovery and that didn't work either. I'll try your other suggestions, and yes still have the token. Where would I find the magiskGapps, or will that not work now either?

 

[OdinVex]

Thanks and sorry I miss spoke. I tried to install the Gapps version of arrow on top of the vanilla... It didn't work and that's when I got the cannot downgrade. I tried to install the pixel recovery through the arrow recovery and that didn't work either. I'll try your other suggestions, and yes still have the token. Where would I find the magiskGapps, or will that not work now either?

You should always format before a sideload. EDL flash restore (entire phone, remember, you lose unlock status, you will need to reflash unlock token, but fortunately no need to get a new bin file). Flash pixel recovery to both recovery_a and recovery_b, boot into recovery_a, stay in recovery and: format, sideload, run adb in the recovery menu and then use set-active for b, reboot directly into recovery (it should take you to b), format, sideload, then reboot. The whole 'a/b' active slot for boot is a lot like dual-boot for Windows/Linux. They're unique on their own. For example, you could have Android 10 and Android 11 on the same phone, if you wanted. A simple set-active would select which set of partitions to use. By the way...FLASH YOUR BOOT PARTITION(s) with the boots that come with the ROM. Otherwise you'll most likely get looped to recovery. I had to do that for my billie8t. You can pre-magisk the boot(s) img files before flashing if you want.

 

[jmfixitman]

So I'm making some headway after running format through adb on both positions. However even after installing pixiel recovery, after a reboot it reverse to the arrow recovery, and then add before I can't sideload anything? Can you explain the EDL flash process? I'm used to the old rooting using twrp, etc...

 

[OdinVex]

You are not flashing both recoveries then. You need to re-read the directions...stop using TWRP, it is NOT ready for these devices. You will not be using TWRP for *anything* with these devices, yet. EDL flashes the entire storage, all partitions. When you flash recovery, you need to flash recovery_a and recovery_b. Just doing recovery will flash whichever is ACTIVE, such as A or B. Re-read the directions, don't skip anything.

 

[jmfixitman]

Alright, I have a lot figured out now, formatted partitions and installed pixel recovery in both. Got the fresh rom installed and so far so good! The only issue now is that I've lost super user access, and I can't sideload Magisk to use that for some reason?? Is there another super user apk that works with this recovery, etc? Thanks again for your help!

 

[OdinVex]

Alright, I have a lot figured out now, formatted partitions and installed pixel recovery in both. Got the fresh rom installed and so far so good! The only issue now is that I've lost super user access, and I can't sideload Magisk to use that for some reason?? Is there another super user apk that works with this recovery, etc? Thanks again for your help!

Why are you attempting to Sideload Magisk? Who said to do that? Install the Magisk APK, copy your BOOT img over, patch it, then flash the resulting BOOT image over boot_a and boot_b...

 

[jmfixitman]

Well I was on the Magisk download site, and while I can install the apk, I still don't have root access. On their site it says to load the magisk.zip using twrp, and since twrp doesn't work on this phone/recovery I tried sideload... I'll try the patching route

 

[OdinVex]

Well I was on the Magisk download site, and while I can install the apk, I still don't have root access. On their site it says to load the magisk.zip using twrp, and since twrp doesn't work on this phone/recovery I tried sideload... I'll try the patching route

You don't need root to patch a BOOT img. Install the APK, run Magisk and simply patch your BOOT img, then use fastboot and flash the boot_a and boot_b partitions with that patched BOOT.img. Ignore anything to do with TWRP, that should have been very obvious at this point.

 

[jmfixitman]

Lol, yes I got the don't use twrp innuendo... I did patch the pixiel recovery image in Magisk, and flashed in partitions a and b, but no luck with getting root. I even started over by doing a format on both partitions and reloading the patched boot image and ROM, still no go. I'll keep messing with it.

 

[OdinVex]

Lol, yes I got the don't use twrp innuendo... I did patch the pixiel recovery image in Magisk, and flashed in partitions a and b, but no luck with getting root. I even started over by doing a format on both partitions and reloading the patched boot image and ROM, still no go. I'll keep messing with it.

...You're kidding right? Who said patch the recovery image? It always has root.. Several posts saying BOOT... FFS. Letting anyone else deal with this person. Five times I said BOOT...

 

[jmfixitman]

No need to be a ****, not everyone is as experienced as you... Other threads said the recovery so I tried that. I'll move on to the boot, which I hadn't downloaded, and thank you for your snarky assistance.

 

[OdinVex]

No need to be a ****, not everyone is as experienced as you... Other threads said the recovery so I tried that. I'll move on to the boot, which I hadn't downloaded, and thank you for your snarky assistance.

Not being a ****, you aren't reading. Piss on someone else with your reverse-blame.

 

[Heykel89]

Hi guru's,

I have just installed the vanilla arrows OS rom on my N10 (BE2029) because stock room was a nightmare (interface issues, impossible to answer calls, minutes of freezing and all that stuff).

Just flashed it yesterday, so far so good, except for one point, quite huge one.

The WiFi range is really poor, I mean I have to be in the same room as my box or I lose the signal.
When I'm connected the speed is as good as with the stock rom.
That's why I think the modem is the culprit here.

Did you ever face this misbehaviour ? Any solution without flashing modem ? And if not, how can I know the modem to pick ?

Thanks for reading !

Heykel.

 

[OdinVex]

Hi guru's,

I have just installed the vanilla arrows OS rom on my N10 (BE2029) because stock room was a nightmare (interface issues, impossible to answer calls, minutes of freezing and all that stuff).

Just flashed it yesterday, so far so good, except for one point, quite huge one.

The WiFi range is really poor, I mean I have to be in the same room as my box or I lose the signal.
When I'm connected the speed is as good as with the stock rom.
That's why I think the modem is the culprit here.

Did you ever face this misbehaviour ? Any solution without flashing modem ? And if not, how can I know the modem to pick ?

Thanks for reading !

Heykel.

The baseband/modem is rarely ever connected to wlan firmware at all (separate chipsets, usually, separate firmware files as well). That being said, maybe they used a different chipset for yours and something isn't by default connecting at a higher standard. Confirmed you're operating at the same 802.11 standard as router? Double-check your case...seen a lot of garbage cases wreck signal. I'd bet it is a conf issue, not firmware. Identify your wlan chipset and see if it is the same as the assumed chipset(s) of Arrow. This is also a ROM for the 5G models, there were baseband differences, though I don't know if it was chipset or firmware. I have noticed some Android devices having wireless issues (cell or wlan) if they replaced/changed versions of firmwares or ROMs, sometimes crappy router firmwares assume profiles of devices and any changes goof something up, notably on NetGear firmwares. Tried restarting router, just to be sure?

 

[Heykel89]

The baseband/modem is rarely ever connected to wlan firmware at all (separate chipsets, usually, separate firmware files as well). That being said, maybe they used a different chipset for yours and something isn't by default connecting at a higher standard. Confirmed you're operating at the same 802.11 standard as router? Double-check your case...seen a lot of garbage cases wreck signal. I'd bet it is a conf issue, not firmware. Identify your wlan chipset and see if it is the same as the assumed chipset(s) of Arrow. This is also a ROM for the 5G models, there were baseband differences, though I don't know if it was chipset or firmware. I have noticed some Android devices having wireless issues (cell or wlan) if they replaced/changed versions of firmwares or ROMs, sometimes crappy router firmwares assume profiles of devices and any changes goof something up, notably on NetGear firmwares. Tried restarting router, just to be sure?

Hi Odin,

Thank you for the answer, and sorry for the late reply, was pretty busy those days.
Well, regarding my SIP box, it's a pretty good one, so nothing wrong with my router, I'm affraid.
Plus, all my devices are working pretty well, girlfriend Xiaomi, Firestick, etc...
It really happened consecutively to my ROM flash.

I will dig here and there to see if I can update my modem only on this Oneplus crap (when I was on CM years ago, on Samsung devices, I remember I've tested many modem to get the one, but I don't know if nowadays it is still possible to do it, especially with Arrow...)

Heykel.

 

[OdinVex]

Hi Odin,

Thank you for the answer, and sorry for the late reply, was pretty busy those days.
Well, regarding my SIP box, it's a pretty good one, so nothing wrong with my router, I'm affraid.
Plus, all my devices are working pretty well, girlfriend Xiaomi, Firestick, etc...
It really happened consecutively to my ROM flash.

I will dig here and there to see if I can update my modem only on this Oneplus crap (when I was on CM years ago, on Samsung devices, I remember I've tested many modem to get the one, but I don't know if nowadays it is still possible to do it, especially with Arrow...)

Heykel.

We don't have to play modem-flashing games anymore. As for why you might be having issues, it could be due to an APK missing. For instance, I'm on Mint Mobile, an VMNO, which uses T-Mobile's network. If I don't have T-Mobile APKs installed that customize the Wi-Fi Calling and VoLTE activation...then I can't use those features and *must* disable them to use regular “5G” (5G protocol over low-frequency 600MHz, aka fake 5G just like AT&T and such)/LTE. Video call would also bust. All would either not work at all or they would start but then stop. That's due to T-Mobile's custom backend bull**** because they wrote it themselves instead of licensing properly-confirming backends.