Hi all,
I have a rooted desire with a rooted stock 2.3 rom installed (http://forum.xda-developers.com/showthread.php?t=1151765)
I have tried to install the alpharev hboot using both the livecd and the usb method, but I recieve a error "unary operator expected" on stage 3. the phone is fine after the process fails and still boots normally.
Is there another way of flashing alphrev? maybe using adb on fastboot?
Cheers
UPDATE: I think i may know why its not working http://forum.xda-developers.com/showthread.php?t=1075113&highlight=alpharev
tru using revolutionary, a lot quicker and easier
On the revolutionary website I complete the required details. e.g. phone model, serial etc... but the drop down does not allow me select my hboot version of 0.80.0000, it only has 0.93.0001? any idea?
Is there a way of flashing alpharev using adb or cwm instead?
Ive tried serveral PC's now and all of them fail with the same error.
I've been through the xda forums and google and simply cant find a way of applying s-off.
The error I get is Unary operator expected on stage 3 of the alpha rev usb stick or livecd
update your phone with a newer RUU (NOT THE GINGERBREAD ONE!!!!!) and then S-OFF
Related
http://forum.xda-developers.com/showthread.php?t=776696&page=29 following this thread i installed the HBoot drivers and then i started unrEVOked 3.14.
It booted into console, then i rebooted again but after then the software on my PC gave me error message "unable to push recovery image to flash" .. ..
- I do change the USB mode
- I have HBoot drivers installed
- I have HTC Sync installed
- I am on Windows 7
- I am using HTC Desire Froyo
Remove HTC Sync.
You need it's drivers, but if you leave it installed it might get in the way.
Uninstalling will not remove the required drivers.
I think...
Thread reported.
Don't post your questions in the development
section!
In answer to your question, follow this guide: http://rootmydroid.co.uk/category/guides/general/
Thank You,
NoobNazi
I followed the guide already and i posted the question after following the guide. it stucks and give me the error that i posted abov.e
i get the same error, so this is a valid topic.
there is Nothing that gives us any information about what else to try, bar sitting and waiting for the rEVOked client to be updated.
The latest version of unrEVOked is up. I tried to root my Desire through it. It rebooted my device couple of times (with previous versions I used to get error at 1st boot).
Now, I am getting this error Backup CID is missing.
Can someone guide?
latest revoked worked fine for me
3.21 sorted all the issues i was having.
Yep, the old unrEVOked (3.14) doesn't support FroYo...get 3.21 and you'll be fine
42turkeys said:
Thread reported.
Don't post your questions in the development
section!
In answer to your question, follow this guide: http://rootmydroid.co.uk/category/guides/general/
Thank You,
NoobNazi
Click to expand...
Click to collapse
Use that guide. If it doesn't work ( as for me ) use Linux with a Ubuntu live CD. Worked first time for.me.
Windows is crap. Too many things to go wrong that wont be obvious making you sound like a idiot.
Direct link. http://rootmydroid.co.uk/guides/gen...esire-wildfire-evo-incredible-with-unrevoked/
Worked first time in W7 x64 Ultimate when I did it with the RC
I have the same windows and latest unrEVOked but it didn't work. It gave me error Backup CID missing
Hmmm,
I have just tried to root my Desire using unrevoked 3 and it seems to go throught the motions but ends on an "internal error couldn't find misc" error message......
I am running a stock O2 Froyo Desire with HBoot .93.......Any ideas?
Try connecting your android in USB storage mode and debugging mode.
My first try gave me the same "internal error: couldn't find misc".
But with the above settings I was able to root my HTC Desire. Thanks unrevoked!
Hi,
A noobie questions.
I have Froyo 2.2 with HBoot .92 and i want to use unrEVOked tool, but before that my sd card has to be empty, or have to format it?
And after i use unrEVOked, i have to flash any custom rom?
Thanx
@ iamtotal, I already have it with those settings... Are you running Froyo?
@ pekas, no you do not have to use a blank sdcard.
Sent from my HTC Desire using XDA App
iamtotal said:
Try connecting your android in USB storage mode and debugging mode.
My first try gave me the same "internal error: couldn't find misc".
But with the above settings I was able to root my HTC Desire. Thanks unrevoked!
Click to expand...
Click to collapse
I tried to do it in USB mode and then Charging mode. In both cases i got the error Validation error: Backup CID missing ...
Please help....i have tried many times on unbranded desire 2.2 ota, 2.10.405.2,hboot 0.93....and STILL get could'nt find misc...tried both on mac and pc....really need help
Alsajosora said:
Hmmm,
I have just tried to root my Desire using unrevoked 3 and it seems to go throught the motions but ends on an "internal error couldn't find misc" error message......
I am running a stock O2 Froyo Desire with HBoot .93.......Any ideas?
Click to expand...
Click to collapse
Ok, so I have a Win7 x64 box, and have all the corect drivers loaded for my phone.
If I run unrEVOked I get the above error message......So my next step was to run in Virtual XP mode to see if maybe it was a X64 issue....Still the same error.....
Last night I reset my phone to factory defaults and re-ran unrEVOked.....No joy....So after trawling through more forum posts I came across how to run unrEVOked from an Ubuntu live cd.....So I downloaded and burnt off the live cd, ran the script as specified (really neat and easy to use BTW) to get the latest version of unrEVOked and run it.......Guess what......Still the SAME error message......Methinks maybe something screwy with the O2 version of Froyo?
Anyone else had the same issue? Are running an O2 rom?
I am stuck with the same error since the beginning. No success, with all the possible tries. I am not sure what version my FroYo is .. O2 or something but its EU region specific.
Bottom line is .. I can't root my Desire .. :|
HI guys,so i have this issue:
I've updated desire with RUU to 2.29.405.5 with 32.49.00.32U_ radio 5.11.05.27 HBOOT 0.93 sometimes ago, after having rooted,in order to restore phone.
Now I want to root it again but I can't!! Unrevoked3.2 goes well untill it reboots and then says 'connection to phone lost.try again'. I've also tryed downgrade method 2.3 to restore HBOOT back to 0.80: Windows prompt says cannot detect the device.
I properly installed HTC sync drivers,modified HBOOT driver from Unrevoked,ran unrvk 3.2 as administration in win 7 but no results.
I tried using a RUU old that my current firmware but it says cannot install it.
Cables and usb port works fine (HTC sync goes fine).
So guys I don't know what to do ,if you have many suggestions I'll appreciate it a lot.
Thank you in advance.
I had issues with unrevoked when I rooted my CDMA Desire as well, turns out that the most recent unrevoked didn't like to work with the Desire for some reason. Using unrevoked 3.21 did the trick though! Rooted through without a problem and was then able to upgrade to the most recent recovery from ROMManager.
Ok
U run unrevoked latest download via there site
And i get to the point were its in hboot and does that thing then reboots.
Ok when it reboots and all,
Unrevoked says Running Root.. .. ..
and then it comes with a error:
Internal Error: Failed to unlock NAND flash?
PLEASE HELP how do i get pass this or whats going on.
and also when i plug in phone should it be on usb charge? ive tried this and ive tried disk one to and same error.
please help..
when in hboot its version 1.06.0000 also if that helps any?
im on rom 2.2 stock bout it like last week
hi, as described, you are using alpharev mod and not unrevoked
unrevoked to root the phone and alpha rev to S-OFF the phone (remove the secure nand)
seems that your hboot is version 1.06.0000 => is it a desire cdma???
coz not yet supported by alpharev maybe in a while => actually no solution to S-OFF your phone as far as I know (may be i'm wrong !)
are you already rooted??? coz you don't need to S-OFF for flashing custom rom
hope this help
Hboot 1.06.0000 is normally cdma I think, and according to this thread:
http://forum.xda-developers.com/showthread.php?t=776696
3.2.1 should root and s-off it?
So I think running it again would be the first thing to try.
Enable "USB debugging" first though, not "charge only"..!
Hi all,
I'm trying to root a HTC Desire, but having no succes with Unrevoked nor Revolutionary.
This phone has the following configuration:
HBOOT 0.93.0001
Radio 32.49.00.32U_5.11.05.27
Stock HTC ROM, version 2.29.405.5
Phone is plugged in as USB drive and with USB debugging enabled. I'm running Unrevoked and Revolutionary on Linux.
Unrevoked
Using Unrevoked 3.32, the process hangs on "Pushing Flasher...". Nothing happens for a long time, application has to be terminated. (When the phone is unplugged, Unrevoked will say "Failed pushing flasher".)
Update: also tried with Unrevoked 3.21 (some forum posts/blogs suggest this version for HTC Desire), but has the same effect.
Revolutionary
When the above turned out not to work after trying several times, I decided to try Revolutionary after reading some posts about it on this forum. I'm using version 0.4pre4. Revolutionary starts doing its work, then tries to reboot the device, but the phone doesn't go past the FASTBOOT screen (showing options BOOTLOADER, REBOOT, REBOOT BOOTLOADER and POWER DOWN). The phone's hardware buttons are locked. After the second try (see below), the buttons are operational, but Revolutionary reports "failed".
=============================================
| Revolutionary S-OFF & Recovery Tool 0.4pre4 |
=============================================
Brought to you by AlphaRev & unrEVOked.
Waiting for device...
Found your device: HTC Desire (bravo-0.93.0001, Android: 2.2, ROM version: 2.29.405.5)
This is a beta release and requires a beta release key.
Please visit: revolutionary.io for more information.
Enter beta key [...]
Beta key accepted - thank you for participating!
Zerging Root... this might take a minute or so.. Root acquired!
Sending in Caroline...
Cleaning up...
Rebooting to fastboot...
When life gives you lemons, don't make lemonade. Make life take the lemons back!
Waiting for fastboot...
Rebooting to fastboot (Once moar...)
FAILED - Go have some lemonade!
Click to expand...
Click to collapse
The strange thing is that I have rooted another HTC Desire phone with the exact same specifications some time ago using the exact same copy of Unrevoked3 with no problems.
Does anyone have an idea what is going wrong and what I can do to solve it?
Thanks!
arjen_dk said:
Hi all,
I'm trying to root a HTC Desire, but having no succes with Unrevoked nor Revolutionary.
This phone has the following configuration:
HBOOT 0.93.0001
Radio 32.49.00.32U_5.11.05.27
Stock HTC ROM, version 2.29.405.5
Phone is plugged in as USB drive and with USB debugging enabled. I'm running Unrevoked and Revolutionary on Linux.
Unrevoked
Using Unrevoked 3.32, the process hangs on "Pushing Flasher...". Nothing happens for a long time, application has to be terminated. (When the phone is unplugged, Unrevoked will say "Failed pushing flasher".)
Update: also tried with Unrevoked 3.21 (some forum posts/blogs suggest this version for HTC Desire), but has the same effect.
Revolutionary
When the above turned out not to work after trying several times, I decided to try Revolutionary after reading some posts about it on this forum. I'm using version 0.4pre4. Revolutionary starts doing its work, then tries to reboot the device, but the phone doesn't go past the FASTBOOT screen (showing options BOOTLOADER, REBOOT, REBOOT BOOTLOADER and POWER DOWN). The phone's hardware buttons are locked. After the second try (see below), the buttons are operational, but Revolutionary reports "failed".
The strange thing is that I have rooted another HTC Desire phone with the exact same specifications some time ago using the exact same copy of Unrevoked3 with no problems.
Does anyone have an idea what is going wrong and what I can do to solve it?
Thanks!
Click to expand...
Click to collapse
with revolutionary did you install the fastboot drivers? read the documentation on the page and there is a link to them. Install the drivers and try again. Then all you gotta do is flash a custom recovery and you can flash away roms. just remember to backup.
Thanks for the message. I'm running the tool on Linux and understand from the documentation that it's self-contained on Linux and no additional drivers are needed. Right? As far as I know I've used both tools correctly.
Any other suggestions on either Unrevoked or Revolutionary are very welcome!
Try a clean sdcard which has only a fat 32 partition and use a stock ROM with no a2sd or Data2sd. Try revolutionary once again with this. Revolutionary does need drivers on windows..in fact their site hosts the driver. Of course Linux doesn't need it..if it fails, try another sdcard with only a fat 32 partition
TouchPal-d from my Desire running Starburst Classic Rom - 450 apps and counting. .
i seem to be going around and around in circles and am about to completely lose my marbles! I am not completely new to this having successfully rooted a vega, htc desire and my one x, several times before.
i am trying to s-off, root and flash new ROM on my mum's old phone so my 5yo can use it for munzeeing.
wildfire/buzz on 2.2.1 with HBOOT1.01.0001
baseband version 13.55.55.24H_3.35.20.10
kernel version 2.6.32.21-g0f9e9b5 [email protected] #1 Tue Nov 30 13:53:39 CST 2010
build number 2.22.405.1 CL295397 release-keys
software number 2.22.405.1
i have uninstalled and reinstalled the drivers over and over again, and now finally seem to be able to get a good adb connection.
however, neither revolutionary tool nor unrevoked3 will work. both find the phone but fail to "do their thing":
revolutionary (downloaded today from revolutionary.io) fails after:
Zerging Root... this might take a minute or so.. _rawadb_handle_msg: unknown command 69766564 Communications with phone unexpectedly interrupted. OR unexpected CLSE. Try again.
unrevoked3 (again fresh download from their website) fails after:
installing package file: 2900000(or so)bytes
installing unrevoked3 service
internal error: installing package failed
i am completely stuck here and can find no way around it.
There is alot about downgrading the boot from 1.01.0002, but i don't have this (and couldnt get that to work either?
what am I missing - i know its something easy/basic.
thanks for any suggestions/help.
dr_nick
dr_nick said:
i seem to be going around and around in circles and am about to completely lose my marbles! I am not completely new to this having successfully rooted a vega, htc desire and my one x, several times before.
i am trying to s-off, root and flash new ROM on my mum's old phone so my 5yo can use it for munzeeing.
wildfire/buzz on 2.2.1 with HBOOT1.01.0001
baseband version 13.55.55.24H_3.35.20.10
kernel version 2.6.32.21-g0f9e9b5 [email protected] #1 Tue Nov 30 13:53:39 CST 2010
build number 2.22.405.1 CL295397 release-keys
software number 2.22.405.1
i have uninstalled and reinstalled the drivers over and over again, and now finally seem to be able to get a good adb connection.
however, neither revolutionary tool nor unrevoked3 will work. both find the phone but fail to "do their thing":
revolutionary (downloaded today from revolutionary.io) fails after:
Zerging Root... this might take a minute or so.. _rawadb_handle_msg: unknown command 69766564 Communications with phone unexpectedly interrupted. OR unexpected CLSE. Try again.
unrevoked3 (again fresh download from their website) fails after:
installing package file: 2900000(or so)bytes
installing unrevoked3 service
internal error: installing package failed
i am completely stuck here and can find no way around it.
There is alot about downgrading the boot from 1.01.0002, but i don't have this (and couldnt get that to work either?
what am I missing - i know its something easy/basic.
thanks for any suggestions/help.
dr_nick
Click to expand...
Click to collapse
You will need to unlock your bootloader on http://www.htcdev.com/bootloader/ then use revolutionary or otherwise your phone is root proof!
KoolKid98189 said:
You will need to unlock your bootloader on http://www.htcdev.com/bootloader/ then use revolutionary or otherwise your phone is root proof!
Click to expand...
Click to collapse
thanks for your reply!
that's the key is it? noone has mentioned that in the forums (though they are pretty old)
struggled with that even, as don't know what the base RUU is to select on 1st page...
dr_nick
dr_nick said:
thanks for your reply!
that's the key is it? noone has mentioned that in the forums (though they are pretty old)
struggled with that even, as don't know what the base RUU is to select on 1st page...
dr_nick
Click to expand...
Click to collapse
Before you attempt to unlock your hboot via htcdev (lots worse that s-off) can you tell me what android programs you have installed on your pc, like htcsync of sony flashtool, android commander. anything like that? its probably a program thats interfeering with your system and not its drivers. Do not update, as to get s-off again you will have to just downgrade back to where you are now :good:
heavy_metal_man said:
Before you attempt to unlock your hboot via htcdev (lots worse that s-off) can you tell me what android programs you have installed on your pc, like htcsync of sony flashtool, android commander. anything like that? its probably a program thats interfeering with your system and not its drivers. Do not update, as to get s-off again you will have to just downgrade back to where you are now :good:
Click to expand...
Click to collapse
thanks heavy_metal_man
i don't think i have anything currently running on the system.
now have android sdk stuff and the universal android drivers.
have uninstalled htc sync manager and htc sync (older version) and removed everything else remotely anrdroid/htc-like from uninstall programs screen.
the great thing is i can now consistently connect to my device in both adb and fastboot modes, so i am definitely making progress. i think the key was that the PC's usb socket i was using is a little intermittent - i have now swapped to a different one (also USB2 instead of 3) and i'm getting a much more consistent connection!
however - i have been trying to unlock the bootloader using htcdev site - but having trouble with the RUU - it now connecte fine and reboots my device into recovery but then crashes. every time.
are you telling me i don't need to RUU on the htcdev site? can i s-off/root without??
thanks again
dr_nick
dr_nick said:
thanks heavy_metal_man
i don't think i have anything currently running on the system.
now have android sdk stuff and the universal android drivers.
have uninstalled htc sync manager and htc sync (older version) and removed everything else remotely anrdroid/htc-like from uninstall programs screen.
the great thing is i can now consistently connect to my device in both adb and fastboot modes, so i am definitely making progress. i think the key was that the PC's usb socket i was using is a little intermittent - i have now swapped to a different one (also USB2 instead of 3) and i'm getting a much more consistent connection!
however - i have been trying to unlock the bootloader using htcdev site - but having trouble with the RUU - it now connecte fine and reboots my device into recovery but then crashes. every time.
are you telling me i don't need to RUU on the htcdev site? can i s-off/root without??
thanks again
dr_nick
Click to expand...
Click to collapse
I would recommend attempting revolutionary from revolutionary.io again, assuming that your hboot is still 1.01.0001! keeping in mind that all htc sync type programs are a no-no ( but you have taken care of that ) usb3 ports a no-no for almost all android development and tools (including this one ) and lastly dont install the revolutionary version of clockworkmod recovery as it has a "charging bug" follow this guide and you shall be fine I recommend that you add clockworkmod recovery version 5.0.2.0 from post 2 section 6. using the pc49img.zip method is usually the easiest. tap this thread to let me know how you got on
yay it worked without problem!
thanks for all your help.
pretty sure it was just the USB3 that was the problem - why have i not read anywhere that this is a no no??
thanks all
drnickf
Pretty sure usb3 was not widely used at the time, ergo not a known issue
Sent from my Nexus 7 using Tapatalk