Droid Mini/Ultra/Maxx SU6-7.7? - Droid Ultra Q&A, Help & Troubleshooting

Just wondering if anyone has any insight on SU6-7.7 on the Droid line? Whether or not anyone know or hear anything about downgrading to a different SU version? I have the firmware file for the latest SU6-7.7 in case anyone wants it.
https://drive.google.com/open?id=0B7hPMTc_G5VPMFVqZmdMSXJEbjA
It would be nice if Motorola/Lenovo would let us do what we want with a phone they no longer "support".

Thanks, I was looking for this.

RichardCA said:
Thanks, I was looking for this.
Click to expand...
Click to collapse
Sure thing! Let me know if you need anything else!

SalmanJohnson2011 said:
Sure thing! Let me know if you need anything else!
Click to expand...
Click to collapse
OK, since you asked...
On a Motorola phones that still have their stock, factory install intact, they do this clever thing where they cycle between a few different boot logo's, with slightly different colors in the Motorola logo on each boot.
Is there any way to replicate that after you're unlocked?

RichardCA said:
OK, since you asked...
On a Motorola phones that still have their stock, factory install intact, they do this clever thing where they cycle between a few different boot logo's, with slightly different colors in the Motorola logo on each boot.
Is there any way to replicate that after you're unlocked?
Click to expand...
Click to collapse
I believe that you can replace the stock boot logo with an unlocked or locked bootloader. There are a quite a few logos to choose from. When you pick one, you fastboot the image.

Oh, to answer your original question, SU6-7.7 appears to be the "terminal" KitKat release for the Droid Ultra/MAXX.
If you go to the Motorola web site you can get an earlier 2014 4.4.4 build, SU4.21 I think. I think that was the first 4.4.4, before any OTA's. This is why I was happy when you posted the more recent one.
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images
I've flashed both, they both seem to work just fine.
Did you have a more specific question?

RichardCA said:
Oh, to answer your original question, SU6-7.7 appears to be the "terminal" KitKat release for the Droid Ultra/MAXX.
If you go to the Motorola web site you can get an earlier 2014 4.4.4 build, SU4.21 I think. I think that was the first 4.4.4, before any OTA's. This is why I was happy when you posted the more recent one.
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images
I've flashed both, they both seem to work just fine.
Did you have a more specific question?
Click to expand...
Click to collapse
Not sure at the moment. XD I'll reply back to this post or PM you if I do. Thanks again! If you have any more info, please let me know!

RichardCA said:
Oh, to answer your original question, SU6-7.7 appears to be the "terminal" KitKat release for the Droid Ultra/MAXX.
If you go to the Motorola web site you can get an earlier 2014 4.4.4 build, SU4.21 I think. I think that was the first 4.4.4, before any OTA's. This is why I was happy when you posted the more recent one.
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images
I've flashed both, they both seem to work just fine.
Did you have a more specific question?
Click to expand...
Click to collapse
When you flashed it to your mini/ultra, where you on SU6-7.7?

SalmanJohnson2011 said:
When you flashed it to your mini/ultra, where you on SU6-7.7?
Click to expand...
Click to collapse
I jumped around a lot. I was playing with marshmallow and lollipop builds and needed to revert back. But I was on the Motorola stock SU4.21 when I flashed it.
I used the process on this page, and got zero errors:
http://forum.xda-developers.com/showthread.php?t=2580060

Help please!!!
Hi everyone im not so good at rooting and fllashing ect ect. iv done it before but always watching youtube videos lol. so i have the droid mini now its a verizon carrier unlocked with android 4.4.4 SU6.7.7 and i would like to install CM so i can customize my phone more also want to get rid of all the bloatware if anyone could please let me knoe if its possible and walk me through this i would really apreciate it!! Thanks in advance :fingers-crossed:

edgar1994 said:
Hi everyone im not so good at rooting and fllashing ect ect. iv done it before but always watching youtube videos lol. so i have the droid mini now its a verizon carrier unlocked with android 4.4.4 SU6.7.7 and i would like to install CM so i can customize my phone more also want to get rid of all the bloatware if anyone could please let me knoe if its possible and walk me through this i would really apreciate it!! Thanks in advance :fingers-crossed:
Click to expand...
Click to collapse
To my knowledge, I don't think you can install custom roms once you install the latest SU update. Beings that you're on SU6-7.7 like me, there's not much you can do until someone comes out with another exploit.

Can I revert to su6-7 after having su6-7.7 update? I could do that after su6-7.3 update though.

ashal said:
Can I revert to su6-7 after having su6-7.7 update? I could do that after su6-7.3 update though.
Click to expand...
Click to collapse
Nope. I've tried and it doesn't work.

SalmanJohnson2011 said:
To my knowledge, I don't think you can install custom roms once you install the latest SU update. Beings that you're on SU6-7.7 like me, there's not much you can do until someone comes out with another exploit.
Click to expand...
Click to collapse
Man this really sucks i hope someone finds a way around this :crying:

edgar1994 said:
Man this really sucks i hope someone finds a way around this :crying:
Click to expand...
Click to collapse
I Agreed dude. I'm with you! I don't know why I keep getting Verizon phones. XD Regardless of what I learned. Haha

SalmanJohnson2011 said:
Nope. I've tried and it doesn't work.
Click to expand...
Click to collapse
Did you try downgrading directly from SU6-7.7 to SU6-7 or you went like SU6-7.7 to 7.3 to 7.2 to SU6-7?
Because for SU6-7.3 I downgraded one by one.

