[ROM/MAGISK]Bad Boyz US Unlocked HTC 10 ROM | N | 2.41.617.3 | v3.2 | updated 2.1.17

chas123 · Dec 17, 2016

Alarand said:
Thanks Downloading now :good:

---------- Post added at 03:48 PM ---------- Previous post was at 03:26 PM ----------

Can't seem to find the "Run_to_build_ROM.bat" from svn. Assuming I can just zip it?

Yes. Hold ctrl Then select data, Meta-inf, System, superuser, and boot.img. Once selected right click, move down to 7zip, and click add to archive. If you don't have 7zip select send to> compressed folder

Edit: ROM builder files committed to the svn

chas123 · Dec 17, 2016

ordeniz said:
Can I flash this over my stock 2.28.401.9?

You can try. It 'probably' won't hurt anything, but a clean flash would be best for performance.

Alarand · Dec 17, 2016

chas123 said:
Yes. Hold ctrl Then select data, Meta-inf, System, superuser, and boot.img. Once selected right click, move down to 7zip, and click add to archive. If you don't have 7zip select send to> compressed folder

So zips don't have to be signed for twrp right? Is that even a thing anymore, if it ever was? Anyways thanks again.

chas123 · Dec 17, 2016

Alarand said:
So zips don't have to be signed for twrp right? Is that even a thing anymore, if it ever was? Anyways thanks again.

No. Sig verification is off in TWRP by default. Unless you check it before flashing you will be fine. You can still sign ROMS w/ the kitchen. I don't

Alarand · Dec 18, 2016

Something peculiar is breaking wifi-calling. Don't think it's specific to the rom, and I can only imagine it's some weird sim config problem. I wish my troubleshooting skills were better lol. On US unlocked using tmo.

benny3 · Dec 18, 2016

Alarand said:
Something peculiar is breaking wifi-calling. Don't think it's specific to the rom, and I can only imagine it's some weird sim config problem. I wish my troubleshooting skills were better lol. On US unlocked using tmo.

Im on TMO and i can't even use the rom yet. For some odd reason my phone is only picking up att network. I don't believe it has anything to do with the rom.

gmoe65 · Dec 18, 2016

benny3 said:
Im on TMO and i can't even use the rom yet. For some odd reason my phone is only picking up att network. I don't believe it has anything to do with the rom.

I ran this Rom for a lil bit last night with the old FW and I'm with T-Mobile it booted up just fine and no problem with Wi-Fi on my end

Captain_Throwback · Dec 18, 2016

Alarand said:
Something peculiar is breaking wifi-calling. Don't think it's specific to the rom, and I can only imagine it's some weird sim config problem. I wish my troubleshooting skills were better lol. On US unlocked using tmo.

Wi-Fi Calling seems to be broken on all the ROMs. It didn't work for me either.

chas123 · Dec 19, 2016

If someone wants to post a log taken while the phone is trying to connect to wifi calling I'll look at it.

munkyvirus · Dec 19, 2016

I pulled this last week on ICE rom, but while it was still based on 2.28.617.8. Turned WiFi calling and VoLTE off then on then pulled log so if an error is happening, it should be in there.

Alarand · Dec 20, 2016

My twrp restore to stock didn't fix the WFC thing. Works again after RUU though. Only thing I noticed was a restart prompt on first boot after ruu saying sim settings have been updated.

The one gimmicky feature I'm somewhat reliant on always breaks on updates ;p

rwc95 · Dec 20, 2016

Alarand said:
My twrp restore to stock didn't fix the WFC thing. Works again after RUU though. Only thing I noticed was a restart prompt on first boot after ruu saying sim settings have been updated.

The one gimmicky feature I'm somewhat reliant on always breaks on updates ;p

When you have it working with stock make your backup with system image, data, boot. And it will work when you restore. If you use system, data, boot it will still be broken on a restore. That has worked for me. I'm stuck with stock rooted debloated on my own as I need my volte to work. Dont care as much about Wi-Fi calling but they seem to be tied together.

Alarand said:
My twrp restore to stock didn't fix the WFC thing. Works again after RUU though. Only thing I noticed was a restart prompt on first boot after ruu saying sim settings have been updated.

The one gimmicky feature I'm somewhat reliant on always breaks on updates ;p

Sent from my HTC 10 using Tapatalk

chas123 · Dec 21, 2016

Volte is working on at&t. Just for ****s and giggles I enabled vowifi in settings. I get the same log messages that were in the log that was posted.

E/ActivityThread(11336): Failed to find provider info for com.htc.vowifi

There is no com.htc.vowifi package in the ROM. Even stock. It leads me to believe that there is a missing symlink

Captain_Throwback · Dec 21, 2016

chas123 said:
Volte is working on at&t. Just for ****s and giggles I enabled vowifi in settings. I get the same log messages that were in the log that was posted.

E/ActivityThread(11336): Failed to find provider info for com.htc.vowifi

There is no com.htc.vowifi package in the ROM. Even stock. It leads me to believe that there is a missing symlink

Probably a missing (or incorrect) permission in the updater-script. The symlinks shouldn't be an issue since they're taken from the system image directly. The set_metadata perms/contexts, on the other hand, were done manually (from previous Android versions), and may have changed (or more may have been added) for Nougat.

