ACER LIQUID Z630 - System Update Loop / Can't boot - Android Q&A, Help & Troubleshooting

This phone is my brother's. He said he just downloaded a system update, I think it is OTA. And when update starts (from the stock recovery? not sure) It stucks at 50% progress bar, and it reboots. And update starts again, and reboots again. It won't boot even after removing battery, putting battery back on and turning the phone on, it persistently go back to loop update system. Should I flash it with a stock ROM? which one? The build no. I think is 1.0020? Can I flash the 1.050 one? Here is a pic of what's happening in a loop.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Follow this guide to reboot into recovery
http://www.hardreset.info/devices/acer/acer-liquid-z630/recovery-mode/
After entering recovery , try factory resetting your device.
This will reset all data.
If the above method didnt work , only option is to flash a Rom manually using SP Flash Tool
Stock Rom
http://vache-android.com/hubicAcer/Z630/OS Images/Acer_AV0L0_T03_1.020.00_EMEA_GEN1.zip

Hello there. Please take a look at this guide by Shreps.
Download a compatible custom recovery (CWM or TWRP) for your device. Also download the firmware (ROM) for your device (list by Shreps). Please refer to the guide (there should be one). You would need to (a) Install necessary drivers, and (b) ADB and Fastboot interface (try this)
Copy the custom recovery image into the root folder of your ADB and Fastboot program. Copy the firmware to your device (via external sdcard since you cant copy directly into the internal sdcard).
Go to recovery via (a) volume up + power buttons, or if device accessible via ADB, (b) adb reboot recovery
In the recovery options, choose 'fastboot' (or simply, via adb: adb reboot bootloader)
Go to your terminal/cmd: fastboot devices - and see if your device is recognized
Then: fastboot boot "recovery.img" (replace "recovery" with the name of the recovery image)
In the recovery, navigate and select "Install" and select the firmware on the external sdcard. (wiki)
If you cant install via fastboot (bootloader must be unlocked first before using fastboot), then flash the rom via SP Flash tool (refer to the guide)

Related

[Q] Help. Stuck in Android system recovery<3e>

hi i managed to update my tab to the latest firmware 4.0.4 . Previously it was already rooted and TWRP installed. I was thinking of rooting and backing up this build so from romtoolbox i boot into recovery mode (thinking that i will be seeing TWRP) But when boot i was shown the folllowing picture
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
since all of my buttons are not working (hence the reason installing TWRP ) i was ok fine lets reboot it via adb. therefore i run adb reboot and yet it still boots back to the same screen . Thinking i need to reverting all of the changes via odin i tried reboot download also does not work. reboot-bootloader also does not work. apprently i am stuck at this screen.
Right now i only have access to adb and is there any way i can recover from this?
many thanks again
I'm assuming you were running some kind of custom rom with TWRP as your recovery before going to stock ICS. Essentially, flashing stock ICS overwrote the old TWRP.
To fix it, flash in TWRP again (its somewhere in the development section) via Odin.
EDIT: If you can't access download mode... Try push the TWRP .tar file via ADB
Sent from my GT-P7510
Soryuu said:
I'm assuming you were running some kind of custom rom with TWRP as your recovery before going to stock ICS. Essentially, flashing stock ICS overwrote the old TWRP.
To fix it, flash in TWRP again (its somewhere in the development section) via Odin.
EDIT: If you can't access download mode... Try push the TWRP .tar file via ADB
Sent from my GT-P7510
Click to expand...
Click to collapse
the thing is i only root and installed twrp for the sake of backing up since my daughter loves to install application. I've read about pushing / Installing application but that would requires root right? this is my command console like
Right now is there a way to force it to boot into download because thats the only way i see i can fix it (without using physical buttons)
Again many thanks for replying.

Please fix half brick of my devices

