Database Users

Xoom (MZ604) Stuck in Honeycomb Animation!!!!

Ok here goes…….I have a problem with my wifi xoom……basically it wont boot. All that happens is a continuous honeycomb type animation that never goes.
This problem started in about February time this year when I was attempting to unlock, root and flash a custom ROM on the device. Since then I have been continually reading the forums and trying various method to resolve the issue.
I cant say exactly what I did at the outset as it was some time ago but I suspect that I may have used an outdated guide or flash the wrong image to my device. I do remember that following that the device booted up fine and then the following morning I was greeted with this problem that I have been unable to resolve.
From ADB dumpstate…. I can see the following entry……(I guess this is the kernel i flashed?)
[ 207.730229] Restarting Linux version 2.6.36.3Tiamat_Xoom-v1.3.0-gc02ada7 (big
[email protected]) (gcc version 4.4.0 (GCC) ) #1
SMP PREEMPT Wed Apr 13 04:27:14 PDT 2011
I have become intimately acquainted with ADB and Fastboot and have tried many times the routine of Unlocking the bootloader, Using fastboot to flash the Motorola Stock image files to flash back to stock and start again. All of this appears to work but when I reboot I get the same bootloop.
Unlike many other posts, I don't have a problem with ADB mounting the Xoom so I know my drivers are correct. I am able to communicate with the xoom via ADB and Fastboot and also use ADB shell to navigate the filesystem.
What happens persistently is that when flashing any image, the xoom reports it has flashed successfully, however when rebooting nothing has changed.
This is particularly evident when trying to flash a recovery image ('recovery-Tiamat-R4c-100611-1150-cwm-1.img' ) to gain access to clockworkmod recovery. When I reboot, all I get is the Android Recovery menu. I have tried this many times paying particular attention to the ….power +vol up……….Moto logo (wait 3 secs)……vol Down………vol up and still get the same result.
I can also make changes to the file system while in ADB shell such as changing the boot animation which actually changes on the screen of the xoom……and also uploading SU and Superuser.apk ………..but when I reboot…all of the changes have been undone and the same problem remains.
I understand that in the later models any custom recovery will be overwritten on reboot? Is this correct?
I took a look at this guide;
http://forum.xda-developers.com/showthread.php?t=1477024
5.) Now you have to rename the 2 notorious files, that reinstall your Stock Recovery over CWM, into a format that is unreadable by the bootloader. In the already opened Command Prompt, type the following commands:
Quote:
adb remount
adb shell mv /system/recovery-from-boot.p /system/recovery-from-boot.p.old
adb shell mv /system/etc/install-recovery.sh /system/etc/install-recovery.sh.old
My problem here is that i cant get the recovery image to stick, and while ever i'm in Fastboot I can't gain shell access to rename the recovery files. If I reboot the device the recovery image gets overwritten and these files are not present.
I have also considered flashing an update.zip via host cable (Android Recovery from USB) to negate the need for clockwork mod but that didn't work either.
I feel like I am so close, there must be something I can rename change to avoid this overwriting cycle. I have a full recursive file listing (ls -alR) for anyone to view in order to help. I don't understand the contents of the OS enough to know what should and shouldn't be there.
Anyone help please ??

If you are planning to flash jelly bean , there is no need to root, just unlock your boot loader and flash recovery IMG and the rom is pre-rooted. Here is a guide.
---------- Post added at 10:36 AM ---------- Previous post was at 10:34 AM ----------
http://forum.xda-developers.com/showthread.php?p=29733454

Can't mount cache... can't change droidboot and recovery

