Related
i have a month old galaxy s i9003 sl running the latest froyo build, i rooted it using one click root, for the past few days my phone would sometimes just freeze up when i try to do something, i have installed loads of apps 144 to be precise, most are on the sd card, is that a problem? one thing i have observed is when i switch on wi-fi and the immediately try accessing an app the phone freezes up, although this isnt the only time that happens.
please advice
Whenever you post anything related to ROM, it is a good practice to mention which version of android you are using including firmware PDA version. As of now many ppl are facing freezing issues on I9003, due to initial unfinished FW versions, but some ppl did not face these problem eventhough the same version of ROM they are using. It could be a single apk file which may be incompatible and responsible for freezing your phone. Try to take logcat using ADB, if the freezing is frequent or if the pattern is known or try upgrading the FW to a different region like XXKB3 (though I dont know where you are from). Some ppl have reported SOD on XXKB3 also but some did not face it, so try your luck.
Well i have the xxkb3 build on my phone, can you please elaborate about how do i go about using the logcat?
thanks
For logcat use adb
open CMD (command prompt) Hope you know that. change directory to the adb tools folder
eg: cd E:/ and_sdk/ adb tools
Now type adb shell
You will see this "$"
type su, the sign will change to "#" after providing root permission from Phone.
now type logcat, wait for some time observe the activities that are flashing on cmd screen, these are the processes running in the background of phone firmware. Now perform the task or sequence of activities that freezes the phone and check the logcat. This will tell you exactly which process is causing problem.
woozydevotee said:
Well i have the xxkb3 build on my phone, can you please elaborate about how do i go about using the logcat?
thanks
Click to expand...
Click to collapse
Because a problem with an app and supersu right after entering the Sim pin, I'd need to post a logcat dump, but honestly I never did it.
How can I do that?
Does logcat contains private information like imei, tel numbers contact and so on?
zooster said:
Because a problem with an app and supersu right after entering the Sim pin, I'd need to post a logcat dump, but honestly I never did it.
How can I do that?
Does logcat contains private information like imei, tel numbers contact and so on?
Click to expand...
Click to collapse
Logcat doesnt give any private information away and it is done via the adb command:
adb logcat > log.txt
This will save the logcat to log.txt file. Or there is a tool in the Sensation Themes and Apps section that gets logcats easyily - search for it
zooster said:
Because a problem with an app and supersu right after entering the Sim pin, I'd need to post a logcat dump, but honestly I never did it.
How can I do that?
Does logcat contains private information like imei, tel numbers contact and so on?
Click to expand...
Click to collapse
i found it for you man http://forum.xda-developers.com/showthread.php?t=1838323
But it's always needed a computer... Isn't there a way to save it directly on the phone?
zooster said:
But it's always needed a computer... Isn't there a way to save it directly on the phone?
Click to expand...
Click to collapse
Download alogcat from Play Store
zooster said:
But it's always needed a computer... Isn't there a way to save it directly on the phone?
Click to expand...
Click to collapse
You could run "logcat > log.txt" (ignoring the quotes) from a terminal on the phone.
Make sure you go to a sensible directory first so you know where it's been saved. I'd suggest "cd /sdcard".
Many off us here are using custom roms and are spamming the developer thread by posting our issues without attaching a logcat
simply like
my bluetooth is not starting
my hdmi is not working
Etc bla bla...
by posting lamely, U r not helping the developer u r just spamming his thread
to really get help, make sure u have a logcat of your problem
What is logcat?
Logcat is the command to view the internal logs of the Android system. Viewing logs is often the best way to diagnose a problem, and is required for many issues. This way you'll find out what apps are doing in the background without you noticing.
Advantages of Logcat
Debugging
You can see what processes are running, if a process is running after a certain interval of time, it will eat battery. So you can also find out what is draining your battery.
What developers need is a logcat To know what is the issue
i will tell u how to make it on a phone itself
1) download an app called ALOGCAT
2) install app and open
3) u will find random text coming there (its not random literally )
leave it in background by pressing homekey
4) this step is specific
for eg. if are having trouble in switching on wifi , try to swtich it on or do fiddle wid anything u have .. just play around with your cell, run the app u think is buggy or whatever
once done
5) press home button for long, select alogcat app,
6) click on options hardware button (right one ) and click on save.
logcat will be saved to sdcard/alogcat folder in the form of txt files.
7) now either u can directly upload the logcat.txt while telling about your problem
or
u can copy the contents of that txt file and paste on www.pastebin.com
after pasting u will get a link something like pastebin.com/******
just copy link and paste along wid ur problem
8) now next time u have a problem make sure u attach a logcat along with it
this method is not useful if u r not able to boot the phone
for that u need to have a pc and android sdk installed along with the drivers
if u have everything installed then
Open the 'run' dialog by pressing the 'Windows' + 'r' buttons on your keyboard (minimize the browser & other non-windows programs)
cmd (this will open a DOS prompt)
cd c:\Android\tools (go to the directory where you extracted the SDK)
adb shell
Now you'll see just a '$'
logcat
You can now just press the power button on your phone to see what happens. It displays everything the device is doing.
This is my first post regarding logcat , so i m sorry for any discrepancy (if there, notify me plz)
P.S - logcat is also useful in case if u r having some trouble wid stock roms
thanks @El_Dark for extending the op.
When you guys are experimenting on a custom rom (i.e. nightlies, betas, RC's, "just cooked", etc.), it's very likely that your phone might not boot correctly, fear not and instead, try using ADB there are loads of guides regarding how to properly set-up your PC for using ADB, starting by the Android SDK's page itself lol
Now, to do the said logcat, open a command window and do:
C:\Users\Dark> cd \<Name of your Android SDK folder>\sdk\platform-tools [Hit ENTER!]
C:\<Android-SDK folder>\sdk\plarform-tools> adb.exe devices (just to make sure your computer detected your phone lol)
C:\<Android-SDK folder>\sdk\plarform-tools> adb.exe logcat -v long > somefile.txt (the "-v long" part creates a nicely formatted file )
That's it!! Remember to zip the file if it's too big
Another tip: Some phones are very catchy when under heavy issues (like mine ) in those cases, timing is essential between rebooting and getting your log, however!!! The adb logcat command makes sure to wait for the device to get detected
Thank you, Now problems will be solved easily.
__________________
Sweet Devil >_<
GT-P3100
Android 4.0.4 ICS
Sun Cellular
"LG should go bankrupt"
GApps+ | Not your typical Gapps.zip
Very good to know. Thanks!
Sent from my SGH-i777
Nice tks!
Thanks for the tips, I use app called CatLog. Works good.
Sent from my Nexus 10 using Tapatalk HD
Thank u very much for ur thread
Sent from my Micromax A50 using xda app-developers app
doctor_droid said:
Many off us here are using custom roms and are spamming the developer thread by posting our issues without attaching a logcat
simply like
my bluetooth is not starting
my hdmi is not working
Etc bla bla...
..............................
...............................
Click to expand...
Click to collapse
Thanks. This is very useful...
Thanks for the post. :good:
A little .20 more to this When you guys are experimenting on a custom rom (i.e. nightlies, betas, RC's, "just cooked", etc.), it's very likely that your phone might not boot correctly, fear not and instead, try using ADB there are loads of guides regarding how to properly set-up your PC for using ADB, starting by the Android SDK's page itself lol
Now, to do the said logcat, open a command window and do:
C:\Users\Dark> cd \<Name of your Android SDK folder>\sdk\platform-tools [Hit ENTER!]
C:\<Android-SDK folder>\sdk\plarform-tools> adb.exe devices (just to make sure your computer detected your phone lol)
C:\<Android-SDK folder>\sdk\plarform-tools> adb.exe logcat -v long > somefile.txt (the "-v long" part creates a nicely formatted file )
That's it!! Remember to zip the file if it's too big
Another tip: Some phones are very catchy when under heavy issues (like mine ) in those cases, timing is essential between rebooting and getting your log, however!!! The adb logcat command makes sure to wait for the device to get detected
HTH!!
El_Dark said:
A little .20 more to this When you guys are experimenting on a custom rom (i.e. nightlies, betas, RC's, "just cooked", etc.), it's very likely that your phone might not boot correctly, fear not and instead, try using ADB there are loads of guides regarding how to properly set-up your PC for using ADB, starting by the Android SDK's page itself lol
Now, to do the said logcat, open a command window and do:
C:\Users\Dark> cd \<Name of your Android SDK folder>\sdk\platform-tools [Hit ENTER!]
C:\<Android-SDK folder>\sdk\plarform-tools> adb.exe devices (just to make sure your computer detected your phone lol)
C:\<Android-SDK folder>\sdk\plarform-tools> adb.exe logcat -v long > somefile.txt (the "-v long" part creates a nicely formatted file )
That's it!! Remember to zip the file if it's too big
Another tip: Some phones are very catchy when under heavy issues (like mine ) in those cases, timing is essential between rebooting and getting your log, however!!! The adb logcat command makes sure to wait for the device to get detected
HTH!!
Click to expand...
Click to collapse
i will add this to op if u permit ..
doctor_droid said:
i will add this to op if u permit ..
Click to expand...
Click to collapse
Of course!! That's the idea
Thank you! Very useful to know.
Hi!
Is there a root available or in the works for the dual-screen NEC Medias W N-05E?
The question has been asked (no answer so far) at the end of a thread under the N-05D but that's a quite different model.
I'd like to create a separate thread for this model to give it more visibility. Hope that's ok!
Thanks in advance!
bohemianRhapsody said:
Hi!
Is there a root available or in the works for the dual-screen NEC Medias W N-05E?
The question has been asked (no answer so far) at the end of a thread under the N-05D but that's a quite different model.
I'd like to create a separate thread for this model to give it more visibility. Hope that's ok!
Thanks in advance!
Click to expand...
Click to collapse
OK! I've made some progress on this: the japanese blogger "dupondroid" appears to say that run_root_shell (hosted at github)
successfully gives temp root. At least, that's my necessarily blurry understanding via google translate. Would any japanese readers here be able to post a better translation?
And a thread at r-2ch dot com links to the github commit in run_root_shell which made that possible: it's commit ID 811be8639aed64c158798a72a1d520a4d21e8b8b "Support N-05E"
Code:
+ { "N-05E", "A1000311", 0xc0094430, 0xc0093ebc }
So it definitely seems temp root is possible.
Sorry for the lack of links but I'm a new user so can't add them for now.
root is easy
bohemianRhapsody said:
OK! I've made some progress on this: the japanese blogger "dupondroid" appears to say that run_root_shell (hosted at github)
successfully gives temp root. At least, that's my necessarily blurry understanding via google translate. Would any japanese readers here be able to post a better translation?
And a thread at r-2ch dot com links to the github commit in run_root_shell which made that possible: it's commit ID 811be8639aed64c158798a72a1d520a4d21e8b8b "Support N-05E"
Code:
+ { "N-05E", "A1000311", 0xc0094430, 0xc0093ebc }
So it definitely seems temp root is possible.
Sorry for the lack of links but I'm a new user so can't add them for now.
Click to expand...
Click to collapse
root is easy via a tool called impactor.
however it's only temporary, I couldn't get /system mounted for rw. so I made a new recovery image to push.
that didn't work either, although I cannot write to recovery there is no error. recoverybkp was successful.
Also I found that the code to enter in recovery mode is based on your imei.
If I remember correctly digit 2,12,13,14 of your imei.
So possible attack vectors are:
1) kernel module to unlock partitions
2) figure out how update.dat files are constructed.
3) write to recovery partition
it0 said:
root is easy via a tool called impactor.
however it's only temporary, I couldn't get /system mounted for rw. so I made a new recovery image to push.
that didn't work either, although I cannot write to recovery there is no error. recoverybkp was successful.
Also I found that the code to enter in recovery mode is based on your imei.
If I remember correctly digit 2,12,13,14 of your imei.
So possible attack vectors are:
1) kernel module to unlock partitions
2) figure out how update.dat files are constructed.
3) write to recovery partition
Click to expand...
Click to collapse
I can't seem to get anything to work i'v tried Impactor did not work just gave me errors also tried run_root_shell but had to have some device.db file with I didn't really figured out, could some one please help?
Lukas_a_1996 said:
I can't seem to get anything to work i'v tried Impactor did not work just gave me errors also tried run_root_shell but had to have some device.db file with I didn't really figured out, could some one please help?
Click to expand...
Click to collapse
I used impactor 0.9.14, you just hook up the phone using microusb and put the phone in usb debugging mode under development options. then selecct "# start telnetd as root on port 22" from the pulldown and click start.
Then using a tool like putty ,telnet to your phone on port 22 (make sure it's connected to you wifi network when you do).
What android version are you running ? 4.1.2 is vulnarable for this attack.
it0 said:
I used impactor 0.9.14, you just hook up the phone using microusb and put the phone in usb debugging mode under development options. then selecct "# start telnetd as root on port 22" from the pulldown and click start.
Then using a tool like putty ,telnet to your phone on port 22 (make sure it's connected to you wifi network when you do).
What android version are you running ? 4.1.2 is vulnarable for this attack.
Click to expand...
Click to collapse
Thanks for the reply . I tried to run the command in impactor but whatever i do i get "Signature bugs unavailable" could it be that i have the wrong ADB drivers installed or is my Impactor setup wrong?
Edit: yeah im running 4.1.2 Build A1001231
You could try if you can just get an adb connection working.
with commands like
adb devices
adb shell
If that works then the rest should work as well.
it0 said:
You could try if you can just get an adb connection working.
with commands like
adb devices
adb shell
If that works then the rest should work as well.
Click to expand...
Click to collapse
All the adb commands basically work but nothing works with impactor i just get error
it0 said:
You could try if you can just get an adb connection working.
with commands like
adb devices
adb shell
If that works then the rest should work as well.
Click to expand...
Click to collapse
Bump!
How to Root Medias N05e
Dear All Pro
Does anyone show me how to root N05e? because there is very few information about that. I want to Swapfile to increase Ram size but it required N05e must be rooted.
So if anyone have any information about N05e, please share. Thanks
nguyenbuulam said:
Dear All Pro
Does anyone show me how to root N05e? because there is very few information about that. I want to Swapfile to increase Ram size but it required N05e must be rooted.
So if anyone have any information about N05e, please share. Thanks
Click to expand...
Click to collapse
There is a way for temp root N05E, basically u can use pm disable command or other su stuff. But u cannot mount system rw right now.
Some news about rooting
If someone in doubt, temp root is 100% working with run_root_shell https://github.com/android-rooting-tools/android_run_root_shell
With this I was able to copy full system, boot and recovery image. But I can't push new boot or recovery.
More than that, almost all fuctions in standard recovery mode (available through "reboot recovery" in root shell) are protected with some code. And it's not 2,11,12,13 numbers of IMEI.
Anyone know where to get this code? Or how to write new boot, recovery image? If we do so, we can get permanent root access =)
Maybe someone have Japanese friends? Search all English web, but maybe in Japan web there are some info.
P.S. with Impactor you only can start talnetd from root, becouse Impactor can't remount /system in rw mode and ro.kernel.qemu=1 option is not working
How to enter recovery mode?
Despite starting this thread, in the end I never did bother to attempt rooting.
Anyway, unfortunately now the phone refuses to boot. Not triggered by anything obvious, haven't installed any new software recently, etc. Just hung one day and then when I removed and re-inserted the battery, it won't get any further than the "docomo" splash screen. I.e. the OS doesn't appear to be getting bootstrapped at all. The "docomo" splash screen appears and disappears then the phone sits there with both screens powered up but blank.
As it happens, I had ADB Debug enabled in the developer options at the time, so I've tried to see if I can adb shell into the device, but no luck. Not surprised as it's clearly not getting far enough into the boot for that to work.
Any other suggestions? From the way it happened I do suspect it might just be hardware failure....
Not even sure how I enter recovery mode -- what are the key combinations for this?
bohemianRhapsody said:
Despite starting this thread, in the end I never did bother to attempt rooting.
Any other suggestions? From the way it happened I do suspect it might just be hardware failure....
Not even sure how I enter recovery mode -- what are the key combinations for this?
Click to expand...
Click to collapse
In recovery mode, clear cache, etc..
To get there hold volume down and power at the same time,then you'll see the broken android then wait/ press vol down a couple of times to see the menu.
GRbit said:
Some news about rooting
If someone in doubt, temp root is 100% working with run_root_shell https://github.com/android-rooting-tools/android_run_root_shell
With this I was able to copy full system, boot and recovery image. But I can't push new boot or recovery.
More than that, almost all fuctions in standard recovery mode (available through "reboot recovery" in root shell) are protected with some code. And it's not 2,11,12,13 numbers of IMEI.
Anyone know where to get this code? Or how to write new boot, recovery image? If we do so, we can get permanent root access =)
Maybe someone have Japanese friends? Search all English web, but maybe in Japan web there are some info.
P.S. with Impactor you only can start talnetd from root, becouse Impactor can't remount /system in rw mode and ro.kernel.qemu=1 option is not working
Click to expand...
Click to collapse
did you ever figure out the recovery keys?
hamishhhhs said:
did you ever figure out the recovery keys?
Click to expand...
Click to collapse
No I didn't(
I'm actually sold this phone and lost interest in the topic.
GRbit said:
No I didn't(
I'm actually sold this phone and lost interest in the topic.
Click to expand...
Click to collapse
do you by chance still have the files you dumped?
Ive teamed with a friend in twitter to try and make a rom for this but I haven't gotten very far
hamishhhhs said:
do you by chance still have the files you dumped?
Ive teamed with a friend in twitter to try and make a rom for this but I haven't gotten very far
Click to expand...
Click to collapse
Sorry, but this was too long time ago. Nothing left
GRbit said:
Sorry, but this was too long time ago. Nothing left
Click to expand...
Click to collapse
how would j be able to get the files from my phone?
hamishhhhs said:
how would j be able to get the files from my phone?
Click to expand...
Click to collapse
I dunno man.
I've already described (in the first post you have quoted) what I achieved with this github repo https://github.com/android-rooting-tools/android_run_root_shell . That's all I've got.
Hi Everyone,
I'm using a Samsung GT-N7105. It has 16GB of internal memory. It has no external SD card.
A few days ago my phone's screen went black. Everything else works fine, including touch, just that the screen is always completely black.
I took it to a repair centre. After the repair centre ran some tests, (they kept my phone for 2 days,) they confirmed it was the LCD screen problem (i.e. a hardware issue). Since that LCD screen is expensive to repair, I chose not to repair it.
So now I want to install Android Screencast on my phone. I connect my phone to my desktop, and to my surprise I discover that USB debugging isn't enabled anymore!
So I call the repair centre and ask them what software changes they made to my phone. Their response is:
1) The partition table has definitely NOT been altered.
2) "Your Android version has not been upgraded."
3) "We used a special software to format your phone." They declined to tell me what software they used, and they don't seem to know which partitions have been "formatted"! But they did say that "format" was not the same as "factory reset".
(Btw the people at the repair centre are non-native English speakers, whereas my first language is English, so it was hard to ask about technical details.)
Therefore my best guess about the software state of my phone is:
1) It's running stock Android 4.1.2, which it's been running since the first day I bought it
2) The bootloader should have no KNOX nonsense
3) Recovery should be stock recovery
4) A few partitions have been "formatted" to unknown states
5) There are no longer any pattern, PIN, or password locks on my phone. If my phone is on and it's been sitting idle, I just have to tap the home button, then swipe the screen, and it unlocks.
I can reconstruct the partition table of my internal memory if you guys need it. I did an entire dump of mmcblk0 about two months ago.
(Btw the size of that dump of mmcblk0 is 15,758,000,128 bytes, which is significantly less than 16GB, even if you count by 1000s instead of 1024s. Unimportant side question, but does anyone know why?)
**************
My main question is: How do I enable USB debugging ON ANDROID with the black screen restriction?
I've searched the forums, and in thread 2395047 (can't post links yet) the recommendation is to flash CWM recovery to get adb access. But keep in mind that my ultimate goal is to be able to install Android Screencast on my phone, so that I can regain full phone functionality (with the help of an attached computer screen). I don't quite see how adb access via CWM recovery can help me to achieve this goal.
Also, I've never actually used CWM recovery before and don't know how it works. One of my concerns is: Once I have flashed CWM recovery, and after I boot into recovery, do I immediately get adb access just by hooking up to USB cable to the desktop? Or do I first have to select some setting, which would be tough to do with a black screen?
Thanks in advance for all your help!
Ernest
(Note to mods: I accidentally posted this question earlier to xda assist when I wasn't logged in. You can delete the earlier duplicate.)
Hello,
I've been dealing with android for a while and have been a member of XDA for a while. In my time here I've searched for a solution to this issue many times all over the web and XDA but never came up with anything useful.
Of the possible solutions I've found, the most likely possibility is to use an OTG cable and mouse to interface your device but this requires you to see the screen which is not an option for you. adb in this situation is only useful if you want to retrieve data from your device. I do remember finding something on the web that could potentially help you turn on USB debugging but I'm having trouble finding it now. I'll keep looking but can't promise anything. In the meantime, try posting your question in the forum linked below.
http://forum.xda-developers.com/galaxy-note-2/help
If that doesn't help you find answers then try posting your question in the forum linked below.
http://forum.xda-developers.com/android/help
I hope this helps, good luck.
Hi Droidriven!
Thank you so much for taking the time to read and reply to my question.
Guess what, with the help of workdowg, I managed to work out a solution! My saving grace is that I'm running Android 4.1.2 and not one of the newer versions. My understanding is that if I was running one of the newer versions of Android, then I wouldn't even be able to get adb access via CWM recovery, because of the extra security measures. (Although I might be wrong about this point; I am still noob.)
I solved my problem in the following way:
1) Flash CWM recovery via ODIN Download mode
2) Boot into recovery, connect phone to desktop computer, open a command line terminal
3) Type "adb shell" to get a root shell in CWM recovery
4) In that root shell, type all the commands in the last code box at the end of the following post:
http://forum.xda-developers.com/showpost.php?p=63829295&postcount=27
(Much thanks to workdowg for this step)
5) Type "exit 0" to exit the shell in CWM recovery, then type "adb reboot"
6) Wait for my phone to reboot to Android
7) Type "adb devices", and now I see that I have adb connection to Android
After this, I was also able to successfully run Android Screencast with my phone. I can see my screen again!
So now, everyone please help me think of some useful search tags for this post / thread.
ErnestChia said:
Hi Droidriven!
Thank you so much for taking the time to read and reply to my question.
Guess what, with the help of workdowg, I managed to work out a solution! My saving grace is that I'm running Android 4.1.2 and not one of the newer versions. My understanding is that if I was running one of the newer versions of Android, then I wouldn't even be able to get adb access via CWM recovery, because of the extra security measures. (Although I might be wrong about this point; I am still noob.)
I solved my problem in the following way:
1) Flash CWM recovery via ODIN Download mode
2) Boot into recovery, connect phone to desktop computer, open a command line terminal
3) Type "adb shell" to get a root shell in CWM recovery
4) In that root shell, type all the commands in the last code box at the end of the following post:
http://forum.xda-developers.com/showpost.php?p=63829295&postcount=27
(Much thanks to workdowg for this step)
5) Type "exit 0" to exit the shell in CWM recovery, then type "adb reboot"
6) Wait for my phone to reboot to Android
7) Type "adb devices", and now I see that I have adb connection to Android
After this, I was also able to successfully run Android Screencast with my phone. I can see my screen again!
So now, everyone please help me think of some useful search tags for this post / thread.
Click to expand...
Click to collapse
I'll have to remember that, I wasn't aware of the difference in 4.1.2, I've not had to deal with 4.1.2, that's good to know.
Glad you got it going, now see if you can find one of your devices on eBay that is no longer working in one or another but still has a good digitizer and glass, you may find one cheap, then you can use the digitizer+glass from the used one to fix the one you are using.
Sent from my SCH-I535 using Tapatalk
Droidriven said:
Glad you got it going, now see if you can find one of your devices on eBay that is no longer working in one or another but still has a good digitizer and glass, you may find one cheap, then you can use the digitizer+glass from the used one to fix the one you are using.
Click to expand...
Click to collapse
That's a really good idea, which I didn't even consider. (Maybe because I've never meddled with hardware before.)
Thanks!