Develop Bugs

[RECOVERY]Samsung Galaxy W i8150 RZRecovery

I'm very happy to announce, that a developer raidzero from rootzwiki forum, has made us a fully working recovery for Samsung Galaxy w i8150!
You can download it from here:
DOWNLOAD
TEMPORARY LINK .... USE THIS IF FIRST ONE DOESN'T WORK
THANKS TO andynroid FOR PROVIDING LINKS!
Flashing recovery is very simple, all you need is root access on your phone, and adb on computer. You just copy downloaded recovery on internal sdcard. Then disconect phone from copmuter. Make sure that USB debugging is on. Now connect it again but don't connect phone memory (computer shouldn't see sdcard and internal memory in Windows explorer), open command prompt and got directory where adb is installed, now enter this:
Code:
adb shell
$su
#dd if=/sdcard/RZR-2.1.4-ancora-rec.img of=/dev/block/mmcblk0p13
This is all. Now turn off phone and turnd it on like this: hold Volume Up + Home + Power button, when Samsung sign appears relese power button but still hold other two, until recovery is loaded. Bamm you are in, and ready to flash something, or backup ! Expolre the recovery, it has a lot of options, you can even choose what color of menus you want .
I would like to thanks raidzero again for all his effort he made! And also big thanks to arco68,for much need informations he provided!
We can now expect, that when developing his recovery and adding new goodies, this recovery will follow others!

great news!! Thanks for your effort!
Has anyone had a chance to test the Recovery?

Will this work on the Samsung Exhibit II?

thanks mate.downloading now. just in case it needs to be recovered. after this we would see custom roms developed by our developers here..

klingel_One said:
great news!! Thanks for your effort!
Has anyone had a chance to test the Recovery?
Click to expand...
Click to collapse
I've tested it and it works
radgoos said:
Will this work on the Samsung Exhibit II?
Click to expand...
Click to collapse
I wouldn't bet that this will work on Exibith II cause every phone has different partitions.

after giving me the command you said to me reacts to: permission denied.. Whi?

lipanz said:
thanks mate.downloading now. just in case it needs to be recovered. after this we would see custom roms developed by our developers here..
Click to expand...
Click to collapse
Definitely...BTW can anyone adv us the rooting method Odin or....

can you show me a screen when you give the command adb?
when I try to restart the device in recovery restarts continuously and never give me the recovery menu

qzem said:
I'm very happy to announce, that a developer raidzero from rootzwiki forum, has made us a fully working recovery for Samsung Galaxy w i8150!
You can download it from here:
www.rzdroid.com/ftp/recovery/gingerbread/2.1.4/RZR-2.1.4-ancora-rec.img
Flashing recovery is very simple, all you need is root access on your phone, and adb on computer. You just copy downloaded recovery on internal sdcard. Then disconect phone from copmuter. Make sure that USB debugging is on. Now connect it again but don't connect phone memory (computer shouldn't see sdcard and internal memory in Windows explorer), open command prompt and got directory where adb is installed, now enter this:
Code:
adb shell
$su
#dd if=/sdcard/RZR-2.1.4-ancora-rec.img of=/dev/block/mmcblk0p13
This is all. Now turn off phone and turnd it on like this: hold Volume Up + Home + Power button, when Samsung sign appears relese power button but still hold other two, until recovery is loaded. Bamm you are in, and ready to flash something, or backup ! Expolre the recovery, it has a lot of options, you can even choose what color of menus you want .
I would like to thanks raidzero again for all his effort he made! And also big thanks to arco68,for much need informations he provided!
We can now expect, that when developing his recovery and adding new goodies, this recovery will follow others!
Click to expand...
Click to collapse
Thanks again, will try this ASAP, just a few questions:
Is /dev/block/mmcblk0p13 the Recovery partition??
Is it been overwritten by the dd if.......of??
Should the original stock recovery?? be backed-up/saved first??
Is there an MD5 or anything to check file integrity:
This could be used on the Device: Android File Verifier
Can the procedure be done using Terminal Emulator on the phone?

Do I need to have stock ROM for it to work?

snake873 said:
after giving me the command you said to me reacts to: permission denied.. Whi?
Click to expand...
Click to collapse
There are two possible reasons for this either you didn't run su command first, or you don't have rooted phone.
irishpancake said:
Thanks again, will try this ASAP, just a few questions:
Is /dev/block/mmcblk0p13 the Recovery partition??
Is it been overwritten by the dd if.......of??
Should the original stock recovery?? be backed-up/saved first??
Is there an MD5 or anything to check file integrity:
This could be used on the Device: Android File Verifier
Can the procedure be done using Terminal Emulator on the phone?
Click to expand...
Click to collapse
1. Yes /dev/block/mmcblk0p13 is recovery partition
2. It is gonna be overwritten with costum one.
3. You can back it up that you reverse dd command. Or I can upload original recovery.
4. There isn't MD5 cause noone made it , you only need MD5 file if you would like to flash this via Odin.
nakTT said:
Do I need to have stock ROM for it to work?
Click to expand...
Click to collapse
Do you know any custom rom for our phone ? But no it is not rom related.
snake873 said:
can you show me a screen when you give the command adb?
when I try to restart the device in recovery restarts continuously and never give me the recovery menu
Click to expand...
Click to collapse
What screen? From computer or phone? Your phone need to be turned on and booted in android when running dd command.

qzem said:
There are two possible reasons for this either you didn't run su command first, or you don't have rooted phone.
1. Yes /dev/block/mmcblk0p13 is recovery partition
2. It is gonna be overwritten with costum one.
3. You can back it up that you reverse dd command. Or I can upload original recovery.
4. There isn't MD5 cause noone made it , you only need MD5 file if you would like to flash this via Odin.
Do you know any custom rom for our phone ? But no it is not rom related.
What screen? From computer or phone? Your phone need to be turned on and booted in android when running dd command.
Click to expand...
Click to collapse
From computer
---------- Post added at 12:09 PM ---------- Previous post was at 11:41 AM ----------
ahahaha ok ok I did thank you very much for your patience

qzem......top marks for your persistence
qzem said:
There are two possible reasons for this either you didn't run su command first, or you don't have rooted phone.
1. Yes /dev/block/mmcblk0p13 is recovery partition
2. It is gonna be overwritten with costum one.
3. You can back it up that you reverse dd command. Or I can upload original recovery.
4. There isn't MD5 cause noone made it , you only need MD5 file if you would like to flash this via Odin.
Click to expand...
Click to collapse
Thanks, gotta learn ODIN first,
btw, thanks for the ODIN d/l........installed it, but still unsure how to proceed???
I have latest Kies installed on my laptop, any reason why you do not use it?? It appears to allow back-ups and restores, also new firmware d/l.
As I am new to Samsung, and also ODIN, but does using ODIN have advantages over Kies, and is it safer to upgrade new f/w with ODIN or Kies, do you lose root, or anything else??
BTW, on the MD5 thing, for the RZR-2.1.4-ancora-rec.img
I used MD5 Checksum Tool from http://www.novirusthanks.org/product/md5-checksum-tool/
to generate the MD5.
File: RZR-2.1.4-ancora-rec.img
Size: 5230592 bytes
Publisher: Unknown
Checksum (MD5): 3b9cc641aa898910b5bad911bd38f675
*File generated by MD5 Checksum Tool*
http://www.novirusthanks.org
Click to expand...
Click to collapse
I just think it is good security practice to check file integrity before applying on your device, as many things can happen, like data corruption, while transferring file from download on Laptop to SD card, and best to check file on device SD or Internal Storage with AFV against MD5 generated at source.........
which I did not check at source, but I am just illustrating for example!!
[BTW, lots of MD5's on rzdroid.com recovery ftp site, here, but not sure of our .img file
The above MD5 is what I got from the d/l file
Thanks again, I saw your stuff with raidzero on rootzwiki.........
top marks for your persistence, and a good result for all i8150 owners.

irishpancake said:
Thanks, gotta learn ODIN first,
btw, thanks for the ODIN d/l........installed it, but still unsure how to proceed???
I have latest Kies installed on my laptop, any reason why you do not use it?? It appears to allow back-ups and restores, also new firmware d/l.
As I am new to Samsung, and also ODIN, but does using ODIN have advantages over Kies, and is it safer to upgrade new f/w with ODIN or Kies, do you lose root, or anything else??
BTW, on the MD5 thing, for the RZR-2.1.4-ancora-rec.img
I used MD5 Checksum Tool from http://www.novirusthanks.org/product/md5-checksum-tool/
to generate the MD5.
I just think it is good security practice to check file integrity before applying on your device, as many things can happen, like data corruption, while transferring file from download on Laptop to SD card, and best to check file on device SD or Internal Storage with AFV against MD5 generated at source.........
which I did not check at source, but I am just illustrating for example!!
[BTW, lots of MD5's on rzdroid.com recovery ftp site, here, but not sure of our .img file
The above MD5 is what I got from the d/l file
Thanks again, I saw your stuff with raidzero on rootzwiki.........
top marks for your persistence, and a good result for all i8150 owners.
Click to expand...
Click to collapse
Well I really don't know that is better to use Kies or Odin. If you want official and (what is supposed to be tested) firmware, tha you better use Kies (but well even with kies your phone could get bricked, I've learned that from one user here ). If you want to flash latest firmware, which sometimes is not availible on all the countries, and you can't get it from Kies fast enaught, than I suggest odin is the choice. I prefere Odin, cause I don't like official stuff .
To use Odin is very simple. You need to turn on phone with Volume Down + Home + Power. When you are prompt (on hte phone),wether to conutioue od cancle, you connect phone and computer with USB cable, and choose contuinu, now you are in download mode. Then all you have to do, to choos proper .ops file (button OPS) in odin, an proper firmware (usually you choos that under One Package button, if you have one package in tar.md5), then you wait for chekcking md5. When is checked you just click Start, and wait for stuff to happen.
Don't forget that there is a possabiltiy that something might go wrong with flashing, but it is not that big one. I suggest, that you first made full nandorid backup with recovery, if something goes wrong, you can boot you phone in recovery and restore it totaly. And one more suggestin when flashing, do it with latop(if possible), so that you have battery and power cable plugged in laptop, if electricyty goes out, that you still have battery to run laptop.
And thanks for the support you guys are showing to me, since I'm not a developer. I try really hard, to get people that are willing to help us developing better roms for our phone !

qzem said:
There are two possible reasons for this either you
Do you know any custom rom for our phone ? But no it is not rom related.
Click to expand...
Click to collapse
Spot on. I just need to know if it is ROM related (that I need a ROM file on my PC).
Thanks for the reply.

Hey there, just a noob question:
Where are adb drivers installed? I'm working under Windows 7.
I tried to google this and ended up here /developer.android.com/sdk/index.html
and downloaded the first two files, but I'm unsure what to do now. Thanks in advance!

Hey qzem,
Am I right, that the adb driver should be installed, when i first installed Kies?
Is your Guide How-To Install the recovery also working on my mac? I think so, or am I wrong?
Perhaps you already figured by now, I'm new to Android!
There is one more thing i can't seem to figure out:
In foreseeable future, there are hopefully some nice custom roms for the Galaxy W. Do I have to install recovery everytime i flash a new Rom? Or is it like a bios, that has nothing to do with the actual Android System?
Thanks for your help in advance

fender90 said:
Hey there, just a noob question:
Where are adb drivers installed? I'm working under Windows 7.
I tried to google this and ended up here /developer.android.com/sdk/index.html
and downloaded the first two files, but I'm unsure what to do now. Thanks in advance!
Click to expand...
Click to collapse
For adb, you need to download Android SDK from here. Download zip file and extract it somwhere. Than go in folder where you have extract it and run SDK Manager, from there you will install adb rivers and everything else. When you are done (it could take a while, to download and install everything), open Command promnt and follow the instrucions I've wrote in first post.
klingel_One said:
Hey qzem,
Am I right, that the adb driver should be installed, when i first installed Kies?
Is your Guide How-To Install the recovery also working on my mac? I think so, or am I wrong?
Perhaps you already figured by now, I'm new to Android!
There is one more thing i can't seem to figure out:
In foreseeable future, there are hopefully some nice custom roms for the Galaxy W. Do I have to install recovery everytime i flash a new Rom? Or is it like a bios, that has nothing to do with the actual Android System?
Thanks for your help in advance
Click to expand...
Click to collapse
The same goes for mac users, there is also Android SDK for mac. You can install Kies before this, but you need both because kies includes drivers for this phone exactly. As far as recoverey goes, if it is not included in ROM, which you flash, I think you'll need to install it again. I hope that developers will include recovery in their roms.

Thanks so far qzem,
It seems like theres someone in your Cyanogenom-Forum-Post qzem, who is trying and willing to help making a custom rom. But he seeks for som guidance!
Perhaps someone with experience like, arco can take him under his wings!

Hi there,
i would like to thank you. Everything works like a charm.
Did the flash, tried the recovery.. and uaaaahhhh....
...i forgot to backup the original recovery!
can someone please, please upload it to somewhere??
thx.
Zetup-EXe

DISCONTINUED noobs guide to unlocking/locking bootloader, rooting, returning to stock

DISCONTIUED PLEASE READ THE END POST!
FIRST THINGS FIRST I TAKE NO RESPONSABILITY FOR YOU BRAKEING OR BRICKING YOU HARDWARE OF ANY KIND! THIS IS A noob's GUIDE
TO UNLOCKING/LOCKING YOUR XOOM'S BOOTLOADER, ROOTING AND ALSO A GUIDE TO GOING BACK TO STOCK. ALL WHAT I HAVE WROTE HERE
IS THANKS TO ALOT OF PEOPLE ON XDA AND VERIOUS OTHER XOOM FORUMS. THERE IS ALOT OF THREADS OUT THERE WHAT ARE VERY CONFUSING
AND THE IS A SIMPLE GUIDE AND I CHOSE TO WRITE IS TO HELP PEOPLE THAT ARNT USED TO THIS KIND OF ANDROID DEV. THIS IS A WAY FOR
WINDOWS OLY AS I DONT AND WONT HAVE A MAC SORRY
THESE STEPS ARE VERY SIMPLE FOR PEOPLE THAT KNOW HOW TO FIND THINGS ON WINDOWS AND I KNOW IT ISNT VERY EASY BUT IT EXPLAINS ALOT
IN A LOT LESS WAY AS THE OTHERS SO ITS SIMPLE.
(<> = SPACE NOT TO CONFUSE PEOPLE)
NEEDED - MOTODEV DRIVES
TIAMAT UNIVERSAL ROOT
TIAMAT 2.2.2 ROM
ORRIGINAL XOOM 3.0 FILES
THANKS TO EVERYONE - okantomi (ORIGINAL HEL FROM HIS GUIDE)
TIAMAT (FOR ALL THE FILS ROOT, ROMS, ETC)
+ EVERYONE ELSE WHO HAS HELPED
LETS GET TO IT THEN
UNLOCKING/LOCKING MOTOROLA ZOOM BOOTLODER:
1. open files from c:/USER/ android or what ever its under for android SDK/AVD (mine was in programfiles x86)
2. open command prompt
3. copy the adress of platformtools.OR.tools from SDK
4. type in cd<>the paste address
5. then type adb + enter
6. then type fastboot<>oem<>unlock or (lock to re-lock the bootloader)
7. should boot into protocal to ask if u accept all the t&c's
8. accept it all (WARNING THIS WILL FACTORY RESET AND ALL DATA WILL BE LOST)
9. it should reboot with bootloader unlocked!
10. then root!
ROOTING:
A. BEFORE WE START DO NOT FLASH A .ZIP FILE THROUGH COMMAND PROMPT AS THIS WILL CAUSE PROBLEMS!
B. GET THE UNIVERSAL ROOT FILE FROM THE TIAMAT FORUM (http://forum.xda-developers.com/show....php?t=1242241)
c. MAKE SURE U HAVE THE TABLET ON CHARGE!
d. copy the tiamat recovery to your tool files
1. open command prompt as before
2. type fastboot<>reboot<> bootloader
i. when in fastboot you may need to unplug and plug the usb back in
3. type fastboot<>flash<>recovery<>then the name of the file wich is either the name it was of download or i suggest
rename it as 3.2 root.img
4. after this is done the device can be re-started and there you have a rooted motorola xoom
RETURNING TO STOCK:
A. BEFORE WE START YOU WILL NEED THE ORRIGINAL FILES FROM THE MOTODEV SITE
(http://developer.motorola.com/products/software/)(COPY THESE TO THE TOOLS OR PROGRAM TOOLS WICH EVER YOU DIRECTED FROM
ORRIGINALY!)
1. open command prompt and navagate to the tools.or.program tools as before
2. TYPE FASTBOOT<>FLASH<>BOOT<>BOOT.IMG
3. TYPE FASTBOOT<>FLASH<>SYSTEM<>SYSTEM.IMG
4. TYPE FASTBOOT<>FLASH<>RECOVERY<>RECOVERY.IMG
5. TYPE FASTBOOT<>FLASH<>USERDATA<>USERDATA.IMG
6. TYPE FASTBOOT<>ERASE<>CACHE
7. TYPE FASTBOOT<>OEM<>LOCK
THIS WILL ONLY GIVE YOU ANDROID 3.0.1 YOU WILL HAVE TO UPDATE MANUALY AS I HAD TO IT ISNT VERY HAD EVEN THO IS TOOK ME A WHILE
TO LEARN IT.... THIS GUIDE IS FOR noob's AS IT SAYS COZ THERE ARE ALOT OF GUIDES OUR THERE WHAT ARE VERY DIFFRENT AND THIS WAY
WORKED FOR ME SO HOPE IT HELPS
if anyone needs more info just get in touch
EDIT: this has not been updated due to the fact i dont have a XOOM anymore! still pease feel free to contact me via PM if you need any help and i will try my best to help! thanks all

Thanks you for this.

I like it...I'll refer peeps to it.
Edit: Yeah, well, reading it over with the questions from scsa20 especially, who I know is very experienced, leads me to see that perhaps this guide needs a bit more work. But I really like that you wanted to share what you have learned and I agree that there are some big holes in all of the available guides. Maybe you could address the issues and incorporate scsa20's recommendations...then you'd have a really useful guide and help a lot of people.

Thanks for this, but you have to fix some links, as the are now they don't work

RETURNING TO STOCK:
A. BEFORE WE START YOU WILL NEED THE ORRIGINAL FILES FROM THE MOTODEV SITE
(http://developer.motorola.com/products/software/)(COPY THESE TO THE TOOLS OR PROGRAM TOOLS WICH EVER YOU DIRECTED FROM
ORRIGINALY!)
1. open command prompt and navagate to the tools.or.program tools as before
2. TYPE FASTBOOT<>FLASH<>BOOT<>BOOT.IMG
3. TYPE FASTBOOT<>FLASH<>SYSTEM<>SYSTEM.IMG
4. TYPE FASTBOOT<>FLASH<>RECOVERY<>RECOVERY.IMG
5. TYPE FASTBOOT<>FLASH<>USERDATA<>USERDATA.IMG
6. TYPE FASTBOOT<>ERASE<>CACHE
7. TYPE FASTBOOT<>OEM<>LOCK
THIS WILL ONLY GIVE YOU ANDROID 3.0.1 YOU WILL HAVE TO UPDATE MANUALY AS I HAD TO IT ISNT VERY HAD EVEN THO IS TOOK ME A WHILE
TO LEARN IT.... THIS GUIDE IS FOR noob's AS IT SAYS COZ THERE ARE ALOT OF GUIDES OUR THERE WHAT ARE VERY DIFFRENT AND THIS WAY
WORKED FOR ME SO HOPE IT HELPS
Click to expand...
Click to collapse
Will these steps flash back stock kernel ? I using tiamat custom kernel such as Odachi. relock bootloader with a custom kernel will make xoom bricked so these step would flash back stock kernel ???

How about turning off caps lock? Oh, and learning how to spell "break"

I'm going to nitpick this as a person who've done this a few times over (but honestly, not too bad of a guide).
TIAMAT 2.2.2 ROM
Click to expand...
Click to collapse
Although the Tiamat ROM is awesome, this guide is supposed to be for rooting only from what I can see and so pointing out to download 2.2.2 (not knowing if the user is really on the LTE version which 2.2.2 won't do they'll need 2.3.0). Sticking to just rooting is best and talk about the varies of ROMs as an extra if that's something they wish to proceed with.
UNLOCKING/LOCKING MOTOROLA ZOOM BOOTLODER
Click to expand...
Click to collapse
I think you mean "XOOM" and not "ZOOM"
1. open files from c:/USER/ android or what ever its under for android SDK/AVD (mine was in programfiles x86)
Click to expand...
Click to collapse
hmm.... what? Thinking of this from a "newb" standpoint, this step doesn't make sense. In fact, how do we even get to this first step?
4. type in cd<>the paste address
Click to expand...
Click to collapse
lol wat? For starters, you can't simply "paste" in a command prompt. If a newb has never used the command prompt, they'll be wondering how to paste, so might want to better explain how (right click and choose paste or click the little C:\ icon on the top left, go to Edit, choose Paste).
5. then type adb + enter
Click to expand...
Click to collapse
What exactly are you trying to have us achieve here?
6. then type fastboot<>oem<>unlock or (lock to re-lock the bootloader)
Click to expand...
Click to collapse
That came out of left field when the last step said to just type adb without anything else... oh, wait, you want us to type adb reboot recovery, is that right? gez, you should of made yourself clear on that.
7. should boot into protocal to ask if u accept all the t&c's
8. accept it all (WARNING THIS WILL FACTORY RESET AND ALL DATA WILL BE LOST)
9. it should reboot with bootloader unlocked!
Click to expand...
Click to collapse
I lump those both into 1 because they don't actually explain what's going on. What you need to do is press the volume down key to change the selection the volume up to select the selection then repeat
1. open command prompt as before
Click to expand...
Click to collapse
You should already be in a command prompt, if not, reopen.
2. type fastboot<>reboot<> bootloader
Click to expand...
Click to collapse
Don't you mean adb and not fastboot? You can't use fastboot if you're not in the bootloader you know.
i. when in fastboot you may need to unplug and plug the usb back in
Click to expand...
Click to collapse
I have yet to see anyone having to do this tbh
3. type fastboot<>flash<>recovery<>then the name of the file wich is either the name it was of download or i suggest
rename it as 3.2 root.img
4. after this is done the device can be re-started and there you have a rooted motorola xoom
Click to expand...
Click to collapse
This steps is all so wrong, plus the link's broken (http://forum.xda-developers.com/showthread.php?t=1242241 is the real link btw).
Simply flashing the recovery from the Universal Xoom Root won't get you rooted, the proper steps is as follows:
1) Boot into the bootloader (adb reboot bootloader)
2) Flash the recovery to the recovery partition (fastboot flash recovery recovery-Tiamat-R4c-100611-1150-cwm.img)
3) Once recovery is flashed, reboot (fastboot reboot)
4) When you get the M logo for the reboot, start pressing the volume down key until you get the option that says Recovery and press the volume up key
5) Flash the zip file containing the root files (choose "Install ZIP from SDCARD" then "Choose ZIP from SDCARD", from there, find the zip file that has the root files that you downloaded from the link posted just above)
I'm not going to touch the restoring to stock, I think I made my point that you should clean up your posts and maybe even checked it (or had someone checked it) before posting it?
(yes, I know I was hard on you but someone gotta do it)
So, yeah, looking over this, it's not really that great of a guide at all because you don't really have anything explained and just have more questions....
And to answer luyenbichta's question, the system.img image will take you out of custom kernel and rom and put you back to stock, once you flash all the images needed you can then issue the fastboot oem lock. Issuing that commend before you have the original images back on will caused you to get an error about the images not being signed, no harm, no foul.

All of this.... AND you can flash HLK75D and save yourself about three hours of manual slow updates!!
Which is available on Motodev, you shouldnt need the link to that by now. Also... no one post after me cause this thread should go buhbye.
scsa20 said:
I'm going to nitpick this as a person who've done this a few times over (but honestly, not too bad of a guide).
Although the Tiamat ROM is awesome, this guide is supposed to be for rooting only from what I can see and so pointing out to download 2.2.2 (not knowing if the user is really on the LTE version which 2.2.2 won't do they'll need 2.3.0). Sticking to just rooting is best and talk about the varies of ROMs as an extra if that's something they wish to proceed with.
I think you mean "XOOM" and not "ZOOM"
hmm.... what? Thinking of this from a "newb" standpoint, this step doesn't make sense. In fact, how do we even get to this first step?
lol wat? For starters, you can't simply "paste" in a command prompt. If a newb has never used the command prompt, they'll be wondering how to paste, so might want to better explain how (right click and choose paste or click the little C:\ icon on the top left, go to Edit, choose Paste).
What exactly are you trying to have us achieve here?
That came out of left field when the last step said to just type adb without anything else... oh, wait, you want us to type adb reboot recovery, is that right? gez, you should of made yourself clear on that.
I lump those both into 1 because they don't actually explain what's going on. What you need to do is press the volume down key to change the selection the volume up to select the selection then repeat
You should already be in a command prompt, if not, reopen.
Don't you mean adb and not fastboot? You can't use fastboot if you're not in the bootloader you know.
I have yet to see anyone having to do this tbh
This steps is all so wrong, plus the link's broken (http://forum.xda-developers.com/showthread.php?t=1242241 is the real link btw).
Simply flashing the recovery from the Universal Xoom Root won't get you rooted, the proper steps is as follows:
1) Boot into the bootloader (adb reboot bootloader)
2) Flash the recovery to the recovery partition (fastboot flash recovery recovery-Tiamat-R4c-100611-1150-cwm.img)
3) Once recovery is flashed, reboot (fastboot reboot)
4) When you get the M logo for the reboot, start pressing the volume down key until you get the option that says Recovery and press the volume up key
5) Flash the zip file containing the root files (choose "Install ZIP from SDCARD" then "Choose ZIP from SDCARD", from there, find the zip file that has the root files that you downloaded from the link posted just above)
I'm not going to touch the restoring to stock, I think I made my point that you should clean up your posts and maybe even checked it (or had someone checked it) before posting it?
(yes, I know I was hard on you but someone gotta do it)
So, yeah, looking over this, it's not really that great of a guide at all because you don't really have anything explained and just have more questions....
And to answer luyenbichta's question, the system.img image will take you out of custom kernel and rom and put you back to stock, once you flash all the images needed you can then issue the fastboot oem lock. Issuing that commend before you have the original images back on will caused you to get an error about the images not being signed, no harm, no foul.
Click to expand...
Click to collapse

Have you guys seen the movie "Super 8"?
Yeah, in that movie there is a train wreck a little bit smaller than this guide.

graymulligan said:
Have you guys seen the movie "Super 8"?
Yeah, in that movie there is a train wreck a little bit smaller than this guide.
Click to expand...
Click to collapse
OK, stop piling on...at least he tried to give back...more than I've seen with a lot of people.

Hi guys thanks for all the comment al try help u all with what worked for me as not alot did work for me I'll answer all your questions one by one after each other so bare with me and thanks again for your posative feed back
Sent from my MZ604 using xda premium

luyenbichta said:
Will these steps flash back stock kernel ? I using tiamat custom kernel such as Odachi. relock bootloader with a custom kernel will make xoom bricked so these step would flash back stock kernel ???
Click to expand...
Click to collapse
This wont brick it I have recently returned to stock as I want a ics rom or official software. As fare as im aware you can flash all models with the stock files and it is is quite easy as it says just tips the command from the original folder and DONT type adb
Sent from my MZ604 using xda premium

scsa20 said:
I'm going to nitpick this as a person who've done this a few times over (but honestly, not too bad of a guide).
Although the Tiamat ROM is awesome, this guide is supposed to be for rooting only from what I can see and so pointing out to download 2.2.2 (not knowing if the user is really on the LTE version which 2.2.2 won't do they'll need 2.3.0). Sticking to just rooting is best and talk about the varies of ROMs as an extra if that's something they wish to proceed with.
I think you mean "XOOM" and not "ZOOM"
hmm.... what? Thinking of this from a "newb" standpoint, this step doesn't make sense. In fact, how do we even get to this first step?
lol wat? For starters, you can't simply "paste" in a command prompt. If a newb has never used the command prompt, they'll be wondering how to paste, so might want to better explain how (right click and choose paste or click the little C:\ icon on the top left, go to Edit, choose Paste).
What exactly are you trying to have us achieve here?
That came out of left field when the last step said to just type adb without anything else... oh, wait, you want us to type adb reboot recovery, is that right? gez, you should of made yourself clear on that.
I lump those both into 1 because they don't actually explain what's going on. What you need to do is press the volume down key to change the selection the volume up to select the selection then repeat
You should already be in a command prompt, if not, reopen.
Don't you mean adb and not fastboot? You can't use fastboot if you're not in the bootloader you know.
I have yet to see anyone having to do this tbh
This steps is all so wrong, plus the link's broken (http://forum.xda-developers.com/showthread.php?t=1242241 is the real link btw).
Simply flashing the recovery from the Universal Xoom Root won't get you rooted, the proper steps is as follows:
1) Boot into the bootloader (adb reboot bootloader)
2) Flash the recovery to the recovery partition (fastboot flash recovery recovery-Tiamat-R4c-100611-1150-cwm.img)
3) Once recovery is flashed, reboot (fastboot reboot)
4) When you get the M logo for the reboot, start pressing the volume down key until you get the option that says Recovery and press the volume up key
5) Flash the zip file containing the root files (choose "Install ZIP from SDCARD" then "Choose ZIP from SDCARD", from there, find the zip file that has the root files that you downloaded from the link posted just above)
I'm not going to touch the restoring to stock, I think I made my point that you should clean up your posts and maybe even checked it (or had someone checked it) before posting it?
(yes, I know I was hard on you but someone gotta do it)
So, yeah, looking over this, it's not really that great of a guide at all because you don't really have anything explained and just have more questions....
And to answer luyenbichta's question, the system.img image will take you out of custom kernel and rom and put you back to stock, once you flash all the images needed you can then issue the fastboot oem lock. Issuing that commend before you have the original images back on will caused you to get an error about the images not being signed, no harm, no foul.
Click to expand...
Click to collapse
I didn't really want to explain how to flash a rom as that way you quoted didn't work for me. I no I have ****ty grammer and spelling but I did type up quick and step by step ifor noobs as this is very new to me. I have experiance with galaxy s and s2 but not in bootloaders and flashing with command prompt. Thanks anyway and I am gunna edit it shortly. But as I say I am happy to explain more to people
Sent from my MZ604 using xda premium

