First of all, just wanted to say that this is a fantastic forum and resource!
I've got a Captivate with 2.2 Froyo (build FROYO.UCKB1) on AT&T, and so far I haven't been able to root. I've followed the wiki and new users guide without having much success. It seems like Samsung or AT&T have introduced some extra barriers to rooting(?)
I initially tried dropping an update.zip tool into my /sdcard folder and rebooting. The error I received was "E:signature verification failed"
After that I tried using ADB to replace the /system/recovery file, but no luck.
So I also tried the SuperOneClick application, using VirtualBox to load a Windows XP guest (I'm running OS X Lion). Unfortunately, the phone is disabled in the list of USB devices. I tried adding it to a filter in Preferences->Ports->USB. SuperOneClick freezes on the "Waiting for device" part.
Has anyone had the same issues?
Related
Hi, i cannot use Galaxy S I9000 One-Click Root program. Always getting this error. i already install net framework:
Im also getting same error while running one root...can anybody help me or suggest an alternative?
I used SuperOneClick root...I'm not sure if this is what you're referring to, or if they're the same, but one thing some don't know is that to root you must
- Enabled USB debugging
- Connect USB Cable, but DO NOT MOUNT SD CARD
Hopefully, one of those do the trick. If not, you may want to try something like Z4root.
Porblem solved, was clicking on the wrong file. Clicked on root.bat and everything ok. I tried using superoneclick but it keeps on looping. Any idead why it does that?
Hi,
I tried to use psouza4's one click root, but I keep getting an unhandled exception error. I double checked the instructions and believe I am following them correctly, but to to avail. I am using XP, but using his tools for Windows 7 first as instructed. He does have a script specifically for XP in case the Windows 7 tool does not work, but I see that it does not have an unroot or restore option.
Am I missing something that is causing this error, or will I have to use the special XP one? If so, how do I unroot if necessary? He indictaes that the Windows 7 tool should work for most XP users, I wonder what makes some (and apparantly mine) not work, unless this error is something unrelated.
Any input would be appreciated. This is my first foray into android from Windows Mobile, so I am quite (obviously) a noob.
Thanks!
I haven't used his tools, but if you are on the leaked OTA 5.7 that exploit will not work. Try zergRush
I've downloaded and tried SuperOneClick 2.2 and 2.3. I'm really wanting to root my Lg Thrill but it just isn't cooperating.
I have my phone on usb debugging and unknown sources is checked! I've tried starting up SuperOneClick before and after plugging in my phone. Each and every time I get the same error:
"The application failed to initialize properly (0xc0000135). Click on OK to terminate the application"
I read in another thread that this could be caused by registry errors so I did what I could to fix any that I had. This has not worked either. Any help is greatly appreciated. Thanks in advance...
EDIT: I finally got it to root... mods please delete this post. Thanks.
Can you post how you figured out the problem?
I may start soon, would like to prepare for any possible predicament.
Thanks
The way I got it to work was installing the latest microsoft .net framework for my computer. I'm using an older laptop and it had recently been wiped clean so that I could do a fresh install. I forgot about about reinstalling all the microsoft garbage onto this computer Once I installed the new .NET framework, the superoneclick worked like a charm. Finally got all the bloatware off and even without a ROM this phone runs MUCH MUCH better than it did before.
Hello folks.
Had a go at rooting Samsung i9000. It's quite old, and clearly clogged up to the hilt with the apps very laggy and frequently crashing. I quite fancied getting rid of the bloatwear too and the bloody annoying splash screen at start up!
Needless to say, it's all gone belly up. I've tried a couple of things using the guides here, but I don't want to keep pushing my luck in case I completely brick the device.
I'm running an i9000 in the UK on the o2 (Well, giffgaff) network. It was running Gingerbread, 2.3.5 I think. As it stands, I can get into the download option, but nothing else. I had used Odin 3, but have since read that the highest level is 1.83, which I now have. This might have caused the initial problem, but it's "soft" bricked. I've tried to flash over a stock rom again, but I keep getting failure notices. I can't get past the "Can't open the serial (COM) port" error message on Odin. I've downloaded the drivers and they have successfully installed.
One thing I don't think I did beforehand was to enable USB debugging.
I also tried the guide on here which uses the pit method, and curiously enough, it went through without the COM port error. The only thing that did, however, was to remove the "Phone + PC" logo. I am still able to get into download though.
Help! I am due to get a new phone very shortly, but it would be very useful to get the phone working again in the meantime! Any help very much appreciated.
If Kies is running in background it will fail, Go into Kies, Tools -> Preferences, unselect "Run Samsung Kies automatically when a device is connected", save the change, close out of Kies, and then restart ODIN. Try flashing now.
Try uninstalling Kies and then reboot and install the Samsung Drivers. Try then.
PFFFFFFFFFFFFFFFFTTT, sent from my i9000
I got my Air 3G a few weeks back and have been largely impressed with it. £120 for a 3G enabled Windows 10/Android 5 tablet? Bargain.
I recently decided to get around to rooting it and then the problems occurred. I followed all of the tutorials I could find and none of them worked. The Toolbox, iRoot, vRoot, Kingroot - on device and from desktop - all said they'd worked but upon reboot none of them had.
I then tried to go straight to updating to a ROM with built in root but that didn't work either. Following the Toolbox instructions I got a "couldn’t find boot device handle" error, followed by the message "E:No valid installer medium found". I Googled them but found nothing useful. Hopefully anyone following in my footsteps will find their way here.
Eventually I discovered this thread and followed the instructions within. At last I was rooted.
Next I tried to install the Xposed framework using TecKnight's tutorial. This didn't work either, despite me running it both as an admin and from the command line directly. It said it had both times and Android even did its 'updating system apps' thing upon reboot, but the framework was nowhere to be found.
I still haven't got it working but all of these issues are leading me to wonder if there's something special about the model I have.
Should I try flashing one of the clean 5.0 ROMs? Is it even safe to do it given the issues I've had so far?
Any observations/suggestions would be gratefully received!