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.

Flash any kernel or modem on CWM

- I made some ZIPs with scripts for you to flash any kernel or modem on CWM.
- It's simple, just drag and drop your file to the correct ZIP.
#Put zImage on the "Flash Kernel [zImage]"
#Put boot.img on the "Flash Kernel [boot.img]"
#Put modem.bin on the "Flash Modem [modem.bin]"
1. Extract the ZIPs from the 7z file first.
2. Just open your ROM file [Cyanogenmod {Also other AOSP, AOKP, etc...}, Samsung Stock, Samsung-based], extract the file, and drag and drop to the ZIP, then you install on CWM Recovery, very simple,
Download

in the meta-in folder, there are some cert files and stuff, do i need to move them in as well?

Good work Marcello
Enviado do GalaxyS2 usando Tapatalk 2.1.3

LogeshMenon said:
in the meta-in folder, there are some cert files and stuff, do i need to move them in as well?
Click to expand...
Click to collapse
There are just binary and script, no need for certs. Just drag and drop or extract and compress the file you want to flash,

Re: boot.img -- have you never had problems with wifi using just the boot.img? Especially across firmwares such as AOSP <-> Samsung?
I always thought you also had to flash dhd.ko, among other modules. The advice here is what I have been following: http://forum.xda-developers.com/showthread.php?t=1059412

stone_ship said:
Re: boot.img -- have you never had problems with wifi using just the boot.img? Especially across firmwares such as AOSP <-> Samsung?
I always thought you also had to flash dhd.ko, among other modules. The advice here is what I have been following: http://forum.xda-developers.com/showthread.php?t=1059412
Click to expand...
Click to collapse
No. Never had any problems. And maybe those libs are already inclued in the ROM, don't know. And all I know is that boot.img = zImage. I've seen a thread saying that you can rename boot.img to zImage.

Unfortunately this didn't work for me - the first time.
I ended up stuck on the boot screen - ie samsung galaxy siii logo appears, no boot animation to imply it's starting up
I tried restore from a CWM backup but there was a checksum mismatch (scrath that idea)
I thought i'd give it one last try.
I flashed your flash modem.zip first, then reflashed my ROM (Ripper ROM v7) with no data wipe, and it WORKED!
I'm pretty happy now because for a while there I thought I had bricked my device!
Now i just have to install a few more zips as addons to my ROM and i'm back in business. (just installed those, restarting now)
*edit* restarted, mods working ok, 4G/LTE connected, everything is good again
Just realized this thread was for the SGS2 whereas I have a i9305 SGS3 4G/LTE. Whoops. Well it worked, but in my case i had to reflash the ROM.
I think I have done it right, but my baseband version in About Phone still shows I9305ZHALI2 (it should read I9305TDVLI5)? The ROM i reflashed does not come with a radio, it uses the one already on your device.

jjcoolaus said:
Unfortunately this didn't work for me - the first time.
I ended up stuck on the boot screen - ie samsung galaxy siii logo appears, no boot animation to imply it's starting up
I tried restore from a CWM backup but there was a checksum mismatch (scrath that idea)
I thought i'd give it one last try.
I flashed your flash modem.zip first, then reflashed my ROM (Ripper ROM v7) with no data wipe, and it WORKED!
I'm pretty happy now because for a while there I thought I had bricked my device!
Now i just have to install a few more zips as addons to my ROM and i'm back in business. (just installed those, restarting now)
*edit* restarted, mods working ok, 4G/LTE connected, everything is good again
Just realized this thread was for the SGS2 whereas I have a i9305 SGS3 4G/LTE. Whoops. Well it worked, but in my case i had to reflash the ROM.
I think I have done it right, but my baseband version in About Phone still shows I9305ZHALI2 (it should read I9305TDVLI5)? The ROM i reflashed does not come with a radio, it uses the one already on your device.
Click to expand...
Click to collapse
This is very old. If you tried on your S3 lte, of course it won't work. Be more careful next time,
Sent from my GT-I9300 using xda premium

