Hello, last night my phone started showing mistakes as "the process com.Google.process.gapps has stopped" or "Google process doesn't answer" without any reason.
I did make a complete wipe through my recovery TWRP (I wouldn't recommend this in base of this experience, CWM is better, really better:crying and it shows "wipe complete" but next to it shows the word "Failed" in red.
- I can turn the phone on sometimes but after the moto boot the screen stays black.
- I installed lollipop again and it says that every process doesn't answer.
- I can't reset the internal memory as I explained before
- I hardly ever used the root with Xposed.
- I have the bootloader unlocked from a while ago.
At least the phone runs the bootloader without problem.
Any solution?
I have never dropped my phone and I have it for months.
P.D. English, is not my native language sorry for the mistakes.
Not sure why it does, but it's been happening to me as well.
Try this:
Go to Settings, Apps, All, and clear data for Downloads. Then disable and enable Downloads. This seems to work.
Try restoring it to kitkat
try this link it works great it will restore your phone to stock kitkat GB version and you can latter update it OTA to lollipop. i have tried it and it works. http://forum.xda-developers.com/moto-g-2014/general/windows-tool-moto-g-2014-xt1068-dual-t2983295 as bootloader is working you will be able to restore i think. just download zip file extract it. it contains instructions too.
Thanks for help me, but still not working.
Actually, what I really need is to be able to delete everything in the phone, I can try changing the system date but I cannot delete the data of the phone.
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???
First off, I want to say that I take full responsibility for this fiasco, it's my own fault because I didn't read the instructions well enough.
I bought a T-mobile G4-H811 in May, successfully rooted it and installed TWRP and all was well.
Last night I decided to install a custom Rom, and I screwed up BAD. I went with the Genisys rom and theme pair, but I didn't wipe the system before installing, and then I only installed the Theme without the Rom (i.e. I installed the Genisys 4.2 theme onto the stock Rom). Surprisingly, the system didn't brick. Instead when I booted back up, I got the error "Unfortunately, camera has stopped", and most phone functions stopped working: camera, audio and video files, youtube, even the dialer. It's got text messaging, web browsing, and that's about it.
I've tried wiping the system and installing the Genisys rom, no change. Also no change with the stock stock rom, and Resurrection Remix rom, exact same problem on all of them. Cyanogen gives install errors, and after I fixed those it just hangs on the boot screen.
I'm perfectly willing to accept that I've irreparably broken my device, but I'm hoping someone here has an idea of what I broke and how to fix it.
Thank you for your time reading this.
MellowshipSlinky said:
First off, I want to say that I take full responsibility for this fiasco, it's my own fault because I didn't read the instructions well enough.
I bought a T-mobile G4-H811 in May, successfully rooted it and installed TWRP and all was well.
Last night I decided to install a custom Rom, and I screwed up BAD. I went with the Genisys rom and theme pair, but I didn't wipe the system before installing, and then I only installed the Theme without the Rom (i.e. I installed the Genisys 4.2 theme onto the stock Rom). Surprisingly, the system didn't brick. Instead when I booted back up, I got the error "Unfortunately, camera has stopped", and most phone functions stopped working: camera, audio and video files, youtube, even the dialer. It's got text messaging, web browsing, and that's about it.
I've tried wiping the system and installing the Genisys rom, no change. Also no change with the stock stock rom, and Resurrection Remix rom, exact same problem on all of them. Cyanogen gives install errors, and after I fixed those it just hangs on the boot screen.
I'm perfectly willing to accept that I've irreparably broken my device, but I'm hoping someone here has an idea of what I broke and how to fix it.
Thank you for your time reading this.
Click to expand...
Click to collapse
use LGUP and search for KDZ file flash it.. have in mind once you are in 20o version you cant downgrade to lower version or wour phone hard bricks.
raptorddd said:
use LGUP and search for KDZ file flash it.. have in mind once you are in 20o version you cant downgrade to lower version or wour phone hard bricks.
Click to expand...
Click to collapse
Thank you!
While I didnt do the same that you did, I had the same symptoms. They even carried over into 20i stock rom. I tried flashing the 20i KDZ and it didnt fix anything. I flashed 20p and everything was magically fixed.
I am being plagued by wifi issues ever since i went to a new version of Purenexus. It seems to have something to do with going to 7.1.1
I've tried the older version of the rom that was working fine before, but i still seem to have wifi issues even in these older versions now.
i tried resurection remix, but still have the same issue.
after a while the wifi wont be connected and it says authentication problem, or sometimes shows it as simply discconected.
i can manually forget the network and re add it and it seems to work fine for a while.
Durring troubleshooting today, i have tried to resey my router, even upgraded the firmware,
anyways, i'd like to flash the factory image to test to see if i still have issues. but i want to make sure that if i install 7.1.1 factory image, or 7.0 that i can still re-flash twrp from adb or am i going to have to find a root exploit?
if i flash a factory image does it "relock" my bootloader? i guess that is the more important question
thanks.
citrusfizz said:
I am being plagued by wifi issues ever since i went to a new version of Purenexus. It seems to have something to do with going to 7.1.1
I've tried the older version of the rom that was working fine before, but i still seem to have wifi issues even in these older versions now.
i tried resurection remix, but still have the same issue.
after a while the wifi wont be connected and it says authentication problem, or sometimes shows it as simply discconected.
i can manually forget the network and re add it and it seems to work fine for a while.
Durring troubleshooting today, i have tried to resey my router, even upgraded the firmware,
anyways, i'd like to flash the factory image to test to see if i still have issues. but i want to make sure that if i install 7.1.1 factory image, or 7.0 that i can still re-flash twrp from adb or am i going to have to find a root exploit?
if i flash a factory image does it "relock" my bootloader? i guess that is the more important question
thanks.
Click to expand...
Click to collapse
There will be no locking of the bootloader unless you issue the command. No exploits needed. Just flash away...
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.