ashal said:
Did you try downgrading directly from SU6-7.7 to SU6-7 or you went like SU6-7.7 to 7.3 to 7.2 to SU6-7?
Because for SU6-7.3 I downgraded one by one.
Click to expand...
Click to collapse
For me, I tried going down one update at a time and it still doesn't work.

it says devoloper phones only
can I flash to my ultra even tho its not a dev phone??

RichardCA said:
Oh, to answer your original question, SU6-7.7 appears to be the "terminal" KitKat release for the Droid Ultra/MAXX.
If you go to the Motorola web site you can get an earlier 2014 4.4.4 build, SU4.21 I think. I think that was the first 4.4.4, before any OTA's. This is why I was happy when you posted the more recent one.
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images
I've flashed both, they both seem to work just fine.
Did you have a more specific question?
Click to expand...
Click to collapse
In case this helps anyone: I recently updated to SU6-7.7 from SU4.21 following the guidance in this thread and referenced resources on a XT1030 (Moto Mini). Initially I tried to get cute and only flashed the system image and modem upgrades; was rewarded with a bootloader loop that did not resolve after a full TWRP restore of the previous build. Next take including everything in the zip except boot.img and recovery.img as my device is unlocked and wasn't sure if flashing boot.img would relock the bootloader. Also wanted to maintain a true recovery. Everything worked fine except the WiFi radio which refused to engage (Bluetooth was ok). After a bit of fiddling dropped back to fastboot and flashed boot.img. Device restarted just fine with bootloader remaining unlocked. Whohoo! I should also note the all of the above was a 'dirty flash'. Never erased the userdata partition; all apps came back just fine. Oh yeah, had to reflash SuperSU but that's pretty standard after a system wipe.
Thanks to all the key contributors in this thread and elsewhere in the forum. After some miserable bootloops a couple years back (foolishly accepted VZW OTA) I froze the rom and vowed never to update it. It's nice to be running the terminal release of KitKat for this device which as several stability/usability features baked in along with the usual security updates (now dated but better than 2014!). I had considered CM 12.1 and CM 13 but needed fully hardware functionality that only seems to come with stock builds.

root successful
Davey126 said:
In case this helps anyone: I recently updated to SU6-7.7 from SU4.21 following the guidance in this thread and referenced resources on a XT1030 (Moto Mini). Initially I tried to get cute and only flashed the system image and modem upgrades; was rewarded with a bootloader loop that did not resolve after a full TWRP restore of the previous build. Next take including everything in the zip except boot.img and recovery.img as my device is unlocked and wasn't sure if flashing boot.img would relock the bootloader. Also wanted to maintain a true recovery. Everything worked fine except the WiFi radio which refused to engage (Bluetooth was ok). After a bit of fiddling dropped back to fastboot and flashed boot.img. Device restarted just fine with bootloader remaining unlocked. Whohoo! I should also note the all of the above was a 'dirty flash'. Never erased the userdata partition; all apps came back just fine. Oh yeah, had to reflash SuperSU but that's pretty standard after a system wipe.
Thanks to all the key contributors in this thread and elsewhere in the forum. After some miserable bootloops a couple years back (foolishly accepted VZW OTA) I froze the rom and vowed never to update it. It's nice to be running the terminal release of KitKat for this device which as several stability/usability features baked in along with the usual security updates (now dated but better than 2014!). I had considered CM 12.1 and CM 13 but needed fully hardware functionality that only seems to come with stock builds.
Click to expand...
Click to collapse
Dear i have successfully rooted mine droid mini su6-7.7 with kingo root (not global) v3.4 successfully now i have superuser app in system directory
---------- Post added at 05:42 AM ---------- Previous post was at 05:20 AM ----------
Dear friends i have successfully root mini droid mini su6-7.7 with kingo root v3.4 (not kingo root global). actually i was trying to flash su4.21 over su6-7.7 with RSD lite v6.1 but failed with max get var and after that tried to flash with RSD lite 5.1 again failed without any error. after all of there method i thought of giving a try to kingo root. i downloaded 2 apps kingo root globalv4.9.7 and kingo root v3.4, kingo root global failed to root but.... kingo root v3.4 succeeded to roo. now i have superuser app in system driectory.
but problem is that after removing system app (amazon) when i restarted the phone all the apps came back and superuser app gone. i don't know why so my request to look into this method .
i have tested this method and worked 100% and i have no intention of making fun of me. i have both the apps but don't know how to upload here
Thanks

Related

[ROM] New stock Rom DEFY JRDNEM_U3_2.51.1 UK

