Database Develop

[SOLVED] Need help bigtime! accidently upgraded

I've been searching and reading to no avail and have lot's of questions and thoughts needed:
Ok, so I was avoiding updating at all cost.. But as the update notifications became more frequent. I accidentally clicked it and my phone began to reboot and update. now on 4.4.2 and here are the questions...
1. Why can't I downgrade a bootloader? (so I can root and such hackery)
2. If I unlocked my bootloader would I be able to use any of the root methods?
2a. Would I be able to use the recovery mode trick here and get SU, or root or something going?
3. Is there a way to unroll an upgrade? either by recovery or some secret downgrade recovery menu? LOL, yea I'm desperate.
My goals are:
- try and root and get the amr-wb codec for tmobile activated by editing build.prop/system files/modems WHATEVER!, it's not activated.
- I miss viper4android, A LOT!
- Just regain the control of everything
I'm willing to do whatever thru Motorola to get it downgraded, I'm am comfortable with adb, flashing, rooting, editing files, and walking into dark rooms.
So please, fill me in people.
p.s. don't tell me to search.... I'm frustrated and have been researching for days.......

Read the stickies dude. There's a complete guide in there. If you can unlock boot loader...root is easy.
If you can't unlock boot loader, no root for 4.4.2.
And no, you can't downgrade now.
Sent from my Moto X cellular telephone...
---------- Post added at 06:31 PM ---------- Previous post was at 06:30 PM ----------
Tip....the sticky you want is in general.
Sent from my Moto X cellular telephone...
---------- Post added at 06:32 PM ---------- Previous post was at 06:31 PM ----------
Also....researching for days? Come on....you're fibbing. LOL. Google "Moto x root 4.4.2"....boom.....answers.
Sent from my Moto X cellular telephone...

I'll make easy read http://forum.xda-developers.com/showthread.php?t=2635366
Sent on my Gummy running Lenoto X

drago10029 said:
1. Why can't I downgrade a bootloader? (so I can root and such hackery)
Click to expand...
Click to collapse
Because no one has found a way to do it so far. The partition where the bootloader is is not visible to you even if you are rooted.
drago10029 said:
2. If I unlocked my bootloader would I be able to use any of the root methods?
Click to expand...
Click to collapse
No not any. You don't want to use the locked bootloader root methods if your bootloader is unlocked. If you have an unlocked bootloader, you do this to root:
Rooting a Moto X With an Unlocked Bootloader
This works to root a Moto X on 4.4.2 as well as 4.4. You will be fine if you just stick to the instructions I posted.

Cozume said:
Because no one has found a way to do it so far. The partition where the bootloader is is not visible to you even if you are rooted.
No not any. You don't want to use the locked bootloader root methods if your bootloader is unlocked. If you have an unlocked bootloader, you do this to root:
Rooting a Moto X With an Unlocked Bootloader
This works to root a Moto X on 4.4.2 as well as 4.4. You will be fine if you just stick to the instructions I posted.
Click to expand...
Click to collapse
Well thanks for the response! I actually found my answer already reading through the custom recovery thread and asking there. You get a thanks anyway for your help and your post. Fyi, that post should probably be in the general section.

Cozume said:
Because no one has found a way to do it so far. The partition where the bootloader is is not visible to you even if you are rooted.
No not any. You don't want to use the locked bootloader root methods if your bootloader is unlocked. If you have an unlocked bootloader, you do this to root:
Rooting a Moto X With an Unlocked Bootloader
This works to root a Moto X on 4.4.2 as well as 4.4. You will be fine if you just stick to the instructions I posted.
Click to expand...
Click to collapse
Actually, I realized that info is inside of the general so I guess we both missed it
http://forum.xda-developers.com/showthread.php?t=2603358

drago10029 said:
Actually, I realized that info is inside of the general so I guess we both missed it
http://forum.xda-developers.com/showthread.php?t=2603358
Click to expand...
Click to collapse
My step-by-step was quoted in that post. Just follow the steps and you will be rooted. It is really easy to root your phone if you have an unlocked bootloader.

