Database Users

Nexus 7 2012 Endless Boot Animation after reverting to stock

So I decided to revert the Cyanogen Mod install on my Nexus 7 back to stock, but after doing so sadly I'm stuck on an endless boot animation with the spinning coloured circles.
The device is a Nexus 7 2012 WiFi only model
The process I followed was,
Reboot to fastboot,
Code:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
fastboot reboot bootloader
fastboot -w update image-nakasi-lmy47v.zip
This was where I got stuck in a boot animation, so I again went through the same process, but this time instead of running the fastboot -w update command, I ran the Flash-All.bat command that was included with the files downloaded from Google. Sadly I just get the exact same result, an endless boot animation.
I can still get to fastboot from being stuck there by holding down Power + Volume Down, and it displays the following information,
Product Name - grouper
Variant - grouper
HW Version - ER3
Bootloader Version - 4.23
Baseband Version - N/A
Signing - not defined yet
Lock State - Unlocked
The guides/fixes I've found so far just seem to be the above steps, to re-flash the stock image from Google, but that just seems to result in me being back to square 1. Does anyone else have any other ideas? Should I try flashing an earlier version of Android from one of the other available images for my device version?

Try to do a factory reset from recovery mode on the device: if you can see the bootanimation its definitely NOT bricked, so don't try any drastic measures just yet.

No idea how the following worked, but it did bring my tablet back from the endless loop.
I just opened its back cover, and applied a light pressure with my fingers on all connectors
Sorry for necroing this thread but I thought someone else might have the same issue!

Bricked my Motorola maxx 2

Hi every body I have bricked my Motorola maxx 2. I'm now stucked in bootloader menu. Recovery is not working. Tried to flash with rsd lite but it's not detecting my phone although it is shown in computer. Also tried fastboot but it says permission denied. What to do now?

Are you sure you installed the right drivers so that rsd lite sees your phone?

Yes I am sure I have installed correct drivers. Device manager recognized my device

How is your device showing in the device manager? Please give a screenshot.

yes i have uploaded it

Luckily rsd lite is now detecting my phone but it doesn't flash it, it says 2/23 flash fail gpt.bin. Where is problem? What to do

Jamil169 said:
Luckily rsd lite is now detecting my phone but it doesn't flash it, it says 2/23 flash fail gpt.bin. Where is problem? What to do
Click to expand...
Click to collapse
what does it say on the device screen?
complete screen details.

my device shows following message
cmd: oem fb_mode_clear
cmd: getvar:max-sparse-size
cmd: oem fb_mode_set
cmd: getvar:max-sparse-size
cmd: getvar:max-download-size
cmd: download:00008000
cmd: flashartition
version downgraded for primary_gpt

some where on the form i read to edit xml file by deleting following lines before flashing. but even this didnt work
<step operation="getvar" var="max-sparse-size"/>
<step operation="oem" var="fb_mode_set"/>
<step operation="oem" var="fb_mode_clear"/>
If im flashing after deleting these lines follwing message comes in device
cmd: getvar:max-sparse-size
cmd: getvar:max-download-size
cmd: flashartition
version downgraded for primary_gpt

Stock firmware which i downloaded contains 2 xml files, which i have attched here.

Jamil169 said:
my device shows following message
cmd: oem fb_mode_clear
cmd: getvar:max-sparse-size
cmd: oem fb_mode_set
cmd: getvar:max-sparse-size
cmd: getvar:max-download-size
cmd: download:00008000
cmd: flashartition
version downgraded for primary_gpt
Click to expand...
Click to collapse
The device should have
AP Fastboot version
battery status
usb connection status...

AP Fastboot Flash Mode (Secure)
BL: 80.A7 (sha-b550fb9, 2015-07-01 09:56:25)
Baseband: M8936_2020632.44.03.21.58R LUX_VZW_CUST
Product/Variant: lux XT1565 16GB P2C
Serial Number: ZY2227ZPHD
CPU: MSM8939
eMMC: 16GB Samsung RV=07 PV=01 TY=57
DRAM: 2048MB Elpida S8 SDRAM DIE=4Gb
Console [NULL]: null
Battery OK
Device is locked. Status Code: 0
Software status: Official
Connect USB Data Cable

And when I connect the USB it says USB connected

Jamil169 said:
And when I connect the USB it says USB connected
Click to expand...
Click to collapse
Your using LUX_5.1.1_LCD23.118-21.2_cid2_subsidy-DEFAULT_CFC.xml.zip ?

