Develop Bugs

[Q] need help installing gingerbread keyboard

i have installed the gingerbread keyboard file on my sd card and have rooted my phone using the visonary method but now i cant seem to get into recovery mode. I have rom manager installed and have flashed clockwork recovery mode. it said that it had sucsessfully installed.
I then flashed it again as i read somewhere that i might need to do it twice as sometimes it dosent work.
when i now click on the recovery option in rom manager all i get is the red triange with the ! in the middle.
any ideas what im doing wrong?
Have tried reading the threads but with 30 plus pages i am now completley confused

Sounds like you don't have S-OFF. What does it say in HBOOT (e.g. hold down volume down and the power button with the phone powered off) ?

steviewevie said:
Sounds like you don't have S-OFF. What does it say in HBOOT (e.g. hold down volume down and the power button with the phone powered off) ?
Click to expand...
Click to collapse
thanks for the quick reply, i think from what i have read that this s-off thing maybe the problem.
can you tell me how do this please
simple steps please as i am struggling with this

just done the hboot hing and at the top of screen it says
vision pvt ship s-on

hpsauce37 said:
thanks for the quick reply, i think from what i have read that this s-off thing maybe the problem.
can you tell me how do this please
simple steps please as i am struggling with this
Click to expand...
Click to collapse
It's a bit confusing because there is more than one way to do this. But by far the safest way is to follow the guide at http://forum.xda-developers.com/showthread.php?t=857390
Have a good read, then if you're not sure, ask questions in that thread on the process.

steviewevie said:
Sounds like you don't have S-OFF. What does it say in HBOOT (e.g. hold down volume down and the power button with the phone powered off) ?
Click to expand...
Click to collapse
S-OFF is a completely different animal. Don't get it confused with being able to boot into recovery.
Sent from my EVO using Tapatalk Pro

rwcj63 said:
S-OFF is a completely different animal. Don't get it confused with being able to boot into recovery.
Click to expand...
Click to collapse
I didn't think you could flash recovery without S-OFF though ? Surely ROM Manager doesn't have the ability to write to the NAND, since the write protection will be on if you're at S-ON ?

steviewevie said:
I didn't think you could flash recovery without S-OFF though ? Surely ROM Manager doesn't have the ability to write to the NAND, since the write protection will be on if you're at S-ON ?
Click to expand...
Click to collapse
Again. S-OFF is a different issue altogether. Being able to write to NAND is a part of the rooting process. Setting security off is not a part of the rooting process. It's a totally different process for a totally different purpose. The caveat would be if unrevoked has been revised to full root and set S-OFF during the same process. I haven't used it in awhile so on that point, I'm not certain.
Sent from my EVO using Tapatalk Pro

rwcj63 said:
Again. S-OFF is a different issue altogether. Being able to write to NAND is a part of the rooting process. Setting security off is not a part of the rooting process. It's a totally different process for a totally different purpose. The caveat would be if unrevoked has been revised to full root and set S-OFF during the same process. I haven't used it in awhile so on that point, I'm not certain.
Click to expand...
Click to collapse
Sorry but that's not right for the DZ/G2. I wonder if you're thinking of how it works on a different Android phone ? The security has been increased on the DZ/G2/DHD compared to, say, the original Desire.
Writing to the system and recovery partitions isn't possible until you get S-OFF. This has nothing to do with rooting, it it because of the increased security on these phones where the NAND is in a hardware write-protect mode for those partitions by default. You can appear to write to the partitions, but it's actually going to cache and is lost when you reboot, until you get S-OFF.

steviewevie said:
Sorry but that's not right for the DZ/G2. I wonder if you're thinking of how it works on a different Android phone ? The security has been increased on the DZ/G2/DHD compared to, say, the original Desire.
Writing to the system and recovery partitions isn't possible until you get S-OFF. This has nothing to do with rooting, it it because of the increased security on these phones where the NAND is in a hardware write-protect mode for those partitions by default. You can appear to write to the partitions, but it's actually going to cache and is lost when you reboot, until you get S-OFF.
Click to expand...
Click to collapse
Actually yes. S-OFF on the EVO is to make sure no matter what, you're always rooted. It came about after the new stock flash would unroot the phone. With S-OFF active, you can flash any stock rom and not lose root. All you would need to do is reflash RA or Clockwork to get back to recovery and flash roms again. Unrevoked forever is the program we used to change the security setting.
So. That is only true for the EVO?
Sent from my EVO using Tapatalk Pro

