Recent content by karthikrr

Yes, but for some reason the last time I did this, I ended up with a bootloop that was only resolved by going back to Lineage. I will try this again though. Bigger question is whether I can only go back to stock 5.x ROM or downgrade back to 4.x ROM. I would like to go back to 4.x because I feel...

You are 100% right about the new phone messing up the experience. And already did the reset, and the internal storage is EMPTY, just the OS and a bunch of pdfs and epubs for me to read, nothing else on it, apps are minimal too. Knowing that the hardware is old, I suppose what I would really...

I've been getting frustrated with the stock lollipop firmware on this device. Just doesn't feel snappy enough, but I seem to remember the device being quite good when I first got it. Had a few questions about stock as well as custom ROMs for this device: 1) Does anybody know if I can downgrade...

Yes, I did downgrade. Dirty flash of OB9 over OB11 worked just fine. However, to be doubly sure, I did disable screen-lock before I did it, AND backed up everything important.

I did not try with Pinning, but on my device, Direct Share no longer works. What I mean is, normally I have my frequent shared contacts right at the top with the corresponding app, so I could always directly share with my wife, for example... Now, that no longer shows up. Weird thing is that it...

Yeah, I thankfully managed to sideload the revert build and get my phone back, but was forced to wipe everything .. Unfortunately, did NOT have a backup, coz I was on the road and got too impulsive when I hit update! Oh well, didn't lose that much, so not a big deal ... HOWEVER, once I got it...

How long did the first boot take for you guys? I flashed and had it on the boot animation for some 20 minutes, finally gave in and rebooted into recovery, now it won't even ask me for password to decrypt the phone and still does not boot. Am I screwed?

Same problem with me, on the OP3 running Open Beta 11. Reflashing SuperSU did not work. Rather than extract the boot.img to reflash that, I ended up reflashing the firmware (and ended up mistakenly using the 4.0.1 file instead of the OPB11 one!) ... Yet to try SuperSU and Magisk again on this...

As far as I know, it was stock recovery when I got it. Wouldn't boot, so tried the rest. Flashing stock firmware did not make any difference, so don't think stock recovery works either. Have not tried extracting stock recovery from the odin tar and flashing directly though.

I've unbricked phones before and even messed with dead EFS partitions and lived to tell the tale, but I cannot for the life of me figure this one out. Somebody gave me a S4 Mini (GT-I9190) that was bootlooping. I got it into download mode and ODIN flashed a firmware without any problems. When...

Nah, I think this happens only if you let TWRP modify the system partition. But, I have not and am not willing to test it out :)

I have no solution for you, but I wonder if you went back to stock recovery first before you relocked the bootloader? I think if you have TWRP and try to relock the bootloader, this happens. NOT that its helpful to you, but if this is the case and you can verify it, might help others avoid...

Clearly you manually downloaded the full ROM file from oneplus or some other site on to the S7. This was NOT an OTA update. Fact because a) thats impossible, b) its the full file, c) its in your downloads folder, when any OTA will go to cache and be inaccessible by you without root and d) THATS...

You need to allow TWRP to modify the system partition. If you said to leave it read-only on first boot, it will revert to stock recovery. The problem is if you flash TWRP now, it wont give you that option again. To find it, reflash, boot into TWRP, go to Mount and change it towards the bottom...

I can confirm the Xiaomi Type C Micro USB adapter does NOT work for OTG. Yes, I had OTG enabled, no go!