thank you. adding boot image download each week will make using your rom even easier for people.
Yes, working fine.
I've added some Sprint APN patches. Please check current weekly build and let me know.Love your work. Keep it up.
Have a small question. I have my phone stock and updated and activated on sprint with an esim. Everything works perfectly. Data and all. When i try to use your rom using your instructions givin. The phone starts up it says sprint is activated. And phone starts up fine. I can make calls and everything. But for the life of me i cannot get data to work at all. I checked *#*#data#*#* and checked my apn and they are all incorrect but im not having any luck changing them. Is there anyway to maybe completely backup my data or radio or something so i can flash it over the rom? Or is there something i havent heard about that could help me out.
Thanks for any help
Thank you for tryna help me out with all this. appreciate it. ill give it a shot and see what happensI've added some Sprint APN patches. Please check current weekly build and let me know.
Did anyone tell you today that you are the f***ing man? Because if not then I'm letting you know right now. You finally got my dam sprint esim and a custom rom to work. Its seriously been like 3 or 4 months of just all kinds of bs with 0 success. Ur the **** bro. Thank you a **** ton.I've added some Sprint APN patches. Please check current weekly build and let me know.
Hmm so it works, but the notification doesn't wanna go away? I guess you tried the usual steps like reboot / clearing caches? What about disabling the notification (for now..)?Perhaps I spoke to soon. (Not about you being a badass and all lol). My service is active and everything. Calls, data, LTE n all that is fine. Problem is I'm getting a sprintdm configuring your mobile network in my notifications. And I can't get rid of the dam thing.. Hopefully you got a few tricks up ur sleeve to be able to handle this ****. The again.
Exactly. I can't figure out why i cant get rid of it. It just stays there no matter what. Ive tried everything uve said plus tons of other ****. No luck. It wont let u disable the dam thing either.Hmm so it works, but the notification doesn't wanna go away? I guess you tried the usual steps like reboot / clearing caches? What about disabling the notification (for now..)?
Not sure tbh, but might be related to this hacky commit.. Need a Sprint user for testing a few builds to figure out. Send me PM for test build download.
not neccessarily every week. i'm updating whenever i had changes in kernel.quick question...when you release the new weekly update, do you release a new boot image download as well? looking forward to this week's update.
correct. if i don't update kernel boot.img remains the same. btw this week we have major kernel updates - uploading new boot images soon.so if i download a new updated version of the rom, would the boot image download work in order to root, even if the boot image download is from a week or so earlier?
Hey @JasonB96 thx for your report.Hey Siluxsept!
JasonB here from the discord, the guy Ralf talked to you about.
I had previously flashed dotOS and wanted to flash to AICP. I followed the instructions and after factory reset and flashing the ROM I tried to flash Gapps. It said not enough space. Downloaded a different Gapps package, same thing.
So I flashed the ROM again. Tried to flash Gapps. Still no luck. So I booted it up to see if I had flashed it right. Booted into the ROM to see if I flashed it right. It booted. I thought maybe I didn't wipe it right. I looked around and found ``fastboot -w``. Did that flashed Gapps to see if it would and it did. By mistake I did reboot to system, instead of factory reset. I see the dotOS boot animation, then it bootlooped.
Pause the story. I believe fastboot -w broke dotOS causing the bootloader to switch slots.
Resume. Back into recovery. ``fastboot -w`` (probably breaking the install in the inactive slot) flash AICP, flash Gapps, it WORKS!
In conclusion, the installation should probably be.
Boot into recovery.
Factory reset.
Flash AICP.
Reboot to bootloader.
Switch to inactive slot.
Boot recovery.
Flash Gapps.
Boot system.
I believe that AICP flashes to inactive slot, causing this whole saga to unfold.
It may also be some interaction with dotOS.
maybe I'm stupid.
Please correct me, and bring me clarity if I've got this wrong.
Edit: I pulled the boot.img from the payload. Is it different from the one that's in the download link. (Somehow I didn't see this, sorry)
Ah, this is where I messed up. I rebooted to bootloader, and then entered recovery.3. after it finished (do not reboot, do not try to flash anything else) hit back button in recovery go to advanced -> reboot to recovery
thats not going to work since you need to be in same recovery session in order to detect the change and switch slots accordingly. you found a pretty nice workaround thoughAh, this is where I messed up. I rebooted to bootloader, and then entered recovery.
So in short. I did not follow the exact sequence.
Thanks for clearing up my confusion.
Team started 12 sources sync today. Be patient.. ;-)Can we expect builds for Android 12 or we should wait for 12L to be stable?
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* 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. Hard & a lot.
*
*/
Did you dirty flash gapps package also?i dirty flashed the weekly update via ADB sideload and now im stuck in the blue bootanimation any solution?
also found some bugs. 1: The Scramble Layout option makes the screen blackout but the phone is still on and receiving notifications so I had to do a factory reset and everything is back to normal. 2: The device sometimes turns off randomly and remains in bootloop, to solve it you have to press the power button once when the unlocked bootloader splash screen appears. 3: And finally, the battery consumption has gotten slightly worse since I installed the ROM, it's not much but it's noticeable