rwcj63 said:
Actually yes. S-OFF on the EVO is to make sure no matter what, you're always rooted. It came about after the new stock flash would unroot the phone. With S-OFF active, you can flash any stock rom and not lose root. All you would need to do is reflash RA or Clockwork to get back to recovery and flash roms again. Unrevoked forever is the program we used to change the security setting.
So. That is only true for the EVO?
Sent from my EVO using Tapatalk Pro
Click to expand...
Click to collapse
yeah I think so.
The new HTC Desire Z and HD had "better" security from htc, basically you can't write anything to nand (/system) until you perma rooted, even then some things such as recovery needed s-off before we could write to that partition.

im going to have to give up on this
i have tried to follow the guide to get s-off but i find it too complicated. I have my phone rooted with visionary but i think thats as far as im going to get.
tried to install the adb thing and get that working but it never recognises the phone. when i remove the drivers and plug it back in then windows automatically installs the drivers again so i never have the option to manually instll them.
this is just becoming a nightmare
someone make it simple for me please....the thread is pages and pages long and even then it seems there are problems

hpsauce37 said:
im going to have to give up on this
i have tried to follow the guide to get s-off but i find it too complicated. I have my phone rooted with visionary but i think thats as far as im going to get.
tried to install the adb thing and get that working but it never recognises the phone. when i remove the drivers and plug it back in then windows automatically installs the drivers again so i never have the option to manually instll them.
this is just becoming a nightmare
someone make it simple for me please....the thread is pages and pages long and even then it seems there are problems
Click to expand...
Click to collapse
Have you tried my guide on adb ? http://forum.xda-developers.com/showthread.php?t=865685

OK, I can use some help too
I have a DZ with stock ROM, root and s-off and CWR.
In my enthusiasm that I knew how to flash rom updates with clockwork (I am running the Godspeed 1Ghz) I downloaded the Gingerbread keyboard rom update from the G2 forum. I think I jumped off a bit too fast...
And now I am stuck in an infinite boot loop. I can get into Clockwork recovery but it just loops the "HTC Quietly Brilliant" forever including the annoying boot sound...
I tried some suggestions to download and reflash a second time, no effect.
I tried to mount /system before flashing, no effect.
Am I forced to go back to factory now?
Also, I found 2 gingerbread keyboards, one in the G2 forum and one over here.
Anyone know what the difference is? They have a different filesize..
Any help is welcome...
*edit*
OK so now I read that it is only to be flashed on a non-stock ROM... so I am now flashing Cyanogen 6.1

try wiping all the caches...

Lennyuk said:
yeah I think so.
The new HTC Desire Z and HD had "better" security from htc, basically you can't write anything to nand (/system) until you perma rooted, even then some things such as recovery needed s-off before we could write to that partition.
Click to expand...
Click to collapse
Wow. I'm really sorry guys. I never knew that's how non evo worked. That totally sucks.
Sent from my EVO using Tapatalk Pro

rwcj63 said:
Wow. I'm really sorry guys. I never knew that's how non evo worked. That totally sucks.
Click to expand...
Click to collapse
S'alright.
HTC really ramped up the security on these new phones, as Lenny said, with this hardware write-protection on certain partitions. But even given that, I was amazed by just how quickly the guys on the #G2ROOT IRC channel, especially Scotty2, managed to crack it !
It also looks like they've opened the phone even wider than many others before, with the "true" radio S-OFF that they achieved.
You can read up all about it in the Wiki - http://forum.xda-developers.com/wiki/index.php?title=HTC_Vision

[Q] Visionary broke my Tmobile G2 phone - PLEASE HELP !!