[Q] error excecuting updater binary in zip with twrp

hi guys when I try to flash a rom appears the message "error excecuting updater binary in zip" someone know how to solve it?
Sorry for my bad english

Your English is fine. Check to make sure there are no spaces in the file name, and if there are, replace them with dashes or underscores. Then try running the zip again.

Strephon Alkhalikoi said:
Your English is fine. Check to make sure there are no spaces in the file name, and if there are, replace them with dashes or underscores. Then try running the zip again.
Click to expand...
Click to collapse
there is no space in the name :\ maybe can be a problem of the recovery's version ?

I mentioned it because the presence of spaces was the reason my copy of Optimized CM12 failed to install. What version of TWRP are you running?

2.8.5.0

Upgrade. 2.8.6.0 is available from the TWRP homepage (once the page comes back up), though I believe a customized copy is available for Alucard and Antares One's Optimized CM12 build in I9505 Original Android Development.
EDIT: 2,8.6.0 can be downloaded from here.

AntaresOne's TWRP will convert the system to F2FS automatically when flashing a rom. He said he was going to make it a choice in a future update. Don't know if he gotten around doing so.

GDReaper said:
AntaresOne's TWRP will convert the system to F2FS automatically when flashing a rom. He said he was going to make it a choice in a future update. Don't know if he gotten around doing so.
Click to expand...
Click to collapse
This problem started when I tried to flash cyano 12 based on 5.1.1 (by AntaresOne) before doing this everything was fine. Maybe the recovery couldn't convert system to F2FS, can be this?

Strephon Alkhalikoi said:
Upgrade. 2.8.6.0 is available from the TWRP homepage (once the page comes back up), though I believe a customized copy is available for Alucard and Antares One's Optimized CM12 build in I9505 Original Android Development.
EDIT: 2,8.6.0 can be downloaded from here.
Click to expand...
Click to collapse
Thank you, I will try it

eleonora97100 said:
Thank you, I will try it
Click to expand...
Click to collapse
It doesn't necessarily needs to be converted. It can run with the default ext4 too. Problem with converting is that it will wipe your internal storage. So that into account.

I had the binary updater issue occur on a flashable zip I made. The cause? I accidentally deleted the line that told TWRP to mount the system partition. Restoring the line solved the issue, so check the script. The developer may have accidentally missed a line.

thank you guys I upgraded the recovery and now it works fine thank you very much

[Root][5.1.1] Root with Stock Kernel

