Database Users

[NIGHTLY][ROM] CyanogenMod 7 for Samsung Captivate (captivatemtd)

This thread is reserved for nightly builds of CyanogenMod Rom for Samsung Captivate.
All Samsung Roms run on top of BML/RFS, CyanogenMod 7 does NOT.
It runs on MTD/yaffs2 (like Nexus One) which means you'll not able to flash just any kernel or run just any other filesystem you want. Use it as it is if possible, otherwise confirm with the kernel developer that you are trying to install whether it would work with CM. We do not support other kernels and know nothing about their capabilities or compatibility. Only the data partition, which is on movinand, is ext4 like on speedmod or voodoo ("lagfix"). No "lagfix" is necessary because this does not use any Samsung proprietary file systems.
CyanogenMod is a free, community built distribution of Android 2.3 (Gingerbread) which greatly extends the capabilities of your phone.
Code:
** These CyanogenMod builds are highly experimental and unsupported.
**
** Please refrain from submitting bug reports for any issues
** you may encounter while running one of these builds.
**
** Submitting bug reports on nightly builds is the leading
** cause of male impotence.
What are Nightly builds? Auto compiled build of the latest CyanogenMod source from github. This version changes each night and aren't officially supported.
If you find bugs/issues you can/must discuss here (do not submit nightlies bugs on CyanogenMod issue tracker).
Warning : Not for new users, flash this build only if you know what you are doing !!! Make SURE you can get into Download mode using only buttons (no other method, Download mode from just buttons is essential).
INSTRUCTIONS:
Latest version: http://download.cyanogenmod.com/?device=captivatemtd
Check the md5sum if you want to be sure that the download worked (different OSes have different programs that do md5, on ubuntu it is md5sum that you run against the zip you download and compare to the md5sum number shown on the download website). ROMManager does this automatically for ROMs you download via ROMManager.
- First time flashing CM 7 to your Captivate (or coming from another ROM)?
Easy way:
Start with a rooted Eclair/Froyo running Eclair/Froyo Bootloaders (do not ask us how to do this).
Install ROMManager Premium.
Flash ClockworkMod Recovery. Pick Captivate (MTD) (ignore the warning about not having an official, pick ClockworkMod 2.x).
Make sure you can reboot into ClockworkMod recovery from ROMManager. Reboot and get back into ROMManager Premium.
Choose download ROMs.
Pick the CyanogenMod Nightlies.
Check the Google Apps addon.
Check Backup current ROM!
Check wipe data, cache, dalvik cache.
Let ROMManager finish the installation.
Harder way:
Make sure you're running a Eclair/Froyo Firmware (2.1 or 2.2) and Eclair/Froyo Bootloaders!
Root your device and install ClockworkMod Recovery.
Do a Nandroid backup!
WIPE (wipe data/factory reset + wipe cache partition)
Install the ROM from internal sdcard using ClockworkMod Recovery
Optionally install the Google Addon (through ROMManager is easiest)
- Upgrading from earlier CM7?
ROM Manager method:
Install ROMManager Premium.
Flash ClockworkMod Recovery. Pick Captivate (MTD) (ignore the warning about not having an official, pick ClockworkMod 3.x).
Choose Download ROMs.
Pick the CyanogenMod Nightlies.
Check the Google Apps addon.
Check Backup current ROM!
Check wipe cache, dalvik cache.
Let ROMManager finish the installation.
Clockwork Mod method:
Download and push the ROM zip file to the sdcard.
Reboot into recovery.
Do a Nandroid Backup!
Install the ROM zip from sdcard (your Google apps will be backed up automatically)
There are no Google Apps bundled with CM ROMs, because Google asked Cyanogen to remove copyrighted apps. After flashing the rom, don't forget to flash Google Addon package if you want it. ROM Manager will allow you to flash it if you just go into it and after flashing the ClockworkMod recovery for MTD devices, choose Download ROMs, and pick Google Apps.
Additional Information:
Maintainers:
atin - http://twitter.com/atinm
codeworkx - http://twitter.com/codeworkx
coolya - http://twitter.com/dumdidum
guiperpt - http://twitter.com/guiperpt
unhelpful - http://twitter.com/unhelpfulone
Irc:
Host: irc.freenode.net:6667
Channels: #cyanogenmod, #cyanogenmod-dev, #cmsgs
Changelog:
Generic Changelog CMSRC Twitter
Device specific Changelog by igor.tonky
Please visit the CyanogenMod Wiki for step-by-step installation walkthroughs and tons of other useful information.
Thank you to EVERYONE involved in helping with testing, coding, debugging and documenting! Enjoy![/QUOTE]