kj2112 said:
Read the stickies dude. There's a complete guide in there. If you can unlock boot loader...root is easy.
If you can't unlock boot loader, no root for 4.4.2.
And no, you can't downgrade now.
Sent from my Moto X cellular telephone...
---------- Post added at 06:31 PM ---------- Previous post was at 06:30 PM ----------
Tip....the sticky you want is in general.
Sent from my Moto X cellular telephone...
---------- Post added at 06:32 PM ---------- Previous post was at 06:31 PM ----------
Also....researching for days? Come on....you're fibbing. LOL. Google "Moto x root 4.4.2"....boom.....answers.
Sent from my Moto X cellular telephone...
Click to expand...
Click to collapse
I will admit I hadn't read the stickies thoroughly enough and when I finally did you it didn't make too much sense to me :/ ... I found my answer last night in the general thread lol. and I wouldn't lie about something like that. I have searched for days for a root method. I didn't think/know bootloader unlocking could let you root so easy.
I came from 2 samsung phones, vibrant or skyrocket if that means anything. Thanks for responding anyway!!

Cozume said:
My step-by-step was quoted in that post. Just follow the steps and you will be rooted. It is really easy to root your phone if you have an unlocked bootloader.
Click to expand...
Click to collapse
Thanks again man, I may be rooting soon. honestly, I just want try & get tmobile HD voice working and viper4android. wish their was another way b/c that's the only reason I want root.

[Q] How do I root on 4.4.2?

How do I root on 4.4.2? I have an unlocked moto x and the bootloader is unlocked

There are probably at leat 200 threads on how to do this, as well as a sticky or two. If you can't figure out how to root an unlocked phone, it's best left stock. You're asking for the basics, and if you can't figure it out, odds are you're likely to break something and have a paperweight on your hands.
Sent from my Moto X

imnuts said:
There are probably at leat 200 threads on how to do this, as well as a sticky or two. If you can't figure out how to root an unlocked phone, it's best left stock. You're asking for the basics, and if you can't figure it out, odds are you're likely to break something and have a paperweight on your hands.
Sent from my Moto X
Click to expand...
Click to collapse
Im an HTC veteran I know how to do all this stuff. I can only find ways of rooting for 4.4 not 4.4.2 and the moto x toolkit wont open for me

Toss the toolkit and see this guide. Has everything you need to know. Use fastboot and learn more about this stuff...versus clicking in a toolkit.
Complete Moto X Guide
---------- Post added at 03:43 PM ---------- Previous post was at 03:42 PM ----------
Very easy once you do it.

GhostSoldier_US said:
Im an HTC veteran I know how to do all this stuff. I can only find ways of rooting for 4.4 not 4.4.2 and the moto x toolkit wont open for me
Click to expand...
Click to collapse
Rooting an unlocked phone is the same, regardless of who the OEM is. And if you "know how to do all of this stuff", why not search and read stickies, rather than using a toolkit, which tend to cause more problems than they solve.
Sent from my Moto X

GhostSoldier_US said:
How do I root on 4.4.2? I have an unlocked moto x and the bootloader is unlocked
Click to expand...
Click to collapse
flash update supersu in recovery or if you already have twrp on your x, then when in twrp and select reboot system, it will ask if you want to root phone, at which point you say yes and it will install super su before rebooting. once it boots, there will be a notification to go to play store to update super su app and install binaries. after that, you golden.

As mentioned above. Follow one of the many guides about rooting.
Here's one: http://forum.xda-developers.com/moto-x/general/ref-how-to-root-4-4-links-guides-t2603358
Thread closed.

[Q] 4.4.2 root

Please excuse my ignorance on this topic. My rooted moto x broke and I just bought a used one. The new phone is running 4.4.2 baseband MSM8960PRO_BP_2323.031.111.OOR KERNAL 3.4.43-G27DE6975.
The last time I rooted my moto withe the cracked screened I restored back to the pre camera updata and then eventually proceeded with the slapmymoto.
Can this still be done on my current phone. I have read some conflicting threads on this
Thanks!!!

4.4.2 cannot downgrade please don't try or you will 100% brick your X. What carrier are you on?

