Database Users

Xoom Stuck on red M!

Please help!!! After I was able to unlock my xoom and went reboot just before the adb remount command it just stays on the red M screen. I am able to get Starting RSD Protocol and Starting fastboot protocol at the top left but that is it. Also I have been able to connect with rsd lite but I dont have the sbf file and can't find it on the web anywhere. Please help!
Thanks in Advance

mhobbs82 said:
Please help!!! After I was able to unlock my xoom and went reboot just before the adb remount command it just stays on the red M screen. I am able to get Starting RSD Protocol and Starting fastboot protocol at the top left but that is it. Also I have been able to connect with rsd lite but I dont have the sbf file and can't find it on the web anywhere. Please help!
Thanks in Advance
Click to expand...
Click to collapse
If you are able to boot into Fastboot Protocol, you probably dont need rsd lite. You should be able to flash all of the files in the command prompt. Try re-locking your Xoom to see if that get you out of the soft brick. If it does, you can then try to unlock it again.
You can re-lock your Xoom by typing the following in the command prompt (while booted into fastboot protocol):
Code:
fastboot oem lock
Once you do this, follow the instructions on your Xoom's screen.
If it works, your Xoom should restart back into factory state once it's finished flashing the files.

I got it to lock back now I have Failed image LNX 0x0002 at the top??

Reboot in fastboot mode (power + vol up, after ~2 secs keep pressing vol-down repeadetly, until Fastboot appears; confirm selection with vol-up) and flash stock via fastboot
Code:
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
You may re-unlock your XOOM after successful update, re-root it, etc.

After the first line of code all I get is (cannot load 'system.img'). I really appreciate the help that I have gotten so far!
I now have managed to get it into CWM recovery... I am going to flash the rest of the steps in the universal root method.

Thanks again! I ended up reflashing the rom from CWM recovery and now I am rooted and back running! !!!

Im glad you were able to fix it.

Xoom wifi rooted but OEM locked again without any img files copied
I unlocked using fastboot oem unlock. But was trying to copy CM zip file using adb push. But I was getting stuck at fastboot screen where it says "starting fasboot protocol support" and nothing happens.
So I wiped /data and /cache
it did not help.
so I locked back again (fastboot oem lock). Now I am stuck with the message
Failed to boot LNX 0x0004
starting RSD mode 2
OneWire: Charger is connected....
Battery charge level: 92% (last two lines are irrelevant anyway)
SO I assume now that I dont have any image it wont boot normal. And since its locked I am not even able to get into fastboor or recovery which were installed correctly before.
help pls.
_TB_TB_ said:
Reboot in fastboot mode (power + vol up, after ~2 secs keep pressing vol-down repeadetly, until Fastboot appears; confirm selection with vol-up) and flash stock via fastboot
Code:
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
You may re-unlock your XOOM after successful update, re-root it, etc.
Click to expand...
Click to collapse
---------- Post added at 06:19 PM ---------- Previous post was at 05:54 PM ----------
I ca run fastboot command. fastboot reboot command does reboot the device. But then it comes back to the screen like this:
--> Fastboot
Starting Fastboot protocol support.
with the Red M in middle.
So I cam not able to run adb but can run fastboot commands. Due to this I can not copy the CM and flash using recovery.
I am able to get to recovery screen too by pressing volume down while rebooting.
But when I try adb push to copy the CM zip, it says error: device not found
Pl help. How do I get the CM zip to the device and run it using recovery (using clockwork).
sashykanth said:
I unlocked using fastboot oem unlock. But was trying to copy CM zip file using adb push. But I was getting stuck at fastboot screen where it says "starting fasboot protocol support" and nothing happens.
So I wiped /data and /cache
it did not help.
so I locked back again (fastboot oem lock). Now I am stuck with the message
Failed to boot LNX 0x0004
starting RSD mode 2
OneWire: Charger is connected....
Battery charge level: 92% (last two lines are irrelevant anyway)
SO I assume now that I dont have any image it wont boot normal. And since its locked I am not even able to get into fastboor or recovery which were installed correctly before.
help pls.
Click to expand...
Click to collapse
---------- Post added at 07:13 PM ---------- Previous post was at 06:19 PM ----------
Problem was I was using the wrong recovery image. Did not realize latest one does not work with xoom. Thanks. found the xoom recovery version in this forum.
sashykanth said:
I unlocked using fastboot oem unlock. But was trying to copy CM zip file using adb push. But I was getting stuck at fastboot screen where it says "starting fasboot protocol support" and nothing happens.
So I wiped /data and /cache
it did not help.
so I locked back again (fastboot oem lock). Now I am stuck with the message
Failed to boot LNX 0x0004
starting RSD mode 2
OneWire: Charger is connected....
Battery charge level: 92% (last two lines are irrelevant anyway)
SO I assume now that I dont have any image it wont boot normal. And since its locked I am not even able to get into fastboor or recovery which were installed correctly before.
help pls.
---------- Post added at 06:19 PM ---------- Previous post was at 05:54 PM ----------
I ca run fastboot command. fastboot reboot command does reboot the device. But then it comes back to the screen like this:
--> Fastboot
Starting Fastboot protocol support.
with the Red M in middle.
So I cam not able to run adb but can run fastboot commands. Due to this I can not copy the CM and flash using recovery.
I am able to get to recovery screen too by pressing volume down while rebooting.
But when I try adb push to copy the CM zip, it says error: device not found
Pl help. How do I get the CM zip to the device and run it using recovery (using clockwork).
Click to expand...
Click to collapse

