Search results

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!

Hmm, so on the OnePlus forums, this seems to be the consensus ... The OnePlus Adapter was for the non-standard Type C on the OP2 and will only allow charging on the OP3, but not OTG. So far, third party standards compatible adapters seem to be working fine. I just ordered the Xiaomi Type C...

OnePlus adapter didn't work for me either. Worked perfectly with the OP2, but not on the OP3. And yes, I did enable OTG, no help. Not sure what the problem is. Going to wait a few days to see if anybody else has something to add.

Hmm, so this is strange. I have a Sandisk OTG enabled USB drive that I just connected to the OP2 using the OnePlus Micro-USB to Type C adapter. Worked perfectly to backup all my stuff from the old phone. I unplugged here and connected it as is to the OnePlus 3 and it doesn't work. Reconnecting...

Yes, it does. You have to go to the Storage Menu and Enable OTG though.

I have both phones, no way the OP2 protector will fit the OP3!

Umm, did you eliminate the USB port as the problem? Try connecting to a different port, preferably on a different computer?

This is usually a power problem. First thing to eliminate is the power socket, so try it somewhere else. If it still has problems, change the cable. If cable too doesn't solve it, try a new power block. If this too fails, oops, maybe not a power problem after all :)

Okay before anything else, not sure if this is permitted by the forum rules, so let me mention the mods, dottat, Sloth, Stephen, SynisterWolf and apologize to you guys in advance if Im breaking the rules here. Please delete this thread if this is not allowed, but bear no malice towards me for it...

They ran into trouble in India, where Micromax signed an exclusivity agreement with Cyanogen OS and so OnePlus was disallowed from selling their phones. Of course, they worked out some kind of resolution for this, I do not remember the details, but OnePlus switched to their in-house OOS because...

I asked OnePlus Customer Care about this and they said NO, just get your data out and send it back, no need to unroot, relock bootloader, nothing else. I used the live chat on the oneplus.net website for this.

I have this exact same problem with my less than a week old OPT. I think its the charging cable gone bad. Using Ampere to check the charging current, I find that it never goes over 200ma and after about a minute (or lesser) disconnects because the software cuts it off when the current is too...

My less than a week old OPT is displaying similar issues. I think its the cable... If I use Ampere to check the amps, on the OPT with the stock cable, it averages about 180-200ma for a few minutes and then says power disconnected. Unplugging and replugging will again prompt the charging to...

Hmm, fair enough. I think the patched boot.img for your device will still work; boot.img gets the device running and then hands off to the, I dunno what to call it, lets say main OS. But to be sure that it would work as well as it should, you need to be sure that nothing was changed at the...

Is there a reason you want to do all of this manually? There are already patched boot.img files for all the different variants, all confirmed to work. And if not, as just discussed, the new cf-autoroot and SuperSU 2.60 beta and above will do this automatically. If you still want to do all...

Hmm, its still a work in progress. The official beta is still 2.52, and the official release is 2.4x still! So what you have is a very unstable root there. That SuperSU keeps failing to update and you hid the notifications ... How does this work? :) Does the existing SuperSU still work well...

SuperSU Beta 2.60 and above should probably get you root without any of this. They are trying out a new "systemless root" method there and some users have reported success. I have personally not used it, so cannot comment on how well it works for this device specifically. If the new SuperSU does...

Same situation, though in my case, Im returning the device. Does anybody know if I even have to relock the bootloader before I return it? Its unlocked and rooted with official twrp recovery. From what I have read so far, relocking the bootloader will brick the device if one does not restore the...

Hmm, this is generally not a problem with your phone or your software, but relates to the power supply. Noise in the power or grounding issues specifically cause the 'ghost touches' and erratic behaviour you describe. If you are lucky, your charger and cable are also fine and the issue is with...

Never mind ... Found a guy who fixed the motherboard for me! Now I have a new problem, the damn display no longer works... But this should be easier, just have to find ANY phone that still has a working LCD and then VERY carefully salvage the display. If a moderator sees this, I guess they can...

Ok, firstly, I know certain discussions about IMEI are NOT acceptable on these forums. I am confident that none of my questions cross that line, but if any do, I request a moderator to please let me know and I will edit the post accordingly. My current situation: I have an ATT Note 3 with a...

I am no expert on this, and cannot offer much advice for it may violate the terms of this site. BUT, it sounds like you have a corrupt EFS partition, which is where the IMEI is stored. It is possible to set it right, but for that, you have to do your own research. Searching these forums for...

Check if the IMEI on the phone (in About Device, or using *#06#) matches the IMEI on the back of the phone behind the battery. I had an S3 that had this problem, would only work on 2G/GSM, never on LTE, and it was because of a corrupt EFS partition (reflected by incorrect IMEI). If this is the...

A full tutorial as well as prepatched boot images can be found here Also, I believe the latest SuperSU Beta (2.6, if memory serves) has automated this process and will patch your boot image for you. Post #258 on the above thread has a member who provides a link. You may want to try this first...

Err, you are assuming this is the problem. Im not convinced that it is though. If it was sepolicy update, we would have many more with this problem. Maybe we still will, but for now, I think if you just want root back, factory reset and do the steps in the OP again, should be fine.

Can you think of anything else you did recently that might be related to this? Perhaps you installed an app that made changes that triggered this? I do not own a P605, so nothing I can do at my end to troubleshoot. But unless other P605 users show up saying their device started bootlooping...

1) What device? 2) What firmware? 3) Did you go from fully stock to root using ONLY the methods in this thread? The only case I know of where it bootloops after a few days is when you run a custom kernel. Samsung patched things so certain changes cause the device to bootloop till you go back to...

Great! Thanks for letting us know ... The issue then was a failed SuperSU install that cannot be undone simply by reflashing. The others with this problem should also do a full factory reset and follow the instructions in the OP, should work perfectly!

Umm, I thought those having trouble were on the P605, not the P600. Another user has a link to a patched XAR P600 that has been reported to work, if you need it.

If all three of you are using the same firmware, can one of you upload the stock boot.img? I doubt its the patch, but can't hurt to try. I would however advise a full factory reset, wipe cache/dalvik/data/system in TWRP and then reflash stock firmware and follow instructions. If that does not...

Did you get this problem after a clean update? Thats the first step, to make sure this is not caused by a dirty install.

Hmm, this is very unusual. Since it says Kernel Not SEAndroid Enforcing, it means the patch worked. So I am not sure creating a new boot.img for you will help. The only thing I can think of is whether you BEFORE these steps, allowed TWRP to install SuperSU automatically. If you did that once...

As annoying as this is going to sound, can you please expand each step and tell us exactly what you did. The process has worked without problems for practically everybody else on this thread, so the first step is to eliminate user error! Additionally, after you flash the patched boot.img...

To the best of my knowledge, this wifi passwords issue is present with BlueCat's approach. Specifically when you flash the PERMISSIVE kernel from the second link. The whole point of this thread was to AVOID doing that. I do not have this issue on my device, and I don't think anybody who followed...

Bootloop, pretty sure because you allowed twrp to patch with SuperSU automatically when you asked for a reboot. You want to say no to it and reboot once and then go back into TWRP and flash the BETA 2.52 SuperSU manually. If this is not the case, we need more information on what exactly you did...

My bad, I didn't see that there were two links. I clicked a link that took me to the permissive kernel thread! That said, it reinforces my comment that more clarity is required on what is being advertized. It would be useful if you edited your post and separated the two links and clearly...