No i tried all these three zip files none is working
DroidMaxx2_XT1565_LUX_VERIZON_5.1.1_LCD23.118-21.2_cid2_subsidy-DEFAULT_CFC.xml.zip
LUX_5.1.1_LCD23.118-21.2_cid2_subsidy-DEFAULT_CFC.xml.zip
LUX_RETASIA_DS_5.1.1_LPD23.118-22_cid7_subsidy-DEFAULT_CFC.xml.zip
One thing more before i bricked it i update it marshmallow

Jamil169 said:
No i tried all these three zip files none is working
DroidMaxx2_XT1565_LUX_VERIZON_5.1.1_LCD23.118-21.2_cid2_subsidy-DEFAULT_CFC.xml.zip
LUX_5.1.1_LCD23.118-21.2_cid2_subsidy-DEFAULT_CFC.xml.zip
LUX_RETASIA_DS_5.1.1_LPD23.118-22_cid7_subsidy-DEFAULT_CFC.xml.zip
One thing more before i bricked it i update it marshmallow
Click to expand...
Click to collapse
None of those will work, if device was on 6.0/Marshmallow
you cannot downgrade firmware with a locked bootloader
Nothing to do until till the correct firmware is available

Is there anyway to unlock the bootloader?

Jamil169 said:
Is there anyway to unlock the bootloader?
Click to expand...
Click to collapse
Not that I'm aware of
Sunshine app is likely the best hope
but I don't think the Maxx 2 (XT-1565) is currently supported
and it would require a working device

Ya maxx 2 is not supported. plenty of thanks for help

6.0 firmware needed for RSD or fastboot ... who can help ?

cant flash recovery on B161 bootloader unlocked but also wont lock again!

Hi guys,
I am trying to flash the OEM info as its currently on according to DC unlocker:
Found Phone : VNS-L11
Model : Huawei HiSilicon Kirin Android phone
IMEI : 860921031654789
Firmware : VNS-C900B161
SIM Lock status : unlocked
my phone about device screen displays:
Model: HUAWEI VNS-L31
BUILD : VNS-L31C432B161
EMUI 4.1.1
ANDROID 6.0
I have downgraded to MM B161 thinking this will help and has factory reset my phone during the process but no luck.
I get a boot-loader unlocked warning since i was on nougat, and unable to lock or unlock the boot-loader when i try.
when trying to flash TWRP recovery i get: FAILED (remote: image verification error)
OEM UNLOCK is enabled and so is DEBUGGING
any ideas, really be great to get this fixed finally

Try to download again TWRP the use the command:
fastboot flash recovery twrp.img

Nexus 10 GT-P8110 Will not accept any flash, rom, kernel, radio, stock!

I got a second hand nexus 10, when it boots up it is on cyanogen mod:
kernel 3.4.67-cyanogenmpd-gedbec95 [email protected] #1 mon nov 18 18:16:58 pst 2015
build date mon nov 16 18:04:11 PST 2015
build number: cm_manta-userdebug 5.1.1 LMY48Y 89d47a5074 test-keys
SELINUX Status Enforcing
When I boot the device it runs the rom and has TWRP 3.0.2-0 installed. When I boot into TWRP and select factory reset and even go as far as wiping system the device reboots back to the ROM. When I uninstall apps or try to flash factory roms the device accepts the files such as recovery.img etc but then reboots to the ROM with the apps I removed still there. It is like whatever I try to do to it it always reverts back to the current ROM and always reboots in the same state, even if I have enabled USB debugging, this disappears on reboot.
I have tried to flash recovery, radio, kernels, system etc etc and the device says it takes them but on reboot it always reverts to the ROM. Nothing I do can change anything on this device.
I have tried a different OS, different USB cable, flashing via sideload, bootloader, fastboot. It is always the same.
Any ideas?????

Further to my last, something strange about this device is that I cannot re lock the bootloader. I am begining to think the bootloader is somehow corrupt, but attempts to flash the stock bootloader do not work. Anything I flash says it has been flashed but upon reboot its back to square 1. I have even gone as far as to unmount the system partition in TWRP and delete several critical system files, and again, on reboot they appear again. Any ideas anyone?

nokiaman2002 said:
Further to my last, something strange about this device is that I cannot re lock the bootloader. I am begining to think the bootloader is somehow corrupt, but attempts to flash the stock bootloader do not work. Anything I flash says it has been flashed but upon reboot its back to square 1. I have even gone as far as to unmount the system partition in TWRP and delete several critical system files, and again, on reboot they appear again. Any ideas anyone?
Click to expand...
Click to collapse
To restore to stock i used "Nexus Root Toolkit" i pushed on "Flash Stock + lock" and then u select the image and follow the indications on screen. It is like ADB commands just it has a GUI so maybe it is easyer.