[Q] Data transfer failure ((Too many links) while sending 'system'

PROBLEM SOLVED! I used another pc, my usb ports were the problem! I recently got my Nexus 7 (2012), wi-fi only , I unlocked it's bootloader, installer TWRP recovery, and rooted it. For all these operations i used the N7 toolkit , because back then, I was a noob. The rooted tablet (4.2.2) worked Perfectly! But, after about 3 months, it's "volume down" button stopped working. I rebooted it, but it went in bootloader, instead of normal system. So I just select "Start" and it was in Safe Mode! OK, my "volume down" didn't work in Safe Mode (and bootloader mode) neither! And every time I reboot it, it goes to bootloader! I thought that it was a software problem confused , so I began flashing a new ROM. I didn't want to use the toolkit because everyone says that it's bad . I downloaded AndroidSDK, I re-downloaded the ADB and Fastboot drivers, and I downloaded the newer version of the bootloader (4.23, .img) . Tablet was already in bootloader and I connected it to the PC. In platform-tools folder I ran the "fastboot devices" command, and It was able to see it . So I copied the bootloader img to the same folder, and I ran "fastboot flash bootloader bootloader-grouper-4.23.img" . Then I rebooted it into bootloader again. IT WORKED! But, it didn't solve the "volume down" problem. My rooted 4.2.2 and TWRP were still on the system. Everytime I power off the tablet, and then hold the "Power" button, it goes into bootloader. It was that button issue causing that. Then I decided to take it to the service (same place where I bought iw the unloct) , but I couldn't because if they saked bootloader, non-stock recovery and the root, the wouldn't accept the warranty . I decided to download the latest 4.3 stock android, and stock recovery, flash them, and lock the bootloader. I downloaded 4.3 stock from google's official site, (nakasi-jwr66y) and I used the flash-all.bat command that came with it.
.bat command looks like this:
PATH=%PATH%;"%SYSTEMROOT%\System32"
fastboot oem unlock
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
fastboot flash bootloader bootloader-grouper-4.23.img
fastboot reboot-bootloader
ping -n 10 127.0.0.1 >nul
fastboot -w update image-nakasi-jwr66y.zip
echo Press any key to exit...
pause >nul
exit
I ran it. It successfully did the oem unlock (it was already unlocked) , all the erase commands, and flash bootloader command. But it was stuck on
"fastboot -w update image-nakasi-jwr66y.zip" . It stays steady for about 30secs , and than it says
"sending 'system' (x-kb)"
After some time it just says Data transfer failure(too manly links) ...
I tried the same process billion more times, but same error :/
I tried
-Re-downloading and installing the drivers
-Changing the usb ports, and microUSB cables,
-Restarting the pc (of course)
-Re-downloading the nakasi-jwr66y
-Downloading the twrp recovery (it successfully flashes it)
-Re-downloading the whole SDK
But it DOESN'T WORK? What should I do? Is the volume-down issue hardware or software ?
Sorry for my bad English :////////
P.S. What is the difference between "fastboot flashall" and "fastboot update" ?

Can't unlock oem from fastboot OP2

UPDATE:
The oem was already unlocked so thats why the command did nothing. (I found it by locking and unlocking it again)
Also I had the wrong SuperSU, I first installed CM14 and than installed the right SuperSU
So I was trying to root my OP2 for the second time (apparently it derooted itself for some reason?)
But now I can't unlock oem from fastboot.
I magicly could flash TWRP and from there I installed SuperSU.
But when I booted my device up, it get's bricked into a boot loop.
I got out of the boot loop and tried again.
So I go into fastboot mode and tried the command again:
>fastboot oem unlock
...
OKAY [ 0.020s]
finished. total time: 0.022s
Click to expand...
Click to collapse
PLEASE do not link me to the unbrick guides - the problem is NOT that it's bricked - The problem is that I can't unlock oem from fastboot and so I can't succesfull root my phone.
What works:
+ getting into the OS
+ getting into fastboot
+ flashing a recovery (even if the device is locked?!)
+ booting into recovery
What doesn't work:
- unlocking via fastboot oem unlock

PepRoween said:
So I was trying to root my OP2 for the second time (apparently it derooted itself for some reason?)
But now I can't unlock oem from fastboot.
I magicly could flash TWRP and from there I installed SuperSU.
But when I booted my device up, it get's bricked into a boot loop.
I got out of the boot loop and tried again.
So I go into fastboot mode and tried the command again:
PLEASE do not link me to the unbrick guides - the problem is NOT that it's bricked - The problem is that I can't unlock oem from fastboot and so I can't succesfull root my phone.
What works:
+ getting into the OS
+ getting into fastboot
+ flashing a recovery (even if the device is locked?!)
+ booting into recovery
What doesn't work:
- unlocking via fastboot oem unlock
Click to expand...
Click to collapse
If you can fastboot flash a custom recovery then your device isn't locked.
When you flashed SuperSU, did you use the stock version and force a systemless installation or did you use a modified version that does this automatically?
If you used the stock version and didn't force a systemless installation, this is probably the reason you're bootlooping.

Spannaa said:
If you can fastboot flash a custom recovery then your device isn't locked.
When you flashed SuperSU, did you use the stock version and force a systemless installation or did you use a modified version that does this automatically?
If you used the stock version and didn't force a systemless installation, this is probably the reason you're bootlooping.
Click to expand...
Click to collapse
Thank you for the advice, maybe I can use it another time.

Bootloader question on 906k

Hello,
I have a galaxsy s5 906k and I've been reading on how to unlock the bootloader as I'm trying to install Remix OS and it seems I've come across a lot of misinformation.... and if possible can someone tell me what exactly I need to unlock the bootloader, as I can't find a list of the appropriate tools? Do I need twrp for my specific device?? Some have said yes and some no.
My phone is already rooted.
Also post unlock bootloader question, can I use the 900k rom from remix to install on my 906k?
EDIT**
I can only boot into download mode, not fastboot mode. adb devices returns the device, but fastboot devices returns nothing. Tried adb reboot-bootloader`and it just shows waiting for any device.
These all boot into download/odin mode!!!!!!
adb reboot download
adb reboot bootloader / adb reboot-bootloader
fastboot oem unlock
fastboot flashing unlock
Only one that boots into recovery mode! Then I go to Reboot to bootloader and it comes back to recovery mode!!!!!!!!!!
adb reboot recovery

(Solved) Please!!! XT1680 Bootloader locked: BOOT UP FAILED

To summarize, I have a Moto G5 Plus, with locked bootloader and I decided to update a ROM STOCK and made a simple mistake by forgetting the OEM unlock option in advance in the configuration menu. An error occurred on the way and tried to return to the stock. Now, when the phone boots up, it enters the boot loader (which is locked) and displays a startup error message that states that you must use the Software Repair Wizard.
trying to enter the recovery gives a code:
AP Fastboot Flash Mode [Secure]
Fastboot Reason: UTAG "bootmode" configured as fastboot
failed to validate boot image
ERROR: Failed to pass validation, backup to fastboot
Boot up failed
Is there a known solution or force a recovery to work?
Thanks to all

Hello;
I found the solution, download the latest firmware from your cell phone, download it just unzip the zip and look for the files: gpt.bin and bootloader.img, those 2 ctrl + c and files go to the folder where they downloaded ADB tools and paste the files there , then execute the steps to open command window here and execute the following:
fastboot flash partitiongpt.bin
fastboot bootloader bootloader.img
fastboot reboot-bootloader
and it is ready to install the downloaded rom.
Gracias a AndresBRS https://www.clangsm.com/forum/index.php?showtopic=466891

Same problem with moto g5s plus xt1804
After flashing it shows failed to start ..failed to boot recovery and when I am trying to unlock bootloader it shows unlock data unavailable

beyondsunshine92 said:
After flashing it shows failed to start ..failed to boot recovery and when I am trying to unlock bootloader it shows unlock data unavailable
Click to expand...
Click to collapse
Install lenovo moto smart assistant in pc and go for rescue and flash the whole firmware.if your device is not supported then flash manually.

Moto smart assistant shows device not supported however I tried many fastboot stock roms but every time I get error invalid signed image. .ph stuck in fastboot

beyondsunshine92 said:
Moto smart assistant shows device not supported however I tried many fastboot stock roms but every time I get error invalid signed image. .ph stuck in fastboot
Click to expand...
Click to collapse
Download the firmware from here and then flash.
https://mirrors.lolinet.com/firmware/moto/potter/official/

riyan65 said:
Download the firmware from here and then flash.
@beyondsunshine92: Did you tried this? Is it working? I am also having the same issue. Please help guys
Click to expand...
Click to collapse