Develop Bugs

Hard Reset Won't Work On My Acer A100

I have tried a hard reset with the volume up button + power button until vibrates then switching screen lock on and off. I see the Erasing user data...Erasing cache... come up then I let go and all it does is gives me the acer logo and proceeds to bootup like normal. I have tried about 100 times lol
I am just trying to figure out how to reset the password on the device I purchased it and it was locked.
I have tried the update.zip thing which didn't work (see below)
Erasing Cache before SD update
SD Update cmd: recovery
--update-package=SDCARD: update.zip
Booting recovery kernel image
Recovery verified failed ...
The bootloader is: Bootloader v0.03.13-ICS: Starting fastboot USB download protocol
I am not sure if the bootloader is locked or not and I don't know if the tablet is rooted how would I check?
Thanks.

craig105 said:
I have tried a hard reset with the volume up button + power button until vibrates then switching screen lock on and off. I see the Erasing user data...Erasing cache... come up then I let go and all it does is gives me the acer logo and proceeds to bootup like normal. I have tried about 100 times lol
I am just trying to figure out how to reset the password on the device I purchased it and it was locked.
I have tried the update.zip thing which didn't work (see below)
Erasing Cache before SD update
SD Update cmd: recovery
--update-package=SDCARD: update.zip
Booting recovery kernel image
Recovery verified failed ...
The bootloader is: Bootloader v0.03.13-ICS: Starting fastboot USB download protocol
I am not sure if the bootloader is locked or not and I don't know if the tablet is rooted how would I check?
Thanks.
Click to expand...
Click to collapse
Sounds like someone relocked the boot loader with a custom recovery installed. It'll say unlocked if it is.
You could let it boot android and see if you can still adb in and get it unlocked again, if its failing to boot android and recovery you bought a tablet someone bricked.
Tapatalked from my GNex - JBSourcery 4.5.6

pio_masaki said:
Sounds like someone relocked the boot loader with a custom recovery installed. It'll say unlocked if it is.
You could let it boot android and see if you can still adb in and get it unlocked again, if its failing to boot android and recovery you bought a tablet someone bricked.
Tapatalked from my GNex - JBSourcery 4.5.6
Click to expand...
Click to collapse
Yeah I think it's bricked luckily the guy at the pawn shop said I could take it back within 30 days since I purchased it with the unknown password on it.
I managed to get a 32gb Nexus 7 from craigslist for $170 today so happy with that.
Thanks!!

craig105 said:
I have tried a hard reset with the volume up button + power button until vibrates then switching screen lock on and off. I see the Erasing user data...Erasing cache... come up then I let go and all it does is gives me the acer logo and proceeds to bootup like normal. I have tried about 100 times lol
I am just trying to figure out how to reset the password on the device I purchased it and it was locked.
I have tried the update.zip thing which didn't work (see below)
Erasing Cache before SD update
SD Update cmd: recovery
--update-package=SDCARD: update.zip
Booting recovery kernel image
Recovery verified failed ...
The bootloader is: Bootloader v0.03.13-ICS: Starting fastboot USB download protocol
I am not sure if the bootloader is locked or not and I don't know if the tablet is rooted how would I check?
Thanks.
Click to expand...
Click to collapse
did you managet to unlock your tablet?
I have the same problem with a Acer Iconia A100 wich has user code...Tryed to hard reset it,I can get into recovery menu, but once the recovery menu appears the device won't take the wipe command.
I can scroll with vol buttons through comands:
-reboot system now,
-apply update from external storage
-wipe data/ factory reset
-wipe chache partition
-apply update from chache
it's just like I am not pressing the confirm button,but all butons are ok
any one has a fix for this problem ???????????

Same issue
dragosgsm said:
did you managet to unlock your tablet?
I have the same problem with a Acer Iconia A100 wich has user code...Tryed to hard reset it,I can get into recovery menu, but once the recovery menu appears the device won't take the wipe command.
I can scroll with vol buttons through comands:
-reboot system now,
-apply update from external storage
-wipe data/ factory reset
-wipe chache partition
-apply update from chache
it's just like I am not pressing the confirm button,but all butons are ok
any one has a fix for this problem ???????????
Click to expand...
Click to collapse
I'm having the exact same issue. I'll let you know what I figure out. I've had mine rooted previously, but have since done a stock ICS update, which removed root. I let the kid play with it for a year and now it's in the exact state you describe. I'm hoping to get it going so I don't need to buy him another tablet!

did you fix this?? im having this issue

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

Wileyfox Swift stuck/boot loop

