yashsingh1/xdaforums huggingface dataset:
[Xposed General] Jacklack3:
Hai! I'm new here so if this isn't the place to put it so sorry! :o

Anyways so I've always wanted to install Xposed, but there are always things getting in my way, until I saw a Xposed file that would work for me perfectly! But I don't have an recovery, the tutorial I took just made me use Odin, but I am rooted with busybox. (if that's important.) Anyways so I saw how to install an custom recovery, then I saw you had to unlock your bootloader, I had to google how to check if it was unlocked and it wasn't, so I then googled how to unlock bootloader and saw you had to delete your files. Now even if I get to backup and restore, I don't like factory resetting things. Until I remembered Odin, I googled it and saw it could flash. So i'm wondering...

Can I installed Xposed using Odin? Or atleast flash an custom recovery to it using Odin without unlocking my bootloader?

Here is my tablet's stats.

Samsung Galaxy Tab A Lollipop 5.0.2 Rooted (Busybox Installed.) Stock Rom Touchwiz SM-T350
[Xposed General] joluke:
No, you can't flash with Odin. Only cwm or twrp
[Xposed General] Jacklack3:
Can I use FlashFire then?
[Xposed General] Sachin:
You should install the framework zip via custom recovery only.
[Xposed General] Dopamin3:
1) Flash TWRP (or CWM or Philz or whatever is available for your device) in Odin

2) Reboot into recovery mode and you will be in this new custom recovery you just put on

3) Flash the xposed framework

4) ?????????

5) Profit!
[Xposed General] Rakuu:
This is wrong, you can use FlashFire for it, I've done it myself a number of times.
[Xposed General] Sachin:
Ahh, ok.

didnt knew this earlier.
[Galaxy S6 General] mystery1989:
How I handled exclusively in viper4android (differential surround - Haas Effect) in one handset'm hearing louder and quieter in the second, and as I remove this function hass efect this volume is balanced whether it is normally what does it depend?
[XDA Assist] dudeman_64:
Hi all.

I have been lurking and reading, now time to post.

Like the title says, I have been given an A510 that did work, until he tried to flash it, and failed............

Tried all the tips to get it to start, no dice.:(

All I get is "Boot image verified failed" or "Entering boot menu mode, Recovery image verified failed".

I guess the question is, what can be done to correct this, or is it toast?

I have tried all of the suggestions in these forums and other sources on the 'net.

Thank you for your time, and keep up the good work!:good:

David.
[XDA Assist] xanthrax:
Hi David !

Can you tell us what exactly "he" tried to flash ?

Thank you !
[XDA Assist] dudeman_64:
Acer

Hi

From what I understand, tried to flash Clockwork Mod recovery, with all the wipe options checked, but I would have to contact Steve to confirm.

I am well versed in networking and all versions of Windows ( work in IT part time) but Android is confusing to me;)

Not sure if that helps.

Thanks.

Dave.
[XDA Assist] xanthrax:
So , when you flash CWM recovery , there are no options to check anything while doing that , maybe he wiped after entering into CWM and maybe he erased everything afterwards

Just ask Steve about what exactly he did and btw , tell him Hi ! :)
[XDA Assist] dudeman_64:
Hi.

Just so we are clear, this used to belong to my brother Steve, he has passed on to me as a project.

If I was the one who flashed it and bricked it, I would say so, I am a big boy and have messed up before...............................

Been playing with computers from the Win 3.1 days and have had my share of "mishaps"

Now that that is out of the way, I text him and asked what exactly he did, and he said he was in stalling the Clockwork Recovery Mod, and that is how the tablet ended up in its current state, that is all the info I have.

So the simple question is, can it be recovered or not?

Seeing as it will not boot far enough to be able to access it with USB I am thinking not.

I have the factory downloads for it.

Thanks.

David.
[XDA Assist] xanthrax:
After a quick search I have found this thread , have alook at it , there are some workarounds and also you can post your issue there , good luck !
[Xposed General] KelvinMead:
maybe I'm a complete ****, but how do i "Must be flashed with a custom recovery (e.g. TWRP) to install the framework.

SDK21 is Android 5.0 (Lollipop), SDK22 is Android 5.1 (also Lollipop)"

i get that i need to have the correct file; xposed-v86.1-sdk22-arm-by-romracer-20160928.zip.asc

and that it needs to be on the phone, but how do i flash?

what is a custom recovery?
[Xposed General] Sachin:
First off a custom recovery is nothing but - The open-source community has extended the original android Recovery system, to add other features:

