Database Info

[GUIDE] Stock to CM5 - Rogers 911 Patched Dream (UPDATED FOR CM6 RC3 in Second Post!)

Please note, this is NOT my own work. It's on the CM Wiki, but since so many people seem to not want to be bothered to read the damn wikis for their intended purpose, I'm going to be a ratbastard enabler and post the steps HERE in a thread, so next time someone goes to post to ask how, IF they use the search function they'll find THIS thread and not threadnaught this forum with questions about how to do it.
This has been tested and works 100%. I have not tried it for CM6, and I don't suggest anyone try it on a 911 patched Rogers Dream until CM6 is stable AND there's a proper kernel image for Dream/Magic 32A/32B. As usual, I hold no responsibility if this bricks your Dream. I have made ROMs for the Raphael, Rhodium, Topaz, and Kaiser, and am an expert on those devices but this is my first actual Android device that I've had for less than a week, and just rooted/flashed it today, so I am NOT an Android expert AT ALL.
Original Guide: Here!
(Note: This guide is for CM5)
Step 1) Download all of the required software. SDK, Fastboot, Exploid from DroidXRoot, SPL 1.33.2005, Amon_Ra Recovery for CM, CM5 Itself, Googleapps, and extra kernel for Rogers Dream.
Step 2) Install extract the SDK archive and rename it to 'sdk' for easier use. In Windows, extract to C:\sdk, linux ~/home/sdk, mac .. wherever you want. Extract the Fastboot.zip to the sdk/tools folder. Move exploid, SPL, and Recovery to sdk/tools for easier use with adb.
Step 3) On your Dream, go to Settings->Applications->Development and enable USB Debugging, and connect your Dream to your computer via USB cable.
Step 4) Enter your sdk/tools directory and type the following:
Code:
* adb push spl-signed.zip /sdcard/1_33_2005_spl.zip
* adb push update-cm5* /sdcard/update-cm5*
* adb push gapps-ds-ERE36B-signed.zip /sdcard/gapps-ds-ERE36B-signed.zip
* adb push bc-5.0.x-ebi1-signed.zip /sdcard/bc-5.0.x-ebi1-signed.zip
* adb push recovery-RA-dream-v1.7.0R-cyan.img /data/local
* adb push exploid /sqlite_stmt_journals
* adb shell chmod 777 /sqlite_stmt_journals/exploid
(*whatever your CM image is.)
Step 5) Running Exploid!
Code:
adb shell /sqlite_stmt_journals/exploid
should produce the following:
Code:
$ adb shell /sqlite_stmt_journals/exploid
[*] Android local root exploid (C) The Android Exploid Crew
[*] Modified by birdman for the DroidX
[+] Using basedir=/sqlite_stmt_journals, path=/sqlite_stmt_journals/exploid
[+] opening NETLINK_KOBJECT_UEVENT socket
[+] sending add message ...
[*] Try to invoke hotplug now, clicking at the wireless
[*] settings, plugin USB key etc.
[*] You succeeded if you find /system/bin/rootshell.
[*] GUI might hang/restart meanwhile so be patient.
Now unplug/replug USB cable to apply exploit. ROOOOOTED!
Step 6) Custom Recovery time!
Type the following:
Code:
adb shell
this will take you to a $ prompt (that's the shell.)
Code:
rootshell
this will ask for a password, which is 'secretlol' without quotes.
Now that you're at a root shell, type
Code:
chmod 666 /dev/mtd/mtd1
exit
Now you're back at the regular shell prompt, type:
Code:
flash_image recovery /data/local/recovery-RA-dream-v1.7.0R-cyan.img
If this gives a "mtd: read error at 0x00000000 (Out of memory)" error, it's okay, just type it again and it should work without the error. This is normal, do not panic.
Once this is complete, type
Code:
exit
and power down the phone. (long hold end key)
Step 7) SPL
Hold Home and press the End key to power up the Dream. At the recovery menu select
Code:
Flash Zip from SDCARD
and select the
Code:
1_33_2005_spl.zip
.
Now reboot by holding home+back. It will take you back to the recovery shell, and this is okay. This is actually what we want. Now, type
Code:
adb shell reboot bootloader
and watch the screen to verify that you see:
Code:
HBOOT: 1.33.2005
RADIO: 3.22.26.17
Now, run the following Fastboot commands:
Code:
fastboot erase system -w
fastboot erase boot
fastboot oem powerdown
Step 8) Flashing CM!
Press home+end to power up the phone in recovery mode, and select
Code:
Flash Zip from SDCARD
, Select your CM image, then
Code:
Flash Zip from SDCARD
and select gapps-ds-ERE36B-signed.zip, and finally
Code:
Flash Zip from SDCARD
and select bc-5.0.x-ebi1-signed.zip.
Once that is complete, home+back to reboot, and you're done. That's it. First CM boot may take 5-15 mins.

Reserved for updates
Click to expand...
Click to collapse
Time for the update!
CyanogenMod6rc3
EBI1 Kernel for CM6rc3
Google Apps, Mdpi Tiny for CM6
Use these the same way you would in the above steps for flashing CM5, obviously replacing the zip files from CM5 with the ones from CM6 during the adb push, and the flashing from zip in recovery console. This should work exactly the same as the above version, but the end result is that you'll have FroYo instead of Eclair.
I waited until RC3 for this update because, in my opinion, RC2 was a bit laggy and overall wasn't as stable.
Also note: This process will work for roms OTHER than CyanogenMod so long as they're either based on CM or have an EBI1 Kernel available. Make sure you use the correct EBI1 Kernel by checking what gapps version the Rom uses if it's CM-based but doesn't link to an EBI1 Kernel. For example, if it's gapps-mdpi-FRF91-3 then it's the CM6rc2 EBI1 Kernel you need.
Any questions? Post 'em here.

Thanks for posting this. I know some people got confused.

I highly recommend people also look at the pre existing thread: http://forum.xda-developers.com/showthread.php?p=7306638#post7306638 if they have questions as that is where the q/a is at.

ezterry said:
I highly recommend people also look at the pre existing thread: http://forum.xda-developers.com/showthread.php?p=7306638#post7306638 if they have questions as that is where the q/a is at.
Click to expand...
Click to collapse
The difference is your thread is a vague shortened process that assumes people are going to follow all the links in your post and read through pages of comments to figure out the exact steps of your "simplified process", where my thread gives them a one-stop-shop from stock to a stable rom. You've linked to your thread, so now people who don't mind looking around then posting tons of questions have their place to go.
Tl;dr version: this thread is for the people who can barely be bothered to use the search function and want everything in one place, your thread is for "everyone else".
Sent from my HTC Dream using XDA App

agentfusion said:
The difference is your thread is a vague shortened process that assumes people are going to follow all the links in your post and read through pages of comments to figure out the exact steps of your "simplified process", where my thread gives them a one-stop-shop from stock to a stable rom. You've linked to your thread, so now people who don't mind looking around then posting tons of questions have their place to go.
Tl;dr version: this thread is for the people who can barely be bothered to use the search function and want everything in one place, your thread is for "everyone else".
Sent from my HTC Dream using XDA App
Click to expand...
Click to collapse
Don't worry I'm following this thread so *I* don't inadvertently support people who don't follow links.

