Database Info

[Q] Xoom stuck on boot screen

The other day my WiFi Xoom stopped getting past the "Motorola Dual Core" screen.
I have removed the SD card.
Android recovery mode gives me the error android with the "!"
It does this plugged in or on battery.
Not rooted.
What else should I try?

neoka said:
The other day my WiFi Xoom stopped getting past the "Motorola Dual Core" screen.
I have removed the SD card.
Android recovery mode gives me the error android with the "!"
It does this plugged in or on battery.
Not rooted.
What else should I try?
Click to expand...
Click to collapse
What were you trying to do before this hapened? Need more info to be able to help.

24348542 26
DavilaDarkness said:
What were you trying to do before this hapened? Need more info to be able to help.
Click to expand...
Click to collapse
Hadn't really done anything. Just normal use. No out of the ordinary installs. Turned it off. Next day I tried turning it on and it won't boot.

Did you ever resolve this ?? I was give one to repair for a child and it too is stuck on the red boot screen. The good thing is the person who sold it to them was a hacker and put TWRP on it of all things. I was floored when I tried to enter recovery and found teamwin.
but the problem is its still stuck on the boot screen, i did flash it 3-4 times with M604 M602 flashes and some other customs but nothing works, it completes flashing and wiping caches but always goes back to stuck on boot screen..
perhaps I have to unclock the bootloader or something for the flash to be succesfull ?

Just wanted to say I fixed it with these commands and firmware if anyone is interested. I tried everything else including flashing with twrp and wiping all caches and it didn't work, getting the stock firmware and doing it like this worked to clear boot screen endless stuck
download fastboot and adb and xoom drivers 6.4 (about 5mb) and the appropriate stock firmware. for me it was ZM604
at the command type
adb reboot bootloader
you may need to unplug and replug cable after it goes in fastboot mode.
fastboot devices
.. should return something "02a439cj0skjdke fastboot" to proceed.
fastboot oem unlock
.. look at your tablet and follow the instructions, for me it was down twice and up once to accept unlock conditions, then it reboots
on reboot press vol down 2 seconds after you see moto logo, it will enter fastboot
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
fastboot erase userdata
fastboot reboot
no need to relock after, you will see android logo and first boot pop up after 2-3 mins

Pixel 2 Recovery Not Working

Hello, I tried resetting my phone and flashing the latest Verizon pixel factory image by using the flash-all.bat file that comes with
"walleye-opd3.170816.012-factory-9626515d"
The bootloader fails to enter recovery mode, cycling back to the bootloader menu. The same thing occurs when I attempt to power on the device from "Start". The bootloader is also unlocked.
Put simply, the device isn't recognized via adb, but it's accessible through fastboot. I can't execute "fastboot boot x.img" because it keeps saying it can't authenticate the image.

Update your adb/fastboot. Only the latest adb works for the Pixel 2.

tina v. said:
Hello, I tried resetting my phone and flashing the latest Verizon pixel factory image by using the flash-all.bat file that comes with
"walleye-opd3.170816.012-factory-9626515d"
The bootloader fails to enter recovery mode, cycling back to the bootloader menu. The same thing occurs when I attempt to power on the device from "Start". The bootloader is also unlocked.
Put simply, the device isn't recognized via adb, but it's accessible through fastboot. I can't execute "fastboot boot x.img" because it keeps saying it can't authenticate the image.
Click to expand...
Click to collapse
You are not the only one. I have the same issue with taimen-opd1.170816.010-factory-c796ddb4.zip while using fastboot boot. I have a bricked phone that which isn't covered under the replacement warranty.

Have you both updated your adb drivers?
Because I had the same.
After updating adb I could flash the image without any problem.

I need help [noob]

I tried to flash stock kdz with LG Flash Tool 2 days ago and process was stopped in the middle of flashing so I had to exit program and to pull my battery off. And then when I tried to turn phone on again it wouldn't boot but it showed only something about fastboot and when I'm trying to flash something with it I get unknown error.
This is what it says on screen:
fastboot int()
loading keystore failed status 5
Usb init ept @ 0x....
udc_start()
--reset---
--portchange---
fastboot: processing commands
Phone wasn't rooted and bootloader was locked, I can't access download mode anymore, neither anything else cause no matter what combination of keys I use it only boot into this.
So what are my options for this?

Phone is Cycling between Bootloader Unlocked Screen and Motorola Sp

I just tried rooting my phone. The phone is cycling back and forth between the bootloader is unlocked screen and the Motorola splash screen.
To repeat some steps from a prior post.
My phone had QPR30.80-58-3 .
I downloaded that ROM and extracted the boot.img file.
I downloaded the latest Magisk Manager and installed it on my phone.
I ran through the patching process for boot.img.
I requested an unlock code from Motorola and unlocked the bootloader.
I flashed the patched boot image which patched partition b.
I flashed the patched boot image to partition a.
I rebooted which began the cycle.
I tried holding down the power button but it returns to the cycle.
I can get back to the bootloader with the Volume Down and Power buttons.
Any suggestions on what could get me back to a functioning phone, rooted or not rooted?