*.system backup and restore (NANDroid),

*.the ability to apply Android changes that aren't approvedby the manufacturers or carriers,

*.improved user interface, including using the touch screeninstead of only the volume and power buttons, and

*.runs adbd, to supportADBconnections. [I just copied and pasted for wiki page]

A custom recovery has abilities to wipe system / flashing zips / modifying system etc.. Features, whereas the stock recovery has few options like apply update / wipe data / factory reset.

Every Android devices ships with stock recovery, when it to comes to rooting / modifying etc.. Then you should need to be on Custom Recovery.

There are many custom recoveries, viz ; TWRP / CWM / Philz / etc...

RN, TWRP is the best recovery out there.

Now, when it comes to xposed, if you were on Android Kitkat [Android 4.4] then, there is no need for a custom recovery in order to install xposed framework, just root [super user] could be enough.

But, on Android 5 +, we'll no longer to install xposed framework without a custom recovery. We need to flash the framework zip via custom recovery like Philz / twrp, once the flashing zip via recovery done, you need to reboot your device, then installing xposed installer app /apk will activate the xposed framework on your Android 5+ devices.

So, if you're using an Android 5+ device, then just root your device, flash a custom recovery, then flash xposed framework zip[acc. to your device's arch, like arm/ 64bit] via custom recovery, then reboot, install xposed installer app, download and activate xposed modules, enjoy.

Ref -

*.what is a Recovery ?

*.xpsoed framework zip

*.xposed uninstaller zip

*.xposed installer apk
[Xposed General] KelvinMead:
ok, so i was having a hard time, as i thought i had unlocked the boot loader, but apparently i hadn't. i have now though. using kingoroot i have unlocked the root, and when i run the xposed installed 3.0.alpha, or 3.1.1 both require me to reboot into recovery.

but i can't seem to get into recovery. i can turn off the unit, plug the power in and;

press power and hold vol+, and i get a little blue light

hold power and vol+, and it vibrates once, then 3 times, then once like - --- - --- - --- - --- - ---

press power hold the vol- and it boots into safe mode.

hold power and hold the vol- and it boots into safe mode

press power and hold the camera, does nothing

hold power and hold the camera, does nothing

do i have a recovery installed on this phone?

ack, the phone is a sony xperia m2, lollipop 5.1.1
[Xposed General] Sachin:
Yerr... Your device's on default recovery [ie;STOCK recovery]

So now, I just did a quick search and found this -

*. [Guide] unlock bootloader .

*. [Guide] [flash twrp] Sony Xperia m2 [Android 5.1.1].

Note that you need to unlock bootloader first then do stuffs.

Do with your own risk . :good:
[Xposed General] KelvinMead:
ok, so i have the boot loader unlocked, when i go to dialler, and do the *#*#737 i can see boot loader unlocked : ok

when i continue on, the tutorial is for pc, and I'm running mac, so I've downloaded the adb and fast boot from the android sdk, and have tested connection etc all is good.

I've used fast boot to install the twrp recovery recommended and the result is;

[Kelvins-MBP:android kelvinmead$ fastboot flash recovery RECOVERY-TWRP-2.8.7.0-D230X_D240X-UPDATED-THEME.img

target didn't report max-download-size

sending 'recovery' (12932 KB)...

OKAY [ 0.409s]

writing 'recovery'...

OKAY [ 1.489s]

finished. total time: 1.898s

Kelvins-MBP:android kelvinmead$

so all looks good.

now, i do this;

[from OFF] Now, to enter into the recovery, press and hold the volume down button, and while you're holding it, press and hold the Power button until it vibrates. When you see the BIG Sony logo, stop holding the Vol- Button.

but this does nothing. it just boots up like normal.
[Galaxy S 4 Q&A, Help & Troubleshooting] hehk1234:
Hello guys, Actually I've noticed problems with gaming experience on my S4 (GT-I9505), CM 13 (both Snapshot,Nighlty, JDC Team) have slow down and drop frames on game Vainglory and Bully, When I back to CM12.1 and Stock Rom (5.0.1), the performance on both OS is very superior than CM13, so why CM13 have this problems ? CM14 or lineage OS have the same issue ?
[T-Mobile Samsung Galaxy S6 Edge] Foye:
Hello All,

I recently purchased a TMobile S6 Edge Plus.

I downloaded ODIN and flashed the 928T kernel located here:

https://xdaforums.com/s6-edge-plus/...-edge-plus-t3194607/post62744199#post62744199

ODIN stated that the flash "passed" and the phone started to reboot. Next thing I know 10 minutes later, it's stuck on the black "S6 edge plus" screen with "kernel is not seandroid enforcing" across the top. Now I cannot turn the phone off or even reboot. I'm pretty new to rooting so Im not sure what I did wrong. The phone is just stuck on the black screen. I have no idea how to fix this.

Can anybody please help me undo what I've done? I was following the root guide from here: https://theunlockr.com/2016/02/04/root-samsung-galaxy-s6-edge-plus/

Thanks,
[T-Mobile Samsung Galaxy S6 Edge] Foye:
So I held down power, down volume, and home button. Then once the phone went black. I quickly pressed the power, up volume, and home button. I'm now into the stock recovery it appears? Not sure what to do from here.... can anybody help me out. (I don't want to be stuck without a phone).
[T-Mobile Samsung Galaxy S6 Edge] Foye:
So got out of the frozen boot image. Flashed a "stock modified kernel" here: https://xdaforums.com/tmobile-galax...ernel-stock-modified-kernel-touchwiz-t3229557