steveyyyy said:
To restore to stock i used "Nexus Root Toolkit" i pushed on "Flash Stock + lock" and then u select the image and follow the indications on screen. It is like ADB commands just it has a GUI so maybe it is easyer.
Click to expand...
Click to collapse
I have tried that, still the same. I do not think there is anything I have not tried! All I want to do is put Kali Nethunter on it. I have even opened up the device to check for water damage and its dry inside. I have even tried a different usb cable, port, operating system.

nokiaman2002 said:
I have tried that, still the same. I do not think there is anything I have not tried! All I want to do is put Kali Nethunter on it. I have even opened up the device to check for water damage and its dry inside. I have even tried a different usb cable, port, operating system.
Click to expand...
Click to collapse
But the device still turns on, what does the bootloader tell? U could use the download mode (powerbutton + volum down). I never used download mode so i can't tell how it works. But on other samsung devices you could send the firmware to the device with "Odin".

steveyyyy said:
But the device still turns on, what does the bootloader tell? U could use the download mode (powerbutton + volum down). I never used download mode so i can't tell how it works. But on other samsung devices you could send the firmware to the device with "Odin".
Click to expand...
Click to collapse
There is no odin download mode on this device just the bootloader which accepts fastboot commands.

nokiaman2002 said:
There is no odin download mode on this device just the bootloader which accepts fastboot commands.
Click to expand...
Click to collapse
The bootloader, if it shows up, what exactly does it tell, does it have some strange behavior like if u push vol up or down it doesn't change text. Maybe retry to flash stock with another PC.

Bootloader looks normal with all the usual options of reboot bootloader, start recovery, and start system. Bootloader state is always UNLOCKED even tho I can try to set it to LOCKED using fastboot. That is what leads me to think the bootloader is corrupt. I have tried another pc, and another usb cable. It is like any command send to it is being ignored but the bootloader is saying OK THATS FINE. I have tried flashing another bootloader and flashing another recovery and flashing boot.img from stock. On reboot it always reverts to TWRP 3.0.2-0 no matter what. I can fastboot reboot a custom recovery or stock and it works, but any commands sent there are dealt with the same way. I may as well buy another from ebay as this thing I have wasted a lot of time on.

fastboot getvar all: Shows bootloader SECURE YES, so the bootloader is secure and will not allow much flashing
(bootloader) product: manta
(bootloader) variant: wifi-only
(bootloader) serialno: R32D1014MET
(bootloader) version-hardware: 8
(bootloader) version-bootloader: MANTAMF01
(bootloader) secure: yes
(bootloader) unlocked: yes
(bootloader) off-mode-charge: enabled(1)
(bootloader) signing: yes
(bootloader) boot partition- type: raw, size: 0x0000000001000000
(bootloader) recovery partition- type: raw, size: 0x0000000001ff0000
(bootloader) metadata partition- type: raw, size: 0x0000000000010000
(bootloader) misc partition- type: raw, size: 0x0000000000400000
(bootloader) cache partition- type: ext4, size: 0x0000000021000000
(bootloader) system partition- type: ext4, size: 0x0000000032000000
(bootloader) userdata partition- type: ext4, size: 0x0000000352c00000

BLOD and cannot enter recovery mode after TWRP or 4 Core img

Hi Guys,
Nexus 6p
BL: angler-03.58
Baseband: angler-03.72
Product: ANGLER-VN2
CPU MSM8994 0x20001
Console: NULL
Battery OK
Device is UNLOCKED
Qfuse status: ENABLED
off-mode-charge: ENABLED
Download mode: DISABLED
I have followed every single thread here and youtube videos and im able to send commands and detect phone through "fastboot"
however i have tried to fastboot
- boot-4Core-bullhead-opm3.171019.013.img
- Oreo4Cores.img
- twrp-3.2.1-0-fbe-4core-angler.img
- twrp-3.3.1-0-angler.img
even after TWRP when I try to access recovery mode it does not run the TWRP, but it bootloop again and again ?
any suggestions

msaithan said:
...Nexus 6p
BL: angler-03.58
Baseband: angler-03.72
Product: ANGLER-VN2
.....
- boot-4Core-bullhead-opm3.171019.013.img
Click to expand...
Click to collapse
I assume according to the entry date of this thread and the missing follow up of your problem, that you by now eventually have figured out where the mistake was made.But by the off-chance that you haven't, did I single the 'keywords' out, by sorting the quote of your OP.
I hope that you didn't brick your phone and could resolve the issue, but realistically do I doubt that. :/