Related
This makes getting into Clockwork, well, clockwork. This flashes Clockwork custom recovery, replacing your stock recovery. To top it off, if you are running a stock ROM, it will root it in the process.
Great job, Unrevoked Team!
Once you load this, don't forget to donate to EFF.
Go get it!
NEW 08-01-2010: shad0wf0x has made a custom Ubuntu LiveCD spin with a script that pulls down the Unrevoked tool and runs it as root - all from the Ubuntu Desktop. This ends hassles for windows users having driver troubles, and requires NO LINUX KNOWLEDGE and NO LINUX INSTALLATION. This should work on any device supported by the unrevoked reflash tool.
Check out shad0wf0x's thread here: http://forum.xda-developers.com/showpost.php?p=7449486&postcount=1
Notes:
Please read Shadowmite's quoted post below carefully
Linux users MUST run reflash as root (sudo su or equivelent - this does NOT mean root is required on the phone - root is not required).
After flashing, the phone will go to Clockwork recovery when shut down with the USB cord connected and charging. Clockwork cannot be used reliably when started in this manner. To start clockwork, start with the USB disconnected and powered down completely, then start the phone into HBOOT and then recovery normally.
I have contacted Koush regarding the missing battery meter while charging. It's unlikely that this will be restored.
Shadowmite said:
Recovery Reflash Tool
Available for linux, mac, and windows all at once. Also should support Evo, Incredible, and Desire. To clarify it will require that you have root already. If you don't, please proceed with the other method (http://forum.xda-developers.com/showthread.php?t=699088) for now to get it until we have a better option (which still is in the works).
First steps:
1. You will need to make sure in windows at least that you have the proper driver for hboot:
http://www.unrevoked.com/rootwiki/doku.php?id=public:windows_hboot_driver_install
2. You will also want to at some point do a adb shell into the phone and su if you have not. Superuser if installed will prompt you to give access. This must be done before the tool will work.
3. HTC Sync is BAD news... If you have it, please uninstall if you have issues, or just for spite. It interferes with us communicating to the device randomly, also pdanet, doubletwist etc could cause issues. If it uses USB and you have problems, try disabling/uninstalling until after the reflash is complete.
4. Make sure you have a sdcard in the phone, it's needed.
5. When asked ALWAYS CHOOSE CHARGE ONLY, perhaps you should check remember this...
THE LINK:http://unrevoked.com/recovery/
Help I'm stuck at waiting for system to settle
check these common issues:
- You switched your driver to the one from this post? It's NOT identical to the SDK one.
- You don't have any usb applications that might be taking focus while we are working with the phone right?
- Is the SD card present in the device?
- You did give su permenent access when you allowed it in superuser right?
---------------
If you want to donate, we prefer donations get made to the EFF. They protect our rights to do what we enjoy, reversing code in devices we own and making them do things we want them to do. Our team donation link is: http://action.eff.org/goto/unrevoked
Click to expand...
Click to collapse
AAA!!! !!!
Wait for it!!!!!
Yesss!!!
Sent from my HTC Liberty using XDA App
This is indeed great news....NOW the real fun begins........
This just isn't working for me at all...I've tried it several times on multiple computers. It never does anything but say waiting for device...............
I have confirmed root several times and installed the proper drivers several times
so what exactly does this do?
nothing until the updated version is posted.
Edit: sorry about that, I didn't answer your question. It will flash Clockwork custom recovery on rooted Arias so that we don't have to go thru the crazy adb chase to get to clockwork. It will replace the stock recovery.
Almost... We haven't pushed the new version up quite yet.
_Opiate_ said:
This just isn't working for me at all...I've tried it several times on multiple computers. It never does anything but say waiting for device...............
I have confirmed root several times and installed the proper drivers several times
Click to expand...
Click to collapse
Okay, here's some news from shadowmite's site.
shadowmite blog said:
Recovery reflash is out…
Published at: 01:06 pm - Friday June 25 2010
Well we released the tool here, and already today we are adding a new device to support, the HTC Aria. Again rooted via the same recovery adbd race they too can benefit from a easy way to get back in to flash roms at will. We will be adding a FAQ to the unrevoked site as well in order to answer some common questions about the process.
http://unrevoked.com/recovery/
In other news, we also still intend to hopefully push a method which will greatly simplify getting root on the newer secure devices using another kernel exploit. While it’s in progress and we have seen it work on desktop machines, and even the android emulator, the phones remain resistant so far. Hopefully we will get this taken care of.
We also have a intent to release a full nand unlock (as opposed to the temporary unlock we use to flash this recovery) which will manifest via a hboot flash. Being a much riskier thing, we are trying to cover ourselves completely before bricking devices testing this.
Click to expand...
Click to collapse
This will make my forays into Froyo much less stressful... you know, not having to spend three hours trying to get clockwork running before I can get my changes onto the phone after I do yet another thing to try fixing the kernel. xD
i think i just cried SO BEAUTIFUL
Have they updated the tool yet?
I haven't heard anything yet.
Almost! We're working out a FAQ and slight revamp to the webpage that was a needed bit. almost up.
Shadowmite said:
Almost! We're working out a FAQ and slight revamp to the webpage that was a needed bit. almost up.
Click to expand...
Click to collapse
Cool. This will make a few happy campers.
Attn1 a question about your quote section on the first post, it says uninstall HTC sync is that for us? If so how do I get my necessary drivers to stay on my computer while uninstalling the linked program? Sorry I am just a little confused...
cropythy said:
Attn1 a question about your quote section on the first post, it says uninstall HTC sync is that for us? If so how do I get my necessary drivers to stay on my computer while uninstalling the linked program? Sorry I am just a little confused...
Click to expand...
Click to collapse
Well, according to Shadowmite's directions, Sync messes up this process. If you have a linux livecd, better to do it from that. I did mine on a Linux box.
Ok, it's live! HTCSync is a problem, it likes to random mess with the communications. Please remove it and then reinstall after you flash...
Also make sure to choose charge only!
Have fun, it's up and ready!
http://unrevoked.com/recovery/
I don't really feel like messing around with linux right now, but really want to try this, is there a workable way to get the drivers without htc sync?
I am quite the newb when it comes to android and rooting period, if I already rooted my phone with a simple oneclick root, and want to use a new oneclick root, one with clockworkmod as part of it, can I just reroot by following the oneclick steps or do I need unroot first?
Sent from my epic 4g
sirens6 said:
I am quite the newb when it comes to android and rooting period, if I already rooted my phone with a simple oneclick root, and want to use a new oneclick root, one with clockworkmod as part of it, can I just reroot by following the oneclick steps or do I need unroot first?
Sent from my epic 4g
Click to expand...
Click to collapse
Well if you already have CWM installed then you shouldn't need to use the new version of the one-click-root method. All this does is simplify the actions even further by doing both tasks at once. If you do want to, for some reason, use the newest root method then I would suggest unrooting first just in case any errors occur with files already existing etc. Hope this helps!
Technically you shouldn't need to do an uninstall, but it doesn't hurt either...
I have rom manager but I don't think I have cwm. Everytime I test it by rebooting I get an error message and the options are still blue unlike the green options that I have seen if cwm is working. Is there some way to just install or flah or whatever it is cwm? If so, where do I get it and how do I do it? Thanks
Sent from my epic 4g
Rom manager won't work unless you have a kernel that supports it. I'm assuming that if you are rooting then it is the stock kernel and rom manager install won't work. You can install right over it if you want. Honestly the simplest way for me to do this was z4root from market and then clockworkmod recovery one click. Not the all in one. The try this last.bat seems to be less prone to failure. And if it is giving you trouble I might suggest that you install the usb drivers on another computer and run cwm rec from a thumb drive.
Sent from my SPH-D700 using XDA App
What... the easiest way is to download noobnl one click zip and the drivers.
Install the drivers (exe). Restart the pc and the phone. Plug in the phone and let it install the phone. As long as it installs adb driver you'll be fine. Extract and open the one click and start the .exe in there. A black window opens, press enter and it should go to town. If you hit enter and it pauses. Just restart the pc again and unplug the phone. Open the one click .exe again, plug the phone in and hit enter. It will go.
Phone restarts and your good to go with clockwork.
5 roots, 5 different computers. Perfect every time. Noobnl has made this cake.
Sent from my SPH-D700
I used the noobnl oneclickexploit when i rooted my phone, i have not flashed any roms or kernels that i know of, please hold my hand and walk me through the process of what i should do to get clockworkmod flashed, should i follow the steps listed above or do i have to do something more?
Honestly, I prefer using the all-in-one batch file.
Install your drivers (if you haven't already)
Turn on debugging mode on your phone
Extract the .zip from the link above somewhere on your pc.
Plug phone into computer and let it recognize.
Run run.bat from the .zip you downloaded.
Press 1 to reroot. It will remove previous roots. Say yes when it asks, andlet it do its thing.
Press 3 to install CWM, say yes, let it do its thing.
And that's it. I've had some phones hang the first time rooting, but after restarting the phone it usually works. Also, keeping the screen alive seems to help. Always give it a few minutes to do its thing, but if it hangs, restart the phone and try again. It may help to restart the computer. I've seen one computer with buggy drivers that refused to do this or odin, but I have successfully done it with both my laptop and my work computer without too much trouble.
Press 1 and 3 on what, my phone or my computer?
Sent from my SPH-D700 using Tapatalk
on computer. when you run it, it'll be a command prompt and you can just follow the instructions on it.
Ok, I understand all those steps, thank you. Next question, is there a place where I can find clockworkmod by itself, if so where, and how do I install?
Sent from my Epic 4g using Tapatalk
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.
Guys,
Been reading all night so i appreciate your help and patience. I just picked up a charge (coming from thunderbolt - finally gave up) and am trying to root and flash some of the roms here.
I am very familar with adb and tried to root but it hung at gingerbreak. from what i understand in order to root, i need to downgrade my firmware to ed1. i am trying to figure out how to do this on a mac.
i downloaded heimdall which looked to be the right solution, but when i load the package in hemidall i get the following error: firmware.xml is missing from the package.
once i am rooted, do i have to use heimdall/odin or can we download zips to sdcard as with the thuderbolt?
also not finding a clear way to install cwm without odin either.
any help would be greatly appreciated.
sincerely
eric
The ADB method is completely wrong. We use custom kernels to root. They are included in all custom ROMs but if you want to just stay stock, flash them in Heimdall (I don't know how to use it, as I use a REAL computer). And most of the time you can just flash new roms in CWM, the only time you can't is when you upgrade GB-Froyo etc. Or when the developer says it's odin only. People have had luck emulating Windows within OS X and using odin from there.
Sent from my Droid Charge running GummyFroyo 1.9.1
Eric, the vast majority of users here use Odin for flashing. I have a Mac and a PC but have not used Heimdall simply because Odin was available, so I can't directly answer questions about Heimdall unfortunately (although I suppose I should learn about it eventually since I'd be able to use my laptop to flash).
There are multiple ways to get rooted, I guess the first question is where you want to end up? Were you looking at Froyo or Gingerbread based ROMs?
Please use the Q&A Forum for questions Thanks
Moving to Q&A
charlie_c said:
Eric, the vast majority of users here use Odin for flashing. I have a Mac and a PC but have not used Heimdall simply because Odin was available, so I can't directly answer questions about Heimdall unfortunately (although I suppose I should learn about it eventually since I'd be able to use my laptop to flash).
There are multiple ways to get rooted, I guess the first question is where you want to end up? Were you looking at Froyo or Gingerbread based ROMs?
Click to expand...
Click to collapse
I pulled out an old XP computer and was able to load a new kernal for root and get CWM installed. Now i have to figure out which ROM!
pnd4pnd said:
I pulled out an old XP computer and was able to load a new kernal for root and get CWM installed. Now i have to figure out which ROM!
Click to expand...
Click to collapse
Gummy 2.0 is gonna hit today!!! its gonna be the ultimate rom
anoninja118 said:
Gummy 2.0 is gonna hit today!!! its gonna be the ultimate rom
Click to expand...
Click to collapse
Agreed! At least until we see Cyanogen(which shouldn't be too long) so we can compare, I've never used Cyanogen before and I'm pretty interested to see what all the hype is about.
Heimdall doesn't work on the Charge
I know your pain, I am a fellow Mac owner. Mac's are sick computers, but I wont touch the portable products.
Anyhow, grab VMWare and get yourself some Windows XP. If you found yourself to XDA Forum, I asure you can figure those out.
One item to mention though, if you use the integrated version on VMWare, and you share files between the PC and mac, the file that you plan to flash with Odin must be in the PC area. You can unzip it on the mac, you can download it on the mac, but when it comes time for Odin, it must be on the PC.
I found this all out by trial and error.
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??