Hi, I recently bought a Droid Turbo, and had the bootloader unlocked by Sunshine. The phone works wonderfully, but I'm having a few issues. Most notably, it takes ages(over 15 minutes) to boot when I'm using a custom rom. I'm specifically trying to use AOKP Android version 7.X. I've tried clearing cache, clearing ART cache, clearing modem, factory resetting, reflashing system, and nothing seems to be fixing it. At first I thought it was the ROM's fault, like maybe it was a common issue with the ROM, but I flashed Bliss to it, and had the same issue. One thing I should note is that it doesn't take very long to boot into the stock Verizon rom. Another issue I'm having is sometimes the orientation sensor doesn't work, It's not that big of a deal, but I thought it would be a good idea to include it. I remember my LG G2 having a similar issue because I had the wrong bootstack flashed, but I'm not sure if a similar context applies to the Droid Turbo.
Are you using the very latest modded TWRP from @bhb27? Not the crap from the official TWRP website, but from our official TWRP maintainer? 3.1.1_mod2 is the latest right now.
He knows what's best for our Quarks (he's a recognized XDA dev) and although he got us official status with TWRP over two years ago, for some reason they won't post TWRP with his tweaks that work best with custom ROMs. Some people using official TWRP can only boot to recovery, their phone won't even boot to their ROM directly. I helped someone with that just this week.
So, we ignore the official TWRP website and download his modded TWRP. This is the one you should be using:
twrp-3.1.1-mod_2-quark.img
https://androidfilehost.com/?w=files&flid=39562
If you are using that, then I don't know. You could also try other ROMs just to see. AOKP is in the top three, in my opinion, but wouldn't hurt to test with something else.
[ROMs][Quarks][List for Moto Maxx and Droid Turbo]
Related
Hi, first off I want to introduce myself since I have been lurking in the forums for some time now but never posted anything. (I am not a developer).
My name is Nicolas, and currently I own a Moto X 2014. (XT1097)
I bought it recently, with lollipop out of the box, and updated via OTA to MM, since I wanted to check what was available to flash I unlocked the bootloader and flashed TWRP to then get root.
All up to this point it was all normal. I proceed to flash CyanPop 4.8 via TWRP, again all normal.
The problem begun when i wanted to flash a MM Stock ROM back, flashed via TWRP and as soon I hit reboot it gets stuck in the M logo with the white backgroud and bootloops there.
I reflashed Stock ROM XT1097, still bootloops, flashed Stock ROM Lite XT1097, still bootloops, flashed Stock rom XT1095, bootloops.
I ended up returning to CyanPop 4.8, (btw, I say its a hybrid in the title because as soon I installed CyanPop, the setup screen told me it was a XT1095)
and cant get out.
I know its kind of messy, but if anyone could bring light to what is going on, I would be extremely grateful, or if anyone knows what to search for to point me in the right direction, also i would be extremely grateful.
Anyway, thanks for all the work you guys do, and for this awesome forum :good::good::good::fingers-crossed:
I was looking into multi-boot on my xt1060. Not important, just a project. Looking around, I saw a pretty cool project here on XDA called DualBootPatcher and started digging around into whether or not it would work for our device. Maybe not even the xt1060, but any variant of the device. Turns out, as of January 8th 2016, our device (all) is supported by DualBootPatcher: https://github.com/hankching/DualBootPatcher-1/wiki/[Devices]-Motorola and https://forum.xda-developers.com/android/development/list-support-devices-dualbootpatcher-t3278937
Anyone used it? I have an unlocked bootloader and I'm running 5.1, however my device has never been OTA'd past 4.4.2. I think it'd be pretty nifty to dual boot into a non-stock ROM for testing or just to give it a try before you fully commit. I'm also kind of impatient and make weekly backups, so I plan on giving it a shot tonight and will report back how it goes.
Tried
I did try this app on Kitkat 4.4.4. I installed Xperience 7.1 and Gapps Nano, I installed it on data partition, but the phone won't turn on, it only vibrates 5 times.
What I did to restore is installing the utilities.zip from TWRP and changing back to my primary rom.
Sidd24 said:
I did try this app on Kitkat 4.4.4. I installed Xperience 7.1 and Gapps Nano, I installed it on data partition, but the phone won't turn on, it only vibrates 5 times.
What I did to restore is installing the utilities.zip from TWRP and changing back to my primary rom.
Click to expand...
Click to collapse
Same result. Damn. I might keep digging into it if I can find the time.
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.
So I have a Moto E5 Plus (hannah) XT1924-8
and I'm in a jam.
I'm new to moto phones I just moved over to this phone 4 days ago from my HTC M9 yeah I have been a HTC guy for a long time.
My stock rom is fubar, when it boots up I get that encrypt storage thing & reset phone etc.... (no password box) but reset phone is not fixing it.
The boot loader is unlocked
& my twrp is on twrp-3.2.3-0-hannah.img got it from twrp.me
So my problem is that I want to re-flash my stock rom but "Lenovo Moto Smart Assistant" witch did worked 4 times this week but now does not want to work anymore.
It comes back at me with "this device is not supported" & that is not true.
So Now I can't get back to stock & I have not been able to get any custom rom to work me as well.
So my ?s to all of you:
Is there some kind of fix for the "Lenovo Moto Smart Assistant"?
and if not then where do I get a copy of the stock rom & some info on how I should go about installing it
and yes I have the newest adb all installed & I think I have the right driver installed "Motorola_Mobile_Drivers_64bit_v6.4.0.msi" Motorola ADB Interface 7/7/2013 v2.0.2.0
Any help will be much appreciated
Also is the phone default encryption getting in the way of me installing Lineage 15.1 or Bootleggers ??
When ever I try to installing a custom rom I get the dreaded 'To Start Android, Enter Password'
also in twrp /data does not mount when ever I booted into twrp, I had to change the format from ext4 to exfat & then change it back to ext4, from that point on it mounts no problem.
My HTC m9 phone did not have encryption on so I'm not use to working around it.
Well I'm going to return this thing & stay with my HTC m9 with only a 10% working battery.
It seems that no one is going to help me.??
there might be reasons why people wouldn't respond
1. this board isn't active like you'd expect it to be
2. there's already threads out there to save yourself from this
anyway, on twrp, you'd need to FORMAT data to have it de-encrypted... and you'd need to flash a certain boot image that prevents it from auto-encrypting, which is in one of the threads. you'd also never would want to use the smart assistant, because as you can see, it won't work. i don't know if there's a stock rom for your variant, so i can't really link you to yours, but getting it from the moto assistant isn't ideal, it's better to get it from here on the forums or something.
so, in order to install a custom rom, flash the boot.img that doesn't have encrypt, and then flash the gsi system image, and then flash magisk in twrp.
There should already be a thread with the xt1924-8 stock firmware in here somewhere just gotta search. If not I'd suggest trying to re-flash the stock recovery and boot images if you have those and then just try to do a recovery from within.
well I already returned it.
I did read many many many guides on here & on other websites before asking for help.
most of them did not say anything about the book.img to turn off the auto-encrypting.
again I never had to work around auto-encrypt before.
Also @wihzard
I did look for a stock rom for (hannah) XT1924-8 but did not find it.
anyways I returned it & now I'm looking for a unused M9 to replace my old one,
I will end up putting LineageOS 16.0 on it.
Thanks for replying
my moto e5 plus is bricked im pretty sure ...any help anyone?
E-TARD_The_LifeCaster said:
well I already returned it.
I did read many many many guides on here & on other websites before asking for help.
most of them did not say anything about the book.img to turn off the auto-encrypting.
again I never had to work around auto-encrypt before.
Also @wihzard
I did look for a stock rom for (hannah) XT1924-8 but did not find it.
anyways I returned it & now I'm looking for a unused M9 to replace my old one,
I will end up putting LineageOS 16.0 on it.
Thanks for replying
Click to expand...
Click to collapse
………………………………………….
I need help as well haven't had much time to get on here and try to get help. I have the XT1924-7 varriant. I had discovered a hidden network that was placed on there by an ex to track me. So I factory reset I had AEX pie installed on it. Come to find out factory reset didn't even get ride of had to follow some extra steps to erase partitions that weren't wiped during the reset with TWRP. So my problem is once booted and going through setup process these pop up start popping up(screen shots below)the first is the modem keeps stopping. I get that about 25 times of hitting ok then I get one last one stating internal error need to factory reset. IVE DONE THAT COMPLETELY DELETED IT ALL RESTORED ALL. I've flashed NON-HLOS alone withe the erase modem 1&2. And still I've done diffent methods of trying to restore and get nowhere. Any help would be appreciated
Hello everyone, try to install several custom roms, there is no tutorial that explains how the rom and twrp are installed. There are many tutorials and they all contradict, some say do this, others say do the other, but all fail.
Twrp boot, flash rom, install custom rom on SLOT A, install TWRP on slot B.
PROVEN ROMS:
PixelExperience:
Very low call volume, impossible to fix.
LineageOS:
Does not start play store, does not allow login to accounts, does not allow to install gapps.
- CURRENT ROM--
Evolution X:
Does not start play store, does not allow login to accounts.
I have been installing customs roms for years and this device is costing me my life. HELP
The most users get in trouble with A/B devices because they don't know exactly the differences between A-only and A/B partitions.
You don't know how to install TWRP? Why? On twrp.me you can find a detailed instruction for every single model.
A custom ROM is always a .zip file and you can flash a .zip file via TWRP. If you flash a ROM while slot _a is set as active you will install the ROM on slot _b. That's all. That is the meaning of semless updates.
Every new ROM must contain a own boot.img. A new boot.img will delete TWRP and Magisk. TWRP is a recovery and A/B devices don't have own partition for recovery. The recovery is merged in the boot partition.
Also Magisk uses the boot.img to patch the ramdisk. Flashing a new boot.img means you override the patched ramdisk with a new own. As a result you need a new Magisk installation.
my recommendation is starting from scratch with a clean stock 10 install then trying again...
lineage wiki probably has the best install instructions https://wiki.lineageos.org/devices/lake/install but also check its forum thread https://forum.xda-developers.com/g7-plus/development/rom-lineageos-17-1-t4076569 for other recommendations . if you want evolution X read the instructions in its thread https://forum.xda-developers.com/g7-plus/development/rom-evolution-x-4-1-69-moto-g7-plus-t4081731 as well but there pretty much the same.... you've probably went threw those threads already based upon you saying you have tried 3 diff roms already, but try again from a clean install of stock 10 (IF you want to run a 10 rom). i know it's not really a "clean/easy/simple" solution/tutorial, but with this device there is some trial and error for getting a half assed working install. however MAKE SURE you are on a stock 10 rom when installing a 10 rom, pixel experience is a 9 rom and that could be part of your problem. moving from android 10 stock, to a 9 rom, then back to a 10 rom will lead to issues. or a 9 rom, to a 10 rom, without moving to stock 10 in between will lead to problems.
as this isnt nearly a widely adopted device, custom rom development and support isnt even close to other devices, so expect bugs. i've always ran cfw's on all my devices ever since the htc g1/dream days, this is my first device i've stuck with stock due to the lack of rom development, lack of widespread use and people actually wanting to use cfw and users to bug report, and stock being more stable... but your mileage may vary. also no disrespect meant towards the hard working dev's who do work on this device, keep it up.
Thank you very much, I feel lucky that you have responded so quickly, sometimes my messages I post in this forum are never answered. Right now I am with revolution X:
--- It has TWRP perfectly installed, it has the boot.img patched with Magisk without any error and rooted perfectly, but google play for more than clean and reinstall it never opens, it does not allow me to login to the accounts, the APPs they close alone, etc.
I will try to put the stock and again but I have very little hope. thanks, again¡¡
prodigy90 said:
Thank you very much, I feel lucky that you have responded so quickly, sometimes my messages I post in this forum are never answered. Right now I am with revolution X:
--- It has TWRP perfectly installed, it has the boot.img patched with Magisk without any error and rooted perfectly, but google play for more than clean and reinstall it never opens, it does not allow me to login to the accounts, the APPs they close alone, etc.
I will try to put the stock and again but I have very little hope. thanks, again¡¡
Click to expand...
Click to collapse
yeah it seems to be pretty finicky getting a good install and gapps seem to have issues. reading all the posts in the lineage17 thread just make me cringe. as much as i'd love to use lineage as my daily driver (or evo X) my days of willing to put up with a buggy rom and daily dirty flashing have come and gone. this was my first, and will be my last, moto device for the the simple fact it just doesnt have the user base and its development is stunted, compared to more widely used devices.
i hope you get something working, the lineage17 thread definetly has some good advice on what people have done to get a working install, should be able to apply flash order etc to a evoX install (minus having to install gapps for evoX)
solved
I managed to perfectly install the Stock Rom with the following tool:
Lenovo MOTO Smart Assistant, a real wonder, simply select the model and in fastboot, immediately install the factory rom.
download.lenovo.com/consumer/mobiles/lmsa_v4.5.0.14_setup.exe
prodigy90 said:
I managed to perfectly install the Stock Rom with the following tool:
Lenovo MOTO Smart Assistant, a real wonder, simply select the model and in fastboot, immediately install the factory rom.
download.lenovo.com/consumer/mobiles/lmsa_v4.5.0.14_setup.exe
Click to expand...
Click to collapse
yup, the LMSA is a great tool for sure. glad you got back to a clean stock install.