So I updated this week to GB 2.3.6 using Kies and the official update from TM. It deleted my root access. I have attempted to root it again using SuperOneClick, but that doesn't seem to be working.
Any other options to root?
What version of SuperOneClick? I have only heard of success with version 2.2
I am trying 2.2 now. I was using an older version.
Like the other 200 threads say... SOC 2.2 will root it fine. So will flashing a drhonk kernel using Odin.
I have used SOC on 4 sga4gs now and it worked on all of them.
Sent from my SGH-T959V using XDA App
shannonkish said:
So I updated this week to GB 2.3.6 using Kies and the official update from TM. It deleted my root access. I have attempted to root it again using SuperOneClick, but that doesn't seem to be working.
Any other options to root?
Click to expand...
Click to collapse
Here is a solution that worked for me. Remember to give thanks for their contribution!
I'm not sure whats up with the link, just copy and past.
http://forum.xda-developers.com/showthread.php?t=1329360
shannonkish said:
So I updated this week to GB 2.3.6 using Kies and the official update from TM. It deleted my root access. I have attempted to root it again using SuperOneClick, but that doesn't seem to be working.
Any other options to root?
Click to expand...
Click to collapse
i also face this problem.
when i use SOC, it stucked in step 7(sometimes stuck in step5 )
Go to http://forum.xda-developers.com/showthread.php?t=1194032
Download stock+Voodoo-T959VKJ1.tar and use the directions listed in the thread.
Since you're on stock you'll want to use the ODIN version since you will not have CWM.
Will give you root and CWM Recovery back. I just did this on my sister's phone that she just picked up for free, so it was stock upgraded with KIES. Worked perfect.
Related
Alright so here is the scenario, I had one of the original leaks of Gingerbread and it was rooted. I upgraded to the newest GB .595 so that I could use Netflix. I am an idiot and I used the stock version so I lost the root. I believe if I was already rooted and I had installed GB .595 Deodex I would have maintained root. So here is the question. I would like to have the best of both worlds (netflix and root), which means that I need to have rooted .595. I would like for someone to tell me exactly what needs to be done. I know I will most likely have to SBF back to Froyo and upgrade from there, but I dont know which files I should be using a such.
I believe that all you need to do is flash the rooted .595 zip. No SBF, no data wipe.
Sent from my DROIDX using XDA App
mmaibl2011 said:
Alright so here is the scenario, I had one of the original leaks of Gingerbread and it was rooted. I upgraded to the newest GB .595 so that I could use Netflix. I am an idiot and I used the stock version so I lost the root. I believe if I was already rooted and I had installed GB .595 Deodex I would have maintained root. So here is the question. I would like to have the best of both worlds (netflix and root), which means that I need to have rooted .595. I would like for someone to tell me exactly what needs to be done. I know I will most likely have to SBF back to Froyo and upgrade from there, but I dont know which files I should be using a such.
Click to expand...
Click to collapse
Try Gingerbreak to root it and install Netflix...
Sent from my DROIDX using XDA App
GingerBreak Should Work
mmaibl2011 said:
Alright so here is the scenario, I had one of the original leaks of Gingerbread and it was rooted. I upgraded to the newest GB .595 so that I could use Netflix. I am an idiot and I used the stock version so I lost the root. I believe if I was already rooted and I had installed GB .595 Deodex I would have maintained root. So here is the question. I would like to have the best of both worlds (netflix and root), which means that I need to have rooted .595. I would like for someone to tell me exactly what needs to be done. I know I will most likely have to SBF back to Froyo and upgrade from there, but I dont know which files I should be using a such.
Click to expand...
Click to collapse
As Big stated Gingerbreak should work but if it does not and you choose to sbf you can get back to 595 real easy. I use the steps below:
SBF back to 340
Once that is done I shut it down and boot into factory recovery, do a wipe and once that finishes while in recovery I run the 588 update file which you can find update information on at the link http://www.droid-life.com/2011/04/12/how-to-manually-update-to-droidx-gingerbread-v4-5-588/
Reboot the phone, activate it and install gingerbreak and run it..http://forum.xda-developers.com/showthread.php?t=1044765
Once phone has rebooted install D2Bootstrap
Boot into recovery and install the 595 Deodexed Rooted version...Download this from the TBH app and you want the one labeled Download Full Gingerbread (2.3.3) Rooted and Deodexed (Blur Version 4.5.595)
I never get bootloops and such by doing it this method and have been using it wil all the different leaks that dropped and I can usually go from SBF to stable GB in less than 20 minutes...
I Hope the Gingerbreak works as that would be the quickets way to go for sure but this method will work if for some reason that does not break it initially while you are already on GB.
Moderator please delete
I haven't purchased the Charge yet, but I'm planning on pulling the trigger soon. Been reading the forums for a while now. I currently have a rooted OG Droid. Now after using this method, will it keep the root after doing the ED2 update?
HaloR1 said:
I haven't purchased the Charge yet, but I'm planning on pulling the trigger soon. Been reading the forums for a while now. I currently have a rooted OG Droid. Now after using this method, will it keep the root after doing the ED2 update?
Click to expand...
Click to collapse
No... ED2 will kill root. Do not update to ED2 until root is available.
There is an ODIN'd rom available that has root for ED2 but that is it.
Right on. Thanks for the speedy reply.
jt's cwm and imnuts rom are prerooted as well.
davey11 said:
jt's cwm and imnuts rom are prerooted as well.
Click to expand...
Click to collapse
My rom is rooted aswell
DroidXcon said:
My rom is rooted aswell
Click to expand...
Click to collapse
Was mentioned in post 3 is why I didn't say yours was.
About how long does it takes cause its been steaking gingers soul for a while now....thanks
brandonaspencer said:
About how long does it takes cause its been steaking gingers soul for a while now....thanks
Click to expand...
Click to collapse
Mine took about 4 minutes
Sent from my SCH-I510 using XDA Premium App
It says its complete and its rebooting but nothing happens
With this method will it make your phone go crazy advising you there is an update?
DroidXcon said:
My rom is rooted aswell
Click to expand...
Click to collapse
When you say your ROM is rooted, I'm assuming by installing your ROM (following the directions in your thread) it will root the phone and install your ROM all in one shot? Sorry for the noob question.
HaloR1 said:
When you say your ROM is rooted, I'm assuming by installing your ROM (following the directions in your thread) it will root the phone and install your ROM all in one shot? Sorry for the noob question.
Click to expand...
Click to collapse
This method is to root ED1 only. This is not a ROM. If you want a rooted rom see the first 2 or 3 posts in developement.
psalm462 said:
With this method will it make your phone go crazy advising you there is an update?
Click to expand...
Click to collapse
All charges are shipping with ED1 and verizon has pushed an update which is ED2 so your phone will ask you to update every 5 minutes whether you root it or not. If you update to ED2 then this root method will not work. If you root your phone and then update to ED2 it will break your root.
To stop the update pop up from occuring go into your build.prop file and change all references of ED1 to ED2 and it will stop asking you to update
danalo1979 said:
This method is to root ED1 only. This is not a ROM. If you want a rooted rom see the first 2 or 3 posts in developement.
Click to expand...
Click to collapse
Right, I understand that. My question was actually in reference to DroidXcon's ROM. He stated that his ROM is rooted. I guess what I'm asking is, by using ODIN to install his (DroidXcon's) file, it will root the phone and install his ROM as well? I'm coming from a rooted D1.
HaloR1 said:
Right, I understand that. My question was actually in reference to DroidXcon's ROM. He stated that his ROM is rooted. I guess what I'm asking is, by using ODIN to install his (DroidXcon's) file, it will root the phone and install his ROM as well? I'm coming from a rooted D1.
Click to expand...
Click to collapse
It will install his ROM, which is rooted. It will not "root" the phone as such, but you will have a rooted phone with ability to run Titanium Backup, etc., when done.
Samsung Androids (at least the Fascinate and Charge) are different from most others in that you can flash almost anything with ODIN, regardless of the condition of the phone (rooted or not, currently running or not).
luigi1111 said:
It will install his ROM, which is rooted. It will not "root" the phone as such, but you will have a rooted phone with ability to run Titanium Backup, etc., when done.
Samsung Androids (at least the Fascinate and Charge) are different from most others in that you can flash almost anything with ODIN, regardless of the condition of the phone (rooted or not, currently running or not).
Click to expand...
Click to collapse
Excellent. Thanks for clearing that up.
danalo1979 said:
Thanks to DroidXcon and others for creating this one click method. This is by far the easiest method to root your charge on ED1. See attachment
Don't forget to thank me for making rooting easy for you to find and don't forget to thank and donate to DroidXcon for creating it.
The Root method is called GingerSnap and its a One click.
1. Make sure your phone is in debugging mode
2. Make sure you have the charge drivers installed on your PC
3. Download the gingersnap .zip file to your desktop
4. Double click on the gingersnap.exe file and press GO
That's it!!!! Your phone will reboot and you will be fully rooted. (permanent root)
Click to expand...
Click to collapse
A bit of newb to the Droid. Will this work on my Charge? Here are the specs:
Firmware : 2.2.1
Baseband: i510.06 V.ED1
SCH-I510.ED1
Kernel Version: 2.6.32.9
Build Number: SCH-I510.ED2
Just getting confused between the ED1 and ED2... Don't want a $500 paperweight.
Ya Know?
Thanks!
Ry.kaz.ryder said:
A bit of newb to the Droid. Will this work on my Charge? Here are the specs:
Firmware : 2.2.1
Baseband: i510.06 V.ED1
SCH-I510.ED1
Kernel Version: 2.6.32.9
Build Number: SCH-I510.ED2
Just getting confused between the ED1 and ED2... Don't want a $500 paperweight.
Ya Know?
Thanks!
Click to expand...
Click to collapse
yes it will work
here are my specs as well, and it's been stealing the ginger's soul for anout 15 mins now...any suggestions?
Firmware : 2.2.1
Baseband: i510.06 V.ED1
SCH-I510.ED1
Kernel Version: 2.6.32.9
Build Number: SCH-I510.ED2
OEM 2.3.6 would like to root keeping everything as close as OEM as possible (don't like the custom ROMs).
Please advise.
Is a Kernel swap possible? Change Kernel to Gain Root then reflash back to Stock kernel?
toshik1 said:
OEM 2.3.6 would like to root keeping everything as close as OEM as possible (don't like the custom ROMs).
Please advise.
Click to expand...
Click to collapse
try vagabond 3.5. It's almost completely stock but rooted.
If you follow directions, you can also flash the stock kernel and retain root.
There is no simple conventional method of root like SOC on the Infuse 2.3.6
---------- Post added at 04:38 PM ---------- Previous post was at 04:19 PM ----------
If you wanted to retain the odex file system,
you will need to flash a gb insecure kernel.
install superuser and busybox
flash back the stock kernel and fix the vold file.
it will be fun to try
Anyone here ever heard of or used OTA Rootkeeper? I have no clue if it will work on a Kies install method (never actually flashed through Kies) but, with my Transformer Prime, we used said app to retain root privileges after an OTA update from Asus. Worked everytime for me, even when updating to ICS from Honeycomb, so maybe Froyo to GB will be similar.
I don't have my Infuse with me (left it at home) or I would attempt it myself. It would be great if someone with prior kernel flashing knowledge could try it; if it doesn't work you can just flash a kernel to get your root back.
Additionally when we first got GB last summer I remember seeing a how-to from a dev explaining how we would achieve root on GB once AT&T released the update (since SOC only works with Froyo for us)...
I have used the ota rootkeeper on my atrix 2 when it got updated. Its a pain in the ass to use. The infuse does not need it plus i don't think it will work. Rooting the infuse is easy if you use the appropriate kernels.
Sent from my MB865 using xda premium
tmease1 said:
I have used the ota rootkeeper on my atrix 2 when it got updated. Its a pain in the ass to use. The infuse does not need it plus i don't think it will work. Rooting the infuse is easy if you use the appropriate kernels.
Sent from my MB865 using xda premium
Click to expand...
Click to collapse
I actually thought it was pretty friggin simple. Open the app/Protect Root/Temp. Unroot/Install OTA Update/DL Rootkeeper/Open/Restore Root. Seems pretty painless to me
And the OP wants as close to stock as possible, sure to me and you flashing an unsecure kernel is easy to gain root, but most ppl would rather have a one click executable through a PC w/ the right drivers for phone.
Soo I was thinking, the Kies Update shouldn't erase everything (apps, sdcard, etc.), Rootkeeper stores su in a place that isn't wiped during an OTA. I could be wrong, the app might not even be compatible, but I don't have my Infuse to try..
The process, if it works, requires very little knowledge to do and gives you root w/o messing w/ kernels:
1. Start from the latest Froyo stock build/ use SuperOneClick w/ drivers to root.
2. DL Rootkeeper/open/protect root/temp. unroot.
3. Run Kies and install the update
4. On your fresh GB build DL Rootkeeper from market, open/restore root.
5. Open Rootchecker and see if it worked. Done.
If it doesn't work, flash a kernel. (hell, what have we lost anyways, 30 mins?)
This weekend I'm driving home for the weekend, I can try it then; till then, any takers?
Again, if you have to know-how to flash a kernel, do it, I'm just brain storming alternatives for those who don't or don't want to.
I gave my personal Opinion about the ota rootkeeper. I just don't like it. Its easy yes but I personally would rather do it manually with a computer. Plus it will not work with kies. Kies is different than a ota update. The leak lb3 is the exact same as official. He can use kies to update, flash a rooted gingerbread kernel then flash the stock lb3 kernel. He will then be rooted with stock kernel.
Sent from my MB865 using xda premium
tmease1 said:
He can use kies to update, flash a rooted gingerbread kernel then flash the stock lb3 kernel. He will then be rooted with stock kernel.
Sent from my MB865 using xda premium
Click to expand...
Click to collapse
in between, the kernels, there is the su binaries and busybox thingie.
qkster said:
in between, the kernels, there is the su binaries and busybox thingie.
Click to expand...
Click to collapse
Im sorry i forgot to add that in.
Sent from my MB865 using xda premium
tmease1 said:
Im sorry i forgot to add that in.
Sent from my MB865 using xda premium
Click to expand...
Click to collapse
10 chars...
tmease1 said:
I gave my personal Opinion about the ota rootkeeper. I just don't like it. Its easy yes but I personally would rather do it manually with a computer. Plus it will not work with kies. Kies is different than a ota update. The leak lb3 is the exact same as official. He can use kies to update, flash a rooted gingerbread kernel then flash the stock lb3 kernel. He will then be rooted with stock kernel.
Sent from my MB865 using xda premium
Click to expand...
Click to collapse
Your right, its your opinion, and Rootkeeper most likely will not play well w/ Kies. Trust me, I would much rather flash a kernel for su, it really is a lot easier than some noobs might think.
As for Kies, I clearly stated that I haven't use Kies for an update, that it might not work and that I could be wrong I'm fully aware Kies is different than OTA; I'm pretty sure it wipes where the su binaries are protected, I only offered a suggestion for the OP, again b/c jumping into flashing things just for root sounds scary. The whole point was to voice possible alternatives, etc, you know, cuz that's what we do here at xda...
@OP, if you want to gain root through a kernel, I would suggest first looking into THESE links as you might have to use some methods listed there.
Also Qk's Back to stock guide HERE can get you to stock B3 w/ custom recovery (rather easy), and his Vagabond Rom has great instructions concerning his rom and stock kernels if need be HERE. Make sure to thank qkster for these. (I guess he has spent a lot of time with the B3 leak. )
We are kind of late to the GB party, it seems things aren't as straight forward as they were in Froyo or GB <= 2.3.5. The links should get you pointed in the right direction to get your phone stock + root. Good luck and READ up!
Root needed
Anyone came up with the rooted version of the following?
http://www.samsung.com/us/support/SupportOwnersFAQPopup.do?faq_id=FAQ00045587&fm_seq=46249
The latest official release from samsung (UCLB3)? My post right ABOVE yours is me explaining how to root the newest build, links included! Read! You would have quickly found that flashing an insecure kernel is your best bet.
Additionally, I tried the method I was discussing in this thread (ota rootkeeper) and it didn't work. (@tmease, you opinion is now fact )
This is a method to root Atrix 2 running on Android GB(2.3.6) / ICS(4.0.4).
EDIT: Last updated on 26th July 2012
WHAT WORKS: Everything including the setting inside superuser which was not working in superuser 3.1
If you use this MOD, then please click on thanks button below.
I have updated this method to latest version of superuser 3.1.3 and su binary 3.1.1 for better compatibility with various Apps.
By following the below instructions you will be rooted in no time. If you have any questions feel free to ask.
Features added in superuser 3.1.3:
1.Temp unroot
2. Ota survival
3. Outdated binary Notification
Method:
1. Enable "USB debugging" in your phone settings
2. Download the attachment Named "Motofail Root (superuser 3.1.3, su binary 3.1.1).zip" to root Android GB(2.3.6)
or Attachment named "ICS_root(superuser 3.1.3 and su binary 3.1.1) .zip" to root Android ICS (4.0.4).
3. Uninstall your old Motorola drivers from PC and install these new drivers.
4. Connect your phone with original USB cable that came with your phone.
5. To root Android GB(2.3.6) click on "Click-To-Root.bat" in the attachment folder or
To root Android ICS(4.0.4) click on "Root.bat" in the attachment folder
6.Your phone will reboot 2-3 times don't remove the USB cable during this process
NOTE: If you are unable to Root even after following the above MOD then perform a Factory restore after OTA update and retry.
Can i root the ics with this?
And my phone is rooted,but can i re-root it?
atrix2 said:
Can i root the ics with this?
And my phone is rooted,but can i re-root it?
Click to expand...
Click to collapse
YES
Thanks for the new update.......
Sent from my GT-S6102 using Tapatalk 2
Please be aware that other A2 users have had issues with Superuser versions higher than 3.0.3.
Sent from my SAMSUNG-SGH-I747 using xda premium
jimbridgman said:
Please be aware that other A2 users have had issues with Superuser versions higher than 3.0.3.
Sent from my SAMSUNG-SGH-I747 using xda premium
Click to expand...
Click to collapse
I haven't been having problems, but I always have been using the older motofail exploit then updating the binary from within the app.
lkrasner said:
I haven't been having problems, but I always have been using the older motofail exploit then updating the binary from within the app.
Click to expand...
Click to collapse
I had the issue the other day, on stock 2.3.6, I also saw that alterdlikeness had a similar issue as well. It was updating past the 3.03 on both su and Superuser.
I had issues on my A2 with 3.1 only, and it would just FC and not work. I had to remove and basically re-root, and leave it at 3.0.1.
jimbridgman said:
I had the issue the other day, on stock 2.3.6, I also saw that alterdlikeness had a similar issue as well. It was updating past the 3.03 on both su and Superuser.
I had issues on my A2 with 3.1 only, and it would just FC and not work. I had to remove and basically re-root, and leave it at 3.0.1.
Click to expand...
Click to collapse
hmm. good to know in case it ever happens to me. I guess I will know I am not alone.
I don't know about other variants but it is working on ATT ROM and I have also assisted the same method to one user in India on androidcentral who was on MEART ROM and it even worked for him.
prasannapmv said:
I don't know about other variants but it is working on ATT ROM and I have also assisted the same method to one user in India on androidcentral who was on MEART ROM and it even worked for him.
Click to expand...
Click to collapse
You missed the point I was trying to make to those wanting to update thier binaries for su and superuser.... not new root exploits.
I just want everyone to know there are issues with 3.1... however today an update to 3.1.2 today has been proven to work for those having the issues that both alteredlikness and I have seen with FCs.
Sent from my MB865 using xda premium
On Stock 2.3.6 rooted. The new updates to the Superuser app allow you to update the binary and use the settings now.
Updating thread for superuser 3.1.2 now..
This method works as stated today I was trying to update my su binary but update was not getting successful so I unrooted and rooted back using this method now everything is updated and running smoothly.
About to root my girlfriends phone to eventually install Lithium.
Coming from a AT&T Galaxy S2 so things are a bit different here.
Should I use this method or Jimmy's from this thread? http://forum.xda-developers.com/showthread.php?t=1327741
After that what steps do I need to take to get CWM installed so I can backup and install a new ROM?
Thanks thanks!
seanpr123 said:
About to root my girlfriends phone to eventually install Lithium.
Coming from a AT&T Galaxy S2 so things are a bit different here.
Should I use this method or Jimmy's from this thread? http://forum.xda-developers.com/showthread.php?t=1327741
After that what steps do I need to take to get CWM installed so I can backup and install a new ROM?
Thanks thanks!
Click to expand...
Click to collapse
I think they are the same, except this one has a more updated version of superuser - I think (someone correct me if I'm wrong).
I personally have always used the one in Jimmy's thread and just update the superuser app and binary (and, thanks for reminding me about that post - I never thanked him until today - and due credit to p3droid & JRW 28 of course).
As for CWM recovery, just install the A2 Bootstrap app after being rooted. Use the bootstrap app - top button, OK, bottom button to boot into recovery.
Good luck to you and your girl!
alteredlikeness said:
I think they are the same, except this one has a more updated version of superuser - I think (someone correct me if I'm wrong).
I personally have always used the one in Jimmy's thread and just update the superuser app and binary (and, thanks for reminding me about that post - I never thanked him until today - and due credit to p3droid & JRW 28 of course).
As for CWM recovery, just install the A2 Bootstrap app after being rooted. Use the bootstrap app - top button, OK, bottom button to boot into recovery.
Good luck to you and your girl!
Click to expand...
Click to collapse
Boom, was one setup ahead of you and just finished all that. Currently backing up in CWM and waiting for a painfully slow download of Lithium and we should be jammin. Can't believe how easy it all was actually.
So I assume since this CWM is loaded from an app there's no way to boot into recovery should a bootloop or rom failure happen? Is that something people worry about?
Thanks for your response bud.
seanpr123 said:
Boom, was one setup ahead of you and just finished all that. Currently backing up in CWM and waiting for a painfully slow download of Lithium and we should be jammin. Can't believe how easy it all was actually.
So I assume since this CWM is loaded from an app there's no way to boot into recovery should a bootloop or rom failure happen? Is that something people worry about?
Thanks for your response bud.
Click to expand...
Click to collapse
The cwm on boot feature may already be included in Lithium (edit: yes, it it included - just checked)... if not, you can set that up rather painlessly. And, yes, some of us do worry about that very much so..
Great thanks! worked perfectly for me on the ICS leak (non AT&T A2)
So I am on Atrix Xperia 4 rom and i was wondering if there is any way to re-root my phone to ICS and then flash the ics rom? I really havent seen anyone ask this yet but sorry if I am repeating anyones question.
matt_12tall said:
So I am on Atrix Xperia 4 rom and i was wondering if there is any way to re-root my phone to ICS and then flash the ics rom? I really havent seen anyone ask this yet but sorry if I am repeating anyones question.
Click to expand...
Click to collapse
Are you on the ICS leak already? Are you on AT&T? If you are on the ICS leak and on AT&T there is a way to root it in the leak thread in the General section. I put the files back up today.
If not, I really am not sure, one of the guys on the other leaks might be able to help there.
I was wondering about rerooting after the OTA update. I found one thread for rooting but that was for leek 1. Just wanting to verify before I do some stupid.
Sent from my MB865 (ATT ATRIX 2) running ICS 4.0.4 via the xda-developers app
ICS_root from http://forum.xda-developers.com/showthread.php?t=1742879 should work.
OTA Rootkeeper seems to have worked for me.
I had Superuser do root protection but it only partially worked. Root could not add new programs. I rerooted using Leak # 1 method. Worked fine. Only issue is that Superuser force closes if you try to save the program permissions to sd card. Hopefully a future update to Superuser will rectify this issue.
sparhawktn said:
I was wondering about rerooting after the OTA update. I found one thread for rooting but that was for leek 1. Just wanting to verify before I do some stupid.
Sent from my MB865 (ATT ATRIX 2) running ICS 4.0.4 via the xda-developers app
Click to expand...
Click to collapse
See my signature for my config & despite the same I rooted using http://forum.xda-developers.com/showthread.php?t=1779968, I cant say about re-rooting though.
kousik said:
ICS_root from http://forum.xda-developers.com/showthread.php?t=1742879 should work.
Click to expand...
Click to collapse
Confirmed.... At least for me.
I was stock GB 2.3.6 rooted. Updated to ICS via OTA and lost root. Used that link above to regain root on ICS.
I was rooted on 2.3.6 and after the ICS OTA I lost root but still have Superuser installed. Is it ok to re-root over existing Superuser? Also what should be the USB connection type? Mass storage? Media Device (MTP)? Camera? Charge Only does not exist on ICS anymore.
Thanks
Jude
Waiting4MyAndroid said:
I was rooted on 2.3.6 and after the ICS OTA I lost root but still have Superuser installed. Is it ok to re-root over existing Superuser? Also what should be the USB connection type? Mass storage? Media Device (MTP)? Camera? Charge Only does not exist on ICS anymore.
Thanks
Jude
Click to expand...
Click to collapse
Reference to 2nd part of your question, I used MTP mode while rooting as indeed charge only mode does not exist. Hope this helps.
kirkgbr said:
Confirmed.... At least for me.
I was stock GB 2.3.6 rooted. Updated to ICS via OTA and lost root. Used that link above to regain root on ICS.
Click to expand...
Click to collapse
Just successfully re-rooted OTA ICS over existing Superuser. USB debugging on and connected as Media Device.