SWEET thanks! Gonna try this out and test it.
Sent from my GT-I9000 using XDA App

Oh snap!
di11i 6.0 w/ Suckerpunch #53
Underclocked to 600mhz
Undervolted to -100mV

Very nice! definitely going to flash it
Is camera working fine now?

Wow
Wow you mean I can actually use Gingerbread on my cappy. I was getting bored of playing with ginger on my HTC dream which is slowwwwer then slow.
Thanks to every dev working on this.

atinm said:
your kitties, doggies and maybe even goldfish are no longer safe.
Click to expand...
Click to collapse
hahaha!
That is the funneyest thing i have herd.

Just want to make sure my understanding is correct
- Don't use "reboot recovery" command or other shiny things to do this!
Flash cm7-captivate-initial-kernel.tar as pda using odin without auto-reboot
So after flash of efs pull battery, get to dl mode, flash initial kernel with auto reboot off. Pull bay after flash go back to recovery?
Do a wipe
Factory restore in clockwork?
Install the Nexus S USB-Drivers from SDK-Manager if you're using windows.
Are these drivers needed to use odin our just files transfers
To revert to a samsung rom, simply use odin with repartition option enabled.
Does odin one click qualify here or use full version?
Just making sure I understand instructions fully, thanks

thx for your hard work man

DAGr8 said:
thx for your hard work man
Click to expand...
Click to collapse
Can't wait to see what you do with this.

Thank you very much but because this is a test release, I will keep my eye very close to see how everyone else does on this ROM. Actually, I'm scared to flash this until it's stable enough for a daily driver .

Can I reserve a post this late? Lol
Sent from my Captivate using XDA App

CM7 getting awfully close!

mcord11758 said:
So after flash of efs pull battery, get to dl mode, flash initial kernel with auto reboot off. Pull bay after flash go back to recovery?
Click to expand...
Click to collapse
No, please read the instructions fifty-thousand times before you do anything. It clearly says to use the three button combo to reboot, directly underneath that. If you do a battery pull while in Download mode, you risk destroying your phone.
mcord11758 said:
Factory restore in clockwork?
Click to expand...
Click to collapse
Yes.
mcord11758 said:
Are these drivers needed to use odin our just files transfers
Click to expand...
Click to collapse
These are drivers to use your phone (incorrect, but avoiding the question). Just install the drivers, because the instructions say so. If you don't, you can't plug your phone into your computer.
mcord11758 said:
Does odin one click qualify here or use full version?
Click to expand...
Click to collapse
Odin One Click. Or Odin3. It doesn't matter. Just reboot into Download mode using the button combo and use Odin.

I must be dumb but, There is no efs-backup for initial kernel to even download, Or I'm unable to find it. On that page, all I see is Initial package, update, and google-addon. No kernel, no efs package.
EDIT: k. I just fail. It was inside the initial package. .-.

Thank you for the response. The initial kernel to be flashed via odin is the z image inside the initial package?