This thread contains a tutorial on how to patch boot.img on Samsung Lollipop devices and achieve root with a stock firmware. The tutorial is intended for those who wish to make their own boot.img for their specific firmware. For the rest, a patched boot.img for each device variant is attached. Simplified instructions for flashing with these patched images is first, followed by the tutorial.
NOTES!
1: YOU MUST EXTRACT THE .IMG FILE FROM THE TAR AND FLASH WITH TWRP. For some reason flashing with ODIN does NOT work with the images attached to this thread.
2: To make ODIN tars, look at @drExel's post here.
3: In most variants, TWRP 2.8.7.0 appears to work, though there are some issues. On some devices, it takes a REALLY long time to boot into TWRP, making you believe the device has frozen, but just give it time and it will load eventually. On other devices, TWRP loads, but touch does not work. In these cases, the S-Pen works without any problems (but is very sensitive). Some users have posted alternate TWRPs that work properly; search the thread for this. I am not including it here because I have not personally tried these versions myself.
4: Since this issue came up multiple times, though it is mentioned in the instructions below, I am stressing this once again. DO NOT ALLOW TWRP TO AUTOMATICALLY INSTALL SUPERSU WHEN YOU HIT REBOOT. THIS WILL CAUSE A BOOTLOOP, GUARANTEED! YOU MUST FLASH THE BETA 2.52 SUPERSU MANUALLY AFTER FLASHING THE PATCHED BOOT.IMG AND CONFIRMING THE DEVICE WORKS PROPERLY!
5: If you take the time to read the entire thread, you will find redirects to other kernels, firmwares and more. I am sure they are excellent, but having not used any of them, I cannot vouch for the outcomes if you flash them. All information related to the other firmwares and any questions you have about them are best served by going to their dedicated threads. This thread is ONLY for a pure stock firmware with only the boot.img patched to permit root, and nothing else touched.
6: XPosed Framework does not work yet for TW LL, but @wanam has an unofficial version here that various members have reported works quite well.
7: Knox WILL be tripped. If you care about Knox, leave now and do not come back!
Simplified Instructions
The thread originally began as a pure tutorial, with only the P607T image. But given the requests others had, and my need to confirm that this works on all variants, I made more patched images. No 'simple instructions' were available earlier because this was not intended for end-users who might flash and find that it does not work. Now that all the images are confirmed working, and we have tested on all variants, here is a simplified set of instructions for those who just wish to flash and do not care what they are flashing.
1: Update to fully stock 5.1.1 for your device. Whether it is OTA or ODIN flash using a firmware from sammobile or elsewhere does not matter. You start with a fully stock device running 5.1.1.
2: Download the appropriate patched_boot.img for your device. They are attached as tar files due to XDA size restrictions, so you must untar and then save the .img file to your device. Also download SuperSU Beta 2.52.zip and save it as is to the same folder on your device where you put the .img file.
3: Download TWRP 2.8.7.0 for your device and flash it with ODIN. To get TWRP to stick, when the device reboots, you must go directly into recovery. If the device reboots normally, TWRP will be replaced by the stock recovery. There are guides on how to flash TWRP and you should go look at them if you are unsure how to do this.
4: Once you are in TWRP, go the Install area. The default is for installing .zip files. At the bottom right of the screen, you will see a button to change to Images. Hit this. Then select the patched_boot.img file that you saved on your device in the previous step. When you hit install, TWRP will ask you whether this is a boot image or a recovery image. Select Boot. Let TWRP do its thing. When done, go back and hit reboot. TWRP will volunteer to install SuperSU for you now. SAY NO TO THIS. If you accept this install, your device will bootloop and you have start all over again!
5: Make sure the device rebooted without any problems. You will see a red "Kernel SEAndroid Not Enforcing" message when you reboot. Ignore it, it just means that the patched boot.img is working. Once you have confirmed that the device is able to boot properly with the patched boot.img, reboot into recovery again. Go back to Install, this time, stick with Zip mode and install the Beta SuperSU 2.52.zip that you saved to your device. Reboot.
6: If you followed instructions properly, you will reboot without any problems. Run SuperSU, allow it to update if it wants to, and to disable knox if you want to. You have a rooted device now with a virgin firmware.
7: This process has worked for enough people now that any errors are user errors. If you are bootlooping after following these instructions to the letter, you should do a full factory reset and try from scratch. A previous incorrect flash of SuperSU that caused a bootloop seems to persist even if you reflash the stock firmware and messes things up. Always perform a clean install!
Tutorial to patch your own boot.img
This section is NOT meant for the non-technical end-user who "... just wants root ... "
So far, it seems the only way to get root on the 5.1.1 Firmware was to flash a permissive kernel that disabled SEAndroid completely. This is a bit like killing the patient to cure the disease. @Chainfire describes a 'trick' to get root with a fully stock kernel on this thread. Special Thanks to @garyd9 and @SHM for helping me get everything working properly.
Part 1:
1) Extract boot.img from your device's stock firmware.
2) Unpack the boot.img to get access to the ramdisk.
3) Copy the sepolicy file from the ramdisk. You will be patching this file to make the usual SuperSU method work again.
The stock image can be extracted from the firmware using any archive tool. To unpack the boot.img, you can take a look at the following threads for tools and instructions.
Carliv's Kitchen : Windows, very beginner friendly.
SHM's Toolset : I used this on Linux.
copy sepolicy from the ramdisk folder to your adb folder (If you are on Windows and using Minimal ADB and Fastboot; I am assuming linux users don't need to be told what to do here )
Part 2:
1) Connect an already rooted device running 4.4+ firmware & SuperSU Beta 2.50+ to your system. Make sure you have adb access.
2) Push the sepolicy file to the device.
3) Run supolicy on the sepolicy file to patch it.
4) Pull the sepolicy file back to your computer.
I used my rooted Note 2 to get the job done. ANY rooted device that permits adb should do the trick, but it needs to be on 4.4+ firmware and running SuperSU Beta 2.50+.
Once you have an adb connection established, do the following (this is from Chainfire's thread referenced at the beginning):
Code:
adb push sepolicy /data/local/tmp/sepolicy
adb shell su -c "supolicy --file /data/local/tmp/sepolicy /data/local/tmp/sepolicy_out"
adb shell su -c "chmod 0644 /data/local/tmp/sepolicy_out"
adb pull /data/local/tmp/sepolicy_out sepolicy_out
Part 3:
1) Replace the sepolicy file in the stock ramdisk with the newly patched sepolicy file.
2) Repack the ramdisk.
3) Make a new boot.img with the stock kernel and repacked ramdisk.
4) Flash new boot.img on your Note 10.1. Reboot, make sure everything is working.
Replace the sepolicy in the ramdisk with the sepolicy_out file that you pulled from your reference device. This means RENAME sepolicy_out and overwrite the original sepolicy file.
Repack the ramdisk using the instructions that came with your tool.
Make a new patchedboot.img file using the instructions that came with your tool.
Copy this patchedboot.img file to your Note 10.1, reboot into TWRP, go to the install zip section, toggle image mode, flash the patchedboot.img file and reboot the device. DECLINE TWRP's friendly offer to install SuperSU for you. This will cause a bootloop!If the device reboots successfully, pat yourself on the back. At this point, all you have done is patched the sepolicy to allow rooting, but you have not yet rooted the device.
Part 4:
1) Use TWRP to install SuperSU Beta 2.50+ (I used 2.52)
2) Reboot
Copy SuperSU Beta 2.50+ (I used 2.52) to the device, reboot into TWRP and install SuperSU. Reboot for rooted Note 10.1 running a Stock Kernel and no compromised SEAndroid. Of course, it goes without saying, this will trip knox. Also, please note that XPosed is not out for 5.1.1 yet, at least not officially. @wanam has an unofficial version here that various members have reported works well.

