First of all I must say that I take no credit for this recovery whatsoever.
It is a modified TWRP v2.8.1.0 that is posted by @hoangnova over at lgviet.com - Link:http://lgviet.com/forum/threads/lg-g-pro-f240lsk-e988-e980-twrp-recovery-2-8-1-0.33587/
We are now in the early developmental stages of Android L and the last version of TWRP that I could locate here at XDA for the E980 was v2.6xx. I feel that we have a need for the latest version of this recovery now that we are transitioning over to Lollipop. With that said, the following is copied straight from his post over at that site.
TWRP Recovery SELinux support only for the rom install or extract img style set_metadata.
- Works well on all the GPRO and GK: E988, E980, and F220K F240LSK.
- Full SELinux support: That means you have can flash the rom CM 4.4, 5.0 or higher (set_metadata).
- USB-OTG Support
- Support for MTP - can copy the data directly to your phone when you are in Recovery
- Support screenshot of Recovery [hold Power + volume controls]
- Supports backup IMEI (EFS)
- Support Hard reset using hardware keys: Hold the Volume Down + Home and resources.
- Can operate on both 4.1.2 and 4.4.2 (even 5.0)
Installation: The first download listed is a flashable ZIP file that can be flashed through whatever recovery you have installed now. Not recommended if your are running a stock based ROM as it causes a "boot certification error" after flashing. Only use the flashable .zip file if you are already running a custom ROM based on CM source.
For those of you that are running a stock based ROM, please use Flashify to flash any of the three .IMG files that are listed below. Descriptions are in the download links.
Note: If you are running a custom ROM that is based on CM source, yet want to use one of the themed versions below, it is safe to use Flashify to install any of the recovery .IMG files below to your device.
All devs, please feel free to use this as a building block to obtain a reliable TWRP 2.8.1.0 recovery for our E980 device.
UPDATE 12/24/2014: Attachment downloads have been removed and all links are now directed to my 4Shared storage. The account has a 3GB per day / 30GB per month limit so I am hoping that it will be satisfactory for our download needs. If anyone would like to set up a mirror, please feel free to do so and PM me with links that I can add to this post.
UPDATE 12/24/2014 - Part 2: This version of TWRP for our G Pro devices now supports SD card in recovery mode!
Many thanks to @soralz , @culot and @hoangnova for delving into the code and providing us with this excellent recovery for our G Pro devices!
All of the above is assuming that your device has already been rooted and a custom recovery installed via the FreeGee method first. Do not flash anything posted in this thread before obtaining root and installing a custom recovery first!
Download Links:
TWRP 2.8.1.0 Unofficial - Flashable Zip -> DOWNLOAD
TWRP 2.8.1.0 Unofficial - .IMG File for Flashify - Stock TWRP Theme -> DOWNLOAD
TWRP 2.8.1.0 Unofficial - .IMG File for Flashify - Play Themed ->DOWNLOAD
TWRP 2.8.1.0 Unofficial - .IMG File for Flashify - Altered Splash Screen -> DOWNLOAD
@soralz Google Drive Mirror - All Versions, IMG and ZIP -> DOWNLOAD
Click to expand...
Click to collapse
Happy flashing but flash at your own risk. I assume no responsibility for any damages incurred by doing so. - HTR
Now, some legal mumbo jumbo:
This recovery is provided "AS IS" and without warranty or support of any kind and I expressly disclaim all other warranties, express or implied, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose. Under no circumstances shall I be liable for any incidental, special or consequential damages that result from the use of, or inability to use this recovery.
- Unless otherwise stated, the recovery image that is made available in the original post of this thread is distributed as "freeware". You may freely use and modify this recovery without restriction, whether it be for personal use or distribution to others.
Click to expand...
Click to collapse
hitekredneck said:
First of all I must say that I take no credit for this recovery whatsoever.
It is a modified TWRP v2.8.1.0 that is posted by @hoangnova over at lgviet.com - Link:http://lgviet.com/forum/threads/lg-g-pro-f240lsk-e988-e980-twrp-recovery-2-8-1-0.33587/
We are now in the early developmental stages of Android L and the last version of TWRP that I could locate here at XDA for the E980 was v2.6xx. I feel that we have a need for the latest version of this recovery now that we are transitioning over to Lollipop. With that said, the following is copied straight from his post over at that site.
TWRP Recovery SELinux support only for the rom install or extract img style set_metadata.
- Works well on all the GPRO and GK: E988, E980, and F220K F240LSK.
- Full SELinux support: That means you have can flash the rom CM 4.4, 5.0 or higher (set_metadata).
- USB-OTG Support
- Support for MTP - can copy the data directly to your phone when you are in Recovery
- Support screenshot of Recovery [hold Power + volume controls]
- Supports backup IMEI (EFS)
- Support Hard reset using hardware keys: Hold the Volume Down + Home and resources.
- Can operate on both 4.1.2 and 4.4.2 (even 5.0)
Installation: This is a flashable ZIP file that can be flashed through whatever recovery you have installed now.
Happy flashing - HTR
Click to expand...
Click to collapse
Awesome! Thanks!
Just wondering... I was using it for a while and does work great. Then, tried to get cyan delta up and running with it today. It seemed to give an error. I then tried it with philz and worked fine.
Is anyone using the two together and experiencing it, or just me?
@hoangnova - Can you shed some light as to why flashing BlissPop v1.1 with this recovery would fail?
By the way, thank you for a recovery that might possibly be modified to work with our device! It seems that it just needs a few bugs ironed out to be fully functional with the E980 for AT&T.
Thanks
hitekredneck said:
First of all I must say that I take no credit for this recovery whatsoever.
It is a modified TWRP v2.8.1.0 that is posted by @hoangnova over at lgviet.com - Link:http://lgviet.com/forum/threads/lg-g-pro-f240lsk-e988-e980-twrp-recovery-2-8-1-0.33587/
Great find cant wait to get into it and see what is possible.
One thing obviously loki support is set up with this recovery right?
Click to expand...
Click to collapse
Do you know if the source is over on git Im gonna look for it in a bit just wondering if anyone has found it?
Im hoping the sources are not so far off as I had came up with a fix for the 2.6.3.3 FreeGee TWRP as it had the same problem wondering if it will be a patch or full blown rewrite.....Anyways I am slow on dev work 3 kids wife and I am a newb but I am or will be working on it.
Fant0m3 said:
Do you know if the source is over on git Im gonna look for it in a bit just wondering if anyone has found it?
Im hoping the sources are not so far off as I had came up with a fix for the 2.6.3.3 FreeGee TWRP as it had the same problem wondering if it will be a patch or full blown rewrite.....Anyways I am slow on dev work 3 kids wife and I am a newb but I am or will be working on it.
Click to expand...
Click to collapse
@hoangnova may possibly be able to provide source. Not sure how often he checks in here though. I think that the more we could get working on this, the better our chances would be.
Yup agreed
I agree but I'm pretty slow at this developer stuff as I've taught myself everything and you know wife and kids and all that BS kind and limit my ability and availabilityI'll eventually find a solution it just may not be in a timely fashion
Modified TWRP 2.8.1.0 to E980
Hi guys, I am using the TWRP a while ago and realise this TWRP almost can't flash any ROM on it for ex. CM11 Nightlies. So I made some modifications to this recovery using simple Android Kitchen. By editing it's default.prop. This recovery is simply taken from f310lr (which preventing us from flashing other ROM because it's a LG GX!) more info.
Summary of changes can refer attachments below.
Working:
Everything, except can't mount External SD Card, now you can flash like a boss.
Download
Flashable zip, with the modified recovery and another one is simply the *.img file. Flash with Flashify or similar app.
Extra, TWRP Materialised theme.
It has been modded to fit my taste for welcoming Lollipop, if you want the TWRP theme simply place it to /sdcard/TWRP/theme/ui.zip.
Hopefully we can get the latest version of twrp going. From the change log it looks like the latest has fuller 5.0 features.
soralz said:
Hi guys, I am using the TWRP a while ago and realise this TWRP almost can't flash any ROM on it for ex. CM11 Nightlies. So I made some modifications to this recovery using simple Android Kitchen. By editing it's default.prop. This recovery is simply taken from f310lr (which preventing us from flashing other ROM because it's a LG GX!) more info.
Summary of changes can refer attachments below.
Working:
Everything, except can't mount External SD Card, now you can flash like a boss.
Download
Flashable zip, with the modified recovery and another one is simply the *.img file. Flash with Flashify or similar app.
Extra, TWRP Materialised theme.
It has been modded to fit my taste for welcoming Lollipop, if you want the TWRP theme simply place it to /sdcard/TWRP/theme/ui.zip.
Click to expand...
Click to collapse
Does it work on lollipop roms?
eocobby721 said:
Does it work on lollipop roms?
Click to expand...
Click to collapse
I suppose the pic can tell you.
@soralz. Thanks for sharing. My comment on latest version was not meant to follow what you shared it was just a comment in general.
The twrp looks great!
soralz said:
I suppose the pic can tell you.
Click to expand...
Click to collapse
Thanks. I asked because I flashed it once n couldn't flash any lollipop rom except da Chinese cm12 ROM. Once again thanks
Verified by yours truly. I flashed this recovery and used it to flash BlissPop v1.3 with no problems whatsoever. Now if only we can get someone that knows their beans to fix the problem with external SD not mounting.
I installed it on "LG optimus G" TWRP 2.6.3.3 from FreeGee of GooglePlay
Guys now I can install this TWRP 2.8.1.0. Recovery through. I repeat that I TWRP 2.6.3.3.
arek78 said:
I installed it on "LG optimus G" TWRP 2.6.3.3 from FreeGee of GooglePlay
Guys now I can install this TWRP 2.8.1.0. Recovery through. I repeat that I TWRP 2.6.3.3.
Click to expand...
Click to collapse
Optimus G, or Optimus G Pro? Which do you have? If it is a G Pro, yes you can flash this one using the twrp 2.6.3.3 that you installed with FreeGee.
arek78 said:
I installed it on "LG optimus G" TWRP 2.6.3.3 from FreeGee of GooglePlay
Guys now I can install this TWRP 2.8.1.0. Recovery through. I repeat that I TWRP 2.6.3.3.
Click to expand...
Click to collapse
*Only works on custom ROM, if you are on stock you will get boot verification error.
So I can not install on Stock 4.4.2.
hitekredneck said:
Verified by yours truly. I flashed this recovery and used it to flash BlissPop v1.3 with no problems whatsoever. Now if only we can get someone that knows their beans to fix the problem with external SD not mounting.
Click to expand...
Click to collapse
From a lengthy dissection of its innards, it looks like it was cobbled together mainly from parts of Nexus 5 and G2 recovery stuffs, and isn't even trying to load the external_sd. There also seems to be several other discrepancies, where its targeting a Nexus 5 or G2, when it should be targeting the almighty G Pro.
Take a look at the '/etc/twrp.fstab' -- it's missing '/external_sd vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1 flags=display="Micro SDcard";storage;wipeingui;removable', which I think may be a culprit in the lack of SD.
I've taken my undisciplined hand at fixing these issues, but I can never seem to repack the goddamn thing properly. I got sad skillz.
EDIT: I just noticed when you 'unpackbootimg' it provides all the info to repack properly. Friggin' duh, yo. Testing time! *crosses fingers and legs and black cats*
---------- Post added at 03:10 PM ---------- Previous post was at 03:07 PM ----------
hitekredneck said:
UPDATE #3 12/19/2014: I have been notified by soralz that when trying to flash the zip file version of this recovery when running a stock ROM, the flash will not process properly and will hand at "boot certification verification." Therefore I am providing a link to the recovery.img that can be installed using Flashify or similar utility.
Click to expand...
Click to collapse
Is it Lokification error/lack?
hitekredneck said:
Download recovery.img for Flashify here-> [URL="https://doc-0k-2g-docs.googleusercontent.com/docs/securesc @soralz
Click to expand...
Click to collapse
Your link doth stink. Exactly what is this 'recovery.img' you have there, where is it from.
culot said:
Take a look at the '/etc/twrp.fstab' -- it's missing '/external_sd vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1 flags=display="Micro SDcard";storage;wipeingui;removable', which I think may be a culprit in the lack of SD
Click to expand...
Click to collapse
Okay, got it:
- Open ADB shell while in OP's TWRP 2.8:
Code:
mount -t /system /dev/block/mmcblk0p23
mkdir /external_sd
echo "/dev/block/mmcblk1p1 /external_sd vfat rw" >> /etc/fstab
mount -t /dev/block/mmcblk1p1 /external_sd
Now the microSD is mounted at '/external_sd'. It does not show up on your computer when you enable MTP though; and next time recovery loads, those changes will be gone, so you have to do it all over again -- that is until someone bakes a fixed twrp.fstab into a recovery.img and/or flashable zip (my attempts so far go bootloops at the LG logo, every time).
---------- Post added at 06:31 PM ---------- Previous post was at 06:27 PM ----------
arek78 said:
So I can not install on Stock 4.4.2.
Click to expand...
Click to collapse
Have you tried using the Sphinx APK to install it? Just worked on my stock Kitkat 20g.
Fant0m3 said:
Do you know if the source is over on git Im gonna look for it in a bit just wondering if anyone has found it?
Im hoping the sources are not so far off as I had came up with a fix for the 2.6.3.3 FreeGee TWRP as it had the same problem wondering if it will be a patch or full blown rewrite.....Anyways I am slow on dev work 3 kids wife and I am a newb but I am or will be working on it.
Click to expand...
Click to collapse
This Omnirom TWRP Recovery and this guide should do fine. You'll have to tinker in the e980 stuff though. You can use the configuration files from OP's version to start with, and then make proper wtih e980 device specifics. This TWRP repo for a Japanese version of the phone holds some solid leads.
It compiled fine for me early this morning, but would not boot. But! After spending many hours since then learning how it really works, I'm certain when I take another crack at it tomorrow that it will be simple to get working. So close, yet so burned out for today.
Related
Main thread + features + install instructions + dev support
http://forum.xda-developers.com/showthread.php?t=2201860
PhilZ Touch is a CWM Advanced Edition that adds all the features you could ever miss in CWM
It is a well proven recovery for many phones
It also adds a full touch interface a completely configurable GUI
Please give your feedback, what works, and any bug you could encounter
Read the features, and check if you are missing something
Also, do not forget to read about the powerful aroma file manager integration and double tap shortcut
Download links
Last version can be found here:
Oppo Find7, Find7a
http://goo.im/devs/philz_touch/CWM_Advanced_Edition
Click to expand...
Click to collapse
XDA:DevDB Information
[find7][CWM Advanced Edition] PhilZ Touch, Tool/Utility for the Oppo Find 7
Contributors
Phil3759
Version Information
Status: Stable
Created 2014-06-27
Last Updated 2014-06-27
temporary download link:
http://d-h.st/users/philz_touch/?fld_id=37658#files
I installed via fastboot but I have a boot loop
QHD Find 7
Running good on my Find7a. Thanks!
@Phil3759
I installed this recovery and was working fine on my find7a. But when try to run the aroma installer I made it got stuck when launching the zip file.
All other custom recovery works fine with the aroma installer I made for find7a.
find 7 can use it?
kom1812 said:
find 7 can use it?
Click to expand...
Click to collapse
I'm gonna say no, not as it is. Unless it has been updated CWM wasn't working, though TWRP does run but at half the size of the screen...
ultramag69 said:
I'm gonna say no, not as it is. Unless it has been updated CWM wasn't working, though TWRP does run but at half the size of the screen...
Click to expand...
Click to collapse
Yeah i can confirm that it doesn't work on Find 7 (X9076)
I installed via fastboot method and booted in CWM with any issue, but next time I wanted to boot into CWM it booted to stock recovery :/ The same for Flashify app method. Any suggestions? I am rooted and with Find 7a, still on ColorOS.
Thanks
Phil3759,
Just installed version 6.48.4 for tests (I used TWRP 2.7.1.0 before) using Tantrums's Recovery flasher v2 (in which I renamed and inserted your new recovery replacinf the 6.42.2) because I simply like your recovery
That said, my first tests are not really good as backup is deadly slow and crashed before the end. For the record, TWRP backup is quite quick (it is having some bugs either such as a magnificent "0 MB has been saved") but it is working OK anyways and custom restore can be done using Titanium Backup.
I attached the recovery log file. As usual, feel free to let me know if I can provide more information.
Sadly I have to go back to TWRP 2.7.1.0 :crying:
The_Steph said:
Phil3759,
Just installed version 6.48.4 for tests (I used TWRP 2.7.1.0 before) using Tantrums's Recovery flasher v2 (in which I renamed and inserted your new recovery replacinf the 6.42.2) because I simply like your recovery
That said, my first tests are not really good as backup is deadly slow and crashed before the end. For the record, TWRP backup is quite quick (it is having some bugs either such as a magnificent "0 MB has been saved") but it is working OK anyways and custom restore can be done using Titanium Backup.
I attached the recovery log file. As usual, feel free to let me know if I can provide more information.
Sadly I have to go back to TWRP 2.7.1.0 :crying:
Click to expand...
Click to collapse
maybe try to set backup format to CWM, not TWRP mode
Also, are you sure you have enough space ?
Phil3759 said:
maybe try to set backup format to CWM, not TWRP mode
Also, are you sure you have enough space ?
Click to expand...
Click to collapse
Good news, CWM mode is working fine. Still really really slow but 100% functional.
Funny though, you have the same 0.00MB saved issue as TWRP (see attached logs).
I'll do further tests tomorrow.
Phil3759,
I finally found where my issues were coming from. I used Find7 recovery instead of Find7a one. I was simply attracted by higher build number
Fortunately, it did no brick my phone
The_Steph said:
Phil3759,
I finally found where my issues were coming from. I used Find7 recovery instead of Find7a one. I was simply attracted by higher build number
Fortunately, it did no brick my phone
Click to expand...
Click to collapse
will it work for x9076
rayQ111,
It is supposed to work with x9076 but I installed it on a x9006 hence my slowness issues.
Do we have to stay with 6.42.2 or can we update to 6.48.4 ? Or is it unnecessary ?
@Phil3759
i made backup on my oppo 7a and while trying to restore the backup now, it gave me all the time the error messgae "No files found"
How can i solve this issue?
Even tried to copy the backup to internal memory but same issue....backup isn't possible
edit: solved is working!
Does aromafm.zip load correctly?
Phil3759,
i find this file OPPO-Find7-philz_touch_6.57.9_cwm6.0.5.1-cn-0920.zip on chinese site. can you tel me if this recovery works on my oppo find 7 x9076 ?
i don't understand if this recovery woks on find7 and/or find 7a
thanks very much
achimaki said:
Phil3759,
i find this file OPPO-Find7-philz_touch_6.57.9_cwm6.0.5.1-cn-0920.zip on chinese site. can you tel me if this recovery works on my oppo find 7 x9076 ?
i don't understand if this recovery woks on find7 and/or find 7a
thanks very much
Click to expand...
Click to collapse
Try it to know it
Sent from my Find7 using XDA Free mobile app
Made this from the new 80220f open EUR kdz.
This is the complete LG KK 20f ROM - nothing missing or messed with.
You can flash SuperSU and get root if you wish - your choice.
I provide this assuming you have an understanding of the terminology used below and appreciate that any flashing activity has some risk.
I strongly advise against using any form of restore from previous backups, such as TB or Nandroid.
Once the process is complete, custom recovery will be lost.
Method:
Download both the ROM zip file linked below and SuperSU zip file (if you want root) and copy to your SD card.
You need to be already on Rooted JB, Rooted KK or PURE CM11 with either TWRP 2.6.3.3 or 2.6.3.4 or TWRP 2.7.0.0 (nothing else).
Reboot to TWRP recovery
Wipe: System, Data, Cache. Dalvik (nothing else)
Flash the ROM zip - ignore any "FAIL" warnings.
Wipe Cache and Dalvik (nothing else)
Go to the Mount page in TWRP and select System (leave the other defaults alone)
Flash the SuperSU zip - ignore any "FAIL" warnings
Reboot
Done
Don't use AutoRec to flash TWRP - you will lose Knock code.
Alternatively - if you have flashed TWRP on another KK Stock ROM (using AutoRec), you can full wipe (not SDCard) and flash this directly without going back to JB.
Download from here:
https://drive.google.com/file/d/0B_ESvfVtZzEwaWRaTjRNUEdDOEE/edit?usp=sharing
Credit to Chainfire for the rooting method.
good job. but you don't put the download ?
paglop said:
good job. but you don't put the download ?
Click to expand...
Click to collapse
Link is there....!
why use AutoRec ? the recovery is lost ?
how do i acquire custom recovery once i flash 20f? flashify app?
zekurosu said:
how do i acquire custom recovery once i flash 20f? flashify app?
Click to expand...
Click to collapse
if we just edit the updater script and remove the recovery partition , our recovery wont be wiped just note that you should never take any OTA while u have custom recovery.
paglop said:
why use AutoRec ? the recovery is lost ?
Click to expand...
Click to collapse
Yes,you will lose your custom recovery if you install this stock rom. But don't care about it.You may use AutoRec and your recovery will be back :good:
Edit : Hmm i think knock code will unusable if we flash TWRP with AutoRec.
Edit 2 : Aarghh i misunderstood. After using AutoRec and we will install any kernel with knock code support.
Flashing this rom is basically just a means of going back to stock. Of course you can use autorec to recovery and then flash a custom kernel to get knock code back, its up to you what you want out of this.
Art Vanderlay said:
Flashing this rom is basically just a means of going back to stock. Of course you can use autorec to recovery and then flash a custom kernel to get knock code back, its up to you what you want out of this. If you want to have a pure stock ROM, kernel and all, its easiest to use the alternative method to keep your recovery (at the bottom of the op)
Click to expand...
Click to collapse
If i'm not wrong,the alternative method is not addicted to keep custom recovery. The custom recovery (whatever you have) won't be there after flashing this rom all the way mate.:good:
Art Vanderlay said:
Flashing this rom is basically just a means of going back to stock. Of course you can use autorec to recovery and then flash a custom kernel to get knock code back, its up to you what you want out of this.
Click to expand...
Click to collapse
Precisely!
If someone already has Custom Recovery, and isn't overly bothered about preserving it, then this is potentially quicker and easier that then kdz method. And with easy root. Big plus point.
If you want a completely Stock experience of course.
What we don't know is how much development LG have done with the kernel. So, if one uses Autorec, any benefits of a later LG stock kernel will be lost.
Enjoy!
I am on v20d stock kit kat rooted with ioroot. D802 model. Does this flashabel rom include bootloader? Cause to have a custom recovery, I will have to use autorec app, which will dowgrade my bootloader. So will this rom work if the recovery has been flashed with autorec?
And also flashing this rom means that stock recovery will be flashed too?
I installed this 20f. it corrects problems ratio with slimport on small screen.
Just updated to D80220F. I can confirm that there is a Google Folder pre created. Havent noticed much else yet. will keep you updated.
Whole system feels super fast. Is it just me or is this faster than 802D/802B?
Knock on seems more reliable. Senses it way better and ignores ghost touches better.. Auto brightness seems to be managing brightness better too.
i have twrp 2.7.0.0 custom recovery, and i'm on d802b firmware (kk stock) with dorimanx kernel...
just 1 question to be sure (because i didn't quite get the OP):
- will i lose twrp if i flash this zip? (if yes, how do i get custom recovery back and safely?)
thanks in advance
Not option for ART
---------- Post added at 09:28 PM ---------- Previous post was at 09:24 PM ----------
60nine yes you lose twrp. It is for return to official.
ok, thanks... and how do i get twrp back? is it even possible?
on that matter - can "recovery.bin" from this zip be replaced by custom recovery .bin file?
shriom_manerker said:
if we just edit the updater script and remove the recovery partition , our recovery wont be wiped just note that you should never take any OTA while u have custom recovery.
Click to expand...
Click to collapse
Can you make a tutorial or write it down how you did it??? Because I wan't stock rom but don't want to lose recovery....
First root, and autorec for instal recovery. But you need a custom kernel .
---------- Post added at 09:58 PM ---------- Previous post was at 09:54 PM ----------
read a little before
ok, so autorec works for 20f... all i wanted to know... (i don't care for knock code, i just want knock on to work)
the OP was a bit confusing - maybe it needs to be updated with a basic FAQ...
if anyone tried to flash this, then used autorec for custom recovery and flashed latest dorimanx 5.7 kernel - please confirm if knock on works (not knock code)
thanks in advance
Not kernel just autorec
[Q&A] [TOOL/UTILITY][TWRP][ 2.8][RECOVERY] TWRP 2.8.1.0 TeamWin Recovery Project 10/
Q&A for [TOOL/UTILITY][TWRP][ 2.8][RECOVERY] TWRP 2.8.1.0 TeamWin Recovery Project 10/23
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [TOOL/UTILITY][TWRP][ 2.8][RECOVERY] TWRP 2.8.1.0 TeamWin Recovery Project 10/23. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
TWRP v2.8.0.0 for P605
Hi! - I also have the "TWRP v2.8.0.0 (external-) backup files not found on SD card"-problem! ... Only internal backup works (to: data\media\0\TWRP)! - If backing up to either external_sd (extSdCard) or USB storage, TWRP first seems to do the job (works, and works ...), but after reboot, no files are stored under: storage\extSdCard\TWRP or under data\media\0\TWRP, or on an attached USB stick/card-reader! ... Only backup to "internal storage" works (correctly?) - and everybody needs root-access for to move the backup to an external medium, especially, if the small 16GB internal memory is full!
I now have bought a Galaxy Note 4, the last week, have rooted it and have installed TWRP v2.8.1.0 on it. - There everything works perfectly! ... Why not on Note 10.1 2014? ... I still wait for the v2.8.1.0 update of TWRP for the P605 device. Will it change that issue?
cstratz said:
Hi! - I also have the "TWRP v2.8.0.0 (external-) backup files not found on SD card"-problem! ... Only internal backup works (to: data\media\0\TWRP)! - If backing up to either external_sd (extSdCard) or USB storage, TWRP first seems to do the job (works, and works ...), but after reboot, no files are stored under: storage\extSdCard\TWRP or under data\media\0\TWRP, or on an attached USB stick/card-reader! ... Only backup to "internal storage" works (correctly?) - and everybody needs root-access for to move the backup to an external medium, especially, if the small 16GB internal memory is full!
I now have bought a Galaxy Note 4, the last week, have rooted it and have installed TWRP v2.8.1.0 on it. - There everything works perfectly! ... Why not on Note 10.1 2014? ... I still wait for the v2.8.1.0 update of TWRP for the P605 device. Will it change that issue?
Click to expand...
Click to collapse
Do you have lt03wifiue?
No, I don't have the Wifi only version. The P605 is with LTE and Qualcom. - Are you sure, that I also can use the v2.8.1.0 of TWRP for the P600 (Wifi only tablet)?
Gesendet von meinem SM-N910F
cstratz said:
No, I don't have the Wifi only version. The P605 is with LTE and Qualcom. - Are you sure, that I also can use the v2.8.1.0 of TWRP for the P600 (Wifi only tablet)?
Gesendet von meinem SM-N910F
Click to expand...
Click to collapse
Please try one of the following depending on your bootloader:
http://techerrata.com/bigbiff/openrecovery-twrp-2.8.1.1-lt03ltexx-4.3.zip
http://techerrata.com/bigbiff/openrecovery-twrp-2.8.1.1-lt03ltexx-4.4.zip
Hi!... v2.8.1.1 /4.4 works perfectly! Thank you very much for your support!... Many people are using either the P600 or the P605 - and I believe, that the official support (also regarding tools to root them, or CyanogenMod) for these tablets is unfortunately a bit slow in contrast to Samsung phones... But somehow, with a bit luck, everything is to find somewhere... I like you!... Carsten
Gesendet von meinem SM-P605
Hello all I have rooted my note10.1 NI1 and I cannot flash any recoveries without boot looping has anyone tested this on on 10.1 WiFi. Version
Could someone please tell me where I can find themes for 2.8.x ?
Thank you!
Hi,
TWRP manager crashes when I try to install TWRP. I select the device as lt03wifiue and select openrecovery-twrp-2.8.1.0-lt03wifiue.img. Then, when I hit install recovery, it downloads and then asks me to verify the partition as /dev/block/mmcblk0p10. When I click yes, it starts and then crashes. I tried multiple twrp versions, but they all crash.
EDIT: I ended up doing it through odin.
maelopam said:
Hi,
TWRP manager crashes when I try to install TWRP. I select the device as lt03wifiue and select openrecovery-twrp-2.8.1.0-lt03wifiue.img. Then, when I hit install recovery, it downloads and then asks me to verify the partition as /dev/block/mmcblk0p10. When I click yes, it starts and then crashes. I tried multiple twrp versions, but they all crash.
EDIT: I ended up doing it through odin.
Click to expand...
Click to collapse
Sorry, it's been doing that for a while. We don't maintain the app, and you should report it to the developer.
I want to download 2.8.5 for p601 but on the twrp website, the latest version is 2.8.0 How can i get 2.8.5?
Can someone give me a link to Download TWRP For Galaxy note 10.1 P601 ?
Except This one which is Corrupt !
techerrata . c o m
S1avash said:
Can someone give me a link to Download TWRP For Galaxy note 10.1 P601 ?
Except This one which is Corrupt !
techerrata . c o m
Click to expand...
Click to collapse
http://dl.twrp.me/lt03wifiue/
I'm trying to install the xposed zip that's been released for the Samsung devices but due to the unsigned zip I need something other than stock recovery. I've been able to sign the zip but when I try to install I receive a bad header (or very similar) message. Obviously I'd like to try and keep the device as close to stock regarding kernal and recovery as possible, but to gain other features the custom recovery is the way to go.
I've decided on using TWRP but can't find a compatible build.
Where would I ask to see if a build for this version can be had and what would I need to provide to facilitate the build. I own a Samsung SM-P607T (lt03ltetmo), Galaxy Note 10.1 (2014 version).
It appears that I've been able to get a good backup of the stock kernal and recovery including what appears to be a valid backup of all the blocks for the device.
I've used Chainfires adb insecure to try and install the zip file, but that turns USB debugging off and I haven't found a work around or fix for that yet.
Thanks for your help.
mlutzow said:
I'm trying to install the xposed zip that's been released for the Samsung devices but due to the unsigned zip I need something other than stock recovery. I've been able to sign the zip but when I try to install I receive a bad header (or very similar) message. Obviously I'd like to try and keep the device as close to stock regarding kernal and recovery as possible, but to gain other features the custom recovery is the way to go.
I've decided on using TWRP but can't find a compatible build.
Where would I ask to see if a build for this version can be had and what would I need to provide to facilitate the build. I own a Samsung SM-P607T (lt03ltetmo), Galaxy Note 10.1 (2014 version).
It appears that I've been able to get a good backup of the stock kernal and recovery including what appears to be a valid backup of all the blocks for the device.
I've used Chainfires adb insecure to try and install the zip file, but that turns USB debugging off and I haven't found a work around or fix for that yet.
Thanks for your help.
Click to expand...
Click to collapse
Have you tried lt03lte version of TWRP yet?
bigbiff said:
Have you tried lt03lte version of TWRP yet?
Click to expand...
Click to collapse
bigbiff, no I haven't, probably being overly cautious on my part.
Would you mind if we took this offline and I ask some questions that I think you can answer for me, rellated.to trying to keep as close to stock as possible while using certain toolsets to enhance the tablet experience.
I think I'll try that version later today, when I have some time...I hadn't noticed it when I was searching for a compatible version.
bigbiff said:
Have you tried lt03lte version of TWRP yet?
Click to expand...
Click to collapse
I need to correct myself, I did see that update. I'm on 5.1.1 and the latest version I've seen is 4.6 and I don't know what I'll break, if anything, or if I currently have the knowledge to roll back to functioning stock recovery if needed. Granted I have backups of the kernal and recovery (from two different sources), first 100 meg blocks...all the device blocks and partitions. It's been about 8 years since I was able to setiously pursue testing and many things have changed on me.
mlutzow said:
bigbiff, no I haven't, probably being overly cautious on my part.
Would you mind if we took this offline and I ask some questions that I think you can answer for me, rellated.to trying to keep as close to stock as possible while using certain toolsets to enhance the tablet experience.
I think I'll try that version later today, when I have some time...I hadn't noticed it when I was searching for a compatible version.
Click to expand...
Click to collapse
mlutzow said:
I need to correct myself, I did see that update. I'm on 5.1.1 and the latest version I've seen is 4.6 and I don't know what I'll break, if anything, or if I currently have the knowledge to roll back to functioning stock recovery if needed. Granted I have backups of the kernal and recovery (from two different sources), first 100 meg blocks...all the device blocks and partitions. It's been about 8 years since I was able to setiously pursue testing and many things have changed on me.
Click to expand...
Click to collapse
Please ask questions here for others benefit.
I am not sure what you are referring to with version 4.6. All you usually need is your stock odin firmware tar to return to stock using Odin.
bigbiff said:
Please ask questions here for others benefit.
I am not sure what you are referring to with version 4.6. All you usually need is your stock odin firmware tar to return to stock using Odin.
Click to expand...
Click to collapse
First, bigbiff I really appreciate your patience with me and taking the time to answer my questions and help me through this process.
I thought the 4.6 was the Android version the recovery was built for and I'm on 5.1.1 and thought I would run into issues considering what I'm reading about this 5.1.1 and the changes that have been incorporated.
My goal in this is to get xposed installed, functioning, and upgradeable if and when the opportunities present themselves, while remaining as close to stock as possible and not tripping that switch (whatever it's named) which for me is still 0x0 although the device status reads custom (fairly easily resolved with a full wipe and factory install is my understanding) .
Currently I'm rooted with Chainfires cf-auto-root for lt03ltetmo. Evrything still works, S-Pen, wireless, etc., etc., etc.
Clearly I need to install a custom recovery. In my reading I came across this thread: http://forum.xda-developers.com/gal...root-tmobile-sm-p607t-5-1-1-firmware-t3215541 and a modded kernal from this thread: http://forum.xda-developers.com/galaxy-note-10-2014/general/root-root-stock-kernel-t3240218. With my current root status and SuperSu installation I'm thinking I need to clean up and uninstall SuperSU and then proceed with the above recommendations.
That is unless just installing the TWRP you mentioned will get me to a stable position.
I'm just looking for the best method to use to get the xposed installed that leaves me with the fewest or no issues as far as using the tablet.
Any recommendations are greatly appreciated.
Hello, I have a Galaxy Note 10.1 2014 Edition. SM-P600. Running Stock 5.1.1 and Rooted.
I am looking for correct TWRP .tar file to flash with ODIN. Thanks.
Q&A for [Recovery][FOTA]CWM and TWRP recoveries for custom ROMs
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [Recovery][FOTA]CWM and TWRP recoveries for custom ROMs. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
cucumber09 said:
Tired waiting for someone to repack kernel with your favorite version of recovery? Or tired to run recovery script every time you update your ROM or kernel? Now you don't need any repacked kernels or recovery-scripts. Use your FOTAKernel as recovery partition!
It works on any kernel with extract_elf_ramdisk utility (it's built in mostly all kernels for custom ROMs, but I am not sure) by @Dees_Troy. And don't forget, that you are doing on your own risk, I am not responsible for bricked devices, acid rains or thermonuclear war.
Installation:
Download zip and flash it via your current recovery. If your current recovery is unusable, you can flash it via terminal emulator:
- Extract FOTAKernel.img and place it to the root of your external SD-card
- Type su and grant root access
- Type
Code:
dd if=/ext_card/FOTAKernel.img of=/dev/block/mmcblk0p23
- Reboot to recovery to test if it works (if not, try again and check if you are doing it correctly).
Download:
TWRP 2.8.4.0 (thanks to @Rohan purohit for compiling it for Xperia L, I just ported and modded it)
TWRP 2.8.0.0/CWM (or scroll down, it's right below this post)
You can restore original FOTAKernel image by following instructions in this post (or just scroll down, it is 3rd post, lol).
Some info:
Sony Xperia devices don't have recovery partition. Instead of this in custom kernels is used recovery-in-boot conception with two-stage boot (ramdisk-recovery is packed inside main ramdisk). And there is partition called FOTAKernel that is used for installing official FOTA (firmware-over-the-air) updates. After unlocking your bootloader it partition becomes redundant, because you cannot use OTA function anymore. So it may be used for storing recovery ramdisk. And this very useful future was implemented by recognized developer @Dees_Troy (lead TWRP developer), he developed utility extract_elf_ramdisk (it is merged to almost all kernels for Sony devices), it extracts recovery ramdisk from FOTA partition instead of using regular one from boot image. So even after updating or changing your kernel or ROM you don't lose your current recovery! Here is some info from Dees_Troy.
BTW, I don't own any of this work, I just adapted recovery images for using them from FOTA partition. And recoveries are not compiled by me.
Click to expand...
Click to collapse
Hey, i use your recovery but when i write reboot recovery in terminal, my phone boots normally. But i can acess it by volume up button. How can i fix it?
Vp10 said:
Hey, i use your recovery but when i write reboot recovery in terminal, my phone boots normally. But i can acess it by volume up button. How can i fix it?
Click to expand...
Click to collapse
It is CM bug, it will be fixed in next nightlies.
Hi bro, i see new twrp update in xperia l thread ..
I hope you to update them ..
Thangs
cucumber09 said:
It is CM bug, it will be fixed in next nightlies.
Click to expand...
Click to collapse
And how we can flash new nightlies without recovery?
Hi, can I install twrp 2.8.4.0 from my FOTA recovery 2.4.0.0?
digt said:
Hi, can I install twrp 2.8.4.0 from my FOTA recovery 2.4.0.0?
Click to expand...
Click to collapse
[emoji782]
AggelosGR said:
And how we can flash new nightlies without recovery?
Click to expand...
Click to collapse
Recovery is accessible, just press many times vol rocker 'till you will enter the recovery.
---------- Post added at 20:59 ---------- Previous post was at 20:55 ----------
2ALL
I'm reading Q&A section not often, better write to main thread or tag me (if you are not quoting me), so I will see the notification.
How to solve image unstability in FOTA TWRP?
Hello @cucumber09. I've been trying your FOTA recovery, which I consider a great solution for our device, but I'm facing image unstability while in recovery: the screen flips and flicks horizontally making it very hard to tap correctly any option, and could lead to fatal errors. Could you please tell me a solution? I've tried flashing several kernels/traditional recoveries, but when I make it work satable in recovery, then the OS does'nt boot (bootloop). I'm using stock 4.3 15.4.A.1.9 ROM, unlocked bootloader, rooted, with Xposed Framework and Gravitybox module.
Also I've tried many KK and LP ROMs but I always return to stock 'cause I can't stand glitches and gaps while listening to my favourite tunes.
Thanks in advance,
e-bert.
e-bert said:
Hello @cucumber09. I've been trying your FOTA recovery, which I consider a great solution for our device, but I'm facing image unstability while in recovery: the screen flips and flicks horizontally making it very hard to tap correctly any option, and could lead to fatal errors. Could you please tell me a solution? I've tried flashing several kernels/traditional recoveries, but when I make it work satable in recovery, then the OS does'nt boot (bootloop). I'm using stock 4.3 15.4.A.1.9 ROM, unlocked bootloader, rooted, with Xposed Framework and Gravitybox module.
Also I've tried many KK and LP ROMs but I always return to stock 'cause I can't stand glitches and gaps while listening to my favourite tunes.
Thanks in advance,
e-bert.
Click to expand...
Click to collapse
Your problem is using the stock sony rom, it doesn't support FOTA recoveries properly, as soon as you switch to any other rom the FOTA recovery will work.
Thanks & new question.
Remorcer said:
Your problem is using the stock sony rom, it doesn't support FOTA recoveries properly, as soon as you switch to any other rom the FOTA recovery will work.
Click to expand...
Click to collapse
OK. Thank you for your quick response. Now, could you suggest to me any custom ROM that has no glitches or gaps in music playing? In yor opinion, which is the best ROM you've tried for our device (Xperia M SS c1904)?
Thanks again.
e-bert said:
OK. Thank you for your quick response. Now, could you suggest to me any custom ROM that has no glitches or gaps in music playing? In yor opinion, which is the best ROM you've tried for our device (Xperia M SS c1904).
Thanks again.
Click to expand...
Click to collapse
Everyone has its own taste in roms, I like stable and clean roms and would suggest cm11 or PA, try some of the roms and I'm sure you'll find your favourite.
Bliss pop is good.try it ,the battery is good.smooth performance and id say not much sound glitch .
Sent from my nicki using XDA Premium 4 mobile app
All hail to all cucumber..
its so frustrated to install kernel only for recovery..
and its more frustrating when your phone not responsive because incompatible kernel.
i recommended to install this trough recovery..
more reliable and low risk..
if you cant install from recovery (signature verification failed), first install another kernel to get unsigned recovery (niu kernel example)..
its a long way, but i'm prefer this than risking my phone because wrong command..
tested in resurrection remix rom 5.1..
Installed fota twrp with terminal, it freezes
So I did just as it was written. Installed it with command thru terminal on a CM 12 rom on Xperia z2.
It did work, for approx 10 seconds. I reboot in recovery, got first the screen for
CM recovery, before it changed to twrp. When I got there, I couldn't press anything
And suddenly it reboot into normal again. Dunno what it can be?!
Stuck on cyanogenmod boot
Flashed it and now i'm stuck on the cyanogenmod boot screen
is TWRP better or CWM...?
i flashed the twrp version 2.8.3.0 stuck on boot animation and when flashed 2.8.5.0 loop of recovery...m on xenon hd 5.1.1 rom...can anyone help???/ i want to flash twrp recovery
Neemac said:
So I did just as it was written. Installed it with command thru terminal on a CM 12 rom on Xperia z2.
It did work, for approx 10 seconds. I reboot in recovery, got first the screen for
CM recovery, before it changed to twrp. When I got there, I couldn't press anything
And suddenly it reboot into normal again. Dunno what it can be?!
Click to expand...
Click to collapse
It is for Xperia M, not Z2. So it won't work on it.
@Neemac i think z2 have official fota twrp, so why you not use them?
Sent from my C1905 using Tapatalk
Team Win Recovery Project 3.0.2-0
WHAT IS TWRP?
Oh come on, you know what it is - don't try to fool me!
In case you're serious, though...
Team Win Recovery Project is a custom recovery for Android devices.
It allows you to back up and restore your data, flash custom ROMs to your device, repair broken file systems, and root your device.
DOWNLOAD
You can find the device page here:
http://teamw.in/devices/samsunggalaxys4active.html
There is a download link there, as well as instructions on how to flash it.
I highly recommend using Odin to flash when possible.
You can find a zip containing Odin as well as a link to Samsung's Mobile drivers page here:
https://idlekernel.com/flash-tools/
CHANGES
v3.0.2-0 - See here for changes!
v3.0.1-0 - See here for changes!
v3.0.0-1 - Initialize new device tree based on CM-13.0 kernel.
FEATURES
MTP support
USB Mass Storage support
Micro SDcard and USB OTG storage support
f2fs file system support (read, write, format, backup & restore)
exFAT file system support (read, write, format, backup & restore)
NTFS file system support (read, write, format)
Backup & restore of modem/baseband/firmware (not bootloader!)
ADB root
Full SELinux support
Built in android 6.0 tree
KNOWN ISSUES
Samsung encryption is not supported
CONTACT & SUPPORT
You can find us on IRC at #twrp on chat.freenode.net.
You can also post in this thread and I will attempt to answer any questions you may have.
SOURCE CODE
TWRP: https://github.com/omnirom/android_bootable_recovery (android-6.0)
Device tree: https://github.com/TeamWin/android_device_samsung_jactivelte (android-6.0)
Kernel: https://github.com/jcadduono/nethunter_kernel_jactivelte (cm-13.0)
CONTRIBUTIONS
Gerrit for TWRP: http://gerrit.omnirom.org/
Gerrit for officially supported devices: http://gerrit.twrp.me/
Nice bro!
Sent from my GT-I9295 using Tapatalk
Good Job! Please update the recovery to have multirom support. Thank you!
kingsven149 said:
Good Job! Please update the recovery to have multirom support. Thank you!
Click to expand...
Click to collapse
You probably want to talk to @spegelius about that.
Devo7v said:
You probably want to talk to @spegelius about that.
Click to expand...
Click to collapse
Yes I write to him
Hi! What an excellent work bro! But can You add please the 'Preload' partition to the format menu? I really want to format this partition because there are a lot of unuseful apks and stuffs.
Hi.
I have problems in restoring my backuped device to another one (both [email protected]).
What I did:
* I used TWRP in recovery mode and backuped whole device (boot, data, efs, etc.) on source device to ext-sd
* I changed name of backup directory from source device (serial number) to correct name of target device
* I used TWRP in recovery mode on target device and restored many combinations of data, boot, system, modem
The results are always the same:
The target device stucks in booting cm (cm-face).
What must I do?
Is here a problem of TWRP or CM or of me? I hope the latter.
Edit:
Solution!
It was my mistake. Now it worked. Yet I took system, data, cache - nothing more.
This really is very nice.
Truly the cat's pajamas.
Can you guys try out https://idlekernel.com/twrp/jactivelte/twrp-3.0.2-1-b1-jactivelte.tar.md5
Trying to fix fail to boot on some newer bootloaders, it's rebased on latest CM13 kernel sources and encryption support is enabled but I have no idea if it works.
jcadduono said:
Can you guys try out https://idlekernel.com/twrp/jactivelte/twrp-3.0.2-1-b1-jactivelte.tar.md5
Trying to fix fail to boot on some newer bootloaders, it's rebased on latest CM13 kernel sources and encryption support is enabled but I have no idea if it works.
Click to expand...
Click to collapse
I will try it soon, when I am at home
Hello, Please I want to ask if i need to unlock my bootloader before flashing the recovery or roms on this i537 running android 4.3
---------- Post added at 08:48 AM ---------- Previous post was at 08:09 AM ----------
Hello, Please I want to ask if i need to unlock my bootloader before flashing the recovery or roms on this i537 running android 4.3
dedon4christ5 said:
Hello, Please I want to ask if i need to unlock my bootloader before flashing the recovery or roms on this i537 running android 4.3
---------- Post added at 08:48 AM ---------- Previous post was at 08:09 AM ----------
Hello, Please I want to ask if i need to unlock my bootloader before flashing the recovery or roms on this i537 running android 4.3
Click to expand...
Click to collapse
This recovery is for i9295 !!!!!! do not flash it on your ATT S4 active
dedon4christ5 said:
Hello, Please I want to ask if i need to unlock my bootloader before flashing the recovery or roms on this i537 running android 4.3
---------- Post added at 08:48 AM ---------- Previous post was at 08:09 AM ----------
Hello, Please I want to ask if i need to unlock my bootloader before flashing the recovery or roms on this i537 running android 4.3
Click to expand...
Click to collapse
You have a locked bootloader, you cannot flash a custom recovery or custom kernel.
Devo7v said:
You have a locked bootloader, you cannot flash a custom recovery or custom kernel.
Click to expand...
Click to collapse
Okay, thanks a lot
irc how to?
jcadduono said:
You can find us on IRC at #twrp on chat.freenode.net.
Click to expand...
Click to collapse
Something's weird with the IRC registration there.
EDIT: Now it worked. The secret was closing the webpage https://webchat.freenode.net/?channels=twrp , and reopening it, suddenly then it worked.
Thanks .-)
Why in the latest official recovery 3.0.2.0 my phone getting so terribly HOT?
I usually used unofficial 2.8.3.0 MultiroomTWRP - when i boot in it, my device is cold (untill i start flashing something), however in the official recovery - the phone is booting with the high temperature of 45-48 degree, then it rise his temperature to 49-50 degree and stopps at that value. I do nothing to rise the temperature: it boots into recovery and lies on the table, that's all what i do, and the phone is warming up himself. Is it normal?
PS: sry for my bag english, i almostly forget it.
anyone can you help me
i have s4 active sgh-i537, rom lollipop (I537UCUCOC6) and rooted (with kingroot and succes)
and now my problem is how to install TWRP/CWM ?
i try flash TWRP and CWM all version via ODIN failed, i try flash .img file via apps TWRP Official/Rashr/Flashify and failed again. TWRP doesnt installed
please someone help me
sorry for bad english...
Siwot Nyubi said:
anyone can you help me
i have s4 active sgh-i537, rom lollipop (I537UCUCOC6) and rooted (with kingroot and succes)
and now my problem is how to install TWRP/CWM ?
i try flash TWRP and CWM all version via ODIN failed, i try flash .img file via apps TWRP Official/Rashr/Flashify and failed again. TWRP doesnt installed
please someone help me
sorry for bad english...
Click to expand...
Click to collapse
You have to check, read more details in forum, but if I'm not wrong your i537 have locked bootloader and this let things more difficult.
The instructions here usually are for i9295, that we can flash without problems.
Read all S4 ACTIVE sections, all threads for the last 2 years, maybe you can find specific instructions to your i537.
Just a note: always prefer other alternatives to kingroot, it is known to spy mobiles.
Siwot Nyubi said:
anyone can you help me
i have s4 active sgh-i537, rom lollipop (I537UCUCOC6) and rooted (with kingroot and succes)
and now my problem is how to install TWRP/CWM ?
i try flash TWRP and CWM all version via ODIN failed, i try flash .img file via apps TWRP Official/Rashr/Flashify and failed again. TWRP doesnt installed
please someone help me
sorry for bad english...
Click to expand...
Click to collapse
You have a locked bootloader, it is not possible to flash a custom recovery on the i537. If you want to be able to use the ROMs in the development section sell your i537 and buy an i9295.
Hi jcadduono!
Would you mind updating the recovery to the latest 3.1.0.0 version?