Related
First I unlocked bootloader with DoomLord method. Then did root. Then for same stupid reason I decided to relock it with flashtool for ZX beta2 and it didn't booted. It vibrates when i push the power button, but nothing appears on the display. Then I did the unlock and root procedure with fastboot on SDK and the phone responded to be connected and commands succeeded but nothing appeared on the display. Please anybody help. What I need to do? Fastboot seems to work. When i plug in to charge the red led does not stay on - it blinks
Can you flash a firmware with flashtools?
Do you have enough battery?
Sent from my C6602 using xda premium
I tried and get error - Cannot delete D:\Flashtool\ . \firmwares\prepared\system.sin
Cannot open bundle.Flash operation canceled
Opening device forR/W
Reading device information
Unable to read from phone after having opened it
trying to continue anyway
Start flashing
Processing loader
Checking header
Ending flash session
Error in processHeader : 6 : The handle is invalid
Error flashing aborted
Close flashtool. Then download and install EMMA (official Flash Tool for Xperia devices) from Sony (https://www.google.ch/#hl=de&safe=o...le+emma+download&oq=sony+mobile+emma+download) and reflash your device with it.
Pay close attention to the instructions on the download page as you need to copy a couple files around before it works.
You need to boot to bootloader mode to flash. This achieved by totally turning off the device and holding VolDown only (not power) while connecting it to your pc.
schaggo said:
Close flashtool. Then download and install EMMA (official Flash Tool for Xperia devices) from Sony (https://www.google.ch/#hl=de&safe=o...le+emma+download&oq=sony+mobile+emma+download) and reflash your device with it.
Pay close attention to the instructions on the download page as you need to copy a couple files around before it works.
You need to boot to bootloader mode to flash. This achieved by totally turning off the device and holding VolDown only (not power) while connecting it to your pc.
Click to expand...
Click to collapse
I downloaded Emma but i cannot register. The say I have to receive an email
petetoto said:
I downloaded Emma but i cannot register. The say I have to receive an email
Click to expand...
Click to collapse
Pay close attention to the instructions on the download page as you need to copy a couple files around before it works.
Click to expand...
Click to collapse
Now I succeeded to connect phone to EMMA but it says locked phone. As I used relock option on Flashtool beta2 now how can i unlock it again? I tried DoomLord method and it gives me error write 'boot' failed. I did also the unlock process from Sony mobile provided and in the command window it says 'okay finished' but bootloader is stil locked
Excellent so far, helps narrowing down the problem.
EMMA only flashes unlocked devices, I figured you are unlocked so I recommended EMMA.
If you're locked, simply get Sony PC Companion and do a "repair" with it. Run PC Companion, boot up the phone, connect it, once PC Companion says connected click "Update firmware" or so. It should then say you're on latest firmware already and asks if you want to perform a "repair". Do so.
Just reread your post. Your device isn't booting, then of course the above doesn't work. You may try, I believe PCC also works with a device in flashmode.
However, you may also download SUS http://www.sonymobile.com/gb/tools/update-service/ and try with that. Its the counterpart of EMMA for locked devices.
Shut down your device (hold VolUp and Power for about 15 seconds, the device should vibrate 3 times in a row). Start SUS, select XZ and when it tells you to, connect your device holding VolDown ONLY. It should then do it's thing.
petetoto said:
First I unlocked bootloader with DoomLord method. Then did root. Then for same stupid reason I decided to relock it with flashtool for ZX beta2 and it didn't booted. It vibrates when i push the power button, but nothing appears on the display. Then I did the unlock and root procedure with fastboot on SDK and the phone responded to be connected and commands succeeded but nothing appeared on the display. Please anybody help. What I need to do? Fastboot seems to work. When i plug in to charge the red led does not stay on - it blinks
Click to expand...
Click to collapse
eek, precisely why i'm too scared to root my XZ.
I've never rooted before and am afraid i'll brick it!
AW: I just damaged my new XZ
samxool said:
eek, precisely why i'm too scared to root my XZ.
I've never rooted before and am afraid i'll brick it!
Click to expand...
Click to collapse
The unlocking and rooting part is not that scary as long as you have no power outage
The problem here was the relocking of the bootloader, there is no known way for that, yet.
I got my phone back thanks to schaggo .
SUS preinstalled it which means that it had been properly locked with Flashtool beta2.
But then no way to unlock again as I tried both ways known here as EMMA asked me to do.
I've rooted my previous X10i and my chieneese tablet wm8650, installed custom ROMs many times
but when I saw the black screen on my brand new XZ I just freezed, couldn't make my brain working.
Now curious about the BE - is it lost with the first unlock or it's back now?
There were some demo videos and music which are gone now and maybe this means BE is no longer working.
I wonder if there's a way to port back BE as FeraVolt did for one of his ROMs
So is your phone locked now?
Aerys said:
So is your phone locked now?
Click to expand...
Click to collapse
Locked! Stock! With all the Sim Blaaa in it! Just the ' BE - videos' are missing!
petetoto said:
Locked! Stock! With all the Sim Blaaa in it! Just the ' BE - videos' are missing!
Click to expand...
Click to collapse
oh darling, I found the way of relocking after 3 weeks of desperate waiting! thank you! thank you! thank you!
so, why do you want to unlock it again since there is root and recovery for locked now?
any way, I'll try to relock my XZ as your instruction. thank you again and again...
---------- Post added at 03:09 PM ---------- Previous post was at 02:27 PM ----------
orc.x.lei said:
oh darling, I found the way of relocking after 3 weeks of desperate waiting! thank you! thank you! thank you!
so, why do you want to unlock it again since there is root and recovery for locked now?
any way, I'll try to relock my XZ as your instruction. thank you again and again...
Click to expand...
Click to collapse
oh, could you tell me how you did relocking?...
orc.x.lei said:
oh darling, I found the way of relocking after 3 weeks of desperate waiting! thank you! thank you! thank you!
so, why do you want to unlock it again since there is root and recovery for locked now?
any way, I'll try to relock my XZ as your instruction. thank you again and again...
---------- Post added at 03:09 PM ---------- Previous post was at 02:27 PM ----------
oh, could you tell me how you did relocking?...
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2162907
And carefully read the whole thread - if you relock you won't bring back Bravia Engine also you can wait untill all the bugs are fixed
AW: I just damaged my new XZ
petetoto said:
Now curious about the BE - is it lost with the first unlock or it's back now?
Click to expand...
Click to collapse
Yes, its lost with the initial unlocking of the bootloader. Maybe it will be ported, maybe not, no way to know at this time.
I still miss an information: yours is locked now, ok, but could it be unlocked again (unlock allowed:yes vs. unlockballowed:no)?
orc.x.lei said:
so, why do you want to unlock it again since there is root and recovery for locked now?
oh, could you tell me how you did relocking?...
Click to expand...
Click to collapse
He already lost BE, DRM and stuff, why limit one self to the less convenient dealing with locked bootloader when an unlocked device offers more flexibility and ease of flashing?
Flashtool for Z beta 2, replace x10thingblah.jar (search flashtool thread), hit relock button, reflash stock with PC Companion/SUS/Flashtool, done.
schaggo said:
Yes, its lost with the initial unlocking of the bootloader. Maybe it will be ported, maybe not, no way to know at this time.
I still miss an information: yours is locked now, ok, but could it be unlocked again (unlock allowed:yes vs. unlockballowed:no)?
He already lost BE, DRM and stuff, why limit one self to the less convenient dealing with locked bootloader when an unlocked device offers more flexibility and ease of flashing?
Flashtool for Z beta 2, replace x10thingblah.jar (search flashtool thread), hit relock button, reflash stock with PC Companion/SUS/Flashtool, done.
Click to expand...
Click to collapse
I have rooting status : unknown
This was said to be a bug - already fixed I think
I haven't tried unlocking again because I'm not sure that yesterday's death of my phone is caused by the relocking
I'm gonna wait and stay on stock for a while to see if this phone works without any problems.
About the BE2 I really don't know what to think : I did some screenshot with XZ on/off and there's no difference.
Then did the same with X10i (FeraLab' s ROM with BE ported) and again didn't find a difference between all of the screenshots including XZ'
Maybe it doesn't work on your X10 either. On my Z, I can make out a difference, especially with the provided stock images, which are VERY colourful on purpose I suppose, to demonstrate the oversaturation of colours BE2 produces
But I may ask again:
1. you reflashed your phone with SUS or Flashtool
2. after the flash you did not root or try to unlock again
3. when checking now (fully stock) your unlock status is "unknown"?
I ask, because root with locked bootloaders also makes the status unknown.
ive got my phone stuck on the sony sign instaling a custom unlocked bootoader rom when my phone has locked boot loader any help atall
i had root and everything was working but after install it said to fix permissions when they were fixed i rebooted but its stuck on sony sign.
any help would be gratful.
do i need emma flash tool ? still waiting for the email so i can use it
schaggo said:
Maybe it doesn't work on your X10 either. On my Z, I can make out a difference, especially with the provided stock images, which are VERY colourful on purpose I suppose, to demonstrate the oversaturation of colours BE2 produces
But I may ask again:
1. you reflashed your phone with SUS or Flashtool
2. after the flash you did not root or try to unlock again
3. when checking now (fully stock) your unlock status is "unknown"?
I ask, because root with locked bootloaders also makes the status unknown.
Click to expand...
Click to collapse
I tried many ways, including restoring everyting with PCC, fully original stock without root, without unlock, but it still says "unknown".
Again, unlock with flashtool 2beta, OK says "unlocked yes". and relock again, "unknown", and unlock again, "yes", switching freely...
Whatever I do, BE2 is dead, forever.
Somehow there is only one thing for now, with the fake relock "unknown", PCC or US or even OTA can accept device updating or restoring.
So to get BE2 back or get "locked" status, we'd wait for devolpers to work out something.
---------- Post added at 08:16 AM ---------- Previous post was at 08:04 AM ----------
schaggo said:
Maybe it doesn't work on your X10 either. On my Z, I can make out a difference, especially with the provided stock images, which are VERY colourful on purpose I suppose, to demonstrate the oversaturation of colours BE2 produces
But I may ask again:
1. you reflashed your phone with SUS or Flashtool
2. after the flash you did not root or try to unlock again
3. when checking now (fully stock) your unlock status is "unknown"?
I ask, because root with locked bootloaders also makes the status unknown.
Click to expand...
Click to collapse
The Japanese devoloper way of locked root will make the status "unlock not allowed", whether device locked or unloced, which is just false information, don't worry.
Hey everyone,
I have a problem.
Long story short, my phone decided to commit suicide.
It seems the battery doesn't want to hold a charge any more.
I guess I have to have it sent to Sony to get fixed or replaced (Does anyone know which it will be?)
I need to check if my bootloader is unlocked or not because of course I can't send it off unlocked.
Before it died, it was on official Kit Kat from Sony, which I put on with Sony Update Service because the phone was in a boot-loop which I couldn't Flashtool out of.
Would the SUS have re-locked the bootloader and unrooted it completely?
Is there some way to check the status in my position?
Thanks
It will only be relocked if you relocked it.
Flashing with sus or pccompanion will not work with an unlocked bootloader anyway
If it was unlocked, it will still be unlocked
does your phone turn on at all?
gregbradley said:
It will only be relocked if you relocked it.
Flashing with sus or pccompanion will not work with an unlocked bootloader anyway
If it was unlocked, it will still be unlocked
does your phone turn on at all?
Click to expand...
Click to collapse
Well before I flashed with SUS I was using TWRP, which I thought needed an unlocked bootloader, but am hoping I'm wrong.
Yes, but only for about a minute at most, after having it plugged into my PC for about 10 minutes I can boot into Android but then it'll just shut itself off again, it's constantly at 1% until it dies.
You seem to not know what an unlocked bootloader is?
You do not need an unlocked bootloader to have root
Did you go trough the process of unlocking your bootloader through the sony website about unlocking the boot?
If not, then its not unlocked as you have never tried to unlock it.
If you can boot up the phone
dial *#*'7378423#*#* and goto service info / configuration. The last line will tell you the status of your boot.
Have you tried flashing the most recent 757 FTF using flashtool?
gregbradley said:
You seem to not know what an unlocked bootloader is?
You do not need an unlocked bootloader to have root
Did you go trough the process of unlocking your bootloader through the sony website about unlocking the boot?
If not, then its not unlocked as you have never tried to unlock it.
If you can boot up the phone
dial *#*'7378423#*#* and goto service info / configuration. The last line will tell you the status of your boot.
Have you tried flashing the most recent 757 FTF using flashtool?
Click to expand...
Click to collapse
I get confused sometimes my bad D:
I'll try that in the morning and let you know.
No software will detect the phone.
Brownman33 said:
Well before I flashed with SUS I was using TWRP, which I thought needed an unlocked bootloader, but am hoping I'm wrong.
Yes, but only for about a minute at most, after having it plugged into my PC for about 10 minutes I can boot into Android but then it'll just shut itself off again, it's constantly at 1% until it dies.
Click to expand...
Click to collapse
well, try plugging you phone into a wall charger for 24 hours.
If your battery is really bad a USB charger will not give it a decent charge
gregbradley said:
well, try plugging you phone into a wall charger for 24 hours.
If your battery is really bad a USB charger will not give it a decent charge
Click to expand...
Click to collapse
it says
Bootloader Unlock Allowed: Yes
Then it's locked
Sent from my C6903 using XDA Free mobile app
Hi,
I have absolutely no idea on android so need help. I have purchased a faulty Moto G (dual sim) 2nd gen and it just gets stuck on the blue moto logo screen (powered by android) for a few seconds then just switches off. I can get into the recovery screen but that's about it.
Any help would be hugely appreciated.
Red_John said:
Hi,
I have absolutely no idea on android so need help. I have purchased a faulty Moto G (dual sim) 2nd gen and it just gets stuck on the blue moto logo screen (powered by android) for a few seconds then just switches off. I can get into the recovery screen but that's about it.
Any help would be hugely appreciated.
Click to expand...
Click to collapse
Return it for a refund/exchange
Red_John said:
Hi,
I have absolutely no idea on android so need help. I have purchased a faulty Moto G (dual sim) 2nd gen and it just gets stuck on the blue moto logo screen (powered by android) for a few seconds then just switches off. I can get into the recovery screen but that's about it.
Any help would be hugely appreciated.
Click to expand...
Click to collapse
If you have not done anything to the phone, like trying to unlock the bootloader or things like that, then yes, just return the device, you got a bad apple.
SirRhor said:
If you have not done anything to the phone, like trying to unlock the bootloader or things like that, then yes, just return the device, you got a bad apple.
Click to expand...
Click to collapse
So is it not repairable?
Red_John said:
So is it not repairable?
Click to expand...
Click to collapse
It is repairable but if you still haven't unlocked your bootloader then you can just get repaired free of cost from the service center but if you decide to do it on your own, you'll have to void your warranty in order to do that!
Sent from my Moto G 2014
pranshubatra707 said:
It is repairable but if you still haven't unlocked your bootloader then you can just get repaired free of cost from the service center but if you decide to do it on your own, you'll have to void your warranty in order to do that!
Sent from my Moto G 2014
Click to expand...
Click to collapse
I think the previous owner tried to root the phone and something went wrong.
I got this message: Your device does not qualify for bootloader unlocking. after following a youtube video on unbricking moto g
Red_John said:
I think the previous owner tried to root the phone and something went wrong.
I got this message: Your device does not qualify for bootloader unlocking. after following a youtube video on unbricking moto g
Click to expand...
Click to collapse
If you bought the phone second hand and have no chance of getting your money back then you can follow these instructions.
https://motorola-global-portal.cust...il/a_id/99825/p/30,6720,9151/kw/factory reset
This will perform a factory reset on you phone and hopefully restore it to how it was.
Go to fastboot mode and tell me bootloader code?
vikasb32 said:
Go to fastboot mode and tell me bootloader code?
Click to expand...
Click to collapse
I'm not sure if this is it:
3A95920645651570#00000000000000
00000000585431303638000000#463A
54BB6B935D6E10A4163726C5FD12703
62BAC#5834D0050F000000000000000
0000000
Red_John said:
I'm not sure if this is it:
3A95920645651570#00000000000000
00000000585431303638000000#463A
54BB6B935D6E10A4163726C5FD12703
62BAC#5834D0050F000000000000000
0000000
Click to expand...
Click to collapse
What about bootloader code?
Does it say 3, 2 or 0?
Anas Karbila said:
What about bootloader code?
Does it say 3, 2 or 0?
Click to expand...
Click to collapse
Sorry for the noob question but how/where do i find that?
Red_John said:
Sorry for the noob question but how/where do i find that?
Click to expand...
Click to collapse
When you boot into bootloader mode.
Anas Karbila said:
When you boot into bootloader mode.
Click to expand...
Click to collapse
Oh right:
Device is LOCKED. Status Code: 0
Red_John said:
Oh right:
Device is LOCKED. Status Code: 0
Click to expand...
Click to collapse
Unlock it and flash factory images again.
Anas Karbila said:
Unlock it and flash factory images again.
Click to expand...
Click to collapse
Just beware that unlocking your boot loader voids your warranty.
I think you should seriously consider just doing a factory reset on your phone.
https://motorola-global-portal.custhelp.com/app/answers/prod_answer_detail/a_id/99825/p/30,6720,9151
Follow the instructions for an external reset.
Anas Karbila said:
Unlock it and flash factory images again.
Click to expand...
Click to collapse
ok i have managed to unlock and it is up and working so far....
I would like to thank everyone on this thread for their help
Red_John said:
ok i have managed to unlock and it is up and working so far....
I would like to thank everyone on this thread for their help
Click to expand...
Click to collapse
Don't say thanks press it
Moto g 2nd gen stuck in boot
Hi everyone,
Sorry for reviving thid thread. I have a moto g 2nd gen with unlocked bootloader status code: 3, it wont go past the boot animation with the globe and Motorola logo then shuts off, screen turns black with faint backlight and i have to press the power button to completely turns it off.
What i did so far.
I booted into recovery and made a cache and data wipe, didn't work.
I flashed a stock firmware. (5.02 btw) through fastboot with bootloader relock, all steps were successful but same result, wont go past animation boot.
I noticed when i issued bootloader lock command, log says successful but bootloader is still unlocked.
Also noticed phone is not detected by my pc except in fastboot mode.
Any help will be much appreciated.
Same Problem
Hi dichar,
I am having the same problem as you had. Did you ever get it resolved ??
If so, how?
Let me know please.
dihcar said:
Hi everyone,
Sorry for reviving thid thread. I have a moto g 2nd gen with unlocked bootloader status code: 3, it wont go past the boot animation with the globe and Motorola logo then shuts off, screen turns black with faint backlight and i have to press the power button to completely turns it off.
What i did so far.
I booted into recovery and made a cache and data wipe, didn't work.
I flashed a stock firmware. (5.02 btw) through fastboot with bootloader relock, all steps were successful but same result, wont go past animation boot.
I noticed when i issued bootloader lock command, log says successful but bootloader is still unlocked.
Also noticed phone is not detected by my pc except in fastboot mode.
Any help will be much appreciated.
Click to expand...
Click to collapse
I have a motorola X with unlocked bootloader, but the flash another ROM, remains intact the stock ROM. So when I try with a custom recovery also remains the stock recovery.
I want flash my phone since all process stops, and sometimes off by itself.
Thanks for any help and excuse me my english.
Model: Moto X 1053 Nextel México.
I dont think that the bootloader of your phone is properly unlocked... From what i understand your post is saying that whenever you flash anything the whole mobile doesn't takes any affects... So still it must be Write Protected... AFAIK... Do this test and make sure that your Boot loader is completely unlocked...
Power off your phone
Wait for 5 Seconds
Press and hold power button and volume down button simultaneously for 4 seconds then release those buttons...
And look out for a yellow line or a any other white line saying Device Status Code
If your bootloader is properly unlocked it must say: Device is unlocked: Status Code 3
If it gives you any other status code... Then your Boot loader might be relocked thats why it must be saying bootloader unlocked on the startup by which i assume you are saying bootloader is unlocked... Checkt these out and tell us... We are always here to help others android owners..
Good luck..
Sent from my ghost using Tapatalk
whizinc said:
I dont think that the bootloader of your phone is properly unlocked... From what i understand your post is saying that whenever you flash anything the whole mobile doesn't takes any affects... So still it must be Write Protected... AFAIK... Do this test and make sure that your Boot loader is completely unlocked...
Power off your phone
Wait for 5 Seconds
Press and hold power button and volume down button simultaneously for 4 seconds then release those buttons...
And look out for a yellow line or a any other white line saying Device Status Code
If your bootloader is properly unlocked it must say: Device is unlocked: Status Code 3
If it gives you any other status code... Then your Boot loader might be relocked thats why it must be saying bootloader unlocked on the startup by which i assume you are saying bootloader is unlocked... Checkt these out and tell us... We are always here to help others android owners..
Good luck..
Sent from my ghost using Tapatalk
Click to expand...
Click to collapse
Thanks for your help. This is the screenshot of my device.
h ttp://i.imgur.com/vENGkWY.jpg?1
cer0n said:
Thanks for your help. This is the screenshot of my device.
h ttp://i.imgur.com/vENGkWY.jpg?1
Click to expand...
Click to collapse
Okay so i saw the screenshot.. Its properly Bootloader Unlocked..
Now the chances might be that your stock recoverry is either corrupted or damaged because your phone's factory reset is not working.. Flash the stock firmware of your phone through RSD LITE... Flash the 4.4.4 version and dont donwgrade... And after flashing the stock firmware... try flashing recovery again. Find the stock firmware of your device according to your model... find the model code at the lower back side of your phone its really tiny so you to have twist the phone to make it visible...
Sent from my ghost using Tapatalk
whizinc said:
Okay so i saw the screenshot.. Its properly Bootloader Unlocked..
Now the chances might be that your stock recoverry is either corrupted or damaged because your phone's factory reset is not working.. Flash the stock firmware of your phone through RSD LITE... Flash the 4.4.4 version and dont donwgrade... And after flashing the stock firmware... try flashing recovery again. Find the stock firmware of your device according to your model... find the model code at the lower back side of your phone its really tiny so you to have twist the phone to make it visible...
Sent from my ghost using Tapatalk
Click to expand...
Click to collapse
I don't find the firmware of moto x Nextel México.
I've read in the web that has not released any firmware Nextel Mexico for moto X.
Is there any other solution?
Thank you
cer0n said:
I don't find the firmware of moto x Nextel México.
I've read in the web that has not released any firmware Nextel Mexico for moto X.
Is there any other solution?
Thank you
Click to expand...
Click to collapse
Which model is your moto x? I've seen nextel firmwares on file factory before... tell me the model of your moto x..
Edit: Sorry i forgot you mentioned above its a XT1053 nextel.. Wait for a couple of hours i have all links of stock firmware sites on my pc.. As i get back home.. I will try find a firmware for you.
Sent from my ghost using Tapatalk
whizinc said:
Which model is your moto x? I've seen nextel firmwares on file factory before... tell me the model of your moto x..
Edit: Sorry i forgot you mentioned above its a XT1053 nextel.. Wait for a couple of hours i have all links of stock firmware sites on my pc.. As i get back home.. I will try find a firmware for you.
Sent from my ghost using Tapatalk
Click to expand...
Click to collapse
Motorola X 1ra Generación (2013), Nextel México.
Ok, thank you!.
cer0n said:
Motorola X 1ra Generación (2013), Nextel México.
Ok, thank you!.
Click to expand...
Click to collapse
http://forum.xda-developers.com/moto-x/general/guide-newbies-how-to-revert-to-stock-t3104208 follow this thread this will help you for sure.
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.