This is why I love Android and XDA! Sweet! Even before Samsung releases it to the I9000 (granted it's still under development).

Are the modem links dead for anyone else?

Yeah I have no idea where the "initial kernel" is. It's not ANYWHERE on the site, nor in the initial package.

Konner920 said:
Yeah I have no idea where the "initial kernel" is. It's not ANYWHERE on the site, nor in the initial package.
Click to expand...
Click to collapse
Yeah, couldn't find that either.

Great job guys. I want to try this as I will flash almost anything once. I will give it some thought. I feel I am one step above noob. Any noobs out there might want to wait some more. Then again if you are a flasher...
Awesome work/progress.
Edit: I made the plunge. Worth every minute.

[TUTORIAL]ClockworkMod Recovery Easy Install

Since people are obviously having trouble installing CWM, I thought I'd make this topic since the other one doesn't seem that it will be updated anytime soon. This does require root.
Step 1: Rooting your phone-Follow the link that's labeled "Superoneclick Root." Download the file and follow instructions. Works on ALL Vibrant Froyo (KA6/KB5) and Eclair. Reboot.
Step 2: Flashing CWM-Download ROM Manager from the market. Open the app, and choose the very first option. It should say "FLash ClockworkMod Recovery." Choose vibrant.
Step 3: Getting into CWM
a. Use the link below that's labeled "Modified 3e REcovery." DOwnload file and follow directions. IF it succeeds, reboot into recovery via 3 button combo and hit rreinstall packages. The phone should reboot into recovery. Hit reinstall packages again and voila.
**Note** this did not work for me.
-OR-
**PRE-POST NOTE** Odin will WIPE ALL APPS AND DATA. Use Titanium Backup from the market to backup apps.
b. If the 3e fix didn't work for you, I suggest using Odin to flash back to stock. Follow either links labeled "Odin Back to Stock" for detailed, step-by-step guides on how to flash back to stock. If it succeeds, reboot to recovery, and you should see "2e recovery" instead of 3e. Hit reinstall packages. It will reboot back into recovery, hit reinstall packages again and voila.
-OR-
c. If those don't work, you can try downloading and flashing a voodoo integrated kernel to access the "red" clockwork recovery via ODIN or SGS Kernel Flasher. I recommend you flash a "stock + voodoo" kernel first however, and then flash your kernel of choice (Overstock, Bali, w/e). MAKE SURE IT'S COMPATIBLE. Follow link down below for stock kernels + voodoo. Find the flasher at the market. This will patch your system with ext4 and is a pretty nice addition. Now, this might take a long time, depending on the amount of apps that you have. You might and probably will hear "linda" which is just a voice that tells you what's happening.
**Note** I have tried SGS kernel flasher multiple times and multiple times it has failed to flash properly---soft brick--boot loop. I'm not saying that you will too, I'm just stating my experiences.
**Disclaimer** I am not responsible for bricked and/or damaged phones, you did it, it was your choice. Although the chance of a hard brick is pretty low.
I do recommend looking at s15274n's guides below if you intend on flashing ROMs. If you don't intend to, might I recommend that you add that to your to do list as well? It might just be a worthwhile experience.
Modified 3e Recovery
http://forum.xda-developers.com/showthread.php?t=833423
Superoneclick Root
http://forum.xda-developers.com/showthread.php?t=803682
Odin Back to Stock + Flashing ROMs
http://forum.xda-developers.com/showthread.php?t=1047087
http://forum.xda-developers.com/showthread.php?t=849028
Stock + Voodoo All Except KB5
http://forum.xda-developers.com/showthread.php?t=870480
Stock + Voodoo KB5
http://forum.xda-developers.com/archive/index.php/t-1036725.html
Hope this helps. Feel free to help me 'perfect' these steps.

Appreciate the effort... I feel (obviously biased) my Noob Root Guide is a little more detailed.. and easier (again, bias), perhaps you want to link to that too in case people are questioning things.
I am NOT a fan of superoneclick OR the modified 3E (like you said it didnt wok for you), just my personal stance. Nice to have options for people though, so thanks!!

I'm running KB5 having Kies'd form the original 2.1 ->2.2 -> 2.2 (KB5). I've also tried the modified 3e recovery without signature check, and it failed to update to CWM for me too.
I'm very reluctant to ODIN to 2.1 stock without getting a real backup. Some questions:
1) Is there nothing I can run from the PC side that can pull a full image from the phone that could be restored if necessary?
2) If I go with the Titanium backup, what exactly will I lose, after ODIN (phone history, settings,..)?
3) If I do ODIN back to 2.1 and install CWM, can I Kies back to KB5 without losing CWM?

kmandel said:
I'm running KB5 having Kies'd form the original 2.1 ->2.2 -> 2.2 (KB5). I've also tried the modified 3e recovery without signature check, and it failed to update to CWM for me too.
I'm very reluctant to ODIN to 2.1 stock without getting a real backup. Some questions:
1) Is there nothing I can run from the PC side that can pull a full image from the phone that could be restored if necessary?
2) If I go with the Titanium backup, what exactly will I lose, after ODIN (phone history, settings,..)?
3) If I do ODIN back to 2.1 and install CWM, can I Kies back to KB5 without losing CWM?
Click to expand...
Click to collapse
1. As far as I know, no.
2. Everthing goes stock...out of the box stock. Import your contacts to your sim card or back it up with AVG or something. SD Card will not be wiped however
3. I believe so, yes.

updated OP!

Rooting GS3 GT-I9300 with Heimdall and Linux

