Database Users

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

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

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

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

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

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

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

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

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

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

It should work

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

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

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

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

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

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

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

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

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

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

[MOD] MultiROM

this is beta release. for t900 only.
I'll write full instruction later. For full description see http://forum.xda-developers.com/show....php?t=2011403
I'm not sure that everything is stable, so I dont publish source code. I dont want to distribute buggy sources. thanks for understanding.
for stock firmware only. for now. use stock firmware as primary. you can flash cm as additional.
Installation:
1. https://yadi.sk/d/9t2yfkIPc7yPj - this is modded recovery. flash via odin (updated 19/10. Thanks to @arcadia2uk for fix flashing bug)
2. https://yadi.sk/d/TtXcwe6Hc54cR - patched stock kernel
https://yadi.sk/d/r2lnH3N3c54eF - multirom main program
flash through modded recovery patched kernel and multirom.
uninstallation:
https://yadi.sk/d/r9ZLm0vCc68um - flash this uninstaller through recovery, then flash original twrp
known issues:
- 1920x1200 resolution in twrp
- in List Roms installed roms dont shown
- in multirom boot menu touchscreen downt work. use buttons (vol-,vol+,power)
multirom apk from play store doesnt support this release.

reserved

more reserved

bonuzzz said:
this is beta release. for t900 only.
I'll write full instruction later. For full description see http://forum.xda-developers.com/show....php?t=2011403
I'm not sure that everything is stable, so I dont publish source code. I dont want to distribute buggy sources. thanks for understanding.
for stock firmware only. for now. use stock frimware as primary. you can flash cm as additional.
Click to expand...
Click to collapse
Nice, I have to try this later on. I noticed that after having installed CM11, I can no longer flash touchwiz (I deleted my back-up, as I no longer needed it...), why I probably have to start all over and use Odin to re-install stock and then install multi ROM on top of it. I will look into it once I get some time over.
When you are saying "stock firmware", could this be any customized touchwiz ROM?
PS the link to the MultiROM decription does not work, here is the correct one http://forum.xda-developers.com/showthread.php?t=2011403

arcadia2uk said:
Nice, I have to try this later on. I noticed that after having installed CM11, I can no longer flash touchwiz (I deleted my back-up, as I no longer needed it...), why I probably have to start all over and use Odin to re-install stock and then install multi ROM on top of it. I will look into it once I get some time over.
When you are saying "stock firmware", could this be any customized touchwiz ROM?
Click to expand...
Click to collapse
yes, every touchwiz rom
I have to recompile cm kernel to support multirom. I'll do it later. It depends on Valera's decision whether support t900 or not.

bonuzzz said:
this is beta release. for t900 only.
Installation:
1. https://yadi.sk/d/Sm4V4SMDc54ay - this is modded recovery. flash via odin
uninstallation:
https://yadi.sk/d/Sm4V4SMDc54ay - flash this uninstaller through recovery, then flash original twrp
Click to expand...
Click to collapse
It doesn't seem correct that the modded recovery and the installer has the same d/l link?
---------- Post added at 11:35 PM ---------- Previous post was at 10:52 PM ----------
bonuzzz said:
yes, every touchwiz rom
I have to recompile cm kernel to support multirom. I'll do it later. It depends on Valera's decision whether support t900 or not.
Click to expand...
Click to collapse
When trying to flash the recovery with Odin there's an error message saying that the MD5 Hash value is invalid, recovery_mr_t900.tar.md5 is invalid.

I recompiled recovery and refreshed links. try again to flash.

bonuzzz said:
I recompiled recovery and refreshed links. try again to flash.
Click to expand...
Click to collapse
Odin is still diplaying the message that md5 is invalid.
Maybe a file w/o md5 would work?

arcadia2uk said:
Odin is still diplaying the message that md5 is invalid.
Maybe a file w/o md5 would work?
Click to expand...
Click to collapse
unpack archive and try to flash recovery.img with flashify. maybe change version of odin. i use 3.09.3