I then flashed the the Darthstar ROM here: https://xdaforums.com/tmobile-galax...m-darthstalker-note5-version-2-aroma-t3217247

I've got the ROM working... but it doesn't appear the hack hotspot/unrestricted tethering is working. Could this be due to already reaching my hotspot limit this month? And needing to wait until next months data resets before the unlimited hack starts working?

Also my data speeds were ungodly slow, so I reset the APN back to factory/default and then changed the mobile network from LTE/3g/2g to "LTE only" and sure enough... my speeds went back to normal. Anybody have a clue why this happened? I'm just worried when I get out to a more desolate place... and if theres no LTE... I'll basically have no service...

Thank you to all who respond!
[Android Q&A, Help & Troubleshooting] TheLogicalGamer:
Hi all. I was looking for an app on my phone to change around a bit. Just to get the hang of Decompiling and recompiling apks for theming purposes.

So I decided on the LGDownloadsUi.apk & decided to change the text color. I decompiled the apk opened the colors.xml located in res/values and changed the color code to red. Recompiled the apk. I went to move the xml to the original zip. (as I have read is proper procedure) in this case because it's a system app. But the values folder is gone.

I tried moving all of the apk files from the recompiled apk to the original (leaving meta folder). Moved it over to linux to use kitchen to create a app/priv-app flashable. Built then flashed however the rom doesn't boot after flashing. Any ideas of what I'm doing wrong?

More info

Phone name/model: LG G3 d851

Android v: 6.0 MM

Running multirom tried flashing on secondary rom that booted just fine before flashing. Thanks in. Advance guys!:)
[Android Q&A, Help & Troubleshooting] TheLogicalGamer:
I discovered that you can edit those xml's build the apk, the copy android manifest.xml and meta folder into the build folder. Then rebuild the apk to avoid signature issues. Instead coping the edit xml's into the new apk.
[Android Apps and Games] tolara:
HELP android Os v2.3 + Whatsapp messenger 11 Dec 2016 "time is up" v2.16.324 is it possible to make unlimited time?
[Nexus 6P Q&A, Help & Troubleshooting] Decimation001:
This is incredibly ridiculous. Why is there a limit on how many messages I can send in a certain period of time? I would like to know if there is any way to remove it. I have searched relentlessly.

1. settings.db doesn't exist anymore and therefore cannot be changed to set a custom limit.