Tto be hoist all the people that have complain I don't no if its my english which yeah im english but I thinks its pritty straight forward that it how to unlock your bootloader, root your device and return to stock its pritty simple. I didn't add how to flash a custom rom as all the guides I found and used I flashed mine from internal memory not on and sd card. But like I say thanks for the possative comments quys
Sent from my MZ604 using xda premium

Out of curiosity, when you go from root back to stock, does the bootloader automatically lock back, or is that done seperately?
Sent from my ADR6300 using Tapatalk

300k said:
Out of curiosity, when you go from root back to stock, does the bootloader automatically lock back, or is that done seperately?
Sent from my ADR6300 using Tapatalk
Click to expand...
Click to collapse
If you tips all the commands in u will need to accept it all again. Well that's what did anyway
Sent from my MZ604 using xda premium

I still can not make this model the root someone help me? Xoom 2 media edition MZ607 wifi 32gb.

Ok I've followed 2 guides which very much the same. I'm having a lot of trouble with this, I'm trying to hard reset my xoom because someone (I don't know who) decided to put on a password lock.
When I type "fastboot oem unlock" it fails.... Please view the images below and please please please help!
Cmd prompt
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Xoom display
Sent from my CM9 Flashed GT - I9100 XDA app-developers app

Bump
Sent from my CM9 Flashed GT - I9100 XDA app-developers app

Orkane1989 said:
Bump
Sent from my CM9 Flashed GT - I9100 XDA app-developers app
Click to expand...
Click to collapse
hey sorry for no reply as i havnt got a xoom anymore if you need any help feel free to inbox me if you need any help op will be updated!

[17.12.2011][CF-Root v5.1] ICL53F - su+bb

