Database Info

ClockworkMod Recovery 3.0.0.5

This is the latest ClockworkMod Recovery!! Instructions to install below
Downloads At bottom of page.
I am not responsible if you brick or damage your phone... blah blah blah... NANDROID FIRST cuz u never know wut might happen XD.
Method I
Flash recovery using: ADB
NOTE: This method will work while you are booting into the current recovery on the phone.
Download ClockworkMod Recovery 3.0.0.5
Copy the recovery.img to root of the SD card.
Boot the phone into recovery.
Open command prompt.
Change directory to the AndroidSDK directory & type the following commands:
adb shell
mount sdcard
flash_image recovery /sdcard/"name of recovery".img
reboot recovery
Your phone should now reboot into the ClockworkMod Recovery (orange text for 3.0+).
Method II
Flash recovery using: RomManager
Download ClockworkMod Recovery 3.0.0.5
On the SD card, go to: /clockworkmod/download/mirror.sea.tdrevolution.net/cm/recoveries.
Rename the old image there named recovery-clockwork-2.5.0.7-heroc.img to recovery-clockwork-2.5.0.7-xxx.img.
Move recovery-clockwork-3.0.0.5-heroc.img to that folder and rename it to recovery-clockwork-2.5.0.7-heroc.img.
Open RomManager and press Flash ClockworkMod Recovery and reboot the phone to recovery, you should see the orange text.
Method III
Method III
Flash recovery using: H-Boot/S-Off Only
Download HERCIMG.zip
md5: 6dcd265a51cc7090824d7f9f889b370b
Move HERCIMG.zip to root of the SD card.
Power off the phone.
Hold the Volume Down and Power buttons until the phone boots into the bootloader.
Wait for bootloader to scan and find HERCIMG.zip.
Press action to install.
The phone should now reboot into the ClockworkMod Recovery (orange text for 3.0+).
http://www.mediafire.com/?2gwhom1m06tbboy - ClockworkMod Recovery 3.0.0.5
http://www.mediafire.com/?u86sj1w22db8kbt - HERCIMG.zip
thanks to romrepo.info/wiki

It would be great if someone could leave some screenshots for me.. i dont have the emulator on this computer srry.

deke2010 said:
It would be great if someone could leave some screenshots for me.. i dont have the emulator on this computer srry.
Click to expand...
Click to collapse
Check in the dev section for my thread on how to install adb. You'll have it up and running in like 15 to 20 min tops
Root-Hack-Mod-Always™

laie1472 said:
Check in the dev section for my thread on how to install adb. You'll have it up and running in like 15 to 20 min tops
Root-Hack-Mod-Always™
Click to expand...
Click to collapse
Im using my dads computer and i cant install anything on it soo..

deke2010 said:
Im using my dads computer and i cant install anything on it soo..
Click to expand...
Click to collapse
You can do all of what the op posted on your phone. Just follow his instructions and you should be fine
Root-Hack-Mod-Always™

laie1472 said:
You can do all of what the op posted on your phone. Just follow his instructions and you should be fine
Root-Hack-Mod-Always™
Click to expand...
Click to collapse
i already have it on my phone but i cant get screenshots without the emulator on the pc which i cant install cuz its my dads computer.

When I download the recovery from my phone it downloads as a txt file. Do I rename it to recovery.img and push it that way.
Sent from my DROIDX using XDA App
EDIT nevermind I did the S Off method worked perfectly.

METHOD1911 said:
When I download the recovery from my phone it downloads as a txt file. Do I rename it to recovery.img and push it that way.
Sent from my DROIDX using XDA App
EDIT nevermind I did the S Off method worked perfectly.
Click to expand...
Click to collapse
Glad you got it working. To answer the question about .txt on the phone, others have reported that using a different browser works for downloading the .img file correctly. I think they used Dolphin browser from the market.

I tried method 2 and method 3 above without success. Trying to go from 2.5.0.1 to 3.0.0.5. Attempts to boot into recovery and then reboots again and boots normally. Suggestions?

Try the ADB method?

stayclean said:
Try the ADB method?
Click to expand...
Click to collapse
I will try that now. Quotes necessary around the filename?

No, do not use quotes.

