« first day (1929 days earlier)      last day (3000 days later) » 

12:47 PM
Burn!
 
guys, how can i write an article regarding an issue and a solution that i found ?
 
@FlatSpeed is your goal actually to write an article, or is it actually a question you've already found the answer to?
if you want to write an article, maybe sign up on a blogging site
if you just have a question you happen to have already answered, there's nothing to stop you writing that here
(assuming the question is on-topic for this site, of course)
 
i wanted to write an article, ok, thanks, i thought they have an article area here also and i was missing it
cheers
 
@FlatSpeed nope, this is just a Q&A site for Android users
 
 
7 hours later…
7:33 PM
I just messed up my tablets when rooting I need some help please
I used odin to install a custom recovery screen
when I install superSu app, it asked me to update the binary, then I got stuck in a boot loop to custom recovery mode
 
7:56 PM
Does anyone know of a sample app (debuggable; not ready for deployment so that `run-as` can be used)? That app should have read and write SMS permissions and should be able to access SMS content provider (don't know whether it also needs permission).

I'm speculating that by using `run-as` on that app, I would be granted a shell with permission to read and write an SMS using content provider. All I need is some information to write. That content can be provided from the telephony database pulled from [this broken but rooted device](http://android.stackexchange.com/q/136569/96277). A bit of
 
@Firelord I don't know – but could you try to split your long chat messages into multiple pieces so one doesn't have to look them up elsewhere ("see full text" link)? ;) I've noticed that quite often recently, and in 90% it were yours ;)
 
@Izzy lol
sure
 
8:13 PM
0
Q: Boot loop on custom recovery mode

medaI just messed up my tablet when rooting I need some help please I used odin to install a custom recovery screen when I install superSu app, it asked me to update the binary, then I got stuck in a boot loop to custom recovery mode. I followed the steps from this guide: http://forum.xda-developer...

 
@meda You can boot into custom recovery, right?
 
yes I can @Firelord
its the custom reovery mode
 
Then do adb push from there.
 
CWM based recovery
 
Which recovery is it?
 
8:17 PM
v6.0.4.8
 
adb push and adb sideload. both should work.
 
C:\Users\Program\Downloads\fastboot>adb push UPDATE-SuperSU-v2.65-20151226141550.zip /sdcard/.
5900 KB/s (4254181 bytes in 0.704s)
thats the command
 
yes
 
however I check in my tablets and its not there
 
no
 
8:18 PM
no?
 
Hold on
 
not able to copy files
because device is not visible in recovery mode
so I search and found this
 
What does adb devices give?
 
I could see my device id and recovery next to it
 
@meda Error?
 
8:21 PM
no errors
C:\Users\Program\Downloads\fastboot>adb devices
List of devices attached
3004a22712fd8100        recovery
 
Then it is copied. Can you not see it from inside the recovery using the option Install Zip or equivalent of it?
 
no it is showing
after I rebooted
before I install it
is it the right file
UPDATE-SuperSU-v2.65-20151226141550.zip
?
I got it from here
@Firelord
 
@meda I prefer 2.49 but let's try with your version first. If it doesn't work we'll try Stable one.
 
ok
but your link pints to UPDATE-SuperSU-v1.94.zip
 
Ignore it for a while.
Focus on your version.
 
8:25 PM
I just did
it did not help
takes me back to custom recovery
 
Is USB-debugging enabled in Android OS?
 
yes it was but I did not plug USB
should I
 
Do this: when booted into recovery mode, find and remove all the files (they are not in dozens) flashed by supersu zip. // Any problem in considering factory reset?
 
I dont understand sorry
but I did try factory reset did not help either
you remove which files?
 
Give me a minute. Let me check which files to delete.
 
8:31 PM
ok
I appreciate your help
thanks
 
This is where it appears to remove old files when updating itself:

-----
ui_print "- Removing old files"

