a little help? - T-Mobile Sidekick 4G

ok im tring to root flash smooth maximus on my buddies sk4g and im a little stuck. when i did my galaxy s it was way different. im trying to use android commander for the modified binary but it tells me abd doesnt work when i oped it and i have the sdk installed. do i have to do this what is the difference between this and my phone to have to do this step

lowlife113 said:
ok im tring to root flash smooth maximus on my buddies sk4g and im a little stuck. when i did my galaxy s it was way different. im trying to use android commander for the modified binary but it tells me abd doesnt work when i oped it and i have the sdk installed. do i have to do this what is the difference between this and my phone to have to do this step
Click to expand...
Click to collapse
you have to flash a rom using cwm!
btw please post questions in general section not the dev section

ok well if a mod could move this thread...i understand how to flash it what i dont get is why i have to modify the binary to run cwm and why android commander wont run to push the file

You need to modify the binary because a stock recovery can't flash unsigned roms, which any rom not from samsung is. Android commander won't push that file because system needs to be remounted as read/write, rather than read only.
You can use my modified oneclickroot script to push the correct modified binary and install the update.zip to get you into CWM
http://forum.xda-developers.com/showpost.php?p=15831175&postcount=124

you have to mod it to get into the right recovery and just use root explorer
download:
http://www.krylon360.com/file_host/sk4g/recovery.zip (This is the recovery.)
http://www.krylon360.com/file_host/sk4g/update.zip (this is the update)
http://www.4shared.com/get/HpENkmN8/...rer_v2124.html (this is root explorer.)
open the first file on your computer and take out the recovery file inside it and place it on the sd card.
place the second file on the sd card
and install the last file.
now open root explorer scroll down and find sdcard,
now open it and find recovery and long press on it. hit copy. now hit the back button once.
now find system. open it.
find bin. open it.
hit on the top mount r/w
hit paste and overwrite the file.
next, power down the device and instead of powering on regularly, press volume down+ power button you should be in the recovery mode.
if it is blue then hit install packages,
if it is red you should be good to go.
NOW YOU HAVE A CWM

thank you i was following another set of directions which apperently were wrong

Related

OBSOLETE.

In the event something happens to your phone, -I'm- not responsible for the damages to it, you are. The end. I've personally tested this method and it works flawlessly.
This tutorial entails gaining full root access on your Evo. That means we -will- be unlocking NAND. But most importantly, we'll be doing it all without the use of a computer. Needless to say, this is going to take a while, especially if you don't have access to a wifi signal. The PC36IMG.zip files are rather hefty and are going to take at least 30 minutes to download. So I suggest you start downloading both of them now.​
Prerequisites: Download Astro File Manager from the market. Open it up, hit the menu key on your phone, select more, select preferences, then scroll down and make sure Enable Browser Download is checked.
This is a template for you guys that'll explain to you how to move a file to the root of your SD card using Astro File Manager.
The files that you've downloaded from the links below are going to be located in the Downloads folder that is on the root of your SD card.
Unless you're using a browser like Xscope or Dolphin, then you'd have to navigate to the particular browser's folder that you're using, open it up and find the downloads folder in there.
When you first open the Astro File Manager app, you're going to be staring at what is the actual root of your SD card. Remember that.
Code:
When I tell you to move something to the root of your SD card, you're going to:
Locate and open the appropriate download folder that contains the file I am referring to.
Long press on the file.
Select Edit.
Select Move.
Press the Back key on your phone 'til you've reached the root of your SD card in Astro File Manager.
Click the Menu key on your phone.
Select Edit.
Select Paste.
When I tell you to rename a file you're going to:
Long press on the file.
Select Edit.
Select Rename.
Rename it accordingly and select done.
Step 1. Download this file http://link.geekfor.me/rootedromzip and move it to the root of your SD card.
Step 2. Power down your phone.
Step 3. Hold down the Volume Down and Power key simultaneously and keep holding it down until you've reached a white screen with 3 android dudes on skateboards.
Step 4. It's going to give you some options, whether or not to install the PC36IMG.zip, select yes (volume up is yes) for any prompt you get.
Step 5. Once you've rebooted you will officially have root access. Just not full root access, we still need to unlock NAND.
Step 6. Navigate to the root of your sd card and rename the PC36IMG.zip file whatever you want, doesn't matter. Just don't name it update. You can even delete it if you want.
Step 7. Download the mtd-eng.zip file here. - http://forum.xda-developers.com/attachment.php?attachmentid=342668&d=1276481802 And the flash_image.zip file here. - http://forum.xda-developers.com/attachment.php?attachmentid=342667&d=1276481776
Step 8. Navigate to the root of your SD card and locate both of the .zip files you just downloaded. Open them, and long press on the files inside of them, then select Edit, then Copy, navigate back to the root of your SD card, press menu, select Edit, and then paste. Do the same thing for both files.
Step 9. Open up the Android Market and download the terminal emulator app by Jack Palevick, it's free.
Step 10. Open the terminal emulator app and type in these commands exactly as they are written. If you get an error, try again.
Note: After each line is completed, hit enter. A # sign means you've run the commands successfully.
Code:
[B]su
cat /sdcard/flash_image > /data/flash_image
chmod 755 /data/flash_image
/data/flash_image misc /sdcard/mtd-eng.img[/B]
Step 11. Download the new PC36IMG.zip file here -http://sdx-downloads.com/sdx/evo/troot/eng-PC36IMG.zipand move it to the root of your SD card, then rename it to "PC36IMG.zip" because the is named eng-PC36IMG.zip, which is wrong. Then power down your phone.
Step 12.
Hold volume down and power to boot into hboot.
- It should now find and verify the PC36IMG.zip on the root of your sdcard. It'll show a blue status bar on the top right of the screen.
- After a minute or so it will ask u if u wanna flash Select YES.
- After it flashes the PC36IMG.zip it will ask if you wanna reboot. Select YES.
Click to expand...
Click to collapse
Step 13. Once your phone has rebooted, download the recovery.img file here - http://files.androidspin.com/downloads.php?dir=amon_ra/RECOVERY/&file=recovery-RA-evo-v1.7.0.1.img Then move it to the root of your SD card and rename it "recovery.img"
Step 14. Still know how to use terminal emulator? Open it up and type in these commands.
Code:
[B]su
cat /sdcard/flash_image > /data/flash_image
chmod 755 /data/flash_image
/data/flash_image recovery /sdcard/recovery.img[/B]
You now have full root access as well as a legit recovery.
If you want to flash a ROM or the newest radio and you don't know how to do that, there's already guides for that. So I won't include that in my tutorial, just click here. http://forum.xda-developers.com/showthread.php?t=710513
ALL CREDIT GOES TO THESE GUYS! toastcfh, keishou, maejrep, Paul, Amon_Ra, Koush, TheBiles, and anybody else I forgot.
PLEASE NOTE THE DONATION SUGGESTION IN MY SIGNATURE.
I must look like a douche what with the bold CAPS asking to note the donation link in my signature, which used to be a link to Dr. Cloverdale's paypal, not mine. Just thought I'd clear that up.
Reserved.
10 char
Great Work!!
Wow, great work!! Seems easy enough to me. I have a quick question as i haven't rooted yet and don't know all it entails.
First, you say after this method that we have a "legit recovery"...does that mean if i hard reboot, that there is a rooted, nand unlocked image you put there already that will flash with a hard reset? And if so, what image did you use? (or is it exactly the same as stock but rooted)
Second, some of the other quides state we need to root, then unlock, then flash a custom recovery...it looks as if you have all 3 steps included right?
Finally, is there anything else you recommend i do after i complete root using your method?? I am looking forward to maximizing this phone!!
Thanks for this guide!!! Can't wait to try it out.
adeyo said:
Wow, great work!! Seems easy enough to me. I have a quick question as i haven't rooted yet and don't know all it entails.
First, you say after this method that we have a "legit recovery"...does that mean if i hard reboot, that there is a rooted, nand unlocked image you put there already that will flash with a hard reset? And if so, what image did you use? (or is it exactly the same as stock but rooted)
Second, some of the other quides state we need to root, then unlock, then flash a custom recovery...it looks as if you have all 3 steps included right?
Finally, is there anything else you recommend i do after i complete root using your method?? I am looking forward to maximizing this phone!!
Thanks for this guide!!! Can't wait to try it out.
Click to expand...
Click to collapse
Legit, as in the most legit recovery on the scene, that being Amon_RA's.
Yup, got all three covered in that order.
Here's a link that shows you an in-depth guide on how to flash ROM's and what-have-you. http://forum.xda-developers.com/showthread.php?t=710513
No problem, man. Let me know how it goes for ya'.
Does this method still work with the latest OTA patch on 6/28/10?
Aren't you supposed to have Superuser Permissions after flashing the first ROM?
and you do get super permissions after you flash a CUSTOM rom....
what's your definition of 'CUSTOM'? This isn't my first time rooting, I unrooted lastnight and decided to try this method to see if it would work. I know for a fact that during the original rooting process the first PC36IMG you flash, you have Superuser permissions. And the second one that is flashed is the ROM to unlock NAND. However, doing this method, after flashing the first PC36IMG, I do not have Superuser permissions
However, it does seem that this method works. So I'm happy. It's good to know that I don't have to rely on a computer to root my phone now. Now the only thing I need to do, is figure out how to UNroot my phone without a computer.
Android believer, did you update to the ota update yesterday? Do you know if this works with the ota v1.47.651.1?
Sent from my Evo using XDA App
gordon1hd1 said:
Does this method still work with the latest OTA patch on 6/28/10?
Click to expand...
Click to collapse
I would assume it doesn't, as this is still toastcfh's method of rooting except it's done without a computer.
@ neckface
Hope you're not tired of hearing from me. First, thanks mass for this.
You say this is Toasts method without computer. I'm on the orig stock ROM, no 1.47 update. I WANT to do the update (for better battery mainly). I want to do whitslacks method. He says you need eng hboot 76.2000. He says use Toasts part 2 to get that.
Should I : use this to get eng hboot, then go to whitslacks for the 1.47 update? You seem to have a pretty good grip on this, so I thought I'd ask your opinion.
(if this is still Toastcfhs method, are these links to the same files he has posted? Meaning, will this get me eng-Hboot 76.2000? )
Thanks a lot.
anybody
Really interested in this. Anyone have success with this from 1.32 SW, and does it give you hboot 76.2000 ?
Thanks in advance.
Scott
OK i must be the dumb one
I have already used the "Unrevoked method" so I thought I could just skip to the Nand unlock. Now the phone(EVO) will not allow me access to my sdCard...and..will not read when I plug it up to my USB PC(windows) instead of it coming up as android like it use to it comes up as Qualcomm CDMA Technologies MSM(new found hardware wizard)....and the phone can only charge when the phone is powered off. Its like the usb is not responding and I can not have access to the SD card via teh device..i need advice
Thank you
Thank you,
I don't know if it was the wrong recovery.img or what, but I could not do a nand unlock. This worked great and did it all off the phone..... Awsome

[Q] I can't root gtablet

This is my first droid product and I really am getting frustrated with it. I can't seem to root into it. Is there some program that I need to download to access the root folder. I have the clockwork mod and TNT but I can't install them. When I try to flash but the stock box with the arrow comes up. Please help I'm retarded.
Use z4root to root, then root explorer to make mounts R/W.
Jim
scopes44 said:
This is my first droid product and I really am getting frustrated with it. I can't seem to root into it. Is there some program that I need to download to access the root folder. I have the clockwork mod and TNT but I can't install them. When I try to flash but the stock box with the arrow comes up. Please help I'm retarded.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=892090
http://forum.xda-developers.com/showthread.php?t=865245
Read the first post of both those threads. You don't need root to install Clockwork or TnTlite.
okay just installed cwmod and tnt but the tab still is starting up regularly. this is step by step of what im doing. i plug my gtab in and activate usb transfer, then on my desktop i have folders such as :android secure,andriod,apps,backup,dcim,download,gtabtntlite,lostdir,recovery,update.zip. so did i put the rom and clockwork in the right area? then when i go into recovery it loads like normal. what the heck am i doing wrong???????
scopes44 said:
okay just installed cwmod and tnt but the tab still is starting up regularly. this is step by step of what im doing. i plug my gtab in and activate usb transfer, then on my desktop i have folders such as :android secure,andriod,apps,backup,dcim,download,gtabtntlite,lostdir,recovery,update.zip. so did i put the rom and clockwork in the right area? then when i go into recovery it loads like normal. what the heck am i doing wrong???????
Click to expand...
Click to collapse
When you boot your tab holding the power/vol+, hold the vol+ until you see "recovery key pressed". If you don't get the clockwork menu then clockwork is not installed.
Read the first post of those to threads carefully and make sure you have the correct command file in the recovery directory.
There are 2 clockwork zips. If you use the internal one you will need to put the update.zip on the root of the internal sdcard andthe recovery folder with the command file on the root of the internal sdcard.
/sdcard/update.zip
/sdcard/recovery/command
the command file deletes the first time you boot. You have to hold the Vol+ when booting until you see "recovery key pressed"
scopes44 said:
okay just installed cwmod and tnt but the tab still is starting up regularly. this is step by step of what im doing. i plug my gtab in and activate usb transfer, then on my desktop i have folders such as :android secure,andriod,apps,backup,dcim,download,gtabtntlite,lostdir,recovery,update.zip. so did i put the rom and clockwork in the right area? then when i go into recovery it loads like normal. what the heck am i doing wrong???????
Click to expand...
Click to collapse
Look in the recovery directory. There should be a file named "command" (just "command", with no extension). Bring that into your PC, and look at it with Notepad or some text editor, and see if it says "SDCARD" or if it says "SDCARD2". Since you put your update.zip into /sdcard, the command file should say "SDCARD", otherwise, recovery is going to look on the external/microSD card, rather than then internal sdcard.
Jim
THANK YOU
man you guys are awsome i finally got the hack to work and let me tell you its worth all the hair i pulled out. thank you guys for tall the patience and understanding the gtab is bad ass now. im using vega 5 and i love it.