It just sucks that people really are that lazy. Seriously. They waste more time typing a question that has been answered 20 times than it would take to search for the proper answer.
So yeah, thanks for posting a topic that has a lot of great information for those of us who aren't lazy, I do personally like yours and think it should be in the informative links sticky. I just wish I had found yours first while I was searching for my answers because it really is informative for those of us not afraid to read and not have things spoonfed to them.
Sent from my HTC Dream [CM5] with xda app.

Thanks for the How-To. It was very easy to follow.

AverageCanadian said:
Thanks for the How-To. It was very easy to follow.
Click to expand...
Click to collapse
No problem! Glad you found it useful. All of those steps now work for CM6, so I will be adding links for CM6rc3 later tonight
Sent from my HTC Dream using XDA App on CM6rc3

update bump.

Tks for the guide. Total newbie here and trying to root my HTC Dream.
Up to now, i fallowed WIKI loll to the letter, tho, when i try to download the EXPLOID, either from your link or the WIKI one, it pup's out as a TROJAN program Exploit.Linux.Lotoor.e !
Is it safe to get it or i shouldn't go there???
I'm stuck to this step now and not sure what to do
Tks for the info..

Wood's said:
Tks for the guide. Total newbie here and trying to root my HTC Dream.
Up to now, i fallowed WIKI loll to the letter, tho, when i try to download the EXPLOID, either from your link or the WIKI one, it pup's out as a TROJAN program Exploit.Linux.Lotoor.e !
Is it safe to get it or i shouldn't go there???
I'm stuck to this step now and not sure what to do
Tks for the info..
Click to expand...
Click to collapse
To the best of my knowledge, it comes up as a trojan because it's a rootkit for Android, which is based on Linux... so virus scanners will consider Exploid as a "virus/trojan" because using a rootkit on a linux machine is basically using a trojan to get root access, which is what you're doing to your phone.. you're using an exploit to get root access.

[TOOL] sbf Flashing in Linux for Windows with Ubuntu Live CD

