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
Related
This is a very quick simple guide, and I won't be tracking this thread answering questions.
You are expected to do a bit of your own research, but this is not complicated.
I won't be hot-linking anything here so use google, it's your best friend.
[ Heimdall Root Method #1 ]
Grab a CWM recovery kernel from a OneClickRoot (zImage).
Flash it with Heimdall to "Recovery".
Boot to CWM recovery and flash your favorite rom.
Done.
[ Heimdall Root Method #2 ]
::The short guide::
Grab a rooted kernel with RFS support (zImage).
Grab a CWM recovery kernel from a OneClickRoot (also a zImage so rename it).
Flash them with Heimdall.
Install Superuser from the Market (recommended).
Flash a rom in CWM recovery if desired.
Done.
[ Heimdall Root Method #2 ]
::The verbose guide::
If using windows, download and install the drivers from Samsung.
Verify the drivers are working (it sometimes helps to re-connect after the initial driver install).
Linux (Ubuntu) users don't need drivers.
Unplug the phone from USB.
Download and install Heimdall.
Download the OneClickRoot of your choice.
Inside the OneClickRoot package there is a zImage file, this is the CWM recovery kernel.
Extract the zImage, rename to "recovery.bin".
Remember CWM v3.0.0.6 will convert to EXT4 if you boot to it, so have a rom ready to install!
Download a custom rooted kernel that supports RFS (DRockstar's Clean Kernel comes to mind).
Find and extract the zImage file from the kernel package.
Open Heimdall.
Add the "zImage" file where it says "Kernel (zImage)".
Add the "recovery.bin" file where it says "Recovery".
Power off phone.
Press and hold both the #1 Key on the keyboard and the Power button to boot to Download Mode.
Connect the phone to the PC via USB.
Click the "Start" button.
Wait for the phone to reboot.
Install Superuser from the Market (recommended).
Flash a rom in CWM recovery if desired.
Done.
=]
That is easy!!! Thanks
if you cant live large, look big in the coffin!!!
Lol. Never thought of doing this. I guess this will be the method of choice since the one click roots will be obsolete soon.
Sent from my SPH-D700 using XDA Premium App
Thats funny this post came up.. I just used heidmall for the first time yesterday
Tapatalkin' it from my Epic 3g
Cool. Expanding on this, where do all the pieces of the EB 13 go if I wanted to go back to that? I assume I expand the tar and place them appropriately?
Bonsai kinda recommends EB13 prior to flashing.
Sent from my SPH-D700 using XDA Premium App
akenis said:
Cool. Expanding on this, where do all the pieces of the EB 13 go if I wanted to go back to that? I assume I expand the tar and place them appropriately?
Bonsai kinda recommends EB13 prior to flashing.
Click to expand...
Click to collapse
PIT = "victory_8G_100528.pit"
FactoryFS = "factoryfs.rfs"
Kernel (zImage) = "zImage"
Param.lfs = "param.lfs"
Primary Bootloader = "boot.bin"
Secondary Bootloader = "Sbl.bin"
Cache = "cache.rfs"
Database Data = "datafs.rfs"
Modem = "modem.bin"
Recovery = "recovery.bin"
Note that the PIT file is not included in the tar files, you will need to obtain this elsewhere (most Odin downloads include it).
Also, if you place the PIT file in the PIT area, Heimdall will not enable the "Start" button unless all files have been selected (as it will re-partition the device).
So only use a PIT when flashing the full tar (all of the individual pieces).
=]
This should be a sticky. Awesome posts Nube.
if you cant live large, look big in the coffin!!!
musclehead84 said:
This should be a sticky. Awesome posts Nube.
if you cant live large, look big in the coffin!!!
Click to expand...
Click to collapse
;] Thankx, but sticky? IDK, maybe someone will re-write it with embedded links and such (photo's maybe) to make a proper "nube-friendly" guide out of it.
This method came in handy for me the other day, I had gone to 100% stock for some CIQ packet capture testing, and was leaving home for a while.
I wanted to have my rooted device back, so I did a quick Heimdall flash of CWM and left the house.
I was then able to be mobile as I used CWM to install my Rom, addons, and etc..
Very quick and convenient IMO, and I'm a bit surprised it hasn't really been mentioned before.
=]
Nm
10char...
nubecoder said:
;] Thankx, but sticky? IDK, maybe someone will re-write it with embedded links and such (photo's maybe) to make a proper "nube-friendly" guide out of it.
This method came in handy for me the other day, I had gone to 100% stock for some CIQ packet capture testing, and was leaving home for a while.
I wanted to have my rooted device back, so I did a quick Heimdall flash of CWM and left the house.
I was then able to be mobile as I used CWM to install my Rom, addons, and etc..
Very quick and convenient IMO, and I'm a bit surprised it hasn't really been mentioned before.
=]
Click to expand...
Click to collapse
Either way its still an awesome guide to use. I just got heimdall set you the other day and used it to flash eb13 and its so much better than odin. People better get used to heimdall cause this will ne our rooting method when gb drops.
if you cant live large, look big in the coffin!!!
This kernel will provide you the standard stock kernel and also includes TWRP recovery.
( disclaimer )
I AM NOT TO BE HELD RESPONSIBLE IF YOU DAMAGE YOUR PHONE
Using Odin to flash this kernel WILL increase your binary counter.
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
( features )
- Team Win Recovery Project 2.2.1
- CIFS Support
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
( how to install using Odin )
1. Restart into download mode by pressing Power + Home + Vol Down
2. Start Odin, and flash the attached kernel as PDA.
Remember to extract the attached file only once. if you end up with a kernel.bin.md5 you extracted twice!
Do not use the PIT, do not have any options checked except for "Auto reboot" and "F. Reset Time"
3. Wait for the device to reboot
( how to install using DD )
This method does not increase your binary counter, but your phone needs to be rooted so you can perform this!
IF YOU'RE NOT FAMILIAR WITH DD I RECOMMEND YOU TO AVOID THIS METHOD
1. Extract the attached file twice. You will end up with a kernel.bin.md5 file
2. Put the kernel.bin.md5 file to /sdcard
3. Start adb shell
4. Do the following commands:
Code:
$ su
# dd if=/sdcard/kernel.bin.md5 of=/dev/block/mmcblk0p15
# reboot
5. Wait for the device to reboot.
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
( special thanks )
- Team Win for creating this awesome custom recovery.
- @Chris41g for starting the TWRP port.
- @hackbob for helping with the kernel issues.
( donations )
if you think that think that the work I put in this kernel is donation worthy,
then click the following link and buy me a beer/coffee/etc...
Donate via Paypal :good:
Enjoy! and don't forget to hit the thanks button
if you find any issues with this kernel, please report!
reserved.
Can you give me just compiled zImage i.e kernel image ASAP?
varun.chitre15 said:
Can you give me just compiled zImage i.e kernel image ASAP?
Click to expand...
Click to collapse
You can download the package and extract the kernel.bin.md5.
While building it's generated as zImage and after renamed to kernel.bin and md5ed for Odin
Well actually, that is not what I need because kernel.bin.md5 contains initramfs which is known as ramdisk usually. But I only need kernel i.e zImage which I am planning to repack to boot.img
Correct me if I am wrong
varun.chitre15 said:
Well actually, that is not what I need because kernel.bin.md5 contains initramfs which is known as ramdisk usually. But I only need kernel i.e zImage which I am planning to repack to boot.img
Correct me if I am wrong
Click to expand...
Click to collapse
Yep you are right, sorry for the misunderstanding.
I can build it (from Github) for you without the ramdisk but I'm not sure it will work correctly without the driver added from the ramdisk to the kernel image during the build.
---------- Post added at 05:27 PM ---------- Previous post was at 05:22 PM ----------
Just to be sure...
I'm trying to compile cm7 and the intrafms are added with the kernel while building the boot.img, because in the intrafms that we are adding to kernel image we are basically adding the modules for wifi,bt, etc...
You sure you don't need them?
hackbob said:
Yep you are right, sorry for the misunderstanding.
I can build it (from Github) for you without the ramdisk but I'm not sure it will work correctly without the driver added from the ramdisk to the kernel image during the build.
Click to expand...
Click to collapse
Ok can you do that, test it and report back ASAP?
This is needed before I release my ROM
btw I think we should move on to main DEV thread
Post your next reply over there
@varun.chitre15
you can try to build it from source...
the source code is available on github: https://github.com/diego-ch/android_kernel_samsung_janice
hackbob said:
[/COLOR]Just to be sure...
I'm trying to compile cm7 and the intrafms are added with the kernel while building the boot.img, because in the intrafms that we are adding to kernel image we are basically adding the modules for wifi,bt, etc...
You sure you don't need them?
Click to expand...
Click to collapse
Oh great!
Can you get me the boot.img compiled while building
I will take what all I need from it
---------- Post added at 09:01 PM ---------- Previous post was at 09:00 PM ----------
diego-ch said:
@varun.chitre15
you can try to build it from source...
the source code is available on github: https://github.com/diego-ch/android_kernel_samsung_janice
Click to expand...
Click to collapse
Well actually I am trying to avoid that because I have no experience in kernel development
Can i extract it from the rom? I got boot.img and recovery.img, is that you need?
Sent from my GT-I9070 using Tapatalk 2
Exactly!
Attach the boot.img
varun.chitre15 said:
Exactly!
Attach the boot.img
Click to expand...
Click to collapse
i sent you a pm
Hi,
I just flashed this using Odin and i cant see my sd card in TWRP so i cant flash any roms and also the device wont root using SuperOneClick it hangs on shell root #7 Waiting for device...
Would it be possible to create a kernel with recovery for Advance with NFC chip?
xCode195 said:
Hi,
I just flashed this using Odin and i cant see my sd card in TWRP so i cant flash any roms and also the device wont root using SuperOneClick it hangs on shell root #7 Waiting for device...
Click to expand...
Click to collapse
Have you setup USB drivers of your phone?
Waiting for device indicates, Superone click is unable to contact your phone.
Am I the only one with TWRP restore not Working properly?
Backedup the default partition (system, data and another that I don't remember), Restored, everything seems fine (no error on twrp) but after a reboot the phone goes into bootloop.
varun.chitre15 said:
Have you setup USB drivers of your phone?
Waiting for device indicates, Superone click is unable to contact your phone.
Click to expand...
Click to collapse
Yep I tried installing them again and it got stuck on the same step but now i also get Hardware ID Failed popup when I connect the device..
Should I reflash the kernel or do something else?
Iv backuped and restored a few times and its ok
Sent from my GT-I9070 using Tapatalk 2
hackbob said:
Am I the only one with TWRP restore not Working properly?
Backedup the default partition (system, data and another that I don't remember), Restored, everything seems fine (no error on twrp) but after a reboot the phone goes into bootloop.
Click to expand...
Click to collapse
I was testing antonio's rom yesterday and before that I made a full backup.
today I restored my backup and everything was fine.
get me a logcat, a dmesg log and also a recovery.log so I can take a look on whats wrong.
xCode195 said:
Hi,
I just flashed this using Odin and i cant see my sd card in TWRP so i cant flash any roms and also the device wont root using SuperOneClick it hangs on shell root #7 Waiting for device...
Click to expand...
Click to collapse
you can also use CWM Flasheable SuperSu from Chainfire instead of supéroneclick
do you have an external sdcard? it wont work with internal memory.
diego-ch said:
you can also use CWM Flasheable SuperSu from Chainfire instead of supéroneclick
do you have an external sdcard? it wont work with internal memory.
Click to expand...
Click to collapse
I would try that if I could get TWRP to read my sdcard,it says its browsing the sdcard but none of my files or folders are there and its just empty.When i reboot into the system everything is there but not in TWRP...
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.
I have a non-rooted phone with TWRP installed. When the phone tries to install the MDL update, the phone boots into recovery, but goes to TWRP. And it fails each time. Has anyone else successfully loaded the update with TWRP installed on a non-rooted phone? Do I need to remove TWRP to get this to work and, if so, how is that done?
Here's the log from TWRP:
Running boot script...
Finished running boot script.
I:Inserting 'install =/cache/321a2cb29b9c.update_SPH-L720_MDC_CSB_user_RP_to_MDL_CSB_user_RP-1.zip'
I:Copying file /cache/recovery/log to /cache/recovery/last_log
I:Attempt to load settings from settings file...
I:Loading settings from '/data/media/0/TWRP/.twrps'.
I:Backup folder set to '/external_sd/TWRP/BACKUPS/cdc9d69d'
I:Version number saved to '/cache/recovery/.version'
I:Switching packages (TWRP)
I:Set page: 'action_page'
Processing AOSP recovery commands...
I:command is: 'install' and I:value is: '=/cache/321a2cb29b9c.update_SPH-L720_MDC_CSB_user_RP_to_MDL_CSB_user_RP-1.zip'
I:Unable to mount '/usb-otg'
I:Actual block device: '', current file system: 'vfat'
I:Unable to mount '/usb-otg'
I:Actual block device: '', current file system: 'vfat'
I:Full zip path: '/external_sd/=/cache/321a2cb29b9c.update_SPH-L720_MDC_CSB_user_RP_to_MDL_CSB_user_RP-1.zip'
Installing zip file '/cache//321a2cb29b9c.update_SPH-L720_MDC_CSB_user_RP_to_MDL_CSB_user_RP-1.zip'
Installing '/cache//321a2cb29b9c.update_SPH-L720_MDC_CSB_user_RP_to_MDL_CSB_user_RP-1.zip'...
Checking for MD5 file...
I:Cannot find file /cache//321a2cb29b9c.update_SPH-L720_MDC_CSB_user_RP_to_MDL_CSB_user_RP-1.zip.md5
Skipping MD5 check: no MD5 file found.
Register_libbootloader_updater Qcom msm8960
Verifying current system...
partition read matched size 9214720 sha 752ba02ce73412313a123b43ac0ae9bc46e13d22
partition read matched size 52009728 sha 52d27452b5e779ba0fdb676c453d3f2d1f294569
2049134592 bytes free on /cache (87488677 needed)
script aborted: assert failed: getprop("ro.secure")=="1"
assert failed: getprop("ro.secure")=="1"
E:Error executing updater binary in zip '/cache//321a2cb29b9c.update_SPH-L720_MDC_CSB_user_RP_to_MDL_CSB_user_RP-1.zip'
E:Error installing zip file '/cache//321a2cb29b9c.update_SPH-L720_MDC_CSB_user_RP_to_MDL_CSB_user_RP-1.zip'
Done processing script file
I installed OUDHS ( http://forum.xda-developers.com/showthread.php?t=2254678 ) over TWRP and still get the same error I bolded from the log above.
Can someone please tell me how to get the stock recovery back? Do I need to flash/odin the base ROM? If so, where can I find the Sprint version?
You want to unroot? There are threads on the MDL update with flashable versions. Read thoroughly because a lot has changed.
Here: http://forum.xda-developers.com/showthread.php?t=2270065
jejb said:
I installed OUDHS ( http://forum.xda-developers.com/showthread.php?t=2254678 ) over TWRP and still get the same error I bolded from the log above.
Can someone please tell me how to get the stock recovery back? Do I need to flash/odin the base ROM? If so, where can I find the Sprint version?
Click to expand...
Click to collapse
Here - I placed the Stock Recovery in tar form on RWilco12's Repo. Just flash With Odin.
I'll be making a one click for this as well. (I'll also make sure all the stock items are tar'd and in one click formats.)
http://www.rwilco12.com/downloads.php?dir=Files/Devices/Samsung%20Galaxy%20S4%20%28SPH-L720%29/Recovery/Stock/MDC
As far as the update failing or not, and if you want to go back completely stock; there are also MDC NoData and Full Restore tars and in his Repo. Depending on your flash history, you may want to obtain root and use Chainfrire's Triangle Away. (Even though the i9505 variant isn't on his supported list, it does work resetting the binary counter) Then you'd want to flash the stock build.
http://www.rwilco12.com/downloads.php?dir=Files/Devices/Samsung%20Galaxy%20S4%20%28SPH-L720%29/Stock%20ROMs/MDC/
MoHoGalore said:
Here - I placed the Stock Recovery in tar form on RWilco12's Repo. Just flash With Odin.
I'll be making a one click for this as well. (I'll also make sure all the stock items are tar'd and in one click formats.)
http://www.rwilco12.com/downloads.php?dir=Files/Devices/Samsung%20Galaxy%20S4%20%28SPH-L720%29/Recovery/Stock/MDC
Click to expand...
Click to collapse
Thanks much! But I'm having an issue loading this. The Odin load started off well, but it's been sitting in the following state for like 10 minutes now. I'm afraid to unplug the phone/stop the update for fear of having a brick. Loading TWRP and OUDHS with Odin only took a few seconds, so it's not looking good.
jejb said:
Thanks much! But I'm having an issue loading this. The Odin load started off well, but it's been sitting in the following state for like 10 minutes now. I'm afraid to unplug the phone/stop the update for fear of having a brick. Loading TWRP and OUDHS with Odin only took a few seconds, so it's not looking good.
Click to expand...
Click to collapse
Looks like you renamed the file. Did you?
Pull battery, boot back into Odin mode and don't rename the file. There's no reason to. It should be .tar.md5
No. I did notice the rename when my Win7 system pulled it down, but I did nothing to it explicitly.
jejb said:
No. I did notice the rename when my Win7 system pulled it down, but I did nothing to it explicitly.
Click to expand...
Click to collapse
Look at my post above. I added a picture. There shouldn't be anything renaming it.
Download a fresh copy, pull battery, get back to Odin mode and re-flash.
MoHoGalore said:
As far as the update failing or not, and if you want to go back completely stock; there are also MDC NoData and Full Restore tars and in his Repo. Depending on your flash history, you may want to obtain root and use Chainfrire's Triangle Away. (Even though the i9505 variant isn't on his supported list, it does work resetting the binary counter) Then you'd want to flash the stock build.
http://www.rwilco12.com/downloads.php?dir=Files/Devices/Samsung%20Galaxy%20S4%20%28SPH-L720%29/Stock%20ROMs/MDC/
Click to expand...
Click to collapse
So in reading about Triangle Away, it seems I may have screwed myself up by loading a custom recovery, even though I'm not rooted? That sucks, if so. But I've not read about anyone else having issues like this and I can't be the only one to have loaded a custom recovery and tried to do the update. Thanks for the procedure, though. I guess I may have to try all of that to get back to stock (if the phone isn't bricked, still trying to load).
Delete
jejb said:
So in reading about Triangle Away, it seems I may have screwed myself up by loading a custom recovery, even though I'm not rooted? That sucks, if so. But I've not read about anyone else having issues like this and I can't be the only one to have loaded a custom recovery and tried to do the update. Thanks for the procedure, though. I guess I may have to try all of that to get back to stock (if the phone isn't bricked, still trying to load).
Click to expand...
Click to collapse
It's not bricked. It's just a failed flash. You have a few choices.
My recommendation for you;
1. Get the rooted, nodata, MDC One Click, the exe. (That way we know nothing will be renaming the file)
2. Put your phone in Odin mode and flash.
3. Go get Chainfire's Triangle Away v2.90 (This is a link to Chainfire's XDA thread which is permissible)
4. Use the app.
5. Backup anything you'd like to keep to pc.
6. Go get the Stock MDC Full Restore and flash via Odin.
Now you'll be back to stock, un-rooted and Official on build and binary and can apply the update from OTA.
You can get the stock build from the Repo.
Turns out it was IE that was forcing the rename on the file. So I pulled it down with firefox and it did not rename it. But when I try to load it, it tells me the MD5 hash did not match and ends. So I took the MD5 off the end and tried it just as a .tar file. Got the same endless load as the first time I tried it above.
I may have to go through the steps you spelled out in your last post, and I really appreciate you taking the time to do that. But shouldn't this stock recovery at least load? I'm a bit worried that if this file won't load, will the others I pull down from the same download site give me the same issues?
Give me a min and I'll upload my tested copy to dev host so you'll have an md5 to compare. Possible it was a bad upload from me to the repo.
Sent from my SPH-L720 using Xparent Skyblue Tapatalk 2
:Edit: Here's the tested copy of the Recovery. http://d-h.st/0fp
MoHoGalore said:
Give me a min and I'll upload my tested copy to dev host so you'll have an md5 to compare. Possible it was a bad upload from me to the repo.
Sent from my SPH-L720 using Xparent Skyblue Tapatalk 2
:Edit: Here's the tested copy of the Recovery. http://d-h.st/0fp
Click to expand...
Click to collapse
Thank you SO much! That copy did work successfully via Odin to put the stock recovery back on the phone. And the MDL update ran successfully after that was done. So I'm now up to the latest level and not rooted. I'll probably put the OUDHS recovery on again now that I have a good copy of the stock recovery that I can always go back to if needed.
It's folks like you that make this board such a valuable resource. Thanks again.
Good to know you got up and running. And I replaced it again on the Repo. Looks like Dev Host went down in the last few minutes so I was worried if you got it or not.
Glad to help. :beer:
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?