*ABANDONED* [ROM][OOS10][11.0][Beta] DerpFest Nord N10 [UNOFFICIAL]

[stoag]

Each time I turn on this ROM the "extreme battery saver" app crashes and it's giving me atrocious battery performance. Either that or the new battery I bought is junk.

Can you fix the battery saver crash?
Is there any info I can provide to help troubleshoot?

Going to try a different ROM to make sure it's not the battery.

 

[ninjasinabag]

How is it possible to have AOD with IPS LCD?

It composites the whole screen instead of the individual pixels required.
Proximity handles waking, and a low power state keeps your phone from going full throttle upon being woken.

 

[ninjasinabag]

Any chance someone has a boot.img for this? I can't personally extract and want to use magisk.

 

[ShadowDrift]

HI, so far I have no issues with this rom and im happy with it. However, I am curious, is the camera resolution using this rom only able to go as high as 16.1MP (4624x3472) when I take regular pictures with the camera app? Is this normal or did I mess up the installation somehow? I still get 1920x1080 resolution when i shoot video though. Any help would be grateful. Thank You.

 

[ninjasinabag]

HI, so far I have no issues with this rom and im happy with it. However, I am curious, is the camera resolution using this rom only able to go as high as 16.1MP (4624x3472) when I take regular pictures with the camera app? Is this normal or did I mess up the installation somehow? I still get 1920x1080 resolution when i shoot video though. Any help would be grateful. Thank You.

Download a different camera. The stock camera with the rom is limited. I'm using Open camera from the play store since it supports switching camera modules.

 

[ShadowDrift]

Download a different camera. The stock camera with the rom is limited. I'm using Open camera from the play store since it supports switching camera modules.

Thank you, you just saved me from having to try another rom and reinstalling and setting up everything again. So far I'm happy with the app. Thank you.

 

[Eliliyah]

I've tried every conceivable way to get this loaded. No matter what I try, it goes to crash dump mode. The only way out is through QDL mode. I tried starting off with several variants of 10. I've tried swapping the slots, multiple recoveries, sideload, flashing from recovery, unlocking critical. It's telling me secure boot is on even after disable verity. Is that a factor? Any suggestions?

 

[boffster99]

I've tried every conceivable way to get this loaded. No matter what I try, it goes to crash dump mode. The only way out is through QDL mode. I tried starting off with several variants of 10. I've tried swapping the slots, multiple recoveries, sideload, flashing from recovery, unlocking critical. It's telling me secure boot is on even after disable verity. Is that a factor? Any suggestions?

I've experienced with my phone which is a model BE2026 that there is A/B partition issues when trying to sideload the rom. I've had to adb sideload immediately after sideloading the rom a copy partition zip which copies the sideloaded rom to the other partition and then reboot after that. works for me. I don't think it works if your coming from OS 11 version but need to have version 10 on your phone prior to installing custom rom. any way. good luck. here is the copy partition zip https://www.androidfilehost.com/?fid=2188818919693768129

 

[stoag]

if you flashed the rom while on A then switch to B

I tried that, after sideload I went back to fastboot mode through recovery and --set-active=b. Still boots into crash dump mode.

Trying bofffster's copy partition zip.

Funny thing is. I had this rom on here before and thought possibly the battery just needed calibration and now I'm kicking myself trying to get it working before. Last time it was so easy.

 

[Eliliyah]

I tried everything with the partitions. I installed on A and switched to B. I installed on B and switched to A. I installed on both. Still no luck.

 

[stoag]

I tried that, after sideload I went back to fastboot mode through recovery and --set-active=b. Still boots into crash dump mode.

Trying bofffster's copy partition zip.

Funny thing is. I had this rom on here before and thought possibly the battery just needed calibration and now I'm kicking myself trying to get it working before. Last time it was so easy.

Well... I got farther than before. Now it's stuck on the loading owl. Been there for half an hour so far...

 

[Eliliyah]

Well... I got farther than before. Now it's stuck on the loading owl. Been there for half an hour so far...

Format data

 

[stoag]

Rebooted into recovery and did a factory reset (format data) and.. that worked. TYVM!

 

[Eliliyah]

Rebooted into recovery and did a factory reset (format data) and.. that worked. TYVM!

Awesome. So you started from 10, sideloaded to whichever slot, flashed the script to the same partition, format data and it worked?

 

[ninjasinabag]

Rebooted into recovery and did a factory reset (format data) and.. that worked. TYVM!

Awesome. So you started from 10, sideloaded to whichever slot, flashed the script to the same partition, format data and it worked?

Only use this rom if you're coming from android 10.

Reboot to recovery, format your device.
Sideload the rom onto your current slot.
Sideload the partition fix.

Reboot into bootloader.
Switch slots using fastboot --set-active=a or fastboot --set-active=b.
Reboot back to recovery.
Sideload your rom onto the slot you switched to.
Factory reset again.

Reboot.

 

[stoag]

Awesome. So you started from 10, sideloaded to whichever slot, flashed the script to the same partition, format data and it worked?

That's correct. When I tried to flash a patched boot image for magisk (perhaps I had the wrong file, yesterday was a long day.) I bricked it again so I've listed the steps in detail.

Started from MSM flashing android 10, because I bricked my device like 12 times, lol.
Went from there to OS to unlock the bootloader.(If your device was previously unlocked, then make sure you setup using mobile data or the option may be greyed out.)