Hey, So at what step in this do I start if I dl'ed the Patched boot img? Thanks in advance.

icemanscion said:
Hey, So at what step in this do I start if I dl'ed the Patched boot img? Thanks in advance.
Click to expand...
Click to collapse
Part 3, Step 4:
Flash new boot.img on your Note 10.1. Reboot, make sure everything is working.
Copy this patchedboot.img file to your Note 10.1, reboot into TWRP, go to the install zip section, toggle image mode, flash the patchedboot.img file and reboot the device. If the device reboots successfully, pat yourself on the back. At this point, all you have done is patched the sepolicy to allow rooting, but you have not yet rooted the device.
Click to expand...
Click to collapse
In TWRP, when you hit Install, on the bottom right, you will see an option for Images. Select that and when you goto the folder with your img, you should see the new img you copied on to your device. Continue with Part 4 for full root.
IF the device does not boot, you want to flash the stock boot.img again, so make sure you have a copy of that on your device as well, so you can recover easily!

karthikrr said:
Part 3, Step 4:
In TWRP, when you hit Install, on the bottom right, you will see an option for Images. Select that and when you goto the folder with your img, you should see the new img you copied on to your device. Continue with Part 4 for full root.
IF the device does not boot, you want to flash the stock boot.img again, so make sure you have a copy of that on your device as well, so you can recover easily!
Click to expand...
Click to collapse
I have issues with TWRP since it wont work properly for me, so I'm going to try it with Philz CWM. Thank you again.