I installed Visionary and everything was working perfect... But I made the stupid mistake to press Permroot and my G2 shut down and never bootup to Andrid OS..
I only see the HTC green logo .. I tried everything on recovery mode.. but I only get the HTC logo and the phone dont go anywere..
I tried to install the original G2 stock ROM but then the update fail saying Im trying to flash a older update. The room in the phone is newer than the update Im trying to install..,
Someone knows were I can find a Custom room that works in my Tmobile G2 USA...?
I need to install the room in recovery mode...ONLY .. because my phone do not boot-up.... So the ADB is disabled and the phone do not work... I only have access to recovery mode...
PLUS the phone is NOT rooted...
And Please dont tell me to do factory Reset.. because I did all that..If Im here is because I have tried everything and I dont get this phone to work.
Is there a room or a custom room somewhere that can be installed in my G2 by Recovery mode..?
If there is ,, can someone give me the link...?
My HBOOT screens says the following
VISION PVT SHIP S-ON
HBOOT- 0.82.0000
MICROP-0425
RADIO-26.03.02.26_M
eMMc-boot
Sep 2 2010, 17:59:38

boyfrom75 said:
I installed Visionary and everything was working perfect... But I made the stupid mistake to press Permroot and my G2 shut down and never bootup to Andrid OS..
I only see the HTC green logo .. I tried everything on recovery mode.. but I only get the HTC logo and the phone dont go anywere..
I tried to install the original G2 stock ROM but then the update fail saying Im trying to flash a older update. The room in the phone is newer than the update Im trying to install..,
Someone knows were I can find a Custom room that works in my Tmobile G2 USA...?
I need to install the room in recovery mode...ONLY .. because my phone do not boot-up.... So the ADB is disabled and the phone do not work... I only have access to recovery mode...
PLUS the phone is NOT rooted...
And Please dont tell me to do factory Reset.. because I did all that..If Im here is because I have tried everything and I dont get this phone to work.
Is there a room or a custom room somewhere that can be installed in my G2 by Recovery mode..?
If there is ,, can someone give me the link...?
My HBOOT screens says the following
VISION PVT SHIP S-ON
HBOOT- 0.82.0000
MICROP-0425
RADIO-26.03.02.26_M
eMMc-boot
Sep 2 2010, 17:59:38
Click to expand...
Click to collapse
Try the following link:
http://forum.xda-developers.com/showthread.php?t=842495

I already did try the link. But I dont understand what option to take..
The one of the options I think will work needs to have the phone ADB running ..
But my ADB is disabled because I can't get to the Android OS and the phone is not rooted..
I was reading that you can connect the phone to the Computer to fix it..
How do I do that ? What program do I need to run it ? But I dont like that option,,,, is to complicated..
Is there a way to fix the phone using the SD card on Recovery mode ?

boyfrom75 said:
I already did try the link. But I dont understand what option to take..
The one of the options I think will work needs to have the phone ADB running ..
But my ADB is disabled because I can't get to the Android OS and the phone is not rooted..
I was reading that you can connect the phone to the Computer to fix it..
How do I do that ? What program do I need to run it ? But I dont like that option,,,, is to complicated..
Is there a way to fix the phone using the SD card on Recovery mode ?
Click to expand...
Click to collapse
1) Just to clarify: VISIONary is a complete fail. Root using the rage method, then you can actually control what's happening to your device.
2) Did you ever flash clockwordmod recovery?
If you can boot into clockwork recovery you just need to flash another ROM.

Try posting this in the Q n A section. I know, posting a question in the QnA forum probably sounded like a CRAZY idea, but guess what, that is where this belongs.

tehseano said:
Try posting this in the Q n A section. I know, posting a question in the QnA forum probably sounded like a CRAZY idea, but guess what, that is where this belongs.
Click to expand...
Click to collapse
this guy is obviously new cut him some slack.....
just follow the instruction on the link carefully
idk why people are having trouble with VISONary i used it to root my phone n it worked....
im new on the forums but i know a thing or two about rooting

That's why I'm using Rom manager.. because its easier for my self.. as soon as you flash clock work recovery.. I believe that you can't go wrong.. I also did something similar and my phone also staid at the HTC screen.. but went back into recovery mode and clicked on restore and went in on my old Rom
sent from g2 using DHD Rom

