Related
has anyone accomplished the root with the updated version on a mac?? extremely stuck
bronsonb said:
has anyone accomplished the root with the updated version on a mac?? extremely stuck
Click to expand...
Click to collapse
You'll need to get android sdk for mac and use the equivilent of adb.exe.
I am in the same boat as you.... waiting... with a mac...
I've rooted it successfully using Parallels (win7) on Snow Leopard.
bronsonb said:
has anyone accomplished the root with the updated version on a mac?? extremely stuck
Click to expand...
Click to collapse
The main issue here is the lack of flashing tools for the mac. So far both Omnious and the Flash Tool are windows only.
Devtone said:
I've rooted it successfully using Parallels (win7) on Snow Leopard.
Click to expand...
Click to collapse
Well... this is one way ofcourse
bronsonb said:
has anyone accomplished the root with the updated version on a mac?? extremely stuck
Click to expand...
Click to collapse
I have.
If you have an Intel based mac, use Parallels (or VMware).
You might be able to get away with Qemu or bootcamping windows will work.
Just dont try to root from the desktop (virtual folder! the script wont work) but from root (C:\).
Also (maybe also on native windows) you have to connect the phone in 1 second or the script wil quit with error. Start the script, connect the phone, press any key to continue..
Btw, I did this on a normal laptop (Dell XPS m1530) running OSX SL 10.6.4 (99,9% native install), virtualizing Win7 to flash
bronsonb said:
has anyone accomplished the root with the updated version on a mac?? extremely stuck
Click to expand...
Click to collapse
One of those times I feel like saying "get a real computer" will fix your issue
First time i couldn't root my phone (also mac with parallels on).
I used the root files from the Bin4ry, Each time step 2 won't work.
Than reading the whole guide i saw Proyaz bunch of files with recently new firmware for x10i, an R2b020 (i think),
This time i had to try three times the root.
First time step 2 wouldnt' work, after retry of step 1 step worked. But then after step 2 i had no sudo rights?, again tried this time, in the meanwhile i was changing clothes for a party, Tada, after third time it worked flawless.
So yes, you can root from mac xD
To be completely honest, when I was new to this phone, I had a heck of a hard time finding the USB driver. I know you are supposed to install Kies, but that's a pretty big download. This 19.6 MB installer is found in the Kies files, I just decided to upload this for the sake of people who don't have the drivers yet.
Please inform me if this has already been posted/does not work.
I have NOT tested this, it should work though.
http://www.multiupload.com/IXQSQT03X7
jwl12345 said:
To be completely honest, when I was new to this phone, I had a heck of a hard time finding the USB driver. I know you are supposed to install Kies, but that's a pretty big download. This 19.6 MB installer is found in the Kies files, I just decided to upload this for the sake of people who don't have the drivers yet.
Please inform me if this has already been posted/does not work.
I have NOT tested this, it should work though.
http://www.multiupload.com/IXQSQT03X7
Click to expand...
Click to collapse
[scratches head] kies doesn't support the infuse (other than the drivers of coarse), installing kies is silly. The drivers are on the Samsung website under product support exactly where you'd expect them to be.
Kies supports my infuse...
Yea true don't get support with kies but until I installed it I never could get my phone to find what it needed to on the computer. It really is important if u end up having issues connecting and finding your phone
Sent from my SAMSUNG-SGH-I997 using xda premium
debra said:
Yea true don't get support with kies but until I installed it I never could get my phone to find what it needed to on the computer. It really is important if u end up having issues connecting and finding your phone
Sent from my SAMSUNG-SGH-I997 using xda premium
Click to expand...
Click to collapse
That's because kies installs drivers, but again the logical place to look for drivers is the Samsung product support section and they are there. Its amazing the simple things this while forum seems to ignore.
---------- Post added at 03:44 AM ---------- Previous post was at 03:40 AM ----------
Naphthoylindole said:
Kies supports my infuse...
Click to expand...
Click to collapse
Which kies functions are supported with the infuse? Can you update firmware? Can you install Samsung apps? Edit contacts? Sync media? I never tried it but as fast as I know only galaxy s phones a supported and the infuse on att is not labeled as a galaxy s. I've heard it doesn't work but I have Linux on my computer and never use windows unless I have to. I have no reason to use kies or USB drivers.
so kies works on infuse now? that would be really helpful if they had an app, because my usb driver is broken and i cant update my phone.
any help?
yes, kies supports the infuse now. and is the only proper way to upgrade to official gingerbread from att.
thats a little stupid idea to say the least...
what about people that dont have a computer, or like me their USB connection on their infuse is not working(im not the only one)?
i cant find any drivers for my infuse or ways to download the update that im pretty sure would fix my phone...they've really left me deserted and want me to pay a fee to have my phones OS reinstalled
on the infuse, gingerbread required a new bootloader which required a computer. you should have drivers loaded with kies, if not you can get them from samsung. you may have to go select the proper driver in device manager. i know it conflicts if you install adb.
The Jack of Clubs said:
on the infuse, gingerbread required a new bootloader which required a computer. you should have drivers loaded with kies, if not you can get them from samsung. you may have to go select the proper driver in device manager. i know it conflicts if you install adb.
Click to expand...
Click to collapse
This method use diff type of drivers....
http://forum.xda-developers.com/showthread.php?t=1524081
Sent from my SAMSUNG-SGH-I997 using Tapatalk 2 Beta-5
devinwithaninfuse said:
thats a little stupid idea to say the least...
what about people that dont have a computer, or like me their USB connection on their infuse is not working(im not the only one)?
i cant find any drivers for my infuse or ways to download the update that im pretty sure would fix my phone...they've really left me deserted and want me to pay a fee to have my phones OS reinstalled
Click to expand...
Click to collapse
Bro your not. My old phone had that. Go yell at them, it is probably broken. Os will not help, tried that. Its sammies fault, they say ooohhh ahhh its software. Bull, unless if yours works on other computers. IF doesnt, then go say you will cancel if they do not treat you correctly.
Oh god necrobump...
So I went from the UCKK4 leak to the newest CatyROM. I was having a lot of issues with the gallery and the music player so I decided to head back to stock for now to put a leak or a different ROM back on. I started up Odin with the pre-installed root+3e return to stock, but it got stuck so I pulled it. Then I went to full on rainbows, no DL mode, nothing. Then I used GTG's unbrick and it got stuck so I pulled again. Now I've got DL mode (regular) But Odin keeps getting stuck on factoryfs.rfs. I rebooted my computer, tried a different port, all that. I can't use another computer since I don't have a second one. I'm definitely at a loss on this one. Anyone got anything?
Redownload or try Adam's Hemidall.
Try a different cord. I had the same problem on a different rom
Sent from my SGH-I997 using xda premium
The phone won't even detect in Heimdall. I can't figure out how to use Adam's either since I've never used Heimdall. The phone does go into DL mode and the PC and Odin detect it, but that's about it
EDIT: I should asp add that when I get up to factoryfs.rfs the DL mode progress bar does show about 1/16 worth of progress.
Seriously guys... nothing else?
Kevinr678 said:
Seriously guys... nothing else?
Click to expand...
Click to collapse
Kev,
If I understood heimdall correctly, according to description, it is different from odin. it installs a different usb drivers.
I think you should give heimdall a try again.
I don't know if odin does anything to prevent heimdall from recognizing your phone or not.
UN-install all usb drivers for the phone.
assign 1 usb port just for heimdall
DL Adam's heimdall uckj4 1click
update to newest java.
put your phone in DL mode.
run 1 click.
zadig should allow you to install it's own usb driver.
if heimdall does not recognize your phone or show connected,
try rebooting windows
and try 1 click again.
if the first flash doesn't work, flash 2nd time with boatloader checked.
good luck
btw, next time you get FC's on gallery or music, it may because there were left over files from the previous rom such as thumbnails and data. you can try to manually locate theses files and delete them and their folders or flush them or even use Tibu to flush or delete the apps and then reboot and reinstall.
qkster said:
Kev,
If I understood heimdall correctly, according to description, it is different from odin. it installs a different usb drivers.
I think you should give heimdall a try again.
I don't know if odin does anything to prevent heimdall from recognizing your phone or not.
UN-install all usb drivers for the phone.
assign 1 usb port just for heimdall
DL Adam's heimdall uckj4 1click
update to newest java.
put your phone in DL mode.
run 1 click.
zadig should allow you to install it's own usb driver.
if heimdall does not recognize your phone or show connected,
try rebooting windows
and try 1 click again.
if the first flash doesn't work, flash 2nd time with boatloader checked.
good luck
Click to expand...
Click to collapse
That's the problem. I've tried all of that. I have to say, I'm very saddened by this issue. I tried Adam's one-click as well, but for some reason, my java won't allow it to open, and I do have the latest. Man, I'm really at a loss on this one... Ireally appreciate the response though. Hmm.... I'm really not sure what to do at this point.
Kevinr678 said:
That's the problem. I've tried all of that. I have to say, I'm very saddened by this issue. I tried Adam's one-click as well, but for some reason, my java won't allow it to open, and I do have the latest. Man, I'm really at a loss on this one... Ireally appreciate the response though. Hmm.... I'm really not sure what to do at this point.
Click to expand...
Click to collapse
it may be your windows. disable firewall? and anti-virus programs?
it may be helpful to borrow someone else's pc - (I had good luck with winXp), install java and try it again.
you're best bet is heimdall from what I read about it.
edit: you may have a corrupt partition at the location, i think heimdall will correct this.
qkster said:
it may be your windows. disable firewall? and anti-virus programs?
it may be helpful to borrow someone else's pc - (I had good luck with winXp), install java and try it again.
you're best bet is heimdall from what I read about it.
edit: you may have a corrupt partition at the location, i think heimdall will correct this.
Click to expand...
Click to collapse
Yeah, I disabled all that. I don't have another personally, but I may be able to borrow my sister's at some point if I can find the cable for the monitor. My brother in-law has a Mac, maybe I could use that if I could figure out how to use newer Mac softwares.
Kevinr678 said:
Yeah, I disabled all that. I don't have another personally, but I may be able to borrow my sister's at some point if I can find the cable for the monitor. My brother in-law has a Mac, maybe I could use that if I could figure out how to use newer Mac softwares.
Click to expand...
Click to collapse
You're almost there, man. If you can get heimdall to run, it will restore your phone.
qkster said:
You're almost there, man. If you can get heimdall to run, it will restore your phone.
Click to expand...
Click to collapse
I sure hope so, haha. I'm quite sad that I can't look at this gorgeous screen
Kevinr678 said:
I sure hope so, haha. I'm quite sad that I can't look at this gorgeous screen
Click to expand...
Click to collapse
try reading this thread..
http://forum.xda-developers.com/showthread.php?t=1367099
qkster said:
try reading this thread..
http://forum.xda-developers.com/showthread.php?t=1367099
Click to expand...
Click to collapse
Sorry man, had to run off and take care of a few things. Trying this now.
Having some issues getting Heimdall to recognize my phone in DL mode. I'll try a few more things before I head off to bed.
make sure you go through the device options and choose the correct device drivers
qkster said:
make sure you go through the device options and choose the correct device drivers
Click to expand...
Click to collapse
I've done that with the Samsungcomposite drivers or whatever with zadig. I'm just having no luck getting it to connect :/
Kevinr678 said:
I've done that with the Samsungcomposite drivers or whatever with zadig. I'm just having no luck getting it to connect :/
Click to expand...
Click to collapse
hmm...i remembered similar problems when i had tried odin first after all the kies and sammy drivers etc - i think it may have borked my usb to recognize heimdall
almost gave up until i tried heimdall first on a different PC...worked immediately.
i guessing your window version and usb drivers may be corrupt...
If you don't have another pc, un-install generic usb drivers and then re-install or try a new usb adapter or hub may fix it.
Maybe reinstall windows?
I may even give it a shot with a virtual box running XP if that'll work.
I have to get up early tomorrow morning, so I'm gonna pick this back up later tomorrow. Thanks a lot for all the help qkster. Hopefully I can get this baby up and running again.
no prob..good luck
Okay I have searched and searched through these forums through and through and there is no possible way the root a Droid 2 Global. I have tried all the ways listed here Pete's way the One Click and the Superone Click and I tried Z4root and that didn't work either! Is there a new way to do this???(When I had my HTC Eris that was unrootable too.) I think Im gonna give up and on my next upgrade I'll probably just get an iPhone 4s or something, because any phone I touch will before outdated and unrootable and unable to flash any of the cool custom roms and play emulators and crap. I'll just an iPhone 4s and talk to siri.
Thanks anyway for all the help guys and thanks developer for all your hard work!!!
-Mars
you're doing something wrong
edit: did you enable usb debugging?
how far did you get?
and miui ics is a cool rom
thousands have rooted their global
at least hundreds anyways
Which stock version are you on? Froyo, GB...
War-Rasta said:
Which stock version are you on? Froyo, GB...
Click to expand...
Click to collapse
Pete's root is suppose to work on froyo too
Sent from my DROID2 GLOBAL using xda premium
Z4root will NOT work on stock 2.3.3. I've been using a Droid 3 one click root tool for linux and it's been working without fail. I've noticed this tool also works on the regular D2. Z4root will only work with the original stock.
EDIT: As far as cool roms, I'm using MIUI ICS. You like ICS but don't want to spend 700 bucks for an off contract phone? That's right. Your D2G runs it just fine lol.
MIUI isn't really ICS. It's just bits and pieces of the framework.
Gasai Yuno said:
MIUI isn't really ICS. It's just bits and pieces of the framework.
Click to expand...
Click to collapse
Diced, mixed, or blended, it's still the best rom I've used
I am using Gingerbread.
System Version 4.5.608.A956
Android Version 2.3.3
What does the DROID3 One-Click Root script tell you? Any errors while you run it?
Gasai Yuno said:
What does the DROID3 One-Click Root script tell you? Any errors while you run it?
Click to expand...
Click to collapse
Nothing. Once it finds the phone and the rooting process begins it will say running expoit 1 of 3 (setting up symlink) and it will remain at the reboot screen forever!
my phone says:
Bootloader DO.11
Battery OK
OK to program
Transfer Mode:
USB
then nothing happens!
This time I got the "server not running" error!
Make sure your phone is set to PC mode with USB debugging on. I usually have to run the script twice. The first time it doesn't do anything. End it and start it again and it works for me every time.
Also, as far as MIUI ICS, it's technically android 2.3.7 but it's still ICS to me lol. It's enough like it to make me happy.
xero925 said:
Nothing. Once it finds the phone and the rooting process begins it will say running expoit 1 of 3 (setting up symlink) and it will remain at the reboot screen forever!
my phone says:
Bootloader D0.11
Battery OK
OK to program
Transfer Mode:
USB
then nothing happens!
Click to expand...
Click to collapse
Have you tried pulling the battery without unplugging the phone from the PC and closing the script's window?
So that it boots normally and continues.
Gasai Yuno said:
Have you tried pulling the battery without unplugging the phone from the PC and closing the script's window?
So that it boots normally and continues.
Click to expand...
Click to collapse
I'm gonna try that now! Standby...
Nope that didn't work! I didnt think was going to either!
I just tried the latest version of SuperOneClick and again with this screen on my phone:
my phone says:
Bootloader D0.11
Battery OK
OK to program
Transfer Mode:
USB
I'm starting to think somehow that this screen somehow not allowing me the further root my phone! With the SuperOneClick the program running and then immediately stopped responding!
Any ideas?
what is the latest version?
I thought you just need it in usb charge mode and have usb debugging on
edit: I don't see a SuperOneClick that works with GB
---------- Post added at 03:49 PM ---------- Previous post was at 03:18 PM ----------
xero925 said:
I just tried the latest version of SuperOneClick and again with this screen on my phone:
my phone says:
Bootloader D0.11
Battery OK
OK to program
Transfer Mode:
USB
I'm starting to think somehow that this screen somehow not allowing me the further root my phone! With the SuperOneClick the program running and then immediately stopped responding!
Any ideas?
Click to expand...
Click to collapse
try petes with a different computer
HTML:
http://www.psouza4.com/Droid3/
1. Make sure you have Motorola drivers installed.
2. Download and unzip 'MotorolaOneClickRoot_psouza4'
3. On your phone: Settings > Applications > Development > USB debugging(check box)
4. Plug phone into computer and select "Charge Only" mode
5. Navigate to 'MotorolaOneClickRoot_psouza4' folder and run 'MotorolaOneClickRoot.exe'
6. Now just follow the instructions in the command window and unlock the phone after each reboot.
For Windows XP users having trouble try this -> v7 .bat One Click
edit: are you trying to using a computer with usb 1.0?
if that doesn't work, maybe sbf
Hi,
i am definitely not an expert, in fact everything i know about android i learned from reading other people's threads but i managed to root my droid 2 global yesterday using superoneclick.
the first time i tried to run it the program froze up in the middle of the process and wouldn't do anything, including close. while i was trying to figure out how to fix i came across a post that said to start the program while usb debugging is off and then turn it on when it says waiting for device so i tried that and it actually worked. go figure.
i have no idea if it will work for you or not but i thought i would share in case you wanted to give it a try.
crazydz said:
Hi,
i am definitely not an expert, in fact everything i know about android i learned from reading other people's threads but i managed to root my droid 2 global yesterday using superoneclick.
the first time i tried to run it the program froze up in the middle of the process and wouldn't do anything, including close. while i was trying to figure out how to fix i came across a post that said to start the program while usb debugging is off and then turn it on when it says waiting for device so i tried that and it actually worked. go figure.
i have no idea if it will work for you or not but i thought i would share in case you wanted to give it a try.
Click to expand...
Click to collapse
Thank you!!!! That worked!!! I can confirm SuperOneClick v2.3.3 works on a D2G running 2.3.3!!!!
Im using Barnacle wireless tethering and gonna flash a custom rom later today!!
Thank you guys so much helping and I plan to donate and support you efforts here!!
the instructions are on the SuperOneClick v2.3.3 thread
http://forum.xda-developers.com/showthread.php?t=803682
Turn USB Debugging OFF
Click Root
When it says: Waiting for Device, Turn USB Debugging ON
It'll now run RATC
When it says: Starting ADB Server...
Turn USB Debugging OFF
Turn USB Debugging ON
Turn USB Debugging OFF
All BEFORE it says "Waiting for device..." again
Click to expand...
Click to collapse
I rooted my tablet and it worked fine. I then proceded to modify my build.prop file. My friend sent me his to work from but i mistakenly copied it over directly. Now the tablet will not boot. How can i restore to factory or whatever i need to do?
(please spare me from the "you shouldn't have done that" speech, trust me i know lol)
need more info
what model number do you have, what can you get into, what cant you get into etc
lowgoz said:
need more info
what model number do you have, what can you get into, what cant you get into etc
Click to expand...
Click to collapse
sorry, late night, not really with it lol
its model tf101 US version and it has the latest ICS firmware, stock recovery. i can get it to load the recovery screen with the wipe data option. sorry for my poor terminology im new to the whole android rooting stuff.
You can download the latest firmware from Asus website.
Unzip it to get the zip file from inside and put it on your external sd card. Boot into recovery and let it flash the ROM again.
Plenty of thread to show step by step if needed.
You could also try to adb push the original file to your tf
baseballfanz said:
You can download the latest firmware from Asus website.
Unzip it to get the zip file from inside and put it on your external sd card. Boot into recovery and let it flash the ROM again.
Plenty of thread to show step by step if needed.
You could also try to adb push the original file to your tf
Click to expand...
Click to collapse
i've already tried this. it just gives me the dead android with a red exclamation point. also for some reason my windows pc says "the device cannot start" and im unable to use adb.
What is the serial number of your tf?
Hopefully it's one that's nvflash compatible
baseballfanz said:
What is the serial number of your tf?
Hopefully it's one that's nvflash compatible
Click to expand...
Click to collapse
dont think it is, starts with B90
i think the mods rudely removed my post in general forum where i was actually getting some help, but whatever. still need help here if anyone has any ideas.
I think you have several options-
1) use adb to fix your build.prop file. This can be done in the rom or recovery. There are adb guides coming out of the woodworks on here. If windows doesn't recognize your device, then get linux or a mac and kick windows to the curb. Nothing but grief.
2) install the correct build.prop via a flashable zip. You can extract the build.prop from the system dump I have in the dev section. Yeah, it's a slow download, but I'm working on something to move it to a faster server.
There's no easy fix... yet. adb will be the "easiest" fix.
gee one said:
I think you have several options-
1) use adb to fix your build.prop file. This can be done in the rom or recovery. There are adb guides coming out of the woodworks on here. If windows doesn't recognize your device, then get linux or a mac and kick windows to the curb. Nothing but grief.
2) install the correct build.prop via a flashable zip. You can extract the build.prop from the system dump I have in the dev section. Yeah, it's a slow download, but I'm working on something to move it to a faster server.
There's no easy fix... yet. adb will be the "easiest" fix.
Click to expand...
Click to collapse
ok well heres the issue. earlier way early this morning when this first started i was able to adb in, saw it was going in an infinite loop in logcat. now for some reason windows, and i've tried 3 installations of it, says the device cannot start. to me it sounds like something weird with the device. any ideas?
The exact same thing happened to me. I booted into recovery and restored from a nandroid backup. Maybe their is a way you can still install recovery and you someone can lend you their nandroid?
roflcopterofl said:
The exact same thing happened to me. I booted into recovery and restored from a nandroid backup. Maybe their is a way you can still install recovery and you someone can lend you their nandroid?
Click to expand...
Click to collapse
i think its too late for that now, adb wont work. im guessing now maybe the recovery isnt working because i had a newer version of the os than i can get a copy of right now. anyone have/know where i can get 9.2.1.17 fw?
If he is getting the dead android, it sounds like he has a stock recovery.
regarding adb, if windows won't start, then get a linux live cd. I think rebound128 has a minimal one in the dev section for nvflash rooting, but it will probably work. Or you can download a ubuntu live cd and boot from there.
one other option would be to wait until asus releases the 9.2.1.17 firmware on their site and download that. You should be able to flash it without the dead android. the 8.6.5.21 won't work because it won't let you install to a previous version. You can only install your current version or later. In your case, that would be 9.2.1.17.
At this point, I would say that windows is holding you back. I wish I had a $1 for every person that gets screwed over by windows- I would be as rich as Bill Gates used to be.
gee one said:
If he is getting the dead android, it sounds like he has a stock recovery.
regarding adb, if windows won't start, then get a linux live cd. I think rebound128 has a minimal one in the dev section for nvflash rooting, but it will probably work. Or you can download a ubuntu live cd and boot from there.
one other option would be to wait until asus releases the 9.2.1.17 firmware on their site and download that. You should be able to flash it without the dead android. the 8.6.5.21 won't work because it won't let you install to a previous version. You can only install your current version or later. In your case, that would be 9.2.1.17.
At this point, I would say that windows is holding you back. I wish I had a $1 for every person that gets screwed over by windows- I would be as rich as Bill Gates used to be.
Click to expand...
Click to collapse
im hearing that from everyone i talk to but in this case i dont think its windows thats causing the problem. like i said, i've tried THREE different installations of windows, and none of them pick up the tablet properly, they see "ASUS Android MTP Device" for some reason, and then it says that device isnt working properly. im probably just gonna wait till asus releases the new firmware. that will definately work....right?
joshcrumley100 said:
im hearing that from everyone i talk to but in this case i dont think its windows thats causing the problem. like i said, i've tried THREE different installations of windows, and none of them pick up the tablet properly, they see "ASUS Android MTP Device" for some reason, and then it says that device isnt working properly. im probably just gonna wait till asus releases the new firmware. that will definately work....right?
Click to expand...
Click to collapse
just tried it on linux, adb wont detect the device, so no luck there. im just hoping the .17 firmware will work on it, if not idk what to do.
In linux, with the TF plugged into the USB, what do you get when you type "lsusb" ??
gee one said:
In linux, with the TF plugged into the USB, what do you get when you type "lsusb" ??
Click to expand...
Click to collapse
it had Asus Transformer or something like that, it had it listed, but thats all. couldnt interact with the device.
Perhaps adb/debugging is not activated in the rom?
I think you'll have to wait until Asus releases a new update, although the last update checked the md5 sum of the build.prop file, so if you made any changes it won't flash.
gee one said:
Perhaps adb/debugging is not activated in the rom?
I think you'll have to wait until Asus releases a new update, although the last update checked the md5 sum of the build.prop file, so if you made any changes it won't flash.
Click to expand...
Click to collapse
Wait so you're saying even after i get the new firmware it still may not work? What a load of BS...
Originally Posted by gee one
Perhaps adb/debugging is not activated in the rom?
I think you'll have to wait until Asus releases a new update, although the last update checked the md5 sum of the build.prop file, so if you made any changes it won't flash.
Click to expand...
Click to collapse
Wait so you're saying even after i get the new firmware it still may not work? What a load of BS...
Click to expand...
Click to collapse
Sorry for the confusion- I think the full 9.2.1.17 rom that asus posts on their website will work, as long as it checks the rom version in recovery default.prop. It's not clear to me how it checks the "rule" that prevents downgrading. It's a maybe, but there's still a chance.
sent from my cyanogen(mod) vision