yashsingh1/xdaforums huggingface dataset:
[Miscellaneous Android Development] mdl054:
Hello, I'm new to ROM development. I'm trying to make a ROM without any google services. I plan to offer it with MicroG. I've had a hard time finding a list of all google services files to remove and I have had to research each file individually and have had poor luck so far. Rather than reinvent the wheel, is there is a list available?
[Galaxy S6 Q&A, Help & Troubleshooting] Rockyuk:
Hi Everyone,

I had a custom rom installed then I could not root it for some reason. So I decided to start all over again and reinstalled stock 7.0. Now I cannot root this or install custom recovery on it! I have tried so many different methods but none of them seem to work
[Galaxy S6 Q&A, Help & Troubleshooting] Fatal_Scythe:
Hi, what's your Model Nr.? Have you tried it with the

CF-Autoroot.zip on your Computer? Otherwise you can also download the Supersu.zip, then flash TWRP with Odin and after that flash the Supersu Zip. :)
[Galaxy S6 Q&A, Help & Troubleshooting] Rockyuk:
Hi Fatal,

I managed to find an auto root and managed to do it via odin. Thank you for your reply ?
[Wing, P4350 General] Creekboyz22:
:DHey guys I know there must be one out there. Im looking for a message threading app. I've tried Vitos and one more and they just dont seem to work too well. If anyone has any better ideas or current apps they enjoy. Please let me know. Thanks in advance.
[Wing, P4350 General] dreIx:
It's only in WM 6.1, its default in this ROMs:)

It's no way to add it to WM5,6...
[Wing, P4350 General] fzzyrn:
actually, there are a bunch of third party programs as well as a palm threaded sms cab. just google for them.

Note- I did not provide a link to the palm sms cab
[Wing, P4350 General] jaekidd1012:
I tried Codys WM6 Threaded SMS app on my Wing running the stock ROM and liked it minus the fact that it couldn't automatically configure itself to T-Mobile's MMS servers.
[Google Pixel XL Questions & Answers] kingbri:
I cannot connect to any network except 2g and I can't send calls or receive messages when on 2g. When the phone boots up, I get a signal icon with the letter "R" next to it and have the numbers 3107 as my carrier, then it switches to verizon. And since the carrier's verizon, I can't freely edit apns because verizon's stupid
[Google Pixel XL Questions & Answers] lafester:
Maybe give us some clue as to what you are running and what caused the problem.
[Google Pixel XL Questions & Answers] kingbri:
This problem has been fixed thanks to [MENTION=1268473]stebo[/MENTION]murkin420, just needed to flash original nougat firmware apparently it was a verizon provisioning issue
[Google Pixel XL Questions & Answers] Phalanx7621:
Thank God. I love the kernel.
[Galaxy Note 4 Q&A, Help & Troubleshooting] grwalker:
This may be a dumb question but does Note 4 micro USB Port have (slightly) different dimensions?

I have a USB to micro USB cable I use to connect a stick to my HTC One X, S3, SamsungTablet, etc. However the micro USB wont fit into my Note 4. (or Note 3 and Note 2 as well).

I also have a endoscope camera with micro USB connector that fits all my micro USB devices except the Note 4 (it also does not fit the Note 3 and 2 as well).

Charging cables however fit all my micro USB connections.

So wondering if the Note 4 USB micro USB port is slightly different in size

Thanks in advance
[Galaxy Note 4 Q&A, Help & Troubleshooting] jackspadeza:
Sup bro.. The issue is not so much the charging port size but rather the retaining clips in the port and on the charger tip.. There's a reason why Samsung suggests you only use the accessories that come in the box. Using other cables could have these clips oddly sized and can very well destroy your charging port over time..

Good luck. Hope this answers your question
[Galaxy Note 4 Q&A, Help & Troubleshooting] grwalker:
OK good to know. Wondered by things didnt fit and wasnt comfortbale putting too much force into making it fit

