Related
I need some help installing amon_ra's recovery. In adb it states I don't have permission to push files. If I try to run a fastboot it states I don't have permission. How can I get the above mentioned recovery on this phone ?
timal said:
I need some help installing amon_ra's recovery. In adb it states I don't have permission to push files. If I try to run a fastboot it states I don't have permission. How can I get the above mentioned recovery on this phone ?
Click to expand...
Click to collapse
You should ask this in the thread that already exists.
If you follow every step listed, that won't happen. Do not skip any steps.
Do not skip any steps
1. Boot the device in fastboot mode, hold down the back button while powering on.
2. Connect via USB.
3. "fastboot boot recovery-RAv1.1.1H.img"
It will reboot into the custom fastboot with a black background. Then you'll be set to do these commands:
adb shell mount -a
Ignore the the errors...
adb push recovery-RAv1.1.1H.img /system/recovery.img
adb push recovery-RAv1.1.1H.img /sdcard/recovery-RAv1.1.1H.img
adb shell flash_image recovery /sdcard/recovery-RAv1.1.1H.img
adb shell reboot
I would have tried all that except the adb drivers are not working with the magic on windows vista. Device manager only shows Android 1.0
timal said:
I would have tried all that except the adb drivers are not working with the magic on windows vista.
Click to expand...
Click to collapse
they work fine, you just need to properly install them.
k4r1m said:
they work fine, you just need to properly install them.
Click to expand...
Click to collapse
Device manager only shows Android 1.0 Which I installed from the most recent sdk. Adb only will show 'waiting for device' even when I try to boot the recovery before flashing.
timal said:
Device manager only shows Android 1.0 Which I installed from the most recent sdk. Adb only will show 'waiting for device' even when I try to boot the recovery before flashing.
Click to expand...
Click to collapse
Switch to Linux ... nah just kidding... you obviously have a driver "issue", it happens to many people using Micro$oft Vi$ta...
Perform the following steps (do not skip any steps) on Vista :
1. Make sure your phone is not connected via usb
2. Download USBdeview and run it as admin (it's very important to run it as admin otherwise you will be unable to uninstall!).
3. Uninstall all drivers that mention Android in the device name or description.
4. Make sure that USB debugging is enabled in your phone (Settings - Applications - Development - USB debugging).
5. Connect your phone via usb.
6. Vista will now look for drivers, point it to the sdk drivers and make sure it uses those.
7. Check with "adb devices" to see if your phone listed.
Amon_RA said:
Switch to Linux ... nah just kidding... you obviously have a driver "issue", it happens to many people using Micro$oft Vi$ta...
Perform the following steps (do not skip any steps) on Vista :
1. Make sure your phone is not connected via usb
2. Download USBdeview and run it as admin (it's very important to run it as admin otherwise you will be unable to uninstall!).
3. Uninstall all drivers that mention Android in the device name or description.
4. Make sure that USB debugging is enabled in your phone (Settings - Applications - Development - USB debugging).
5. Connect your phone via usb.
6. Vista will now look for drivers, point it to the sdk drivers and make sure it uses those.
7. Check with "adb devices" to see if your phone listed.
Click to expand...
Click to collapse
Thank you I tried all the above. Long story short brick, no power dead . This hobbie is getting expensive.
hello, can i root my official 2.3.3 optimus one with gingerbreak from this thread http://forum.xda-developers.com/showthread.php?t=1044765 ? i mean will it work? If not is where any simple ways to do what?
Can i root 2.3.3 with gingerbreak ?
Click to expand...
Click to collapse
no
How to root LG Optimus One P500 on gingerbread 2.3.3
1. Be sure that you have installed the original V20 GB ROM
2. if you have it installed and tried different methods to root on it do a factory reset before trying this one
3. Be absolutely sure that you have all the phone-drivers installed when working with the phone in USB debugging mode, if not install them (http://www.mediafire.com/file/t3gvrb6345yay99/LGUnitedMobileDriver_S497MA20_WHQL_ML_Ver_1.0.msi)
4. Download SuperOneClickv1.9.5-ShortFuse (http://forum.xda-developers.com/attachment.php?attachmentid=624175&d=1307984755), after download extract the files into a folder with the same name as the archive.
5. After you extracted the files, go to C:\Windows\System32 and copy the cmd.exe to the folder where you extracted the files, in my case C:\Users\myuser\Desktop\SuperOneClickv1.9.5-ShortFuse\ADB.
6. Enter the phone settings menu, to the Development and tick the USB debugging mode. Connect the USB cable to the phone, wait until it recognizes it
7. right click on cmd.exe from the ADB folder, Run as administrator, than write:
adb devices
adb shell
echo 1 > /data/local/lge_adb.conf (do not close the window)
8. Leave the settings to the SuperOneClick as they are when it opens, click on ROOT and wait, it will say Starting ADB server..., than it will do it's job and than it will appear Waiting for device... it will say ok --- if it freezes while running psneuter do the following:
a. Turn USB Debugging OFF wait until it will appear in the window again Starting ADB server..., after that,
b. Turn USB Debugging ON, and after this trick it will start rooting.
rockvoid said:
no
How to root LG Optimus One P500 on gingerbread 2.3.3
1. Be sure that you have installed the original V20 GB ROM
2. if you have it installed and tried different methods to root on it do a factory reset before trying this one
3. Be absolutely sure that you have all the phone-drivers installed when working with the phone in USB debugging mode, if not install them (http://www.mediafire.com/file/t3gvrb...ML_Ver_1.0.msi)
4. Download SuperOneClickv1.9.5-ShortFuse (http://forum.xda-developers.com/atta...5&d=1307984755), after download extract the files into a folder with the same name as the archive.
5. After you extracted the files, go to C:\Windows\System32 and copy the cmd.exe to the folder where you extracted the files, in my case C:\Users\myuser\Desktop\SuperOneClickv1.9.5-ShortFuse\ADB.
6. Enter the phone settings menu, to the Development and tick the USB debugging mode. Connect the USB cable to the phone, wait until it recognizes it
7. right click on cmd.exe from the ADB folder, Run as administrator, than write:
adb devices
adb shell
echo 1 > /data/local/lge_adb.conf (do not close the window)
8. Leave the settings to the SuperOneClick as they are when it opens, click on ROOT and wait, it will say Starting ADB server..., than it will do it's job and than it will appear Waiting for device... it will say ok --- if it freezes while running psneuter do the following:
a. Turn USB Debugging OFF wait until it will appear in the window again Starting ADB server..., after that,
b. Turn USB Debugging ON, and after this trick it will start rooting.
Click to expand...
Click to collapse
Thanks, what was very informative, much more informative than i have found superoneclick instructions with google. Thanks again
rockvoid said:
no
How to root LG Optimus One P500 on gingerbread 2.3.3
1. Be sure that you have installed the original V20 GB ROM
2. if you have it installed and tried different methods to root on it do a factory reset before trying this one
3. Be absolutely sure that you have all the phone-drivers installed when working with the phone in USB debugging mode, if not install them (http://www.mediafire.com/file/t3gvrb...ML_Ver_1.0.msi)
4. Download SuperOneClickv1.9.5-ShortFuse (http://forum.xda-developers.com/atta...5&d=1307984755), after download extract the files into a folder with the same name as the archive.
5. After you extracted the files, go to C:\Windows\System32 and copy the cmd.exe to the folder where you extracted the files, in my case C:\Users\myuser\Desktop\SuperOneClickv1.9.5-ShortFuse\ADB.
6. Enter the phone settings menu, to the Development and tick the USB debugging mode. Connect the USB cable to the phone, wait until it recognizes it
7. right click on cmd.exe from the ADB folder, Run as administrator, than write:
adb devices
adb shell
echo 1 > /data/local/lge_adb.conf (do not close the window)
8. Leave the settings to the SuperOneClick as they are when it opens, click on ROOT and wait, it will say Starting ADB server..., than it will do it's job and than it will appear Waiting for device... it will say ok --- if it freezes while running psneuter do the following:
a. Turn USB Debugging OFF wait until it will appear in the window again Starting ADB server..., after that,
b. Turn USB Debugging ON, and after this trick it will start rooting.
Click to expand...
Click to collapse
wait i need ADB for this instaled on pc right?
adb is included in superoneclick zip-file.
just extract zip-file and you have adb...
Teraman said:
hello, can i root my official 2.3.3 optimus one with gingerbreak from this thread http://forum.xda-developers.com/showthread.php?t=1044765 ? i mean will it work? If not is where any simple ways to do what?
Click to expand...
Click to collapse
http://www.lg-p500.ru/2011/06/root-android-233.html - got root on original rom with no problem. You can translate it on Google translate if russian language is not for you Sorry for English - rules forbid me to write here in Lithuanian
rockvoid said:
no
How to root LG Optimus One P500 on gingerbread 2.3.3
1. Be sure that you have installed the original V20 GB ROM
2. if you have it installed and tried different methods to root on it do a factory reset before trying this one
3. Be absolutely sure that you have all the phone-drivers installed when working with the phone in USB debugging mode, if not install them (http://www.mediafire.com/file/t3gvrb...ML_Ver_1.0.msi)
4. Download SuperOneClickv1.9.5-ShortFuse (http://forum.xda-developers.com/atta...5&d=1307984755), after download extract the files into a folder with the same name as the archive.
5. After you extracted the files, go to C:\Windows\System32 and copy the cmd.exe to the folder where you extracted the files, in my case C:\Users\myuser\Desktop\SuperOneClickv1.9.5-ShortFuse\ADB.
6. Enter the phone settings menu, to the Development and tick the USB debugging mode. Connect the USB cable to the phone, wait until it recognizes it
7. right click on cmd.exe from the ADB folder, Run as administrator, than write:
adb devices
adb shell
echo 1 > /data/local/lge_adb.conf (do not close the window)
8. Leave the settings to the SuperOneClick as they are when it opens, click on ROOT and wait, it will say Starting ADB server..., than it will do it's job and than it will appear Waiting for device... it will say ok --- if it freezes while running psneuter do the following:
a. Turn USB Debugging OFF wait until it will appear in the window again Starting ADB server..., after that,
b. Turn USB Debugging ON, and after this trick it will start rooting.
Click to expand...
Click to collapse
whese links are broken
Teraman said:
whese links are broken
Click to expand...
Click to collapse
sorry... fixed it in my 1st post...
usb drivers: http://www.mediafire.com/file/t3gvrb6345yay99/LGUnitedMobileDriver_S497MA20_WHQL_ML_Ver_1.0.msi
superoneclick: http://forum.xda-developers.com/attachment.php?attachmentid=624175&d=1307984755
rooted successfully
rockvoid, milion thanks to you
tried same with my p500 v20c but it keeps getting stuck in the psneuter running thing. tried turning debugg off and on and rebooting device between tries but not getting anywhere i guess i'll have to wait for something else to come by unless theres any other way but i've looked everywhere and there isnt
have you done the following, without getting an error?
adb devices
adb shell
echo 1 > /data/local/lge_adb.conf (do not close the window)
Click to expand...
Click to collapse
I did but not that exact way i put em just with the spaces in between them. does it matter? me and dos don't really get along lol
enobano said:
I did but not that exact way i put em just with the spaces in between them. does it matter? me and dos don't really get along lol
Click to expand...
Click to collapse
you must type it exactly.... with "enter-key" after every line...
adb devices (enter-key)
adb shell (enter-key)
echo 1 > /data/local/lge_adb.conf (enter-key)
done in 10 seconds thanks a lot mate. crystal clear advice.
by the way is busybox obligatory after root or is it ok without? i see in most of those tutorials they say to install it.
thanks again man
Hi, I succesfuly rooted my P500 with these instructions, however after reboot it seems that rooting was lost. Did I miss something for making the rooting permamanent?
> Never mind it seems there was a glitch in an app getting root rights, it's working fine
enobano said:
by the way is busybox obligatory after root or is it ok without? i see in most of those tutorials they say to install it.
thanks again man
Click to expand...
Click to collapse
no it´s not obligatory.. it´s optional
still not rootin
Crashing
Hy, i think i rooted my phone ,because i followed the steps you posted and i didn't get any errors , but when i try to run different apps like titanium backup or rom manager super user crashes,not even the fix permissions in rom manager will fix it.any ideas ? oh and i was talikn on my phone and it reboted directly from the android loading screen..what do you think? root problem or phone glitch.thanx in advance
My screen first cracked and then the LCD completely went now... I have files I need to retrieve off the phone. It is rooted and running some ICS build... I believe the phone is in USB debugging mode, the screen still 'works' I can unlock the phone but nothing is displayed on the screen. Possibly someone could help me out with the adb process for pulling the contents off the /sd
Any help will be GREATLY appreciated, thank you for your time.
ur usb mass storage should still work. can u just plug ur phone to a usb port and get things off the phone ?
As previously stated. I believe the phone was in USB debugging mode. And now the screen is completely black... impossible to navigate to where i need to be.
You'll need adb setup on your computer, and you'll need to cd your way into the folder with adb.exe. Forgive me for hotlinking, but this will make it easier: Download this file, courtesy of NexusSHacks.com (I believe it is Zedomax around here). I would advise to unzip the contents in this file to your C:\Nexus directory, so that adb.exe is at C:\Nexus\adb.exe.
Now, plug in your phone. Open your start menu and search for "cmd" and open up Command Prompt. This is the basic Windows CLI (Command Line Interface).
First, you'll need to open the directory of the Nexus folder you created earlier. To do this, type in the command prompt:
Code:
cd C:\Nexus
Now, you want to make sure adb sees your phone:
Code:
adb devices
The adb service should start and if it sees your phone it will pop up a serial number. If there is no serial number, you can't use adb while inside android and you'll need to tick the option or find an alternative way. Assuming it finds your device, you are good to go.
In order to copy the /sdcard folder of your Nexus S, you will use the pull command. We will throw all of the files into C:\Nexus\sdcard, for reference. So in the command prompt, type:
Code:
adb pull /sdcard .\sdcard
It looks a little confusing but don't stress. Just make sure you type it in exactly (dot, correct slash, etc). This will take a little while since it might transfer up to ~15GB worth. You'll see a new line with "C:\Nexus>" with a flashing cursor when it is done. Then you can view all the contents of your sdcard at C:\Nexus\sdcard and do with them as you please.
Also note, for this you'll need up to ~15GB of free space on your C:\ partition, make sure you have this before you start. Good luck
old post I know, but I just dropped my Samsung Captivate (rooted with debugging on) and internal screen cracked (gorilla glass is perfectly fine!), so I am in the same boat. After DAYS... actually DAYS of trying everything from every forum I FOUND A FIX!!!
Now admittedly, I am unsure which of these two (or both) fixed the issue, but here is what I did:
via Google Play's online "shop", I installed "Auto Mount Your SD Card" by JRTStudio (admittingly, unsure if this did anything as I cannot verify if it installed or anything via the phone)
https://play.google.com/store/apps/...wsMSwxLDEsImNvbS5qcnRzdHVkaW8uYXV0b21vdW50Il0.
then I DL'ed MoboRobo and after a few frustrated phone reboots, usb cable connections and much cursing IT CONNECTED!
http://www.moborobo.com/
I am currently DLing all my files from my broken phone!
I had to pass this along as I said... NOBODY seems to know about this as it has taken me DAYS to do this! Not even ATT (Current carrier) nor Spring (whom I am switching to in a month or so) could help me!
You save my life with that "moborobo". Thank you very much.
Glad I could help!!!
Thanks went to both of u, quit important piece of knowledge.
One question; r u downloading "moborobo" on ur Android, on your pc or on both of them?
just on PC, not needed on the phone unless you want to go via WiFi
Harbb said:
If there is no serial number, you can't use adb while inside android and you'll need to tick the option or find an alternative way.
Click to expand...
Click to collapse
What do you mean by this?
My adb service doesn't detect my phone, I used Droidzone's tutorial. I believe usb debugging needs to be on for adb to work, which in my case is useless cause my screen is broken so can't turn on usb debugging.
This is what happens:
---------------------------
C:\>adb devices
List of devices attached
C:\>
---------------------------
---------- Post added at 11:31 PM ---------- Previous post was at 11:23 PM ----------
^when I say broken, I mean the whole screen is distorted, I cannot see anything
droidoidoid said:
What do you mean by this?
My adb service doesn't detect my phone, I used Droidzone's tutorial. I believe usb debugging needs to be on for adb to work, which in my case is useless cause my screen is broken so can't turn on usb debugging.
This is what happens:
---------------------------
C:\>adb devices
List of devices attached
C:\>
---------------------------
---------- Post added at 11:31 PM ---------- Previous post was at 11:23 PM ----------
^when I say broken, I mean the whole screen is distorted, I cannot see anything
Click to expand...
Click to collapse
Reboot to recovery. Bam, working ADB. You can navigate there pretty easily. Pull battery, then re-insert. VOL + & PWR, two click on VOL -, PWR button once. You're in recovery now.
QtADB also can be used is this case
http://qtadb.wordpress.com/download/
paskalion said:
QtADB also can be used is this case
http://qtadb.wordpress.com/download/
Click to expand...
Click to collapse
No go on this either.
Downloaded QtADB, ran the .exe
Pointed to the folder with the aapt and adb binaries, program opened up
Phone's connected and on (I can hear texts coming through), hit refresh a few times, still not detecting
polobunny said:
Reboot to recovery. Bam, working ADB. You can navigate there pretty easily. Pull battery, then re-insert. VOL + & PWR, two click on VOL -, PWR button once. You're in recovery now.
Click to expand...
Click to collapse
That's a little tough. I'm using a Galaxy S so I'm following instructions for that, but it's hard to know if I'm in recovery mode or not. Since adb doesn't detect the device, it's hard to know whether the phone went into recovery mode, or whether adb is setup correctly. It would be handy for a voice sample to play "recovery mode" once the phone boots into it.
droidoidoid said:
That's a little tough. I'm using a Galaxy S so I'm following instructions for that, but it's hard to know if I'm in recovery mode or not. Since adb doesn't detect the device, it's hard to know whether the phone went into recovery mode, or whether adb is setup correctly. It would be handy for a voice sample to play "recovery mode" once the phone boots into it.
Click to expand...
Click to collapse
You're in the wrong forum, then.
And whether or not adb is installed properly, you would know in your device manager under Windows. Appears as a device.
polobunny said:
You're in the wrong forum, then.
And whether or not adb is installed properly, you would know in your device manager under Windows. Appears as a device.
Click to expand...
Click to collapse
Ok... Galaxy S i9000 stuff goes in the Galaxy S i9000 forum.... that's probably why my other post got deleted! :laugh:
As for adb... it appears as a process in task manager, so it's running - I know that much. It's not appearing as a device in device manager (why would it if it's a process? or are you referring to my phone appearing as a device?)
Only areas I can think of that aren't correct are the environment variable and the way I'm doing recovery mode. Since I can't see the screen, I don't know which one is causing the issue! :crying:
Samsung broken??
Contact this guy in Paris , he's very good and friendly!! he repairs my blue Galaxy S3 in front of me
Tel: 0950 850 500 Direct Technique
repare-galaxy com
don't hesitate to call them because i know their skills and it's very good!!
tell them that u call from Mike ciao guys!!
Problem!
Harbb said:
Code:
adb pull /sdcard .\sdcard
It looks a little confusing but don't stress. Just make sure you type it in exactly (dot, correct slash, etc). This will take a little while since it might transfer up to ~15GB worth. You'll see a new line with "C:\Nexus>" with a flashing cursor when it is done. Then you can view all the contents of your sdcard at C:\Nexus\sdcard and do with them as you please.
Click to expand...
Click to collapse
Hey, I got to this problem and I got stuck. I also have a Nexus S with a cracked screen. When I put in the final phrase into the command window it just told me that 0 filles were pulled! Why didnt it pull my files?
What I am trying to do is get all of my pictures and others off the phone.
Please help!
SkullMblem said:
Hey, I got to this problem and I got stuck. I also have a Nexus S with a cracked screen. When I put in the final phrase into the command window it just told me that 0 filles were pulled! Why didnt it pull my files?
What I am trying to do is get all of my pictures and others off the phone.
Please help!
Click to expand...
Click to collapse
This happened to me as well. You have to make sure that your phone has its sdcard folder mounted. Type "adb shell" to get access to the phones command terminal. Then type in "mount /sdcard" I think, or maybe it was "mount sdcard". Either way will probably work so long as you are in the root directory of the phone. You can navigate around in the phone just like a normal linux terminal. "ls" shows list of files and folders in the current directory, "cd foldername" moves into a folder, "cd ../" moves back, "cd /" goes to root directory, etc. Anyhow, once you have mounted the sdcard, you can type exit to leave the shell terminal, and then issue the command "adb pull /sdcard .\sdcard" to get the files. I had a custom rom image in the root of my sdcard so the move took quite a while ~15 minutes. On success of the pull command you should see a bunch of statuses like:
pull: sdcard/data/somefile -> .\sdcard/data/somefile
pull: sdcard/DCIM/somefile -> .\sdcard/DCIM/somefile
.
.
.
XXXX files pulled. 0 files skipped
(Some more transmission stats)
Hope it works out for who ever reads this.
Side note:
On my phone the screen was smashed. I replaced it and it still would not turn on, but it was still running. I had a rooted phone with CM10 rom on it. ADB debugging was one (if its off your pretty much screwed). I started up the phone, and plugged in the usb cable. I tried to use both adb and fastboot from windows terminal. "fastboot devices" would echo back nothing, and "adb devices" would echo back my phone's device number but state it was offline. So to get it online I did the following:
1.) pull batttery.
2.) boot into bootloader (hold power and volume up) the phone shouldn't vibrate if it does you have just normally powered it on. It took me quite a few times to get this to go into the bootloader. To make sure you get in the bootloader type "fastboot devices". If nothing comes up you not there.
3.) once verified you are in the bootloader you need to go into recover mode. Press volume down twice and then hit power (this would normally move the cursor on your phone down to recovery and select it if you could see whats happening on the screen).
4.) wait a bit for it to load into recovery, try typing "adb devices". You should eventually see you device show up as online. At this point you may enter the shell as above, mount the sdcard, exit the shell and pull your files.
Windows instuctions:
Prerequisites are installing adb.exe and fastboot.exe via installing the Android SDK on your computer. They will show up in the platform-tools folder of the install location. Add that folder to your environmental path variable so you can run the ADB and fastboot commands from any folder. Install the ADB driver for your phone (allows you to issue adb commands to your phone when USB is plugged in) by plugging in your phone and going to device manager, find your phone which should show up as a exclamation point, right click update driver, click "browse...", then "let me pick...", click top entry something like "show all", and then let the list populate. On the left look for "samsung" and then select the first one that is something like "samsung adb driver interface". And you should be good to go.
Sorry for the long winded post, I just like to try and explain as much as possible.
Successfully Recoverd data
Well My Samsung S2's Screen broke down few days ago.. Now i have retrieved the data by following the 2nd method in the following article..! I Hope this works for you aswell...
I can not Post the link here.. PM me if you want the link...!
I've read a couple dozen of the pages from http://forum.xda-developers.com/showthread.php?t=1905674&page=95 titled
Nabi2 root and Gapps install
Click to expand...
Click to collapse
.
Using Win7 x64. Nabi2 version: 1.9.37 recently updated.
Can't post to above thread because this is my first post (restricted to "General" forums).
In "Jmz Nabi Recovery Installer" window it is always stuck in the "If stuck here drivers are not installed" step.
Prior to installing "PdaNet for Android" from http://junefabrics.com/index.php,
I had 2 devices in Control Panel under "Other devices" with a yellow '!'. One of the looked like the Nabi device. The other is named "MTP".
After installing PdaNet, only MTP remains with the yellow exclamation point.
What should the Nabi look like in the Control Panel if its properly configured with a driver and where would it be?
And what is MTP?
Apparently I'm still having a driver/connection problem from adb.
USB Debugging is on in the Nabi.
Put the nabi in 'fastboot' mode
Open a CMD Prompt and browse to the 'files' folder within 'jmzrootpackage'
Then type:
adb.exe
fastboot devices
It should return a value (fastboot working and drivers are installed)
Let me know how it goes.
Put the nabi in 'fastboot' mode
Open a CMD Prompt and browse to the 'files' folder within 'jmzrootpackage'
Then type:
adb.exe
Click to expand...
Click to collapse
Part of this command is missing right? Without input parms it just outputs the "uses" message.
fastboot devices
Click to expand...
Click to collapse
Unfortunately this returned nothing for me.
I'm glad you responded. Other suggestions?
Here is how i done it using Windows 8 x64
I done 3 nabi2's this way but had a lot of trouble first so here is what worked for me:
Sadly, i don't have any nabi2 with me now to explain exactly how i done it
1) First boot the Nabi2 normally and turn off usb debugging.
2) When fully booted connect USB cable.
3) Check device manager and drivers should be installed.
4) Unplug USB cable and turn on USB Debugging and Unknown Sources.
5) Reconnect USB Cable.
6) Drivers should install.
7) Install PDA Net on Laptop/PC
8) Select Samsung device from option screen when installing.
9) Wait for install to complete and drivers to install
10) Shut down Nabi2
11) Boot Nabi in fastboot (Hold + and Power buttons)
12) Select fastboot protocol
13) Here i seen Windows 8 take about 60 seconds installing fastboot drivers
To make sure fastboot drivers are installed i went to this thread
Code:
http://forum.xda-developers.com/showthread.php?t=1590800
and download ADB (save it to C:\SDK\platform-tools) and read over the helpful instructions in the thread.
Open command Prompt
Type the following (shown in RED) in the CMD window the opened:
cd\
cd C:\SDK\platform-tools
adb.exe (a list of options should be listed)
fastboot devices (it should list a number after you enter this)
If number displayed then you are good to go.
Reboot Nabi2 and wait to complete
Go to the location you saved jmzrootpackage
Go to files folder inside jmzrootpackage
Double click install.bat
Follow on screen prompts ( I took option 1)
TWRP recovery installs
I had trouble installing GAPPS.zip with an error being displayed about unable to mount /data
I copied GAPPS.zip to a SD Card and inserted to Nabi2
i install zip from EXT-SD Card even though it gives a load of errors about not able to mount /data
Wipe Cache/Dalvik
Reboot Nabi2
Go to daddy/mommy mode and you should have Google Apps installed.
Any problems let me know.
I'm using Windows 7 x64.
Your instructions with selecting "Samsung" for PdaNet install appears
to have done something right. So maybe I'm a little closer.
It completed the PdaNet install successfully and when I reconnect the
Nabi I see a message popup on Windows saying PdaNet connected something.
(It was too quick.)
So maybe I'm not doing the "Fastboot" portion correctly.
On Nabi hold <Power> and <Vol+> down at same time to turn it on.
Resulting Menu:
Boot Normally
Fastboot Protocol
Recovery Kernel
Forced Recovery
Use <Vol-> to move the selected item.
Moved selected item down to "Fastboot Protocol".
Use <Vol+> to "enter" selected item.
New Menu:
Bootloader
Continue
Reboot-bootloader
Reboot
Poweroff
Selected "Continue", and entered(<Vol+>).
At this point the Nabi boots up.
On PC in adminstrator mode for command window and with ALL anti-virus
security turned off:
> adb.exe kill-server
> adb.exe start-server
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
> fastboot.exe devices
Nothing. (sigh)
After looking at Victoria Antonio's youtube of this process I'm convinced the driver install is still not correct.
Somehow it gets mucked up when I use PdaNet. Not sure how or why.
To make this picture clearer I posted some screen shots on my website: http <colon, 2 forward slashes>skippyvondrake.com
I hope someone can tell me how to unmuck what I've mucked.
skippyV said:
Selected "Continue", and entered(<Vol+>).)
Click to expand...
Click to collapse
Don't press Continue on the Nabi after selecting fastboot protocol
After selecting fastboot protocol leave it.
skippyV said:
> fastboot.exe devices
Click to expand...
Click to collapse
The command is:
fastboot devices
not
fastboot.exe devices
Thanks for telling me about when I'm in fastboot mode.
I DO get a device number when in fastboot mode and from 'fastboot devices'
But adb still cannot "see" the device. All commands using adb result in:
error: device not found
Regardless of what mode the Nabi is in.
SOLVED
I finally decided to try this with a different computer. Same OS and architecture.
But this computer didn't have various android development "kits" installed previously.
And it worked without a hitch.
The youtube by Victoria Antonio pointed out a few nuances I didn't know.
And you helped too, BBKGTTDi, so giving you "thank you" points.
Chow!
Glad you got it work SkippyV
I just need to figure out now, when i download a game to the Nabi2 from the playstore, how to get it so show in the kids mode
BBKGTTDi said:
Glad you got it work SkippyV
I just need to figure out now, when i download a game to the Nabi2 from the playstore, how to get it so show in the kids mode
Click to expand...
Click to collapse
When I get there - if I figure it out - I'll send you a private email sense that would be a different "thread'. There are other nuances I've noticed too...
show game in Nabi mode after rooting
@BBKGTTDi, I thought there would be a way to send private messages/emails on this forum - but I don't see it.
I ran into the same problem after rooting the Nabi. The "Add Apps" app doesn't work as its supposed to.
It worked prior to rooting.
It does list the newly installed apps, but selecting them for Nabi-Mode, rebooting, and they aren't there.
Only visible in Mommy/Daddy mode.
So if you figure it out please let me know!
The "Add Apps" app is working correctly now. Don't know what happened before.
I must be getting "Nabi-ed out".
Let me know if you're still having troubles.
skippyV said:
I'm using Windows 7 x64.
Your instructions with selecting "Samsung" for PdaNet install appears
to have done something right. So maybe I'm a little closer.
It completed the PdaNet install successfully and when I reconnect the
Nabi I see a message popup on Windows saying PdaNet connected something.
(It was too quick.)
So maybe I'm not doing the "Fastboot" portion correctly.
On Nabi hold <Power> and <Vol+> down at same time to turn it on.
Resulting Menu:
Boot Normally
Fastboot Protocol
Recovery Kernel
Forced Recovery
Use <Vol-> to move the selected item.
Moved selected item down to "Fastboot Protocol".
Use <Vol+> to "enter" selected item.
New Menu:
Bootloader
Continue
Reboot-bootloader
Reboot
Poweroff
Selected "Continue", and entered(<Vol+>).
At this point the Nabi boots up.
On PC in adminstrator mode for command window and with ALL anti-virus
security turned off:
> adb.exe kill-server
> adb.exe start-server
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
> fastboot.exe devices
Nothing. (sigh)
Click to expand...
Click to collapse
I ve got the same problem using windows xp, 7 or 8.1 after OTA update to jellybean.
Any ideas of what is going on?
arvati said:
I ve got the same problem using windows xp, 7 or 8.1 after OTA update to jellybean.
Any ideas of what is going on?
Click to expand...
Click to collapse
I did have those problems last year. Still think they were driver related.
I use mehtuus's package now. He has a useful install script.
http://forum.xda-developers.com/showthread.php?t=2172843
And when I want to use adb in "manual" mode I just launch a command prompt from his
'adb' directory (package is named 'mn2ri-v1.5.0-beta2.zip').
Try playing with his installer. And see if anything is displayed using:
Code:
adb devices
Thanks skippyV. I got it in fastboot last week with ubuntu and installed TWRP sucessfully.
**UPDATE**
NEW VERSION
THIS RELIES ON ADB COMMANDS, SO IF YOU DO NOT HAVE USB DEBUGGING TURNED ON, OR A CUSTOM RECOVERY TO BOOT TO, THEN IT WILL NOT BE AS SIMPLE AS JUST RUNING THE PROGRAM.
Another user was having issues because he had an emulator installed, so I updated the file to give you the choice between an emulator, or device. I intend to update further to allow you to check for and select an individual device, that will come soon..
----------------------------------------------------------------------------------------------------------------
Recently my Galaxy s2's screen smashed, and, after replacing it with a GS4, i realized that many of my pictures were stuck on the internal sd card of the GS2. Being unable to turn on mass storage mode, I made a very simple tool that makes using adb pull a simple, painless process, even for the most computer illiterate of android users. Hope this helps if anyone needs it.
For anyone having issues...
If you had not previously activated USB Debugging, there are several steps you need to follow in order to enable ADB
SCREEN WORKING TOUCH BROKEN NO CUSTOM RECOVERYfirst, if you can see your screen, and have access to an otg cable, plug a mouse in to the otg cable, and the otg cable into the phone. Use the mouse to enable USB debugging, or to transfer files.
HOW TO ENABLE USB DEBUGGING
SCREEN WORKING TOUCH BROKEN WITH CUSTOM RECOVERYboot to your custom recovery ADB commands will work here. (usually hold vol- + pwr)
HOW TO BOOT TO RECOVERY
Once in custom recovery, connect the device to the PC.
open CMD and enter the following commands;
cd c:\android (this is your ADB path, c:\android is default)
adb devices
The result should be something like
List of devices attached
051a4dd5 recovery
^^this number will be different for you
if you get a result on ADB devices, then you can use the program
SCREEN BROKEN TOUCH BROKEN WITH CUSTOM RECOVERYboot to your custom recovery ADB commands will work here. (usually hold vol- + pwr)
HOW TO BOOT TO RECOVERY
Once in custom recovery, connect the device to the PC.
open CMD and enter the following commands;
cd c:\android (this is your ADB path, c:\android is default)
adb devices
The result should be something like
List of devices attached
051a4dd5 recovery
^^this number will be different for you
if you get a result on ADB devices, then you can use the program
SCREEN BROKEN TOUCH BROKEN NO CUSTOM RECOVERYnow things get complicated...
*The following is paraphrased from this site
1. download the custom recovery image for your device. Copy the recovery image to a convenient location on your computer, preferably with a short path. We will be placing it on the C Drive directly (not in any folder) and using that in the next steps.
Note: The recovery image should have .img extension. If it is in a zip file, extract the .img file from it.
I recommend clockwork mod non touch from this page
2. Power your device off and reboot your device to FASTBOOT or DOWNLOAD MODE depending on which type of device you have.
(most devices are fastboot, SAMSUNG typically uses DOWNLOAD MODE)
how to boot to fastboot or download mode
[FASTBOOT]3. Connect your device to your computer via USB and wait till you see the PC recognize the device
to check if your device is in fastboot and connected use CMD and enter the following commands;
cd c:\android (this is your ADB path, c:\android is default)
fastboot devices
you will see a list of connected devices. if not, something went wrong.
4. Launch Command Prompt and type the following commands;
cd c:\android (this is your ADB path, c:\android is default)
fastboot flash recovery c:\recovery.img
5. Wait for the process to finish.
6. Turn device off then boot to your custom recovery ADB commands will work here. (usually hold vol- + pwr)
HOW TO BOOT TO RECOVERY
Once in custom recovery, connect the device to the PC.
open CMD and enter the following commands;
cd c:\android (this is your ADB path, c:\android is default)
adb devices
The result should be something like
List of devices attached
051a4dd5 recovery
^^this number will be different for you
if you get a result on ADB devices, then you can use the program
[RECOVERY MODE (SAMSUNG)]USE THE INSTRUCTIONS ON THIS PAGE
Once in custom recovery, connect the device to the PC.
open CMD and enter the following commands;
cd c:\android (this is your ADB path, c:\android is default)
adb devices
The result should be something like
List of devices attached
051a4dd5 recovery
^^this number will be different for you
if you get a result on ADB devices, then you can use the program
HOPEFULLY THIS HELPS. REMEMBER TO CHECK THE FORUM PAGE FOR YOUR DEVICE IF YOU RUN INTO ISSUES. THIS ISN'T ANYTHING THE MEMBERS OF XDA HAVEN'T DONE THOUSANDS OF TIMES OVER.
Don't forget to hit "Thanks"
i'll bump this thread for those who didn't see this amazing tool, this tool is really useful, thank you very much
Hi,
Sturggling to find the .adb file as my phone shows up as a "Portable Device" any ideas?
Cheers
Thank you!
I joined just to say thank you to FuzzyMeep Two. Thanks for an awesome tool! It worked better than advertised!
:good:
Thanks again!
-th3r3isnospoon
Question
Hi! Can I use that to restore data not from sdcard but from internal memory of the device? I was storing photos on device memory on my Asus TF300T and now its bricked. I need to restore these photos, my girlfriend has something like 1000 of them from her trip to Caracas. Its very important for her. I already managed to connect the device through fastboot and I launched anb in cmd. What should I do next? Please help me guys
koperkowy said:
Hi! Can I use that to restore data not from sdcard but from internal memory of the device? I was storing photos on device memory on my Asus TF300T and now its bricked. I need to restore these photos, my girlfriend has something like 1000 of them from her trip to Caracas. Its very important for her. I already managed to connect the device through fastboot and I launched anb in cmd. What should I do next? Please help me guys
Click to expand...
Click to collapse
Yes, when it references SD Card it means the internal "SD" storage built in to the phone, not the removable one. It should work as long as ADB can connect.
Sorry for taking so long to reply, i really hope you got your pictures back.
FuzzyMeep Two said:
Recently my Galaxy s2's screen smashed, and, after replacing it with a GS4, i realized that many of my pictures were stuck on the internal sd card of the GS2. Being unable to turn on mass storage mode, I made a very simple tool that makes using adb pull a simple, painless process, even for the most computer illiterate of android users. Hope this helps if anyone needs it.
P.S. I apologize if i have posted this in the wrong place, if so please let me know.
Click to expand...
Click to collapse
Really great stuff - so simple but so effective. Cheers and thanks.
Error msg
zobes said:
Really great stuff - so simple but so effective. Cheers and thanks.
Click to expand...
Click to collapse
When i run that tool, i get the error mesg: more than one device and emulator,
I dont want to uninstall the emulator coz it was a headache getting it running
How i procede to select the device to be used
alisdairjk said:
When i run that tool, i get the error mesg: more than one device and emulator,
I dont want to uninstall the emulator coz it was a headache getting it running
How i procede to select the device to be used
Click to expand...
Click to collapse
NEW VERSION
Try this, i haven't gotten to test it, so please let me know if it worked for you, I added the option of selecting an emulator or USB device, because of your post. Hopefully it helps.
When I try to run this I also get an error message saying that the adb.exe file cannot be found.
Please can anyone help?
Joeb29 said:
When I try to run this I also get an error message saying that the adb.exe file cannot be found.
Please can anyone help?
Click to expand...
Click to collapse
Have you also installed ADB, as well as this software?
I'm also having an issue - I have installed java, java SDK and ADB, so I can now run the data recovery tool. But when I do I'm getting "error:device not found" - am I missing drivers or something? I couldn't get all the way on the ADB configuration, because part of it required me to do something on the device... anyway, looks like the computer isn't recognising the the phone at the moment.
Any help very gratefully received (phone is Samsung Galaxy S2).
joffmeister said:
Have you also installed ADB, as well as this software?
I'm also having an issue - I have installed java, java SDK and ADB, so I can now run the data recovery tool. But when I do I'm getting "error:device not found" - am I missing drivers or something? I couldn't get all the way on the ADB configuration, because part of it required me to do something on the device... anyway, looks like the computer isn't recognising the the phone at the moment.
Any help very gratefully received (phone is Samsung Galaxy S2).
Click to expand...
Click to collapse
I have the same situation right now. Managed to make your program work then I get the "error:device not found". My phone does show up in the computer folder(albeit not in mass storage mode), but isn't that what this program was made to work around?
My phone is a LG Optimus G with a smashed glass... The LCD still displays fine, but I'm stuck at my swipe lock because the digitizer is dead.
Thank you for your help and your wonderful program.
Thanks for this app. My girlfriend broke her screen and digitizer on her Galaxy S4. She never turned USB Debugging mode and has a lock on her screen. When using your app I get the same error when I use adb by itself which is "error: closed". ADB detects my phone but any command I use in ADB or with your app I get that same error.
Do you know how to fix this? Thanks in advance.
Thanks a lot man.
dude this tool is just amazing and does exactly what it promised. I was spending sleepless nights thinking about how to recover my data from my broken galaxy nexus and now that I have it I can rest easy. Seriously can't thank you enough for this. Just joined xda to thank you buddy.:laugh::fingers-crossed:
Getting an error "The system cannot find the path specified."
I start the recovery tool, set eh adb path successfully, and then I get this error. If I try running the recovery to pull the DCIM library I get this:
"error: device not found"
What can I do?
Thanks!
Either way this is an amazing tool, seeing how it helped some people already. :good:
Hi, Seem to have the same problem as many others, Device not found. I cant change to MTP mode on my LG G2.
I hope someone can find a solution to this problem.
Program seems amazing doh.
Hello,
This is really a great tool ! I was wondering if you could add the possibility to recover the external sd card aswell.
Device not found
Tried to recover a Samsung Galaxy S3 mini with a broken screen
I installed adb and RecoverData, run it and then get a "device not found error"
What can I do?
Amazing app. thank you so much :good:
FuzzyMeep Two said:
**UPDATE**
NEW VERSION
Another user was having issues because he had an emulator installed, so I updated the file to give you the choice between an emulator, or device. I intend to update further to allow you to check for and select an individual device, that will come soon..
----------------------------------------------------------------------------------------------------------------
Recently my Galaxy s2's screen smashed, and, after replacing it with a GS4, i realized that many of my pictures were stuck on the internal sd card of the GS2. Being unable to turn on mass storage mode, I made a very simple tool that makes using adb pull a simple, painless process, even for the most computer illiterate of android users. Hope this helps if anyone needs it.
Don't forget to hit "Thanks"
Click to expand...
Click to collapse
Hi, Thank you very musch, It's so usefull for me.. :angel: