Database Develop

[Q] Problem rooting Stock froyo captivate

Hi All,
I just purchased my Captivate yesterday from Costco (Expecting to still get the 2.4 Eclair) but unfortunately I got the Froyo 2.2 on my new captivate.
I tried rooting it using superoneClick and it just gets stuck on "Waiting for Device". I have drivers properly installed on my windows 7 64 bit machine (because I can use the phone and access its internal SD card).
Can anyone have suggestion or faced similar problems?
I have tried disabling/re-enabling usb debgging while it says "Waiting for the device"

Search the forum. There are a few threads floating around on different ways to root the stock froyo build. I don't know why the superoneclick wont work in your case but a search will turn up some info for you.

thanks. I will search the the threads and will post my results here in this thread for someone like me struggling with the same problem.

If you were planning on flashing a custom ROM after rooting anyway, you could use Odin one-click from download mode to flash 2.1 eclair, and then go from there.

Are you sure you are enabling debugging? I just used superoneclick on my phone last night after I flashe dback to stock.
First thing I do is change the phone in settings to - Ask on Connection, then I enable debugging.
Also you could try a different USB port on your computer and also make sure you have all of your necessary drivers installed.
I hope you get it figured out!

PeteSeiler2010: I haven't tried different USB port yet. I will try tonight and see if it goes through.
For usb debugging, I tried that as I mentioned. Let me just conform what I did. When it says "Waiting for device" for several seconds, I disconnected USB cable from either phone or computer (because it says that if you are stuck on "waiting for device", disable and re-enable usb debugging) because without disconnecting the cable, phone didn't let me disable the USB debugging..
So looks like I am missing something here??

22andy2 said:
PeteSeiler2010: I haven't tried different USB port yet. I will try tonight and see if it goes through.
For usb debugging, I tried that as I mentioned. Let me just conform what I did. When it says "Waiting for device" for several seconds, I disconnected USB cable from either phone or computer (because it says that if you are stuck on "waiting for device", disable and re-enable usb debugging) because without disconnecting the cable, phone didn't let me disable the USB debugging..
So looks like I am missing something here??
Click to expand...
Click to collapse
want a much easier method? install speedmod kernel using odin, reboot into recovery, advanced features (not the CWM version), and choose the option that says something like "root phone" and choose the "simple" option. congratulations, you are now rooted and running a custom kernel with CWM that can install a custom ROM.
next time, please do not post this in development as this has NOTHING to do with development. Q&A or general next time, please.

How did someone with no posts, post a question in this section? I thought you had to have a minimum of 10 posts to post in here.

I am sorry if I have missed that rule for the new posting but I am new (just two days old) into the android world and for the xda forums as well..

22andy2 said:
I am sorry if I have missed that rule for the new posting but I am new (just two days old) into the android world and for the xda forums as well..
Click to expand...
Click to collapse
So why is your join date Dec 2007?

CB650 Wolf said:
So why is your join date Dec 2007?
Click to expand...
Click to collapse
thats when I just registered.. I will be the active member now as I officially own the android phone.
I really appreciate all of you guys work and I didn't mean to offend any one by posting the thread here.
I already apologize for missing the rule for the 10 minimum posts on forum before posting.

I rooted my device successfully by using odin. Thanks all of you for the suggestions.

[Q] At wits end!! Please Help.