Thanks
[Galaxy Note 4 Q&A, Help & Troubleshooting] raul6:
Did you try without the case cover, in case you are using one. It could be stopping the usb from being fully inserted
[ZTE Axon 7 Questions & Answers] bondchadbond:
ive seen a few people post on here with this problem but none of the posted solutions are working for me. Im on oreo b12, on verizon. i have tried rooted and unrooted. I have 4g lte data connected no problem, but when the hotspot goes up it is not transmitting data. I do pay for the hotspot which makes this aggravating. i did some searching on here and the xda forums, and i read about changing the APN settings, which i have to no avail in helping this. I read about the "settings put global tether_dun_required 0" and tried that only to get an error "failure calling service settings" (i may be a little off im running from memory right now). when googling that error i read about changing the selinux to permissive, thats where i was over my head and was denied, but i stopped there. does anyone here have an idea of another way for me to try to tackle this? was i doing something wrong? I was rooted when i tried all of this, i reinstalled and went unrooted to see if that would help but it did not. Any help or a guiding light would be appreciated and i know this question has come up a few times before its just not working for me.
[ZTE Axon 7 Questions & Answers] RobboW:
I'm still on stock, non rooted Nougat and encrypted and have 2 SIMs, was hotspotting my personal SIM no problem but couldn't hotspot my work SIM which was a real PIA. I ensured the APN was good but that didn't help. After some googling for solutions I used my PC and ADB to alter a setting for it.

Now I can hotspot it perfectly. Can't remember what it was but it was a basic command. At the time I also removed a bunch of system apps I didn't use, mostly Google bloat. Made the phone snappier again too.
[ZTE Axon 7 Questions & Answers] bondchadbond:
if you do remember can you post that here? im redigging into this
[ZTE Axon 7 Questions & Answers] InspectMyGadget:
How can u not remember no help at all
[ZTE Axon 7 Questions & Answers] RobboW:
Keep your pants on, I never saw the reply here :rolleyes::o

If I get some googling time I'll have a look, but you guys could do the same...;)
[ZTE Axon 7 Questions & Answers] InspectMyGadget:
Do it for all of us Google it for us before you post a incomplete reply. If you are unaware of how to create a link to save others to complete your reply maybe try posting that .

It's like saying I know where the true superior being resides in religious texts "Google It" as educated beings know there isn't one but that doesn't stop people googling it and leading them into a pointless search on truth based on someone's made up fairytale.

My pants are on the way they should be on unlike yours because I use a belt as where you has their bare arse hanging out for others to see.

(Made a arse of yourself)

Ball is in your court
[ZTE Axon 7 Questions & Answers] RobboW:
You want me to help you whilst insulting me, strange way to go about it :confused:

Have a read of this and you get the idea of what needs doing. You have to be comfortable using ADB.

https://diggle.tech/news/2016/03/enable-tethering-android-5-1-beyond-marshmallow/

Another setting to try is:

net.tethering.noprovisioning=true

I can't check it myself as after Oreo update my phone works with hotspot off either SIM anyway.
[OnePlus 6 Guides, News, & Discussion] rickysidhu_:
Very informative and I'd even recommend this read for users who already know a bit about the partitions!
[OnePlus 6 Guides, News, & Discussion] lollyjay:
Excellent guide. Can I link it?
[OnePlus 6 Guides, News, & Discussion] iElvis:
Of course, your guide is linked here too. :highfive:
[OnePlus 6 Guides, News, & Discussion] MishaalRahman:
A quick read over this and I can't find anything glaringly wrong with it. Nice write up. Considering adapting it for the Portal if you're okay with that, OP.
[OnePlus 6 Guides, News, & Discussion] iElvis:
Feel free!
[OnePlus 6 Guides, News, & Discussion] lollyjay:
Done! And thank you.
[OnePlus 6 Guides, News, & Discussion] vikasb32:
Still little confused here.so if I flashed full ROM zip(not ota zip) from twrp then I have updated system or my phone will soft brick?
[OnePlus 6 Guides, News, & Discussion] iElvis:
Flashing the full rom zip will give you an updated system, but stock unless you follow by reinstalling twrp, etc.
[OnePlus 6 Guides, News, & Discussion] sighted:
No other words than THANK YOU! You've clarified our minds!
[OnePlus 6 Guides, News, & Discussion] texasaggie1:
Nice write up. I did have a question though. If I flash the full stock rom in TWRP does it automatically flash to the non-active partition? I've had a couple of unexpected issues when flashing.
[OnePlus 6 Guides, News, & Discussion] hithere4x:
Man that's something

Any way Thank you