icemanscion said:
I have issues with TWRP since it wont work properly for me, so I'm going to try it with Philz CWM. Thank you again.
Click to expand...
Click to collapse
Good luck Just make sure you have the stock boot.img around, in case there are any problems. You are the first one trying it on the P600, or at least the first who cared to write in this thread, so this is uncharted territory!

So to get the patches boot.img, we unpack the tar file posted in the OP?
Sent from my SM-P600 using Tapatalk

iridaki said:
So to get the patches boot.img, we unpack the tar file posted in the OP?
Sent from my SM-P600 using Tapatalk
Click to expand...
Click to collapse
Yes. xda does not allow me to post an image file greater than 8mb, but the P607T image is 10.5mb, so had to tar it. Decided to be consistent with all the images.
Technically, you can try to flash that .tar with ODIN, but in my case, it would not work. Only flashing the .img through TWRP did.

karthikrr said:
Yes. xda does not allow me to post an image file greater than 8mb, but the P607T image is 10.5mb, so had to tar it. Decided to be consistent with all the images.
Technically, you can try to flash that .tar with ODIN, but in my case, it would not work. Only flashing the .img through TWRP did.
Click to expand...
Click to collapse
Thank you! And thank you for providing us with a patched kernel!
I'll try rooting and installing Xposed tonight and report back!

iridaki said:
Thank you! And thank you for providing us with a patched kernel!
I'll try rooting and installing Xposed tonight and report back!
Click to expand...
Click to collapse
Technically its just a patched boot image with a STOCK kernel, but yea, glad to help The real work was done by Chainfire and garyd9 and SHM helped me put this thing together, so they deserve the thanks!
If you get Xposed on it, let me know which version. The official one does not work on TW LL yet, but I believe Wanam has another version out that does. I haven't had the time to install it and test it, so your review will be helpful.

karthikrr said:
Technically its just a patched boot image with a STOCK kernel, but yea, glad to help The real work was done by Chainfire and garyd9 and SHM helped me put this thing together, so they deserve the thanks!
If you get Xposed on it, let me know which version. The official one does not work on TW LL yet, but I believe Wanam has another version out that does. I haven't had the time to install it and test it, so your review will be helpful.
Click to expand...
Click to collapse
Any contribution is a worthy contribution!
Wanam Xposed works perfectly on my Note 4 and I think it will work on the 10.1 as well. I'll report back soon!

SM-P600-TWRP 2.8.7.0 touch input doesn't work, but stylus input does
Hi!
Thanks for your posts, I'm sifting through is now. I was reflashing TWRP 2.8.7.0 (for SM-P600) and discovered that it wasnt responding to touch input. But I quickly discovered that it's UI does respond to the s-pen
I'll share my rooting experience as soon as possible.
V

Hey !! Can you give me the ROM of Darkdroid for Micromax A177. Thanks

Vasishtha said:
Hi!
Thanks for your posts, I'm sifting through is now. I was reflashing TWRP 2.8.7.0 (for SM-P600) and discovered that it wasnt responding to touch input. But I quickly discovered that it's UI does respond to the s-pen
I'll share my rooting experience as soon as possible.
V
Click to expand...
Click to collapse
How do you make it? I cannot flash the twrp successfully, there is always an error saying ''Recovery is not SEAndroid Enforcing''.

iopxiang said:
How do you make it? I cannot flash the twrp successfully, there is always an error saying ''Recovery is not SEAndroid Enforcing''.
Click to expand...
Click to collapse
You should wait a few moments. TWRP will open.
Flashing the SU.zip ends up in Bootloop for me._.