New official version stock English rom for UK v2.51.1 released.
DOWNLOAD: Defy Rom v2.51.1
thanks, but where can we find the changelog of this new rom ?
Great! Will give it a try.
might try this tomorrow, although I can't see it being anything major, at the end of the day its not been push OTA as an update yet. I just tried the supposedly "no blur" firmware too and there was still loads of blur on it!
it is unrootable for the moiment.
Are z4root (or other rooting methods) and tenfar's recovery working with this ROM? 'Cause someone in another topic said, that he flashed this ROM, and now he can't flash back anything older than this. (http://forum.xda-developers.com/showpost.php?p=10023019&postcount=7)
And stuck with this ROM, without root and recovery, would be a huge pain in the *ss.
Edit: I think I got my answer from bihariel's post.
TPGamer said:
Are z4root (or other rooting methods) and tenfar's recovery working with this ROM? 'Cause someone in another topic said, that he flashed this ROM, and now he can't flash back anything older than this. (http://forum.xda-developers.com/showpost.php?p=10023019&postcount=7)
And stuck with this ROM, without root and recovery, would be a huge pain in the *ss.
Edit: I think I got my answer from bihariel's post.
Click to expand...
Click to collapse
i don´t know, but i have the "deblured" 2.34.1 firm rooted with z4root and with the clockwork recovery working
Thanks, have installed and its a nice improvement.
Not a giant leep but more of a polish. I must be one of the few people that likes the email client in motoblur.
i aint going anywhere near this it its not rootable then - there nothing wrong with 2.21 imo. And I like the blur email app too lol
If this rom isn't rootable, doesn't that mean that the guys at motorola "fixed" the exploit, that we used, to get root access (and because of that, we need to find another exploit)?
the problem is that you can not flash any older than this and without root you can not flash custom recovery and can not restore nand backup.
if you flash older the phone wont boot.
Yep now unable get root access. Oh well
im stuck on this UK rom too! im not giving up so easy though... just need root and we are good.
TPGamer said:
If this rom isn't rootable, doesn't that mean that the guys at motorola "fixed" the exploit, that we used, to get root access (and because of that, we need to find another exploit)?
Click to expand...
Click to collapse
i don't think so, because 2.34.1 central europe firm, wich also was uploaded today, is rootable and keeps clockwork mod recovery working
andyirons said:
i don't think so, because 2.34.1 central europe firm, wich also was uploaded today, is rootable and keeps clockwork mod recovery working
Click to expand...
Click to collapse
we need another exploit for this rom atleast
jboogie3 said:
im stuck on this UK rom too! im not giving up so easy though... just need root and we are good.
Click to expand...
Click to collapse
I´ve just flashed back from 2.34.1 to 2.21.0 with no major problem.
Looks like 2.51.1 UK comes with a secret within.
jboogie3 said:
we need another exploit for this rom atleast
Click to expand...
Click to collapse
yes, indeed
ya... moto patched it.. my devices goes offline after doing the - ./rageagainstthecage-arm5.bin using the droid2root method... if only it could stay online then we could have root
what the fnck....I just flash the 2.51 two hours ago. i've try atleast 3 method to root this ...all failure....Fnck moto.....
see what they did is baited you in with "noblur" and now your stuck without root!

[Q] XT1030 Rooted, 4.4 update keeps rebooting