Here's a custom Ubuntu LiveCD made with ADB and the Linux sbf_flash script for sbf flashing your Droid 2 if you've failed in Windows with RSDlite or just want to have the convenience of flashing with only two Linux commands.
PLEASE READ ENTIRE POST BEFORE FLASHING ANYTHING!
If you want to follow this tutorial on your existing linux setup the sbf_flash file can be found on Google
READ OR RISK BRICK If you don't have the 2.3.2 update then you can sbf with EITHER the 2.2.0 (stock) or the 2.3.2(OTA update) but only if you don't have the update yet. Once you have the 2.3.2 update (through sbf or update.zip) you can ONLY sbf with the 2.3.2.sbf
Please have your phone charged up if not completely near complete or risk dealing with the consequences
Thanks Androidnite
1. Download 2.2.0.sbf file (for Droid 2 without 2.3.2 update only) or 2.3.20 HERE (for Droid 2's that have the 2.3.20 update) and put it on a flash drive. Yes even if you have one that you used with RSDlite.(this way we know you have the right one and it's all there)
2. Download the LiveCD ISO via torrent file attached below and unzip it and open the file with your choice of torrent program then BURN the downloaded file to a blank CD with your favorite burning software(I like DVD Decrypter or Imgburn). I recommend no faster than 4x in order to prevent burning "coasters".
3. Make sure your computer's BIOS is set to boot from the CD Drive then start your computer with the Disk in the drive.
4. Wait for the language list to pop up select "English". Then select "Try Ubuntu without installing"
5. Take the flash drive you put the .sbf file on and put it in your computer’s USB port and copy it to the same directory as the sbf_flash file. It will be the “Home” folder.
6. Plug your phone in via USB now and turn it off then hold the ‘up’ arrow on the keyboard and power on the phone to go into the bootloader.
NOTE: If your phone is not in operating condition Hold the 'UP' arrow on your keyboard and power on your phone for it to be recognized by your computer by entering the bootloader.
7. Open a command prompt by ‘CTRL+ALT+T’ or Applications>Accessories>Terminal
8. Type the first command then press enter and then do the same with one of the last two commands depending on the sbf you are trying to flash.
For both sbf's
Code:
chmod +x sbf_flash
Then
For the 2.2.0 sbf ONLY*OLD SBF*
Code:
sudo ./sbf_flash DROID2_X6_2.2.20_SHADOW_BP_C_01.09.05P_P2_USERBLD_SECURE.sbf
Or
For 2.3.2 sbf ONLY
Code:
sudo ./sbf_flash VRZ_A955_2.3.20_1FF_01.sbf
NOTE: every space in the .sbf's title should be taken by an underscore "_" and shouldn't contain other spaces or the command will not be recognized because it doesn't follow the command's syntax.
Now your phone should start flashing. Let it go and it should reboot in 20-30 minutes.
That should be it let me know what problems you have.
Boot Loop?
facelessuser said if you get a boot loop after flashing wipe your data and cache in recovery.
Instructions:
1. Pull your Battery.
2. Replace battery and power on while holding down the X key.
3. Wait for the android triangle to load.
4. Press the Search key (the magnifying glass)
5. Use down arrow and navigate to wipe data/factory reset and press OK.
6. Reboot phone.
Click to expand...
Click to collapse
These instructions are by theecho.
Not getting the updated baseband? From BP_C_01.09.05P to BP_C_01.09.07P
NOTE: Be sure to update your baseband before you load a custom ROM as the update needs to see the blur on your phone.(If you root it before updating you might not be rooted afterward I don't know).
After you sbf with the 2.3.20 sbf file above and you don't see and updated baseband then you can use the Update.zip
to update your baseband by:
1. Download the update.zip and put it in the /sdcard/ folder or the root of the sdcard (same thing)
2. Shutdown D2
3. While you hold the 'X' button on the keyboard, turn on the D2
4. You should be in Stock recovery not Clockwork Recovery.
5. Press the 'magnifying glass' (search) button on keyboard to bring the menu up
6. Use the volume buttons to scroll and the Camera button to Select 'apply sdcard:update.zip'
7. Then choose 'reboot system now' and you should have an updated baseband.
Click to expand...
Click to collapse
Thanks for the info Quackers
Thanks:
First, thanks Matt4542 for putting the flashing in Linux tutorial which the commands I used were adapted from.
Next, a thanks to theecho for hosting the files for everybody’s access and making this really easy for me as I am a newbie to file hosting.
Last, but not least the inspiration for the custom Ubuntu ISO and help while making it...shad0wf0x from the XDA HTC Aria section(s) needs a thank you as well.
Please keep issues on this thread to allow faster responses.
Even if you used the RSDlite method by Darkonion first. RSDlite related posts should go there and Ubuntu method posts stay here.
Thanks and may your Droid 2 live on!

This sounds convenient. I am going to add this to the information directory.

I just want to say Thank you from the bottom of my heart for un-bricking my Droid 2 with the Ubunta Live CD program you created. I truly thought my phone was dead! I would very much like to send a donation your way for all the hard work you put into this. Please let me know by PM on how I can send the donation. Again, Thank you Thank you Thank you!!!!
Sent from my DROID2 using XDA App

lol no problem but i just enabled you to get to the flashing it was matt4542 and his linux tutorial that really fixed your phone....but if you really want to donate just head to the site where the files are hosted http://Droid2files.com and click on the donate button under my pic (yes that's what I really look like lol).
I thank you for wanting to thank me and for wanting to contribute to my well being!
p.s. think about thanking matt4542 and TheEcho for hosting the files (for FREE) and shad0wf0x for inspiring the LiveCD.

newk8600 said:
lol no problem but i just enabled you to get to the flashing it was matt4542 and his linux tutorial that really fixed your phone....but if you really want to donate just head to the site where the files are hosted http://Droid2files.com and click on the donate button under my pic (yes that's what I really look like lol).
I thank you for wanting to thank me and for wanting to contribute to my well being!
p.s. think about thanking matt4542 and TheEcho for hosting the files (for FREE) and shad0wf0x for inspiring the LiveCD.
Click to expand...
Click to collapse
Okay, donation just sent to you and TheEcho!
Now I just need a way to send Matt4542 and shad0wf0x their donation

Well Matt4542's donate link is here and I'm checking with shad0wf0x about his.
And thanks again for your donation(s)!

Got Ubuntu installed - files transferred to "home"/ubuntu directory - phone connected in bootloader - first chmod flash command didn't seem to do anything (returned to $ prompt), 2nd sbf flash gives command not found error - what am I doing wrong?

Jacklad said:
Got Ubuntu installed - files transferred to "home"/ubuntu directory - phone connected in bootloader - first chmod flash command didn't seem to do anything (returned to $ prompt), 2nd sbf flash gives command not found error - what am I doing wrong?
Click to expand...
Click to collapse
Click on the browser icon and navigate to this page. Then try using the copy/paste feature rather than typing it in yourself.
Sent from my DROID2 using XDA App

newk8600 said:
Well Matt4542's donate link is here and I'm checking with shad0wf0x about his.
And thanks again for your donation(s)!
Click to expand...
Click to collapse
You are more than welcome!
Matt's donation has been made, and patiently waiting to make donation to shad0wf0x

Jacklad said:
chmod flash command didn't seem to do anything (returned to $ prompt), 2nd sbf flash gives command not found error - what am I doing wrong?
Click to expand...
Click to collapse
The first command changes permissions (chmod) for 'sbf_flash' giving it the ability to execute (-x) so you won't see anything unless you change directory (cd) to the file and then list it with it's permissions with ('ls -l' both being lowercase L's)
For the second one can you tell me which command it can't find.
Is it troubled with 'sudo' (do with super user priveleges) or with sbf_flash. You might not have typed it in correctly. Remember the space between 'sudo' and './'
Sent from my DROID2 using XDA App

Terri M said:
You are more than welcome!
Matt's donation has been made, and patiently waiting to make donation to shad0wf0x
Click to expand...
Click to collapse
No donation necessary, happy to have helped, if you really want to donate to somebody, donate to the EFF (http://www.eff.org/).

I agree with shad0wf0x the EFF is helping with litigation on behalf of the Yes Men. If you don't know who they are I'd wiki them. They do some pretty amazing things.
Sorry I got off topic. lol

Jacklad said:
Got Ubuntu installed - files transferred to "home"/ubuntu directory - phone connected in bootloader - first chmod flash command didn't seem to do anything (returned to $ prompt), 2nd sbf flash gives command not found error - what am I doing wrong?
Click to expand...
Click to collapse
Alright, I'm having the same problem. I have bootloader up and the files transferred, here is what i typed in the terminal and what it gave me:
[email protected]:~$ chmod +x sbf_flash
[email protected]:~$ sudo ./sbf_flashDROID2_X6_2.2.20_SHADOW_BP_C_01.09.05P_P2 _USERBLD_ SECURE.sbf
sudo: ./sbf_flashDROID2_X6_2.2.20_SHADOW_BP_C_01.09.05P_P2: command not found
[email protected]:~$
I copied and pasted it directly from the post, so I don't know what is going wrong here. Please help.

Sudo ./sbf_flash droid2...... The problem is the lavk of a space netween sbf_glash and the filename
Sent from my DROID2 using XDA App

zibrah3ed said:
Sudo ./sbf_flash droid2...... The problem is the lavk of a space netween sbf_glash and the filename
Sent from my DROID2 using XDA App
Click to expand...
Click to collapse
Failed again, but in a new way.
[email protected]:~$ chmod +x sbf_flash
[email protected]:~$ sudo ./sbf_flash DROID2_X6_2.2.20_SHADOW_BP_C_01.09.05P_P2 _USERBLD_ SECURE.sbf
SBF FLASH 1.08 (mbm)
DROID2_X6_2.2.20_SHADOW_BP_C_01.09.05P_P2: No such file or directory
!! failed
im guessing that the file in the home folder has a slightly different name with spaces n stuff? I know my name doesnt have the spaces around the _USERBLD_ would that mess it up?

im guessing that the file in the home folder has a slightly different name with spaces n stuff? I know my name doesnt have the spaces around the _USERBLD_ would that mess it up?
Click to expand...
Click to collapse
Yes if the file name isn't exaclty the same it will show an error. Go to the file and right click it and select the filename and copy it. Then put it in place of the filename that registered the error. I'll check into the filename problem.
Sent from my DROID2 using XDA App

Sweet! It's finally started flashing. Hopefully it won't run into anymore weird things. Thanks a ton for the help!!

mgalceran said:
Thanks a ton for the help!!
Click to expand...
Click to collapse
No problem thanks for pointing out the name difference.
Sent from my DROID2 using XDA App

trying to unbrick my cousin's droid 2...i followed the directions carefully and I keep getting "waiting for phone" message in terminal, but I already have the phone plugged in and it is in bootloader mode, why won't it detect?

Thanks a lot for the help! My phone was doing the boot loop so I followed your guide. Now everything is just like it was when I got the phone. When everything was done and the computer said the phone was rebooting I still had the boot loop issue. I then saw where facelessuser said you have to clear the cache, so I did and she booted up normally.
Something funny to note, in the terminal it said Droid X found, I thought that would be an issue but everything worked fine.
Thanks again, you saved me!

[Tool][Guide]Linux tools

I. How to root Defy via Linux!
A simple script for rooting Defy from Linux. I use SuperOneClick 1.9.1 files in my script, and I rooting succesfully my device from Ubuntu 11.04.
It does not install "bussybox" and "Android Terminal", just "su" and "Superuser.apk".
I hope it will work for someone else too.
Using:
0. install usb grants on your computer (see adb install method)
1. unzip file
2. run RootDefy.sh
3. after succesfully install, reboot phone (./adblinux reboot)
Download:
(version 0.2) download
Changelogs:
Code:
[B]02.06.2011:[/B] Version 0.2
- Added header to script
[B]13.05.2011:[/B] Version 0.1
- correct Defy device number
- correct /system filesystem type and path
[B]12.05.2011:[/B] First release
II. How to flash a SBF via Linux!
0. charge your phone 100%!
1. download and extract your sbf file: download
2. download sbf_flash file (same directory): download, or see the editor blog
3. chmod +x sbf_flash
4. sudo ./sbf_flash xxxxxx.sbf
Now your phone should start flashing, and phone will reboot when finish it.
III. How to unroot Defy via Linux!
Go to this topic: link

Nice, will try this =)

nice work!
I have been looking for it
Thx.

Great. I'm under linux too, each time I root a rom I launched a script from sdcard. For next time I'll test your script.
Fyi, I flash rom under linux too. I use 'sbf_flash', that works very well!
( but unsuccessfull under mac )
Now I'm looking for deodex script. I wrote and test some but still get errors with some apk and jar
Sent from my MB525 using XDA App

rumcajsz said:
I made a simple script for rooting Defy from Linux. I use SuperOneClick 1.9.1 files in my script, and I rooting succesfully my device from Ubuntu 11.04.
It does not install "bussybox" and "Android Terminal", just "su" and "Superuser.apk".
I hope it will work for someone else too.
Using:
0. install usb grants on your computer (see adb install method)
1. unzip file
2. run RootDefy.sh
3. after succesfully install, reboot phone (./adblinux reboot)
Download:
link
(sorry for my bad english)
Click to expand...
Click to collapse
I believe that this script will not work for Motorola Defy for the following reasons:
1)on lines 17-19 the script checks if there are any udev rules matching a Samsung device (for Samsung devices the idVendor attribute is 04e8, but for Motorola devices, the idVendor attribute is 22b8).
2)on line 53 you are remounting the /system partition specifying that the file system is yaffs2 and the device block is /dev/block/mtdblock0.
On my Defy the file system used is ext3 and the device is /dev/block/mmcblk1p21
I have managed to root my defy a few days ago, from my linux box, using the files used by Sooperonelick (rageagainstthecage, superuser.apk, su and busybox) but considering the facts stated above.
@MisterWB
Fyi, I flash rom under linux too. I use 'sbf_flash', that works very well!
( but unsuccessfull under mac )
Click to expand...
Click to collapse
Did you used the last version for sbf_flash? On the original site its stated that the same binary should work on linux and mac

