yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 Mini Original Android Development] slouse1:
It is really strange. To get out of the boot loop, I pulled the battery last night and left it out all night. This morning, when I put the battery back, and tried once again to boot into TWRP, it worked. Tried to re-boot into recovery from TWRP itself and it worked. Shut down from within TWRP, tried to reboot using button combination: stuck on recovery booting. Rebooted using power button and pressed the button combination again to boot into recovery: got into TWRP. Tried again to reboot into recovery from TWRP: stuck on recovery booting. Again pressed power to reboot, then power combination to boot into recovery: stuck in recovery booting. Again and again. I will take the battery out again, wait for a few hours and try again, and if I get into TWRP, I will try to wipe whatever I can from within TWRP. I really don't understand why it works a couple of times and then it does not any more. I did not take any action between the reboot-attempts, no wiping, no battery removal.
[Galaxy S 4 Mini Original Android Development] bierma32:
[MENTION=9060853]slouse1[/MENTION]

To boot into Recovery you must hold Power , Volume up and Home button, if you see the Samsung logo hold only Volume up and Home so long if you see the TWRP.
[Galaxy S 4 Mini Original Android Development] slouse1:
Been holding it for hours - can I release now? :D

I tried this before and just re-tried again, to be sure. I know how to get into stock recovery and never have problems with that, so I don't see why I should be doing something differently to boot into a custom recovery. I rather think that there is something in the boot loader or somewhere interfering with booting into anything but stock. Is there any way to find out or to do an entirely clean install?

UPDATE: it seems quite consistent now: if I leave the battery out over night, I can boot into TWRP the next morning. Does this hint help?
[Galaxy S 4 Mini Original Android Development] slouse1:
[MENTION=6005084]ripee[/MENTION], I re-flashed stock rom, went through the setup, re-booted into download, flashed twrp using heimdall, took usb cable out as soon as heimdall reported success and took out battery just after it vibrated during reboot. Left battery out for a few hours, then managed to boot into twrp. However, when trying to reboot into recovery from twrp, it got stuck again. Turned off the phone and removed battery, waited several minutes, put battery in again and was able to boot into twrp. Repeated several times, sometimes I can reboot into twrp from twrp once, and then it gets stuck on the second attempt to reboot into twrp. What else can I try?
[Galaxy S 4 Mini Original Android Development] ripee:
Perhaps your phone's memory or mainboard are failing. Try wiping all internal partitions from twrp and flashing 3.2.1 from an SD card.
[Galaxy S 4 Mini Original Android Development] slouse1:
I already tried wiping all internal partitions, see Post #31. But what do you mean by flashing 3.2.1 from an SD card? Do you mean from within twrp? How could I do this? By the way, if the phone's memory or mainboard was failing, wouldn't you expect to see some problems with the stock rom as well? No trouble with the stock rom!
[Galaxy S 4 Mini Original Android Development] ripee:
I mean flash 3.2.1 from the sd card from within 2.7 or whichever works for you. Beyond this I have no idea how to help you. Unless someone else can reproduce the problems you're having, I don't even know where to start.
[Galaxy S 4 Mini Original Android Development] slouse1:
So far no luck with booting consistently into any recovery except for stock. Also tried 2.7, CWM and others.
[Galaxy S 4 Mini Original Android Development] msbln:
Flash in Reverse

Can a successful flashing with a custom recovery be reversed?

An unsuccessful flashing of a custom recovery often leads to re-flashing with a kind of a vendor's backup recovery, right? So, where does this backup recovery come from? And how can this re-flash be initiated?

Maybe I'm on the wrong track but I'm curious to know.
[Galaxy S 4 Mini Original Android Development] ripee:
The kernel and recovery partitions are completely separate in the S4 Mini. Stock recovery is always re-installed by the stock rom after flashing of twrp if the battery isn't pulled right after twrp flashing completes. This is a safeguard against an unstable unofficial recovery. This of course only happens if you don't pull the battery fast enough and only if you have the stock rom flashed to the system partition already. If you have Lineage, for example, it will not flash its own recovery if you don't pull the battery fast enough.
[Galaxy S 4 Mini Original Android Development] msbln:
Bootloop into Recovery

I flashed the system recovery with both twrp 3.2.1-1 and 3.2.1-0 - with the same result: bootloop into TWRP. I have a 9192 and flashed it using heimdall, no errors. What might have gone wrong?

Is the following line correct?

heimdall flash --BOOT twrp-x.x.x-x-serranodsdd.img --RECOVERY twrp-x.x.x-x-serranodsdd.img

from the website

