Search results

Ok, me thought this is a recovery issue and as there is currently only alpha software. I do not think that this is the issue in this case. By now I can install the PBRP that was kindly provided via dropbox. Me thinks something was weird in the TWRP I installed that triggered this. Since I...

Thanks, that worked. I did try integrating it into the stock update script, just in case, still had stock recovery after that. Strange. Explicitly flashed it afterwards and got PBRP. Great! Immediately flashed xiaomi.eu 11.0.5. Tried to sideload Magisk, but that seems to be wonky in this...

I am unfortunately not on Telegram;-( Someone sent me this, but the link s recursive ;-( https://t.me/pbrp_testers/9182 cheers afx

Which one would be the right one? The stock install script already does that. So me thinks that would not change anything as I tried stock and then flash custom recovery several times. cheers afx

Joyeuse: Phone stuck in "the system has been destroyed" after recovery flash Hi, I've messed up my global Redmi Note 9 Pro (Joyeuse). I had various issues updating to Xiaomi.EU 110.0.5 because of the dynamic storage while using PBRP 2.9.1 and 3.0 unofficial builds which I found on XDA. So I...

Not mounted by default anyway... cheers afx

Hi, the thread header states that this has a fix for dynamic partitions. But I do get an error from the dynamic partition assertion when trying to flash Xiaomi.EU 11.0.5 ;.-( thx afx

Hmm, looks like this does not support dynamic partitions. I run into an assertion error trying to install the xiaomi.eu 11.0.5 ROM. cheers afx

I would assume this is a limit for disk space usage for a specific id or group. Which to me seems some weird artifact in the context of the boot process. I might be wrong of course. cheers afx

Yes, I see that too, but who cares about quota ? cheers afx

Me thinks it should. cheers afx

Cool, Thank you so much! But are the install instructions correct? Download PitchBlack Recovery flashable zip from bellow Extract the PBRP zip Goto fastboot mode in your device Flash the recovery.img by fastboot flash recovery.img Boot into PBRP Copy the zip to internal storage Flash it...

Thanks! I think I already do have the 9x firmware because there where issues that required me to download a newer vendor ROM sometime earlier this year. So I think I should flash oxygenos-9.0.5-bl-km-5.0.8-firmware-3T.zip Reflash the current LOS 16 Wipe cache/dalvic, reboot and be happy. I...

After some recent update of Lineage OS (20191018) my phone suddenly complains that selinux is set to permissive. I know how to switch this from a root shell at runtime, but I would prefer to have this set to enforcing permanently. And why did it suddenly flip? O3T, LOS 16 20191020, Magisk 20...

Ok, some more tidbits. Re-installling the phone leads to exactly the same apps having problems. Workaround: Install the apps from the play-store and then load their data from TiBu. A PITA, but better then doing all the setup again. But wait.. No account data was restored. Just to make sure, I...

Hi, been a Titanium user for a long time and usually it works like a charm. But now I am stuck. Re-installed LOS 16 (20191018) with formatted data/system/cache after a hosed OTA on my OP3T. Now TiBu has issues with about 30% of the backups (for example YouTube, Locus, Okuna). None of the three...

Same here with lineage-16.0-20190925-nightly-oneplus3. It goes through description, displays the boot animation for a while and then reboots into recovery (TWRP) cheers afx

A regular reboot in TWRP works fine, it was just after the Install step where I had seen that message. cheers afx

Another useful post for Titanium users: https://forum.xda-developers.com/showpost.php?p=78599004&postcount=4 cheers afx

Yup, flashing it already. Still the TWRP message about no OS installed, But Lineage boots!!!! THX!! afx

Thanks! So what is the best course of action now. Stick with OOS until the next build or flash LOS 15.1 and then upgrade (or is this again a complete reflash)? thx afx

This is the one I have installed. I already went on a Google tour before asking here. I got OOS installed that way. But only after I ignored the "No OS Installed" message in TWRP. This killed TWRP, so flashed that again, then (after the wipe sequence) LOS 16, Gapps and Magisk and I am back to...

Yes, as this is also part of the Lineage install instructions. cheers afx

Dupe

Dupe

Hi, tried going from stock OxygenOS (rooted) to LineageOs 16 according to the LineageOS Instructions. No dice. After flashing successfully, including nano gapps, TWRP (3.2.3-1) tells me that there is no OS. Reboot ends in the bootloader. Tried flashing stock OxygenOS and it only shows me the...

N/A

Been using rsync wrapper for quite a wile now and it works just fine (two stock Oreo systems). Give it a try. cheers afx

Ok, found something today: Rsync Wrapper by Letscorp from the play store. seems to work, though one needs to experiment a bit with the options. cheers afx

Hi, before Oreo I happily used "Rsync for Android" to sync images from my NAS to my Pixel C (and backups the other way). Since Oreo this no longer works. The rsync and ssh executables in /sdcard/Android/data/eu.kowalczuk.rsync4android/files/ are no longer executable, as the sdcard is mounted...

Actually, I did fastboot reboot and then adb reboot recovery. But that does not work. The keys directly after flushing worked. cheers afx

Just flashed 7.1.1. Then tried to flash TWRP again, did not work, got the message: "$ fastboot flash recovery ../TWRP_dragon_3.0.2-23.img target reported max download size of 268435456 bytes erasing 'recovery'..." After some google search I used "$ fastboot -S 512M flash recovery...

Ok, that might explain it. Been using the latest xceed which is m. Funny enough, now the r/w prompt from TWRP no longer shows up. This is really weird... Ok, will try with the stock kernel... ---------- Post added at 10:07 PM ---------- Previous post was at 09:54 PM ---------- Ok, used the...

Flashed the whole sheebang again: fastboot flash system system.img fastboot flash vendor vendor.img fastboot flash recovery recovery.img fastboot flash boot xceed-v8.02-NRD90M.img fastboot reboot It went to the google boot logo. Where it now sits... cheers afx

That worked... At least to get TWRP the prompt for R/W again. But the when I try to reboot, TWRP complains about no boot image? I thought boot and system are independent.. So I went into fastboot again and flashed the kernel image. Still TWP complains that there is not boot image when I use the...

Thanks, found it myself after I realized there is a shell with a find command... Can't get to a normal system ;-( Unfortunately. deleting .twrps does not bring the prompt back.. Well, there is data on it that I do not want to recreate, it just takes too long... cheers afx

If just could find it (TWRP reaction is quite sluggish... it's a pain browsing it). thx afx

Drat, I read that a bit too late. I have ticked the option to never show me this screen again. So thought reflash TWRP to get it back, but that did not bring back the option and I see nothing in the preferences to re-enable it again. Any ideas how to get it back? thx afx

Unfortunately, since I switched, I do get a random reboot about once a day (low usage). I did set it up from scratch. cheers afc

Ok, waiting then ;) thx afx

Would it be sane to flash the individual N factory images (nrd90m) and xceed-v8.02-NPD90G.img over the latest M release with the xceed kernel? I really don't want to do a full factory reset... And is xceed-v8.02-NPD90G ok for nrd90m or should we wait for a new xceed kernel? thx afx

Hi, I am totally puzzled. Use the Pixel C earlier this morning to read stuff with the kindle reader, Wanted to do some more reading a few hours later and suddenly it no longer accepts the pin code (Message states "Wrong Pin"). The device is rooted (I use the Xceed kernel with TWRP recovery)...

I just installed system.img and vendor.img from MXC89K and then the 3.18 xceed kernel via fastboot. Now I get a message on each reboot that my system has an internal problem and I should contact my vendor. But so far the system seems to work fine. Any ideas? Or shoud I just ignore it? thx afx

Thanks, sounds like a plan ;) cheers afx

Now that the new rom is out (ryu-m5c14j-factory-b714e9bd), how do I install it? I assume I can not perform an OTA install but need flash it via TWRP right? Flash it like the one in the first post and then do the kernel (xceed-kernel-google-dragon-v6.10-RELEASE-mxc14g) and su again on top? Or...

Why ZIP? Why not an IMG from the TWRP devices page? cheers afx

TWRP 2.8.6 does not see encrypted sdcard on N4 Looks like I have a related problem to those quoted below on my N4. I had problems with the nightly updates of CM 12.1 which would not reboot with the installed older (don't remember which release) TWRP. Thought I might need a newer recovers...

.84 issues Same issue here (Germany, Vodafone). I had stock 4.3 and now moved to CM 10.1.2 but the radio is still .84. The phone often goes from blue to grey bars without any connectivity. Stock 4.3 was problematic connectivity-wise, but this is even worse. cheers afx ---------- Post added...