I was lazy to search and read about the whole thing , but you help to provide what I need to know .
[OnePlus 6 Guides, News, & Discussion] iElvis:
Correct. When you flash the full stock rom, it will install to the inactive slot, and it will mark that slot as the new active slot, which means that if you reboot right after flashing, you will boot onto a fully stock slot without twrp. This is why you need to immediately flash the twrp installer (which always flashes to both slots), then reboot to recovery, which will get you onto the new slot, with twrp, from which you can reflash magisk, etc.
[OnePlus 6 Guides, News, & Discussion] texasaggie1:
Ah ok. I just ended up flashing the stock ROM twice, once to each partition. Then I ran the Twrp installer. Then I flashed magisk twice, once to each partition and that fixed my issues
[OnePlus 6 Guides, News, & Discussion] carlos67:
Excellent write up :good:
[OnePlus 6 Guides, News, & Discussion] RusherDude:
Awesome writeup!!! this needs an sticky big time.

One question, why does TWRP flash stuff on current slot but full roms on the other slot (and changes slot then?). It is because it replicates the Update Engine protocol or something with entire stock roms only?

PS: I wish there was a more detailed version after the initial setup, like when **** happens and slots get disabled by the bootloader and such. I wonder if when an slot is disabled you can twrp enable/change into it or only flashing stock image works? There's a lot of stuff like this, like what happens if you manage to make both slots unusable (even if bootloader partition works, fastboot wouldn't be reachable right? :S).

This seems like just a hell of an environtment to control compared to the simple old partition scheme.. yeah, here you can have 2 systems set up incase something breaks, great, but you do not control the boot process, the bootloader does, and this is not good for us. Something that affects both slots at the same time like TWRP can go wrong (for example a bugged release of TWRP) and derp you both systems and let you without an unusable phone without even fasboot?... yeah qualcomm protocol but come on..

You'd add on the guide that you can disable seamless updates on developer options. This is very important!! I think that the manual OTA flashing is the way to go if we want to not get into ****..

And you're right, this is ultra intimidating, I've never ever had any problems rooting and such my first android phone.. it was an easy read explaining that bootloader->kernel->system->user, 1) unlock 2) twrp 3) flash root and mods and do nandroids... and if something goes wrong, if you never touched the bootloader partition you could always go into fastboot and fix, or into TWRP and fix even if system bootloops. Here if system bootlops you can't even use TWRP or fastboot on that slot???? wtf... super intimidating.

You added most of the good stuff on the first post.. how about a new section "the bad side" or something like that with all the stuff im saying and more bad stuff that I don't even know yet? :P You will evade most people getting onto those situations and post here asking about that stuff.

Thanks!
[OnePlus 6 Guides, News, & Discussion] iElvis:
I assume because it's coded to flash to both slots. The stock rom updates are set up to use Google's A/B approach, which sets out a specific process for flashing updates.

The A/B info page I linked explains exactly what happens:

You can see there are multiple stages here, and if the bootloader can't even load, that slot won't be marked as active.

There's an even more detailed version here: https://source.android.com/devices/tech/ota/ab/ab_implement

As I understand it, twrp can change active slots, but if the slot has been marked unbootable (because it's not bootable), then it probably has to fixed with a clean reflash.

Unless the slot is completely empty, you should still be able to get to bootloader. Obviously, if the bootloaders are corrupted on both slots, you have a brick, but you can do that on non-A/B phones too.

I'm not sure the situation is that dire. A bad release of twrp could bork a non-A/B phone the same way? Here you've got two slots instead of one.

I'm not seeing an option to disable A/B updates anywhere.

I don't think this is true. If you're simply in a system bootloop, you can still get into bootloader.
[OnePlus 6 Guides, News, & Discussion] RusherDude:
Thanks :)

All this is related to the same doubt. On the flow on the page you linked, it tries to boot, if it fails N times it sets the slot as unbootable and changes to the other. You cannot just change to the previous slot and enter fasboot there since the bootloader won't boot that already unbootable boot. It is considered unbootable even if its a system issue with bootloader/kernel working.. or I'm getting that wrong? On a normal partitions phone, you won't ever get locked to enter fasboot because system won't boot, here it will happen per the flow diagram on the site...

Not A/B updates, but automatic updates. I don't have the phone, but I've been told in this sub that there's an option to disable automatic updates there.
[OnePlus 6 Guides, News, & Discussion] iElvis:
I think I see what you may be missing here. One slot being unbootable doesn't lock you out of fastboot. You can get into fastboot on the other slot, where you can flash anything you want to either slot. So you're not locked out of it if it fails to boot, you just can't boot up on that slot and the system will boot on the other slot.

