Develop Bugs

So I decided to try to flash a Generic System Image (GSI)...

aaaaand it booted!
I just flashed Resurrection Remix GSI by phhusson and it works. With EMUI 8 beta you can now flash a treble ROM. Still, this requires further testing so be careful. I'm not responsible for bricked phones. Here are the steps:
1. Make sure your device is on EMUI 8 beta with unlocked bootloader (guide: https://forum.xda-developers.com/honor-6x/development/hwota7-hwota8-honor-6x-t3792601)
2. Download GSI from this thread https://forum.xda-developers.com/pr...opment/resurrection-remix-phh-treble-t3767688 and move it to the folder where you installed ADB
Note: Honor 6x doesn't support seamless update so you want the A-only image, not the A/B one. Just in case you don't know already, Honor 6x has arm64 architecture.
3. Open cmd and navigate to your ADB folder
4. Reboot your phone to fastboot mode and type 'fastboot flash system name-of-the-image.img' where name-of-the-image.img is your downloaded GSI.
5. Hit enter and wait for it to finish installing
6. Famous words: "Reboot and pray"
Problems:
1. Since we don't have a treble-compatable TWRP build yet, there is no way to install gapps for now. I will try to find an image that includes them.
2. All the problems present on the actual ROM (check ROM thread)
3. There are likely others. (There always are some)
I'd like it if others tried to flash this and share their experiences here.
Thanks to @phhusson, @vovan1982, @HassanMirza01, Huawei, RR team and everybody else I forgot to mention.

How's the battery life?

Amirk365 said:
How's the battery life?
Click to expand...
Click to collapse
I'm flashing AOSP right now. It has gapps preloaded so I'll update when I've tested enough.

TheParallelOne said:
I'm flashing AOSP right now. It has gapps preloaded so I'll update when I've tested enough.
Click to expand...
Click to collapse
Thanks,in the mean time I'm looking for a proper cable to root my phone lol

UPDATE:
I flashed AOSP GSI and it boots normally as well. Has gapps and root as well, but you'll need the og supersu (phh's). Chainfire's su doesn't work. Also, you can't give adb root access via dev options so you cant pull boot image to patch it with magisk right away. I'm also unable to get stock camera to work but will experiment with that in the future. Battery life seems a bit better than on nougat roms but then again I'm running pure AOSP with no major battery consumer app on it for now. That's it for now.

@TheParallelOne
Did you try to use stock camera app from there?
https://forum.xda-developers.com/project-treble/trebleenabled-device-development/huawei-stock-camera-app-treble-roms-t3735169
Cool that you already tried to flash a GSI image :good:

TheParallelOne said:
aaaaand it booted!
I just flashed Resurrection Remix GSI by phhusson and it works. With EMUI 8 beta you can now flash a treble ROM. Still, this requires further testing so be careful. I'm not responsible for bricked phones. Here are the steps:
1. Make sure your device is on EMUI 8 beta with unlocked bootloader (guide: https://forum.xda-developers.com/honor-6x/development/hwota7-hwota8-honor-6x-t3792601)
2. Download GSI from this thread https://forum.xda-developers.com/pr...opment/resurrection-remix-phh-treble-t3767688 and move it to the folder where you installed ADB
Note: Honor 6x doesn't support seamless update so you want the A-only image, not the A/B one. Just in case you don't know already, Honor 6x has arm64 architecture.
3. Open cmd and navigate to your ADB folder
4. Reboot your phone to fastboot mode and type 'fastboot flash system name-of-the-image.img' where name-of-the-image.img is your downloaded GSI.
5. Hit enter and wait for it to finish installing
6. Famous words: "Reboot and pray"
Problems:
1. Since we don't have a treble-compatable TWRP build yet, there is no way to install gapps for now. I will try to find an image that includes them.
2. All the problems present on the actual ROM (check ROM thread)
3. There are likely others. (There always are some)
I'd like it if others tried to flash this and share their experiences here.
Thanks to @phhusson, @vovan1982, @HassanMirza01, Huawei, RR team and everybody else I forgot to mention.
Click to expand...
Click to collapse
Bro do complete research first. we have fully working twrp. use twrp on elemental Rom. and installation procedure is also completely wrong. first flash twrp from fastboot using command fastboot flash recovery_ramdisk RECOVERY V2.img then check the recovery and reboot to boot loader then flash system image then reboot to recovery do formats data then install gapps then again reboot to boot loader then flash stockrecovery from dot os thread which is also treble rom then reboot to stock recovery do factory reset now device will boot fine.
Also there are some bugs like mtp,battery drain,heating issues on normal usage and slow charging in some rims. I have tried 4 roms and decided go back to elemental Rom. but these treble roms much better than nougat custom roms comparing to them these can be used as daily driver. pure Android 8.1 roms with all latest features.

Can you provide screenshots please

That's great news. TFS bro.

Edwin Davis said:
Can you provide screenshots please
Click to expand...
Click to collapse
mtp working on some roms and battery drain is not that much compared to emui 8 stock now im gonna try more roms.
Treble roms are much faster and more stable you can't find any bugs. even I was surprised honor 6x can run stock android with this much stability.

Battery drain comparison
on stock emui 5 5% drain for hour while watching movie in mx player no apps running in background all freezed.
on emui 8/treble roms 7-8% while watching movie on mx player but didn't freezed any apps only apps running telegram and whatsapp.
conclusion if u r in emui8 go for treble roms for complete pixel experience

4G VoLTE
it got volte?

What about the volte and gcam ?

Question [Help] With Custom Rom Charge

When i try to charge my phone with custom rom it crashes then reboot Tried it with crDroid and DerpFest, when on miui it works,tried changing kernel to InfiniR Alioth v2.12 but no luck
what can i do ?

Sorry about the thread but searched this everywhere and didn't find anything just a post on Reddit.
On MIUI 12.5
I unlocked bootloader
Fastboot boot twrp-3.6.1_11-0-alioth.img
Wipe data ,internal storage and Cache
Format Data
Reboot recovery
Flashed MIUI firmware V13.0.2.0.SKHMIXM
Flashed crDroid
Reboot to system
No errors but when I connect the USB to fast charge with 33w the phone crash and then reboot.
Normal charge works, only fast charge crash.
Tried with Derpfest got the same error.

Not sure if this is the issue, or even it's required for crDroid to be on latest A12 MIUI13 to flash crD...
but for my rom at least (ancientOS) and possibly others, if not all, is it not recommended or required to be on latest MIUI12.5, then flash crDroid 12/other A12 roms. Could try that - no idea about ARB though going back from MIUI13 to MIUI12.5, you'll have to check
also check with whatever rom thread you choose as to whih is the recommended FW
I might be wrong completely. just offering some thoughts. I'm sure i recall reading somewhere flashing MIUI13 is a no no for flashing custom A12 roms after
bottom line: my advice is use MIUI12.5.6 as a base flash, before A12 custom rom

reg66 said:
bottom line: my advice is use MIUI12.5.6 as a base flash, before A12 custom rom
Click to expand...
Click to collapse
Why not 12.5.8.0 ?

Tomek0000 said:
Why not 12.5.8.0 ?
Click to expand...
Click to collapse
Yeah no doubt that would do the same, if that is indeed the issue

reg66 said:
Yeah no doubt that would do the same, if that is indeed the issue
Click to expand...
Click to collapse
Tried different firmwares same problem,tried 12.5.6 , 13.0,12.0

[FIRMWARE] Flashable firmware / modem / baseband / RIL [OnePlus Nord] [avicii]

Flashable firmware / modem / baseband / RIL only (no full ROM).
Basically, it's a set of firmware/modem/baseband/RIL extracted from the OxygenOS Full ROM update payload and packed into a custom recovery flashable ZIP. Useful for users of a custom ROM, since the firmware/modem/baseband/RIL is never updated on most custom ROMs and thus becomes outdated. Those who use OxygenOS don't need this, since the firmware/modem/baseband/RIL is also updated with OTAs.
Important
If you have a OnePlus Nord (avicii) AC01AA, AC01BA or AC01DA and a custom ROM installed, feel free to proceed. However, I recommend making a backup before and get the unbrick tool from here, just in case.
Flash it with any (custom) recovery. It's not necessary to delete, wipe or format anything before or after installation.
Note: Packages are not signed.
Check the baseband version with: Settings → About phone → Android version → Baseband version
For OnePlus Nord - avicii - Android 12 based ROMs:
VersionModelDownload link11 F.20 AC01AAGlobalOnePlus_Nord_11-F-20-AC01AA_global_firmware.zip11 F.20 AC01BAEuropeOnePlus_Nord_11-F-20-AC01BA_europe_firmware.zip11 F.20 AC01DAIndiaOnePlus_Nord_11-F-20-AC01DA_india_firmware.zip
Baseband version after update: Q_V1_P14 or: MPSS.HI.2.5-01081-SAIPAN_GEN_PACK-1.7761.62_VENDOR
For OnePlus Nord - avicii - Android 10 and 11 based ROMs:
VersionModelDownload link11.1.10.10 AC01AAGlobalOnePlus_Nord_11-1-10-10-AC01AA_global_firmware.zip11.1.11.11 AC01BAEuropeOnePlus_Nord_11-1-11-11-AC01BA_europe_firmware.zip11.1.10.10 AC01DAIndiaOnePlus_Nord_11-1-10-10-AC01DA_india_firmware.zip
Baseband version after update: MPSS.HI.2.0.c9-00023-SAIPAN_GEN_PACK-1.422164.2.446371.2
Last Updated: 2023-06-04

Reserved 1

Reserved 2

Reserved 3

Great work! Thanks for the contribution.

can u plz update latest beta 2 recovery & boot img, got stuck on latest oos12 beta when tried to flash custom recovery as no custom recovery for oos12 beta right now, thanks in advance

Thank you for your work!
I guess this maybe does not work with the LineageOS recovery? I tried to sideload using apply from ADB in the LineageOS recovery, but I keep getting the following error
"E3004: This package is for "OnePlus Nord" devices; this is a "".

hermesjconrad said:
Thank you for your work!
I guess this maybe does not work with the LineageOS recovery? I tried to sideload using apply from ADB in the LineageOS recovery, but I keep getting the following error
"E3004: This package is for "OnePlus Nord" devices; this is a "".
Click to expand...
Click to collapse
I have included a safeguard so that these files cannot be accidentally installed on a device other than the Nord. But for some reason the LOS developers decided to name the device differently in LOS 17 recovery. In LOS 18 (or alternatively Orange Fox) recovery everything should work fine.
So I have removed this protection for now until an official LOS 18 or 19 is released. Download the appropriate package again and try to flash it again, it should now be able to be flashed with adb sideload.

Worked like a charm with the removed control, thank you very much Doc Sniper!
Straying slighty off-topic, would OrangeFox be the recovery that you'd recommend instead of LOS 17.1 default? Or rather TWRP?

vikd007 said:
can u plz update latest beta 2 recovery & boot img, got stuck on latest oos12 beta when tried to flash custom recovery as no custom recovery for oos12 beta right now, thanks in advance
Click to expand...
Click to collapse
Sorry, but I don't quite understand the problem? These packages update the firmware if you have a custom ROM installed. But since the OxygenOS Open Betas are official packages, they include the firmware anyway and these packages here are kind of useless for you.
But even if the packages were of use to you, neither the boot nor the recovery image is included.
I can offer to extract the two images so you can install them with fastboot flash, please send me the download link to the corresponding ROM and I'll see what I can do.

hermesjconrad said:
Worked like a charm with the removed control, thank you very much Doc Sniper!
Straying slighty off-topic, would OrangeFox be the recovery that you'd recommend instead of LOS 17.1 default? Or rather TWRP?
Click to expand...
Click to collapse
LOS recovery is totally OK if you only want to perform updates. But if you want to make backups and restore or want to get to the data partition, then it is no longer sufficient. Unfortunately there is still no official TWRP, so I use Orange Fox and it works great with the unofficial LOS 18, but you have to look in the Orange Fox thread there is a link to a newer version than the one in the opening post (see post 81 on page 5).

sniperle said:
Sorry, but I don't quite understand the problem? These packages update the firmware if you have a custom ROM installed. But since the OxygenOS Open Betas are official packages, they include the firmware anyway and these packages here are kind of useless for you.
But even if the packages were of use to you, neither the boot nor the recovery image is included.
I can offer to extract the two images so you can install them with fastboot flash, please send me the download link to the corresponding ROM and I'll see what I can do.
Click to expand...
Click to collapse
thanks for prompt revert bro, i was on stock latest beta was trying to flash custom recovery but no custom recovery support oos 12 beta for so stuck on bootloop so asked for help if i can get latest boot and recovery img, but somehow a trick worked and finally on custom rom... thanks bro and appreciate ur work

vikd007 said:
thanks for prompt revert bro, i was on stock latest beta was trying to flash custom recovery but no custom recovery support oos 12 beta for so stuck on bootloop so asked for help if i can get latest boot and recovery img, but somehow a trick worked and finally on custom rom... thanks bro and appreciate ur work
Click to expand...
Click to collapse
Good to hear your phone is working again.
If you ever have a bootloop again because your recovery doesn't start, you can also start a recovery from the computer via fastboot.
In short: Download the recovery image to your computer. Then connect the phone with a usb-cable. Then start the phone in fastboot mode. Then upload and start the recovery from the computer with "fastboot boot name_of_recovery_image.img".

Doc Sniper said:
Good to hear your phone is working again.
If you ever have a bootloop again because your recovery doesn't start, you can also start a recovery from the computer via fastboot.
In short: Download the recovery image to your computer. Then connect the phone with a usb-cable. Then start the phone in fastboot mode. Then upload and start the recovery from the computer with "fastboot boot name_of_recovery_image.img".
Click to expand...
Click to collapse
problem was there is no recovery for oos beta 12 as of now and no latest boot image

Managed to bork my phone by trying to upgrade magisk, managed to unbork by changing boot slots with fastboot, really neat.
Wanted to say thank you for providing the latest update file. Didn't need it in particular, but cool to have it and know it is available!

vikd007 said:
thanks for prompt revert bro, i was on stock latest beta was trying to flash custom recovery but no custom recovery support oos 12 beta for so stuck on bootloop so asked for help if i can get latest boot and recovery img, but somehow a trick worked and finally on custom rom... thanks bro and appreciate ur work
Click to expand...
Click to collapse
I faced the same issue.. want to move on to a custom ROM but have 2 questions:
1. Does the phone loose Widevine L1 upon bootloader unlock on OOS12? I know i have to stop the phone from booting up after bootloader unlock and directly install the custom ROM, but i got stuck due to the recovery problem.
2. Does the custom ROM work good after this?

Hi,
Thank you for your work.
Unfortunately, update with LOS recovery doesn't work (LOS 19.1 recovery).
It says "Signature verification failed, error 21".
I have Magisk installed if it means anything in this case.

blorkraider said:
Unfortunately, update with LOS recovery doesn't work (LOS 19.1 recovery).
It says "Signature verification failed, error 21".
Click to expand...
Click to collapse
The ZIP files are not signed hence the message. But as far as I know, LOS-Recovery can also flash unsigned ZIPs. When the message appears, you can switch to yes with the volume buttons and then confirm with the power button. Then the ZIP should be installed.

Now that OOS12 is available for all regions can you post the modem files from those? It seems 12 unlocks 5G in some countries.

mythos_ said:
Now that OOS12 is available for all regions can you post the modem files from those? It seems 12 unlocks 5G in some countries.
Click to expand...
Click to collapse
According to the official Oneplus site, version 11 is still the current release version. Can you send me a download link to the release version of OOS 12? Thanks.

Question Copy partition after msm?

Hi guys,
So I can't for the life of me get a rom installed. Drivers are fine, fastboot commands always ends up booting into the recovery, but it won't read or flash the rom. I've tried crdroid, pixel, nameless. For the hell of it tried lineage over pixel recovery and that installed?!
I've been seeing the odd post/comment about how msm restore only pertains to one boot and you should update twice so both boots are covered? I also see a copy partion zip floating around but is this a12 or a13 or work on both?
For what it's worth I've been able to root it successfully. Any thoughts or advice would be appreciated.
Edit: I'm. Coming from a msm restore
Thanks

chinbags said:
Hi guys,
So I can't for the life of me get a rom installed. Drivers are fine, fastboot commands always ends up booting into the recovery, but it won't read or flash the rom. I've tried crdroid, pixel, nameless. For the hell of it tried lineage over pixel recovery and that installed?!
I've been seeing the odd post/comment about how msm restore only pertains to one boot and you should update twice so both boots are covered? I also see a copy partion zip floating around but is this a12 or a13 or work on both?
For what it's worth I've been able to root it successfully. Any thoughts or advice would be appreciated.
Edit: I'm. Coming from a msm restore
Thanks
Click to expand...
Click to collapse
when I restore my device I tipically run copy partition just after I unlock bootllader
then you know every flash should boot, even flashing twice (on A and B partition) it shod be always safer, since starting condition is the same

Psk.It said:
when I restore my device I tipically run copy partition just after I unlock bootllader
then you know every flash should boot, even flashing twice (on A and B partition) it shod be always safer, since starting condition is the same
Click to expand...
Click to collapse
Do you run it once or do you run copy partition after each update?

Had trouble at first too. But the copy partitions file is just so that the same firmware is on both slots. If you follow this post for nameless, you shouldn't have any problems. Should be noted that you should be on the latest (c.63-66) and be using the latest dtbo.img, vendor_boot.img, and boot.img files from the links posted in that thread)
[ROM][OOS CAM][OFFICIAL][OnePlus 9 Pro][13.0.0_r41]Nameless AOSP[2023/05/09]
Nameless AOSP for OnePlus 9 Pro [lemonadep] Nameless AOSP is based on Android Open Source Project, inspired by Google Pixel. We offer a smooth and stable experience for your device with a selected set of amazing features that provide an...
forum.xda-developers.com

chinbags said:
Do you run it once or do you run copy partition after each update?
Click to expand...
Click to collapse
just the first time unlocking

Question How to install Ricedroid 10.2 that doesn't come with boot file ?

riceDroid - Browse /lisa at SourceForge.net
sourceforge.net
I noticed that there's no boot file and just vendor boot
So can I install this rom with Lineage recovery after flashing vendor boot ?
Or is boot file not necessary

open the zip and look
EDIT:
Ok not so simple, the payload.bin rom include firmware i upload the boot.img vendor_boot.img and dtbo.img
yes lineage recovery work.
google for extract payload.bin if you want it do by yourself.

Trismo said:
open the zip and look
EDIT:
Ok not so simple, the payload.bin rom include firmware i upload the boot.img vendor_boot.img and dtbo.img
yes lineage recovery work.
google for extract payload.bin if you want it do by yourself.
Click to expand...
Click to collapse
I have lineage os installed rn
So can I go into recovery and just sideload the rom then format and reboot (to replace my current rom)
instead of flashing the 3 files?
Or should I flash the 3 files in adb then sideload rom in recovery

Yes If the recovery is not newer than Droid recovery.
If you get problems flash with fastboot the 3 files and reboot recovery

I used AOSPA boot.img, it worked correctly, but I already say that Rice 10.2 has a crash problem in SystemUI, it happens every half hour on average, it's not just in 11 NE, in my F3 it's happening the same.

Trismo said:
Yes If the recovery is not newer than Droid recovery.
If you get problems flash with fastboot the 3 files and reboot recovery
Click to expand...
Click to collapse
This is unrelated to the title
but does the adb cmd method to flash fastboot stock miui rom work on this phone without errors?

I already use they Xiaomi adb and fastboot tools to flash original miui stock roms, You can try it with that, If it doesn't work for you that way, you can do it using fastboot (press the power button and volume down).If you want to install "Ricedroid, you already have the process: use a custom recovery, it can be PixelOs Recovery or Pixel Experience recovery, both are very complete.

Morretz said:
I used AOSPA boot.img, it worked correctly, but I already say that Rice 10.2 has a crash problem in SystemUI, it happens every half hour on average, it's not just in 11 NE, in my F3 it's happening the same.
Click to expand...
Click to collapse
Personally, I do not recommend version 10.2 of RICEDROID, since I found several errors in the launcher, as my colleague said, as well as errors in the display in the case of video games, since it only detects a finger.

Pepenamer01 said:
Personally, I do not recommend version 10.2 of RICEDROID, since I found several errors in the launcher, as my colleague said, as well as errors in the display in the case of video games, since it only detects a finger.
Click to expand...
Click to collapse
I ended up leaving Rice 10 on my two devices, performance was very bad, heating up, high consumption, and an annoying bug of crashing QS making the screen turn off, I ended up going back to MIUI since I didn't find any stable custom rom without high consumption

From my point of view it seems great that you return to miui, although you may also want to try PixelOs, LineageOs or CherishOs, which in my opinion are custom roms that are not so well known, but they have an amazing quality in all aspects, now I am using PixelOs on my Mi 11 Lite 5g NE (Lisa)