https://wiki.lineageos.org/devices/serranodsdd/install#installing-a-custom-recovery-using-heimdall

EDIT: Stupid me, looks like I've overwritten the boot partition. Hopefully flashing the bootloader will help.
[Galaxy S 4 Mini Original Android Development] ripee:
The boot partition is the kernel. It gets flashed as part of your rom. The bootloader is completely different!!
[Galaxy S 4 Mini Original Android Development] msbln:
Yes, I was wandering why the

I9192UBSCQB2_I9192UBUCOC2.tar

doesn't contain any boot.img. Now I know :crying:
[Galaxy S 4 Mini Original Android Development] msbln:
Even a guide can be wrong sometimes

In order to get the phone running again, I snatched the boot.img from

https://samsung-firmware.org/download/Galaxy__S4__Mini__Duos__/8c25/SER/I9192XXUCOA2/I9192QERCOA2/

The phone is working again, but probably only in this lucky case. I believe this is uncommon procedure and shall not be advised. For me it was a good option as I'd overwritten the boot partition anyway.

Does anyone by chance know, who has written or can edit the guide on

https://wiki.lineageos.org/devices/serranodsdd/install#installing-a-custom-recovery-using-heimdall ?

There are unexperienced people like me who stick to the guide word by word and use the given code nearly literally, in this case with fatal results.
[Galaxy S 4 Mini Original Android Development] fahrer17:
Can someone please tell me how to check the version of bootloader and modem? And how do I update these with the *.tar files provided in OP?

Unfortunately I'm not too familiar with the S4Mini; I'm just responsible for a friend's phone... :D
[Galaxy S 4 Mini Original Android Development] ripee:
Get the app DevCheck Hardware and System Info, one of its screens will have the bootloader and modem listed. I can't link to it since it has a paid version, but the free version works fine just to see these values.

First boot into Download mode, holding down the volume down, home, and power buttons together. When the text appears on the screen, let go of all 3 buttons, then press volume up. Plug the phone into the computer and proceed with flashing. If you have Windows, use Odin to flash the .tar file using its "AP" button.

All Samsung devices can be flashed this way. If you have Linux, use Heimdall to do the flashing. Instructions are all over the internet.
[Galaxy S 4 Mini Original Android Development] fahrer17:
Thanks ripee!

Ok, I see. I was hoping I could do it in TWRP. I'm at work now with no Odin or Linux PC available atm - so we'll have to check it later...
[Galaxy S 4 Mini Original Android Development] ripee:
You could also do it on the phone itself if it is already rooted, using an app called FlashFire, but if something doesn't flash properly, you could brick the phone worse than if an Odin of Heimdall flash failed, which you could re-do by just rebooting into Download mode again.
[Galaxy S 4 Mini Original Android Development] fahrer17:
Thanks again - really no need to take this risk ;)
[Galaxy S 4 Mini Original Android Development] slouse1:
[MENTION=6005084]ripee[/MENTION] I managed to get into twrp again and read somewhere else as well that it could help to re-flash twrp from within twrp to make it stick. But for this I need a recovery.zip as opposed to a recovery.img, right? Where could I get one for GT I9192? Thanks for your help!
[Galaxy S 4 Mini Original Android Development] fahrer17:
No, you can use the *.img. When in "Install" toggle the button "Install Image" down on the right. With this button you switch between flashing a *.zip and *.img.
[Galaxy S 4 Mini Original Android Development] slouse1:
Thank you, this worked! Unfortunately, it still hangs on the Samsung logo when trying to reboot into recovery. :crying:
[Galaxy S 4 Mini Original Android Development] HemanthJabalpuri:
Sir can I flash modem.img in your latest TWRP. with 321X_v1_hdpi_light_play-signed theme and using fla**** to flash imgs, an option added to flash modem imgs also.....Screenshot is attached...
[Galaxy S 4 Mini Original Android Development] ripee:
TWRP only has the option of flashing boot or recovery within itself. If fla**** allows for modems in IMG format to be flashed, I cannot comment on that because I've never tried it. Modems are usually flashed through Odin in TAR format or Heimdall in IMG format.
[Galaxy S 4 Mini Original Android Development] HemanthJabalpuri:
Sir I tried FlashFire to flash stock ROM..

I flashed protected partitions also like bootloader primary and secondary, modem, trusted zone safely without any problems.....

I have doubt that is there any problems arise when I want to flash second time without any errors in the same mobile i.e., serranodsdd?
[Galaxy S 4 Mini Original Android Development] IronRoo:
Thanks for the updated TWRP, only just got around to flashing it, as sick in bed LOL!