Dear all,
I've used device name EBEN T4 (e人e本 T4 - from china). I rooted device and deleted/modified system. So, now it can not boot, it stuck at manufacter logo. I wiped data/factory reset or wipe cache but not success. So it need to be reflashed device roms.
Device allowed me to enter recovery mode and select update rom from zip file on SDCard (internal memory). I saved zip file on SDCard. BUT SDcard have so many folders and files in root folder, and zip file names "update.zip" - it means that it is on near last of list, and recovery limited number of line to view, so i could not browse to update file.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Device has Vol +/-, home, left, right, back, menu and power button. (Home + Power will bring me to recovery mode)
Device use CPU Freescale i.MX535, android 2.3.4, origional recovery system.
Please suggest me how to fix that by anyway.
P/S: I found that Back + Power will bring me to fastboot interface?
Need help so much
That's why you should backup your system before rooting etc. Do you have a stock image of your device?
eagleeyetom said:
That's why you should backup your system before rooting etc. Do you have a stock image of your device?
Click to expand...
Click to collapse
Thank you for reply.
This is stock image: http://update.eben.cn/t4/update.zip
I found that my device could enter fastboot mode by press back + power button.
When connect usb, screen show:
[fastboot mode]
fastboot is in init......
fastboot transfer buffer: 0x0000000
flash <1 word i cant recoginze> is MMC: 1
USB Mini b cable Connected!
fastboot initialized
USB_SUSPEND
USB_RESET
USB_RESET
Windows device Manager (on WIndows 7 32bit) shows that device connect (ADB), i'm used to use many ADB universal driver (google, ClockworkMod). When i used "fastboot devices" command, it reponsed nothing.
Could i connect to fastboot to update file update.zip to device? If ok, how i connect?
Fastboot will give you nothing, mate. Try to set up the ADB and use adb sideload <path/to/zip> without "<>" or delete folders in recovery by going to adb shell and changing the dir by cd command and removing them by rm -r foldername.
Good luck.

[GUIDE] - How to fix force close when downgrade firmware without data on sdcard lost

I'm not responsible for any damage what-so-ever done to your phone, you accept this risk.
Hi all,
I'm proud to present guide how to fix force close when downgrade firmware without data on sdcard lost.
In case , I have flashed OptimusG3 V1.4 that is a higher firmware than LG G2 D80220c then I want to return to stock with KDZ flashing method (Use D80220c firmware).
While G2 boot normally and prepare enter to system I got many error.In this case the one way you have to use TOT flashing method.Your data in SDCARD will be lost.
Testing on D802 Work.... All files in Zip for D802 Only ..
You can apply with other variant. Changing recovery.img and laf.bin
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I have a little guide to help you return back to stock without data on SDCARD lost.
1. Download LG_Root_LP_20150313.zip
This is a new ROOT method from
http://forum.xda-developers.com/android/development/guide-root-method-lg-devices-t3049772
I got it from that link.I'm adding recovery.img that is a TWRP Recovery in to zip file and laf.bin Partition.
2. Unzip LG_Root_LP_20150313.zip
3. Put G2 in Download Mode
4. Open command DOS in LG_Root_LP_20150313 (Click Command Prompt.bat )
5. Checking what is port that connect between G2 and Computer (Run ports.bat)
6. Use command > Send_Command.exe \\.\COM41
COM41 is a port that connecting between G2 and Computer which find from 5.
This Method is RISK!!.It will be destroy your DOWNLOAD MODE. Please consider before use the next command...
7. Use command
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/laf
FOR destroy DOWNLOAD MODE
8. Use command
LEAVE
For exit. then G2 will be reboot
9. Trying Enter DOWNLOAD MODE again .The Phone will be enter fastboot mode instead.
10. Don't worry. In command prompt.Use Command
fastboot.exe boot recovery.img
For Reboot to TWRP Recovery
11. In TWRP .Choose Wipe > Advanced Wipe > Check
- Dalvik Cache
- System
- Data
- Cache
Then Swipe to Wipe
12. In TWRP Choose Home Button then Choose Reboot > Power Off
13. Tring Enter DOWNLOAD MODE again .The Phone will be enter fastboot mode instead.
Use Command
fastboot.exe flash laf laf.bin
For fix DOWNLOAD MODE
14. Use Command
fastboot.exe reboot
For exit fastboot mode
15. After that Trying Enter to DOWNLOAD MODE .You can Flash KDZ firmware normally.
ENJOY......