Orrite guys,
This is my first thread post on xda so i hope that - 1: i get it in the right place... and 2: i hope it helps
OK, so i wanted to root/flash away on my GS3 GT-I9300 but i'm a linux user (peppermint - variation of ubuntu 12.04) and i had a hard time finding the information i needed to be confident enough to attempt using a terminal with heimdall to flash a recovery image onto my fone so i could install .zips like the awesome supersu
I'll keep it short and simple, because it is... its just not a common way as most people are windows or mac and personally i loathe both
Attached is a .zip with everything you need and a copy of these instructions.
Here we go:
I have done this on my own GS3 GT-I9300 a couple of times, as well as one other GS3 GT-I9300
Put fone into download mode - Volume Down, Home and Power buttons together till it responds and connect to your pc
FAQ
Q: Does this root method erase my settings and apps?
A: No, it doesn’t touch a thing, very safe to do.
Q: I ended up in Kernel panic mode, what do I do?
A: Relax, that’s same as ODIN download mode, simply run Heimdall again and flash the files again, it will work.
Q: I don’t get ClockworkMod Recovery like you do, just get Android with belly open.
A: If you’ve updated to newer software update, the stock OS will over-write ClockworkMod Recovery on reboot. To fix this, make sure “auto-reboot” is checked off in ODIN, then take the battery out when it’s done flashing in ODIN. Then enter ClockworkMod Recovery right away
Note: below is the 'no reboot' command line for linux (make sure you specify the correct file path to the recovery image) - once flashing is finished, unplug the phone and remove the battery. Replace the battery and now boot straight to recovery and flash supersu.zip
Command line for flashing recovery image
sudo heimdall flash –recovery recovery.img –no-reboot
It really is that simple.
Humanspida
Credits to everyone on xda (too many to list but you know who you are) with threads providing help on this, as well as:
galaxys3root.com/galaxy-s3-root/how-to-root-galaxy-s3-on-linuxubuntu
which was the other place i eventually used
hope this helps.
.

