WARNING: Rooting (and related processes) can be dangerous if you do not understand the concepts, risks and procedures involved.
Although we are often at hand to help, you will receive much better help if you have read the FAQ's and guides several times before undertaking the task of rooting. Not only will you understand the possible causes and fixes for issues you encounter, it will also help you to give US the information we need to help YOU!
What is rooting?
Rooting is the process of gaining root access to Android. Android is based on the Linux operating system. Root access is superuser permissions (SU), much like an Administrator in Windows.
OK Great, but what does it get me?
Well, it gives you more control over your phone essentially. You can run full backup of your entire phone, control how the CPU is used by Android, save internal memory to name but a few.
See this list by Usta, made for your convenience:
Fix the low internal storage problem
Remove carrier/manufacturer bloatware
To get the latest OS updates
Ability to make a true backup of your phone as a complete image (nandorid backup).
Ability to use some great applications that are only available for rooted phones. A good example is Titanium Backup.
The fun to try new ROMs that can completely change the look and feel of your phone. For example, ASOP ROMs make my Desire look like a Google Nexus phone, while MIUI ROMs make it look like an iphone.
Added features and functionality - some ROMs can enable HDMI output, enable ad-hoc WiFi connectivity, enable 720p video recording, enable WiFi tethering, be very battery efficient with adjusted kernels, ability to overclock/underclock your phone, etc.
Anything else?
If you use the unrEVOked or revolutionary methods, they also flash (installs onto flash memory) a custom recovery (Clockworkmod recovery).
What is recovery?
When you turn on your phone, the phone's bootloader loads 1 of 2 things. Android or recovery. When you flash a custom recovery using unrEVOked, revolutionary or fastboot commands the HTC recovery is replaced.
The 2 main recoveries that we used to recommend here are clockwork mod 2.5.0.7 and AmonRA 2.0.1. Now though, 4ext is our favoured recovery
Note* there are other versions of both amonra and cwm but we strongly discourage any other version than the above.
Whats it for?
Booting into the custom recovery gives you the ability to flash custom roms, take backups, clear data etc. UnrEVOked flashes this AND roots your existing Android OS. You do not have to use a custom ROM to be rooted using this method.
How do I get to recovery?
From off, Hold Volume down and press Power. This boots you to the Bootloader. There is a recovery option here. You need to use volume up and down to navigate the menu, then power to select the recovery option. This then loads your custom recovery. Now you can use the track ball to navigate the recovery menu
UnrEVOked only works for 2.2.1 or lower however. Any 2.2.2 or 2.3.3 GSM ROM must use revolutionary. Also, any hboot 1.02 or higher needs to use revolutionary too. Please see Mattb81's Guide:
Revolutionary is a joint project between Alpharev (responsible for S-off on 2.2 devices) and unrEVOked.
Revolutionary doesn't actually root the phone in itself. It S-off's the device, which then allows you to fastboot flash a custom recovery - see the adb and fastboot FAQ here (Skip the adb section).
Once you have flashed a recovery, you can either:
1) Flash a zip to root your current ROM (if you do not plan on flashign a custom one) or
2) Jump straight to flashing a custom ROM (As root is not needed to flash a ROM, only custom recovery)
How will I know if it has worked?
UnrEVOked creates an application called "superuser" within your App Drawer. This is the application that manages requests from applications for Root/SU/Superuser privileges.
If using Revolutionary, your Hboot version will now start with a 6.x
1) Your firmware IS too new. Check your version. The ARA 2.32.415.x is now rootable. Ensure you are using the 3.32 version of Unrevoked if you are on an ARA build - 3.32
2) If you forced all apps to SD card, this is impairing the installation of the superuser app. Go back through the guide and substitute "pm setInstallLocation 2" foir "pm setInstallLocation 0" and try it again
Other UnrEVOked errors...
There are other errors involving "failed to unlock NAND" or containing "MISC" or "backup CID". Although there are lengthy ways to overcome these which often will not work, it may just be as well to downgrade using teppic74's downgrade tool (GSM ONLY), to 2.1 and try with an older unrEVOked version.
Another error received is "Internal error: installing package failed." This can sometimes be down to there not being enough space on the device in "internal storage". You can delete some apps or even wipe as a possible work around.
It is also worth noting that hboot 1.02 and over are not supported by Unrevoked. You may get "Waiting for root" errors with unrevoked.
Is rooting risky?
Flashing anything is never without risk, however providing you don't disconnect cables or power down devices whilst the process is taking place, it is fairly safe. Flashing Radio's however, is not.
What's not safe about flashing radios / what are Radios?
Radio is the software required to run the physical radio which sends / receives voice and data from your phone. Its like the driver for the part of the phone that makes it a phone.
Flashing Radio's is risky because it can result in permanent brick (dead and unrepairable phone).
CDMA phones do not have flashable radios. If you see a radio released, its for GSM and flashing it can perm-brick your phone
Do I need to flash a radio though?
Not really, You already have one. The radio is in a different part of the memory of the phone, so flashing a ROM will not over write your radio, unless the ROM includes a radio which is quite rare.
This said, certain functionality of a ROM may not work if the recommended radio is not present. I would suggest reading up on the ROM you are thinking of installing and checking your radio version from the About Phone menu. For example, 2.2's camera won't function with a pre 2.2 radio
Some older guides refer to specific Hboot versions. Where as the HBoot version itself does not matter using unrevoked, before rooting -check if the Hboot states "BRAVO PVT4 SHIP S-ON", where PVT4 is the bit we are concerned about.
If you do have PVT4, you then need to check if your erase size is 40,000.
To check erase size, you can simply download "terminal Emulator" from the market and type:
Code:
cat /proc/mtd
(And press enter) - This should work on non-rooted devices
If it is NOT 40,000 - ignore the rest of this section.
If it IS 40,000 you need to use the latest Amon-RA recovery image (rather than the standard supplied) with unrevoked when rooting. Use Unrevoked 3.21 if you can.
When using unrEVOked, whilst it is on the "Waiting for device" screen, go to FILE > Custom recovery - Choose the Amon-RA image you downloaded.
If you want Clockworkmod recovery, once rooted and flashed Amon RA, if you run the latest Alpharev S-OFF, you can flash a modified clockworkmod recovery using that
AlphaRev 1.8 (Sometimes S-OFF has been known to fail on some (AOSP) roms. If this happens, take a backup and flash a rooted stock sense rom.)
***Caution, I have had a report that one member was struggling to partition his SD card using Gparted whilst this modified CWM recovery was installed. Reflashing the Amon-RA resolved this.
If you have already rooted with unrevoked and have no desire to S-Off, re-run unrevoked and select amon RA as recovery. Make sure once booted into android though, you clear data on the superuser app - Settings>applications>manage Applications
If you are on Android 2.3.3 RUU or hboot 1.02 or over, You HAVE to S-off to do what you previously could do before simply by rooting with unrEVOked.
More information about Hboots in I need to send my phone back, should I return it to Stock with an RUU?section.
I have an SLCD, should I be worried?
When the SLCD was new, things like RUUs, recoveries and ROMs didn't support it. This would cause the screen to not work. This should be rare now its been around a while. Just be careful not to flash anything old. Start current and don't go backwards.
The below statement is not necessarily true anymore. The Android 2.3.3 RUU from htcdev.com debrands (works on branded handsets without goldcards) and is still aceppted for warranty by HTC. However, this RUU doesn't work on all branded phones (theres a list somewhere of which work). In the case that your phone is not supported, see the below answer:
For rooting itself, no. However, if your phone is branded, you should definitely make one.
Why should I make a Goldcard?
Branded phones need a gold card to de-brand. The goldcard Hides the true identity (branding) of the phone, allowing non-branded official roms to be installed.
From time to time, flashing a ROM goes wrong. You can't get into recovery, you have no option but to download an official RUU (Rom upgrade utility) and restore it to stock. Some branded RUU's simply do not exist, so you need a gold card to install a generic one.
Please note by many it was believed the goldcard must be made on your working phone and would only work on that phone. We now know this to be inaccurate. The goldcard tool uses the CID from the SD card (not phone) so the goldcard should be universal across android devices. The Image the goldcard creates however, can only be used on the card it was created for.
If your phone works with the 2.3.3 releas eon htcdev.com, it doesn't matter. Just use that, otherwise:
Crying and pleading to your gods may well be your only chance now. Actually as the gold card does not need the phones cid to create, just the sd, you can make using a card reader. This does ruleout using goldcard helper from the market though, incase goldcard tool can't get the cid
***Be aware, if you are S-off with an R2 hboot (example: CM7 r2), this has Write protection on it. This means that an RUU will NOT overwrite it. The hboot will remain and may effectively void warranty. It ia also worth noting that if you don't want to overwrite the hboot (remainign s-off) you must ensure that the /system size of the hboot will fit the RUU in it. CM7 is 145MB, which is much smaller than the stock 250 MB, so a sense RUU's system will NOT fit.
You need to fastboot flash the downgrade.img
If you RUU whilst on such a hboot that is too small, you will get an error stating that system [fail]. If you boot into recovery, hboot or fast boot, you will see a screen with 4x ! (1x! in each corner).
Fear not, Fastboot still works. Boto into fastboot and you will see this screen, connect usb and fastboot flash the downgrade.img then run the RUU again
How do I know which RUU is right for me?
Each RUU in its file name has the software build version in the format of x.xx.xxx.x (eg 2.29.405.5). All android 2.1 eclair versions start with a 1. All Froyo start with a 2.
You can get your phone's current version from settings>about phone as long as you have not flashed a custom rom. You should make a note of this before rooting.
Does rooting void my warranty?
Tough one, there is some debate on that. If you return it to a generic Stock if it was originally branded, provided it is official, you may be able to get away with it. HTC will know if it is the right ROM or not, but they may still fix it.
Whats the best Custom ROM to flash?
That is too subjective a question to ask. Narrow down what you want. Do you want something familiar but with more options? If so get a Sense ROM. Do you want something as far from familiar as possible? Get a Vanilla AOSP ROM. Narrow down that Choice, then we'll talk some more.
Whats types of custom ROM are there?
There are 3 main categories of custom ROM:
Sense - ROMs based on HTC sense roms. These ROMS give you a stock feel. Based on official or leaked HTC sources, these are guaranteed to work well. You can also get sense roms ported from other devices such as the Desire S or test builds featuring sense 3.0
AOSP - These ROMS are built from google's open source project. These ROMS are build by the development community from 100% google code. They are vanilla (pure android - no Manufacturer user interface (such as sense). These ROMS are often very fast and with the correct choice of ROM and Kernel, very stable.
Miui - Miui originated as a Chinese Development project, but many deelopers around the world have picked up this innovative rom (based on AOSP, but with an innovative User interface) and modified it. There are now many different versions of Miui ROMs available
ROM Manager looks good, should I use that?
As easy as it looks to use ROM manager, it has caused many issues for people either flashing, backing up or restoring. We recommend you don't use it. It takes away a need for knowledge of the process and makes you dependant on your SD card, which if it breaks, we will have to spend a long time helping you fix. Please learn to do the process manually.
It lists all the good roms. Be aware that you already need to be rooted. If you want to use apps2sd+, you will also need to have partitioned your card first. See the apps2sd+ FAQ in my signature.
Be aware that you may need to wipe. However, for stock / HTC sense based roms for the desire (not including ports such aas the desire HD ports), you MAY get away without doing a data wipe. AOSP (vanilla) roms will definitely need a wipe
Its always best to take a nandroid backup of your existing rom. See the Nandroid section further on in this FAQ.
Also you should backup your apps and data. Titanium Backup is a great app for this. However, I also use mybackup pro for sms and call logs, but there are alternatives out there.
If you have to wipe, this is due to an incompatibility with system settings from your old rom. See the wiping section, also further on in this FAQ.
So (based on clockworkmod recovery):
1) download you chosen ROM onto SD card
2) Do all your backups
3) Boot into recovery manually (see recovery section earlier)
4) Choose "wipe data / factory reset"
5) Choose "Install zip from SD card"
6) Once complete, choose "reboot system now"
It can take 10 minutes to boot up first time, so give it this long before taking further action. If it still has not booted, pull out the battery, but ONLY when the boot animation is on. NEVER during a flashing process.
If you can obviously see the boot animation looping, this may be due to the lack of wipe. Pull the battery and boot into recovery and perform the wipe.
Once booted, if you wiped, set up the phone with network and market access and download Titanium again and whatever data restore app you used for sms (if desired).
If you wiped, be careful which option you choose to restore. You dont want to restore system settings, so "restore missing apps with data" is a good one to choose.
Now, enjoy setting up and playing with your phone.
Do I NEED S-Off?
Well, it depends what you want to do, but for most things you do not need it.
The HTC Desire has a security flag contained within the radio's NVRAM. S-Off flashes a custom HBoot which ignores this security flag.
Note CDMA desires are s-off by default if rooting via unrevoked, providing unrevoked supports the radio version of the desire
Some custom ROMS suggest you flash a particular partition table via S-Off (HBoot with new partition layout) which will change the size of your /system, /cache and /data partition - giving more space for "internal storage".
Other advantages are being able to replace the splash screen and deleting apps whilst Android is running. For the latter, there are other, easier methods.
AlphaRev 1.8 (Sometimes S-OFF has been known to fail on some (AOSP) roms. If this happens, take a backup and flash a rooted stock sense rom.)
Get AutoKiller. This is NOT a task killer. It clears EMPTY apps from memory. These are not apps that are running in the background or doing anything. Android does itself kill these, but this application allows you to change the thresholds of memory to do this.
Get Autostarts. Each android app listens to certain events that occur on your phone. Some apps listen to events that they do not require. This app allows you to prevent some apps listening to some events. For example, I don't want photo bucket to listen for an event based on my location. I don't need it to know where I am. TuneWiki does not need to know if I have installed an application.
What else can I do?
Well with custom ROMS, you may have the choice of installing a custom Kernel, which will run the CPU at the same speed as standard (998Mhz) but using less voltage (saving battery). This is called Undervolting.
At the same time, if you have SetCPU, you can overclock a kernel (if it permits) to run at a faster speed than normal, but at the same voltage as 998Mhz. You can compromise between the two.
What is a Kernel?
It's the heart of the operating system (hence the name, like the kernel of a nut, the most important part of anything). It provides the environment for the phone's software to work, including access to the hardware. [Teppic74]
What is Nandro]id Backup?
Nandroid backup is a backup that takes an entire snapshot of your phone as it is. This can be done from clockworkmod recovery, under the backup menu. It is not referred to as Nandroid in clockworkmod.
It can be restored at any time, over any ROM and will restore your phone to be EXACTLY as it was when the backup was taken. Always take this backup before flashing a ROM.
**Note, there is a known issue whereby you can sometimes get into a bootloop after your first Nandroid backup if you rooted using unrEVOked 3.21 (or later) due to corruption of the NAND. Booting back into recovery and restoring the backup you have just taken should resolve this
What other back up options have I got?
Titanium Backup is good. It backs up your applications, their data and settings plus system settings. Unlike Nandroid, it does not back up the ROM.
Settings between ROMS can differ, so if you over write new ROM settings with older settings backed up with titanium, some functionality can be lost. If you factory reset and it fixes it, try to restore as little as possible with titanium. Factory reset is the same as a wipe. titanium backs up what is wiped.
As we are not wanting to restore data for system apps, it is best to make provision for your contacts, sms, call logs if required.
If you have google contacts, nothing is needed. I personally use sms backup+ which backsup to my gmail account. I can restore or leave. Also I can browse the SMS via gmail. Great.
So what is all this about wiping? Do I need to?
Maybe. If you go from one stock ROM to a custom ROM, or one Custom ROM to another, the settings may not be compatible. You can wipe from ClockworkMod Recovery. - Wipe data/factory reset.
If the ROM is stuck in a boot loop for more that 10 minutes, you may have to back to recovery and do a wipe of the Data partition
Tell me more about Bricking?
A bricked phone is a dead phone. You can not recover it. It is very rare a true brick has happened. If you flash a dodgy ROM (by that I mean if you have a corrupt download or make a mistake), you can 98% of teh time recover it. Maybe with a Nandroid restore, an RUU or something.
During your rooting and flashing career, you will experience plenty of things you think are a brick. They are not. You just need to calm down, research, ask questions and get help.
Flashing corrupt or incorrect radio files is the most common form of permanent / true brick. As I said before, take care.
Can I still receive OTA updates?
No. Most custom ROMS block out this feature, but if you have rooted your existing rom, you may still get the option to install OTA. PLEASE DO NOT!!! You need to disable the setting that checks for updates. OTA updates often cannot be installed, but sometimes they appear to work. However this can lead to huge issues in the future so I beg you, please do not try to install one.
Device(s): Samsung Galaxy S II, Asus Eee Transformer
Carrier: Not Provided
Thanks: 108
Thanked 18 Times in 17 Posts
Excellent guide, Dan, many thanks - AGAIN!
Currently trying to partitian my 32Gb SD card using ROM Manager. It's been 23 minutes so far and I'm still staring at a warning triangle with a little droid. Don't knwo if it makes any difference but I quick-formatted the SD card before starting, and my phone is NOT attached to the USB cable...
Device(s): HTC Desire
Current ROM: Redux 2 Test Builds (Gingerbread 2.3.5)
Carrier: Not Provided
Thanks: 90
Thanked 217 Times in 79 Posts
Quote:
Originally Posted by turbohobbit
Excellent guide, Dan, many thanks - AGAIN!
Currently trying to partitian my 32Gb SD card using ROM Manager. It's been 23 minutes so far and I'm still staring at a warning triangle with a little droid. Don't knwo if it makes any difference but I quick-formatted the SD card before starting, and my phone is NOT attached to the USB cable...
I answered in the other thread you posted this on...
Tough one, there is some debate on that. If you return it to a generic Stock if it was originally branded, provided it is official, you may be able to get away with it. HTC will know if it is the right ROM or not, but they may still fix it.
~ Has anyone any first hand experience on this?
Yup..Apparently rooting a Non-branded phone cannot void one's warranty. It's a legal loophole of HTC's warranty policy. The fineprint only excludes damages that come from physical abuse, and use of non branded hardware. HTC doesnt actually exclude flashes or softbricks from warranty. I was able to return my Desire after a softbrick
BUT, if its branded with an operator, I'm not sure. The Operator may have a seperate warranty policy which you sign. One will have to check fineprint on that.
__________________
I dont subscribe to every thread I reply to, so post in relevant official threads for a speedy response. Alternately use the official Supernova forum
Good points about the goldcard. Too many people end up unable to recover because they didn't make one, since it's not necessary just for rooting.
This bit about the kernel:
Its basically an interface that sits between the Android OS and the hardware. Almost like an interpreter.
Not really, it's the the heart of the operating system (hence the name, like the kernel of a nut, the most important part of anything). It provides the environment for the phone's software to work, including access to the hardware.
The Following User Says Thank You to teppic74 For This Useful Post:
Good points about the goldcard. Too many people end up unable to recover because they didn't make one, since it's not necessary just for rooting.
This bit about the kernel:
Its basically an interface that sits between the Android OS and the hardware. Almost like an interpreter.
Not really, it's the the heart of the operating system (hence the name, like the kernel of a nut, the most important part of anything). It provides the environment for the phone's software to work, including access to the hardware.
I'll edit that in. Thank you. I'll use that pretty much verbatim...
Obviously I am a newbie here and this q might seem very naive
My phone specs:
Android Version 2.2
Baseband Version 32.49.00.32U_5.11.05.27
Kernel Version 2.6.32.15-gd96f2c0
htc-kernel@and18-2 #1
Build Number 2.32.415.3 CL283905 release-keys
Software Number 2.32.415.3
Browser Version WebKit 3.1
BRAVO PVT3 SHIP S-ON
HBOOT 0.93.0001
MICROP -051d
I guess it is the BRAVO ARA one, meaning the arabic version..
I have now tried over five times independantely using unrevoked on
Win 7 64
Win XP
Linux using Slax LiveCD
ALL NO ROOT!!!!
I ran into a few remaks adout that rom that it is the arabic rom, the one that unrevoked still can't root (2.32.415.3) same as mine. been searching all over for a way to root this rom
Device(s): HTC Desire (depreciated)
Blue Galaxy s3 (international)
Carrier: Not Provided
Thanks: 114
Thanked 1,016 Times in 838 Posts
Quote:
Originally Posted by danfrance
Ahhh good stuff. This cause voda is the only build version higher than ARA?
yes thats right
the exploit was patched in the ARA build but not the voda which is higher
youll find this is likely because of it being arabic that its patched, they will probably ban root out there due to information theft concerns and stuff. look what they were like about blackberries.
goes to show you though that htc's root exploit is intentionally left in there on other roms :P
Edit:
And I checked Aurax for you. It doesnt have Arabic support.
By the way, It wouldnt be hard for a dev to create a custom rooted Sense Rom for your ARA version, if there are enough requests. Unfortunately havent seen many requests for it on XDA.
But it takes some effort to create a custom Rom.
Last edited by droidzone; January 1st, 2011 at 01:52 AM.
The Following User Says Thank You to droidzone For This Useful Post:
Device(s): HTC Desire (depreciated)
Blue Galaxy s3 (international)
Carrier: Not Provided
Thanks: 114
Thanked 1,016 Times in 838 Posts
there is a rooted arabic rom on xda but it doesnt get updated often. http://www.ce4arab.com/vb7/showthread.php?t=271317
if you want to root you have to flash the voda build
its a bit of a pain for you to return back to stock ARA as your bootloader version will be too high so it will not let you flash one lower (ARA is 32) via RUU or PB99img.zip
At this point you would need to use teppics downgrade utility (found on XDA Devs) to downgrade it to a slcd compatible 2.1 build and then you can RUU it back to the Arabic rom
Last edited by Rastaman-FB; January 1st, 2011 at 09:28 AM.
there is a rooted arabic rom on xda but it doesnt get updated often. [Ñæã .. W1002 ] ááÏíÒÇíÑ .. 2.2 ÇáÚÑÈí ÇáÑÓãí .. ãÍÏË 24/12/2010 - ÇáßãÈíæÊÑ ÇáßÝí
if you want to root you have to flash the voda build
its a bit of a pain for you to return back to stock ARA as your bootloader version will be too high so it will not let you flash one lower (ARA is 32) via RUU or PB99img.zip
At this point you would need to use teppics downgrade utility (found on XDA Devs) to downgrade it to a slcd compatible 2.1 build and then you can RUU it back to the Arabic rom
Actually I didnt elaborate on the rooting process b/c I'd spelled out the steps for him in the XDA thread.
I think there's an additional element of uncertainty here. We know that Teppic's downgrade tool is based on the rageagainstthecage vulnerability patch, which seems to be working ok upto 2.29. However, noone seems to have tested if rac works on this particular version. Since HTC is well aware of the patch, they could have patched it too, in which case no current downgrade scripts may work.
Device(s): HTC Desire (depreciated)
Blue Galaxy s3 (international)
Carrier: Not Provided
Thanks: 114
Thanked 1,016 Times in 838 Posts
Quote:
Originally Posted by droidzone
Actually I didnt elaborate on the rooting process b/c I'd spelled out the steps for him in the XDA thread.
I think there's an additional element of uncertainty here. We know that Teppic's downgrade tool is based on the rageagainstthecage vulnerability patch, which seems to be working ok upto 2.29. However, noone seems to have tested if rac works on this particular version. Since HTC is well aware of the patch, they could have patched it too, in which case no current downgrade scripts may work.
rageaggainstthecage has to work as its the method used to backdoor by unrevoked and this why you can use voda to root and not the arabic. its patched in the arabic and not the voda
anyone on voda want to try visionary? thats rageagainstthecage temproot
also you said (just run the ruu again to go back) you cant do that when going from a higher version
Last edited by Rastaman-FB; January 1st, 2011 at 09:49 AM.
rageaggainstthecage has to work as its the method used to backdoor by unrevoked and this why you can use voda to root and not the arabic. its patched in the arabic and not the voda
anyone on voda want to try visionary? thats rageagainstthecage temproot
Thanks, didnt know that Unrevoked was based on that.
Device(s): HTC Desire (depreciated)
Blue Galaxy s3 (international)
Carrier: Not Provided
Thanks: 114
Thanked 1,016 Times in 838 Posts
Quote:
Originally Posted by droidzone
But then, why hasnt Unrevoked Forever still not been released for Desire?
what do you mean?
whats the difference between unrevoked 3.22 and unrevoked forever?
EDIt:
i see what you mean, the way desire is the security flags are not stored within the radio.
cdma gets s-off like forever but the gsm stack is more complicated and as such needs a dedicated tool (aka alpharev)
Last edited by Rastaman-FB; January 1st, 2011 at 10:18 AM.
what do you mean?
whats the difference between unrevoked 3.22 and unrevoked forever?
EDIt:
i see what you mean, the way desire is the security flags are not stored within the radio.
cdma gets s-off like forever but the gsm stack is more complicated and as such needs a dedicated tool (aka alpharev)
Yup. Forever (=S-OFF) still not launched for GSM Desire.
i dont think it ever will hence why they shared their nand unlock method to the alpharev team
they would not have done this if they had intention of launching forever for gsm desire themselves
alpharev is better imo anyway as it supports more fastboot commands that CDMA desire doesnt
Well, I'd have loved if Alpharev would include the rooting process too, a one step Root+S-OFF would be great for a LiveCD program. A lot of users get probs with Win drivers for Unrevoked.
I didnt know that Unrevoked gave Alpharev the method of S-OFF. Good to know.
Device(s): HTC Desire (depreciated)
Blue Galaxy s3 (international)
Carrier: Not Provided
Thanks: 114
Thanked 1,016 Times in 838 Posts
Quote:
Originally Posted by droidzone
Well, I'd have loved if Alpharev would include the rooting process too, a one step Root+S-OFF would be great for a LiveCD program. A lot of users get probs with Win drivers for Unrevoked.
I didnt know that Unrevoked gave Alpharev the method of S-OFF. Good to know.
i see where you are coming from.
Im in two minds about this really as the alpharev solution requires a flash of a device critical partition. cdma unrevoked doesnt flash hboot it just changed the flag in the radio stack.
too many things in one process to go wrong if it doesnt mantain a correct root or doesnt boot properly when it instigates the s-off proceedure so it fails at a critical point and kills the device
unrevoked changes quite a few things on a base rom, if you remember it takes about 7mins for the whole process and alpharev takes about the same but needing multiple reboots as they go through the process
so 15 - 20 mins of arse clenching freakout panic. the failure rate would be high just on impatient people pulling the device mid process if it gets hung on a job which happens quite often
Im in two minds about this really as the alpharev solution requires a flash of a device critical partition. cdma unrevoked doesnt flash hboot it just changed the flag in the radio stack.
too many things in one process to go wrong if it doesnt mantain a correct root or doesnt boot properly when it instigates the s-off proceedure so it fails at a critical point and kills the device
unrevoked changes quite a few things on a base rom, if you remember it takes about 7mins for the whole process and alpharev takes about the same but needing multiple reboots as they go through the process
so 15 - 20 mins of arse clenching freakout panic. the failure rate would be high just on impatient people pulling the device mid process if it gets hung on a job which happens quite often
Valid point that you've got there. ;-) I remember biting my impulse to pull the cable and see if it had hung. :-)
I have a French HTC Desire - does that affect any of the rooting steps?
Also I must say the new part in your FAQ about HBOOT isn't very clear... I've done a bit of research and can't even seem to figure out how to check my phone's HBOOT. Maybe i've just missed the obvious though
[FAQ]ROOTING (Updated 7th April 2012)
but i now have the Superuser Ninja myself.