[HOWTO][ROOT]KM8 P 2GB/8GB S912 Amlogic TV Box Android 7.1, TWRP Root Instructions

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This is how I rooted my KM8P, using help and tools made by people far more awesome than me. Probably works for other RAM/ROM size variants too and possibly for Android 6 if you can get the TWRP for it.
1. Copy TWRP.zip and Magisk.zip file to SD Card or USB key. The Android recovery can read extFAT but TWRP cannot. FAT32 works for both.
2. Boot to Android recovery - hold reset and power on until logo appears Reset hole is at the front on the top face where the "KM8 P" writing is.
3. Apply update, from external.
4. "Install" TWRP (attached, for Android 7) - It will just load, not actually install. Optionally backup your ROM now or have a recovery zip on hand.
5. Install magisk from TWRP - I used 15.3 (attached) but feel free to try a newer one.
5a. I could not update Magisk via the manager so I flashed 17.1 via TWRP. (attached)
6. Reboot
7. Install BusyBox (Stericson)
8. Open Magisk Manager - Check for update
9. Donate a couple of bucks to topjohnwu for Magisk: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
This worked for my T95Z Plus with a few hiccups. I had to wire up the UART.
Since updating to 7.1 it won't boot to recovery from the reset button anymore. I had to use UART to get into the bootloader console (hold space while plugging in power) and execute "run recovery_from_flash". It refuses to boot recovery images directly from external media anymore, but by going into recovery this way I was able to execute TWRP (which starts up in Russian, but can be changed) and make a backup.
Next, installing Magisk ended up being a chore. I had to use the "create patched image" method. For whatever reason it refused to let me copy files to my USB stick, so I ended up having to split the patched image into chunks and email them to myself... anyway, TWRP was able to flash the image.
The final complication is that Magisk could only install to the recovery partition (no ramdisk) which means it's only active when booting in recovery mode. I was able to make this the default mode from the bootloader console by executing "env set bootcmd run recovery_from_flash" and "saveenv". After that, it boots up normally with Magisk enabled. I guess I don't have an actual recovery mode now, but I can use UART or USB Burn Tool to recover from bricking, so no big deal.
(Also Android itself was in Vietnamese but again this can be changed)
Thanks for the files and guide!

[GUIDE] Flashing any Custom recovery on Poco X3 | ADB Fastboot

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Yes until now people ask here, how to flash custom recovery over stock mi recovery. It's easy and quick detailed guide, Let's start.
Pre-requirement:
1- unlocked bootloader.​2- USB debugging enabled:
- Go to settings -> My device -> All specs -> hit build number 7 times till you see message ( you are developer now..)
- Then go to settings -> Additional settings -> Developers options -> Toggle on "USB debugging".
3- Download Minimal ADB Fastboot & install it.
Steps:
1- Download the custom recovery IMG to your PC.
2- re-name the IMG file to easy name such as: flash_me.img
3- copy the IMG file to the "Minimal ADB Fastboot" installation Dictionary.
4- Run "cmd-here.exe" as Administrator.
5- turn off your device and hold the "volume down + power" to enter fastboot mode.
6- once you booted in fastboot plug-in your device with usb cable to PC.
7- type in cmd :
Code:
fastboot flash recovery flash_me.img
8- When it finished type this command, When the screen goes off, Immediately Press "Volume Up + Power buttons" to boot into Recovery mode. or you will reset all the steps of flashing
Code:
fastboot reboot
9- Done
Good job.
Just a note: regarding point 3 of the pre-requirements, the official and most updated source would be https://developer.android.com/studio/releases/platform-tools...
pnin said:
Good job.
Just a note: regarding point 3 of the pre-requirements, the official and most updated source would be https://developer.android.com/studio/releases/platform-tools...
Click to expand...
Click to collapse
Thanks for your note
I had just uploaded latest version that I use and uploaded on my drive
(I meant to involve something I already tested)
my regards
i have unlocked the bootloader and i want to install a recovery, do i need to root my phone before flashing a recovery or not???
thanks in advance
MLDamazigh said:
i have unlocked the bootloader and i want to install a recovery, do i need to root my phone before flashing a recovery or not???
thanks in advance
Click to expand...
Click to collapse
No root need it. Flash recovery in fastboot mode and ur good to go.

Categories

Resources