tuxtm said:
I believe that this script will not work for Motorola Defy for the following reasons:
1)on lines 17-19 the script checks if there are any udev rules matching a Samsung device (for Samsung devices the idVendor attribute is 04e8, but for Motorola devices, the idVendor attribute is 22b8).
2)on line 53 you are remounting the /system partition specifying that the file system is yaffs2 and the device block is /dev/block/mtdblock0.
On my Defy the file system used is ext3 and the device is /dev/block/mmcblk1p21
I have managed to root my defy a few days ago, from my linux box, using the files used by Sooperonelick (rageagainstthecage, superuser.apk, su and busybox) but considering the facts stated above.
Click to expand...
Click to collapse
Thanks for the advice, I will correct their lines ...

You're welcome.
If you want to make a script that will work on all devices you could parse the /rpoc/mounts file from the device and extract the device that's mounted to /system and the file system used (in this case the udev part would also need to be modified)
Also, did you check if the adb binary you are using doesn't need any other external libraries installed by Android SDK. I'm asking this because in the sooperoneclick zip I downloaded, I saw some dll files which I' guess that are used by the adb windows binary, and I don't know if the linux adb binary doesn't need some external libraries, which should also be included in your zip file.
Good luck

tuxtm said:
@MisterWB
Did you used the last version for sbf_flash? On the original site its stated that the same binary should work on linux and mac
Click to expand...
Click to collapse
Yes I use it on mac+linux... but on my mac, at beginning sbf_flash see my phone, but when I want to flash a sbf, sbf_flash freeze on message "waiting for phone" It seems usb behavior varies on mac models.
Anyway, thanks for your reply.
@everyone
This thread could-be a good space to exchange about linux tools.
In this case rumcajsz should change the first post's title, and maintain text, links ...
What do-you think about ? Or do-you prefer a new thread ?

MisterWB said:
Fyi, I flash rom under linux too. I use 'sbf_flash', that works very well!
Sent from my MB525 using XDA App
Click to expand...
Click to collapse
where can i download sbf_flash?
thank you.

MisterWB said:
@everyone
This thread could-be a good space to exchange about linux tools.
In this case rumcajsz should change the first post's title, and maintain text, links ...
What do-you think about ? Or do-you prefer a new thread ?
Click to expand...
Click to collapse
Great idea, I changed it.
johnw.xda said:
where can i download sbf_flash?
thank you.
Click to expand...
Click to collapse
The download link in the first post now.

