Database Users

[Q] Webtop without dock

Hi I am new to this forum and I'm not an expert, I really would like to use the webtop without a dock,i tried following the instructions posted here but nothing happens, I don't know what am I missing. Am I supposed to run the install file on my computer or on my phone? When I run it on my computer a black screen appears and some command and then I says to press any key and that my phone will reboot, but nothing happens. Am I supposed to do something to my phone?
I'm on att gingerbread, not rooted, I enabled debugging mode.
Thank you

You need to root and probably deodex
sent from my Atrix via XDA premium

You are probably right, but why then on Fenny's post it says no root or deodex needed??
http://forum.xda-developers.com/showthread.php?t=980193

oh well look at that,
you run the script from your computer but your phone has to be connected and have all the right drivers on your computer
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Can you please be a little more specific, I have the drivers for motorola media link and the phone portal, also for usb connection.

do you know what ADB is and how to use it?

No. I don't know... I just enabled the debugging mode on my phone

clastrag said:
No. I don't know... I just enabled the debugging mode on my phone
Click to expand...
Click to collapse
ok connect your phone to hyhour computer and make sure the computer knows it is connected
then run the script

good advice
If I were you I'd be VERY CAREFUL and investigate and learn all you can BEFORE doing any mods on your phone. Too many phones have been bricked (rendered useless) by running things you know little about.

I did that but the doesn't do anything, it doesn't reboot like it says on the script. I know it's connected because when I enable debugging I see the pop up screen for the internal memory and the sd card

Thanks for your concern I really appreciate it.what I like about this is that doesn't require root

Root
Hi
I also had exactly the same problem.
I wanted webtop, without really rooting my device.
It didnt work out. Also ran the script no reboot etc.
I then rooted my device, Fenny assisted me to create 2 files for the stock 2.2.2 atrix 4g (The older version of the os)
I copied them manually using root explorer, rebooted, and walla, i had the webtop working.
I still have those files.....
If you need them, PM me, its worth a try...

Stuck at bootscreen

Okay, I am new to the rooting and modifying android devices.. I rooted my Nexus 7 using supersu and was making modifications with ROM toolbox pro. I changed the boot screen, the font, and the wireless icon(starting out small) well when I restarted my tablet it wouldn't get past the lboot screen that I set to.
When I went into recovery mode, I tried to recovery my old system but it giving me md5 missing.. so I'm kinda of stuck
is there a direct approach to the solution?

Nice tip. Only use stuff like mods tha are on xda. Use metamorph to impalement theming stuff or flashable zips. Regaurds your situation ty flashing the rom again. Wipe data factory reset. If all else fails flash the google factory image and learn from your mistakes you made. Most problems you get in the future are pretty easily fixed with a bit of patience
Sent from my Nexus 7 using Tapatalk 2

leelaa said:
Nice tip. Only use stuff like mods tha are on xda. Use metamorph to impalement theming stuff or flashable zips. Regaurds your situation ty flashing the rom again. Wipe data factory reset. If all else fails flash the google factory image and learn from your mistakes you made. Most problems you get in the future are pretty easily fixed with a bit of patience
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
I was afraid you were going to say that.. alright thank you, I will try this a soon as possible and report back.

Hohokam337 said:
I was afraid you were going to say that.. alright thank you, I will try this a soon as possible and report back.
Click to expand...
Click to collapse
Okay so wiping the data/factory reset didn't work, how do i go about flashing the google factory image?

http://forum.xda-developers.com/showthread.php?t=1907796
Sent from my Nexus 7 using xda app-developers app

http://forum.xda-developers.com/sho...Factory Image with fastboot / return to stock
Sent from my Galaxy Nexus using Tapatalk 2

Now i am running into this error with the command prompt..
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Move your android folder to the C: Drives root folder and try directing the command prompt from there.
Type :-
cd c:\Android\android-sdk\platform-tools
adb

mr_tris said:
Move your android folder to the C: Drives root folder and try directing the command prompt from there.
Type :-
cd c:\Android\android-sdk\platform-tools
adb
Click to expand...
Click to collapse
Got it,
Thank you all for the help

[Q] Unable to reboot to Recovery

I'm unable to boot into recovery after flashing the [JB 4.2] - CleanROM 2.5 rom. The ROM has horrible performance issue and I'm unable to flash a different ROM now. I have try going to reocvery by press & hold volume up+down and power button to go into bootloader (which works) and when I go to recovery mode I get the following screen. I get the same screen when doing it with ADB (adb reboot recovery).
Any help will be greatly appreciated. Thanks
UPDATE: I also noticed that this ROM has changed my folder structure. All the folders used to be stored in /sdcard/ directory. Now it keeps moving ALL my folders into a /sdcard/0/ and android auto populates new folders. it did it twice and now my folder and files are located in /sdcard/0/0/. Any fix to this?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

What are you talking about?
That IS the recovery screen.

GldRush98 said:
What are you talking about?
That IS the recovery screen.
Click to expand...
Click to collapse
LMAO!

The stock recovery, yes. You need to use goomanager or rom manager to reinstall the custom recovery. At which time you should be able to put things back together.
Sent from my Nexus 7 using Tapatalk 2

