Related
Okay, I have been able to get ADB access to the I-Mobile i858; but I cannot get root. There is an SU program and Busybox pre-installed on this device. I tried changing the permissions of SU to 4755 and 6755 without success. It looked like it was trying but something is interfering with root. Maybe if we work together we can figure this out. I even modified a flash image to set the permissions when it flashed the new image. That still did not give me root.
Here is how you get ADB to connect. It is kind of a pain but at least now we can talk to the device.
1. Install the "Android Terminal Emulator" by Jack Palevich from the Android Market to your device.
2. Download the Android ADB device drivers from this link and un-rar them.
http://www.generalmobile.com/support/dstl1/DSTL1_USB_Driver.rar
3. Open Device Manager on your computer.
4. Make sure debugging is turned off on your device in Settings>Applications>Devices.
5. Open the Terminal Emulator you downloaded in step 1 and type in the following command "<enter>setprop persist.service.adb.enable 1<enter>".
6. Go back to Settings>Applications>Development on your device and turn USB Debugging on. Click OK when prompted to confirm.
7. Plug the USB cable into your i858 and then your computer's USB port. In my tests using a reliable hub is okay.
8. You will see a device under Universal Serial Bus Controllers that says either "USB Mass Storage Device" or "USB Composite Device." Watch that section in Device Manager to see which one is the new one when you plugged in your device.
8. Uninstall the Mass Storage or Composite Device that was added to Device Manager when you plugged in your computer. You do this by right-clicking it and selecting "Uninstall".
9. On Device Manager Click the Actions pull down menu and click "Scan for hardware changes".
10. If you are lucky an unknown Android Device will no be listed in the Device Manager as not working due to no drivers installed. Go to properties of this device and update drivers browsing to the folder when you unzipped the drivers downloaded in step 2 above. The Android ADB drivers will now install.
11. If that doesn't work keep uninstalling the Mass Storage or Composite Device and rescan until the Android Device appears in Device Manager.
12. If you unplug it you will have to go back to step 4 but you can skip step 5.
13. If you reboot or turn off your device you will have go to back to step 4.
14. Unfortunately, I have to do this ritual every time I want to connect to the device by ADB; but heck it sure beats having no ADB access at all.
Now that you guys have ADB access let's rock this device, root it and have some fun. I spent all day trying to root it without success. I did manage to make the phone do some weird things and reboot a couple of times. I was changing permissions for the pre-installed "su" program in "/system/bin" but obviously there is something else that needs to be done to root this device. At least we are one or two steps closer now.
Thanks for sharing with us your work
For me i just delete apps befor i flash the rom because after when the apps installed i can t delet them because there are protected.
closer66 said:
Thanks for sharing with us your work
For me i just delete apps befor i flash the rom because after when the apps installed i can t delet them because there are protected.
Click to expand...
Click to collapse
If the device was rooted then you could delete them on the phone.
I-Mobile i858 has been rooted!!!
Okay, the I-Mobile i858 comes pre-rooted but there is something wrong with the way it was setup and root doesn't work. You download a program called Universal Androot and let it re-root the device so that it corrects whatever mistakes the ODM put in that made root not work. In your browser go to the following URL and install the program.
http://bit.ly/cwNm9u
When you run the program it says the device is already rooted; but there is some problem as the rooting is not complete. So you tell the program to root the device again. After it is done the device is rooted and stays rooted after reboot. Programs like Boot Control that require root access now work. There is a SuperUser Authorizer app that will intercede the first time and ask you if you want to give root permission to that app. That is a good thing and will protect you from malicious programs getting root that can cause you all kinds of nightmares.
But, I am root and I still cannot uninstall the pre-installed apps. How do you do that even as root? I am missing something.
hey great new s thanks for your work today i went to the i-mobile shop in samui and there say rom update is official confirm to 2.1 or maybe 2.2 there dont know excactly
Now i have root thanks. But following problem when i try to delete some apps that pre installed.
Says delete it but in real do not delete the app ummm
do you have any id why i can not delete the apps??
closer66 said:
Now i have root thanks. But following problem when i try to delete some apps that pre installed.
Says delete it but in real do not delete the app ummm
do you have any id why i can not delete the apps??
Click to expand...
Click to collapse
Any pre-installed apps cannot be deleted the normal way. Install Titanium Backup from the Android Market and let it have root when requested. You can use that program to uninstall pre-installed apps with root.
Rooted! ADB! Now this device gets much more useful! Great work jboxer, thanks!
BTW the rooting app has been updated to v1.6.1
Home page:
http://blog.23corner.com/tag/universalandroot/
Download:
http://bit.ly/aa4jxJ
Follow this Link droidsans.com/node/4018
ROOTING:
Since z4root, one of the easiest ways to root, is not working on Froyo in Galaxy 3, I decided to make this separate thread for instructions on how to root Froyo using Superoneclick.
First and foremost: Enable USB Debugging by going to Settings>Applications>Development. Make sure it is ticked.
Download the attached Superoneclickv1.5.zip file. Extract its contents. Make sure your phone drivers are installed on the computer (Samsung Kies). Then follow the steps:
1. From the extracted contents, run the file named Superoneclick.
2. Turn off your phone, then connect it to the computer using the USB Cable. Don't turn on the phone. Keep it off but connected to the computer.
3. In Superoneclick, click on the 'Root' button. After a few seconds, it'll say 'Waiting for device'.
4. Now turn on your phone (while it is still connected to the computer). Superoneclick will detect the phone.
5. Now the phone will be rooted, while it is starting up. When it is started, it'll be rooted.
6. After rooting, download and install busybox on your phone. It should take care of any slowing down of your phone after rooting.
That's it. The phone is now rooted, although it would be so much better if z4root worked on Froyo..
For those getting stuck at the 'pushing raceagainstthecage' step, try this method. Credits go to haree:
1. login as admin and then open the application. Or right click on Superoneclick.exe and click on 'Run as administrator'.
2. turn off ur Virus protection
3. remove all the additional external USB devices(this seems to confuse the SW)
i removed all the above mentioned
and then follow the instructions u will be successful
it worked for me now i have 2.2 and rooted
Click to expand...
Click to collapse
UNROOTING INSTRUCTIONS:
Unfortunately, the method to unroot by clicking on the Unroot button in Superoneclick does not work. So follow the following steps to unroot.
1. Download rootexplorer.apk (attached) and install Root Explorer on phone.
2. Run Root Explorer. A 'Superuser Request' prompt will come up. Press Allow.
3. Now, on the top, there will be a button saying 'Mount R/W'. Press it. It should change to 'Mount R/O'. The button should say 'Mount R/O' in order for you to be able to do anything in the following steps.
4. Now scroll to the bottom, click on system. Then click on bin.
5. In the bin folder, look for a file named 'su'. Long press on this file, and select Delete to delete it.
6. Now go back to the system folder by pressing the Back button once.
7. Now enter the app folder. Scroll down and look for the file named 'superuser.apk'. Long press on this file and delete it.
8. Exit Root Explorer after this. Uninstall it if you don't want to use it.
9. That's it. Your phone will be un-rooted.
Another method to unroot:
1. Download and install Terminal Emulator (attached).
2. Run Terminal Emulator on the phone. If you don't see a keyboard to type, press Menu and press Toggle Soft Keyboard.
3. Type su and press enter. Press Allow on the 'Superuser Request' prompt. The $ sign will change to a #.
4. Now type the following line exactly as it is and press enter: mount -o rw,remount /dev/block/mtdblock3 /system
5. Nothing will happen visually. The pointer will shift to a new line.
6. Now type the following line and press enter: rm /system/bin/su
7. Again, type following line and press enter: rm /system/app/superuser.apk.
8. Now exit Terminal Emulator. Your phone is un-rooted.
Hehe, first i thought it makes no sense to write a howto on this since its described in the SOC thread anyway, but man the idea to do it during boot is ubercool, didn't think of that...
FadeFx said:
Hehe, first i thought it makes no sense to write a howto on this since its described in the SOC thread anyway, but man the idea to do it during boot is ubercool, didn't think of that...
Click to expand...
Click to collapse
I know it's explained in the SOC thread, but many people keep asking on the "Samsung Galaxy 3 GT-i5800: root, gps fix, upgrading" thread about rooting Froyo, so I thought it's better to have one SOC thread right in the Galaxy 3's Development Section. It'll save everyone reading through a lot of pages on that thread..
addicted2088 said:
I know it's explained in the SOC thread, but many people keep asking on the "Samsung Galaxy 3 GT-i5800: root, gps fix, upgrading" thread about rooting Froyo, so I thought it's better to have one SOC thread right in the Galaxy 3's Development Section. It'll save everyone reading through a lot of pages on that thread..
Click to expand...
Click to collapse
hi
when i see a few reports that this is working for our G3 ill add this link to the roll up thread very nice of you to give this info to all keep up the good work
one question will this also un root the phone
haree said:
hi
when i see a few reports that this is working for our G3 ill add this link to the roll up thread very nice of you to give this info to all keep up the good work
one question will this also un root the phone
Click to expand...
Click to collapse
Can't unroot using the same procedure, but have added another procedure to do it.
This method does work for everyone. The only new step in my procedure is to do it while the phone is booting.
help! !
cant root. stuck at "waiting for device"..... tried everything.. no luck. can anyone help?
coolzarjun said:
cant root. stuck at "waiting for device"..... tried everything.. no luck. can anyone help?
Click to expand...
Click to collapse
Are your phone drivers properly installed? Does your computer make a 'Hardware connected' ding sound when you turn on the phone? If not, then you'll have to install Samsung Kies and then connect the phone to the computer to install the drivers. Try rooting after that.
all drivers are installed.. i reinstalled twice.. when i connect in usb debugg.. says installing some adb stuff after fews secs.. comp says hardware might not work properly not properly installed. all other drivers wrk fine.. wat can i do to install adb drivers properly. . i have windows xp
coolzarjun said:
all drivers are installed.. i reinstalled twice.. when i connect in usb debugg.. says installing some adb stuff after fews secs.. comp says hardware might not work properly not properly installed. all other drivers wrk fine.. wat can i do to install adb drivers properly. . i have windows xp
Click to expand...
Click to collapse
Connect your phone to your computer. Then open the Device Manager. Then look for the entry 'SAMSUNG Android Composite ADB Interface' in the list. It might be under the ADB Interface tab. Right click on the 'SAMSUNG Android Composite ADB Interface' and uninstall it.
Then reconnect your phone to the computer and see if the ADB drivers get installed properly this time.
did that also....uninstalled and connected the phone. still the same error..
hardware not properly installed.. it might not work properly
i got windows xp 32-bit
can u help ?? plz !
coolzarjun said:
did that also....uninstalled and connected the phone. still the same error..
hardware not properly installed.. it might not work properly
i got windows xp 32-bit
can u help ?? plz !
Click to expand...
Click to collapse
Sorry, I'm using Windows 7, so I've no idea what to do about the drivers in Windows XP. Try updating Kies..
i also have win 7 and it doesnt work...help??
reist said:
i also have win 7 and it doesnt work...help??
Click to expand...
Click to collapse
I can't help if the drivers on your computer are not installed properly. After connecting the phone while it is ON, open the Device Manager and see if the ADB driver is properly installed.
If the drivers are properly installed, this method will work..
Edit: As mentioned by mhndk14 below, enable USB Debugging in Settings>Applications>Development.
I also had the same problem with windows 7. Just make sure that the USB Debugging is enabled and then try again. It worked for me.
how to bring the phone back to factory settings
hi how can i get back my phone to the original factory settings? i rooted using z4mod and when unrooted the live wallpapers wont go... and how do i get my boot menu when restarted on my 1 5801??
nageshkaja said:
hi how can i get back my phone to the original factory settings? i rooted using z4mod and when unrooted the live wallpapers wont go... and how do i get my boot menu when restarted on my 1 5801??
Click to expand...
Click to collapse
To remove the Live Wallpapers, you'll have to root your phone, and then use Root Explorer to remove the files Livewallpaperspicker.apk from system/app, and libRS.so and librs_jni.so from system/bin. Then un-root your phone. Be sure to press the 'Mount R/W' button in Root Explorer to be able to delete the files.
As for restoring your boot menu, that procedure is there somewhere in the Development section. The boot menu changes because of upgrading, not rooting.
It seems i have lost haptic feedback after rooting(jpb), anybody else experience this?
Edit: lol
It was probably sue to the "forced" reboot, but I accidently dropped my phone (batteries feel out) and now it's working
stubborn_d0nkey said:
It seems i have lost haptic feedback after rooting(jpb), anybody else experience this?
Edit: lol
It was probably sue to the "forced" reboot, but I accidently dropped my phone (batteries feel out) and now it's working
Click to expand...
Click to collapse
Yeah, haptic feedback stops working sometimes on JPA and JPB after rooting. But restarting the phone corrects it. (Although your method of restarting the phone was too brutal!! )
Thanks addicted2088...worked perfectly...
successfully rooted..........
now i need to know how to install live wallpapers......
thanks
I have downloaded the one click and samsung drivers. The program opens fine. But I have read some people getting phones messed up from rooting with this program?
Should I remove the SD card first before rooting?
Does this program work with 2.2 one click for Galaxy?
Thanks!
Hey
the version i used is 1.7 and no problem here ....
I have read somewhere that you should unmount your sd card , well i didnt and still got phone rooted..
i dont see much of problem with it ..... it will take around 5 mins so just be patient.....dont forget to install samsung drivers .... and put phone into developer mode
Can not get it to work.
Yes I did download Samsung drivers succesfuly.
Yes I enabled Debugging mode succesfully
Tried using both One click 1.7 in Rage mode. Tries to work but just cursor flashing and does nothing.
Then used the other One click program that comes up with BLUE SAMSUNG I9000 and has choice to One click 2.1, 2.2 or remove root.
I choose 2.2 and then phone resets like when I used Clockwork on my old HD2.
I chose correctly to install the files.
PHone loads files but then get error code and wont install them. Reads Signiture Verification Failed!
I read others having same issue of phone not letting files install.
Anyhelp!
I know its not rooted as Titanium Backup is not getting root permission..
iceshark said:
Can not get it to work.
Yes I did download Samsung drivers succesfuly.
Yes I enabled Debugging mode succesfully
Tried using both One click 1.7 in Rage mode. Tries to work but just cursor flashing and does nothing.
Then used the other One click program that comes up with BLUE SAMSUNG I9000 and has choice to One click 2.1, 2.2 or remove root.
I choose 2.2 and then phone resets like when I used Clockwork on my old HD2.
I chose correctly to install the files.
PHone loads files but then get error code and wont install them. Reads Signiture Verification Failed!
I read others having same issue of phone not letting files install.
Anyhelp!
I know its not rooted as Titanium Backup is not getting root permission..
Click to expand...
Click to collapse
Down root check fron the market. Just because Titainium is not getting root permission does not mean it's not rooted. It’s not that difficult to root the SGS 4G Phone. The first thing you need to do is make sure your phone is communicating with your computer. Install the Samsung USB drivers.(make sure you have the right drivers for your O.S. either 32bit or 64bit) In your phone go into Settings/Applications/Development and make sure you check “USB debugging”. Connect your Tethering cable to your phone. On your home screen you should see “USB Connected” popup on top of your screen. You should be able to press USB connected button from the drop-down menu on the home screen and see the external SD card on the computer now. If that works then Turn off USB storage. (leave “USB debugging” checked) Then Download SuperOneClickv1.7-ShortFuse, expand the file and go to SuperOneClickv1.7-ShortFuse Directory. Run the SuperOneClick App. When it opens don’t change anything and just click “Root” and let it run. It should say rooted when done. Then go to the Market on your phone and get Titanium Backup and install it. It will ask for SuperUser permission and accept that on your phone. If that fails press “Problems” button, Then “Get Busybox”. Install the new Busybox. You may have to close and reopen Titanium Backup again. BTW this post should be in general.
yeah, i dont suggest you use rage. it took forever for me to root the phone that way. i left it on psneuter and it rooted in about 5 minutes
Sent from beyond the Galaxy
Thanks guys! Yes Rage was the issue. I followed his instructions and left in pnuueter and it worked perfectly! Now my Titanium is rooted and working.
Now if we could just get a good Apsd to let us format the SD card to ext 4 that would be a perfect world!
Thank you.
Moved to proper forum.
menacetwosociety said:
yeah, i dont suggest you use rage. it took forever for me to root the phone that way. i left it on psneuter and it rooted in about 5 minutes
Sent from beyond the Galaxy
Click to expand...
Click to collapse
^ thats what i forgot to tell him to change it lol
Rooted my SGS4G using Superoneclick.
2 things I noticed. Your AV will think that Rage is a virus. NOD32 kept quarantining it. I turned off both AV and FW.
Also, after you install the Samsung USB driver, reboot your computer. I had that "waiting for device" message until I rebooted computer. Then it flew. The driver doesn't offer to reboot, or tell you to.
Z
Hello everyone I'm in the dinc2 forums. I'm a marine and the other day I was showing a guy I work with my s-off rooted dinc2 running miui and he immediately was interested. He has the inspire and I was looking for a little know-how on what to do and we don't really have the time to search religiously due to work. He's running stock 2.3.3 any help would be appreciated if you want to email me my email is [email protected]
Thanks!
Linch89 said:
Hello everyone I'm in the dinc2 forums. I'm a marine and the other day I was showing a guy I work with my s-off rooted dinc2 running miui and he immediately was interested. He has the inspire and I was looking for a little know-how on what to do and we don't really have the time to search religiously due to work. He's running stock 2.3.3 any help would be appreciated if you want to email me my email is [email protected]
Thanks!
Click to expand...
Click to collapse
Ace Hack Kit
That will walk you through the root/s-off/unlock process. It's been VERY much simplified over time, now it's just a 1 step process. Read the effen manual a few times before you start - but like I said, at this point it's very straight-forward.
Once installed hit up the MIUI thread. Basically you'll download the ROM to your SD, boot to recovery, perform a wipe, and flash the ROM
And thank you for your service and dedication to this wonderful country of ours!
He said the adb drivers won't connect
Any specific error messages? At what point is this happening? Is he trying to run the hack kit or just trying to access an ADB shell?
The hack kit contains all necessary adb files/drivers
Make sure he's done all of this:
Make sure HTC USB Drivers for Android are installed (included in the Hack Kit @ tools/windrivers)
Disable all malware detection, including Windows Defender
Uninstall HTC Sync
Uninstall Droid Explorer
Uninstall iTunes or stop service
Uninstall Other phone pda or tablet software
We just tried on our lunch we disabled everything the HTC drivers were already installed with sync uninstalled. We were at the pre-step where you run the command as an admin and the command window comes up for a second and closes itself. Does his phone need temp root to run the kit?
trouble rooting my phone
when i run the hack as admin on windows 7 it give an error message this is what the error message says
check adb connectivity
shad0fox04/2011
service not running
error error error
phone not plug in or driver not installed or usb debugging not enable
error error error
pres any key to continue the it just cut off i checked all of that and everything is good to go so what is the problem lol
did u ever find out y adb wont connect im having d same problem
Linch89 said:
We just tried on our lunch we disabled everything the HTC drivers were already installed with sync uninstalled. We were at the pre-step where you run the command as an admin and the command window comes up for a second and closes itself. Does his phone need temp root to run the kit?
Click to expand...
Click to collapse
Did you install the drivers that came with the kit just to be safe?? I just did this like 2 days ago and it worked perfect..
Linch89 said:
We just tried on our lunch we disabled everything the HTC drivers were already installed with sync uninstalled. We were at the pre-step where you run the command as an admin and the command window comes up for a second and closes itself. Does his phone need temp root to run the kit?
Click to expand...
Click to collapse
Has he by any chance tried a different USB port? And is the phone in charge only mode, it's not mounting itself as a disk drive automatically? I don't know how feasible it might be, but if he has another computer available try running it there and see if you get any different results. At least then we might be able to narrow down better whether it's the software, the computer, or the phone.
jonathanj942 said:
when i run the hack as admin on windows 7 it give an error message this is what the error message says
check adb connectivity
shad0fox04/2011
service not running
error error error
phone not plug in or driver not installed or usb debugging not enable
error error error
pres any key to continue the it just cut off i checked all of that and everything is good to go so what is the problem lol
Click to expand...
Click to collapse
Another simple thing that I have to ask about...you guys did extract all the contents of the hack kit somewhere on your computer, correct? You're not trying to run it from the .zip?
If it is extracted,
go to the tools\win\ directory.
Hold Shift and Right-Click in an empty spot, select "open command window here"
type "adb devices" and hit Enter
You should see 12 alpha-numerics listed under "List of devices attached"
If you don't see anything under this, then for some reason adb isn't recognizing your phone is plugged in. In which case I'd try a different USB port or computer
Hi all!
I rooted my Droid Maxx 4.2.2 successfully using an app I pushed to my phone then ran on my phone (MotoRoot I think, but I get the various MotoRoot, Slap, PwnMotos confused) .
Things were just peachy but I wanted to update to 4.4 while retaining root.
So I went to waynekent 's site page 6 page and the guide in xt1080kk.zip to do this.
Made it successfully through all steps and ended up with "Now your device is on a undefiled, clean install of 4.2.2_12.15.15."
and here I stay.
I cannot seem to get telnet to connect to my phone. Both PC and phone are on same WIFI, USB debugging enabled, verify apps off, firewalls and antivirus off. When I try start telnet as system on 2222 using Cydia Impactor, a "PayLoad" program opens and immediately closes with no chance for me to do anything. Telnet program itself times out.
Trying other methods like installing SlapMyMoto or PwnMymoto..apk via ADB results in a install_parse_FAILED_UNEXPECTED_EXCEPTION error
Unknown if related: My write protection has been disabled.
Any help would be greatly appreciated!
Charlierb3 said:
Hi all!
I rooted my Droid Maxx 4.2.2 successfully using an app I pushed to my phone then ran on my phone (MotoRoot I think, but I get the various MotoRoot, Slap, PwnMotos confused) .
Things were just peachy but I wanted to update to 4.4 while retaining root.
So I went to waynekent 's site page 6 page and the guide in xt1080kk.zip to do this.
Made it successfully through all steps and ended up with "Now your device is on a undefiled, clean install of 4.2.2_12.15.15."
and here I stay.
I cannot seem to get telnet to connect to my phone. Both PC and phone are on same WIFI, USB debugging enabled, verify apps off, firewalls and antivirus off. When I try start telnet as system on 2222 using Cydia Impactor, a "PayLoad" program opens and immediately closes with no chance for me to do anything. Telnet program itself times out.
Trying other methods like installing SlapMyMoto or PwnMymoto..apk via ADB results in a install_parse_FAILED_UNEXPECTED_EXCEPTION error
Unknown if related: My write protection has been disabled.
Any help would be greatly appreciated!
Click to expand...
Click to collapse
Got my telnet sorted out but now when I try the command dalvikvm -cp /sdcard/RockMyMoto.jar RockMyMot
I get the message
device is not write protected
executing step 3...
and then it stops there. Any tips?