I just ran a backup but got a couple of error messages

1st backup had two errors

"error installing zip file '@/cache/recovery/block.map"

and

"unable to locate '/preload' partition for backup calculation"

2nd try

the first error didn't appear but still had

"unable to locate '/preload' partition for backup calculation"

Doesn't that mean I won't be able to restore?

Do we even have a preload partition on this phone? Anyone know?
[Galaxy S 4 Mini Original Android Development] Dante2468:
trust LineageOS ROMs signatures

TWRP 3.2.1-1-98fc399c still can’t verify the signature of LineageOS builds:

Could you add trust of the official signing keys ?

My workaround for now is to (irrationally) check the ZIP’s SHA2 hash and CRC integrity, in addition to validating the signing key

"C:\Program Files (x86)\Java\jdk1.8.0_141\bin\jarsigner.exe" -verify -certs -verbose lineage-14.1-20180526-nightly-serranoltexx-signed.zip
[Galaxy S 4 Mini Original Android Development] ripee:
If you can show me how, sure.
[Galaxy S 4 Mini Original Android Development] ripee:
I used the exact same partition map as in the serrano-common lineage repo, which has no preload partition listed. Have you tried restoring it yet?

Edit: nvm, I found the problem. I'll post new builds in the next couple of days.
[Galaxy S 4 Mini Original Android Development] HemanthJabalpuri:
Sir I replaced the stock recovery.img with your twrp recovery.img in Stock Firmware of my serranodsdd INDIA........Can I able to flash this with odin.....? Or not...

---------- Post added at 12:12 PM ---------- Previous post was at 12:05 PM ----------

Because of my volume down is not working I cannot go to odin mode manually .....

Now I reboot to bootloader from your twrp....

But after flashing stock it is not possible....

and also stock recovery not boot at all in my mobile...Thats why I have this problem

Is there any way to flash stock firmware and your twrp at same time....i.e., not booting to home screen after flashing stock rom....

I dont know if this possible by unchecking Auto-reboot option in Odin.....Can anyone help....
[Galaxy S 4 Mini Original Android Development] bierma32:
Also for Odin you need the Download mode, so you need a working Volume Down button.
[Galaxy S 4 Mini Original Android Development] HemanthJabalpuri:
That is my problem if i flash stock.......

I can go to download mode now because I have twrp.... bro
[Galaxy S 4 Mini Original Android Development] bierma32:
OK , now you want to install Stockrom ?

Wipe cache , dalvik and factory reset .

Boot from TWRP into Download mode.
[Galaxy S 4 Mini Original Android Development] HemanthJabalpuri:
But how can I flash TWRP after flashing stock rom....is there anyway to flash both at the same time...?
[Galaxy S 4 Mini Original Android Development] HemanthJabalpuri:
[MENTION=6005084]ripee[/MENTION] I have a doubt that why bootloader and modem for device are given in op......

My device is I9192DDUCOF2 ....can I flash those modem and bootloader files over this....

my device is also same weird one as [MENTION=9060853]slouse1[/MENTION] have.....

If yes it should flashed before or after flashing twrp?
[Galaxy S 4 Mini Original Android Development] ripee:
I put the latest bootloaders and modems alongside TWRP because they are often overlooked by rom devs. If you keep up with your device's custom rom, it's a good idea to keep up with the latest bootloaders and modems as they are released. They have nothing to do with TWRP, but I may as well offer them at the same time.

As for flashing twrp from within twrp, you can flash an IMG file by selecting "Install Image" from the main Install menu.
[Galaxy S 4 Mini Original Android Development] HemanthJabalpuri:
My question is not answered.......

Can I flash that bootloader and modem in op in my I9192DDUCOF2.......?
[Galaxy S 4 Mini Original Android Development] ripee:
yes
[Galaxy S 4 Mini Original Android Development] JerseyChewi:
I've got a problem with my I9195 that I haven't found noted elsewhere. Currently on LOS 14.1 and looking to update to 15.1. I flashed the recovery_ltexx.img from arco68's thread from within TWRP 2.x (forgot exact version) but after rebooting, it's just stuck on the TWRP logo. This is different from the issue others have been reporting where it gets stuck on the Samsung logo. I've also tried twrp-3.2.1-1-serranoltexx.img from the TWRP site and twrp-3.2.1-2-serranoltexx.img from this thread, which I flashed with Heimdall but they all do the same thing. I know the flash has at least partly worked because I can see the TWRP version number on that screen. I actually can get an adb shell at this point but it's otherwise essentially unusable. Any ideas? I thought about flashing the bootloader/modem tar but that seems risky and probably unnecessary.

