yashsingh1/xdaforums huggingface dataset:
[General Questions and Answers] Droidriven:
Safestrap recovery is not like TWRP or CWM custom recovery. When using Safestrap, you don't "flash" or "install" the ROM, it is never supposed to actually be flashed onto the device. Safestrap is only used to "boot" the ROM of your choice. The way it works is, your stock OS boots, then, Safestrap interrupts the booting process just before system boots, then Safestrap inserts the ROM of your choice and boots that instead of your stock system. If you flashed the ROM in Safestrap, it probably overwrote your stock OS, that isn't how you were supposed to do it. You probably have a locked bootloader(which is probably why you're using Safestrap, since it is the only option for devices with locked bootloader), when you "flash" the ROM, it overwrites the stock system(or sometimes, doesn't overwrite anything, instead, it sets a "flag" for the bootloader to know that the device has been tampered with), then when you boot the device, the locked bootloader sees the custom ROM system but ignores it because it isn't stock, it doesn't pass the signature and security checks built into the locked bootloader, the locked bootloader does not allow the custom system boot, this causes the device to bootloop as if their is no OS at all(this pretty much describes your situation). You're supposed to leave your stock OS alone and then in Safestrap, place your custom ROM in one of the other slots(not in the slot where your stock OS is), then when you boot Safestrap, choose the OS you want then boot that OS.

If you've overwritten your stock OS(or if a flag was set) you'll have to completely recover the device by flashing the stock firmware then starting over with rooting and installing Safestrap.

If your bootloader is unlocked, you need to flash TWRP instead of Safestrap recovery, then you can flash your ROMs.
[General Questions and Answers] Sam Nakamura:
What's your setup like?

Magisk? Xposed? Mods? Any specific modules installed?

Beta or stable OOS? Custom Kernel?

Ever had a liquid damage, heavy rain, etc.?

Tried to clean flash with stock kernel, without modifications?

What have you tried to solve the problem so far?
[General Questions and Answers] @srmahunt:
See the screenshots for the list of magisk and xposed modules installed.

I am on stock oos stable build and stock kernel.

I haven't done any kernel modification and haven't tried clean flasging though.

No liquid damage or anything(the switches work fine after boot and if i work continuously with my device, the problem starts after my device goes to sleep for sometimes)

I tried to disable the mods and the problem still exists.
[General Questions and Answers] Sam Nakamura:
WOW, this is massive! :eek:

I'd guess it's indeed related to the tons of modifications you applied, you should actually do the "exclude/include game", what I mean is it would be reasonable to uninstall xposed and all magisk modules followed by a dirty flash of the current ROM you're using, then you can start to slowly re-install first the magisk modules one by one, carefully observing when the issue starts, look out for culprits to the weird behavior you have described, if all goes well and you find nothing out of the ordinary do same with the xposed modules - this mess of modules can easily cross influence each other, I mean that sher probability on your setup that 1 or more modules don't play nicely with each other is simply much bigger than for the average user, I would even say you cannot run so many different mods simultaneously without expecting issues like you described...

Think again what of those modules are really needed and what can be left behind, minimalistic setups are more likely to be more stable!

The only real advice I could give you is to tide up this chaos, this mess is most likely is the reason for your problem - good luck :)

Edit: looks like you're additionally using Substratum (however the statusbar could be xposed too, not sure), if so this could also be something to look into too, potentially...
[General Questions and Answers] Droidriven:
I agree, that is just way too much for any device to really keep up with. It's almost certain to be unstable even if, under normal circumstances, everything installed would normally work well together in some mixture one way or another, just the fact that the device has soooo..... much stuff installed/modified, it's just way too many pieces of software for the hardware to handle all at one time or to multi-task between everything at each instance "this" or "that" module or other software is needed/loaded/reloaded/cached during usage, RAM and CPU just doesn't have enough "hands" to juggle everything. Especially considering that each mod is applied using a framework that operates at the system level, which requires the system try to maintain all of the mods back and forth at each instance, continuously, that's asking a lot of any device.
[General Questions and Answers] DB126:
Ridiculous - just asking for trouble w/o corresponding benefit. Get you s!#t in order, figure out what's important, jettison the rest. Join a module hoarder anonymous group for help if needed.

