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.
Related
Hi:
I unlocked and successfully rooted my Nexus 10 (JB 4.3). Also have TWRP 2.6.1 installed. It worked fine with the stock rom rooted. Then I tried to install Custom Rom.. Paranoid Android..3.99. Everything went smooth until.I got stuck in BOOTLOOP. Reading the forums posts, I went back to recovery and wiped cache/dalvik cache.. and rebooted.. This time it proceeded with the ANDROID IS UPGRADING...but at the end of this once I got the lock screen..the dreaded UNFORTUNATELY SYSTEM UI has STOPPED window pops up and this is where I am stuck.
I have since then booted into recovery and cleaned cache and reinstalled custom roms.. PA, STOCK, CM 10.2 many times but of no use. The tablet is stuck at the SYSTEM UI HAS STOPPED.
Is there any way to fix this... ? ANY HELP WILL BE GREATLY APPRECIATED
I would be glad to get back to FACTORY SETTINGS if I can. Note that I can push files from my MAC using "ADB" and then use recovery.
THANK YOU IN ADVANCE FOR YOU ALL.
Edit: Well guess what... I did not see FACTORY RESET in TWRP all along (BEING DEFAULT ACTION) and was just wiping cache/dalvik cache before rebooting. FACTORY RESET is a life saver.... it works. Hope this helps others in similar situation. I am back on CM 10,2 and running.
Excellent. That was gonna be my suggestion, but glad you got it figured out.
Sent from my Nexus 10
vicky4112 said:
/snip
Click to expand...
Click to collapse
In the future, learn to use fastboot. ADB only helps you if you have a custom recovery that can run ADB onboard, which isn't always the case (for example, if you kill your internal storage). What could have saved you here would have been:
fastboot wipe userdata
fastboot wipe data
fastboot update -w /path/to/stock-image.zip
It's harder to kill fastboot on Nexus devices, so it's worth learning.
Rirere said:
In the future, learn to use fastboot. ADB only helps you if you have a custom recovery that can run ADB onboard, which isn't always the case (for example, if you kill your internal storage
Click to expand...
Click to collapse
Alternatively, TWRP can mount an otg-usb device. Totally saved my tush the other night.
We’re excited to announce that we’ve released Remix OS 2.0 ROMs for Nexus 9 and Nexus 10. The Nexus 9 and Nexus 10 ROMs are now available for download here:
Nexus 9 ROM
http://www.jide.com/remixos/devices/nexus9
Nexus 10 ROM
http://www.jide.com/remixos/devices/nexus10
Flash Tutorial
http://support.jide.com/hc/en-us/articles/218081838
We’ve also been conscious of all the interest that Nexus 9 and 10 users have expressed in being able to experience Remix OS 2.0 on your tablets. And, although we’re still a relatively small team, we definitely heard your comments and are excited to finally have Remix OS 2.0 ready for you.
You can submit your bug report here:
http://bit.ly/1qh2jQq
Cheers
does this work on the lte variant?
Based on Android 5.11? No thanks.
I am not sure if I want to downgrade my nexus 9 to 5.11.
But Android 6.x and N are not good enough for me at least.
I am thinking if any other customize rom can be used.
Also Ubuntu for tablet might be a choice.
Any hopes of being able to load this via TWRP recovery? Or being able to load this via ADB while still keeping TWRP recovery?
Is there a possibility now to use google account and google services or still no?
Woofly said:
Any hopes of being able to load this via TWRP recovery? Or being able to load this via ADB while still keeping TWRP recovery?
Click to expand...
Click to collapse
You can fastboot flash while keeping twrp
maelfilk said:
Is there a possibility now to use google account and google services or still no?
Click to expand...
Click to collapse
It now comes with play store. Overall it's world's better than 1.5.
dictionary said:
You can fastboot flash while keeping twrp
It now comes with play store. Overall it's world's better than 1.5.
Click to expand...
Click to collapse
Sweet. Does it have Google Play Services as well? Are we able to run apps like Gmail and Play Music?
Woofly said:
Sweet. Does it have Google Play Services as well? Are we able to run apps like Gmail and Play Music?
Click to expand...
Click to collapse
Yes sir. Haven't tried play music, but running gmail and hangouts fine. When you fastboot flash things, just don't flash recovery. Also, I had to flash the old 5.1.1 bootloader and vendor first.
Anyone here NOT getting a bootloop after installing? what am i doing wrong here....
th3fallen said:
Anyone here NOT getting a bootloop after installing? what am i doing wrong here....
Click to expand...
Click to collapse
Working fine for me here. Was getting constant reboots and bootlooping before I flashed back to 5.1.1 first though. Bootloader and vendor especially. Then wiped everything but internal in TWRP, then fastboot flashed Remix except for twrp. Booted into TWRP before booting into the system. Worked great after that.
So does it work for LTE variant? Also anyone running custom kernel with it? (afaik FIRE-ICE has special kernel)
Bootloopers
To all those getting bootloop:
* Download latest 5.11 image LMY48T (not 6.x) https://developers.google.com/android/nexus/images#volantis
* In theory you only need to flash bootloader-flounder-3.44.1.0123.img however to be on the safe side I ran the whole ./flash-all.sh
* Now reboot the bootloader (even if you are already there, since we just flashed a different one), then run the following:
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash cache cache.img
# flashing vendor.img will solve the problem of annoying messages on boot/unstable play services
fastboot flash vendor vendor.img
# there is no userdata.img , so we can wipe userdata like so:
fastboot -w
* Now reboot and it should work great. With my experience so far it seems very stable
dictionary said:
Working fine for me here. Was getting constant reboots and bootlooping before I flashed back to 5.1.1 first though. Bootloader and vendor especially. Then wiped everything but internal in TWRP, then fastboot flashed Remix except for twrp. Booted into TWRP before booting into the system. Worked great after that.
Click to expand...
Click to collapse
Working fine for me here. Was getting constant reboots and bootlooping before I flashed back to 5.1.1 first though. Bootloader and vendor especially. Then wiped everything but internal in TWRP, then fastboot flashed Remix except for twrp. Booted into TWRP before booting into the system. Worked great after that.
Click to expand...
Click to collapse
That was my issue. Thanks
Bootloop on second boot
So after the tablet seemingly working perfectly and no boot loops on install, it is now only bootlooping after rebooting (even after wiping cache) And this is after installing 5.11 factory image before remix os.
Will try factory reset etc.
i am really interrested in this OS
but before i am doing anything i want to ask some questions
1) how far is google play and google play store integrated? can i open every app?
2) can i type without a manual keyboard?
3) is LTE supported in this version?
I will try this as soon as I get home. Can't wait to test it.
Fallon9111 said:
To all those getting bootloop:
* Download latest 5.11 image LMY48T (not 6.x) https://developers.google.com/android/nexus/images#volantis
* In theory you only need to flash bootloader-flounder-3.44.1.0123.img however to be on the safe side I ran the whole ./flash-all.sh
* Now reboot the bootloader (even if you are already there, since we just flashed a different one), then run the following:
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash cache cache.img
# flashing vendor.img will solve the problem of annoying messages on boot/unstable play services
fastboot flash vendor vendor.img
# there is no userdata.img , so we can wipe userdata like so:
fastboot -w
* Now reboot and it should work great. With my experience so far it seems very stable
Click to expand...
Click to collapse
What I find even easier, is to go into twrp. Do all the usual wipes (data, cache, dalvik, system), then reboot into bootloader. It'll say no OS installed in twrp, but that's fine. Then I fastboot flashed the 5.1.1 image manually, skipping recovery.img . Once done, I reboot recovery. It'll boot into twrp. (Doing this ensures that twrp won't be overwritten upon first boot). Then rebooted into 5.1.1. Just making sure it worked fine. Now reboot into twrp. Wipe the same things again, and this time install RemixOS. Again, reboot into twrp. Now reboot. Should be okay. I just don't like having to constantly reflash twrp. Either way works great though.
th3fallen said:
Working fine for me here. Was getting constant reboots and bootlooping before I flashed back to 5.1.1 first though. Bootloader and vendor especially. Then wiped everything but internal in TWRP, then fastboot flashed Remix except for twrp. Booted into TWRP before booting into the system. Worked great after that.
That was my issue. Thanks
Click to expand...
Click to collapse
No problem.
Fallon9111 said:
So after the tablet seemingly working perfectly and no boot loops on install, it is now only bootlooping after rebooting (even after wiping cache) And this is after installing 5.11 factory image before remix os.
Will try factory reset etc.
Click to expand...
Click to collapse
I've rebooted several times, including changing DPI, and no issues. I know you said you installed 5.1.1 prior, but did you do a complete wipe before flashing RemixOS?
oediv said:
i am really interrested in this OS
but before i am doing anything i want to ask some questions
1) how far is google play and google play store integrated? can i open every app?
2) can i type without a manual keyboard?
3) is LTE supported in this version?
Click to expand...
Click to collapse
1. I haven't tried every single app, nor will I, but gmail, hangouts, drive, Google+, all work fine.
2. You mean, is there an onscreen keyboard? If so, then yes. I haven't connected a hardware keyboard.
3. Not sure. Give it a try and let us know! It won't break LTE, so worst case scenario is you just flash back to whatever you had before.
---------- Post added at 10:11 PM ---------- Previous post was at 10:10 PM ----------
maelfilk said:
So does it work for LTE variant? Also anyone running custom kernel with it? (afaik FIRE-ICE has special kernel)
Click to expand...
Click to collapse
The current 10.2.1 Fire and Ice will cause boot loops and break Wi-Fi. Elemental X for 5.1.1 works fine though. Running it now.
dictionary said:
I've rebooted several times, including changing DPI, and no issues. I know you said you installed 5.1.1 prior, but did you do a complete wipe before flashing RemixOS?
Click to expand...
Click to collapse
Yeah, I did a full factory image thing, and even let it boot once into 5.1.1 before rebooting back to fastboot and installing remix. I'm not sure what caused the boot loop problem, (wiping the caches and even a factory reset from twrp didn't fix this), but after flashing factory images then installing everything a 2nd time, the tablet seems to be working fine. So I'm not really sure why it went wrong (looking back in my terminal history I don't spot any obvious errors)...
Fallon9111 said:
Yeah, I did a full factory image thing, and even let it boot once into 5.1.1 before rebooting back to fastboot and installing remix. I'm not sure what caused the boot loop problem, (wiping the caches and even a factory reset from twrp didn't fix this), but after flashing factory images then installing everything a 2nd time, the tablet seems to be working fine. So I'm not really sure why it went wrong (looking back in my terminal history I don't spot any obvious errors)...
Click to expand...
Click to collapse
Yeah that's odd. After I flashed 5.1.1 and let it boot, I rebooted to TWRP, and wiped data, cache, system, and dalvik. Then rebooted to bootloader, then fastboot, and flashed boot.IMG, system.IMG, cache.IMG and vendor.IMG. Didn't have an issue. Glad it's working now for you though.
I bought this phone used and the person who had it before me it rooted and installed some of different ROMs on it. After getting my used moto x pure 2015 running android 6.0. I booted it up and tested all the functions (including downloading a few apps) Wi-Fi, camera, audio/charging jacks ext. Everything worked fine. So did normal factory reset (not using TWRP) just to make sure everything was clean before using it as my daily. Then, (BUM BUM BUM!) when I tried to start downloading all my apps. None of them would download even though the Wi-Fi was working. Error 492 I think.
I started trying custom ROMs because I was having two big issues (apps not downloading and incoming call not bringing up accept/decline screen) with my stock rom. and wanted to fix those issues with a fresh stock image.
This is all new to me and has not been as easy as anticipated. If anyone knows a clean factory image I could flash or a fail proof fix to error 492 that would be helpful. I really just want to return to fully working Motorola stock android, but the files I have used haven’t fixed the issue. I have searched for a factory image without finding one…
Is there a way to flash the Motorola image through TRWP?
Otherwise, maybe you can help me with my flashing method, and maybe tell me what I am doing wrong. I tried to flash multiple stock images all with the same issue. I have also tried to flash Resurrection Remix, and Brocken OS, both having resulted in a bootloop. I am starting to think I have done something wrong. The steps I have taken so far have been these:
My bootloader is unlocked status code 3.
My phone is not rooted. Do I need root?
First I downloaded adb and fastboot.
Then I flashed TWRP (3.0.2).
I never installed the official Motorola stock image because flashing it from fast boot wouldn’t work and it couldn’t be flashed with TWRP because it is a .gz not a .zip. (I knew a .gz needs to be flashed with fastboot but I knew TWRP was easer so I didn’t fuss with it)
After flashing TWRP to my phone, I downloaded (yes, I checked the md5) the various ROMs to my computer then transfered them to my phone via micro SD card.
Here are the file’s names if that matters:
moto_x_pure_edition_stock_x1575_mphs24.49-18-3_v1-odexed
(booted and Wi-Fi but play store won’t download apps)
moto_x_pure_edition_stock_x1575_mph24.49-18_v1-odexed
(booted but no Wi-Fi)
Broken-v4.9.1-clark-6.0.1-OFFICIAL-20160824 (with Broken_gapps_lp5.1.x_09172015)
(Brocken was the only non-stock that got past boot, but I still couldn’t get past set up without an error and never made it to the system.)
ResurrectionRemix-N-v5.8.0-20161220-clark (7.1 gapps failed to flash but I booted it anyway.)
(boot loop after both of my tries)
I got Wi-Fi working on one of the above stock ROMs (so I KNOW it works) but couldn’t even turn Wi-Fi on in all the others.
The method I used to flash all of the above files in TWRP was:
Wipe
Full wipe (davlik cache, data, system, cache)
(used for RR and Brocken)
Factory reset (using TWRP) (davlik cache, data , cache)
Used for the stock ROMs or even after flashing .zip file I got the error: no OS installed.
Install
Select file of ROM flash (gapps if needed) and flash
I can’t remember which ones but on some of them after flashing I again did a factory reset.
Then I rebooted
Thanks for reading. Sorry it was so long. I tried to add as much useful information as possible. Hopefully someone smarter than me will see my error(s) and help me get my phone into fully working order.
cont.
I really just want to return to fully working Motorola stock android, but the files I have used haven’t fixed the issue. I have searched for a factory image without finding one…
Is there a way to flash the Motorola image through TRWP?
Otherwise maybe you can help me out with my flashing method and maybe tell me what I am doing wrong. I tried to flash multiple stock images all with the same issue. I have also tried to flash Resurrection Remix, and Brocken OS, both having resulted in a bootloop. I am starting to think I have done something wrong. The steps I have taken so far have been these:
My bootloader is unlocked status code 3.
My phone is not rooted. Do I need root?
First I downloaded adb and fastboot.
Then I flashed TWRP (3.0.2).
I never installed the official Motorola stock image because flashing it from fast boot wouldn’t work and it couldn’t be flashed with TWRP because it is a .gz not a .zip. (I knew a .gz needs to be flashed with fastboot but I knew TWRP was easer so I didn’t fuss with it)
After flashing TWRP to my phone, I downloaded (yes, I checked the md5) the various ROMs to my computer then transfered them to my phone via micro SD card.
Here are the file’s names if that matters:
moto_x_pure_edition_stock_x1575_mphs24.49-18-3_v1-odexed
(booted and Wi-Fi but play store won’t download apps)
moto_x_pure_edition_stock_x1575_mph24.49-18_v1-odexed
(booted but no Wi-Fi)
Broken-v4.9.1-clark-6.0.1-OFFICIAL-20160824 (with Broken_gapps_lp5.1.x_09172015)
(Brocken was the only non-stock that got past boot, but I still couldn’t get past set up without an error and never made it to the system.)
ResurrectionRemix-N-v5.8.0-20161220-clark (7.1 gapps failed to flash but I booted it anyway.)
(boot loop after both of my tries)
I got Wi-Fi working on one of the above stock ROMs (so I KNOW it works) but couldn’t even turn Wi-Fi on in all the others.
The method I used to flash all of the above files in TWRP was:
Wipe
Full wipe (davlik cache, data, system, cache)
(used for RR and Brocken)
Factory reset (using TWRP) (davlik cache, data , cache)
Used for the stock ROMs or even after flashing .zip file I got the error: no OS installed.
Install
Select file of ROM flash (gapps if needed) and flash
I can’t remember which ones but on some of them after flashing I again did a factory reset.
Then I rebooted
Thanks for reading. Sorry it was so long. I tried to add as much useful information as possible. Hopefully someone smarter than me will see my error(s) and help me get my phone into fully working order.
I think this thread will help you: https://forum.xda-developers.com/showthread.php?t=3489110
Sent from my XT1572 using Tapatalk
Install stock firmware via fastboot... if that dont fix the issue, install TWRP make a full wipe, FULL, and install the stock firmware again, eventualy that sould fix the issue.
RK2116 said:
Install stock firmware via fastboot... if that dont fix the issue, install TWRP make a full wipe, FULL, and install the stock firmware again, eventualy that sould fix the issue.
Click to expand...
Click to collapse
I'm having a similar issue. Tried the TruPure rom but I want to switch back to stock. If I do a full wipe, would I be able to use the files that Motorola provides on their website and flash those throught fastboot? Or through TWRP? Any chance you have a link to a guide on how to do the latter option (installing through TWRP)? I'm just trying to get my device back to 100% stock so that I can receive OTA.
cdiaz8 said:
I'm having a similar issue. Tried the TruPure rom but I want to switch back to stock. If I do a full wipe, would I be able to use the files that Motorola provides on their website and flash those throught fastboot? Or through TWRP? Any chance you have a link to a guide on how to do the latter option (installing through TWRP)? I'm just trying to get my device back to 100% stock so that I can receive OTA.
Click to expand...
Click to collapse
Odexed one, install with TWRP, full wipe before doing that, no GApps, just ROM, them, install stock recovery vía fastboot. After that you Will be stock with OTAs.
https://forum.xda-developers.com/mo...t/rom-marshmallow-6-0-september-2016-t3536120
RK2116 said:
Odexed one, install with TWRP, full wipe before doing that, no GApps, just ROM, them, install stock recovery vía fastboot. After that you Will be stock with OTAs.
https://forum.xda-developers.com/mo...t/rom-marshmallow-6-0-september-2016-t3536120
Click to expand...
Click to collapse
Thank you for sharing that link. I think I get it but it seems too easy considering what I've tried so far. Just to make sure I get it:
I should download the odexed rom, go to twrp and wipe data, cache and dalvik then flash the odexed rom through the install function? And thats it? I've literally tried a ton of stuff so if this takes care of it, this is great!
cdiaz8 said:
Thank you for sharing that link. I think I get it but it seems too easy considering what I've tried so far. Just to make sure I get it:
I should download the odexed rom, go to twrp and wipe data, cache and dalvik then flash the odexed rom through the install function? And thats it? I've literally tried a ton of stuff so if this takes care of it, this is great!
Click to expand...
Click to collapse
Yes, also wipe system, make a backup before If you want, but remember, for the OTAs support you need yo flash the stock recovery via fastboot. Good luck.
RK2116 said:
Yes, also wipe system, make a backup before If you want, but remember, for the OTAs support you need yo flash the stock recovery via fastboot. Good luck.
Click to expand...
Click to collapse
This got me back to stock! You are the real MVP.
So I remember seeing a recovery.img file in the factory image that motorola posted on its site. Does it have to be a specific stock recovery or do I need a specific one to match with the file I just installed?
thanks again
cdiaz8 said:
This got me back to stock! You are the real MVP.
So I remember seeing a recovery.img file in the factory image that motorola posted on its site. Does it have to be a specific stock recovery or do I need a specific one to match with the file I just installed?
thanks again
Click to expand...
Click to collapse
Just a stock one, if Motorola have one use that.
RK2116 said:
Just a stock one, if Motorola have one use that.
Click to expand...
Click to collapse
So I'm on stock build 49-18-8 and flashed the recovery from 49-18-3. I went into fastboot and selected recovery. I got the android character with an !
I then did the power button and volume up and got into stock android recovery. Am I supposed to see the android character with ! each time I try to reach the recovery menu? Just wondering if I did this correctly.
Thanks again for pointing me to these resources!
cdiaz8 said:
So I'm on stock build 49-18-8 and flashed the recovery from 49-18-3. I went into fastboot and selected recovery. I got the android character with an !
I then did the power button and volume up and got into stock android recovery. Am I supposed to see the android character with ! each time I try to reach the recovery menu? Just wondering if I did this correctly.
Thanks again for pointing me to these resources!
Click to expand...
Click to collapse
Yes.
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:
Hello everyone.
Today I decided to wipe my phone and install NucleaRom on it. Everything ran well for a few hours but eventually the device froze, so I rebooted into the bootloader and then into recovery to wipe and restore my backup. The problem is, when the phone tries to wipe the data partition it reboots back into the bootloader.
At this point, I cannot wipe the phone, restore a backup, or reinstall NucleaRom. I just want to get back to stock rooted 7.0, which is how it was yesterday.
Can anyone help me figure this out? I do not have a backup phone and am pretty desperate at this point!
I tried to reflash the stock NPH25.200-22 image using fastboot but I start getting errors and the phone freezes on the bootloader screen. Just completely puzzled! I've been tinkering with Android phones since 2010 and have never run into something this bad before.
I think your problem might be caused by how f2fs is implemented in unofficial TWRP and NucleaROM. It does something to the data partition that doesn't always play nice.
Warning, what I suggest here is going to format your whole data partition. If there's anything on it you'd like to keep, I'd suggest backing it up with TWRPs built-in file manager or over USB to a computer before attempting this.
If I were in your situation, here's what I'd try:
1) Download the latest official TWRP
2) Flash it with fastboot:
Code:
fastboot flash recovery twrp.img
3) Don't reboot normally. Use the volume rocker to select recovery and boot into it.
4) In TWRP select Wipe -> Advanced Wipe
5) Tick the Data box and then hit Repair or Change Filesystem
6) Select Change Filesystem
7) Select F2FS and let it format data
8) Reboot to bootloader and fastboot flash the full firmware package you were trying to. If you were already on that firmware or higher it is normal for bootloader and gpt.bin to fail, you can ignore those errors. Make sure every other step exits successfully, if not then repeat the step.
9) Reboot to system and cross your fingers
I'm not certain this will fix your problem, but if your phone is already non-booting, it isn't going to make it worse.
jason2678 said:
I think your problem might be caused by how f2fs is implemented in unofficial TWRP and NucleaROM. It does something to the data partition that doesn't always play nice.
Warning, what I suggest here is going to format your whole data partition. If there's anything on it you'd like to keep, I'd suggest backing it up with TWRPs built-in file manager or over USB to a computer before attempting this.
If I were in your situation, here's what I'd try:
1) Download the latest official TWRP
2) Flash it with fastboot:
Code:
fastboot flash recovery twrp.img
3) Don't reboot normally. Use the volume rocker to select recovery and boot into it.
4) In TWRP select Wipe -> Advanced Wipe
5) Tick the Data box and then hit Repair or Change Filesystem
6) Select Change Filesystem
7) Select F2FS and let it format data
8) Reboot to bootloader and fastboot flash the full firmware package you were trying to. If you were already on that firmware or higher it is normal for bootloader and gpt.bin to fail, you can ignore those errors. Make sure every other step exits successfully, if not then repeat the step.
9) Reboot to system and cross your fingers
I'm not certain this will fix your problem, but if your phone is already non-booting, it isn't going to make it worse.
Click to expand...
Click to collapse
Thank you for the suggestion! I made the attempt but once my phone tries to format the data partition, it vibrates for about 5 seconds and then reboots back to the bootloader. It has been doing this yesterday every time I would try it. Do you have any suggestions as to why this is, and how to correct it?
I've pretty much given up hope at this point and was going to order a new phone. But it would be nice to get this back in working order so I can resell it or trade it in for a discounted price. The phone has been really good to me over the years and, besides a slightly worn down battery, still works fairly well. Hate to see it turn into a paper-weight when the hardware is still working!
EDIT: Tried the same thing, but this time using ext4 and it worked! Going to try and manually flash the firmware and see what happens!
LyleFerguson said:
Thank you for the suggestion! I made the attempt but once my phone tries to format the data partition, it vibrates for about 5 seconds and then reboots back to the bootloader. It has been doing this yesterday every time I would try it. Do you have any suggestions as to why this is, and how to correct it?
I've pretty much given up hope at this point and was going to order a new phone. But it would be nice to get this back in working order so I can resell it or trade it in for a discounted price. The phone has been really good to me over the years and, besides a slightly worn down battery, still works fairly well. Hate to see it turn into a paper-weight when the hardware is still working!
Click to expand...
Click to collapse
Did you format with the latest official TWRP or the unofficial version of TWRP linked to the NucleaROM OP? There are differences. If one isn't working, try the other. I think it is just a matter of finding the right TWRP version to work with your data partition and reformatting it to fix it. I've also seen formatting it to ext4, then formatting it back to f2fs as a suggested fix for this.
If you just want to try different TWRP versions without constantly flashing new recoveries you can just boot into an image without actually flashing it with fastboot:
Code:
fastboot boot twrp.img
Others have had this problem of not being able to wipe before and solved it. Don't give up. I think you'll find the answer you're after in the official LOS thread or possibly the TWRP thread, but unfortunately with forums there's a lot of noise and the information is quite disjointed.
I've steered clear of the nougat firmware and rebased custom roms myself because it still seems to be in somewhat of a state of flux, so I don't have any firsthand experience with this.
jason2678 said:
Did you format with the latest official TWRP or the unofficial version of TWRP linked to the NucleaROM OP? There are differences. If one isn't working, try the other. I think it is just a matter of finding the right TWRP version to work with your data partition and reformatting it to fix it. I've also seen formatting it to ext4, then formatting it back to f2fs as a suggested fix for this.
If you just want to try different TWRP versions without constantly flashing new recoveries you can just boot into an image without actually flashing it with fastboot:
Code:
fastboot boot twrp.img
Others have had this problem of not being able to wipe before and solved it. Don't give up. I think you'll find the answer you're after in the official LOS thread or possibly the TWRP thread, but unfortunately with forums there's a lot of noise and the information is quite disjointed.
I've steered clear of the nougat firmware and rebased custom roms myself because it still seems to be in somewhat of a state of flux, so I don't have any firsthand experience with this.
Click to expand...
Click to collapse
I used the TWRP that you had linked me. Formatted using ext4 and then tried flashing the files manually with fastboot. My phone is now back to normal!