Hi
I have been having this issue with my Xoom for quite some time after I tried to reset it back to stock and followed the instructions I found at a thread which I have lost, but included the instruction to lock the bootloader, which I have since learned is not advisable, and have not been able to fix it after many Google searches for solutions.
Each time I turn my Xoom on it comes up with this message:
{
"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"
}
So far I have tried solutions from these forum threads:
Failed to boot LNX 0x0004 Startinmg RSD mode 2 Xoom WIFI ONLY MZ604
Failed to boot LNX 0x0004 Startinmg RSD mode 2 Xoom WIFI ONLY MZ604
(Xoom WiFi Only MZ604) failed to boot lnx 0x0004 - starting rsd mode 2
Stuck at Motorola Dual-Core? [Wifi-Only]
Every time I get stuck at the same place: <waiting for device> on my command prompt, while my Xoom sits on this screen:
I have set up fastboot and adb on my pc using the tool I found on this thread:
[TOOL] [WINDOWS] ADB, Fastboot and Drivers - 15 seconds ADB Installer v1.4.2
My Xoom is a wi-fi only EU model (wingray), I do not have the original USB cable that it came with though I do not think that makes a difference. I am at a loss as to how to fix this problem.
Is there anyone with an up to date solution for this issue? Thanks.
what happens when you type "adb devices" ?
the commands for flashing the stock image are as follows (i have a copy, if you need it PM me)
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
fastboot oem lock
Fixed!
Thanks for replying
After you questioned what happened when I typed 'adb devices' I had the very belated brainwave of maybe checking that it was correctly set up with one of my other devices (duh! ><). Thus it was I discovered that despite the installer I had used assuring me that it was correctly set up, I found that it wasn't actually correctly set up.
With my Nexus 7 as a test device, and the WugFresh Nexus Toolkit at my disposal I was able to set up ADB so that it worked with my N7. Plugging in my Xoom I found that it was still invisible to my computer, so I Googled for Motorola USB drivers and came up with the Motorola Device Manager which installed it's own ADB driver. Once that does done I was pleased to find that my PC was now able to see my Xoom and I have flashed the stock images I got from the Motorola website and my Xoom has now been fixed!
Thanks for your help and inspiration
That's great news! Enjoy your resurected Xoom
Related
Hello everybody
Well, I have his issue. I tried to flash some new roms into the OPO yesterday and I had some issues with one, so I decided to flash other one, but when I wiped the things I also wiped the internal storage and I didnt know that that would erase my OS, now i'm trying to flash a rom but it wont let me with the bootloader because it says its locked, and if i try to unlock it using OPO toolking via ADB sideload the phone shows it requires ADB 1.0.32 which is the same that i have installed on my computer and if I try it using the bootloader option it just restarts and it keeps being locked. If I try to send a rom with the CMD on my pc it says "error: closed"
I have done some research and found some similar cases but not simiilar enough to have the same fixes
I have windows 10 and TWRP is 2.8.7.0
If anybody helps me that would be pretty useful
Thanks!
minor9719 said:
Hello everybody
Well, I have his issue. I tried to flash some new roms into the OPO yesterday and I had some issues with one, so I decided to flash other one, but when I wiped the things I also wiped the internal storage and I didnt know that that would erase my OS, now i'm trying to flash a rom but it wont let me with the bootloader because it says its locked, and if i try to unlock it using OPO toolking via ADB sideload the phone shows it requires ADB 1.0.32 which is the same that i have installed on my computer and if I try it using the bootloader option it just restarts and it keeps being locked. If I try to send a rom with the CMD on my pc it says "error: closed"
I have done some research and found some similar cases but not simiilar enough to have the same fixes
I have windows 10 and TWRP is 2.8.7.0
If anybody helps me that would be pretty useful
Thanks!
Click to expand...
Click to collapse
SOLUTIONS THAT MIGHT WORK
1) Use Fastboot instead of Sideload
Cmd
Go to Fastboot folder with CD
Boot into Fastboot , then type fastboot devices.
If you see the Oneplus One, then just download a random ROM and FLASH the ZIP
2) [Toolkit] Wug's Bacon Root Toolkit v1.0.3 [Updated 04/16/15] by WugFresh ---> LINK
Screenshots 1
{
"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"
}
Screenshot 2
3) [GUIDE] How to unbrick or make your phone 100% stock by vigneshvar1
This installing Android CM11s but you can afther that installing a other rom of your choise. --> LINK
Hello guys, last week I installed the unofficial port of MM from here http://forum.xda-developers.com/shield-tablet/general/unofficial-update-original-shield-t3281541 and everything was going well until yesterday the screen got frozen. I tried to reboot the tablet but It got frozen in the nvidia boot logo, so I tried to reinstall the ROM through fastboot. This step is when I realized that I cant write sometimes through fastboot. I can go into this mode but sometimes the writing failed until now everytime it fail. This is the error reported on the screen:
writing 'boot' ...
FAILED (remote: (FileWriteFailed)
This is a screen capture of the command window:
{
"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 think that I have broken the bootloader but I cant find the bootloader img for the tablet. Any help will be thanked!
If fastboot is working you still have a working bootloader. You are in fact in the bootloader. I'm not sure why fastboot write would fail. Perhaps the Windows fastboot driver should be reinstalled.
The bootloader is flashed by a "blob" file and is included with restoration images. If the bootloader does get damaged somehow, you can only boot to APX mode and only Nvidia can repair that.
Try do download and use minimal ADB.
Also reinstall the fastboot driver on your PC (deleting tablet from control panel/system/.... and connecting it again and istall again the driver you download from nvidia site or here on XDA)
best thing you can do if fastboot commadn don't work (happen to me) is download a recovery imagere (again nvidia developer site or here on XDA) and use the flashall.bat.
Magic done for me
and u can use it when u have only Apx? .... i cant find driver for it ... i have only black screen alltime
helllo ..! but still the above case wil work for the deactivated shield's..? my sheilds are now in apx mode..
Sent from my SHIELD Tablet using xda premium
If you can only boot APX mode you are stuck. There's no driver for APX mode so you can't do anything with it. Only NVidia can repair it at that point.
I don't know if this may be important but two days before this happened I encrypted the tablet. this may be affect the bootloader? The tablet is still unusable since I can't flash anything thought fastboot starts.
I purchased a nice Willeyfox Swift in very good condition with Android 7.1.2. , wanted to install LineageOS + MicroG via ADB.
OEM unlock and USB Debugging Mode enabled, drivers installed, the device was perfectly recognized, bootloader unlocked ("DEVICE STATE- unlocked"),
but then problems started:
When I wanted to flash TWRP via platform-tools, „< waiting for any device >“ appeared. This happened using Windows 10 as well as Mac OS (so I guess, drivers aren’t the problem).
TWRP -package is: „twrp-3.5.0_9-0-crackling,img“
{
"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"
}
Has anyone any idea?
Thanks for help!
ADB and Fastboot are 2 completely different softwares: ADB deals with device's Android OS whereas Fastboot deals with device's bootloader.
To successfully run Fastboot commands you have to establish a Fastboot connection as 1st thing of all things:
Code:
adb devices
adb reboot bootloader
fastboot devices
jwoegerbauer said:
ADB and Fastboot are 2 completely different softwares: ADB deals with device's Android OS whereas Fastboot deals with device's bootloader.
To successfully run Fastboot commands you have to establish a Fastboot connection as 1st thing of all things:
Code:
adb devices
adb reboot bootloader
fastboot devices
Click to expand...
Click to collapse
Thanks a lot - I skipped "adb reboot bootloader"
Now it works.
Just with a problem often posted along with Wileyfox:
After successfully having installed TWRP, the device only reboots into bootloader, not to system.
But I'll follow this problem on other threads (or do you have an answer?)
finally, I managed it: Thanks to wowi63 , I first intalled Cyanogen, before installing lineageOS. Thank you again for reminding me not to forget <adb reboot bootloader> (I did it before with another device, even had it on my list of procedures, but was just to blind to see...)
I'd like to close this thread
jwoegerbauer said:
ADB and Fastboot are 2 completely different softwares: ADB deals with device's Android OS whereas Fastboot deals with device's bootloader.
To successfully run Fastboot commands you have to establish a Fastboot connection as 1st thing of all things:
Code:
adb devices
adb reboot bootloader
fastboot devices
Click to expand...
Click to collapse
I logged into XDA just to thank you very much!
Cant belive I failed something so elementary.
Finally after 2 days I am able to fix my device.
Thanks.
my zenfone 4 problem:
it is charging but i am stuck at asus logo with rotating circle and whenever i am trying to get into droid boot it is showing an android with yellow helmet
{
"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"
}
As long as a phone powers on it's NOT hardbricked, but softbricked if Android doesn't get properly started.
even if it is soft bricked i am not able to get into recovery mode this was showing:
Re-flash phone's STOCK ROM.
damn, i am not able to get into fastboot dude that's what it is all about if i would be able to get into fastboot i would have flashed my phone long time ago.when i ty to get into fastboot android sign with yellow helmet appears.
My zenfone 4 problems:
access to droidboot or recovery (stuck at android icon with a yellow helmet), so i cant flash a rom or firmware.
Tried different combo keys, but always stuck with that android icon.
You typically re-flash a STOCK ROM by means of ADB Sideload method.
ook so for using adb sideload method u need to get into droid boot what i am saying it i am not able to get into droid boot mode and everytime i try an android sign with yellow helmet appears.
You are absolutely WRONG.
What you have to do is running ADB commands as follow
Code:
adb devices
adb reboot sideload
adb sideload <FULL_PATH_TO_STOCK_ROM_ZIP_FILE_ON_PC_HERE>
i am noob please can u tell me the steps elaborately OKAY,
NOW I HAVE GOT IT BUT IS NOT SOWING ANY DEVIICES I HAVE CONNECTED MY MOBILE SEE:
Then you obviously never have enabled USB Debugging on phone what is prerequisite to run ADB commands.
jwoegerbauer said:
Then you obviously never have enabled USB Debugging on phone what is prerequisite to run ADB comso
Click to expand...
Click to collapse
so,now what should i do?
Was trying to flash my CN ROM to the WW ROM.
Forgot to turn on USB Debugging in Developer Tools.
Couldn't get it work using HunterTik's guide.
Ran flashall_ATF from windows explorer.
Command prompt flashed on screen then vanished.
Tried running flashall_ATF in an elevated command prompt.
It failed but has apparently wiped the ROM. Device is now stuck in boot loop to fastboot.
Whatever option I choose reboots the device back to fastboot.
Windows can see the device but adb devices returns List of Devices Attached is blank.
How do I recover the phone from here?
Found this thread Rog phone 5 stucked on fastboot
Ran this command: fastboot -v flash all WW_ZS673KS_18.0830.2101.75_M2.13.24.14.1-ASUS_1.1.63_Phone-user.raw
Received these lines of text & now device boots to splash screen, gets stuck there, reboots a few times then sends me back to fastboot.
Still can't access recovery mode
{
"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 is now back in a fastboot loop with no access to any options but power off & restart.
Your phone is broken
Buy a new phone and don't try to mess with it next time
Flash back to CN and try again.
or, get a dump of the official firmware, then sent boot / recovery / super over fastboot manually.
[Windows] Asus OTA payload auto extractor
Since nobody is doing it, I thought I'd package it and just put it here to help people This is a packaged version of Vm03's payload dumper make to work with windows without installing python and other stuff I also included a single line script...
forum.xda-developers.com
also, you might want to try 9008 rescue. it seems like whatever you're trying to do wiped / repart the partitions. that's why the BL is confused.
also, if you're on win11, some driver related **** can mess things up causing flashing fail.
yurishouse said:
also, you might want to try 9008 rescue. it seems like whatever you're trying to do wiped / repart the partitions. that's why the BL is confused.
also, if you're on win11, some driver related **** can mess things up causing flashing fail.
Click to expand...
Click to collapse
9008 rescue is the direction I was headed & you're right. Although, on reflection, the partitions were already deleted prior to running the 'fastboot -v flash all xx.raw' command. Not sure how, since that command was the only thing I did which resulted in something happening.