after initial android setup having selected mobile data instead of wifi, skipping google account setup, and entering a pin... basically and as soon as it would allow me to, i swipe down from top and use the gear icon to enter settings.

settings->about phone
accessed developer options by tapping build number 7 times
went back to settings->system->developer options
toggled oem unlocking
enter pin
toggled usb debugging
hit always allow checkbox and ok on popup for authorization
adb reboot fastboot in my terminal
had to go to English Advanced then Reboot to fastboot on my phone using vol down and power
fastboot flash cust-unlock unlock_code.bin <~from the same directory where I stored the unlock code i got from OnePlus. (I contacted the FCC to get my metro phone network-unlocked, then contacted OP for the code.)
fastboot oem unlocking
hit volume down twice and power to unlock bootloader
it reboots itself to the OS after wiping everything...
back to step 1 so...

>after initial android setup having selected mobile data instead of wifi, skipping google account setup, and >entering a pin... basically and as soon as it would allow me to, i swipe down from top and use the gear icon to >enter settings.

>settings->about phone
>accessed developer options by tapping build number 7 times
>went back to settings->system->developer options
(oem unlocking should be greyed out because the bootloader is already unlocked)
>toggled usb debugging
> hit always allow checkbox and ok on popup for authorization
>adb reboot fastboot in my terminal
>had to go to English Advanced then Reboot to fastboot on my phone using vol down and power
then in my terminal
fastboot flash recovery DerpFest-11-Recovery-billie-20211023.img
fastboot reboot recovery
go to 'apply update'->'apply from adb' on my phone then back to terminal
adb sideload Derpfest-11-Community-billie-2021023.zip
wait like 10 minuites... it takes a good long while.
my terminal never goes past 47% for some reason and I always get 'adb: failed to read command: Success' when its finished
on my phone i used vol up and power to go back to the initial recovery screen
again went to apply update->apply from adb then back to terminal
adb sideload copy-partitions-20210323_1922.zip
hit vol down and power to select yes when it says signature verification failed
when it finishes and says OK i hit vol up to go back
then down to Factory Reset->Factory Reset->Format Data/Factory Reset
then reboot and

voila derpfest!

 

[stoag]

Just fyi, magisk works fine with the boot.img extracted from payload.bin in the derpfest zip. I must've flashed the wrong one this morning.

 

[boffster99]

yeah I went ahead and tried flashing this rom. used the partition zip after the derpfest zip then factory reset data and reboot. works pretty good so far. I like the owl animation in the beginning.

 

[Eliliyah]

That's correct. When I tried to flash a patched boot image for magisk (perhaps I had the wrong file, yesterday was a long day.) I bricked it again so I've listed the steps in detail.

Started from MSM flashing android 10, because I bricked my device like 12 times, lol.
Went from there to OS to unlock the bootloader.(If your device was previously unlocked, then make sure you setup using mobile data or the option may be greyed out.)

after initial android setup having selected mobile data instead of wifi, skipping google account setup, and entering a pin... basically and as soon as it would allow me to, i swipe down from top and use the gear icon to enter settings.

settings->about phone
accessed developer options by tapping build number 7 times
went back to settings->system->developer options
toggled oem unlocking
enter pin
toggled usb debugging
hit always allow checkbox and ok on popup for authorization
adb reboot fastboot in my terminal
had to go to English Advanced then Reboot to fastboot on my phone using vol down and power
fastboot flash cust-unlock unlock_code.bin <~from the same directory where I stored the unlock code i got from OnePlus. (I contacted the FCC to get my metro phone network-unlocked, then contacted OP for the code.)
fastboot oem unlocking
hit volume down twice and power to unlock bootloader
it reboots itself to the OS after wiping everything...
back to step 1 so...

>after initial android setup having selected mobile data instead of wifi, skipping google account setup, and >entering a pin... basically and as soon as it would allow me to, i swipe down from top and use the gear icon to >enter settings.

>settings->about phone
>accessed developer options by tapping build number 7 times
>went back to settings->system->developer options
(oem unlocking should be greyed out because the bootloader is already unlocked)
>toggled usb debugging
> hit always allow checkbox and ok on popup for authorization
>adb reboot fastboot in my terminal
>had to go to English Advanced then Reboot to fastboot on my phone using vol down and power
then in my terminal
fastboot flash recovery DerpFest-11-Recovery-billie-20211023.img
fastboot reboot recovery
go to 'apply update'->'apply from adb' on my phone then back to terminal
adb sideload Derpfest-11-Community-billie-2021023.zip
wait like 10 minuites... it takes a good long while.
my terminal never goes past 47% for some reason and I always get 'adb: failed to read command: Success' when its finished
on my phone i used vol up and power to go back to the initial recovery screen
again went to apply update->apply from adb then back to terminal
adb sideload copy-partitions-20210323_1922.zip
hit vol down and power to select yes when it says signature verification failed
when it finishes and says OK i hit vol up to go back
then down to Factory Reset->Factory Reset->Format Data/Factory Reset
then reboot and

voila derpfest!

Got it. Finally lol Thanks!

OP - Can we get the shell script added to the rom? Thanks for your hard work!

 

[78t140@broadstripe.net]

i still have this version not derfest r installed been working great over a year now but first time tryed using hotspot and it just cuts out comes back with error anyone know of a fix ??