I am currently using Lineage Os 16. But my phone still has auto rotate bug which it got from asus stock 0.57 update. When i was on stock 0.57 l, i tried updating it into 0.58 via both ota and full zip files. But it always showed error even though both were of same letters(WW). Thats y i rooted the phone and tried clean flashing different ROMs. But the bug didnt go. Finally i downgraded my phone into stock Oreo but still the bug was there. Currently , i am using Lineage OS 16 with the auto rotate bug... Please help me to remove this bug. I am really disappointed... Please suggest any solutions
Related
before this , my a500 is on HC 3.2. because of HC 3.2 doesnt have root access yet , so i downgraded it to 3.0.1 using this and update to 3.1..
and because of that , my media directory can't be played by default music player or any media apps and my pics can't be displayed at gallery. But the media file is still intact in my storage. what happened ?
and it kept showing my "Maps" has stopped unexpectedly , i never used that app ! T.T
Are you still on the unstable 3.0.1 that you downgraded to, or did you flash a new rom? If you're still on 3.0.1 with root, then flash a new custom rom and see if that fixes your issues. If you're still experiencing random force closes, I'd try reflashing the rom. Had to flash mine three times before everything got ironed out.
Still new at this myself, but hope that helps...
Since you downgraded and rooted, I would suggest trying a 3.2 ROM and see if that fixes your problems. Sounds like your ROM is in an unstable state. Also as smhism stated, sometimes you have to try more than once to get everything working. Also make sure you follow all the steps carefully in CWM so that you wipe everything before upgrading and installing new ROMS, otherwise you could experience issues like that one.
i'm on 3.1 (stock rom) rooted 4.010.40_COM_GEN1..
i did upgrade it using unstable updates on the link above..
but i guess i dont want to flash some new roms now , coz i got a lot of other things to take care of..
or maybe it can't be played and detected because of i'm updating using unstable updates ?
I would try to do the downgrade to 3.0.1 again and then upgrade to 3.1 once more and see if anything gets changed. Also, did you root 3.0.1 before updating to 3.1?
Hi everyone,
To flash the last rom (nightly ) of LineageOS ( in Oreo,from the 2 february), i had to put the firmware 5.1.7. After flash this firmware i was able to flash the ROM but it makes my phone extremely slow and with screen issues (i can still use the tactile but the screen doesnt follow).
I restored but the problem stills then i put le last stable ROM from Oneplus on android pie (9.0.3). It is a bit better (still really slow) and after a moment i get now like a white noise (same as on TV but with color moreover) by wink ( was more and more often on Google Maps), I had to reboot cause i couldnt use more my phone.
Thanks you in advance !
Ps : I've got TWRP from siankatabg and i'm not rooted , if you want me to send log tell me how pls.
Up :good:
When you were flashing did you used this instructions?
https://forum.xda-developers.com/oneplus-5/how-to/official-oxygenos-4-5-2-7-1-1-ota-t3627003
Flash codework's TWRP for Pie. After that reboot into recovery, wipe everything down and use clean flash instructions for your OTA. It should be able to fix any issue you were having. If not let me know.
Yes i followed the clean flash way (it didn't resolve my issue) but my issue occured before i flash pie, when i flashed lineageOS 15.1 with the firmware 5.1.7 required (which i flashed too). A restoration didnt change that issue.
I tried with the TWRP from codework but it doesnt recognise my internal stockage.
Thanks of your time.
Raidenne said:
Yes i followed the clean flash way (it didn't resolve my issue) but my issue occured before i flash pie, when i flashed lineageOS 15.1 with the firmware 5.1.7 required (which i flashed too). A restoration didnt change that issue.
I tried with the TWRP from codework but it doesnt recognise my internal stockage.
Thanks of your time.
Click to expand...
Click to collapse
Hi, try wiping everything down with the new TWRP, after that reboot into recovery once more. Install last normal working OOS to see if that helps you. If not maybe it is hardware issue? Let me know once you wiped and installed the last working OOS on it.
I have installed multiple roms and firmware updates on my device with codework's TWRP and never had big issue like this. In my opinion best option for you to trace your steps back to the last working version of your os and try learning what might have gone wrong.
Ebeninyo said:
Hi, try wiping everything down with the new TWRP, after that reboot into recovery once more. Install last normal working OOS to see if that helps you. If not maybe it is hardware issue? Let me know once you wiped and installed the last working OOS on it.
I have installed multiple roms and firmware updates on my device with codework's TWRP and never had big issue like this. In my opinion best option for you to trace your steps back to the last working version of your os and try learning what might have gone wrong.
Click to expand...
Click to collapse
My issues seem gone since few weeks with the last OTA (it very rarely happens now). I don't know what caused that even if i use my backup.
Thanks for your support !
Fingerprint Scanner Null after Pie ROM Flash - Custom ROM won't fix. Stock Only
Ok, the story.... Moto G5+ retail, running 8.1 Oreo, Bootloader Unlocked, rooted using Magisk 16.7 and was able to backup my Stock Oreo ROM once rooted, or I'd be dead in the water.
So wanting to stay ahead, I tried my hand at RR v7's Pie version, which, after some troubleshooting, was able to install successfully; but I don't much care for the google bar and other hard-coded "pure android" features. Same thing with Pixel Exp. Not to mention that Pie disallows call recording among a few other things Google decided to stifle its customers with. Deal breaker. So - moving on...or back for that matter.
I proceeded to download RRv6, which is btw running nicely on a 2nd G5+, same GApps, installs perfect except - FingerPrint Reader is not acknowledged. Period. No Security settings, No RR Config to access it, Nada. No matter what ROM I flash outside of the StockROM I backed up, it won't recognize the fp reader upon boot up. Whether I clear Dalvik/Cache, All DATA, do a full Wipe, DATA WIPE, REPAIR, FORMAT, nothing allows me to install RR v6.0 or any other flavor, Oreo or Pie, even while trying a dirty flash over Stock Oreo on this Moto G5+. Tried with several SD Cards, downloading fresh zip files from RR. I even went so far as to image the working G5+, then copy into the 2nd G5's SN folder, and do a restore, just loops - even after repairing the partition. I managed to work around that, Restored the image, but still no FP recognized by the initial Google startup/setup. It's almost as if the phone's been "firmwared" or "tagged".
Any ideas what could be lingering from Android Pie that would survive a F2FS/exT Format? Because something updated some kind of firmware on the phone during a Pie ROM flash, that now won't let me go back to anything below Pie, with a working fingerprint reader. The only difference between the G5 that works and this one is the working one has never seen Android 9. And it's staying that way til we come up with a way to hack the google crap.
Any help would be - awesome to say the least.
Thanks for looking.
Hello,
The issue with fingerprint is that after flashing stock Oreo ROM it replaces some files related to fingerprint sensor.
Hence all the newer custom ROM builds use the Oreo firmware related files. Hence it worked on the Pie ROM.
RR v6 would be still using the old nougat firmware hence you need to flash a file for it work. Which will replace the fingerprint related files for Nougat Stock firmware:
https://androidfilehost.com/?fid=1322778262904029634
In case you want to revert the changes and use Pie ROMs:
https://androidfilehost.com/?fid=1322778262904029635
sharan.nyn said:
Hello,
The issue with fingerprint is that after flashing stock Oreo ROM it replaces some files related to fingerprint sensor.
Hence all the newer custom ROM builds use the Oreo firmware related files. Hence it worked on the Pie ROM.
RR v6 would be still using the old nougat firmware hence you need to flash a file for it work. Which will replace the fingerprint related files for Nougat Stock firmware:
https://androidfilehost.com/?fid=1322778262904029634
In case you want to revert the changes and use Pie ROMs:
https://androidfilehost.com/?fid=1322778262904029635
Click to expand...
Click to collapse
That would make sense if PHONE1 manifested the same thing. But I went from StockOreo to RRv6-Oreo w/out losing anything and having to flash any FP Firmware. I used the RRv6 Official from 18-0911. Which is what's been leading me to believe there's something awry with this 2nd G5. I wonder is it possible PHONE2 has some slight firmware variance that is simply ignoring during the RR flash? Anyway, I'll give this a shot. this is TWRP flash, not fastboot, yes? Just being clear as I'm not proficient at this just yet.
Thanks Sharan!
DJScribe said:
That would make sense if PHONE1 manifested the same thing. But I went from StockOreo to RRv6-Oreo w/out losing anything and having to flash any FP Firmware. I used the RRv6 Official from 18-0911. Which is what's been leading me to believe there's something awry with this 2nd G5. I wonder is it possible PHONE2 has some slight firmware variance that is simply ignoring during the RR flash? Anyway, I'll give this a shot. this is TWRP flash, not fastboot, yes? Just being clear as I'm not proficient at this just yet.
Thanks Sharan!
Click to expand...
Click to collapse
Yeah, give it a try. And yes it's to be flashed via TWRP.
[SOLVED]
sharan.nyn said:
Yeah, give it a try. And yes it's to be flashed via TWRP.
Click to expand...
Click to collapse
Sweet! I had to reflash from scratch as for some reason it wouldn't let me update the ROM already running. But once I re-flashed RRv6-8.1, then flashed FP, it's now back. You rock Sharyn - nice work!
Now if only we found a way to cleanup that Pie - hate the perpetual time stamp, search bar and inability to record voice. Which is why I'm staying on Oreo til further notice. I know it was Google who took it away on v9.
Thanks again Shar!
:good::victory:
DJScribe said:
Sweet! I had to reflash from scratch as for some reason it wouldn't let me update the ROM already running. But once I re-flashed RRv6-8.1, then flashed FP, it's now back. You rock Sharyn - nice work!
Now if only we found a way to cleanup that Pie - hate the perpetual time stamp, search bar and inability to record voice. Which is why I'm staying on Oreo til further notice. I know it was Google who took it away on v9.
Thanks again Shar!
:good::victory:
Click to expand...
Click to collapse
Crap - so turns out this solution was short-lived. FingerPrint Scanner is back to inactive and FPzip isn't fixing it. Only StockOreo brings it back. Tried a plethora of ROMs from Nougat to Oreo, nothing but Pie and stock Oreo. Symptoms say it's the ROM, but a ROM that is currently working on the 1st G5 won't work either. Still looking for solutions, anyone...
I used to have Havoc OS and everything was working fine but the location. it never worked for some reason and i needed it on my everyday life.
So used UPPERCUT to install stock ROM, ONLY to quickly realise that CAMERA, FLASHLIGHT and YouTube didn't work.
(when opening camera there was only a black screen, flashlight said i was using a camera app and YouTube was endlessly loading without showing my feed)
I wiped everything and flashed stock ROM from here: https://forum.xda-developers.com/lg...-h870-eu-30b-rom-t4007979/page10#post83380121
STILL having the same problem.....
when using havoc OS i didnt have this problem...
any ideas?
Did you flashed Nougat first? If not flash Nougat
to further explain my problem,
even though Camera used to work fine on HAVOC OS,
now even when using a Hardware Tester from Play Store, the app can't find a the camera...
can flashing stuff on your phone kill hardware?
I had a similar issue with a H872. Camera & proximity wouldn't work after flashing back to stock Oreo from Havoc. Someone here suggested flashing back to Nougat. Lo and behold...it fixed all my issues. I then performed software updates to get to the latest stock version.
Good luck!
While ago I changed my rom from Stock Miui to MiuiMix it was very smooth and then I wanted to try some aosp based rom after a while of using them I tried to go back to miui mix but everytime I install it the phone freezes and reboots itself automatically I can't even get pass the Set up wizard with all this freezing, I managed to get pass it but most of apps don't work or work but after restarting they don't work, I tried different miui based rom and all Stock roms with different version the only version that was working fine was 10.3.x but after updating it the freezes and rebooting and weird auto action started again, I did some digging i found out in An xda thread some guy has similar problem and they said it has something to do with persist so i flashed a new persist but nothing changed now i lost L1 DRM and gor stuck with L3 DRM, now I'm on PixelOS everything works fine but can't get back to MIUI.
Data formated in recovery?
Which firmware do you use?