kynov said:
I tried method 2 and method 3 above without success. Trying to go from 2.5.0.1 to 3.0.0.5. Attempts to boot into recovery and then reboots again and boots normally. Suggestions?
Click to expand...
Click to collapse
don't flash the 3.0.0.5, you don't need it for GB. the reason I think people have been having so much trouble is that the recovery is overclocked, so some phones can't handle it. same thing goes for the GB rom, if it loops and hangs etc., just flash a capped 691 kernel after the rom and gapps, it *should* work.
OK NOW - TO ALL FUTURE POSTS - PLEASE DON'T, LOL.
AOSP MADE THIS RECOVERY AND IS CONSTANTLY UPDATING IT
3.0.0.5 CAN BE FOUND IN THE 2.3 GINGERBREAD THREAD
INSTALL METHODS CAN BE FOUND ON THE THREAD "READ ME" WIKI,
DIFFERENT VERSIONS CAN BE FOUND ON ROMREPO.INFO

il Duce said:
don't flash the 3.0.0.5, you don't need it for GB. the reason I think people have been having so much trouble is that the recovery is overclocked, so some phones can't handle it. same thing goes for the GB rom, if it loops and hangs etc., just flash a capped 691 kernel after the rom and gapps, it *should* work.
OK NOW - TO ALL FUTURE POSTS - PLEASE DON'T, LOL.
AOSP MADE THIS RECOVERY AND IS CONSTANTLY UPDATING IT
3.0.0.5 CAN BE FOUND IN THE 2.3 GINGERBREAD THREAD
INSTALL METHODS CAN BE FOUND ON THE THREAD "READ ME" WIKI,
DIFFERENT VERSIONS CAN BE FOUND ON ROMREPO.INFO
Click to expand...
Click to collapse
AOSP didn't make CWM.....

stayclean said:
Try the ADB method?
Click to expand...
Click to collapse
EDIT: Managed to get 2.5.0.1 back on there. Gonna leave it as-is.

What's the clock speed on this?

theimpaler747 said:
AOSP didn't make CWM.....
Click to expand...
Click to collapse
ok Koush did, I know, but the version we are using is tweaked by him.
would you correct me if I said he made his rom, because technincally google MADE it, but he did in fact tweak it,build it,compile it, for the hero.
@aiwetir - 768

Method III worked fine for me. Just follow instructions carefully, and don't forget to do "su" first (lets terminal use root privileges).
I'm curious why RomManager doesn't update the version number. I know I'm using 3.0.0.5 because of the new orange text, but RomManager still shows 2.5.0.1
Anyone?

theimpaler747 said:
AOSP didn't make CWM.....
Click to expand...
Click to collapse
Pretty sure he tweaked cwm3.0.0.5 to make it work for our phones ... I'm sure duce didn't mean he made it made it just wrong wordage lol come on Impaler. You know aosp be a tweaker to make our phones the **** lol
Sent from my HTC Hero CDMA using XDA App

il Duce said:
ok Koush did, I know, but the version we are using is tweaked by him.
@aiwetir - 768
Click to expand...
Click to collapse
Beat me to it haha ... Impaler just hating caus3 his epic isn't as awesome as our hero's hahaha jk
Sent from my HTC Hero CDMA using XDA App

[Q] flashed wrong kernal on my xoom 3.1

I am new to this posting and asking questions. I have a xoom and rooted it and updated it with 3.1 and then I went and updated it with the new rom which came out the other day. I did something studpid and didn't wait for the resolution to the sdcard not being seen after flashing the new deodex rom. I looked on the kernal manager and when I what I thought was the latest kernal I decided to flash it. I now can only get to recovery mode and I don't want to make another mistake. Can someone tell me if I can safely do a wipe data/factory reset? Will that get me back so I can flash the deodex rom back? You dev guys are really awesome and I really appreciate all of your work. Thank you for your support.

razor532 said:
I am new to this posting and asking questions. I have a xoom and rooted it and updated it with 3.1 and then I went and updated it with the new rom which came out the other day. I did something studpid and didn't wait for the resolution to the sdcard not being seen after flashing the new deodex rom. I looked on the kernal manager and when I what I thought was the latest kernal I decided to flash it. I now can only get to recovery mode and I don't want to make another mistake. Can someone tell me if I can safely do a wipe data/factory reset? Will that get me back so I can flash the deodex rom back? You dev guys are really awesome and I really appreciate all of your work. Thank you for your support.
Click to expand...
Click to collapse
If you can get to recovery, just re-flash the rom, it includes its own kernel.

Ok I will and let you know if I am successful. Thank you

