Boot hanging on orange M screen - Moto G5S Questions & Answers

I just rebooted my G5s and it's hanging on the orange part of the boot sequence (orange background, yellow M).
Hard rebooting, clearing cache etc does not change anything.
It seems to be the part where I usually enter my code for decrypting /data (the pattern) but I am not sure.
Any ideas?
I rebooted alright yesterday, and before that. No updates since then...

Ok, it's fixed but I am unsure what fixed it.
Attempt 1, failed:
Flashed system chunks from https://forum.xda-developers.com/mo...h-official-firmware-moto-g5s-montana-t3687768
-> still hanging
Attempt 2, failed
Flash TWRP, wipe cache + dalvik cache
-> nothing changed
Attempt 3, success:
Flashed everything except erase userdata from
https://forum.xda-developers.com/mo...h-official-firmware-moto-g5s-montana-t3687768
-> success, devices boots and all my data is still there
So, one of the other flash commands must have fixed it.
Any ideas?

Related

Can't wipe/edit data patition

I finally flashed a non Sense ROM onto my dev edition M8, and now I can't even touch /data. I got the enter password to decrypt storage bug while using Paranoid Android, so I followed the steps here to get back to a working system, but the ROM never booted to the password screen. It froze on the boot animation, the went in a loop, I tried to wipe data through recovery, the screen went blank after a few seconds, and then tried to boot the system again. I can't get it to wipe via fastboot either as I get a "FAILED (remote: not allowed)" when trying erasing and formatting data/userdata. I also can't delete anything from /data in recovery. Does anyone have a fix for this? Flashing other ROMs also suddenly quit and go back to trying to boot the system.
Edit: Flashing a stock recovery to wipe /data fixed it. Why didn't I think about that sooner?

Stuck on load screen, unabled to enter recovery, adb erase cache has no effect

So my second zenfone is dead.
Like many others, it gets stuck at the asus loading screen with the spinning wheel.
This did not happen after any obvious action, like an update - it was just turned off when i woke up, and wont load beyond the spinning wheel of death.
I have booted into fast boot mode (power and vol +), selected [recover mode] and got the broken android logo.
I then hit power and vol+, then release vol+ as suggested, but instead of a menu, i get a bunch of yellow console output, 3rd line of which is:
E: failed to mount /cache (invalid argument)
This appears for less than a second, then back to flashing broken android logo.
Repeating ( power and vol+, then release vol+) results in the same briefly visible console output
I turn off, and reboot into fast boot mode, and try using adb.
I enter the command 'fastboot erase cache' and it completes in 0.4 seconds, no errors. Has no effect on phone (reboot stuck loading, recovery mode same error as above).
Next i try 'fastboot format cache' - the command appears to work, but again completes in just over a second, and has no effect on the phone.
The only info i could find directly relating to this error is on a random .info website, so im reluctant to follow the steps:
http://mobilecon.info/fix-asus-zenf...-into-recovery-mode.html#sthash.slqGoK95.dpbs
Anyone here solved this issue? Or is it time for a warranty claim?
Thanks
http://www.ibtimes.co.uk/how-unbrick-asus-zenfone-2-fix-bootloop-issues-1511521
Just don't do step 15 (factory reset) if you want to keep your old data.
azthemansays said:
http://www.ibtimes.co.uk/how-unbrick-asus-zenfone-2-fix-bootloop-issues-1511521
Just don't do step 15 (factory reset) if you want to keep your old data.
Click to expand...
Click to collapse
Thanks for the link - it looks much the same as the one i posted, with the addition of flashing the system image.
Do you know if there is any danger in trying without flashing system 1st?
Also, have you used or seen this method used specifically to fix the mount failure i have described, or its just a general 'de-bricking' guide?
Finally, do you or anyone else have any insight into why this might have happened in the 1st place - as i mention, i did not do anything beyond normal use prior to the issue.
thanks
Sounds like the recovery corrupted... could be a range of things from improper shutdown to an improperly coded app that caused the error. If you want to flash just the recovery and see if that fixes it, go right ahead, but don't forget to erase your cache after you flash recovery.
Whenever I get stuck in a bootloop, the steps I follow are:
1) clear the cache and see if it fixes it, as something might be there that's preventing you from booting
2) flash the most current firmware to see if it fixes it, as something might have modified a section of one of the partitions that's preventing you from booting (make sure to clear cache after flashing)
3) contact support because it's more likely hardware failure
There's no danger in flashing any of those partitions, at most you'd lose the Xposed framework, root and busybox - which are easy to reinstall. It doesn't affect much else, and your info should be intact. I would advise getting the firmware from a reputable source though... I just get it off the Asus website, then root the phone after.
Try reinstall recovery
Download stock recovery(there is download link from zenfone2 index)>go fastboot mode>then flash recovery using command :
fastboot flash recovery (recovery image name).img
>Reboot to recovery>adb sideload full firmware