That said, beyond initial load times this amazing collection of rubbish is not necessarily burdensome on the underlying hardware or OS. Each item has its own characteristics which may or may not impact system performance. Far more likely are 'unforeseen' (cough) conflicts between modules as most casual developers don't engage in meaningful environmental or regression testing.

tl;dr: keep it simple; profit.
[General Questions and Answers] kreuziger#:
Custom ROM Note 3 N900A - HELP

I did place the custom ROM in ROMslot 1... and I got nothing. I am assuming my bootloader is locked as I have the Note 3 fom ATT. How can I check if it is unlocked? And what about the boot .img I mentioned?

---------- Post added at 03:10 PM ---------- Previous post was at 02:56 PM ----------

I did place the custom ROM in ROMslot 1... and I got nothing. I am assuming my bootloader is locked as I have the Note 3 fom ATT. How can I check if it is unlocked? And what about the boot.img I mentioned?
[General Questions and Answers] Sam Nakamura:
I don't think there's a need to further test as it's well known that the Note 3 AT&T cannot be unlocked, there's no method available to this day, see this recent thread from the Note 3 AT&T forums which confirms this:

https://xdaforums.com/note-3-att/help/bootloader-unlock-news-hope-t3828429
[General Questions and Answers] kreuziger#:
Custom ROM Note 3 N900A - HELP

I did place the custom ROM in ROMslot 1... and I got nothing. I am assuming my bootloader is locked as I have the Note 3 fom ATT. How can I check if it is unlocked? And what about the boot.img I mentioned?
[General Questions and Answers] Droidriven:
If I remember correctly, your custom ROM doesn't go in slot 1, that is reserved for your stock OS, your custom ROM should be placed in a slot other than the one that your stock ROM is in. Safestrap won't work without your stock OS, only the stock OS can boot past your locked bootloader, then once booted past the bootloader, Safestrap takes over and gives you an "opening" to boot the system of your choice instead of continuing to boot your stock OS. What boot.img? I'm assuming that you're using a modified stock ROM? It still requires your stock OS to start the booting process, it can't use the boot.img in your ROM by itself.

When your device boots, it's supposed to boot your stock OS starting with your stock bootloader, then, after the kernel loads but just before the system loads, Safestrap interrupts the boot chain, then inserts the ROM you choose, then it uses the boot.img from your ROM. It can't just go straight into booting your ROM, it has to have the original stock OS to properly start the booting process because it "piggybacks" on your stock OS to get past your locked bootloader. Your modified stock ROM cannot be where the booting process starts, it doesn't work that way.

Flash your stock firmware to return the device to normal, then start over. Root the device, install Safestrap, then apply your ROM to the correct slot without disturbing the slot where your stock OS, and don't try to "flash" anything. You're not using Safstrap to flash anything, You're only using it to "boot" the ROM, similar to booting a Linux live USB or Linux live CD, or similar to using a dual boot configuration on your PC, your stock OS is still there, you're just running something else on top of it or alongside it.
[General Questions and Answers] justcallmeali:
Help Needed!!!

I am sending this message hoping that someone will help me with my issue regarding my S8+ which doesn't want to update from 7.0 because I moved from the states to Malaysia.

Model Number: SM-G955U

Android Version: 7.0

Samsung experience version: 8.1

Baseband Version: G955USQS2BQL1

Service Provider:

SA0MC_SM-G955U_OYN_XAA_0144

98899A355A38474B34

XAA/XAA/SPR

I really would appreciate if someone helps me updating it to Oreo as my video calling and a lot of other features stopped working.
[General Questions and Answers] Droidriven:
Supposedly, all of the US variants of S8+ offered by the various US carriers can flash a S8+ firmware from any of the other US carriers, but it's still recommended to flash the original carrier specific firmware.

Since you're using the device in another country, try flashing a firmware for one of the GSM based carriers(AT&T or T-Mobile, for example). Here is a list of all firmware for SM-G955U.

http://samsung-updates.com/device/?id=SM-G955U

