Related
Ok so I was trying to install a custom recovery on my P500 and when it turned on it gave me this message
fast boot mode started
udc_start
Click to expand...
Click to collapse
I plug it in it gives me
fast boot mode started
--suspend--
--reset--
--port/change--
--reset--
--port/change--
Click to expand...
Click to collapse
I tried out this method: http://forum.xda-developers.com/showthread.php?t=1088046
After keying the fastboot commands in it says <waiting for device>. Some Google hits told me that it's because I don't have latest USB drivers. I'm sure I do, but I've re-installed them just to be sure. But to no avail.
I'm still on my stock ROM (untouched), phone is rooted (duh) and this is my first attempt to install a custom recovery.
Not allowed to post on that thread ofc, my first post here. All help greatly appreciated. Thanks
Here is the Simple way ..try it
this link for latest working Rom >>
http://forum.xda-developers.com/showthread.php?t=946354
how to root >>
Enable USB debugging on your phone by going to Settings –> Applications –> Development. Check the ‘USB Debugging’ option.
Make sure you have a SD card inserted and mounted in your phone (Don’t know if it’s necessary but before proceeding further I formatted my SD card after taking a backup of the data in it. Why take a risk? Smile)
Download the GingerBreak APK from XDA Developers and get it onto your phone.
Install it by browsing to the GingerBreak APK in any file manager.
Open GingerBreak from your app drawer and press the root button.
Wait for a few minutes. If there are no problems, the device will reboot itself. (The reboot will take quite some time.)
You will see a SuperUser app in your app drawer after the reboot. Open it and see if it is working.
You now have a rooted Optimus One P500 phone.
Now install custom recovery
Follow the below steps to install custom recovery on your LG Optimus One P500.
Install Android Terminal Emulator from Android Market.
Download the file "amon_ra_recovery_installer.zip" from here or here.
Check the MD5 hash value of the downloaded ‘zip’ file. You can use HashTab to do this. Right click on the downloaded file and ensure the MD5 matches 86db8a52b01f049cadb8f097a4c5bd9e.
Extract the contents of the ‘zip’ file to the root of the SD card (Don’t extract inside any folder. For example if your SD Card is mounted on J: in Microsoft Windows then the four extracted files should be right under J:/ like J:/flash_image)
Open the terminal emulator app on your phone and type ‘su’ without the quotes. This will prompt a popup on your phone from the SuperUser app asking you whether you want to give root permissions for the terminal emulator app. Click ‘Allow’ and proceed. The shell prompt will change from the previous user shell ‘$’ to root shell ‘#’ in the emulator.
Now type in the following command and press Enter. The custom recovery will be flashed on to your phone and it will reboot into Custom Recovery.
sh /sdcard/rf.sh
Shut down your phone and boot into Recovery using the Volume Down, Home and Power switch keys. You can move through the options using the volume up/down keys. Use the Menu button to select the option.
In the recovery menu, select Backup/Restore, then select Nand backup. What this will do is backup your current ROM on your SD card, if something goes wrong while flashing the new ROM you can simply boot into recovery and restore your previous ROM.
Connect the phone to your computer and inside Recovery main menu click the option ‘USB-MS toggle’ and then ‘USB-MS Toggle SDCard’. This will unmount the SD card so that you can see it in your computer. Backup everything from your SD Card. Eject from computer and toggle USB again from recovery to mount the SD card back in phone.
Though it is not a necessity for this ROM, I would suggest partitioning your SD card to create swap and ext partitions. The ext partition will come in use if you want to install apps onto your SD card later. This is different from what you see in Froyo versions of Move to SD option. Partitioning will format your SD card, so make sure you backup your SD card as mentioned in Step 3.
Go back to the recovery menu again and select ‘Partition sdcard’. Then select ‘Partition SD’. Create a swap partition of size 0 and ext partition of size 512. Once done hit Back to go again to the ‘Partition sdcard’ menu. Convert the partition you just created to ext 3 and then ext4 using the options ‘SD:ext2 to ext3’ and ‘SD:ext3 to ext4’.
Toggle USB from recovery again. Inside the SDcard create a folder AAA and copy the ROM you downloaded in Step 1 into the folder ‘AAA’ on your SDCard. Once done, eject the SD card and toggle USB again to mount the SD Card in the phone again.
Go to the Wipe option in the recovery menu and wipe userdata, /data, /sd-ext, /sdcard/.android_secure, /cache, ‘Dalvik-cache’
Then go to the Flash Zip option in the recovery menu and select the zip file you copied in Step 6.
Sit back and relax while the zip is flashed. Once recovery shows that flashing is complete, reboot phone from recovery. The first boot will take quite some time.
Enjoy Gingerbread 2.3 on your LG Optimus One P500.
@ above completely unrelated to his problem.
Sent from my LG Optimus One P500 using XDA App
Appreciate your post but it has nothing to do with query sadly.
I was doing what you've mentioned in the installing recovery section when things went wrong.
I run Win7 x64 btw.
istoner said:
Some Google hits told me that it's because I don't have latest USB drivers. I'm sure I do, but I've re-installed them just to be sure. But to no avail.
Click to expand...
Click to collapse
That is correct - drivers issue.
1/ Add DEVMGR_SHOW_NONPRESENT_DEVICES to your environment on Windows and set the value to 1. (In Advanced system settings, Google if you do not know how.) Log off and log back on.
2/ Run devmgmt.msc
3/ There, View - Show hidden devices
4/ Go thru it and uninstall everything Android-related (for starters, ADB Interface and stuff under it, Disk drives, Modems, Ports (COM and LPT), USB controllers - might not be complete list above)
5/ Reboot the PC.
6/ Install the latest drivers for your phone.
7/ If it worked, once you have plugged in the phone stuck in fastboot mode, in device manager you should see Fastboot interface (Google USB ID) in ADB Interface section.
Thanks, trying that out now.
doktornator,
Thanks a bunch. It was an issue with the drivers, I tried your method a few times with little success. Then I let Windows find the drivers (out of all the things), and that worked. Relieved and slightly embarrassed that Windows could what I couldn't
Good that it works now. Fingers crossed to unbrick your phone soon.
Oh it's unbricked and ready to go again lol.
Hi, I am on Windows XP with the exact same problem.
Have tried the B2CApp for driver updates with no luck. Tried windows automatic driver installation,again no luck.
Anything else that I could try on a Win XP machine?
UPDATE:
I have fixed the issue. Got the drivers mentioned in this thread:
Anyone else stuck with Windows XP not recognizing the device even after the B2CApp installation, try these drivers:
http://android.modaco.com/topic/324744-waiting-for-devicefastboot/#
hi guys
Same issue here...and I've had all of the above problems (missing dll, the "waiting for device" due to the absence of proper drivers, etc) . I was able to solve everything up to step 2 of the procedure, i.e., when I type "fastboot flash recovery recovery.img" I get the error message: "cannot load recovery.img".
I tried with both the .img files extracted from the CWM link and AmonRA (thinderg). Any ideas? What am I doing wrong? This is going for hours now and I'm getting desperate!
droidao said:
hi guys
Same issue here...and I've had all of the above problems (missing dll, the "waiting for device" due to the absence of proper drivers, etc) . I was able to solve everything up to step 2 of the procedure, i.e., when I type "fastboot flash recovery recovery.img" I get the error message: "cannot load recovery.img".
I tried with both the .img files extracted from the CWM link and AmonRA (thinderg). Any ideas? What am I doing wrong? This is going for hours now and I'm getting desperate!
Click to expand...
Click to collapse
is the name of the .img file recovery.img?
the command is really fastboot flash recovery (name of file).img
Yes it is...Actually I tried both ways (renaming and keeping the original name)! But I've finally figured it out!!! Here was the problem: when I installed android sdk I added the paths of the required directories (tools and platform-tools) to the system variable section so I could launch tools without writing the path all the time...However, because desperate times call for desperate (and often silly) measures, I decided to type the command cd "name-of-directory" anyway and that...made the trick.
This community is indeed great...I'm going to distribute some "thankyous" now!
I had the same problem with Win7, Updating the drivers from the device manager of w7 worked for me. Hope it helps.
Ps: will take around 15 mins updating.
I did an NVflash after struggling to load VEGaN 7 for a couple days figuring it was the partition issue that I have read about. Flash went off without a hitch - or so I thought.
I went to flash VEGaN 7 again, but my computer would not recognize connection via USB. Attempted to login to clockwork mod but instead I get message - "booting recovery image".
Thinking a factory reset might somehow free up my USB connection I did a factory reset - now I'm stuck in a bootloop.
So, to review--
I can't connect to PC via USB, Access CWM, or get past the bootloop.
BTW - I noticed while looking for options to connect to USB that it appeared my Internal and external SD cards switched locations after the NV flash. External, although not accessible was 12.9 gig and my internal showed slightly less than 1 gig.
Anyway, is there any hope for my G tab - I have never been so frustrated over such a simple process in my entire life.
sorry looked for a way to move this post to the correct location...
gunnervike said:
I did an NVflash after struggling to load VEGaN 7 for a couple days figuring it was the partition issue that I have read about. Flash went off without a hitch - or so I thought.
I went to flash VEGaN 7 again, but my computer would not recognize connection via USB. Attempted to login to clockwork mod but instead I get message - "booting recovery image".
Thinking a factory reset might somehow free up my USB connection I did a factory reset - now I'm stuck in a bootloop.
So, to review--
I can't connect to PC via USB, Access CWM, or get past the bootloop.
BTW - I noticed while looking for options to connect to USB that it appeared my Internal and external SD cards switched locations after the NV flash. External, although not accessible was 12.9 gig and my internal showed slightly less than 1 gig.
Anyway, is there any hope for my G tab - I have never been so frustrated over such a simple process in my entire life.
Click to expand...
Click to collapse
When you NVFlashed, did you use the version with or without CWM. If you did the version without CWM then that would explain no CWM.
When you say you can't connect to PC are you talking about APX mode (NVflash)?
Go here http://viewsonic-gtablet-for-dummies.webs.com/ and follow the instructions for CODE RED step by step. Make sure download everything via the links on the dummies site to make sure you get the right stuff.
Al
No I used the version with CWM, which is why I was suprised to see the "booting recovery image" and then it just continued to boot. I tried both APX via USB and a typical USB connection after loading --where PC gave error "device not identified".
gunnervike said:
No I used the version with CWM, which is why I was suprised to see the "booting recovery image" and then it just continued to boot. I tried both APX via USB and a typical USB connection after loading --where PC gave error "device not identified".
Click to expand...
Click to collapse
So, just to verify, you hold Vol(-) and press/hold Power, 3 birds appear & screen goes black...that is APX mode. Connect usb cable to PC & what does the PC say?
USB device not recognized -
Still having that problem with USB device not recognized.
However, I have gone to ...for dummies site and reflashed device using the "flash USB driver" to temorarily gain access with USB connection. With NVFlash I Am back to having clockworkMod and working GTab with original software 1.1
Again going to flash rom - but Upon connecting USB i get the message "USB device not recognized" - I have attmpted to mount USB through CWM, but still getting that same error.
gunnervike said:
Still having that problem with USB device not recognized.
However, I have gone to ...for dummies site and reflashed device using the "flash USB driver" to temorarily gain access with USB connection. With NVFlash I Am back to having clockworkMod and working GTab with original software 1.1
Again going to flash rom - but Upon connecting USB i get the message "USB device not recognized" - I have attmpted to mount USB through CWM, but still getting that same error.
Click to expand...
Click to collapse
If your tab boots, you don't have to use CWM/mount & storage to transfer your rom to the internal sd. Put your external in your PC, copy the rom to it, move back to the tab & copy to your internal. There are also other ways to transfer it but we can talk about that later if you like.
If that works you can still flash your rom & then we can work on getting the usb up.
So, the usb not recognized is when you try to connect after your tab is either all booted up or in CWM mount & storage (and not when you are in APX mode doing NVFlash)?
If you look in device manager what does it show?
Try connecting your tab to a differet PC & see it detects it correctly?
If it works on another PC, you may want to tryto use USBDview http://www.nirsoft.net/utils/usb_devices_view.html to look at the USB dvices that are connected or have been connected to your PC. You can find the gTab devices in the list & then use it's command line options (see instructions included with it) to remove(uninstall) them from the PC. Then you can reconnect to see if it will detect & install the driver correctly.
Can't use external load on pc to transfer rom. No card access.
USB did work in apx mode following instructions in code red. I thought of usin another pc and duplicated the failed results there.
Device manager showed yellow exclamation mark and would'n't install any driver I pointed it to (both computers) Unknown USB device.
Btw I want to thank you for trying to help me out on this. You people who lend your knowledge are commendable.
gunnervike said:
Can't use external load on pc to transfer rom. No card access.
USB did work in apx mode following instructions in code red. I thought of usin another pc and duplicated the failed results there.
Device manager showed yellow exclamation mark and would'n't install any driver I pointed it to (both computers) Unknown USB device.
Click to expand...
Click to collapse
OK, try this. We are going to use Mobisynapse to wirelessly transfer files to & from your PC to the tab.
Download mobisynapse from my dropbox http://dl.dropbox.com/u/36150173/Mobisynapse.exe & install on your PC.
From your gTab, download Mobisynapse system tool from my dropbox to your tab & install http://dl.dropbox.com/u/36150173/com.mobisystems.office_registered-1.apk.
Start the app on the tab, click More & select Connect to PC to switch it to ON.
Start the Mobisynapse on your PC, it shoud see your tab, once it sees it click connect.
From there, go to the Files icon & you should see an Explorer type screen. PC on the left, tablet on the right. You can transfer files in either direction. Transfer your Rom files or whatever you want.
Let me know when you have downloaded the apps from my dropbox so I can remove them.
Al
I downloaded them and installed, on tab it shows up as officesuite. When I run it "more" is not an option. On pc it simply says (can not connect to android device) under "choose devices". I did turn on USB debugging on tab.
gunnervike said:
I downloaded them and installed, on tab it shows up as officesuite. When I run it "more" is not an option. On pc it simply says (can not connect to android device) under "choose devices". I did turn on USB debugging on tab.
Click to expand...
Click to collapse
Opp! Put the wrong one there. Give me a few & I'll put the correct on there.
aabbondanza said:
Opp! Put the wrong one there. Give me a few & I'll put the correct on there.
Click to expand...
Click to collapse
Here's the correct on for the tab app:
http://dl.dropbox.com/u/36150173/Mobisynapse%20system%20tool_1.3.apk
aabbondanza said:
Opp! Put the wrong one there. Give me a few & I'll put the correct on there.
Click to expand...
Click to collapse
Ok, there we go. Gimme a few
Do I need to create a "roms" folder, and is it supposed to be the zip folder or the files within the zip folder?
gunnervike said:
Do I need to create a "roms" folder, and is it supposed to be the zip folder or the files within the zip folder?
Click to expand...
Click to collapse
It's easier that way, that way you can easily differntiate it from other files/folders. If you create the folder, then put the zipped rom inside the folder.
I turned connect to pc on. Running mobisynapse on pc it sees the tab just fine. I click connect and it pulls up info about tab, BUT when I go to files tab --- right side of screen is greyed out. It won't transfer files.
gunnervike said:
I turned connect to pc on. Running mobisynapse on pc it sees the tab just fine. I click connect and it pulls up info about tab, BUT when I go to files tab --- right side of screen is greyed out. It won't transfer files.
Click to expand...
Click to collapse
Third icon from the left...looks like a little file cabinet.
lol, yeah 3rd from left...
It seems to connect just fine, but under the file tab I can only see files from the PC on the left - the right side doesn't show any files and all buttons are greyed out. Again, under the home tab I have access to the GTab just fine. I can see apps, contacts, etc. but under file tab - no files on right side and buttons are not accessable.
So do you see the left (PC side)? Is the right side populated at all & what is in the drop down folder box (should be /sdcard)!
So I got some help from Divx and another user that I can't think of the name (sorry ;( ) but I ended up having to delete the sde and install the orig firmware. So that was successful. Now I, trying to install the sde. I downloaded the correct file .aos. I went into recovery and chose update system firmware. The device then goes through a format process, then asks me to connect usb. When I do that, windows (windows 7 btw, I didn't have this problem when I went through thr process the first time) windows tells me it can't use the storage device unless I format it. I tried that of course, but now it just says update failed. I suspect it has to do with the formatting. Can anyone point me in the right direction on how to get around this? Am I doing something wrong?
Sent from my DROID4 using Tapatalk 2
Hey guys.
I have Samsung galaxy ace 5839i (stock for 5830i) and I am using it for a few years, but this problem came for the first time.
Always, when I try to connect my mobile to pc using cable, it just won't connect, it won't even show me the notification of connecting.
Before this problem, I connected it to fedora linux and it was succesful, but now? It won't show me that USB sign even in windows.
Any help?
Thanks in advance
@LiQuDiAk, basically s5839i and s5830 i are identical in many areas ,, few questions though,, did you root your device or you are on android 2.3.6 stock version / kernel 2.6.35.7 ?
when you are in your windows device manager ( while you are connected , do you see any exclamation / question marks in front of the corresponding driver), you can always uninstall your old driver, reboot , then try compiled driver in attachment , and reboot to take proper effect in your registry (tested on win xp/7 -32bit) . Also check your device settings>Application>Development > USB Debugging and make sure the option is checked. now lets check your debugging mode through ADB command and see if your device is being recognized. download platform zip attachment, unzip it and put the folder someplace like your desktop. Now open your command prompt (cmd) through whatever means you are comfortable and change directory (cd) to the unzip folder or simply open your folder and drag/drop adb.exe into your CMD to be in the right place very fast. Then type "adb devices" without quotation marks and report for more troubleshooting .Assuming your Samsung cable is not faulty of course.
@ehsanotaku Yes i did root my phone on pheonix fire rom. No i do not see any. And debugging is checked, that was my first guess why it was causing this. I was checking, whether my device is recognized in linux (only available OS in present) and it was NOT, but the cable is not faulty, because it was charging my phone... but i will do recognize process on windows, hope it will get better. But thanks so far!
so, the driver didnt help, but the adb devices got me something long which i do not completely understand (i am a girl and not IT) so...
LiQuDiAk said:
so, the driver didnt help, but the adb devices got me something long which i do not completely understand (i am a girl and not IT) so...
Click to expand...
Click to collapse
off topic though, gender discrimination is prejudice,, sorry if you are offended . Learning from each other despite your gender,does not undermine your knowledge EVER mate You might find it hard to believe, but I am quite novice in android stuff myself ( learning a great deal from some female members though ).
Back to topic at hand now,,,So let Perfectly Clear take away the time-consuming tasks and fix some stuff ..1. so you can not access your sdcard's content from either systems,, even if you try some live bootable Ubuntu disk/flash into your system and boot it up,, you can't access the mount drive content , right?
2. screenshot of your device manger while you are connected always help mate
3. those long streams of numbers and words is supposed to be your device name , it means your device is communicating with your pc ( /sdcard/ should not be corrupted). You can push (copy ) some vital files to your device with following command :
again same path >> put some file into your desktop (drag/drop to cmd)
i.e: "adb push C:\Users\ehsanotaku\Desktop\test.txt /sdcard/"
back to your device and check root of your files with whatever file explorer you got to approve the theory
4. forgot to ask , just to be on the safe side your device is not in boot loop process, stuck on samsung splash screen or something like that, right?
okay, thanks!
1. I cannot access it trough USB to mobile way, but from SD card adapter, yeah I can (it is just the weird feeling, when you always have to put out your sd and do it that way, i would like to sort this out)
2. http://s1.postimg.org/nkta50u3x/Untitleddas.png I suppose the unknown device is my phone.
3. Just a question, my phone is not connected, i cannot access it and this doesn't help
4. Nope, it is working, i can access everything, just this connecting problem i have. anything else is running smoothly.
Let's say any of this will work, do you think flashing a stock rom will help? I am not sure, if this is problem of rom or not, so...
And maybe i wasn't clear (my bad if not) but when i plug the cable in my device and pc, pc will make this sound of new device found, but it wont show me anything, so my phone. It will charge, but it wont connect, it is behaving like it is on a charger and not connected to the phone.
@LiQuDiAk, Hasty actions are done in a hurry, sometimes without the necessary care or thought. Now let's not leap to any conclusion about your Android custom Rom and flashing back to stock. lets focus on your first most obvious problems,which is driver related.
You didn't declare your flavor of windows: i.e: Windows x86 based-PC;professional 7
Not so sure of your OS Name/Version and System Type, search "system information" in your search box.
Your task manger depicted ACPI x64 ( 64-bit system, no wonder previous 32-bit compatible didn't work out for you ).
Symptoms observed so far:
1. USB cable only charges ( remember your USB cable data line might be the culprit. Just in case of only charging,checking with another set recommended. Your USB port might be problem, some dirt or faulty data line, checking with another USP port doesn't heart though.
2. Windows recognizes something more (like in your case, struggling to find proper corresponding driver), but cannot see it as a Samsung android device (cannot allocate the installed USB drivers to the device).
-If you got Kies (Samsung proprietary software) installed on your PC, delete it with a descent uninstaller program such as CCleaner free version .Kies might cause driver conflict , use it as only last resort , if all drivers failed to communicate with s5830i device.
-Also Uninstall your previous given driver same way, now restart , back to system and grab set of universal Samsung Drivers from attachment .
3.Can't see your "USB connected" in Android notification bar, so you cant click on it and mount your storage data part while you are connected to your PC.
-Normally, when you plug in your Android device, Windows will recognize it as an MTP (Media Transfer Protocol) device and quietly mount it.
However, if you’ve ever attempted to unlock your device such as to install a new ROM or root it, then such miss behaviors might be expected occasionally .
Before i go for more troubleshooting , please provide a full screenshot from your "About Phone" page in your settings . I am quite curious about this phoenix Rom you have mentioned though . I am quite familiar with at least dozen of discontinued/ported projects, but never heard of such ported Rom from other models into s5830i .
Couple of solutions :
Navigate to your settings,Storage and touch the upper-right corner for the “USB computer connection” options, if you have this part available.
make sure “Media device (MTP)” is selected. ( if you have USB Utilities section or whatever added section in your custom settings go there . Selecting that will do the trick. If it does not, then you likely have a driver problem.
Open your device manager, Right click on your unrecognized device in question,choose update driver software, choose Browse my computer,find it through given x64 drivers in your package ,Restart. ( After a successful installation, restart your PC, you must have something like the picture in attachment ) .
Problem was not resolved, Uncheck your debugging option,power off your phone. Now hold Volume(+) + Home + Power for a couple of seconds simultaneously to get to your Samsung Recovery or your Clockwork Recovery, choose Reboot( might be some process/service in your background, which interfere with your Auto USB connected feature of your device. See if the problem is being resolved .
Problems have been persisting, we might need to format your SD card, but before that, insert it into your card reader, in your file explorer window choose Tools>Folder options>select view tab> tick your select hidden file.folders. Now copy all of your SD card's contents into some folder, safe inside your PC.
We can format your card through your clockwork mod recovery console, or some partition tools such as free mini partition wizard,,
problem still persist? let me know
Hey
After some rest with this, my mobile got it solved (dunno why, just once tried to do it and it works.)
So, thank you very much with your answers!!!!
And about that screenshots, I will PM you
But, really, thanks a lot, mate!!!!
Hello,
I installed yesterday a custom rom with 2.3.4 for an Xperia Play device and I've noticed that the phone is properly recognized, all drivers are fine, I can go into fastboot mode, bootloader unlocked, etc... and I can see the microSD card from the phone when this is plugged to the computer via USB.
The problem is that I copy files from the computer to the phone, windows takes its time and at the end says that it's all good, you can see the files in the phone, however when you then unplug the phone and go to that location, none of the new files are there?! :S
More weird is that then you plug the phone back to windows and the files appear there again?
Any idea what could be going on? and how I could copy files from windows to this android in this case?
Cheers!!
Maybe just links
Maybe you just linked to the files on your Computer. Move/Rename them on your Computer and see if you can still open them on your phone. If no you just created a link to the data stored on your computers hard drive. If yes I also can't tell you what's going on
Thanks, no the files were the complete files, no links.
I've been looking into this further, and reflash the mobile with a total different rom and still happening there (although with this new rom doesn't happen 100% of the times like with the other). What I've just now noticed is that the mobile doesn't recognize those files, but... if I REBOOT it, then they appear once it starts up?! so weird.... :S