[Q] How do I keep ClockworkMod?

OK, so after fighting with my Nexus S 4G for three hours trying to get it rooted (it took 15 - 30 minutes for my Hero and Evo Shift) I finally established root and wanted to install ClockworkMod. Of course I've come to learn that it's just not that simple, and I have to rename the default recovery, which require r/w permissions, and just more hoops to jump through.
Long story short, I rooted, set r/w access and renamed install-recovery.sh and used ROM Manager to install ClockworkMod. Reboot to recovery, and all seems well. Except that the next time I reboot, I'm back to the default recovery, my renamed install-recovery.sh.old is no where to be found and low and behold, install-recovery.sh is back.
Considering how easy this was with HTC devices... I'm starting to get a little pissed off.
Anyone have any idea why I can't maintain ClockworkMod?
Why don't you just use fastboot and flash the recovery image? It will be permanent if you do that... It takes about ten seconds.
Download the clockwork mod recovery and rename it to recovery.img then reboot your phone into the bootloader (hold volume up while you power on your phone). With the Android sdk installed and in your path, type fastboot flash recovery recovery.img and enjoy. If you want more specific help, you can pm me. I'll need to know what type of computer you have, Windows, Mac, or Linux in that case.
Sent from my Nexus S 4G using XDA Premium App
If you're sure you did the renaming properly and after that the file got restored back, I'd suggest you trying to trick the system by making a backup of the original install-recovery.sh and then instead of renaming it, just delete everything in that file so you still have the file named install-recovery.sh which will do noting to the recovery partition
radadev said:
Download the clockwork mod recovery and rename it to recovery.img then reboot your phone into the bootloader (hold volume up while you power on your phone). With the Android sdk installed and in your path, type fastboot flash recovery recovery.img and enjoy. If you want more specific help, you can pm me. I'll need to know what type of computer you have, Windows, Mac, or Linux in that case.
Sent from my Nexus S 4G using XDA Premium App
Click to expand...
Click to collapse
OK... tried this. No go.
Reboot still shows the default and not clockwork.
The file I renamed on my i9020a to prevent stock recovery from being reinstalled was in the folder \etc and was called install-recovery.bak
Cheers
So you're saying that your NS is rooted but when you boot into recovery, default recovery replaces CWM right?
1) Download 'Root Explorer' and 'ROM Manager' from the Market (Skip this step if you already have done so)
2) Reboot
3) Open 'Root Explorer' and open 'etc' directory
4) On the top right hand corner, click the 'Mount R/W' button
5) On the same directory, find 'install-recovery.sh' and rename this file to a different name (e.g. install-recovery.sh.old)
6) Open 'ROM Manager' and click 'Flash ClockworkMod Recovery.'
7) Reboot
jungbum said:
So you're saying that your NS is rooted but when you boot into recovery, default recovery replaces CWM right?
1) Download 'Root Explorer' and 'ROM Manager' from the Market (Skip this step if you already have done so)
2) Reboot
3) Open 'Root Explorer' and open 'etc' directory
4) On the top right hand corner, click the 'Mount R/W' button
5) On the same directory, find 'install-recovery.sh' and rename this file to a different name (e.g. install-recovery.sh.old)
6) Open 'ROM Manager' and click 'Flash ClockworkMod Recovery.'
7) Reboot
Click to expand...
Click to collapse
This is the first thing I tried. No dice.
Sophos1 said:
The file I renamed on my i9020a to prevent stock recovery from being reinstalled was in the folder \etc and was called install-recovery.bak
Cheers
Click to expand...
Click to collapse
I don't see an "install-recovery.bak"
Stupid question, is your bootloader still unlocked?
wild1z said:
Stupid question, is your bootloader still unlocked?
Click to expand...
Click to collapse
Yep. Still unlocked. Super-user and root programs appear to work fine. Can pull apks and push them back. I really don't know why this isn't working for me. Just thought maybe I wasn't alone.
Shadodragon said:
Yep. Still unlocked. Super-user and root programs appear to work fine. Can pull apks and push them back. I really don't know why this isn't working for me. Just thought maybe I wasn't alone.
Click to expand...
Click to collapse
Have you tried to lock it back up and return to stock? I suspect you are using the latest clockwork mod too right? I feel your pain. My Hero was a PITA to root and it had all kinds of wanky problems one day and the next.. Blue skys.
wild1z said:
Have you tried to lock it back up and return to stock? I suspect you are using the latest clockwork mod too right? I feel your pain. My Hero was a PITA to root and it had all kinds of wanky problems one day and the next.. Blue skys.
Click to expand...
Click to collapse
See, the Hero was easy for me. The Nexus seems 10 times harder to do things to.
I have noticed this, I have an:
etc\install-recovery.sh
and
system\etc\install-recovery.sh
Do I need to rename both?
Shadodragon said:
See, the Hero was easy for me. The Nexus seems 10 times harder to do things to.
I have noticed this, I have an:
etc\install-recovery.sh
and
system\etc\install-recovery.sh
Do I need to rename both?
Click to expand...
Click to collapse
I can only tell you what I would do. I would try to get it back to stock and lock it up to start over.
Maybe JasonMahoney, AOSP and Lilduce will come on over and share this fun with us.

