So I restored my PureNexus backup after trying Android O DP2, just noticed this morning that my phone doesn't recognize rotation. I have a motorcycle game that requires rotating the phone and it doesn't recognize any input. I also tried rotation a YouTube video to full screen and no beans. Autorotate is on btw...
I already tried wiping the system/cache and reinstalling PN, my only other option is a full wipe unless there is any easier fix.
Running into the same issue....
flashed "O" yesterday, installed TWRP, clean flashed PN,vendor,radio, bootloader and have no rotation. also brightness is not working and proximity isn't working either. also a slow wake up from screen off (1-2 seconds)
I just flashed May's factory Image and my brightness was still messed up (didn't test the other stuff...woops) currently flashing April's Image to see if that fixes it.
nope, didn't fix it. rotation and brightness don't work. flashing O now. what a ****ing PITA.
Did "O" just **** our sensors?
GatorsUF said:
So I restored my PureNexus backup after trying Android O DP2, just noticed this morning that my phone doesn't recognize rotation. I have a motorcycle game that requires rotating the phone and it doesn't recognize any input. I also tried rotation a YouTube video to full screen and no beans. Autorotate is on btw...
I already tried wiping the system/cache and reinstalling PN, my only other option is a full wipe unless there is any easier fix.
Click to expand...
Click to collapse
turdbogls said:
Running into the same issue....
flashed "O" yesterday, installed TWRP, clean flashed PN,vendor,radio, bootloader and have no rotation. also brightness is not working and proximity isn't working either. also a slow wake up from screen off (1-2 seconds)
I just flashed May's factory Image and my brightness was still messed up (didn't test the other stuff...woops) currently flashing April's Image to see if that fixes it.
nope, didn't fix it. rotation and brightness don't work. flashing O now. what a ****ing PITA.
Did "O" just **** our sensors?
Click to expand...
Click to collapse
Same thing happened to me when I went back to 7.1.2. The only thing that fixed it was to completely wipe the /data partition. Back up all your data before you do it :good:
bouchigo said:
Same thing happened to me when I went back to 7.1.2. The only thing that fixed it was to completely wipe the /data partition. Back up all your data before you do it :good:
Click to expand...
Click to collapse
doesn't flashing a factory image do this? I flashed 2 different image files and neither one fixed it. if I have to flash back to 7.1.2, then boot into TWRP and Wipe Data, I'll do that. just want to make sure is all.
I flashed back to O and everything is working now, so I know the sensors are't physically damaged, its absolutely software related.
turdbogls said:
doesn't flashing a factory image do this? I flashed 2 different image files and neither one fixed it. if I have to flash back to 7.1.2, then boot into TWRP and Wipe Data, I'll do that. just want to make sure is all.
I flashed back to O and everything is working now, so I know the sensors are't physically damaged, its absolutely software related.
Click to expand...
Click to collapse
Yes, it's software related. I usually don't wipe /data unless necessary. Are you flashing images one by one, using the flash-all.bat, or flashing the OTA. Flashing images one by one won't wipe /data, and the OTA will not wipe /data. Using the flash-all.bat should, unless you modify the file and remove the "-w" from one of the lines in the file.
Yes, flash back to 7.1.2, then wipe data.
bouchigo said:
Yes, it's software related. I usually don't wipe /data unless necessary. Are you flashing images one by one, using the flash-all.bat, or flashing the OTA. Flashing images one by one won't wipe /data, and the OTA will not wipe /data. Using the flash-all.bat should, unless you modify the file and remove the "-w" from one of the lines in the file.
Click to expand...
Click to collapse
I downloaded the factory image .zip and used Nexus Root toolkit to flash it. my internal memory is wiped completely during the install. not sure what the flash-all.bat is.
turdbogls said:
I downloaded the factory image .zip and used Nexus Root toolkit to flash it. my internal memory is wiped completely during the install. not sure what the flash-all.bat is.
Click to expand...
Click to collapse
I don't know how that tool kit works, I prefer doing things manually. I just went back to stock 7.1.2 (flashing images one by one), then wiped /data, and all my sensors worked after that.
flash-all.bat is in the main file, you use that to flash all the images without using any tool kits:
bouchigo said:
I don't know how that tool kit works, I prefer doing things manually. I just went back to stock 7.1.2 (flashing images one by one), then wiped /data, and all my sensors worked after that.
Click to expand...
Click to collapse
I'm flashing stock 7.1.2 now. how did you wipe /data? through command lines, or through stock/custom Recovery?
---------- Post added at 10:41 AM ---------- Previous post was at 10:36 AM ----------
bouchigo said:
I don't know how that tool kit works, I prefer doing things manually. I just went back to stock 7.1.2 (flashing images one by one), then wiped /data, and all my sensors worked after that.
flash-all.bat is in the main file, you use that to flash all the images without using any tool kits:
Click to expand...
Click to collapse
looks like the toolkit flashes the images one by one. i following the command line and its doing them (bootloader, radio, boot,recovery,vendor, system) one by one.
turdbogls said:
I'm flashing stock 7.1.2 now. how did you wipe /data? through command lines, or through stock/custom Recovery?
Click to expand...
Click to collapse
You can do it in fastboot if you want, but I just did it in twrp.
bouchigo said:
You can do it in fastboot if you want, but I just did it in twrp.
Click to expand...
Click to collapse
F me. still isn't working. had O DP2 installed, flashed stock 7.1.2, flashed TWRP, wiped data, even formated data. still not working. any other suggestions?
Edit: resetting the device thorugh the settings>backup & reset seems to have worked. brightness working, rotation working, prox I assume is working.
thanks for the help everyone!
Could it be radio or bootloader? O still have those images flashed from the ODP
turdbogls said:
Running into the same issue....
flashed "O" yesterday, installed TWRP, clean flashed PN,vendor,radio, bootloader and have no rotation. also brightness is not working and proximity isn't working either. also a slow wake up from screen off (1-2 seconds)
I just flashed May's factory Image and my brightness was still messed up (didn't test the other stuff...woops) currently flashing April's Image to see if that fixes it.
nope, didn't fix it. rotation and brightness don't work. flashing O now. what a ****ing PITA.
Did "O" just **** our sensors?
Click to expand...
Click to collapse
I fixed the problem by flashing stock with the flash-all.bat file and locking the bootloader. Android O really messed up my mind. For a second i thought my phone was faulty, starting hitting the thing on my palm like a hard reset would work:laugh::laugh::laugh:
Related
I first rooted my Nexus 6p that was completely stock using the system less root method. After I flashed the modified boot and twrp and rooted, my camera wasn't working. It just shows the camera icon and a black screen. I looked up the problem and many people said flashing a vendor image would work, but after doing so, it just tells me there was an internal error, so I reflashed the factory images. After doing so, camera still wasn't working. I also saw one person flashed a different modified boot but this only gives me a bootloop. Does anyone know a fix to the camera problem? Thanks!
kwcty6888 said:
I first rooted my Nexus 6p that was completely stock using the system less root method. After I flashed the modified boot and twrp and rooted, my camera wasn't working. It just shows the camera icon and a black screen. I looked up the problem and many people said flashing a vendor image would work, but after doing so, it just tells me there was an internal error, so I reflashed the factory images. After doing so, camera still wasn't working. I also saw one person flashed a different modified boot but this only gives me a bootloop. Does anyone know a fix to the camera problem? Thanks!
Click to expand...
Click to collapse
It's most likely caused by flashing the wrong boot.img, when you flashed the factory images to go back to stock did you flash the boot.img too?
Heisenberg said:
It's most likely caused by flashing the wrong boot.img, when you flashed the factory images to go back to stock did you flash the boot.img too?
Click to expand...
Click to collapse
I think I did.. I can try reflashed the stock boot.img again though. But I'm not sure what I did wrong because I just flashed the modified boot necessary for twrp?
kwcty6888 said:
I think I did.. I can try reflashed the stock boot.img again though. But I'm not sure what I did wrong because I just flashed the modified boot necessary for twrp?
Click to expand...
Click to collapse
TWRP doesn't require a modified boot.img anymore, it hasn't for a long time, unless you're using the Android N dev preview. You also need to ensure that you flash the right boot.img to suit your ROM build. For example, if you flash the MHC19I boot.img on a ROM that's based on MTC19T you'll get problems, like the camera not working.
Heisenberg said:
TWRP doesn't require a modified boot.img anymore, it hasn't for a long time, unless you're using the Android N dev preview. You also need to ensure that you flash the right boot.img to suit your ROM build. For example, if you flash the MHC19I boot.img on a ROM that's based on MTC19T you'll get problems, like the camera not working.
Click to expand...
Click to collapse
Unfortunately I re-flashed the factory boot and recovery (using build MTC19T), and the camera is still not working. Do you have any other thoughts? Thanks for your help!
kwcty6888 said:
Unfortunately I re-flashed the factory boot and recovery (using build MTC19T), and the camera is still not working. Do you have any other thoughts? Thanks for your help!
Click to expand...
Click to collapse
Flash the full factory images (except userdata), then flash the latest TWRP, not boot into TWRP and enter the wipe menu, select advanced wipe, tick the data box and wipe it. Boot up and see if that helps.
None of the sensors in my phone are working except the fingerprint sensor.
What should I do ?
Factory reset!
If you're coming from O you can flash latest nougat factory image, some people got that issues when they rolled back to nougat. As I first used my 7.12 twrp backup my sensors stopped working too. I had forgotten to sign out of android beta, after I did that under android O my sensors start working again with my nougat backup.
DavePKR said:
Factory reset!
Click to expand...
Click to collapse
Full wiped phone through recovery flashed new ROM, vendor, radio, bootloader. Nothing works. Also looks like I don't have any files related to sensors. :s
Flash the factory image
nimrulzz said:
Full wiped phone through recovery flashed new ROM, vendor, radio, bootloader. Nothing works. Also looks like I don't have any files related to sensors. :s
Click to expand...
Click to collapse
Flash the 7.1.2 image from here https://developers.google.com/android/images using "flash-all.bat" then do a Factory Reset from "settings - backup and reset ....."
I had the same problem after I installed Android O and went back to 7.1.2.
https://forum.xda-developers.com/nexus-6p/help/sensors-stopped-nexus-6p-t3610252
DavePKR said:
Flash the 7.1.2 image from here https://developers.google.com/android/images using "flash-all.bat" then do a Factory Reset from "settings - backup and reset ....."
I had the same problem after I installed Android O and went back to 7.1.2.
https://forum.xda-developers.com/nexus-6p/help/sensors-stopped-nexus-6p-t3610252
Click to expand...
Click to collapse
Thanks a ton. It worked finally !!!!
Hi! Guys I have a problem, which doesn't resemble the BLOD, so here is what has happened. I was running stock android June build on 6p, rooted. And my phone started random reboots. I thought it could be fixed with either stock or custom rom. So I decided to flash AOSPA. I went into twrp but could not flash it, phone rebooted each time. I tried stock images via flash all command as well as manual. No rom worked although I could flash kernel etc. I used The Flash's custom twrp and fixed data and was able to flash rom easily, but it bootlooped on google logo, and rebooted. Now I can flash roms etc but it bootloops. Although Tesla rom did go into bootanimation before bootlooping.
So what can I do? Is it software related? What do you guys say!
PS. I did look into other threads, nothing was similar, although I did try a few mentioned fixes.
osamaasif786 said:
So what can I do? Is it software related? What do you guys say!
Click to expand...
Click to collapse
Use fastboot to FORMAT system, userdata and cache. Note any errors during the FORMAT process.... and then try flashing a full image from Google using flash-all.bat
v12xke said:
Use fastboot to FORMAT system, userdata and cache. Note any errors during the FORMAT process.... and then try flashing a full image from Google using flash-all.bat
Click to expand...
Click to collapse
It gives no error and did try the flash-all.bat method no luck.
osamaasif786 said:
It gives no error and did try the flash-all.bat method no luck.
Click to expand...
Click to collapse
I'd say you were squarely in a small group of people who are able to access and fully use Recovery but still boot loop after formatting and installing a clean image. If you've already tried a factory reset from the stock recovery I think you are done. Hardware issue. Replacing the motherboard is a fix, but not economically viable.
I had the same issue formatting data and cache to Ext4 and flashing modified stock ROM fixed. It would boot to Google logo freeze reboot and sometimes get to boot animation freeze and reboot.
Exodusche said:
I had the same issue formatting data and cache to Ext4 and flashing modified stock ROM fixed. It would boot to Google logo freeze reboot and sometimes get to boot animation freeze and reboot.
Click to expand...
Click to collapse
Which modified one, can you share the link?
osamaasif786 said:
Which modified one, can you share the link?
Click to expand...
Click to collapse
Cortex ROM it's flashable stock firmware with extras . Though my symptoms where the same I hope I'm not giving you false hope. Worth a shot though.
The only was I recover my phone without replacing is using https://forum.xda-developers.com/nexus-6p/general/boot-images-bootloop-t3633723 < method from here... but the phone is lag af as it is only running 1 core on stock july build. Good luck for that.
I have the same issue going on. i was trying to flash magisx and suddenly it is stuck in bootloop. i tried flashing stock images and everything. i can access twrp and flash eveything and they are getting flashed fine but still it is stuck on the bootloop.
TheTickReborn said:
I have the same issue going on. i was trying to flash magisx and suddenly it is stuck in bootloop. i tried flashing stock images and everything. i can access twrp and flash eveything and they are getting flashed fine but still it is stuck on the bootloop.
Click to expand...
Click to collapse
So have you used fastboot to FORMAT system, userdata and cache? Did each format command complete with no errors?
Hello,
So I just installed 8.1 stock, and installed magisk. I wanted to confirm that when I put my phone into fastboot mode and install a rom with adb that it completely wipes the phone as it should, in preparing for a new install, especially making a big jump from 7-8. I'm pretty sure it does, b/c my internal storage was wiped. I went from 7.1.2 to 8.1. I'm asking because my phone still seems to run a *tiny* bit choppy. I made a mistake before, by installing an 8.1 custom rom over 7.1.2 (instead of going to stock 8.1 first), and it had problems. Screen tearing, and the performance was awful. So I started over, and did it right. I'm pretty sure it does wipe, but I thought it would perform a little better than it does; There is still some choppiness and lag.
Bottom line is, I just don't know if I should go into recovery and completely wipe with TWRP, and then install 8.1 through adb.
Thanks!
edit: And what's up w/ entropy? We can't generate entropy anymore?
ibawanzingee said:
Hello,
So I just installed 8.1 stock, and installed magisk. I wanted to confirm that when I put my phone into fastboot mode and install a rom with adb that it completely wipes the phone as it should, in preparing for a new install, especially making a big jump from 7-8. I'm pretty sure it does, b/c my internal storage was wiped. I went from 7.1.2 to 8.1. I'm asking because my phone still seems to run a *tiny* bit choppy. I made a mistake before, by installing an 8.1 custom rom over 7.1.2 (instead of going to stock 8.1 first), and it had problems. Screen tearing, and the performance was awful. So I started over, and did it right. I'm pretty sure it does wipe, but I thought it would perform a little better than it does; There is still some choppiness and lag.
Bottom line is, I just don't know if I should go into recovery and completely wipe with TWRP, and then install 8.1 through adb.
Thanks!
edit: And what's up w/ entropy? We can't generate entropy anymore?
Click to expand...
Click to collapse
Installing via factory image only wipes the device in two cases:
1) execute the flashall script to install the image
2) manually flash each partition of the factory images then run fastboot format userdata afterwards
If you did not do either of these then no it wouldn't wipe your device. You can always wipe and start over if you feel like you notice lag.
Sent from my Nexus 5X using Tapatalk
Thanks for the reply, I'm glad I can confirm it was a full wipe. I did the first step - executed the flashall script. Still seems there's a bit of lag.
I'm going to try SuperXE again tonight. It ran really bad for me when I tried it twice, but everyone is raving about how good it is. I'm going
to have to try that, b/c the stock rom doesn't work like I would like it to.
SlimSnoopOS said:
Installing via factory image only wipes the device in two cases:
1) execute the flashall script to install the image
2) manually flash each partition of the factory images then run fastboot format userdata afterwards
If you did not do either of these then no it wouldn't wipe your device. You can always wipe and start over if you feel like you notice lag.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
ibawanzingee said:
Thanks for the reply, I'm glad I can confirm it was a full wipe. I did the first step - executed the flashall script. Still seems there's a bit of lag.
I'm going to try SuperXE again tonight. It ran really bad for me when I tried it twice, but everyone is raving about how good it is. I'm going
to have to try that, b/c the stock rom doesn't work like I would like it to.
Click to expand...
Click to collapse
May be you can try flash factory 7.1.2, then flash 8.1 images. I was also on 7.1.2 until 2 days ago. I flashed last factory image of Nougat booted it, then flashed 8.1, booted just to make sure its all good, flashed TWRP and elemental X kernel.
Hi all!
So I have a Moto G4 Plus on 7.1.2 RR with Magisk root. I installed ElementalX kernel and overclocked and disabled fsync. However, as I was watching YouTube, my phone randomly froze and rebooted and wouldn’t boot up. It’d be stuck at the boot animation forever. Seeing this, I took a logcat and here is a link to it. I noticed that this line kept looping:
Code:
java.lang.NullPointerException: Attempt to read from field 'java.lang.String com.android.server.pm.Settings$VersionInfo.fingerprint' on a null object reference
I searched the error up on Google, and it led me to this StackExchange site. I had the same symptoms (the jobs.xml file was empty, I turned off fsync, etc.), so I did as it said (I backed up my data partition and did rm -rf /data/system), and I thought my problem was solved, but when I tried booting up my phone again, it still got stuck at the boot animation. Granted, the logcat was different now (here is a link to it), but it keeps looping at:
Code:
waiting for service sensorservice
or
Code:
waiting for service AtCmdFwd
I tried googling for that, but I couldn’t find any useful results, so I guess now I'm stuck. Any suggestions where to go from here?
Thanks so much!
@strongst and @sd_shadow, would you guys be willing to give some advice? I've been stuck without a phone for a couple of weeks now...
matetoes said:
@strongst and @sd_shadow, would you guys be willing to give some advice? I've been stuck without a phone for a couple of weeks now...
Click to expand...
Click to collapse
I would just reflash firmware, Fastboot.exe
sd_shadow said:
I would just reflash firmware, Fastboot.exe
Click to expand...
Click to collapse
Which partitions? Can I do it without losing my data (i.e. only reflash system or something)?
matetoes said:
Which partitions? Can I do it without losing my data (i.e. only reflash system or something)?
Click to expand...
Click to collapse
You can try reflashing just system, but I wouldn't count on any method saving data.
Sent from my Gemini 4G using XDA Labs
sd_shadow said:
You can try reflashing just system, but I wouldn't count on any method saving data.
Sent from my Gemini 4G using XDA Labs
Click to expand...
Click to collapse
I just gave up and updated to Pie with Arrow OS ¯\_(ツ)_/¯. At least it wasn't a hardware problem.
In these type of cases, flash RR on on top of your current ROM (without wiping anything i.e dirty flashing).
It seems like kernel issue and when you flash RR again, it will replace the custom kernel and you will have your RR kernel back.
Edit: you won't lose any data by this method.
Heeth21 said:
In these type of cases, flash RR on on top of your current ROM (without wiping anything i.e dirty flashing).
It seems like kernel issue and when you flash RR again, it will replace the custom kernel and you will have your RR kernel back.
Edit: you won't lose any data by this method.
Click to expand...
Click to collapse
Yeah, I tried that. I first wiped the data partition as instructed by the [URL="hthttps://android.stackexchange.com/questions/157601/marshmallow-not-bootlooping-but-not-starting]StackExchange post[/URL] then dirty flashed latest RR, but after waiting 10-15 minutes, I could still see those two messages (waiting for service sensorservice and waiting for AtCmdFwd). I have Nandroid backups of that bootlooped state but I'm kinda stumped on how to recover it at this point
matetoes said:
Yeah, I tried that. I first wiped the data partition as instructed by the [URL="hthttps://android.stackexchange.com/questions/157601/marshmallow-not-bootlooping-but-not-starting]StackExchange post[/URL] then dirty flashed latest RR, but after waiting 10-15 minutes, I could still see those two messages (waiting for service sensorservice and waiting for AtCmdFwd). I have Nandroid backups of that bootlooped state but I'm kinda stumped on how to recover it at this point
Click to expand...
Click to collapse
No, no need to wipe any partition......Just reflash RR without wiping anything except cache/dalvik.
And are you using some mods like Xposed? If yes, first flash their uninstalling zip from TWRP i.e uninstall them, then flash RR again(without wiping anything).
If that doesnt work too, then it doesn't seems like kernel issue.
Heeth21 said:
No, no need to wipe any partition......Just reflash RR without wiping anything except cache/dalvik.
And are you using some mods like Xposed? If yes, first flash their uninstalling zip from TWRP i.e uninstall them, then flash RR again(without wiping anything).
If that doesnt work too, then it doesn't seems like kernel issue.
Click to expand...
Click to collapse
I didn't using anything like Xposed. I had systemless root with Magisk and passed SafetyNet.
Actually, I did not wipe data, I just removed /data/system because some files like jobs.xml were empty and the phone didn't know how to start if those were empty. The reasoning was that if /data/system was gone, the phone would regenerate all those files and I could copy those files to my computer, restore the Nandroid backup before the removal of that folder, then copy back those files.
Alas, the phone still would not boot after removing /data/system so there must be some other problem going on (perhaps kernel issue, as you mentioned). I took Nandroid backups before and after every step I took so if you have any idea how to fix it we can always go back if something gets messed up.