Related
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
Hello all.
I rooted my Razr HD after the most recent update (prior to KitKat), so I'm rooted but not unlocked. In my ultimate wisdom, I completely removed (did not merely freeze) some bloatware apps, and only today am learning they are necessary to receive OTA updates.
A factory reset did not restore the apps.
Is it possible to get these bloatware apps back onto my device, or am I pretty much screwed?
If there is a way to restore them, am I screwed anyway due to having previously rooted my device and not having a way to flash a ROM?
My apologies if these questions are dumb; I've been looking for information regarding this for a couple hours and have come up empty so far.
Depending on what version you are currently on, you will need to get the correct FXZ image to fastboot onto your device to return it to stock.
Go here to fix you right up:
http://www.droidrzr.com/index.php/topic/45494-how-to-xt926-upgrade-to-kitkat-ota/
Sent from my Nexus 7 using Tapatalk
Thanks a lot for the advice and the links. The process seems to work ok up until it tries to flash system.img.ext4, at which point it returns the message "Phone returned FAIL.; phone connected". If I remove that one line from the XML file, everything else goes through with no issues, so that seems to be the last thing holding me back.
When I attempt to boot the phone, I receive the following:
No valid PIV block in SP for system
piv validation failed (system)
Fastboot Reason: Boot Failure
Click to expand...
Click to collapse
I will double-check some things and try one more thing before I declare myself stuck again.
Well, I'm glad I ran my double-checks because I would have wasted someone else's time otherwise. After updating to a slightly more recent version of RSD Lite, it got all the way through the reflash process.
My phone boots now. The stock apps are back. I'm letting all my apps update before I attempt the KitKat update, but I'm feeling confident about this. iBolski, I can't thank you enough, and I will love you forever.
A little help..
Thanks for posting this! However I'm running into an issue. I downloaded the latest firmware for my XT907 as well as the latest version on RSD Lite, but when I go to flash the stock image I get an error message that says "unknown fastboot command [getvar]. Any ideas??
Worked for me
Thank you iBolski. The process failed the first time I ran RSD Lite, but it worked the second time. I did not unplug the phone or take it out of Fast Boot mode before trying it the second time. This is very helpful.
froyton said:
Well, I'm glad I ran my double-checks because I would have wasted someone else's time otherwise. After updating to a slightly more recent version of RSD Lite, it got all the way through the reflash process.
My phone boots now. The stock apps are back. I'm letting all my apps update before I attempt the KitKat update, but I'm feeling confident about this. iBolski, I can't thank you enough, and I will love you forever.
Click to expand...
Click to collapse
Eustace2 said:
Thank you iBolski. The process failed the first time I ran RSD Lite, but it worked the second time. I did not unplug the phone or take it out of Fast Boot mode before trying it the second time. This is very helpful.
Click to expand...
Click to collapse
Glad it helped.
---------- Post added at 03:05 PM ---------- Previous post was at 03:00 PM ----------
moodaddy said:
Thanks for posting this! However I'm running into an issue. I downloaded the latest firmware for my XT907 as well as the latest version on RSD Lite, but when I go to flash the stock image I get an error message that says "unknown fastboot command [getvar]. Any ideas??
Click to expand...
Click to collapse
Go back to the following link and get the latest FXZ generator. SamuriHL has been updating it as people have been reporting issues:
http://www.droidrzr.com/index.php/topic/45349-rsd-script-generator/
He updated it yesterday to handle issues for your phone (XT907) and the XT926s as well. See if that fixes your issue. Otherwise, I'm not sure how else to help you.
So the usual things has happened.. I have looked many different places, forums, and posts and the closest thing I have found was this thread.
http://forum.xda-developers.com/showthread.php?t=2423716
However it didnt help me at all so now I am posting this to see if there is an angel out there that can help me.
He is the problem.
1. It will show this if I plug it in to my PC but I cant turn on the device by its self.
"AP Fastboot Flash Mode (S)
10.9B(*) (sha-1e9f557, 2013-09-25 16:26:59)
eMMC Info: Size 16GB
Device is LOCKED. Status Code: 0
Battery Low
Transfer Mode:
USB Connected
Fastboot Reason: Flash Failure"
2. It doesnt charge.. I dont think
3. When I hold the Vol- and PWR for 10 ten then add the Vol+ it sometimes will go to the bootloader and then it will boot.
Can I fix this to not show this message every time?
Thanks for your time
-Avethepizzaman
You'll need to get it charged first, before you do anything.
Sent from my HTC6525LVW using Tapatalk
RikRong said:
You'll need to get it charged first, before you do anything.
Sent from my HTC6525LVW using Tapatalk
Click to expand...
Click to collapse
K I have it charged..
Avethepizzaman said:
K I have it charged..
Click to expand...
Click to collapse
per my post in the thread you quoted,
did you download your firmware version and flash one of the files with fastboot?
any flash normally fixed this error.
bweN diorD said:
per my post in the thread you quoted,
did you download your firmware version and flash one of the files with fastboot?
any flash normally fixed this error.
Click to expand...
Click to collapse
I think so. I tried to flash this firmware using RSD Lite v6.16..
VZW_XT907_4.4.2-KDA20.62-10.1_CFC_1FF.xml
But when i go to fastboot and start to flash that firmware it gives me two errors the first one is on the phone stating.
Also does the fact the my phone in running on 4.4.2 verison 182.46.15 matter at all?
"downgraded security version
update gpt_main version failed
preflash validation failed for GPT"
and the second one is RSD starting
"Failed flashing process. 3/21 flash partition "gpt.bin" -> Phone returned FAIL."
Then I simply hold all three of my buttons on the phone and boot normally and it works.. I just need to get rid of that message.
Thanks for helping
Avethepizzaman said:
I think so. I tried to flash this firmware using RSD Lite v6.16..
VZW_XT907_4.4.2-KDA20.62-10.1_CFC_1FF.xml
But when i go to fastboot and start to flash that firmware it gives me two errors the first one is on the phone stating.
Also does the fact the my phone in running on 4.4.2 verison 182.46.15 matter at all?
"downgraded security version
update gpt_main version failed
preflash validation failed for GPT"
and the second one is RSD starting
"Failed flashing process. 3/21 flash partition "gpt.bin" -> Phone returned FAIL."
Then I simply hold all three of my buttons on the phone and boot normally and it works.. I just need to get rid of that message.
Thanks for helping
Click to expand...
Click to collapse
edit the xml file in the firmware and completely remove the line containing "gpt".
im assuming you already removed the "getvar" line because it didnt throw an error, if you didnt remove those too.
you can also remove the "erase userdata" line so it wont wipe all your data off.
after editing, save and run rsd again.
fyi, fastboot is not the same as rsd, but rsd should solve the problem just the same.
bweN diorD said:
edit the xml file in the firmware and completely remove the line containing "gpt".
im assuming you already removed the "getvar" line because it didnt throw an error, if you didnt remove those too.
you can also remove the "erase userdata" line so it wont wipe all your data off.
after editing, save and run rsd again.
fyi, fastboot is not the same as rsd, but rsd should solve the problem just the same.
Click to expand...
Click to collapse
Before I do this I have been reading that if I got the 182.46.15 update that I got on the 9/9 then im strewed and I can do anything.. should I still try what you said? Ha im a noob and kinda scared so I dont want to mess things up!
Avethepizzaman said:
Before I do this I have been reading that if I got the 182.46.15 update that I got on the 9/9 then im strewed and I can do anything.. should I still try what you said? Ha im a noob and kinda scared so I dont want to mess things up!
Click to expand...
Click to collapse
im about to go to bed, but we need to backup a bit.
did i miss where you said you have a xt907?
i just noticed thats the firmware you are trying to flash, but this is a xt925/926 forum.
i can still help you, either way, but you should try to post in the correct forum in the future to avoid confusion and flashing something wrong.
if your phone is locked, you will need the most recent firmware. then you can make the adjustments i suggested and it will work fine.
worst that would have happened by flashing the correct, but older version, is soft brick. annoying but totally fixable.
flashing the wrong phones software is generally not fixable though.
bweN diorD said:
im about to go to bed, but we need to backup a bit.
did i miss where you said you have a xt907?
i just noticed thats the firmware you are trying to flash, but this is a xt925/926 forum.
i can still help you, either way, but you should try to post in the correct forum in the future to avoid confusion and flashing something wrong.
if your phone is locked, you will need the most recent firmware. then you can make the adjustments i suggested and it will work fine.
worst that would have happened by flashing the correct, but older version, is soft brick. annoying but totally fixable.
flashing the wrong phones software is generally not fixable though.
Click to expand...
Click to collapse
Again I want to thank you for your help because its really.. helpful? Ha.
Anyway things are making sense now. I know I have the xt926 and its running 182.46.15 and its 4.4.2. So instead of flashing the wrong phone I flashed this firmware
VZW_XT926_4.4.2-KDA20.62-10.1_CFC_1FF.xml
which it the firmware for 182.46.10. I then did what you told me to do earlier on getting rid of the line containing "gpt" and the line "getvar". Now im getting new errors starting.
On RSD:
"6/19 flash tz "tz.mbn"
On PHONE:
"downgraded security version
update tz version failed
preflash validation failed for tz"
So yea... New problems.
Thanks Avethepizzaman
Avethepizzaman said:
Again I want to thank you for your help because its really.. helpful? Ha.
Anyway things are making sense now. I know I have the xt926 and its running 182.46.15 and its 4.4.2. So instead of flashing the wrong phone I flashed this firmware
VZW_XT926_4.4.2-KDA20.62-10.1_CFC_1FF.xml
which it the firmware for 182.46.10. I then did what you told me to do earlier on getting rid of the line containing "gpt" and the line "getvar". Now im getting new errors starting.
On RSD:
"6/19 flash tz "tz.mbn"
On PHONE:
"downgraded security version
update tz version failed
preflash validation failed for tz"
So yea... New problems.
Thanks Avethepizzaman
Click to expand...
Click to collapse
That's a lower version. Unless you unlocked your bootloader, which it appears you haven't, you cannot downgrade from 182.46.15. If you didn't unlock your bootloader (which I'm assuming because in your first post, you showed that the status said "locked" in fastboot mode), then you have no way to root, unlock the bootloader nor downgrade. You can only reflash the latest which is 182.46.15.
Avethepizzaman said:
Again I want to thank you for your help because its really.. helpful? Ha.
Anyway things are making sense now. I know I have the xt926 and its running 182.46.15 and its 4.4.2. So instead of flashing the wrong phone I flashed this firmware
VZW_XT926_4.4.2-KDA20.62-10.1_CFC_1FF.xml
which it the firmware for 182.46.10. I then did what you told me to do earlier on getting rid of the line containing "gpt" and the line "getvar". Now im getting new errors starting.
On RSD:
"6/19 flash tz "tz.mbn"
On PHONE:
"downgraded security version
update tz version failed
preflash validation failed for tz"
So yea... New problems.
Thanks Avethepizzaman
Click to expand...
Click to collapse
ok, i was tired and forgot about the "tz".
to avoid any further confusion, download the firmware from here and replace the xml file with this one. i already edited it. then flash again.
now that we have all the facts straight, and files in line, it should go fine this time.
Wow! thank you for making it super easy for me! Alrightly so everything flashed perfectly and it passed this time! I understand that since the new update 182.46.15 with a locked bootloader that I cannot root or unlock the bootloader. However every time I boot my phone up, it still keeps giving my warnings in the bootloader. After doing the flash I have a new bootloader failure that gives the error of.
"Fastboot Reason: Sticky bit flash_failure."
So I guess my new goal is to get rid of these bootloader errors.. Is this even possible? Thanks Again!
Avethepizzaman said:
Wow! thank you for making it super easy for me! Alrightly so everything flashed perfectly and it passed this time! I understand that since the new update 182.46.15 with a locked bootloader that I cannot root or unlock the bootloader. However every time I boot my phone up, it still keeps giving my warnings in the bootloader. After doing the flash I have a new bootloader failure that gives the error of.
"Fastboot Reason: Sticky bit flash_failure."
So I guess my new goal is to get rid of these bootloader errors.. Is this even possible? Thanks Again!
Click to expand...
Click to collapse
wow, your phone is being a pita lol
follow the instructions here to fix that.
Everything worked! I am back to normal! Thank you for everything because there was a lot of stuff that I didnt even know about! Thank you for making XDA awesome!
Avethepizzaman said:
Everything worked! I am back to normal! Thank you for everything because there was a lot of stuff that I didnt even know about! Thank you for making XDA awesome!
Click to expand...
Click to collapse
np! happy to help
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
EDIT: Looks like its not MM but some security update, so that sucks but I'd still like to know if anyone successfully got back to stock from rooted 5.1.1
Hi everyone.
I'm trying to find a way to restore my H950 to stock and completely remove any trace of root so that I can install an OTA update. I have tried installing the update with LG PC Suite and LGMobile Support Tool. Both of them say that I am on the latest software (5.1.1 H950v11?). It has been so long since I rooted it that I can't remember what method I used. If anyone has any idea how to flash it back to stock, I'd appreciate the help!
More Details:
I have an H950 (US AT&T) rooted on 5.1.1 and I just started getting an update yesterday saying that I have a system update available. When I tried to download and update, the phone I got an error while the update was still at 0%. When the phone restarted I got the "This phone is suspected in rooting..." Error.
I have tried following this thread [Guide] LG G Flex 2 Stock Firmware (Go Back to Stock) KDZ & TOT Method
but it didn't work. I got the flash utility to run but I still had SuperSU after it flashed my phone and the update still failed due to "Suspect in rooting."
I also tried following this thread [Tool] Easy Restore/Unroot Tool for LG G Flex 2 [09/15/15]!!
but I could not get it to work. The utility just hangs at "Working..."
Anyone successfully used either of these methods on an H950 with 5.1.1 to get back to stock?
Thanks in advance!
2nd method
timishue said:
EDIT: Looks like its not MM but some security update, so that sucks but I'd still like to know if anyone successfully got back to stock from rooted 5.1.1
Hi everyone.
I'm trying to find a way to restore my H950 to stock and completely remove any trace of root so that I can install an OTA update. I have tried installing the update with LG PC Suite and LGMobile Support Tool. Both of them say that I am on the latest software (5.1.1 H950v11?). It has been so long since I rooted it that I can't remember what method I used. If anyone has any idea how to flash it back to stock, I'd appreciate the help!
More Details:
I have an H950 (US AT&T) rooted on 5.1.1 and I just started getting an update yesterday saying that I have a system update available. When I tried to download and update, the phone I got an error while the update was still at 0%. When the phone restarted I got the "This phone is suspected in rooting..." Error.
I have tried following this thread [Guide] LG G Flex 2 Stock Firmware (Go Back to Stock) KDZ & TOT Method
but it didn't work. I got the flash utility to run but I still had SuperSU after it flashed my phone and the update still failed due to "Suspect in rooting."
I also tried following this thread [Tool] Easy Restore/Unroot Tool for LG G Flex 2 [09/15/15]!!
but I could not get it to work. The utility just hangs at "Working..."
Anyone successfully used either of these methods on an H950 with 5.1.1 to get back to stock?
Thanks in advance!
Click to expand...
Click to collapse
i've had success by 2nd method (stock system.img) when i flashed chinese v11z tot.
did u enabled usb debugging option?
also permitted adb access on your computer?
that window show up for a very first few seconds when your computer tries to get adb permission.
all of them fails... tell me i have v12d tot file
sjc0211 said:
i've had success by 2nd method (stock system.img) when i flashed chinese v11z tot.
did u enabled usb debugging option?
also permitted adb access on your computer?
that window show up for a very first few seconds when your computer tries to get adb permission.
all of them fails... tell me i have v12d tot file
Click to expand...
Click to collapse
Could you please upload v12d tot?
It will be very helpful.
Thanks
I cannot upload that on public because of network traffic
fyter said:
Could you please upload v12d tot?
It will be very helpful.
Thanks
Click to expand...
Click to collapse
Instead, give me private message
timishue said:
EDIT: Looks like its not MM but some security update, so that sucks but I'd still like to know if anyone successfully got back to stock from rooted 5.1.1
Hi everyone.
I'm trying to find a way to restore my H950 to stock and completely remove any trace of root so that I can install an OTA update. I have tried installing the update with LG PC Suite and LGMobile Support Tool. Both of them say that I am on the latest software (5.1.1 H950v11?). It has been so long since I rooted it that I can't remember what method I used. If anyone has any idea how to flash it back to stock, I'd appreciate the help!
More Details:
I have an H950 (US AT&T) rooted on 5.1.1 and I just started getting an update yesterday saying that I have a system update available. When I tried to download and update, the phone I got an error while the update was still at 0%. When the phone restarted I got the "This phone is suspected in rooting..." Error.
I have tried following this thread [Guide] LG G Flex 2 Stock Firmware (Go Back to Stock) KDZ & TOT Method
but it didn't work. I got the flash utility to run but I still had SuperSU after it flashed my phone and the update still failed due to "Suspect in rooting."
I also tried following this thread [Tool] Easy Restore/Unroot Tool for LG G Flex 2 [09/15/15]!!
but I could not get it to work. The utility just hangs at "Working..."
Anyone successfully used either of these methods on an H950 with 5.1.1 to get back to stock?
Thanks in advance!
Click to expand...
Click to collapse
You chose cse flash and wiped correct? If you didn't that's why my guide removes everything 100% if you follow it correctly.
Sent from my iPhone using Tapatalk
CSE flash? Sorry I didn't see that in your guide for the H950 on the AT&T network. I'm looking at your guide and not seeing the CSE Flash unless the LG Tool is the CSE FLash? I had the same problem with SuperSU left over and not able to update. I tried the default Upgrade method, then got a minios OS screen on the the Board method.
hyelton said:
You chose cse flash and wiped correct? If you didn't that's why my guide removes everything 100% if you follow it correctly.
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
It's entirely possible that I am technologically inept, but I am having the exact same issue as the OP. I followed your guide (which was very helpful) for the TOT method, and there is no option to use CSE flash, or at least it's not discussed in the instructions.
I flashed my phone twice using your TOT guide -- pretty sure I followed it to the letter. It completed successfully, but when the phone rebooted, I still had root access. I'm not sure how to unroot this thing so I can receive OTA updates (and maybe sell later on down the road).
Thanks for the help!
---------- Post added at 04:29 PM ---------- Previous post was at 03:41 PM ----------
Umm, so I found a possible solution on another thread in this forum. Maybe the answer was so simple that nobody thought to mention it. But apparently, you can just remove root access within the SuperUser app; just select "Full Unroot" or "Total Unroot" from settings. Then run this TOT flash, and you should be GTG. I am trying this now and will report as to whether I am successful.
jwhite326 said:
It's entirely possible that I am technologically inept, but I am having the exact same issue as the OP. I followed your guide (which was very helpful) for the TOT method, and there is no option to use CSE flash, or at least it's not discussed in the instructions.
I flashed my phone twice using your TOT guide -- pretty sure I followed it to the letter. It completed successfully, but when the phone rebooted, I still had root access. I'm not sure how to unroot this thing so I can receive OTA updates (and maybe sell later on down the road).
Thanks for the help!
---------- Post added at 04:29 PM ---------- Previous post was at 03:41 PM ----------
Umm, so I found a possible solution on another thread in this forum. Maybe the answer was so simple that nobody thought to mention it. But apparently, you can just remove root access within the SuperUser app; just select "Full Unroot" or "Total Unroot" from settings. Then run this TOT flash, and you should be GTG. I am trying this now and will report as to whether I am successful.
Click to expand...
Click to collapse
Rooted or not you should be able to go back to stock. And CSE flash is for the kdz method of lg flash tool. Which I didn't realize what model they were needing help with. Also with the H950 LGUP should be used instead of normal flash tool to avoid any issues with the flash tool.
Sent from my iPhone using Tapatalk
hyelton said:
Rooted or not you should be able to go back to stock. And CSE flash is for the kdz method of lg flash tool. Which I didn't realize what model they were needing help with. Also with the H950 LGUP should be used instead of normal flash tool to avoid any issues with the flash tool.
Click to expand...
Click to collapse
Hmm. Thanks for helping us out. So I am kind of confused. I reinstalled the Tot file using LGUP, and it completed successfully. I selected "REFURB" mode, and it completed successfully. But after it finished, my phone is still rooted. (I verified with root checker.) I just want to go back to stock so I can get OTA updates (and MM hopefully, when/if AT&T releases it). Now my phone won't get OTA updates because it says it's "suspected of rooting." I bought the phone used off of Swappa, so I'm not sure how exactly the original owner rooted it.
jwhite326 said:
Hmm. Thanks for helping us out. So I am kind of confused. I reinstalled the Tot file using LGUP, and it completed successfully. I selected "REFURB" mode, and it completed successfully. But after it finished, my phone is still rooted. (I verified with root checker.) I just want to go back to stock so I can get OTA updates (and MM hopefully, when/if AT&T releases it). Now my phone won't get OTA updates because it says it's "suspected of rooting." I bought the phone used off of Swappa, so I'm not sure how exactly the original owner rooted it.
Click to expand...
Click to collapse
At this point you'd be better off waiting for a KDZ of MM when it comes out for the H950. (But remember, root will probably never be achieved for our devices on MM, if that's something you care about).
I remember buying TWO H950s. Both needed the OTA for the latest Lollipop. But despite several hours, several methods, and several hours at the ATT store, I was never able to get OTAs working on either of them. It was impossible.
And supposedly impossible for several other users on XDA, who couldn't get OTAs working for their ATT Flex 2's. So even if you manage to unroot, don't get your hopes high believing OTAs will work.
Did somebody ever able to go back to stock (H950) from rooted 5.1.1? Where did you get the TOT file?
trudeo said:
Did somebody ever able to go back to stock (H950) from rooted 5.1.1? Where did you get the TOT file?
Click to expand...
Click to collapse
i think it is only for sale.
tswtech2 said:
i think it is only for sale.
Click to expand...
Click to collapse
It's not for sell.. it's on my server and it's free. Along with h it being in my back to stock thread.
Sent from my iPhone using Tapatalk
hyelton said:
It's not for sell.. it's on my server and it's free. Along with h it being in my back to stock thread.
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
oh ok . i apologize for the confusion
tswtech2 said:
oh ok . i apologize for the confusion
Click to expand...
Click to collapse
No problem. I think I've had it since March
Sent from my iPhone using Tapatalk
tswtech2 said:
oh ok . i apologize for the confusion
Click to expand...
Click to collapse
is it the v12d tot?
tswtech2 said:
is it the v12d tot?
Click to expand...
Click to collapse
11z. 12d is non existent or if it is available it's being sold for a crazy price.
Sent from my iPhone using Tapatalk
hyelton said:
11z. 12d is non existent or if it is available it's being sold for a crazy price.
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
yeah that's why i was saying it was for sale. i had you confused with this jinior member that says they have it but they aren't posting it.
tswtech2 said:
yeah that's why i was saying it was for sale. i had you confused with this jinior member that says they have it but they aren't posting it.
Click to expand...
Click to collapse
If any member is trying to sell it on the forums report them. That's not allowed and looked down upon here. I pubically post everything I have and can get for everyone
Sent from my iPhone using Tapatalk
tswtech2 said:
yeah that's why i was saying it was for sale. i had you confused with this jinior member that says they have it but they aren't posting it.
Click to expand...
Click to collapse
i flashed this v11 firmware to a [hone that had 12d and now it shows authenticate error #9. so i was looking for 12d firmware
---------- Post added at 02:16 PM ---------- Previous post was at 02:07 PM ----------
tswtech2 said:
i flashed this v11 firmware to a [hone that had 12d and now it shows authenticate error #9. so i was looking for 12d firmware
Click to expand...
Click to collapse
and now when i connect to lg support tool it says i have the latest firmware eventhough it has v11 not, v12d.