Download the firmware for one of the GSM carriers, then flash that firmware via Odin on PC. I doubt you can do this via OTA while in another country, so if you're trying to update via OTA, that isn't going to work, you'll have to flash it via Odin to update.
[General Questions and Answers] Sam Nakamura:
You could also try one of the VPN APPs from Play Store and change your location to U.S. then trigger the update (maybe reboot before) again via setting -> software update, if only your current location is the problem this should be an easy fix, otherwise go with the solution suggested by [MENTION=5691352]Droidriven[/MENTION], this should work in any case...
[General Questions and Answers] Droidriven:
That might work, but I'm not sure. It seems to me that the current firmware on the device is a Sprint firmware. If I remember correctly, Sprint is a CDMA network, I could be wrong, but differences in networks may interfere with the OTA option. I'm not sure it is only a location thing in this scenario. Then again, I'll learn something out of this scenario if it's just a location thing.
[General Questions and Answers] zelendel:
If it is a carrier version then he is out of luck as the carriers push the OTA only to devices on their network. Location will have nothing to do with it. Unless he in on Sprint then he will not be getting OTA updates ever again.
[General Questions and Answers] xunholyx:
Yep. Your account has to have been active in the last 50 days iirc. The OTAs are pushed out according to your IMEI/MEID being on the network still
[General Questions and Answers] kreuziger#:
Well, there is a slot for stock....then Rom slot 1, 2, 3 ,4. Im assuming you forgot there is a stock ROM slot as well. I left that one alone and activated ROM slot 1. So stock I can still boot into. So now I dont put another stock on slot 1 right? I wouldn't see why.

