yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 i9505 Original Android Development] Emphyr:
I guess I qualify as a "normal user" compared to you guys :) A couple of noob questions if I may; What do you mean by F2FS Support? It seems redundant since TWRP also can convert to F2FS...or does it mean something else? And I am pretty sure a flashed zips too :confused:

Keep up the good work! My S4 have never been faster tnx to Optimized CyanogenMod 12.1 builds
[Galaxy S 4 i9505 Original Android Development] stratoll:
well after flashing recovery from twrp manager on my i337 MDL resulting in "custom" and padlock on screen i had to unroot and then reroot because I did not know of a better method to get rid of the tripped counter. But I can confirm that the flashable zip works.

You have my thanks (Y)
[Galaxy S 4 i9505 Original Android Development] Rhoban:
Original TWRP doesn't have flashable recovery zips, they only provide tar and img files.

Don't know about the F2FS part.
[Galaxy S 4 i9505 Original Android Development] Emphyr:
Oh ok, tnx for the clarification :)
[Galaxy S 4 i9505 Original Android Development] Undefined Origin:
A little help please

I'm coming from 2.8.7.0-F2FS and flashed the new 3.0-F2FS via recovery. Flash said sucessful, but when I try reboot into recovery I get stuck at the blue "recovery booting" screen. I can use TWRP Manager to flash back to standard 2.8.7.0, but trying 3.0-F2FS gets me into the same loop. Trying 3.0 from TWRPManager gets the yellow triangle

Any suggestions (preferably phone only, no USB link)
[Galaxy S 4 i9505 Original Android Development] bladez:
Is there a way now how to mount the SD card to PC with the new TWRP? In the 2.7 one I could go to Mount>Mount SD card and the SD card would show up as a removable drive on my Windows machine, but now I only find MTP available, which is very wonky and fails file copies a lot of times for me.
[Galaxy S 4 i9505 Original Android Development] side:
works on me :/

i just reboot to recovery and plug in the USB
[Galaxy S 4 i9505 Original Android Development] bladez:
Yeah, but that's just MTP mounting, not USB Mass Storage (UMS/MSC) mounting type. TWRP used to offer USB Mass Storage mounting option apart from the default MTP mounting, but I can't find that option anymore. I need the PC to access the raw file system of my SD card and not just the way it's accessed using Media Transfer Protocol.
[Galaxy S 4 i9505 Original Android Development] nunein:
I'm missing 'Mount USB Storage' as well. So I went back to version 2.8.7.0 :(
[Galaxy S 4 i9505 Original Android Development] finallau:
will there be any difference like bugs using ext4 and etc rather than F2FS?
[Galaxy S 4 i9505 Original Android Development] side:
f2fs means friendly 2 file system.

it is considered to be faster than the regular ext4
[Galaxy S 4 i9505 Original Android Development] Jochen K.:
Crash during Nandroid backup

Hi,

a few days ago I started a Nandroid backup, and after a short while it stopped with a red error message.

I bought the 128 GB SanDisk Ultra just a day or two before this event.

If this is possible to find out from the log, could one of the experts please tell me whether this was just a one-off hiccup, or whether the new card is defective and should be returned?

(The second backup went through without problems).

Regards,

Jochen
[Galaxy S 4 i9505 Original Android Development] r0ckarong:
The build from TWRP themselves has F2FS support as far as I can tell. I know that in the past AOne included some features that had not been in the official build. For now is there any reason to flash this one over the official build?
[Galaxy S 4 i9505 Original Android Development] side:
hello :)

as i already said there are only 2 reasons to flash this.

1-f2fs format type....All JDCRoms works with f2fs and it is concidered to be faster than ext4