UPDATE: Never mind, it got there after leaving it for a few minutes!!
[Galaxy S 4 Mini Original Android Development] DonQuichotte:
Adopted Storage? If yes, seems to be normal, had it too.

bye DonQ
[Galaxy S 4 Mini Original Android Development] JerseyChewi:
Yes, I later realised that was the cause.
[Galaxy S 4 Mini Original Android Development] Alex-71:
I cannot restore a nandroid backup with TWRP 3.2.2.0 on serranoltexx device.

The backup was created successfully and the restore was also successfully. But restarting the phone leads to a bootloop.

Details:

- I had Lineage 14.1 installed

- I created the nandroid backup of all partitions. Not 100% sure about the TWRP version but i think it was 3.2.1.0 or 3.2.2.0

- I wiped system, data and cache partitions an then flashed Lineage 15.1

- Due to an issue with a corrupt signal-app backupfile i wanted to go back, so i wiped system, data and cache partitions again

- and restored the nandroid backup (only system and data partitions) with TWRP 3.2.2.0 -> Bootloop

For now i'm back to Lineage 15.1.

Has anyone an idea what causes the bootloop? Should i try to restore boot, modem, efs and persist partitions as well? Though i don't think these partitions could have been touched by Lineage 15.1 Rom.
[Galaxy S 4 Mini Original Android Development] ripee:
It's best to restore all the partitions that are selected by default when you make the backup. It's also best to restore a nandroid backup on the same twrp version as you had made it.
[Galaxy S 4 Mini Original Android Development] HemanthJabalpuri:
Bro it is because you didnot restored boot partition

..

It is the main cause of your bootloop...

The minimal restoration is system and boot......

If you want exactly same as before then you have to restore data also.....
[Galaxy S 4 Mini Original Android Development] Alex-71:
Thank you!

I restored all available partitions including boot and everything works fine now.
[Galaxy S 4 Mini Original Android Development] HemanthJabalpuri:
Sir [MENTION=6005084]ripee[/MENTION] ...

One small suggestion is...

Instead of Announcement Make a post when new builds are up....sir

So that it can be noticed quickly....

Many people dont know that there is a follow project option is there for DevDB.....

Thanks for Official TWRP sir.....:good:

also is there any difference between twrp that is uploaded in basketbuild and twrp.me?

Since md5 is not matching......
[Galaxy S 4 Mini Original Android Development] ripee:
twrp.me builds are generated by their build server, that's why.
[Galaxy S 4 Mini Original Android Development] AdilKZO:
Guys, help pls. I am getting error 255,when trying to restore data.

Error restoring backup "extractTarFork() process ended with ERROR: 255"
[Galaxy S 4 Mini Original Android Development] ripee:
https://xdaforums.com/showthread.php?t=2236620&page=48

Error restoring backup "extractTarFork() process ended with ERROR: 255" #758

extractTarFork() process ended with ERROR: 255 #964

The cause may be a file on your phone.
[Galaxy S 4 Mini Original Android Development] AdilKZO:
It didn't help. I have Lineage 14 installed. Also, I cannot access storage while in the system.
[Galaxy S 4 Mini Original Android Development] fassal:
Thank you for keeping up support!

Will you also support I9195I or serranoveltexx again? Unfortunately the versions on twrp page do not support decryption of data (it does not work).

Thank you!
[Galaxy S 4 Mini Original Android Development] jihadinhorocks:
my twrp only reads .zip file not .img how do I flash this?
[Galaxy S 4 Mini Original Android Development] HemanthJabalpuri:
In file manager of choosing zip file... see bottom right, there is an option called Install Image..
[Galaxy S 4 Mini Original Android Development] Mokonasse:
Hi everyone ,

I'm getting some trouble to get TWRP on my S4 mini GT-I9195I.

I've tried almost everything and every combination i found on XDA and others .

Downloaded : Odin3_v3.13.1

and : custom-twrp-3.2.0-1-serranoltexx-STABLE.tar.md5

On phone Vol down + home + Pwr to enter download mode

On Computer Open Odin as admin > UNcheck Freset time and auto reboot > load the tar file in AP , start .

Than i reboot on phone with power and when it vibrates i push VOL UP and HOME ... Getting into download mode again.

I tried :

- Power to reboot than at vibration Vol UP + Home

- Power to reboot than at vibration Vol DOWN + Home

- Power to reboot than at vibration Vol UP + Home + PWR

- Power to reboot than at vibration Vol DOWN + Home + PWR