thx for that man
also, if you're on a i64 based computer, do not use the last version of heimdall, but the 1.3.1 instead
github/Benjamin-Dobell/Heimdall/issues/43 (I'm not allowed to post links here...)

jobano said:
also, if you're on a i64 based computer, do not use the last version of heimdall, but the 1.3.1 instead
github/Benjamin-Dobell/Heimdall/issues/43 (I'm not allowed to post links here...)
Click to expand...
Click to collapse
This should be sorted now. As of November 2013 I've been successfully using the heimdall from ubuntu repositories (v1.4.0) on x86_64.

[RECOVERY] TWRP 2.6.3.0 for Samsung Galaxy S4 Mini LTE (GT-I9195)

UPDATE: Do not flash cm-11 roms with the current stable version (2.6.3.0) of TWRP. It won't work. I will create new builds for the I9195 and the I-9190 after someone this issue.
Hi!
I've compiled a TWRP 2.6.3.0 for the Samsung Galaxy S4 Mini LTE (GT-I9195) with crypto support. I've attached a screencapture during an installation of an cyanogenmod update from my encrypted /data partition using goomanager. So i thought, maybe someone can use this because i didn't find any build for the device yet.
I'm not sure if you can use it with encrypted stock samsung roms (I've included some samsung libs, but i couldn't test it), but for cm it should work. And any unencrypted devices..
Should work for the GT-I9190 and GT-I9192 as well, as written on page 4.
Installation as usual (Odin (tar.md5.zip - needs to be unzipped) or Heimdall (.img)):
For Odin:
Download the recovery-twrp-2.6.3.0-serranoltexx.tar.md5.zip and unzip it
Turn off the phone.
Press and hold home, volume down and power. Download screen should appear.
Connect USB cable, and press volume up
Start Odin, uncheck "F. Reset Time" and "Auto Reboot", and then click AP button.
Select extracted "recovery.tar.md5" file and press Start button.
A blue transfer bar will appear on the device showing the recovery being transferred. Check the Message Window in Odin for: "All threads completed. (succeeded 1 / failed 0). The transfer has successfully completed.
Long press the power botton to turn it off.
Hold volume up, home button and power buttons simultaneously to boot into recovery mode.
Sorry, i couldn't post in the Developer Forum and no direct links (< 10 Post for me). And a special thanks to @Dees_Troy for helping me getting the right crypto options.
I hope the image works, first time building a TWRP for me. At least it won't brick your device
_____________
Edit 18.09.2013. (Already Fixed) If the screen locks in the recovery after a few minutes idle (without userinput), the screen gets greyish after the unlock, but the recovery still seems to work properly (see post #4 for image). I've asked in the twrp channel on freenode and tried a fix, that didn't help. . So, it seems more cosmetic. I wonder if someone else gets this, because they said in the channel, they've never seen something like that before.
_____________
Edit 19.09.2013: Sourcecode with my modifications here: https://github.com/johanneszab
Its mainly the BoardConfigCommon.mk and recovery.fstab for TWRP and enryption in the msm8930-common repo and the crypto libs in the recovery directory in the serranoltexx repo.
_____________
Edit 20.09.2013: New recovery.img without Screentimeout, so no more messed up screen after screenlock.
_____________
Edit 28.09.2013: Added SELinux and exfat and removed USB-OTG Support. Recovery should be ready for Android 4.3 with this settings. You won't lose SELinux contexts if you should ever make a backup and then restore it. Thanks to @Dees_Troy for the SELinux informations!
_____________
Edit 19.10.2013: Recreated, reuploaded and tested .tar.md5.zip file with odin since i somehow completely ****ed it up (post #12 and so forth). I'm so sorry for all those broken files without testing and thanks for the Info!
Code:
$ md5sum recovery-twrp-2.6.3.0-serranoltexx.img
9262c28bf81632c66ff1133d6078c8c6 recovery-twrp-2.6.3.0-serranoltexx.img
$ md5sum recovery-twrp-2.6.3.0-serranoltexx.tar.md5.zip
e5014d5e230a5bb1103771b30dd2a159 recovery-twrp-2.6.3.0-serranoltexx.tar.md5.zip

Can I confirm that an alternative to heimdall would be using Odin to flash, as we used to with CWM?

Whosat said:
Can I confirm that an alternative to heimdall would be using Odin to flash, as we used to with CWM?
Click to expand...
Click to collapse
Yap, I think that should work. I've read that heimdall is just an open source replacement for odin and i used heimdall because i've followed the cyanogenmod install instruction for the serranoltexx. They flashed the cwm-recovery with heimdall and it worked. So, i think, it will do it
Its my first samsung device, i've just got it 2 weeks ago, and for my old N1 there wasn't much flashing lately.. so many changes for me

Whosat said:
Can I confirm that an alternative to heimdall would be using Odin to flash, as we used to with CWM?
Click to expand...
Click to collapse
in odin it is not possible to select an .img file fpr flashing. i found this thread that discribes how to convert a .img to an odin flashable file
edit: i converted the file and flashed it successfully with odin. recovery works. i did a backup => ok
two issues / questions:
1) the graphic gets messed after the screen goes off ( i cant supply a screenshot right now)
2) backups going to the internal sdcard. is it possible to change the backup path to the external sdcard? - found it myself
finally i took a screenshot can you please check this

ratelutz said:
edit: i converted the file and flashed it successfully with odin. recovery works. i did a backup => ok
two issues / questions:
1) the graphic gets messed after the screen goes off ( i cant supply a screenshot right now)
2) backups going to the internal sdcard. is it possible to change the backup path to the external sdcard? - found it myself
finally i took a screenshot can you please check this
Click to expand...
Click to collapse
Ah, thanks for clarifying odin for me
Okay, since i'm not the only one with that screentimeout issue, i've modified the image and completely disabled it for now. I think it's anyways not really necessary in a recovery. Well, as it seems to only happen with the S4 mini and happened to you as well, it's maybe driver/chipset related and would take some more time to fix. And i'm not so much into that code..
I reuploaded the image in my first post. Works fine for me now.

Iirc, Mobile Odin is capable flashing .img files? Going to test it after i switch roms and report back.
E: Ah, silly me, should've known our device is not supported by Chainfire

labbe- said:
Iirc, Mobile Odin is capable flashing .img files? Going to test it after i switch roms and report back.
E: Ah, silly me, should've known our device is not supported by Chainfire
Click to expand...
Click to collapse
Okay, i used these simple 3 steps to make that .zip into a .tar.md5 and attached it in my first post:
Code:
$ tar -H ustar -c recovery.img > recovery.tar
$ md5sum -t recovery.tar >> recovery.tar
$ mv recovery.tar recovery.tar.md5
Hope that file works with Odin now.

yeah i used that method as well
Sent from my GT-I9195 using Tapatalk 2