boyfrom75 said:
I already did try the link. But I dont understand what option to take..
The one of the options I think will work needs to have the phone ADB running ..
But my ADB is disabled because I can't get to the Android OS and the phone is not rooted..
I was reading that you can connect the phone to the Computer to fix it..
How do I do that ? What program do I need to run it ? But I dont like that option,,,, is to complicated..
Is there a way to fix the phone using the SD card on Recovery mode ?
Click to expand...
Click to collapse
Ok, this is a snip from the link in the second post, it sounds like your are stuck in a boot loop with s-on, if so then this part is the part you need to try:
"*if you have stock or eng-recovery installed.
will the phone attempt to boot android at all? where is it stuck at?
a good min after it starts to try to boot, type these commands:
adb remount
adb shell
if you can get in shell then theres still hope. back out shell for a second and start here:
put the cwm recovery.img and wpthis.ko in your sdk folder
adb remount
adb push wpthis.ko /data/local/wpthis.ko (specific for your kernel)
adb push recovery.img /data/local/recovery.img
adb shell
# insmod /data/local/wpthis.ko (should get same function not implemented error as when u rooted first time)
# dd if=/data/local/recovery.img of=/dev/block/mmcblk0p21 (now wait a min or 2 to give it time to finish)
#sync (give it another min or to just to be safe)
#reboot recovery
at this point you should be in cwm recovery. follow instructions above for flashing with s-on."
So now you are gonna have to install Andriod SDK to your computer and the drivers for the G2, there is gonna be a lot of reading and some downloading on your part to do this. Next your gonna have to download cwm recovery.img and wpthis.ko in your sdk folder and then follow the instructions above to recover your phone. Unfortunatly there is no one click fix. Its gonna take a lot of reading and understanding to do this on your part. Gonna have to learn to use ADB there a guide for that and run some basic command promts. Im no Dev or anything but I taught myself by doing a lot of reading, watching videos and a lot of searching. Hope you find the will to do it and recover you phone. Plus we are here to help walk you through some of it but your also gonna have to do some leg work to. GOOD LUCK.

I don't think the OP knows what adb is... you gotta do some more reading get over your fear of using your computer to fix your phone. Its really nothing to be afraid of and its not at all complicated.
Sent from my HTC Vision using XDA App

I'm gonna assume he knows what ADB is and if that's the case, your only option is using one of the full updates...from tmobile. It would have to be a new version of course, for your recovery to allow it. Trying reading through thr RUU threads, perhaps something or someone there can help.
Goodluck, and sry.
Sent from my HTC Vision using XDA App

android602 said:
That's why I'm using Rom manager.. because its easier for my self.. as soon as you flash clock work recovery.. I believe that you can't go wrong.. I also did something similar and my phone also staid at the HTC screen.. but went back into recovery mode and clicked on restore and went in on my old Rom
sent from g2 using DHD Rom
Click to expand...
Click to collapse
Brah its not even rooted yet
Sent from my T-Mobile G2 using XDA App

Not only does he not know what adb is... he didn't even have usb debugging enabled... Not sure that affect's whether or not he can use adb in the recovery or not... but just saying

omarsalmin said:
Not only does he not know what adb is... he didn't even have usb debugging enabled... Not sure that affect's whether or not he can use adb in the recovery or not... but just saying
Click to expand...
Click to collapse
USB debugging does need to be enabled. I know this because I always forget that step when I'm trying to use ADB on a new Android device.
If OP wants a working phone again, he'd better take his pretty-looking paperweight back to get it replaced (just drop it in your toilet first).

blackknightavalon said:
USB debugging does need to be enabled. I know this because I always forget that step when I'm trying to use ADB on a new Android device.
If OP wants a working phone again, he'd better take his pretty-looking paperweight back to get it replaced (just drop it in your toilet first).
Click to expand...
Click to collapse
WATER DAMAGE! Haha I don't think warranty covers that
I just read somewhere that in order for VISIONary to perm root you need to have S-OFF. OP made a boo boo by attempting to perm root with S-OFF.

omarsalmin said:
WATER DAMAGE! Haha I don't think warranty covers that
I just read somewhere that in order for VISIONary to perm root you need to have S-OFF. OP made a boo boo by attempting to perm root with S-OFF.
Click to expand...
Click to collapse
actually all the older guides (including the one I used to root my phone) said you ran perma root first then do s-off.
the perma root method in visionary was made before we even had s-off (only like a day before, but still before).
It sounds to me like your having the same problem that some people have been having with the rage method, only because you have s-on still your stuffed.
Basically for some reason newer phones seem to be getting a corrupt rom when perma rooting by any method. If you had s-off you could manually flash a recovery then a new rom.