Ah, yes, you can indeed disable automatic upgrades. You can also just download the OTA and not reboot, which I've done several times. Download, stop the process, reboot to recovery before the slot switches over.
[OnePlus 6 Guides, News, & Discussion] RusherDude:
In that scenario, yes you could reflash from slot B, but if you manage to then also bootloop on slot B, you end up with 2 slots with bootloader & kernel partitions working properly, system not booting and unable to enter fastboot or twrp on any of those? My doubt here is if bootloader/fastboot is "always there" even if you derp on both slots or not. If there isn't and you're reduced to qualcomm protocol having 2 correct aboot/fastboot partitions it is the most idiotic measure I have seen done by Google in a long time.

I'm interested in that. Which process do you kill? And after rebooting to recovery, you just reboot normal and the slot change and such is ignored and system ignores the download ota and such? or from now on you can't reboot normally again?
[OnePlus 6 Guides, News, & Discussion] iElvis:
That question I can't answer. So far I haven't seen anyone get stuck on a black screen except when they manually changed the active slot in twrp and had a blank slot. As I noted in the OP, manually switching is a risky thing to do unless you know exactly what you're doing. It would indeed seem odd for Google to insist on a structure that allows it to happen, but then again, the design of the arrangement doesn't anticipate people deliberately circumventing the safeguards. Maybe someone else can weigh in on that.

Two different things here. You can accept the OTA and let it install, then dismiss the reboot request and manually reboot to twrp. Since you're still on the old slot (the active slot doesn't switch over until there's a successful boot on the updated slot), you reboot to your existing twrp, and from there you can reflash twrp (which installs on both slots). Then rebooting to recovery again will get you over to the new slot and you can reinstall magisk, etc.

I don't think you can accept the OTA and not have it install. You can download the full zip from the official site, load it onto your phone, and then flash manually in twrp. But you do still need to immediately reinstall twrp after you do it, before rebooting, because the slot will switch when you reboot and the new slot has stock recovery until you flash twrp.
[OnePlus 6 Guides, News, & Discussion] RusherDude:
I see. It's a chaotic scenario waiting to happen for a flasher on a bad day :P.