Can I flash CyanogenMod with this?
My question is that can I flash CyanogenMod with this recovery as in the installation of CyanogenMod it says only install with
"Use ClockworkMod Recovery.
Warning: Only use this recovery to flash CM-10.2. Otherwise, you risk bricking your phone!"
I just wanted to clarify.

It should work

This is very interesting when I try to flash it via odin, odin stops responding and I have to close it.
Nevermind used heimdall and flashed it. The long awaited twrp is here. I made several post asking for this and I love it. Finnaly a real useful recovery

Whosat said:
Can I confirm that an alternative to heimdall would be using Odin to flash, as we used to with CWM?
Click to expand...
Click to collapse
Yes you can confirm that this build of TWRP is an alternative to CWM through Odin BUT the provided .tar.md5 crash Odin everytime !
The solution i've found is : (Linux required...)
-> download the .img file attached to this post and rename it to recovery.img
-> then create the .tar.md5 from the previous file using this code :
Code:
tar -H ustar -c recovery.img > recovery.tar
md5sum -t recovery.tar >> recovery.tar
mv recovery.tar recovery.tar.md5
Code which has already been given by @johanneszab on his post !
I have then an Odin flashable & working TWRP build ... i can attach it to this post if anybody wants to I've tested it a little bit : partitions successfully seen, wiped cache & dalvik and finally backed up stock SAMSUNG ROM OK :thumbup:
Have a nice day
Tapatalked from my TF300T
PS : Great work @johanneszab :thumbup:

ne0zone75 said:
Yes you can confirm that this build of TWRP is an alternative to CWM through Odin BUT the provided .tar.md5 crash Odin everytime !
The solution i've found is : (Linux required...)
-> download the .img file attached to this post and rename it to recovery.img
-> then create the .tar.md5 from the previous file using this code :
Code:
tar -H ustar -c recovery.img > recovery.tar
md5sum -t recovery.tar >> recovery.tar
mv recovery.tar recovery.tar.md5
Code which has already been given by @johanneszab on his post !
I have then an Odin flashable & working TWRP build ... i can attach it to this post if anybody wants to I've tested it a little bit : partitions successfully seen, wiped cache & dalvik and finally backed up stock SAMSUNG ROM OK :thumbup:
Have a nice day
Tapatalked from my TF300T
PS : Great work @johanneszab :thumbup:
Click to expand...
Click to collapse
Did you also a restore from backup. Worked the phone well after restore?

ladislav.heller said:
Did you also a restore from backup. Worked the phone well after restore?
Click to expand...
Click to collapse
Not yet... I'll give it a try today
Tapatalked from my GT-I9195

Is it possible to flash recovery-twrp-2.6.3.0-serranoltexx.img via dd command directly from Terminal Emulator?
Anybody tried?
The command should be something like this:
dd if=/sdcard/recovery-twrp-2.6.3.0-serranoltexx.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery bs=512
But I am not sure whether the above is correct.

ne0zone75 said:
[..] BUT the provided .tar.md5 crash Odin everytime !
Click to expand...
Click to collapse
hmm, strange stuff . Thanks for that info! I had even checked md5sums and the command history for the file. Didn't test it with odin though, still haven't it installed. So, i recreated the file, maybe this time it works, ..

johanneszab said:
hmm, strange stuff . Thanks for that info! I had even checked md5sums and the command history for the file. Didn't test it with odin though, still haven't it installed. So, i recreated the file, maybe this time it works, ..
Click to expand...
Click to collapse
Odin still craches right afther you hit "start"....
EDIT:
Installed the recovery using heimdall, but I'm still not able to mount the USB-OTG....
Does anyone have the same problem, have the same with CWM-recovery?

Keon91 said:
Odin still craches right afther you hit "start"....
EDIT:
Installed the recovery using heimdall, but I'm still not able to mount the USB-OTG....
Does anyone have the same problem, have the same with CWM-recovery?
Click to expand...
Click to collapse
I'm so sorry for those crap odin files . I'm going to install odin now, make a third new image and flash it once to make sure it works. This is so strange because those 3 commands are no brainer . Maybe ubuntu messed up their tar .. i don't know :/.
I've turned off USB-OTG in the build, because i thought that the S4 Mini doesn't support it (and it depends on some hardware?!). I've no clue about USB-OTG, but i've read in the forums here in some posts that the S4 Mini doesn't support it and i couldn't try it in my first builds that included USB-OTG, because i don't have any hardware for it, ..