[Q] Noob guide?

Im very new to development on the Sidekick. I have my phone rooted and thats it. I want to put the final smooth maximus on it. How do I go about do that??
Additional info:
As I said I only have it rooted, I dont have CWM on it or anything else.
A step by step noob friendly guide would be helpful please.
Install CWM from here ,
Put the Update.zip on your /SDCARD
Install root manager from phone , put moddedrecovery on your /SDCARD then navigate it to /SYSTEM/BIN rename Recovery.bin to Recovery.bak then move krylon's there .
Terra27 said:
Im very new to development on the Sidekick. I have my phone rooted and thats it. I want to put the final smooth maximus on it. How do I go about do that??
Additional info:
As I said I only have it rooted, I dont have CWM on it or anything else.
A step by step noob friendly guide would be helpful please.
Click to expand...
Click to collapse
I dont see a link? Also what is a good free root manager??
http://www.4shared.com/file/kdrTVrGw/Root_Manager_v195.htm
there's root manager & here's CWM
http://forum.xda-developers.com/showthread.php?t=1124453
Terra27 said:
I dont see a link? Also what is a good free root manager??
Click to expand...
Click to collapse
Now how do I put the manager on my phone?? Thank you for being so patient!
Put the .apk on your /SDCARD open file's application from your sidekick & install it
Terra27 said:
Now how do I put the manager on my phone?? Thank you for being so patient!
Click to expand...
Click to collapse
if u ever need help feel free to pm me
Sent from my SGH-T839 using XDA Premium App
Now how do I install it?? Sorry I'm confused on all this. I thought I knew that. Phone dev isn't my forte..
Terra27 said:
Now how do I install it?? Sorry I'm confused on all this. I thought I knew that. Phone dev isn't my forte..
Click to expand...
Click to collapse
Go to files , go to place where you saved the .apk and Just click on it , then a option may come up say package installer click on that then it will install.
Hope this helped you.
Sent from my SGH-T839 using Tapatalk
Okay so I got everything done and it soft bricked so I used ODIN to unbrick it and when I retry to get into CWM it always errors out now, I've redone everything I originally did and it won't go back into CWM. Why?
Sounds like you didn't replace the recovery binary correctly if it's giving a "verification failed" error.
I did though, I rooted my phone using super one click, robooted it, replaced recovery in system/bin with krios' and left the update.zip on the root and it still didnt. I dont think it really rooted though..
Terra27 said:
I did though, I rooted my phone using super one click, robooted it, replaced recovery in system/bin with krios' and left the update.zip on the root and it still didnt. I dont think it really rooted though..
Click to expand...
Click to collapse
do you have the superuser app? if not its not rooted.
I have it.
Terra27 said:
I have it.
Click to expand...
Click to collapse
okay so download the recovery file and move it to sytem/bit and overwrite the old recovery file. place the update.zip on to your sd card the volume down+power on should get you there! if its blue i think you have to press reintall packages
Try my script here, it'll place the recovery and cwm for you:
http://forum.xda-developers.com/showpost.php?p=15831175&postcount=124
So after having my phone brick twice, will someone PLEASE take the time to type a step by step noob friendly guide. Please
Define brick. Where did you have issues and what issues did you have?
Terra27 said:
So after having my phone brick twice, will someone PLEASE take the time to type a step by step noob friendly guide. Please
Click to expand...
Click to collapse
download:
http://www.krylon360.com/file_host/sk4g/recovery.zip (This is the recovery.)
http://www.krylon360.com/file_host/sk4g/update.zip (this is the update)
http://www.4shared.com/get/HpENkmN8/...rer_v2124.html (this is root explorer.)
open the first zip file (recovery file) on your computer and take out the recovery file inside it (should be the only file) and place it on the sd card.
place the second file (the update file) on the root of your sd card
and install (root explorer) the last file just like you would a normal apk file.
now open root explorer scroll down and find sdcard,
now open it and find recovery and long press on it. hit copy. now hit the back button once.
now find system. open it.
find bin. open it.
hit on the top mount r/w
hit paste and overwrite the file.
next, power down the device and instead of powering on regularly, press volume down+ power button or volume up+volume down+camera+power on you should be in the recovery mode.
if it is blue then hit re-install packages,
if it is red you should be good to go.
NOW YOU HAVE A CWM
Goodluck and have fun flashing.
tylermaciaszek said:
download:
http://www.krylon360.com/file_host/sk4g/recovery.zip (This is the recovery.)
http://www.krylon360.com/file_host/sk4g/update.zip (this is the update)
http://www.4shared.com/get/HpENkmN8/...rer_v2124.html (this is root explorer.)
open the first zip file (recovery file) on your computer and take out the recovery file inside it (should be the only file) and place it on the sd card.
place the second file (the update file) on the root of your sd card
and install (root explorer) the last file just like you would a normal apk file.
now open root explorer scroll down and find sdcard,
now open it and find recovery and long press on it. hit copy. now hit the back button once.
now find system. open it.
find bin. open it.
hit on the top mount r/w
hit paste and overwrite the file.
next, power down the device and instead of powering on regularly, press volume down+ power button or volume up+volume down+camera+power on you should be in the recovery mode.
if it is blue then hit re-install packages,
if it is red you should be good to go.
NOW YOU HAVE A CWM
Goodluck and have fun flashing.
Click to expand...
Click to collapse
okay I can get that far, but when I attempt to flash smooth mazimus on it, it will get to the tmo/sidekick/samsung screen and I'll hear a weird female robotic voice. 4 bricks, 1 with the FC vibrations, 3 with that weird voice.