Fabi7775 said:
You should wait a few moments. TWRP will open.
Flashing the SU.zip ends up in Bootloop for me._.
Click to expand...
Click to collapse
Did you flash the boot.img before flash SU?

iopxiang said:
Did you flash the boot.img before flash SU?
Click to expand...
Click to collapse
Actually not, sorry.
I just thougt it is worth a try.

The SM-P600 rooting(with your patched boot) was a success! I encountered no problems at all. Only the lack of touch responsiveness of twrp 2.8.x had me worried, but thankfully the s-pen had my back and I was able to browse the twrp UI with it.
I'm now restoring all my apps with titanium backup, I'll try out xposed later this afternoon.
Regarding the LL update: wow this tablet completely feels like a new device, the fluidity is just stunning. 60 fps animations

Vasishtha said:
The SM-P600 rooting(with your patched boot) was a success! I encountered no problems at all. Only the lack of touch responsiveness of twrp 2.8.x had me worried, but thankfully the s-pen had my back and I was able to browse the twrp UI with it.
I'm now restoring all my apps with titanium backup, I'll try out xposed later this afternoon.
Regarding the LL update: wow this tablet completely feels like a new device, the fluidity is just stunning. 60 fps animations
Click to expand...
Click to collapse
Finally, a confirmation Thanks for letting us know!
As for TWRP, I believe the 2.6.3.3 (or something else in the 2.6 series) works without any problems on the P600.
XPosed is officially not out for Samsung LL, BUT Wanam has a version in development that works well, according to @iridaki on this thread. If you switch TWRP or try Wanam Xposed, post an update here as well!
And yes, the LL update actually made the device feel so damn good, its practically a Note 10.1 (2015 Edition)!

karthikrr said:
Finally, a confirmation Thanks for letting us know!
As for TWRP, I believe the 2.6.3.3 (or something else in the 2.6 series) works without any problems on the P600.
XPosed is officially not out for Samsung LL, BUT Wanam has a version in development that works well, according to @iridaki on this thread. If you switch TWRP or try Wanam Xposed, post an update here as well!
And yes, the LL update actually made the device feel so damn good, its practically a Note 10.1 (2015 Edition)!
Click to expand...
Click to collapse
Twrp 2.6.x does work, however there is no option to flash .img files on those versions.
So you either have to use heimdall or something else in order to flash that boot.
The unofficial xposed 5.1.x on my nexus 5 worked without any problems, so I expect the same for the LL variant. But I'll keep you posted.
The multiwindow transitions now have fade in/out effects <3 and we now can snap floating windows to either the left or right sides D:

karthikrr said:
Update 3: The patched P600 image has been confirmed to work by @Vasishtha, who also says TWRP 2.8.7.0 works with the S-Pen, but no touch input.
Click to expand...
Click to collapse
Can we use Temasek's 2.8.7.0 TWRP that has touch working?

LineageOS 7.1 for SGP771

Hi. As a result of Androplus stoppage of his kernel support I decided to create this theme. I'm not a developer.
I use LineageOS more than two months, and it's stable. Originally it was built by andralex, he didn't create this threat as he was waiting the permission from other developer whose groundwork he used. But I lost contact with him. Seems he is very busy.
Now the other developer builded the rom, his nickname is kv123.
--------------
To get usb otg working use this in terminal when you inserted usb stick
Code:
su
echo 1 > /sys/module/qpnp_smbcharger_extension/parameters/start_id_polling
------------
After any lineageos update dont forget about play store to give permissions for storage. Otherwise it wont download any apps larger the 20 mb.
Lineage camera is a bit buggy, so it's better to use open camera.
---------
There are the links
[STRIKE]https://www.androidfilehost.com/?fid=745425885120730219[/STRIKE]
https://yadi.sk/d/Zfxi3agx3HkLQL
Some developer links:
https://review.lineageos.org/#/q/project:LineageOS/android_kernel_sony_msm8994
https://github.com/LineageOS/android_kernel_sony_msm8994
If you want I can ask kv123 to build the rom for sgp712 too.
------------
Some screenshots:

Oh. You need also replace wifi calibration file here: /system/etc/firmware/wlan/bcmdhd/bcmdhd.cal and reboot
It's forgotten to be added.
Updated fixed version at yandex disk.

Thanks for this. It is exactly what I am looking for and I hope my tech skills are up to the task.
BTW, this link comes up "404 not found. Can't find it!"
https://www.androidfilehost.com/?fid=745425885120730219
Would you have another we can try?

Thats because kv123 removed version with wifi buggy.
Use my mirror link or this.
https://www.androidfilehost.com/?fid=817550096634767960

alex009988 said:
Hi. As a result of Androplus stoppage of his kernel support I decided to create this theme. I'm not a developer.
I use LineageOS more than two months, and it's stable. Originally it was built by andralex, he didn't create this threat as he was waiting the permission from other developer whose groundwork he used. But I lost contact with him. Seems he is very busy.
Now the other developer builded the rom, his nickname is kv123.
--------------
To get usb otg working use this in terminal when you inserted usb stick
------------
After any lineageos update dont forget about play store to give permissions for storage. Otherwise it wont download any apps larger the 20 mb.
Lineage camera is a bit buggy, so it's better to use open camera.
---------
There are the links
https://www.androidfilehost.com/?fid=745425885120730219
https://yadi.sk/d/Zfxi3agx3HkLQL
Some developer links:
https://review.lineageos.org/#/q/project:LineageOS/android_kernel_sony_msm8994
https://github.com/LineageOS/android_kernel_sony_msm8994
If you want I can ask kv123 to build the rom for sgp712 too.
Click to expand...
Click to collapse
Hi, could you please add some screenshots?

Ok. Added to the top.

need rom for SG712 please...

Thanks for sharing. SGP712 build would be great

Charsher47 said:
Thanks for sharing. SGP712 build would be great
Click to expand...
Click to collapse
Kv123 told me that he's gonna build the rom for 712 too.

I don't have SPG712, so i cannot test it. I was lazy to download firmware for 712, so libs are from 771. Hope they are the same. Who have please leave some feedback.
SGP712_lineageos_14_1
P.S. Nfc may not work. I will need to do some tests.

kv123 said:
I don't have SPG712, so i cannot test it. I was lazy to download firmware for 712, so libs are from 771. Hope they are the same. Who have please leave some feedback.
SGP712_lineageos_14_1
P.S. Nfc may not work. I will need to do some tests.
Click to expand...
Click to collapse
I flashed the rom with Androplus' TWRP-3.0.2-0-20160604, Error 7 because target device is karin_windy but the recovery says the device is karin (actually SGP712, it's karin_windy).
So i deleted the device verification in the updater-script, and it's Error 6 now...

Phil_Libra said:
I flashed the rom with Androplus' TWRP-3.0.2-0-20160604, Error 7 because target device is karin_windy but the recovery says the device is karin (actually SGP712, it's karin_windy).
So i deleted the device verification in the updater-script, and it's Error 6 now...
Click to expand...
Click to collapse
Why do you use androplus recovery? Use normal recovery, take it from yandex disk. And boot by vol- and power till it vibrates.

alex009988 said:
Why do you use androplus recovery? Use normal recovery, take it from yandex disk. And boot by vol- and power till it vibrates.
Click to expand...
Click to collapse
Nothing happens after I flashed the recoveries from yandex disk（both 3.0.3 and 3.1), so I tried androplus recovery...
Is there a modified boot.img for those recoveries?
P.S. I flashed 32.3.A.2.33.ftf first.
---------- Post added at 10:29 AM ---------- Previous post was at 10:22 AM ----------
I flashed 32.3.A.2.33 with flashtool, then flash the recovery in fastboot mode with:
Code:
fastboot flash recovery [I]recovery name[/I]
then pressed vol- and power, nothing happens and the tablet boots to the system.