2. I'm rooted, have EX kernel and Pure Nexus 7.1.1 ROM. Neither support changing the limit natively.
[Nexus 6P Q&A, Help & Troubleshooting] jhs39:
The limit is probably set by your carrier. If that's the case you won't be able to change it in the ROM or phone build prop.
[Nexus 6P Q&A, Help & Troubleshooting] Decimation001:
Is it in the build prop? There wasn't a limit on a different phone.
[Nexus 6P Q&A, Help & Troubleshooting] jhs39:
The limit just started when you got the 6P? How long were you using the phone before the limit became an issue? Are you on stock or a custom ROM? Who is your phone carrier? Are you using a stock SMS Program or different one? Maybe someone will have an answer if you provide more information. What is the limit, by the way? Do you know? I know that the program Automate limits texts as a security precaution. Maybe a third party program is causing the issue. Have you tried booting into safe mode and seeing if the limit still exists?
[Nexus 6P Q&A, Help & Troubleshooting] Decimation001:
The limit is on my 6P running Resurrection Remix 7.1.1 on francoKernel. NOT on my other Note5 which is 6.0.1 stock kernel and ROM. Both are/were on T-Mobile. Both use Textra. Not sure what the limit is.
[Nexus 6P Q&A, Help & Troubleshooting] jhs39:
Maybe something went wrong when you installed your custom ROM or Kernel. I've never heard of a text message limit on the Nexus 6P. You get an error message when you try and send a text saying you have reached the limit and the text can't be sent? Or is it a size limit? Or a limit to the number of recipients you can send a message to? I've heard of limits on the latter two but not on total number of messages that can be sent. At least not in North America.
[Nexus 6P Q&A, Help & Troubleshooting] Decimation001:
The limit was both on Pure Nexus and RR. It limits how many messages I can send to anyone within a certain amount of time. I can still press "accept" to send but it's really annoying and spams me.
[Nexus 6P Q&A, Help & Troubleshooting] jhs39:
That kind of sounds like you might have malware/adware installed on your phone. You might want to download something like Malwarebytes and do a scan of your phone.
[Nexus 6P Q&A, Help & Troubleshooting] shaneaus:
The SMS limit is built into Android. Previous to N it was a setting that could be altered in the build.prop and an option to change it was baked into RR. With N the settings were moved into the framework (from what I could find it appears it the telephony section?) and the option to change the setting was not baked into the new ROMs.

