Database Develop

root for vzw moto x 4.4.2?

While we wait for real root for 4.4.2...in the meantime, I wouldn't mind having root with write protection upon reboot. Could someone walk me through the process for that? I'm more than happy to reapply any changes when the phone is rebooted (which won't be too often, hopefully)

If you're already on 4.4.2....you can't root. Can't downgrade to do the safe strap method.
If you are on 4.2.2 or 4.4....then read the safe strap thread. Also there's a couple ROMs now that apparently root and disable write protection. But again, if you are already on 4.4.2....you can't do it.

I saw it mentioned in a thread that root could exist but with write protection. Is that not true?

terrorist96 said:
I saw it mentioned in a thread that root could exist but with write protection. Is that not true?
Click to expand...
Click to collapse
You can't root on 4.4.2 period. There's no way. Simple as that.
Sent from my XT1060 using Tapatalk

DroidOnRoids said:
You can't root on 4.4.2 period. There's no way. Simple as that.
Sent from my XT1060 using Tapatalk
Click to expand...
Click to collapse
Guess I'll just wait

terrorist96 said:
Guess I'll just wait
Click to expand...
Click to collapse
That's the only thing to do. It sucks because I'm stuck too.
Sent from my XT1060 using Tapatalk

terrorist96 said:
I saw it mentioned in a thread that root could exist but with write protection. Is that not true?
Click to expand...
Click to collapse
The only way was to have it on 4.4 before taking ota. I guess root survived with write protection enabled tho.
But already being on 4.4.2.....can't root now.

This is kinda weird. I was talking to Motorola via the help app and the representative was adamant in telling me that I am able to unlock my bootloader on the Verizon version. I even said that xda developers say it cannot be unlocked but he told me it was possible and to try it. He linked me here:
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-b
Has anyone tried this?

terrorist96 said:
This is kinda weird. I was talking to Motorola via the help app and the representative was adamant in telling me that I am able to unlock my bootloader on the Verizon version. I even said that xda developers say it cannot be unlocked but he told me it was possible and to try it. He linked me here:
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-b
Has anyone tried this?
Click to expand...
Click to collapse
I think the rep told you wrong. According to this link (found on the page that you linked under the "Find Your Device" section) https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/87215, it only works with the Verizon Dev Edition. You can give it a go, but it will probably reject the attempt. If Verizon has changed their policy (highly doubtful) a lot of people would be extremely happy. Anyway, give it a shot. The worst that can happen is that it tells you that your device doesn't qualify.

Yeah, I even sent him that page saying that only the sprint, t-mobile and US Cellular versions can be unlocked. But I'll try this tomorrow. Anyone else can feel free to do so as well in the meantime.

kj2112 said:
The only way was to have it on 4.4 before taking ota. I guess root survived with write protection enabled tho.
But already being on 4.4.2.....can't root now.
Click to expand...
Click to collapse
Correct.
If you were on 4.4, you could root and disable write protection. When you took the 4.4.2 OTA, write protection became re-enabled, but you kept root. Of course this meant any changes/installs/etc made to /system and the like since taking 4.4.2 would be lost at power off/on.
Once 4.4.2 is on your phone, you can't root, and you can't disable write protection, unless you have a developer edition, or a carrier edition like Sprint, T-Mobile, etc that Moto gives out the bootloader unlock codes on their web site for. Once you unlock the bootloader you can root and write protection is disabled, and this can be done no matter what rom is on the phone.
The bounty to unlock the bootloader for VZW/ATT (who can't get codes from moto's web site), has continued to grow. No one has found a way. Same with some older Moto's too. Same with the updated GS4 and GS5, and so on.... So the chances of seeing a bootloader unlock hack are fading. Root exploits seem to get patched with each new ROM update (to root 4.4, you had to downgrade and root 4.2.2), so that is getting harder.
To be realistic, the only way to ensure you can have root and write protection disabled is to buy a Developer Edition, or from a carrier that allows you to unlock the bootloader. Yup it can cost more, and you can't customize its look, but its a small trade off if you *NEED* working root no matter what rom comes on your phone. Its a trade off I had to make, but it was easier when I did it as I was paying full price (to keep my unlimited data), and the Dev Edition was the only 32gig option for Verizon at the time.
---------- Post added at 09:46 PM ---------- Previous post was at 09:44 PM ----------
terrorist96 said:
This is kinda weird. I was talking to Motorola via the help app and the representative was adamant in telling me that I am able to unlock my bootloader on the Verizon version. I even said that xda developers say it cannot be unlocked but he told me it was possible and to try it. He linked me here:
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-b
Has anyone tried this?
Click to expand...
Click to collapse
As @HeroOfTime has said, unless Moto has reversed their course of action, Verizon and ATT non-developer phones can not receive an unlock code via Moto's web site.
That is why there was such a big "to do" about the Chinese site that was selling codes not too long ago. (which has been shut down).
Once you try it. Please let us know. There are MANY who would be very happy if Moto has changed things!!

Well, I tried and got the expected error telling me that my device wasn't eligible. Guess that Motorola rep didn't know what she was talking about. I talked to someone else and they basically confirmed it, saying you can only do it on the Dev Edition on Verizon. :\

I'll just leave this right here.... PLEASE be smart and do not start spamming him with "ETA?" and other b.s. that will make him not want to share it. We are NOT entitled to his work. If he decides to share, he will. Leave it at that.

jimmiet said:
I'll just leave this right here.... PLEASE be smart and do not start spamming him with "ETA?" and other b.s. that will make him not want to share it. We are NOT entitled to his work. If he decides to share, he will. Leave it at that.
Click to expand...
Click to collapse
He's already said that he's not going to release it. Jcase is a lost cause.

Jump on this while you can !! -> http://forum.xda-developers.com/moto-x/general/china-middleman-t2751177

terrorist96 said:
He's already said that he's not going to release it. Jcase is a lost cause.
Click to expand...
Click to collapse
He said on Twitter that it would more than likely be released just not by him.
Sent from my XT1060 using XDA Premium HD app

Well let's hope so.

And then 4.4.3 will come out. Lol

kj2112 said:
And then 4.4.3 will come out. Lol
Click to expand...
Click to collapse
His tweet did say "Don't OTA"

I've been searching for an answer to my problem and this is the best thread I have seen but....I'm a little confused. Here is what I did:
Bought a BOOST Mobile MOTO-G.
I unlocked the bootloader. I can be done on this device.
I flashed CWM from recovery. It worked fine.
From recovery, I flashed the VERIZON 4.4.2 image.
Booted the phone, activated it on PagePlus.
Went back to recovery, flashed SUPERSU. It worked....no errors.
Root checkers say I have root. I cannot use anything that needs root such as Titanium.
I connected the phone and did :
adb shell
getprop ro.boot.write_protect
It returned a 0 (zero)
Does this make sense? I just would like someone to confirm it does. Reading this thread has helped but it is the ZERO write protect thing that is throwing me.
Thanks in advance.

Dead Turbo?

So I was running CF 1.3 base for quite a while with no issues. Two days ago my phone shut down on me and would not boot. I wipe everything multiple times. I wiped cache. I did a factory reset, nothing... I wiped again. Nothing.
It gets past the Motorola logo and then just sits at the boot screen. A couple of times it would say updating android, it would finish, but then it would go right back to the boot screen. After about 8 hours it finally booted and I used it all day yesterday. This morning my issue is back. I've flashed different images to see if it has something to do with 1.3. It's all the same. I think I might try to go back to kit kat. It seems to be a software problem, but I am starting to think that something most be wrong with my hardware.
I found this thread: https://forums.motorola.com/posts/b0021413e7
I think my phone is shot... Any ideas?

When I had my Razr Maxx I had an issue that was similar and nothing I tried would fix it. Factory reset cache wipe flashing different roms nothing. Finally I decided to factory restore it with RSD Lite and after that the problem went away and I was able to do everything again like normal. I don't know why a factory reset wouldn't fix it and that did but it did.

Thanks. That is my next step. Do you know where I can find the RSD image?
Is this what I need? http://forum.xda-developers.com/dro...quark-stock-firmware-moto-maxx-droid-t3063470
Do I need to worry about flashing radios and stuff back to 4.4.4?

Seems to be. Honestly I've used it on many Motorolas in the past but I haven't read much about using RSDlite on the turbo. I would just do some googling around I'm sure you'll find it

my2cents said:
So I was running CF 1.3 base for quite a while with no issues. Two days ago my phone shut down on me and would not boot. I wipe everything multiple times. I wiped cache. I did a factory reset, nothing... I wiped again. Nothing.
It gets past the Motorola logo and then just sits at the boot screen. A couple of times it would say updating android, it would finish, but then it would go right back to the boot screen. After about 8 hours it finally booted and I used it all day yesterday. This morning my issue is back. I've flashed different images to see if it has something to do with 1.3. It's all the same. I think I might try to go back to kit kat. It seems to be a software problem, but I am starting to think that something most be wrong with my hardware.
I found this thread: https://forums.motorola.com/posts/b0021413e7
I think my phone is shot... Any ideas?
Click to expand...
Click to collapse
This just happened to me yesterday. Long story short, I have a strong suspicion that something about the recent Moto Actions update is breaking our phones for reasons that I describe here: http://forum.xda-developers.com/droid-turbo/help/complicated-problem-restore-doesnt-help-t3184251. I managed to fix it, but I re-broke it because I'm an idiot and the method I used before isn't working. If you get it fixed and get your 1.3 CF image back up and running, I would strongly recommend against allowing the Moto Actions update. I have a feeling that we're going to be hearing more about this soon from other people.

TheSt33v said:
This just happened to me yesterday. Long story short, I have a strong suspicion that something about the recent Moto Actions update is breaking our phones for reasons that I describe here: http://forum.xda-developers.com/droid-turbo/help/complicated-problem-restore-doesnt-help-t3184251. I managed to fix it, but I re-broke it because I'm an idiot and the method I used before isn't working. If you get it fixed and get your 1.3 CF image back up and running, I would strongly recommend against allowing the Moto Actions update. I have a feeling that we're going to be hearing more about this soon from other people.
Click to expand...
Click to collapse
That makes sense, after I finally got mine going, I updated Moto Actions and all the other apps it crashed again in about 12 hours. If I can finally get it to boot again, I think I am going to test your theory. If you figure out how to get it booted again, please share!
Edit, which rootjunky image did you flash? SU2-12?

my2cents said:
That makes sense. Like an idiot, after I finally got mine going, I updated Moto Actions and it crashed again. If I can finally get it to boot again, I think I am going to test your theory. If you figure out how to get it booted again, please share!
Click to expand...
Click to collapse
I did get it booted again. I flashed the kitkat update (not the stock, stock update 1, which is what you should be on if you're using mofo) file on the firmware thread that was posted here using the version of RSDlite that was posted there. The key is just to wait a really, really long time. Even if the screen goes black, it could potentially still be booting, especially if the back of the phone gets warm. I left it plugged in, let it get to the boot animation and left the house for several hours, and when I got back it appeared to be functional, but things were slow and choppy at times and my home button didn't work. The settings menu from the pull down menu didn't work either. I had to access settings from the app drawer. I tried a factory reset from the settings menu, and that just re-broke everything. So now I'm back at square one. I re-flashed the same image using RSDlite again, and now I've waited about 10 minutes and I'm still looking at the boot screen, which at this point is normal since the problem occurred.
I got a hold of an old copy of the Motorola Sensor Services apk. As far as I can tell, this is the apk that is replaced by Moto Actions, which according to Google Play is only compatible with 5.0 and above. My plan for tonight is to wait until the thing decides to boot, attempt to start the stock Sensor Services app and get it to do the sensor firmware uninstall that I mentioned in my other post. If that doesn't work, I'm going to try to install the apk that I found and see if I have any more luck with that. I'll report back here when I get a chance to do that. Let me know if you figure out a solution.
---------- Post added at 03:48 PM ---------- Previous post was at 03:33 PM ----------
my2cents said:
That makes sense, after I finally got mine going, I updated Moto Actions and all the other apps it crashed again in about 12 hours. If I can finally get it to boot again, I think I am going to test your theory. If you figure out how to get it booted again, please share!
Edit, which rootjunky image did you flash? SU2-12?
Click to expand...
Click to collapse
Yeah, I used SU2-12.

I followed the procedure outlined here to go back to stock. https://www.youtube.com/watch?v=6avEPGWB8E0 I used the SU2-12 file, but I lost everything... Thanks for the help. I hope there is a fix for this soon! I'll test your idea about MOTO Actions and report.
Edit: Well, I thought my phone was booting when I wrote the above, but it has been 30 minutes and it has not booted...

So, I can get it to boot - although it is not easy and it takes me like 30 minutes and I haven't found a full proof method yet, but after it goes to sleep I have to start the process all over. It has been a frustrating 3 days.

TheSt33v said:
This just happened to me yesterday. Long story short, I have a strong suspicion that something about the recent Moto Actions update is breaking our phones for reasons that I describe here: http://forum.xda-developers.com/droid-turbo/help/complicated-problem-restore-doesnt-help-t3184251. I managed to fix it, but I re-broke it because I'm an idiot and the method I used before isn't working. If you get it fixed and get your 1.3 CF image back up and running, I would strongly recommend against allowing the Moto Actions update. I have a feeling that we're going to be hearing more about this soon from other people.
Click to expand...
Click to collapse
I think you are onto something. I'm currently on 4.4.4 and it is bone stock. When I go into the Play Store it shows that I have Moto Actions installed, but when I click on the app it says that it is not compatible with my device. I've tried wiping the data from the app, force closing it, and clearing the cache. None of that has prompted me to uninstall the sensors. By the way, I found the Moto sensors app and tried doing the same thing, no luck.
So, I think I have the 5.1 Moto Actions installed still, which is causing the 4.4.4 image to freak out. I've thought about trying to go official 5.1 and see if that fixes it, but since I have a replacement on the way, think I might just leave it be - unless someone (like you) figures this thing out.

my2cents said:
I think you are onto something. I'm currently on 4.4.4 and it is bone stock. When I go into the Play Store it shows that I have Moto Actions installed, but when I click on the app it says that it is not compatible with my device. I've tried wiping the data from the app, force closing it, and clearing the cache. None of that has prompted me to uninstall the sensors. By the way, I found the Moto sensors app and tried doing the same thing, no luck.
So, I think I have the 5.1 Moto Actions installed still, which is causing the 4.4.4 image to freak out. I've thought about trying to go official 5.1 and see if that fixes it, but since I have a replacement on the way, think I might just leave it be - unless someone (like you) figures this thing out.
Click to expand...
Click to collapse
I ended up getting a replacement from Motorola too. If it has 5.1 on it, I'll sell it and get one with 4.4.4. Thanks a lot for the tip, by the way. I might still work on it just as a hobby, but I'm out of ideas. Of all the many, many devices I've tinkered with, this is the first one that I ever permanently messed up, so I'd like to fix it as a matter of pride, but I now only have 48 hours to do so. After looking at logcats, the partition table of the phone and the androidmanifest.xml of the motorola sensor services apk, I'm pretty much certain that this app writes those sensor drivers to a partition other than the ones that get flashed when we up/downgrade (ie system, boot, recovery, etc.), which is why these processes don't fix the problem. Theoretically, if I knew which partition that was, I could find someone with a working Turbo who could dump that image, and if I get lucky and it's a partition that isn't sig checked by the bootloader (like the radios, for example), I could flash that and be good to go. I have no idea how to figure out which partition that would be, though. The obvious choice was the "firmware" partition, but that partition has a lot of drivers that seem to relate to lots of different important things, so messing with that seems scary. I also don't know anyone who is knowledgeable enough to generate that image (myself included), so it's a moot point.

TheSt33v said:
I ended up getting a replacement from Motorola too. If it has 5.1 on it, I'll sell it and get one with 4.4.4. Thanks a lot for the tip, by the way. I might still work on it just as a hobby, but I'm out of ideas. Of all the many, many devices I've tinkered with, this is the first one that I ever permanently messed up, so I'd like to fix it as a matter of pride, but I now only have 48 hours to do so. After looking at logcats, the partition table of the phone and the androidmanifest.xml of the motorola sensor services apk, I'm pretty much certain that this app writes those sensor drivers to a partition other than the ones that get flashed when we up/downgrade (ie system, boot, recovery, etc.), which is why these processes don't fix the problem. Theoretically, if I knew which partition that was, I could find someone with a working Turbo who could dump that image, and if I get lucky and it's a partition that isn't sig checked by the bootloader (like the radios, for example), I could flash that and be good to go. I have no idea how to figure out which partition that would be, though. The obvious choice was the "firmware" partition, but that partition has a lot of drivers that seem to relate to lots of different important things, so messing with that seems scary. I also don't know anyone who is knowledgeable enough to generate that image (myself included), so it's a moot point.
Click to expand...
Click to collapse
My question is why hasn't anyone else's device gotten borked since the update? I've had it since the update was distributed with no issues and use Moto Actions continuously. Seems like if it really is a combination of writing drivers to a partition that isn't compatible it would be a universal issue. If only 2 people who have a mofo'd 5.1 IMG (out of probably hundreds) experienced issues my bet is on some weird glitch that occured when you initially flashed the updated firmware to get 5.1 working on the mofo'd device, rather than some general driver incompatibility.

GeoFX said:
My question is why hasn't anyone else's device gotten borked since the update? I've had it since the update was distributed with no issues and use Moto Actions continuously. Seems like if it really is a combination of writing drivers to a partition that isn't compatible it would be a universal issue. If only 2 people who have a mofo'd 5.1 IMG (out of probably hundreds) experienced issues my bet is on some weird glitch that occured when you initially flashed the updated firmware to get 5.1 working on the mofo'd device, rather than some general driver incompatibility.
Click to expand...
Click to collapse
I agree. Either it was a corrupt driver installation that worked just well enough for the app not to realize it, or the firmware update happens silently only when requested (similar to Google play services), and we're all one chop chop flashlight away from a phone apocalypse. Hopefully it's the former.

So, I went ahead and updated my device to official 5.1 and the problem is still there. The moto actions app that is installed still says that it is not compatible with my phone. I have cant figure out how to clear it or delete it or anything. And when I think I have it, I let the phone sleep and I can't bring it back to life again without waiting for a 15 min+ boot. Oh well, at least the bootloader says "official" now rather than "modified." So, Motorola should not complain about it. Thanks for trying to figure it out @TheSt33v

my2cents said:
So, I went ahead and updated my device to official 5.1 and the problem is still there. The moto actions app that is installed still says that it is not compatible with my phone. I have cant figure out how to clear it or delete it or anything. And when I think I have it, I let the phone sleep and I can't bring it back to life again without waiting for a 15 min+ boot. Oh well, at least the bootloader says "official" now rather than "modified." So, Motorola should not complain about it. Thanks for trying to figure it out @TheSt33v
Click to expand...
Click to collapse
Good to know. I picked the $25 option specifically because the free one requires an inspection, but I'll probably update it anyway. I'm not surprised that it didn't solve the problem though. When we flash those upgrade/downgrade images, we're basically just doing manually what RSD lite/Verizon upgrade agent does automatically.

ctopher4
TheSt33v said:
This just happened to me yesterday. Long story short, I have a strong suspicion that something about the recent Moto Actions update is breaking our phones for reasons that I describe here: http://forum.xda-developers.com/droid-turbo/help/complicated-problem-restore-doesnt-help-t3184251. I managed to fix it, but I re-broke it because I'm an idiot and the method I used before isn't working. If you get it fixed and get your 1.3 CF image back up and running, I would strongly recommend against allowing the Moto Actions update. I have a feeling that we're going to be hearing more about this soon from other people.[/QUO​TE]
you called it! Just spent 2 hours reflashing 1.3 first repeated V4A, then Base. flashing sick Android upon Recovery attempt, FAIL. reflashed radios and such and with different "vol& pwr" sequence was able to get in to wipe cache. Not hat it would help me but i viewed chche Logs and im wondering if, to the right person, it would help to have copies of them?? It's a bunch of pages tho and and not sure if it would help.
My plan it to, in Recovery, Factory wipe, then reboot to Bootloader and attempt to flash base. W/ all sys.img's, then wipe caches again. ihave read the whole thread early yesterday morning but i fell asleep prob 20 times during. it was like 3 ishi think SO, i'll now go re read probably to find that you've already ruled out "my plan"
Click to expand...
Click to collapse

ctopher4 said:
TheSt33v said:
This just happened to me yesterday. Long story short, I have a strong suspicion that something about the recent Moto Actions update is breaking our phones for reasons that I describe here: http://forum.xda-developers.com/droid-turbo/help/complicated-problem-restore-doesnt-help-t3184251. I managed to fix it, but I re-broke it because I'm an idiot and the method I used before isn't working. If you get it fixed and get your 1.3 CF image back up and running, I would strongly recommend against allowing the Moto Actions update. I have a feeling that we're going to be hearing more about this soon from other people.[/QUO​TE]
you called it! Just spent 2 hours reflashing 1.3 first repeated V4A, then Base. flashing sick Android upon Recovery attempt, FAIL. reflashed radios and such and with different "vol& pwr" sequence was able to get in to wipe cache. Not hat it would help me but i viewed chche Logs and im wondering if, to the right person, it would help to have copies of them?? It's a bunch of pages tho and and not sure if it would help.
My plan it to, in Recovery, Factory wipe, then reboot to Bootloader and attempt to flash base. W/ all sys.img's, then wipe caches again. ihave read the whole thread early yesterday morning but i fell asleep prob 20 times during. it was like 3 ishi think SO, i'll now go re read probably to find that you've already ruled out "my plan"
Click to expand...
Click to collapse
Damn. I was hoping I was wrong. Yeah, I did what you suggested many, many times. If you end up reflashing 4.4.4 and you see the message to uninstall the sensor firmware, do it and FLASH NOTHING ELSE until a solution is found. If not, it's really easy to get a new one from Motorola.
Click to expand...
Click to collapse

TheSt33v said:
ctopher4 said:
Damn. I was hoping I was wrong. Yeah, I did what you suggested many, many times. If you end up reflashing 4.4.4 and you see the message to uninstall the sensor firmware, do it and FLASH NOTHING ELSE until a solution is found. If not, it's really easy to get a new one from Motorola.
Click to expand...
Click to collapse
O Jeez, xda gave me a " token timed out message" but only after I hit post reply and, it was a novel! I have to get at least 2.5 hours sleep tonight because that been normal lately. Besides setting up Moto functionality, I'm golden and I do have their updates blocked best I can anyway. Hope all is working.
Click to expand...
Click to collapse

ctopher4 said:
TheSt33v said:
O Jeez, xda gave me a " token timed out message" but only after I hit post reply and, it was a novel! I have to get at least 2.5 hours sleep tonight because that been normal lately. Besides setting up Moto functionality, I'm golden and I do have their updates blocked best I can anyway. Hope all is working.
Click to expand...
Click to collapse
Awesome! Well I managed to fix it too, Moto functionality included!!!! I'll explain on my other thread.
Click to expand...
Click to collapse

What was the solution that found? I'm going through the same problem.

Root Removal

Hi I have a DROID Turbo that currently has the MOFO Rooted ROM installed. I have to send my in for the screen replacement, but need to remove the Root as this voids the warranty. I have went to the SU app and clicked on the remove root, but am unsure if that is all I need to do besides wiping my cell.

raxhunter said:
Hi I have a DROID Turbo that currently has the MOFO Rooted ROM installed. I have to send my in for the screen replacement, but need to remove the Root as this voids the warranty. I have went to the SU app and clicked on the remove root, but am unsure if that is all I need to do besides wiping my cell.
Click to expand...
Click to collapse
I had to use the screen replacement last summer for my first Turbo, which was purchased from Verizon around Thanksgiving 2014. I never took an OTA update and got MOFO root as soon as it came out. I'm not sure if this works for everyone, but the only way I was able to have the "Modified" Software status on bootloader changed to Unmodified before I sent it back for replacement was to plug it into a windows computer with Verizon's Upgrade Assistant installed, wipe everything and reset to factory (backup anything you want to save first), and let it update. I couldn't read the screen but after letting the busted phone update, I do remember somewhere within the Verizon application it stated the software status was Unmodified (or what ever else it's supposed to say).
Not sure if it will work for you but it's something to try.

Thank you for the info... I'll give it a try

raxhunter said:
Thank you for the info... I'll give it a try
Click to expand...
Click to collapse
If that doesn't work, you might have to purchase moforoot or Sunshine in order to flash an unrooted image, and to get rid of the Modified line.

I tried the rootjunky unroot, but still see the modified line in boot. I also tried the VZW update tool, but the communications seem to stop around 17 of 20 packets... I've been stumped all day... Can you post a link for the MOFO unmodified image? Or the sunshine rout... I've paid for the MOFO root, so maybe I don't need to buy it...
Thanks in advance

raxhunter said:
I tried the rootjunky unroot, but still see the modified line in boot. I also tried the VZW update tool, but the communications seem to stop around 17 of 20 packets... I've been stumped all day... Can you post a link for the MOFO unmodified image? Or the sunshine rout... I've paid for the MOFO root, so maybe I don't need to buy it...
Thanks in advance
Click to expand...
Click to collapse
I'm not sure about this article's reliability, but it looked like it could help you.
Or you can download these files for the appropriate firmware version and flash them after unlocking with Sunshine.
Your best bet would be to flash the stock system image with mofo. Unfortunately, I was unable to find the flashable moforoot unrooted image.
I'm unsure if this would change the Modified line to Unmodified; if it doesn't than I have no idea.
Additionally, Motorola offers a repair service where you can send in a device to be repaired either for a small fee or for free. With the paid option, they don't inspect the actual device, and they send you a new phone. This could be used as a last resort.

I tried the article... The downgrade didn't work... I'll see if sunshine will work...

The sunshine one is the same one I tried earlier from rootjunky... The software line in the boot still sez modified, but the software in the about phone area sez official.. Dunno...

You might have to just use the Motorola service. Why do you want to get rid of the Modified line, again?

raxhunter said:
I tried the rootjunky unroot, but still see the modified line in boot. I also tried the VZW update tool, but the communications seem to stop around 17 of 20 packets... I've been stumped all day... Can you post a link for the MOFO unmodified image? Or the sunshine rout... I've paid for the MOFO root, so maybe I don't need to buy it...
Thanks in advance
Click to expand...
Click to collapse
Factory reset, then use the Verizon update tool? Wait for it to actually finish? It probably takes a long time.
Sent from my XT1254 using Tapatalk

Latiken said:
You might have to just use the Motorola service. Why do you want to get rid of the Modified line, again?
Click to expand...
Click to collapse
The screen is cracked, VZW will replace the screen for free if phone is less then 1yr old, but in the return box there is a clause for modified software that won't cover the broken screen.

SpyderPride said:
Factory reset, then use the Verizon update tool? Wait for it to actually finish? It probably takes a long time.
Sent from my XT1254 using Tapatalk
Click to expand...
Click to collapse
That's what I tried... It gets to about packet 17 of 20 then the screen sez lost communication... It's weird because onbthe cell is sez USB connected...

raxhunter said:
The screen is cracked, VZW will replace the screen for free if phone is less then 1yr old, but in the return box there is a clause for modified software that won't cover the broken screen.
Click to expand...
Click to collapse
You don't have to use Verizon's service. There's two options you can use, both from Motorola: a paid one and a free one. The link is in one of my previous posts.
Someone on the forum said that with the paid option, they send you a new (or very well refurbished) Turbo without looking at your current device (so they wouldn't penalize you for it being modded.)
The free option is a bit more iffy. The same someone said that they check the device, but Motorola didn't specify if they check the software, or just the hardware.
The paid option would be your best bet, but you can opt for the free option if you feel a bit risky.

Any help rooting Samsung Tab E

I've spent the last couple of days looking for a way to root, but I've come up empty. Apparently not many people own this tablet, even though it's sold at Verizon?
The model number is SM-T567V
If anyone knows of a way to root it, or some alternative method that worked for them, nothing is too crazy at this point, lol.

Lncorporate said:
I've spent the last couple of days looking for a way to root, but I've come up empty. Apparently not many people own this tablet, even though it's sold at Verizon?
The model number is SM-T567V
If anyone knows of a way to root it, or some alternative method that worked for them, nothing is too crazy at this point, lol.
Click to expand...
Click to collapse
No chance, it's a bootloader locked device.
Kingroot or kingOroot are your only hope.

ashyx said:
No chance, it's a bootloader locked device.
Kingroot or kingOroot are your only hope.
Click to expand...
Click to collapse
Crapsicle; I've been able to get the root to work on kingo root, but then anytime my tablet needs restarting it goes into a bootloop. Any insight in regards to a possible fix?
If not I'll probably return it in exchange for an iPad.

Lncorporate said:
Crapsicle; I've been able to get the root to work on kingo root, but then anytime my tablet needs restarting it goes into a bootloop. Any insight in regards to a possible fix?
If not I'll probably return it in exchange for an iPad.
Click to expand...
Click to collapse
Now you have root, try and reroot with kingroot then remove kingo.
Samsung has Kernels which restrict rooting, but Kingroot has good success at circumventing this.

gained root but still loops
used the kingoroot way mentioned then ran kingroot gained root 100% working removed kingoroot everything seemed to go well tried to reboot and right back into the bootloop so can get root but can not reboot device
---------- Post added at 12:46 AM ---------- Previous post was at 12:42 AM ----------
just got this tablet my self a few days ago and been trying to gain root since super annoying to say the least but something should pop up soon for it cause its not a terrible tablet so if root can be gained already something just has to be tweaked to fix bootloop i can deff see it being fixed also is any know dev wanna look into this i wouldnt mind throwing ya some money for fixing boot loop issue with rooting.

I got the same result, it seems unlikely that there will be a root mostly because apparently Verizon goes out of their way to prevent users from rooting. But I don't know much about the android rooting scene so don't take my word for it.
I actually just ended up exchanging mines for an iPad, there's currently a working Jailbreak.

psychatog64 said:
used the kingoroot way mentioned then ran kingroot gained root 100% working removed kingoroot everything seemed to go well tried to reboot and right back into the bootloop so can get root but can not reboot device
---------- Post added at 12:46 AM ---------- Previous post was at 12:42 AM ----------
just got this tablet my self a few days ago and been trying to gain root since super annoying to say the least but something should pop up soon for it cause its not a terrible tablet so if root can be gained already something just has to be tweaked to fix bootloop i can deff see it being fixed also is any know dev wanna look into this i wouldnt mind throwing ya some money for fixing boot loop issue with rooting.
Click to expand...
Click to collapse
If you hot reboot you won't lose root.
DONATE ME HERE IF YOU WANT TO BUY ME A BEER OR HIT THE THANKS BUTTON IF I HELPED YOU

It's not loosening root I'm concerned with as I got it to stick last night just the boot loop is the issue for some reason king root by it self will not give me permanent root so I have to use both programs

looking for a Moto X4 with unlockable bootloader

I am going to buy this.
https://www.amazon.com/gp/product/B07BDW3GV8/ref=ox_sc_act_title_1?smid=AWH9OQ2LSV12U&psc=1
I asked the seller but no answer.
could some one tell me?
thank you so much

Help me please

Yes it is unlockable. Make sure you buy the unlocked version and not the Alexa or Android One version.
To unlock it, you first have to enable "OEM Unlocking" in developer options, then use fastboot to unlock the bootloader in fastboot mode on the phone.

You can't root those phones from Amazon. I got one and had to return it. Ended up getting a Google fi model (bare bones android, no bloat) and it was like 50 bucks cheaper than amazon but I did go with their service. End of story is that I unlocked the phone directly from Motorola and I rooted it no problem with Magisk.
https://fi.google.com/account#buydevices

Arsenal420 said:
You can't root those phones from Amazon. I got one and had to return it. Ended up getting a Google fi model (bare bones android, no bloat) and it was like 50 bucks cheaper than amazon but I did go with their service. End of story is that I unlocked the phone directly from Motorola and I rooted it no problem with Magisk.
https://fi.google.com/account#buydevices
Click to expand...
Click to collapse
I just bought a Moto X4 on Swappa with the Android One logo on the back. I was doing some reading and started getting worried that I wouldn't be able to unlock the bootloader. Thank you for confirming that it can be done on the Google Fi/Android One model.

TadMSTR said:
I just bought a Moto X4 on Swappa with the Android One logo on the back. I was doing some reading and started getting worried that I wouldn't be able to unlock the bootloader. Thank you for confirming that it can be done on the Google Fi/Android One model.
Click to expand...
Click to collapse
No problem sir. Not saying you use this piece of technology but I could not get Xposed Framework to work on that phone. No matter how I tried it would boot loop my phone. Additionally if you are going to root it then you want to be aware of this thread:
https://forum.xda-developers.com/moto-x4/how-to/guide-how-to-flash-official-factory-t3808348
It has the factory roms for all three builds (amazon, fi and retail) so you're fairly safe if something goes wrong.
Good luck!

Arsenal420 said:
No problem sir. Not saying you use this piece of technology but I could not get Xposed Framework to work on that phone. No matter how I tried it would boot loop my phone. Additionally if you are going to root it then you want to be aware of this thread:
https://forum.xda-developers.com/moto-x4/how-to/guide-how-to-flash-official-factory-t3808348
It has the factory roms for all three builds (amazon, fi and retail) so you're fairly safe if something goes wrong.
Good luck!
Click to expand...
Click to collapse
I haven't used Xposed in some time but thanks for the heads up. I do plan on rooting. Get everything I need from Magisk with a few modules. I wanted to use CarbonROM but looks like it hasn't been updated in some time. Lineage will work just fine as it's an official release with regular updates.

TadMSTR said:
I haven't used Xposed in some time but thanks for the heads up. I do plan on rooting. Get everything I need from Magisk with a few modules. I wanted to use CarbonROM but looks like it hasn't been updated in some time. Lineage will work just fine as it's an official release with regular updates.
Click to expand...
Click to collapse
Lineage works well, but be careful the last three (3) updates broke my phone.
You can recover it,but it is anoying as hell.

Posting in case anyone else runs into this issue. I received a used Moto X4 I bought on Swappa. This is the Android One version; still had a Fi sim in it. It appears a factory reset was done but when I went into developer options to allow oem unlocking the slider was greyed out. While troubleshooting I saw an option in the bootloader called Factory and decided to try it. I assumed that was a factory reset but it didn't appear to do so as I didn't have to run through the initial setup again. Though I did have to re-enable developer options, so something got reset. This time the slider to allow oem unlocking was no longer greyed out. I was then able to unlock the bootloader.
---------- Post added at 05:25 PM ---------- Previous post was at 04:33 PM ----------
JensKuehnel said:
Lineage works well, but be careful the last three (3) updates broke my phone.
You can recover it,but it is anoying as hell.
Click to expand...
Click to collapse
I'm running the 10/17 build and all seems okay.