Related
***********Don't follow this method**************
THIS is what you want to do. This thread is an older method.
Do this at your own risk!!!....I'm by no means an expert on this. In fact it's the first time I have done this. There are probably tons of guide to doing this on the T-Mobile version but I made this to help people with the Canadian Rogers G1. So it only applies to that specific phone. This is also expecting you be using Windows (I use XP but Vista will work but I don't know where the command prompt is found....google it if it isn't in the usual spot). Also the commands would be the same using a Mac but yet again I don't know what or where the equivalent of windows command prompt would be found on a Mac.
First off you need the Android SDK which you can get from here (http://developer.android.com/sdk/1.5_r2/index.html).
Unzip the folder inside the .zip file to C:\Android so the final resulting file structure will look like C:\Android\android-sdk-windows-1.5_r2\
Now do the steps 2 and 3 found here http://developer.android.com/guide/developing/device.html
I have cut and pasted these steps here but if you are using a mac you may need to refer to the link. Actually refer to it anyways in case I missed something.
**************** Steps 2 and 3 *********************
Turn on "USB Debugging" on your device.
On the device, go to the home screen, press MENU, select Applications > Development, then enable USB debugging.
Setup your system to detect your device.
If you're developing on 32-bit Windows, you need to install the 32-bit USB driver for adb. The USB driver is included in the SDK package. To install it, follow these steps:
1.Connect your Android device via USB. When the Found New Hardware Wizard appears, you'll be asked if you'd like Windows Update to search for software. Select No, not this time and click Next.
2.Select Install from a list or specified location and click Next.
3.Select Search for the best driver in these locations. Browse to the usb_driver/x86 in the SDK package (<sdk>\usb_driver\x86).
4.Click Finish. The system should install the driver files as necessary. Your machine may require a reboot.
********************************************
Plug your USB cord into your phone and plug the USB cord into your computer.
Open a command prompt in windows by going to Start/Run and then type cmd. You should a dos like window open up. Now navigate to the directory C:\Android\android-sdk-windows-1.5_r2\tools
Type “adb devices” to confirm USB Debugging is turned on
Keep the command prompt open for later use
Get fastboot from here (http://www.htc.com/www/support/android/adp.html) and put it in the tools section of the SDK
Get these files http://drop.io/ii4t2ax and put them in the tools section of the SDK. Mount your sd card so you can copy update.zip to the root of your sd card.
Turn off your phone and then press the camera button and the power on button so it loads up to fastboot mode (or whatever it is called..lol). Once it gets to the screen with 3 androids on skateboards on the bottom you should press the “call” button to the farthest left. It should go to another screen that says “FASTBOOT USB”. If it only says “FASTBOOT” then you gotta plug in the USB cable which you should have left plugged in if ya followed the steps properly .
Now in the command prompt you need to type “fastboot boot recovery.img” don't touch your phone tile it gets to a new choice of menus in recovery mode. Once it gets there you should make a nandroid backup. I really urge you to make the backup. Make sure there is space left on your SD card.
So follow the menus and press the button combination to make the back up and once that is done press the other button combination to apply the update.zip file....Do not touch your phone at all....I'll cut and paste what Haykuro's directions were on this part to emphasize the importance of not touching anything....
(LET IT FINISH, DO NOT TOUCH ANYTHING UNTIL YOUR PHONE IS COMPLETELY IDLE. DO NOT TOUCH AFTER FIRST REBOOT (WHEN CHIP APPEARS) UNLESS YOU LIKE A BRICK. )
Mine didn't take very long but if it does still do not touch anything. Please....just don't!
Once it is done press HOME+BACK to reboot the phone out of recovery mode.
Power off your phone and then press the camera button while pressing the power on button to go back to the fastboot menu. Press the “call” button (to the farthest left remember!) so you see it say “FASTBOOT USB”. Once again...If it only says “FASTBOOT” then you gotta plug in the USB cable which you should have left plugged in if ya followed the steps properly .
In the command prompt which you should have left open for convenience you have to type “fastboot flash boot boot.img”
Then type “fastboot flash recovery recovery.img”
Then type “fastboot reboot”
At this point you basically have root but you need to change permissions on a file that need to be on the phone so everything works as your would expect with root
Turn the phone on to be on the operating system.
Type “adb root” in the command prompt to confirm you have root access
Download this file http://www.magicandroidapps.com/su.zip
Unzip the file to the tools folder of the SDK
In the command prompt type “adb remount”
Then type “adb push su /system/bin/su”
Then type “adb shell” and you should get prompted with a # symbol
Type “chown root.shell /system/bin/su” right after the # symbol
Then type “chmod 6755 /system/bin/su”
That should be it...try running the market enabler or SetCPU which you can get here http://forum.xda-developers.com/showthread.php?t=505419
If they work then you have root....currently you CANNOT use any of the custom roms because they were made for T-Mobile versions of the G1. I'm waiting for conversions of these roms myself so have fun waiting just like me. This is the first time I have ever hacked/rooted any phone so be sure to research stuff yourself...I might have things wrong. Who knows....it's all a risk just like I took when I decided to try it without having a step by step guide to read from.
Remember guys...I JUST wrote this so be sure to read it the whole way through before jumping into things. Post problems you run into here so I can fine tune it.
so you managed to root the rogers G1?? great job!! did you figure this out yourself???
no...Haykuro did this. I just took all the available information and put it in order to help others do it. It was all in this thread here http://forum.xda-developers.com/showthread.php?t=522127
Can we get a tutorial of how to flash a new rom now I really want to try out the new hero rom.
there are currently no compatible roms. Cyanogen would like to port his ROMto the rogers version but he doesn't have a rogers phone to test with. Hopefully we would not need to buy him a whole phone just to port his ROM....if he employed a bunch of testers to help him he might be able to do it. I really don't know what he requires to do this though. I'm sure we will get some compatible roms soon. Maybe some of the roms do work....pretty early in the game to know what works and what doesn't. I've personally been having a great time ever since I bought this phone just reading about it, watching things happen and tinkering with things. I can just imagine how Haykuro feels being the one to make this happen. I need a compatible ROM to go further though.
XwXDv8XwX said:
there are currently no compatible roms. Cyanogen would like to port his ROMto the rogers version but he doesn't have a rogers phone to test with. Hopefully we would not need to buy him a whole phone just to port his ROM....if he employed a bunch of testers to help him he might be able to do it. I really don't know what he requires to do this though. I'm sure we will get some compatible roms soon. Maybe some of the roms do work....pretty early in the game to know what works and what doesn't. I've personally been having a great time ever since I bought this phone just reading about it, watching things happen and tinkering with things. I can just imagine how Haykuro feels being the one to make this happen. I need a compatible ROM to go further though.
Click to expand...
Click to collapse
Is Haykuro working with Cyanogen? Man I just want to play with the Rogers Rom. Oh well I guess I'll settle for getting rid of the Rogers crap and being able to buy stuff on the Market finally.
Yep, I made a 3.6 for the Rogers Dream. I haven't actually tested it because I don't have one, but I used Haykuro's tools to build the boot image. Let me know if it works for you guys!
Holy...where is that at? lol
My wife has gotta get her ass home with my phone damnit! lol
http://forum.xda-developers.com/showthread.php?t=518851
lol, I just finished restoring my phone too. Oh well I am downloading your files now cyanogen, here's to hoping I don't brick my phone on my first flash attempt.
Can someone point me to a guide to flash this rom to my phone?
XwXDv8XwX said:
Can someone point me to a guide to flash this rom to my phone?
Click to expand...
Click to collapse
After you have rooted, copy the file to your sdcard as "update.zip", boot into the new recovery mode, wipe your data if you are coming from the stock build, then flash the update! The first boot will take a bit longer than usual. Check my thread for a FAQ.
Just wanted to say "Thank You" I have been following the threads in the background for the better part of a week, and was hesitant to give it a shot as I am not too sharp on dealing with dos boxes. However followed it along and everything went off perfect, grabbed set CPU and installed it and works. So I guess I have root. Not really sure what I can do with root, but will look forward to browsing around and seeing what is cool.
The big thing is I want to be able to flash new roms. So I guess this is the first step in doing that. (already actively flash PPC roms on the Hermes)
Again thanks for everyones work on this.
well here it goes....it'll be the first time I ever flashed a new rom to my phone...at least I know some other people have tested this version of cyan's rom so I feel pretty safe doing this. I would just send it back and pretend I don't know what's wrong with my phone if I did brick it but things seem to be going pretty smooth so far.
I wonder if Cyanogen meant to wipe date first or after I applied the update.zip.....I figure he meant to wipe after I apply the update since the update was on the sdcard so I would not be able to apply an update I wiped off the sdcard. It's taking longer to boot up like he said so hopefully that's a good sign. I did just remember there were a few pics I would have prefered to save...lol....oh well.
XwXDv8XwX said:
I wonder if Cyanogen meant to wipe date first or after I applied the update.zip.....I figure he meant to wipe after I apply the update since the update was on the sdcard so I would not be able to apply an update I wiped off the sdcard. It's taking longer to boot up like he said so hopefully that's a good sign. I did just remember there were a few pics I would have prefered to save...lol....oh well.
Click to expand...
Click to collapse
No, you wipe before the update. Wiping doesn't erase your SD card, only the internal data partition.
Also, my ROM is a "Google" based ROM. You'll have to sacrifice the spiffy HTC dialer and Exchange support, but I include all the other HTC apps.
How's your flash going XwXDv8XwX? I tried, but was stuck on the Rogers screen for more than 10 minutes. I rebooted the phone and tried again using the "adb logcat" command to try and see what my phone is doing but as soon as it restarted I stopped getting stats. Is this like a 20-30 minute setup process perhaps?
This is taking ALOT longer than usual. It's staying at the rogers logo right now....how bad is this?
Hi I've been reading these forums for ages but only just signed up, I'm looking to root my hero (surprise) and complete newb.
Basically current build/software is 3.32.405.1 so 2.1, followed the rooting instructions exactly, then rebooted holding home and power on buttons but it just boots straight into a red triangle with exclamation mark in the middle of it, I can hold power and volume up to get a small menu with apply sdcard: update but tried that after getting frustrated and that said that the file wasn't verified.
how do I get the normal recovery screen because already have a villainrom on the sdcard.
You need to do the root process to get to the care bear, then flash villainrom on the care bear, before rebooting.
That will get you sorted
Well I rooted using universal androot, then used the teminal to input the su (press enter)
flash_image recovery /sdcard/recovery.img (press enter) part of instructions but at no point do I see the care bear :S
I have the same problem as Ejen. The phone is root i have superuser permission i do titanium backup .I put RA-hero-v1.7.0.1 with Better Terminal Emulator. When I turn off phone and press Home&Power I get a picture phone with a triangle. Does anyone have an idea how to solve this?
Yes, this is because stock rom automatically reflashes recovery with the stock one each shutdown iirc.
You need to stop this happening, but I can't remember the command. When you have root using universal androot though, you can stop it happening.
Or maybe it's too early for me. Wait till I've had a coffee or two and I'll revisit this...
Perhaps you can edit /system/etc/install-recovery.sh. A quick look trough /system didn't find anything like a shutdown script so perhaps this file is run by the android environment.
I had this same issue the other night, been searching for a fix, hopefully one appears here soon, thanks Pulser_g2, i was hoping to install your 1.5 Rom
Bloke
Ah seems I'm not the only one well at least I wasn't just being silly then, well tried it multiple times but still seem to have no success even tried the unlockr websites method with no success either.
If anyone knows thanks
Right... Are you on 1.5 or 2.1 just now?
Could someone (preferably the most tech savvy here) if you're on 2.1, try http://forum.xda-developers.com/showthread.php?t=726118 and see if that works.
I'm trying to work out what's going on here...
P
I'm 2.1 and had been using your other guide to root my phone but embarrasingly got stuck at stage 2 whilst trying to set up ADB (my knowledge of cmd is very limited to the point I only know the command tree ), saw the guide on XDA and thought that looks really simple so tried that instead, then tried unlockr method when XDA's didn't work now given up and asked for help
Ejen said:
I'm 2.1 and had been using your other guide to root my phone but embarrasingly got stuck at stage 2 whilst trying to set up ADB (my knowledge of cmd is very limited to the point I only know the command tree ), saw the guide on XDA and thought that looks really simple so tried that instead, then tried unlockr method when XDA's didn't work now given up and asked for help
Click to expand...
Click to collapse
Ok,... So how far did you get on setting up adb http://www.villainrom.co.uk/forum/s...de-Setting-up-ADB-and-how-to-use-it.-(Windows) ?
I had done up to part 4 using ADB, opened up cmd prompt I couldn't seem to push stuff to the SD card and was unsure what I did wrong.
When checking the USB works part 3, I used the link chose part 2, HTC sync users > ADB I couldn't find android_winusb when updating the driver software. I'm probably missing something or being silly now but I don't know
Ejen said:
I had done up to part 4 using ADB, opened up cmd prompt I couldn't seem to push stuff to the SD card and was unsure what I did wrong.
When checking the USB works part 3, I used the link chose part 2, HTC sync users > ADB I couldn't find android_winusb when updating the driver software. I'm probably missing something or being silly now but I don't know
Click to expand...
Click to collapse
Type adb devices, and if you see your phone's serial number, then you don't need to worry about drivers. Remember to "cd" into the correct folder first.
I'll try that but CD did nothing I'm running windows 7 and it sticks on C:\users\username Can't go back
Ejen said:
I'll try that but CD did nothing I'm running windows 7 and it sticks on C:\users\username Can't go back
Click to expand...
Click to collapse
Where have you downloaded your Android SDK too?
for example > "cd c:\SDK\tools"
pulser_g2 said:
Right... Are you on 1.5 or 2.1 just now?
Could someone (preferably the most tech savvy here) if you're on 2.1, try VillainROM Roots 2.1 and see if that works.
I'm trying to work out what's going on here...
P
Click to expand...
Click to collapse
I guess that is already on the phone RA-hero-v1.7.0.1 as you said stock rom automatically reflashes recovery. I suppose that the method VillainROM Roots 2.1contains RA-hero-v1.6.2.img. What will then happen with recovery if i try to do again root with VillainROM Roots 2.1?
When you try that method, you get the phone booted into patched recovery, at which point you take a nandroid backup and flash a custom ROM.
this prevents the recovery being lost. Just try it
I'm not at home and can not install ADB and run runindos.bat. I have on SD card recovery and FroydVillain 1.5. That's why I tried this method.Next week I'll be home and if someone does not fix the problem i will try the method you suggested me.
Can I try to put again recovery with Better Terminal Emulator, maybe recovery was corrupted ....
i went through the same thing!!
Ejen said:
Hi I've been reading these forums for ages but only just signed up, I'm looking to root my hero (surprise) and complete newb.
Basically current build/software is 3.32.405.1 so 2.1, followed the rooting instructions exactly, then rebooted holding home and power on buttons but it just boots straight into a red triangle with exclamation mark in the middle of it, I can hold power and volume up to get a small menu with apply sdcard: update but tried that after getting frustrated and that said that the file wasn't verified.
how do I get the normal recovery screen because already have a villainrom on the sdcard.
Click to expand...
Click to collapse
helloo!! i apologise if i am interupting or butting in whilst your in the middle of other solutions... i just saw the title and jump right in. i went through the exact same thing just 2 weeks ago!! unfortunately for me there was no successful forums or websites at the time... it sounded like a simple problem, with no simple solution.
this may not be what you where looking for, but its a very quick easy method that definately worth a try.
so... am i right in saying you have the official OTA HTC android 2.1 update?? and you now want to get this rooted?? and have you also tried rooting using the two common methods, the "one click root" and the "unrevoked" one? thats wat i did and i kept being stuck at the same red triangle and exclamation mark.
those methods (and countless others) will not work with the official htc hero android 2.1. (as far as i know) what you will need to do is downgrade the phones software. check htc's website and look for the older RUU and using the computer get your hero back to android 1.5. (under no circumstance should you upgrade your 1.5 android to the 2.1 android via HTC's OTA update... its only going the remove the root access!!!! - always reject it)
then continue to root as per the numerous rooting guides. done? now, obviously you will want to flash an android 2.1 rom. if you want to keep to htc's original 2.1, you can search for this in the forums under 'development'. or go ahead and flash the custom roms (villianrom).
thats exactly how i did it. im not entirely sure if this is the info you are after... but reply back and ill be happy to answer any query - big or small. (i should warn you, im no expert - but this forum is filled with the earths most powerful brains - u should have an answer in no time!!)
I have an HTC Hero. I ran the simple root method and got Carebare response.
I too have read numerous threads in the forum here and elsewhere but can't seem to get past the USB section.
adb says no device
I can use HTC Sync to sync data to the phone.
The SDK is installed and I have previously used it to capture screen shots of my device.
If I try to run one of the RUU executables, it fails with a [114: USB Error] (number may be wrong but the message is right.
I can mount the SD card and copy files to/from it.
I am running Windows 7 Home Premium 64bit on a Quad Core AMD CPU.
If I do the Home/Power thing, I get the same red triangle as described in the 1st message of this thread.
Fwiw, I have successfully and repeated loaded ROM's on my previous phone (HTC S621) so I am not a complete newb (but i am newb to Android).
What am I missing? This shouldn't be this hard (at least from what I've seen posted anyway)
Hi, I was going to setup adb on my froyo MT4G, but I didn't...now I am trying to setup fastboot and ADB on my computer, but I can't figure it out. It seems like guides are written for android 2.2 when it comes to the MT4G and ADB. I have cm7 on my phone, so how do I setup ADB for it? I am trying to find it, but I don't know enough to know what would work, have tried certain guides, but once I get to a point where there is a disclaimer I tend to shy away since, I am not sure what guide I should be following for my weird situation and trying to setup adb for it..Please, thank you.
Just go to android.com and get the sdk stuff. There's intructions on the site and on here. The only difference for cm7 is your gonna need to go through the sdk and avd manager and download the stuff for 2.3. PM me after you get everything downloaded and I'll help you through any part you get stuck on.
Hmmm might be awhile before I can try this but I will
jbrew78 said:
Just go to android.com and get the sdk stuff. There's intructions on the site and on here. The only difference for cm7 is your gonna need to go through the sdk and avd manager and download the stuff for 2.3. PM me after you get everything downloaded and I'll help you through any part you get stuck on.
Click to expand...
Click to collapse
Sent from my MT4G running Gingerbread
Honestly, I think your long term fix is ubuntu. A lot of people don't want to hear that, but it's easier than you think. You can run a dual boot, or set up a virtual machine on your current computer. You can download vmware here:
http://www.vmware.com/products/player/
And ubuntu here:
http://www.ubuntu.com/desktop/get-ubuntu/download
Then install adb, fastboot, etc. and never have any driver issues again. Problem solved.
Android SDK for ADB:
http://developer.android.com/sdk/index.html
I think the executable file installs so you can run the commands from dos prompt without the difficulties of making it executable.
Fastboot:
http://developer.htc.com/adp.html
You'll need to save it to the same folder the sdk tools are in to use it in dos prompt.
Then it's reading on how to do all the necessary things to root/flash/etc.
Thank you. I am downloading the sdk files right now, I wish I had a computer so I could read more about developing and stuff...right now I just have to use my GFs when im over here, but I have to avoid things once I start getting interested otherwise I will be sucked into an abyss of knowledge for hours, and snap out of it, and then have to figure out why she is mad at me, hahhaha... so I have a generic question though... is fastboot basically like terminal? And you can get into it from hboot right? Don't need to have your computer connected to it or anything right?
foxdl99 said:
Android SDK for ADB:
http://developer.android.com/sdk/index.html
I think the executable file installs so you can run the commands from dos prompt without the difficulties of making it executable.
Fastboot:
http://developer.htc.com/adp.html
You'll need to save it to the same folder the sdk tools are in to use it in dos prompt.
Then it's reading on how to do all the necessary things to root/flash/etc.
Click to expand...
Click to collapse
fastboot has 2 components: one on the computer for entering commands onto the phone while it is in fastboot mode (the second thing). So yes, it has to be on the computer to enter commands like flashing recoveries. There are alternate methods for everything, you can flash recoveries using flash_image from the phone as well, for example.
foxdl99 said:
fastboot has 2 components: one on the computer for entering commands onto the phone while it is in fastboot mode (the second thing). So yes, it has to be on the computer to enter commands like flashing recoveries. There are alternate methods for everything, you can flash recoveries using flash_image from the phone as well, for example.
Click to expand...
Click to collapse
Wait so I have to connect my phone to my computer to use fastboot cmds on my phone?
So if I have fastboot setup, and I am walking around with my phone in my pocket and I pull it out and check xda and see a new splash screen I want. I can reboot into bootloader, and then enter fastboot and type some kind of command like.. fastboot splash3 google.img and that will work? Or your saying I have to have it plugged into the computer?...because if that is the case then whats the difference between ADB and fastboot?
fastboot is for messing with the boot section of the phone while in fastboot mode on the phone, whereas adb messes with the os itself. And you do have to have it connected to your pc to use. As to the boot images or animations, you can install some of those with root explorer by putting them in the appropriate place in the file system. For instance, boot animations go in /system/media/bootloader.zip. But some modders put out a .zip flashable file that you can flash in recovery. Confusing, huh? If you find one you want to try, the dev should let you know how to install it.
I think what you're looking for though is root explorer, which will allow you to modify certain areas on the fly from the phone. It's a paid app.
Edit: with the splash screen, i think you may have to use fastboot because it goes in the bootloader section which I don't think you can access any other place. But I'm not sure.
I have root explorer... hmm I guess I have been missing what fastboot is all about... well maybe ill just get it all setup and play with it to figure it out.. thanks for your help I'm going to sleep for now.
foxdl99 said:
fastboot is for messing with the boot section of the phone while in fastboot mode on the phone, whereas adb messes with the os itself. And you do have to have it connected to your pc to use. As to the boot images or animations, you can install some of those with root explorer by putting them in the appropriate place in the file system. For instance, boot animations go in /system/media/bootloader.zip. But some modders put out a .zip flashable file that you can flash in recovery. Confusing, huh? If you find one you want to try, the dev should let you know how to install it.
I think what you're looking for though is root explorer, which will allow you to modify certain areas on the fly from the phone. It's a paid app.
Edit: with the splash screen, i think you may have to use fastboot because it goes in the bootloader section which I don't think you can access any other place. But I'm not sure.
Click to expand...
Click to collapse
Sent from my MT4G running Gingerbread
i have read LOTS of forums on this, but have found no diffinative, working methods. has anyone actually ever done this, and if so what method did you use? links/guides would be much appreciated! thanks
I also have searched everywhere and apart from "get a pc" or "get parallels and windows 7 for your mac" I've heard nothing concrete.
Any advice on this would be hugely appreciated!
ishamm said:
i have read LOTS of forums on this, but have found no diffinative, working methods. has anyone actually ever done this, and if so what method did you use? links/guides would be much appreciated! thanks
Click to expand...
Click to collapse
No guys, all the methods posted are just theoretical blabber posted for the LULZ!...
.... NOT!!!
... all the methods mentioned on this forum work, unless stated otherwise...
only a handful require a Windows PC
yes, preinstall method works, CWM root package works, gingerbreak works,
1-click easy root also works
follow the link, go to post 3... and you have directions for Mac OS
sorry, i didnt mention, im not on gingerbread (thanks to tmobiles slow updating), and most of these rooting methods seem to require it. would going straight to unlocking the bootloader be easier on mac? (i realise the methods arent written for fun, but many require a lot of presumed knowledge of terminal commands, which unfortunately i lack XD )
thanks
Bootcamp or parallels with windows 7. That's how I did it.
xploited said:
No guys, all the methods posted are just theoretical blabber posted for the LULZ!...
.... NOT!!!
... all the methods mentioned on this forum work, unless stated otherwise...
only a handful require a Windows PC
yes, preinstall method works, CWM root package works, gingerbreak works,
1-click easy root also works
follow the link, go to post 3... and you have directions for Mac OS
Click to expand...
Click to collapse
Many thanks, I'll try one of the ones you mentioned.
I'd love to try the one click method for mac but I clocked on the link, went to third post and it's not as you suggested it might be.
If there is a simple oneclick method for mac dullards like me it would be great to tell me where to go for it. Thanks again!
i have tried using dorootv3.sh and doroot2, on terminal, but both always fail, is there any other .sh that has been shown to work?
---------- Post added at 06:19 PM ---------- Previous post was at 05:32 PM ----------
basically, after a load of different attempts, my main problem seems to be this: to root on mac, i need 2.3.4 (i have 2.2.2); to get 2.3.4 i need to unlock the bootloader; and to unlock the bootloader it must be rooted.
it seems im stuck in this cycle, and dont really know what i should do. any help would be great.
can i flash with the at&t 2.3.4 from this thread http://forum.xda-developers.com/showthread.php?t=1125944 ?
you dont need root to unlock bootloader....you unlock bootloader through an sbf flash
we seriously need a popup box on every freaking forum that will explain what ROOT actually is.
root is SYSTEM access within the OS. outside of the OS, root doesnt mean squat
you will wipe all your system when you unlock your bootloader which means:
contacts stored on phone (unless you export them to vcf on sdcard)
settings
text messages
user installed apps
it does NOT wipe internal or external sdcard (i always keep a backup of this stuff on my computer anyway when i start messing with my phone)
oh sorry, in that case i totally got the wrong end of the stick reading the noob intro howtos so to unlock the bootloader what sbf do i need to flash? that i can do now through terminal, which is very handy, but i havnt come across any howto on bootloader unlocking that just says flash an sbf
http://briefmobile.com/how-to-unlock-the-atrix-4g-bootloader
i typed in google.com
'unlock motorola atrix bootloader'
a link lead me directly to that.....its the exact same tut listed here on xda....
sorry, im having a serious slow day, just gone on holiday so brain is totally out of gear XD thanks so much for clearing up the root/bootloader confusion, i have now unlocked successfuly, and will be installing my first rom!
ishamm said:
sorry, im having a serious slow day, just gone on holiday so brain is totally out of gear XD thanks so much for clearing up the root/bootloader confusion, i have now unlocked successfuly, and will be installing my first rom!
Click to expand...
Click to collapse
its not just you confused with root. its xda-wide.
for some reason sooooo many people have this notion that root=unlocking bl/s-off/rom-flashing
its frustrating to see people suggesting to others on some forums around here that they need to 're-root' their device when they are already on a rooted rom....its baffling that so much misinformation can be spread like wildfire.
my last confusion, for now XD, is this: the alien rom contains an image, which i can flash ok, but also a Meta Inf folder and System folder. if i follow this method
"
1. Extract all the files to the same directory and CD there in the terminal.
2. Put your phone in fastboot mode (turn it on holding volume down button then press volume up)
3. Type these commands in the terminal:
chmod +x moto-fastboot-osx64
./moto-fastboot-osx64 flash boot XXXXXX.boot.img (work out what Tegra part you need to flash and change the XXXXXX to that!)
./moto-fastboot-osx64 flash system ORFR234-system.img
./moto-fastboot-osx64 flash webtop webtop.img
./moto-fastboot-osx64 reboot
"
what should i do with the 2 folders, since as far as i know, i cant just flash folders right?
thanks
ishamm said:
my last confusion, for now XD, is this: the alien rom contains an image, which i can flash ok, but also a Meta Inf folder and System folder. if i follow this method
"
1. Extract all the files to the same directory and CD there in the terminal.
2. Put your phone in fastboot mode (turn it on holding volume down button then press volume up)
3. Type these commands in the terminal:
chmod +x moto-fastboot-osx64
./moto-fastboot-osx64 flash boot XXXXXX.boot.img (work out what Tegra part you need to flash and change the XXXXXX to that!)
./moto-fastboot-osx64 flash system ORFR234-system.img
./moto-fastboot-osx64 flash webtop webtop.img
./moto-fastboot-osx64 reboot
"
what should i do with the 2 folders, since as far as i know, i cant just flash folders right?
thanks
Click to expand...
Click to collapse
alien rom, as with any other custom rom, comes packaged for CLOCKWORK MOD RECOVERY
you dont extract rom zips
you need CWM installed on your unlocked atrix, then you boot to recovery, and flash the rom zip
oh man, just when i thought i'd started to understand everything! XD
if its not too much trouble, can you explain the method to go about installing alien on a mac, or if it exists, link a relevent thread? i can only find ones which confuse me even more
many thanks
ishamm said:
oh man, just when i thought i'd started to understand everything! XD
if its not too much trouble, can you explain the method to go about installing alien on a mac, or if it exists, link a relevent thread? i can only find ones which confuse me even more
many thanks
Click to expand...
Click to collapse
you dont install roms from your computer
you need to make sure you have CWM installed. you can do this with fastboot
fastboot this recovery on
http://download.clockworkmod.com/recoveries/recovery-clockwork-5.0.2.0-olympus.img
instructions can be found
http://forum.xda-developers.com/showthread.php?t=1204500
you download a rom to your phone and flash it through recovery. no computer needed at all after you have unlocked and flashed recovery on.
and is this do-able without an SD card installed? before i get halfway down the road and find im screwed XD also it seems i need to be rooted for CWM, though i still cant find a way to do it...
ishamm said:
and is this do-able without an SD card installed? before i get halfway down the road and find im screwed XD also it seems i need to be rooted for CWM, though i still cant find a way to do it...
Click to expand...
Click to collapse
did you actually read the post above????
you can fastboot the recovery image.
you DO NOT need root in order to do so.....
yes i did read it... while it might be obvious to you, some of us have no idea what were doing. loads of howtos include having to install the rom from a SD card. also CWM says "The SD Card needs to be mounted to use ROM Manager" so i dont think its too much of a stretch to think i need one
ishamm said:
yes i did read it... while it might be obvious to you, some of us have no idea what were doing. loads of howtos include having to install the rom from a SD card. also CWM says "The SD Card needs to be mounted to use ROM Manager" so i dont think its too much of a stretch to think i need one
Click to expand...
Click to collapse
you dont need rom manager....
you boot into recovery and install from there.......
A. download rom
B. transfer to phone's storage (if you download directly from phone, obviously skip this step)
C. boot into recovery
D. wipe data/factory reset (option in CWM recovery)
E. select option: install from sdcard
F. confirm
G. after flash is complete reboot your phone, you are now on a new rom.
Hello
My phone tells me that it is ready to update to Kit Kat.
Before I install Kit Kat I would like to learn how to go back to Jelly Bean if things go t1ts-up.
So, I would like to learn how to root my phone?
I would also like to learn how to backup everything including the Jelly Bean operating system, and I would like to know how to revert my phone back to Jelly Bean?
Please forgive my ignorance, but this whole process genuinely scares me. I have only ever rooted my Samsung Ace phone once and the experience left a bitter taste in my mouth.
I did manage to root my phone. I also thought that I had created a backup but when I tested the backup I discovered that my phone got wiped and I ended up with a brick. I eventually found an official Samsung ROM but it wasn't the one I wanted and it caused a few problems, especially with the Bluetooth feature.
I hope you can understand or appreciate my apprehension with even contemplating such a task on my expensive Nexus 4.
Cheers muchly
the lemming said:
Hello
My phone tells me that it is ready to update to Kit Kat.
Before I install Kit Kat I would like to learn how to go back to Jelly Bean if things go t1ts-up.
So, I would like to learn how to root my phone?
I would also like to learn how to backup everything including the Jelly Bean operating system, and I would like to know how to revert my phone back to Jelly Bean?
Please forgive my ignorance, but this whole process genuinely scares me. I have only ever rooted my Samsung Ace phone once and the experience left a bitter taste in my mouth.
I did manage to root my phone. I also thought that I had created a backup but when I tested the backup I discovered that my phone got wiped and I ended up with a brick. I eventually found an official Samsung ROM but it wasn't the one I wanted and it caused a few problems, especially with the Bluetooth feature.
I hope you can understand or appreciate my apprehension with even contemplating such a task on my expensive Nexus 4.
Cheers muchly
Click to expand...
Click to collapse
You might want to check out the Wugfresh's toolkit if you are not incline with technical stuff. The toolkit is in the Development section.
Hello
I have no idea what Wugfresh's tool-kit is.
Sorry
the lemming said:
Hello
I have no idea what Wugfresh's tool-kit is.
Sorry
Click to expand...
Click to collapse
I would suggest that you study up and follow this guide here. http://forum.xda-developers.com/showthread.php?t=2010312
I was like you when I first got the nexus. Didn't know what to do and the steps seems to be so complicated. Hell..I even took couple of days to finally succeed in installing the drivers. And for me I think it is better to learn the basics of using adb before trying out the toolkits. If you start with toolkits and you will later on rely entirely on the toolkits. This is not good as some problems, the toolkits might not be able to solve it for you.
Btw, look into original android development for wug's toolkits. It is pinned there. Should be easy to find.
Sent from my Nexus 4 using xda premium
You seem to be taking interest in Rooting and stuffs. I would suggest you to get handy with a few ADB and FASTBOOT commands and you won't need any toolkit ever in Life !!!
Its very very very easy in Nexus Devices.
Here is my attempt to make you learn :-
1. Say Bye Bye to your phone OS version.
2. Open Command Prompt or Terminal.(Assuming, you have SDK & Drivers installed)
Code:
adb devices
It shall return you the device id.
3. Reboot to BootLoader
Code:
adb reboot-bootloader
4. Check for your device's recognition in FastBoot Mode.
Code:
fastboot devices
5. I assume you have all the files(Factory Image tar.gz extracted to a folder)
just type :-
Code:
flash-all.bat
BOOM...
You are now on stock KitKat !
Now, To get a Custom Recovery (IMHO go with TWRP),
1. Download latest recovery from the official website.
2. Type when in FastBoot Mode.
Code:
fastboot flash recovery openrecovery-twrp-2.6.3.4-mako.img
(Or whatever the name is)
3. Reboot your device.
Now, to get the ROOT ACCESS, after booting up the device,
1. Download the latest UPDATE-SuperSU zip from here.
2. Keep it somewhere in DEVICE STORAGE.
3. open TWRP RECOVERY
4. FLASH that ZIP
5. HIT THANKS !
Have Fun ...
Welcome to the Flashing Fraternity !!! LOL
miku3191 said:
You seem to be taking interest in Rooting and stuffs. I would suggest you to get handy with a few ADB and FASTBOOT commands and you won't need any toolkit ever in Life !!!
BOOM...
You are now on stock KitKat !
Click to expand...
Click to collapse
Hello
Thank you for replying but I fear that I will not be following your advice at the moment.
I initially asked how to ROOT my phone so that I can learn how to do backups and recoveries. My phone is ready for the Over The Air official upgrade.
I want to take things one step at a time rather than causing problems by blindly following code.
Sorry
the lemming said:
Hello
Thank you for replying but I fear that I will not be following your advice at the moment.
I initially asked how to ROOT my phone so that I can learn how to do backups and recoveries. My phone is ready for the Over The Air official upgrade.
I want to take things one step at a time rather than causing problems by blindly following code.
Sorry
Click to expand...
Click to collapse
If you want official OTA update of KitKat you should update it, and after that unlock bootloader and root phone. That way nothing will go wrong.
If you unlock bootloader and root your phone OTA update will cause problems like stuck in bootloop(your phone will be stuck on nexus logo and it will never boot into android)
If you want to learn about rooting I suggest you this http://forum.xda-developers.com/showthread.php?t=2367406
this is excelent tutorial how to root your nexus 4 http://forum.xda-developers.com/showthread.php?t=2018179
and if you are more comfortable to hear and see somebody do it you can check out this page it have video of full process and pictures for every step http://nexus4root.com/nexus-4-root/how-to-root-nexus-4-windowsmac-osxlinuxubuntu/
Good luck!:cyclops:
miku3191 said:
You seem to be taking interest in Rooting and stuffs. I would suggest you to get handy with a few ADB and FASTBOOT commands and you won't need any toolkit ever in Life !!!
Its very very very easy in Nexus Devices.
Good luck!:cyclops:
Click to expand...
Click to collapse
This process is an absolute nightmare.
All I want to do is back-up my Jelly Bean phone operating system and have it safe in case the OTA Kit Kat goes wrong. I thought that this was sensible and safe practice before doing any updates, especially something as serious as a system update?
I have now tried several Tutorials on how to root my phone and all I have succeeded in doing is wiping my phone clean and returning it to Factory Settings. The latest Tutorial was here
http://forum.xda-developers.com/showthread.php?t=2010312
I followed the following advice to this point
1) All of the files that are required, need to be in one (i.e., the same) directory. It does not matter what it is called, but all the files need to be in there, with NO subfolders. EVERYTHING needs to be extracted into this one directory;
2) Download the attachment from the end of this post and extract the contents to the directory created in step 1. (Latest version for Windows is here). Note: if all you want to do is unlock your bootloader, skip to step 7 in this section (C).
7) Reboot your device into bootloader mode (by turning it off, hold volume down, and press and hold power) and plug it into your computer;
8) Open a command prompt in the same directory (i.e., make sure you are in the same directory as your files are located). You can hold the shift key when you are in the folder in Windows explorer and right-click in a blank spot and it will open a command prompt.
I then get to the bit about rooting
E. Optional -- Root
If you want to get root access follow the steps below. (And no, this will not flash a custom recovery, and not, it will not make you "not stock".) Unlocked bootloader required. See steps above.
1) Download (to your computer) the latest version of CWM (from here) or TWRP (from here) for your device;
http://www.clockworkmod.com/rommanager/
http://www.clockworkmod.com/rommanager/developers/mako?name=Google Nexus 4
And when I click the link I am blinded by options. This is a nightmare.
Could somebody please cut through all this hyperbole and just explain how I get ROOT?
I have been at this for 24 hours solid.
the lemming said:
This process is an absolute nightmare.
All I want to do is back-up my Jelly Bean phone operating system and have it safe in case the OTA Kit Kat goes wrong. I thought that this was sensible and safe practice before doing any updates, especially something as serious as a system update?
I have now tried several Tutorials on how to root my phone and all I have succeeded in doing is wiping my phone clean and returning it to Factory Settings. The latest Tutorial was here
http://forum.xda-developers.com/showthread.php?t=2010312
I followed the following advice to this point
1) All of the files that are required, need to be in one (i.e., the same) directory. It does not matter what it is called, but all the files need to be in there, with NO subfolders. EVERYTHING needs to be extracted into this one directory;
2) Download the attachment from the end of this post and extract the contents to the directory created in step 1. (Latest version for Windows is here). Note: if all you want to do is unlock your bootloader, skip to step 7 in this section (C).
7) Reboot your device into bootloader mode (by turning it off, hold volume down, and press and hold power) and plug it into your computer;
8) Open a command prompt in the same directory (i.e., make sure you are in the same directory as your files are located). You can hold the shift key when you are in the folder in Windows explorer and right-click in a blank spot and it will open a command prompt.
I then get to the bit about rooting
E. Optional -- Root
If you want to get root access follow the steps below. (And no, this will not flash a custom recovery, and not, it will not make you "not stock".) Unlocked bootloader required. See steps above.
1) Download (to your computer) the latest version of CWM (from here) or TWRP (from here) for your device;
http://www.clockworkmod.com/rommanager/
http://www.clockworkmod.com/rommanager/developers/mako?name=Google Nexus 4
And when I click the link I am blinded by options. This is a nightmare.
Could somebody please cut through all this hyperbole and just explain how I get ROOT?
I have been at this for 24 hours solid.
Click to expand...
Click to collapse
The point you are missing is that your fear is clouding your ability to simply read and comprehend the proper steps to take. My friend rooting your phone with a toolkit is a simple task but you ask what is Wugs toolkit instead of taking the time to search for it an read up. YOu do not want to root your phone but to have someone do it for you. I used to do this for people back in the days where I would log into their pc and root their phones from my home.
My friend its simple your bootloader is unlocked and now all you need to do is push a recovery over to your phone. Now go to the TWRP thread and download the image file and follow the instructions given to you to flash the recovery. I fear if following these simple directions are too much for you maybe you should simply leave your phone alone before the next step is you calling Google with an issue or having to buy another phone...
Sorry but thats my honest opinion....
Edit: Boot into bootloader and check to see if its says unlocked. If so then all thats left is flashing a recovery
the lemming said:
This process is an absolute nightmare.
And when I click the link I am blinded by options. This is a nightmare.
Could somebody please cut through all this hyperbole and just explain how I get ROOT?
I have been at this for 24 hours solid.
Click to expand...
Click to collapse
Reading your posts, I understand your frustration. Here are my suggestions, 1) step away from your PC for a few minutes or an hour or get a cup of water, 2) put the phone aside, 3) read and re-read the information in Google Nexus 4 threads just to get the knowledge first and then start working on your phone. You will be doing fine. BTW, you should have a back up phone that you can use while working on your Nexus 4.
playya said:
Edit: Boot into bootloader and check to see if its says unlocked. If so then all thats left is flashing a recovery
Click to expand...
Click to collapse
Thank you for this useful bit of information.
the lemming said:
Thank you for this useful bit of information.
Click to expand...
Click to collapse
You got it man I know but sometimes the truth hurts... You have been given all the information laid out for you in the posts above. If this is still too difficult for you your only other task is to actually have somebody do it for you this is nothing more than simply reading and taking your time. I tell you this with all sincerity I would rather see you stop now than later see another thread created by you saying possibly bricked
Sent from my Nexus 4 using Tapatalk
---------- Post added at 02:51 PM ---------- Previous post was at 02:51 PM ----------
playya said:
You got it man I know but sometimes the truth hurts... You have been given all the information laid out for you in the posts above. If this is still too difficult for you your only other task is to actually have somebody do it for you this is nothing more than simply reading and taking your time. I tell you this with all sincerity I would rather see you stop now than later see another thread created by you saying possibly bricked
Take care
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
Sent from my Nexus 4 using Tapatalk
the lemming said:
And when I click the link I am blinded by options. This is a nightmare.
Could somebody please cut through all this hyperbole and just explain how I get ROOT?
I have been at this for 24 hours solid.
Click to expand...
Click to collapse
I trust that you have read the entire guide from that link you post. To get you see this clearly. Rooting is very easy. You just have to:
1. Install driver, download platform-tools (if you don't wanna download the entire android sdk) and SuperSU I trust that all the links are given in that guide.
2. Make sure you device is detected in adb. Copy SuperSU.zip into your device.
3. Unlock your device.
4. Push recovery. fastboot flash recovery recovery name.img
5. Reboot into recovery and flash SuperSu.zip
6. Reboot. Done.
Really..this is all it takes to perform a simple rooting. But if you're not the one who likes to read..and try to understand the steps. I suggest you not to mess with your device. You are more likely to brick it than make it better. The truth hurts but it is for your own good. Unless you prove me wrong. Then you are awesome instead
Sent from my Nexus 4 using xda premium