Develop Bugs

Factory Reset - Now Bootloop

So I was using a cooked MCR ROM, but wanted to factory reset to start fresh. I went into the bootloader and selected factory reset and now it loops the boot animation over and over.
I've tried different ROM's, I've re-partitioned the SD (at one point I was seeing errors about not being able to access Apps2SD) and each ROM will boot up, take a long while on the first animation and then loop itself afterwards.
This isn't a normal boot loop, it doesn't actually reboot, just loop the animation.
Any ideas?

well yes you will need to flash your rom again, can you actually access your clockwork recovery menu by holding down the volume key when the system boots up ?
(fYI, it may come up with the with fastboot screen first)

oooo sorry forgot to mention, youll need to go into the recovery menu and also format the following by selecting mounts and storage before you reflash
- Data
- Cache
- Boot
- System
then once you reflash you should have it sorted, some boot animations do loop on first start up, if it takes longer then say 10 mins then you know its done, unfortunately there is no sure way to tell.

Okay thanks, wasn't sure about formatting boot and system.

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

Does not boot. Corrupted /data parition?

Hello,
my Samsung Galaxy S4 mini with bliss ROM stated to turn off spontaneously and sometimes it didn't start again (the Samsung logo appeared and then the phone went dead, it was impossible to enter recovery mode, download mode shut down itself immediately). After several tries, it booted normally. This happened again - and I found out it was a bad power button, which I replaced. Now it is possible to enter both recovery mode and download mode with no problems. However the main OS doesn't boot up. So I tried to do a full wipe in recovery mode and CWM recovery rebooted the phone, when it was trying to format /data partition. So I tried to flash stock firmware with ODIN. It also didn't boot up, but at least the stock recovery gave me a hint what is wrong. When I perform full wipe, I get error: "E:format_volume: make_extf4fs failed on /dev/block/platform/msm_sdcc.1/by-name/userdata"
I tried to flash the phone again, this time with a PIT file and let ODIN to reformat the partitions. However, no change. How can I fix it?

Try twrp

Factory reset stuck and Fastboot mode with device state locked

Hello,
Please find below the context from my BootLoader :
Phone: Wileyfox Swift 2+
Product Name - Marmite
Bootloader version - marmite-0-g184aa0da
Secure boot - enabled
Device state - locked
The problem I encountered and the actions I made:
The phone got stuck on the boot screen (frozen picture on phone start)
ADB (android debug) was not enabled before the phone got stuck. The phone was not rooted either.
I went to the recovery mode and decided to perform a wipe cache, with success
Then, I tried to perform a Factory reset from the recovery mode menu. It remains stuck at this step Formating /data. I left it for around 14 hours, then I decided to reboot.
I tried 3 times the Factory reset and it remained stuck at this step
I tried $fastboot flash recovery twrp-3.3.1-0-marmite.img when rebooting to the Bootloader (using power and volume up keys), however, it always displays < waiting for any device >
My questions:
How can I format the phone in this context? I don't mind loosing data so far, I just want to get back to a working phone.
Is it possible to flash a phone on which "Device State" is "Locked", not rooted, no custom bootloader, no debug enabled ? If yes, would you mind explaining it to me?
Thank you for any help you may provide

Mi Max 3 stuck in fastboot

Long story short, I tried to flash a global ROM on my Mi phone. However, after a few unsuccessful attempts at doing so, my phone is now stuck in the fast boot screen.
I tried all I know and what I can find online, but the problem still persists, where when holding the power button it would boot to main power screen and then make a buzz and go back to the fastboot screen.
Have tried:
- Resetting through recovery mode (pow + vol up)
- plugging phone into my computer to reflash the ROM (error remote: unknown command) / on my phone it would switch out of fastboot and instead display this message: "press any key/button to shutdown"
- pow + vol down (held for more than 1 minute)
- pow (held for more than 5 minutes, everytime it would boot and then boot back into fastboot mode with the buzz in between)
- ADB console commands:
- fastboot reboot
- fastboot device
- tried using MiPCSuite, plugged my phone in, but application didn't detect my phone
- running all applicable applications as mentioned above as admin
- when resetting phone progress bar would stop at 1.03% then it would say reset completed (I don't think did reset the phone, but whatever...)
- tried different ROM versions, Global and China (Once again it would either switch out of fastboot on screen OR in the flash tool it would display the error "unknown command" which I assume would be something to do with the communication between my PC and the device itself)
At this point I don't know what else to do, watched every tut on youtube, read pretty much all the forums I could find related to this issue.
Any help would be much appreciated!

Is it locked or unlocked?
I whould try to update firmware, then recovery (wipe all at this point) and at the end ROM (format data, wipe dalvik and cache at this point), always worked for me. But - the phone should be unlocked for this

Wywern.pl said:
Is it locked or unlocked?
I whould try to update firmware, then recovery (wipe all at this point) and at the end ROM (format data, wipe dalvik and cache at this point), always worked for me. But - the phone should be unlocked for this
Click to expand...
Click to collapse
I have tried going into recovery mode and wiping all data, and trying to update the firmware via the flash tool. But as I said above I can't it gives me the error "error: FAILED(remote:unknown command)" and since I can't get into my phone, I can't use mipcsuite either or enable and settings.

Note - wipe data and format data is not the same
I've stuck with some stupid error ("erase all data" message and reboot to twrp) for hours until I formated data

jayX23 said:
I have tried going into recovery mode and wiping all data, and trying to update the firmware via the flash tool. But as I said above I can't it gives me the error "error: FAILED(remote:unknown command)" and since I can't get into my phone, I can't use mipcsuite either or enable and settings.
Click to expand...
Click to collapse
did you solve it? i also need to flash rom via mi flash tool but I do exact same error.