2-Themes(look post #2)

Nothing more nothing less.

If any bugs exists,its due to official TWRP.not jdc's one
[Galaxy S 4 i9505 Original Android Development] side:
hmm....maybe defective sd ? maybe not capable to read 128gb sd through twrp?

I dont know....Try with other sdcard just for test.

also disable compression
[Galaxy S 4 i9505 Original Android Development] r0ckarong:
I have the TWRP 3.0.0 build installed and that offers me formatting to F2FS as well. So I don't see the difference?!
[Galaxy S 4 i9505 Original Android Development] Rhoban:
Why don't you just flash and see for yourself.

It can't possibly take longer than 2 minutes for the whole process.

Download the jdc recovery img, boot into twrp, switch to image mode and flash the jdc recovery img.

Reboot recovery and test.
[Galaxy S 4 i9505 Original Android Development] z06blaze:
Is there anyway safestrap could be integrated with TWRP? I have the i337 S4 which means I'm stuck on the MDL bootloader which may affect performance on some ROMs. If a ROM could be installed using MDL, then safestrap could be used to switch to a more recent bootloader and if I wanted to flash again, I could just go back to MDL. Would something like that be possible or even work? I have some Java, Android, C/C++ experience that I could help contribute if it's feasible and worth it.
[Galaxy S 4 i9505 Original Android Development] paolo2331:
Twrp 3.0.1-0 is out. Will we have the updated version with f2fs support? :D
[Galaxy S 4 i9505 Original Android Development] jimbomodder:
+1
[Galaxy S 4 i9505 Original Android Development] sjamie:
That would be absolutely WONDERFUL but I think it may just be wishful thinking due to the amount of work involved and it would only benefit certain AT&T users (and possibly some Verizon users).
[Galaxy S 4 i9505 Original Android Development] christoophat:
Updated my baseband/modem using Odin (back to stock KK). Applied CF-auto root, and now want to flash TWRP. I have grabbed the zip file from the supplied link, went to stock recover & tried to flash, but keep getting footer error & verification fail, and will not work. What am I doing wrong here?

Duh...I forgot that I need to add recovery first thru Odin, THEN update via recovery. Sorry! Has been a while....
[Galaxy S 4 i9505 Original Android Development] okidokiss:
and 3.0.2-0
[Galaxy S 4 i9505 Original Android Development] grot84:
+1
[Galaxy S 4 i9505 Original Android Development] Zeitraffer:
+2
[Galaxy S 4 i9505 Original Android Development] okidokiss:
Is this still alive?!?
[Galaxy S 4 i9505 Original Android Development] Annunneo:
I'm currently using this recovery without any issues, haven't updated since I first flashed it and see no need to.
[Galaxy S 4 i9505 Original Android Development] okidokiss:
Yeah, me too. But, you know... We like to update[emoji4]

Enviado do meu GT-I9505 através de Tapatalk
[Galaxy S 4 i9505 Original Android Development] droidblitz:
I am about to flash JDC ASOP MM rom and just flashed TWRP 3.0.0.0 and this came up upon rebooting.

What should i do with it?

Proceed to read only?
[Galaxy S 4 i9505 Original Android Development] laupuy:
No, ignore. Just swipe and enter into recovery
[Galaxy S 4 i9505 Original Android Development] Tech 4 9:
Hello all. So I think I screwed up my (reg)twrp recovery. I'm on Vruamdk and tried to update from 3.0.0-0 to 3.0.2-0 using twrp manager. The partitionooked right (as far as research could tell) dev/block mmcblk0p21 so I hit yes. It gave a error and said version already installed (which it isnt) and upon reboot to recovery I got scrambled twrp screen followed by pink bootloop screen. Can I flash this jcdtwrp using flashify and be all good? Kinda nervous here. Thanks so much.
[Galaxy S 4 i9505 Original Android Development] mattgyver:
If you want to flash 3.0.2-0, just download the 3.0.2-0 IMG from TWRP.me and use flashify.

Why jump through the hoops of installing JDCTeam's TWRP build, if you plan on flashing a different TWRP right away?

Sent from my TARDIS
[Galaxy S 4 i9505 Original Android Development] Tech 4 9:
The links in op all say something about "themes". Which one is the actual recovery?..the one that says "image" but under "theme"? Thanks.
[Galaxy S 4 i9505 Original Android Development] mattgyver:
Click "download IMG and sources", under JDCTEAM Theme. It'll be a zip file on Google Drive. Extract recovery.IMG and you'll be able to flash that with flashify.
[Galaxy S 4 i9505 Original Android Development] Rhoban:
You could update by downloading the img file from their site and flashing it through the actual recovery or Flashify.
[Galaxy S 4 i9505 Original Android Development] side:
hello guys.

about people asking if still alive:

Yes it is :P why shouldnt be alive ?

We didnt release 3.0.2 because dees troy already made great work on it.if we work on it,we will make just some themes.
[Galaxy S 4 i9505 Original Android Development] nsiti:
Hi, I was wondering if I could get some help here. Galaxy S4 with CM 13 installed (clean flash). Was running this version of TWRP but my phone is not recognized as rooted. Then something happened and now I cannot enter recovery mode. I used odin to recover back to CM 13, and now I'm trying to flash twrp again. My version is jflteatt.

Question 1: Is the best way to flash TWRP on a non-rooted phone using Download mode, and a .tar? If so, where can I find a recent .tar version of TWRP? I only see .img versions on the official site.

Question 2: Assuming I can get TWRP back on my phone, how can I make sure root sticks?

Thanks in advance.

Edit, I have subsequently tried to use adb fastboot but it hangs at waiting for device.

Edit 2, found a twrp 2.6.3.0 tar file but odin 3.09 fails to flash it.
[Galaxy S 4 i9505 Original Android Development] Rhoban:
Hey there,

I assume you have the Samsung drivers installed?

Since you are already on CM13, and most probably rooted, you're better off trying to flash it one of the .img files with Flashify.

Note that CM builds have their own root manager and root is disabled by default. You have to enable it from the developer options.
[Galaxy S 4 i9505 Original Android Development] nsiti:
The problem is that even though root is enabled in CM13, the phone is not rooted and thus cannot run rooted apps, and I cannot seem to flash twrp either via Odin or fastboot.

Is there another way to root the phone? Perhaps an old method?
[Galaxy S 4 i9505 Original Android Development] Rhoban:
Try installing supersu from the play store.

Your device has a locked bootloader, so that might be the reason why odin fails to flash TWRP.

I understand that more recent versions of TWRP have loki patch included. But I don't think it would hurt to loki patch manually.
[Galaxy S 4 i9505 Original Android Development] nsiti:
SuperSU says: "There is no SU binary installed and SuperSU cannot install it, that is a problem. If you just upgraded to Android 5.0 you need to manually re-root...."

How on earth did my bootloader go from unlocked to locked when all I did was upgrade from CM 12 to 13 and from TWRP 3.0.0 to 3.0.2?

So I'm stuck on CM 13 unrooted? Or is there some other way to re-root the device?

Thanks.
[Galaxy S 4 i9505 Original Android Development] Rhoban:
JFLTEATT is AT&T variant.

AT&T phones come with a locked bootloader straight from Samsung.

I wonder... Does download mode confirm it's AT&T? The phone model should be SGH-I337.
[Galaxy S 4 i9505 Original Android Development] mattgyver:
Common misconception.. The ATT S4, as GDReaper said, has a locked bootloader. Always has been locked. The Loki script made the MDB/MDL locked bootloader allow custom ROMs, recoveries, etc. The newer bootloaders are locked down even tighter. SafeStrap is the only option, which really limits what they can do.

Sent from my TARDIS
[Galaxy S 4 i9505 Original Android Development] nsiti:
That's correct, my phone is AT&T, however, the early models like mine with Bootloader MDL were not locked.

---------- Post added at 08:45 AM ---------- Previous post was at 08:40 AM ----------

My AT&T bootloader was one of the first, ie MDL variant. I have been running custom ROMS for years, GPE, CM 12, now CM 13 via TWRP. The question is: was my bootloader recently locked somehow (and how) and can I do anything so I can load a recovery at this time?

Thanks.
[Galaxy S 4 i9505 Original Android Development] mattgyver:
No. MDB (my S4's bootloader version), and MDL (your bootloader version) are NOT unlocked. It is a locked bootloader. The loki script was created to address it, by working around the locked bootloader. Here is the thread about Loki: http://xdaforums.com/showthread.php?t=2292157

Newer bootloaders, which were upgraded whenever someone did an OTA, patched the code that Loki used. When patched, it limited newer bootloaders to SafeStrap recovery, which severely limited what could be flashed to the phone.

I've been seeing a lot of people saying that the TWRP.me build of 3.0.2 still has that bug for some people, where loki isn't working right. Not happening to everyone, but definitely happening to some..

You can use flashify to flash JDCTeam's 3.0.0 build, which works fine. That is what I ended up having to do, too.
[Galaxy S 4 i9505 Original Android Development] nsiti:
If I've lost root, I can't use flashify, correct? That's my problem, no matter what I try (odin, flastboot) I can't flash a recovery. :(
[Galaxy S 4 i9505 Original Android Development] mattgyver:
Did you lose root the second you flashed to CM13? Did you look in Developer Options and make sure Root Access is set to either "Apps Only" or "Apps and ADB", and NOT set to disabled?
[Galaxy S 4 i9505 Original Android Development] nsiti:
Thanks for your help. I believe I lost root when I flashed from JDC's 3.0.0 version of TWRP to the official 3.0.2 version of TWRP. After flashing when I selected reboot system, the phone would not complete booting and gave an ominous AT&T error message about non-permitted software being used. To fix this I used Odin and did a stock recovery (I did not flash a kernel). This allowed the phone to boot back into CM 13.

Developer Options root access is set to Apps and ADB yet no rooted apps will work. Sounds like I messed up at one or two points along the way.
[Galaxy S 4 i9505 Original Android Development] Rhoban:
How about flashing a stock rom (beware not to flash a locked up one that won't allow you to root or modify anything) and start from scratch. Cuz at the moment you're pretty much stuck if you don't have root access.
[Galaxy S 4 i9505 Original Android Development] nsiti:
Do you have one to recommend? Thanks.
[Galaxy S 4 i9505 Original Android Development] Rhoban:
I guess you could flash your MDL stock rom, if you can find it.
[Galaxy S 4 i9505 Original Android Development] nsiti:
I just wanted to follow-up and say that I was able to find and flash the stock MDL rom, then I had to reroot the phone, then install the TWRP from this thread, then CM 13. However, once again SuperSU 2.65 did not stick (thankfully this time the process did not un-root my phone) ie the phone would not boot so I had to reflash CM 13 and am using the built in root. Thanks for the help given in this thread.
[Galaxy S 4 i9505 Original Android Development] lorenzitto:
Hi everyone, no chance of making this working on i9515? I have older TWRP 2.X .

I would really try to change from EXT4 to F2FS
[Galaxy S 4 i9505 Original Android Development] Rhoban:
Hey there,

Normal TWRP 3.0.0 also has the option to change file system.
[Galaxy S 4 i9505 Original Android Development] lorenzitto:
I forgot how to update recovery to TWRP 3.0.0.2

Its better with flashfire by chainfire or rawr? Which app I could use? I'm running latest sombre's Cyanogenmod 13 port on i9515
[Galaxy S 4 i9505 Original Android Development] Rhoban:
You can update it with Odin, you can update it with Flashify, don't know if you can update it with Flashfire, but you can also update it using your current custom recovery.
[Galaxy S 4 i9505 Original Android Development] lorenzitto:
I think I'll do with Flashify, updating from TWRP 2.8.7.0 to 3.0.0.2 from inside a pre-installed TWRP sounds bit of a paradox.

Or a recovery can update itself using the .img and .tar files? Or I need to create a .zip?
[Galaxy S 4 i9505 Original Android Development] okidokiss:
A recovery can update itself without any problem.

You can also use TWRP app from playstore.
[Galaxy S 4 i9505 Original Android Development] Rhoban:
You boot into TWRP and flash the 3.0.0.2 img file.

Then you go to reboot and reboot into recovery. The new one should boot up.

The only thing you have to do different, compared to a normal flash, is to switch TWRP from zip mode to img mode.

If that fails, try the app method. But there is no reason it should fail, I updated the same way and always update it this way. No apps needed.
[Galaxy S 4 i9505 Original Android Development] side:
this :good:
[Galaxy S 4 i9505 Original Android Development] JayQuery:
Hi.

Quick question. I'm on the CWM recovery and to change to the TWRP recovery, if i understand correctly, i can just flash the flashable zip from here through my current recovery? Or do i have to do it through download mode and odin?
[Galaxy S 4 i9505 Original Android Development] side:
since u are on OTHER recovery,i would recommend to flash via odin.although i dont think there is such a difference
[Galaxy S 4 i9505 Original Android Development] Rhoban:
You should be able to flash it with your existing recovery.

If you're rooted, you can also flash it with Flashify.
[Galaxy S 4 i9505 Original Android Development] adsactly:
I really hope this fixes my issue. I tried updating to the latest Cyanogenmod Nightlie for my device and now I am stuck in Bootup Screen it won't go past it.
[Galaxy S 4 i9505 Original Android Development] asad007:
I have stock non rooted firmware, with stock recovery.

Can i flash via the recovery??
[Galaxy S 4 i9505 Original Android Development] jimbomodder:
No, you need to flash the recovery via Odin.
[Galaxy S 4 i9505 Original Android Development] asad007:
I dont see .tar here ?
[Galaxy S 4 i9505 Original Android Development] laupuy:
Here: https://dl.twrp.me/jfltexx/ then flash any recovery you want.

;)
[Galaxy S 4 i9505 Original Android Development] A838:
Is there a reason why this is not updated to 3.0.2?

(I know that question sounds demanding, sorry)
[Galaxy S 4 i9505 Original Android Development] Rhoban:
Because there aren't any major changes in 3.0.2.0.
[Galaxy S 4 i9505 Original Android Development] walttheboss:
I'm on 3.0.2 and it works great. Only bug fixes from 3.0.0.
[Galaxy S 4 i9505 Original Android Development] nalibanani:
Has anyone installed this recovery on the att I337 yet? I have one but I don't want to install it till I'm fully sure it will load properly, I don't want to trigger the "unauthorised system trying to install" pop up!

Looking forward to the answer, thank you!
[Galaxy S 4 i9505 Original Android Development] cesande:
Same here

Same question here. I am on I337 MDL.

I tried a different TWRP install zip and got hung at the 'non approved software' screen.

I assume that was because it didn't handle LOKI correctly.

Had to rebuild the phone with stock MDL, root, load my working CWM recovery back and then restore a nandroid backup.

Scared the crap out of me at first but got it back.

Would like to move from CWM to TWRP as my first step towards moving to JDCTeam optimized CM... but need some validation that this version works as I think it should.

-Chuck
[Galaxy S 4 i9505 Original Android Development] side:
i am using this version of twrp since i built it
[Galaxy S 4 i9505 Original Android Development] cesande:
Thanks flash the zip in OP with CWM here soon and report back.

Probably tomorrow morning.
[Galaxy S 4 i9505 Original Android Development] cesande:
100% confirmed working with i337 MDL!

Had Jeboo Recovery i337 v2.7 installed which is CWM.

Backed up EVERYTHING I could with that and then saved off my SD card.

Loaded JDCTeam TWRP... made me feel good that it said that it was checking if LOKI was needed.

Booted right up...

Booted into TWRP to check everything...

I could navigate in file manager to my CWM backup and see it but if I hit 'Restore' it could not find it...

Sooo..

Did a backup with TWRP - default of Boot - Data - System (Named to what I wanted..... LOVE this feature... can't do with CWM)

Did a backup of EFS (I already had one but why not) again with what I wanted for name.

Did a backup of Recovery (I already had one but why not) again with what I wanted for name.

Rebooted to System (something CWM didn't handle nice.... it would do a shut down... LoL).

CM12 fired right up and all is good...

Man I like TWRP soooo much better than CWM after just using it for an hour or so.

Now onto CM13 for next step.

HUGE thanks [MENTION=5968293]side[/MENTION] for this!
[Galaxy S 4 i9505 Original Android Development] texasniteowl:
Hey everyone, I have an AT&T I337 w/MDL bootloader which is rooted with TWRP 2.5.0.2 on it. Can I flash directly to this recovery from TWRP 2.5.0.2 or do I need to do any interim flashes or any other prepatory steps?
[Galaxy S 4 i9505 Original Android Development] Rhoban:
I'm not familiar with those devices, but normally you should be able to update straight away.
[Galaxy S 4 i9505 Original Android Development] texasniteowl:
Thanks, I did use flashify, but everything appears to have worked fine...that is, it does boot into recovery, TWRP 3.0.0-0 by JDCTeam.

Two questions. First, just to clarify, I think by reading this thread that the recovery has loki for the recovery built in for the i337's? Second, my previous version was so old that this new version popped a screen about "unmodified system partition" and whether I wanted to allow read/write. I wasn't sure, so I thought I ignored it and it would ask again. Only, it has not asked again so far. Is the checkbox under Mount that says "Mount System partition read-only" the same thing? Meaning if I uncheck that, then it will allow read/write to the system partition? What is the pro/con either way? (I guess I need to go find the TWRP official thread and try to read about it.)
[Galaxy S 4 i9505 Original Android Development] Rhoban:
Loki is something that is included in ROMs, not recovery.

Mount /system in recovery is not the same thing as what you described.
[Galaxy S 4 i9505 Original Android Development] texasniteowl:
Any idea how to get that initial "Unmodified System Partition" screen to pop up again then? Or do I even need to worry about it?
[Galaxy S 4 i9505 Original Android Development] Rhoban:
If it's similar to what I've been getting, then the only sure way I know is to wipe your internal storage.

Or find out where TWRP stores the configuration file and delete it.
[Galaxy S 4 i9505 Original Android Development] pxrave:
no update to 3.0.3 or 3.0.4 ? including new f2fs fixed etc...
[Galaxy S 4 i9505 Original Android Development] Rhoban:
Not even the official one has been updated yet.
[Galaxy S6 Edge Q&A, Help & Troubleshooting] caspergotchi:
The reason i want to do this is i own an ATT s6 edge (SM-G925A) but im in the uk and im on the H3G (3) network. It is network unlocked. It would be nice if the phone acted as if i had bought it here (able to update OTA, boot with 3 logo etc). I found the firmware on sammobile (SM-G920F), it was only a single file though, using Odin3 i loaded it into the AP tab, but i just got a fail and a soft brick which i fixed with the original ATT firmware that has 4 files. AP,BL,CP and CSC. I'll admit i'm not sure what they do individually.

I really want to know, is what i'm trying to do even possible and if so, where if i needed, can i get a more complete firmware file? I'd be really grateful of any help or advice, thanks.
[Sony Xperia Z Ultra] M4Gaming:
Hi xda team

I really search everywhere for a solution but nothing

I want to install costum recovery on my xperia z ultra

I didn't found anything

Can you help me

Thank you
[Sony Xperia Z Ultra] RealityFails:
Nuts dual recovery?
[Sony Xperia Z Ultra] M4Gaming:
Actually there is any recovery on my phone
[Sony Xperia Z Ultra] M4Gaming:
Hello

I Really Try It But It's Give Me This Problem

http://xdaforums.com/xperia-z-ultra/help/stuck-boot-t3271810
[Sony Xperia Z Ultra] RealityFails:
So your doesn't boot up?
[Sony Xperia Z Ultra] M4Gaming:
Yes I Need To Flash My Phone To Fix That Problem

Now the phone is right but there is no recovery
[Sony Xperia Z Ultra] RealityFails:
Download flashtool

And flash stock ftf
[Sony Xperia Z Ultra] M4Gaming:
Dude The Phone Is Right It's Working But I need A Recovery