I tried to use recovery but my xoom won't see the sd card. I have adb running but really am afraid to use it without some help. Don't want to brick my xoom. I have the kernal zip but don't 1.4.4 and thought if I could flash the kernal to my xoom that would maybe fix it. I read somewhere that you shouldn't flash a zip file, so I don't know what to do. any help would be appreciated. Thank you

razor532 said:
I tried to use recovery but my xoom won't see the sd card. I have adb running but really am afraid to use it without some help. Don't want to brick my xoom. I have the kernal zip but don't 1.4.4 and thought if I could flash the kernal to my xoom that would maybe fix it. I read somewhere that you shouldn't flash a zip file, so I don't know what to do. any help would be appreciated. Thank you
Click to expand...
Click to collapse
Please don't flash any xip file through adb! Why not go into RomManager app and look for an earlier version of recovery, maybe 3.0.2.5, and flash that. A good recovery should allow you to flash from your sdcard through clockwork mod recovery.

I can't get to the rom manager app. Am I missing something? The OS won't boot up and I only have version 4 of the clockwork recovery. What should I do?

razor532 said:
I can't get to the rom manager app. Am I missing something? The OS won't boot up and I only have version 4 of the clockwork recovery. What should I do?
Click to expand...
Click to collapse
There is your problem, you did not read the warnings...DO NOT USE CWM 4.
Grab Recovery Image (solarnz-R4c-100611-1150) FLASHED THROUGH FASTBOOT from this post.
http://forum.xda-developers.com/showthread.php?t=1074979
Fastboot flash it, if you don't know how read the post or read my sig. Once you have a working recovery, try my post above.

bwcorvus said:
There is your problem, you did not read the warnings...DO NOT USE CWM 4.
Grab Recovery Image (solarnz-R4c-100611-1150) FLASHED THROUGH FASTBOOT from this post.
http://forum.xda-developers.com/showthread.php?t=1074979
Fastboot flash it, if you don't know how read the post or read my sig. Once you have a working recovery, try my post above.
Click to expand...
Click to collapse
Flash the .img file as bwcorvus says, not the .zip.
Take your time.

OK, Thank you very much,,, I will be more careful in the future. I am back up and running the new rom with an older recovery. That taught me a good lesson never to install an earlier version of a kernal and never to try and flash a .zip file from adb. Thank you for the instructions. Is there a book for "adb for dummies"? My name should be in it...
thank you again...

Np, glad you got it working. And guess what? You got to learn something .

razor532 said:
OK, Thank you very much,,, I will be more careful in the future. I am back up and running the new rom with an older recovery. That taught me a good lesson never to install an earlier version of a kernal and never to try and flash a .zip file from adb. Thank you for the instructions. Is there a book for "adb for dummies"? My name should be in it...
thank you again...
Click to expand...
Click to collapse
There is actually an ADB tutorial somewhere on this site...seriously, do a search. It had a lot of great information. I like to know what I'm doing...it makes me more nervous to just blindly follow instructions with something like this, but I'm still mostly blind (sigh).

My SGS is dying, need help to save it

Hi everybody, i wasnt sure whether to open this subject here or in "Android Software Development". sorry if i was wrong, and if i did you can transfer the topic to the right place, tnx
Few days ago i was trying to put in a rooted kernel in my sgs using odin. after clicking start the odin showed FAIL and from this moment on, the device didnt want to boot or go to recovery mode, only to download mode..
After trying abou a 1000 different other kernels i decided to try this : http://forum.xda-developers.com/showthread.php?p=22555425.. after doing step num 4, odin showed the fail mark again and from that moment on, the device wouldnt want to go to either download mode nor recovery mode.. so the situation is- the device DOESNT react to any click on any key.. JUST NOTHING
I have ordered JIG from someone.. after pluging it in and going back to download mode, is this ICS tutorial mentioned above gonna work for me or is it gonna fail again?
Btw sorry for digging like this, im just so despert for help.. TNX FOR ANY HELP!

If ur on download mode why don't you use odin to flash a stock rom instead off flashing a new kernal!
Be carefull on flashing related.. If ur on black death screen ur [email protected] a new phone!
Sent from my GT-I9000 using Tapatalk

Cus all i wanted was to switch the karnel without changing the rom and wiping my data' what would of happen if i change my rom. furthermore i did changed to stock rom as a part of the tutorial above and thats the part the phone was bricked.
btw what is a black death screan? when the phone dont respond?

Can u be more specified what kind of rom & kernal? What kind of sgs phone
Black death screen is when nothing appear on ur screen after flashing prosedure! not even a single object or image, when that time come... Ur phone is useless..
Sent from my GT-I9000 using Tapatalk

