Hello, has been a w hile since I was here last time. However, my moto g 5g plus gives me a hard time now. I was using it and at some point the power button stopped working. First it worked only randomly but now it is dead. Before the phone shut down i was able to test the fingerprint sensor and it worked. The last few days i noticed that the connection resets randomly from 5G to 4G to H+ and sometimes i had to restart the phone to have a working connection. I was thinking there is a firmware bug in the stock firmware that continues showing up over time. Last time i did a firmware recovery using the motorola rescue tool but that doesen't work anymore because i cant enter boot loader mode. I have seen that there is the qualcom flash tool out there and im wondering if im able to flash the device without bootloader mode as im not able to start it. And if the problem is software related or not. For the qualcom flash tool i probably need the "firehose" files, where can i find the right one for my device?
I have an update, I think it is a software problem. I have tried unlocking the bootloader and as soon I did everything worked same before. Then I flashed linageos and as as able to use it for one day until (when playing pokemon go it happened again) now the power button responds with delay. But it responds. I have tried to reflash lineage and stock using rescue assistant but nothing helps. Then I tried reboot in edl mode for blankflash but that one also doesent work. It starts the process when it sees the device but it terminates with an error. I have dumped all partitions using the recovery shell. But not sure where to search for as I don't have a dump of the stock partitions. I think there has been some corruption of one of the data in _a slot and now _b slot too. Someone knows what and where to look for? Maybe I need a dump of stock device?
It seems there is something wrong with bootloader. Now I'm not able to flash in fastboot mode. But it works when I flash the gpt.bin after restart in fastboot. I start the download on the PC and then connect the phone and power up in bootloader mode. After that I can flash as normal but after reboot everything same before, no fastboot working. And if I flash stock ROM and lock the bootloader it says no operating system found. I have tried using blankflash from lolinet but that one also doesent work. It recognises the device but then it stops. Is it possible that I have got this sort of thing ota? This is so weird. The power button works but just delayed. Is it on a different chip what is maybe broken? But that would be very strange. I have another phone I treat not as nice as this one and that works like new.
Ah I enter edl by using linage recovery
Deleted all the partitions, now it seems the device doesn't boot the stock ROM if I flash it. What are the essential partitions needed to boot the stock ROM? How can I restore the missing partitions? Thanks
Related
Sorry, I'm relatively new to rooting and I looked through the threads and found similar problems, but none that seem to exactly match mine.
I have a rooted VS985 that I was trying to flash with the AndroidNow HD 6.1 ROM using TWRP and I guess the flash tool crashed. It was stuck on a black screen for an hour or two so I hard reset it and after that, the phone will only flash the LG logo for a second before the screen turns off and the indicator light alternates flashing red and blue. As far as I can tell, the computer does not detect it when it is in this mode (seems similar to the secure boot issue that some people have been having). I cannot enter download mode (the LG logo flashes on and the indicator light flashes blue once and then both turn off) but I can still boot into TWRP Recovery. When I try to boot into download mode, even while the screen is off, my computer detects the phone as QHSUSB_BULK. Also, when in recovery mode, my computer can detect the phone as a G3 and I can access it with adb tools but I don't know where to go from here. I have tried using the LGFlashTool but I can't seem to access the phone because it will not enter download mode and I've tried reflashing AndroidNow HW 6.1. The flash completes and says it is successful, but the phone still will not boot properly.
Luckily, I got the phone a few days ago from Costco, so there is a good chance I can still return it, but I would like to fix it if I can.
Any help would be greatly appreciated.
pyroguy3590 said:
Sorry, I'm relatively new to rooting and I looked through the threads and found similar problems, but none that seem to exactly match mine.
Any help would be greatly appreciated.
Click to expand...
Click to collapse
You said you have adb working.
Did you make a backup of your stock download mode at anypoint of time? (Iaf.img)
I guess it can be pushed back using adb, but am not very sure. Even if not, maybe you can take the stock Iaf.img from someone else and try pushing it via adb using this command:
Code:
dd if=/storage/external_SD/stock-laf.img of=/dev/block/platform/msm_sdcc.1/by-name/laf
Then you can boot into the download mode using the command:
Code:
fastboot boot stock-laf.img
It doesn't look like I have the stock laf.img backed up. I'll try to get it from someone. Thanks, I'll let you know what happens when I get it.
I need this tooi fi h
had a nandroid backup but accidentatlly delted it when i formatted my internal memory now im stuck on liquidsmooth custom rom cant get into download mode so kdz/tot will not work for me... I have twrp installed and that works though. I need to use adb to flash those files or have a stock vs985 that i can flash with twrp... I have vs985 i like the liquid smooth room but the camera and video camera doesnt work as good as it did with stock...
Any help or ideas would bee aprraciedated ive tried everything
just Switch off your mobile.. and put out bettery from it,
And In Pc Download Any Official Tot rom For Your lg g3 vs985 than Open LG Flash Tool 2014
download it from Xdadevelopers any version
Than Put back your bettery In Your Mobile And dont press any button Just put your usb in,your pc and Same time Put Pin in your mobile and press Volume up button And Your Mobile goes in Download Mod Automaticly..
Than Just Flash any Tot Software in It..
Its Working Like Charm,,
Try it It is Working for me Also
I have updated my Nexus 5x to 7.1.1 beta and after a day it powered off and I got the infamous red led during charging. I was not able to turn the phone on even after leaving the charger on for some days. I thought it is bricked and left it alone connected to my computer.
However today, out of nowhere Google logo popped up. It was bootlooping, but I was able to enter bootloader and original recovery. I wanted to flash it from bootloader, but was unable, because it was still oem locked. And I was not able to oem unlock, because I did not do the required part in the Developer Tools menu. I tried to adb sideload OTA in the original recovery, but sideloading stopped after uploading ~48% every time.
So I opted for the "VolumeUp + Power" mode flashing. Phone was recognized and I started flashing the appropriate TOT file. However at 33% on phone and 28% on the PC, progress stopped. And after a minute or so phone turned off. Currently it has no signs of life at all. Have I completely bricked it now? Is there a way to recover from interrupted "VolumeUp + Power" flashing mode?
EDIT: at first I though maybe the battery died during flashing. But interruption was not abrupt. First the progress slowed down to halt. And then after some time phone turned off.
It seems not all is lost. Have a blinking red light again after leaving it connected to computer for a day. Back to square one, but at least it is alive.
Your motherboard is dead.
And it is not your fault, mine also died while using beta 7.1 and I sent it RMA. They replaced for a new one.
But in my case i had unlocked bootloader, I flashed back 7.0 and it gave no results, still bootloop that's why I sent
Thanks for the info.
After leaving my phone with a clamp on a power button throughout the night (so the red light would flash continuously), I got it booting into "VolumeUp + Power" mode and this time I have successfully flashed the same TOT file via LGUp software. It was still bootlooping after flashing. Now I was able to enter into bootloader and recovery and this time sideloading the same previous file actually works. However it still bootloops.
Anyway, I tried to RMA it and after giving my IMEI to the Google rep, they said that they could not find it in their system after checking US and UK store records. Also tried calling LG warranty, but they do not know of my IMEI either. I got this phone from Swappa, so I left wondering where did the original owner of this phone got it from. He claimed that he got it as a present...
BlinK_ said:
Thanks for the info.
After leaving my phone with a clamp on a power button throughout the night (so the red light would flash continuously), I got it booting into "VolumeUp + Power" mode and this time I have successfully flashed the same TOT file via LGUp software. It was still bootlooping after flashing. Now I was able to enter into bootloader and recovery and this time sideloading the same previous file actually works. However it still bootloops.
Click to expand...
Click to collapse
out of curiosity, have you ever tried to flash custom recovery through the bootloader ? If you can, you might also wanna try to make a EFS backup, wipe all partition, then flash custom rom or near-stock rom like this one, just for the sake of testing.
anazhd said:
out of curiosity, have you ever tried to flash custom recovery through the bootloader ? If you can, you might also wanna try to make a EFS backup, wipe all partition, then flash custom rom or near-stock rom like this one, just for the sake of testing.
Click to expand...
Click to collapse
I wanted to flash custom recovery but was unable to do so, because device is still OEM locked. And I am unable to unlock it, because I did not do the confirmation in the Developer Options before device started to bootloop. Is there a way to flash custom recovery without this step in Developer Options?
BlinK_ said:
I wanted to flash custom recovery but was unable to do so, because device is still OEM locked. And I am unable to unlock it, because I did not do the confirmation in the Developer Options before device started to bootloop. Is there a way to flash custom recovery without this step in Developer Options?
Click to expand...
Click to collapse
For now, no way that I can think of. You could try to oem unlock it until it work, just cross your finger I guess?
I have some progress here. Since I was able to sideload various OTA images, I started doing that one by one and seeing if some of them would not bootloop. And after flashing 7.0.0 (NRD91N) from here (https://developers.google.com/android/ota) phone booted successfully and now is working. Will report if I get any problems.
Hey guys,
I would have liked to get the OREO update, because it said every time is up-to-date, and I wasn't patient. because all of these already get it, and the battery life was terrible with, and I have just 30 days to cancel the phone if I'm unsatisfied with it, so it was urgent for me to update and try it.
But I didn't know enough from the newest devices, so that I need unlocked bootloader to flash STOCK ROM or ROOT or for flash RECOVERY
Mine is XT1789-06, I tried to flash first this ROM:
https://androidfilehost.com/?fid=962187416754456314
It didn't tell this is TMO. :/
This changed my baseband to TMO and my boot image to T-mobile, after I didn't have signal and the fingerprint sensor didn't work.
I wanted fix it with RETAIL ROM flashing.
I tried to flash this: https://androidfilehost.com/?w=files&flid=241773
After that my phone didn't boot, says your device is corrupt.
Cause this I tried to flash back the previous version so this: NASH_RETAIL_7.1.1_NPXS26.122-68-4_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
from here https://firmware.center/firmware/Motorola/Moto Z2 Force/Stock/
But no result. The baseband stucked on TMO, the phone is not start up. Fall back to fast boot mode.
After and mean while these things I tried many things.
The Motorola Device Manager isn't working at all.
The Software Upgrade Assistant what the phone want when show boot up failed message isn't working just say processing device information and isn't going further. I don't understand why the phone ask it, because that is for verizon phones.
The RSD lite says the model name is Fastboot nash S and isn't start to flash anything, when I press the start it says the phone failed to switch to fastboot mode, but it's in that.
I tried already flash more different ROMs, but didn't work one of them .
Recovery is unable, the phone isn't rooted, the bootloader is locked, however sometimes it showed ""Your device software cannot be checked for corruption. Please lock the bootloader", but I checked in the powershell and in fastboot mode I looked what phone says, so it's locked.
I was thinking maybe if I unlock it will solve the problem, but I can't turn it on, so the developer options are unavailable and I don't know maybe it won't help, if I can do it somehow.
Now if I want turn on the phone it's going to fastboot mode right away or say your device is corrupt... and after.
I can't try flash it through Qualcomm 9008 because the PC recognise the device for fastboot device.
In the device manager the computer shows Motorola ADB interface.
I try to unbrick for 3 days, please help me.
Thanks a lot in advance.
Same here, if you find anything out DM me
I already contacted with the phone, I will bring back to Repait it.
I couldn't find out nothing, I tried everything what was possible.
i think i found a solution i just dont know how it works exactly, something to do with a batch file and a full flash of the phone
https://forum.xda-developers.com/z2-force/how-to/how-to-return-to-stock-sprint-t3694783 im going to try this and let you know
Hey all, I got my XA2 a couple months ago and have been really enjoying it. Right out the box, I flashed LineageOS and the phone's been operating mostly fine for a while, with the exception of OTA updates. For a while, attempting to install a zip to slot B was causing problems with the modem, and after a certain point it was hanging on the Lineage boot screen.
I wanted seamless updates to work, so I tried something I thought would work. Using the unofficial FlashTool, I flashed the official Sony 12.9 ROM (July patch, I think?) hoping to OTA to the current 13.38 ROM and "reset" the B partitions to their stock state. However, the built-in Software Update kept saying I was up-to-date, and Xperia Companion on my laptop said it couldn't check for updates. So, I tried another route of using the official Sony Flash Tool "Emma." I saw two updates, so I flashed the older one (4.01 I think) and it worked fine. Then I used Fastboot to switch active partitions to the B slot and flashed the newer version (5.29 I think). I noticed the active slot had been changed back to A, so I set it to B and Fastboot rebooted. This is where I experienced problems.
Upon trying to power up the device, I see the LED flash green briefly, and nothing happens on screen. Upon plugging the device in with either volume key pressed, attempting to recover the device, I get the same thing with the flashing LED, except it does this repeatedly, and thus am unable to boot into Fastboot or Flash Mode. Am I screwed? It's not too terrible as I have other devices I can use, although now I essentially have a $300 paperweight...
If you are linux try to check dmesg when plugging into pc, in windows check device manager.
However, due to the fact its doing something at green led and abl/xbl is what sets led red I suspect there is an issue booting off emmc or something.
You could also check the serial log if you want to be sure of the isssue.
EDIT: try plugging into USB with the power key pressed
See if that does anything
If not, try plugging in with volume up pressed
Did you manage to recover your phone again? It seems mine went broken now the same way.
I had flashed some Oreo based firmware (50.1.A.13.123) probably to Slot A to be able to OEM unlock it and remove the branding and bring it back to Oreo from Pie. Then unlocked bootloader and followed the LOS flashing guide and flashed LOS to Slot a. After rebooting TWRP it hang in a casual bootloop. Maybe there was a Pie based Firmware flashed to Slot B. I've tried to reflash original Oreo firmware to Slot A again and now I can't manage to get into flashmode or fastboot mode. Even forced shotdown or reboot with holding Power+VolUp and 2 minutes way won't work it seems. Linux cosole doesn't report anything using dmesg here.
Any idea? What do you mean how to check serial console - the phone one or pc?
I recently found a moto g5 in one of my fellow "old tech" drawers and decided to turn it on, it was on the
1. May 2018
Security patch on nougat, I decided to use the inbuilt system updater to go to Oreo, and now....it crashes during flashing process after about 25-30% completion,
Now im guessing boot or System is not properly installed due to the zip file having aborted mid-flash
Recovery doesn't properly boot as that is used to install the update and thus imidiately goes to doing that
Also, it hang up during installation on random times, it basically has a record of 2mins of not crashing whilst still being stuck on 30%
I got it to "boot" when trying factory mode, yeah it crashed mid boot animation...not a help
Any suggestions? EDL mode maybe?
Can you not flash firmware via fastboot
In theory as long as firmware is signed you don't need an unlocked bootloader to flash firmware
Firmware can be downloaded from https://mirrors.lolinet.com/firmware/moto/cedric/official/
You can also try the lenovo moto smart assistant to flash the firmware
https://forum.xda-developers.com/g5/how-to/guide-how-download-official-fastboot-t3916778
If not you will most likely need a motherboard replacement or jtag firmware flash at a repair shop
TheFixItMan said:
Can you not flash firmware via fastboot
In theory as long as firmware is signed you don't need an unlocked bootloader to flash firmware
Firmware can be downloaded from https://mirrors.lolinet.com/firmware/moto/cedric/official/
You can also try the lenovo moto smart assistant to flash the firmware
https://forum.xda-developers.com/g5/how-to/guide-how-download-official-fastboot-t3916778
If not you will most likely need a motherboard replacement or jtag firmware flash at a repair shop
Click to expand...
Click to collapse
SOMEHOW it just decided to boot, I have never seen such behaviour, even on my g5s which I had for a while, (and am currently daily driving to school if it wasn't closed....NEVER
Maybe I'll unlock it and try somehow recreating it? Well it's in physically rough shape but all components inside are fine...so that can't be the reason....?
My g5 got stuck in a bootloop without an update, no root or anything modded. Is there any way to recover the data if its stuck like this?
anonymous724 said:
My g5 got stuck in a bootloop without an update, no root or anything modded. Is there any way to recover the data if its stuck like this?
Click to expand...
Click to collapse
Flash the stock rom and boot the device. But this will format the device.
To save data, remove the command fastboot erase userdata
Fastboot erase customisation.
Apps may be gone, but files In internal storage will be safe, like download,photos, music.
riyan65 said:
Flash the stock rom and boot the device. But this will format the device.
To save data, remove the command fastboot erase userdata
Fastboot erase customisation.
Apps may be gone, but files In internal storage will be safe, like download,photos, music.
Click to expand...
Click to collapse
no luck on this front, gets to the passcode screen, write in passcode then motorola logo shows and screen keeps on turning off and on.
Thanks for the effort though, much appreciated
Mine is similar to yours. Initially was on permanent loop of the following:
1. Boot to moto g splash screen... Repeat
2. Boot to lock screen then usually a few loops of 1. (after entering the patter or left Idle)
The phone initially didnt have any developer options enabled.
I wiped cache using recovery mode. Restarted and pretty much the same thing except that it would on rare occasions actually fully boot up usually only last a few minutes before cycling between steps 1 and 2 above.
I used those rare boot ups to backup all files and enable any USB debugging /oem unlock (incase I need to use a solution dependent on these being enabled.)
Factory resetted it and its still the same with the random successful boot amongst the numerous failed ones.
I managed to hook it up to Lenovo's Lmsa and flash the latest ROM. Now I get a lot more successful boots but still loops every so often. The downside is that I can no longer do any functions that make use of the audio/ mic/ video (can take pictures). If I do then it will crash and loop.
The hardware test on the LMSA passed for every component before flashing to the latest version. Post update it predictably fails on the audio/ mic components.
I guess I'll have to go back to the old version to see I get the audio back.