Develop Bugs

[Q] Help, won't boot any custom roms.

After trying to flash a new rom after being on AOKP M1 for a little while (http://forum.xda-developers.com/showthread.php?t=1875923) the phone got stuck at the Black and white Samsung Galaxy SIII screen and didn't boot upon hitting reboot system now on cwm. Tried again, tried reflashing and the whole 9 yards wouldn't boot at all. So I turned to odin and went to the prerooted latest JB build (http://forum.xda-developers.com/showthread.php?t=1949687) and then reflashed touch cwm and tried to reflash the rom. Same problem. So, I odin'd back to the non rooted UVDLJA. Rerooted and reflashed cwm and blahblahblah. I said hmm maybe it's the rom, I then tried to flash this rom (http://forum.xda-developers.com/showthread.php?t=1993934) and when I tried to reboot system now after the process; again the phone got stuck at the black and white Samsung Galaxy SIII screen and did not boot. The phone works fine when I odin it to stock builds but refuses to boot custom roms. Can someone help me here? I haven't been able to find a solution for days. :crying:
PS I'm a noob, don't kill me lol
edit: forgot to include I have the Tmobile variant

Did you wipe data and cache when you flashed the new rom?

nyyankees1237 said:
After trying to flash a new rom after being on AOKP M1 for a little while (http://forum.xda-developers.com/showthread.php?t=1875923) the phone got stuck at the Black and white Samsung Galaxy SIII screen and didn't boot upon hitting reboot system now on cwm. Tried again, tried reflashing and the whole 9 yards wouldn't boot at all. So I turned to odin and went to the prerooted latest JB build (http://forum.xda-developers.com/showthread.php?t=1949687) and then reflashed touch cwm and tried to reflash the rom. Same problem. So, I odin'd back to the non rooted UVDLJA. Rerooted and reflashed cwm and blahblahblah. I said hmm maybe it's the rom, I then tried to flash this rom (http://forum.xda-developers.com/showthread.php?t=1993934) and when I tried to reboot system now after the process; again the phone got stuck at the black and white Samsung Galaxy SIII screen and did not boot. The phone works fine when I odin it to stock builds but refuses to boot custom roms. Can someone help me here? I haven't been able to find a solution for days. :crying:
PS I'm a noob, don't kill me lol
edit: forgot to include I have the Tmobile variant
Click to expand...
Click to collapse
a few questions:
and i can verify the issue is something on your end, because the ROM you tried was mine, and nobody has had that issue (not booting it)
do this...
1. make sure you have the latest version of clockwordmod, don't use twrp
2. re-download my ROM (just for sake of not adding any other variables to your issue, because mine should boot)
3. put ROM on external SD card
before continuing... take a quick look at my thread here in QA titled "flashing ROMs correctly every time" .... so you can get some instruction on verifying MD5 of the download... don't worry, the thread will explain that you...
now proceed
4. boot to recovery
5. do a factory reset - 3 times do this, just to be thorough. people will say you don't need to, but like i said, just for the sake of removing variables
6. go to mounts and storage, format system 3 times - (yes, through recovery as well)
7. flash ROM, and reboot
EDIT*** i will say this, ALWAYS format system when flashing a new ROM

cobraboy85 said:
a few questions:
and i can verify the issue is something on your end, because the ROM you tried was mine, and nobody has had that issue (not booting it)
do this...
1. make sure you have the latest version of clockwordmod, don't use twrp
2. re-download my ROM (just for sake of not adding any other variables to your issue, because mine should boot)
3. put ROM on external SD card
before continuing... take a quick look at my thread here in QA titled "flashing ROMs correctly every time" .... so you can get some instruction on verifying MD5 of the download... don't worry, the thread will explain that you...
now proceed
4. boot to recovery
5. do a factory reset - 3 times do this, just to be thorough. people will say you don't need to, but like i said, just for the sake of removing variables
6. go to mounts and storage, format system 3 times - (yes, through recovery as well)
7. flash ROM, and reboot
EDIT*** i will say this, ALWAYS format system when flashing a new ROM
Click to expand...
Click to collapse
thanks for the info, will try this all out soon. I've been flashing roms for years now and have never run into anything like this, and as previously stated, this didn't occur solely with your rom which has me thinking something has happened to the phone itself. will get back to you soon and once again thank you

chucktdriscoll said:
Did you wipe data and cache when you flashed the new rom?
Click to expand...
Click to collapse
of course, wiped data, cache, & delvik

nyyankees1237 said:
of course, wiped data, cache, & delvik
Click to expand...
Click to collapse
my point is...
coming from a cm based ROM, or aokp, whatever you said... you would want to format system as well.

nyyankees1237 said:
After trying to flash a new rom after being on AOKP M1 for a little while (http://forum.xda-developers.com/showthread.php?t=1875923) the phone got stuck at the Black and white Samsung Galaxy SIII screen and didn't boot upon hitting reboot system now on cwm. Tried again, tried reflashing and the whole 9 yards wouldn't boot at all. So I turned to odin and went to the prerooted latest JB build (http://forum.xda-developers.com/showthread.php?t=1949687) and then reflashed touch cwm and tried to reflash the rom. Same problem. So, I odin'd back to the non rooted UVDLJA. Rerooted and reflashed cwm and blahblahblah. I said hmm maybe it's the rom, I then tried to flash this rom (http://forum.xda-developers.com/showthread.php?t=1993934) and when I tried to reboot system now after the process; again the phone got stuck at the black and white Samsung Galaxy SIII screen and did not boot. The phone works fine when I odin it to stock builds but refuses to boot custom roms. Can someone help me here? I haven't been able to find a solution for days. :crying:
PS I'm a noob, don't kill me lol
edit: forgot to include I have the Tmobile variant
Click to expand...
Click to collapse
I was having some of the same issues. I downloaded XquiziT's Superwipe and ran it by installing from external sd card. I ran it three times to clear everything out, then I wiped data, cache and the rest three times.
No probs for me after that.

Will definitely give that a try as well! Thank you! Will post my results when the holiday is over.
Happy thanksgiving
Sent from my SGH-T999 using xda app-developers app

[Q] MIUI for V One Help! (What in hells name am I doing wrong?!)

Hey there;
Firstly, thanks for your great efforts on the ports of your roms and consistent, useful forum help.
I appreciate that you probably get a load of these threads but I could really use some help with the installation of the ROM, as I've had a load of problems trying to install it.
I am attempting to install the MIUI rom (http://forum.xda-developers.com/showthread.php?t=1797515), and I am coming from the original software that comes with the device.
I have an unrooted One V, coming from the base OS and kernel. Currently, I can't get past the Jellybean Android screen (getting stuck on starting apps), and usually I can't even get past the MIUI screen at all. Here are the steps I've taken;
- I downloaded this kernel: boot-TK-USB-201302150054 from this thread: http://forum.xda-developers.com/show....php?t=1765687 and flashed it in fastboot, twice.
- Then launch into recovery, follow the instructions on your thread (format all apart from SD), and go ahead and install the .zip.
- Clear Delvik, clear Battery and Fix permissions, then proceed to reboot in an attempt to get in. At this point it hangs on MIUI screen for up to 5 minutes.
- I then try re-flashing the kernel in fastboot again. Still no help.
- I then try and reinstall the .zip from the SD card, and still no improvement.
I imagine I'm doing something very wrong, but I can't work out what it is and it's driving me crazy.
Can you help?!
Thanks in advance, Reasoner.

you are installing an older rom version which has no support..and is old

paarthdesai said:
you are installing an older rom version which has no support..and is old
Click to expand...
Click to collapse
Any chance you good point me in the right direction for an newer version?
Also, am I doing all the steps right?

paarthdesai said:
you are installing an older rom version which has no support..and is old
Click to expand...
Click to collapse
Okay, I have now attempted to install YOUR version of MIUI, and I'm still not having any luck.
I have;
- Flashed the boot.img using the one you suggest on your thread (twice)
- Booted into Recovery, cleared all caches excluding SD
- installed from .zip in CWM Recovery
- Cleared Delvik
On reboot I still get stuck on the MIUI screen.

Reasoner said:
Okay, I have now attempted to install YOUR version of MIUI, and I'm still not having any luck.
I have;
- Flashed the boot.img using the one you suggest on your thread (twice)
- Booted into Recovery, cleared all caches excluding SD
- installed from .zip in CWM Recovery
- Cleared Delvik
On reboot I still get stuck on the MIUI screen.
Click to expand...
Click to collapse
Ignore this, tried again and got through! Thanks a bunch!

AOSP, RR Resurrection Remix, ArrowOS and others

I just wanted to point out that I have been able to boot some treble GSI on my device from different roms like AOSP, RR, ArrowOS in the treble section of XDA and some of them boot fine, but I have found some issues:
PHH PIE GSI doesn't like magisk it breaks wifi and mobile data once magisk is flashed
PHH Oreo AOSP GSI I do not remember any issues besides being too stock for my liking
RR GSI It has so many options almost comparable to what a Venom Rom would be for HTC devices
TWRP it is not able to read encryption on any of this GSIs
AOSP Oreo I don't remember if the other variants GSIs does not read exFAT formatted MicroSD (works on PIE GSI)
https://forum.xda-developers.com/project-treble/trebleenabled-device-development
I would like more users to share their experience here with GSIs
the steps I took to flash this
1. make sure you download an arm64 AB GSI image from your favorite ROM
2. go to TWRP wipe section wipe system, Dalvik cache data & internal
3. go to TWRP wipe section format data, type yes
5. restore stock Vendor.img and stock Boot.img
6. flash GSI
7. reboot & enjoy
first boot might take awhile it encrypts the device, thi is the part that makes TWRP not being able to decrypt data since TWRP decrypts Qualcomm Encryption on our device but no stock android encryption this part it is possible to fix by TWRP team and it will probably come in later

Thanks for sharing. I was planning on trying out a GSI this weekend and see how it goes. Glad it works!

I forgot to save the stock vendor and stock boot file I need these two files Can you help

emrince said:
I forgot to save the stock vendor and stock boot file I need these two files Can you help
Click to expand...
Click to collapse
https://forum.xda-developers.com/u12-plus/how-to/collection-htcu-u12-ruu-firmware-t3794664/page24
Read the OP there

I tried to boot the RR img, no dice.
Backed up modified rom on slot b
Switched to slot a in TWRP, supposedly empty
Wiped system, data, cache, dalvik
Flashed prior stock vendor img and boot img
Flashed RR ab arm64 su gapps Img
Rebooted slot a
Bootloop
Interestingly, after looking 3 times, my phone booted back to slot b by itself back to stock, back up restored just fine
I realize I didn't wipe factory reset with yes

Finally got RR to to boot! It's a very finicky process. I think my problem was I kept trying to "dual" boot, Viper in one slot and the GSI in the other. Turns out it just has to be in the active slot, regardless of which slot you switch to in TWRP. Maybe that's obvious for some. This a/b partition business sure has a learning curve.
Anyway, things I noticed on RR: Lots of customization as usual for RR, very fast and smooth, screen brightness is on max all the time regardless of slider or auto brightness, and I couldn't make phone calls but texting worked. Everything else seemed to work fairly well. I love the fling navbar....on to the next one.

I'm not sure if anyone else is trying the GSI's, this doesn't seem to be a very active thread. So far I have only been able to boot RR 8.1 GSI. I have tried multiple other images without any success. I think the reason I didn't get data and calls didn't work on RR is that I am on Verizon and the HTC u12 does not have CDMA radios. Volte calling was not available on the rom. Oh well. I'm excited for the upcoming developments in the Viper forum. If anyone knows a fix for data on verizon with the GSI's, I'm all ears. Thanks

Anybody successful in making one of this ROMs a daily driver?
Sent from my HTC U12+ using XDA Labs

Resurrection Remix 8.1 is pretty stable if you are on a gsm network. I popped in a Tmobile sim card and it was pretty solid. There are some minor annoyances like the inability to adjust the brightness (always on full), though decreasing screen pixels makes it more dim, vendor mismatch message on boot, and no volte or wifi calling. There may be some other small things like with the camera and bluetooth but I didn't keep it for long as I am on Verizon and don't get data. I could see using it as a DD though. There are probably ways to fix the annoyances I mentioned.

Have any of you tested this version of RR on U12+?
https://forum.xda-developers.com/pr...0-resurrection-remix-v7-0-arm64-32-b-t3891636
For example, face recognition, 4k camera mode, slow motion recording, 3D sound, AudioFocus, bokeh mode etc.?
regards
q

@JEANRIVERA Is i't there any working Android P GSI rom?
Just can't wait anymore HTC for P update =)

nomaj said:
@JEANRIVERA Is i't there any working Android P GSI rom?
Just can't wait anymore HTC for P update =)
Click to expand...
Click to collapse
Original PHH, ArrowOS & DescendantOS all work fine, the only problem is no Magisk support yet

JEANRIVERA said:
Original PHH, ArrowOS & DescendantOS all work fine, the only problem is no Magisk support yet
Click to expand...
Click to collapse
So.. i will missing root? and fixes for google sotre etc ?

JEANRIVERA said:
Original PHH, ArrowOS & DescendantOS all work fine, the only problem is no Magisk support yet
Click to expand...
Click to collapse
I have problem with install ArrowsOS, i have still bootlops.. It's probably related to a / b boot, how to fix this? Twrp say "No OS installed", i set wipe system,data,cache next i flash vendor, boot and system file, i made a mistake?

JEANRIVERA said:
Original PHH, ArrowOS & DescendantOS all work fine, the only problem is no Magisk support yet
Click to expand...
Click to collapse
@JEANRIVERA
Is't this update helpping us?
2019.3.28 Magisk v19.0
https://forum.xda-developers.com/showpost.php?p=79216305&postcount=50https://forum.xda-developers.com/showpost.php?p=79216305&postcount=50

mientus25 said:
I have problem with install ArrowsOS, i have still bootlops.. It's probably related to a / b boot, how to fix this? Twrp say "No OS installed", i set wipe system,data,cache next i flash vendor, boot and system file, i made a mistake?
Click to expand...
Click to collapse
Hey, I'm having the same problem. Did you work out a solution to get any GSI to boot on your U12?

SilentAchiever said:
Hey, I'm having the same problem. Did you work out a solution to get any GSI to boot on your U12?
Click to expand...
Click to collapse
I tried to find a solution for 12 hours and nothing came of it

I's dual sim working on GSI roms?
---------- Post added at 10:38 AM ---------- Previous post was at 10:36 AM ----------
mientus25 said:
I tried to find a solution for 12 hours and nothing came of it
Click to expand...
Click to collapse
1. make sure you download an arm64 AB GSI image from your favorite ROM
2. go to TWRP wipe section wipe system, Dalvik cache data & internal
3. go to TWRP wipe section format data, type yes
5. restore stock Vendor.img and stock Boot.img
6. flash GSI
Did you flashed GSI rom from point 6?

Yes, i follow this instruction and twrp say "OS no installed".

mientus25 said:
Yes, i follow this instruction and twrp say "OS no installed".
Click to expand...
Click to collapse
Check this... wiping
"for GSI it is better to wipe from stock recovery "

How to flash system_ext?

Hey guys and gals!
So I don't wanna keep posting on other ROM threads to be annoying, so I will create a thread of my own. How do one flash the system_ext.img coming from Stock (root) ? I absolutely cannot get any TWRP versions (Chinese or English) to function. I take my passcode off and it's always 0mb. Doesn't matter if I am on a custom ROM or not. It's just something I cannot get to work. ONE time, it seen my storage but it would not flash a ROM. SO how can I flash this image via fastboot?
Global version of OOS. Although, I am currently on EXTENDED. I said Stock because I'll always have a Crash Dump, and need to start over. It's also tiresome to flash YAAP (12-18-20) then use the updater to create the image. Again, some things with this device, I'm getting used to. I'm all for learning and testing everything. I just cannot find a way to flash this image or get TWRP to function.
Have a great day!

So I would suggest you update your fastboot tools, because once you have the partition created assuming you are coming from a rom that has the system ext img it shouldn't be a problem. For example this is what I did, I was on RR remix so twrp chinese was working ( by the way I don't know why it wouldn't work for you if it works for everyone else) from there its just a matter of flashing the zip that contains the img. You can try derp,evox, yaap etc. After that again just flash what ever rom you desire it shouldn't be any issues. Also to keep in mind that a11 with twrp does not work with a pin only with a pattern, even tho I have read you said you have no pin lock. Wouldn't really know why your device would be the case but you can try that out .

lil_kujo said:
So I would suggest you update your fastboot tools, because once you have the partition created assuming you are coming from a rom that has the system ext img it shouldn't be a problem. For example this is what I did, I was on RR remix so twrp chinese was working ( by the way I don't know why it wouldn't work for you if it works for everyone else) from there its just a matter of flashing the zip that contains the img. You can try derp,evox, yaap etc. After that again just flash what ever rom you desire it shouldn't be any issues. Also to keep in mind that a11 with twrp does not work with a pin only with a pattern, even tho I have read you said you have no pin lock. Wouldn't really know why your device would be the case but you can try that out .
Click to expand...
Click to collapse
Sorry for the delay. Wish XDA would alert me, better. So Chinese TWRP is working now, on XTEND. I dunno, sometimes it works and sometimes I get 0mb. I think that point, to go onto a ROM WITH that image, should be fine. Since I always had troubles, I'd only fastboot flash to different ROMs. Trust me, for all my time on Android, this device is making me needy and a big newb. I just waiting for that "then don't bother to flash anything and shut up" LOL! BUT then again, I'm not on r/jailbreak. So once the partition is created, I can go to a ROM without that image? Do you know how I can check? Because I would like to just flash Hydrogen but don't wanna jump to stock. I think I can just flash a ROM with it and reboot back to the bootloader without setting up, right?

draymond1987 said:
Sorry for the delay. Wish XDA would alert me, better. So Chinese TWRP is working now, on XTEND. I dunno, sometimes it works and sometimes I get 0mb. I think that point, to go onto a ROM WITH that image, should be fine. Since I always had troubles, I'd only fastboot flash to different ROMs. Trust me, for all my time on Android, this device is making me needy and a big newb. I just waiting for that "then don't bother to flash anything and shut up" LOL! BUT then again, I'm not on r/jailbreak. So once the partition is created, I can go to a ROM without that image? Do you know how I can check? Because I would like to just flash Hydrogen but don't wanna jump to stock. I think I can just flash a ROM with it and reboot back to the bootloader without setting up, right?
Click to expand...
Click to collapse
That img will always exist is part of android 11 so it will be the norm. Every rom in the future will have it as seen on some custom roms right now, I flashed the h2os from twrp since I was coming from derp. So I didnt go back to stock. When you flash that img a partition will be created so the space will be available for when you flash another rom. So in the case that for example you were on derp and decided to fastboot flash h2os 11 you will not have issues flashing with fastboot commands the system_ext to both slots. ( By the way you need to specify which slot so I recommend you have a custom rom prior on both slots better if it's a11 rom.) The command fastboot flash system_ext_a system_ext.img and system_ext_b system_ext.img is to be used when doing it with fastboot command from fastbootd. If you decide to go with twrp from any custom rom a11 like the ones mentioned before just flash and right after you flash format data. You will lose twrp since the zip has the new recovery from oneplus. Reboot to recovery and again format data reboot enjoy. If you want to use just regular fastboot method you have to flash every img in the zip like 23 or so don't rememeber in order for it to work. So to make it simple for you. Flash a custom a11 rom with twrp if you are on a custom rom already. To both slots. After reboot and have the rom settle by letting it start to home screen. Save the zip of h2os to the phone reboot to recovery flash h2os zip not don't reboot but in twrp go to wipe format data. Then reboot to recovery again it will reboot to stock recovery format data again reboot and enjoy.
You will still have a custom rom in the other slot and if you want to have the stock on both slots just use the ota system update form stock rom local upgrade
There you go it should be simple and quick it took me like ten minutes to set it up and flash yesterday. By the way despite being a beta I really enjoy h2os 11. Do expect some minor bugs since it's a beta build.

I'll leave a link so you can read about system_ext and android new partition going forward. https://source.android.com/devices/bootloader/partitions

lil_kujo said:
I'll leave a link so you can read about system_ext and android new partition going forward. https://source.android.com/devices/bootloader/partitions
Click to expand...
Click to collapse
You're a wealth of information! Thanks for helping me to understand!
Edit: I tried the installing of two ROMs but I couldn't get it. I tried XTEND and Derp. But I had trouble with Xtend not being able to boot after setting up Derp. I had to wipe data for it to boot. Then lost everything. Bleh.

Can I ask you for your recommendation for an A11 ROM to have on a slot?

draymond1987 said:
You're a wealth of information! Thanks for helping me to understand!
Edit: I tried the installing of two ROMs but I couldn't get it. I tried XTEND and Derp. But I had trouble with Xtend not being able to boot after setting up Derp. I had to wipe data for it to boot. Then lost everything. Bleh.
Click to expand...
Click to collapse
So just to give you some more context, when you have to different rom on each slot is normal you have to format data, one : because they might have different data format , example oneplus only supports ext4 while derp is f2fs. So when flashing derp and the other slot is xtended is expected you will have to format in some occasions it might boot but you will have a buggy experience. So now that you have two custom roms and twrp try flashing h2os and again always format data and format data again in stock recovery since that will change the data format to ext4.

draymond1987 said:
Can I ask you for your recommendation for an A11 ROM to have on a slot?
Click to expand...
Click to collapse
Derp works perfect, that is the one I was coming from.

lil_kujo said:
So just to give you some more context, when you have to different rom on each slot is normal you have to format data, one : because they might have different data format , example oneplus only supports ext4 while derp is f2fs. So when flashing derp and the other slot is xtended is expected you will have to format in some occasions it might boot but you will have a buggy experience. So now that you have to custom roms and twrp try flashing h2os and again always format data and format data again in stock recovery since that will change the data format to ext4.
Click to expand...
Click to collapse
So I can have derp AND Hydro running? But like, when I format data, it was a full data wipe. I guess what you're talking about, right? Like I said, both ROMs kinda worked but it force a "fastboot -w". Maybe since I can get TWRP to work, I can wipe data there, and not touch user data?

draymond1987 said:
So I can have derp AND Hydro running? But like, when I format data, it was a full data wipe. I guess what you're talking about, right? Like I said, both ROMs kinda worked but it force a "fastboot -w". Maybe since I can get TWRP to work, I can wipe data there, and not touch user data?
Click to expand...
Click to collapse
On 7t there is no such thing as dual boot you can have of course one rom in one slot and another different slot on the other slot and it would work, also when you fastboot -w you are not erasing the imgs, you are erasing user data. The imgs from the rom will always be there until you change them. There is no way of saving data because of what i mentioned before of the different dat file ext4 and f2fs, when you are on stock it will "make data work for it but not for other roms" because of the decryption issue for one and second because of the format ext4. The only two roms i have tried so far that you can have dual boot are EVO x and Derp because there code is so similar coming from the same dev. SO to answer your question, Yes you can have two different ROMS but the rom that you use for setup that will be the one that will take over, in this case stock will take over data, which means you wont be able to use the other slot till you format data again and get rid of the encryption so that the other rom can use data partition. I know it sounds complicated but it really is very simple.

It is rather simple. I did notice a few people using those ROMs in slots. I mean, it's not a big deal if I can have two ROMs. I do miss the days of dual booting though.
May I ask, and this isn't to make a ROM work with Stock on a slot. Can you convert the file system to F2FS? I stumbled across a ROM that said it was better on this device but I can't find that post.

draymond1987 said:
It is rather simple. I did notice a few people using those ROMs in slots. I mean, it's not a big deal if I can have two ROMs. I do miss the days of dual booting though.
May I ask, and this isn't to make a ROM work with Stock on a slot. Can you convert the file system to F2FS? I stumbled across a ROM that said it was better on this device but I can't find that post.
Click to expand...
Click to collapse
yes you can, it depends, if the rom supports it. the fastboot way is way to complicated so twrp is the best option, when you choose wipe you will see a setting that says advanced, from there you choose data and click the option change format or repair then you will see some options. do note that when you change the type it will erase your data. do note that only data will change your system data will still be ext4.

lil_kujo said:
yes you can, it depends, if the rom supports it. the fastboot way is way to complicated so twrp is the best option, when you choose wipe you will see a setting that says advanced, from there you choose data and click the option change format or repair then you will see some options. do note that when you change the type it will erase your data. do note that only data will change your system data will still be ext4.
Click to expand...
Click to collapse
Ahh okay, I think I understand a little better now. Thanks for everything so far!

Palladium OS Unofficial Oneplus 5 and 5T (Vanilla and GAPPS)

include <std_disclaimer.h>
/*
* Your warranty is... still valid/probably? ( Subject to OEM's)
*
*We are not responsible for bricked devices, dead SD cards
* unpleasant experiences. Custom ROM's are Custom for a reason and
* as developers, we try our best to give you the most complete experience
* When you choose our ROM, its a choice which you make but it doesnt make us
* liable to any unfortunate events. But we will be happy to help for the greater good.
/
Palladium OS is not yet another ubiquitous os but a trendsetter of its own level. The Prime focus here
are on speed, stability and above all, its a community driven os where everyone can experience their ideas
without any limitations. All these is complemented by the Meteor Fall programme which are a series of OTA updates
which adds in new features and suggestions. So, now you know why its christened The Palladium OS.
Source
Palladium: PalladiumOS
Install Instructions
Backup your personal data (Important)
- Download the ROM and GApps and transfer them to your device.
- Boot to recovery (TWRP recommended).
- Wipe the System, Cache, Data and ART/Dalvik cache.
- Flash the ROM
- Flash Gapps Zip file (Only for Vanilla variant)
- Reboot your device.
Downloads
ROM: sourceforge
GApps: NikGapps
Credits
- Google for AOSP
- LineageOS
- Project Fluid
- ShapeShift OS
- Pixel experience
- Project Streak
- Dot OS
- Octavi OS
- Bliss ROM
- AICP & POSP & Pixys Team for thread template idea
- Also many pro devlopers who all help us to bring this rom to you..
- Please let us know if we forgot to mention your name in credits..
AND TO THE PALLADIUM TEAM FOR THIS ROM​
Build Author/Maintainer - Arokz Dpk
Device Name - Oneplus 5 and 5T
Device Codename -dumpling and cheeseburger
Kernel Source - https://github.com/ArokzDP/kernel_oneplus_msm8998
ROM Status - Unofficial
Android Version - 11.0
ROM Version - v1.3

thanksssssss

Wow! Thank you, is it my birthday? I will flash over the next couple of days. Thank you once again.

I have just tried to flash the gapps version. I flashed with Majisk and got stuck in a bootloop for 25 minutes. Went back into recovery, went through the wipe process again and re-flashed Palladium. I got the 'successful' flash message in Twrp, but when I went to reboot it said that there was no OS installed. I was able to flash the ROM that I was on previously (Pixel) without any problems. Maybe I had a corrupted download, sadly I don't have the time to try again right now, I will try again in a few days.

Drhedphuk said:
I have just tried to flash the gapps version. I flashed with Majisk and got stuck in a bootloop for 25 minutes. Went back into recovery, went through the wipe process again and re-flashed Palladium. I got the 'successful' flash message in Twrp, but when I went to reboot it said that there was no OS installed. I was able to flash the ROM that I was on previously (Pixel) without any problems. Maybe I had a corrupted download, sadly I don't have the time to try again right now, I will try again in a few days.
Click to expand...
Click to collapse
Am on the same gapps version and it booted jus fine for me. If the zip is corrupted u wont be getting successful flash message. Maybe try again afterwards when free. Also happy that u tried it.

Arokia said:
Am on the same gapps version and it booted jus fine for me. If the zip is corrupted u wont be getting successful flash message. Maybe try again afterwards when free. Also happy that u tried it.
Click to expand...
Click to collapse
I also guess the boot loop could be due to encrypted or decrypted thing. Try with f2fs instead...

Arokia said:
I also guess the boot loop could be due to encrypted or decrypted thing. Try with f2fs instead...
Click to expand...
Click to collapse
Okay, thank you for the advice. I will let you know.

Added to the OnePlus 5 Index Thread here.

Drhedphuk said:
I have just tried to flash the gapps version. I flashed with Majisk and got stuck in a bootloop for 25 minutes. Went back into recovery, went through the wipe process again and re-flashed Palladium. I got the 'successful' flash message in Twrp, but when I went to reboot it said that there was no OS installed. I was able to flash the ROM that I was on previously (Pixel) without any problems. Maybe I had a corrupted download, sadly I don't have the time to try again right now, I will try again in a few days.
Click to expand...
Click to collapse
Happened to me as well but i got it fixed by flashing the vanilla rom first and then let it boot, after that i rebooted back to the recovery and flashed gapps. Worked just fine. Hope this will help anyone having a similar issue

Any way to get rid of the home buttons and have a home bar instead ? Couldn't find any option like Derpfest has. Props for the great rom, I'm loving it and the battery life is just incredible.

Jalef said:
Happened to me as well but i got it fixed by flashing the vanilla rom first and then let it boot, after that i rebooted back to the recovery and flashed gapps. Worked just fine. Hope this will help anyone having a similar issue
Click to expand...
Click to collapse
Thank you very much. Which gapps package did you flash?

No good for me. Whatever I try. It says that I have successfully flashed, yet when I go to reboot it says that there is no OS installed, both versions.

Drhedphuk said:
No good for me. Whatever I try. It says that I have successfully flashed, yet when I go to reboot it says that there is no OS installed, both versions.
Click to expand...
Click to collapse
Make sure you have the zip files anywhere in your internal storage. But not inside a folder within the internal storage. Because whenever you wipe data,system,cache and dalvik it will also wipe the downloaded files inside the download folder.

Jalef said:
Make sure you have the zip files anywhere in your internal storage. But not inside a folder within the internal storage. Because whenever you wipe data,system,cache and dalvik it will also wipe the downloaded files inside the download folder.
Click to expand...
Click to collapse
I kept them in the same place that I kept Pixel ROM and was able to flash that afterwards. Plus the APK's that I had within that folder and the Majisk zip were fine too. Weird issue.

Drhedphuk said:
I kept them in the same place that I kept Pixel ROM and was able to flash that afterwards. Plus the APK's that I had within that folder and the Majisk zip were fine too. Weird issue.
Click to expand...
Click to collapse
That's actually weird because when i flashed on my end everything got deleted from there

Drhedphuk said:
No good for me. Whatever I try. It says that I have successfully flashed, yet when I go to reboot it says that there is no OS installed, both versions.
Click to expand...
Click to collapse
Maybe you should try a different recovery?! I use Orange Fox and had no problems with flashing this Rom. Installed the Vanilla version plus Nik Gapps full package.

KeinePanik said:
Maybe you should try a different recovery?! I use Orange Fox and had no problems with flashing this Rom. Installed the Vanilla version plus Nik Gapps full package
Click to expand...
Click to collapse
KeinePanik said:
Maybe you should try a different recovery?! I use Orange Fox and had no problems with flashing this Rom. Installed the Vanilla version plus Nik Gapps full package.
Click to expand...
Click to collapse
I was wondering whether my codeworx Twrp was maybe outdated. Can I flash Orange fox over the top of codeworx with a zip file?
Edit: Flashed Orange Fox, I'll try again.

Yesss!! Flashed it! It was obviously the recovery version that I was running. On the suggestion of @KeinePanik I flashed Orange Fox recovery and voila! (Thank you my friend)
My apologies to the developer and everyone else for flooding this thread with my issues.
I have been running the app for about 5 hours now and can report that it is really smooth, great battery life and some nice UI extras. Many thanks to the dev, will it go official?

Current release has june sec. patch or shall I wait for the upcoming update if it around the corner ???

m.omdaa said:
Current release has june sec. patch or shall I wait for the upcoming update if it around the corner ???
Click to expand...
Click to collapse
Security patch is May 5.