A2Trip said:
4.4.2 cannot downgrade please don't try or you will 100% brick your X. What carrier are you on?
Click to expand...
Click to collapse
AT&T

Dont think AT&T can have unlocked bootloaders but that's easiest way to gain root access. But in development should be an exploit for 4.4.X I'll post a link. : http://forum.xda-developers.com/showthread.php?t=2771623

A2Trip said:
Dont think AT&T can have unlocked bootloaders but that's easiest way to gain root access. But in development should be an exploit for 4.4.X I'll post a link. : http://forum.xda-developers.com/showthread.php?t=2771623
Click to expand...
Click to collapse
Thanks!! before I cracked the screen on my old one I had the boot loader unlocked and root access......this sucks.

Okay so UL BL is available for AT&T? Unlock on motos site first and get code. Once unlocked you can flash TWRP or CWM through fastboot reboot to recovery and when you reboot system it will root for you. Boom! lol

pooler00 said:
Thanks!! before I cracked the screen on my old one I had the boot loader unlocked and root access......this sucks.
Click to expand...
Click to collapse
If you haven't already, check on the thread titled "China Middleman Back??" in the general sub-forum. He is selling bootloader-unlock codes for AT&T and Verizon devices. He may or may not have your code, but if not you get refunded...so no risk.
If he does, it will be absolutely fantastic for you because you won't have to rely on these exploits, and will gain permanent root-ability.
@A2Trip is completely correct in that you WILL brick your phone if you attempt to downgrade.
The middleman is your only hope.
Good Luck :good:
---------- Post added at 11:53 AM ---------- Previous post was at 11:52 AM ----------
A2Trip said:
Okay so UL BL is available for AT&T? Unlock on motos site first and get code. Once unlocked you can flash TWRP or CWM through fastboot reboot to recovery and when you reboot system it will root for you. Boom! lol
Click to expand...
Click to collapse
No. At least not from the official Moto site. Both AT&T and Verizon FORBID Moto from giving out unlock codes for their branded phones.

Got it. USC got love...that sucks.

A2Trip said:
Got it. USC got love...that sucks.
Click to expand...
Click to collapse
Agreed.
There IS a "temp-root" method already available for 4.4.2 (4.4.3+ patches it). It's the PIE exploit.
BUT!!! It is temp-only, does not allow write access to /system, does not disable write-protect, and the exploit must be run again (from ADB, so you must attach to a PC) each time you reboot...
So not very useful at all :/
---------- Post added at 12:00 PM ---------- Previous post was at 11:58 AM ----------
pooler00 said:
Thanks!! before I cracked the screen on my old one I had the boot loader unlocked and root access......this sucks.
Click to expand...
Click to collapse
You didn't have the BL unlocked if you were using SlapMyMoto - you were using a write-protect-disable exploit. BIG difference. If at any point you would have updated to 4.4.2+, you would have permanently lost root and write-protect-disable. Bootloader unlock is permanent. None of the exploits are.
Also, I KNOW someone is going to say it: Questions belong in the Q&A forum, not General. Your thread will probably be moved by a moderator..... In the future, be sure to post in the correct forums.