DDeveryday said:
I'm unable to boot into recovery after flashing the [JB 4.2] - CleanROM 2.5 rom. The ROM has horrible performance issue and I'm unable to flash a different ROM now. I have try going to reocvery by press & hold volume up+down and power button to go into bootloader (which works) and when I go to recovery mode I get the following screen. I get the same screen when doing it with ADB (adb reboot recovery).
Any help will be greatly appreciated. Thanks
UPDATE: I also noticed that this ROM has changed my folder structure. All the folders used to be stored in /sdcard/ directory. Now it keeps moving ALL my folders into a /sdcard/0/ and android auto populates new folders. it did it twice and now my folder and files are located in /sdcard/0/0/. Any fix to this?
Click to expand...
Click to collapse
The ROM did not change your file structure. It is the 4.2 update that does that. Doesn't matter stock or custom ROM you are gong to get the new file structure.
Clean ROM may have killed performance for you, but you have something else going on because Clean ROM is working great for many many users.
As for your growing 0 folders you need to update your recovery to stop that from happening.
Sent from my Nexus 7 using xda premium

[Q] ADB connection problem - Device Offline

This is weird. I never had this problem with my Galaxy S3.
I've enabled USB Debugging on the phone.
Even toggled it off, rebooted and turned it on again.
I've also rebooted my computer and even updated SDK Toolkit.
No change in problem though.
Every time I try to connect to my phone from ADB, it just tells me the device is offline (see attached pic).
Any ideas?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Mine said that also one time before I accepted the adb connection on the phone
Sent from my A500 using Tapatalk HD

StolenVW said:
Mine said that also one time before I accepted the adb connection on the phone
Sent from my A500 using Tapatalk HD
Click to expand...
Click to collapse
I'm not getting any popup for that.

CZ Eddie said:
I'm not getting any popup for that.
Click to expand...
Click to collapse
Try this
http://www.wugfresh.com/faqs/how-to-fix-adb-device-is-listed-as-offline-on-android-4-2-2/
And if you do a Google search for
how to fix adb device offline
It comes up with other things to try
Sent from my A500 using Tapatalk HD

Thanks, I tried the info in that link but never got the pop-up asking for ADB permissions.
I did google prior to posting also. I listed in my OP what I tried (which is what my googling suggested).
I'm about to ODIN back to factory stock anyways. So I'll try again after that. Maybe I messed something up during all the bloatware removal I did yesterday.

Nope, a fresh ODIN install of stock ROM didn't help at all.
Guess I'll have to uninstall & reinstall Android Toolkit maybe.
EDIT:
Using Motochopper root tool, I finally got the popup. And made sure to select "always allow from this computer". I think that should fixit.
EDIT #2:
Nope, that didn't help at all. Still "offline".
EDIT #3:
Actually, using the ADB from Motochopper does work. It's just the ADB from my Android Toolkit that doesn't work.

Sounds like one in android tool kit is out of date
Try updating the android sdk
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2

[Q] ADB: Device Unauthorized Error

Hello,
I just recently purchased a new Samsung Galaxy Note 3 (N900T) and I am having problems with adb. Whenever I launch adb shell .... It says "Error: Device Unauthorized. Please Check the confirmation dialog on your device." However, this is no confirmation dialog. There has never been one. I do have USB Debugging Enabled, and I have tried disabling it and re-enabling it and it still does not ask me to authorize the device on my phone. I have also restarted the phone, and the computer. Nothing seems to work, and I can not use adb due to this issue.
There is also no "adb_key" file located in /data/misc/adb/ or in the .android folder on my pc.
Can anyone tell me how to authorize my device so I can use adb?

Hi.
Don't know if you found an answer on your problem but I have an Note 3 SM-N9005 an what i have done was to delete the adb folder in /data/misc and then the authorise popup poped up assoon as i plugged my phone into the pc. But just extra info on adb If you want to use adb debugging shell on pc, get the latest version from goolge.
Hope this helped. This worked for me.

how if phone on bootloop, so we can't see pop up confirmation.
any idea?

Clear Auth first, then retry.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my leanKernel 3.2 powered stock 4.4.2 (NF1) SM-N900T

toastido said:
Clear Auth first, then retry.
Sent from my leanKernel 3.2 powered stock 4.4.2 (NF1) SM-N900T
Click to expand...
Click to collapse
i repeat, how if phone on bootloop, so we can't see pop up confirmation.
just stuck at logo.

monkey_kungfu said:
i repeat, how if phone on bootloop, so we can't see pop up confirmation.
just stuck at logo.
Click to expand...
Click to collapse
This has nothing to do with adb. i wasn't even replying to you, i was replying to OP, so lose the attitude.
Edit: i now see this was an old thread. That's what you get for posting in a dead thread.
Sent from my leanKernel 3.3 powered stock 4.4.2 (NF1) SM-N900T

oh... i'm so sorry.
can u help me, with that my problem?
edit : i just want a solution

Instruction with Windows PC:
1. Make a copy from C:\Users\User\.android\adbkey.pub
2. Rename it to adb_keys
3. Paste it in your smartphone under /data/misc/adb/adb_keys
4. Restart the smartphone and adb with "adb kill-server" and "adb start-server"