I Have noticed quite a few - as in 3+ Moto G 2nd gens's are having problems with corrupted partitions, i.e OTA fails to install half way through or cant install via Mfastboot and / or Custom recoveries.
Due to the corrupted partition (or rather partition table) IT wont allow flashing / erasing or clearing / factory resets
There's no proven cure but MAYBE locking and then unlocking boot loader again may fix this as it WIPES data.
AS a Precaution I suggest anybody that who is thinking of upgrading / downgrading or restoring does a FULL FACTORY reset AFTER they have backed up phone.
Yes its extra work but with memory cards being cheap and playstore / google accounts backing up your apps, contacts etc, it's simply lazy and Dangerous Not to backup....
so...
my moto gave up during OTA update to 5.0.2 -> flash and rebbot OK, but "optimizing applications", took an eternity, then (in the middle of the job) the screen went black.
after a cold reboot it finished and everythings allright now..
My Moto G has this problem too!
The userdata and cache partitions seem to be corrputed as they give the error: blkdiscard on partition /dev/block/platform/msm_sdcc.1/by-name/userdata ( /cache )failed
This happens in stock recovery.
Help
I have this Problem too.I was in lexodus Rom then my phone shutdown,then i Turned it on and all apps fc's .I tryed to flash it With twrp but it cames an error execute update binary .I cant restore or wipe anything .And when i try to restore it with you stock Rom installer in succes but it still the same rom with the same Problem .I need help Please PS sorry for my Bad english
When the partition table is completely hosed, you can't lock the bootloader, only unlock. And unlocking in this state does not wipe it.
There is no recovering from this state, and honestly you get what you pay for with these phones.
When the battery drops below 5%, there is a high probability of the eMMC being ****ed in this way (I have had it happen on 4 phones now!). Undoubtedly a major design flaw.
I messed up partitions on my oneplus one. Most specifically the data one trying out f2fs. I was able to recover the partition by formatting it with a combination of philz cwm, twrp, and parted. I don't remember what I did as I was desperate to fix my oneplus. You can look into learning how "parted" works and you may be able to reformart the partition through adb shell.
I know this is a bit of hogwash help, but I was able to recover my /data partition.
Edit: also if I understand correctly, just because your partition table gets effed up, doesn't mean your recovery doesn't contain the proper information to put it back properly. I was able to boot my phone into temporary philz and twrp by command line using fastboot. I'll see of I can find some info.
Sent from my Moto G 2014 using XDA Free mobile app
Here is the command to boot a recovery img from fastboot
fastboot boot customrecovery.img
from there, you can try to use philz to format your partitions, or TWRP. Which ever recovery works for you. Then, presumably if this works, you should be able to restore your device to factory or install a custom recovery or rom.
In twrp i can Format all expect infernal storage .when i Format data it says OK but the data is still there and When i try to boot philz cames a bootloop
rukusx7 said:
Here is the command to boot a recovery img from fastboot
fastboot boot customrecovery.img
from there, you can try to use philz to format your partitions, or TWRP. Which ever recovery works for you. Then, presumably if this works, you should be able to restore your device to factory or install a custom recovery or rom.
Click to expand...
Click to collapse
You can't boot a recovery with that command when the moto g is in this state sadly.
Code:
C:\android\platform-tools>fastboot boot twrp.img
downloading 'boot.img'...
OKAY [ 5.280s]
booting...
FAILED (remote failure)
finished. total time: 15.319s
Literally the only thing you can do is unlock the bootloader (and not lock it again), and sometimes access the stock recovery (where nothing works).
The only hope of recovery is the MBM-CI (qualcomm blank flash programmer) files, which motorola keep to themselves. For this reason, buying a moto g is risky.
Also no Chance to recover our moto g ?:crying:
Darkimmortal said:
You can't boot a recovery with that command when the moto g is in this state sadly.
Code:
C:\android\platform-tools>fastboot boot twrp.img
downloading 'boot.img'...
OKAY [ 5.280s]
booting...
FAILED (remote failure)
finished. total time: 15.319s
Literally the only thing you can do is unlock the bootloader (and not lock it again), and sometimes access the stock recovery (where nothing works).
The only hope of recovery is the MBM-CI (qualcomm blank flash programmer) files, which motorola keep to themselves. For this reason, buying a moto g is risky.
Click to expand...
Click to collapse
I'm on the same boat, but actually when I try to boot, it goes in an endless bootloop of a Motorola logo (not the animation particularly). I've tried only with TWRP. I'll try later with CWM.
Flashing goes well but.... crap, I hate this
Darkimmortal said:
You can't boot a recovery with that command when the moto g is in this state sadly.
Code:
C:\android\platform-tools>fastboot boot twrp.img
downloading 'boot.img'...
OKAY [ 5.280s]
booting...
FAILED (remote failure)
finished. total time: 15.319s
Literally the only thing you can do is unlock the bootloader (and not lock it again), and sometimes access the stock recovery (where nothing works).
The only hope of recovery is the MBM-CI (qualcomm blank flash programmer) files, which motorola keep to themselves. For this reason, buying a moto g is risky.
Click to expand...
Click to collapse
So if i unlock bootloader and root phone will i be at risk?? Or i am only at risk if i mess with partitions or try to lock bootloader again?
How come "qualcomm blank flash programmer" will affect on eMMC?
lol'd..
Nor the unlocking\locking will work in this state.
Darksl1der said:
How come "qualcomm blank flash programmer" will affect on eMMC?
lol'd..
Nor the unlocking\locking will work in this state.
Click to expand...
Click to collapse
Sorry to ask but, do you even know what a emmc flash programmer is?
jhonnyx said:
Sorry to ask but, do you even know what a emmc flash programmer is?
Click to expand...
Click to collapse
Am enthusiast of device-modding, IT-engineer and a big fan of Motorola phones since 2005.
Of course I understand.
I mean this tool could help somehow by taking part of restoring, but supposed to fix issues over WRITABLE memory.
In case of RAW partitions - should delete partition table and recreate then, since plain format refused.
Anyway, my point was about this tool - it's not classic HardBrick state, Bootloader is working thou. We will use flasher if we'll replace eMMC-chip, for example
Related
Hi I have the XT1570, running unlocked and with rooted but stock 5.1.1. I have run in to some issues with the recovery part.
Firstly I wanted to go back to the recovery and flash a stock recovery so I could get the OTA for MM, i did that using fastboot, and the flash worked fine according to fastboot, however once i rebooted into recovery it would not load, got an error message, I forget now something about dumping back to bootloader.
Anyway i fixed it got TWRP back on again, then tried a different stock recovery, same thing same error, so i thought I would easily get back to TWRP by the same method, flash again. I was wrong, now fastboot told me , target reported max download size of 536870912 bytes
error: cannot load 'twrp-2.8.7.1-clark': No error
Remember this is the exact same TWRP image i have just flashed not 5 mins before.
So i thought ok then, maybe an old image is in there taking up space or something.
C:\Users\David\Desktop\Mfastboot\Mfastboot>fastboot erase recovery
erasing 'recovery'...
(bootloader) Erase allowed in unlocked state
OKAY [ 0.017s]
finished. total time: 0.019s
Now I get the message:
Invalid boot image header.
Error:failed to load kernel
Boot up failed.
I presume I have deleted everything in the recovery partition, and so messed it up good, but I dont know how to fix it at this point.
I also erased the cache along the way (via fastboot) as I tried to get the OTA update to work anyway just to see what would happen, so I had to erase the cache to cancel updates
I must reiterate, I can boot into Android and use my phone no issues, at all, just I have no recovery at all and this means updates arent going to work, also i cant seem to find a reliable source for a stock recovery.
Some step by step help would be appreciated, as I am not an expert by any means on this.
Thank you.
Also my device was bought in China as that is where I am, it does indeed have the code name XT1570, dual sim, I would assume it is basically the same as the XT1572 asian. I do also have an original backup of the phone after unlocking bootloader, before root, which was my next port of call after changing the recovery back to stock.
fixed it i was just being foolish, someone delete this thread it is of no use.
Can you explain how you fixed it? I too have deleted the recovery in an attempt to flash twrp, but now neither twrp nor the stock recovery are there?
Tapatalk'd from my Twisted, Racing Nexus 5
So i just saw the new Oxygen OS 3.1.0 is out in OTA form. Me being rooted i tried flashing it through twrp, which i had installed before. (i should also note that i had Xposed installed too, on Oxygen OS 3.0.2) now i think i might have gotten my zip file wrong and installed a previous version. The boot animation is the square, triangle and circle one. It just goes through my apps and tries to update them for eternity. When i try putting the device into recovery (power+vol down) it just freezes on the oneplus logo. I later discovered that i can use fastboot when in that mode. I tired flashing twrp but i couldnt boot into it. fastboot boot recovery.img didnt work either, giving me this:
downloading 'boot.img'...
OKAY [ 0.746s]
booting...
FAILED (remote: dtb not found)
finished. total time: 1.011s
Now i have no idea what to do. I'm sure I've made SOME kind of mistake along the way, but i cant find a way to fix this. I have a nandriod backup of just before flashing if that might help.
fastboot reboot-bootloader puts me in fastboot mode but it doesnt change anything.
also, ADB naturally wont detect the phone whatsoever.
Ill be very glad for any help! Thanks!
Are the drivers accurate? Does your PC recognize your device as it should in Device Manager? That's usually what I check first when I have fastboot errors. I think the only way to fix this is through fastboot... so I would focus on trying to get that to work first.
SynderBlack said:
So i just saw the new Oxygen OS 3.1.0 is out in OTA form. Me being rooted i tried flashing it through twrp, which i had installed before. (i should also note that i had Xposed installed too, on Oxygen OS 3.0.2) now i think i might have gotten my zip file wrong and installed a previous version. The boot animation is the square, triangle and circle one. It just goes through my apps and tries to update them for eternity. When i try putting the device into recovery (power+vol down) it just freezes on the oneplus logo. I later discovered that i can use fastboot when in that mode. I tired flashing twrp but i couldnt boot into it. fastboot boot recovery.img didnt work either, giving me this:
downloading 'boot.img'...
OKAY [ 0.746s]
booting...
FAILED (remote: dtb not found)
finished. total time: 1.011s
Now i have no idea what to do. I'm sure I've made SOME kind of mistake along the way, but i cant find a way to fix this. I have a nandriod backup of just before flashing if that might help.
fastboot reboot-bootloader puts me in fastboot mode but it doesnt change anything.
also, ADB naturally wont detect the phone whatsoever.
Ill be very glad for any help! Thanks!
Click to expand...
Click to collapse
**** man. I'm in the same boat as of a few hours ago. I was having a ProxyController wakelock and the few Google results I saw told me I should reflash the modem. I accidentally flashed the old modem (OOS2, I believe). I can't boot into my rom OR TWRP. BUT fastboot does work. I also get the "remote: dtb not found" error when trying to boot from the recovery image.
As long as we have fastboot, we can always go back to OOS 3 using the various unbrick methods. I'm trying to avoid having to go through that whole mess of re-rooting/unlock the bootloader etc etc. I'll post on here if I'm successful.
Update: I NEED a functional phone so I just went and erased everything. Sorry I couldn't be of much help to you man. What I did:
I went here and downloaded the fastboot version of OOS3 and converted the bat scripts into bash scripts (I only have Linux computers near me right now...; the commands in that bat script are exactly the same as they would be in bash, I just had to rename the ".bat" to ".sh" and make it executable). I'm back in OOS 3 now, unfortunately. There IS a way mentioned on the page below that talks about how you can prevent userdata from being formatted, but I didn't really care too much. Hope that helps.
http://forum.xda-developers.com/oneplus-2/general/rom-mirrors-official-oxygen-os-roms-ota-t3209863
I have tried everything to get this phone to boot up. I was downloading the Oreo B2 via OTA, not sideloading. While the update was installing, I went about my business. I walked away for a few minutes and came back to a phone that just sat at the boot screen. I let it sit for about an hour, thinking that was some how normal. After an hour, I hard powered down and it came back to the same screen. I have rebooted at least 50 times now with no luck.
I can boot into fastboot, but not recovery. If I try to go into recovery, it goes to the boot screen and sits there. I have tried to switch partitions, it is stuck on A, without luck. The bootloader is locked and I can not remote unlock it via fastboot. Nor can I manually change the boot partition to B.
I have an open ticket with Essential, but they have been blowing me off and basically told me I'm out of luck since I was in their Beta program. They told me to go to XDA. A$$wipes! Any help you can offer is greatly appreciated since I'm stuck with a bricked phone and having to use an old iPhone since I cannot be without a phone.
Exact problem happened to me last week and a very helpful XDA member saved me.
Just hook up phone to pc by adb, type in 'fastboot devices' (while in fastboot mode) and install 7.1.1 os again. You'll lose everything but at least you won't be softbricked anymore.
Edit: sorry, just read you do not have unlock bootloader so this probably won't work.
Have you tried wiping data in while in fastboot? That might get it to boot.
Sent from my PH-1 using Tapatalk
You don't need an unlocked bootloader to sideload the install (following the BETA instructions: https://www.essential.com/developer/beta-builds
Since you can use fastboot, it looks like you have working ADB environment, so you should be able to follow those instructions. The STOCK recovery works very differently than TWRP, so make sure you follow those intructions, particularly the "Apply update from ADB" part. It took me a while to understand this, especially because the type on the screen is so tiny, I couldn't tell any words were changing.
I'm having the same issue (stuck on the boot logo "powered by android" screen) and I can get into fastboot mode, however if I try to go into recovery mode it just gets stuck on the boot screen again.
When in fastboot mode, the device state is "locked" is there any ways to get this fixed?
You could try: (you will lose all your data)
fastboot -w
fastboot reboot
ilpolpi65 said:
You could try: (you will lose all your data)
fastboot -w
fastboot reboot
Click to expand...
Click to collapse
Here's what I've got
Code:
fastboot -w
wiping userdata...
Erase successful, but not automatically formatting.
Can't determine partition type.
FAILED (remote: unknown command)
erasing 'userdata'...
FAILED (remote: Erase is not allowed in Lock State)
finished. total time: 0.002s
It's still having the same issue..
update im still stuckk
Have you tried booting to bootloader and mounting /system?
This is obviously corruption of the firmware, and has nothing to do with wiping userdata. Download the full firmware and flash all of it through fastboot.
I also have my phone stuck The bot is closed and I can not do anything
V0idst4r said:
This is obviously corruption of the firmware, and has nothing to do with wiping userdata. Download the full firmware and flash all of it through fastboot.
Click to expand...
Click to collapse
I also have my phone stuck
The bot is closed and I can not do anything
Same here
It can't get passed the logo and I can't get any command in adb to go in fastboot. And recovery is a no go. Yay
Ph-1 stuck at boot, bootloader locked
kuyzz said:
update im still stuckk
Click to expand...
Click to collapse
We're able to fix the issue???
Followed a tutorial on how to install lineage-14.1-20180817-UNOFFICIAL-cedric, but somehow missed a step or messed up.
I unlocked the bootloader, not exactly but in general: flashed the boot.img and rebooted, phone started and was able to use android.
But some strange problems occurred, like somehow my PIN was not recognized and device failed to factory reset.
Locked the bootloader again because of the warning (here's my mistake I guess) and now am unable to flash or revert to stock.
I am able to boot into android, did enable USB debug and bootloader unlock.
But everytime I boot I get the warning a different kernel has been installed (instead of wrong key before) and permission is always denied remotely.
C:\ad>fastboot flash logo logo.bin
Sending 'logo' (2186 KB) OKAY [ 0.068s]
Writing 'logo' (bootloader) flash permission denied
FAILED (remote: '')
Finished. Total time: 0.077s
This happens with everything, permission denied.
If I try to unlock it again via fastboot commandline (Windows) I get:
"(bootloader) invalid boot state"
Starting the phone in fastboot, the status is "flashing_locked".
What can I do now?
I am a noob, therefor the tutorial...
Thanks
thugscorpion said:
Followed a tutorial on how to install lineage-14.1-20180817-UNOFFICIAL-cedric, but somehow missed a step or messed up.
I unlocked the bootloader, not exactly but in general: flashed the boot.img and rebooted, phone started and was able to use android.
But some strange problems occurred, like somehow my PIN was not recognized and device failed to factory reset.
Locked the bootloader again because of the warning (here's my mistake I guess) and now am unable to flash or revert to stock.
I am able to boot into android, did enable USB debug and bootloader unlock.
But everytime I boot I get the warning a different kernel has been installed (instead of wrong key before) and permission is always denied remotely.
C:\ad>fastboot flash logo logo.bin
Sending 'logo' (2186 KB) OKAY [ 0.068s]
Writing 'logo' (bootloader) flash permission denied
FAILED (remote: '')
Finished. Total time: 0.077s
This happens with everything, permission denied.
If I try to unlock it again via fastboot commandline (Windows) I get:
"(bootloader) invalid boot state"
Starting the phone in fastboot, the status is "flashing_locked".
What can I do now?
I am a noob, therefor the tutorial...
Thanks
Click to expand...
Click to collapse
First, this thread is for g5 plus not for g5, so post in that thread.
Solution:- which firmware you are trying is it for g5 or g5+, if you flash wrong firmware then this happen, try downloading your firmware and then flash it.now you are on stock. If you don't know how to Flash, you can prefer XDA threads or use Lenovo Moto smart assistant app (pc) that will flash the firmware for you.
If you want to go on custom ROM then, first go to stock rom as it will restore your boot.img and custom ROM can work. If you directly want to go to custom rom (skiping above procedure) then flash boot.img from ADB or twrp and install custom ROM.
Here is the thread to Flash stock ROM:-
https://forum.xda-developers.com/g5...-flash-stock-romfactory-t3691396/post74221633
Link for Lenovo Moto smart assistant app:-
https://support.lenovo.com/in/en/downloads/ds101291
And if you are using XDA threads it has old firmware which can brick you Device you can get your firmware from here and chose which firmware channel you belong:-
https://mirrors.lolinet.com/firmware/moto/potter/official/
At last to not take risk remove bootloader and gpt commands from ADB.
It is a G5 Plus and I get permission denied with adb or fastboot.
In android I van go go developers option and OEM unlock is ON, if I go fastboot, flashing is locked.
thugscorpion said:
It is a G5 Plus
Click to expand...
Click to collapse
Well LOS14....-cedric is the G5 variant. You didn't flash the wrong firmware did you?
Apperently I did...
Is there a way to fix it?
the Lenovo recovery tool mentioned above doesn't do anything with the "flash" option.
Put the phone in fastboot mode and it is not recognized by the Lenovo application.
Can still manual send fastboot and adb via the Windows command line but still "locked" and "pemrission denied".
the command fastboot flashing unlock did the trick for now.
But, I want to revert to stock, what is the correct way?
Can someone point me to a good how to or tutorial with recent files?
EDIT: I see LineageOS officially is not supporting the G5 plus, but there is a unofficial version in the G5 plus forums.
I'm still thinking of customizing because of all the bloatware and sluggish performance.
reïnstalled TWRP, put Pixel Experience on an SD card, booted TWRP recovery, did several attempts to clean all data / cache etc. but got several errors, retried, rebooted, chose all options and installed Pixel.
First try phone did not boot, froze on Pixel boot, again wiped everything, again installed Pixel and now it boots.
good lesson.
Phone is not entirely recognized the correct way, google security speaks of a Moto X (4) and the phone itself mentions the exact model number instead of Moto G5 Plus.
thugscorpion said:
reïnstalled TWRP, put Pixel Experience on an SD card, booted TWRP recovery, did several attempts to clean all data / cache etc. but got several errors, retried, rebooted, chose all options and installed Pixel.
First try phone did not boot, froze on Pixel boot, again wiped everything, again installed Pixel and now it boots.
good lesson.
Phone is not entirely recognized the correct way, google security speaks of a Moto X (4) and the phone itself mentions the exact model number instead of Moto G5 Plus.
Click to expand...
Click to collapse
Yeah security does show as Moto X4. That's normal.
One final question: On reboot I always end up in the fastboot menu without holding power and volume down, I also always get the unlock warning.
Is this a sign the bootloader is still not okay?
And is there an easy way to fix it?
Dear all, Pls help me )':
Similar to other post, my situation goes like this
1)my magisk manager was hidden (Renamed)
2)tried updated magisk apk no issue, just the main magisk updates which i updated within app (selected recommended) it return errors.
3)did a restart then unable to boot to normal android environment.
4)stuck in boot screen whereas shown 'your device is corrupt.....'
5)firstly was able to boot into TWRP recovery mode
6)my mistake was flash magisk 21.4.zip on top
7)now stuck in fastboot bootloop which shows "BOOTLOADER VERSION -" and "BASEBAND VERSION -" as empty!
8)no longer able to access TWRP
9)reboot bootloader -> brings it back straight to fastboot mode, Power off and on -> brings it back straight to fastboot mode, Start recovery -> brings it back straight to fastboot mode Just fastboot working.
my device details.
-using last version of Oxygen OS (android 9) on my Oneplus 6T . did not upgrade to android 10
-cant remember if my USB debugging in dev mode settings is turned off
Troubleshoot i did so far
-i have tried flash twrp-3.3.1-27-fajita-Pie-mauronofrio.img from fast boot which return this error
C:\adb>fastboot boot twrp-3.3.1-27-fajita-Pie-mauronofrio.img
downloading 'twrp-3.3.1-27-fajita-Pie-mauronofrio.img'...
OKAY [ 0.666s]
booting...
FAILED (remote: Failed to load/authenticate boot image: Load Error)
finished. total time: 0.679s
Hi, Hopefully someone can assist you here....
Only possible way is to pull the boot.img from the Fastboot ROMs Thread. Otherwise you may have to try MSM to unbrick your device.
Huskied said:
Only possible way is to pull the boot.img from the Fastboot ROMs Thread. Otherwise you may have to try MSM to unbrick your device.
Click to expand...
Click to collapse
greatly appreciate your help! flashing fastboot rom works.
however during booting up phone everytime is will shown "Your device is corrupt it can't be trusted". - fixed by further applying latest OTA updates
[deleted]
Huskied said:
Only possible way is to pull the boot.img from the Fastboot ROMs Thread. Otherwise you may have to try MSM to unbrick your device.
Click to expand...
Click to collapse
@Huskied Will flashing only the boot.img delete all data from internal storage?
I want to boot into a twrp.img so I can decrypt and recover the data but I get the same failure to authenticate error.
spinergist said:
@Huskied Will flashing only the boot.img delete all data from internal storage?
I want to boot into a twrp.img so I can decrypt and recover the data but I get the same failure to authenticate error.
Click to expand...
Click to collapse
flashing boot.img will only touch boot and nothing else.
Huskied said:
flashing boot.img will only touch boot and nothing else.
Click to expand...
Click to collapse
If I understand correctly, and before I get too excited about getting my data back, then does that mean I can fix this authenticate error without losing my encrypted data if I do fastboot flash boot boot.img?
(I have some book chapters from my novel that I really don't want to risk losing so its important to figure out if twrp will let me decrypt the data if I flash the new boot.img)
spinergist said:
If I understand correctly, and before I get too excited about getting my data back, then does that mean I can fix this authenticate error without losing my encrypted data if I do fastboot flash boot boot.img?
(I have some book chapters from my novel that I really don't want to risk losing so its important to figure out if twrp will let me decrypt the data if I flash the new boot.img)
Click to expand...
Click to collapse
If it doesn't boot and you can't your data back, Dirty flashing might be the last hope. Otherwise, Data will stay encrypted unfortunately.