Related
Hi.
I recently tried to root my Magic to install CyanogenMod, but it didn't work. I can't remember exactly what I did, but I followed various tutorials that I found on this site and other similar ones. I couldn't find a tutorial that went all the way from unrooted phone to rooted with CyanogenMod installed, so I switched between a couple of different ones that seemed easy to follow.
Since breaking my Magic I have tried various methods to get it working again and used google and XDA posts, but I can't do it and I'm getting quite frustrated.
Please can someone provide steps to follow that will let me access my Android OS (preferably with the latest CyanogenMod installed, but that isn't as important).
At the moment I can access fastboot on the phone, but not the main OS or the Recovery ROM I installed (cm-recovery-1.4).
I have '32B' (not sure what it means though) and 'G'
Thank you in advance for any help.
first, download recovery rom here:
http://forum.xda-developers.com/showthread.php?t=530492
Latest :
RAv1.2.1H if it's an htc phone
RAv1.2.1G if it's a google (marked with google behind)
then download android sdk and install it.
then type in a command window:
fastboot boot adressofyourrecoveryrom.img
once your phone has booted in recovery:
adb shell mount /sdcard
adb push adressofyourupdate.zip /sdcard
and on your phone:
wipe data
apply: update.zip
it's ok :-D
kiltaiga said:
first, download recovery rom here:
http://forum.xda-developers.com/showthread.php?t=530492
Latest :
RAv1.2.1H if it's an htc phone
RAv1.2.1G if it's a google (marked with google behind)
then download android sdk and install it.
then type in a command window:
fastboot boot adressofyourrecoveryrom.img
once your phone has booted in recovery:
adb shell mount /sdcard
adb push adressofyourupdate.zip /sdcard
and on your phone:
wipe data
apply: update.zip
it's ok :-D
Click to expand...
Click to collapse
Thanks for your quick reply.
RapidShare is being incredibly annoying and won't let me download the file. Do you have a mirror?
google branded
for htc branded, i've not mirror
First of all, please let me thank all the people involved into this process:
o unrevoked and AlphaRevX teams (for their great tools)
o davidreece (for reporting the temp root method) http://forum.xda-developers.com/showthread.php?t=1190992
Since Revolutionary is not able (yet) to acquire root access on our ROM, I thought I'd get a temp root access BEFORE launching Revolutionary.
As a matter of facts I have successfully S-OFFed my device running the latest 1.47.401.4 ROM (HBOOT 0.98.0002).
I could not test this method on any other ROM version, but as long as you are able to get temp root using the commands below, you should be safe to go.
So let's get straight to the instructions:
PREREQUISITES:
o You know what you are doing. Messing up with your NAND implies a risk that you should be aware of.
o Android SDK installed. Download the "android-win-tools" from the following link otherwise (thanks .sh4d0w.) and extract the files to your \Windows directory: http://www.4shared.com/file/KK6KvF7Q/android-win-tools.html
HOW TO:
o Get your version of Revolutionary from their site: http://revolutionary.io/
o Ensure your device has "Debug USB" enabled and is connected to your PC in "Charge only" mode.
o Download fre3vo from the following link: http://forum.xda-developers.com/attachment.php?attachmentid=661246&d=1311240968
o Open a command prompt and issue the following commands to get temp root access: (thanks again, davidreece!)
Code:
adb push fre3vo /data/local/tmp
adb shell chmod 777 /data/local/tmp/fre3vo
adb shell [i](you'll get a $ prompt)[/i]
/data/local/tmp/fre3vo -debug -start FAA90000 -end FFFFFFFF [i](you should be kicked off adb shell and get back to your command prompt)[/i]
adb shell [i](you should get a # prompt now)[/i]
exit
o DO NOT disconnect or switch your device off!!
o Now that your phone has temporary root access, launch Revolutionary and follow instructions on screen.
o In a matter of seconds you will see the new HBOOT in place
o You may want to answer Y when prompted whether to install CWM or not. It will install the new 4.0.1.4 version of the tool.
o Download the attachment below and flash it via CWM. It will install su and Superuser.apk. Restart your phone and you'll end up with a rooted stock rom.
You should be able to achieve the same results on Linux as well.
That's it, folks.
thank you
but got this problem :
'adb' is not recognized as an internal or external command operable program or batch file.
thank you!!! Worked! Perfect!
hassan1990 said:
thank you
but got this problem :
'adb' is not recognized as an internal or external command operable program or batch file.
Click to expand...
Click to collapse
1. download and install JDK
2. download and install Android SDK
3. run "SDK Manager.exe" and install Android SDK Platform-tools
4. in \platform-tools\ you found adb.exe
thanx you all for this unstuctions now it works for me!!
were can i find de cwm on my phone now?
Gr.Roymar
@ slvrbllt
Add this to the tutorial.
Copy content on adb-win-tools from here>> http://www.4shared.com/file/KK6KvF7Q/android-win-tools.html
To C:/Windows
This is for:
'adb' is not recognized as an internal or external command operable program or batch file.
Because most of us don't have those files preinstalled in windows.
for HBOOT 0.98.0000, you don't need the temp root right?
Right, i can confirm it works without temp root
Only have Debuging on and phone in charge only, and run the program
Enc0der said:
Hi,
just wanted to let you know that your method for s-off finally (!) worked for me on my desire s.
I can't reply on your thread (new user..), but feel free to quote me if someone asks if this works
I'm s-off'ed now
thank you!
Click to expand...
Click to collapse
You're welcome!
so easy
thank tou
Work's like a charm! Thanx!
Although my antivirus (Norton Internet Security) killed revolutionary when i tried to download CWM.. No hassle though, just installed it manually afterwards..
Thanks, it worked.
Hi guys,
My DS is S-OFF now too , but GingerBreak 1.2 seems doesn't work. It still shows rotating circle but nothing happens. Any ideas ?
Thanks for reply.
vencis said:
Hi guys,
My DS is S-OFF now too , but GingerBreak 1.2 seems doesn't work. It still shows rotating circle but nothing happens. Any ideas ?
Thanks for reply.
Click to expand...
Click to collapse
Same for me.. but.. is it a problem? If i want to flash a custom Rom? Not really, right? 4ext is flashed so i can flash a Rom or will something break if i do that?
Cheers
Yes, you're right. I can use prerooted stocked rom or some custom rom. Thanks.
Hi All, followed instructions as laid out. When using revolutionary it hangs waiting for fastboot. Any Idea's?
Thanks
Thanks a lot for this one... I have added this to my FAQ section on this guide http://forum.xda-developers.com/showthread.php?p=16000143#post16000143.
Hope you don't mind
Thanks, it worked. It was a long night
Thanks again!
EbiEre said:
Same for me.. but.. is it a problem? If i want to flash a custom Rom? Not really, right? 4ext is flashed so i can flash a Rom or will something break if i do that?
Cheers
Click to expand...
Click to collapse
No, you are right and should be fine
All of the custom roms come pre rooted anyway, So simply flash one from recovery as you suggested and you'll be ok
Sent from my HTC Desire S using XDA Premium App
it's not working.. i don't know why. it's stuck at acquiring root.. any suggestion? i've done all the adb command. and it's already show #..
this is my third time i tried
(sorry for my bad english)
I see there are a lot of users here in these forums that either are scared of ADB or have no idea how to use it or what to do with it.
The beauty of ADB is it's cross platform, it works on Windows, Mac, and Linux.
The adb commands everyone should know how to use are very basic and used for file manipulation and device control.
To use ADB Google will tell you you need to download and install the most current Android SDK. If you want to write apps for Android, this is true, but for most people there's no need to do this.
You can get everything you need from one of the one clicks.
You need adb and fastboot for your platform.
Download them and put them in a directory of your choice, on my Mac they live in /Android.
I've dug them up and attached adb and fastboot for all platforms. Just unzip them and put the ones for your Operating System somewhere easy to get to.
if you're on Windows you'll need drivers. The best way to get the driver is to download HTC Sync from here http://dl4.htc.com/managed-assets/support/software/htc-sync/htc_sync_setup_3.2.20.exe and install it. After it is installed make sure it isn't running.
I'm now going to go through a few simple adb command and what they're for.
To use ADB or Fastboot your phone has to be in USB Debugging mode Set this in Settings/Developer Options on the phone.
Open a Command prompt
Navigate to the location you put the adb and fastboot commands
1) adb reboot
this command does exactly what it says. If you type it without any modifiers your phone will reboot. You can also reboot recovery or reboot bootloader.
2) adb push
Adb push is the command for putting a file on your device.
The format to use the command is adb push /filelocation/filename /destination the destination is usually /sdcard
3) adb pull
this command is how you get a file off of your phone
adb pull /file location the file will be downloaded to the location of your adb executable
4) Sometimes to help you troubleshoot a problem you may be asked to provide a logcat to someone. What this means is a log of the what is happening on the device. Getting one is easy
adb logcat > logcat.txt
this will create a logcat file and save it to the directory on your computer that you're running the adb commands from. To stop the logcat just use ctrl-c
Now on to fastboot
fastboot is a special mode on Android phones that allow system level partitions to be written or commands executed.
fastboot only works if your phone is in bootloader mode.
Once in bootloader mode
open a command prompt and navigate to where you installed the fastboot executable
You need fastboot to unlock your bootloader
fastboot flash unlocktoken Unlock_code.bin
and to relock it:
fastboot oem lock
you can also use fastboot to flash recoveries
fastboot flash recovery recovery.img use the filename of the recovery you downloaded.
If you've installed the 2.20 firmware from AT&T and you have root, you'll need to flash the kernel for any new rom separately using fast boot.
unzip the rom you've downloaded and locate the boot.img file and put it in the same directory as your fastboot and dab commands
reboot to bootloader then flash the kernel using the command fastboot flash boot boot.img. after hat you can boot into recovery right from the bootloader and install your rom.
These commands are just a few very basic ones.
There's no reason to be afraid of the command line or these tools.
I hope this quick and dirty tutorial helps someone.
If there's something else that can be explained here, feel free to add it to the thread and I'll add it to the OP.
you're right. nobody should be afraid of adb/fastboot commands or understanding WHY they are useful.
i would as far to say that if you dont understand basic adb/fastboot commands, then you have no business modding your phone....
You gotta add that they need to open a command line from the directory that has adb in it and type the commands from there.
_MetalHead_ said:
You gotta add that they need to open a command line from the directory that has adb in it and type the commands from there.
Click to expand...
Click to collapse
Oh yeah, duh
gunnyman said:
Oh yeah, duh
Click to expand...
Click to collapse
You're slackin'
I would go so far to say that this lack of comfort with adb/fastboot is the single largest contributor to the issues people have had in rooting and unlocking their HOXs over the last two months. Thanks for taking the time to put this together. Should help quite a few people unsure of adb/fastboot in general.
Another adb usage that may be helpful to add to this list is adb pull of user apps before updating ROM and then pushing them back. I have often seen people unsure of the best way to restore apps after a ROM upgrade. For me TiB works great, but you need to know what to restore via TiB and what to configure again manually. I think Scott posted the general steps in one of his CleanROM threads, but adding it to this list would be good too.
Just realized it's exactly two months since I received my pre-ordered HOX . No bricks, a superb HOX that I haven't had to warranty replace for any reason so far, and then comes along Scott with his fantastic CleanROM series. What a fun-filled ride it has been so far
Add adb logcat as well please, not enough people know how to use it
nice bro! this will come in handy for those that need it. i was there once! we all were. but good job man!
rohan32 said:
Add adb logcat as well please, not enough people know how to use it
Click to expand...
Click to collapse
Good call. Tomorrow I'll update it.
Done. Keep the suggestions coming. I know enough to get someone started, but I'm no developer.
I like this. Information that won't get old and everyone needs at one point or another. Nice call gunny.
Stickify!
this is great! excellent idea gunny
Oh yeah, stickied! :highfive: Too bad noobs still won't read it lol. They never read anything :silly:
_MetalHead_ said:
Oh yeah, stickied! :highfive: Too bad noobs still won't read it lol. They never read anything :silly:
Click to expand...
Click to collapse
Yeah but now we can be snarky and say "didn't you read the effing sticky???"
What about common connection issues?
Im facing one now
Funny you should say that. Your post made me realize it was missing.
So I'm getting a replacement One X from AT&T on July 19th and need to send my current phone back. I unlocked the bootloader and flashed ROM's on my current phone, so I should just follow this guide to return my phone back to stock before shipping it out to AT&T, correct?
Sent from my HTC One X using Tapatalk 2
acles003 said:
So I'm getting a replacement One X from AT&T on July 19th and need to send my current phone back. I unlocked the bootloader and flashed ROM's on my current phone, so I should just follow this guide to return my phone back to stock before shipping it out to AT&T, correct?
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
lock bootloader install RUU
done
Simple and awesome thread. Should help a lot of people.
This really helped me out before I became a member, thanks
hi guys, i'm trying to install the clockwork touch 5.8.0.2 crespo on my Nexus S (GSM), i have create the folder in C: with in the file, i have installed the driver of my phone, but when i open the prompt for write fastboot flash recovery recovery-clockwork-touch-5.8.0.2-crespo.img, he tells me "fastboot is not recognized as internal or external command, executable programm or file batch.", what can i do??
i also want to install this after: http://forum.xda-developers.com/showthread.php?t=1764119, someone can help me also for this??
DavideDroid said:
hi guys, i'm trying to install the clockwork touch 5.8.0.2 crespo on my Nexus S (GSM), i have create the folder in C: with in the file, i have installed the driver of my phone, but when i open the prompt for write fastboot flash recovery recovery-clockwork-touch-5.8.0.2-crespo.img, he tells me "fastboot is not recognized as internal or external command, executable programm or file batch.", what can i do??
i also want to install this after: http://forum.xda-developers.com/showthread.php?t=1764119, someone can help me also for this??
Click to expand...
Click to collapse
You need to have AndroidSDK installed or atleast have fastboot executable.
Once you have that, you can either set the path in environment variables or just go to that path using command line and use the fastboot command.
You should follow this instruction, it's very helpful.
http://nexusshacks.com/nexus-s-root/how-to-root-nexus-s-or-nexus-s-4g-on-ics-or-gingerbread/
superatmos said:
You need to have AndroidSDK installed or atleast have fastboot executable.
Once you have that, you can either set the path in environment variables or just go to that path using command line and use the fastboot command.
Click to expand...
Click to collapse
I already have the SDK; the site from which i was following the tutorial have told me i miss the fastboot.exe, can you tell me where I can find it??
rubenflush said:
You should follow this instruction, it's very helpful. (i can't quote the url)
Click to expand...
Click to collapse
But that is for the 4G version, is the same thing?
I just rooted my first Android device the day before yesterday. One problem I ran into is that the Android SDK now installs to "C:\Users\USER\AppData\Local\Android\android-sdk" instead of "C:\android-sdk" like most instructions give.
These are the instructions I followed to root my phone: wiki.cyanogenmod.com/wiki/Nexus_S:_Full_Update_Guide (Sorry for the lack of a link. I just found out I'm not able to post links because I'm new )
They helped me out a lot but it took a lot of time and concentration to get it done. Just keep in mind where Android SDK installs and change the paths to the new path when you need to.
DeadBra1ns said:
I just rooted my first Android device the day before yesterday. One problem I ran into is that the Android SDK now installs to "C:\Users\USER\AppData\Local\Android\android-sdk" instead of "C:\android-sdk" like most instructions give.
These are the instructions I followed to root my phone: wiki.cyanogenmod.com/wiki/Nexus_S:_Full_Update_Guide (Sorry for the lack of a link. I just found out I'm not able to post links because I'm new )
They helped me out a lot but it took a lot of time and concentration to get it done. Just keep in mind where Android SDK installs and change the paths to the new path when you need to.
Click to expand...
Click to collapse
Thank you very much, tomorrow i try again following this tutorial
Yes same thing, sorry for late post.
Sent from my Nexus S using xda app-developers app
I want to download the latest possible ADB/Fastboot binaries because a little bird whispered in my ear that the Asus USB ID's have been added so -i 0x0b05 isn't needed when using fastboot on the TF201.
Anyways, I do NOT use the "android-sdk" nor have I ever downloaded it. I simply used a tool called knives and forks which put the binaries in system32/syswow64 and then somehow symlinked them to always respond when typing "adb" in CMD regardless of where i start the CMD. I don't need to cd to an android-sdk folder (I don't even have one, derp)
So how can I update to the latest binaries WITHOUT downloading the sdk?
removed
shabbypenguin said:
while not the most ideal answer, i work on a lot of low end devices and in an effort to keep it simple for em i bundle up the binaries needed for most devices. normally i have adb for all 3 platforms and fastboot for all three. ive yet to update the mac and linux binaries but my zip does have the latest windows adb/fastboot
www.Shabbypenguin.com/OUDstuff/Tools/ADB-Tools.zip
Click to expand...
Click to collapse
Much obliged!
Thank you! You just saved me from a 2-3hr download tethered to my phone!
shabbypenguin said:
while not the most ideal answer, i work on a lot of low end devices and in an effort to keep it simple for em i bundle up the binaries needed for most devices. normally i have adb for all 3 platforms and fastboot for all three. ive yet to update the mac and linux binaries but my zip does have the latest windows adb/fastboot
www.Shabbypenguin.com/OUDstuff/Tools/ADB-Tools.zip
Click to expand...
Click to collapse
I've been frustrated with error: device offline.
My SDK manager is still downloading stuff & I found this thread.
Latest adb helps!!!
Thank you so much.
dsymbol said:
I've been frustrated with error: device offline.
My SDK manager is still downloading stuff & I found this thread.
Latest adb helps!!!
Thank you so much.
Click to expand...
Click to collapse
that zip is old, instead http://androidforums.com/faqs/443072-adb-guide-updated-2013-05-21-a.html#post5389081
use teh attached file there. chances are the device offline is due to outdated adb and a 4.2 device.
shabbypenguin said:
that zip is old, instead http://androidforums.com/faqs/443072-adb-guide-updated-2013-05-21-a.html#post5389081
use teh attached file there. chances are the device offline is due to outdated adb and a 4.2 device.
Click to expand...
Click to collapse
you're absolutely correct.
i've updated to 4.3 & run into device offline problem.
Your adb 1.0.31 helps. in less than 5 mins, while i've been sitting here for 3 hours waiting for the SDK manager to update files.
Thanks for this!