Search results

Constant vigilance... *rolling one eye*

So the code rounds up the value, thereby increasing the risk of the actual value being smaller than the threshold? :-(

@Ex novo is right - when facing such issues one has to clean as much as possible. It hurts (a lot) to erase (format, "yes") data, and it should become a habit to erase (wipe) system. Magisk doesn't (or rather shouldn't) have an effect on the boot process, and it certainly cannot fix it. As for...

I think NikGapps 13 is for Android 13 = LineageOS 20, not 18.x ...

You may want to give MinMicroG a shot

This doesn't seem to help - the XA2 was released in Feb 2018 and would also classify as "5 years old". There's still /e/ and iodéOS.

@davestuarts So you installed Magisk-v25.2.zip (or .apk) in TWRP? You've also got to upgrade the Manager by installing Magisk-v25.2.apk in user space - yes, both are identical but handled differently!

@Odin<3 To clarify the situation, you may run "adb shell" in both recovery and normal mode (the latter will require activation of developer options), then `get prop | grep serrano`. If in TWRP `serranolte` and `serranoltexx` show up, you've got the right recovery - if not, get it replaced with...

@ahoellrigl I just checked the link to the 3.6.2 build from the original post, it seems to be still the same. With that one, besides the issues reported in #631, I found that I couldn't reliably adb into recovery; replacing it with the official 3.6.2 still in sdcard fixed the issue (but removed...

The path @mbrodala suggests could be shortened if there was a flashable zip that does the removal - this way one, if interested in GApps, would instead flash LOS, the microG remover, the favoured GApps, and perhaps Magisk, without the need to reboot ... Am I missing some important point?

Just attempted a phone call / USSD code - which was denied. This apparently isn't related to the condition @jbohac had reported as `getprop gsm.sim.state` returned `LOADED`. So I tried to shutdown for a full reboot - but pressing the power button didn't show the menu at all. Since I had seen...

My Xiaomi Mi 9 SE running Stock wasn't notified as well - both Pixels (4a, 6a) got it. The "Nina" app suggests to give feedback at https://warntag-umfrage.de - won't that be biased? (BTW the poll wants to know my age and education level. Huh?)

On samfirmware, find the latest upgrade for your operator/country (and triple check the phone model!), compare with the baseband currently on your phone, they should not differ by a long time. Mine (Germany, unbranded) has I9195XXSCQAI, with a build ID starting with I9195XXUC (and three more...

I just picked up my Z3c and checked whether NFC works (I had attempted to change the battery a few months ago - but failed - and left the device in a drawer since...) To my surprise, I apparently did not manage to completely disconnect NFC, as NDEF tools could read a tag. :happy: Build number...

@pgb.1968 make sure that you upgrade your bootloader/modem combo (iow: stock firmware) before switching to LOS

Good point - this one is indeed a DS one (I've been using it with a single SIM for ages, so I had forgotten there was a second slot)!

@jbohac I can't check with my S4mini right now, but on another Android phone there may be a `gsm.sim.state` that *contains* `LOADED` but isn't identical (I've seen "ABSENT,LOADED" - is there an explanation somewhere what that means?). You perhaps may want to change the script to use the return...

Did you start from the right (latest) baseband version?

Welcome back @arco68, you've been missed!

@SamVVaeck Which GApps are you using?

@johnmaster This is a S4 mini forum, and the SCH-1545 seems to be a S4 variant?

So this would require the GApps "survival script" to be removed/deactivated before flashing the ROM?

Um, sometimes reformatting cards with different filesystems leaves some traces of the previous format - and since `mount` tries to autodetect the current format there may be false detections. Nuking (zero out) the first and last MB of the card would fix that.

Since iodé is a derivative of LOS (as stated in the thread title), it's supposed to come with LOS's features and faults. And since it seems to be common knowledge (I never took the chance to corrupt my system by putting part of it onto a sd card) that the "adoption" doesn't work reliably - you...

@Berni-0815 is it still true after ~18 months that adopted storage (ie, combining the sdcard with internal storage) doesn't work? I don't trust sdcards too much, and would never rely on them for functionality of the core system, but others may have a different opinion, and fuse can't be that...

Um, what would be wrong with AndyYan's LOS builds? (Don't have a 2pro to try them myself.)

$ md5sum lineage-18.1-20220421-nightly-pioneer-signed.zip 5eb35d3ed80bf14851618fbddc4aed6c lineage-18.1-20220421-nightly-pioneer-signed.zip is this the latest one, and would you need the recovery too?

(I would have posted that to the TWRP thread but that one didn't get updated for a long time, and perhaps it'd be the wrong one anyway.) I've run into a strange issue with the TWRP 3.6.2 provided via the links in the OP. I'm used to "adb devices" returning "recovery" so I can push stuff into...

(deleted)

AFH apparently didn't get updated yet, Mega works ;)

I'm wondering whether there's a flashable zip file that performs the tasks listed above?

I checked the kernel versions in the latest LineageOS versions available, and found - Samsung S7 Edge (hero2lte) : 3.18 - Sony Xperia Z5c (suzuran) : 3.10 - Moto E 1st gen 2015 (condor) : 3.4.112 - SIII neo (s3ve3g*) : 3.4.113 - S4 mini (serrano*) : 3.4.113 While "condor" has been abandoned long...

Some apps also check for TWRP folder (rename it) and Magic survival script (/system/addon.d/99-magisk.sh, rename it). Some apps even check for unlocked BL :(

Wiping data (aka internal storage) isn't sufficient, you'll have to format.

Some apps check for unlocked boot loader, in which case you're lost...

For curiosity's sake: which kernel version does this ROM use? Found it: in the intro video, a "3.4.113" string can be found.

I admit that I don't use any of my S4minis to call someone (or be called)... With the I9195 there's a lot of hope that internet access will continue to work, and indeed SIP is still an option (I'm accepting suggestions which software to use). Still I'm wondering what the hard-limiting factors...

@danguyf Could you boot (not install) TWRP via fastboot?

@aigezhe There's little chance - but since the source codes are there, go ahead :)

What the error says... SDK versions (of the APK and the OS) don't match

Apparently these tweaks also made the ROM smaller by about 8 MB. Nice ;-) Many thanks!

Does this ROM support Power over OTG? The magnetic charging port isn't too stable...

Did you *format* data, and erase system? What, in addition to the ROM, do you install?

Sometimes it takes a little pain to wake up from daily (and other) routines. No harm done.

Are you sure Orange FR still supports 3G?

Indeed, I found it the rather hard way. You may have guessed that this phone is my only A/B device ... None of the others would require this particular procedure. Lesson learned, I hope I'll remember this once Lineage 20 becomes available.

Hi, I've been trying to setup one phone (@arco68's TWRP 3.6.2 and LOS 18.1, MindTheGapps, Magisk 25.2 with some modules, basic apps), then "clone" it to another I9195 - only to fail in multiple places. TWRP didn't recognize a dump written to the SDcard on the first phone after that was moved to...

Indeed, on their channel on Telegram (BiTGApps Downloads) they (TheHitMan) wrote yesterday,

For the record, I only had to follow these instructions without any paperclip magic - after disconnecting the battery, pressing "left" (Vol-) while plugging in was sufficient. YMMV...

With Magisk 25.2 and the USNF module, I can't get SafetyNet checker to fully succeed. Any suggestions?