johanneszab said:
I'm so sorry for those crap odin files . I'm going to install odin now, make a third new image and flash it once to make sure it works. This is so strange because those 3 commands are no brainer . Maybe ubuntu messed up their tar .. i don't know :/.
I've turned off USB-OTG in the build, because i thought that the S4 Mini doesn't support it (and it depends on some hardware?!). I've no clue about USB-OTG, but i've read in the forums here in some posts that the S4 Mini doesn't support it and i couldn't try it in my first builds that included USB-OTG, because i don't have any hardware for it, ..
Click to expand...
Click to collapse
As i posted above, i've created successfully a flashable Odin file using your IMG one AND i used Ubuntu 12.04.3 x64 to perform this so Ubuntu is not involved in the difficulties you're facing for creating a working TAR.MD5; i'd like to suggest that those difficulties are maybe caused by the filename you give to the input / output of your shell commands ... in my experience they have to be the same and short (only filename extension differs of course).
That said you did a really great job with your TWRP build :thumbup: ... i know this is a difficult task to build one
PS : I still do not have tested the restore process of my device's nandroid backup i made earlier this week using your TWRP build ...
Tapatalked from my TF300T

I'm sorry , I don't mean usb-otg but how can I Mount my storage sdcard and / or internal storage to my pc, trough USB?
Sent from my GT-I9195 using xda app-developers app

Root, recovery and custom rom setup for Galaxy S5 (SM-G900I)

Hi all,
How are you?
I've been looking at these forums for most of the day, though am still quite confused. If someone could assist to clarify it would be much appreciated (as I would like to avoid to brick my phone).
I'm currently running Stock Android, Marshmallow version 6.0.1 with the 1 November 2016 Security Patch.
The model of my phone SM-G900I (Australian edition).
So I've come across the following links with the instructions on how to root and install recovery, though quite confusing.
http://forum.xda-developers.com/show....php?t=2699648
Recovery Query?
I understand that you need to download the Samsung Drivers and Odin.
I've downloaded the TWRP files for my phone - twrp-3.0.2-2-klte.img.tar and twrp-3.0.2-2-klte.img.tar.asc
Do I need to use the twrp-3.0.2-2-klte.img.tar.asc file at all?
Root Query
Is the towelroot method of rooting the S5 still relevant. The reason I ask, is that when I had posted an initial question on the XDA assist, I was advised that this may not work.
If the towelroot method is no longer relevant, would the CF-Autoroot method below work?
http://forum.xda-developers.com/show....php?t=2696537
If neither of the above methods work I have seen mentions of "flashing root" via TWRP.
Are there any known instructions on how to do that on XDA or any other website?
Or is it just a matter of obtaining the superSU zip file from https://download.chainfire.eu/696/supersu/ and flashing it?
The other information seems straight forward re using the Samsung Tool to backing up the device and the EFS .
Any help would be much appreciated.
Thank you.

just flash the .img file in download mode, and dont use the asc file at all. also dont use twrp 3.0.2-2, just use 3.0.2 (not 3.0.2-1 or 3.0.2-2 as they can be pretty buggy). Towelroot has long since become irrelevant back in the 5.0 days unfortunately so all you need to do is find the appropriate supersu.zip file and put it on your phones sd card (either internal or external), boot into recovery an install that zip via TWRP then reboot. Should be good to go. The classic "root via recovery" method