bonuzzz said:
unpack archive and try to flash recovery.img with flashify. maybe change version of odin. i use 3.09.3
Click to expand...
Click to collapse
I renamed the tar file by taking away the .md5, that worked.
The boot with the stock ROM went fine. However, I tried install my cm11 by restoring a backup and got stuck, or so I thought it actually came to life after having looked a SOD for 5 min. so I guess it went well. Next problem is that when I'm on the MultiROM boot menu it doesn't give me the option to select the alternative ROM, but makes the countdown and then boots internal. There is no possibility for me to select my alternative ROM as the blue strip does not react to touch. Well, I hope you understand what I mean...
---------- Post added at 09:59 AM ---------- Previous post was at 09:29 AM ----------
bonuzzz said:
unpack archive and try to flash recovery.img with flashify. maybe change version of odin. i use 3.09.3
Click to expand...
Click to collapse
It might also be linked to the fact that the recovery is trying to validate the ROM as a v2awifi, while it should be v2wifixx on the T-900.
I assume the recovery.img need to be modified?
---------- Post added at 10:19 AM ---------- Previous post was at 09:59 AM ----------
It's actually as simple as touch mode that is disabled in the bootmenu, and you have to use up/down keys to select and power key to confirm your ROM choice (I bet it says this in the OP already...)
Now when that is cleared out it seem to be running great, but as I need to test drive another T-900 Rom I have to uninstall it as I need original TWRP to flash that ROM, due to the naming convention.
After all this gave me the opportunity to test the uninstaller that also worked well
.
So the only issue is the Recovery naming convention the T-900 should be v2wifixx.
This is how I came to have the v2wifixx:
TWRP 2.8.0.0 downloaded from http://www.techerrata.com/browse/twrp2/v2wifixx where I selected openrecovery-twrp-2.8.0.0-v2wifixx.img.tar and flashed it with Odin 3.07. This is the most common version for T-900 owners, as they followed the posted instructions HERE. It's also the version for which Valeria ported the cm-11.

I dont have t900, so i dont know these details
v2wifixx or v2awifixx?