I would confirm the version of the boot image you flashed matches the version of the installed rom. You could also try to flash the unpatched / original boot.img to see if that gets you booting again.

dafunk60 said:
I would confirm the version of the boot image you flashed matches the version of the installed rom. You could also try to flash the unpatched / original boot.img to see if that gets you booting again.
Click to expand...
Click to collapse
I checked that the image I patched was from the QPR30.80-58-3 ROM which matched the level after the phone was updated.
I flashed that original boot image which flashed partition a and then rebooted. I did not flash partition b.
It first came up with the unlock warning screen. It sat on the Motorola splash screen for a noticeable amount of time followed by a yellow screen with a circle around the Motorola symbol. Finally it ended up on a blue Hello there screen with a yellow start button.
This screen was unresponsive. Eventually through various cyclings through all this I ended up on a screen that said Android could not boot and gave me an option of a factory reset. I did that but it did not help getting past the Hi there screen.
I went back and flashed the QPR30.80_58 image on both partitions a and b. This got me back to setting up the phone again. The phone is at QPR30.80_58. I am considering just rooting at this level.

So I tried patching the original QPR30.80_58 boot image. I did notice that it appeared the phone had automatically staged the QPRS30.80_58_3 update. I proceeded in (false) hopes that I could stop that.
It flashed the b partition. Ended up stuck in the bootloader unlock loop. I flashed the a partition but no change.
Previously I had ended up on a recovery screen automatically after some time. I could not force this to happen.
I tried flashing the original unpatched boot image but would end up on a non-functioning Hello there screen.
I tried adb recovery and adb shell but came back with device unauthorized.
I tried following some instructions on using fastboot erase userdata and fastboot erase cache. No change.
I finally found out that the Recovery menu was option off the bootloader screen. However, that came up with No command.
Lenovo Rescue did not want to recognize my XT2043-4 device.
I flashed the unpatched retail QPRS30.80_58_3 boot image to both a and b partitions. That got me back to a functioning phone. After getting through the login and setup steps I did find that it was at QPRS30.80_58_3.
Out of curiosity, I tried Lenovo Rescue again. I received a "Failed to match connected device. Reconnect device, then try again." which did not work.
Now I am at a loss.

DougPeterson said:
So I tried patching the original QPR30.80_58 boot image. I did notice that it appeared the phone had automatically staged the QPRS30.80_58_3 update. I proceeded in (false) hopes that I could stop that.
It flashed the b partition. Ended up stuck in the bootloader unlock loop. I flashed the a partition but no change.
Previously I had ended up on a recovery screen automatically after some time. I could not force this to happen.
I tried flashing the original unpatched boot image but would end up on a non-functioning Hello there screen.
I tried adb recovery and adb shell but came back with device unauthorized.
I tried following some instructions on using fastboot erase userdata and fastboot erase cache. No change.
I finally found out that the Recovery menu was option off the bootloader screen. However, that came up with No command.
Lenovo Rescue did not want to recognize my XT2043-4 device.
I flashed the unpatched retail QPRS30.80_58_3 boot image to both a and b partitions. That got me back to a functioning phone. After getting through the login and setup steps I did find that it was at QPRS30.80_58_3.
Out of curiosity, I tried Lenovo Rescue again. I received a "Failed to match connected device. Reconnect device, then try again." which did not work.
Now I am at a loss.
Click to expand...
Click to collapse
Happy to hear you have a working phone again! The lack of touchscreen response & the stuck at the hello screen issues are what others have reported when they used a boot image from a different version than on the phone. I suspect that something got confused between the version & slot somewhere along the way. As far as the Lenovo Rescue software not seeing the phone, it's communicating via ADB. If I recall correctly I needed to reauthorize the PC to connect via ADB after updating from 30.80-58 to 30.80-58-3. When I connect the phone via USB there's a popup on the phone asking to authorize the PC. Can you connect via ADB in the command line? If yes, you may want to reinstall the Lenovo software. If no, I would troubleshoot the ADB connection.
I originally rooted the 30.80-58 version. When 30.80-58-3 was released all I did was flash the unpatched boot.img, took the update OTA, let it reboot, then flash a patched boot.img from 30.80-58-3. All worked as expected, user data was intact.

