Related
bought a phone off ebay (eris)
how do i know if its running 2.1leak or 2.1 root?
Check the bootloader version. 1.46 or 1.47 and it would be the OTA; 1.49 and it's a leak.
[Edit: Hold volume down and the power button when you power it on to check.]
it says 1.47. does this mean i can downgrade to 1.5 using tutorial
I'm not an expert at this, but i do know (i think) two things. One, hboot V 1.47 can be rolled back to 1.5 via that tutorial. Two, you can install the original root rom, as it works with the OTA update, directly to the current version... (I think)
i have been trying to flash amon recovery image so i can do the 1.5 downgrade tutorial but it doesnt seem to work
Try installing the root pb00img file, and see what happens, as it seems the phone has the OTA update, and you have to have root to flash the recovery image... (I believe)
If you are trying to root, you can do so directly from the ota.
in terms of rooting android 1.5 and 2.1 are pretty much the same.
you can root using both
you can flash the same roms on both
you can downgrade back to 1.5 once you root on both
etc
osiris20025 said:
i have been trying to flash amon recovery image so i can do the 1.5 downgrade tutorial but it doesnt seem to work
Click to expand...
Click to collapse
I would recommend that you check out the following thread. They made a nice app that can help through the process.
http://forum.xda-developers.com/showthread.php?t=661413
I installed the root pb00img file and worked fine then downgraded to 1.5 using the tutorial, THANKS!
Full Rom link
http://android.clients.google.com/p...2cf141e6a.signed-soju-ota-102588.f182cf14.zip (89.9 MB)
Link for GRH78C
http://android.clients.google.com/p...9e.signed-soju-GRI40-from-GRH78C.98f3836c.zip
Link for GRH78 only
http://android.clients.google.com/p...2bf.signed-soju-GRI40-from-GRH78.e0b546c4.zip
As posted here by Matrik: http://forum.xda-developers.com/showpost.php?p=11616226&postcount=389
I figured I'd get this unburied for everyone interested (which is likely a lot of folks).
If you're stock and unrooted - download this and place it on the root of the SD card - named update.zip. Boot into recovery. Hold Pwr and then Vol up and then choose to apply update.zip.
just got it on mine too.
does anyone know if this build is still rootable in the same method of 2.3.2? just curious
krohnjw said:
http://android.clients.google.com/p...2bf.signed-soju-GRI40-from-GRH78.e0b546c4.zip
As posted here by Matrik: http://forum.xda-developers.com/showpost.php?p=11616226&postcount=389
I figured I'd get this unburied for everyone interested (which is likely a lot of folks).
Also Mirrored if the download breaks for some reason:
http://hotfile.com/dl/107285073/f39f21c/e0b546c442bf.signed-soju-GRI40-from-GRH78.e0b546c4.zip.html
Click to expand...
Click to collapse
WOW - didn't think I'd see this so soon - thanks for digging it out man.
Guess I'll be the guinea pig
jaker.the.skater said:
just got it on mine too.
does anyone know if this build is still rootable in the same method of 2.3.2? just curious
Click to expand...
Click to collapse
If your bootloader is unlocked then rooting is as easy as flashing CWM and flashing the SU binary.
If the bootloader is locked then the changelog indicates that you will not longer be able to use fastboot boot to load CWM and root that way.
With that said, I applied a lot of updates on my Nexus One without losing root and kept the boot loader locked the whole time. You'll need to pay attention, but you should be able to do the following.
Download the SU binary zip and place that on the SD card.
The OTA will not overwrite CWM until it actually boots. So, after you apply the OTA boot directly into recovery and apply the SU zip. This will give you root. (Just pay attention and hold vol up when it goes to reboot)
When you subsequently load up android CWM will be overwritten. At this point you can use the flash_image binary to manually flash CWM to recovery (or potentially ROM Manager).
ok my bootloader is unlocked. so basically i just do like before where you rename the install recovery.sh file so that cwm sticks? if so then cool beans.
jaker.the.skater said:
ok my bootloader is unlocked. so basically i just do like before where you rename the install recovery.sh file so that cwm sticks? if so then cool beans.
Click to expand...
Click to collapse
Yes sir. 10 chars
very cool.
Can i dowload this on a stock Ns
Sent from my Nexus S using XDA App
doesnt work for me - failed at file_getprop("/system/build.prop"
this update seems to be for build GRH78 - GRI40 ie 2.3.1 to 2.3.3
Im on 2.3.2 .......
any idea's???
moon-unit said:
doesnt work for me - failed at file_getprop("/system/build.prop"
this update seems to be for build GRH78 - GRI40 ie 2.3.1 to 2.3.3
Im on 2.3.2 .......
any idea's???
Click to expand...
Click to collapse
same here..... hmmm
krohnjw said:
If your bootloader is unlocked then rooting is as easy as flashing CWM and flashing the SU binary.
If the bootloader is locked then the changelog indicates that you will not longer be able to use fastboot boot to load CWM and root that way.
With that said, I applied a lot of updates on my Nexus One without losing root and kept the boot loader locked the whole time. You'll need to pay attention, but you should be able to do the following.
Download the SU binary zip and place that on the SD card.
The OTA will not overwrite CWM until it actually boots. So, after you apply the OTA boot directly into recovery and apply the SU zip. This will give you root. (Just pay attention and hold vol up when it goes to reboot)
When you subsequently load up android CWM will be overwritten. At this point you can use the flash_image binary to manually flash CWM to recovery (or potentially ROM Manager).
Click to expand...
Click to collapse
So what your saying is we can ( Possibly ) install 2.3.3 via the link with rooted devices with an unlocked bootloader ( if the 2.3.3 does not lock bootloader / root ) and then just re install superuser e.c.t and were away ?
Same here, update fails. I am on 2.3.2 and Stock non-rooted.
hutzdani said:
So what your saying is we can ( Possibly ) install 2.3.3 via the link with rooted devices with an unlocked bootloader ( if the 2.3.3 does not lock bootloader / root ) and then just re install superuser e.c.t and were away ?
Click to expand...
Click to collapse
Yes - if you're unlocked then you'll only need to remove the isntall-recovery.sh and reflash CWM/su and you're golden.
It's a bit trickier for users who rooted without unlocking the boot loader and do not want to unlock at this point.
Looks like this is for GRH78, NOT GRH78C- we'll have to wait for that package still.
Update is for build number GRH78 only :-(
Wow!
Thx)
SupaDupaFly24 said:
Update is for build number GRH78 only :-(
Click to expand...
Click to collapse
Yeah, that is, only for 2.3.1 until now.
We'll have to wait for the GRH78C (2.3.2) build update.
this really pisses me off. i was on 2.3.2 and i got the ota but when i tried to install it from cwm it didn't work. so then when i saw this one i gave up on the one i had and now its gone. turns out i should've just did a logcat and got the one for 2.3.2.
oh well it'll be up soon
Sweet. I was trying to get to stock ROM and i was on 2.3.1
2.3.3 Flashed just perfectly
I did a nandroid backup to 2.3.1 and then installed the update and it worked fine.
Please, Could you make step by step guide, how to apply update from that link on stock, nonroot device. Thanks.
Sent from my Nexus S using XDA App
The phone is stuck at 2.3. I'm puzzled to say the least. I attempted to manually download and install both 2.3.2 and 2.3.3 with the same result, the install was aborted with an error related to my /system/build.prop file. I suspect I need 2.3.1 before I can go to 2.3.2 or 2.3.3 but I see no way to update to 2.3.1. I just replaced a Vibrant with the Nexus S for the NFC features and I need 2.3.3 on my phone to get the latest NFC updates. I'm stuck. I called T-Mobile and Samsung and neither was any help. I bought the phone unlocked and swapped by sim card from my Vibrant to the Nexus S. The phone reports no system updates available. I don't want to root the phone at this point, I just want to update from 2.3.0 to 2.3.3. Anyone know what to do before I return it to Best Buy? It's not much use to me as a development device if I can't update it. Thanks.
Grant
I finally found a link to the full 2.3.3 ROM that allowed me to finally update.
i was stuck on 2.3.1 and my I updated to 2.3.3 without any problems, i thought at first i would need 2.3.2 but it worked and now i'm on 2.3.3.
Also to anyone who cares, haven't lost my data connection yet after upgrading it to 2.3.3
ukchucktown said:
The phone is stuck at 2.3. I'm puzzled to say the least. I attempted to manually download and install both 2.3.2 and 2.3.3 with the same result, the install was aborted with an error related to my /system/build.prop file. I suspect I need 2.3.1 before I can go to 2.3.2 or 2.3.3 but I see no way to update to 2.3.1. I just replaced a Vibrant with the Nexus S for the NFC features and I need 2.3.3 on my phone to get the latest NFC updates. I'm stuck. I called T-Mobile and Samsung and neither was any help. I bought the phone unlocked and swapped by sim card from my Vibrant to the Nexus S. The phone reports no system updates available. I don't want to root the phone at this point, I just want to update from 2.3.0 to 2.3.3. Anyone know what to do before I return it to Best Buy? It's not much use to me as a development device if I can't update it. Thanks.
Grant
Click to expand...
Click to collapse
Well, I can tell you how to do this but you'll have to boot a custom recovery. No flashing no nothing, just boot it. You'll also lose all your apps. If that all sounds okay then follow the steps below:
You'll need to download a few files:
Download the Google Nexus S CWM file here (its at the bottom of the list) - http://www.koushikdutta.com/2010/02/clockwork-recovery-image.html
Download the Android SDK here and install it following the instructions included on the page - http://developer.android.com/sdk/index.html
And finally download the Stock 2.3.3 NANDroid backup here - http://www.mediafire.com/?weataw4w7v1anl4
Now that you've got those files and everything installed (I'm going to assume you know a bit about running android commands through a computer but if not I can elaborate later) put the recovery image in the Android SDK tools folder and open a command line program. CD to the directory of your SDK tools folder and type this command in:
Code:
fastboot boot recovery-clockwork-3.0.0.5-crespo.img
Once you're in CWM use the volume buttons to highlight and the power button to select the highlighted option. Now go into mounts and storage and mount USB storage. Unzip the Stock 2.3.3 file to the root of your SDcard (or just move the unzipped folder, all of it exactly as it unzips there). Eject the drive from your computer, and then unmount it on the phone. Now go to backup and restore and choose restore and choose the backup in there. This will replace all of your internal storage with completely bone stock android 2.3.3
Thanks kenvan for the recovery process. I tried it and it works too. I needed the right files then I was able to update. All I could find initially were update zips that patched from one minor release to the next. I finally tracked down the full 2.3.3 ROM on another thread.
Grant
Im rooted with an unlocked bootloader, if I flash the full rom via the update.zip method I am understanding that I will lose root and it cannot be obtained again using the fastboot OEM unlock method?
Sent from my Nexus S using XDA App
Safest Easiest Way To Keep Root With 2.3.3
Bronk93 said:
Im rooted with an unlocked bootloader, if I flash the full rom via the update.zip method I am understanding that I will lose root and it cannot be obtained again using the fastboot OEM unlock method?
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
if you have clockwork mod use this as a restore and you will have a rooted 2.3.3 its the easiest way to do it.
http://www.mediafire.com/?c1ww7zb837uycbk
just unzip and put the backup folder in your clockworkmod recovery folder boot into recovery and restore 2.3.3 takes 2 minutes and you will boot up with a rooted 2.3.3
Take a look at this:
http://forum.xda-developers.com/showthread.php?p=10495201
I had the same problem, if this is your case I suggest you to contact google and they will solve your problem.
EDIT: I see you solved it.
All,
I have updated to 2.3.4, lost root as expected and tried to reroot 2.3.4.
I had no luck, once i ran ./Gingerbreak the script would sit and not do anything after displaying the initial text.
Has anyone successfully done this?
I thought about updating with the prerooted 2.3.4, but the devs started to add all sorts of stuff in there, and right now that is not what I am after.
Thanks!
Also anxiously waiting for a 2.3.4 root option.
- No custom boot loader means I can't use the current SU.zip process.
- I didn't unlock the boot loader on the phone and now really don't want to go through the hassle of having the phone reset when I do... too much on it.
- Can't do a nandroid backup (to unlock) because I don't have root.
Catch 22 circle. Am keeping my eyes open, hopefully someone comes up with an alternate method. Once I get root again I will unlock the boot loader after making a backup so this doesn't happen again.
51Cards said:
Also anxiously waiting for a 2.3.4 root option.
- No custom boot loader means I can't use the current SU.zip process.
Click to expand...
Click to collapse
Custom bootloader? Just unlock the one you have and flash a new recovery. It takes a whopping 3 minutes to flash recovery, then SU, and reboot. If you want to keep everything stock so you can OTA, the stock ROM will overwrite the recovery when you boot and you'll end up with rooted stock ROM with OEM recovery. If you want to then flash a custom rom, you can do so through ROM manager.
Want to unroot? Download the FRG33 passimg.zip and boot into bootloader.
This stuff is stupid easy on the N1.
ATnTdude said:
Custom bootloader? Just unlock the one you have and flash a new recovery.
Click to expand...
Click to collapse
Ok so feeling like a newb here.
First I meant 'custom recovery', not 'custom boot loader'... mixup in terms on my part.
But to put in a custom recovery I need to unlock the phone. Once I unlock the boot loader doesn't the phone reset to factory state? I had seen that mentioned several times and in the unlock video I was watching. After the phone was unlocked it went back to "Welcome to Android" etc on the next startup. Have far too much in the phone I don't wish to loose and I can't Nandroid it without root.
Thanks for the info.
I had used Gingerbreak on my 2.3.3 - after 20 seconds of searching on XDA I found that you can simply install ROM Manager, flash RA custom recovery, boot into recovery, remove signature verification, flash update.zip followed by su.zip and you keep root .... all this WITHOUT an unlocked bootloader...
I am attempting to keep my phone as stock as possible and only root to block ads and sometimes push some new app that google wont release to the n1.
I really don't want to mess with custom anything on my daily driver (used for business also). I have my g1 for that
SO....has anyone used gingerbreak successfully on 2.3.4?
Disregard. I misread the post.
MitchRapp said:
I had used Gingerbreak on my 2.3.3 - after 20 seconds of searching on XDA I found that you can simply install ROM Manager, flash RA custom recovery, boot into recovery, remove signature verification, flash update.zip followed by su.zip and you keep root .... all this WITHOUT an unlocked bootloader...
Click to expand...
Click to collapse
Yeah, the ROM manager option would have worked well before I did the OTA for 2.3.4 and lost root. I will keep it in mind for the future, thanks!
I'm sure there's a better, faster, more direct way, but here's how I went from 2.3.4 stock to 2.3.4 rooted without unlocking the bootloader.
1. Flash FRG33 as passimg.zip on SD card.
2. Flash FRG33 to GRI40 as update.zip on SD card using stock recovery.
3. Root GRI40 2.3.3 using Gingerbreak.
4. Install ROM Manager app and install Clockworkmod Recovery.
5. Open GRI40 to GRJ22 update zip file and REMOVE Recovery folder from it.
6. Boot into Clockworkmod Recovery and flash modified update.zip from step 5.
7. Install SU.zip from Clockworkmod right.
Voila! Rooted GRJ22 2.3.4 with locked bootloader. Lot of steps, but I don't think it took more than 10-15 minutes.
Exactly what I did. Works smoothly and you're all set in minutes. As long as you had root in the first place, on 2.3.3.
Sent from my Nexus One using XDA Premium App
DownloaderZ said:
All,
I have updated to 2.3.4, lost root as expected
Click to expand...
Click to collapse
This was the same lesson I learned when I rushed in with Froyo --> GRI40 update the moment it became available. I lost my root and had to wait for Gingerbreak release. Now when they release OTAs, I wait until I understand how to keep the root under the new update before accepting it. Seems like a better approach to me.
Sent from my Nexus One using XDA App
GnatGoSplat said:
I'm sure there's a better, faster, more direct way, but here's how I went from 2.3.4 stock to 2.3.4 rooted without unlocking the bootloader.
1. Flash FRG33 as passimg.zip on SD card.
2. Flash FRG33 to GRI40 as update.zip on SD card using stock recovery.
3. Root GRI40 2.3.3 using Gingerbreak.
4. Install ROM Manager app and install Clockworkmod Recovery.
5. Open GRI40 to GRJ22 update zip file and REMOVE Recovery folder from it.
6. Boot into Clockworkmod Recovery and flash modified update.zip from step 5.
7. Install SU.zip from Clockworkmod right.
Voila! Rooted GRJ22 2.3.4 with locked bootloader. Lot of steps, but I don't think it took more than 10-15 minutes.
Click to expand...
Click to collapse
I'm looking to download all the files for this so I'm set from the start. I found FRG33 here but I haven't found the GRI40 update yet (although I haven't really looked yet either, that's not my question). I'm wondering, the site I listed has FRG83 as well as 33, does it matter which to use? 33 mentions a possible error.
What's the deal?
Thanks,
I think you should be able to use FRG83 instead. All you really need is something that can be named passimg.zip installed by the bootloader itself.
I got the GRI40 update from here:
http://android.clients.google.com/p...b119f8.signed-passion-ota-102588.656099b1.zip
GRI22 update:
http://android.clients.google.com/p....signed-passion-GRJ22-from-GRI40.71d2f9ec.zip
That sucked!!! I lost all my settings and apps when I moved back to froyo?? I wasn't expecting that
Oh yeah, I forgot about that. Flashing PASSIMG.zip wipes out everything because it's a full flash.
brettbellaire said:
That sucked!!! I lost all my settings and apps when I moved back to froyo?? I wasn't expecting that
Click to expand...
Click to collapse
There is no way to downgrade Android without wiping everything, as a downgrade is only possible with leaked shipped ROMS (i.e., ROMs that re-write the entire NAND flash memory on the device...
droidexplorer said:
This was the same lesson I learned when I rushed in with Froyo --> GRI40 update the moment it became available. I lost my root and had to wait for Gingerbreak release. Now when they release OTAs, I wait until I understand how to keep the root under the new update before accepting it. Seems like a better approach to me.
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
I do that as well now. However I have some steps I figured out that work for me. It's more direct (only 2 flashes, plus su), but you have to pay attention. If you didn't already have a CWM backup though, it will wipe everything:
1) Flash to FRG33 using PASSIMG_Passion_Google_WWE_2.16.1700.1_FRG33_release_signed.zip (rename to PASSIMG.ZIP), takes you to 2.2
2) Root using Super-One-Click
3) Install ROM Manager and flash CWM
4) Flash b90257ed8cd3.signed-passion-GRJ22-from-FRG33-121341.b90257ed.zip, takes you directly to 2.3.4
5) DON'T LET PHONE REBOOT into Android, go to recovery then Flash su-2.3.6.1-ef-signed.zip
6) Remove/rename /system/etc/install-recovery.sh via ADB
7) If you have a recent backup, use CWM to 'advanced restore' the data portion.
8 ) Profit! (or root)
Step 5 may require explanation:
Android will reboot at least once during the flash, this is ok, as it loads right back into recovery. However after the second reboot, it will boot normally. You must INTERRUPT this boot process (hold power button, battery pull, etc). At this point CWM is still on there (don't know why, I thought flash was going to wipe it).
The reason you have to interrupt the boot process (for anyone who doesn't know) is because of the install-recovery.sh script. Stock android will automatically flash the stock recovery on bootup.
So boot into CWM, then flash su. After bootup up again, CWM will be gone, but we have root! So remove (I renamed) that file (/system/etc/install-recovery.sh), then reflash CWM using ROM Manager.
EDIT: After posting this, I had a thought: it should be possible to remove install-recovery.sh via CWM using ADB. That would remove the step of reflashing CWM a second time. I updated the step-by-step, but left the explanation as-is.
When I originally wrote these steps a few months ago, gingerbreak wasn't released. So I don't rely on it.
Just wondering, but would you always be safe and able to root by flashing SU.zip if you just never let it overwrite the custom recovery?
I thought you can always pull out the Recovery folder from the update zip file and it won't overwrite your custom recovery. Granted, that will require you to download updates manually rather than OTA, but that's easy enough.
GnatGoSplat said:
Just wondering, but would you always be safe and able to root by flashing SU.zip if you just never let it overwrite the custom recovery?
I thought you can always pull out the Recovery folder from the update zip file and it won't overwrite your custom recovery. Granted, that will require you to download updates manually rather than OTA, but that's easy enough.
Click to expand...
Click to collapse
In theory. It does seem to work for other devices (gTablet). I haven't had much luck with modifying the updater-script inside the zip file however. Whenever I change one, I get errors when I flash the zip. That's why I haven't tried that method.
I wanted to make my own flashable zips to tweak ROMs on my own, but never could get it to work, so I abandoned my work.
In addition though, you could just try to replace the recovery.img in the zip file with CWM. That might work too, as long as signature verification is off. I don't remember if I tried that.
EDIT: Forgot one key thing: Doing this won't prevent the OS from reflashing the stock back anyway on bootup (using install-recovery.sh). You MUST remove that file regardless, if you're on a stock ROM. If you want to remove that from the zip you can, but again requires updater-script changes. However if you want to OTA, then I'd recommend just renaming it, since some OTA's update that file. That way you can rename it back for the update.
On the GRI40 to GRJ22 update, I didn't have to do anything too complicated like modifying scripts. I simply yanked the Recovery folder out of the update and that seemed to do the trick with no error messages and CWM still intact.
Hi about 10 months ago I rooted my Wildfire with no problems using Turkeys ultimate guide from these forums.
I have got apps to sd, live wallpapers running, and all is good. However my phone is still S-on and the H Boot version is 0.80.0002.
When I was playing around with the settings in SetCPU it informed me that the binary was out of date and to update it, but when i tried it would not update as the phone is still S-on.
My question is can I S-off using Revolutionary as it is already rooted? Obviously I will back up using clockworkmod, but if I s-off the phone are there any obvious advantages apart from being able to update the binary in SetCPU?
Thanks
Are you talking about an outdated Superuser Binary? If so, you can download the latest binary here:
http://tinyurl.com/63tsg9c
And simply flash it in Clockworkmod Recovery. This will give you the updated binary and SetCPU should work fine again.
If you have to get S-OFF, then, you will have to apply the official Froyo RUU and update your HBoot to 1.01.0001 because Revolutionary doesn't support any other HBoots, including 0.80.x. Advantages include a writeable /system partition (Which enables you copy paste stuff in the /system folder on a running handset, one case in point is precisely what you described. This will allow updating of the binary), and the other advantage is enabling of Fastboot commands, which allows you to flash stuff like radio's, recoveries, nandroid backups etc directly to the phone without using Clockworkmod Recovery.
Tl;dr - You will have to completely format your device, install official Froyo, and only then can you obtain S-OFF
And simply flash it in Clockworkmod Recovery.
When you say simply flash it in Clockworkmod recovery, what do you mean? And when you say apply the official Froyo RUU and update the HBoot how can I do that as I am running Wildpuzzle ROM at the moment and it says there are no updates available, so can you explain in simple terms what steps to take?
Thanks
Flash in Clockworkmod Recovery - Same way as you installed your WildPuzzle ROM ZIP file. Turn off phone, start using Vol Down + Power, then navigate to RECOVERY, Press Power Button. Here, select "Install Zip from SDCard", then browse to "Select Zip from SDCard", and select the Zip file I linked above.
This entire process is called "flashing".
If you are still interested in getting S-OFF:
- Download the EXE WWE Froyo 2.22.405.1 RUU from here:
http://shipped-roms.com/index.php?category=android&model=Buzz
- Connect your Wildfire to your PC, run it. It will automatically proceed and perform the required steps.
- If you get s Customer ID 131, you will need to create a Goldcard using your SDCard. This an be done using GoldcardTool. The required steps and download can be found here:
http://android.modaco.com/topic/308798-pc-application-goldcardtool/
IMO, I would not recommend you to go for S-OFF since it doesn't seem you are too much inclined to stuff like these (It is not a necessity. Besides, once /system is writeable, it is a two edged sword. Messing something up there will likely cause your phone to not boot). Further, it breaks certain functions on Sense ROMs which needs an additional fix found here:
http://forum.xda-developers.com/showthread.php?t=1156713
hey man, you could also try the test version of unrevoked 3.2 and run that to s off your phone. it works on your h-boot ( i know as i have the same)
since i am new the forum wont let me post the link, its to sstop spamming :/ just search for unrevoked test 3.2 ( it has to be test 3.2 because the others wont work on the hboot to my knowlege. :/)
just download the program and run it and it should do it with no hassle.
good luck
heavy_metal_man said:
hey man, you could also try the test version of unrevoked 3.2 and run that to s off your phone. it works on your h-boot ( i know as i have the same)
Click to expand...
Click to collapse
That's totally incorrect. Rooting with Unrevoked =/= S-OFF. Besides, on the very first line the OP says he has rooted his phone using Unrevoked.
ah, sorry about that i was looking at unrevoked forever :/ just ignore me ........