Paul_Lunardi said:
Hi all,
How are you?
I've been looking at these forums for most of the day, though am still quite confused. If someone could assist to clarify it would be much appreciated (as I would like to avoid to brick my phone).
Recovery Query?
I understand that you need to download the Samsung Drivers and Odin.
I've downloaded the TWRP files for my phone - twrp-3.0.2-2-klte.img.tar and twrp-3.0.2-2-klte.img.tar.asc
Do I need to use the twrp-3.0.2-2-klte.img.tar.asc file at all?
Root Query
Is the towelroot method of rooting the S5 still relevant. The reason I ask, is that when I had posted an initial question on the XDA assist, I was advised that this may not work.
If the towelroot method is no longer relevant, would the CF-Autoroot method below work?
http://forum.xda-developers.com/show....php?t=2696537
.
.
Click to expand...
Click to collapse
1. Plug in your phone and let the drivers load.
If phone unrecognized then head to Playstore you can find loads of apps for drivers
2.unplug your phone and turn it off
3.Load odin.
Some versions of Odin are outdated. So watch for that.
4.Holding your turned off phone. Hold the volume down power and home buttons. Done correctly it should bring you to a page saying custom Roms can damage your blah blah. Volume up to continue down to reboot. Plug your phone in then Push volume up if you feel ready to Join us Oh Padawan.
Now I am sorry for the lengthy information, most likely you have already gotten to this point, but I just want to make the same page for you and future readers. No point in asking a bunch of potentially irrelevant questions when one explanation is sufficient.
5. Odin should find your phone which will be represented by a lit up colored square on the left side indicating a Com:value# which number is of little consequence just tells you which port it found it at. Do not dwell on this.
6. Using an extraction program such as .7z take your CF auto root .Tar file, not the .Asc, and extract. You should be able to find an file with ap in the extension.
7.Take the path from the URL bar of this window including the name of the ap file and copy it over to Odin. In Odin you will see the place to put it is represented by AP.
8. CLICK START AND WAIT WITH JEOPARDY MUSIC.
9. IT MAY REBOOT A FEW TIMES BUT UNTIL IT SAYS success OR FAIL IN ODIN DO NOT TOUCH.
10. Repeat steps 7-9 for twrp.img
10. Now taking this was a success turn your phone off. Unplug and holding volume UP power and home Gets you into twrp recovery. If all is well you can reboot into system. Ignore the kernel warning.

^^^^^ theres the long explanation LoL ^^^^^^^^ i disagree with step 9, but meh

Hi all,
Thanks for the detailed instructions.
So it appears that you can perform the task in 2 ways, ie
* By initially flashing TWRP first using Odin (whilst phone is in download mode), then running the TWRP and then copying over the supersu file to the sd card, then flashing this.
Or alternatively, following the above steps which first
* roots the phone by using Odin within download mode and the "cf auto root" file. Then once again using odin and flashing the TWRP file via odin.
This is my understanding.
Please let me know if I've misunderstood, otherwise thanks all. I'll be giving it a try soon.
My eventual goal is to install the Resurrection Remix Rom, so fingers crossed.

Paul_Lunardi said:
Hi all,
Thanks for the detailed instructions.
So it appears that you can perform the task in 2 ways, ie
* By initially flashing TWRP first using Odin (whilst phone is in download mode), then running the TWRP and then copying over the supersu file to the sd card, then flashing this.
Or alternatively, following the above steps which first
* roots the phone by using Odin within download mode and the "cf auto root" file. Then once again using odin and flashing the TWRP file via odin.
This is my understanding.
Please let me know if I've misunderstood, otherwise thanks all. I'll be giving it a try soon.
My eventual goal is to install the Resurrection Remix Rom, so fingers crossed.
Click to expand...
Click to collapse
the cf auto root file usually isnt necessary, nor is flashing supersu really as the newer twrps have the root function built right in. Itll ask you if you want to enable superuser rights the first time you boot into it. Just swipe right and its rooted. Alternatively, flashing supersu from within twrp or the cf auto root also work. CF is the acronym for the dev ChainFire, he is the man (or she, and conversely "the woman" or whatever LOL)!! But the crux of what you need is twrp installed, from there youre usually set. Get rooted, make a nand of your stock setup and flash away. Also, id make sure to download the stock tar.md5 file of your phones firmware in case all goes awry (or to hell in a handbasket or enter clever euphemism for stuff going bad here) so you can flash the stock tarball in Odin if you get stuck in an endless bootloop and your stock restore file doesnt work. Also, when resoring from AOSP to TouchWiz or vice versa, does require a few boxes to be checked for it to work, but it happens all the time. Happy flashing and feel free to ask away if you run into anything man!

Thanks all for clarifying.
I did have some difficulties along the way though I did successfully install twrp.
So I downloaded one of the latest versions of odin on mums computer. Laiche the twrp tar file in the ap section. Loaded it then restarted the device. Ran recovery though it was still the default android recovery ie it appeared as though nothing had changed. I looked at another forum which suggested to turn ooff the auto reboot option in odin and perform a battery pull and then launch directly into twrp. This actually worked after much agony.
I then loaded a superuser zip and flashed it onto the phone.
Rebooted confirmed that the phone was rooted.
I then relaunched the twrp recovery and ran a nand? backup of my device. Then I attempted to install a custom rom ie resurrection remix. Unfortunately it did load though the screen appeared to freeze after boot and was therefore unusable. Thank goodness the restoring of the backup worked.
I'll reattempt the installation of a custom rom very soon. Fingers crossed.
Thanks.