Maybe it's better: fastboot flash recovery twrp.img ?
This twrp only requires updated bootloader from 7.0 stock.
Also i need to keep these buttons pressed untill it vibrates that is 2-3 seconds.
You can find kv123 at this thread http://4pda.ru/forum/index.php?showtopic=706675
Also you can try to contact with andralex8. He has just 712 tablet. And it worked for him. But I'm not sure if he answers you quickly.
If you keep trouble with the recovery, try twrp from this https://forum.xda-developers.com/z4-tablet/general/guide-nougat-drm-fix-root-twrp-sgp771-t3555265

Phil_Libra said:
Nothing happens after I flashed the recoveries from yandex disk（both 3.0.3 and 3.1), so I tried androplus recovery...
Is there a modified boot.img for those recoveries?
P.S. I flashed 32.3.A.2.33.ftf first.
---------- Post added at 10:29 AM ---------- Previous post was at 10:22 AM ----------
I flashed 32.3.A.2.33 with flashtool, then flash the recovery in fastboot mode with:
Code:
fastboot flash recovery [I]recovery name[/I]
then pressed vol- and power, nothing happens and the tablet boots to the system.
Click to expand...
Click to collapse
Sorry if I have missed something obvious, but are you attempting to flash LineageOS? In which case I am confused as to why you are flashing the Sony Rom 32.A.2.33?
For my part I am gearing up to attempt the LineageOS install but would like to have a backup copy of the Sony firmware in case it goes wrong.
Assuming you installed an English version, which one did you select from here:-
https://xpericheck.com/device/SGP771

Indeed, if you try something especially unchecked, better to have a backup.
But you also need to have last sony rom(any of android 7.0) in order to update bootloader and have last twrp working.

alex009988 said:
Maybe it's better: fastboot flash recovery twrp.img ?
This twrp only requires updated bootloader from 7.0 stock.
Also i need to keep these buttons pressed untill it vibrates that is 2-3 seconds.
You can find kv123 at this thread http://4pda.ru/forum/index.php?showtopic=706675
Also you can try to contact with andralex8. He has just 712 tablet. And it worked for him. But I'm not sure if he answers you quickly.
If you keep trouble with the recovery, try twrp from this https://forum.xda-developers.com/z4-tablet/general/guide-nougat-drm-fix-root-twrp-sgp771-t3555265
Click to expand...
Click to collapse
Androplus‘ recovery need a modified boot.img so I wonder if the same as the recovery in yandex disk?
And recovery from https://forum.xda-developers.com/z4-tablet/general/guide-nougat-drm-fix-root-twrp-sgp771-t3555265 is the same as Androplus’ recovery.

Ok. If you've done everything right I guess 712 dosent work with 771 recovery. I'll tell about it to kv123 and you can say it on your own on 4pda.

Please anybody who has 712 model. Test 3.1 recovery from yandex disk and confirm or contradict if it dosent work for you.

Phil_Libra said:
Nothing happens after I flashed the recoveries from yandex disk（both 3.0.3 and 3.1), so I tried androplus recovery...
Is there a modified boot.img for those recoveries?
P.S. I flashed 32.3.A.2.33.ftf first.
---------- Post added at 10:29 AM ---------- Previous post was at 10:22 AM ----------
I flashed 32.3.A.2.33 with flashtool, then flash the recovery in fastboot mode with:
Code:
fastboot flash recovery [I]recovery name[/I]
then pressed vol- and power, nothing happens and the tablet boots to the system.
Click to expand...
Click to collapse
alex009988 said:
Please anybody who has 712 model. Test 3.1 recovery from yandex disk and confirm or contradict if it dosent work for you.
Click to expand...
Click to collapse
I'm seeing the same results. Tried the same recoveries to no avail.