You're only option that I'm aware of would be pie root ( http://forum.xda-developers.com/moto-x/orig-development/root-4-4-x-pie-motorola-devices-t2771623 ). It's a tethered root though so rebooting your phone will lose root access. Also no system write.

gunvalk said:
You're only option that I'm aware of would be pie root ( http://forum.xda-developers.com/moto-x/orig-development/root-4-4-x-pie-motorola-devices-t2771623 ). It's a tethered root though so rebooting your phone will lose root access. Also no system write.
Click to expand...
Click to collapse
??? Already stated in post #4 AND post #9

Root without unlock bootloader?

I am a newbie for nexus lineup. I am going to jump to N6 from oneplus one. As far as i know from search, every post says N6 can only root after unlock bootloader. So i just want to know can i root without unlock bootloader? And is it possible to get update OS from OTA after bootloader unlock?
Sent from my A0001 using XDA Premium 4 mobile app

aungkhaingoo said:
I am a newbie for nexus lineup. I am going to jump to N6 from oneplus one. As far as i know from search, every post says N6 can only root after unlock bootloader. So i just want to know can i root without unlock bootloader? And is it possible to get update OS from OTA?
Sent from my A0001 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
you cant root your device without unlocking the bootloader. to root, you need to flash a custom recovery, then flash the supersu.zip file. none of which tou can do with a locked bootloader. in order to flash a custom recovery, you need to unlick the bootloader. and you will get an ota with root, but you cant apply it, so its pointless.

aungkhaingoo said:
I am a newbie for nexus lineup. I am going to jump to N6 from oneplus one. As far as i know from search, every post says N6 can only root after unlock bootloader. So i just want to know can i root without unlock bootloader? And is it possible to get update OS from OTA after bootloader unlock?
Sent from my A0001 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
You may be able to do this by using chainfire's autoroot tool. But why the reluctance to unlock? It's not difficult. Unlocked bootloader has no effect on accepting OTA. On the other hand, root will prevent you from accepting OTA. It's easy to fastboot flash back to stock when a new OTA becomes available. And it's even easier to download the Google factory images and fastboot flash them. Plenty of "how to" threads on the general section.
With that said, the only reason I can see for not unlocking your bootloader would be if your employer has restrictions, or your are really worried about someone stealing your device and getting your personal information.
---------- Post added at 12:16 PM ---------- Previous post was at 12:16 PM ----------
simms22 said:
you cant root your device without unlocking the bootloader. to root, you need to flash a custom recovery, then flash the supersu.zip file. none of which tou can do with a locked bootloader. in order to flash a custom recovery, you need to unlick the bootloader. and you will get an ota with root, but you cant apply it, so its pointless.
Click to expand...
Click to collapse
I seem to be walking in your footsteps today. Sorry about that.

cam30era said:
You may be able to do this by using chainfire's autoroot tool. But why the reluctance to unlock? It's not difficult. Unlocked bootloader has no effect on accepting OTA. On the other hand, root will prevent you from accepting OTA. It's easy to fastboot flash back to stock when a new OTA becomes available. And it's even easier to download the Google factory images and fastboot flash them. Plenty of "how to" threads on the general section.
With that said, the only reason I can see for not unlocking your bootloader would be if your employer has restrictions, or your are really worried about someone stealing your device and getting your personal information.
---------- Post added at 12:16 PM ---------- Previous post was at 12:16 PM ----------
I seem to be walking in your footsteps today. Sorry about that.
Click to expand...
Click to collapse
na, thats ok, even great! im just bored at work at the moment, lol

[Q] Locked bootloader, bootloop... brick?

Hi all! Im not a motorola user of any sorts, but a friend of mine, who's not a great english speaker and doesn't have an xda account, bricked, or at least so it seems, his Moto X 2014 (xt1097).
He tells me that Motorola and Google now include a checkbox in the "developer options" which, without being checked, will not allow the user to unlock the bootloader via the almighty fastboot oem unlock command.
That being said, the problem is now pretty clear: he cant access that dev option setting, because of the initial bootloop, thus being stuck with an unlock-able bootloader...
I know that it's a not good practice to go all gung ho flashing roms, without a unlocked bootloader and TWRP installed; at least I wouldn't sleep easy without them.
So... what's next? Is there a RSD method to flash the phone back to complete stock? Is there a way to check that checkbox via ADB? Any input will be much appreciated.

ad astra said:
He tells me that Motorola and Google now include a checkbox in the "developer options" which, without being checked, will not allow the user to unlock the bootloader via the almighty fastboot oem unlock command.
Click to expand...
Click to collapse
This is only true if he upgraded to 5.1, which it sounds like he did.
ad astra said:
That being said, the problem is now pretty clear: he cant access that dev option setting, because of the initial bootloop, thus being stuck with an unlock-able bootloader.
Click to expand...
Click to collapse
First what did he do to get into the bootloop? Was he part of the 5.1 soak test and then he tried to flash back to 5.0 to take the OTA?
He needs to try to get into bootloader mode. When the screen powers on, he needs to press and hold the power button until the screen turns off. Then immediately press and hold the vol down button, then after 2 seconds or so, w/o releasing the volume down, press and hold the power button. Keep pressing both power and vol down and hold them for about 4 seconds then release them both. That should get him into bootloader mode.
ad astra said:
I know that it's a not good practice to go all gung ho flashing roms, without a unlocked bootloader and TWRP installed; at least I wouldn't sleep easy without them.
Click to expand...
Click to collapse
You in fact cannot flash a ROM with a locked bootloader.
ad astra said:
So... what's next? Is there a RSD method to flash the phone back to complete stock? Is there a way to check that checkbox via ADB? Any input will be much appreciated.
Click to expand...
Click to collapse
First, get him into bootloader mode. Then you need to tell us what version of the bootloader is he on? Is it 60.14 or 60.11? And is this the Brazil XT1097?

JulesJam said:
This is only true if he upgraded to 5.1, which it sounds like he did.
Click to expand...
Click to collapse
Yep, that's exactly the case.
JulesJam said:
First what did he do to get into the bootloop? Was he part of the 5.1 soak test and then he tried to flash back to 5.0 to take the OTA?
Click to expand...
Click to collapse
If i'm not mistaken it was the other way around. He tried to update to 5.1 (I believe that the zip was form a different vendor).
JulesJam said:
He needs to try to get into bootloader mode. When the screen powers on, he needs to press and hold the power button until the screen turns off. Then immediately press and hold the vol down button, then after 2 seconds or so, w/o releasing the volume down, press and hold the power button. Keep pressing both power and vol down and hold them for about 4 seconds then release them both. That should get him into bootloader mode.
Click to expand...
Click to collapse
Already tried. The bootloader is locked. Tried to unlock (with fastboot), error appears which points to the checkbox in developer tools not being set to true.
JulesJam said:
You in fact cannot flash a ROM with a locked bootloader.
Click to expand...
Click to collapse
I understand what you mean, I meant that you can flash updates from sdcard with stock recovery.
JulesJam said:
First, get him into bootloader mode. Then you need to tell us what version of the bootloader is he on? Is it 60.14 or 60.11? And is this the Brazil XT1097?
Click to expand...
Click to collapse
Btw, he ended up sending the phone back to his carrier, for RMA, and got a new one. So.. we didn't check that. What's the difference between both? Now he managed to flash (with unlocked bootloader) the 5.1 rom and his bootloader version shows 60.16.
On the other hand, the phone's argentinian made. The flashing process which resulted in brick was as follows: 1) updated the stock 4.x.x movistar argentina rom with a brazilian 4.4.4 rom over stock recovery (he tells me that, as both roms are latinamerican, recovery update of those roms is possible). Then he seems to have updated to 5.1 soak. And then, and I dont reaaaly understand why.... he flashed another 5.1 soak that should have been only used for upgrading directly from 5.0.
The point is, he got locked out of any possible recovery method by being unable to unlock his bootlader (which we could access but was obviously locked for flashing).
Anyway, I think this thread will be of general interest so I'll continue to provide info on the case.

ad astra said:
Already tried. The bootloader is locked. Tried to unlock (with fastboot), error appears which points to the checkbox in developer tools not being set to true.
Click to expand...
Click to collapse
That wasn't the point of getting into bootloader mode. The point was to flash back to stock system. That would stop the bootloop then he could boot into system, go into settings and enable unlocking.
---------- Post added at 12:28 AM ---------- Previous post was at 12:27 AM ----------
ad astra said:
Btw, he ended up sending the phone back to his carrier, for RMA, and got a new one.
Click to expand...
Click to collapse
That is fine if that was an option, but those CLNR devices from the carriers are crap. All he had to do when he was in bootloader mode was flash back to stock.
---------- Post added at 12:29 AM ---------- Previous post was at 12:28 AM ----------
ad astra said:
The point is, he got locked out of any possible recovery method by being unable to unlock his bootlader (which we could access but was obviously locked for flashing).
Click to expand...
Click to collapse
No he did not. If you can get into bootloader mode then you can flash system back to stock, then you can boot and enable the OEM unlocking.
---------- Post added at 12:32 AM ---------- Previous post was at 12:29 AM ----------
ad astra said:
the 5.1 rom and his bootloader version shows 60.16.
Click to expand...
Click to collapse
OK so this is yet another 5.1 bootloader version. The only one I have seen is 60.14.

JulesJam said:
That wasn't the point of getting into bootloader mode. The point was to flash back to stock system. That would stop the bootloop then he could boot into system, go into settings and enable unlocking.
---------- Post added at 12:28 AM ---------- Previous post was at 12:27 AM ----------
That is fine if that was an option, but those CLNR devices from the carriers are crap. All he had to do when he was in bootloader mode was flash back to stock.
---------- Post added at 12:29 AM ---------- Previous post was at 12:28 AM ----------
No he did not. If you can get into bootloader mode then you can flash system back to stock, then you can boot and enable the OEM unlocking.
---------- Post added at 12:32 AM ---------- Previous post was at 12:29 AM ----------
OK so this is yet another 5.1 bootloader version. The only one I have seen is 60.14.
Click to expand...
Click to collapse
But how? His bootloader was locked, and we even tried to use recovery to flash back a stock image which returned an error. We tried this using adb sideload and it didn't work. We even edited the .xml file and tried the nokia flashing tool, which also resulted in a failed attempt.
Maybe im missing something... but I only know of 3 methods of flashing via bootloader:
1) fastboot command.
2) adb sideload.
3) vendor flash tool (like Odin, and nokias RDS or something like that).