Also I didn'r mean to say "flash" with safe strap. I do understand all of that. I just don't see what is going on wrong ..Any other ideas.. Sorry :(
[General Questions and Answers] :
OK.

Q: Can your isp see links you've tapped on while using a VPN app on phone connected to my Wi-Fi which is not behind a vpn.

???
[General Questions and Answers] Mr. Cube:
Hello, I have a OnePlus 5T with OxygenOS 5.1.5 and Magisk 17.1.

My question is why does Poweramp music player have access to the /sbin directory without root?

Do I have to worry about that? :confused:

thx
[General Questions and Answers] Back_lash23:
help pls

i got a huawei y6 II.

i done a factory rest and i need to sign into google but the wifi wouldn't start it says connection failed.

i tried mutiple wifi points none of them worked.

i hope you guys can help me.

edit:i fixed it.
[General Questions and Answers] Droidriven:
[MENTION=7125933]Sam Nakamura[/MENTION]?
[General Questions and Answers] :
Can someone please explain?

Sent from my HTC One M9 using The ClaRetoX Forum App
[General Questions and Answers] scorpio76r:
I know that my job can. So I'm guessing that the answer is yes.
[General Questions and Answers] :
Damn... I'm going to open up a ticket with my vpn service.

This vpn craze is starting to raise questions and I don't really understand the tunneling traffic etc. So it's all new to me this year.. I will update my question thread. Thanks for answering
[General Questions and Answers] Back_lash23:
supersu

hi

i got a huawei y6 II (cam-l21). i originally rooted it using TWRP.

i updated super su and i lost my root privilege.

it says binary occupied. i installed older versions when it ask to update the binary normal way didn't work nor did TWRP.

i tried installing it manually using TWRP and the zip file but it didn't work (i tried multiple versions including 2.79) it just reboots no new app,no root access,nothing.

hope you guys can help.
[General Questions and Answers] SubwayChamp:
Remove first all the binaries with this https://xdaforums.com/showpost.php?p=63615067&postcount=2459

And then flash it again following this thread for your specific model https://xdaforums.com/android/general/rooting-huawei-y6-ii-cam-l21-t3501162
[General Questions and Answers] Back_lash23:
first thank you for your help.

but when i install unSU it tells me to flash boot.img. i looked it up. apparently i have to download the stock firmware and i shall find it there but instead i found a folder called dload and inside of it i found UPDATE.app

also i attempted to install magisk and it says error 1.
[General Questions and Answers] SubwayChamp:
If the zip did the job now reflashing your boot.img you will replace any remain from your kernel, take a boot from the same rom that you are using right now (extract it from the zip) and flash it using fastboot.

UPDATE.app contains the factory image, it's OK, you could need it at any time and it's better have it always when you are attempting to do modifications onto your device.

And to root it again you can pick the latest (as last step) Magisk, I guess 17.1 and flash it in TWRP. Same result, you can patch the boot image that you will to use with the actual rom and then flash it using fastboot.
[General Questions and Answers] :
Hi, I'd like to ask if someone had tried to install Galaxy S5 Neo's (SM-G903W) Nougat firmware on SM-G903F and what results you got? Any help would be greatly appreciated!
[General Questions and Answers] Giorgi-geo:
Rooting LG G3

WHAT IS BUMP?

I have LG G3 on MM, and I want to root it, so I think this is the only way - downgrade and root.

But I have a question, what the hell is BUMP? 1, 2. If I downgrade to 4.4 and root with kingroot or oneclickroot or something, will I not be able to install TWRP? or will TWRP be limited in some way cause it's not bumped?

How can locked phone be rooted in the first place? And if it's already rooted why do you need BUMPed TWRP?
[General Questions and Answers] scorpio76r:
If you downgrade to 4.4, you will be able to root it from the device itself via King root etc. As far as twrp is concerned, there are no limits as long as you have it installed which can be done via flashify.
[General Questions and Answers] DJ8ones:
Need some help understanding patching

TL;DR - Need some help learning how to patch android, specifically android-x86. I have a diff file to work with and am not sure how to use it.

**I had this post nicely formatted with embedded links, but it looks like I can't use those since I'm new. Sorry for the inconvenience of the odd-looking <dot> within my URLs**

I'm trying to load www<dot>android-x86<dot>org/releases/releasenote-8-1-rc1 to my ASUS convertible laptop. I'm having the same issue that is talked about here:

groups<dot>google<dot>com/forum/#!topic/Android-x86/AebKX154VDk

There is a solution listed at the bottom of that thread that talks about applying a kernel patch. Following the advice of lambdadroid, I want to make the patch contained here:

github<dot>com/me176c-dev/android_kernel_asus_me176c/commit/0bff9b2eb67f0430c1a8dbe4a19f3296b090578a

The problem is, I've never had to patch any Linux variant. I'm good with learning something new, but it's a little overwhelming. I feel like I'm so close to getting this resolved and just need a little guidance.

I got started by trying to follow the one-two punch of:

1. www<dot>android-x86<dot>org/getsourcecode

2. www<dot>android-x86<dot>org/documents/customizekernel

But even there, just downloading a >10 GB source file didn't feel quite right. Maybe I'm trying to oversimplify things, but it feels like I should be patching just the offending driver. And even if I follow those two, I'm not confident I know how to fold the diff file in correctly.

I generally don't like posting questions that are easily answered by simple searches. I've been searching around for guidance on kernel patching both in general and for android. I just don't feel confident yet that I've found the resources I need.

I thought about posting this to groups<dot>google<dot>com/forum/#!forum/android-x86 and maybe I still should. I just felt that the question was a little to basic for that group and this seemed like a safe place to ask it.

Ok, I've rambled long enough. Thanks in advance for any help.
[General Questions and Answers] Droidriven:
To patch the kernel, it requires compiling a completely new kernel with the patch/commit applied during the build process. Compiling a new kernel requires syncing repo and download the source for your device, which is where your 10GB comes from, you can't build the new kernel without the source. It isn't the kind of thing that can be done by modifying an existing file, you gotta start from scratch to compile the new kernel with the patch added to it.

Kernel development can be tricky business, there really aren't any good sources to use as guides to do this, every device and Android version varies from one to the next. These differences make it impossible to make a straight forward, all included, step by step guide for building/patching kernels. You're gonna have to refer to multiple guides and hope that you make sense of it.

Or, you can try reading some kernel development threads here at XDA, if you have questions, post your questions in the kernel development threads, if you haven't made enough posts to allow posting in development threads, try sending a PM to one of the developers or experienced members that you find in the kernel development threads, they might be willing to help.
[General Questions and Answers] DJ8ones:
That's exactly the kind of feedback I was looking for. I will probably try to do some more research before engaging developers or experienced members. Thanks for the help!
[General Questions and Answers] Giorgi-geo:
Thanks.

But what is BUMP? as far as I know it's for lg g3 and maybe g2.
[General Questions and Answers] nickkessler695:
What does mata mean?
[General Questions and Answers] Ibuprophen:
Mata is the codename for the "Essential PH-1" device.

An example of a known codename would be the Samsung Galaxy S5 device having a codename "klte".

~~~~~~~~~~~~~~~

UNLESS asked to do so, PLEASE don't PM me regarding support. Sent using The ClaRetoX Forum App on my SM-G900V device.
[General Questions and Answers] crussellp:
Hello all,

I am interested in rooting and installing a custom ROM on the Chinesium phone I bought the other day and I am having a hard time getting started.

(Can't post a link to the phone but a Google search of E&L S60 should get you there)

Rooting seems to be specific to the model of the phone and processor type, and I am seeing nothing that coincides with my model number.

CPU: Arm64 - V8A

Model: S60 (full_kxd6753_65_s60)

Manufacturer: Alps

OS: Nougat (7.0)

Does anyone know how to go about figuring out

1st - How to Root this thing

2nd- What ROM to install

Do I just look for other phones with known Rooting techniques that closely match my hardware? I'm not adverse to bricking it, but I also don't want to just see what happens by trying something that has a high probability of bricking my phone either!

Any and all guidance and/or suggestions would be welcome!

THEN... I went off into the wild on my own without any guides... and bricked my phone.

I used the ROM for a Umi Iron Pro with the exact same specs... and BRICK.

I can still connect to the phone with a USB cable and my PC recognizes it. Just no boot.

Any pearls of wisdom?

Please?
[General Questions and Answers] xunholyx:
There's a lot missing from this post.

You are running with an unlocked bootloader and a custom recovery now?
[General Questions and Answers] Sniperboy1:
How to install K6 power rom on a K6 Note K53a48?

I am looking for the method of deleting first 2 lines of text but I don't know from where.

I am familiar with using K6 Power TWRP image.
[General Questions and Answers] SubwayChamp:
According to this thread https://xdaforums.com/k6-power/how-to/super-thread-t3682044 the K6/K6Power/K6Note are treated as one, if the roms are compatible for all these models and you are receiving an error from TWRP related to the model you have to delete the first or two lines where you find words like "This package is for....." "getprop(ro.product..........)" .

If you are not sure yet, upload a screenshot of the updater-script opened with Notepad++ and do a copy before to made a modification.
[General Questions and Answers] Droidriven:
Get a new device, but this time, if you want a device that can be rooted, research the devices you are looking at before you buy them to see if there is a known rooting method for it and/or if TWRP and custom ROMs are available for the device.

Also, the cheap, knock-off, Chinese devices are not usually supported by developers here, even the low-end and mid range devices the mainstream manufacturers don't get much support(for example, a low end Samsung device or mid range LG device) The more popular, mainstream brands and models are the ones that get support for rooting and ROMs, especially the flagship models such as the Galaxy S devices. With the Chinese devices, there aren't many options, even if you DO find a rooting method, root is about as far as it gets, no ROMs.

I don't know why everyone buys a cheap android device and then comes here looking for root and all the cool stuff when root and the cool stuff is focused on the more popular and mainstream devices. It's like buying the cheapest car available and then going to a shop that builds race cars thinking the shop is going to have something for your car when the stuff they build is for a car that your car could never compare to.
[General Questions and Answers] JaneKimC:
Bricked THL T100s

Hi!

I have a bricked THL T100s

I have TWRP for recovery 2.7.1.1

I tried flashing some old roms that I know work but while it was booting, the battery fell out

Now I found that my system, cache and data as well intstorage is not mounted and I have no OS and can't flash a new one too

I've tried repairing the partitions (from wipe) and switching from ext4 to ext2 and back to no avail

What steps can I take to try and fix this? Thank you