In Eclipse during debuging LogCat messages not comming
Error : Unable to open log device '/dev/log/main': No such file or directory
ROM : GTR v7.8.x
Kernel : [email protected]))
How to fix this issue please help guys.
matrixrak said:
In Eclipse during debuging LogCat messages not comming
Click to expand...
Click to collapse
Because you fail to RTFM?
http://forum.xda-developers.com/showthread.php?t=1529777
neko95 said:
▷TO ENABLE OR DISABLE LOGCAT
▷TYPE: "dslog" TO DISABLE
▷TYPE: "enlog" TO ENABLE
FYI, MUST REBOOT TO TAKE EFFECT
Click to expand...
Click to collapse
"enlog" does not working in GTR v7.8.x
I tried the "enlog" cmd
FYI, I rebooted device also still it does not working.
Flashed: GTR v7.8.x
Still same error, "Unable to open log device '/dev/log/main': No such file or directory"
Please I tried many times but it does not taking any effect, What i missing? BOSS.
Checking Logcat in Ginger Snaps v1.3 ROM
Flashed ROM: GSnaps v1.3
entered CMD: "enlog"
Replay: mv: can't rename '/system/etc/init.d/95logger': No such file or directory
Logcat Enabled!
It does not able to remove that startup script so, check this guys.
matrixrak said:
I tried the "enlog" cmd
FYI, I rebooted device also still it does not working.
Click to expand...
Click to collapse
Never used the ROM, never used the kernel either. Why don't you ask in the ROM thread after your have tried that with the stock kernel shipped with that ROM?
Finally got to work on GSnaps v1.3
Finally got it worked on GSnaps v1.3
Please fix cmd "enlog".
I manually moved that "95logger" script file and rebooted device.
also "enlog" cmd does not work in GTR v7.8.x keep that guide of GSnaps clean guys it is very dirty to understand.
Please fix this issue if any one finds, otherwise this great innovated ROM to O1 will lead to a hated one by our beloved developers present out there.
Finally, i can continue my development work.
Anyway keep the good work and thanks to lophrae dude, u realized me.
When ICS port of Gsnaps or GTR will come ? eager to flash that one also.
Cheer up.
matrixrak said:
Finally got it worked on GSnaps v1.3
Please fix cmd "enlog".
I manually moved that "95logger" script file and rebooted device.
also "enlog" cmd does not work in GTR v7.8.x keep that guide of GSnaps clean guys it is very dirty to understand.
Click to expand...
Click to collapse
Did you run the script as root?
P.S. ROM suggestions need to be posted in the ROM thread, not here.
Please understand anyone before under estimate
Hello BOSS, till now i flashed xperia x10, xperia mini pro and many others. Their rom is very good please GSnap document is very dirty even
a Expert could mislead.
By the way, I prepared from past one year before proceeding to flash my device O1.
Besides, I don't have much time in child's play to waste XDA developer time and mine.
I correctly tested that CMD ("enlog") in GTR v7.8.x it does not work. I think u read that GSnap rom correctly thousand times.
and only in GSnap "enlog" this cmd worked for me. No one mentioned to enter that command in GTR vX.
matrixrak said:
Besides, I don't have much time in child's play to waste XDA developer time and mine.
Click to expand...
Click to collapse
Ditto. Geez... Post on the ROM thread! http://forum.xda-developers.com/showthread.php?t=1529777
No ROM developer will read ROM suggestions in a badly titled thread in general section. I am NOT the developer of that ROM. Never used it in fact.
P.S. Did you run the command as root?
Missed to check as Root
Ok, thank u.
I missed that to check as Root, no error message came and enlog worked.
Your help greatly appreciated.
Related
Hello everyone,
I've already posted 2 threads here! People have been helping me understand alot of this rooting/recovering and stuff.
But i need your help again. I have a LG P500 with official 2.3.3 update and I want to flash the TWRP on my phone (phone was rooted. I have the superuser app) Im following this tutorial http://forum.xda-developers.com/showthread.php?t=1146566 but im stuck at the "su" command!(by stuck i dont mean bricked! I just can go further than that step!)
When i use that command it takes a while and then it says "Permission denied".
Isnt it supposed to ask me for permission? It didnt even show anything to choose if i want to give the permission or not!
If any of you have another way to flash that custom recovery or could help me with this one i would really appreciate your help! (im kinda noob but i heard that ROM manager has a "good" reputation when it comes to bricking phones so ill probably pass all the tutorials that i need to use it!)
PS: i downloaded the TWRP from this site TakamineSubasa gave me (http://lg-p500.zrusit.eu/forum/viewtopic.php?f=4&t=7). And also im using Terminal Emulator from the market to write the commands.
Would really appreciate all the help anyone could give me!
Thank you in advance
edit: sorry didnt see that you were using terminal emulator, please go to Superuser app and be sure "Terminal" is listed in the allow list
I dont have any apps listed on the superuser app! And i dont know how to add them!
BAAAM! From xda app! (LG P500! LEGEN.....DARY!)
Mmm thats weird, when you enter "su" command it should prompt permission :S
Try reinstalling Terminal emulator
If that doesnt work, maybe root is screwed.... After you try re-rooting your phone, install Android SDK then do the recovery install within windows command
Oh, and please post which version of stock rom is in your phone... go to settings --> about phone and post that details, and check if its v10a ,b c, etc...
Some letters doesnt like to be rooted the easy way...
PS: If you dont want to install Android SDK also try the second method in the guide i gave you
just download rom manager
then download CWM recovery
after that, reboot into recovery
and flash any recovery zip file that u wan
The first time you use a function that needs root permission, you should automatically get a screen like this: http://fs03.androidpit.info/ass/x66/772466-1281914300690.jpg
After you click allow, you'll be able to use the su function. I suggest you try using other program that asks for root (for example NoFrills CPU Control, or enable root explorer setting in ES File Explorer). If the screen doesn't show up you may want to repeat the rooting process. By the way, did you root the phone before or after official upgrade?
Alternatively, you can try the LGMDP process for unrooted phones: http://forum.xda-developers.com/showpost.php?p=15217609&postcount=3
I've heard a lot that using ROM Manager isn't recommended, due to the many reported issues related to it like fastboot, but since I've never tried that I can't vouch for sure.
What I did on my phone was use this "simplified method" to install custom recovery: http://forum.xda-developers.com/showpost.php?p=13422938&postcount=91
You'll get an AmonRa v1.2 by following this guide, but after that you can easily flash any recovery you want including TWRP using ciaox's guide: http://forum.xda-developers.com/showthread.php?t=1065197
XeactorZ said:
just download rom manager
then download CWM recovery
after that, reboot into recovery
and flash any recovery zip file that u wan
Click to expand...
Click to collapse
Hello XeactorZ
I appreciate your help but im not an expert in this (only rooted my phone once and apparantely i did it wrong!) and what i heard is that ROM manager is well known for bricking phones and i dont want to take that risk since i dont really want to be without my phone.
Btw my software version is V20c!
I'll try to install ES File Explorer and enable the root explorer setting to see if i accidently pressed the deny option and now its not allowing me to do anything!
if its the case then ill have to unroot and re-root again right? (used this tutorial: http://forum.xda-developers.com/showthread.php?t=1200167).
Another thing! when i use the command "su" on the terminal emulator i sometimes get a force close error from the superuser app.
Palmaaa said:
Hello XeactorZ
I appreciate your help but im not an expert in this (only rooted my phone once and apparantely i did it wrong!) and what i heard is that ROM manager is well known for bricking phones and i dont want to take that risk since i dont really want to be without my phone.
Btw my software version is V20c!
I'll try to install ES File Explorer and enable the root explorer setting to see if i accidently pressed the deny option and now its not allowing me to do anything!
if its the case then ill have to unroot and re-root again right? (used this tutorial: http://forum.xda-developers.com/showthread.php?t=1200167).
Another thing! when i use the command "su" on the terminal emulator i sometimes get a force close error from the superuser app.
Click to expand...
Click to collapse
Just go to applications menu and clear data for ES file explorer.
I just tried to enable the root explorer option but, again, superuser app forced closed..
terratrix i only installed ES explorer now, i think that didnt affect anything on the superuser permissions. I'll probably unroot and re-root the phone again today. Cant do it at work but ill try to do it at home.
If you have any ideas i could try, please leave a post! would really appreciate it.
Thank you everyone.
PS: right after i posted this i tried to open the superuser app and now it simply doesnt open. Always force closes!
Palmaaa said:
Hello XeactorZ
I appreciate your help but im not an expert in this (only rooted my phone once and apparantely i did it wrong!) and what i heard is that ROM manager is well known for bricking phones and i dont want to take that risk since i dont really want to be without my phone.
Btw my software version is V20c!
I'll try to install ES File Explorer and enable the root explorer setting to see if i accidently pressed the deny option and now its not allowing me to do anything!
if its the case then ill have to unroot and re-root again right? (used this tutorial: http://forum.xda-developers.com/showthread.php?t=1200167).
Another thing! when i use the command "su" on the terminal emulator i sometimes get a force close error from the superuser app.
Click to expand...
Click to collapse
well but so far i use so many time
my phone didn;t bricked @@
I understand you, but i have no experience in this kind of things and i guide myself basicaly for what i read in this forum!
But thank you very much for the time you spent trying to help!
Palmaaa said:
I understand you, but i have no experience in this kind of things and i guide myself basicaly for what i read in this forum!
But thank you very much for the time you spent trying to help!
Click to expand...
Click to collapse
Yeah as i said, ROM Manager has a risk of bricking your phone, so AVOID it...
And as i said, you either re-root your phone, or use the second method in the guide i posted (LGMDP)
Palmaaa said:
I understand you, but i have no experience in this kind of things and i guide myself basicaly for what i read in this forum!
But thank you very much for the time you spent trying to help!
Click to expand...
Click to collapse
yes i also know
but every person sure got his / her 1st time
u didn't try forever will won't get the answer
just my opinion
Well using ROM manager will be my last option ill first try too re-root my phone(think that will work) and if that doesnt solve the problem i use the other method TakamineSubasa adviced!
But will only use ROM manager if those 2 methods fail! So wish me good luck
Any ideas or solutions to this problem please post them! Even if i solve my problem other solutions may help anyone else!
Thank you very much!
Palmaaa said:
Well using ROM manager will be my last option ill first try too re-root my phone(think that will work) and if that doesnt solve the problem i use the other method TakamineSubasa adviced!
But will only use ROM manager if those 2 methods fail! So wish me good luck
Any ideas or solutions to this problem please post them! Even if i solve my problem other solutions may help anyone else!
Thank you very much!
Click to expand...
Click to collapse
well good luck then
report back result either success or fail
Palmaaa said:
Well using ROM manager will be my last option ill first try too re-root my phone(think that will work) and if that doesnt solve the problem i use the other method TakamineSubasa adviced!
But will only use ROM manager if those 2 methods fail! So wish me good luck
Any ideas or solutions to this problem please post them! Even if i solve my problem other solutions may help anyone else!
Thank you very much!
Click to expand...
Click to collapse
No no no, dont you dare! --> http://forum.xda-developers.com/forumdisplay.php?f=837
See, ROM Manager = "Da Brick Maker"... daily bread bricks sponsored by ROM Manager
TakamineSubasa said:
No no no, dont you dare! --> http://forum.xda-developers.com/forumdisplay.php?f=837
See, ROM Manager = "Da Brick Maker"... daily bread bricks sponsored by ROM Manager
Click to expand...
Click to collapse
yeah, for those unlucky guys. be warned.
i will still use it though. served me quite well. never failed even once. <knock on wood>
Well i told you guys i would post to tell you how it went!
I managed to "fix" that denied permission problem. What i did was simply update superuser app! And BOOOM! problem fixed.
All went well with the Recovery flashing, I also flashed CM7(had a few scares but managed to fix them [thanks to that im now half asleep at work ]) but after i flashed CM7 and booting into it, i found a problem. My phone doesnt have GSM. I found it wierd that when i booted into it the first time it didnt ask me for my PIN but i didnt even noticed as i was really sleepy. This morning i noticed that i had an "x" next to that GSM scale or w/e you want to call it. And i also dont have my SIM contacts listed.
Im posting this here just to update you guys about how it went but ill do a thread so i try to fix my problem and hopefully it will help someone else!
Thank you guys for all the help you gave!
Hey guys, I bought the Xperia sola phone a couple of weeks ago and everything worked perfectly. After a week I found out that I wanted to root it and flash a new rom(KA02 Xperia SSpeed). At first I only unlocked the bootloader and flashed a rooted kernel. The problem I've been experiencing after that is that it is impossible to activate wifi/hotspot. I always get "Error" when I try.
I've read somewhere that it's pretty common after unlocking the bootloader. Is it any way to fix this?
Thanks in advance,
Doctor X
Copy The Wifi Modules Given In The Zip And Give The Following Permissions
Read Write
1Owner Owner
2Group
3Others
The Name Equals Tick
Use Root Explorer
Hit A Thankxx If It Helped Plezz :angel:
Solar Monster said:
Copy The Wifi Modules Given In The Zip And Give The Following Permissions
Read Write
1Owner Owner
2Group
3Others
The Name Equals Tick
Use Root Explorer
Hit A Thankxx If It Helped Plezz :angel:
Click to expand...
Click to collapse
Which zip?
Anyway, when I first rooted the phone I kept the stock rom and used the "Advanced Stock Kernel" by DooMLoRD. After rooting wifi wouldn't turn on. Now I use the Xperia SSpeed kernel as mentioned in the first post.
It'll be fine for me to flash back the original kernel and relock the bootloader if it will fix the problem.
If anyone has the original image that I can use with fastboot I'd be grateful.
Thanks,
Doctor X
Solar Monster said:
Copy The Wifi Modules Given In The Zip And Give The Following Permissions
Read Write
1Owner Owner
2Group
3Others
The Name Equals Tick
Use Root Explorer
Hit A Thankxx If It Helped Plezz :angel:
Click to expand...
Click to collapse
Okay, I found out what you meant. I used v1 of the kernel actually because I downloaded everything from the XDA hosting thing. I'm using v2 now, but I got a problem with the phone memory. Even if I've erased everything and flashed the SSpeed kernel and rom it says its full. And I don't understand a sh*t.
Okay I got the integrated storage to work again and installed the wifi modules, but now I experience the same problem as before. I just get "Error" when I try to activate wifi.
Anyone?
I got relevant information when I ran dmesg.
[19289.333679] cw1200_load_firmware: can't read config register
[19289.334686] cw1200_wlan: probe of mmc2:0001:1 failed with error -110
Click to expand...
Click to collapse
I did post this in the anroid Q&A section but was told this section may be more approriate...
Okay I have tried everything I could before coming to this point, so you guys are my last hope... Basically I upgraded my partners live with walkman phone to ICS. Now she is complaining because it crashes all the time etc... So I followed one of the guides on here to downgrade. I downloaded flashtool and I downloaded the firmware. I deleted everything in the frimware folder as per the instructions. I then copied and pasted the gingerbread firmware into the folder and exited...
Then whenever I try to flash it, it says I need to install the drivers... I've tried to do that by going to the drivers folder etc. I've installed everything in there but nothing works and the LWW isn't listed anyway... I'm using windows 7 if that helps...
I've even tried doing this through my linux partition and that was a little over my head... Had to do all sorts in the terminal, I did try but no luck there either...
I've seen people in the comments ask for help and they seemed to have no problem when directed to the guide... I have follwed the guide to a tee multiple times, this is why I hate myself! lol
Please Please help me so I can shut my whining other half up! Trust me she whines even more than me! lol
check this form http://forum.xda-developers.com/showthread.php?t=1709880 it helps you to downgrade and root
usman_fareed said:
check this form http://forum.xda-developers.com/showthread.php?t=1709880 it helps you to downgrade and root
Click to expand...
Click to collapse
Hey thanks for the speedy reply but as I said in the OP I have tried this guide (well not this one but one exactly the same)... I have downloaded flashtool I have downloaded the firmware (gingerbread). I have done evrything, put it in the right folder etc... Just when I try to flash it it says I need to install the drivers, it comes up red... I go to the drivers folder install them but nothing works... Just keeps saying I must install drivers...
Still looking for a solution here guys, having no luck though... Any suggestions?
hatemyself said:
Still looking for a solution here guys, having no luck though... Any suggestions?
Click to expand...
Click to collapse
Windows is asking you for drivers? Your post isn't very clear...you probably need to install adb drivers on your pc, have you done that? Also ics on lww shouldn't crash and reboot all the time, did you upgrade through pcseus or through flashtools?
Guys big problem here
whenever i try to change cpu frequency my phone
reboots.. All kernel having same problem....i thought it
was Rom problem. But it isn't .. Stock ics having same
problem... I tried to flash stock ics Rom...but surprisingly
flash tool saying 'flash aborted' . It got stuck on flashing
kernel long time then flash aborted... Water do i do?
What's wrong?
I don't think this is flashtool related problem cuz
previously everything was working fine .. Something
wrong with my bootloader i think .. Changing Rom,
changing kernel,deleting all apps etc nothing helps
never Oc my phone.. I usually underclock it
Get logcat and post it on the corresponding rom thread.
So corresponding developers will help you.
svprm said:
Get logcat and post it on the corresponding rom thread.
So corresponding developers will help you.
Click to expand...
Click to collapse
it's happening with every rom.... even stock ICS. 587(nandroid backup )
d main problem is I cannot flash stock ICS. 587 anymore!!! I hv latest flashtool and drivers.... and how to get logcat? would d play store app do d job?
Logcat:
Plug the mobile.
type this cmd
"adb logcat > log.txt"
It will place the log.txt on opened dir.
What error is showing while trying to install a Stock ROM?
svprm said:
Logcat:
Plug the mobile.
type this cmd
"adb logcat > log.txt"
It will place the log.txt on opened dir.
What error is showing while trying to install a Stock ROM?
Click to expand...
Click to collapse
it get stuck on flashing kernel for a long time then flashing aborted.. nothing else..
Maybe a hardware problem?
Sent from my MT11i using xda premium
Q&A for Pure AOSP 4.4.4 ***international rom***
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for Pure AOSP 4.4.4 ***international rom***. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
plsdontpwn.me seems to be down
plsdontpwn.me does not respond. Cloudflare reports host error.
sameersbn said:
plsdontpwn.me does not respond. Cloudflare reports host error.
Click to expand...
Click to collapse
Thanks, looking into it
sameersbn said:
plsdontpwn.me does not respond. Cloudflare reports host error.
Click to expand...
Click to collapse
It's back online now, thanks for pointing it out.
Lloir,
Trying to figure out why my SuperSU won't work properly on this ROM is beyond my skills. Works fine on Omni. Relocked, unlocked bootloader multiple times, flashed the ROM/gapps/supersu (2.16) via CWM, but still get "SU binary not installed and SuperSU can't install it...". Found su in system/xbin where my root checker app said it was, busybox installed v1.22.1 in system/xbin. Maybe su binary permissions are not correct? Anyway, if there is anything else I can do, please let me know when you get a moment. In the meantime, I am loving your AOSP 4.3. Yeah, I know, why go back to JB? Wanted to try your AOSP ROM as a daily driver (and need a camera) so it works perfectly.
I did learn from my past mistake and actually posted in the CORRECT thread.
Lloir,
I asked Chainfire about my SuperSU issues. From the logs I sent, was told the su daemon wasn't starting at boot time. Was told to ask if ROM supported starting install-recovery.sh at boot time? I hope my explanation makes sense. Thank you for your time.
stickt73 said:
Lloir,
I asked Chainfire about my SuperSU issues. From the logs I sent, was told the su daemon wasn't starting at boot time. Was told to ask if ROM supported starting install-recovery.sh at boot time? I hope my explanation makes sense. Thank you for your time.
Click to expand...
Click to collapse
I'm one person...Give me time
I have problem with starting ROM.
After flashing it is stuck on screen where is showing word Android (with animation). Left it like that for one hour and something, still didn't want to boot, restarted it, same thing. CWM is from link from thread.
Steps for flashing I applied:
1.Flashes rom zip from recovery, deleted cache and data before
2. Booted to fastboot and flashed kernel
3. Flashed gapps and rebooted
While waiting rom to start adb on my pc cannot see device.
Can you help me with this?
Sent from my HTC One X+ using XDA Free mobile app
komple said:
I have problem with starting ROM.
After flashing it is stuck on screen where is showing word Android (with animation). Left it like that for one hour and something, still didn't want to boot, restarted it, same thing. CWM is from link from thread.
Steps for flashing I applied:
1.Flashes rom zip from recovery, deleted cache and data before
2. Booted to fastboot and flashed kernel
3. Flashed gapps and rebooted
While waiting rom to start adb on my pc cannot see device.
Can you help me with this?
Sent from my HTC One X+ using XDA Free mobile app
Click to expand...
Click to collapse
you should have deleted system too not just cache and data. This rom 100% boots so it's something you are doing wrong.
komple said:
I have problem with starting ROM.
After flashing it is stuck on screen where is showing word Android (with animation). Left it like that for one hour and something, still didn't want to boot, restarted it, same thing. CWM is from link from thread.
Steps for flashing I applied:
1.Flashes rom zip from recovery, deleted cache and data before
2. Booted to fastboot and flashed kernel
3. Flashed gapps and rebooted
While waiting rom to start adb on my pc cannot see device.
Can you help me with this?
Sent from my HTC One X+ using XDA Free mobile app
Click to expand...
Click to collapse
Also, make sure you are flashing the Elite Kernel from nik3r and NOT the boot.img from the ROM zip. Like Lloir said, there's no reason for the ROM not to boot unless you've done something wrong.
Lloir said:
you should have deleted system too not just cache and data. This rom 100% boots so it's something you are doing wrong.
Click to expand...
Click to collapse
I was wrong sorry guys, wrong kernel.
Sorry for asking this, when can we expect camera or version 5.0?
---------- Post added at 01:58 PM ---------- Previous post was at 01:56 PM ----------
stickt73 said:
Also, make sure you are flashing the Elite Kernel from nik3r and NOT the boot.img from the ROM zip. Like Lloir said, there's no reason for the ROM not to boot unless you've done something wrong.
Click to expand...
Click to collapse
I had wrong kernel, after posting this I realized that , off course
stickt73 said:
Lloir,
Trying to figure out why my SuperSU won't work properly on this ROM is beyond my skills. Works fine on Omni. Relocked, unlocked bootloader multiple times, flashed the ROM/gapps/supersu (2.16) via CWM, but still get "SU binary not installed and SuperSU can't install it...". Found su in system/xbin where my root checker app said it was, busybox installed v1.22.1 in system/xbin. Maybe su binary permissions are not correct? Anyway, if there is anything else I can do, please let me know when you get a moment. In the meantime, I am loving your AOSP 4.3. Yeah, I know, why go back to JB? Wanted to try your AOSP ROM as a daily driver (and need a camera) so it works perfectly.
I did learn from my past mistake and actually posted in the CORRECT thread.
Click to expand...
Click to collapse
Lloir,
After what seemed like forever, I found a solution to my problem of not having root access. Found this in another forum, but it solved the same problem I had:
Run in adb shell:
mount -o remount,rw /system
echo persist.sys.root_access=1 >> /system/build.prop
reboot
It's amazing what can happen when the search button is used.
Download links do not work
shalane said:
Download links do not work
Click to expand...
Click to collapse
It's being worked on, huge issue when the server got moved.
Lloir when will you upload bug free aosp 4.4.4 Rom for one x plus
Thanks in advance
pranavrocksharma said:
Lloir when will you upload bug free aosp 4.4.4 Rom for one x plus
Thanks in advance
Click to expand...
Click to collapse
Never :good:
Lloir said:
Never :good:
Click to expand...
Click to collapse
Sorry for posting the same post here and there.
Please don't change your decision.
Please