Hello list,
I have been trying to root my Nexus S with the 2.3.3 update but I've been unsuccessful. I have tried "Allgamer's" GRH78 and a couple of others on youtube but I think the problem is my laptop (windows 7 32-bit) wont recognize the phone. Is there something I'm missing? Has anyone rooted their 2.3.3 phone, and if so can you send a link or PM me so I can figure this out? I eventually want to flash the Cyanogenmod 7 so any help at all would be greatly appreciated.
When I had my HD2 I installed HSPL and flashed all types of ROM's without issue. My Nexus S is acting like my ex......
Thanks,
Rich
Madmax0609 said:
Hello list,
I have been trying to root my Nexus S with the 2.3.3 update but I've been unsuccessful. I have tried "Allgamer's" GRH78 and a couple of others on youtube but I think the problem is my laptop (windows 7 32-bit) wont recognize the phone. Is there something I'm missing? Has anyone rooted their 2.3.3 phone, and if so can you send a link or PM me so I can figure this out? I eventually want to flash the Cyanogenmod 7 so any help at all would be greatly appreciated.
When I had my HD2 I installed HSPL and flashed all types of ROM's without issue. My Nexus S is acting like my ex......
Thanks,
Rich
Click to expand...
Click to collapse
try this http://forum.xda-developers.com/showthread.php?t=875875
Will that work with 2.3.3? And what the hell am I doing wrong that I cant get my laptop to recognize my phone???
Madmax0609 said:
Will that work with 2.3.3? And what the hell am I doing wrong that I cant get my laptop to recognize my phone???
Click to expand...
Click to collapse
Well, you can try to install this driver: http://mazodude.comze.com/files/drivers.rar
That link takes me to a blank page....??? Have you rooted your Nexus and was it at 2.3.3 when you started?
Thanks, and sorry for all the questions.....I'm just trying to get this resolved.
Madmax0609 said:
That link takes me to a blank page....??? Have you rooted your Nexus and was it at 2.3.3 when you started?
Thanks, and sorry for all the questions.....I'm just trying to get this resolved.
Click to expand...
Click to collapse
Did you install the Android SDK? If so, I apologize as I'm not familiar with the shortcut commands for windows but you should try this:
Code:
*File path to your android sdk/tools folder*\fastboot devices
If you get a result like
Code:
################# fastboot
then your phone is being recognized, if not other troubleshooting stepsmight have to be taken.
Havent tried that yet. I will give it a shot.
Thanks!
was having the same issue with fastboot, use these drivers from pda.net
http://www.junefabrics.com/android/download.php
Having the same problem. I've tried PDAnet and am currently updating (again) SDK, but I can't get the fastboot or adb to recognize the device, no matter how hard I try. For what it's worth, my bootloader was unlocked when I upgraded to 2.3.3 (via Clockword Mod), and the unlock status seems to have been preserved. It still says "unlocked," and boots with the open padlock.
Sorry for the double post, but I posted as I was working on it. What worked for me: I had a 2.3.3 stock image booted from Clockwork. I didn't have root permissions with the stock.
The new stock (is it technically a ROM, or is a ROM just Cyanogen, Bionix, etc., like awesome developers create?) preserved the unlocked bootloader (which I've not re-locked, because I never cared about the padlock boot), but not the root. So I was left with a stock 2.3.3 with an unlocked bootloader.
I tried everything to get my phone recognized via USB under the SDK/adb, but couldn't. I adbed and fastbooted devices, uninstalled and reinstalled PDAnet, even deleted and then redownloaded and reinstalled java, SDK, *and* drivers. To no avail.
The first time I rooted, though, I used the one-click method in the MoDaCo forums, by . . . Paul(?). I think that's his name. It's a simple zip file. So I unzipped to my desktop. Which gave me a folder with the GRI40 Nexus S superboot. I disconnected my phone, shut it off, then held the volume up and power keys until it booted into the fastboot bit. Once it was in fastboot (with the green Android and the orange text up top and the blue text options along the side), I reconnected the USB, then just double-clicked the .bat file in the superboot folder.
That gave me root. I verified via rootchecker, and the moment I confirmed root, I went to Clockwork, reflashed Clockwork Mod Recovery, and did a complete back-up. That's where I am now. Not sure where I'm going from here, but I have 2.3.3 GRI40 root with baseband i9020xxb1, and that's how I did it.
willentrekin said:
Sorry for the double post, but I posted as I was working on it. What worked for me: I had a 2.3.3 stock image booted from Clockwork. I didn't have root permissions with the stock.
The new stock (is it technically a ROM, or is a ROM just Cyanogen, Bionix, etc., like awesome developers create?) preserved the unlocked bootloader (which I've not re-locked, because I never cared about the padlock boot), but not the root. So I was left with a stock 2.3.3 with an unlocked bootloader.
I tried everything to get my phone recognized via USB under the SDK/adb, but couldn't. I adbed and fastbooted devices, uninstalled and reinstalled PDAnet, even deleted and then redownloaded and reinstalled java, SDK, *and* drivers. To no avail.
The first time I rooted, though, I used the one-click method in the MoDaCo forums, by . . . Paul(?). I think that's his name. It's a simple zip file. So I unzipped to my desktop. Which gave me a folder with the GRI40 Nexus S superboot. I disconnected my phone, shut it off, then held the volume up and power keys until it booted into the fastboot bit. Once it was in fastboot (with the green Android and the orange text up top and the blue text options along the side), I reconnected the USB, then just double-clicked the .bat file in the superboot folder.
That gave me root. I verified via rootchecker, and the moment I confirmed root, I went to Clockwork, reflashed Clockwork Mod Recovery, and did a complete back-up. That's where I am now. Not sure where I'm going from here, but I have 2.3.3 GRI40 root with baseband i9020xxb1, and that's how I did it.
Click to expand...
Click to collapse
Are you on a PC or a mac?
PC
Loaded up Cyanogen. Seems okay. Tried adding the Honity kernel, but that seems to bugger everything up.
willentrekin said:
PC
Loaded up Cyanogen. Seems okay. Tried adding the Honity kernel, but that seems to bugger everything up.
Click to expand...
Click to collapse
Cyanogen is nice as it adds some features but if you've been living without them you might never notice having them lol. More people need to buy macs <.< I can help anyone get root on a mac >.>
I'm noticing that. It seems like kernels are what introduce problems for me; I've run Bionix and Cyanogen without issue, but as soon as I load up a kernel, I start getting force closes in any app that requires superuser permissions. I've discovered that managing the apps to clear their data/caches can help, but I'd like to find a more stable set up.
willentrekin said:
I'm noticing that. It seems like kernels are what introduce problems for me; I've run Bionix and Cyanogen without issue, but as soon as I load up a kernel, I start getting force closes in any app that requires superuser permissions. I've discovered that managing the apps to clear their data/caches can help, but I'd like to find a more stable set up.
Click to expand...
Click to collapse
When you flash the kernel run fix permissions before you reboot. For me cfs kernels.
Related
I've asked this in many threads, but no answer.
I've been able to obtain root with clockwork recovery on my hero using my mac but now I have an epic4g and I've been able to gain root access on the epic using my mac, but I'm not able to install clockworkmod on it. I've tried rom manager, and it says that it's installed, but I'm unable to boot into clockwork recovery. I've tried via rom manager and via the vol down/camera/power keys and it always loads into the default recovery.
Any ideas on how to get clockworkmod on my epic using a mac (I have no access to windows and don't want to install windows on my mac just to install clockworkmod on my phone as once it's on there, I won't need it again.)
Any help with this would be greatly appreciated.
I'm looking forward to flashing some of the new roms on my epic.
Thanks!
not sure on mac but i have a linux script, not familar with mac os, i might be able to whip up a short little one tomorrow tho...
Second the request
I would also appreciate it. Although I have parallels installed I still run into many headaches with adb, would be very appreciative!
Any help would be appreciated. I've tried everything that I could find and got the phone rooted via mac, and I've tried to duplicate the commands in run.bat that I've found for installing clockworkmod, but it doesn't work. Thanks!
Would anyone be willing to tell me how they rooted on their mac?
Thanks in advance,
Chris
Someone ported a oneclick root for the mac, but it doesn't include clockworkmod.
ok guys here you go, i updated the mac osx script by baggage to include clockwork let me know how it goes
whoops forgot to add the file
http://dl.dropbox.com/u/10162842/OneclickOSX.zip
I finally figured out how to get to clockworkmod! It took reading dozens and dozens of threads all the way through.
I can only access via the down vol, camera, power and then trigger update from the samsung recovery and then I have access to clockworkmod.
I'm finally glad that worked!
Still a bit cumbersome as I haven't found a way to get into clockworkmod directly either with rom manager or with button method. It's always a two-step process.
sounds like you flashed the patched one then used teh update, use teh one click i made and it will install 2.5.1.0 so no more needing to do that update.zip business
I have the 2.5.1 version. But I still have to do the update.zip thing.
I saw yours in my days of readings, but in the sake of time, can you show me the thread. I rooted using the one-click mac root but couldn't get clockworkmod to work, so I found another thread, downloaded the windows version, looked at run.bat in a text viewer and did all the commands manually. Most worked, but some did not, but I guess they didn't need to as it eventually worked.
just posted it above, mine original was for linux this one is new for mac os x
or you can click the link in my sig
After receiving my second Hero I had noticed something weird about its software version... From what I remembered, it started with 2.27 on the last one I had and raised my curiosity/concern. I had heard about a root patch that was being sent out OTA by Sprint and after a little digging found the extremes that everyone was going through to achieve a successful root. The most common was to flash back .6 then to .5 which doesn't have the patch. I spent over an hour trying to find ANY copy of the 2.31.651.6 update and could not find anything. Then there where methods using the SDK which I'm sure could work, however the bootloader was a b!tch to access. I thought it would be entertaining to see If Sprint's new .7 root patched could be broken simply by the android market and third party developers; no use of Odin, unrevoked, HTC sync, no messing with debugging, not custom 2.31.651.7 (careful) and absolutely no flash backs! So here it is... enjoy.
All you will need ready is:
1).zip file of whichever OS you plan to flash. (I prefer the cm build's).
2)Rom Manager from the market (work's well with clockwork and cm).
3)Heroroot101.apk (Don't remember if it's on the market or third party).
4)NANDROID!!!!!!
All you do is run heroroot010 and push the root me button.
Reboot your phone and let it fully boot back up (give it a minute or two).
Turn it off and boot into recovery by holding down volume button and power.
I'll be damned there is a recovery image now by darchstar.
At this time there is no need to wipe just choose and flash rootme.zip
When you reboot you will see that sprint know's you're rooted already and wants to update you... This is fine.
Open Rom Manager, flash Clockwork (replacing darchstar) reboot into recovery mode and flash your new OS (DON'T FORGET TO WIPE).
I like your detailed method, but SuperOneClick was really easy too.
Install HTC Sync (v2 for Hero)
Enable USB debugging
Open SOC
Click Root
Plug in phone when prompted
Wait a bit.... then done.
There really is alot of outdated information on these forums. All versions of the stock ROMs can be rooted one way or another.
Above is two possible solutions
I agree with porkrinds but y would you replace Darchstar Recovery its the best IMO Thanks Darchstar
Root-Hack-Mod-Always™
Porkrinds said:
There really is alot of outdated information on these forums. All versions of the stock ROMs can be rooted one way or another.
Above is two possible solutions
Click to expand...
Click to collapse
Forum update, prune, re-sticky time?
I used one click method & there's no recovery image.
Great Way to Root Hero with 2.31
Used this without a hitch, has recovery & all took about 2 minutes...
http://forum.xda-developers.com/forumdisplay.php?f=643
cybertimber2007 said:
I like your detailed method, but SuperOneClick was really easy too.
Install HTC Sync (v2 for Hero)
Enable USB debugging
Open SOC
Click Root
Plug in phone when prompted
Wait a bit.... then done.
Click to expand...
Click to collapse
Hey man I just used your little posts instructions to root my Wife's hero (my evo is already rooted)
I can't believe how easy that was thanks so much everything appears to be working I have superuser authority and am going to try flashing a new rom momentarily
I downloaded and installed the Incredible S Beta rom that is listed somewhere on this site for the Incredible. My issue is I want to revert to another ROM, HOWEVER, now my Superuser keeps force closing and will not allow ROM Manger to flash. I try to reboot in HBoot and ONLY get the start-up screen when doing Vol- and Power. Any suggestions on how to get into Hboot or another way to flash a different ROM when SuperUser will NOT allow permissions or Rom Manger wont reboot into Recovery (because superuser forecloses and wont let me flash Rom Manager
BTW-The Incredible S Rom works great...just NO pic/video (As it states in the description.)
Editing to take away some of the clutter (my clutter)
I am not sure what happened. As stated above once the ROM (which is great!) was installed, Rom Manager was no longer granted superuser access (was trying to reboot into recovery via Rom Manager). It wiped the Recovery Version from the phone and would not let me flash a new recovery. Everything else seemed to work fine (superuser permissions, ie. SetPC, etc.)
I tried plugging the phone in and reflashing Unrevoked directly to the phone. Unrevoked stated the root access was denied and asked if I had a "newer firmware".
I also tried uninstalling superuser (to only reinstall and see if it fixed the issue), however, Superuser was included in the ROM and would not let me uninstall.
The only way I was able to get back into Recovery was to re-run Unrevoked Flash and UNPLUG the phone when Unrevoked managed (somehow) to get the phone into bootloader. From there Clockwork ran fine.
Installed a different ROM and all is good.
The only thing I can think of is: In some post regarding the Incredible S being not branded to a certain carrier. When the ROM was installed, it showed "EVDO" in the notification bar (which leads me to believe it is for Sprint), I am not sure how THAT would affect anything being on a Verizon phone...again..only thing I can think of.
Just reboot the phone directly into recovery.
evilkorn said:
Just reboot the phone directly into recovery.
Click to expand...
Click to collapse
It wont let me. I dont think...I tried the Vol-+power...nothing..just reboots. Tried booting into recovery via Rom Manager, but since superuser no longer is granting persmission it wont even do that...is there another way to flash a different ROM?
I just tried reflashing Unrevoked directly to it...it failed to access boot, something about the firmware being too new...???
I dont know anything about your device but maybe your root is broken? Re root and re install superuser goodluck.
Sent from my X10a using XDA App
shahkam said:
I dont know anything about your device but maybe your root is broken? Re root and re install superuser goodluck.
Sent from my X10a using XDA App
Click to expand...
Click to collapse
Oh, HTC Incredible.
I went into Rom Manager (and against ALL I have read) am trying to instal and reboot using Rom Manager...instead of going into recovery mode...phone is just sitting here "thinking" right now...nothing YET about being denied root access...fingers crossed...
OK, not sure this was SMART...Hooked phone back up to PC, ran Unrevoked flash kit again...unplugged phone once it came up in recovery...have access NOW to CLockwork...wiped data..installing different ROM as I type...hopefully this will work..
YAY...close call...sorry to waste everyones time..lol. So..If your installing the INcredible S Rom onto your incrediable..I have learned two things...1.) Unrevoked failed to push recovery due to the firmware...2.) you may lose superuser ability....
You would get more help if your thread title would actually be helpful.
Include your phone model, the rom you tried, and what happened (SuperUses FCs[forcecloses]).
Caps, lots of exclamation marks and a title like ZOMFG I NEED HELP, usually deters skilled people from threads like this.
Dark3n said:
You would get more help if your thread title would actually be helpful.
Include your phone model, the rom you tried, and what happened (SuperUses FCs[forcecloses]).
Caps, lots of exclamation marks and a title like ZOMFG I NEED HELP, usually deters skilled people from threads like this.
Click to expand...
Click to collapse
Good point...just paniked. Someone can close this or change title.
You can do it yourself through the edit button. Make it accurate so people who have the same problem and search for it will find your thread and your solution.
Ok so im a noob to this android thing, ive successfully rooted my phone twice with super one click and it worked perfect but as soon as i flashed my phone with "odin Ec10 with root+cw" it all went crazy. i could not get root access from any of my apps. So i used odin to flash it back to 2.1 and rooted it with super one click, bt when it sent the SU test i got nothing, i downloaded root checker and tested to see if i had it rooted but it gave me this:
Root acess is not properly configured or was not granted
SU binary not found in the system declared path.
Now i flashed 2.2 with odin and its still giving me the same thing. super one click is not doing its job and im stuck with an unrooted phone. i also tried restoring to factory settings and wiping cache but still nothing. maybe something messed up in the system folder or something idk, if you need more info ill answer anything, ill be active on the forum for a while.
Check and make sure USB Debugging is enabled in the phone's settings under Applications -> Development.
i tried that, still didnt work.
This may sound a bit stupid but have you tried rebooting the phone? I've flashed ROMs before where I wouldn't get SU access on the initial boot and had to reboot it to get it to start doing its thing.
ok i got it!!!! I guess SUper One Click only roots my phone when i start Super One click and wait for it to way "waiting for device" i turn on my phone, as the Samsung logo pops up S.O.C. starts rooting it Correctly. Finally after my 12th flash (lol) it works. thanks anyways guys. Hopefully no one else has this problem.
Strange, but hey, whatever works. Glad you got it fixed.
Evo 3D on Android 4.0.3, root fail
I had updated my HTC Evo 3D OTA from 2.3.3 to Android 4.0.3 software version 3.28.707.1 then unlocked it using HTC Method. Unlock success than I flashed recovery with CWM Shooter. Flash success but when I load recovery, the phone just boot up normally. CWM screen not loaded to load custom ROM.
When I open ROM Manager it says:
You must root your phone for ROM Manager to function. Superuser was not found at "/system/bin/su" or "/system/xbin/su". Use Google Search on your computer to find instruction to root your phone.
When I open SUperuser apps it says:
su binary not found
I already tried USB debugging mode, and flash with other .img with other version of CWM. Still not working.
I don't know why ADB is not working while normally booted! It works when in recovery, please help me. I am using Senseless version 3.7.1
cwest31 said:
I don't know why ADB is not working while normally booted! It works when in recovery, please help me. I am using Senseless version 3.7.1
Click to expand...
Click to collapse
Read this entire guide.
blackknightavalon said:
Read this entire guide.
Click to expand...
Click to collapse
koooooooooooool
reinstalled sdk following instructions carefully! its not an sdk problem
cwest31 said:
reinstalled sdk following instructions carefully! its not an sdk problem
Click to expand...
Click to collapse
ADB is part of the SDK.
Sent from a message in a bottle.
cwest31 said:
I don't know why ADB is not working while normally booted! It works when in recovery, please help me. I am using Senseless version 3.7.1
Click to expand...
Click to collapse
There is literally no information in this posting that someone can use to help you.
Blackknightavalon's direction to the SDK webpage is about as helpful of a reply as you can expect to solicit with the information you have provided.
This is like going to a car forum, and saying " I have a blue camaro. It won't start. I tried turning the key. Help please"
What commands are you trying to run through adb?
What errors are you getting, if any?
What do you see when you type "adb devices"
What operating system are you running on the computer you are trying to connect from?
Have you turned on "usb debugging" in the options menu on the phone?
There are a whole lot of things that can be your problem, and we'd love to help, but we can't help you if you don't tell us what's wrong.
Doubtless someone else will get back to you before I get a chance to, since my time is very limited these days online, but posting some more information about your problem will elicit a response that may actually help you.
Best of luck!
Blue6IX said:
There is literally no information in this posting that someone can use to help you.
Blackknightavalon's direction to the SDK webpage is about as helpful of a reply as you can expect to solicit with the information you have provided.
This is like going to a car forum, and saying " I have a blue camaro. It won't start. I tried turning the key. Help please"
What commands are you trying to run through adb?
What errors are you getting, if any?
What do you see when you type "adb devices"
What operating system are you running on the computer you are trying to connect from?
Have you turned on "usb debugging" in the options menu on the phone?
There are a whole lot of things that can be your problem, and we'd love to help, but we can't help you if you don't tell us what's wrong.
Doubtless someone else will get back to you before I get a chance to, since my time is very limited these days online, but posting some more information about your problem will elicit a response that may actually help you.
Best of luck!
Click to expand...
Click to collapse
Make sure you have current adb drivers for your phone. It will show android composite in device manager. Fastboot will show fastboot device. Seeing a yellow question mark is bad.
Make sure your pathing is set up right.
Typing "adb devices" and if you see your device. If so you're ready to roll.
I usually get fastboot errors like this when I don't have drivers installed right.
sent from my Agent Orange MT4G Slide using xda premium
Droidmoder said:
Make sure you have current adb drivers for your phone. It will show android composite in device manager. Fastboot will show fastboot device. Seeing a yellow question mark is bad.
Make sure your pathing is set up right.
Typing "adb devices" and if you see your device. If so you're ready to roll.
I usually get fastboot errors like this when I don't have drivers installed right.
Adb is part of the adk. It's to help debug and install things via a directlink to the computer. Its found in platform tools and is considered a dev tool.
sent from my Agent Orange MT4G Slide using xda premium
Click to expand...
Click to collapse
sent from my Agent Orange MT4G Slide using xda premium
I get Error Message with ADB
Hey guys, so I perm rooted with S-OFF my mytouch 4g slide, with theunlockr.com youtube video and guide using revolutionary. then I attempted to install a ROM with ROM MANAGER, and it got stuck on the splash/loading screen. After some searching I found out that this meant that I could have potentially BRICKED the phone, so I followed theunlockr.com's guide to UNROOTING the phone, and it worked, I flashed the original stock tmobile rom, and it loaded fine, I tried to start the whole process again, but now I get stuck in the very beginning, trying to get TEMP root, I start the fr3vo exploit like the guide stated, but then i keep getting error messages on the command line prompt saying that there is an error with ADB, then when I power the phone with volume down and power, the revolutionary is no longer on the top of the screen, but it still says SHIP S-OFF. Does that have to do anything with my problem? is there a way to GET S back to ON, so I can start the process over? or am I better off having S off??? I installed ROM MANAGER and tried to flash a recover image thinking that having S off would allow me to do this, but I get error messages saying there are problems with the permissions. the web site for the guide I used to root is this one incase anyone wants more details into what I did, any help would be greatly appreciated. theunlockr.com/2011/09/09/how-to-permanently-root-and-gain-s-off-on-the-t-mobile-mytouch-4g-slide-revolutionary-method
Use perm root method. Myself I flashed oneclick in recovery, but you can follow the guide the perm root part.
Btw rom manager supports flashing of the new cwm only. I checked the roms in rom manager they aren't supported. You have to go to the cm7 thread here and download and flash cm7 from recovery.
Just redo root process and install cwm from rom manager. Then go to the dev section and flash your favorite rom in recovery. My sig has directions on how to do everything.
Also if you're having permissions error use root explorer on the rom manager apk make sure it has execute checked. Also I think rom manager has a fix permissions button. Its never worked for me.
S off will allow flashing of cwm. However you need to be rooted to flash cwm threw rom manager. My sig has a guide on installing cwm without being rooted.
sent from my Agent Orange MT4G Slide using xda premium
Thanks for the QUICK reply, but I looked at the guide, and it stated I have to have recovery installed, BEFORE I do the perm root method, but I dont have recovery, when I do HBOOT, and I try to boot into recovery, I get a red exclamation mark on the screen and I have to end up taking out the battery. Thats why I was wondering if having S OFF from the beginning now is what is messing me up when I am trying to ROOT again, I mean, I am doing the same steps.... just now I get errors when I try to do the TEMP root step... so I cant continue... and I cant get ROM MANAGER to flash a recovery image... is there a guide or steps someplace that can guide me to root the MT4G slide already having S off?
I found the problem myself, I had to enable USB Debugging.
I had USB debugging enabled.... hmmmm you made me doubt myself... I guess I will try it again, since I flashed stock rom again all settings were reverted... so I cannot VERIFY I had USB debugging on, but I was sure I did... I will try again and post... I am reflashing the stock rom like 5 times a days trying to root again =(
wait... cwest31, you had which same problem? because I was writing about 2 problems: about booting into recovery with S off, but no recovery image (hence I got red exclamation mark), and trying to get ROM MANAGER to flash a recovery image on my phone since I have S off already, but I get error messages (problem with permissions)
RT2023 said:
I had USB debugging enabled.... hmmmm you made me doubt myself... I guess I will try it again, since I flashed stock rom again all settings were reverted... so I cannot VERIFY I had USB debugging on, but I was sure I did... I will try again and post... I am reflashing the stock rom like 5 times a days trying to root again =(
wait... cwest31, you had which same problem? because I was writing about 2 problems: about booting into recovery with S off, but no recovery image (hence I got red exclamation mark), and trying to get ROM MANAGER to flash a recovery image on my phone since I have S off already, but I get error messages (problem with permissions)
Click to expand...
Click to collapse
Umm...did you read the full instructions very carefully? When you get to the part where you flash the Superuser .zip file, you need to try it several times before it'll hold.
blackknightavalon said:
Umm...did you read the full instructions very carefully? When you get to the part where you flash the Superuser .zip file, you need to try it several times before it'll hold.
Click to expand...
Click to collapse
What he said.
Also ROM MANAGER WILL NOT WORK UNLESS ROOTED. Get rooted then try flashing the image. The compendium also has step by step guides using terminal emulator once rooted
sent from my Agent Orange MT4G Slide using xda premium
Also I want you op and the other one to be clear on what s off is and root.
Getting S OFF allows unsigned zips to be flashed. This means you can now flash roms and root. Without s off you cannot root, rom, kernels. S OFF is not root.
Root is gaining admin rights over your phone. this allows programs that require access to the root files to have access to them. ROM Manager, titanium backup, drocap, setcpu will be granted access to the root files and programs which unrooted phones would not be granted access .
This can be a reason why you two are having trouble using rom manager unrooted. Rom manager cannot access the files it needs
sent from my Agent Orange MT4G Slide using xda premium
Please go follow this thread ---> http://forum.xda-developers.com/showthread.php?t=1178606. It tells you how to Permanently root a device that is already s-off.
AWESOME!!! turns out i just had to run revolutionary TWICE, and the second time it figured out it was already rooted and then asked if I wanted to install recovery, I dont know how to do it manually so I clicked yes, and THEN i was able to go into recovery and flash the PERM root ZIP, rebooted and i had SUPERUSER in my app drawer!!!! awesome, now to try to get the version of google talk installed that actually allows for video chat!!! I HATE QIK!!!!!!
DROIDMODER, CWEST31: Thanks so much for the lenghty explanation and help. I have loved android for the ability to customize, and I had the G1, MOTOCLIQ, G2, and now MT4GS, I rooted my G2, but didnt do anything to it because i was scared to F it up, but with the MT4GS I got the balls to do it just because I was SOOOO UPSET that the phone comes with a version of GTALK that does NOT ALLOW FOR VIDEO CHAT!!?!?! WTF!!! whats the front camera for then?! and QIK sucks, not all my friends are on tmobile... i was even more upset when the HTC AMAZE has a version of GTALK that does allow for video chat straight out of the box!!! this is my main push to wanting to root... thanks for letting me vent! lol and thanks for all your great info
RT2023 said:
AWESOME!!! turns out i just had to run revolutionary TWICE, and the second time it figured out it was already rooted and then asked if I wanted to install recovery, I dont know how to do it manually so I clicked yes, and THEN i was able to go into recovery and flash the PERM root ZIP, rebooted and i had SUPERUSER in my app drawer!!!! awesome, now to try to get the version of google talk installed that actually allows for video chat!!! I HATE QIK!!!!!!
Click to expand...
Click to collapse
Your welcome! now procead to install undead's senseless ROM (Best Rom available) and also get rom manager and flash the official CWM recovery! Also proceed to "thank."
mmmm... I tried to install a ROM before and thats what F-ed everything up =/ I am hesitant, I really want a Gtalk version that allows for video chat, does the senseless rom have video gchat capabilities??