bonuzzz said:
I dont have t900, so i dont know these details
v2wifixx or v2awifixx?
Click to expand...
Click to collapse
v2wifixx is the one. (no a after the 2)
But as I mentioned, apart from the small glitches you mention in the OP everything runs smoothly, and what a relief it is to quickly transfer between different ROMs. Great work, I just wished we had a decent touchwiz ROM for the T-900... Thank you, Great work (but I'm getting used to it ) With this, the only thing I had wished for is a 64G internal SD, rather than the 32G I have, unfortunately you can't perform miracles Bonuzzz.
I've been looking into MultiROM before, bet never saw the need for it, but after this experience I have also installed it on my HTC One (m8) which allows me to test ROMs quickly and smoothly, what a difference it makes.

Updated 10/18/2014 08:40am EST
Temporary work around:
1. backup you TouchWiz ROM* (TW),
2. install cm11(s) prior to MultiROM and make a backup,
3. recover your TW, and
4. proceed with MultiROM install after Bonuzzz's instructions in post 1
Once a fixed recovery is available, simply flash this new recovery image and you're good to go. As of that point you can update cm11 nightly's on the go.
HOW to Updating/changing ROMs
Primary ROM (Internal)
- Flash ROM's ZIP file as usual, do factory reset if needed (it won't erase secondary ROMs) (note: don't forget fixed kernel)
- Go to Advanced -> MultiROM in recovery and do Inject curr. boot sector.
Secondary Android ROMs
- If you want to change the ROM, delete it and add new one. To update ROM, follow these steps:
- Go to Advanced -> MultiROM -> List ROMs and select the ROM you want to update.
- Select "Flash ZIP" and flash ROM's ZIP file.
* I installed Bonuzz's Custom ROM 1.0.1 (for the P-900) and flashed his MultiROM kernel (see post 1) on top of it. And with no other modifications it seems to work perfectly well. I have only encountered a single minor issue, auto screen-rotation didn't work, but mine is always locked in landscape anyway. I froze the TouchWiz launcher and using Google Now Launcher instead, it couldn't be done w/o freeze, and also fixed an issue with incorrect cropping of my wallpaper. After all everything is good, and as always a great performance by Bonuzzz. Thank you/arc

reuploaded recovery. try again.

bonuzzz said:
reuploaded recovery. try again.
Click to expand...
Click to collapse
It looks like you accidentaly re-uploaded the same file, I have the same error message saying:
This package is for device: v2wifixx; this device is v2awifi.
E:Error executing updater binary in zip '/tmp/mr_update.zip'
Click to expand...
Click to collapse

arcadia2uk said:
It looks like you accidentaly re-uploaded the same file, I have the same error message saying:
Click to expand...
Click to collapse
you talked about multirom file but wrote recovery. i tried to find problem in wrong place.. redownload again

bonuzzz said:
you talked about multirom file but wrote recovery. i tried to find problem in wrong place.. redownload again
Click to expand...
Click to collapse
I sent you an e-mail about the problem a few minutes ago

Am I correct to assume that the only way to install cm-11 with gapps is by flashing a backup under MultiROM?
Or, at least until you can get the Advanced/MultiROM/List ROMs option corrected, since that seems to be to only place where you can flash a .zip on top of an existing ROM, and this install option only allow you to make a simple flash, or have I missed something?

bonuzzz said:
reuploaded recovery. try again.
Click to expand...
Click to collapse
Do I feel that you're abandoning this project, when you're this close....

[Guide] How to port Cwm or CTR recovery for any device

Port recovery to any Device, snapdragon, mediatech doesn't matter​
Hi guys...
Once again i am back with an Extreme guide...
Its about porting Recovery if you don't have source or if you like to use your own thing...
Ok lets start......​
Do it with your own risk, I am not responsible for anything happens to your mobile, friends, family and etc
Click to expand...
Click to collapse
Requirements:
1. Android Kitchen or Android image kitchen (Search on xda or
google)
2.NOTEPAD++ (Search on google)
3. Flash tool (flashify, rashr etc)
4. Cygwin ( if you are using Windows)
5. Recoveries that you want to port, must be from same structured chip set device, and same resulotion
Tips: Search on Google on how to set up android kitchen with cygwin
Step:1
Frist take your stock boot.img, stock recovery.img and
any other recovery like CWM or CTR (Without
TWRP)
Tips: If you don't know how to get a dump of boot.IMG or recovery.IMG, Google is there to help you! You can also use Diskinfo to get partition info, download it from play
Now put them in safe folder and unpack boot.img in a
new folder, then unpack Stock recovery in another
folder and unpack your cwm or CTR recovery in
Another folder.......
All done!!
Tips: search Google how to unpack .IMG with android kitchen or android image kitchen
Click to expand...
Click to collapse
Step:2
Now go to your unpacked boot.img and then go to "ramdisk" folder then copy these files and paste it
to your recovery (whitch you want to port)
1.meta_init.modem.rc
2.meta_init.project.rc
3.meta_init.rc
Done! :3
Click to expand...
Click to collapse
Step 3:
Now go to your unpacked stock recovery and copy "(#Kernel)" and paste it to your unpacked recovery (Which you want to port).Then again go to unpacked stock recovery>ramdisk and copy these files and paste them in your unpacked recovery>ramdisk (which you want to
port) and replace them all...
1.fstab
2.ueventd.rc
3.ueventd.goldfish.rc.
Done!
Click to expand...
Click to collapse
Step 4:
Now go to your stock unpacked CWM or CTR and go to
ramdisk/etc and copy ( recovery.fstab ) and paste
it to you unpacked recovery (which you want to
port) /ramdisk/etc and replace......
Done!Now go to your unpacked recovery (whitch
you want to port) then go to ramdisk and open
default.prop and ask also open the default.prop. compare them, change the values of port recovery according to stock recovery.
All Done!
Click to expand...
Click to collapse
Finel step :
Repack the ported cwm, take it to your phone and open any flash tools and flash your new recovery!!
Click to expand...
Click to collapse
N.B.--> This method will not work in TWRP porting beacuse porting TWRP is different...
Sometimes your new recovery may not work...if it does not work then try again with new recoveries from different device or redo the whole thing
I hope this post was helpfull and if you
successed to port your new recovery then dont
forget to give me some credits
if you like this post then click on :good: button... It may increase the rate of
giving new guides...​ :highfive:

Hi, I am trying to do a CWM recovery for Amazon fire phone which is a Snapdragon 800 - unfortunately i cannot find any custom recoveries which have the amazon fire phones resolution of 1280 x 720 can you advise if there is a workaround for this situation?

Hey there, if you are porting cwm, the resolution isn't gonna be a problem. Find same structured device and you would be good to go.
Edit: the fonts will maybe look smaller.

But if you are porting CTR recovery the resolution would be a problem, it will cause you touch problem in recovery

Thanks. One problem right at the first hurdle is in step 2
i do not have these files in my boot ramdisk folder
1.meta_init.modem.rc
2.meta_init.project.rc
3.meta_init.rc
Attached is a screenshot of what i have in mine?!?

Can I get a screenshot of the unpacked recovery ( that you want to port)? I want to compare these files

The screenshot of the unpacked Recovery's ramdisk folder actually

Sure, attached. This is my recovery from my Amazon phone and also the recovery for a nexus 5 which uses the same processor

Init.rc, ueventd.rc, replace these two files

Snapdragon device's boot and recovery structure is different, I thing I have to do the tutorial again with snapdragon details

BTW is there any other version of cwm available for your device? You can take a look inside that recovery for more info. And if your device has source, I recommend that building it from source would be best for you

Hi, I actually just built from source but nothing happens when phone should go into recovery. Just stays on the Amazon screen. I then flash the stock recovery back and it works fine. I'm pretty sure that i compiled it correctly as i got no errors used CM11 as source. (Attached if it helps)
To be honest it was a shot in the dark anyway as the phones bootloader is locked and i was trying with flashify.apk

Have you tried grabbing a logcat after rebooting from recovery?

Thats my next step

And what does the logcat says?

Please help.
I have got an android device with Broadcom Processor with android 4.4.2. I had tried to learn using Ubuntu and tried to build recovery from source. But, it seems a clumsy path and hard to understand. I could not finish syncing repo and retired from my trial a month ago. Can I use this tutorial to port recovery to my device? How can I know which CWM for an android can be ported to mine?

bro this is not working for snapdragon devices. as i am not getting meta files into its recovery not even in the ported one.

I can't understand the which recovery is which, like in Step 3 you said Stock recovery and unpacked recovery (Which you want to port) where i guess stock is the original recovery and unpacked is CWM/CTR.
But on Step 4 you said:
"go to your stock unpacked CWM or CTR and go to
ramdisk/etc and copy ( recovery.fstab ) and paste
it to you unpacked recovery (which you want to
port) /ramdisk/etc and replace."
so stock unpacked CWM is CWM but which one is he unpacked recovery now?

bro i have micromax a108 with mt6582m chipset and i want to port ctr for my device but i am not getting and recovery developed for mt6582m devices

Please write a new guide for Qcom Chipset !
Sent from my redmi note 4 using xda Forums PRO

Yoga Tab 2 Kernel Compilation

Has anyone else made any serious attempts at compiling a kernel? Prompted by doctorow's thread about the wakelock issue, I got interested in compiling a kernel so it could actually be fixed. For anyone who's tried at all, there are obviously some missing files in Lenovo's release.
I tried copying over the missing files from ASUS's Zenfone kernel release (since it uses the same SoC and their kernel had all the files that make was complaining about). Between that and commenting out some references to a nonexistent tablet_config.h header, it managed to at least finish compiling. Unfortunately I don't have a bootloader-unlocked device to test on yet, so I'm not terribly confident that it actually works.
P.S.: I'm not really sure if this belongs in the dev section or not? Sorry if it's in the wrong place, but I can't start threads there anyway at my current post count.

iampanis said:
I tried copying over the missing files from ASUS's Zenfone kernel release (since it uses the same SoC and their kernel had all the files that make was complaining about). Between that and commenting out some references to a nonexistent tablet_config.h header, it managed to at least finish compiling. Unfortunately I don't have a bootloader-unlocked device to test on yet, so I'm not terribly confident that it actually works.
Click to expand...
Click to collapse
Interesting, I haven't even gotten that far when I tried to compile them. The sources are most likely not up to date or even representative of the actual firmware kernel. For example, when I looked at the battery driver, I noticed in the published sources, the polling interval was hard-coded in such a way that it would completely ignore the setting of the poll_interval kernel parameter. But we know that this is not true for the actual firmware which is in fact respecting the setting of said parameter.

@Grarak and me have managed to get the messy "source code" of Lenovo to build. I have additionally added some security patches and stripped some kernel modules. Since we don't want to violate the GPL like Lenovo, we have pushed the kernel to GitHub.
Bear in mind that there may be some issues, given the kernel is a work in progress. It boots on stock as well as on cm-12.1, though.

Olivier said:
@Grarak and me have managed to get the messy "source code" of Lenovo to build. I have additionally added some security patches and stripped some kernel modules. Since we don't want to violate the GPL like Lenovo, we have pushed the kernel to GitHub.
Bear in mind that there may be some issues, given the kernel is a work in progress. It boots on stock as well as on cm-12.1, though.
Click to expand...
Click to collapse
Same kernel works for both 830f and 1050f?
Could you please post a compiled kernel? (which I assume can be flashed simply via fastboot)
Thanks!

raenye said:
Same kernel works for both 830f and 1050f?
Could you please post a compiled kernel? (which I assume can be flashed simply via fastboot)
Thanks!
Click to expand...
Click to collapse
Sure, here you go: kernel-yt2-20160327.img. I think it will boot on 1050F.

Olivier said:
Sure, here you go: kernel-yt2-20160327.img. I think it will boot on 1050F.
Click to expand...
Click to collapse
Hello, I have a 1050F too is somebody tried this kernel on 1050F? Is it possible to support wake gesture kernel extensions with this kernel?

Olivier said:
Sure, here you go: kernel-yt2-20160327.img. I think it will boot on 1050F.
Click to expand...
Click to collapse
I was able to unlock bootloader, install TWRP and flash this kernel via fastboot on both 830F and 1050F.
It works fine (and the battery life seems better since there's no wakelock bug).
Thanks!
Looking forward to alpha-grade CM....

raenye said:
I was able to unlock bootloader, install TWRP and flash this kernel via fastboot on both 830F and 1050F.
It works fine (and the battery life seems better since there's no wakelock bug).
Thanks!
Looking forward to alpha-grade CM....
Click to expand...
Click to collapse
Did you use.
Fastboot Flash recovery recoveryname.img.
or
Fastboot flash boot bootname.img
To send it to the tablet.

corasman said:
Did you use.
Fastboot Flash recovery recoveryname.img.
or
Fastboot flash boot bootname.img
To send it to the tablet.
Click to expand...
Click to collapse
The kernel goes to the boot partition. So 2nd option.

raenye said:
The kernel goes to the boot partition. So 2nd option.
Click to expand...
Click to collapse
Thanks ,I'll give it a try.
O.K tried this
I put the file in to my ADB folder
from a command prompt I typed Fastboot flash boot c:/adb/kernel-yt2-20160327.img and it returned
FAILED (remote: unknown command) any suggestion please.

corasman said:
Thanks ,I'll give it a try.
O.K tried this
I put the file in to my ADB folder
from a command prompt I typed Fastboot flash boot c:/adb/kernel-yt2-20160327.img and it returned
FAILED (remote: unknown command) any suggestion please.
Click to expand...
Click to collapse
Using windows? paths are c:\directory\file and not c:/directory/file
I used the fastboot executable from the tethered recovery package.
Checklist:
Did you unlock bootloader? it won't boot otherwise.
Did you backup current boot partition from TWRP/CWM?
Did you boot the tablet in fastboot mode? (down+pwr)
Can fastboot detect your tablet? (fastboot devices)

raenye said:
Using windows? paths are c:\directory\file and not c:/directory/file
I used the fastboot executable from the tethered recovery package.
Checklist:
Did you unlock bootloader? it won't boot otherwise.
Did you backup current boot partition from TWRP/CWM?
Did you boot the tablet in fastboot mode? (down+pwr)
Can fastboot detect your tablet? (fastboot devices)
Click to expand...
Click to collapse
Yes to all.
I wondered if the command slashes were the right way / or \ the way I used is what I used to unlock the bootloader and install TWRP.
I have tried the slashes the other way and get the same result, as in \ .

raenye said:
I was able to unlock bootloader, install TWRP and flash this kernel via fastboot on both 830F and 1050F.
It works fine (and the battery life seems better since there's no wakelock bug).
Thanks!
Click to expand...
Click to collapse
Hmm, I'm getting a high battery_wake_lock (on the April OTA firmware) -- even when running this kernel!
Any idea how can this be?

Hi,
I was trying to play a little bit with kernel provided by @Olivier and @Grarak ...
1. Binary Image kernel-yt2-20160327.img boots up fine on 1050l, but LTE is not working. Rest seems to be fine...
2. In next steps I replaced initrd.img with a little modified stock one - and LTE started to work - I removed from initrd almost all modules leaving only bcm43241.ko.
3. Battery wakelock problem seems not be resolved - brief check at bq27x00_battery.c in repository shows that wake_lock is still set under bq27x00_battery_suspend_resume()
... so I trying to fix this battery driver but I have problem with kernel - I can compile it successfully, but it doesn't boot
@Olivier:
1. Which branch was used to build kernel-yt2-20160327.img?
2. Which config did you use ?
My procedure using android-ndk-r12b toolchain:
# git clone ...github.com/lenovo-yt2-dev/android_kernel_lenovo_baytrail
# export PATH=~/android_yoga/toolchain/bin:$PATH
# export CROSS_COMPILE=x86_64-linux-android-
# export ARCH=x86
# make cyanogenmod_YT2_10_defconfig --- if this right config?
# make -j8 ----- lot's of warninigs, but kernel is compiled sucesfully.
# abootimg --create boot_test5.img -f bootimg.cfg -k bzImage -r initrd.img ---- bzImage from arch/x86/boot
> fastboot.exe flash boot boot_test5.img
... kernel stuck somewhere, it's doesn't even come to Zygote phase (lenovo animation). Is there any way to see kernel boot messages ?

Hi
I would also like to experiment with the Kernel, but I need to unlock the bootloader. unfortunately the thread is deleted files and I can not, can anyone help me even for private?
I have a 1380F in KitKat
Kind regards

airmalaga said:
Hi
I would also like to experiment with the Kernel, but I need to unlock the bootloader. unfortunately the thread is deleted files and I can not, can anyone help me even for private?
I have a 1380F in KitKat
Kind regards
Click to expand...
Click to collapse
I used this procedure: mobility.forumsee.com/a/m/s/p12-9574-0973888--yoga-tab-unlocking-daaa-deee-daaa-dooo.html
Patched ESP file I found on another forum: forum.android.com.pl/topic/259763-odblokowanie-bootloader%C3%B3w-yoga-tab-2/#entry4598175
For me it worked on Lolipop, but I as know bootloader changed arch x32->x64 during Lolipop->KK upgrade... I don't know if this esp will work on KK (at least do backup of ESP and boot partitions before).
---------- Post added at 12:07 PM ---------- Previous post was at 11:52 AM ----------
BTW: I was able finally to compile and startup my modified kernel using CM building engine from this thread .
I removed all wakelock code from bq27x00_battery_x8.c
For 1050L I merged: kernel from @Olivier repository + my patch on bq27x00_battery_x8.c + my initrd based on stock + stock Lolipop.
First tests seems to be very promising:
- finally NO battery_wakelock in Wakelock Detector
- LTE is working
- GPS is working
- Sound system is working
- No crashed till now
If anybody is interested i can attach img file.

Thx :good:
jasfasola said:
I used this procedure: mobility.forumsee.com/a/m/s/p12-9574-0973888--yoga-tab-unlocking-daaa-deee-daaa-dooo.html
Patched ESP file I found on another forum: forum.android.com.pl/topic/259763-odblokowanie-bootloader%C3%B3w-yoga-tab-2/#entry4598175
For me it worked on Lolipop, but I as know bootloader changed arch x32->x64 during Lolipop->KK upgrade... I don't know if this esp will work on KK (at least do backup of ESP and boot partitions before).
---------- Post added at 12:07 PM ---------- Previous post was at 11:52 AM ----------
BTW: I was able finally to compile and startup my modified kernel using CM building engine from this thread .
I removed all wakelock code from bq27x00_battery_x8.c
For 1050L I merged: kernel from @Olivier repository + my patch on bq27x00_battery_x8.c + my initrd based on stock + stock Lolipop.
First tests seems to be very promising:
- finally NO battery_wakelock in Wakelock Detector
- LTE is working
- GPS is working
- Sound system is working
- No crashed till now
If anybody is interested i can attach img file.
Click to expand...
Click to collapse

jasfasola said:
I removed all wakelock code from bq27x00_battery_x8.c
For 1050L I merged: kernel from @Olivier repository + my patch on bq27x00_battery_x8.c + my initrd based on stock + stock Lolipop.
Click to expand...
Click to collapse
Cool, could you push your patch to GitHub?
jasfasola said:
First tests seems to be very promising:
- finally NO battery_wakelock in Wakelock Detector
- LTE is working
- GPS is working
- Sound system is working
- No crashed till now
Click to expand...
Click to collapse
The kernel should be working, but the ALS is broken (seems to be a sensor from Avago) - you'll notice that if you use automatic brightness.

Olivier said:
The kernel should be working, but the ALS is broken (seems to be a sensor from Avago) - you'll notice that if you use automatic brightness.
Click to expand...
Click to collapse
Fixed. That was quite easy. Driver al3320 was in place. The problem was permissions set by script init.byt_t_ffrd8.rc in initrd. By default it's root/root, but it should be system/system. I already corrected paths and checked it - it's working. If you could give me permission to repo I can push the patch.
BTW: I see lot's of things are being hard-coded into initrd scripts. Since we changed config kernel, all those scripts must be checked. I can try to do it in free time...but some things are platform depended so, another original initrd from lolopop on 830f would be nice to compare...

jasfasola said:
so, another original initrd from lolopop on 830f would be nice to compare...
Click to expand...
Click to collapse
What do you need exactly? @jasfasola

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.