Hi guys.
So I purchased 2 of the Droid Minis for my kids. They are both on 12.15.15 (camera update) 4.2.2 and started bugging them to take the update to 4.4
Before letting them take the update, I wanted to root them both so I could install tracking software on them, so I followed the thread here: http://forum.xda-developers.com/showthread.php?t=2509590
(for RockMyMoto)
PwnMyMoto never did anything but error, so I figured it was because of the camera update.
I successfully rooted BOTH XT1030 phones following the RockMyMoto OP, verified by installing SuperSU and double verified by installing TiBU from my license. Both phones are truly rooted as both asked me to grant or deny root access, and I've even checked via RootManager and it does indeed allow access.
So after following the link above and successfully rooting both phones, I started the 4.4 update on the first one and waited for it, but it just rebooted over and over, which made me stop in my tracks on the second phone.
Right now, the phone that was supposed to be taking the 4.4 update will boot all the way to a usable homescreen, but it reboots after about 20 seconds of having hit the homescreen. It's been doing this for about an hour now.
I've gotten enough time to get into Settings > About and check, and it's still on 4.2.2 (12.15.15), and even allows to check for updates before rebooting again (if I'm quick, I can even push the button to check for updates, but the device only lasts for 20 seconds before it automatically reboots.
I've tried booting into Recovery, but it just reboots into normal mode, lasts 20 seconds and reboots again.
I'm stuck, and would appreciate some help here. I'm not new to flashing, having been a crackflasher since the OG D1. Although, I have to say that these Droid Mini's are significantly harder to work with than my Note3, S4 and any of my previous phones...
help PLEASE?!
Obviously, my daughter has a bunch of games on her phone after having it since Christmas, and I'd definitely prefer not to lose her data. I had the foresight to make a TiBU backup before moving forward with the 4.4 update, but in it's current state of rebooting, it won't stay on long enough for me to copy the TiBU folder to my computer.
If I knew how to fastboot, perhaps I could fastboot the files for 4.2.2 back to the phone without losing her data - at least so I could transfer the TiBU folder over in case the phone has to be RSD'd back to stock...
If this is an option, please help me out with the exact commands that I might need. Thanks in advance!!
EDIT: I read how to fastboot (hadn't done it for a couple years) and found the correct files for the xt1030 here: http://sbf.droid-developers.org/phone.php?device=2
I downloaded and unzipped the 12.15.15 file.
I then used fastboot to push boot.img, motoimg.img, recovery.img successfully (although there is NO recovery no matter how I try to boot into it)
BUT, when I fastboot flash system.img, it comes up with several errors and fails, so I'm sure that the problem actually exists in the system image on the phone.
*** I DID NOT erase anything, only dirty flashed. I did this because I need to back up the user data before anything happens to it.
If I do erase system on the phone, will I lose her data? What about the other images that are still on the phone??
**EDIT: I found that I needed to use mfastboot instead of the standard fastboot to flash the system.img because it's apparently too big - mfastboot breaks it into smaller chunks and pushes them correctly, however, the phone still reboots.
This isn't considered a bootloop, it will boot all the way into the homescreen, stay active and live for around 20 seconds and then reboot.
I'm already going to be in trouble when she finds out she can't use her phone in the morning... PLEASE help a brother out!
Hope that info helps someone to help me better!
Unfortunately the Droid Mini and Max has yet to get their own device forums. So, I have moved the post to this forum in hopes some folks can help as the Ultra may share some characteristics as it's a relatively new device getting the 4.4 update as well.
MD
Moscow Desire said:
Unfortunately the Droid Mini and Max has yet to get their own device forums. So, I have moved the post to this forum in hopes some folks can help as the Ultra may share some characteristics as it's a relatively new device getting the 4.4 update as well.
MD
Click to expand...
Click to collapse
Thanks MD.
I just now figured it out on my own.
I hope that this thread will serve to help anyone that may stumble across a similar problem on their XT1030 device - perhaps even other Moto devices.
WHAT I FOUND:
While fastbooting and mfastbooting files to the phone, I realized that it wasn't working because I was missing something somewhere, so I opened the XML file in the original 12.15.15 zip and went through it line by line.
The one thing that I had neglected to do while in fastboot was to ERASE CACHE.
Once I had erased cache via fastboot (and obviously after pushing all the proper img files), it all worked correctly after reboot - the phone no longer reboots on it's own and immediately started the download of the OTA 4.4.
I hope that this post helps anyone else that happens across this problem.
Psychlone said:
Thanks MD.
I just now figured it out on my own.
I hope that this thread will serve to help anyone that may stumble across a similar problem on their XT1030 device - perhaps even other Moto devices.
WHAT I FOUND:
While fastbooting and mfastbooting files to the phone, I realized that it wasn't working because I was missing something somewhere, so I opened the XML file in the original 12.15.15 zip and went through it line by line.
The one thing that I had neglected to do while in fastboot was to ERASE CACHE.
Once I had erased cache via fastboot (and obviously after pushing all the proper img files), it all worked correctly after reboot - the phone no longer reboots on it's own and immediately started the download of the OTA 4.4.
I hope that this post helps anyone else that happens across this problem.
Click to expand...
Click to collapse
Glad you solved it. Yeah, cleaning cache is always a good thing.. Sure your daughters will be happy now!
You have to follow this guide here http://forum.xda-developers.com/showthread.php?t=2603358 to gain root after 4.4 Update.
Hatary said:
You have to follow this guide here http://forum.xda-developers.com/showthread.php?t=2603358 to gain root after 4.4 Update.
Click to expand...
Click to collapse
Incorrect. That will not work for his device.
Topsnake said:
Incorrect. That will not work for his device.
Click to expand...
Click to collapse
I have a Droid Mini too and followed this guide. Now i have a rooted Droid Mini with Kitkat.
If he is already on Kitkat, then you are right of course!He forgot to disable write-protection (http://forum.xda-developers.com/showthread.php?t=2551113) and flashing back to the camera update (12.5.5) and using SlapMyMoto (http://forum.xda-developers.com/showthread.php?t=2538896) before the Kitkat update.
Hatary said:
I have a Droid Mini too and followed this guide. Now i have a rooted Droid Mini with Kitkat.
Click to expand...
Click to collapse
I don't see how, seeing as we cannot downgrade from 4.4 to 4.2.2
Maxx'd out Kit Kat
Topsnake said:
I don't see how, seeing as we cannot downgrade from 4.4 to 4.2.2
Maxx'd out Kit Kat
Click to expand...
Click to collapse
Sorry i edited my post before! Of course it doesn't work when he updated already to 4.4
Hatary said:
Sorry i edited my post before! Of course it doesn't work when he updated already to 4.4
Click to expand...
Click to collapse
I see. At any rate, ive streamlined the process for our phones here
http://forum.xda-developers.com/showthread.php?t=2616104
Maxx'd out Kit Kat
Never take a ota update while rooted
Same thing happened to me but i learned the hard way that you should never take a OTA update while rooted because it screws things up and the phone is not stable enough to run Android OS without crashing and rebooting again. So what i did is i used RSD lite to reset to stock and after making sure root was gone i took the OTA update and now my DROID ultra is working fine . and FYI if you still want root when running KitKat use slapmymoto to keep root it requires you to have 4.2.2 already installed and then follow some steps so you can keep root in KitKat hope it helps!
What version of RSD Lite for XT1030?
droidusr2014 said:
Same thing happened to me but i learned the hard way that you should never take a OTA update while rooted because it screws things up and the phone is not stable enough to run Android OS without crashing and rebooting again. So what i did is i used RSD lite to reset to stock and after making sure root was gone i took the OTA update and now my DROID ultra is working fine . and FYI if you still want root when running KitKat use slapmymoto to keep root it requires you to have 4.2.2 already installed and then follow some steps so you can keep root in KitKat hope it helps!
Click to expand...
Click to collapse
What version of RSD Lite did you use? I've tried 5.6, 6.4, 6.5, with different USB cables including the one that comes with the phone but I cannot get RSD Lite to recognize my device. I tried fastboot as well but it keeps giving me an error about missing XML files when I try to flash.
MINI root
Hatary said:
I have a Droid Mini too and followed this guide. Now i have a rooted Droid Mini with Kitkat.
If he is already on Kitkat, then you are right of course!He forgot to disable write-protection (http://forum.xda-developers.com/showthread.php?t=2551113) and flashing back to the camera update (12.5.5) and using SlapMyMoto (http://forum.xda-developers.com/showthread.php?t=2538896) before the Kitkat update.
Click to expand...
Click to collapse
Hi, I have MINI with factory 4.4
How can I root it and have custom recovery ( TWRP )
I cannot find guide for XT1030...
THANKS
zsebob said:
Hi, I have MINI with factory 4.4
How can I root it and have custom recovery ( TWRP )
I cannot find guide for XT1030...
THANKS
Click to expand...
Click to collapse
you can't root 4.4. You are stuck until (hopefully) someone releases a root exploit for 4.4
---------- Post added at 11:40 AM ---------- Previous post was at 11:38 AM ----------
mschwartz33 said:
What version of RSD Lite did you use? I've tried 5.6, 6.4, 6.5, with different USB cables including the one that comes with the phone but I cannot get RSD Lite to recognize my device. I tried fastboot as well but it keeps giving me an error about missing XML files when I try to flash.
Click to expand...
Click to collapse
can you post a screen shot/picture of the error you are getting and also the cmd window where you are entering the fastboot commands?
BladeRunner said:
you can't root 4.4. You are stuck until (hopefully) someone releases a root exploit for 4.4
---------- Post added at 11:40 AM ---------- Previous post was at 11:38 AM ----------
can you post a screen shot/picture of the error you are getting and also the cmd window where you are entering the fastboot commands?
Click to expand...
Click to collapse
Thanks! The downgrade to JB and root and update to 4.4 not working on Mini?
zsebob said:
Thanks! The downgrade to JB and root and update to 4.4 not working on Mini?
Click to expand...
Click to collapse
downgrading isn't possible

Confused about if there's root for 4.4 etc

Ok so I got my XT1080 few days or whatever and it had the first 4.4 ota, you know the one with the transparent status bar but still that blue jelly bean hue on the status bar etc.... So not thinking of it I just decided to see if there was another ota and there was so I got it and now I want root.... Here's what I want to know please.. Without telling me to go read 30 pages on another post can someone just tell me
Is there root for me
If so do I have to have boot loader unlocked, I've had phones with locked boot loaders and still flashed Roms
Can I flash Roms on this device with a locked boot loader via twrp
I mainly read that you have to downgrade to a certain version use jcase method it something? I got lost in that bounty post..
Yes there is!
Note
This little guide assumes you know how to install adb and use basic command-line tools.
First, flash your phone back to a older version with rsdlite. (instructions: http://forum.xda-developers.com/showpost.php?p=53141176&postcount=6)
Second, use jcase's pie exploit. (instructions: http://forum.xda-developers.com/mot...-x-pie-motorola-devices-t2771623/post53128101)
Third, use motowpnomo, but executing "adb shell /data/local/atvc/root.sh" in a separate cmd window every time the device reboots (instructions for motowpnomo: http://forum.xda-developers.com/moto-x/orig-development/kill-write-protection-motowpnomo-t2551113 as for the command, just spam it till it goes through)
Forth, install your superuser application (and safestrap if you want custom rom functionality)
Fifth, profit!
Note that you do have read/write access to system and root access, but still a locked bootloader.
bluebloomers said:
Yes there is!
Note
This little guide assumes you know how to install adb and use basic command-line tools.
First, flash your phone back to a older version with rsdlite. (instructions: http://forum.xda-developers.com/showpost.php?p=53141176&postcount=6)
Second, use jcase's pie exploit. (instructions: http://forum.xda-developers.com/mot...-x-pie-motorola-devices-t2771623/post53128101)
Third, use motowpnomo, but executing "adb shell /data/local/atvc/root.sh" in a separate cmd window every time the device reboots (instructions for motowpnomo: http://forum.xda-developers.com/moto-x/orig-development/kill-write-protection-motowpnomo-t2551113 as for the command, just spam it till it goes through)
Forth, install your superuser application (and safestrap if you want custom rom functionality)
Fifth, profit!
Note that you do have read/write access to system and root access, but still a locked bootloader.
Click to expand...
Click to collapse
Wow I love you!
alright my inner noob is going crazy. i see a zillion threads on how you need to roll back to 4.2.2 rom. my question is do i need to roll back if im on 4.4 stock?
i must have downloaded every tool and rom needed by this point. a step by step would be awesome. lots of tutorials available but im seeing they are mostly off of the x which i do understand is practically a sibling to the ultra and maxx.
any info or step by step would be awesome. lastly if i dont need to roll back to an earlier version that would be super. thanks!!!
kdm212 said:
alright my inner noob is going crazy. i see a zillion threads on how you need to roll back to 4.2.2 rom. my question is do i need to roll back if im on 4.4 stock?
i must have downloaded every tool and rom needed by this point. a step by step would be awesome. lots of tutorials available but im seeing they are mostly off of the x which i do understand is practically a sibling to the ultra and maxx.
any info or step by step would be awesome. lastly if i dont need to roll back to an earlier version that would be super. thanks!!!
Click to expand...
Click to collapse
What build of 4.4 are you one? 19.5.3 or 19.6.3?
Topsnake said:
What build of 4.4 are you one? 19.5.3 or 19.6.3?
Click to expand...
Click to collapse
19.5.3 it should be made known i plan on using the phone with t-mobile and the outside hope that i can have a fully functional phone with lte...
Well that makes things more difficult, TMobile has an LTE to Voice/text handoff issue present in 19.5.3 and 19.6.3. I hear its corrected in 4.4.4. Do you have an unlocked boot loader?
Topsnake said:
Well that makes things more difficult, TMobile has an LTE to Voice/text handoff issue present in 19.5.3 and 19.6.3. I hear its corrected in 4.4.4. Do you have an unlocked boot loader?
Click to expand...
Click to collapse
Boot loader is not unlocked. However if I do the update I won't be able to get root. Correct?
Correct. You are on the correct version to begin root. With Jcase's pie and run wp off. You can keep that when you update to 19.6.3 however when you update to 4.4.4 youll lose root (unless you preserve it) but you definitely lose wp off
Topsnake said:
Correct. You are on the correct version to begin root. With Jcase's pie and run wp off. You can keep that when you update to 19.6.3 however when you update to 4.4.4 youll lose root (unless you preserve it) but you definitely lose wp off
Click to expand...
Click to collapse
Alright but I won't be able to take advantage of lte I imagine. Right? Can you point me the right direction with a link? So am I correct with root, recovery, rom? Or am I missing some stuff in there? I appreciate the responses!
kdm212 said:
Alright but I won't be able to take advantage of lte I imagine. Right? Can you point me the right direction with a link? So am I correct with root, recovery, rom? Or am I missing some stuff in there? I appreciate the responses!
Click to expand...
Click to collapse
Link to what specifically? You dont need to downgrade on your version
Topsnake said:
Link to what specifically? You dont need to downgrade on your version
Click to expand...
Click to collapse
Ok to which version? After the downgrade root, recovery, rom? Unlock the boot loader in any of those steps?
kdm212 said:
Ok to which version? After the downgrade root, recovery, rom? Unlock the boot loader in any of those steps?
Click to expand...
Click to collapse
You don't need to downgrade of you are on 19.5.3. You just need to run motopie then motowpnomo.
You can't unlock the bootloader unless you have a code or a developer edition.
No recovery or rom needed.
Root-wp off- Root survival mode in supersu- update to 19.6.3 then stay there unless you want to update to 4.4.4 to address the tmobile lte issue
Then the sequence would be Root-wp off- Supersu survival-update to 19.6.3- supersu survival-update 4.4.4
Topsnake said:
You don't need to downgrade of you are on 19.5.3. You just need to run motopie then motowpnomo.
You can't unlock the bootloader unless you have a code or a developer edition.
No recovery or rom needed.
Root-wp off- Root survival mode in supersu- update to 19.6.3 then stay there unless you want to update to 4.4.4 to address the tmobile lte issue
Then the sequence would be Root-wp off- Supersu survival-update to 19.6.3- supersu survival-update 4.4.4
Click to expand...
Click to collapse
Alright cool, I will start hunting around for all of these tools and threads. Thank you sir!
kdm212 said:
Alright cool, I will start hunting around for all of these tools and threads. Thank you sir!
Click to expand...
Click to collapse
No problem
any tips on keeping root after reboots? also, is there a major difference from 19.5.3 to 19.6.3?
kdm212 said:
any tips on keeping root after reboots? also, is there a major difference from 19.5.3 to 19.6.3?
Click to expand...
Click to collapse
Run motowpnomo to gain wp off then safe strap can install su to system
Ok my buddy has a regular Droid Maxx and after seeing my Droid Maxx DE with Xposed Framework he wants to root his. Looking into it is a bit more work than mine. I have never used adb so I was hoping someone could help me out with this.
TheDroidURLookinFor said:
Ok my buddy has a regular Droid Maxx and after seeing my Droid Maxx DE with Xposed Framework he wants to root his. Looking into it is a bit more work than mine. I have never used adb so I was hoping someone could help me out with this.
Click to expand...
Click to collapse
What version is it on?
Topsnake said:
What version is it on?
Click to expand...
Click to collapse
19.5.3

[Q] Flashing bootloader locked Cricket Moto G/LTE to retail firmware

I want to flash my Cricket Moto G (xt1045) 4.4.4 to the retail 4.4.4 version for a few reasons. Mainly to get access to tethering and the chance that I will be able to update to Lollipop since my hope of cricket releasing the update is fading.
I've been searching around and cannot find a definite answer to this. Lots of people say it should work but I have yet to find anyone who successfully did so. Some say to flash all files but the bootloader and it should be good while others say being the official Motorola firmware everything will flash without a problem.
Has anyone took the plunge and tried it? I would, but I really don't want to be stuck with my Lumia 520 backup phone if I screw something up. Thanks!
macgi77 said:
I want to flash my Cricket Moto G (xt1045) 4.4.4 to the retail 4.4.4 version for a few reasons. Mainly to get access to tethering and the chance that I will be able to update to Lollipop since my hope of cricket releasing the update is fading.
I've been searching around and cannot find a definite answer to this. Lots of people say it should work but I have yet to find anyone who successfully did so. Some say to flash all files but the bootloader and it should be good while others say being the official Motorola firmware everything will flash without a problem.
Has anyone took the plunge and tried it? I would, but I really don't want to be stuck with my Lumia 520 backup phone if I screw something up. Thanks!
Click to expand...
Click to collapse
Anyone? I found a link with instructions but I can't post it until I have 10 posts. If anyone wants to try it, search for "viraj's flash stock rom lock bootloader moto g"
macgi77 said:
Anyone? I found a link with instructions but I can't post it until I have 10 posts. If anyone wants to try it, search for "viraj's flash stock rom lock bootloader moto g"
Click to expand...
Click to collapse
http://dev-viraj.blogspot.in/2015/01/flash-stock-rom-firmware-lock.html
Is that the page? His instructions and ROM download seem to be for a XT1068, not a XT1045. Did you find the ROM files for a 1045 somewhere? I'd like to get access to wifi tethering, too...
Yes, that is the page. I'm assuming the software install would be the same for all models in the Moto G group. The ROM files are located in a thread on here titled "Moto G 4G/LTE Stock Firmware (XT1039/40/42/45)"
Would post a link, but I'm still not allowed.
macgi77 said:
Yes, that is the page. I'm assuming the software install would be the same for all models in the Moto G group. The ROM files are located in a thread on here titled "Moto G 4G/LTE Stock Firmware (XT1039/40/42/45)"
Would post a link, but I'm still not allowed.
Click to expand...
Click to collapse
Link for those looking for it.
Thanks for the link. Maybe I will give this a try, I'm buying an android stereo for my car and need wifi tethering to run the GPS.
If you wind up trying it before I do, let us know! This would theoretically only update the ROM, we'd still be stuck with a locked bootloader, right? If we could find a 4.4.2 ROM, then the Sunshine S-off unlock would work, and we'd be set.
RonnieTheBear said:
Link for those looking for it.
Thanks for the link. Maybe I will give this a try, I'm buying an android stereo for my car and need wifi tethering to run the GPS.
If you wind up trying it before I do, let us know! This would theoretically only update the ROM, we'd still be stuck with a locked bootloader, right? If we could find a 4.4.2 ROM, then the Sunshine S-off unlock would work, and we'd be set.
Click to expand...
Click to collapse
No problem. I will report back if I try, you do the same if you beat me to it! Yes, the bootloader would still be locked, but the software should install since it is an official Motorola signed software. I think I recall reading somewhere that flashing to 4.4.2 would not allow unlocking through sunshine though.
macgi77 said:
No problem. I will report back if I try, you do the same if you beat me to it! Yes, the bootloader would still be locked, but the software should install since it is an official Motorola signed software. I think I recall reading somewhere that flashing to 4.4.2 would not allow unlocking through sunshine though.
Click to expand...
Click to collapse
macgi , I gave this a try last night and the results were extremely not good. Wasn't able to flash the retail firmware, got a bunch of "prevalidation flash failed" on some items, but not others, and then it wouldn't boot. Tried to reflash the cricket firmware to revert back, and got the same prevalidation error for the boot image and the partition gpt.bat file, and now I can't get past the fastboot screen.
RonnieTheBear said:
macgi , I gave this a try last night and the results were extremely not good. Wasn't able to flash the retail firmware, got a bunch of "prevalidation flash failed" on some items, but not others, and then it wouldn't boot. Tried to reflash the cricket firmware to revert back, and got the same prevalidation error for the boot image and the partition gpt.bat file, and now I can't get past the fastboot screen.
Click to expand...
Click to collapse
That sucks. That was the only thing keeping me from trying, the process of fixing it if something screwed up. Hopefully someone has an idea how to fix it since I'm not quite and expert in recoveries.
Thanks for reporting back though!
macgi77 said:
That sucks. That was the only thing keeping me from trying, the process of fixing it if something screwed up. Hopefully someone has an idea how to fix it since I'm not quite and expert in recoveries.
Thanks for reporting back though!
Click to expand...
Click to collapse
Yeah, no problem - it's possible I messed something up in the flashing operation, but I thought you'd want to know.
RonnieTheBear said:
Yeah, no problem - it's possible I messed something up in the flashing operation, but I thought you'd want to know.
Click to expand...
Click to collapse
I'm assuming you tried using the link above? Or did you try flashing each individual file and skipping the bootloader file which was talked about in the firmware thread? (I believe it was around pages 20-30 if I recall)
Found it
@JoeSyr, maybe I'm missing something here specific to Moto G LTE, but flashing a firmware image does not require an unlocked Bootloader. I would do it manually, skip most of the steps, and only flash the system.img initially.
mfastboot flash system system.img_sparsechunk1
mfastboot flash system system.img_sparsechunk2
mfastboot flash system system.img_sparsechunk3
The only way you can get into serious trouble would by flashing the motoboot.img (Bootloader) and phone no longer loads fastboot mode. But even then, is there not a hardbrick mbm-ci recovery option for Moto G 4G
Click to expand...
Click to collapse
macgi77 said:
I'm assuming you tried using the link above? Or did you try flashing each individual file and skipping the bootloader file which was talked about in the firmware thread? (I believe it was around pages 20-30 if I recall)
Found it
Click to expand...
Click to collapse
I tried running the ROM Install.bat file the guy put together in the first page you/I linked to, which did attempt to flash the bootloader. It sounds like this person you're quoting is saying the flash should be operational even just flashing those three chunks of the system image file? I think those files wrote okay, but it still didn't boot. Problem might be with this other partition file i mentioned.
RonnieTheBear said:
I tried running the ROM Install.bat file the guy put together in the first page you/I linked to, which did attempt to flash the bootloader. It sounds like this person you're quoting is saying the flash should be operational even just flashing those three chunks of the system image file? I think those files wrote okay, but it still didn't boot. Problem might be with this other partition file i mentioned.
Click to expand...
Click to collapse
That's what it sounds like. Any luck restoring the phone yet?
no, haven't really gotten a chance to mess with it, yet. I popped my sim card into an old samsung galaxy Blaze I had laying around as a backup, and I've been getting by with that for the time being. I think I've still got to figure out what the next thing I should try is. Might try asking around in some more of the subforums, here.
RonnieTheBear said:
no, haven't really gotten a chance to mess with it, yet. I popped my sim card into an old samsung galaxy Blaze I had laying around as a backup, and I've been getting by with that for the time being. I think I've still got to figure out what the next thing I should try is. Might try asking around in some more of the subforums, here.
Click to expand...
Click to collapse
Good luck, let us know how you make out.
RonnieTheBear said:
no, haven't really gotten a chance to mess with it, yet. I popped my sim card into an old samsung galaxy Blaze I had laying around as a backup, and I've been getting by with that for the time being. I think I've still got to figure out what the next thing I should try is. Might try asking around in some more of the subforums, here.
Click to expand...
Click to collapse
Any update?
macgi77 said:
Any update?
Click to expand...
Click to collapse
I tried flashing with some more tools, different firmwares, and different combinations of commands, no luck.
I found a guy in the stock firmware thread that had the exact same problem as me, and has the same cid as my phone, cid 10, which no one else seems to have. They think it might be why the preflash validation failed.
Other users suggested that if a cricket lollipop firmware image is developed at some point in the future, that would be able to flash without error. I reached out to the user to see if he ever resolved it, but didn't get a response.
Anyway, the sense that I got is that my problems were because my cid didn't match. Is yours cid 10 as well? you can check from adb. If it's not, you might be fine attempting it.
It's been a while since I checked, but I believe it is cid 10 as well. Now just hoping cricket releases Lollipop soon.....
The lollipop release for the retail (non carrier) version just came out OTA yesterday, apparently, so hopefully Cricket is not too far behind...Though it will probably take a while to go from an OTA update to a downloadable firmware image.
I contacted Motorola tech support today, they said they would replace the phone for $75 + taxes (flashing firmware via adb fastboot voids the warranty, of course), and told me it wouldn't have the Cricket firmware on it, so worst case, i would be gaining tethering ability, best case, they might send me a variant (xt1039?) that is capable of being rooted and installing a custom ROM in addition to tether. I'll probably take this option if I'm not able to get it working once the lollipop xt1045 firmware file shows up.
That's not a bad deal. Hopefully you can get it working when lollipop comes out though. Thanks for the update!

[GUIDE] How to Update OTA Step by Step on Moto g4 plus

This guide is to help out the people who are rooted to know exactly what to do if you get an OTA notification so that there are no errors.
This guide will only work for the Systemless rooting. Guide here
The basic things for achieving OTA after rooting can be found here
Basic things to keep in mind if:
1. Still on soak - Follow this guide and come back to marshmallow and then you should be able to take the OTA.
2. If you are on Stock and rooted - Make a nandroid backup and then the next step is pretty simple, go to SuperSU app and click on the option Full Unroot and click on yes and then again yes and wait for the Phone to reboot. Once it starts back wait for the optimization of the Apps and then download the OTA and then install it. Make sure it is the Stock recovery through which you flash the OTA.
It should go through Smoothly. I have done it twice. Since Nougat doesn't support any known root method yet, so keeping a titanium backup before unrooting is preferred so that as soon as it supports root u can restore all of it back.
Happy updating!
I personally won't install N until we have a rooting method. Because there is no "coming back" if root doesn't materialize.
SoNic67 said:
I personally won't install N until we have a rooting method. Because there is no "coming back" if root doesn't materialize.
Click to expand...
Click to collapse
That's true! But it'll be just a matter of time before we get it!
SoNic67 said:
I personally won't install N until we have a rooting method. Because there is no "coming back" if root doesn't materialize.
Click to expand...
Click to collapse
I have downgraded using my tutorial. And i told you that the firmware that i posted is official...
http://forum.xda-developers.com/moto-g4-plus/how-to/guide-downgrade-to-marshmallow-nougat-t3515961
TechBurner said:
I have downgraded using my tutorial. And i told you that the firmware that i posted is official...
http://forum.xda-developers.com/moto-g4-plus/how-to/guide-downgrade-to-marshmallow-nougat-t3515961
Click to expand...
Click to collapse
I don't know but XT1643, doesn't come out of the box MPJ24.139-13.1.... it comes out with 23.1 i guess...
That guide did work perfectly!
abhi212b said:
I don't know but XT1643, doesn't come out of the box MPJ24.139-13.1.... it comes out with 23.1 i guess...
That guide did work perfectly!
Click to expand...
Click to collapse
I know that works perfectly right now, the only reason i made the tutorial on how to downgrade is because we had the same scenario for Moto g 1st gen. People got used to downgrading using the normal method, what they didnt realize was that the bootloader and gpt were not being flashed and they showed failed when you did that for the official firmware. But after a month tons of Moto g 1st gens got hard bricked because of that. Anyone who tried to downgrade from modified stock or custom rom based on Lollipop (At that time) Got their phone hard bricked. It's the same for Nougat also and is same for All cross android versions after Kitkat.
With every new update they release a new partition table and a new bootloader . The new bootloader doesnt allow you to flash the previous bootloaders over it and same for partition but for some varients of the phone the warning is not there and the older bootloader is flashed resulting in a hard brick. This is also true for Custom roms based on the official firmware (which will come) and devices in which a custom kernel has been flashed.
I am not saying trust me, i am just saying be careful .
^ That's what I meant when I said "no coming back". You are stuck with a N bootloader and a MM firmware. Might work fine, might not.
Quick question
I have a XT1643
On stock rooted rom with elemental kernel.
Got an update notification yesterday.
I flashed the stock boot.img I found on the forum but the wifi is not working after flashing that.
what do I need to do in order to get it working and get the update?
Thanks
SoNic67 said:
^ That's what I meant when I said "no coming back". You are stuck with a N bootloader and a MM firmware. Might work fine, might not.
Click to expand...
Click to collapse
I agree with you on this. I am stuck with an N Bootloader and and MM firmware.
I can upgrade to an N ROM but I get FP issues (cosmetic, but still not desirable)
I cannot take an official OTA anymore because even if I downgrade to stock, I still have an N Bootloader which prevents me from taking OTA.
Unless we get a stock N rom, I guess we are stuck with this setup.
Sent from my Moto G (4) using Tapatalk
SoNic67 said:
^ That's what I meant when I said "no coming back". You are stuck with a N bootloader and a MM firmware. Might work fine, might not.
Click to expand...
Click to collapse
It will i guess because then again u can take an OTA to N ...
tandon.ayush said:
Quick question
I have a XT1643
On stock rooted rom with elemental kernel.
Got an update notification yesterday.
I flashed the stock boot.img I found on the forum but the wifi is not working after flashing that.
what do I need to do in order to get it working and get the update?
Thanks
Click to expand...
Click to collapse
Everything needs to be on stock! Stock boot, recovery, logo, kernel etc. then it works ! any modifications will lead to an error!

Categories

Resources