I know how annoying it is trying to set up ADB, open a terminal, export logs to local files, copy, paste, etc just to submit a bug report or help a developer diagnose an issue.
That is why I put together this little app to do all of that for you!
This app runs the following commands:
dmesg
logcat -v time -d
logcat -v time -b radio -d
getprop
uname -a
ps
It puts these together into a single document and uploads it to Pastebin, so you can just put a link in a forum thread or IRC or in the bug tracker.
To run these, sadly it needs root. It also requires permissions to read phone identity so that it can automatically mask your ESN/MDN/etc in the logs before it uploads them. It also requires permissions to read account information so that it can mask all of your accounts in the logcat.
EVEN WITH ALL OF THOSE THINGS BLOCKED AUTOMATICALLY PLEASE LOOK OVER YOUR LOG BEFORE GIVING OUT THE URL. IT IS A PRIVATE PASTEBIN AND IF YOU FIND SOMETHING PRIVATE YOU CAN REMOVE IT.
Usage:
Install the app on your phone.
Run the app.
Add any information that should be masked (keep in mind private phone ids and accounts will be masked automatically).
Hit PasteBin! and wait for the upload to finish.
Note the url at the bottom of the screen and give it to whoever requested your logs.
This is just a simple app to help get logs, but if you have any suggestion of how it might be better, do let me know by posting in this thread.
Known Issues:
If you add too many mask strings the app doesn't scroll so you lose the PasteBin! button and/or the resulting URL.
Google Code Project: http://code.google.com/p/getlogs/
Version History:
Version 1.2
Added filtering to "just a file" output
Limited dmesg and both logcats to only 1000 lines each to prevent OutOfMemory Exceptions.
Version 1.1
Added ability to just save the file, no upload. (/sdcard/Android/apps/com.GetLogs/data/)
App now remembers the last message, in case you forget to write down your pastebin address.
Added ps to the list of processes run.
Version 1.0
Initial Version
Upgrade Instructions:
Uninstall current version if installed.
Install new version.
good work, thanks button pushed
Ok so, update - application not installed error, yes I have unknown sources selected, just doesn't install. Any ideas?
Sent from my MSM using XDA App
VistroDistro said:
Ok so, update - application not installed error, yes I have unknown sources selected, just doesn't install. Any ideas?
Sent from my MSM using XDA App
Click to expand...
Click to collapse
Hm, I get the same thing, I've never published an android app before and I chose not to sign it, maybe I need to do that...
EDIT: Ok I signed it and it installs now, sorry about that.
worked like a charm : )
again, good work
Hi,
Is there any way for the file to be dumped on the phone instead of uploading it to pastebin. The user can then pick his way of displaying the file to the world.
This is awesome, gonna install it when I get home so I can get highlandsun some logs of radio failures that occur when I'm at my desk at work. (I never have time to get the logs from the terminal when working, and I can't ADB at work.)
New version in first post, see the Version History for the updates.
Awesome work!
Nice work rpierce99. This should help get us a flood of logs .
Awesome! Will have a try.
I'm running this but it's not giving me a url and I can't see to find the file that it's supposed to create.
Demonic240 said:
I'm running this but it's not giving me a url and I can't see to find the file that it's supposed to create.
Click to expand...
Click to collapse
If you hit the pastebin button the url gets spit out just below the button. If you want the file it is in /sdcard/Android/apps/com.GetLogs/data/
Deleted...
Demonic240 said:
I posted the data file in another thread but I don't think anyone was able to look at it. Here is the logs for my tilt2. The issue I'm running into is that wifi loses the data connection immediately when the phone goes to sleep. The wifi signal does not drop, and in fact still says I'm connected, so the only way to regain data is to turn off the wifi then back on. Would someone be able to look at these logs and help me out here?
Click to expand...
Click to collapse
Hrm...
No offense, but this really doesn't belong here. IIRC, you posted the logs in the FRX06 thread - which is good, but don't you remember me mentioning opening a bug on the tracker? Obviously if there's already a bug open, just add your comments/logs to it... if there isn't already a bug on it, open a new bug with your comments/logs .
Seriously, this has absolutely nothing to do with this thread.
arrrghhh said:
Hrm...
No offense, but this really doesn't belong here. IIRC, you posted the logs in the FRX06 thread - which is good, but don't you remember me mentioning opening a bug on the tracker? Obviously if there's already a bug open, just add your comments/logs to it... if there isn't already a bug on it, open a new bug with your comments/logs .
Seriously, this has absolutely nothing to do with this thread.
Click to expand...
Click to collapse
Ah, I'll remove it then. Sorry about that.
Better dmesg binary
In the interest of having more readable kernel logs...
Delete your current /bin/dmesg and put this one in there instead. Make sure you chmod it 755.
highlandsun said:
In the interest of having more readable kernel logs...
Delete your current /bin/dmesg and put this one in there instead. Make sure you chmod it 755.
Click to expand...
Click to collapse
At work without adb. Using terminal on Rhod.
What am I missing?
Code:
$ $ su
# mount -o remount,rw /
# rm /bin/dmesg
# cp /sdcard/dropbox/dmesg /bin
cp: write error: No space left on device
# ls -l /bin/dm*
-rwxrwxrwx 1 0 0 0 Jun 29 10:10 /bin/dmesg
It does remove dmesg, it does copy the new, but filesize=0
Your rootfs is full. You can install it in /system/bin or /system/xbin instead. There's already one in there too, which is a symlink to toolbox. You should delete the symlink first, of course.
@HYC: Oh yes, sweet. Thanks.
@rpierce99: "Just a file" gives me..... just a file ... and crashes. However, the file is good. Thanks.
Related
All you need to do is extract this and run the "runme.bat"
Code:
echo off
cls
echo *********************************
echo * Please plug the USB into Nook *
echo *********************************
pause
adb kill-server
adb devices
echo *******************
echo * Blocking Update *
echo *******************
adb shell mount -o remount,rw /dev/block/mmcblk0p5 /system
adb push block-1.1.sh /system/media
adb shell sh /system/media/block-1.1.sh
ping -n 5 127.0.0.1 >NUL
echo Success
adb reboot
adb kill-server
echo *****************************
echo * You nook is rebooting *
echo * Disconnect the USB cable! *
echo * Wait until rebooted... *
echo * *
echo * BN 1.1 Update Blocked *
echo * *
echo *****************************
pause
exit
Download
Can you release an "Undo" script as well that undoes what this does?
I was under the impression that the otacert rename was a dud and the build.prop was very questionable???
found this and replied to the discussion on the subject.
IMO, Until the OTA is squashed we are going to have a repetitive debockle of blowing up everyones rooted work and would think addressing this would be of significant value:
-cut-n-paste-
I was wondering what you folks thought of this 'prevent' 1.1 hack??
http://forum.xda-developers.com/showthread.php?t=930477
seems reasonable to me, adding:
127.0.0.1 csqaint.barnesandnoble.com
(looks to be the primary check for updates?)
and
127.0.0.1 bncs.barnesandnoble.com
(just for good measure but might have unwanted consequences?)
to /etc/hosts file
I would personally like to be able to put an end to this 'forced' OTA update behind us and be able to sideload any updates from bn manually at our convienence in the future.
how bout u??????
In reviewing the script it appears to apply the build.prop spoof update?
I thought this was questionalble in overall effectiveness?? and even if it worked would have to be reapplied after every update from bn???
I noticed an interesting reply from ixampl as follows:
What I did when the first scare of an update arose was:
a) Checked in /data/data/com.bn.nook.devicemanager/databases/ for an sql file
b) Pulled the sql file.
c) Dump its contents with sqlite3.
d) In it there's an entry for OTAs... with value "auto"
e) Changed that value to "manual"
f) Pushed the modified database file to the device.
I never got any OTA updates. Still on first OS version.
This is exactly what I'm lookin for, a permenant block unless of course the database update got reversed back to auto?????
is this normal? i go into settings/device info/about your nook color. it still shows 1.0.1? where do i have to go to verify this is blocked?
C:\NC - Auto Config Script 1.0.1>adb push block-1.1.sh /system/media
32 KB/s (506 bytes in 0.015s)
C:\NC - Auto Config Script 1.0.1>adb shell sh /system/media/block-1.1.sh
cp: not found
sed: not found
sed: not found
sed: not found
sed: not found
john10101 said:
is this normal? i go into settings/device info/about your nook color. it still shows 1.0.1? where do i have to go to verify this is blocked?
C:\NC - Auto Config Script 1.0.1>adb push block-1.1.sh /system/media
32 KB/s (506 bytes in 0.015s)
C:\NC - Auto Config Script 1.0.1>adb shell sh /system/media/block-1.1.sh
cp: not found
sed: not found
sed: not found
sed: not found
sed: not found
Click to expand...
Click to collapse
You dont have busybox installed on the NC?
bonzer2u said:
In reviewing the script it appears to apply the build.prop spoof update?
I thought this was questionalble in overall effectiveness?? and even if it worked would have to be reapplied after every update from bn???
I noticed an interesting reply from ixampl as follows:
What I did when the first scare of an update arose was:
a) Checked in /data/data/com.bn.nook.devicemanager/databases/ for an sql file
b) Pulled the sql file.
c) Dump its contents with sqlite3.
d) In it there's an entry for OTAs... with value "auto"
e) Changed that value to "manual"
f) Pushed the modified database file to the device.
I never got any OTA updates. Still on first OS version.
This is exactly what I'm lookin for, a permenant block unless of course the database update got reversed back to auto?????
Click to expand...
Click to collapse
Can you elaborate a little further on what commands you used so I might be able to add it into a script.
i dont think so... what installs busybox?
No offense, but this isn't a worry any more anyway. We already have a CWM flashable update.zip that updates you to 1.1, but does not harm your root or installed aps. Why are people bothering with all this "blocking" nonsense?
From this thread:
http://forum.xda-developers.com/showthread.php?t=874871
Attached is a working sqlite3 binary. Copy it to /system/bin and you will be able to edit sqlite databases on the nook itself.
--------------------------------------------------------------------------------
Attached Files sqlite3.7z (11.9 KB, 56 views)
-----------------------------------------------------------------------------
And I found a sqlite3 sample that will need to be edited like somthing as follows:
In your terminal,
$ adb pull /data/data/com.bn.nook.devicemanager/databases/settings.db settings.db
$ sqlite3 settings.db
sqlite> update secure set value='manual' where name='an entry for OTAs???-Dont know the parameter here'
;
sqlite> .q
$ adb push /data/data/com.bn.nook.devicemanager/databases/settings.db settings.db
$ adb reboot
Hope this helps, I dont know the input name for placeholder.
xboxexpert said:
You dont have busybox installed on the NC?
Click to expand...
Click to collapse
Ok i installed busy box off the market, and ran the script!!! success. when i rebooted it told me that 1.1.0 has been installed. and it now shows 1.1.0 in the about.
i suggest noting busy box in the original post.
Divine_Madcat said:
No offense, but this isn't a worry any more anyway. We already have a CWM flashable update.zip that updates you to 1.1, but does not harm your root or installed aps. Why are people bothering with all this "blocking" nonsense?
Click to expand...
Click to collapse
not everyone wants to upgrade to 1.1, or has cwm installed.
john10101 said:
Ok i installed busy box off the market, and ran the script!!! success. when i rebooted it told me that 1.1.0 has been installed. and it now shows 1.1.0 in the about.
i suggest noting busy box in the original post.
Click to expand...
Click to collapse
It says 1.1 is installed but its really not. (Spoofed it)
john10101 said:
not everyone wants to upgrade to 1.1, or has cwm installed.
Click to expand...
Click to collapse
Uh... why? What is there about 1.1 not to want? And if you are ok with doing all of this to block an update, there is no reason not to have CWM (which is quite stable). Sorry, but this really is all just wasted effort..
Divine_Madcat said:
Uh... why? What is there about 1.1 not to want? And if you are ok with doing all of this to block an update, there is no reason not to have CWM (which is quite stable). Sorry, but this really is all just wasted effort..
Click to expand...
Click to collapse
Took me 2 seconds to throw together...took longer to upload then anything. Its just for people who want it. If you dont want it I dont want you to have it :/
xboxexpert said:
Took me 2 seconds to throw together...took longer to upload then anything. Its just for people who want it. If you dont want it I dont want you to have it :/
Click to expand...
Click to collapse
Don't get me wrong, im not knocking your work, just people's reasoning for wanting it done in the first place. I understand before the update.zip was developed, since it would break root and mess up your apps. But now, there is no reason not to take the update; thus the continued demand for this is puzzling.
If you really want the OTA update to stop, take a look at the updater-script inside the sideload_update.zip file from B&N. The first two lines read:
Code:
assert(getprop("ro.product.device") == "zoom2" ||
getprop("ro.build.product") == "zoom2");
I think those are set in the build.prop file. Change either ro.build.product or ro.product.device to something other than zoom2 (say zoom2a), and the rest of the script won't continue. This is what people are seeing when the file gets downloaded OTA and then disappears without being applied. If for some reason you must avoid it, make that change and you will stop the update cold. Not sure what the side effects of making the change are, but there would be an easy way to revert by undoing the edits, if you need to.
Wasn't this already available from another forum member?
http://forum.xda-developers.com/showthread.php?t=930382
Seems a lot easier to just copy and replace build.prop with a filemanager.
Divine_Madcat said:
Uh... why? What is there about 1.1 not to want? And if you are ok with doing all of this to block an update, there is no reason not to have CWM (which is quite stable). Sorry, but this really is all just wasted effort..
Click to expand...
Click to collapse
Yah go ahead and read thru the cwm thread and try to convince anyone in this forum that it is 100% stable. Not to suggest that anyones efforts are not welcome and appreciated but if you asked the actual devs involved I would bet they would not suggest so as well.
I for one have rooted twice (1.0 and 1.0.1) with autoroot and am 100% stable, never had a crash or the pleasure to have to restore/rebuild, not interested in the stock browser or anything else bn has to offer, quite happy and perhaps lucky with the way its workin now. I also dont appreciate being strong armed an update without a confirmation, hell even microbuddies doesnt have that kinda gawl.
I guess it will take one of the next of many 'future forced' updates from bn that bothches all the work that you have put into your NC and for whatever reason your recovery doesnt work and you are forced to rebuild from scratch before you realize that if you had a permenant block in place, you could have the time for outstanding efforts of the local devs to stabilize an upgrade path before you pulled the trigger?
The database hack appears to be best way to permanently kill OTA, no need for future updated spoof build.prop scripts (before you get hit) and no worries about being updated and possibly blown up while your sleepin and bn pushes an update out before you get the news.
or maybe its just me..........
Exactly! If you are not diligently checking the forum everyday, you wouldn't know BN is pushing out 1.1 update and you wouldn't know there is a pre-nootered 1.1 version available. BN will update you OTA before you know any better and screw up your rooted setup. Hence the need for a permanent update block.
I'm posting this here for visibility for Fascinate users and ROM developers. In the following thread you can find all the information, as well as how to download and apply the patch files:
http://forum.xda-developers.com/showthread.php?t=977154
I'm sure it will be incorporated into the major ROM's soon. However, if you install apps from unverified sources, or regularly try out new apps from the market, you shouldn't wait.
Patching via CWM:
imnuts said:
Here are two zips if people want them and don't feel like going to another thread/page/topic/whatever.
DroidDreamMalwarePatch_pre-edify.zip
DroidDreamMalwarePatch_edify.zip
Click to expand...
Click to collapse
Patching via ADB or terminal emulator:
Alternatively, probably the quickest way (and if you copy and paste, the most fool-proof) if you are rooted and know how to use ADB, is to open up a command prompt or a terminal emulator on the phone to access the adb shell. If on a PC, type:
Code:
adb shell su
Then type the following lines, omitting the $ and # (if you are on a terminal emulator, start here):
Code:
$ su
# mount -o rw,remount /dev/block/stl9 /system
# touch /system/bin/profile
# chmod 444 /system/bin/profile
You are now protected from the current iteration of DroidDream Malware. Consider installing a security program like LookOut to protect against future vulnerabilities.
Original Post:
Rodderik said:
[Patch][Rom]Malware Exploit for all pre-Gingerbread phones
Who is affected? All phones pre-gingerbread
Who should act? Users and developers using pre-gingerbread roms
How do I fix? Flash attached .zip at the bottom of this post or use one of the alternate methods down there
What if I think I was infected? Completely wipe your device, format sdard, go back to stock and re-apply rom, then flash the attached .zip (before installing any apps)
Why should I care? read below...
http://www.androidpolice.com/2011/0...your-phone-steal-your-data-and-open-backdoor/
Link to publishers apps here. I just randomly stumbled into one of the apps, recognized it and noticed that the publisher wasn’t who it was supposed to be.
Super Guitar Solo for example is originally Guitar Solo Lite. I downloaded two of the apps and extracted the APK’s, they both contain what seems to be the "rageagainstthecage" root exploit – binary contains string "CVE-2010-EASY Android local root exploit (C) 2010 by 743C". Don’t know what the apps actually do, but can’t be good.
I appreciate being able to publish an update to an app and the update going live instantly, but this is a bit scary. Some sort of moderation, or at least quicker reaction to malware complaints would be nice.
EDIT: After some dexing and jaxing, the apps seem to be at least posting the IMEI and IMSI codes to http://184.105.245.17:8080/GMServer/GMServlet, which seems to be located in Fremont, CA.
I asked our resident hacker to take a look at the code himself, and he’s verified it does indeed root the user’s device via rageagainstthecage or exploid. But that’s just the tip of the iceberg: it does more than just yank IMEI and IMSI. There’s another APK hidden inside the code, and it steals nearly everything it can: product ID, model, partner (provider?), language, country, and userID. But that’s all child’s play; the true pièce de résistance is that it has the ability to download more code. In other words, there’s no way to know what the app does after it’s installed, and the possibilities are nearly endless.
Click to expand...
Click to collapse
The offending apps from publisher Myournet:
* Falling Down
* Super Guitar Solo
* Super History Eraser
* Photo Editor
* Super Ringtone Maker
* Super Sex Positions
* Hot Sexy Videos
* Chess
* ????_Falldown
* Hilton Sex Sound
* Screaming Sexy Japanese Girls
* Falling Ball Dodge
* Scientific Calculator
* Dice Roller
* ????
* Advanced Currency Converter
* App Uninstaller
* ????_PewPew
* Funny Paint
* Spider Man
* ???
Click to expand...
Click to collapse
http://www.androidpolice.com/2011/0...-android-nightmare-and-weve-got-more-details/
Now, on to some more details of the virus. We should point out that this vulnerability was patched with Gingerbread, meaning any device running Android 2.3+ should be fine. In other words, if you’re looking to play the blame game (which I’m not, but having read all the comments on the original post, many people are), then there’s plenty to go around. The hole was fixed by Google, but it’s relatively useless since many phones aren’t yet running a version of Android that is protected. It’s noteworthy that some manufacturers released updates that patched the exploit for devices without updating to Gingerbread; unfortunately, it appears that minority is quite a small one.
Perhaps most important is the question of what infected users can do about their situation; unfortunately, the answer is not much of anything. Because the virus opens up a backdoor and can bring in new code at any time, the only way to really rid an infected device of any damage is to completely wipe the device – not exactly the optimal solution, but it looks like the only one available, at least for now.
Finally, Justin notes that ROM developers working with pre-Gingerbread versions of Android can prevent the virus from backdooring in code by putting a dummy file at /system/bin/profile.
Click to expand...
Click to collapse
As you can see androidpolice.com reports on this backdoor and roots and steals personal information. The apps are removed from the market but that doesn't mean they got them all. Attached is a flashable fix as suggested by androidpolice.com
So users can flash this .zip or simply create a blank file called profile and place it in /system/bin/ (developers are encouraged to include this file in future releases. A blank file is not going to affect performance at all)
Alternate methods:
Using 'adb shell' or terminal emulator (should work on any ROOTED phone) as suggest by xaueious here
Code:
$ su
su
# remount rw
Remounting /system (/dev/stl9) in read/write mode
# touch /system/bin/profile
# chmod 644 /system/bin/profile
#
Alternate 2:
Download blank profile file from here (or create one and name it profile)
Use a program like Root Explorer to copy it to /system/bin/
Then longpress on it and check the permissions should be read/write for user, read for group, and read for others.
Alternate 3:
cyansmoker has put together an apk for the patch here https://market.android.com/details?id=com.voilaweb.mobile.droiddreamkiller
Thanks for pointing this out photoframd and androidpolice.com for investigating and reporting!
UPDATE: I renamed the .zip file and reuploaded it (350 hits wow). Also in the edify scripted version I added 644 permissions to the file (but if you already flashed it then it should have defaulted to that). I also added a pre-edify version of the patch thanks to xaueious for people using a recovery that does not yet understand edify.
Click to expand...
Click to collapse
Thanks
Sent from my Rocking dj05, themed superdark w/o swype mod, voodoo 5, with custom boot and shutdown.. With premium xda app.
I would also recommend installing the free Lookout Mobile Security app. I find it to be very non-intrusive on my phone, no negligible battery drain or performance issues. Just scans any app you install, looking for bad stuff. Also does weekly full system scans, contact backup, and provides phone lock/alarm/location tracking features in case you lose it. Premium version has even more bells and whistles.
Posted from my EB01 SuperClean Fascinate with Voodoo
This has been stuck for the time being as it seems to be affected a BOATLOAD of users. Thanks for the linkage!
Here are two zips if people want them and don't feel like going to another thread/page/topic/whatever.
adb shell busybox touch /system/bin/profile
is all you need. Most fascinate kernels (of recent) have a bug, and /system is mounted as r/w.
So everyone should flash this no matter what rom you are using? Should we flash the new cwr also?
sorry delete
jcase said:
adb shell busybox touch /system/bin/profile
is all you need. Most fascinate kernels (of recent) have a bug, and /system is mounted as r/w.
Click to expand...
Click to collapse
adb shell chmod 644 /system/bin/profile
also?
NOsquid said:
adb shell chmod 644 /system/bin/profile
also?
Click to expand...
Click to collapse
This would probably be a good thing. Basically locks the file from being written to, right? Should I add it to the first post?
lasportsfan said:
So everyone should flash this no matter what rom you are using? Should we flash the new cwr also?
Click to expand...
Click to collapse
Yes.
All this is is a quick fix that will create a blank file. The current iteration of the malware checks to see if it already exists. This file fools it into thinking it already exists, so it moves on.
As you might guess, the author needs to only update his code to bypass this, in order for this to be an issue again.
And now that this is out, someone else will probably try it. Someone who is a little more thorough.
Moral of the story?
Be careful.
Consider running something like LookOut.
Backup your important data regularly.
As far as CWM goes, is there some kind of connection to the malware thing? Or just in general?
(If just in general, it's better to ask elsewhere as to not derail the thread).
Otherwise, I don't believe the newest (orange) clockwork recovery from ROM manager is fully compatible yet. Last I heard, it still had some bad binaries and 1 bad mounting point. Stick with the Red from JT's thread (which is the same bundled into SuperClean). Other than a couple superficial bugs that don't hurt anything, it works wonderfully and has more features than the orange CWM currently has.
GizmoDroid said:
This would probably be a good thing. Basically locks the file from being written to, right? Should I add it to the first post?
Click to expand...
Click to collapse
I dunno, it was in Rodderik's post but jcase didn't mention it. He's smarter than me, that's why I asked...
444 or 000 would be safer as that would prevent the file from being overwritten at all. 444 for read-only, 000 for no access.
If I never downloaded any of the apps in the list and have lookout on my phone is this neccesary to download or should i not be worried?
italysfinest327 said:
If I never downloaded any of the apps in the list and have lookout on my phone is this neccesary to download or should i not be worried?
Click to expand...
Click to collapse
Who should act? Users and developers using pre-gingerbread roms
Click to expand...
Click to collapse
I'd say that means you should be worried. Those apps listed are just the ones that were found on the market with them from one publisher. Just how virus's can get put into any application on a PC, the same can be done on phones.
Remember folks, our phones are just as exploitable as any other computer, so be careful!
good thing the patch came out!
imnuts said:
444 or 000 would be safer as that would prevent the file from being overwritten at all. 444 for read-only, 000 for no access.
Click to expand...
Click to collapse
Not sure whether Android interprets permissions differently from desktop Linux, but even if a file is 000 the owner can delete it on Debian. And root definitely can. If the file needs to be there for the root exploit to work, then this prevents it, but if they can run the root exploit and get root while this file is there then changing permissions on it will do nothing.
iofthestorm said:
Not sure whether Android interprets permissions differently from desktop Linux, but even if a file is 000 the owner can delete it on Debian. And root definitely can. If the file needs to be there for the root exploit to work, then this prevents it, but if they can run the root exploit and get root while this file is there then changing permissions on it will do nothing.
Click to expand...
Click to collapse
This is just another reason why I see this as a quick fix for what will need to have a much better one in the future.
If anyone hears of a more robust solution (besides using LookOut), let us know!
I navigated through Root Explorer to system/bin/profile and found a file there that reports
"01 Aug 08 06:00:00 rwxr-xr-x 0 bytes".
The 2008 date has me worried, although the 0 bytes means it is empty. Does anybody know if this is put there by FrankenClean 2.8 as a fix for this issue, or am I the only one on SuperClean seeing this (which would be bad!)
SupraLance said:
I navigated through Root Explorer to system/bin/profile and found a file there that reports
"01 Aug 08 06:00:00 rwxr-xr-x 0 bytes".
The 2008 date has me worried, although the 0 bytes means it is empty. Does anybody know if this is put there by FrankenClean 2.8 as a fix for this issue, or am I the only one on SuperClean seeing this (which would be bad!)
Click to expand...
Click to collapse
It is included in SC2.8. The 0 bytes is the best indicator that you are clean, since this patch is merely an empty file.
If you were infected, that file would actually have code in it.
For CWM 2.5.x.x DJ05, which one do you flash? or both?
DroidDreamMalwarePatch_pre-edify.zip
DroidDreamMalwarePatch_edify.zip
Thanks and sorry for the trouble, just wanted to be sure.
This is the Q&A topic for [thread="20962941"]GTabCombOver[/thread].
Does flash player work on this rom?
I think only opera browser
Best HC Yet
I really like this ROM. Couple of items of note that i have seen. My Wifi started to error out. I have tried fixing it, but it still just reports error. I am going to try pershoots kernel. I had issues before with Clems HC kernel. Second I tried inserting a USB disk, and the status bar says USBDisk2 inserted, but it does not appear to be mounted.
Flash
AeroToxin said:
Does flash player work on this rom?
Click to expand...
Click to collapse
Flash works for me in Opera, but it can be a bit touchy.
What version of opera and flash are you using? I downloaded opera mobile 11.1 because 11.5.3 gives me problems, I'll put in a url, push enter, and whatever I type goes away it tries to load the page and just stops (like I pushed cancel on loading the page). Then I was gonna download flash 10.3 and opera started acting up made the tablet slow and had to reboot.
USB and Wifi
markmac said:
I really like this ROM. Couple of items of note that i have seen. My Wifi started to error out. I have tried fixing it, but it still just reports error. I am going to try pershoots kernel. I had issues before with Clems HC kernel. Second I tried inserting a USB disk, and the status bar says USBDisk2 inserted, but it does not appear to be mounted.
Click to expand...
Click to collapse
Does turning it off and on fix the wifi?
I'll look into using a usb disk soon.
No just keeps going into an error state. It seems to be after modifying the WPA_Supplicant with Root Explorer, is when it errors. For work, my company uses LEAP and this is the only way i know of to get it to work. I have done it a hundred times with different ROMs. For some reason unless i leave the wpa_supplicant unmodified, it goes into error. I have double checked and re-checked to see i haven't made any mistakes.
markmac said:
No just keeps going into an error state. It seems to be after modifying the WPA_Supplicant with Root Explorer, is when it errors. For work, my company uses LEAP and this is the only way i know of to get it to work. I have done it a hundred times with different ROMs. For some reason unless i leave the wpa_supplicant unmodified, it goes into error. I have double checked and re-checked to see i haven't made any mistakes.
Click to expand...
Click to collapse
That would probably be the reason. GTabComb has a different wpa_supplicant from most ROMs, so it might not be compatible with the modification you are using. Can you give me more details on what you are doing to modify it?
Sure. Basically I was adding the network, from the Settings applet to use 802.x. I would then modify the supplication to look like the following with Root Explorer:
Network={
ssid=”<networkname>”
scan_ssid=1
key_mgmt=IEEE8021X
auth_alg=LEAP
eap=PEAP
identity=”<domain>\<username>”
password=”<password>”
phase2=”auth=MSCHAPV2”
}
Only after i modified it did it error. Before i modified, the entry was still there, but in the default form which didn't work.
Let me know if there is anything i could test for you. This is the only thing holding me back from finally being happy with an HC ROM.
markmac said:
Sure. Basically I was adding the network, from the Settings applet to use 802.x. I would then modify the supplication to look like the following with Root Explorer:
Network={
ssid=”<networkname>”
scan_ssid=1
key_mgmt=IEEE8021X
auth_alg=LEAP
eap=PEAP
identity=”<domain>\<username>”
password=”<password>”
phase2=”auth=MSCHAPV2”
}
Only after i modified it did it error. Before i modified, the entry was still there, but in the default form which didn't work.
Click to expand...
Click to collapse
Is that the entirety of your wpa_supplicant.conf file or only a fragment? Because, there are other parameters missing, and it says "Network=..." instead of "network=...". Not sure if case matters in the wpa_supplicant.conf file, but, it is something to check.
A detailed debug output would help in troubleshooting your problem. Get it by doing this in CWM:
Code:
$ [B]adb remount[/B]
$ [B]adb shell mv /system/bin/wpa_supplicant /system/bin/wpa_supplicant.bin[/B]
$ [B]adb push wpa_supplicant /system/bin/wpa_supplicant[/B]
$ [B]adb shell chown root.system /system/bin/wpa_supplicant[/B]
$ [B]adb shell chmod 755 /system/bin/wpa_supplicant[/B]
Use this shell script as the wpa_supplicant to push:
Code:
#!/system/bin/sh
exec /system/bin/wpa_supplicant.bin -ddd "[email protected]"
Collect the logs like this:
1. Power off gTab.
2. Connect USB cable.
3. Run "adb logcat -v time > logcat.txt" in a CMD.exe window.
4. Power on gTab.
5. Kill the adb logcat or shutdown tablet after WiFi has errored out.
This will collect all the logs right from the beginning.
That was just the section I edited. I don't have my cable with me so i can't run ADB right now. I did just do the same thing on Flashback and it worked, but I prefer to run GtabCombOver.
heapsize
What app can I use to change the heapsize? Also, dumb question.... What app should I use to adjust the overclocking?
markmac said:
I did just do the same thing on Flashback and it worked, but I prefer to run GtabCombOver.
Click to expand...
Click to collapse
Try using the wpa_supplicant binary from Flashback, then...
---------- Post added at 11:02 PM ---------- Previous post was at 10:59 PM ----------
cgingermany said:
What app can I use to change the heapsize?
Click to expand...
Click to collapse
Just edit /system/build.prop and change dalvik.vm.heapsize.
awesome, thank you! I'll give that a shot. On the dev page someone there said switching those up a little was helping with overall performance so I'll give it a shot and let you guys know. Thanks again.
gtabcombover said:
That would probably be the reason. GTabComb has a different wpa_supplicant from most ROMs, so it might not be compatible with the modification you are using. Can you give me more details on what you are doing to modify it?
Click to expand...
Click to collapse
Actually, I'm having the same problem, and I haven't made any changes to wpa_supplicant.
The only way to get WiFi functioning again is to reboot the device. I can't turn off WiFi, because it just keeps saying "Error." I even tried going into airplane mode, but it made no difference.
In my case, the problem seems to be related to the fact that I've changed the setting for the wifi disconnect policy to "Never when plugged in." I don't remember having this problem prior to making that change.
I've changed it back to "Never" and will report on whether the problem persists.
dagwud said:
Actually, I'm having the same problem, and I haven't made any changes to wpa_supplicant.
The only way to get WiFi functioning again is to reboot the device. I can't turn off WiFi, because it just keeps saying "Error." I even tried going into airplane mode, but it made no difference.
In my case, the problem seems to be related to the fact that I've changed the setting for the wifi disconnect policy to "Never when plugged in." I don't remember having this problem prior to making that change.
I've changed it back to "Never" and will report on whether the problem persists.
Click to expand...
Click to collapse
Mine wont connect at all....... What am I doing wrong?
dagwud said:
In my case, the problem seems to be related to the fact that I've changed the setting for the wifi disconnect policy to "Never when plugged in."
Click to expand...
Click to collapse
Very unlikely.
Will need to look at logs to determine the actual cause of your problem. See post #12. Also get the kernel messages using:
Code:
C:\> [B]adb shell dmesg > dmesg.txt[/B]
---------- Post added at 09:30 PM ---------- Previous post was at 09:23 PM ----------
cgingermany said:
Mine wont connect at all....... What am I doing wrong?
Click to expand...
Click to collapse
Do a basic check. Look at the wpa_supplicant.conf file and see if it looks OK. As a minimum, for home networks, check that the ssid= and psk= values are correct:
Code:
C:\> [B]adb shell cat /data/misc/wifi/wpa_supplicant.conf[/B]
Again, will need to look at logs to find out what's wrong.
rajeevvp said:
Very likely.
Will need to look at logs to determine the actual cause of your problem. See post #12. Also get the kernel messages using:
Click to expand...
Click to collapse
I haven't had time to do as you've requested. However, restoring the setting to the "default" has alleviated the problem. The device appears to be turning off WiFi after a period of time, since it's often had to reconnect after I turn the screen back on.
I'll get to the logs when I'm at my computer and have the time to wait for the wifi error.
Posted it here as this section gets the most views. If needed tom will move it to the rightful section.
There has been a lot of disappointing posts all over the forum with people complaining about bugs, while not providing any kind of information for the developers aside from "X doesn't work" or "I get random reboots".
Well, without the proper knowledge, how are we going to fix it? We don't know what kernel you may be running, what version number you're on, or any information that the system spits out to let you know there's an error. So, I decided to start this thread, to hopefully teach newbies how to give us (developers) proper knowledge when complaining about issues.
This thread will have 3 sections, Logcat (App / system debug log.), Dmesg (active kernel output) and last_ksmg (Typically if you get a random reboot or something of that sort {this is the same as dmesg except it gets the info from the last shutdown [like a kernel panic]})
Section 1: Logcat This log should almost always be included just because it provides more info than just saying something doesn't work. It will essentially tell you which apps are crashing and why and it also gives output of what they're doing. (Your system is running through apps, the dialer, wireless radio's, etc are all ran through apps.) so, if something is general, like a system force close, please just include a logcat.
How to get a logcat: Well, this is REALLY simple, all you need to do is just get adb up and running (google how to do that, I don't feel like writing a 'how to use adb' tutorial for everyone's phone.) and then type
Code:
adb logcat
then you just right click, select, and paste to the thread. It's really that simple!
For more info, check out my logcat guide here.
Section 2: Dmesg
This is getting into issues such as wifi not working, sleep of death, etc. Basically, things that make us go "OH F***" when we use our devices. Note: You will need adb access for this to work, same as logcat. What this will do is get us live kernel output so we can know things like "What driver is the kernel loading {or not loading for that matter}" and similar things. This is linux, so kernel output is important if a hardware aspect isn't working right. How to get a dmesg: This is simple as well, no matter what operating system you're on (mac, windows, linux) just type
Code:
adb shell dmesg > dmesg.txt
and then it will have written the output to a .txt file in your current directory. Either paste the contents to the thread, or attach it to your post. You can also get the dmesg by using terminal emulator. Instead though, you dont type adb shell, you need to also include it to somewhere you will be able to save it. Like /sdcard so, the command goes
Code:
dmesg > /sdcard/dmesg.txt
Just get it off your sdcard and get the contents to the developer!
Section 3: last_kmsg Ok, the last thing is last_kmsg. When android kernels crash, they write the log to last_kmsg so then you can find out what's going on. This is usually for issues such as random reboots and other various kernel panic symptoms. A kernel panic happens when the kernel tries to do something it can't. It doesn't mean wrong permissions, it could just have errored out on something and died which can cause a few things. Anyway, developers REALLY need this if debugging a kernel because it gives us a viable way to see WHAT it's trying to do instead of trying to guess what it is trying to do How to get a last_kmsg: This is super simple and the same on all phones no matter what, what you need is adb up and running (or terminal emulator) and either in adb shell, or terminal emulator just type
Code:
cat /proc/last_kmsg > /sdcard/last_kmsg.txt
or you can do
Code:
adb shell cat /proc/last_kmsg > kmsg.txt
and that will write it to your current working directory from cmd.
Hopefully, this way we developers can have our lives be a little bit easier and you can learn more about android.
Taken from here. All due credits to him. I just edited a little part.
___________XDA Premium__________
Don't be a noob. Be a newbie..!!
Details here.
____________________________________
Nice.
i will add this in my developer 101 thread in next update...thanx
Xenon X said:
i will add this in my developer 101 thread in next update...thanx
Click to expand...
Click to collapse
Sure.
___________XDA Premium__________
Don't be a noob. Be a newbie..!!
Details here.
____________________________________
Nice tutorial :good:
Nice guide:good:
download error
when i press download rom.it doesn't download
it shows this error report when i trying to download rom
"Unable to resolve domain name
Please make sure:
- You are connected to the Internet.
- Your DNS server settings are correct.
Error code 105 (net::ERR_NAME_NOT_RESOLVED)"
please help me
Our developers are hard workers and when one of us finds a problem with a ROM or kernel it is difficult to troubleshoot without some type of log. Since the developers spend a lot of their free time creating things for us to make our phone more enjoyable the least we could do is provide something useful to them to assist in the development of their creations.
Most of you here already know how to get logs, but for those who don't or are rusty at it here are links with useful information and apps to assist in obtaining a log. Also, .torrented provided the basic commands if you're okay using adb.
So let's give back to our developers by giving them logs which are vital for development.
All-in-one logger for use in Windows
http://forum.xda-developers.com/showthread.php?t=1944776
Another logcat tool for use in Windows
http://forum.xda-developers.com/showthread.php?p=28193613#post28193613
Lumberjack- apk for obtaining logs while in android
https://play.google.com/store/apps/details?id=net.solarnz.apps.lumberjack
Universal how to get and read logcat
http://forum.xda-developers.com/showthread.php?t=2274119
There are three types of logs that are used most often: logcat, dmesg, and last_kmsg. Here is an explanation of what they are and what they're useful for
Indirect said:
Alright guys, I was on an irc channel when I considered posting this since it's rather important. There has been a lot of disappointing posts all over the forum with people complaining about bugs, while not providing any kind of information for the developers aside from "X doesn't work" or "I get random reboots".
Well, without the proper knowledge, how are we going to fix it? We don't know what kernel you may be running, what version number you're on, or any information that the system spits out to let you know there's an error. So, I decided to start this thread, to hopefully teach newbies how to give us (developers) proper knowledge when complaining about issues.
This thread will have 3 sections, Logcat (App / system debug log.), Dmesg (active kernel output) and last_ksmg (Typically if you get a random reboot or something of that sort {this is the same as dmesg except it gets the info from the last shutdown [like a kernel panic]})
Section 1: Logcat
This log should almost always be included just because it provides more info than just saying something doesn't work. It will essentially tell you which apps are crashing and why and it also gives output of what they're doing. (Your system is running through apps, the dialer, wireless radio's, etc are all ran through apps.) so, if something is general, like a system force close, please just include a logcat.
How to get a logcat:
Well, this is REALLY simple, all you need to do is just get adb up and running (google how to do that, I don't feel like writing a 'how to use adb' tutorial for everyone's phone.) and then type
Code:
adb logcat
then you just right click, select, and paste to the thread. It's really that simple!
Section 2: Dmesg
This is getting into issues such as wifi not working, sleep of death, etc. Basically, things that make us go "OH F***" when we use our devices. Note: You will need adb access for this to work, same as logcat.
What this will do is get us live kernel output so we can know things like "What driver is the kernel loading {or not loading for that matter}" and similar things. This is linux, so kernel output is important if a hardware aspect isn't working right.
How to get a dmesg:
This is simple as well, no matter what operating system you're on (mac, windows, linux) just type
Code:
adb shell dmesg > dmesg.txt
and then it will have written the output to a .txt file in your current directory. Either paste the contents to the thread, or attach it to your post.
You can also get the dmesg by using terminal emulator. Instead though, you dont type adb shell, you need to also include it to somewhere you will be able to save it. Like /sdcard so, the command goes
Code:
dmesg > /sdcard/dmesg.txt
Just get it off your sdcard and get the contents to the developer!
Section 3: last_kmsg
Ok, the last thing is last_kmsg. When android kernels crash, they right to last_kmsg so then you can find out what's going on. This is usually for issues such as random reboots and other various kernel panic symptoms. A kernel panic happens when the kernel tries to do something it can't. It doesn't mean wrong permissions, it could just have errored out on something and died which can cause a few things. Anyway, developers REALLY need this if debugging a kernel because it gives us a viable way to see WHAT it's trying to do instead of trying to guess what it is trying to do
How to get a last_kmsg:
This is super simple and the same on all phones no matter what, what you need is adb up and running (or terminal emulator) and either in adb shell, or terminal emulator just type
Code:
cat /proc/last_kmsg > /sdcard/last_kmsg.txt
or you can do
Code:
adb shell cat /proc/last_kmsg > kmsg.txt
and that will write it to your current working directory from cmd.
Hopefully, this way we developers can have our lives be a little bit easier and you can learn more about android.
I'm glad to have written this and devs, feel free to link to this guide as a "bug reporting FAQ"
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=23036410
@orangechoochoo, any urge to update the title and the content to provide information about getting dmesg output and last_kmsg?
Once your android device is plugged into your machine, enable Android Debugging in the Developer Options! (this has to be enabled)
If you do not have ADB installed go find a tutorial and install it! (this is a must)
Very simple command, what this does is it will start ADB and output the text into a text file called logcat.txt, once you are done re-creating the error/FC/whatever take that file and upload the contents to a paste site such as https://www.pastebin.com
It's free and you do not need to sign up to create a paste!
logcat via ADB!
Nix:
Code:
[email protected]:~$ adb logcat > logcat.txt
Windows:
Code:
C:\android-tools> adb logcat > logcat.txt
last_kmsg via ADB!
Nix:
Code:
[email protected]:~$ adb pull /proc/last_kmsg
Windows:
Code:
C:\android-tools> adb pull /proc/last_kmsg
dmesg via ADB!
Nix:
Code:
[email protected]:~$ adb shell dmesg > dmesg.txt
Windows:
Code:
C:\android-tools> adb shell dmesg > dmesg.txt
crpalmer said:
@orangechoochoo, any urge to update the title and the content to provide information about getting dmesg output and last_kmsg?
Click to expand...
Click to collapse
I just finished adding more stuff, let me know if you want me to put anything else that will be helpful. The All in One tool looks useful if someone is stuck in the boot animation, and Lumberjack looks useful for obtaining logs while booted in android.
Thanks for the quick links, I'm sure it will help alot of users out. MY question is whether devs want us to filter anyting out, its not too hard to select faults and errors and filter useless info.
This should be pinned.. for sure!
jake.corey.jacobs said:
MY question is whether devs want us to filter anyting out, its not too hard to select faults and errors and filter useless info.
Click to expand...
Click to collapse
That would be nice to know, last night I provided Pio a long a$$ logcat so I feel bad for giving him that extra homework
The ROM was stuck in the boot animation and logcat was spitting out line after line after line so I hit ctlr C to stop it.
Nice guide...