[HowTo] Root official AT&T 2.3.6 Gingerbread and UCLB3 leak - Infuse 4g

Often, folks ask how to root the Samsung UCLB3 leak or how to root the official AT&T Gingerbread release for the Infuse 4G (both are one and the same at the time of writing this). This how-to explains how to do this.
Note that this also works for rooting the earlier UCL** and UCK** leaks.
Easiest option - flash a rom that is already rooted.:
An easy option is to flash this Odin tar.md5 that I put together. It flashes stock UCLB3 with root already installed.:
http://forum.xda-developers.com/showthread.php?t=1613523
Another easy option, if you already have cwm recovery, is to download and flash this version.:
http://forum.xda-developers.com/showthread.php?t=1508619
And another easy option from qkster to get UCLB3 + cwm recovery in a Heimdall One-Click package.:
http://forum.xda-developers.com/showthread.php?t=1524081
Another easy option - do it yourself.:
Another easy option is to flash one of the custom Gingerbread kernels with CWM recovery from here. This won't wipe your current OS, data, or apps.:
http://forum.xda-developers.com/showthread.php?p=27123262
Download and place this file on your internal sdcard.:
http://downloads.androidsu.com/superuser/Superuser-3.0.7-efghi-signed.zip
Then, put your phone in recovery mode. Shut phone off. Hold down power button and both volume buttons, and once the Samsung logo appears, let go of the power button. Keep holding volume buttons down until you get to red CWM recovery.
From there, install the Superuser zip by choosing "install zip from sdcard".
More involved option - do it yourself.:
If you're like me, though, and like to do things the hard way, then below is another way to root the official release and leaked versions.
(Don't have the AT&T GB release or the UCLB3 leak yet? You can get the UCLB3 Gingerbread leak at this link: (http://forum.xda-developers.com/showthread.php?t=1507658). Extract the file in 7zip. Place the extracted file in the PDA slot in Odin. Flash.)
a.) Assuming that you have already flashed the Samsung UCLB3 leak, or that you already have it through AT&T and Kies mini, know these two things.: First, SuperOneClick WILL NOT root this release at the time of writing this. Second, you won't be able to root with the stock kernel, so you will need to flash a custom kernel at least temporarily.
b.) If you intend to go back to the stock UCLB3 kernel after using a custom kernel to root (not a bad idea if you want to keep all stock functionality), then follow this step. If you plan to keep the custom kernel (which allows for improvements such as CWM recovery, Voodoo lagfix, etc.) then skip this step.
If you intend to go back to the stock UCLB3 kernel, save some time and disable Voodoo lagfix by creating a directory on your internal sd card (/sdcard/), labeled Voodoo. Inside that folder, place an empty file named disable-lagfix (with no extension).
If you go back to flash the stock kernel, you will have issues doing so if you have Voodoo lagfix enabled.
c.) Use Heimdall to install a recent custom GB kernel.
Download a recent custom GB kernel. A good custom kernel to use is Entropy's Daily Driver, which can be found at this link.:
http://forum.xda-developers.com/showthread.php?t=1212795
Download and install the Heimdall suite on your computer. Follow ALL installation instructions in the README.txt file included with the program, including instructions for installation of the usb driver in zadig. If you don't install the libusb driver that comes with the program, your phone won't be detected, and you'll only receive error messages. Here is the download link.:
https://github.com/Benjamin-Dobell/Heimdall/downloads
d.) Put your Infuse 4G in download mode
Battery pull method: Pull battery, hold down volume keys, replace battery, connect usb cable, and continue to hold volume keys until phone is in download mode.
e.) On your computer, place the custom kernel zImage in the same directory as heimdall.exe. In a command prompt, make this your working directory, and type this into the prompt on your computer.:
Code:
heimdall flash --kernel zImage
If kernel flash is successful, the phone will reboot. If you disabled Voodoo lagfix, the phone will boot up without much wait. If you didn't disable Voodoo lagfix, wait for the robotic lady voice to go on about all that is being done to enable Voodoo lagfix. Hope you don't mind waiting. You remember that I suggested that you disable Voodoo lagfix, right?
f.) Download the cwm installable zip at the link below, and place it on your internal sdcard (/sdcard/). You'll flash this in recovery in a moment to get root.
ChainsDD Superuser zip (to flash in cwm recovery):
http://downloads.androidsu.com/superuser/Superuser-3.0.7-efghi-signed.zip
g.) Put the phone in Recovery Mode.
Button method: With the phone turned off, press and hold both volume buttons, as well as the power button. Release the power button after you see the Samsung logo on screen, and continue to hold the volume buttons.
h.) In recovery, choose "Install zip from sdcard". Select "Choose zip from sdcard", and choose the Superuser zip file that you placed on the internal sd card. Select "Yes -Install zip". When installation is complete, go back in the menu and choose "Reboot system now" After the reboot, you should now have the Superuser program and all system files necessary to be rooted.
i.) If you intend to keep Entropy's custom kernel, then you are done. You have rooted UCLB3 at this point, with a custom kernel.
If you want to flash the stock kernel now, you can do so, and you will keep root. To do that, download and extract the stock kernel zImage from HERE. Be sure that Voodoo lagfix is disabled before going back to the stock kernel. Use the same steps outlined in part e.) of this tutorial to flash the stock zImage, or just use SGS Kernel Flasher on the phone.
External sdcard issues?: If you go back to the stock kernel after flashing a custom kernel, you will most likely have trouble seeing your external sdcard. To fix this, use Root Explorer (or a similar app) to edit /system/etc/vold.fstab. In Root Explorer, browse to /system/etc and choose "Mount R/W" to gain write permission to the directory. Open vold.fstab in the built in text editor. Change the mmc2 in the last line to mmc1. Save and exit. Reboot, and you will regain use of your external sd card.
Hope that helps someone!
Is there a way to do this in Odin. Heimdall doesnt recognize the phone to be connected and Im much more comfortable doing it in Odin. Is there a tar file of the kernel to be able to flash it?
jscott30 said:
External sdcard issues?: If you go back to the stock kernel after flashing a custom kernel, you will most likely have trouble seeing your external sdcard. To fix this, use Root Explorer (or a similar app) to edit /system/etc/vold.fstab. Change the mmc2 in the last line to mmc1. Save and exit. Reboot, and you will regain use of your external sd card.
Click to expand...
Click to collapse
Can this step be avoided if we remove the external card before flashing the temporary kernel, then replace it after flashing back to the stock kernel?
(Thanks for the great summary, by the way!)
elivaldez84 said:
Is there a way to do this in Odin. Heimdall doesnt recognize the phone to be connected and Im much more comfortable doing it in Odin. Is there a tar file of the kernel to be able to flash it?
Click to expand...
Click to collapse
To get Heimdall to recognize your phone:
Put your device in download mode, and with the usb cable attached, open zadig (in the Drivers folder of your Heimdall install). In the "Options" menu in zadig, choose "List All Devices" and install the "Samsung USB Composite Device" driver. Then, Heimdall will recognize the device.
Sent from my SGH-I997 using Tapatalk 2
Gary02468 said:
Can this step be avoided if we remove the external card before flashing the temporary kernel, then replace it after flashing back to the stock kernel?
(Thanks for the great summary, by the way!)
Click to expand...
Click to collapse
You can try, but I'm pretty sure that you will still have to edit vold.fstab. Let us know what you find.
Sent from my SGH-I997 using Tapatalk 2
Even though my phone is already rooted, I wanted to thank you for this. I followed the best method I could find a few weeks ago: flashing the already rooted rom. If your phone isn't rooted, doesn't have CWM, and you want to make a backup, that method is more involved than the DIY one you have here.
So, if anyone is facing a similar problem (you need CWM to do the nandroid, you need root to install CWM), follow this.
jscott30 said:
Inside that folder, place an empty file named "disable-lagfix" (without quotes, and with no extension).
Click to expand...
Click to collapse
I'm using the stock "My files" application, can create the folder no problem, how to create the empty file with no extension?
I can copy any file from another folder, rename it but it still has its original extension. Even from PC I can only create a file with a certain extension.
toshik1 said:
I'm using the stock "My files" application, can create the folder no problem, how to create the empty file with no extension?
I can copy any file from another folder, rename it but it still has its original extension. Even from PC I can only create a file with a certain extension.
Click to expand...
Click to collapse
There are several ways to do this.
On the phone, I use ES File Explorer. With that app, you can create a new file without an extension.
Easy way on a Windows PC is to create an empty file in Notepad++ or even Notepad. Choose "Save As", and put quotes around the file name: "myfile"
In Linux, I just use the touch command to create the file, and then push it to the device with adb.
Sent from my SGH-I997 using Tapatalk 2
Initialising connection...
Detecting device...
ERROR: Failed to access device. libusb error: -12
Heimdall? Did you install drivers in zadig while in download mode?
Sent from my SGH-I997 using Tapatalk 2
Ran the file from zadig directory-not noted anywhere in description :-(
3. Got the error message...
I succeeded in installing Entropy's custom kernel and the ChainsDD via cwm, per your instructions. But when I try to reinstall the stock kernel (zImage extracted from UCLB3), Heimdall gets as far as "Uploading KERNEL 100%" but then says "ERROR: Failed to confirm end of file transfer sequence! KERNEL upload failed!".
The phone then reboots, and the kernel version is reported as 2.6.35.7-I997RUXKG3-CL366622. I tried a second time, with same results.
UPDATE: I tried re-extracting zImage and running heimdall again, but it still failed. Then I tried using SGS Kernel Flasher instead and it worked. So I'm happily back to 2.6.35.7-I997UCLB3-CL977492 now.
toshik1 said:
Ran the file from zadig directory-not noted anywhere in description :-(
3. Got the error message...
Click to expand...
Click to collapse
Yeah, check your Heimdall install. And you're right, instructions for installing Heimdall aren't in this tutorial. Plenty of good documentation at the link where you downloaded Heimdall, and that would be another good tutorial topic. A few posts back in this thread, I did explain to someone else how to use zadig to install usb drivers for Heimdall. Find that and see if that helps. Until you have correctly installed drivers, you won't have a working Heimdall install. Read well at the install link.
Edit: The install link directs you to the README.txt file in the Heimdall install folder. Follow ALL of the steps there.
Sent from my SGH-I997 using Tapatalk 2
Gary02468 said:
UPDATE: I tried re-extracting zImage and running heimdall again, but it still failed. Then I tried using SGS Kernel Flasher instead and it worked. So I'm happily back to 2.6.35.7-I997UCLB3-CL977492 now.
Click to expand...
Click to collapse
Good! Glad you figured it out. Not sure why your transfer was wonky in Heimdall, as I've yet to see it fail like that.
Sent from my SGH-I997 using Tapatalk 2
Having trouble now getting the external_sd back. I'm using Root Browser Lite to edit vold.fstab, but when I save the file, the browser goes through the motions of saving it and claims to have succeeded, but when I examine the file it's unchanged. (The browser does claim to have superuser privileges.)
Gary02468 said:
Having trouble now getting the external_sd back. I'm using Root Browser Lite to edit vold.fstab, but when I save the file, the browser goes through the motions of saving it and claims to have succeeded, but when I examine the file it's unchanged. (The browser does claim to have superuser privileges.)
Click to expand...
Click to collapse
Does root browser have an option to mount a system folder as read/write? It sounds like you haven't mounted the directory for writing to it.
In Root Explorer, all you do is browse to the folder, select mount r/w, open the file in the built in text editor, edit, and choose "Save and Exit".
Sent from my SGH-I997 using Tapatalk 2
jscott30 said:
Does root browser have an option to mount a system folder as read/write?
Click to expand...
Click to collapse
No, not that I could find. So I switched to another app (FileSlick) for that, and now it's all working. Thanks again!
I'm still at the same error.
toshik1 said:
I'm still at the same error.
Click to expand...
Click to collapse
Same libusb error still means the same thing: You don't have the libusb drivers installed properly. Keep at it, and good luck.
Update: For those who don't want to mess with Heimdall and swapping kernels to get root on stock UCLB3, I've put together an Odin tar.md5 that will install the AT&T / Samsung 2.3.6 Gingerbread release with root already installed. This will install just like the Samsung leaks, and comes with all of the same stuff: stock kernel, etc. After I finish testing and uploading it, I'll start a thread in Development.
This will eliminate having to go through a long list of difficult steps to get root on stock UCLB3.
EDIT - I have a working tar.md5 for this, but need to work on it a little more before I post later this weekend.

Categories

Resources