I have made several posts requesting info on how to change this - but, no one has responded (either they don't know, don't care, or haven't seen my posts). I need this option for work so badly I'm willing to learn how to build my own ROM. But, not worth getting started if I don't know how to fix the one important thing I need changed.
[Nexus 6P Q&A, Help & Troubleshooting] jhs39:
If the limit is built into Android why is nobody else having the same problem as you? Do you do something with your SMS that the average user doesnt't? Are you using your SMS to send advertising to large numbers of people, for instance?
[Nexus 6P Q&A, Help & Troubleshooting] shaneaus:
I don't understand why you are even asking this... I appreciate you willingness to help out. But... If you can't help out - just don't respond. You have exhibited that you don't have any knowledge of the settings we are speaking of - AND, I explained the setting is now in the framework. So, unless you know of a way to modify the framework without building a custom ROM - then, please stop implying that we don't have an issue - just because you don't understand what the issue is...

Your first response "The limit is probably set by your carrier" was uneducated speculation.

Your second response included several questions the OP had answered in his original post - he stated he had researched the issue, was using a custom rom/kernel... Then, you followed that up by more speculation: "Maybe a third party program is causing the issue. ."

Your third response isn't helpful as you merely question the OP's knowledge that he even knows he has an issue: "I've never heard of a text message limit on the Nexus 6P." Basically, you just admit your ignorance of there being an issue: " I've heard of limits on the latter two but not on total number of messages that can be sent." Which would imply to most that you won't have any knowledge of how to fix said issue.

Your forth response is to suggest there is malware? Again implying that the OP has no idea about what they are speaking.

Finally, when I post and explain that the setting was once there and easily modified with a build.prop change and that the code was moved...

You again imply that we have some sort of 'phantom issue:' "why is nobody else having the same problem as you?"

If you don't know the answer why waste our time? Do a search and you could easily find another post or two here on XDA in which I explained my situation/problem...

Once again, if you can help - we will surely appreciate any assistance! But, if you don't KNOW how to help; please, don't continue to ask questions which suggest we don't know what we are talking about.

[MENTION=7546851]Decimation001[/MENTION] - I did some research and inside the framework there are two sections related to "telephony" (which is where it appears the settings were moved). Seems they are ODEX files. Might be able to de-compile, make a correction, re-compile, replace in current ROM. I'll start looking into it over the next week or so.
[Nexus 6P Q&A, Help & Troubleshooting] jhs39:
I guess you can keep talking to yourself then.
[Nexus 6P Q&A, Help & Troubleshooting] hanschke:
I have got the same problem. I want to sent to silvester round about 140 SMS to my people and got the message because of the limit.
[Nexus 6P Q&A, Help & Troubleshooting] Decimation001:
Can you give me the names of the files? I know how to compile and recompile so I'd be happy to try and make some modifications.
[Nexus 6P Q&A, Help & Troubleshooting] shaneaus:
No need to get your feelings hurt. But, I'm not here to "just talk to people" or socialize. I'm here to attempt to solve an issue. If you can assist - then, I will be very grateful for any assistance!

[MENTION=7546851]Decimation001[/MENTION]:

Here is the old build.prop method (posted from a member on another Android forum:

"Note: If you move to Marshmallow this will not work anymore as the file "settings.db" is irrelevant under Android 6.0 (annoying but true)

You need:

Root

something like Root explorer and sqLite editor

Open this file: /data/data/com.android.providers.settings/databases/settings.db

Go to "global" subsection, then look for the following two entries

"sms_outgoing_check_max_count" and "sms_outgoing_check_interval_ms"

If they don't exist (by default they aren't there) then create them.

Set the first one to whatever you want (its the maximum number of texts you can send per timeframe (eg.1000)

Set the second one to whatever timeframe you are measuring in millisecond units (eg. 1800000)

My settings were

sms_outgoing_check_max_count 1000

sms_outgoing_check_interval_ms 1800000

This example limits my texts to 1000 messages every 30 minutes

Close file, making sure to save saving if requested to do so.

Reboot system. The new settings will override the Android internal ones.

Hacked "

However, I sent him a PM and he does not know how to make the change in the newer versions of Android. From research I did it appeared that Android moved this setting into the Framework under "Telephony" and you can see that in the structure here:

https://www.researchgate.net/figure...-Android-Telephony-system-architecture-from-6

I've been trying to look for the merge/change in the files here:

https://android.googlesource.com/platform/frameworks/opt/telephony/

I haven't found the specific change/code yet.

However, if you use Root Explorer in an installed ROM - you might find the relevant code by unpacking/searching here:

/system/framework/telephony-common.jar/classes.dex

/system/framework/telephony-ext.jar/classes.dex

I'll try to keep looking for the change in the source code - should have occurred during the transition from Android 5.0 to 6.0....
[Nexus 6P Q&A, Help & Troubleshooting] Decimation001:
I found the files. It's SmsUsageMonitor.class in telephony-common.jar. It has the values:

this.mLimit.set(Settings.Global.getInt(this.mContext.getContentResolver(), "sms_outgoing_check_max_count", 30));
this.mPeriod.set(Settings.Global.getInt(this.mContext.getContentResolver(), "sms_outgoing_check_interval_ms", 60000));

Now the problem is recompiling and making it a jar again.
[Nexus 6P Q&A, Help & Troubleshooting] Hungry hustler:
[MENTION=711322]shaneaus[/MENTION] Dang dude, chill out...
[Nexus 6P Q&A, Help & Troubleshooting] shaneaus:
I am very "chill." Don't understand why you made the comment.

[MENTION=7546851]Decimation001[/MENTION] That is awesome! It took me quite awhile to hunt down different forum threads to find out where the settings had been moved. I was all prepared to attempt to start learning how to compile/decompile those files! But, between working 70 hrs/wk, spending one night with my kids, one night with my girlfriend, and monitoring my home which is under construction - I just haven't had the time! My partner who shares responsibility for sending out the texts for the contract work we schedule is anxiously waiting on my finding a solution! I'm hoping you can re-compile the file!

I'm just concerned at this point that this would have to be done every single time a new version of a ROM is used... Wondering if it could be made into a flashable .zip file which would only change that line of code changing the 30 to 200 or 300....

In any case - is this something we could just extract the classes.dex file, use apktool to decompile, change "30" to "300", recompile, and push the altered .dex file back into place? I understand using "tools" isn't the best way to go - but, I won't have much time to devote to this for the next 4-6 months. So, if apktool will do the trick for now... I'm willing.
[Nexus 6P Q&A, Help & Troubleshooting] shaneaus:
Ok, I figured out how to decompile the "classes.dex" file using baksmali. However, I can't find the Telephony-common.jar file.

I have found similar code here: out/com/Android/internal/telephony/SmsUsageMonitor$SettingsObserver.smali

".line 248

const-string/jumbo v2, "sms_outgoing_check_max_count"

const/16 v3, 0x1e"

Also, in this file: SmsUsageMonitor$SettingsObserverHandler.smali

" .line 263

const-string/jumbo v1, "sms_outgoing_check_max_count""

But, I don't know how to modify it as it isn't in the format I'm accustomed to seeing... From what I read it is in a smali syntax and I don't know how to modify this code.

[MENTION=7546851]Decimation001[/MENTION] - any ideas?

---------- Post added at 02:54 AM ---------- Previous post was at 02:17 AM ----------

Ok... Looks like if I change the hexadecimal "0x1e" (means 30) below to "0x12c" (means 300), save, recompile using baksmali, and re-insert into my ROM it should work?:

out/com/Android/internal/telephony/SmsUsageMonitor$SettingsObserver.smali

".line 248

const-string/jumbo v2, "sms_outgoing_check_max_count"

const/16 v3, 0x1e"