Btw I wonder, on the scenario you say (I haven't seen anyone get stuck on a black screen except when they manually changed the active slot in twrp and had a blank slot), the user changed manually the active slot into a black screen (unflashed or corrupt other slot ok). If you change the slot, and that slot is not bootable or anything, shouldn't it just fail at trying to boot it and re try to boot into the working slot again?

I guess that this scenario happens when the phone is new and there is nothing flashed on slot B and the user changes to slot B on TWRP. right? But in that scenario A works, why is anyone getting stuck on one of the slots being the other bootable? this is interesting!

Aww :( though u could skip the OTA. I see, thanks!! In that procedure, you need to flash rom, then reflash twrp, then reboot twrp (without switching slot manually). It will auto switch slot to new twrp on other slot, then flash rest of the stuff, correct?

Sorry for all the questions :P. I'm trying to understand very well I'm what I'm getting into...
[OnePlus 6 Guides, News, & Discussion] iElvis:
I'm not a twrp developer, but I assume that what twrp does is change the ActiveBootSlot and markBootSuccessful values from one slot to the other. That's what's dangerous if you don't have a clear and correct idea of what's on that slot. You're circumventing the normal process for changing the values. That isn't to say there's never a reason to do it, but it's one of those tools that can cause problems in untrained hands. If the system follows those values and finds nothing to boot with, it stops. Normally the values don't get changed until there has been a successful install on the slot, which will prevent a black screen. But if the values have been changed to an empty slot, the system will keep trying to boot it, and you have no way to change them back.

Fortunately, that seems like a worst-case scenario that's possible only on a new phone with a blank slot B, and on which the clueless owner immediately decides to start fooling around with twrp (having said that, a few people here have done exactly that). Once it's been flashed at least once, you should be able to get into fastboot because there will be bootloaders on both slots.

I'll allow that it does seem a little dangerous to ship with a blank slot on a phone that is so popular with phone modders. But they do warn you that you're taking responsibility for what you're doing. :D

Correct. More on that here: https://xdaforums.com/oneplus-6/how-to/guide-how-to-install-official-twrp-t3801558
[OnePlus 6 Guides, News, & Discussion] RusherDude:
But even if values of the derped/null slot are changed to ActiveSlot, PreferredSlot and BootableSuccesfull, it will try to boot, fail (because no BL/KERNEL/SYSTEM/whatever) and then decrease count and try until it reaches 0 and marks it as BootableUnsucesfull and deactivates the slot, in which case you change back to the one where you were when you derped with TWRP and can boot. Why do the black screen happen? why is the bootloader not auto turning the slot to disabled again when it can't boot anything on the null slot? That is against the A/B flow on the google site, there is no exception there, if the boot failed it will end up disabling the slot and changing to the previous one, but here by what you're telling it doesn't happen and the user is always on a black screen because the bootloader never disables the slot. Either this is a bug or theres something important we are skipping here.... that should never happen!!!!!

The only scenario when I see the black screen happening to these guys is if on TWRP they missed flashing something (even magisk if they needed it for having it previously) and thus the "first" slot is ALSO ****ed up, so these guys are in the both slots derped scenario and if can't boot to any slot.... even if bootloaders there are working..... Google are dumbs.

Once its flashed, if you derp slot B you can enter fastboot on A yes, but the fact that you can flash on A or B at any time on fastboot or twrp makes it really really easy for someone to derp the 2 slots at the same time, and even if there are fastboot partitions there...
[OnePlus 6 Guides, News, & Discussion] gippy2:
Well after reading that ,has made a whole lot of things easier to understand..Thank you very much op.:good:
[OnePlus 6 Guides, News, & Discussion] djrocks:
Thanks [MENTION=4656338]iElvis[/MENTION]... We really need more people like you on xda.. Makes development more fun and exciting...
[OnePlus 6 Guides, News, & Discussion] iElvis:
Yeah, that's not how it works. It hasn't happened to me, but you can get out of the black screen and back to bootloader manually. I believe it's not getting marked unbootable because that process is part of how the update engine is supposed to work. If you just manually switch over, I don't think anything gets marked.
[OnePlus 6 Guides, News, & Discussion] RusherDude:
Well, I think that it's the own BL who would mark the slot as unbootable after the failed attempts in this case, but as you say it sounds recoverable... otherwise something is missing here.

Anyway, when you specify "but you can get out of the black screen and back to bootloader manually", I wonder how this goes, because per de flow diagram by google, the bootloader will try to boot to the new changed slot, fail, then decrease count and switch to the other slot and boot it, so if the user gets stuck at the black screen is because the phone is not failing to boot one and moving to the other for some reason. Do you know any scenario where with one working slot the phone wouldn't switch into it for some reason after failing to boot the other one?
[OnePlus 6 Guides, News, & Discussion] iElvis:
We're past the point where I can speak knowledgeably about what exactly is going on. But several people black-screened by somehow borking the 5.1.9 upgrade and switching slots manually in an attempt to get out. Black screen seems like a dead end – the phone just stops. It's not part of the update process, so it's not following that flow chart.

Here's a thread that may help you understand better: https://xdaforums.com/oneplus-6/help/boots-to-os-immediately-shuts-reboots-t3817951
[OnePlus 6 Guides, News, & Discussion] RusherDude:
I see, thanks a ton for all the help!! Yes, it finally ended! Sorry for kidnapping the thread lol
[OnePlus 6 Guides, News, & Discussion] iElvis:
Not sure what you're asking. You can certainly install custom roms.
[OnePlus 6 Guides, News, & Discussion] iElvis:
No. You cannot install non-A/B roms on an A/B phone. The partition layout is not the same and it will either fail to flash or brick your phone.
[OnePlus 6 Guides, News, & Discussion] iElvis:
There is no "partition A". There are a series of duplicated partitions, e.g., boot_a, boot_b, system_a, system_b, etc. But not all partitions are duplicated. Trying to change that arrangement is likely to break one or both of your slots.

What you're trying to do will not work. You are going to brick your phone if you try to force it to happen.
[OnePlus 6 Guides, News, & Discussion] iElvis:
Updated OP with link to this XDA Portal article that all of you should read.

https://www.xda-developers.com/how-...ess-updates-affect-custom-development-on-xda/