Related
Hello everyone, recently I have started digging into the world of modding so I tried rooting, custom ROMs and custom kernels. Everything was working fine until yesterday, when I decided to move from lineage to pure nexus with elementalX kernel. I had some trouble with the installation and I had to re flash the same ROM several times because it soft bricked( At the end the problem was the radio and bootloader version ).But when I configured the ROM I saw that the autorotation on YouTube wasn't working, so I started searching for solutions on Google but with no luck. I swear I've tried ALL the possibile solutions (installing an app to see if the proximity sensor works, reflashing pure nexus and Resurrection Remix and lineage and stock Nougat and stock Marshmallow ROM, wiping data cache system ART/DALVIK internal storage, factory resetting from stock, editing the proximity firmware manually, disassembling the phone to check hardware error and so on ) but I can't get this sensor working, I can't even find the cause of this faulty sensor . I would really appreciate ANY kind of suggestions, thanks in advance
RichardCasales said:
Hello everyone, recently I have started digging into the world of modding so I tried rooting, custom ROMs and custom kernels. Everything was working fine until yesterday, when I decided to move from lineage to pure nexus with elementalX kernel. I had some trouble with the installation and I had to re flash the same ROM several times because it soft bricked( At the end the problem was the radio and bootloader version ).But when I configured the ROM I saw that the autorotation on YouTube wasn't working, so I started searching for solutions on Google but with no luck. I swear I've tried ALL the possibile solutions (installing an app to see if the proximity sensor works, reflashing pure nexus and Resurrection Remix and lineage and stock Nougat and stock Marshmallow ROM, wiping data cache system ART/DALVIK internal storage, factory resetting from stock, editing the proximity firmware manually, disassembling the phone to check hardware error and so on ) but I can't get this sensor working, I can't even find the cause of this faulty sensor . I would really appreciate ANY kind of suggestions, thanks in advance
Click to expand...
Click to collapse
Flash the vendor.img in TWRP or fastboot that matches the build name of the rom you are installing. This gets updated monthly so custom rom users need to flash this each month.
Sent from my Nexus 5X using Tapatalk
I think am already updated with the latest vendor for my current ROM (pure nexus with N2G47F vendor.img)
RichardCasales said:
I think am already updated with the latest vendor for my current ROM (pure nexus with N2G47F vendor.img)
Click to expand...
Click to collapse
Well, it looks like you'll have to wipe the entire device and reinstall the latest factory image.
Edit: Does autorotation work anywhere else?
Sent from my Nexus 5X using Tapatalk
Sadly auto rotation doesn't work anywhere, I've wiped all the phone ( system, internal storage, dalvik and cache) and installed the latest factory image but the problem doesn't seem to solve..
RichardCasales said:
Sadly auto rotation doesn't work anywhere, I've wiped all the phone ( system, internal storage, dalvik and cache) and installed the latest factory image but the problem doesn't seem to solve..
Click to expand...
Click to collapse
Interesting, no working autorotation anywhere. Which factory image are you using (include entire file name)? Could you screenshot the computer after you run the entire command for installing factory image?
Sent from my Nexus 5X using Tapatalk
The zip file name of the image was (image-bullhead-n2g47)
I installed the factory.img manually because I had trouble with the flash-all.bat file.
I don't think I can take a screenshot of the computer anymore because the PC wasn't mine and I can't have access anymore.
I take it you have tried sensor apps to see if it gives any values,
I have the same problem, warranty states it is due to water damage.
Does anyone know where the sensor is on the board?
Bmi160 gyroscope
i've been struggling lately to install miui on my device and i remember that i used to be able to. but now, every time i flash any build of Miui, it looks like it's messing up the graphic card. steps i did:
having ob 18 installed, i flashed 3.2.8(and 3.2.7) firmware and modem (everything ok)
next, i flashed miui(all of them, with and without gapps)
and after the instalations succeds,, i reboot, and the screen looks blueish and pixelated, like it's burned.
the only way yo fix this was to flash 3.2.8 firmware and modem again, just to be able to boot to the rom
BUT.... that's not it
i boot succesfully into the rom, and if i lock, then unlock the phone, that overlay gets back
the problem is present even on the bootloader and recovery menu.
i'm back to oos now, but i will flash it again tonight and post some pictures
cheers
Here is a video I made
XDRdaniel said:
i've been struggling lately to install miui on my device and i remember that i used to be able to. but now, every time i flash any build of Miui, it looks like it's messing up the graphic card. steps i did:
having ob 18 installed, i flashed 3.2.8(and 3.2.7) firmware and modem (everything ok)
next, i flashed miui(all of them, with and without gapps)
and after the instalations succeds,, i reboot, and the screen looks blueish and pixelated, like it's burned.
the only way yo fix this was to flash 3.2.8 firmware and modem again, just to be able to boot to the rom
BUT.... that's not it
i boot succesfully into the rom, and if i lock, then unlock the phone, that overlay gets back
the problem is present even on the bootloader and recovery menu.
i'm back to oos now, but i will flash it again tonight and post some pictures
cheers
Click to expand...
Click to collapse
thanks
MarJava said:
thanks
Click to expand...
Click to collapse
for what? :|
XDRdaniel said:
for what? :|
Click to expand...
Click to collapse
不错啊
MarJava said:
不错啊
Click to expand...
Click to collapse
what's nice?
XDRdaniel said:
i've been struggling lately to install miui on my device and i remember that i used to be able to. but now, every time i flash any build of Miui, it looks like it's messing up the graphic card. steps i did:
having ob 18 installed, i flashed 3.2.8(and 3.2.7) firmware and modem (everything ok)
next, i flashed miui(all of them, with and without gapps)
and after the instalations succeds,, i reboot, and the screen looks blueish and pixelated, like it's burned.
the only way yo fix this was to flash 3.2.8 firmware and modem again, just to be able to boot to the rom
BUT.... that's not it
i boot succesfully into the rom, and if i lock, then unlock the phone, that overlay gets back
the problem is present even on the bootloader and recovery menu.
i'm back to oos now, but i will flash it again tonight and post some pictures
cheers
Click to expand...
Click to collapse
是不是底包问题
MarJava said:
是不是底包问题
Click to expand...
Click to collapse
it isn't? do you know what's causing the problem? did it ever happend to you?
XDRdaniel said:
it isn't? do you know what's causing the problem? did it ever happend to you?
Click to expand...
Click to collapse
我没用MIUI啊
change your file system for ext4 ... miui rom just suport ext file system and that fixed the issue for me
pedrosantosobral said:
change your file system for ext4 ... miui rom just suport ext file system and that fixed the issue for me
Click to expand...
Click to collapse
Thats riiiight. Now i remember that a moyh ago i switched from ext4 to f2fs.
Yet, i can't tell if this is the reason, because now i am running the latest miui from x_s, and this one runs just fine.
Thank you anyway.
Did you actually get the same screen issue?
XDRdaniel said:
Thats riiiight. Now i remember that a moyh ago i switched from ext4 to f2fs.
Yet, i can't tell if this is the reason, because now i am running the latest miui from x_s, and this one runs just fine.
Thank you anyway.
Did you actually get the same screen issue?
Click to expand...
Click to collapse
No I had a different issue but I'm 100 sure that problem comes due to your file system...the versions u using is adapted to f2fs so it works but unmodified versions have a lot of issues and some of them doesn't even boot on f2fs
Sent from my OnePlus 3 using XDA Labs
Latest miui is based on nougat or marshmallow ? Can you give me a link for the miui you installed ? I want to test it
Diaze said:
Latest miui is based on nougat or marshmallow ? Can you give me a link for the miui you installed ? I want to test it
Click to expand...
Click to collapse
Still mm based. It has the firmware included, so you can flash it over any rom.
https://www.androidfilehost.com/?fid=961840155545570150
I am currently using aosp 8.0 ROM as my daily driver. When I found out that the new aosp 8.1 ROM is available,I flashed(did a clean wipe thou)it got encryption issue(and asked me to reset my phone..when I clicked on the reset button it just used to boot me into my Twrp recovery)so thought something was faulty in the ROM
Then I saw pixel experience ROM based on 8.1 flashed got the same issue again.....I tried to install stock 7.0 recovery from Lenovo it say resetting system but the problem is still there....I also tried changing my my data partition to ext4 but the problem still exist.....SOMEONE PLZ HELLLPPPP
..btw every 8.0 and lower version of ANDRIOD ROM works perfectly.
Hi flash this on twrp https://build.nethunter.com/android-tools/no-verity-opt-encrypt/no-verity-opt-encrypt-6.0.zip and let me know if it works for you, had the same problem.
rksayush said:
I am currently using aosp 8.0 ROM as my daily driver. When I found out that the new aosp 8.1 ROM is available,I flashed(did a clean wipe thou)it got encryption issue(and asked me to reset my phone..when I clicked on the reset button it just used to boot me into my Twrp recovery)so thought something was faulty in the ROM
Then I saw pixel experience ROM based on 8.1 flashed got the same issue again.....I tried to install stock 7.0 recovery from Lenovo it say resetting system but the problem is still there....I also tried changing my my data partition to ext4 but the problem still exist.....SOMEONE PLZ HELLLPPPP
..btw every 8.0 and lower version of ANDRIOD ROM works perfectly.
Click to expand...
Click to collapse
Change data partition to ext4 and den reflash
Use Boardsearch
https://forum.xda-developers.com/lenovo-p2/help/encryption-unsuccessful-aufter-flashing-t3732484
I don't understand
roli0201 said:
Use Boardsearch
https://forum.xda-developers.com/lenovo-p2/help/encryption-unsuccessful-aufter-flashing-t3732484
Click to expand...
Click to collapse
What do u want to say mate?
Problem was solved
ASP02 said:
Change data partition to ext4 and den reflash
Click to expand...
Click to collapse
Just wiped all the data and changed it to ext4 and flashed the ROM again it worked for me.thanks
It didn't but
Cuvillier said:
Hi flash this on twrp https://build.nethunter.com/android-tools/no-verity-opt-encrypt/no-verity-opt-encrypt-6.0.zip and let me know if it works for you, had the same problem.
Click to expand...
Click to collapse
Well I was unable to solve my problem with this but I ahve a question when do I have to flash this before flashing the ROM or after flashing this rom I am making a YouTube video on this issue so your opinion will help a lot thanks.
i have the problem on all oreo roms, i press encrypt, then i see the custom logo loading, and at the reboot i am STILL UNENCRYPTED. the problem is that being unencrypted i do not see any option to use the FINGERPRINT scanner!
Hi all, I flashed the MIUI global stable 9.5.6.0 ROM through a fastboot flash and everything is working perfectly, except for the YouTube app. When I open the app it just keeps showing the circle loading animation and remains there, even after selecting trending, subscriptions, library or even searching.
Oddly enough, when I flashed the 9.2.7.0 NEIMIEK Nougat ROM through fastboot, YouTube was working fine. However, upon updating to MIUI 9.5.6.0 Oreo through updater app, the YouTube problem came up problem. Does anyone have any idea how to fix this issue? Any help is appreciated.
KeyLimePies said:
Hi all, I flashed the MIUI global stable 9.5.6.0 ROM through a fastboot flash and everything is working perfectly, except for the YouTube app. When I open the app it just keeps showing the circle loading animation and remains there, even after selecting trending, subscriptions, library or even searching.
Oddly enough, when I flashed the 9.2.7.0 NEIMIEK Nougat ROM through fastboot, YouTube was working fine. However, upon updating to MIUI 9.5.6.0 Oreo through updater app, the YouTube problem came up problem. Does anyone have any idea how to fix this issue? Any help is appreciated.
Click to expand...
Click to collapse
go to app setting and clear data/cache of the youtube app
devcon69 said:
go to app setting and clear data/cache of the youtube app
Click to expand...
Click to collapse
I've already done so but the same issue persists.
did u try updating the app?
From my experience, when such things occurs, that's almost always "incomplete" ROM flashing.
There is big chance that some partition didn't flash correctly and that this particular app have some residual data and it's in some "limbo" state.
My advice to You is to make clean flashing procedure.
Hridul P.K said:
did u try updating the app?
Click to expand...
Click to collapse
Yup, I uninstalled all updates and udpated again, still have the same issue
Jehonan said:
From my experience, when such things occurs, that's almost always "incomplete" ROM flashing.
There is big chance that some partition didn't flash correctly and that this particular app have some residual data and it's in some "limbo" state.
My advice to You is to make clean flashing procedure.
Click to expand...
Click to collapse
Hmm... I was thinking that a fastboot flash would be the cleanest flashing procedure, should I flash through recovery instead?
KeyLimePies said:
Hmm... I was thinking that a fastboot flash would be the cleanest flashing procedure, should I flash through recovery instead?
Click to expand...
Click to collapse
Yes it is!
I didn't get impression that You have flash fastboot type of firmware! If this is the case, what flashing procedure did You choose?!
You should choose flash_all.bat or flash_all.sh (this depends on OS on which You are, if You are on Windows (flash_all.bat + MiFlash application) or Linux (from terminal sudo ./flash_all.sh)) If You flashed this way, than phone is in stock condition and there is no reason that some rudimentary app like YouTube can not work! Then Your problem is somewhere else (maybe network related issue?)
Jehonan said:
Yes it is!
I didn't get impression that You have flash fastboot type of firmware! If this is the case, what flashing procedure did You choose?!
You should choose flash_all.bat or flash_all.sh (this depends on OS on which You are, if You are on Windows (flash_all.bat + MiFlash application) or Linux (from terminal sudo ./flash_all.sh)) If You flashed this way, than phone is in stock condition and there is no reason that some rudimentary app like YouTube can not work! Then Your problem is somewhere else (maybe network related issue?)
Click to expand...
Click to collapse
I definitely flashed using fastboot and used flash_all.bat.... I am just really confused as to why you the YouTube app is not working.. everything else is working fine
Same problem
KeyLimePies said:
I definitely flashed using fastboot and used flash_all.bat.... I am just really confused as to why you the YouTube app is not working.. everything else is working fine
Click to expand...
Click to collapse
Got this problem too on Miui 11 , Have installed global miui 11 via fastboot (flash_all), and the problem still exist.. .Any solutions? Great thanks..
So, I unlocked my bootloader and wanted to flash Lineage OS, but my phone had a different opinion.
I went into TWRP and tried to format data, but I'm getting
Code:
Formatting Data using mkfs.f2fs...
mkfs.f2fs -t 0 -r 16384 /dev/block/mmcblk0p56
process ended with ERROR: 1
Unable to wipe Data.
Unable to format to remove encryption.
I've tried repairing the data partition, changing the filesystem, nothing works...
Any ideas as to what might be wrong, or how to fix it?
Thanks
todorare said:
So, I unlocked my bootloader and wanted to flash Lineage OS, but my phone had a different opinion.
I went into TWRP and tried to format data, but I'm getting
I've tried repairing the data partition, changing the filesystem, nothing works...
Any ideas as to what might be wrong, or how to fix it?
Thanks
Click to expand...
Click to collapse
Which recovery are u using ?
Armaty said:
Which recovery are u using ?
Click to expand...
Click to collapse
I was using TWRP, but I somehow managed to fix it using Redwolf. Have no idea what happened, but it's ok now.
Hello, I encountered the exact same issue with same origin...
Do you remember what you did to sort this out ?
thanks
(I posted in another thread, before finding yours)
You should check the f2fs kernel workaround guide .
Your problem is due to using incompatible twrp .
Read the guide you'll get around the problem .
0101chaitanya said:
You should check the f2fs kernel workaround guide .
Your problem is due to using incompatible twrp .
Read the guide you'll get around the problem .
Click to expand...
Click to collapse
Thanks... well that's weird, because I downloaded the TWRP recovery linked in LineageOs kuntao install page and I'm coming from stock...
Anyway I just solved my issue by installing Redwolf recovery :
There I could format /data.
I installed crdroid + gapps, but got a "Encryption Unsuccessful" on reboot.
I changed /data from f2fs to ext4 and could reboot properly.
Phone is working good. (I can't get fingerprint reader to unlock my crdroid rom but that's another story and maybe normal limitation, I'll check).
eljuggy said:
Thanks... well that's weird, because I downloaded the TWRP recovery linked in LineageOs kuntao install page and I'm coming from stock...
Anyway I just solved my issue by installing Redwolf recovery :
There I could format /data.
I installed crdroid + gapps, but got a "Encryption Unsuccessful" on reboot.
I changed /data from f2fs to ext4 and could reboot properly.
Phone is working good. (I can't get fingerprint reader to unlock my crdroid rom but that's another story and maybe normal limitation, I'll check).
Click to expand...
Click to collapse
If you ever need to format data just use official build from twrp.me. The one from Lineage wiki has some problems for now. Redwolf is probably based on official one, that's why you succeded.
The thing is that you need to use it ONLY to format /data partition and then switch back to Lineage one before flashing system zip. Known problem, wiki is just a little misguiding here.
Hello. Same problem here, not solved with RedWolf, neither official TWRP.
I've just followed the guide about lineage 15.1 and I really don't know how/if proceed.
Any help would be really appreciated
trespass23 said:
Hello. Same problem here, not solved with RedWolf, neither official TWRP.
I've just followed the guide about lineage 15.1 and I really don't know how/if proceed.
Any help would be really appreciated
Click to expand...
Click to collapse
Update: after closing and run again RedWolf, tap to Format data, magically it worked. I don't know why but thats'it.
Thanks.
this issue seems to pop-up now and then.
just to make it easier for future users coming across this issue. I had explained the issue here in the following post and how to fix it.
just scroll down till it says: "so for those that would like to switch to f2fs but for some reason end up in "black screen with blue led and the phone vibrates".
it applys to the same /data issue.
page 25 off official lineageos 8.1 thread:
https://forum.xda-developers.com/lenovo-p2/development/rom-lineageos-15-1-p2-t3814361/page25