The file contexts is now in a binary format which makes it more difficult to read/extract. Though I think there may be a tool for that somewhere...

p50kombi · Dec 21, 2016

Captain_Throwback said:
Probably a missing (or incorrect) permission in the updater-script. The symlinks shouldn't be an issue since they're taken from the system image directly. The set_metadata perms/contexts, on the other hand, were done manually (from previous Android versions), and may have changed (or more may have been added) for Nougat.

The file contexts is now in a binary format which makes it more difficult to read/extract. Though I think there may be a tool for that somewhere...

Subscribing to here to see if you guys will be able to figure it out.
Ive got tons of logs etc all posting towards enable_vowifi prop not being there.

chas123 · Dec 21, 2016

Captain_Throwback said:
Probably a missing (or incorrect) permission in the updater-script. The symlinks shouldn't be an issue since they're taken from the system image directly. The set_metadata perms/contexts, on the other hand, were done manually (from previous Android versions), and may have changed (or more may have been added) for Nougat.

The file contexts is now in a binary format which makes it more difficult to read/extract. Though I think there may be a tool for that somewhere...

I nosed around for a bit trying to find something to extract the bin file just to compare it to the one in the kitchen. Need to revisit that.

The other line in the log- I/ActivityManager(3626): Cannot resolve ContentProvider=com.htc.vowifi

Like I said- That package does not exist. The call for it comes from Settings i.e content://com.htc.vowifi. Presumably, the actual URI/content would come from wfc-provider.apk and the actual vowifi apk would be WFCWifiCall.apk w/ the package name com.htc.wfcwificall. I might try to flash a sparse_dat ROM to see what happens.

Captain_Throwback · Dec 21, 2016

chas123 said:
I nosed around for a bit trying to find something to extract the bin file just to compare it to the one in the kitchen. Need to revisit that.

The other line in the log- I/ActivityManager(3626): Cannot resolve ContentProvider=com.htc.vowifi

Like I said- That package does not exist. The call for it comes from Settings i.e content://com.htc.vowifi. Presumably, the actual URI/content would come from wfc-provider.apk and the actual vowifi apk would be WFCWifiCall.apk w/ the package name com.htc.wfcwificall. I might try to flash a sparse_dat ROM to see what happens.

I'm pretty sure @nkk71 knows how to extract the file_contexts.bin. If he could share that knowledge with us and @SuperR. as well it would probably allow the kitchen to find the proper contexts/permissions for whatever files are different/missing.

p50kombi · Dec 21, 2016

chas123 said:
I nosed around for a bit trying to find something to extract the bin file just to compare it to the one in the kitchen. Need to revisit that.

The other line in the log- I/ActivityManager(3626): Cannot resolve ContentProvider=com.htc.vowifi

Like I said- That package does not exist. The call for it comes from Settings i.e content://com.htc.vowifi. Presumably, the actual URI/content would come from wfc-provider.apk and the actual vowifi apk would be WFCWifiCall.apk w/ the package name com.htc.wfcwificall. I might try to flash a sparse_dat ROM to see what happens.

If there's anything I can do to help figure this out, let me know...
I'm kind of dependant of WiFi calling, it's close to Christmas so its quiet with calls at the moment thankfully.

Oh, btw. That's WiFi calling in the UK on EE network

SuperR. · Dec 21, 2016

Captain_Throwback said:
I'm pretty sure @nkk71 knows how to extract the file_contexts.bin. If he could share that knowledge with us and @SuperR. as well it would probably allow the kitchen to find the proper contexts/permissions for whatever files are different/missing.

The kitchen already extracts file_contexts.bin. It has for a while now actually. The bin format was introduced in M for some devices. Take a look in 00_project_files after extracting your rom. file_contexts is the extracted file_contexts.bin if it exists. The kitchen does not use any preset file_contexts, only preset file permissions. file_contexts2 is a filtered list the kitchen uses for set_metadata roms.

LeeDroid · Dec 21, 2016

SuperR. said:
The kitchen already extracts file_contexts.bin. It has for a while now actually. The bin format was introduced in M for some devices. Take a look in 00_project_files after extracting your rom. file_contexts is the extracted file_contexts.bin if it exists. The kitchen does not use any preset file_contexts, only preset file permissions. file_contexts2 is a filtered list the kitchen uses for set_metadata roms.

That's what I thought.. the log errors thrown by WiFi calling do look to be security related, just not had time to try and get to the bottom of it yet.. doesn't look like the advanced calling features props are being set at all once the system partition has been modified, which leads me to think it could be verity or selinux related, a layer of security for carrier configurations

P.S .. really appreciate the work you do on the kitchen, it certainly makes life a lot easier when jumping to a new base

[ROM/MAGISK]Bad Boyz US Unlocked HTC 10 ROM | N | 2.41.617.3 | v3.2 | updated 2.1.17

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Inactive Recognized Contributor

Senior Member

Recognized Developer

Senior Member

Senior Member

Attachments

Senior Member

Senior Member

Senior Member

Recognized Developer

Senior Member

Senior Member

Recognized Developer

Senior Member

Recognized Developer

Recognized Developer

Similar threads

Top Liked Posts