Related
I'm trying to fix a friend's G1, which he bought on ebay from US.
I've no experience whatsoever dealing with Android, so this is new. But I'm fairly capable of understanding every technical process you could use, so I think I'll understand your explanations.
Whenever I connect the device to a PC via USB, the computer detects an unknown device, but the phone just restarts at the splash screen. Notice that it has two different behaviors: When there's no cable connected, it just shuts down after 2 or 3 seconds at the Android screen; when I connect a USB cable, instead of shutting down it restarts continuously.
The first thing I did was to unroot the phone and put the official RC29 rom. Unfortunately, the problem persisted.
I have access to the recovery menu and the bootloader (I don't know if this is the correct term, it's the Camera+Power menu).
The major problem (I think) is that I don't have access to the console, as the recovery menu I have is the original one.
So, can anyone help me with this? Thank you.
Options:
Root the phone and use a custom recovery.
ADB also enables use of the terminal through the shell command. -- You could also use ADB to get a logcat and see what happens before the reboots.
But I don't see how the terminal would help, it sounds like hardware failure if it does it with a stock and custom rom.
Don't I need access to the OS in order to root the phone?
Which SPL do you have?
A boot loop or crash at startup can be caused by many, many things.
Get hold of the android sdk.. inside the /tools folder are 2 programs called ddms and adb, you can start the phone while connected by usb and use either of these programs to grab a startup log. Post the log here and we can hopefully see what's causing the crash.
You probably shouldn't have unrooted the phone.. that's going to make things more difficult.
adb and ddms can't find the device. There's an "Android Phone" in the Device Manager, but as the phone keeps restarting, I guess it isn't on enough time to be able to be detected by adb and ddms.
Edu115 said:
adb and ddms can't find the device. There's an "Android Phone" in the Device Manager, but as the phone keeps restarting, I guess it isn't on enough time to be able to be detected by adb and ddms.
Click to expand...
Click to collapse
Did you install the usb driver that's packaged with the sdk? the one windows installs by default doesn't work for adb or ddms.
If you've got this driver installed and ddms doesn't see the phone, that's pretty ominous.. it should show up there as "offline" as soon as you power it on.
goldenarmZ said:
Did you install the usb driver that's packaged with the sdk? the one windows installs by default doesn't work for adb or ddms.
If you've got this driver installed and ddms doesn't see the phone, that's pretty ominous.. it should show up there as "offline" as soon as you power it on.
Click to expand...
Click to collapse
Thanks, I fixed that and I got the ADB drivers, but the same thing happens. I can't get the attached devices, nothing appears on the list.
One note: this last time I tried to connect the phone via USB it booted, but I couldn't sign in, because as soon as I slid the keyboard, the phone shut down.
So, now I have a "Android ADB Interface", but still no devices listed with adb device.
Right now sometimes (like in 40 tries) the phone turns on and I can use the touchscreen, but when I need to sign-in, it tells me to slide the keyboard and it shuts down.
I still can't get the attached devices using adb, even after trying in other computers.
Edu115 said:
Right now sometimes (like in 40 tries) the phone turns on and I can use the touchscreen, but when I need to sign-in, it tells me to slide the keyboard and it shuts down.
I still can't get the attached devices using adb, even after trying in other computers.
Click to expand...
Click to collapse
what happens if you start with the keyboard open?
you know, it could be a hardware fault, a dry joint or loose wire
the sliding of the keyboard just jolts it.
I've read several topics but i couldn't find the right answer. I hope you can help me.
The problem i have happened without me doing anything recent. I have never flashed any rom, and i rooted my phone for titanium backup like 2 month ago and it worked fine.The last things i did was to install pocket legend, the new mmorpg like 3 days ago.I charge my phone during night, and take it for the day in the morning. Today, the screen stayed black when i picked it up. When i reboot, the screen goes black after the samsung logo.
The problem is that i have recovery mode (the 3 buttons) disabled and when i try to connect to kies it says i am not in samsungs kies mode.. Is there a way to force it to detect my phone so i can try update it?
According to the wiki, my phone doesnt seem to be bricked as i can still see the battery charging when i plug it. Is my phone bricked? Any hope?
I know the easiest way would be to return it to the store, but i dont want them to see my personal information/rooting as i cant even factory reset it.
There is also that topic on internal sd that has failed but i think this is not my case. You can still boot into android without the internal sd right?
I've seen a topic on soldering two mini usb cable to force the phone to go into recovery mode. I not familar enough to do it. If this method could solve my problem, could anyone sell me one?
Was there an over the air update today that could've done this to my phone?
I am lost, please help i am really clueless in what is happening to me.
are you able to go to download mode
flash your phone that way with odin i had the same problem as you
download mode as in using the 3 buttons? no i cant unless there is another way?
I can't get odin to recognize my phone.. I can't get into os so no usb debugging...
read this
http://forum.xda-developers.com/showthread.php?t=819551
then it'll help you flash back to whatever you want
Okay, I know the jig will DEFINITELY work in this case. Any phone state I've come across with that jig, I can throw the phone into downloading. However, it seems that there MAY be hope for you PRIOR to using the jig. Are you familiar with the ADB commands? If so, turn on the phone, connect via USB, run cmd as administrator, navigate to the proper adb folder and under the prompt type in adb devices. If it shows any device, type in adb reboot download and it'll throw it into download mode for you.
AllGamer said:
read this
http://forum.xda-developers.com/showthread.php?t=819551
then it'll help you flash back to whatever you want
Click to expand...
Click to collapse
I think the JIG is my last resort but i dont have any solder skill
If you know anyone that could sell me one i would be very happy!
krazykidd said:
Okay, I know the jig will DEFINITELY work in this case. Any phone state I've come across with that jig, I can throw the phone into downloading. However, it seems that there MAY be hope for you PRIOR to using the jig. Are you familiar with the ADB commands? If so, turn on the phone, connect via USB, run cmd as administrator, navigate to the proper adb folder and under the prompt type in adb devices. If it shows any device, type in adb reboot download and it'll throw it into download mode for you.
Click to expand...
Click to collapse
Good to hear that the JIG would work. As for ADB commands, doesn't it need the usb to be put in debugger mode? Is there any way to do it externally, without going in the setting menu? I am not very familiar with the adb commands but if its doable i will go read about it.
Thanks for suggestions!
slay3r85 said:
As for ADB commands, doesn't it need the usb to be put in debugger mode? Is there any way to do it externally, without going in the setting menu? I am not very familiar with the adb commands but if its doable i will go read about it.
Click to expand...
Click to collapse
exactly... it's not possible via ADB in your conditions
Thanks you for help!
I still tried but it said that it couldn't find my phone.
I leaning toward making a JIG. I just have to figures out how if no one sell them
Did you really tryed Download Mode?
"Vol Down" + "Home" + "Power" instead of "Vol Up" + "Home" + "Power"?
I tried several time different combo listed on wiki without any success. About 3h long!
I bought my phone the first day it came out so i guess the hardware method is locked.
As soon as i can get it back running i will apply that new fix for the combo.
I am a bit worried about the homemade JIG, will it still work without usb debugging?
Where in the world are you?
If you are in the GTA area, then you can invite me for a coffe
slay3r85 said:
I tried several time different combo listed on wiki without any success. About 3h long!
I bought my phone the first day it came out so i guess the hardware method is locked.
As soon as i can get it back running i will apply that new fix for the combo.
I am a bit worried about the homemade JIG, will it still work without usb debugging?
Click to expand...
Click to collapse
Yes. It will. As long as the phones off and the jig is in when you turn it on
Sent from my SGH-T959 using XDA
AllGamer said:
Where in the world are you?
If you are in the GTA area, then you can invite me for a coffe
Click to expand...
Click to collapse
I wish i could but i live too far Quebec / Laurentides. I think its about 8h driving!
krazykidd said:
Yes. It will. As long as the phones off and the jig is in when you turn it on
Sent from my SGH-T959 using XDA
Click to expand...
Click to collapse
Thanks you for confirming this! I ordered the components and i will try to do it myself.
Some people have done it without any solder skill ! I hope it get here fast! I didn't know i would miss my phone so much!
Seriously! ??? I just soft bricked my phone I really don't know why these software and hardware companies can't get this right the first time. I was going to by an iphone until a sales rep showed me the galaxy s and I was impressed until I saw the black screen of death. A whole lot of B.S. to fix something that should work right in the first place. I'm getting tired of faulty equipment.
My Galaxy is still under warrenty I'll bring it back to store but I'm fed up with worthless technology.
black screen help plz
hey guys i have a galaxy s vibrant which will turn on nd the home nd back nd other buttes will turn on but my screen wont any idea what it might be ?
So my HTC Hero has bit it. It has had a bad touch digitizer for about a week now. Is there ANY way to remove my text messages off the phone, perhaps with ADB? My phone will turn on and I can look at the screen but cannot touch anything. As such, I cannot unlock it.
Does anyone have any suggestions?
rjhall said:
So my HTC Hero has bit it. It has had a bad touch digitizer for about a week now. Is there ANY way to remove my text messages off the phone, perhaps with ADB? My phone will turn on and I can look at the screen but cannot touch anything. As such, I cannot unlock it.
Does anyone have any suggestions?
Click to expand...
Click to collapse
If it's rooted, you could conceivably pull the database file from it if you knew where it was, someone here should know that and this should bump your post back to the top.
aiwetir said:
If it's rooted, you could conceivably pull the database file from it if you knew where it was, someone here should know that and this should bump your post back to the top.
Click to expand...
Click to collapse
It's not rooted, but with the screen off, I could always do so. I think USB debugging is on... Not actually sure.
rjhall said:
It's not rooted, but with the screen off, I could always do so. I think USB debugging is on... Not actually sure.
Click to expand...
Click to collapse
If USB debugging is enabled, you can get a root shell (soft root) with the rageagainstthecage exploit and do what you need to do.
jasonmaloney said:
If USB debugging is enabled, you can get a root shell (soft root) with the rageagainstthecage exploit and do what you need to do.
Click to expand...
Click to collapse
Alright, do you know where the text messages are saved?
rjhall said:
Alright, do you know where the text messages are saved?
Click to expand...
Click to collapse
Dialer storage. Don't remember the exact path offhand.
jasonmaloney said:
Dialer storage. Don't remember the exact path offhand.
Click to expand...
Click to collapse
Would it be possible for me to get to it in ADB without rooting the phone?
the path is /data/data/com.android.providers.telephony/databases/mmssms.db
I'm not sure if root access is required, but good luck
Sent from my HERO200 using XDA Premium App
The Fer-Shiz-Nizzle said:
the path is /data/data/com.android.providers.telephony/databases/mmssms.db
I'm not sure if root access is required, but good luck
Sent from my HERO200 using XDA Premium App
Click to expand...
Click to collapse
Sorry, my experience with ADB is limited. What are the commands I would need, or where would I find a list of commands/functions? I tried the official Android Developer pages and found nothing helpful.
EDIT: Sorry, just got off third shift a couple hours ago and my brain doesn't want to work. I managed to figure out the commands but...
!!!A new challenger appears!!!
I don't have USB debugging enabled. My touchscreen doesn't work. I am in quite a pickle, I believe. I can't get the PC to recognize the phone without USB debugging on. Is there a way to turn it on without a screen?!
rjhall said:
Sorry, my experience with ADB is limited. What are the commands I would need, or where would I find a list of commands/functions? I tried the official Android Developer pages and found nothing helpful.
EDIT: Sorry, just got off third shift a couple hours ago and my brain doesn't want to work. I managed to figure out the commands but...
!!!A new challenger appears!!!
I don't have USB debugging enabled. My touchscreen doesn't work. I am in quite a pickle, I believe. I can't get the PC to recognize the phone without USB debugging on. Is there a way to turn it on without a screen?!
Click to expand...
Click to collapse
Wait... you said just the digitizer is broken? As in, the screen is intact but you just can't make any touch selections?
Are you on the stock (HTC Sense) firmware? If so, you can unlock the phone by pressing MENU on the lockscreen. From there, press MENU again, and use the trackball to navigate to Settings. Turn on USB debugging and root the phone. Install a custom recovery image, then reboot into recovery and do a nandroid backup. Then you'll be able to keep everything, not just your text messages.
jasonmaloney said:
Wait... you said just the digitizer is broken? As in, the screen is intact but you just can't make any touch selections?
Are you on the stock (HTC Sense) firmware? If so, you can unlock the phone by pressing MENU on the lockscreen. From there, press MENU again, and use the trackball to navigate to Settings. Turn on USB debugging and root the phone. Install a custom recovery image, then reboot into recovery and do a nandroid backup. Then you'll be able to keep everything, not just your text messages.
Click to expand...
Click to collapse
It's hard to explain the problem I'm having. The screen doesn't turn on or respond to touch inputs. If I squeeze the phone's sides hard enough, I can get the screen to come on. Soon as I let up, it goes dark. Keys still light up, though. If I do anything with the keys, it doesn't show up on the screen. I have no idea how to get past this.
I am on stock HTC firmware now. I completely reflashed the entire phone with the 2.1 utility. That is, before it randomly stopped working.
After USB debugging is enabled, I can just pull the entire system directory, no? No need for nandroid or anything?
cracked screen
Hey guys My screen is being repaired for the next couple days and I reallly need to check my text messages....Can I get more clearification on what you guys are tallking about because im lost but Im up for anything as long as I can see my texts,
I don't know if it's possible to do this, but it's worth a try. Have you heard of "Air Droid"? It allows you to interface with your phone via a WiFi connection. If you can download an apk file of Air Droid, then flash it to your phone, you might be able to run it. Although your screen digitizer isn't working, your trackball can still select screen items. If it works, you can do a connect to WiFi, see the code, then use the browser interface. I think through that you can access data on the phone, including text messages.
Also, there are some apps that perform SMS to email. You could theoretically have your text messages sent to your email account.
Hi all.
Looking for some insight and help. I've had an unfortunate situation with my Moto X. I went to the store to buy my son a toy, and for whatever reason the price was not coming up correctly. I ended up taking a picture of the price and when I showed the older lady working the register, she grabbed my phone from my hand and proceeded to drop it, shattering the screen. She was old, and more upset about it that I was. I told her not to worry about it and went on my way. The screen and digitizer still worked at this point, but I didn't bother trying to recover my files. After a day, everything just stopped working. Doh!
Now I can get the phone into fastboot mode, and adb sideload even though I can't see the screen. I believe USB debugging is off. I really would like the pictures off the phone, of the first 6-7 months of my sons life. So here are my question:
Does the Moto X display the screen via hdmi without any interaction with the screen? Can it simultaneously use a mouse as well with the right dongle?
Does Mofo require usb debugging, and if not, can I load a rom via fastboot/mofo that would allow access to the sdcard?
Those are the only 2 options I can think of that may work, but not exactly sure.
Thanks for any help!
Are they auto backed up to Google+ Photos?
cal196 said:
Those are the only 2 options I can think of that may work, but not exactly sure.
Click to expand...
Click to collapse
When you turn the phone on and connect it to your computer does your computer recognize the phone? Do you have Motorola Device Manager installed on your computer?
chrisrozon said:
Are they auto backed up to Google+ Photos?
Click to expand...
Click to collapse
They are not unfortunately.
JulesJam said:
When you turn the phone on and connect it to your computer does your computer recognize the phone? Do you have Motorola Device Manager installed on your computer?
Click to expand...
Click to collapse
Yes and Yes. I have everything set up on the computer and can get a response from fastboot devices. I can get the phone into recovery as well and put it into sideload mode in adb. I already have a 2nd Moto X that I am using to show me the exact volume down up button pushes I need to get me where I'm going.
cal196 said:
Yes and Yes. I have everything set up on the computer and can get a response from fastboot devices. I can get the phone into recovery as well and put it into sideload mode in adb. I already have a 2nd Moto X that I am using to show me the exact volume down up button pushes I need to get me where I'm going.
Click to expand...
Click to collapse
Why don't you just turn the phone on regularly and plug the phone into your computer - you should see the internal storage. The pictures you took with your camera are in the DCIM/camera folder.
Can you see the pictures that way? If so, try to copy the pictures to your computer.
JulesJam said:
Why don't you just turn the phone on regularly and plug the phone into your computer - you should see the internal storage. The pictures you took with your camera are in the DCIM/camera folder.
Can you see the pictures that way? If so, try to copy the pictures to your computer.
Click to expand...
Click to collapse
I checked with my working Moto X, and it requires that you unlock it at least once before it shows up as internal storage. I have a pattern passlock on the broken phone.
cal196 said:
I checked with my working Moto X, and it requires that you unlock it at least once before it shows up as internal storage. I have a pattern passlock on the broken phone.
Click to expand...
Click to collapse
If you can get into recovery, then you may be able to do an adb pull of the /sdcard/DCIM/Camera folder.
adb pull /sdcard/DCIM/Camera
If it works, that would leave all of the photos in the directory where you have navigated to in the command prompt.
But I am not sure if you can pull if you have pattern passlock on the broken phone. If you could, that would make the pattern passlock worthless. All you can do is try.
If you can't access the phone, then take it to a repair shop and pay to have them extract the photos if the photos are that important to you. I am sure they can either fix the screen to enable you to enter your pattern or they may have a way to bypass those passlocks to pull the files.
If there were some easy way to bypass the pattern passlocks, then they would be worthless so I doubt you will be able to get anything off of that phone without either paying to fix the screen or paying a repair shop to use equipment to bypass the passlock.
JulesJam said:
If you can get into recovery, then you may be able to do an adb pull of the /sdcard/DCIM/Camera folder.
adb pull /sdcard/DCIM/Camera
If it works, that would leave all of the photos in the directory where you have navigated to in the command prompt.
But I am not sure if you can pull if you have pattern passlock on the broken phone. If you could, that would make the pattern passlock worthless. All you can do is try.
If you can't access the phone, then take it to a repair shop and pay to have them extract the photos if the photos are that important to you. I am sure they can either fix the screen to enable you to enter your pattern or they may have a way to bypass those passlocks to pull the files.
If there were some easy way to bypass the pattern passlocks, then they would be worthless so I doubt you will be able to get anything off of that phone without either paying to fix the screen or paying a repair shop to use equipment to bypass the passlock.
Click to expand...
Click to collapse
Thanks for your suggestions. I was just able to solve my own problem. I ordered an OTG cable and plugged in a wireless mouse. I practiced a few times with my other phone, and then tried with the broken phone and was able to get the passlock on the 2nd try, unlocking the phone, and allowing the media drive to show up after plugging into my computer. I pulled my photos and all is good.
Thanks again
cal196 said:
Thanks for your suggestions. I was just able to solve my own problem. I ordered an OTG cable and plugged in a wireless mouse. I practiced a few times with my other phone, and then tried with the broken phone and was able to get the passlock on the 2nd try, unlocking the phone, and allowing the media drive to show up after plugging into my computer. I pulled my photos and all is good.
Thanks again
Click to expand...
Click to collapse
Ok so then after you unlocked it, you were able to just copy using the copy function of your PC or did you have to use adb?
JulesJam said:
Ok so then after you unlocked it, you were able to just copy using the copy function of your PC or did you have to use adb?
Click to expand...
Click to collapse
Yes, after unlocking the drive shows up on my PC. :good:
So long story short my Nexus 6 got ran over by a car (maybe multiple...) screen is shattered into a million pieces and completely black. I'm just hoping to try and recover my pictures off of the phone. I am able to boot into the bootloader by holding down the volume/power buttons and my computer will recognize it fine, and everything seems to work from there. TWRP seems to flash successfully but when I try to boot into it weird things happen. Basically if left alone I will hear my computer keep chiming that my phone is connecting in adb mode, then losing connection, and cycling like this every 15 seconds or so. The adb devices command usually lists the the device as attached, but sometimes with the "offline" or "unauthorized" tag. In addition to this, any commands like adb pull or adb shell give me "error: protocol fault (couldn't read status): No error".
Again, the phone will be stable in fastboot, but keep dropping and reconnecting in adb.
Earlier today I was brainstorming how I was gonna hack the NAND chip out of the phone, but was delighted when I got home from work and it actually connected through fastboot. Now just hoping I can actually recover my data. Any ideas?
Never set Google to back up photos?
Sent from my Nexus 6 using XDA Free mobile app
leetonion said:
So long story short my Nexus 6 got ran over by a car (maybe multiple...) screen is shattered into a million pieces and completely black. I'm just hoping to try and recover my pictures off of the phone. I am able to boot into the bootloader by holding down the volume/power buttons and my computer will recognize it fine, and everything seems to work from there. TWRP seems to flash successfully but when I try to boot into it weird things happen. Basically if left alone I will hear my computer keep chiming that my phone is connecting in adb mode, then losing connection, and cycling like this every 15 seconds or so. The adb devices command usually lists the the device as attached, but sometimes with the "offline" or "unauthorized" tag. In addition to this, any commands like adb pull or adb shell give me "error: protocol fault (couldn't read status): No error".
Again, the phone will be stable in fastboot, but keep dropping and reconnecting in adb.
Earlier today I was brainstorming how I was gonna hack the NAND chip out of the phone, but was delighted when I got home from work and it actually connected through fastboot. Now just hoping I can actually recover my data. Any ideas?
Click to expand...
Click to collapse
first off, fastboot only connects to the device in the bootloader mode. ADB NEVER EVER connects to the device when in the bootloader. that sound you are probably hearing isnt "adb" connecting, but just the sound you hear when you connect to the computer.
I know, just didn't word it right. The chime from my computer is just it recognizing the phone, but it coincides with adb losing connection and (I'm assuming) my phone crashing or rebooting somehow...I just need some way to pull files from the sdcard folder and adb doesn't seem to work in my current situation.
If you are lucky and the mobile boot into system then try this http://www.vysor.io/
Sent from my Nexus 6 using Tapatalk
AhmadOkda said:
If you are lucky and the mobile boot into system then try this http://www.vysor.io/
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Interesting app ya linked to, but wouldn't he need to be able to install the app on the device before he would be able to see it on his desktop? Just asking because it said available on Google Play.
Sent from my Nexus 6 using XDA Free mobile app
leetonion said:
So long story short my Nexus 6 got ran over by a car (maybe multiple...) screen is shattered into a million pieces and completely black. I'm just hoping to try and recover my pictures off of the phone. I am able to boot into the bootloader by holding down the volume/power buttons and my computer will recognize it fine, and everything seems to work from there. TWRP seems to flash successfully but when I try to boot into it weird things happen. Basically if left alone I will hear my computer keep chiming that my phone is connecting in adb mode, then losing connection, and cycling like this every 15 seconds or so. The adb devices command usually lists the the device as attached, but sometimes with the "offline" or "unauthorized" tag. In addition to this, any commands like adb pull or adb shell give me "error: protocol fault (couldn't read status): No error".
Again, the phone will be stable in fastboot, but keep dropping and reconnecting in adb.
Earlier today I was brainstorming how I was gonna hack the NAND chip out of the phone, but was delighted when I got home from work and it actually connected through fastboot. Now just hoping I can actually recover my data. Any ideas?
Click to expand...
Click to collapse
Does your Nexus have root access?
31ken31 said:
Interesting app ya linked to, but wouldn't he need to be able to install the app on the device before he would be able to see it on his desktop? Just asking because it said available on Google Play.
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
I tested dot on my mobile
You only need usb debugging enabled and it will install itself with no action from my side
Sent from my Nexus 6 using Tapatalk
You can do adb commands in recovery. if you can get into recovery you should be good to go.
Miss read OP. Thought you were trying to boot normal and not boot into recovery.
leetonion said:
I know, just didn't word it right. The chime from my computer is just it recognizing the phone, but it coincides with adb losing connection and (I'm assuming) my phone crashing or rebooting somehow...I just need some way to pull files from the sdcard folder and adb doesn't seem to work in my current situation.
Click to expand...
Click to collapse
To help troubleshoot, try holding down power when you think it has booted to feel for a vibration. If it vibrates you know it booted. From there you may need to enter a password through adb (there are guides, I can't remember of f the top of my head how). Once you are in, you can use this to help navigate your phone http://forum.xda-developers.com/showthread.php?t=2786395. There's a learning curve and high latency but, it works. I have been in a similar situation and I was able to pull it off using this method.
As far as it rebooting or crashing, or whatever else, there's not much I can do to help with that across the internet, good luck to you.
And one last thing, try playing with this. http://www.pocketables.com/2014/10/using-twrps-new-adb-interface.html Looks like you can control TWRP through a command prompt, maybe you can get your files.
And one last, last thing. When in the bootloader menu, the options go like this. You cna also get into these optiosn through fastboot but, I figured it couldn't hurt.
START <--- First option you boot into. If you are holding it's possible to go down one extra though, be careful.
RESTART BOOTLOADER
RECOVERY MODE
POWER OFF
FACTORY MODE
BARCODES
BP TOOLS
QCOM
BOOTLOADER LOGS