OK folks, I know some of you are going to jump straight down my throat, but please, back off and stick to the friendly forums that this used to be where anyone would help anyone.
the story so far is that I once loved my Nexus One, I've had it since launch, I have ran Cynogen Mod 7 for a couple of years, I have had MUI roms running, I have played with various kernels, updated radio, upgraded hardware, all was going wonderfully.
the one thing I could never get was full SU!! Heck knows why!!
I then started getting random problems and downloaded the original google frf83 software and flashed the phone via update.zip using amon-ra recovery.
I thought all was well after this, as my phone received 3 OTA updates and now my phone is on...
Android 2.3.6
Baseband 32.41.00.32U_5.08.00.04
Kernel 2.6.35.7-59465-g42bad32 ([email protected] #1)
Build GRK394
I noticed that in the Status (settings) it was displaying my old sim card number, which is not the number for the sim in the phone now. his I thought was odd and that something had gone wrong.
So as most of us would do, I went to boot AmonRa recovery and it wasnt available, it had been overwritten with the default recovery; ok lets just ADB and reflash it, I hadnt used ADB for a couple of years because I did everything through AmonRa's awesome recovery!!
So off I go, install the SDK, all the appropriate packs including the USB driver, just like I did when I originally flashed the phone with the recovery image!
But an old problem came back that I hadnt even been bothered about because I always put stuff on SDcard via a card reader!!
I have had consistent problems with my nexus one for some time now in regards to the USB drivers, no matter what I do the phone will not install and I believe it could be some conflict in the device.
I am running Vista Ultimate (fully registered) and no matter what I do I cannot get the Nexus One to install. It will only display as unknown device, which is absolutely useless.
I have browsed every post and tried everything I have found, and yet nothing is working. I have used devmgmt, I have tried the roll backs, I have tried to install every driver available to get it working. I have uninstalled the device, updated drivers after fresh install attempts, I have even formatted my laptop thinking it may have had a corrupt OS and bought Vista Ultimate.
I am not a complete noob and I have been around these forums for some years, but I never thought I would have to cry out like a 4ucking Noob with such a seemingly simple problem, but it is not simple, I have done everything I can possibly find!!
I must get the USB working in order to get the recovery back, I can access my phones default recovery but it will not work when trying various roms as update.zip!!
I have tried the terminal commands on the phone to install the recovery.img but I do not have SU access and the phone point blank refuses.
I have attempted to change and remove the recovery files reffered that are causing the revert to default recovery, but shock.. I cannot delete because of insufficient permissions. I cannot ADB because the USB driver refuses to install.
So if I cannot change the files due to permissions, I cannot ADB because of USB, I cannot get to Ra's recovery because of bootfiles, I cannot use default recovery to update.zip... I am absolutely losing my mind and I'm going nuts browsing the forums for the second week running, yes I am now on day 12 of trying to fix this problem and at a complete loss...
Can someone please help??
I will even allow remote access to pc because I am that desperate to resurrect my beloved Nexus One.
I also have a Galaxy I9000 without 3 button download mode but that is an entirely different story!!
Please just someone, come to an oldskoolers rescue, and yes PAYMENT will be given to the knight in shiny armour!!

You could try on another computer which doesn't run Vista

tommert38 said:
You could try on another computer which doesn't run Vista
Click to expand...
Click to collapse
Or just use fastboot instead of adb...

His Nexus One isn't recognized by the computer, so that won't help unfortunately. Also, I've never heard of build GRK394..

tommert38 said:
His Nexus One isn't recognized by the computer, so that won't help unfortunately. Also, I've never heard of build GRK394..
Click to expand...
Click to collapse
Install the drivers for fastboot already Jeez and then read How to use android for dummies.

[Q] Samsung Galaxy s5300 - will rooting and flashing a ROM help?

I am a n00b, and I accept that.
I have a Samsung Galaxy Pocket (s5300). It looses network connection (while still showing that it has signal). I took it to a Samsung dealer and they reloaded the software, and a week later it does it again.
My question: Will rooting and installing a custom ROM fix this? (I don't want to root and custom ROM if I should rather take it in for repairs again and then do it when they have fixed it).
Your help is appreciated, by this n00b.

[email protected] said:
I am a n00b, and I accept that.
I have a Samsung Galaxy Pocket (s5300). It looses network connection (while still showing that it has signal). I took it to a Samsung dealer and they reloaded the software, and a week later it does it again.
My question: Will rooting and installing a custom ROM fix this? (I don't want to root and custom ROM if I should rather take it in for repairs again and then do it when they have fixed it).
Your help is appreciated, by this n00b.
Click to expand...
Click to collapse
Try a different modem.
"To err is human, to forgive is divine"
Sent from my SGS II

immortalneo said:
Try a different modem.
"To err is human, to forgive is divine"
Sent from my SGS II
Click to expand...
Click to collapse
It's an Android phone, not a modem. I really like this phone and would love it to work properly.

[email protected] said:
It's an Android phone, not a modem. I really like this phone and would love it to work properly.
Click to expand...
Click to collapse
Lol... You've got a lot of reading to do. Modem is part of your phone that deals with connectivity. Since you have not rooted and don't want to, send it in. But yes rooting it and flashing a different modem would help
Sent from my Note ll

Thanks

Well, I thought I might as well root and load a custom ROM onto my phone (seeing as the Vodacom software on it does not seem to work properly).
I managed to root the device easily (following a tutorial on the XDA forums). I then downloaded odin and a cusom ROM from the site, custom ROM needs the stock ROM installed, so I downloaded that as well. OK, phone shows green android logo in Odin Mode, now Windows fails to install the drivers for my device.
Let's try Linux (I am running Peppermint Three), I install Heimdall (works like Odin), the ROM I downloaded for Odin won't work here and there isn't a ROM available for Heimdall for the s5300.
So now I am stuck halfway through loading a different ROM onto my phone. Have heard I can try installing KIES for the Windows drivers. Will try that and report back.
*** Time for an update:
Downloaded and installed Kies. Windows now properly detects my phone, Odin showed the yellow block it was supposed to, and my phone is rooted and flashed to stock Android. Thanks to everyone at this forum for their great articles. Hopefully I will get better at this stuff some day.

[Q] O2X bricked after restoring from nandroid backup? [Linux-related]

Hi there, honored experts!
Today I got my precious Optimus Speed bricked, after I successfully restored a recent nandroid backup.
I've been happily running paranoid android for the last months, and often updated the phone with the help of goo.im manager. Today I did a full factory-reset after the CWM upgrade-process, to get rid of the old "disappearing keyboard"-bug. I backed up all my apps and data with superbackup and titanium-backup, and even created an online nandroid-backup (freshly updated nandroid-scripts and patch for my device).
After the reset I had issues to restore everything, since ti-backup often got stuck in batch-restore-processes. Because I couldn't stop the stuck process, it required me to soft-reboot the device a few times. And in the end, it failed to boot.
So I went into CWM, and restored my nandroid-backup. This went fine, and no errors were reported. But after soft-rebooting it, it only showed the LG-Logo-Screen, and nothing else happened. So I tried to get back into CWM - with no luck .
I've tried every possible key-combination I could find, and the only mode I can bring my device into is "S/W Upgrade". In this mode it is recognized by my laptop (running Linux), but rustys recovery fails, because nvflash reports:
Code:
sh ./flash-recovery-ext.sh
Nvflash started
USB device not found
even though lsusb shows:
Code:
# lsusb
Bus 001 Device 017: ID 1004:6000 LG Electronics, Inc. KU330/KU990/VX4400/VX6000
I'm fresh out of ideas - maybe one of you can help me out? Otherwise the only thing I could try now is to turn it back in where I bought it.

I'm no expert at these matters,but I can tell you from my experience because I bricked mine P990 two times and was able to bring it back to life.
In both instances I used Smartflash, found V30a ICS ROM for it and flashed it over it, and it came back to life.
But when you do this,you will have ICS bootloader and you won't be able to install PA or CM since they work on the old bootloader.
Or you can flash it to the stock Gingerbread ROM https://hotfile.com/dl/168874678/8ea13eb/NVFlash_LGP990_V20Q_EuroOpen.7z.html
And I would recommend reinstalling nv flash drivers before,just in case the error is on your computer. http://www.mediafire.com/?cdgwwgkdozht8pw

Also, try All in one kit, http://forum.xda-developers.com/showthread.php?t=2020737 maybe it will help you. I repaired my bricked phone with it a lot of times. Its very easy to use as everything is explained there.

Jasper_bin
this device is 99% unbrickable
just go ahead with the AIOT by SPYROSK (this guy is a silent killer with amazing skills)....link in my signature
it works like a magic....real magic if you read the opening post and do it properly
Thanks

Hi Obersoldat,
I'm currently on the new BL - PA has a spin for the old, and one for the new BL. Is smartflash a windows-binary? Since I currently have no access to a windows-machine :-/.
Hi Make1 and Sreeprajay,
thanks for your recommendation. I'll also hit that thanks button if it helps me solve this, but first I've got two questions:
1st: As said above, I currently have no access to a windows-machine. Therefore I wanted to try working this out with nvflash on Linux. AFAIK this should be possible, even though there would be no nice menu-system. The question is if there's a difference due to the special drivers on windows which are mentioned everywhere? I ask that, because I've successfully rooted my buddies TP-Tablet on Linux with adb, and without any special drivers (which were said to be mandatory on windows).
2nd: What am I aiming for in Spyrosks AIOT? Instantly I'd think option 2B (Change Recovery with NVFlash) might help me. As in ProgMaqs Full-Brick-Repair. Then I'd look into the batch-Scripts, and simply manually execute the needed Steps.

Ok, so I dug up my old windows-tower from the attic, soldered a power-cord that I was missing, and fired it up. Took me more than 2 hours - thats what I meant with "no access to a windows-machine".
I ran Spyrosks AIOT, but no luck . The only possible ways to save this phone, are IMHO the nvflash based methods. But nvflash on windows reports the same error: "USB device not found".
Yes - I installed the driver out of the AOIT - but it seems that it cannot be activated for my phone. I think it's not in the right state to be recognized as a device that would need that driver, so windows won't activate it.
Attached is a screenshot of how the phone appears in my Device-Manager when connected in "S/W Upgrade"-mode.
Do you still think this phone can be saved somehow? I had high hopes as I read that this phone is nearly unbrickable

Come on, please someone help me. I'm not trying to be lazy here, or have someone else do the searching/thinking for me. I just can't figure out how to solve this - propably due to a lack of experience.
I don't think this is a simple problem - but there must be a reason why that phone is said to be 99% unbrickable. I hope I'm not the other 1% in this case.
Anyone?

I would have known what to do if the pc recognized your phone when you've installed drivers because almost exact problem happened to me few days ago.
Okay, now I will suggest random things well, I'm just trying to help :/
I suppose cwm isn't working?
Then about S/W Upgrade mode, have you installed APX drivers? Because when you connect phone in S/W upgrade mode with APX drivers installed then Device manager shows no errors.
You also mentioned that you restored a backup so it means you have latest backup of your system which you wanted to use. Tell me if I'm not correct. Then full wipe of your phone will fix everything, you will just flash a new rom, do the rooting stuff again and then you can restore your backup again.

maybe its because you are on linus, try restoring a STOCK GB KDZ if you are on the old layout, if you are in the new layout use a official LG smartflash, try that on windows and use AIO Toolkit !

Hey, thanks a lot! Actually the last Tip did the Trick!
After I downloaded and installed the full LG phone suite, I was able to restore the phone with the official LG support-tool. During the installation of the PC-Suite one or two new drivers were installed, which then lead to the phone beeing correctly recognized by the Windows 7 on the PC.
So to sum that up, and clarify the questions I brought up earlier:
Can the windows Drivers do more than what the native ones on Linux?
Absolutely yes! Only the drivers which came with the PC-Suite made my PC recognize the P990, which it didn't do before. Propably even the special drivers which come with Spyrosks AIOT depend on them (correct me if thats not true).
Can I restore my bricked phone with only Spyrosks AIOT?
In my case that did not work. Even after installing the PC-Suite and its drivers (including the support-tool drivers) the nvflash based methods in spyrosks AIOT did not find my device, which was connected over USB. But LGs support-tool did, and revived the device .
Hope that helps other people in my situation. The legendary unbrickability of this thing is proven once again
Thanks to all of you (Yesyesyes - I'll hit that button right away!)

[Q] Can't root optimus 2x *PLEASE HELP*

Hello,
probably this question was asked a lot but I can't find anything that can help me.
I've latest ICS software on my LG Optimus 2X (4.0.4) and I would like to root my phone. I've checked USB debugging mod and unknown sources, tried every method I've found and still can't root my phone. Also I've installed drivers for my phone and tried on other pc, same think. I've tried method without PC, Z4root. It starts to root and in one moment app crashes and I must restart my phone to open it again. Super one click stuck on step 5 or 7. I read threads about that problem and I couldn't find any usefull. Please help. What's wrong? I really need to root my phone because it starts to be slow and I'm already sick of running background apps.
Thank you for help

I've finally made it. I've download all in one tool kit and in main windows pressed ''I'' button and installed NVFlash and it worked finally