Related
I have had some issues with my phone since unlocking with sunshine. See separate thread http://forum.xda-developers.com/droid-turbo/help/help-bricked-xt1254-unlocking-to-t3279581 for description. I have a theory about this now and would like some opinions from folks with more experience.
I used device encryption on my Turbo before the OTA update to Lollipop. After encrypting the phone I would be prompted to enter my PIN to decrypt the data partition before the phone would boot, and then I'd have to enter the PIN again after boot to unlock it. After the OTA I no longer had to enter my PIN when booting the phone, but I would still have to enter it after boot to unlock. After the OTA the phone still reported that it was encrypted in the system security settings even though it didn't need a PIN to decrypt at boot time. That makes sense from what little I know because encrypting the device re-writes the data partition, and the OTA didn't touch the data partition and could not un-encrypt it. I was baffled by this, but I didn't want to factory reset and wipe the data partition to let me re-encrypt the phone.
So after the OTA, the data partition of my phone was still encrypted, but magically the phone was able to decrypt data and boot without my PIN. I don't know why. But one clue is that after unlocking and installing TWRP I looked at TWRP log and saw a log message saying something about decrypting with default PIN. Anyway, I never wiped data, but my phone somehow manages to boot. Re-flashing system and recovery caused problems at first, but now it seems to be back to the way it was. I haven't flashed a new ROM yet, but I expect that when I do I'll have to wipe data and that will get everything back to normal.
My question is has anyone else experimented with device encryption and is this behavior expected?
Thanks.
Not having to enter a PIN with the factory image was a bug I initially discovered, and reported, during the *initial* Android L SOAK test. Needless to say, they never fixed the bug (plus one of the Stagefright CVEs) during the second SOAK rollout. I reported it then, too. They did nothing. That second SOAK was the straw that broke the camel's back, for me. I will never participate in another.
As far as this bug goes, what I would do, is an FDR, and re-encrypt your device to wipe the key store and start over.
Sent from my DROID Turbo via Tapatalk. Now with that cyanogenmod goodness.
I got notifications that the SU4TL-49 OTA was ready to install on my phone, and I had read that if you try to install it with anything but stock recovery that you get into a boot loop. I figured it was a matter of time before I ended up accidentally installing the OTA upgrade and so decided to wipe my phone and go back to stock, and I would use that opportunity to re-encrypt the phone. It took me a couple of tries before I discovered that factory reset isn't enough to remove the encryption, and that I had to reformat the data partition. This took a few hours of going back and forth between reverting to stock, upgrading, rooting, configuring and starting over before I finally got it right, but eventually the phone said that it wasn't encrypted and gave me the option to encrypt. What a pain. After setting up all my apps for the third or fourth time I thought I was done. Whenever I rebooted I was prompted for my PIN before android booted. I even had to enter my PIN to run TWRP.
At least that's the way it was for a few hours. Now when I reboot it just starts up android with no password again. All the effort to un-encrypt and re-encrypt seems to have been a waste. Oh well, at least I avoided getting into boot loop hell.
Hopefully this unencrypting without requiring password/PIN thing gets fixed when (if) they come out with M for the turbo.
This just keeps getting better and better. I decided to flash the Unofficial CM13 ROM this afternoon just for fun. I got it all set up when I found that the GPS receiver wasn't working. Searching the thread I found a link to a flash-able radio image to fix that, and when I rebooted to TWRP it prompted me for a password to decrypt the data partition! Unfortunately it didn't like my PIN no matter how many times I entered it. I don't know if there's something about entering a numerical PIN on the qwerty keyboard, but it had worked earlier in the day before it stopped prompting for passwords. After a bunch of tries and reboots I gave up and downloaded a fastboot flashable version of the same. I've spent most of the day screwing around with this phone already and I'm not going to reformat the data partition again today for sure! Maybe it just needs a good night's sleep.
Astrobrewer said:
This just keeps getting better and better. I decided to flash the Unofficial CM13 ROM this afternoon just for fun. I got it all set up when I found that the GPS receiver wasn't working. Searching the thread I found a link to a flash-able radio image to fix that, and when I rebooted to TWRP it prompted me for a password to decrypt the data partition! Unfortunately it didn't like my PIN no matter how many times I entered it. I don't know if there's something about entering a numerical PIN on the qwerty keyboard, but it had worked earlier in the day before it stopped prompting for passwords. After a bunch of tries and reboots I gave up and downloaded a fastboot flashable version of the same. I've spent most of the day screwing around with this phone already and I'm not going to reformat the data partition again today for sure! Maybe it just needs a good night's sleep.
Click to expand...
Click to collapse
Encryption is totally broken on CM13. The issue is that our version of TWRP cannot decrypt it. I contacted the maintainer of TWRP for our device about this issue and he said that he tried to fix the issue, but he failed.
Also, official CM13 has been out for a while now for the Turbo. No need to go with the unofficial version.
Thanks for the info @TheSt33v, but I'm not sure that it's totally broken.
The strange thing is that I was using TWRP 3.0.2 just fine after encrypting phone while on stock ROM, and it worked for a while even after flashing CM13. Then it just stopped liking my PIN. But CM13 takes my PIN and decrypts data just fine. So my phone is usable for now, and the problem of it decrypting without asking for a PIN is solved for now. I just went to cyanogenmod and see that there's a CM13 recovery. Based on your post I'm guessing that's what is broken, so no point in flashing that. Oh well, at least my phone is secure.
Astrobrewer said:
Thanks for the info @TheSt33v, but I'm not sure that it's totally broken.
The strange thing is that I was using TWRP 3.0.2 just fine after encrypting phone while on stock ROM, and it worked for a while even after flashing CM13. Then it just stopped liking my PIN. But CM13 takes my PIN and decrypts data just fine. So my phone is usable for now, and the problem of it decrypting without asking for a PIN is solved for now. I just went to cyanogenmod and see that there's a CM13 recovery. Based on your post I'm guessing that's what is broken, so no point in flashing that. Oh well, at least my phone is secure.
Click to expand...
Click to collapse
Just FYI, our TWRP maintainer has fixed decryption. You can get the latest version here: https://www.androidfilehost.com/?w=files&flid=39562 (version 3.0.2-0 mod 02 as of this writing). I still had trouble decrypting a partition that was previously formatted using the stock recovery menu, but once I formatted the data partition using this version of TWRP and re-encrypted, it decrypted fine.
TheSt33v said:
Just FYI, our TWRP maintainer has fixed decryption...
Click to expand...
Click to collapse
Yes they have fixed it! I found TWRP Mod 2 over the weekend and saw from the change log that decryption was fixed. I flashed it and it works great. No problems decrypting my previously encrypted data partition since I flashed mod 2. The funny thing about it is that basic TWRP 3.0.2 (no mod) worked well enough for long enough for me to flash CM13, and it even seemed to work for a little while after that. But then it decided that it didn't know how to decrypt my phone anymore and I was stuck until Mod 2. I can't explain why it worked for a while and then stopped, but I'm very happy that mod 2 fixed it.
Thanks for your help and support. Sometimes I feel like I'm the only user who encrypts his phone. There don't seem to be a lot of threads about encryption/decryption issues.
Astrobrewer said:
Yes they have fixed it! I found TWRP Mod 2 over the weekend and saw from the change log that decryption was fixed. I flashed it and it works great. No problems decrypting my previously encrypted data partition since I flashed mod 2. The funny thing about it is that basic TWRP 3.0.2 (no mod) worked well enough for long enough for me to flash CM13, and it even seemed to work for a little while after that. But then it decided that it didn't know how to decrypt my phone anymore and I was stuck until Mod 2. I can't explain why it worked for a while and then stopped, but I'm very happy that mod 2 fixed it.
Thanks for your help and support. Sometimes I feel like I'm the only user who encrypts his phone. There don't seem to be a lot of threads about encryption/decryption issues.
Click to expand...
Click to collapse
Most people don't seem to think it's worth the impact that it has on performance.
I was worried about the performance hit too before I tried it. But I don't notice any real difference in performance. Of there is a hit it's too small for me to tell.
Sent from my DROID Turbo using XDA-Developers mobile app
Astrobrewer said:
I was worried about the performance hit too before I tried it. But I don't notice any real difference in performance. Of there is a hit it's too small for me to tell.
Sent from my DROID Turbo using XDA-Developers mobile app
Click to expand...
Click to collapse
This is a very interesting thread. I would like to encrypt so I can setup my work exchange email as its a requirement. Just to clarify what is the order to do this in? Currently I am running RR 6.01 but have run CF's 1.3.6 ROM most of the time as its awesome.
Can I encrypt using RR or do I need to switch back to CFs ROM or to stock Lollipop after installing the upgraded TWRP in place of the standard version I am running now?
thanks for the help and information.
oldidaho said:
This is a very interesting thread. I would like to encrypt so I can setup my work exchange email as its a requirement. Just to clarify what is the order to do this in? Currently I am running RR 6.01 but have run CF's 1.3.6 ROM most of the time as its awesome.
Can I encrypt using RR or do I need to switch back to CFs ROM or to stock Lollipop after installing the upgraded TWRP in place of the standard version I am running now?
thanks for the help and information.
Click to expand...
Click to collapse
You can encrypt on RR. Just make sure you're running TWRP version 3.0.2-0 mod 2: https://www.androidfilehost.com/?w=files&flid=39562
If encryption fails, you'll need to format your data partition (aka do a factory reset) using this version of TWRP. Then it will work.
TheSt33v said:
You can encrypt on RR. Just make sure you're running TWRP version 3.0.2-0 mod 2: https://www.androidfilehost.com/?w=files&flid=39562
If encryption fails, you'll need to format your data partition (aka do a factory reset) using this version of TWRP. Then it will work.
Click to expand...
Click to collapse
thanks so much for the clarification! Being encrypted, how does that affect installing future updates or restores? Can I still flash ROMS and other ZIPS from TWRP the same as now?
oldidaho said:
thanks so much for the clarification! Being encrypted, how does that affect installing future updates or restores? Can I still flash ROMS and other ZIPS from TWRP the same as now?
Click to expand...
Click to collapse
The only difference is that you'll have to enter your password/pin every time you boot twrp. Don't try to use a pattern lock. Everything else will be the same.
TheSt33v said:
The only difference is that you'll have to enter your password/pin every time you boot twrp. Don't try to use a pattern lock. Everything else will be the same.
Click to expand...
Click to collapse
thank you for the help! I was able to encrypt my RR MM install without having to wipe the data partition. It now prompts me to put my PIN in when booting up and when going into the modded version of TWRP. It then is able to decrypt the partition in TWRP so as you said just like before. Only difference is a little longer boot up time. Performance seems the same to me.
oldidaho said:
thank you for the help! I was able to encrypt my RR MM install without having to wipe the data partition. It now prompts me to put my PIN in when booting up and when going into the modded version of TWRP. It then is able to decrypt the partition in TWRP so as you said just like before. Only difference is a little longer boot up time. Performance seems the same to me.
Click to expand...
Click to collapse
Guess I spoke too soon. phone was working fine for a day. Yesterday at work I'm looking at my phone as it reboots on its own (just sitting there). I then get cant decrypt partition message. Cant do anything and it wont boot up into the OS WO giving this error. In TWRP still cant do anything because it cant decript the partition. So I formatted the data partition and started over. I had saved a recent backup to my PC so I was able to get back to that. Now running CFs latest instead of RR. I need my phone, cant take a chance on this happening again as I was instantly dead in the water. Just wont encrypt.
oldidaho said:
This is a very interesting thread. I would like to encrypt so I can setup my work exchange email as its a requirement. Just to clarify what is the order to do this in? Currently I am running RR 6.01 but have run CF's 1.3.6 ROM most of the time as its awesome.
Can I encrypt using RR or do I need to switch back to CFs ROM or to stock Lollipop after installing the upgraded TWRP in place of the standard version I am running now?
thanks for the help and information.
Click to expand...
Click to collapse
oldidaho said:
thank you for the help! I was able to encrypt my RR MM install without having to wipe the data partition. It now prompts me to put my PIN in when booting up and when going into the modded version of TWRP. It then is able to decrypt the partition in TWRP so as you said just like before. Only difference is a little longer boot up time. Performance seems the same to me.
Click to expand...
Click to collapse
oldidaho said:
Guess I spoke too soon. phone was working fine for a day. Yesterday at work I'm looking at my phone as it reboots on its own (just sitting there). I then get cant decrypt partition message. Cant do anything and it wont boot up into the OS WO giving this error. In TWRP still cant do anything because it cant decript the partition. So I formatted the data partition and started over. I had saved a recent backup to my PC so I was able to get back to that. Now running CFs latest instead of RRI need my phone, cant take a chance on this happening again as I was instantly dead in the water. Just wont encrypt.
Click to expand...
Click to collapse
Well, just as you used CM13 Marshmallow and RR Marshmallow just fine without encryption, not sure why you went to CF Lollipop instead of RR just because encryption didn't work. It just seems you were implying it's CM13 or RR at fault when you used them just fine before, and even now on CF you are NOT using encryption.
But it's your phone, so you can run what you want.
I do commend you for having a recent backup on your PC.
ChazzMatt said:
Well, just as you used CM13 and RR just fine without encryption, not sure why you went to CF instead of RR just because encryption didn't work. But it's your phone.
Just not sure why you are implying it's CM13 or RR at fault when you used them just fine before, and even now on CF you are NOT using encryption.
I do commend you for having a recent backup on your PC.
Click to expand...
Click to collapse
I should have clarified, I dont think RR had anything to do with my issue. I actually really liked RR, it has some great features, great performance and good battery life too. I just missed the Moto features in the stock and CFs ROMs.
oldidaho said:
I should have clarified, I dont think RR had anything to do with my issue. I actually really liked RR, it has some great features, great performance and good battery life too. I just missed the Moto features in the stock and CFs ROMs.
Click to expand...
Click to collapse
Strange. I've been using RR M encrypted for several weeks now with no issues. Oh well. If you're happy with modified stock, that's all that matters. You can encrypt that too if you like. I'm a big fan of the Moto features as well, and RR M has basically all of them built in besides Voice (chop chop flashlight was removed for a while, but it has been added back). Although I've never understood what Voice offers that Google Now does not.
Mystery solved!
Astrobrewer said:
... At least that's the way it was for a few hours. Now when I reboot it just starts up android with no password again. All the effort to un-encrypt and re-encrypt seems to have been a waste. Oh well, at least I avoided getting into boot loop hell.
Hopefully this unencrypting without requiring password/PIN thing gets fixed when (if) they come out with M for the turbo.
Click to expand...
Click to collapse
I have been running the CM13 ROM for the past few months and it's been great, but now that Verizon came out with official Marshmallow I decided to go back to a stock-based ROM again because I've been missing VOLTE. So I flashed ComputerFreak274_MM. After flashing and rooting I was back in the stupid state of the phone saying that it was encrypted but booting without a PIN. It seemed unreal that Moto/Verizon would have left this bug in MM too. So I reformatted data, re-flashed and rooted the ROM and tried encrypting. Then I discovered that it won't encrypt if it's rooted. So back to wiping, re-formatting and flashing again, but this time I am able to successfully encrypt before rooting. Success! Now root and start setting up the phone. Now I have to enter my PIN before it will boot into the system or into TWRP. Yay! By now it's 1:00am and I have to be at work early, so I let it sit overnight while my apps download. In the morning I flash SuperSU and notice that I wasn't prompted for a password to decrypt when I booted into TWRP and I wasn't prompted for password when booting system after flashing SuperSU. WTF!!! More time wasted. It seemed that stock ROMs just don't like encryption. :crying:
Anyway, after stewing about it all day I randomly chanced into the solution. In the Security settings menu there's an option under Encryption called "Secure start-up" which only becomes available when phone is encrypted. The Secure start-up options says:
"You can further protect this device by requiring your PIN before it starts up. Until the device starts up, it can't receive calls, messages, or notifications, including alarms. This helps protect data on lost or stolen devices."Secure start-up defaults to disabled for some reason, and when it's disabled the phone automatically decrypts itself when it boots without requiring PIN entry. So you can encrypt your phone and still be totally unprotected. What a dumb-ass default!
But when I enable Secure start-up then encryption works the way it should -- with phone prompting for PIN before booting. Maybe I just didn't notice it, but I didn't see anything when I encrypted the phone saying to enable Secure start-up to actually protect the phone. I'm guessing that this option was there in Lollipop too; but who knew???
After more than 10 months after release, BLU has promised on delivering the marshmallow update. I just saw the notification today at around 4:00PM CMT.
Currently updating!
9000RPM said:
After more than 10 months after release, BLU has promised on delivering the marshmallow update. I just saw the notification today at around 4:00PM CMT.
Currently updating!
Click to expand...
Click to collapse
Screen Shots Please....
I just updated last night. Everything running smoothly. I had the phone rooted previously but the one click root app got removed in the update process. If anyone has success rooting after the upgrade, I'd love to know about it.
I upgraded this morning and I've been having lots of issues with my installed apps, like Facebook, Messenger, Whatsapp and more, and of course I lost Root which was previously accomplished by KingRoot which doesn't work anymore.
Also I noticed that during the update process, particularly while flashing the firmware, it was flashed using my TWRP recovery and afterwards it got removed.
I'm sure that if I start fresh by performing a factory reset, all will be fluid and in working order, minus TWRP and Root of course, at least for the time being.
All in all, the update to Mashmellow seems to be awesome, some new features.
Cheers!
I'm having issues with the update. It downloads just fine and when I go ahead and try to install...it just spins around on "unzipping" and then proceeds to restart..or turn off for that matter. The phone turned off...I didn't do anything to it just let it sit there for a while and then I saw the charge icon show up (the one you see when the phone is off and charging) at which point I started the phone up. The phone did not update and I can basically repeat the process. There is 4.30 GB of space free and no SD card. What do I do?
EDIT:
So I tried again, kept at it and it eventually worked. Updated just fine but now there are doubles of all folders in the phone. When I plug it into my computer, all the folders (Music, Download etc etc) are showing up twice with the same contents in the each of them...
What...is...going...on?
Was pretty laggy at first. Decided back up my files and do a factory reset. Works much better now.
disChapo said:
Was pretty laggy at first. Decided back up my files and do a factory reset. Works much better now.
Click to expand...
Click to collapse
Yeah, mine is working flawlessly after a factory reset! Much improvement compared to Lollypop!
Anyone found a Root for Marshmellow yet?
Unless Blu changed something other than the interface I'd guess TWRP won't be working on MM anytime soon. It's a problem seen in the Gionee phone and I would expect the same to happen to the Blu. As for root and a custom recovery (although not a great one) you could try following these instructions: https://forum.hovatek.com/thread-15270.html
I've played a bit with the Gionee Marshmallow firmware on my Vivo XL during the past month or so, and one thing that really bugs me is that it seems to be shipping with a kernel that is way older than it should be on an MM release. And the OTA service that is known for leaking info also seemed to still be present in the updated firmware.
Can someone who's got the Blu update check if these two things are the same for the Blu release please? Enter device info in the settings menu and check the Kernel version for me. And, if you guys manage to get root, check if AdupOTA is still lurking in there.
batoussai said:
Can someone who's got the Blu update check if these two things are the same for the Blu release please? Enter device info in the settings menu and check the Kernel version for me.
Click to expand...
Click to collapse
Kernel Version: 3.18.19
Build Number: MRA58k
Custom build version: BLU_V0030UU_V07_GENERICM14-11-2016
Does anybody with TWPR/root upgraded to official 6.0 successfully? What's exact procedure/steps?
I have my Blu Vivo XL with TWRP now, in last (small) OTA update a few months ago, I tried flashing back to original recovery and rom, but still failed OTA.
I feel like the answer is a really obvious No. I've tried to google around but honestly not seeing a definitive answer. Is there hope? Am i just a noob? Would I use a custom rom, are there any surefire custom solutions for a closet to factory edition?
Klownicle said:
I feel like the answer is a really obvious No. I've tried to google around but honestly not seeing a definitive answer. Is there hope? Am i just a noob? Would I use a custom rom, are there any surefire custom solutions for a closet to factory edition?
Click to expand...
Click to collapse
I don't know of any reason why you can't just download the NBD91P image from here and flash each partition manually from the bootloader using fastboot, or download the NBD91P OTA image from here and flash it following the instructions on that page. I haven't heard or read anything at all that the stock factory image won't work on a T-Mobile Nexus 6.
Edit: If you haven't manually flashed an image before I have always used the instructions under "Method 2 : (Long, but works always)" on this page.
I would just load the OTA. There isn't any issues with it on t-mobile. was running the stock ROM for awhile. Now testing out CM14.1
I'm on nitro 7.1.1 on tmo with zero issues. Been flashing DP and no issues either in the past.
Sent from my Nexus 6 using XDA-Developers mobile app
ozzmanj1 said:
I'm on nitro 7.1.1 on tmo with zero issues. Been flashing DP and no issues either in the past.
Sent from my Nexus 6 using XDA-Developers mobile app
Click to expand...
Click to collapse
Hello I am also on nitro 7.1.1 on tmo. I cannot make or receive calls. I can but no sound and call automatically disconnects at 17 seconds. Also when pushing call button signal drops to hspsa. Then up again when it disconnects. Any idea on how to fix calls? Any info is greatly appreciated thank you.
Dopemusic89 said:
Hello I am also on nitro 7.1.1 on tmo. I cannot make or receive calls. I can but no sound and call automatically disconnects at 17 seconds. Also when pushing call button signal drops to hspsa. Then up again when it disconnects. Any idea on how to fix calls? Any info is greatly appreciated thank you.
Click to expand...
Click to collapse
I've never had any issues. My wife and nephew and older brother all have nexus 6 phones with nitro installed and have had zero issues on Tmo. Off hand have you checked your APN settings? Have you tried a fresh clean install? When I do a clean install I go and wipe, data, system, cache, etc, but leave internal storage alone. I know it gets wiped on install but I do it anyways to be sure. Other then checking APN settings and or fresh install I am stumped why anyone should be having issues. Sorry I can't give more insight. I guess the other issue could be your radio ....May want to look into flashing a different radio to see how it fares
Edit -. Link for flashable radios
http://forum.xda-developers.com/showthread.php?t=3066052
Hope any of these suggestions help
Sent from my Nexus 6 using XDA-Developers mobile app
So 7.0 just OTA'ed for me today 3/10/17. Given the recent issues with 7.1 I'm kind of OK with that.
Note10Dude - what 7.0.0 OTA or Factory Image do you find works well with T-Mobile? I think my radios are funky with 7.1.1 N6F26U - thanks in advance.
Note10.1Dude said:
So 7.0 just OTA'ed for me today 3/10/17. Given the recent issues with 7.1 I'm kind of OK with that.
Click to expand...
Click to collapse
What I wound up doing was go to the T-Mobile page and established the official latest factory image was 6.0.1 MMB29K - installed that using Wugfresh. After installing and logging into WiFi and my Gmail account was prompted to install 7.0.0 NBD92G - this installed fine and then after installing a couple of security updates was able to Re-Lock my Bootloader (I wanted Android Pay to accept my credit cards). Data reception is still degraded significantly, am now thinking there is a problem with the tower.
voyageurs60 said:
Note10Dude - what 7.0.0 OTA or Factory Image do you find works well with T-Mobile? I think my radios are funky with 7.1.1 N6F26U - thanks in advance.
Click to expand...
Click to collapse
I just posted this same response in a separate, but similar thread.
It's likely, in doing your updates, the modern (radio) software was updated as well. The modems are OS version independent and you may now have one that doesn't work as well for you as your original one did. You may not know which one you started with, but you could just try several to see if any improve the situation for you. Here are flashable zips of many of the modems.
You might also double check your APN settings against TMO website. I use Sprint, so no APNS, thus I can't really give you a step thru. If you search though, it's not an uncommon discussion.
I have build number NBD92G. No issues for me; I took it as an OTA. It has baseband MDM9625_104670.31.05.42R. T-mo did not push a May security update that I am aware of; I hope that indicates they are trying to validate a 7.1.1.
So, T-mobile is still on 92G for the last 3 months without security update. With the rumors of 7.1 being pushed again, anybody seeing anything? We will be EOL in October for security updates, and I plan to side-load the final one if T-mobile doesn't push it, but I do think they should be doing their job and letting our phones take the latest updates.
I successfully rooted my droid (that came with lollipop), using this guide
https://forum.xda-developers.com/droid-turbo/general/guide-how-to-unlock-bootloader-install-t3292684
installed twrp backed up the stock OS and installed resurrection remix lollipop rom. I did not install any different modems or radios as I planned to stay on lollipop.
Everything worked great yet after a day or two the display/phone would appear to lock up. I can press power, the display doesn't come on and when (usually) moving the the volume up/down I do hear sounds. Sometimes at this point it will reboot by itself, other times I have to reboot it.
When it comes up it goes through the android is upgrading thing, and sometimes works fine after, sometimes not, regardless eventually this problem repeats.
Thinking it was perhaps RR I tried straight Cyanogenmod, and eventually the rooted stock OS, both have this same problem.
I've tried using it with very minimal installed in the way of apps, same issue.
I've tried saving the log to SD to peer at later, but going through it I don't really see anything obvious to show what the problem is.
I"m wondering if there's a problem with the phone itself (it's a refurb) and am considering unrooting it and returning it.
Anyone seen this or thoughts on what might be the issue?
p.s.
if you happen to have a good link handy to an unrooting guide you might shoot it my way thanks.
thanks in advance!
What versions of the other ROMs did you use? Lollipop also, or Marshmallow? Nougat? For rooted stock ROM did you upgrade to Marshmallow? None of the Lollipop ROMs are supported anymore, so hard to answer for those.
There are ways to grab logs after a reboot, but here's another suggestion...
I use Auto Reboot app (needs root) to schedule a reboot my phone every day while I'm asleep.
This seems to keep the cobwebs cleared out, so the phone runs better. I know you want to find the issue, but maybe it's an accumulation of apps not releasing RAM orb something. This might help prevent that.
thanks for the reply
ChazzMatt said:
What versions of the other ROMs did you use? Lollipop also, or Marshmallow? Nougat? For rooted stock ROM did you upgrade to Marshmallow? None of the Lollipop ROMs are supported anymore, so hard to answer for those.
Click to expand...
Click to collapse
I tried the last released CM lollipop snapshot, as well as the last nightly.
For RR it was last released, "ROM OS Version: 5.1.x Lollipop"
ChazzMatt said:
There are ways to grab logs after a reboot,
Click to expand...
Click to collapse
Yeh I've been saving it to the SD so I can view it after a reboot, I've looked at 4 or 5 of them after the problem occurred and at least to me nothing really stood out
ChazzMatt said:
but here's another suggestion...
I use Auto Reboot app (needs root) to schedule a reboot my phone every day while I'm asleep.
This seems to keep the cobwebs cleared out, so the phone runs better. I know you want to find the issue, but maybe it's an accumulation of apps not releasing RAM orb something. This might help prevent that.
Click to expand...
Click to collapse
Yeh I expect it might periodically need a reboot but if it's just unpredictiably locking up or rebooting on its own it's not very usable.
I think I'm just going to have to try to unroot and return, maybe I'll go with a LG V20 as I don't want to have pay to re-root another one of these and possibly have same issue. Also the whole pay to have some app do something secret to my phone does leave me a bit uneasy.
Kind of a bummer as I'm actually pretty impressed with this device, fast, good battery, takes nice photos, only drawbacks for me are no removable SD and lack of LED notification, but I was willing to live without those given how good everything else was.
thanks
Same here,
I tried with different Roms 7.X, still blocking and display not turning on.
I'd appreciate some help.
Thanks!
Android Version: 7.1.2
Current Rom: AOKP
Kernel: 3.10.107-Stock-bhb27-nougat-kerneL
MrN00b said:
Same here,
I tried with different Roms 7.X, still blocking and display not turning on.
I'd appreciate some help.
Thanks!
Click to expand...
Click to collapse
FWIW and in case it helps you or someone else, I seem to have fixed mine finally, here's what I did.
First I installed latest twrp (mod 4) https://androidfilehost.com/?w=files&flid=39562 (there's a thread on this twrp if you want tor read on it). That in itself didn't fix the issue but did finally let me format and got rid of an 'mkfs.f2fs: invalid option -- r, ERROR=1' type error I used to get.
I installed this stock zip from twrp as described in thread:
https://forum.xda-developers.com/droid-turbo/development/rom-su4tl-49-100-stock-t3390041
It would never actually boot it would shut my phone off not long after showing the boot screen, and I'm not sure if doing that was necessary or not.
Taking some suggestions from here:
https://forum.xda-developers.com/droid-turbo/help/help-request-custom-rom-phone-unlocked-t3767070
I dug up the last official CM 13 snapshot:
https://www.google.com/search?q=cm-13.0-20161221-SNAPSHOT-ZNH5YAO3Y5-quark.zip
sha1: 9a219dd487c27e51b0c5c4922812838f394099c5
Wipe and installed with no gapps and voilà it would boot consistently. Without reinstalling I tried installing pico gapps and it would still boot though it took maybe 15 mins initially.
I want Nougat so I wiped and installed lineage-14.1-20180612-UNOFFICIAL-quark.zip from https://forum.xda-developers.com/moto-maxx/development/rom-t3494646 again no gapps and it also booted fine, whereas previously it would hang on booting. Without reinstalling ROM I tried installing opengapps nano and it would just hang.
I could then no longer get it to boot again, so I reinstalled CM13 no gapps, which booted fine, wipe and install lineage-14.1-20180612-UNOFFICIAL-quark.zip no gapps, and now it boots fine though currently it's taking a while.
I should perhaps note I took twrp backups inbetween steps whenever I had a working boot, (ex before installing gapps), but once the phone went back to hanging on boot, those restores didn't help. Only reflashing CM13 seemed to clear things up.
My ultimate goal is a LOS ish Nougat/Oreo ROM with no gapps using microg, and running tmobile, I'll see what I end up with.
The T-Mobile website is showing the update is complete and it is going out to devices. Has anyone received the update?
OnePlus 7 Pro: Update to Android 11
OnePlus 7 Pro Software version: Android 11 Phase: Complete The software has been approved to launch and is now available. When it's ready for you, your device will provide a notification that t
www.t-mobile.com
Wondering if anyone has taken the update and been able to keep root and TWRP.
Edit: Just getting the update now. Will let you know how it goes.
Edit 2: I was not able to keep root and TRWP, the update installs after it restarts so flashing the TWRP retention script then Magisk into inactive slot just cause the update to fail. Will have to boot TWRP then install both liked normal I hope...
Please update us. I just installed the global firmware a couple weeks ago on my t-mobile unit and haven't had great battery life so I might switch back but want to keep root
_-..zKiLLA..-_ said:
Please update us. I just installed the global firmware a couple weeks ago on my t-mobile unit and haven't had great battery life so I might switch back but want to keep root
Click to expand...
Click to collapse
Battery life is great, not having the same issues I had with the beta/international firmware except I am still having issues with calls coming through the stereo speaker and not the phone ear speaker.
Also, I can't get TWRP to boot so I can't install TWRP and root with Magisk. I've tried the TWRP from the forum and the latest from the TWRP website.
DylanTheVillian said:
Battery life is great, not having the same issues I had with the beta/international firmware except I am still having issues with calls coming through the stereo speaker and not the phone ear speaker.
Also, I can't get TWRP to boot so I can't install TWRP and root with Magisk.
Click to expand...
Click to collapse
Does that mean we need the update file? I haven't come across much info on rooting our stock t-mobile roms nor have I seen them for download
_-..zKiLLA..-_ said:
Does that mean we need the update file? I haven't come across much info on rooting our stock t-mobile roms nor have I seen them for download
Click to expand...
Click to collapse
I will try some more versions of TWRP tonight hopefully. I had to stop and work. E should be able to use the normal process, just need a working TWRP.
Twrp isn't supported for oos11 on 7 series yet
I haven't seen the rom to download...but switching to inactive slot should work....for magisk...if not...search how to extract n patch boot.img with payload dumper and magisk....I did it super easy...however...while doing I decided to install magisk to inactive slot (Global) and install keep_data.apk n all went well ...so I didn't have to push the rooted boot.img externally
DylanTheVillian said:
Battery life is great, not having the same issues I had with the beta/international firmware except I am still having issues with calls coming through the stereo speaker and not the phone ear speaker.
Also, I can't get TWRP to boot so I can't install TWRP and root with Magisk. I've tried the TWRP from the forum and the latest from the TWRP website.
Click to expand...
Click to collapse
Same issue with the speaker here too.. this is on a virgin/untouched t-mobile 7pro
I'm on a stock phone with the calls only coming through speakerphone issue as well. Is there a known workaround?
to the guys having that speaker issues are you guys having black screen issues at 90hz and wake up issues at full resolution?
because I have those all those.
Danton1316 said:
I'm on a stock phone with the calls only coming through speakerphone issue as well. Is there a known workaround?
Click to expand...
Click to collapse
Saw this on the OnePlus forum. For those with the issue where the callers voice comes out the microphone instead of the earpiece, here is something to try: "Stop HearingAidService under Bluetooth running services in Developer options under system. I had the same issue. Hearing aid services are being turned on without Bluetooth being on." Someone on the forum tried it with success. I have gone back to 10 so I cannot test it.
Danton1316 said:
I'm on a stock phone with the calls only coming through speakerphone issue as well. Is there a known workaround?
Click to expand...
Click to collapse
toggling the bluetooth on and off works for me
technocrat7 said:
toggling the bluetooth on and off works for me
Click to expand...
Click to collapse
Do you have to do this for every call, or does it work after doing it just once?
tperki said:
Saw this on the OnePlus forum. For those with the issue where the callers voice comes out the microphone instead of the earpiece, here is something to try: "Stop HearingAidService under Bluetooth running services in Developer options under system. I had the same issue. Hearing aid services are being turned on without Bluetooth being on." Someone on the forum tried it with success. I have gone back to 10 so I cannot test it.
Click to expand...
Click to collapse
do you have to do this every boot or just once?...because i downgraded just like you to 10 because it was annoying and the worst is the lockscreen dpi change that made it hard to put my fingerprint or pattern...forcing me to reboot...
A few days ago I got another update. It fixed the speakerphone issue.
guitardoc64 said:
A few days ago I got another update. It fixed the speakerphone issue.
Click to expand...
Click to collapse
Can someone upload the TMobile update?? Why is it nowhere online?
teflon252 said:
Can someone upload the TMobile update?? Why is it nowhere online?
Click to expand...
Click to collapse
OnePlus7ProTMOOxygen_11.O.20_GLO
Full Android 11 T-Mobile OTA ,Haven't seen it anywere . If for some reason someone needs. Don't think you can flash with twrp, but I have unpacked and flashed in fastboot...
forum.xda-developers.com
does anyone have a oos 10 tmobile rom that i can use to downgrade?
teflon252 said:
Can someone upload the TMobile update?? Why is it nowhere online?
Click to expand...
Click to collapse
[ROM][STOCK][GM1915][FASTBOOT][11] T-Mobile OnePlus 7 Pro OOS 11.0.1.2 Stock Firmware (Root Optional)
T-Mobile OnePlus 7 Pro OOS 11.0.1.2 Stock Firmware (Root Optional) This thread is for the T-Mobile OnePlus 7 Pro GM1915 Model ONLY WARNING Proceed at your own risk. I am not responsible for any damage to your device. Performing the instructed...
forum.xda-developers.com
weakNPCdotCom said:
[ROM][STOCK][GM1915][FASTBOOT][11] T-Mobile OnePlus 7 Pro OOS 11.0.1.2 Stock Firmware (Root Optional)
T-Mobile OnePlus 7 Pro OOS 11.0.1.2 Stock Firmware (Root Optional) This thread is for the T-Mobile OnePlus 7 Pro GM1915 Model ONLY WARNING Proceed at your own risk. I am not responsible for any damage to your device. Performing the instructed...
forum.xda-developers.com
Click to expand...
Click to collapse
People do not know how to get root with the stock Tmo Rom. Took me forever to figure that out.