usb tether
Hi,
thanks for both script, works well for me.
I like: go first to recovery menu (vol donw and power) with usb connected and run the flashing script, perfect...
How do you usb tether with your defy and linux ? (ubuntu)
I use this a lot with my previous phone htc.
I run the french froyo rom (http://forum.xda-developers.com/showthread.php?t=1072367), but i did not found the m.stone usbtether app.
Maybe you got a sbf with every things working natively with linux and no blur?
Regards and BRAVO again...

usb tether
Usb tether is ok with proxoid and port fowarding with the defy (see proxoid wiki).
It is not like my old htc as the device is seen by the pc as a network interface (usb0). In this way you got an IP to communicate with your phone (i am using it for vlc remote for example and other app where ip is needed).
When i plug my defy on usb I got 3 menu: motorola pc, windows sync, sd and nothing.
Is there a way to have menu without motorola and windows stuff ? ( sorry for duplicate the question between this form and the french froyo rom one...)
++

That option should be related to the Media Portal application. Maybe if you would rename it (by changing the apk extension to something else) would do the trick. I didn't test this so, I can not tell you if it will work or if it won't brick your phone
/LE I have just renamed the MediaPortal.apk and apk for the Media Share (I belive it is HomeSyncWizard.apk)then rebooted the phone, but the "Portal and Tools" and "Windows Media Sync" options are still there.

I have to check what is the difference between HTC and motorola.
Tkx for the try,

added "unroot" to first post

On an aside, superoneclick and sbfdepacker can both be ran with mono
If you running 64bit distro ensure libncurses 32bit is installed

I tried SOC & mono (ubuntu 10.10, 11.04: 32 bit), and it doesn't worked for me.

http://forum.xda-developers.com/showpost.php?p=8699742&postcount=537
Follow the link on there, it will work although the script's here do it just as well anyway, but the sbfdepacker, I can find no equivalent of.

I tried this way...

Hi,
If
i root an froyo offical french rom with this script to backup my stuff
install 2nd-init
upgrade to an GingerRom with fixed sbf
then flash back the official french sbf
will i keep my warranty ?
No way to find out i rooted my defy?
I will try mono...

[ROOT + CWM + OC KERNEL + Ubuntu] ZTE V11A / V71A / v55 HC3.2

The information provided in this thread is no longer up to date, although useful troubleshooting information can be found for those having issues. For those who would prefer to have the most up-to-date versions of CM9, CM10 or ParanoidAndroid supported by an awesome developer, go here
WARNING: IF YOU UPDATE YOUR TABLETS TO THE LATEST v03 UPDATES OF THE OFFICIAL ROM, YOU WILL LOSE THE ABILITY TO ROOT IT USING THE SUPERBOOT METHOD AND IT WILL BECOME A HUGE PAIN TO RE-INSTALL CWM/CUSTOM ROMS. INSTRUCTIONS FOR THIS SITUATION ARE PRESENTED BELOW, BUT PLEASE KEEP THIS IN MIND AND TRY TO READ THE THREAD CAREFULLY BEFORE MAKING SUCH CHANGES.
For those who need it, you can find a nandroid backup of Vodafone Romania's stock ROM for the v71a, here
Hello friends. With great thanks to utkanos, Koush and mobilx we now have a public alpha CWM and root available on both the ZTE V11A and the V71A, also known as the SFR StarTab 7/10, Vodafone SmartTab 7/10, as well as Sprint's (ZTE) V55 with credits due to utkanos for porting CWM, mobilx for being arguably the most motivated searcher of the holy root grail, and PaulOBrien from modaco and his superboot solution. We also thank alterbridge86 and eldarerathis for their advice and support. Additionally, credits go to joe.stone for custom kernel with loop device support, OC, touched voltages and a few other goodies.
Also, for interested developers, I have made the source code of the kernel available in a more easily accessible fashion. The source code (3 parts, contains the source for both models) is available here:
Part 1, Part 2, Part 3.
INSTALLING CWM:
A new optimized version of CWM for 7"and 10" tabs has been put together by joe.stone. I will also keep utkanos' links available below for those who prefer his versions or wish to thank him for his early efforts in making our tablets awesome
joe.stone said:
For those who have troubles with cwm recovery (freeze while backup ) i have created a new version. Flashable from fastboot.
10" CWM Recovery
7" CWM Recovery
Credit goes to joe.stone.
Click to expand...
Click to collapse
joe.stone said:
If you updated your tablet ROM via OTA or updater exe and can no longer install CWM, follow the following instructions:.
In firmware v03b fastboot flash is disabled and from a running system flash_image will fail too.
Download the twrp recovery http://goo.im/devs/joestone/twrp/v71_recovery.img
download the twrp recovery zip flashable version too
http://goo.im/devs/joestone/twrp/V71A_TWRP.zip
download kernel #60
http://www.4shared.com/zip/tzrUo5_N/v7_kernel_60.html?
copy the two zip files to the sdcard
If you want flash kernel#60 then do the following:
adb reboot bootloader
the tablet will reboot and you will get only a blank screen . Be sure that the drivers are installed from windows update for the fastboot interface.
check it with : fastboot devices. If you get waiting for device the drivers are not installed.
fastboot boot v71_recovery.img
The twrp recovery comes up. Now you can install twrp by selecting install menu. Browse to the v71twrp.zip on the sd and install it. Now you have permanent twrp recovery.
now go back to install menu browse to the v7_kernel_60.zip and install it.
reboot and enjoy.
These are kernel #60 links for the other models :
Sprint Optik (V55)
http://www.4shared.com/zip/RTZrSXyV/v55_kernel_60.html?
SmartTab10 (V11A)
http://www.4shared.com/zip/PrW1TWHF/v10_kernel_60.html?
OR
You can flash cwm using adb , you need root rights .The best is when adbd is running in root mode (for eaxample kernel#60).
Download this :flash_image binary
then turn on usb debugging.
to flash cwm you need the following commands:
adb push CWMrecovery.img /data/local/tmp
(where cwmrecovery.img is the name of the cwm image file name.)
adb push flash_image /data/local/tmp
adb shell chmod 755 /data/local/tmp/flash_image
adb shell (you need # not $ for flashing , so if you got $ type su to get #)
cd /data/local/tmp
./flash_image /dev/block/mmcblk0p18 CWMrecovery.img
Dont forget to remove the install-recovery.sh file from /system/etc othervise it will install stock recovery at system start if it has not the stock recovery.
To revert the bootloader you need to flash NON-HLOS.bin"to "/dev/block/mmcblk0p1" and "emmc_appsboot.mbn" to "/dev/block/mmcblk0p7" from a previous version .
Click to expand...
Click to collapse
Utkanos' v11a version is here.
Utkanos' v71a version is here.
Credit goes to utkanos, mobilx and koush. I have also attached these files at the end of the post.
Also attached, is the original 7-inch stock recovery file, for users who may wish to return to stock and have not performed backup.
--> Plug your tablet into usb, launch a command line, and use "adb reboot bootloader"
--> Download the CWM Recovery image from the link that fits your device.
--> Place it into the adb/fastboot folder (I am assuming you have downloaded fastboot already from the link above, during the root procedure).
--> In the command line, navigate to that folder (use "cd <path>").
--> input the command "fastboot flash recovery <filename>".
--> Reboot into recovery mode (should be Power + Volume down).
--> You should now be in CWM Recovery, and can now attempt to perform a nandroid backup.
Also, in order to prevent a possible hang, you should:
--> Reboot the tablet into the Android OS;
--> Mount it through USB;
--> Go into the clockworkmod folder;
--> Create an empty file with no extension called ".hidenandroidprogress"
After a period of testing this will be submitted to the Koush's Rom Manager. Source code is also available herehere, linked from utkanos' post.
What works:
Nandroid backup/restore on internal sdcard
Battery stats wipe
Dalvik wipe
Cache wipe
etc.
What does not work so far:
USB mass storage
credits:
utkanos
Koush
Click to expand...
Click to collapse
Modified Kernel Available, all credits to joe.stone, give him thanks here:
joe.stone said:
Here it is.
There is a new kernel version available. The new version is #60 and flashable from cwm recovery .
Changelog :
-Revert GPU overclock
-Revert change of system audio files (because of bootloops on some devices after installation #55)
-Increased system volume on kernel level
-Changed VMALLOC_RESERVE=0x19000000 to VMALLOC_RESERVE=0x10000000
-Added Apple Magicmouse HID support
-Added Microsoft HID support
-Changed cpu minimum freq 345MHz to 432 MHz to avoid the black screen effect (the screen does not wake up , you have to reset )
V55_kernel_60.zip Hope will work fine on v55.
V7_kernel_60.zip
V10_kernel_60.zip
Click to expand...
Click to collapse
Also, Benny3 has put together a CWM-flashable ROM package for the V55 tablet, including Joe's kernel #60 and a number of useful goodies. You can thank him and download the package from here.
Both device (v71, v11) were migrated into one kernel tree , so they both use the same source. (In case of v71 it is much newer source)
The whole kernel source was updated from the v55 sources .
Now they are in cwm recovery flashable format , because this package updates the kernel modules too in /system/lib/modules and enables to use the agps and NTP server setting was corrected . It points to europe.pool.ntp.org instead of the test one . Now my tab finds position within seconds . With the new kernel for me it seems the touchscreen is much better , but as before I am waiting for the feedbacks. Other fixes include: Touchscreen sensitivity, USB Charging etc.
Installation :
download the zip file
copy it to your tab's internal storage
start the tab in clockworkmod recovery
select install zip from sdcard
select the file for your model
install
reboot
and stock kernel for 10" :
stock kernel[/QUOTE]
Finally, if you want to obtain a dump of boot.img, please consider the following advice, also by mobilx, here:
mobilx said:
It is a mmcblk device not mtdblock
dd if=/dev/block/mmcblk0p8 of=/sdcard/boot_backup.img
dd if=/dev/block/mmcblk0p18 of=/sdcard/recovery_backup.img
Click to expand...
Click to collapse
ROOTING:
mobilx said:
It is recommended that you skip these steps and proceed to flashing clockwork mod for your respective device from the start using fastboot, and from inside CWM install joe's kernel (or custom rom), which you can find below. Joe's kernels and rom already come with significant updates to stock Vodafone systems, and are pre-rooted.
We will use superboot to root. What does superboot do? It puts the SU binary and makes a 'insecure' kernel to be loaded temporarily on to the device through ADB remount. So it's only purpose is to make ROOT. After execution, you will still be on the stock kernel, only with root privileges.
This method is for the advanced users only who want to have root before we have a fully functional CWM running. With the CWM the root method will be easier.
IMPORTANT!
At this point we have no way to repair a broken device to a factory state. We can unroot and that is it. It is advisable do make dump of your rom before making any changes to the system. We are not responsible for any damage that can occur in the root process and after that.
What will you need?
--> Download Fastboot+Superboot.img from here.
--> Install ADB through the SDK, download from here, although the ADB included with the ZTE drivers should also work.
--> Install the ZTE drivers, you can find them here, although they should already be included on your device when first mounting it.
--> don't forget to enable USB debugging in the tablet's application settings.
--> Put the fastboot.exe and the superboot.img files in the working directory you will be running adb from (Default should be at "C:\Program Files\ZTE Handset USB Driver".
--> Open a Command Line (Start Menu > Run > CMD) and navigate to the working directory. (Use "cd C:\Program Files\ZTE Handset USB Driver" or alter the path accordingly).
--> Write the following commands withing the command line:
--> adb reboot bootloader
--> fastboot boot superboot.img
--> The device should now boot with the Superuser.apk installed and SU in the /system/xbin/su, as well as allowing you adb root commands. Now run the following:
--> adb remount
--> adb shell
--> ln -s /system/xbin/su /system/bin/su
--> You can now exit the ADB shell and reboot the tablet.
--> Install busybox from the market and check the SU binary version with the Superuser.apk - try to update. If it succeed you are done.
Credits:
sangemaru
utkanos
PaulOBrien from modaco and his superboot solution
Click to expand...
Click to collapse

Reserved for future posts

I have ZTE V11A aka Vodafone Smart Tab 10 in my possession
I'm very interested in obtaining root for this device, so if I can be of any help, please let me know.
I hope that whis device will gain more popularity in the near future, because of it's excellent hardware and low price.
Is there any progress going on with rooting this device?
P.S. Two more questions,
Has anyone found where to buy 40pin to hdmi cable/connector? (because you don't get one in the box)
Does any of you experience clock drift with your device after some time, mine is drifting forward about 20min per day with no automatic Network Sync.
Thank you.

assdksl said:
I have ZTE V11A aka Vodafone Smart Tab 10 in my possession
I'm very interested in obtaining root for this device, so if I can be of any help, please let me know.
I hope that whis device will gain more popularity in the near future, because of it's excellent hardware and low price.
Is there any progress going on with rooting this device?
Click to expand...
Click to collapse
Currently, me and mobilx are trying to put aside time to either:
obtain a dump of the boot.img that we can inject su and superuser.apk into;
compile the source code into a flashable rom that we can inject su and superuser.apk into;
get clockworkmod working on the device;
Due to time constraints, I haven't made much headroom this week, but I'm taking a couple of days off work and hope to make some progress.
P.S. Two more questions,
Has anyone found where to buy 40pin to hdmi cable/connector? (because you don't get one in the box)
Does any of you experience clock drift with your device after some time, mine is drifting forward about 20min per day with no automatic Network Sync.
Thank you.
Click to expand...
Click to collapse
Haven't looked for it, but so far accessories for this line of devices seem to be lacking. With the popularization by Vodafone and the launch of the new Sprint V55 and similar tablets, these accessories should become more popular.
I haven't had any problems with the time on my device, sounds really weird.

assdksl said:
Does any of you experience clock drift with your device after some time, mine is drifting forward about 20min per day with no automatic Network Sync.
Click to expand...
Click to collapse
Clock drift is happening due to Network-provided time setting. Im not sure what is causing this. It could be related to a Vip network or a failure of a process which obtains time from the network. If you want this not to happen just untick that option in settings.

Thank you both for quick answering my questions.
mobilx said:
Clock drift is happening due to Network-provided time setting. Im not sure what is causing this. It could be related to a Vip network or a failure of a process which obtains time from the network. If you want this not to happen just untick that option in settings.
Click to expand...
Click to collapse
Yes, indeed, but when I untick sync with Network-provided time, clock is ticking faster then it should.
It seems that clock chip on my device is not calibrated well or there is some other bug, it seems that it is HW issues... this is little more explained here:
http://blogs.keynote.com/mobility/2...wrist-watch-android-doesnt-keep-the-time.html
It seems that I was unfortunate and get device with bad clock, also without root I'm unable to use ClockSync app that will solve my problem.
But what is bugging me, is the fact that I also have SGS I9000, and it is synchronizing with Vip network just fine.
Mobilx are you experiencing time drift issue with network-provided time sync, but with manual time settings it is working fine?
sangemaru said:
Currently, me and mobilx are trying to put aside time to either:
obtain a dump of the boot.img that we can inject su and superuser.apk into;
compile the source code into a flashable rom that we can inject su and superuser.apk into;
get clockworkmod working on the device;
Due to time constraints, I haven't made much headroom this week, but I'm taking a couple of days off work and hope to make some progress.
Click to expand...
Click to collapse
I am a software developer, and I have some Android programming knowledge, but I'm not experienced much with Linux and compiling flashable Roms, but I can try In any case, if I can help, just let me know.

assdksl said:
Mobilx are you experiencing time drift issue with network-provided time sync, but with manual time settings it is working fine?
Click to expand...
Click to collapse
Yes it happend to me once. First I unticked the network-provided time sync and after restart I ticked it again. The clock is fine since than.

assdksl said:
I am a software developer, and I have some Android programming knowledge, but I'm not experienced much with Linux and compiling flashable Roms, but I can try In any case, if I can help, just let me know.
Click to expand...
Click to collapse
Well, so far what possible leads we have that I can think of are these:
mobilx suggested this thread http://forum.xda-developers.com/showthread.php?t=443994 for packing/unpacking boot.img
to quote Alterbridge of Team Overcome: "I presume the ZTE tablet uses boot.img format for its kernels, in which case you can extract the initramfs using mkbootimg (there are a number of scripts floating around). from there you can modify whatever you want in the initramfs and then repackage the boot.img and be on your way."
eldarerathis gave me some more instructions: "You basically need to extract the ROM's zip and add su/Superuser in the proper folders (su in /system/bin, Superuser in /system/app). You'll probably also have to look at the updater-script and add something to give su executable permission. It's usually something like 'set_perm(0, 0, 6755, "/system/bin/su");' that you need to add. The updater-script should be in the zip under /META-INF somewhere."
These are some of the useful bits of advice I received that could probably be put to good use when I have some free time. If you feel that anything is helpful, feel free to try it out.

sangemaru said:
Well, so far what possible leads we have that I can think of are these:
mobilx suggested this thread http://forum.xda-developers.com/showthread.php?t=443994 for packing/unpacking boot.img
to quote Alterbridge of Team Overcome: "I presume the ZTE tablet uses boot.img format for its kernels, in which case you can extract the initramfs using mkbootimg (there are a number of scripts floating around). from there you can modify whatever you want in the initramfs and then repackage the boot.img and be on your way."
eldarerathis gave me some more instructions: "You basically need to extract the ROM's zip and add su/Superuser in the proper folders (su in /system/bin, Superuser in /system/app). You'll probably also have to look at the updater-script and add something to give su executable permission. It's usually something like 'set_perm(0, 0, 6755, "/system/bin/su");' that you need to add. The updater-script should be in the zip under /META-INF somewhere."
Click to expand...
Click to collapse
Thank you, I will do some reading for a start.
We are sure that bootloaders are unlocked?
sangemaru said:
Currently, me and mobilx are trying to put aside time to either:
obtain a dump of the boot.img that we can inject su and superuser.apk into;
compile the source code into a flashable rom that we can inject su and superuser.apk into;
get clockworkmod working on the device;
Click to expand...
Click to collapse
Did you consider getting clockworkmod working in more details? Is it simpler then above method?
I have found this article regarding putting clockwork mode to new devices, I just read it briefly...
http://www.koushikdutta.com/2010/10/porting-clockwork-recovery-to-new.html

assdksl said:
Thank you, I will do some reading for a start.
We are sure that bootloaders are unlocked?
Did you consider getting clockworkmod working in more details? Is it simpler then above method?
I have found this article regarding putting clockwork mode to new devices, I just read it briefly...
http://www.koushikdutta.com/2010/10/porting-clockwork-recovery-to-new.html
Click to expand...
Click to collapse
That's fine. We have a dev utkanos who agreed to build the CWM for our device. He is very experienced in this stuff. The only way to build a proper CWM is to get a boot.img dumped or extracted from a leaked ROM.
So what we need to do:
Get root via some exploit (there is none for 3.2 HC yet) , dump boot.img and build CWM, flash CWM with fastboot, or
Find leaked ROM , extract boot.img, build CWM, flash CWM with the fastboot, root device with Update.zip
Yes the fastoboot is working and the bootloader is unlocked.
I have tried these exploits so far:
GingerBreak
psneuter
zergRush
Also I have tried:
Acer iconia 100 method ADB
Acer iconia 500 method
All ideas are welcome.

Ladies and gentleman the ROOT is here Device is successfully rooted with the superboot method.
Thanks to my friend sangemaru who made this possible.
Expect CWM soon. utkanos is working on it.
Need some testing, before this goes to public

That's great news mobilx! Looking forward to a root and ICS sometime in the future

Congrat`s guys,nice work and many thanks from all users.
This is a beginning of a beautiful friendship with SmartTab
We expect nice custom roms and maybe in a short time and ICS rom for this excellent tablet.
If I or we (other members) can help with something,please,let us know,i dont know programming but i can use Paint (just kidding)

Jeeej!!! I'm looking forward to it!

Ok lets roll
While we are waiting for CWM to be build we can root ZTE V11A/V71A aka Vodafone SmartTab 10/7 with the superboot.
What the superboot does? It puts SU binary and makes a 'insecure' kernel to be loaded temporally on to device( ADB remount). So it's only purpose is to make ROOT. After reboot you are on your old kernel but with the root.
This method is for the advanced users only who want to have root before we build a CWM. With the CWM the root method will be easier.
IMPORTANT!
At this point we have no way to repair a broken device to a factory state. We can unroot and that is it. It is advisable do make dump of your rom before making any changes to the system. We are not responsible for any damage that can occur in the root process and after that.
What we need?
ADB installed through SDK
Zte drivers installed --> debugging ticked in options
fastboot + superboot.img --> Put files in the adb working dir
>adb reboot bootloader
>fastboot boot superboot.img
Device should boot with Superuser.apk installed and SU in the /system/xbin/su.
>adb remount
>adb shell
#ln -s /system/xbin/su /system/bin/su
Install busybox from the market and check the SU binary version with the Superuser.apk - try to update. If it succeed you are done.
#exit
$exit
>adb reboot
Device will reboot with the stock kernel but rooted.
Credits:
sangemaru
utkanos
PaulOBrien from modaco and his superboot solution

Thx mobilx! Hvala

All it's OK
It's working also on v71a.......LOL
10x man

urs71 said:
It's working also on v71a.......LOL
10x man
Click to expand...
Click to collapse
I can also confirm this working on 7 inch

urs71 said:
It's working also on v71a.......LOL
10x man
Click to expand...
Click to collapse
jakaka said:
I can also confirm this working on 7 inch
Click to expand...
Click to collapse
That is great guys. sangemaru will be very happy because he owns A71A
So you can confirm that it boots and the touchscreen is working? That means the kernel is the same for those two variants.

V17A
YES, all work perfectly...........setcpu, blackmarkt,root uninstaller, lucky patcher, etc
The only differences between v11a and v71a is the size of the display
we are wating for CWM..........10x again
v71a

[Q] How To Root Samsung Galaxy S Blaze 4G SGH-T769 on Linux?

I got Samsung Galaxy S Blaze 4G SGH-T769 (it comes with Gingerbread). My goal is to get Cyanogen Mod there, so first I planned to root it and use CWM to install a CM. But I need to do it on Linux, so all the instructions found around suggesting using Odin don't help. So far I found Heimdall and installed it on Debian x86_64.
But I'm not sure what else is needed to actually root it. I found some examples with some "one click" methods, but that's not helpful (since they are for other models). Any advice?
Thanks.

shmerl said:
I got Samsung Galaxy S Blaze 4G SGH-T769 (it comes with Gingerbread). My goal is to get Cyanogen Mod there, so first I planned to root it and use CWM to install a CM. But I need to do it on Linux, so all the instructions found around suggesting using Odin don't help. So far I found Heimdall and installed it on Debian x86_64.
But I'm not sure what else is needed to actually root it. I found some examples with some "one click" methods, but that's not helpful (since they are for other models). Any advice?
Thanks.
Click to expand...
Click to collapse
Hate to be a hater, but the KISS rule applies here. Just do it on a windows machine, your Linux friends won't know. Don't have one? Borrow a friends, it shouldn't take you long.

Cirkustanz said:
Hate to be a hater, but the KISS rule applies here. Just do it on a windows machine, your Linux friends won't know. Don't have one? Borrow a friends, it shouldn't take you long.
Click to expand...
Click to collapse
That's an option, but I won't have an access to one until somewhat later. Just tried to figure out a way to do it on Linux now. But if that's going to be a huge hassle - I'll wait until I'll access Windows to do it. On the other hand I'd still prefer to know how to do it on Linux, in case I'll need to do it again. Heimdall is supposed to work (disregarding potential bugs, like one I got there when trying to extract a PIT file with failed interface), but I'm not sure where to get all the needed components for it (like rooted firmware and what not).

shmerl said:
That's an option, but I won't have an access to one until somewhat later. Just tried to figure out a way to do it on Linux now. But if that's going to be a huge hassle - I'll wait until I'll access Windows to do it. On the other hand I'd still prefer to know how to do it on Linux, in case I'll need to do it again. Heimdall is supposed to work (disregarding potential bugs, like one I got there when trying to extract a PIT file with failed interface), but I'm not sure where to get all the needed components for it (like rooted firmware and what not).
Click to expand...
Click to collapse
Go into the blaze dev section and checkout the blaze Bible by nick. Its a one stop for everything you need.

jbats said:
Go into the blaze dev section and checkout the blaze Bible by nick. Its a one stop for everything you need.
Click to expand...
Click to collapse
I looked there, so far I only saw: In The Beginning There was Root.ROOT!(Via Odin) CWM Vr-5.5.0.4(Via ODIN). As I wrote above, this doesn't help me, since method with Odin to unlock the bootloader is for Windows only. Unless I missed something (that page does look confusing enough for a newcomer).
Btw, that rooted kernel (tar file) mentioned on the Odin method, doesn't work with Heimdall. So unless you succeeded doing it somehow, I'm not sure how exactly that would help me.

shmerl said:
I looked there, so far I only saw: In The Beginning There was Root.ROOT!(Via Odin) CWM Vr-5.5.0.4(Via ODIN). As I wrote above, this doesn't help me, since method with Odin to unlock the bootloader is for Windows only. Unless I missed something (that page does look confusing enough for a newcomer).
Btw, that rooted kernel (tar file) mentioned on the Odin method, doesn't work with Heimdall. So unless you succeeded doing it somehow, I'm not sure how exactly that would help me.
Click to expand...
Click to collapse
I was pointing you in that direction for if and when you got near a computer using windows. Unfortunately you'll have to root that way. Once rooted you can stay away from win afterwards and just download and flash zips in recovery. I dual boot win 7 and Ubuntu 12.10.

Why has nobody suggested Android SDK? Odin is not the only way to do it (although the easiest, perhaps).
OP, are you trying to root the stock GB? If so, you should install Android SDK for linux (google it), and then use command adb from {android SDK install dir}/platform-tools/ directory. Please refer to http://wiki.rootzwiki.com/Android_SDK for detailed instructions.
The usage is the following:
Code:
$ adb push boot.img /sdcard/external_sd
Where boot.img is the rooted boot image for GB.
Code:
$ adb shell dd if=/sdcard/external_sd/boot.img of=/dev/block/mmcblk0p8
Then, you can also copy CWM or TWRP. to the sd card and flash in the same way:
Code:
$ adb push recovery.img /sdcard/external_sd
Code:
$ adb shell dd if=/sdcard/external_sd/recovery.img of=/dev/block/mmcblk0p22
I think for rooted GB, you can download superuser app from the Google Play, or maybe, you will need to push it to /system/app through ADB.

Got a friend with a rooted phone? Got a otg cable? Use root transmission XDA link
There are a lot of rooting apps as well, but I wouldnt trust anything not found on XDA or the play store.

E107946 said:
Why has nobody suggested Android SDK? Odin is not the only way to do it (although the easiest, perhaps).
OP, are you trying to root the stock GB? If so, you should install Android SDK for linux (google it), and then use command adb from {android SDK install dir}/platform-tools/ directory. Please refer to http://wiki.rootzwiki.com/Android_SDK for detailed instructions.
The usage is the following:
Code:
$ adb push boot.img /sdcard/external_sd
Where boot.img is the rooted boot image for GB.
Code:
$ adb shell dd if=/sdcard/external_sd/boot.img of=/dev/block/mmcblk0p8
Then, you can also copy CWM or TWRP. to the sd card and flash in the same way:
Code:
$ adb push recovery.img /sdcard/external_sd
Code:
$ adb shell dd if=/sdcard/external_sd/recovery.img of=/dev/block/mmcblk0p22
I think for rooted GB, you can download superuser app from the Google Play, or maybe, you will need to push it to /system/app through ADB.
Click to expand...
Click to collapse
Thanks. I have a fastboot and adb tools, from Android Platform Tools (it's a smaller package than a whole SDK: dl.google.com/android/repository/platform-tools_r16-linux.zip ). But will writing the rooted image unlock the bootloader? I'm a bit confused here. I thought the locked bootlader that was a main barrier for writing new images like CM with recover tools, and Odin/Heimdall actually unlock bootloader as a prerequisite for the rest. So will adb achieve the same? And if it does, what rooted image I should use for Blaze. One of these?
hotfile.com/dl/163659712/8fd8b1d/SGH-T769_UVLB7_Rooted_Deodexed_ROM.zip.html
hotfile.com/dl/163658008/35fc621/SGH-T769_UVLF4_Rooted_Deodexed_ROM.zip.html

OK, I managed to write a rooted kernel using Odin in the end. But that doesn't seem to help to write Cyanogen Mod to the device. I installed CWM (from Google's store) and rebooted into recovery. Now whey trying to apply an update using a CM image from download.cyanogenmod.org/?device=t769&type=
I'm getting the same signature verification error:
E: failed to verify whole-file signature
E: signature verification failed.
Does it mean that I still need to get another bootloader to flash it as well somehow?

UPDATE: OK, I figured it out. I flashed CWM from the CWM application itself, and then rebooted into recovery, which brought up CWM recovery. From there writing Cyanogen Mod worked without any issues.

Well, since you flashed boot image from Odin, you could just flash CWM with Odin as well. It would save you some time. But you figured everything out in the end anyway..
As a suggestion, I would recommend trying AOKP Beta. It is more stable than CM10 and works flawlessly with USB storage. It is my daily driver for over 2 weeks now.