Hi all.
I have a phone stuck in boot loop. It's a stock ROM, Android 7.1.2 (January 2018) but I dont have exact image reference (Wileyfox/switf/crackling 7.1.2/N2G48B/eeea277114 from recovery mode) . Secure boot is still enabled and phone is locked, but I have the unlock schema
When the phone boots, it stucks approximately 2 seconds after the lock screen. The screen then turns off and it reboots after a few minutes. If I am fast enougth, I sometimes have time to unlock but it freezes immediately after, and reboot after a while.
It started after the phone has been turned off. The last application installed is the GEEV application. Maybe it's the cause, or maybe the phone is full.
What I tried:
As stated in Facebook Wileyfox post ( unable to post full url: officialwileyfox/posts/1844545742523409),
I can access the safe mode (vol down at Wileyfox logo), but it does not change anything, it still stucks and I can not deactivate the last application installed.
I can access the bootloader and recovery mode, but I cannot access it via adb / fastboot (linux), I suppose because I cannot enable acces in devolopper mode in phone setting. I tried to update an older image from SD card, but the phone refused to downgrade to an older image.
I also tried to wipe cache partition.
Photo and contacts are backup, only SMS are not backup and I would like to access it.
Do you have any suggestion to access user partition or unblock the phone wihout wiping user data?
Thanks

If you can reach recovery mode there should be a phone reset option that can clear the apps.

Here are recovery mode choices:
-Reboot system
-Reboot to booloader
-Apply update from ADB
-Apply update from SD card
-Wipe data/factory reset
-Wipe cache partition
-View recovery logs
-Run graphics test
-Power off
I already tried wipe cache partition without result.
But I didn't try wipe data as this will also wipe SMS, won't it?

SMS should be saved to the cloud and restored when you enter your gmail account after the reset.

No it's not saved, that's why I need to access the phone if there is a way

If you can unlock the bootloader you could install twrp recovery which has an mtp mode which would give you access to your files. Suspect unlock bootloader will not be available to you.

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.

A5 2017 (SM-A520F) bricked after TWRP wipe before installing custom ROM

Hi!
So it appears I have soft-bricked my phone. At least I hope this is a soft one, but looks harder and harder with every minute.
What I did:
- I have an A5 2017 initially running Android 8.0.0 build A520FXXUGCTKA.
My plan was to install Lineage for MicroG on it. I followed the instructions on the Lineage website, encountered immediately an absence of OEM unlock button, solved it with flashing latest stock ROM with CSE which also reset the device and doing the date/time trick (+- 8 days), after which OEM unlock appeared and I had both it and USB debugging on.
So I proceeded to install TWRP and was able to successfully boot into it, after which I followed the next fatal steps:
Now tap Wipe. <<did this
Now tap Format Data and continue with the formatting process. This will remove encryption and delete all files stored in the internal storage. <<did this, and it suddenly gave me a bunch of errors about being "unable to mount /data"
I disliked this and decided that I have to solve this before proceeding to step 3 of the guide. So I found somewhere a solution to go to Advanced Wipe, select the Data partition and repair it, which I did, but after this step I think it recommended to reboot the phone, which I unfortunately did... and I was stuck in Samsung boot with only the logo loading. I panicked and immediately tried to go back to recovery, which stopped the loop and game me the red message Only officially released binaries are allowed to be flashed.
So the status of the phone right now is:
- I cannot go into recovery mode anymore. It gives the red message about official binaries.
- Phone doesn't load into system either. It again gives the red message.
- I can go into Download mode and see the following status:
ODIN MODE
DOWNLOAD SPEED: FAST
PRODUCT NAME: SM-A520F
CURRENT BINARY: CUSTOM
( I did not actually go to step 3 of the guide and try to upload the custom ROM. But I suspect this is because it now sees the ROM as changed/damaged)
SYSTEM STATUS: Official
RMM STATE: Prenormal
(This line was absent when I managed to turn on the OEM unlock finally. Now it's back)
FRP LOCK: OFF
Secure Download: Enabled
- I cannot upload ROMs via Odin anymore. The device isn't seen by it with Download mode like before. The drivers were installed by me previously and I was able to upload via Odin. I tried to reinstall them with zadig, but instead of 2 entried named Gadget Serial like before, zadig now only sees one Gadget serial and one Unknown device #1.
I tried to flash ROM in parts to the partitions directly (binaries, img) via Heimdall (using phone.pit mapping I downloaded a bit earlier via Heimdall). Heimdall said that it was a success on each download part, but also wrote 0% near the progress and it seems that it did nothing.
To me, phone looks now as if it sees its ROM as damaged, but ignores any attempts to get anything on it anymore. Which is logical because it seems to have either locked itself in a new state or restored to the state where the USB debugging and OEM unlock are not turned on. And I can't obviously get the system to load to turn them on.
Maybe somebody encountered a similar situation and knows how to get it out of this state or what this might be?