I'm having some issues with my pixel:
Unlocked, but Stock (no root, no twrp) on Android Beta NPG05E (7.1.2). Yesterday morning I've had some issues with hangouts (receiving, but not sending any messages), so I restarted my phone.
On the first reboot it was stuck with the dots animation, at some point i restarted it again by pressing the power button for a long time (like 30 sec?).
This time the phone was booting into OS but there are even more issues: Fingerprint reader not working ("hardware not available") - but gestures do, displays that mobile data is disabled (but is actually enabled), having no notifications at all, the navigation bar button to switch apps does not work (vibration feedback, but no action triggered) and probably a lot more.
Next I checked for Software Updates and also found one - the beta OTA! Seeing this I remembered that the beta dialog was not present at the last boot up and also noticed that Android Version is 7.1.1
This also explains all the issues - going back from Beta to stock is not supported without wipe.
(now i know: --> Somehow the phone might have switched between the two slots?)
While all this happened while I was still on vacation, I then applied the OTA once again and was back to 7.1.2 - but the issues weren't gone. Only Fingerprint reader was working again, the other problems remained.
So next I would probably need to do a factory reset - but I wanted to make a backup with TitaniumBackup first:
Booting TWRP RC1, flashing SuperSU 2.79 SR3, reboot --> no binary found (?)
So I checked and I was back to 7.1.1 again!
Using TWRP I could see that I was on slot B - the build.prop says NMF26U (7.1.1), while on slot A was NPG05E (7.1.2 Beta). So I switched the active slot to A and was on 7.1.2 Beta again - and SuperSU is running well (which means SuperSU installer actually installed on the correct slot, but somehow it got switched right after flash or during reboot).
Did somebody experience something similar? Do you know if there is anything else (besides an OTA) which changes the active slot?
I will probably go for a TB backup now, factory reset and restore the user apps.
Related
Hey mates,
A weird problem happens to my phone and it is now pretty annoying.
After I switched back from Oreo and restored my nandroid, everything worked just fine until a week (or two) ago... then suddenly I got one (sometimes even two) of my SIM cards.... empty! It just says slot empty. No signal, no nothing! Only thing I can do is restart. But it keeps happening over and over, randomly!
My device is XZ F8332 running Nougat 41.2.A.7.76. Also list something that might have gone wrong:
- unlocked BL
- kernel patched by this tool but I used ta_poc instead of DRMfix.
- TWRP v3.2.1
- Magisk v15
- Systemless xposed v89
- Greenify latest
What I have tried:
- flash kernel
- re-install Magisk
- wipe cache + davik
- (sounds stupid but I tried everything as I googled) turn off -> remove SIM tray -> turn on -> turn off -> insert SIM tray with both SIMs -> turn on
So far no luck.
Any ideas?
Edit: After days testing by selectively removing apps, I strongly believe AdGuard is the culprit! Uninstalling it solves the issue. It's been 5 days now and I haven't encountered any sim lost. Hope it helps.
Edit 2: I was using AdGuard with root (proxy mode) and HTTPS enabled. You can try disabling some features see which one causes the issue. I decided not to use it anymore.
boydzethuong said:
My device is XZ F8332 running Nougat 41.2.A.7.76. Also list something that might have gone wrong:
- unlocked BL
- kernel patched by this tool but I used ta_poc instead of DRMfix.
- TWRP v3.2.1
- Magisk v15
- Systemless xposed v89
- Greenify latest
Click to expand...
Click to collapse
Try using AndroPlus Kernel because it has a DRMfix as well. The DRMfix might be the culprit.
https://kernel.andro.plus/tone2.html the version you need to flash is v31 (Which is the latest I think). But please do go through the requirements before you attempt anything.
Cheers
Tiqqy said:
Try using AndroPlus Kernel because it has a DRMfix as well. The DRMfix might be the culprit.
https://kernel.andro.plus/tone2.html the version you need to flash is v31 (Which is the latest I think). But please do go through the requirements before you attempt anything.
Cheers
Click to expand...
Click to collapse
Thanks for the reply. I however don't think DRMfix is the culprit. Because I simply don't use it. Instead I use ta_poc. One thing is, before I flashed Oreo (to give it a try), it was working flawlessly. When I went back to Nougat, I restored the whole nandroid. So everything should be exactly the same. Well, expect some apps got updated (e.g. Magisk and TWRP)
My phone had been working fine for quite some time running praetorians 3.2.1 twrp and the weekly version of AICP 8.1 Last week I tried to flash Bliss 9.0 and everything went wrong. (Note I'm not blaming anyone for this, I know stuff happens when you play with your phone)
After much trial and error I finally got the stock os loaded through erecovery and got praetorians twrp back on. But, now when I flash into twrp and it asks for the password to decrypt data it rejects the password. When I installed the stock os this time it asked for a 6 digit pin instead of the 4 digit pin when I initially setup the phone but twrp won't take either the new one or the old one. I pm'd praetorian but he didn't know what the problem was.
I have a copy of removeencryption.zip which I think I've used in the past but now when I run it, even though it reports sucessfully installed, nothing changes. So now I can't do a nandroid backup of /data, although I can do one of system for all the good that does. I've tried official twrp and the 3.2.3 version referenced in the Bliss rom thread but I've not been able to get to the point I was at prior to last week, with data decrypted. In the blur of activity over the last week I think I tried to install a rom but couldn't because data was encrypted. Does that sound right?
If I'm stuck here that's ok - I've got the stock os rooted with xposed running and my favourite launcher installed. I can live with that on this great phone. But I'd like to get back to where I was before. Is that possible?
encrypted media filesystem will be mostly overwritten or a part of it, if not full (esp the critical start)
low level recovery tools will not recognize the data at all
only long shot is to dd your entire disk content as an image and experiment with it on PC while you enjoy the favorite launcher
What partitions get updated when one does the full update using the full image found in the firmware finder? I saw in one thread (ota update on rooted phone) a mention of flashing both ramdisk and ramdisk_recovery.
I wonder if doing such an update - hopefully with Pie after Saturday, might 'reset' my phone back to where I can decrypt data using praetorians twrp?
Hi,
I'm quite new to operating with Android phones, anyway..
I had been running the stock MIUI 10 10.2.2.0 Stable ROM on my Redmi Note 6 Pro. I've decided to try PixelExperience ROM because it runs on Android Pie and I like design of pure Android. So I flashed twrp by MrR00t (it has to support Pie ROMs and it really worked), boot into twrp, canceled decrypting storage, wiped data partition, flashed disable dm-verity and force encryption, flashed pie firmware, rebooted to recovery again and installed latest PixelExperience.
Everything was fine (i mean camera worked) and I've decided to root the phone for changing emoji. I've changed them successfuly. And I wasn't fed enough so I was unhappy that the PIN is not 'entered' automaticaly (I mean after entering 5 or 6 numbers auto "enter" press). This feature provides GravityBox, so I've installed successfully Xposed for my device (not wrong version, I am pretty sure about that) and then wanted to install custom GravityBox for Android Pie (official is not avaiable yet). It needed two other modules installed before ('Magisk Riru Core' and 'Magisk EdXposed Beta'), I've installed them successfully, then I rebooted the phone and installed GravityBox from link given in the thread. Then activated GravityBox module in Xposed and rebooted for activating.
Unfortunately the phone soft-bricked, so I reinstalled PixelExperience and wiped Dalvik/Cache and rebooted to system. Camera stopped working (I mean camera app didn't even display any button, no settings, just black screen).
I have already tried installing stock stable MIUI ROM, beta ROM and camera doesn't work on either of them. Also tried hardware test and it stops working after trying to run camera test. No matter which camera (both front and both main doesn't work). BUT both LED flashes works.
Please, help me, I am out of ideas
btw. I know the issue seems to be physical, BUT it stopped working after flashing something.. Phone also bricked, I think there is some connection.. Thank you all for the time
EDIT: I have found out that it's caused by damaged file "persist" located in dir: /dev/block/bootdevice/by-name/persist. I did replace it with persist.img file extracted from fastboot version of latest pie beta ROM MIUI in twrp terminal. That file is probably responsible for system communication with all the sensors, as I read in internet, and Xiaomi devices are blocked to manipulate with it by just flashing ROM in fastboot (this function is called arb = anti rollback).
Hello! I have had my One plus 7 pro international running for months now, rooted, following this guide https://forum.xda-developers.com/oneplus-7-pro/how-to/guide-bootloader-unlock-twrp-install-t3940368. I had the OTA update notification for quite some time now, but I ignored it because I was lazy. A few weeks ago my phone must have auto updated however, as I started noticing banner ads again that adaway usually blocked, and I have had a few other minor issues like GPS taking longer to connect or find where I am, wifi disconnects, and google not understanding what it usually does. Phone still works just fine, just minor issues I didn't really experience before.
I would like to completely reset the phone to clean it up, and re root and setup TWRP again, but im not sure how to safely do that since my phone was updated improperly (automatically). I have magisk still installed, but the modules dont seem to be working properly. Rebooting to recovery will reboot me to one plus recovery instead of twrp. When I restart is still says my boot loader is unlocked, and some apps (like chase mobile app) still say my phone is rooted. Oxygen updater says im up to date on OxygenOS 10.0.3.gm21aa.
What would be the best option for me to clean everything up, get my root modules working again, and have the phone fully up to date and stable? Any information would be greatly appreciated.
follow the same steps you followed first time. Boot to TWRP flash magisk, No need to factory reset. Flash twrp again if you want and reboot to system
Unfortunately, I have a problem. My phone was on the power cord overnight and pulled the latest update (EEA 12.5.5.0 Enhanced). It was then booted into OrangeFox (OrangeFox recovery with OTA support) and waited for my OK. I didn't think anything of it and didn't make a backup either, as I assumed that everything would go smoothly like the last update.
The update then went on, but there was probably an error, because now I have a bootloop (yellow Poco lettering for about 2 seconds). I can't use an old backup because I'm abroad right now and I don't want to lose the apps I've already set up (pandemic, tracking apps, certificates, ...).
Does anyone have a quick trick or the latest full ROM that I can just iron over or any other good quick idea? Change bootloader slot or other options? OrangeRecovery and Fastboot are still accessible. Now I only have ADB/Fastboot on my work laptop, but I still can't list the device with adb devices. I guess I still need to install the Xiaomi driver for it, but that should be the minor issue.
Update: I am currently downloading the different ROM versions (fastboot, recovery and incremental update), just in case they are needed.
OTA for the rom and using ofox? hmm it's not supported unless you will flash stock rom maybe. I don't know much more. Correct me if im wrong.
OTA works very well with orangefox and AICP 16.1...