if [ -f "/system/bin/install-recovery.sh" ]; then
if [ ! -f "/system/bin/install-recovery_original.sh" ]; then
mv /system/bin/install-recovery.sh /system/bin/install-recovery_original.sh
ch_con /system/bin/install-recovery_original.sh
fi
fi
if [ -f "/system/etc/install-recovery.sh" ]; then
if [ ! -f "/system/etc/install-recovery_original.sh" ]; then
mv /system/etc/install-recovery.sh /system/etc/install-recovery_original.sh
 
@Firelord thanks, Im new to this
how do I run this script
 
On a second thought, this may work as well: in recovery mode, mount system and data partition, then execute:

adb shell
rm -rf /data/app/eu.chainfire.supersu*
rm -rf /data/data/eu.chainfire.supersu
rm -rf /system/bin/su
rm -rf /system/xbin/su
rm -rf system/xbin/daemonsu
rm -rf /system/bin/.ext/.su
 
ok I removed
adb shell
rm -rf /data/app/eu.chainfire.supersu*
rm -rf /data/data/eu.chainfire.supersu
rm -rf /system/bin/su
rm -rf /system/xbin/su
rm -rf system/xbin/daemonsu
rm -rf /system/bin/.ext/.su
whats next @Firelord
 
Unmount those partitions and reboot. If it still boot-loop, try a factory reset again.
It is not a boot-loop if the device ends up in recovery mode. What is the last think you notice in your current boot sequence before the device reboots and ends up in recovery mode?
@meda: not working, the device that is?
 
9:15 PM
@Firelord I tried rebooting
then factory reset then reboot again
still not working :-S
everything was fine until superSu app recommended to update the binary, when I pressed it im stuck in recovery mode
bootloop might not be the right term
is my device bricked? @Firelord
 
:27455270: no, you can flash the firmware and remain happy, and it seems that I'm out of ideas other than recommending firmware flashing.
 
at this point I just want it to boot, root or not
what do you suggesst
 
Flash the stock ROM.
Do a clean flash.
 
ok please tell me how, or refer me to a guide
 
I don't have any Samsung device and no experience with flashing them, but various blogs and websites should be dealing with them. I'm sure of it. You may refer to them. A simple query: "YOUR_DEVICE flash stock rom" should help.
:27453111: Will that be on-topic on SR?
 
9:26 PM
on topic on what?
I found this
Will try it now
 
Sure
@Izzy: Will this be on-topic on SR?
 
@Firelord You know a trusted source to download rom stock from
 
@meda This is considered trustworthy by many users: sammobile.com/devices
 
@Firelord I'd say so (but explain "sample app"). The answer then is probably "Tasker" :)
I mean: it should fit depending on what you mean by "sample app"
 
:27455698: it is not debuggable
 
9:34 PM
??
 
@Izzy I can't do run-as on tasker?
 
@Firelord Is the device rooted?
 
@Izzy no Sir
 
You can "run-as" root then :)
Oh.
 
:27455743: lol, but not an option here.
 
9:35 PM
OK, sorry – misinterpreted the "run-as" part ;)
So you want that app to use it – not to "explore its sources"?
 
This is strange. When I'm referring your comments, I'm seeing a number instead of your name and an icon.
@Izzy Yes.
Use it only for the purpose of run-as.
 
@Firelord Then I'd say go for it. I don't see why it shouldn't be on-topic on SR: you have a use-case, clear requirements, and looking for an app – right?
@Firelord I'd say that's a purpose :)
 
Thanks. Will do, but first I have to find if something already exists and comes across my path.
 
Brainstorming: Helium can utilize a local ADB server. Wouldn't that mean … ?
 
:27455812: run-as won't work on it.
 
9:39 PM
Hm? I thought adbd can do that?
 
 
2 hours later…
11:22 PM
The favicon that the main site uses, is it original and licensed? I see that this site uses the same favicon.
 
@Firelord I tried stock rom
not helping :(
I now regret attempting rooting
 

« first day (1929 days earlier)      last day (3000 days later) »