Didnt Work, than i tried ON ODIN to go for auto reboot :

-at vibration VOL UP + home

-at vibration VOL DOWN + home

-at vibration VOL UP + home + Power

-at vibration VOL UP + home + Power

For the record for each try i starder phone shutted it down to restart the odin stuff .

Since nothing worked i tried with : openrecovery-twrp-3.0.2-1-serranoltexx-STABLE.tar.md5 . Didnt help either

So i took an older Odin version , and didnt help either.

Could you please help me out ?

Thx
[Galaxy S 4 Mini Original Android Development] mielletseed:
the i9195i is a complete different device in the same housing so you are using a wrong recovery file...

Your device is called serranoveltexx

https://twrp.me/samsung/samsunggalaxys4mini64bit.html
[Galaxy S 4 Mini Original Android Development] Mokonasse:
Me wanna bang my head against a wall... I found your link yesterday even before i wrote. Downloaded all files to find a .md5 ...... i just didnt noticed you could just install the .tar with odin :'( .

Well ty very much all work fine now :laugh::angel:
[Galaxy S 4 Mini Original Android Development] mushishi06:
Right version

To find the right info/ version you can use the playstore app call "Droid Hardware Info" he will give wich model you are on (eg: serronoltexx)
[Galaxy S 4 Mini Original Android Development] kevinarol:
Hi, Can anyone helpe? I was using unofficial LOS16 when this error happened.

Excuse if my english is bad, is not my mother language.

Few days ago want to use an app called GLTools, ask me if I have enough space, I check it and mark "Yes", reboot to twrp 3.2.3 and install the zip, phone reboot and the OS starts normally, next day in the morning I see that the phone its completely dead, doesn't even start in download mode, searching through google I find a debrick.img for i9190, was able to restore the "download mode", I install stock rom using odin and when the phone reboot the twrp still there and doesnt pass the first screen O_o , try few more times and the same.

Let the phone in its box, today I try heimdall using Linux Mint, install the stock rom and the same, twrp still there but this time was able to pass first screen and show me some errors, I attach the links of the photos.

I cant repait not change file system of any partition :( hope somebody can give an idea of what happened.

Serrano3G -i9190

https://i.imgur.com/7FZvld9.jpg

https://i.imgur.com/bpmbGmF.jpg

https://i.imgur.com/54j5YY3.jpg
[Galaxy S 4 Mini Original Android Development] Arslan140:
Looks like GLTool unmount System,Data,Caches Partitions after installing Zip.

Under the category Mount you would see a range of partitions available to be mounted. Selecting an entry (check-mark) would automatically mount that partition and deselecting the entry would unmount that partition. You can mount/unmount multiple partition like System,Data,Caches.Marking them will fix your issues.
[Galaxy S 4 Mini Original Android Development] kevinarol:
Thanks for your answer but I already try that and can't mount anything just System and externalSD :(
[Galaxy S 4 Mini Original Android Development] gothmog123:
Guys, is TWRP for the s4 mini going to be maintained in the future?

It looks like development stopped in July 2018 for international LTE.

Does anyone know anything?
[Galaxy S 4 Mini Original Android Development] ripee:
What exactly would you like to be maintained other than what is currently functional? The sources are reviewed and revised if need be every time TeamWin releases a new version, especially if something in the sources would prevent the new version from being properly compiled by TeamWin's build server.
[Galaxy S 4 Mini Original Android Development] gothmog123:
I see. Sorry, stupid question. I had no idea. I'm not a developer. Thanks for giving us twrp and keep up the good work.
[Galaxy S 4 Mini Original Android Development] cdurex:
Had a problem with the latest install on my i9195, the process I did was:

I installed the TWRP App from playstore, then downloaded the 3.2.3-0 recovery for my device, then hit install

(I had the custom-twrp-3.2.0-1-serranoltexx-STABLE-signed.zip installed)

then I rebooted to the recovery and all of a sudden, it started in flashing something screen then rebooted.

My device was reset and deleted all my apps and left my phone as if I had just installed the ROM...

Now I have no latest backup no logcat no nothing.

Just a heads-up for everyone using the app to install the recovery.
[Galaxy S 4 Mini Original Android Development] kurtn:
It is so easy to install a recovery without twrp app.
[Galaxy S 4 Mini Original Android Development] jacklev:
hello guys, help me please... I just sacrifice all my modem/efs directory, so my 3g is broken now, only hawe h/h+ on my gt-i9190. can I flash the modem without pc somehow? I saw some zips for twrp for it, for another devices, but not for me :(