Lennyuk said:
It sounds to me like your having the same problem that some people have been having with the rage method, only because you have s-on still your stuffed.
Basically for some reason newer phones seem to be getting a corrupt rom when perma rooting by any method. If you had s-off you could manually flash a recovery then a new rom.
Click to expand...
Click to collapse
The OP here used Visionary, not rage. Not sure which problem with rage you're referring to, because I've never seen anyone stuck in a boot loop just because they did rage.
His phone also seems to have been messed with before he got it, e.g. it's a G2 but running the DZ radio (which is fine, but implies someone has been doing things to it).

steviewevie said:
The OP here used Visionary, not rage. Not sure which problem with rage you're referring to, because I've never seen anyone stuck in a boot loop just because they did rage.
His phone also seems to have been messed with before he got it, e.g. it's a G2 but running the DZ radio (which is fine, but implies someone has been doing things to it).
Click to expand...
Click to collapse
2 people last week on the same day got partial bricks by using rage, I had to talk both of them through flashing a recovery manually in order to install a non corrupt rom.
I have a feeling the perma root process is corrupting roms on newer devices, not sure on the why though.

Lennyuk said:
2 people last week on the same day got partial bricks by using rage, I had to talk both of them through flashing a recovery manually in order to install a non corrupt rom.
Click to expand...
Click to collapse
You said this the other day, but I asked you for links and I don't think you replied (but maybe I missed that).
Are you sure they didn't use Visionary first ? That's usually what corrupts the ROM. Because rage is very very simple, it's not like Visionary which does complicated stuff. I really don't see how rage on its own can corrupt a ROM.
If you have any links to threads where people have not used Visionary, only rage, and have corrupted the ROM, then I'd be very interested.

steviewevie said:
You said this the other day, but I asked you for links and I don't think you replied (but maybe I missed that).
Are you sure they didn't use Visionary first ? That's usually what corrupts the ROM. Because rage is very very simple, it's not like Visionary which does complicated stuff. I really don't see how rage on its own can corrupt a ROM.
If you have any links to threads where people have not used Visionary, only rage, and have corrupted the ROM, then I'd be very interested.
Click to expand...
Click to collapse
Come on man, I shouldn't have to prove myself...
but here you go
http://forum.xda-developers.com/showthread.php?t=871288
and
http://forum.xda-developers.com/showthread.php?t=871552
both using RAGE and not VISIONARY.

Lennyuk said:
Come on man, I shouldn't have to prove myself...
but here you go
http://forum.xda-developers.com/showthread.php?t=871288
and
http://forum.xda-developers.com/showthread.php?t=871552
both using RAGE and not VISIONARY.
Click to expand...
Click to collapse
Sorry you took it that I was asking you to prove yourself. I wasn't, I was just asking for information, because I'm interested in the subject.
I'd seen those threads but do you know for certain they didn't try Visionary first, find it didn't work properly, then try rage ?
I could of course be wrong, but I don't see how rage can cause corruption because it doesn't do a lot, it just fires up a bunch of processes to exploit a way to get root. It's so much simpler than Visionary, which does a whole load of RAM disk stuff and other things that could be more risky if it goes wrong.
I suspect in those two cases that something else had already messed with their phones to cause the boot problem.

How to enable S-on in bootloader

I ran unrevoked 3 and tried a few things and decided it was not for me, I ran the Sprint RUU and it all worked fine. But under the bootloader screen it still shows S-off. Can I renable it?

venom_762 said:
I ran unrevoked 3 and tried a few things and decided it was not for me, I ran the Sprint RUU and it all worked fine. But under the bootloader screen it still shows S-off. Can I renable it?
Click to expand...
Click to collapse
Sry to hear that. See if THIS helps.

