Hi Guys
I have the XT1092 with the GB ROM installed and I am having some serious trouble getting it to update to android 5.0 I have unlocked the bootloader.
I must have downloaded and tried to install the update for 5.0 about 6-7 times now. I have tried clearing the cache and installing afterwards, this did nothing and also doing a factory reset and installing it after and I get the same problem.
The phone reboots, thers a screen with the android on his back with 'system update installing' and then it gets about 25% through, briefly an exclamation mark appears and the phone reboots.
It goes back into the 4.4.4 and then a screen appears saying 'Software update unsuccessful sorry there was a problem updating your Motox, No changes were made'.
Is there anything else I can try?
I did try to flash the EU ROM on not long ago and I gave up, is there anyway I can put a fresh GB Rom and flash everything back on again from scratch?
Any help is appreciated
Cheers
Alex
Ok I have flashed the EU 4.4.4 rom found on another thread, Now I am struggling with ADB.
When I run System update it shows that the EU 4.4.4 rom is now installed all good and proper but it
says I am all up to date, The liar!
So I am trying to sideload the 5.0 update to my device using adb. The strange thing is, that when the phone is powered on in the 4.4.4 and I run a 'adb devices' command I can see the phone there in the list of devices.
But when I put it into recovery and select the adb sideload option it is not coming up on the 'adb devices' command
Anyone know why?
Related
So here's the deal. I had a Moto X Dev Edition with TWRP recovery and the latest CyanogenMod ROM, working properly.
I returned to stock using a Motorola ROM and their instructions, did get a gpt_main error in the process, but since it worked for a certain Reddit user (goo.gl/2sEmjz -- can't post links yet!) I decided to continue. It booted fine into stock, but when I did system updates, it would reboot into TWRP. So I flashed the recovery.img file. After that, the phone booted, then rebooted, and went into a recovery "installing updates."
I walked away for a second, came back, and the screen was black. I can't "force it off," it doesn't appear to be running, and I can't get into fastboot. Is the phone bricked (which I'm leaning to), or is it still running and I just need the battery to run out, or is there some other way to revive this phone via USB?
Hoping there's some expert I can get advice from, and thanks in advance!
Hi guys.
I have a moto X 1058 which I bought to someone about 3 months ago, it's an used phone so I can't rely on warranty.
I received the phone with Android 5.0, no root, bootloader locked, perfect conditions.
I installed Android 5.1 through an OTA update. Soon after the update, the phone began to boot suddenly every now and then with no apparent reason. Because of this I decided to downgrade to Kitkat 4.4.4 (The rom I downloaded is called: RETAIL-BR_4.4.4_KXA21.12-L1.26_52_cid12_CFC_1FF) (I am from Colombia and the firmware of the phone is from Brazil). I used RSD lite, unlocked the bootloader, USB debug, etc. However the installing took way too long so I booted the phone while it was still installing (If i didn't do this, the installing would have probably taken 8 hours or so, because the system.img file was too big to download to the phone which is why i guess it took RSD so long). Anyways, I don't know why this happened, I just decided to boot it and see what happened. It went in a boot loop. I no longer have access to the bootloader screen. After two boots I can press POWER+VOLUME UP to get access to the screen "Android system recovery". Where the only options are:
reboot system now (takes me to the boot loop again)
apply update from sdcard (does nothing really)
aply update from ADB (My pc won't recognize my device anymore, RSD litle doesn't recognize my device either, I tried with mfastboot manually but it says "waiting for device" and does nothing)
wipe data/factory reset (tried this option as well, but nothing)
wipe cache partition (nope).
What can I do? I think this means my phone is soft bricked. How can I fix this? How can I get the bootloader screen back? I can't even turn off my phone, it's stuck in this bootloop. The only thing i can do is to stay in the system recovery screen, but i don't know what to do next. I don't handle Android systems at all, everything I did was based on youtube tutorials, so I'm a little slow to understand the basic concepts. Can someone explain me?
Thank you very much.
You don't downgrade Motorola phones!
Sent from my iPad using Tapatalk
Is your device fixed now?
mlspot said:
Hi guys.
I have a moto X 1058 which I bought to someone about 3 months ago, it's an used phone so I can't rely on warranty.
I received the phone with Android 5.0, no root, bootloader locked, perfect conditions.
I installed Android 5.1 through an OTA update. Soon after the update, the phone began to boot suddenly every now and then with no apparent reason. Because of this I decided to downgrade to Kitkat 4.4.4 (The rom I downloaded is called: RETAIL-BR_4.4.4_KXA21.12-L1.26_52_cid12_CFC_1FF) (I am from Colombia and the firmware of the phone is from Brazil). I used RSD lite, unlocked the bootloader, USB debug, etc. However the installing took way too long so I booted the phone while it was still installing (If i didn't do this, the installing would have probably taken 8 hours or so, because the system.img file was too big to download to the phone which is why i guess it took RSD so long). Anyways, I don't know why this happened, I just decided to boot it and see what happened. It went in a boot loop. I no longer have access to the bootloader screen. After two boots I can press POWER+VOLUME UP to get access to the screen "Android system recovery". Where the only options are:
reboot system now (takes me to the boot loop again)
apply update from sdcard (does nothing really)
aply update from ADB (My pc won't recognize my device anymore, RSD litle doesn't recognize my device either, I tried with mfastboot manually but it says "waiting for device" and does nothing)
wipe data/factory reset (tried this option as well, but nothing)
wipe cache partition (nope).
What can I do? I think this means my phone is soft bricked. How can I fix this? How can I get the bootloader screen back? I can't even turn off my phone, it's stuck in this bootloop. The only thing i can do is to stay in the system recovery screen, but i don't know what to do next. I don't handle Android systems at all, everything I did was based on youtube tutorials, so I'm a little slow to understand the basic concepts. Can someone explain me?
Thank you very much.
Click to expand...
Click to collapse
okay, i had a slim rom running on my fire (5.1.1) and tried to go to cm12 using flashfire. i made sure that wipe was at the top of the list. it got stuck on installing the new rom, so after 30 minutes i restarted tablet. i got stuck in the cm logo bootloop. i do still have access to the amazon stock recovery. tried to do a data wipe/factory reset. still stuck at logo bootloop. i tried to sideload the amazon stock bin file, but it stops after 5 seconds and says "failed to read command: invalid argument" and goes back to the recovery main menu. if you try to do another sideload, it instantly says "timed out waiting for package. installation aborted" before you even press anything. have to restart device to try sideloading again.
at one point i had it almost install cm12 from a zip file through sideload, but at the very end it gave me a signature verification fail. since i can't boot the phone, i can't turn on usb debugging. sometimes it'll show up in the device manager as mtp but never shows up as fire or android device or any of that. it will show up on adb devices command when its in fastboot, but can't do anything with it from there. i've tried all the different ways in the forums here and rootjunky, but nothing seems to work at all. any ideas if i'm doing something wrong or is this just bricked, regardless of stock recovery?
tried a few commands to see if i could fastboot one of the roms or stock images, but they all tell me its missing the android-info.txt
dorkydroid said:
okay, i had a slim rom running on my fire (5.1.1) and tried to go to cm12 using flashfire. i made sure that wipe was at the top of the list. it got stuck on installing the new rom, so after 30 minutes i restarted tablet. i got stuck in the cm logo bootloop. i do still have access to the amazon stock recovery. tried to do a data wipe/factory reset. still stuck at logo bootloop. i tried to sideload the amazon stock bin file, but it stops after 5 seconds and says "failed to read command: invalid argument" and goes back to the recovery main menu. if you try to do another sideload, it instantly says "timed out waiting for package. installation aborted" before you even press anything. have to restart device to try sideloading again.
at one point i had it almost install cm12 from a zip file through sideload, but at the very end it gave me a signature verification fail. since i can't boot the phone, i can't turn on usb debugging. sometimes it'll show up in the device manager as mtp but never shows up as fire or android device or any of that. it will show up on adb devices command when its in fastboot, but can't do anything with it from there. i've tried all the different ways in the forums here and rootjunky, but nothing seems to work at all. any ideas if i'm doing something wrong or is this just bricked, regardless of stock recovery?
tried a few commands to see if i could fastboot one of the roms or stock images, but they all tell me its missing the android-info.txt
Click to expand...
Click to collapse
try stock 5.1.2 firmware
otherwise there is no fix that I know of
Sent from my KFFOWI using XDA Labs
i started trying to get it going, but got the same results. eventually the battery died and it doesn't want to charge anymore, so hopefully i'm still under warranty. thanks for all the help though, been a reader here for a really long time. just sucks to get a hard brick for the first time. used a droid x for four years straight with a locked bootloader and never came across a problem like this
dorkydroid said:
i started trying to get it going, but got the same results. eventually the battery died and it doesn't want to charge anymore, so hopefully i'm still under warranty. thanks for all the help though, been a reader here for a really long time. just sucks to get a hard brick for the first time. used a droid x for four years straight with a locked bootloader and never came across a problem like this
Click to expand...
Click to collapse
I fear I'm in the same boat. Which version of flash fire were you using?
Any further progress?
Sent from my Nexus 7 using XDA-Developers mobile app
Hello, i wanted to root my device so i used the Toolkit.
After i unlocked the bootloader and installed TWRP i wanted to update it to Android 7.0. I decided to use the OTA update and reinstalled the stock recovery and closed the bootloader again. After closing the bootlader the phone won't start anymore. The bootscreen appears for 1sec and the a white light appears. That's all!
I already tried to wipe all data nothing is helping. If i'm in recovery i can't even use "Install from internal storage"
Pls help!
frittler said:
Hello, i wanted to root my device so i used the Toolkit.
After i unlocked the bootloader and installed TWRP i wanted to update it to Android 7.0. I decided to use the OTA update and reinstalled the stock recovery and closed the bootloader again. After closing the bootlader the phone won't start anymore. The bootscreen appears for 1sec and the a white light appears. That's all!
I already tried to wipe all data nothing is helping. If i'm in recovery i can't even use "Install from internal storage"
Pls help!
Click to expand...
Click to collapse
Ok got it running again after i reopend the bootloader but i still want to close it again!
Hi there,
I got a bricked G5S+, which I reported in another thread already.
It was booting, showing the blue Motorola screen but ended up with a lying down android with a red questionmark and saying 'no command'.
That happened after I rebootet the cellphone for a longer time.
I read through a couple of threads and finally decided, I need to flash stock again.
I did not have switched on USB debugging and so on, as the phone was quite new to me and now cannot access android anymore to do so.
Anyway I thought: fine: I will just flash the stock OS again taking care of the software defect.
After having had some issues I flashed Sanders (SANDERS_NPS26.116-26_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml) following that thread here:
https://animetrick.com/flash-stock-rom-moto-g5s-plus-locked-bootloader-2018/
It is quite similar as this thread, which deals with installing a stock OS to a bootloader-locked phone:
https://forum.xda-developers.com/g5-plus/how-to/solution-to-flash-stock-romfactory-t3691396
The thing is I followed all steps but still get the same error:
A lying down android with a red questionmark and saying 'no command'.
Does anyone have an idea what else to try?
I am not aversed to install a custom Rom, such as the official RR v6.0.0, but I have no idea how to do so with a currently bricked phone.
Maybe you guys have a solution for me to unbrick and finally use my phone again.
Thanks a lot!
Regards from Germany
Matt
Hey bro Im not sure if you still need help but, if so can you try to boot into a recovery?
Hi Carlos,
yes I still need help.
I can boot into recovery. And fastboot runs and detects the phone, too.
Any idea what I can do?
Go ahead and download twrp from the Roms sections and also begin the process to unlock the boot loader, we can see if it still can be done without having enabled the setting in the developer sections, and if so we can either then flash the recovery and a custom rom or install stock again.
Sent from my iDevice running Smoothshake v11.3.1
I solved my problem:
It was the SD card. I cannot believe it.
I got myself another G5S Plus and swapped everything:
Same issue.
So I removed the memory card and all good again.
There is no need anymore to install a custom rom (at least not currently )
I am quite sad though not having figured that out earlier, becoz all my data is lost now....
Thanks for your help though!
I have fallen into same issue, i cannot install any custom rom or recovery to it but i can access fastboot & one recovery that has update via adb sideload / sd card but nothing works, shows failed line 2 error / install aborted .
the device just showing oem locked in fastboot & rom install or recovery install fails & says cause too many links
the phone starts & stucks after the motorola logo
anybody with any idea?