---Update---
Nevermind, I see this has already been discussed in this thread:
https://forum.xda-developers.com/moto-x4/help/to-force-8-1-ota-project-fi-x4-t3786726
This is a common problem with no solution ATM.
_________
The update screen comes up (see pic1), I click "download and install", and after it downloads the 945MB update file, I get this error screen (see pic2).
After I click "OK", the update screen reappears a few minutes later, and the cycle repeats.
Would getting a logcat help me diagnose this problem?
I've got the XT1900-1 A1 model, and the bootloader is unlocked, but nothing else (no root, no custom kernel or recovery).
(screenshots)
The only solution i've found to get the OTA to work (verified by others as well as my self)
Reboot after each fail and try again - if you watch the screen the % complete will increase each time before fail, eventually ending in a successful upgrade! (At which time your phone is now more secure than ever - USB file transfer won't work with a lock screen pin/pattern/fingerprint.
same problem here
Related
Hi Everyone,
I have a (Milestone) problem and would love input from anyone who can help.
This is an interesting situation, so feel free to skip the quote section if you'd like to avoid the, albeit quite summarized, background information.
I purchased this device from kijiji. Apparently it's an internal device, with GP hardware and a 90.70 bootloader.
My first mistake was misreading some instructions. On this device you can enter fastboot mode by pressing VolumeDown. I mistook this for bootloader (forgive me, they sound similar), and attempted to flash .sbfs from here. Of course this doesn't work.
What i did find was that i could flash .sbfs fine if i started to run RSD while the device was running (because it restarts itself properly into bootloader). That is, i got Vulnerable recovery to run okay. And then rooted/nandroid backups.
But later i got adventurous and tried to update the annoying outdated bootloader (because of course, i thought you couldn't flash sbfs to it directly). As urged by the community, it's backed up incase anyone needs it.
So i started RSD while the device was running, to flash 90.78. Almost instantaneously the device restarts, but instead of going into bootloader it tries to boot. And fails. Which brings me to:
Click to expand...
Click to collapse
The device gets stuck on the Motorola M splash screen. Every once in a while (~3 minutes?) it goes blank and comes back.
A summary of the state:
Recovery mode will not boot. I've tried X and Camera Button
Bootloader boots. It reads 90.78.
.SBFs can be flashed. It seems like everything is working okay.
Fastboot mode can boot. My PC can detect the device but seems unable to write/read from it
adb logcat forever sits on -waiting for device-
I've tried flashing a number of .sbfs. I've redone the bootloader a few times, tried a number of roms. But now i'm out of ideas.
I'm open to suggestions and really hoping someone can help me figure out a way to restore this. Thanks !
I'll try just one bump, i'm getting desperate.
Nevermind, this got figured out. Consider this closed please .
Hi, I did just got into a similar situation:
- Recovery mode will not boot. "I've tried X and Camera Button" (Same like you)
- Bootloader boots. It reads 90.78. (I tried several BL 90.73, 90.74 and 90.78)
- Several .SBFs can be flashed. It seems like everything is working okay.
Did you get any solution or just discard that phone?
I upgraded my Note 4 OTA yesterday and it appears to be working fine. But there is one thing I would like to find out if others have experienced. Since the update, when I boot into recovery mode I get the following message; "installing system update." This stays on the screen for about 15 seconds and then disappears and is replaced by "No command". Then I am presented with the usual recovery mode menu. Does anyone else get these results when booting into recovery mode since doing the update? Does anyone know how to make it stop this behavior? It doesn't appear to be causing any practical problems as I can still access everything you normally could in recovery mode, I just have to wait a little longer to get in. Any info is appreciated. Phone is not rooted.
--Burbank Jim
Same thing happening to me. I'm sure it's nothing.
While fiddling around in some game, the device goes out due to empty battery (without warning beforehand).
Battery should have lasted several more hours, but the battery status is at 0% so I have to wait a few
minutes before being able to restart. On restart, device boots up normally. (weird: my background got replaced by
stock image). After entering PIN, a few dozen error messages appear (something stopped working), after
clicking 'ok' on the last message, screen goes black (not out).
Next restart, same same, thoug now after maybe a dozend error messages (which I am clicking happily away)
somewhere I spot the message "Android updating"..... black screen.
Boot to recovery:
AP Fastboot Flash Mode (S)
48.82(*) (sha-e004609, 2014-12-19 14:35:02)
CPU: bla
eMMC: more bla
DRAM: blabla
Battery OK
Device is UNLOCKED. Status Code: 3
(BTW: What is status code 3?)
Selecting any option (except 'Barcode', which works nicely) the Moto G boots up 'normally'. No recovery screen, nothing.
Straight to "Warning, Bootloader unlocked", same same, .... black screen.
I tried exposing front camera to bright light because some people seem to have problems with
automated brightness control. That's not it.
The history of that device:
Stock rom
-> some things I don't remember, prob some KitKat 4.4.4 custom roms
-> OTA update (yay, soft brick \o/ )
-> stock 5.0.2 according to tutorial of same hero from around here
(of which for the most part, ofc, I don't know what the hell I am doing by typing all that)
Now i tried flashing new Marshmellow 6.0 roms according to instructions by heroes
http://forum.xda-developers.com/moto-g-2014/general/official-stock-firmware-t3018682
http://forum.xda-developers.com/moto-g-2014/general/official-firmware-titan-xt1068-t3312933
which cmd and the console in phone bootloader acknowledge one by one, no errors.
Upon reboot, same same, .... black screen.
Then I tried to get rid of that (stock?) bootloader by installing TWRP
mfastboot.exe flash recovery twrp-3.0.2.1-titan.img
but the next time I enter recovery, I'm back to that stock bootloader.
It seems the device is writing all instructions into the Nether.
Things I don't want to read:
- hard bricked
- Motorolla doesn't care about unlocked phones
- you're f*cked
Everything else will be greatly appreciated Any ideas what to try next?
Hello -
I've been a long time reader/lurker and have been able to resolve most issues reading and searching.
I have a G925A S6 Edge variant. It came to me with a blue screen stating "System Software Not Authorized by AT&T". I have downloaded various ODIN images and applied and I get the same results no matter what.
The phone requires resetting a few times to boot. When it finally boots, I receive several app crash errors. I have tried to install TWRP and it fails and gives a secure error in download mode.
I know the phone isnt unlocked and I cannot fine the OEM unlock setting anywhere in settings which is probably causing the issue.
Anyone have an idea?
Thanks
mj4g2 said:
Hello -
I've been a long time reader/lurker and have been able to resolve most issues reading and searching.
I have a G925A S6 Edge variant. It came to me with a blue screen stating "System Software Not Authorized by AT&T". I have downloaded various ODIN images and applied and I get the same results no matter what.
The phone requires resetting a few times to boot. When it finally boots, I receive several app crash errors. I have tried to install TWRP and it fails and gives a secure error in download mode.
I know the phone isnt unlocked and I cannot fine the OEM unlock setting anywhere in settings which is probably causing the issue.
Anyone have an idea?
Thanks
Click to expand...
Click to collapse
You not reading enough. Phone have lock bootloader and you can't unlock at all as of now. This mean you can't use any other recovery then stock.
On Edge of Galaxy
Thanks.
I was asking about TWRP only because I cant get the phone to behave properly. No matter what version I use, I get constant force closes on tons of apps...
Ive tried all the below versions:
G925AUCS5DPJ1
G925AUCS6DQC1
G925AUCS6EQE1
G925AUCU1AOCE
G925AUCU6EQCF
Im currently on the Nougat version G925AUCS6EQE1.
After I flashed each version in ODIN, I had to force reboot a few times to get past dm-verify and "No command" errors. Eventually, I got it to boot. From then on out it boots properly.
One other oddity, is under "Service", it says KT twophone service" - in settings.
I have no idea what the previous owner did to get it locked up on the "System software not authorized" message, but the phone would do nothing until I ran ODIN.
mj4g2 said:
Thanks.
I was asking about TWRP only because I cant get the phone to behave properly. No matter what version I use, I get constant force closes on tons of apps...
Ive tried all the below versions:
G925AUCS5DPJ1
G925AUCS6DQC1
G925AUCS6EQE1
G925AUCU1AOCE
G925AUCU6EQCF
Im currently on the Nougat version G925AUCS6EQE1.
After I flashed each version in ODIN, I had to force reboot a few times to get past dm-verify and "No command" errors. Eventually, I got it to boot. From then on out it boots properly.
One other oddity, is under "Service", it says KT twophone service" - in settings.
I have no idea what the previous owner did to get it locked up on the "System software not authorized" message, but the phone would do nothing until I ran ODIN.
Click to expand...
Click to collapse
No command it is normal. Just wait for phone to start. Then go to recovery and do factory reset.
BTW. Are you sure it is G925A model, just asking to be sure.
On Edge of Galaxy
Yes - SM-G925A printed on back and shows on download mode screen.
mj4g2 said:
Yes - SM-G925A printed on back and shows on download mode screen.
Click to expand...
Click to collapse
Great. Try ODIN again and flash E1. This time when you see "No command " just wait and let boot all the way. Then restart in recovery and factory reset. Reboot and let us know what you got.
On Edge of Galaxy
Hey there folks,
Today morning I have looked into the Magisk app, I think it was in version 24.3, and it said it has an update.
I have pressed on the update, it opened the shell, and patched the relevant ROM, nothing unusual.
Then it rebooted.
Here comes the hassle.
The stock oneplus boot image came in (my phone has a boot animation and an 1+ and android splashscreen before) and I was like waiting.
After 30 secs I thought that it is taking an unusually long time, but maybe its the new module.
A few minutes later I considered that there is something wrong with it, and tried to hardware reboot it, maybe it would solve my problem.
Still nothing
Current situation : My guess is that it got bricked, it is not in bootloop, but probably my patch has failed as it does not boot in
nor adb nor fastboot (while the device is in fastboot mode) detects it from a Win10 powershell/cmd, from which I have had no problem connecting before
Any idea how can I fix it and recover the data from it at least?