You have your kernel. Open it with 7zip, extract boot.img
Install Heimdall.
Start your GS in Download Mode
Run zadig.exe and install the correct drivers.
Put boot.img in Heimdall file.
Open cmd.exe, go to c:\heimdall (or where you put it)
type :
heimdall flash --kernel boot.img
Enjoy

barome said:
You have your kernel. Open it with 7zip, extract boot.img
Install Heimdall.
Start your GS in Download Mode
Run zadig.exe and install the correct drivers.
Put boot.img in Heimdall file.
Open cmd.exe, go to c:\heimdall (or where you put it)
type :
heimdall flash --kernel boot.img
Enjoy
Click to expand...
Click to collapse
Plus, remember to kill all Kies processes from background
PS. Since you are only flashing kernel, you won't end up with hard bricked phone..only bootloaders can mess up your phone that badly..so it's probably only driver problem or something like that..try Heimdall as suggested
Sent from my sandwiched SGS

I haven't got my JIG yet so my phone is still DEAD BLACK.. ill update the post after i'l restore the download mode..
and btw i didn't realy understand what "barome" said :
Install Heimdall.
Start your GS in Download Mode
Run zadig.exe and install the correct drivers.
Put boot.img in Heimdall file.
Open cmd.exe, go to c:\heimdall (or where you put it)
type :
heimdall flash --kernel boot.img
Click to expand...
Click to collapse
whats Heimdall is?
whats zadig.exe is and where can i get it? (or i already have it in the files from the tut and dont know it yet..)
what is boot.img and where can i get it?
and tnx again for your patient answers and ur will to help! appreciate it ALOT!

panahi said:
I haven't got my JIG yet so my phone is still DEAD BLACK.. ill update the post after i'l restore the download mode..
and btw i didn't realy understand what "barome" said :
whats Heimdall is?
whats zadig.exe is and where can i get it? (or i already have it in the files from the tut and dont know it yet..)
what is boot.img and where can i get it?
and tnx again for your patient answers and ur will to help! appreciate it ALOT!
Click to expand...
Click to collapse
Hi. With google, try to find heimdall. It's a software including zadig.
Boot.img is in your kernel's zip file.

I dont have this file (Boot.img) in the kernel's file posted in the tut above... is it supposed to be in the device itself?

What file have you in kernel's zip ?

Listen, i have downloaded 4 different zips.
1st was ICS_4.0.3_MR1-RC4.2_I9000 (the rom itself from the tut) which includes a boot file img somwhere inside of it.
2nd was odin
3rd was i9000XWJVZ 2.3.6 ROM (the stock GB rom i think) which includes 5 files : APBOOT.....md5 , CODE......md5 , CSC......md5 , MODEM......md5 , and finaly s1_odin.pit
4th and final was CF-Root-XX_OXA_JVZ-v4.3 KERNEL which includes the file
"CF-Root-XX_OXA_JVZ-v4.3-TAR.tar"

panahi said:
1st was ICS_4.0.3_MR1-RC4.2_I9000 (the rom itself from the tut) which includes a boot file img somwhere inside of it.
Click to expand...
Click to collapse
So you've got a boot.img....

Actuali i wasnt sure if thats the file u ment cus i have beent told to first flash a stock GB rom with a stock kernel and AFTER that to flash the ICS. the boot file is in the ICS rom files.
sorry for questioning u but its the second time im getting bricked becuase of others mistakes so im a bit scared.

Xoom bricked

Hi there everyone,
I have a huge problem. Last night i bricked my xoom. I was following a tutorial on this forum. and after unlocking the bootloader it told to flash a file called boot.img after doing so and typing fastboot reboot, the device wouldnt start behind the motorola logo. i tried allot of thing and also did flash some other stock android 4.0.4 boot.img files now with the last one mentioned i managed to get the xoom (wifi) to boot a little further. because the ripple movie with the motorola logo is shown. but it stucks at that movie.
Does anyone know if i can flash an image on the xoom that will atleast fix the problem of not rebooting so i can try another tutorial.
I have searched the internet for solutions, many of them linked to threads on this forum. but almost all download links in these tutorials are old and broken.
Can someone please help me unbrick my device? And maybe a link to a good working unroot tutorial for my xoom wifi with android 4.0.4.

Try get back to Stock.
Download from HERE
and do some OTA updates afterwards so everything will be up to date.
Then wipe and try again from scratch..
Worked for me perfectly just a few days ago.