hello xda community
I made sure to try everything (or almost) before post here
my ZenFone 5 show a message that it cannot mount the cache partition and I am stuck on the Asus logo (I can access droidboot and recovery but I cannot replace them)
factory reset and cache wipe does not make any change (they return the same "can't mount cache" error.
I am trying to change the current droidboot and recovery to fastboot and TWRP but not matter how much I flash them, it does not take change (yes, I am unlocking the bootloader)
I am also executing a script to get the original partitions table back but when sec_offline_update_image.cmd executes the command "fastboot oem partition /tmp/partition.tbl" I get the error "FAILED(remote: GPT command failed)"
as this came out of thin air, I didnt have the chance to activate developer mode on my phone
I starting to get concerned .... any help?
thnk you very much in advance

@dgadelha any help ?

What are the specs of your Zen 5?

dgadelha said:
What are the specs of your Zen 5?
Click to expand...
Click to collapse
ZenFone 5 - A501CG T00J
Serial # with 0123456789ABCDEF issue
Box info: A501CG2 / A501CG-1F589 / CPU Intel Clover Trail Plus + Dual Core 1.6 Ghz, Purple, 8GB RAM
I already checked basically all links on Google related to the above issues (4 days Googling it already).
I really don't know what to do anymore.

A little more context @dgadelha.
2 months ago, I unlocked my bootloader for the 1st time and installed BlueLight 3.24.40.87... after the installation I locked my bootloader again using the boot, recovery and droidboot images contained in UL-ASUS_T00F-TW-3.24.40.87-user (Asus' official).
BlueLight worked fine with minor bugs for 2 months until past week when it suddenly started to crash a LOT, get slow and overheat (I didn't had time to fix it).
Then suddenly, all Android services and apps on the phone crashed and the phone turned off entering in a bootloop (Asus logo) everytime I reboot.
Since then I am getting the "E:Failed to mount /cache (Invalid argument)" issue when loading the recovery mode.
Since then I am also not being able to flash anything on my phone... no different recovery, no other fastboot and no other image... I get success messages on the flash process but nothing changes after restart (I can still access droidboot and recovery but nothing works there as the "Failed to mount /cache" error pops up for any action I try... recovery mode shows version 3.24.40.87_201).
When I try a system image via adb sideload I get error "Total xfer: 0.00x".
When I try "sec_offline_update_image.cmd" I get an error on the command "fastboot oem partition /tmp/partition.tbl"... the error is "FAILED(remote: GPT command failed)".
I have tried 2 different "partition.tbl" files... one that contains the "spare" partition and another one that contains "misc" instead... both failed.
I am now currently trying xFSTK (I don't even know what this does on my phone) and ASUS Flash Tool... ASUS Flash Tool returns "Flash image failure (FAILED (remote: GPT command failed))".
PS: I forgot to activate developer mode and other related options before the crash.
I hope that my phone is somehow alive... btw, thank you very much in advance!!!

jaabax said:
A little more context @dgadelha.
2 months ago, I unlocked my bootloader for the 1st time and installed BlueLight 3.24.40.87... after the installation I locked my bootloader again using the boot, recovery and droidboot images contained in UL-ASUS_T00F-TW-3.24.40.87-user (Asus' official).
BlueLight worked fine with minor bugs for 2 months until past week when it suddenly started to crash a LOT, get slow and overheat (I didn't had time to fix it).
Then suddenly, all Android services and apps on the phone crashed and the phone turned off entering in a bootloop (Asus logo) everytime I reboot.
Since then I am getting the "E:Failed to mount /cache (Invalid argument)" issue when loading the recovery mode.
Since then I am also not being able to flash anything on my phone... no different recovery, no other fastboot and no other image... I get success messages on the flash process but nothing changes after restart (I can still access droidboot and recovery but nothing works there as the "Failed to mount /cache" error pops up for any action I try... recovery mode shows version 3.24.40.87_201).
When I try a system image via adb sideload I get error "Total xfer: 0.00x".
When I try "sec_offline_update_image.cmd" I get an error on the command "fastboot oem partition /tmp/partition.tbl"... the error is "FAILED(remote: GPT command failed)".
I have tried 2 different "partition.tbl" files... one that contains the "spare" partition and another one that contains "misc" instead... both failed.
I am now currently trying xFSTK (I don't even know what this does on my phone) and ASUS Flash Tool... ASUS Flash Tool returns "Flash image failure (FAILED (remote: GPT command failed))".
PS: I forgot to activate developer mode and other related options before the crash.
I hope that my phone is somehow alive... btw, thank you very much in advance!!!
Click to expand...
Click to collapse
Hi,
Did you have any kernel mods when using BlueLight?
Sorry but I don't know if it had a custom kernel, but a custom one could have lead a storage drive crash.
Also, xFSTK will just attempt to restore your droidboot and dnx/ifwi, not the partition table or w.e.
Maybe you could try extracting the Jelly Bean RAW file with 7-Zip, flash the droidboot signed image (should be like, fastboot flash fastboot file.img, or fastboot flash droidboot file.img), the droidboot signed image name might be something like droidboot.signed_POS.bin (it's an img file too, but with a bin extension).
After flashing that droidboot image, reboot your bootloader and try running the sec_offline_image_update.cmd again.
I wish I had Zenfone Assist active yet, but had to take down it.
Thanks

Hey jaabax, were you able to fix your device ?

Hi @vikrammarkiv.
Sorry for the big delay in response... I am not using this e-mail anymore and I quit fixing my phone.
Unfortunately I could not fix it and I ended up buying another phone.
Could you fix it?
Sorry again and hope you fixed it.
Best regards.

same issue, anyone got any update on fix?

jaabax said:
A little more context @dgadelha.
2 months ago, I unlocked my bootloader for the 1st time and installed BlueLight 3.24.40.87... after the installation I locked my bootloader again using the boot, recovery and droidboot images contained in UL-ASUS_T00F-TW-3.24.40.87-user (Asus' official).
BlueLight worked fine with minor bugs for 2 months until past week when it suddenly started to crash a LOT, get slow and overheat (I didn't had time to fix it).
Then suddenly, all Android services and apps on the phone crashed and the phone turned off entering in a bootloop (Asus logo) everytime I reboot.
Since then I am getting the "E:Failed to mount /cache (Invalid argument)" issue when loading the recovery mode.
Since then I am also not being able to flash anything on my phone... no different recovery, no other fastboot and no other image... I get success messages on the flash process but nothing changes after restart (I can still access droidboot and recovery but nothing works there as the "Failed to mount /cache" error pops up for any action I try... recovery mode shows version 3.24.40.87_201).
When I try a system image via adb sideload I get error "Total xfer: 0.00x".
When I try "sec_offline_update_image.cmd" I get an error on the command "fastboot oem partition /tmp/partition.tbl"... the error is "FAILED(remote: GPT command failed)".
I have tried 2 different "partition.tbl" files... one that contains the "spare" partition and another one that contains "misc" instead... both failed.
I am now currently trying xFSTK (I don't even know what this does on my phone) and ASUS Flash Tool... ASUS Flash Tool returns "Flash image failure (FAILED (remote: GPT command failed))".
PS: I forgot to activate developer mode and other related options before the crash.
I hope that my phone is somehow alive... btw, thank you very much in advance!!!
Click to expand...
Click to collapse
Same problem, only fastboot and GPT failed (Asus zenfone 2 ze551ml). No solution

Exactly the same problem. It appears there are no fixes. How did the xf... thingy go?

Оh man.. I have the same issue, and can't fix it...

Can't boot into TWRP after rooting with TENFAR ver. 1.10

Hi all,
So I recently received a new Axon 7 after having my old one replaced, and I can't seem to root this one. The guide for the root that I am following is located here (https://www.reddit.com/r/Axon7/comments/5ezwj3/axon_7_the_current_rooting_and_custom_rom/)
After I type
Code:
flash.exe -p COM(port) -r
it says
Code:
writing recovery.img success, Device Rooted!
However, when I go to boot into the TWRP recovery, my phone shuts off and does nothing. If anyone could help me figure out how to boot into TWRP, I would appreciate it! Thanks!
EDIT: adb reboot bootloader just restarts the phone and adb reboot recovery shuts it off. Am puzzled...

[SOLVED] Unable to boot any recovery, stuck with fastboot-screen and unlocked bootloader-warning after trying to run Lineage18 recovery on Android9

I'm trying to boot a Oneplus 6T into linage recovery-mode, so I can install latest version of Linage.
I can boot into fastboot, but I am unable the boot the recovery image (or any recovery, also tired with TWRP). When I run "fastboot boot [recovery-image-nam-and-version].zip", I get no errors, all looks good, but the phone then just immediately reboots/switches into a screen showing the OnePlus logo + "Fastboot Mode", and then just hangs there forever.
If I boot normally I am greeted with the "The boot loader is unlocked" warning-screen. It also just hangs there, nothing happens. Nothing is booted.
I am running latest version of Fastboot. OEM is unlocked. When I boot into fastboot, I get this content:
PRODUCT_NAME - sdm845
VARIANT - SDM UFS
BOOTLOADER VERSION -
BASEBAND VERSION -
SERIAL NUMBER - [redacted]
SECURE BOOT - yes

Solved. Turned out I was a fool and had somehow missed the big red blinking WARNING only to try to install Lineage on Android 11. (I will never do that again, I promise)
SOLUTION that worked:
Getting out of the fastboot-loop: Seems like everything needed to go back to the outdated Android 9 to work, as this was what was originally installed. So: re-install Android 9, upgrade to 10, upgrade to 11, install Lineage. In more detail:
re-partitioned the device, using this guide (selecting an older version, going back to Android 9. I chose the olderst of the 9s, maybe a newer would have done the trick too): https://forum.xda-developers.com/t/...t-stock-fastboot-roms-for-oneplus-6t.3862516/
on Linux I had to poke around in the zip-file a bit, but the quick fix was to copy all the commands in the "Fastboot Partitions" section into a textfile and create a script out of it ("#!/bin/bash" in the top, and search/replace "fastboot" to "~/Downloads/location-to-downloaded-gsuite-tools/fastboot"
first boot launched a very simple recovery system. Chose clear all cache and wipe all. After a couple of failed reboot-cycles, it succesfully booted Android 9
(Unsuccesfully tried to upgrade to Android 10 using system dialogues)
Managed to boot into TWRP recovery after fastbooting it:
From TWRP:
Sideloaded TWRW-install into boot to make it persistent recovery. (Pay careful attention to version-numbers, all you install have to fit Android 9)
Sideloaded "copy-partitions.. .zip" as recommenden by Lineage
Sideloaded Android 10 .zip
Booted into Android 10
ran system update successfully to Android 11 (takes some time, appr. 20)
Booted Lineage recovery via Fastboot, this time it ran
Followed the Lineage install-guide through to sideload Lineage 18
Thanx to the people in Lineage IRC to point a lot of this out.

Lumia 520 RM-914 with lineage os. Constantly restart after showing nogia logo.

Hello,
half a year after installing the os lineage, I decided to turn on the nokia again. Unfortunately, the phone restarts when the Nokia logo appears. All I can do is go to fastboot by holding down the volume down key. When I try to run twrp with command: fastboot boot twrp.img the phone will also restart. Nokia was completely unused for half a year, it had to be deleted by itself. ADB is not working. Anyone have any idea what can be done to run it? Charge the battery probably won't work without the proper boot.img. Could it be the fault of a discharged battery?

OKAY. Somehow I managed to restore the phone to Win 8. After switching to fastboot (volume down + connecting the USB cable to PC) I ran a series of commands: fastboot oem device-info, fastboot oem unlock, fastboot reboot bootloader. After this last command, OS lineage started - maybe something has crashed. I used fastboot from the file which is attached flash.7z ,then follow the instructions on the page:
Restore Windows Phone 8 if you have Android installed (Windows instructions)
Thanks to @feherneoh who posted the content of this thread originally here:Post #1 Post #2 NOTE: DO NOT ask for a backup. If you do not have one, you have to accept to be permanently on Android like me. Create a folder somewhere that we can...
forum.xda-developers.com
I have fallow through all the steps.
I manually copied the fame_wp_unlocked.gpt file from running the lineage OS to the / sdcard directory because adb commands do not work in TWRP. I run the sgdisk --load-backup /sdcard/fame_wp_unlocked.gpt / dev / block / mmcblk0 command manually from TWRP terminal.
When flashing partitions, i used the command not like flash TZ.img but fastboot flash TZ TZ.img etc ... (name of the partition mmust be written before image name). After that i was abe to restore all system thru WIndows Phone Internals application.
Better not to upload this Lineage OS - only problems! The phone may have been blocked by the network !!!