Hi, I have a GS4 (Sprint) with TWRP 2.6.0.0. I've been reading up on the permission problems of the backups created with this version and as of now, 2.6.3.0 is out, which fixes these issues.
So I want to update from 2.6.0.0 to 2.6.3.0 but for some reason, it will not even after going through the correct update steps.
Method 1: I updated to 2.6.3.0 from goomanager but when I boot into TWRP, it still says 2.6.0.0.
Method 2: I odin'ed the TAR of 2.6.3.0 and right afterwards, TWRP said 2.6.3.0. But after having rebooted the device and then if I go back to TWRP, it says 2.6.0.0 again!
Here's the curve ball. I'm on Carbon ROM (9/13 release, JB 4.3) and I can't seem to update TWRP if Carbon is running. If I restore Touchwiz and then update with goomanager, it correctly updates and when I boot in to TWRP, i see that it's 2.6.3.0 and even after booting back and forth between Touchwiz and TWRP, it still remains as 2.6.3.0. But when I restore Carbon ROM, TWRP 2.6.0.0 comes back and even if I update it, it still stays on 2.6.0.0. My intention is to remain on Carbon (rather, non-Touchwiz) for the long term so I do want to get this issue resolved.
Help please! Thanks!!!
Big letters to make it obvious:
THIS IS NOT THE GALAXY S4 SUB-FORUM.
This sub-forum is strictly for the Galaxy S4 Active which is the water-resistant variation of the Galaxy S4.
Related
I am just installing the Rogers Lollipop OTA and wondering if the older TWRP versions 2.6.3.4 still work or do I need to use a newer version 2.8.5.0 or something.
OK, finished the OTA, flashed TWRP 2.8.5.0 and rerooted with SU zip 2.43.
All Good
Thanks
Kevin
Can I use fireflash to update TWRP whilst using cm12.1 ROM?
I suppose you could, since FireFlash is just an app to flash files outside of recovery, pretty much like flashify. Although, in my experience, i've never updated my Kindles TWRP as i've never seen the need to, but i did update my Samsung Galaxy Tab 3 TWRP from like 2.5 something to 2.8.6.0 by just flashing a zip like normal and then instead of rebooting to system just reboot to recovery again and everything has worked fine with it. Although if you're adamant about doing it through fireflash i'd assume you could.
Guys, what would be the latest TWRP for our SM-G920T, and where would I find an Odin-flashable TWRP file? (Somehow I do not trust TWRP Manager with the task of flashing TWRP.)
Just in case it matters, I am currently rooted on the latest DOI1 FW.
Aqua1ung said:
Guys, what would be the latest TWRP for our SM-G920T, and where would I find an Odin-flashable TWRP file? (Somehow I do not trust TWRP Manager with the task of flashing TWRP.)
Just in case it matters, I am currently rooted on the latest DOI1 FW.
Click to expand...
Click to collapse
https://dl.twrp.me/zeroflte/
datdirtyscrew said:
https://dl.twrp.me/zeroflte/
Click to expand...
Click to collapse
Thank you! One of the things that I find irritating about TWRP Manager is that it asks me to confirm/verify the partition where TWRP gets flashed to. Now how can I possibly know if dev/block/platform/15570000.ufs/by-name/RECOVERY is the right place for my device? (Is it?) The second thing that bothers me about TWRP Manager is that it doesn't correctly detect the latest TWRP version, and often it offers to install an older version.
Did twrp-2.8.7.2-zeroflte.img.tar work for you?
After updating to DOI1, I get boot loops after trying to flash TWRP.
I can get into recovery and download mode just fine, but it won't boot to the OS.
RiskPrime said:
Did twrp-2.8.7.2-zeroflte.img.tar work for you? After updating to DOI1, I get boot loops after trying to flash TWRP. I can get into recovery and download mode just fine, but it won't boot to the OS.
Click to expand...
Click to collapse
I bit the bullet eventually (sesing as flashing TWRP via ODIN is a PITA), and flashed TWRP using TWRP Manager. I got an error message upon flashing, though it looks like TWRP flashed just fine. (Go figure!) Anyway, TWRP Manager flashes TWRP 2.8.7.1. It may be that TWRP people didn't consider TWRP 2.8.7.2 safe enough to flash, which is why TWRP Manager doesn't offer the option. That may be your explanation for your troubles.
Hi All / @bauner,
Does anyone know if there is a TWRP 2.8.7.0 or TWRP 3.0.2.1 available for our Note, that works in Android 4.4.4 (KitKat)?
I've found a TWRP 2.8.7.0 and a TWRP 3.0.2 which I believe @bauner very kindly wrapped up for us, to flash in ISORec. However when I flash 2.8.7.0 it shows as 2.8.1.0 when inside recovery.
I'm not sure if this has anything to do with ISORec, still trying to get my head around that. I understand that it separates the Recovery from the Kernel. But not sure if ISORec is supported on Android 4.4.4 (KitKat) ?
- when I flash 2.8.7.0 on KitKat, and then boot into Recovery, it shows up as 2.8.1.0?
Do those ISORec Recoveries look for a certain API / (SDK?) build of Android, and if it doesn't detect required version it doesn't flash?
I really need to get either 2.8.7.0 or 3.0.2.1 in order for Lanchon Re-Pit program to work... and happy with my build of KitKat until a stable Android 7.0 is out....
Cheers, Lister
Lister Of Smeg said:
Hi All / @bauner,
Does anyone know if there is a TWRP 2.8.7.0 or TWRP 3.0.2.1 available for our Note, that works in Android 4.4.4 (KitKat)?
I've found a TWRP 2.8.7.0 and a TWRP 3.0.2 which I believe @bauner very kindly wrapped up for us, to flash in ISORec. However when I flash 2.8.7.0 it shows as 2.8.1.0 when inside recovery.
I'm not sure if this has anything to do with ISORec, still trying to get my head around that. I understand that it separates the Recovery from the Kernel. But not sure if ISORec is supported on Android 4.4.4 (KitKat) ?
- when I flash 2.8.7.0 on KitKat, and then boot into Recovery, it shows up as 2.8.1.0?
Do those ISORec Recoveries look for a certain API / (SDK?) build of Android, and if it doesn't detect required version it doesn't flash?
I really need to get either 2.8.7.0 or 3.0.2.1 in order for Lanchon Re-Pit program to work... and happy with my build of KitKat until a stable Android 7.0 is out....
Cheers, Lister
Click to expand...
Click to collapse
In official cm11 the isorec recovery should work in builds after Mar 25, 2016.
If you don't use official cm11 then maybe the twrp 2.8.1.0 is the default recovery which is included in the kernel.
Maybe repit will also work with the older twrp version.
But make a backup of your rom on the external sdcard and also backup the files from your internal sdcard to your pc if something should go wrong
Hi @bauner,
First of all, thanks for the prompt reply... and apologies my delayed response back... Work has been a nightmare, been nearly a week Ive been trying to find time to sort phone out, backup data and so on... anyway....
Thanks for the sound advice, my Android 4.4.4 rom is sadly very out of date, as I was using the much loved Dirty Unicorn 8.2 (which hadn't been updated since sometime around 2015) and so therefore certainly didn't have ISORec support, if it at all??? I didn't go down the stock CM11 route, as I loved the tweaks that were in DU.
RePit may of worked, as it bawked out a couple of times, and couple of different errors. But my main error, which took some getting around... Was files and filesystem. It appeared a file got corrupt on the internal SD, and therefore could not be copied or removed. I eventually had to WIPE the partition completely (after copying what I could).
Bit the bullet, and upgraded to your great CM13 build as of now... I'm not a fan of Googles latest Material Design feel, and much prefered the retro (more colourful / 3D icons) of the older Android, ie: KitKat... that appears to have more features available to that OS. It appears no LP / MM / N have the kinda tweakability of yester-year roms.
Upgraded, RePit'd and got 1.5GB System, 6GB Data, and whatever is left (7GB) for internal SD Card. So I THANK YOU BAUNER for your advice, I'm all sorted now...
I'm prolly gonna stick with your CM13 / MM build now, until CM14 / N is stable (this is not a push or ETA... I appreciate your VAST EFFORTS and it's ready when its ready!!!) as I've found Apps that cater for bits from old OS, such as "Driving Mode" where it had built in TTS that would announce SMS / Incoming Calls, and other notifications. And various other visual elements...
Is it possible to restore a backup from a different partition table. Will it just fill those partitions with the data, or do you think it would look for the same size partitions and as they've increased, will fail to restore...
Cheers, Lister
bauner said:
In official cm11 the isorec recovery should work in builds after Mar 25, 2016.
If you don't use official cm11 then maybe the twrp 2.8.1.0 is the default recovery which is included in the kernel.
Maybe repit will also work with the older twrp version.
But make a backup of your rom on the external sdcard and also backup the files from your internal sdcard to your pc if something should go wrong
Click to expand...
Click to collapse
Lister Of Smeg said:
...
Is it possible to restore a backup from a different partition table. Will it just fill those partitions with the data, or do you think it would look for the same size partitions and as they've increased, will fail to restore...
Cheers, Lister
Click to expand...
Click to collapse
You can restore your backup without problems. It will not change the new partition sizes
I was running latest LineageOS nightly build with Official TWRP 2.8.7.0 before. Then I decided to try Unofficial TWRP (3.1.0 and then 3.0.2) & some nougat ROMs.
(1)Flashed recovery in fastboot, went OK.
(2)Flashed XPerience ROM & OpenGapps, went OK.
(3)Tried to wipe cache/dalvik, stuck forever.
(4)Manually rebooted, after boot animation i get stuck on a "Encryption Unsuccessful" screen, where i can only hit Reset Phone button which reboots into recovery wipe cache etc and then the whole cycle starts again.
Can someone suggest the easiest method to get my device functional again?
Also somewhere in between my internal storage was shown as 0MB, which I fixed by repairing data partition.
My phone is an XT-1060 Developer Edition.
You may need to re-flash to an older TWRP; I can say I have had similar issues with the unofficial 3.X.X releases, in my case mainly stemming from (according to the logs) something breaking and becoming unable to mount the Cache partition. Re-flashing the same version did not work, and a different 3.X version of TWRP would restore functionality for a bit, but then it would crop up again at some point (I couldn't even flash NAND backups, had to re-flash recovery first). Another issue is that there are only a couple of the unofficial releases available because that OP's hosting site went down (BasketBuild I think?). So I went back to the last official TWRP and MM for now, though if anyone has any recommendations to avoid/fix this, that would help a ton!