If you can still get into fastboot, then its not bricked.
Get some stock images and flash them via fastboot and you'll be fine.

Cubanluke88 said:
If you can still get into fastboot, then its not bricked.
Get some stock images and flash them via fastboot and you'll be fine.
Click to expand...
Click to collapse
Indeed it worked. i downloaded the official images and flashed them im on android 3.0.1 again and all seems to work just fine now.
Next problem is i cant find a descent tutorial on this forum how to root the xoom. all download links are either removed due to copyright issues or the links are just broken.
How does it work actually?
1. I unlocked the boot loader wich is very easy.
but then? Do i need to flash a rooted image over the existing? i dont really understand how this works. I rooted my Desire HD with a good tutorial in minutes. Not many people seems to really know how to root the Xoom.
Also i would like to know if the different tutorials are for different android versions or can i aply all tutorials of rooting when i stay on android 3.0.1?
I also tried to flash a recovery.img to the recovery partition and press volume down 3 seconds after the moto logo apears but when i do i get an android robot with a big " ! " on his belly and it takes 5 minutes to load the menu. when im in it tells me there is no sdcard present when i try to flash a rooted rom (zip file).
Is there someone reading this thats willin to explain to me how to do a root the easiest way? Please if links are posted be sure everything on that thread is working. Im pretty sure i will pull it off with some push in the right direction.
Thank you!
(edit) omg im stupid, offcourse the sdcard wont work... it never worked at 3.0.1. on the xoom. can i follow this tutorial:
http://rootzwiki.com/topic/451-how-to-root-the-wifi-only-xoom-301/
Could someone read over it and see if this is a good tutorial? last time i flashed a boot.img the whole xoom got stuck... is that because i had the wrong boot.img on the wrong android version? or should boot.img always work?

Do you plan on flashing to a custom rom after rooting? If so, you can just skip rooting altogether.
I say this because I'm not particularly familiar with that rooting method you linked (though reading through it, it makes sense, all its doing is pushing the necessary files for root access to the xoom via adb). I used a rooting script flashed through a custom recovery over a year ago - unfortunately the download link seems to be broken (I might have a copy at home).
So there's a few things you can do:
1. If you just want a custom rom - download the rom zip file and store on your device. Flash TWRP (my preferred recovery) in fastboot. Boot into TWRP and flash the rom zip file.
2. If you want stock OS root access -
a) Follow those steps you linked and see what happens. If things go wrong, you should be able to just flash those stock images again.
b) Wait for me to get home and see if I have the root script. You'll need to flash a custom recovery though in order to use it.

Cubanluke88 said:
Do you plan on flashing to a custom rom after rooting? If so, you can just skip rooting altogether.
I say this because I'm not particularly familiar with that rooting method you linked (though reading through it, it makes sense, all its doing is pushing the necessary files for root access to the xoom via adb). I used a rooting script flashed through a custom recovery over a year ago - unfortunately the download link seems to be broken (I might have a copy at home).
So there's a few things you can do:
1. If you just want a custom rom - download the rom zip file and store on your device. Flash TWRP (my preferred recovery) in fastboot. Boot into TWRP and flash the rom zip file.
2. If you want stock OS root access -
a) Follow those steps you linked and see what happens. If things go wrong, you should be able to just flash those stock images again.
b) Wait for me to get home and see if I have the root script. You'll need to flash a custom recovery though in order to use it.
Click to expand...
Click to collapse
Ok thanks for your answer. Ill try to unroot with that method flashing directly to the recovery.img i also know now what i did wrong. i flashed the recovery.img not to the recovery partition but to the boot partition LOL. thats why the xoom didnt boot anymore
I see allot about Nightlies Eos, 4.1.1. is that a good rom? Does it look like the stock version?

eos 4.1.1 is simply awesome and its also pre rooted' so your bootloader is unlocked, all you gotta do now is install twrp recovery via fastboot ( my preffered recovery) then flash eos via recovery
Sent from my Xoom using XDA Premium App