ad astra said:
The flashing process which resulted in brick was as follows: 1) updated the stock 4.x.x movistar argentina rom with a brazilian 4.4.4 rom over stock recovery (he tells me that, as both roms are latinamerican, recovery update of those roms is possible). Then he seems to have updated to 5.1 soak. And then, and I dont reaaaly understand why.... he flashed another 5.1 soak that should have been only used for upgrading directly from 5.0. .
Click to expand...
Click to collapse
Thanks, so he tried to take a different model's 5.1 OTA when already on 5.1.
---------- Post added at 12:36 AM ---------- Previous post was at 12:33 AM ----------
ad astra said:
But how?
Click to expand...
Click to collapse
mfastboot flash system system.img
You need the system.img file of course for your model. This is why I encourage everyone to use Motorola Device Manager to upgrade - it leaves a copy of the image files on your computer.
---------- Post added at 12:37 AM ---------- Previous post was at 12:36 AM ----------
ad astra said:
But how? His bootloader was locked,
Click to expand...
Click to collapse
You don't need an unlocked bootloader to flash a signed image. Unlocking your bootloader is only needed to flash unsigned images and to disable write protection.
---------- Post added at 12:38 AM ---------- Previous post was at 12:37 AM ----------
ad astra said:
we even tried to use recovery to flash back a stock image which returned an error. We tried this using adb sideload and it didn't work.
Click to expand...
Click to collapse
You don't do it through recovery - you do it through bootloader mode.

