So today I set about unlocking the bootloader and rooting my Moto X 2014 Pure Edition XT1095.
Unlocking the bootloader went just fine. Then I went to root it. I booted the pure2014sb.img but it didn't work. The phone would just hang on the Motorola logo. Then I read somebody later said that doesn't work on lollipop, so I booted the CF-Auto-Root-victara-victaratmo-xt1095.img instead. That showed me the rooting status page thing before it rebooted, and then rebooted again, but when it fired up after that it was still hanging on the Motorola logo.
Then I attempted this http://forum.xda-developers.com/showthread.php?p=56928477#post56928477
Now the phone will not even hang on the logo, it gets to the animated moto logo part and then turns off half way through. I cannot get back into fastboot state either. It just doesn't respond to power + vol down at all.
EDIT: Actually scratch the not being able to get into fastboot state thing. I just had to hold the buttons down for way longer than normal. I just kept holding them until it showed something. It ended up being like 15 seconds instead of 3-4 like usual.
Help!
slak? said:
So today I set about unlocking the bootloader and rooting my Moto X 2014 Pure Edition XT1095.
Unlocking the bootloader went just fine. Then I went to root it. I booted the pure2014sb.img but it didn't work. The phone would just hang on the Motorola logo. Then I read somebody later said that doesn't work on lollipop, so I booted the CF-Auto-Root-victara-victaratmo-xt1095.img instead. That showed me the rooting status page thing before it rebooted, and then rebooted again, but when it fired up after that it was still hanging on the Motorola logo.
Then I attempted this http://forum.xda-developers.com/showthread.php?p=56928477#post56928477
Now the phone will not even hang on the logo, it gets to the animated moto logo part and then turns off half way through. I cannot get back into fastboot state either. It just doesn't respond to power + vol down at all.
EDIT: Actually scratch the not being able to get into fastboot state thing. I just had to hold the buttons down for way longer than normal. I just kept holding them until it showed something. It ended up being like 15 seconds instead of 3-4 like usual.
Help!
Click to expand...
Click to collapse
Same happened to me early this morning when I was trying to install 5.0.2
You have to flash any firmware you want just avoid to flash the modem and there ate several post here in the general section
Just remember. Don't flash the modem unless is the same firmware you have or else you will lose signal.
Regards
Thanks for the input. I used the instructions in this thread to get my phone back to working condition:
http://forum.xda-developers.com/moto-x-2014/general/guide-update-xt1095-pure-edition-to-t2937074
I was unable to get it to pick up the 4.4.4 to 5.0 update zip in recovery mode, so I just used the regular OTA update to do it. After that I booted the CF-Auto-Root-victara-victaratmo-xt1095.img and it worked!
slak? said:
Thanks for the input. I used the instructions in this thread to get my phone back to working condition:
http://forum.xda-developers.com/moto-x-2014/general/guide-update-xt1095-pure-edition-to-t2937074
I was unable to get it to pick up the 4.4.4 to 5.0 update zip in recovery mode, so I just used the regular OTA update to do it. After that I booted the CF-Auto-Root-victara-victaratmo-xt1095.img and it worked!
Click to expand...
Click to collapse
Great! Glad it helps
Enjoy the lollipop Sweet my friend.
Related
Hi all
I unlocked the bootloader, then rooted the phone then flashed a custom ROM. All went well, then for some reason the phone switched off and for a few hours it would not turn on at all. I left it on charge and eventually I could turn it back on.
However since then I have not be able to boot into fastboot made at all. When i first turn the phone on I am clicking the up volume to get into fastboot, but I never get the sony logo, instead it goes straight to the boot image from the rom (the colourful X), and it does not progress any further, I think the ROM was KA revolution.
Anyone have any ideas? I am completely stuck
and I have followed the steps here using the Update service tool from SONY http://forum.xda-developers.com/show....php?t=2216974
the phone detects fine but it tells me I have custom software and it can't be updated.
fixed now... its all good
Sorry for the bump but do you mind telling me how you got it working?
can somebody please help me? my screen just went black at work today and it does nothing at all now. if I hold the power button it vibrates once. if I hold power+volume down I get to recovery. I tried to reboot from there and I get the unlocked bootloader warning screen and from there it just goes to a black screen. so I get back to recovery and installed my back up and that didn't help at all. somebody please help me.
So the bootloader is unlocked, what else have you done to the phone?
You may need to reflash it with rsdlite.
OP you need to provide more details. are you getting the M logo? is it bootlooping? is the phone doing ANYTHING but getting in to recovery?
load the fastboot menu and use mfastboot to flash the system, boot and recovery images. you should be able to bring the phone back to life without losing data.
640k said:
OP you need to provide more details. are you getting the M logo? is it bootlooping? is the phone doing ANYTHING but getting in to recovery?
load the fastboot menu and use mfastboot to flash the system, boot and recovery images. you should be able to bring the phone back to life without losing data.
Click to expand...
Click to collapse
Im not getting the M logo. Not bootlooping. just get the warning bootloader unlocked screen. sits there for 10 seconds or so and then screen goes black. that's it.
to flash the system, boot, and recovery images. am I getting those form here:http://forum.xda-developers.com/showthread.php?t=2452246
jeb192004 said:
Im not getting the M logo. Not bootlooping. just get the warning bootloader unlocked screen. sits there for 10 seconds or so and then screen goes black. that's it.
to flash the system, boot, and recovery images. am I getting those form here:http://forum.xda-developers.com/showthread.php?t=2452246
Click to expand...
Click to collapse
just downloaded and opened that up. I don't think that's it....
Steve-x said:
So the bootloader is unlocked, what else have you done to the phone?
You may need to reflash it with rsdlite.
Click to expand...
Click to collapse
the only thing ive done to the phone is put xposed framework on it and gravity box. that was prob a month ago tho. this is the first prob ive had with the phone.
You may want to follow this guide to return the phone to stock firmware:
http://forum.xda-developers.com/showthread.php?t=2446515
You could also try commenting out the line that overwrites user data so you don't lose your data.
Try plugging your phone into the original charger and then boot to recovery, from their try rebooting while still plugged in. If that doesn't work try this again but wipe just the caches and reboot while plugged in. I have had a screen go black before on other devices and plugging the original charger(car and most others didn't work) in and booting to recovery then rebooting would get it working again.
PS When you boot to recovery check your battery level.
well...I used the moto x toolkit and returned to stock using that. everything booted up. so far everything is looking good. lost all my data but that's not that big of a deal.
640k said:
OP you need to provide more details. are you getting the M logo? is it bootlooping? is the phone doing ANYTHING but getting in to recovery?
load the fastboot menu and use mfastboot to flash the system, boot and recovery images. you should be able to bring the phone back to life without losing data.
Click to expand...
Click to collapse
Well im with the same problem but i got the M logo and is not stuck in bootlooping.... right after the boot it goes black...
Hi
I have an AT&T XT1058 with locked bootloader, on 4.4.4
I tried to rest it to factory, but it got stuck on 'Erasing...' (with the little droid) for more than an hour, so I reset it.
Since then it won't boot, only keep stuck on 'Erasing...'. I've tried reflashing it with ATT_XT1058_4.4.4-KXA21.12-L1.26_CFC_1FF both using RSD lite and manually using mfastboot, but no luck - the phone still boots to 'Erasing...' and sometimes after that to the recovery.
I didn't find anything in relevant threads. Does anyone have an idea?
Selecting 'Factory' in the bootloader seemed to fix it.
It is more comlicated than that
The phone does boot after selecting 'factory' in bootloader, but only once - turning the phone off and on again brings it back to its 'erasing...' state. Besides that the phone seems to not be able to charge the battery
mokagi said:
It is more comlicated than that
The phone does boot after selecting 'factory' in bootloader, but only once - turning the phone off and on again brings it back to its 'erasing...' state. Besides that the phone seems to not be able to charge the battery
Click to expand...
Click to collapse
Were you able to get this resolved? I have a xt1095 doing the same thing when I flash a stock recovery. Just shows the android guy and just stuck at erasing... When I flash TWRP it doesn't get stuck at the "erasing..." anymore but just boots straight into TWRP.
Sorry for the late response, I missed the notification on your message.
I wasn't able to fix it, returned it to motorola.
Hey Xda-ers,
I'm freakin out about my phone. I was using hangouts this morning and it just rebooted itself and got stuck on boot screen. It has NEVER done this before and always worked fine. I was on USS Enterprise ROM I believe. I can only get into download mode, so naturally I tried to flash stock h81120o (the version I was already on and rooted) and LGUP completed fine. Only my bootloader was still unlocked and it still was stuck on boot screen. Does anybody know what I can do to at least relock the bootloader so I can do a warranty claim with T-mobile....or get my phone back working if this is not catastrophic.
Oh I also tried holding down & power, no recovery...and cannot use the buttons to factory reset either. Then it loops and get stuck again.
Ditto
FUZER384 said:
Hey Xda-ers,
I'm freakin out about my phone. I was using hangouts this morning and it just rebooted itself and got stuck on boot screen. It has NEVER done this before and always worked fine. I was on USS Enterprise ROM I believe. I can only get into download mode, so naturally I tried to flash stock h81120o (the version I was already on and rooted) and LGUP completed fine. Only my bootloader was still unlocked and it still was stuck on boot screen. Does anybody know what I can do to at least relock the bootloader so I can do a warranty claim with T-mobile....or get my phone back working if this is not catastrophic.
Oh I also tried holding down & power, no recovery...and cannot use the buttons to factory reset either. Then it loops and get stuck again.
Click to expand...
Click to collapse
Did you ever find an answer to this ? Almost the same thing happened to me , i updated H81120p Extreme and phone booted back into Boot Screen and stayed there forever. I tried flashing H81120p using LGUP but am stuck on boot screen still.
hypervi said:
Did you ever find an answer to this ? Almost the same thing happened to me , i updated H81120p Extreme and phone booted back into Boot Screen and stayed there forever. I tried flashing H81120p using LGUP but am stuck on boot screen still.
Click to expand...
Click to collapse
infamous bootloop, hardware issue.?
raptorddd said:
infamous bootloop, hardware issue.?
Click to expand...
Click to collapse
How can i tell if this is indeed a hardware issue ? I am guessing it is though also the serial number falls in the problem range.
Hey, sorry to bother everyone with another bootloop thread by I just can't for the life of me work out if I'm doing something wrong, or my device is more of a dud than usual.
So got the phone yesterday, did some ota updates ended up in a bootloop.
Now at this point my bootloader wasn't unlockable as I hadn't enabled it in developer settings.
By some miracle it managed to boot itself back into the OS after an hour of fiddling and i decided to enable the option in developer settings.
Now I've unlocked the boot loader and got all the flashing related fastboot commands working i've
Flashed a stock image using the miflash tool, seems to succeed but then on reb but once it's done i'm still in a boot loop!
I've been able to boot into twrp a few times (though most of the time I can't and am still in a bootloop)
Tried flashing a custom rom, but I always seem to be in a boot loop after attempting that.
Throughout the last few hours i've also managed to hit the os a couple of times but it seems very easy to accidently put it back in a bootloop.
If anyone has advice of something to try, that would be great.
(was trying stock image version 10.0.9.0, going to try and go back to stock Oreo)
Smtih said:
Hey, sorry to bother everyone with another bootloop thread by I just can't for the life of me work out if I'm doing something wrong, or my device is more of a dud than usual.
So got the phone yesterday, did some ota updates ended up in a bootloop.
Now at this point my bootloader wasn't unlockable as I hadn't enabled it in developer settings.
By some miracle it managed to boot itself back into the OS after an hour of fiddling and i decided to enable the option in developer settings.
Now I've unlocked the boot loader and flashed a stock image using the miflash tool which all seems to go swimmingly, but once it's done i'm still in a boot loop!
Throughout the last few hours i've managed to get into the os a couple of times.
I've been able to boot into twrp a few times (though most of the time I can't)
Tried flashing a custom rom, but I always seem to be in a boot loop after attempting that.
Sometimes it goes to a failed to boot screen, while other times it seems to loop endlessly.
If anyone has advice of something to try, that would be great.
(was trying image version 10.0.9.0, going to try and go back to stock Oreo)
Click to expand...
Click to collapse
Try some custom kernel, or patched boot img
I've found in 3 Mi A2 phones (mine, gf and family member) the bootloop is actually easy to overcome pretty quickly by waiting. I got the bootloop with all of them when they updated to two updates from what they came with no bootloader unlocked or flashing.
In each case I plugged the phone in, and left it rapidly turning on and off. Make sure to watch the phone, it will possibly come up with an error screen a couple of times so just press to continue trying to boot (also a glitched screen maybe that says fastboot with no options, press the volume control and the option to continue appears again). After a minute or two the phone will get to the normal charging screen, at that point the bootloop is fixed just hold power button until it starts.
Longest I had to wait was coming up to 2m, one time less than 30s.
NotOverHere said:
I've found in 3 Mi A2 phones (mine, gf and family member) the bootloop is actually easy to overcome pretty quickly by waiting. I got the bootloop with all of them when they updated to two updates from what they came with no bootloader unlocked or flashing.
In each case I plugged the phone in, and left it rapidly turning on and off. Make sure to watch the phone, it will possibly come up with an error screen a couple of times so just press to continue trying to boot (also a glitched screen maybe that says fastboot with no options, press the volume control and the option to continue appears again). After a minute or two the phone will get to the normal charging screen, at that point the bootloop is fixed just hold power button until it starts.
Longest I had to wait was coming up to 2m, one time less than 30s.
Click to expand...
Click to collapse
Yeah, A2 have A/B partition and if update is faulty and the phone ends in bootloop, after a few failed boots, it will boot from other partition.
NotOverHere said:
I've found in 3 Mi A2 phones (mine, gf and family member) the bootloop is actually easy to overcome pretty quickly by waiting. I got the bootloop with all of them when they updated to two updates from what they came with no bootloader unlocked or flashing.
In each case I plugged the phone in, and left it rapidly turning on and off. Make sure to watch the phone, it will possibly come up with an error screen a couple of times so just press to continue trying to boot (also a glitched screen maybe that says fastboot with no options, press the volume control and the option to continue appears again). After a minute or two the phone will get to the normal charging screen, at that point the bootloop is fixed just hold power button until it starts.
Longest I had to wait was coming up to 2m, one time less than 30s.
Click to expand...
Click to collapse
I think something along these lines is how i managed to get into the phone the first time and enable oem unlocking.
After a lot of playing around I was able to get the phone to boot by flashing the latest Oreo image (9.6.16)
After that tried going to a pie image again from fast-boot image (10.0.8) and once again ended up in a boot loop.
Lastly I flashed a fast-boot image of the latest ota (10.0.10) and managed to boot in.
So phone is at least all working now. Thanks for everyones help. Just hope the next ota doesn't bootloop the phone again.
@NotOverHere: When the phone finally does boot up, do you find it's stable and reboots are fine after that?
Smtih said:
I think something along these lines is how i managed to get into the phone the first time and enable oem unlocking.
After a lot of playing around I was able to get the phone to boot by flashing the latest Oreo image (9.6.16)
After that tried going to a pie image again from fast-boot image (10.0.8) and once again ended up in a boot loop.
Lastly I flashed a fast-boot image of the latest ota (10.0.10) and managed to boot in.
So phone is at least all working now. Thanks for everyones help. Just hope the next ota doesn't bootloop the phone again.
@NotOverHere: When the phone finally does boot up, do you find it's stable and reboots are fine after that?
Click to expand...
Click to collapse
Plss post the link of 10.0.10