sygys said:
Ok thanks for your answer. Ill try to unroot with that method flashing directly to the recovery.img i also know now what i did wrong. i flashed the recovery.img not to the recovery partition but to the boot partition LOL. thats why the xoom didnt boot anymore
I see allot about Nightlies Eos, 4.1.1. is that a good rom? Does it look like the stock version?
Click to expand...
Click to collapse
EOS is a pretty AOSP rom. No theme, though you can apply one if you like and change a few colors. There are various toggle additions you can add that make the user experience much better. It also comes with an overclockable kernel and is very very stable (despite being a nightly) The team has been supporting the Xoom for over a year and is very committed to the Xoom.
---------- Post added at 01:15 PM ---------- Previous post was at 01:11 PM ----------
sygys said:
Ok thanks for your answer. Ill try to unroot with that method flashing directly to the recovery.img i also know now what i did wrong. i flashed the recovery.img not to the recovery partition but to the boot partition LOL. thats why the xoom didnt boot anymore
I see allot about Nightlies Eos, 4.1.1. is that a good rom? Does it look like the stock version?
Click to expand...
Click to collapse
As for flashing, just gotta make sure your text is good before hitting the enter key. Recovery flash should look something like this:
fastboot flash recovery recovery.img
Click to expand...
Click to collapse
Some instructions for flashing can be found here
While that page is specifically for locking and flashing to return to stock, the commands are universal for fastboot. Hell, if you wanted to, you could manually restore a nandroid backup via fastboot and flashing images.

I can confirm that tf300t JB does install of tf700t perfectly!!!

i downloaded tf300t software. renamed recovery. went into twrp factory reset. installed recovery file. as well as JB GApps.. and im running very creamy JB on my tf700t. others say you can brick. maybe i got lucky.

so do you have to be unlocked to install this?
Sent from my ASUS Transformer Pad TF700T using xda app-developers app

im not sure. i did it unlocked via twrp. i dont know the process of doing it unlocked.

i suggest you to post a video before people start bashing you like they did for the other guy
so do you have to be unlocked to install this?
Click to expand...
Click to collapse
he said he did it with twrp...so yes you have to unlock

I'm running the TF300 also.
I also renamed & flashed the zip via TWRP.
I lost root & it appears recovery also.
I'll advise as I find out more.
So far everything else is great.

Be careful flashing the TF300 ROM. It does replace the bootloader as well, so if it bricks, you're probably hardbricked.

I can confirm that it is working

If this is a troll its a good one because i am very close to trying this myself.

its not bs, we already know its possible cause that other guy got it ota. how? mystery, but the build numbers dont lie, he has a 300 version firmware

i have a working twrp recovery. download the blob file. enter fastboot. rename the file twrp.blob
make sure your device is being read by entering adb device, device should show..then enter this
fastboot -i 0x0B05 flash recovery twrp.blob
then enter into recovery.
working on a root right now

okay guys. working jelly bean. working recovery... working root. im so happy

So would doing this slow down the processor?
By this i'm talking about the eco, standard, and performance settings.
- They would be clocked differently, or am i wrong?

ill run a benchmark right now

Thats really awesome news !
Could you maybe write a little more detailed how you got that to work ?
I for instance do not understand what "renamed recovery" in the first post means and i do not understand this part :
"download the blob file. enter fastboot. rename the file twrp.blob"
Where did you download the blob file.

oh okay so when you download the blob from twrp its a longer name. its not necessary but just convenient.
the original name is openrecovery-twrp-2.2.1.4-tf700t.blob
its just more convenient to name it twrp.blob
here is the website
teamw.in/project/twrp2/105

if there are any devs out there. will i experience any problems from only factory resetting upgrading to jb from ics. should i have qiped the system?

ultramegaman963 said:
i have a working twrp recovery. download the blob file. enter fastboot. rename the file twrp.blob
make sure your device is being read by entering adb device, device should show..then enter this
fastboot -i 0x0B05 flash recovery twrp.blob
then enter into recovery.
working on a root right now
Click to expand...
Click to collapse
Where do I download blob file from?
I assume that I'll have to have root first before I can do much else.
So I'm standing by.

You are a brave man, risking your infinity to experiment. I hope you are under warranty and able to exchange at best buy or something if you brick. I'm glad someone is experimenting though. Best of luck to you, I'll be interested to see how it all works out. If stock 300 JB runs on the infinity, I wonder if custom roms from the 300 will run too. The Hydro rom makes me jealous that we don't have such a big dev scene yet.

forgive me if i am asking a noob question but does that method need unlock?

the website is teamw.in/project/twrp2/105
and no. when you install jelly bean your root and recovery are not there anymore.
the steps i took were to flash recovery via fastboot.
go into recovery. and flash superuser (which you can get from http://androidsu.com/superuser/ )
download the Superuser-3.2-RC3-arm-signed.zip and put in the root of micro sd card
flash and you will have a successfully rooted device.