JulesJam said:
Thanks, so he tried to take a different model's 5.1 OTA when already on 5.1.
---------- Post added at 12:36 AM ---------- Previous post was at 12:33 AM ----------
mfastboot flash system system.img
You need the system.img file of course for your model. This is why I encourage everyone to use Motorola Device Manager to upgrade - it leaves a copy of the image files on your computer.
---------- Post added at 12:37 AM ---------- Previous post was at 12:36 AM ----------
You don't need an unlocked bootloader to flash a signed image. Unlocking your bootloader is only needed to flash unsigned images and to disable write protection.
---------- Post added at 12:38 AM ---------- Previous post was at 12:37 AM ----------
You don't do it through recovery - you do it through bootloader mode.
Click to expand...
Click to collapse
Nice. I was about to test that :/ But i desisted because i thought it was the same as the normal fastboot... Damn, why didn't I try that when I stumbled upon that yesterday......
Thanks for the info! And also thanks for the tip on the motorola deivce manager upgrade thing. The LG suite does the same thing and so I keep my stock image safely stored.

ad astra said:
Maybe im missing something... but I only know of 3 methods of flashing via bootloader:
1) fastboot command.
Click to expand...
Click to collapse
Yes, this works. You don't need an unlocked bootloader to do it, but you do need mfastboot if the image file you have is a single image file. If you have the system already broken down into chunks, you can use regular fastboot.
ad astra said:
3) vendor flash tool (like Odin, and nokias RDS or something like that).
Click to expand...
Click to collapse
The one you want for a Moto X is the Motorola tool - RSDLite. RSDLite has mfastboot as a part of it.
You needed mfastboot to flash a single file system.img. Regular fastboot from the SDK won't work. mfastboot is motorola's version of fastboot.
Regular fastboot can only flash chunks of system. I think they have to be 256MB or less in size.
---------- Post added at 12:44 AM ---------- Previous post was at 12:41 AM ----------
ad astra said:
Nice. I was about to test that :/ But i desisted because i thought it was the same as the normal fastboot... Damn, why didn't I try that when I stumbled upon that yesterday......
Click to expand...
Click to collapse
I was trying to help you, but you didn't post back.