oooh that sucks. you have to re-root (you can just use unrevoked 3 again), then put the unrevoked s-on tool (found in the FAQ section of this thread http://unrevoked.com/rootwiki/doku.php/public/forever ) on the root of your sdcard. boot into recovery, and flash it as you would a rom. then check bootloader to make sure it is s-on. if it is, run the ruu again.
just curious, why dont u like root?

I just tried to re-run Unrevoked 3 and it will not reconnect, the tool just says waiting for device.
And I don't like root because of too much power.

venom_762 said:
I just tried to re-run Unrevoked 3 and it will not reconnect, the tool just says waiting for device.
And I don't like root because of too much power.
Click to expand...
Click to collapse
usb debugging is probably not on. try that.
too much power? like too much battery consumption (wtf?) or too much power over the phone?

too much stuff for me to f-with.

venom_762 said:
too much stuff for me to f-with.
Click to expand...
Click to collapse
hahah ok then. so ya turn debugging on (settings, applications, development, usb debugging) and put the phone on charge only and run unrevoked.

ok I found it, I was trying to root from the hboot screen.

Can't I just wait for the OTA from sprint and that would just turn S-back on?

venom_762 said:
Can't I just wait for the OTA from sprint and that would just turn S-back on?
Click to expand...
Click to collapse
no, it wouldnt turn s-on, and you might not even be able to accept it. if you are having a hard time using unrevoked, seeing as your rom no longer has root permissions, i can lead you through manually flashing amon-ra recovery to your phone and you can flash ur s-on from there.

I just got it to root again using Unrevoked 3 and restored to right after my first root. I should be able to now install the S-on tool and install it from the recovery menu?

venom_762 said:
I just got it to root again using Unrevoked 3 and restored to right after my first root. I should be able to now install the S-on tool and install it from the recovery menu?
Click to expand...
Click to collapse
That is correct. Also, I'm pretty sure that since you were still S off, you could've just flashed a pc36img of a recovery from the bootloader, flashed the s on tool, and then ran RUU.
Edit : just saw that dk already suggested that. Sorry.
Sent from my PC36100 using XDA App

Update I figured it out and ran the S-on tool, booted into the bootloaded and verified it was back on. I then ran the RUU and it should be fully stock and ready to install the OTA?

I just don't want to be that guy does not or has a failed update when the official OTA is out.

Anyone? I dying to know if I can install the next ota.

venom_762 said:
Anyone? I dying to know if I can install the next ota.
Click to expand...
Click to collapse
If you're back to stock, s on, and aren't on the latest OTA, then yes, you can take the OTA if you'd like to. That will bring you up to the latest software update.
Sent from my PC36100 using XDA App

Great I am relieved, I just wondered if when its pushed out if I have problems seeing it. Thank you guys for all of your help.

venom_762 said:
Great I am relieved, I just wondered if when its pushed out if I have problems seeing it. Thank you guys for all of your help.
Click to expand...
Click to collapse
sorry for leaving you in the dark for a while. that was one crazy day. but i'm at my comp now so i can help (not that there's anything left to do).
if i were you, i'd double check you are fully unrooted. boot into bootloader, and make sure you are s-on. then boot into recovery and make sure you have no custom recovery, just the stock htc one. also make sure your rom has no superuser app installed. if not, you are all good.

No prob man, I booted into the bootloader and S-On is back on and then tried to boot into recovery, a black screen with a red triangle came up so I assume there's no recovery installed. There is also no superuser Icon in the app draw.
The main reason I returned to stock is,is that this is my primary and only phone. I plan on getting the Nexus S when it come to sprint so I will see you guys again. That way if I bork the NS I got my trusty evo to activate.
Again thank you all for the help.

venom_762 said:
No prob man, I booted into the bootloader and S-On is back on and then tried to boot into recovery, a black screen with a red triangle came up so I assume there's no recovery installed. There is also no superuser Icon in the app draw.
The main reason I returned to stock is,is that this is my primary and only phone. I plan on getting the Nexus S when it come to sprint so I will see you guys again. That way if I bork the NS I got my trusty evo to activate.
Again thank you all for the help.
Click to expand...
Click to collapse
ok ya ur totally unrooted. enjoy the cage some prefer it there.
just saying, the evo is freaking hard to brick.

Can't s-off alpharev

Hi guys I'm trying to s-off using alpharev ISO disc...it goes through the process then after rebooting stage 3 I get 4 lines that say unary operator expected ... I shut down pc and phone boots as usual...
I'm running rxmix s v1.1

maybe change to stock ROM and try s-off again

Yes like the post above switch to a ROOTED stock froyo rom worked for me, the reason your getting errors is because the rom you are running has probably got data2whatever, data++ ect... this affects the alpha rev process.

Ditto above. Alpharev doesn't work on a2sd or similar ROMs... Look back a couple pages and you'll see I started a thread with the same issue. I'm on IC GB a2sd+...
Once pc is repaired, I plan to load stock Telstra RUU and try again, then re-root...