dafunk60 said:
Happy to hear you have a working phone again! The lack of touchscreen response & the stuck at the hello screen issues are what others have reported when they used a boot image from a different version than on the phone. I suspect that something got confused between the version & slot somewhere along the way. As far as the Lenovo Rescue software not seeing the phone, it's communicating via ADB. If I recall correctly I needed to reauthorize the PC to connect via ADB after updating from 30.80-58 to 30.80-58-3. When I connect the phone via USB there's a popup on the phone asking to authorize the PC. Can you connect via ADB in the command line? If yes, you may want to reinstall the Lenovo software. If no, I would troubleshoot the ADB connection.
I originally rooted the 30.80-58 version. When 30.80-58-3 was released all I did was flash the unpatched boot.img, took the update OTA, let it reboot, then flash a patched boot.img from 30.80-58-3. All worked as expected, user data was intact.
Click to expand...
Click to collapse
I double checked that I had USB debugging set, given I have reset a couple of times. I revoked all USB access and reinstalled the Rescue app. I still get the Failed to match connected devices error.
fastboot device will list the phone.
adb devices or adb devices -l does not list anything and adb shell says no devices/emulators found.
If I try to get into recovery mode I get a No command screen. I have been trying to take notes on what I did but there have been gaps in all the fiddling. I may have only flashed one partition the last time I tried putting back a stock boot image.
For USB drivers I downloaded the latest from Motorola. Was that sufficient for this?

DougPeterson said:
I double checked that I had USB debugging set, given I have reset a couple of times. I revoked all USB access and reinstalled the Rescue app. I still get the Failed to match connected devices error.
fastboot device will list the phone.
adb devices or adb devices -l does not list anything and adb shell says no devices/emulators found.
If I try to get into recovery mode I get a No command screen. I have been trying to take notes on what I did but there have been gaps in all the fiddling. I may have only flashed one partition the last time I tried putting back a stock boot image.
For USB drivers I downloaded the latest from Motorola. Was that sufficient for this?
Click to expand...
Click to collapse
If you want to get into recovery, boot into the bootloader than do
Code:
fastboot reboot fastboot
That'll boot you into fastbootd which has an option to go to the real recovery

DougPeterson said:
I double checked that I had USB debugging set, given I have reset a couple of times. I revoked all USB access and reinstalled the Rescue app. I still get the Failed to match connected devices error.
fastboot device will list the phone.
adb devices or adb devices -l does not list anything and adb shell says no devices/emulators found.
If I try to get into recovery mode I get a No command screen. I have been trying to take notes on what I did but there have been gaps in all the fiddling. I may have only flashed one partition the last time I tried putting back a stock boot image.
For USB drivers I downloaded the latest from Motorola. Was that sufficient for this?
Click to expand...
Click to collapse
If adb isn't showing any devices connected that would explain why the rescue software cannot find your phone. Perhaps you don't have the correct driver installed. Windows Device Manager shows the phone as a Motorola ADB Device on my PC.
View attachment 5061327
Another possibility is that you have multiple versions of adb on your PC. Older versions won't work but the adb.exe in "C:\Program Files (x86)\Rescue and Smart Assistant" works for sure. With your phone booted into android & unlocked, plug it into your PC. Do you see the "USB debugging connected" on the phone? If you don't I would re-check that USB debugging is enabled. If you do see the debugging notification, on your PC, open a command prompt and navigate to "C:\Program Files (x86)\Rescue and Smart Assistant". Run
Code:
adb devices
Does adb find your phone?

stuck at bootloader , No OS No Recovery :(

hi my oneplus 7 pro 1910 stuck at bootloader and when i press start or recovery it gets back to the bootloader screen i cant even turn off the phone
i accidentally wiped all partitions in twrp and made a format .
anyhelp ? ive tried to do the fastboot rom flash but my pc doesnt detect my phone
i tried almost every solution i found but nothing works

Your bootloader needs to be unlocked to use a fastboot ROM.
Is it unlocked?

@soka said:
Your bootloader needs to be unlocked to use a fastboot ROM.
Is it unlocked?
Click to expand...
Click to collapse
Yes it’s unlocked , any help

Search on the fast boot rom thread for the fast boot rom version you were last on, i have used this many times and it worked.
One thing to note, after it flashed everything , I ended up in crash dump error. I went into stock recovery and wiped/formatted my device and it boot up great.

https://forum.xda-developers.com/t/msm-tool-guac-for-all.3934691/ - just follow this guide

One thing that worked for me is when your phone is plugged into your pc open a command prompt and type fastboot boot twrp-*.img (make sure it is the .img not .zip), and from there download the twrp installer .zip and flash that, reboot to recovery, and install the OTA for your device (OTAs can be found at this thread).
If it fails to boot and gives you an error, try fastboot getvar all to see which slot is currently active then do fastboot --set-active=*inactive slot letter* then fastboot --set-active=*original active slot letter* then try to boot to the twrp .img from fastboot again. If fastboot doesn't detect your device at all, try seeing if adb devices outputs anything, and if it does type adb reboot bootloader