JulesJam said:
I was trying to help you, but you didn't post back.
Click to expand...
Click to collapse
Dont get me wrong. You did help me (thats why i left u a thanks) :good: My friend just went and did his thing on his own. I probably live in a different time zone, and my work doesn't allow me to be online the whole day. It was really late when I posted, I wasn't expecting a reply on the fly so I went to sleep. I continued this thread just because of curiosity.
On a side note, my friend checked his phone and, it seem'd alright, closed box and all. He worked a time at Motorola so he knows what was getting into. It seems the whole mess happened because of a forum post which indicated that he was flashing a soak test rom, when it was actually a final release (or something like that). This last, ended up messing up his system.

The only way to recover the original phone would have been to flash 5.1 or newer firmware to it. Had the bootloader been unlocked he could have just flashed 5.0.x without an issue(skipping motoboot and gpt).
Nobody should ever mess around with soak files unless they have an unlocked bootloader.

Steve-x said:
The only way to recover the original phone would have been to flash 5.1 or newer firmware to it. Had the bootloader been unlocked he could have just flashed 5.0.x without an issue(skipping motoboot and gpt).
Nobody should ever mess around with soak files unless they have an unlocked bootloader.
Click to expand...
Click to collapse
Agreed. Very poor judgement on behalf of my friend. Lesson learnt I guess, now he's bootloader is unlocked and he managed to flash 5.1 as previously intended.
It seems that the guy who posted the soak mistakenly posted the wrong file and caused a lot of problems for a lot of people... but, nevertheless u cant trust everything to go right... so that's my friends own fault for not unlocking, backing up and investigating enough.

i had the same problem.... any solution for bootloop Moto X 2014 whith Locked Bootloader?

Lussardi said:
i had the same problem.... any solution for bootloop Moto X 2014 whith Locked Bootloader?
Click to expand...
Click to collapse
Have you tried erasing cache and data? If that does not work you could flash your stock firmware.
Could you tell us what you did to get into your bootloop. More info helps us know how to fix your problem.
Sent from my XT1095 using Tapatalk

AGISCI said:
Have you tried erasing cache and data? If that does not work you could flash your stock firmware.
Could you tell us what you did to get into your bootloop. More info helps us know how to fix your problem.
Sent from my XT1095 using Tapatalk
Click to expand...
Click to collapse
I tried all options, fastboot erase userdata, fastboot erase cache, Flash lollipop 5.1 via RSD nothing seems works

Lussardi said:
I tried all options, fastboot erase userdata, fastboot erase cache, Flash lollipop 5.1 via RSD nothing seems works
Click to expand...
Click to collapse
You still have not told us what you did that caused the bootloop.
Sent from my XT1095 using Tapatalk

AGISCI said:
You still have not told us what you did that caused the bootloop.
Sent from my XT1095 using Tapatalk
Click to expand...
Click to collapse
I do not know ... a customer came in for repair, so do not know the reason why he stayed so.