bailz2506 said:
Hi guys I'm trying to s-off using alpharev ISO disc...it goes through the process then after rebooting stage 3 I get 4 lines that say unary operator expected ... I shut down pc and phone boots as usual...
I'm running rxmix s v1.1
Click to expand...
Click to collapse
First, you better use USB stick instead of a disc, it is faster a more reliable.
Secondly, you won't be able to get s-off unless you flash either stock rom or AOSP rom ( oxygen worked for me without any problems).

mikeraul said:
First, you better use USB stick instead of a disc, it is faster a more reliable.
Secondly, you won't be able to get s-off unless you flash either stock rom or AOSP rom ( oxygen worked for me without any problems).
Click to expand...
Click to collapse
+1, I s-off my phone with oxygen running on it.

ThaNx everyone for the help will try it that way and let you all no if it worked
Sent from my HTC Desire using XDA App

thanks everyone for the help it worked fine now i have fully rooted and s-offed htc desire...now to get back into the flashing fun.
When the moderator reads this i have no problems if this thread is deleted thanks again

bailz2506 said:
thanks everyone for the help it worked fine now i have fully rooted and s-offed htc desire...now to get back into the flashing fun.
When the moderator reads this i have no problems if this thread is deleted thanks again
Click to expand...
Click to collapse
Happy to hear

Hi folks. Writing this without any hope that someone is online at the moment.
I'm currently using alpharev to flash HBOOT on my htc desire. It has stucked on step 3 with two lines on phone's screen:
Aplharev SPLBOOT version 2.0
...
Normal NAND detected. Non-PVT4
and keeps hanging like that nearly an hour already.
The phone is rooted, with Clockworkmod recovery and InserCoin 2.0.1 DATA2EXT ROM installed.
Did anybody have the same behaviour while flashing HBOOT?
Should I be patient and wait for some miracle to happen?
thanks in advance.

Are you S-Off already??

use the new S-OFF utility. It's a lot quicker and easier. Just make sure you uninstall HTC Sync, or at least make sure it isn't running.

777ace said:
Are you S-Off already??
Click to expand...
Click to collapse
no...
just saw here an advice to wait for a long term and the to pull out the battery and reboot.
did as he said.
device is rebooting in fastboot mode...
will try to restore previous ROM from recovery mode...

n0vice said:
no...
just saw here an advice to wait for a long term and the to pull out the battery and reboot.
did as he said.
device is rebooting in fastboot mode...
will try to restore previous ROM from recovery mode...
Click to expand...
Click to collapse
try it with the new utility.. it should work for you..

finally I've restored my previous ROM (and sh*tted a pile of bricks during this hour).
HBOOT screen says that my device is still S-ON. strange... maybe that's because of 'DATA2EXT' ROM onboard.
bortak said:
use the new "...revolutionary.io/" S-OFF utility. It's a lot quicker and easier. Just make sure you uninstall HTC Sync, or at least make sure it isn't running.
Click to expand...
Click to collapse
thanks. I'll try it when my hands will stop shaking

You won't be able to alter HBoot without S-Off...
I am not sure how the new Utility that bortak linked to works, but I know that the "old" alpharev will not S-Off if you are using A2SD/D2SD/D2EXT type ROMs. You will need to flash stock RUU (do not use latest GB update RUU!!!), or one of the AOSP ROMs, such as Oxygen, before proceeding.
Once you have S-Off, you can go back and re-root, then upgrade your HBoot etc.

777ace said:
You won't be able to alter HBoot without S-Off...
I am not sure how the new Utility that bortak linked to works, but I know that the "old" alpharev will not S-Off if you are using A2SD/D2SD/D2EXT type ROMs. You will need to flash stock RUU (do not use latest GB update RUU!!!), or one of the AOSP ROMs, such as Oxygen, before proceeding.
Once you have S-Off, you can go back and re-root, then upgrade your HBoot etc.
Click to expand...
Click to collapse
thanks. I'll follow your advice.
I'm still wondering, why TUT-makers didn't mention this A2SD/D2SD/D2EXT ROMs inconsistency.
I think this should be written in large letters on the first line for noobs like me