This rooted kernel is for the "rooting beginners" and those who want to keep as close to stock as possible. CF-Root takes the kernel from an original firmware, and just adds root and busybox.
THIS IS NOT A ROM - it is only a modified kernel. You need to have the relevant firmware already on your device. You do NOT need to wipe anything for this patch. You DO need to read the instructions. PLEASE READ THE ENTIRE FIRST FEW POSTS!
Donate
There have now been nearly 1.000.000 downloads of CF-Root for various devices (see for example Galaxy S1, Galaxy Tab 7", and Galaxy S2), and many more if you include ROMs, kernels, etc that use it. Don't be a leech, buy me a beer (and use the "Thanks" button!). Imagine if every CF-Root user had donated me $1...
Main features
- The kernel is fully stock and taken from the original firmware, with just the following added:
- Superuser v3
- Busybox v1.19
- Custom boot / init scripts
- Insecure
Installation instructions
Please see the next post !
Recovery
Unlike CF-Root for various other devices, CF-Root for the Galaxy Nexus does not include any recovery, due to kernel and recovery being separate partitions on the device. This means you don't need to flash a recovery with your kernel.
Custom boot / init scripts
CF-Root will execute the following scripts if present, in the order listed:
- /system/etc/init.d/* (there can be many files here, no extensions! use "#!/system/bin/sh")
- /system/bin/customboot.sh
- /system/xbin/customboot.sh
- /data/local/customboot.sh
Please make sure you chown / chmod the scripts correctly so they can be executed. Pretty much root:root / 755.
Busybox
Busybox by default creates symlinks in /sbin. You can turn this off by executing the following:
adb shell setprop persist.busybox.nosymlink 1
And reboot your device.
Installing busybox over the included version
It is possible to install a custom busybox over CF-Root. However, this is not without risk. CF-Root makes heavy use of scripting, and many CF-Root scripts rely on the internal busybox version. If you do install a seperate busybox version (always use "stericson" installer!), install it to /system/xbin. Installing it to /system/bin will mess things up for sure. Even if you do that part right, it may still break CF-Root, so make sure to make a backup before trying.
How ?
I wrote my own toolchain to ease patching of initramfs, and that is what all this is based on. It is now used to make CF-Root for many devices!
Help! Which file do I use ?
Check Settings -> About phone -> Build number and find the matching download. YAKJU downloads are for GSM, MYSID downloads are for LTE.
Download
These are general-purpose downloads. See the posts following this one for the kernels.

Instructions
IMPORTANT: If your device is not yet OEM unlocked, both methods WILL WIPE your data ! If you are already OEM unlocked, this does not happen.
Flashing with ODIN
ODIN: Short
- Flash CF-Root-xxx-vX.X.tar (from the attached zip) as PDA in ODIN, without repartition. Done.
ODIN: Long
- Follow these instructions to the letter. Do not touch any buttons or checkboxes that are not listed below to touch!
- Unzip the attached CF-Root-xxx-vX.X.zip
- (USB) Disconnect your phone from your computer
- Start ODIN
- Click the PDA button, and select CF-Root-xxx-vX.X.tar
- Put your phone in download mode (turn off phone, then hold volume-down + power to boot)
- (USB) Connect the phone to your computer
- Make sure repartition is NOT checked
- Click the START button
- Wait for the phone to reboot
- Done (if it took you more than 30 seconds, you need practise!)
Flashing with FASTBOOT
Fastboot: Short
- Flash boot.img (inside the tar inside the attached zip) as boot. Done.
Fastboot: Long
- Unzip the attached CF-Root-xxx-vX.X.zip
- Untar the CF-Root-xxx-vX.X.tar (found inside the zip)
- Find the boot.img file that you extracted
- (USB) Disconnect your phone from your computer
- Put your phone in fastboot mode (turn off phone, then hold volume-up + volume-down + power to boot)
- (USB) Connect the phone to your computer
- If your device is not yet OEM unlocked - NOTE: This wipes your data!
fastboot oem unlock
- (1) Flash the kernel (permanent):
fastboot flash boot boot.img
- Press the power button to boot
- or (2) Flash the kernel (temporary, applies root only):
fastboot boot boot.img

Downloads
Remember: I only have the GSM version, so the LTE versions are not tested by me !
CF-Root-GGN_YAKJU_ICL53F-v5.1.zip
CF-Root-GGN_MYSID_ICL53F-v5.1.zip

-- reserving yet another post --

I have the LTE SGN and my build number is ICL53F, not MYSID

theboo7 said:
I have the LTE SGN and my build number is ICL53F, not MYSID
Click to expand...
Click to collapse
And thus you should use:
CF-Root-GGN_MYSID_ICL53F-v5.1
and specifically not:
CF-Root-GGN_YAKJU_ICL53F-v5.1

omanomanom, tastes like bacon.
*installs*

finally the greatness has arrived on the galaxy nexus

So this changes/modifies the kernal to add root? What about OTA updates?
Sent from my Galaxy Nexus using XDA App

@chainfire
if my device is ITL41F and what can i do?
can i flash your other thread ICL53F rom via odin
and then flash cf-root kernel via odin again?

kangxi said:
So this changes/modifies the kernal to add root? What about OTA updates?
Click to expand...
Click to collapse
It should not interfere with OTA updates ...
leamoor said:
@chainfire
if my device is ITL41F and what can i do?
Click to expand...
Click to collapse
There's no ITL41F version yet, not sure if I'm making one. 53F is out already ...

Chainfire said:
It should not interfere with OTA updates ...
There's no ITL41F version yet, not sure if I'm making one. 53F is out already ...
Click to expand...
Click to collapse
Thanks for the quick response. Gonna try it when I get home.
Sent from my Galaxy Nexus using XDA App

Thanks for the quick response，but i'm not get the ITL53F yet
if my version is ICL53F,how can i made oem unlock？

leamoor said:
Thanks for the quick response，but i'm not get the ITL53F yet
if my version is ICL53F,how can i made oem unlock？
Click to expand...
Click to collapse
Use this command :
fastboot oem unlock
Also, @Chainfire, you should add a warning stating that "fastboot oem unlock" wipes data

Chainfire i knew you would come with a cr-root kernel...thanks!!!
Sent from my Galaxy Nexus using xda premium

Okay i did this, but my phone is now stuck on the Google Screen with a lock on the bottom that is unlocked.
When i go back to the bootloader and select Recovery Mode.
I get an Android with a "!"
Reboots back to the Google and nothing happens =(
The only way to start my Device is in CMD and using Superboot =S
Help!

Glad to see Odin works. I like having that safety net for when ROMs attack.

chainfire, je bent een baas! grtz uit haarlem.
pitje

cdesai said:
Use this command :
fastboot oem unlock
Also, @Chainfire, you should add a warning stating that "fastboot oem unlock" wipes data
Click to expand...
Click to collapse
get out noob this thread is sacred

Will this work with buildnumber ITL41F?
If not what should I do to make use of this kernel?
Many THanks in advance

[Q] Where do I start?

I bought this Xperia ARC LT15a on Friday and have been having LOTS of trouble figuring out what to do with it. I came on here and I can say the tutorials aren't very noob-friendly because you have your own "lingo" that I dont understand whatsoever.
Now, for you guys to understand my frustration, I am coming from IOS, and was told "rooting" an Android phone is a much simpler process then jailbreaking an iPone. Well, that sure as hell has proven to be wrong since I can't even figure out how to UPDATE my phone >_>
First off, what I'm trying to do is update it to ICS. Sony says you can do it using the PC Companion, but it says I'm up to date. Same thing with the SEUS or whatever you call it...says I'm up to date. I am running Android Ver. 2.3.4 so I'm pretty sure I am NOT up to date...my IM number (or whatever) is listed as compatible with ICS so it should just update via seus or pc companion...but no...
So someone linked me to tutorials on how to FLASH ics to it... but all of the tutorials have dead links and are completely useless to me now...
Can someone PLEASE tell me what to do... I just want to update to ICS and root it, but I can't even f***ing update.........!!!! very frustrating

i felt exactly the same mate haha
but this was my first smartphone full stop lol
is it the tutorial links in general that are dead?
but do some searching, i found pretty much everything i needed on here
and now i can change ROMS, kernels, baseband etc in minutes
im sure someone more helpful will be along soon lol

Right - I haven't posted much but having been pretty much under the same level of noob frustration before I'll try to help....
First - Often, during updates you can be driven mad with reboots and reboot cycles..... hopefully, what is outlined below can be a guide to sorting out any problems you might have.
1. Backup everything.
- go to play store and search for "backup" and you'll find what you need. I use Astro File Manager for application backup and sms backup for messages. I'm not bothered about backing up anything else.
2. Unlock the Bootloader.
- download sdk starter package
Code:
://developer.android.com/sdk/index.html
- so far as I can figure this will facilitate communications between your pc and phone. CyanogenMod Wiki guides you through this process:
Code:
://wiki.cyanogenmod.com/wiki/Howto:_Install_the_Android_SDK
- download latest version of fastboot. Now, you'll never double click on this program to run it. Instead you'll run commands from your command tool which will use the program to do the work.
- record your IMEI - in dialer type in *#06# for your IMEI & write it down.
- get your phone attached in fastboot mode. to do this you turn off your phone and hold the menu button while you attach it via USB to your computer.
- see if you're connected properly. Look for command prompt (Windows Key - All Programs - Accessories). Right click on this and run as administrator. Type in the following: fastboot -i 0x0fce getvar version . It will give an obviously positive message if you are correctly connected - if not, ensure you've attached in properly.
- get code to unlock bootloader - go here:
Code:
://unlockbootloader.sonymobile.com/
and go through the process to get an unlock key. Once you have this, go back to your command prompt and type fastboot -i 0x0fce oem unlock 0xUNLOCKKEY (where UNLOCKKEY is the number you have gotten from Sony website. You should get a confirming message.
Now that you've unlocked the bootloader you need to decide what kind of kernel and ROM you want. You can regard the ROM as software whereas the kernel links the software to the hardware. This is my limited understanding anyway.
3. Now, sometimes people make standalone kernels and sometimes they are kept with the ROM.
This leaves a couple of options
- you can flash a stand-alone kernel using flashtool (
Code:
://androxyde.github.com/
). The process is pretty simple.
- Now, if you download a ROM which advises that you need to extract and flash a file called "boot.img" there is a different method. In this case your ROM zip file can be extracted to find the boot.img file.
When you get the boot.img file you can place it in C:\. Now, all advice will be to place it in the platform-tools folder which is created in step 1. It doesn't matter really so long as you point at the right place when flashing.
(I also think that you can use flashtool in flashmode to do this job....)
4. Now you have a kernel on your Xperia and seeing as you've got the bootloader unlocked you can now unplug the phone and turn it on. While the phone is booting up, keep toggling the volume button and it should go into bootloader. This is a text-based interface that allows you several functions.
Somewhere in there is an option to mount the SD card (for which you need to plug into your comp again)
5. You'll see the phone's SD card in Windows explorer and will be able to put your ROM onto it (NOT the extracted stuff from earlier but the original zip file).
6. You can now install this ROM but first clear all data and the dalvik cache. I also always to the battery stats here too. It might take a little bit of exploring to find these.
7. Now you can go to "install zip from SD Card". Step through and you will find where you put the ROM zip file. Select it and install the ROM.
At this point, you may get a bit frustrated - because it's here that you find things like:
The ROM sucks
Bits don't work or
You can't get it to work
For any of the above try again....
Currently I'm on Paranoid Android ICS ROM which I like but if I can't get the Wi-Fi working there's no way I'll be sticking to it. Another that I really liked and will return to is Boost HD RC4
I hope it works out for you.....
Tony

Canned30 said:
Right - I haven't posted much but having been pretty much under the same level of noob frustration before I'll try to help....
First - Often, during updates you can be driven mad with reboots and reboot cycles..... hopefully, what is outlined below can be a guide to sorting out any problems you might have.
1. Backup everything.
- go to play store and search for "backup" and you'll find what you need. I use Astro File Manager for application backup and sms backup for messages. I'm not bothered about backing up anything else.
2. Unlock the Bootloader.
- download sdk starter package
Code:
://developer.android.com/sdk/index.html
- so far as I can figure this will facilitate communications between your pc and phone. CyanogenMod Wiki guides you through this process:
Code:
://wiki.cyanogenmod.com/wiki/Howto:_Install_the_Android_SDK
- download latest version of fastboot. Now, you'll never double click on this program to run it. Instead you'll run commands from your command tool which will use the program to do the work.
- record your IMEI - in dialer type in *#06# for your IMEI & write it down.
- get your phone attached in fastboot mode. to do this you turn off your phone and hold the menu button while you attach it via USB to your computer.
- see if you're connected properly. Look for command prompt (Windows Key - All Programs - Accessories). Right click on this and run as administrator. Type in the following: fastboot -i 0x0fce getvar version . It will give an obviously positive message if you are correctly connected - if not, ensure you've attached in properly.
- get code to unlock bootloader - go here:
Code:
://unlockbootloader.sonymobile.com/
and go through the process to get an unlock key. Once you have this, go back to your command prompt and type fastboot -i 0x0fce oem unlock 0xUNLOCKKEY (where UNLOCKKEY is the number you have gotten from Sony website. You should get a confirming message.
Now that you've unlocked the bootloader you need to decide what kind of kernel and ROM you want. You can regard the ROM as software whereas the kernel links the software to the hardware. This is my limited understanding anyway.
3. Now, sometimes people make standalone kernels and sometimes they are kept with the ROM.
This leaves a couple of options
- you can flash a stand-alone kernel using flashtool (
Code:
://androxyde.github.com/
). The process is pretty simple.
- Now, if you download a ROM which advises that you need to extract and flash a file called "boot.img" there is a different method. In this case your ROM zip file can be extracted to find the boot.img file.
When you get the boot.img file you can place it in C:\. Now, all advice will be to place it in the platform-tools folder which is created in step 1. It doesn't matter really so long as you point at the right place when flashing.
(I also think that you can use flashtool in flashmode to do this job....)
4. Now you have a kernel on your Xperia and seeing as you've got the bootloader unlocked you can now unplug the phone and turn it on. While the phone is booting up, keep toggling the volume button and it should go into bootloader. This is a text-based interface that allows you several functions.
Somewhere in there is an option to mount the SD card (for which you need to plug into your comp again)
5. You'll see the phone's SD card in Windows explorer and will be able to put your ROM onto it (NOT the extracted stuff from earlier but the original zip file).
6. You can now install this ROM but first clear all data and the dalvik cache. I also always to the battery stats here too. It might take a little bit of exploring to find these.
7. Now you can go to "install zip from SD Card". Step through and you will find where you put the ROM zip file. Select it and install the ROM.
At this point, you may get a bit frustrated - because it's here that you find things like:
The ROM sucks
Bits don't work or
You can't get it to work
For any of the above try again....
Currently I'm on Paranoid Android ICS ROM which I like but if I can't get the Wi-Fi working there's no way I'll be sticking to it. Another that I really liked and will return to is Boost HD RC4
I hope it works out for you.....
Tony
Click to expand...
Click to collapse
I should have mentioned that the only thing I was successful doing was unlocking the bootloader...but then I was told to re-lock it so I could update using the PC companion.......... very annoying
thanks for the detailed reply..
I'm thinking now I wont bother with ICS and ill just root my current version 2.3.4 but yet again ive run into problems with dead links since most have not been updated since this time last year..
*EDIT*
I've tried DooMLords app thing to root, and all I get is a bunch of errors
trying to post a pic with all the errors but im not allowed...............................frustration after frustration after frustration

Try downloading some custom kernels n Roms from this site to see which version of ICS suits not best
There are threads with very explicit details on how to do so, you just need to look
I used to be a noob, on longer the case now.
Currently running acronium 2.4 with doomkernel v04 with WiFi modules, learned how to do all this from here
I'll figure out a site to upload all that I've downloaded so you have access to them with instructions cause some links don't work in other threads
Sent from my LT15i using xda app-developers app

[ROOT][UNROOT][CWM RECOVERY][STOCK KERNEL][STOCK RECOVERY] Google ADT-1 Android TV

Hello All,
Root
If on stock, uprooted (ever), go to method 1. If not, keep reading.
Now, in the latest Molly CF-AutoRoot, it flashes a modified kernel to gain root that causes OTA updates (i.e. impending 5.0.1) to fail, this was due to the fact that until a couple days ago, the modified kernel was necessary. Chainfire found a way to fix it without modifying the kernel and implemented it in SuperSU 2.37. If you are rooted, used CF-Auto Root, and wish to retain root, but regain the stock kernel for OTA's, simply follow root method 2.
Method 1
To Root from stock LPX13D, Download the following attached files and place them on your desktop (important):
- CWR_MOLLY_LPDX13D.img
- UPDATE-SuperSU-v2.37.zip
1. Install ADB on your system using: http://forum.xda-developers.com/showthread.php?t=2588979
2. Plug in your USB Keyboard to the back of your ADT-1
3. Enter the settings app on your ADT-1, go to "About" ==> "Build Number", and tap multiple times until it says "No need, you are already a developer. Exit this menu and you should now see a "Developer Options" menu, select it and check "Enable USB Debugging" and confirm your choice.
4. Go to Settings ==> Security, and check allow apps from unknown sources, confirm your choice.
5. (On PC) Plug in your ADT-1 and open a PowerShell (or CMD Prompt) and issue the command "Adb devices, and verify that your ADT-1 shows up as "device" and not "offline", if offline, reinstall ADB/Check your USB connection, then run "cd desktop"
6. Now run the command "adb reboot bootloader"
7. Run "Fastboot devices" to verify your ADT-1 is connected.
8. Here you have an option... if you want to be able to unroot and take OTA's, Run "Fastboot boot cwm_molly_recovery_lpx13d.img", as this will just boot CWM once, leaving the stock recovery in place or if you want a permanent custom recovery, run "fastboot flash recovery cwm_molly_recovery_lpx13d.img", but beware, no OTA's without stock recovery!
9. (On the ADT-1) Using your USB keyboard, use the down arrow key to select "install zips"
10. Select "Install Zip from sideload"
11. (On PC) run "adb sideload UPDATE-SuperSU-v2.37.zip"
12. (On ADT-1) Select "**Go Back**"
13. Select "Reboot to system"
14. Select "No" when asked to restore Root, as this's feature does not work yet.
15. Profit!
Method 2
To Root from CF-auto rooted LPX13D and regain stock kernel (This will not restore Build.prop and other system changes!), Download the following attached files and place them on your desktop (important):
- CWR_MOLLY_LPDX13D.img
- UPDATE-SuperSU-v2.37.zip
- stockbootlpx13d.img
1. Install ADB on your system using: http://forum.xda-developers.com/showthread.php?t=2588979
2. Plug in your USB Keyboard to the back of your ADT-1
3. Enter the settings app on your ADT-1, go to "About" ==> "Build Number", and tap multiple times until it says "No need, you are already a developer. Exit this menu and you should now see a "Developer Options" menu, select it and check "Enable USB Debugging" and confirm your choice.
4. Go to Settings ==> Security, and check allow apps from unknown sources, confirm your choice.
5. (On PC) Plug in your ADT-1 and open a PowerShell (or CMD Prompt) and issue the command "Adb devices", and verify that your ADT-1 shows up as "device" and not "offline", if offline, reinstall ADB/Check your USB connection, then run "cd desktop"
6. Now run the command "adb reboot bootloader"
7. Run "Fastboot devices" to verify your ADT-1 is connected
8. Run "fastboot flash boot stockbootlpx13d.img"
9. Here you have an option... if you want to be able to unroot and take OTA's, Run "Fastboot boot cwm_molly_recovery_lpx13d.img", as this will just boot CWM once, leaving the stock recovery in place or if you want a permanent custom recovery, run "fastboot flash recovery cwm_molly_recovery_lpx13d.img", but beware, no OTA's without stock recovery! Then you must run "fastboot reboot recovery"
10. (On the ADT-1) Using your USB keyboard, use the down arrow key to select "install zips"
11. Select "Install Zip from sideload"
12. (On PC) run "adb sideload UPDATE-SuperSU-v2.37.zip"
13. (On ADT-1) Select "**Go Back**"
14. Select "Reboot to system"
15. Select "No" when asked to restore Root, as this's feature doe snot work yet.
16. Profit!
Unroot
Requirements:
- stockbootlpx13d.img
- recovery.img
1. Enter the SuperSU app, and go to Settings ==> Full Uproot, and verify your choice. (Stop here if you didn't use CF-auto root)
2. Plug your ADT-1 into your PC and run the command "cd desktop", then "adb reboot bootloader", then "fastboot flash boot stockbootlpx13d.img"
3. Run "fastboot flash recovery recovery.img"
4. Then "fastboot reboot"
5. Un-Profit!
To take an OTA Update
If you followed this guide correctly, just unroot from within SuperSU as shown in Step 1. Of the unroot section. It will leave you 100% stock. Then take the OTA.
Downloads
Stock Boot Image LPX13D (stockbootlpx13d.img): https://www.dropbox.com/s/vayt67s513v9z8u/stockbootlpx13d.img?dl=0
Stock Recovery Image LPX13D (recovery.img): https://www.dropbox.com/s/yqu6lhuvzcz2rsu/recovery.img?dl=0
CWM Recovery Img (cwm_molly_recovery_lpx13d.img): https://www.dropbox.com/s/8evaum04mv843dp/cwm_molly_recovery_lpx13d.img?dl=0
SuperSU 2.37.zip: http://download.chainfire.eu/636/SuperSU/UPDATE-SuperSU-v2.37.zip
Optional: Install Leanback Launcher from here to allow launching sideloaded apps: https://play.google.com/store/apps/details?id=eu.chainfire.tv.sideloadlauncher&hl=en
Happy Modding!
Credits:
Chainfire: The super amazing SuperSU, and the awesome CF-Auto Root, thank him!
GTAVHacker: Used CWM Recovery Image as a base, thank him!
Myself: Stock Images, and the guide.

npjohnson said:
CWM Recovery (cwr_molly_recovery_lpx13d.img): https://www.dropbox.com/s/yqu6lhuvzcz2rsu/recovery.img?dl=0
Click to expand...
Click to collapse
Thanks for this! Should the file on dropbox be named cwr_molly...? When I go to the download it simply says recovery.img.

good work
This is awesome, thanks for sharing, I'd really like to see TWRP ported as well, they allow OTA installs/mtp, adb sideloads & more, this is a great step in the direction of seeing custom roms

OP download links updated. My apologies.

Well, TWRP didn't have mouse/keyboard support last I checked. So I'll work with it. But Philz Touch recovery or cannibal open touch should be both cool and doable.
Edit: TWRP has mouse & keyboard support and is possible, but requires a bit more work than is worth it right now.
CWM also has iffy support for OTA's I am finding, hit or miss, try at your own risk.
CWM also has the ADB sideload ability...... that's how you have to flash the SuperSU mentioned in the OP

I cant seem to get this to work. I tried using just the boot option and it just reboots into the bootloader. I tried the flash as well and recovery never boots. Any chance the problem is that this is for the ADT1 (molly) and not the Nexus Player (Fugu)?

The title of the post indicates ADT-1. You need to make sure any modification you do is appropriate for the device you have. The ADT-1 uses and Android processor/chip set while the Nexus Player uses an Intel processor/chip set.

Is there not a subforum for the adt1?

hmmmm CWM

jscat1 said:
Is there not a subforum for the adt1?
Click to expand...
Click to collapse
No there is not! I know, it sucks, but until that changes, looks like we are setting up shop on the fugu forums. XD

thanks so much for this. the ADT-1 needs more love on xda

twrp
if you guys could work on twrp that would be awesome, I plan on working on a rom with my kernel soon, for now check out my kernel and let me know how it runs in origin dev section

defconoi said:
if you guys could work on twrp that would be awesome, I plan on working on a rom with my kernel soon, for now check out my kernel and let me know how it runs in origin dev section
Click to expand...
Click to collapse
Thanks man. TWRP is actually gonna be more than it is worth. CWM should work just fine, it actually has better support for keyboard.
I'll mess with it. Did you build the kernel with the ADT-1 and x86 architecture in mind?

defconoi said:
if you guys could work on twrp that would be awesome, I plan on working on a rom with my kernel soon, for now check out my kernel and let me know how it runs in origin dev section
Click to expand...
Click to collapse
might work on getting twrp for for the adt-1 with mouse and keyboard support.
just received mine tuesday.
has anyone created repos for this device yet?

mkaymuzik said:
might work on getting twrp for for the adt-1 with mouse and keyboard support.
just received mine tuesday.
has anyone created repos for this device yet?
Click to expand...
Click to collapse
Haha. Sadly no. I had a partially working tree until gtvhacker posted a fully functional CWM. I gave up after that. You should pry ask him, if he gives you access could you shoot the links over to me? My partially working tree has been the only reason I haven't built CM yet. It fails mid way through compilation.

npjohnson said:
Haha. Sadly no. I had a partially working tree until gtvhacker posted a fully functional CWM. I gave up after that. You should pry ask him, if he gives you access could you shoot the links over to me? My partially working tree has been the only reason I haven't built CM yet. It fails mid way through compilation.
Click to expand...
Click to collapse
im working on a new tree. open to anyone to contribute and add things. created a github organization for this purpose
https://github.com/adt1-dev
PS: im new to this and learning on the way.
Edit: are your sources on github?

npjohnson said:
Haha. Sadly no. I had a partially working tree until gtvhacker posted a fully functional CWM. I gave up after that. You should pry ask him, if he gives you access could you shoot the links over to me? My partially working tree has been the only reason I haven't built CM yet. It fails mid way through compilation.
Click to expand...
Click to collapse
If you're referring to the builds I released on GTVHacker forums for CWM recovery on the ADT-1, I didn't build the kernel or use any Android TV or ADT-1 source (it wasn't even available when I had started). I just used generic CM Android 4.4, reused the kernel and fstab from the stock ADT-1 recovery, and made a few changes to the default generic BoardConfig.mk.

Any plans on making recovery for nexus player? Just curious

Can someone direct me to a stock copy of a (full) build.prop from LRX22G? I think my build.prop is incorrect (long story, let's just say the LRX22G OTA did not go smoothly for me) and I want to just flush it and replace it with a "clean" one?
Thanks

illuminerdi said:
Can someone direct me to a stock copy of a (full) build.prop from LRX22G? I think my build.prop is incorrect (long story, let's just say the LRX22G OTA did not go smoothly for me) and I want to just flush it and replace it with a "clean" one?
Thanks
Click to expand...
Click to collapse
You can just download the factory image and extract it. Here is a little tutorial if you are unsure how to extract.