Hi everyone, i have a Xoom 2 ME bricked and starts only fastboot mode. I´ve tried to restore with RSD Lite, but the "boot_signed" file gives a error, "preflash validation failed". I´ve also tried to restore it with the commands directly and all files gives ok least "boot_signed" (Only fastboot european roms).
Is it possible flash fake_cid file through the fastboot? I´ve tried and it gives me a error, "command restricted" and with allow-mbmloader-flashing-mbm.bin dont work.
Master-DJ said:
Hi everyone, i have a Xoom 2 ME bricked and starts only fastboot mode. I´ve tried to restore with RSD Lite, but the "boot_signed" file gives a error, "preflash validation failed". I´ve also tried to restore it with the commands directly and all files gives ok least "boot_signed" (Only fastboot european roms).
Is it possible flash fake_cid file through the fastboot? I´ve tried and it gives me a error, "command restricted" and with allow-mbmloader-flashing-mbm.bin dont work.
Click to expand...
Click to collapse
I just brought mine back to life with the instructions here:
http://forum.xda-developers.com/showthread.php?t=1485741&page=78
I used adb and fast boot from Google's SDK but it took some messing about to get adb to see the Xoom.
Related
Hi, So I am trying to restore to factory firmware (Telus/Koodo) firmware and I keep getting this error:
Code:
error: cannot load 'system.img_sparsechunk.1 ': No Error
I get the error for all the sparsechunks. I'm not sure what to do. If this is any help My phone is unlocked status code 3. However, it is stuck in bootloop.
Thanks!
Canuckfan101 said:
Hi, So I am trying to restore to factory firmware (Telus/Koodo) firmware and I keep getting this error:
Code:
error: cannot load 'system.img_sparsechunk.1 ': No Error
I get the error for all the sparsechunks. I'm not sure what to do. If this is any help My phone is unlocked status code 3. However, it is stuck in bootloop.
Click to expand...
Click to collapse
What are the actual files you have downloaded called? It could be: system.img_sparsechunk1 - also flash them in order, system.img_sparsechunk0, system.img_sparsechunk1, system.img_sparsechunk2
Hi! Thanks for the reply! I checked the name and I did not enter it in correctly! It now works! But antoher problem has occured! I managed to lock the device ( i ended the program with fastboot oem lock) and the moto g said locked! in blue. I thought it got stuck so i pressed the power button. The warning unlocked bootloader still shows but the phone is Locked Status 2. The CMD prompt gave me this when I entered fastboot oem lock
Code:
...
FAILED (status read failed (too many links))
There are already numerous threads on the subject of 'fastboot oem lock failed' - I don't know why it fails.
This is one alternative solution:
http://forum.xda-developers.com/showthread.php?t=2548530
Hey Guys,
I rooted my device a while ago and everyday had to dismiss the OTA update for the last few months. The other night I accidentally accepted the OTA and know my phone is stuck in a bootloop when connected to power. I'm occasionally able to get into Fastboot mode for RSD to see the phone, ADB will not see the phone. When I attempt to select Recovery or Factory the phone bootloops. I have also tried House of Moto and that didn't work.I have tried flashing all the files located at sbf with no luck. In Fastboot the Device is listed as UNLOCKED with a Status Code: 1.
Any help will be greatly appreciated.
When I flash using House of Moto I get an error for the following:
gpt.bin
motoboot.img
logo.bin
boot.img
recovery.img
system.img
NON-HLOS.bin
uniqueflips said:
Hey Guys,
I rooted my device a while ago and everyday had to dismiss the OTA update for the last few months. The other night I accidentally accepted the OTA and know my phone is stuck in a bootloop when connected to power. I'm occasionally able to get into Fastboot mode for RSD to see the phone, ADB will not see the phone. When I attempt to select Recovery or Factory the phone bootloops. I have also tried House of Moto and that didn't work.I have tried flashing all the files located at sbf with no luck. In Fastboot the Device is listed as UNLOCKED with a Status Code: 1.
Any help will be greatly appreciated.
When I flash using House of Moto I get an error for the following:
gpt.bin
motoboot.img
logo.bin
boot.img
recovery.img
system.img
NON-HLOS.bin
Click to expand...
Click to collapse
Does it ever actually boot up and then just restarts? Or are you never getting to the homescreen?
no home screen
Hi,
It won't even boot loop unless it's connected to power. When it is it just boot loops, tried everything but can't get past the boot loop. Spent countless hours trying to make any progress.
try flashing TWRP from fastboot
Code:
fastboot erase recovery
fastboot flash recovery name.img
if you get into recovery try restoring a nandroid
if that doesnt work, make sure you are flashing the appropriate SBF from the update you were in teh process of taking. My bet is somehow your device got partially updated (bootloader) so you are now unable to flash the SBF you were prevously on. ie. you were on 4.2.2, and took the 4.4 update, you need to flash the SBF for 4.4, not 4.2.2
Once you get back up and running, make sure you disable the Moto OTA app using titanium or the like. That should prevent the phone from trying to take an update again.
Still no luck
Thanks everyone for the suggestions, I'm not sure which firmware it was trying to install so I installed all the firmwares available via House of Moto and still no luck. Tried performing a Full and Keep Data and still the phone will continue to boot loop. One thing I did notice during the install using House of Moto I see the following error multiple times:
(bootloader) Variable not supported!
I got this error on all 5 firmwares.
Any ideas...
uniqueflips said:
Thanks everyone for the suggestions, I'm not sure which firmware it was trying to install so I installed all the firmwares available via House of Moto and still no luck. Tried performing a Full and Keep Data and still the phone will continue to boot loop. One thing I did notice during the install using House of Moto I see the following error multiple times:
(bootloader) Variable not supported!
I got this error on all 5 firmwares.
Any ideas...
Click to expand...
Click to collapse
what version of android were you on prior to this happening. What version was the OTA attempting to update you to?
I think I was on Android 4.4 Blur_Version.19.5.3.obake_verizon.Verizon.en.US, not 100% sure what it was trying to install 4.4.4 or 4.4 19.6.3.
Tried House of Moto again and on the 4.2.2 12.15.15 and 4.4.4 I don't get the (bootloader) Variable not supported! error. The phone still boot loops.
uniqueflips said:
I think I was on Android 4.4 Blur_Version.19.5.3.obake_verizon.Verizon.en.US, not 100% sure what it was trying to install 4.4.4 or 4.4 19.6.3.
Tried House of Moto again and on the 4.2.2 12.15.15 and 4.4.4 I don't get the (bootloader) Variable not supported! error. The phone still boot loops.
Click to expand...
Click to collapse
have you tried with the latest version of RSD lite?
If so make sure you edit the XML file to remove the part about erasing userdata
lets try this too... go to sbf.droid-developers.org and download this file for the maxx "Android 4.4.4
Blur_Version.21.11.21.obake_verizon.Verizon.en.US"
Install the latest moto device manager and RSD lite, then try flashing (might erase userdata)
If that does not work, you can manually flash each file in fastboot, lmk if any of that works
last Q, do you have a motorola factory cable?
Tried with and without removing the getvar file and no luck, still stuck in an endless boot loop when connected to power. ADB still doesn't see the device even in Fastboot mode. Never flashed each file in fastboot individual doesn't that require ADB?
uniqueflips said:
Tried with and without removing the getvar file and no luck, still stuck in an endless boot loop when connected to power. ADB still doesn't see the device even in Fastboot mode. Never flashed each file in fastboot individual doesn't that require ADB?
Click to expand...
Click to collapse
no you dont use adb from fastboot, you use "fastboot"
Lets see if we can get you booted to a recovery. Download this file, save it as recovery.img in your ADB directory.
boot to fastboot and run this command to determine fastboot sees the device
Code:
fastboot devices
If you see your device, then run the next command
Code:
fastboot flash recovery recovery.img
then try to boot to recovery. post result (make sure when you highlight "recovery" in fastboot you use volume up to select it. I just made the mistake of using power and my phone wouldnt boot to recovery)
Hello,
I was facing a lot of issues with my YUPHORIA. So, I tried to flash it using the official instructions on official forum using Fastboot.
The flashing got stuck when it was trying to flash the "system" partition. I disconnected the cable and tried the flashing process again.
Now, I am able to flash everything else except "system"
It is giving an error -
"FAILED (remote: flash write failure)"
ADB is not detecting my phone.
QFIL is also showing "No Ports Found"
However, Fastboot is working fine.
I donot have TWRP on my phone as of now.
Please help !
I am having exact same problem. Were you able to find solution for it?
Same issue here
Did you get the final solution?
I cant not flash system.img to my softbricked Yu Yuphoria 5110 even with the latest version of adb and fastboot and even with the -S option! Nothing works! Can't flash only system.img, other images are getting flashed. Pl help!
Hi,
I have tried almost every thing to start my asus zenfone 6 (a601cg) which is stuck on fastboot. tools such as xFSTK, Asus Flash tool when ever i run "fastboot oem partition /tmp/partition.tbl" command it gives an error of "FAILED (remote: GPT command failed)". even i have tried some oem commands which failed showing "unknow OEM command". i think its a fastboot issue & i tried to change my fastboot via xFSTK tool which runs properly & status is successful but i think its not updating the fastboot.
Kindly help badly stuck into this.
pratikdoshi4u said:
Hi,
I have tried almost every thing to start my asus zenfone 6 (a601cg) which is stuck on fastboot. tools such as xFSTK, Asus Flash tool when ever i run "fastboot oem partition /tmp/partition.tbl" command it gives an error of "FAILED (remote: GPT command failed)". even i have tried some oem commands which failed showing "unknow OEM command". i think its a fastboot issue & i tried to change my fastboot via xFSTK tool which runs properly & status is successful but i think its not updating the fastboot.
Kindly help badly stuck into this.
Click to expand...
Click to collapse
Hey there same problem here but i got a zenfone 2 ze550ml. I tried an oem token commad and same result. Did you fix your phone?
Hello guys I need some help. I'm stuck in fastboot mode with no recovery or OS too l, let me retrace my steps.
I had my px3 rooted on stock but I was bored with stock and tried to flash bootleggers rom and followed instructions to wipe "everything" but internal storage, so I did including storage under internal storage and flashed the ROM and twrp with it. After it just rebooted back to recovery every time I tried normal boot. (I'm assuming I F'd up by wiping storage). So I googled what to do about looping recovery and one suggestion was to factory reset so I did; I can no longer access recovery. I've tried flashing factory image, flashing the twrp zip, trying to boot straight to twrp, I can't get to adb sideload and it says "no valid slot to boot" on fastboot screen any suggestions?
Got another on fastboot, "error booting boot.img"
Does your PC recognize the phone in Fastboot mode? I would try flashing the full factory image again. Ensure you have the latest platform tools and the correct firmware for your device.
fury683 said:
Does your PC recognize the phone in Fastboot mode? I would try flashing the full factory image again. Ensure you have the latest platform tools and the correct firmware for your device.
Click to expand...
Click to collapse
Yes it does and I've got everything from twrp .zip and .IMG, factory images and ota zip.
I did make progress just now and switched to slot B and got TWRP to show up:laugh: might just sideload OTA and pretend this never happened
Update, adb sideload taking too long to start
wergrun said:
Yes it does and I've got everything from twrp .zip and .IMG, factory images and ota zip.
I did make progress just now and switched to slot B and got TWRP to show up:laugh: might just sideload OTA and pretend this never happened
Update, adb sideload taking too long to start
Click to expand...
Click to collapse
You need to get back to fastboot, and run the flash all bat file from the full factory image.
TonikJDK said:
You need to get back to fastboot, and run the flash all bat file from the full factory image.
Click to expand...
Click to collapse
I tried that but I keeps giving me an error, I'll post it when I get the chance
Problem SOLVED! used video by MaowDroid "Pixel 2 (XL): Un-root and return to stock using factory images"
fury683 said:
Does your PC recognize the phone in Fastboot mode? I would try flashing the full factory image again. Ensure you have the latest platform tools and the correct firmware for your device.
Click to expand...
Click to collapse
I have the same issue, except my computer will not recognize the device in fastboot. I tried two different computers, Windows 10 and laptop running Linux.
wergrun said:
Problem SOLVED! used video by MaowDroid "Pixel 2 (XL): Un-root and return to stock using factory images"
Click to expand...
Click to collapse
Followed the video, but I get an error:
'FAILED (remote: Failed to write to partition Not Found)'
I've tried: bootloader, bootloader_a, bootloader_b and bootloader_other and get the same error.
I'm stuck....
SS823 said:
Followed the video, but I get an error:
'FAILED (remote: Failed to write to partition Not Found)'
I've tried: bootloader, bootloader_a, bootloader_b and bootloader_other and get the same error.
I'm stuck....
Click to expand...
Click to collapse
I did get that too but it was because I forgot to put a space after "bootloader_a ", are you Stuck at around the 9 minute steps?
Yes, right around the end at 9 minutes. Everything works fine - bootloader, radio, etc. When I get to the end of the img zip file I get this message:
checking product...
OKAY [ 0.060s]
checking partition-exists...
FAILED (remote: variable not found)
finished. total time: 0.360s
I am at a loss.