Lol, you're right on that!!
If you look on alpharev site, it is mentioned in the text, but VERY small!
Requirements:
The only requirement right now is that the ROM you're running is rooted.
As techniques such as 'data2ext' have been popping up, these might disturb our finely-tuned flashing process.
Please revert to a rooted stock ROM if possible. Your /data partition is used for temporary storage of important files.
Click to expand...
Click to collapse
I missed it the first time also, had lots of dramas, and finally spotted that note after many frustrating hours. It should have been written in bright red, 72 cap at the top of screen!!

You need to use an a2sd Rom like lee Droid 2.5.
Alpha rev state this at start of web page using data2sd can cause problems.
Flash lee Droid 2.5 and try it again, you should be fine
Kind regards
John
Sent from my HTC Desire using XDA Premium App

It is being said on Alpharev website under "requirements".
Though I agree it should be said in tutorials too.
n0vice said:
thanks. I'll follow your advice.
I'm still wondering, why TUT-makers didn't mention this A2SD/D2SD/D2EXT ROMs inconsistency.
I think this should be written in large letters on the first line for noobs like me
Click to expand...
Click to collapse
Sent from my HTC Desire using XDA App

I need help finding the right ruu so i can get s-off :(

I'm trying to get s-off with my htc evo 4g and im getting so frustrated i cant find anything complete. so far I was able to downgrade my phone to 2.2 from this small tut on themikmik but it never tells how to get actual s-off..i tried unrevoked 3.22 and it stops at waiting for root. im pretty sure i have the hboot drivers installed and it tells my phone what to do up untill it says waiting for root and does nothing. please im a very sad panda. if someone had a link to the ruu that would update my hboot to 2.15.0001 or 2.16.0001 hboot that is rootable with revolution that might work. thank you for your time.

Try here:
http://www.shipped-roms.com/index.php?category=android&model=Supersonic

Thank you! do you happen to know which one of those I should use? Also when I downgraded last I guess it locked my boot loader is that a problem?

Kannz2 said:
Thank you! do you happen to know which one of those I should use? Also when I downgraded last I guess it locked my boot loader is that a problem?
Click to expand...
Click to collapse
Unfortunately it's been way too long since I've messed with the OG EVO. The locked bootloader won't be a problem, though.

Hopefully someone could tell me? I don't really want to update past the hboot I need For the revolution root.

Kannz2 said:
Hopefully someone could tell me? I don't really want to update past the hboot I need For the revolution root.
Click to expand...
Click to collapse
Should be this one:
http://www.shipped-roms.com/downloa....15.00.0808_NV_2.15_release_209995_signed.exe

Thank you I'll try it out I hope I don't mess it up. I just hook the phone up and click on the exe right? Does it need to be in a certain mode?

Kannz2 said:
Thank you I'll try it out I hope I don't mess it up. I just hook the phone up and click on the exe right? Does it need to be in a certain mode?
Click to expand...
Click to collapse
You can run it with the phone booted to the OS or from the bootloader while connected via Fastboot USB mode. Once you've done that just run the exe from your computer by double-clicking on it. You may need to install HTC Sync also.

um it seems that when i try to use that update it says that it is the wrong update and it gives a error "signarure error" with the spelling error.. :crying:

Kannz2 said:
um it seems that when i try to use that update it says that it is the wrong update and it gives a error "signarure error" with the spelling error.. :crying:
Click to expand...
Click to collapse
Is the RUU version newer or older than what's installed on your phone?

I was able to find a flashable image and i got s-off with revolutionary. uh do you happen to know a good kernel to go with cm? or does it flash its own kernel when the rom is flashed? i was able to find a link for cm 7.2 or something like that. know a link for a good kernel? i heard tiamat or mason kernels are good but i cant find a mirror for either of them. you know a place to get them? or a old mirror? thanks for your help ^^

I don't normally make ROM recommendations but if you're looking to go the AOSP route, Deck's Reloaded is one of the best. Everything works. Period. This was one of the last ROM's I ran on my OG EVO before I upgraded. It has the Mason kernel already built in, too.
http://forum.xda-developers.com/showthread.php?t=1661605

thanks for all the help. ^^ You know somewhere that has some custom startup animations? I changed the splashscreen to the green android pooin on a apple but right now its stock boot animation.

Take a look at the themes & apps section. Also, I know that the ROM Toolbox app used to include some custom boot animations.