Cannot load image fastboot

I've recently tried to update my radio and bootloader to the latest versions, i was on a custom rom (7.1.1), I've updated the bootloader and radio via fastboot and wiped the cache then rebooted then my phone was stuck in a never ending boot and all is saw was the boot animation, i decided to reboot the phone so i held the power button until it restarted and to avail, the same thing happened. I rebooted to twrp and tried to wipe the cache and dalvik/ART cache and i got an error that it cannot be mounted and the partition size was at 0mb and twrp could not repair it either, and it could not format any of my partitions, so i tried to return to stock and i tried to flash the images from the stock .zip provided by google and it said that it could not load any images. I can access download mode and twrp, any solutions? (someone said to flash the vendor image after flashing both the radio and bootloader images? could that have cause my problem because it did not flash it?
i was on the latest vendor already)
thanks.
EDIT: after continuously trying to wipe the cache & dalvik/ART cache in twrp it worked and it recognized the partitions and it wiped and my device was able to boot, i'm not sure what caused the problem but it boots properly now, although i'm not sure if i can flash in fastboot again, otherwise it works.

Can't mount data, twrp custom rom issue

Was running the pixel experience rom, have been for a month.. and I had a very strange issue today, the whole phone just froze, I force restarted it, and everytime It would reboot it would just hang/freeze or unlock and display nothing on my screen but the wallpaper.. ended up trying to restore from an old backup I had, but realized it was when I was running an oreo rom.. got stuck in a loop for fastboot, used twrp to re-install this rom, and it was taking forever to boot, at the G logo.. so stupidly instead of having patience and waiting, I rebooted and formatted data, or tried too, (read it somewhere) and its just been hung on that for hours now "formatting data" Dunno what to do.. I should have just waited on the initial boot after re-installing this rom, forgot it took forever.. dunno if should just keep waiting.. or try an flash back stock rom, and re-do everything.. I think my data partition is corrupted, or unmountable.. so not for sure how to proceed.
Format data or wipe data ?? Formatting data will remove encryption and everything will be erased
Wipe data just erases data partition
Try to clean flash once again by wiping system data cache
Here is the issue now.. when I would go to format data, it would just stay stuck on formatting data with ext4 or w/e ... I left it for an hour or more, and nothing.... so decided to use miflash an restore everything. it goes all the way... but never actually says success just still says flashing, even with the green bar full and says finished 200s or something.. the last part of the log always stops after:
"[3:52:43 AM 49c50e2d]:err:writing 'vendor' 2/2...
[3:52:43 AM 49c50e2d]:errKAY [ -0.000s]
[3:52:43 AM 49c50e2d]:err:finished. total time: 23.850s"
so I've let that set for 20 minutes or more, then finally I just manually kick it out of fast boot, and it'll start to boot with MI Logo, and it has the white bar at the bottom, the bar loads all the way then it just hangs there, ive left it over night an its just stuck there
Even now I can fastboot flash a recovery image, and boot into it, but its unable to mount data, missing crypto header.. maybe I should just let the "format data" take its time maybe eventually it will?

2nd Gen FireTv bricked/boot loop with TWRP

Hi all,
My AFT wouldn't boot this AM. Booted to TWRP and tried a wipe cache but got an error with cache not present, went into advance wipe and fixed this.
Installed latest pre-rooted rom. No errors rebooted but wouldnt boot.
Installed previous version 5.2.4.0 firetv goes into a boot loop (white amazon logo then back to Twrp screen)
Also tried installing the unbrick image again no joys.
Any ideas?
thanks
I've had this issue before, make sure system is mounted and if it boots up factory reset from settings but make sure you have access to a pre rooted rom on either USB or ext xd
bamemanxxa3416 said:
I've had this issue before, make sure system is mounted and if it boots up factory reset from settings but make sure you have access to a pre rooted rom on either USB or ext xd
Click to expand...
Click to collapse
When I go into TWRP recovery and check whats mounted everything appears to be mounted.
When I do an advanced cache wipe or normal wipe. Messages respond success no errors Just will not boot.
This all started because I turned on the AFT and it was dead and would only boot to twrp and when checked the cache was in error tried the usual wipe/advance wipe still errors. the did a change system and redid the ext4 this brought back a "clean system" no more errors on installing due to cache and everything looked good. Just still no boot.

Categories

Resources