I tried turning on my Shield (WiFi) tablet today and it just stays stuck on the nVidia logo. I tried booting into recovery and it also just sits, stuck on the nVidia logo. I figured it might be corrupted (bad update, possibly), so I decided to restore it to factory settings by using the latest system image files from nVidia on their Dev site. I followed the instructions, but didn't get too far when I needed to unlock my bootloader and it failed, returning:
Code:
(bootloader) Showing Options on Display.
(bootloader) Use device keys for selection.
(bootloader) erasing userdata...
(bootloader) erasing userdata done
(bootloader) erasing cache...
(bootloader) erasing cache done
(bootloader) unlocking...
FAILED (remote: (Unknown error code))
finished. total time: 14.872s
I have tried 2 computers, 2 USB cables, and still have had no luck getting it to unlock the bootloader to flash the factory image. I also did some digging and found that my bootloader is listed as UNDEF_BUILD and that some people had luck restoring it though flashing the file tegra124-tn8-p1761-1270-a04-e-battery.dtb, but it won't let me do that because it also complains my bootloader is locked.
The tablet is out of warranty, so I really don't want to have to RMA it due to cost. Any ideas or hope of bringing it back to life?
Related
Hello everyone.
I am hoping someone might be able to help me out.
I had been using the sensation for a while with the s-off bootloader with no problems.
Recently I tried to update it to see how it would work on the lolipop builds that are out.
I updated the recovery to 2.8.3.0 TWRP and tried to flash the rom.
It looked like it completeled normally but when I went to restart the phone it will only boot into the fastboot of the boot loader. I can not get it to boot into the rom or recovery.
I have tried to reflash the recovery using fastboot but get the following error:
FAILED (remote: image update error)
I used the command (fastboot flash recovery recovery.img) to try and flash a previous one that worked.
I can use fastboot to boot the recovery though and then it will load.
But when the recovery is loaded or by using the adb terminal I can not access any of the partitions.
It seems like the partition table is corrupted.
I have been trying to find a hboot to reflash but I also can not seem to use the command
fastboot OEM reboot RUU
That command gives me the following error
...
(bootloader) [SD_HW_ERR] read data fail in CMD18
(bootloader) [SD_HW_ERR] SD: Read data fail..
(bootloader) [ERR] partition_read_emmc(732): error 2
(bootloader) Start Verify: 0
(bootloader) [SD_HW_ERR] read data fail in CMD18
(bootloader) [SD_HW_ERR] SD: Read data fail..
(bootloader) [ERR] partition_read_emmc(732): error 2
(bootloader) Start Verify: 0
(bootloader) erase sector 130560 ~ 131071 (512)
(bootloader) emmc_erase(1852): sd_write_sector failed!
OKAY [ 0.081s]
finished. total time: 0.082s
Currently the phone is on Firmware 3.33
s-off
hboot 1.27.110
Does anyone know where I might be able to find the firmware / hboot to reflash to see if that fixes the partitions on the phone?
Or any other way to fix this?
I am finding it hard to try and dig up files that have working links for this device anymore.
If I am not mistaken, reflashing the firmware should be able to fix it though.
I think I might need to find the RUU and just reflash back to stock and am waiting on the download for that as we speak. Just dreading going through and rerooting the phone again.
The wire part was really tricky.
Any help would be greatly appreciated.
Thank you for your time to read this.
TheArtiszan said:
Hello everyone.
I am hoping someone might be able to help me out.
I had been using the sensation for a while with the s-off bootloader with no problems.
Recently I tried to update it to see how it would work on the lolipop builds that are out.
I updated the recovery to 2.8.3.0 TWRP and tried to flash the rom.
It looked like it completeled normally but when I went to restart the phone it will only boot into the fastboot of the boot loader. I can not get it to boot into the rom or recovery.
I have tried to reflash the recovery using fastboot but get the following error:
FAILED (remote: image update error)
I used the command (fastboot flash recovery recovery.img) to try and flash a previous one that worked.
I can use fastboot to boot the recovery though and then it will load.
But when the recovery is loaded or by using the adb terminal I can not access any of the partitions.
It seems like the partition table is corrupted.
I have been trying to find a hboot to reflash but I also can not seem to use the command
fastboot OEM reboot RUU
That command gives me the following error
...
(bootloader) [SD_HW_ERR] read data fail in CMD18
(bootloader) [SD_HW_ERR] SD: Read data fail..
(bootloader) [ERR] partition_read_emmc(732): error 2
(bootloader) Start Verify: 0
(bootloader) [SD_HW_ERR] read data fail in CMD18
(bootloader) [SD_HW_ERR] SD: Read data fail..
(bootloader) [ERR] partition_read_emmc(732): error 2
(bootloader) Start Verify: 0
(bootloader) erase sector 130560 ~ 131071 (512)
(bootloader) emmc_erase(1852): sd_write_sector failed!
OKAY [ 0.081s]
finished. total time: 0.082s
Currently the phone is on Firmware 3.33
s-off
hboot 1.27.110
Does anyone know where I might be able to find the firmware / hboot to reflash to see if that fixes the partitions on the phone?
Or any other way to fix this?
I am finding it hard to try and dig up files that have working links for this device anymore.
If I am not mistaken, reflashing the firmware should be able to fix it though.
I think I might need to find the RUU and just reflash back to stock and am waiting on the download for that as we speak. Just dreading going through and rerooting the phone again.
The wire part was really tricky.
Any help would be greatly appreciated.
Thank you for your time to read this.
Click to expand...
Click to collapse
Okay so the only good news I can see is that if you can make the RUU run it will not s-on your phone so rooting will be easy but, if fastboot oem reboot RUU doesn't work then your in alot of trouble. When you download the RUU (any I'd one for the sensation of XE will do) run it and then extract the .zip (search on Google if you are unsure how to) when you have that extract everything and then move system.img data.img and anything rom related out of the folder. Your aiming to only have hboot related items and the android txt file in there. Zip it back up by highlighting all the files and make a zip file, not by zipping the folder. Rename the zip file to the device model number with img (i think its pg58img.zip) then pass it to your sdcard and then reboot to hboot.
If your hboot can "update" it will hopefully be able to restore/remake your damaged partition table but if that fails your options are really limited. A J-tag would be able to restore the devices partition tables forcefully but you would need a repair shop to do that.
Sent from my LG-D802 using Tapatalk
heavy_metal_man said:
A J-tag would be able to restore the devices partition tables forcefully but you would need a repair shop to do that.
Sent from my LG-D802 using Tapatalk
Click to expand...
Click to collapse
or if you know what to do about jtag method see here
http://forum.xda-developers.com/showthread.php?t=2775115
Yeah I think I'm toast then.
I tried grabbing the default Rom .zip and flash with boot loader and that failed.
Not sure if it needed to be on a gold card or not though.
TheArtiszan said:
Yeah I think I'm toast then.
I tried grabbing the default Rom .zip and flash with boot loader and that failed.
Not sure if it needed to be on a gold card or not though.
Click to expand...
Click to collapse
Shouldn't make a difference as you are s-off.
What happens if you issue the command. Fastboot getvar all
Does it work?
Sent from my LG-D802 using Tapatalk
friend brought me a d820e to look at, says it happens after OTA (sounds weird...)
my analysis as follows:
1. bootloader stays locked after reboot, tried "fastboot oem unlock" several times
2. flashing factory image, custom recoveries, cache, etc... are failed
Code:
sending 'recovery' (9434 KB)...
OKAY [ 0.515s]
writing 'recovery'...
FAILED (remote: flash write failure)
finished. total time: 0.696s
.
3. factory reset/date wipe/cache wipe results in:
Code:
Can't mount /cache/etc...
i could try to flash with LG flashtool but i'm not sure which TOT i should use, don't want to brick the device even more.
any other suggestions?
device info:
Code:
tools>fastboot.exe getvar all
(bootloader) max-download-size: 0x40000000
(bootloader) version-hardware: rev_11
(bootloader) version-baseband: M8974A-2.0.50.2.22
(bootloader) version-bootloader: HHZ12d
(bootloader) version-cdma: N/A
(bootloader) variant: hammerhead D820(E) 16GB
android system recovery LRX22C
sh33z0r said:
1. bootloader stays locked after reboot, tried "fastboot oem unlock" several times
Click to expand...
Click to collapse
eMMC is dead.
anything to do or just rma?
sh33z0r said:
anything to do or just rma?
Click to expand...
Click to collapse
If it's still in warranty, RMA. If it isn't, send it to LG and pay for repair (motherboard swap).
Okay, so all day, I've been trying to fix this damn phone because of a root fail. I unlocked the bootloader, installed SuperSU and now the phone just reboots with a white screen and red words saying this build is for development purposdes only. I can get to download and bootloader mode fine though. Its S-On Bootloader Unlocked. I would honestly settle for it to be set to factory settings as I just need the phone fixed. Rooting has been so stressful. I don't care about losing data.
I'm thinking it failed because I used an SDHC 32GB Micro SD Card? Ive been trying to use a recovery img, Im using HTC Android Phone ROM Update Utility and thats not working. It asks to update the ROm version from 3.35.401.12 to image version (shows nothing). Then it says image error 158 (cannot update my android phone).
When flashing a recovery image, I get:
C:\Users\shaif\Downloads\Root M9>fastboot flash recovery recovery.img
target reported max download size of 800000000 bytes
sending 'recovery' (32848 KB)...
OKAY [ 2.503s]
writing 'recovery'...
(bootloader) HOSD CL#671758
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) Update partition OK
(bootloader) [email protected]
OKAY [ 2.792s]
finished. total time: 5.301s
Still not working.
Also tried fastboot oem rebootRUU but that took me to a screen that says Security Warning
Someone please help me, Im desperate
Hi !
I see that you have fixed your issue https://forum.xda-developers.com/showpost.php?p=71188370&postcount=1372 so I close this down
Cheers !
Hello guys, i had this phone xt1032 moto g that some months ago had some battery issues and keep shuting down and say "optimization app" every time....
This problem became very frequently until the phone keep blocked into boot screen for ever.... i think that the problem was the battery and i change it....but the problem still remain.
I try with POWER BTN + VOL DOWN -> factory...and same boot blocked
POWER BTN + VOL DOWN -> recovery ...and get the robot with red alert and no command message (i try all the things suggested by wasconet(dot)com
But nothing...
I try to flash the recovery with the twrp but get error
MBP-di-Dariolatform-tools ddz$ ./fastboot flash recovery /Users/ddz/Desktop/GPe_5.1/ROOT-RECOVERY/twrp-2.8.6.0-xt1032.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:recovery: not found
target reported max download size of 536870912 bytes
sending 'recovery' (8480 KB)...
OKAY [ 0.373s]
writing 'recovery'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.406s
i try with 4 different version..the last one and some olders but same errors and when i open the recovery same robot with message no command.....
I think that the battery problem had damaged the SO...maybe the boot (like a softbrick).... there is something that can i do, or just take the phone and burn it?
EDIT:
I can't shut down the phone...if press 10 sec power button the phone restart and for shut down it i must disconnect battery or enter fastboot withouth action and the phone shut down alone..
THanks
SOLVED:
I solved the problem by unlocking the bootloader and followed this guide with All in one command that do everything:
https://forum.xda-developers.com/moto-g/general/gpe-lollipop-5-1-1click-installer-t3075522
Before that i was able to wipe cache and data/factory in the image with death robot and "no command" just pressed vol up and power a lot of times and the commands appear.
I use the guide because the wipe data/factory don't restore the phone so i flashed a new ROM following the guide linked..... if not work initially because i don't unlock the bootloader (very easy to do).
Hello,
So I have been using my Shield Tablet just fine for the past few years but now its locked on the Nvidia logo when it boots up, I've tried going into recovery mode to factory reset but then it just hangs on "No Command" I noticed that the bootloader is locked so I got ABD and fastboot. Once I setup the tablet to register in fastboot devices, I then use 'fastboot oem unlock' like it says to from the Nvidia support forums, but it fails and gives this command. Can anyone help me out to figure out what is wrong?
.... > fastboot oem unlock
(bootloader) Showing Options on Display.
(bootloader) Use device keys for selection.
(bootloader) erasing userdata...
(bootloader) erasing userdata done
(bootloader) erasing cache...
(bootloader) erasing cache done
(bootloader) unlocking...
FAILED (remote: '(')
fastboot: error: Command failed
Any advice would be helpful
Malzra said:
Hello,
So I have been using my Shield Tablet just fine for the past few years but now its locked on the Nvidia logo when it boots up, I've tried going into recovery mode to factory reset but then it just hangs on "No Command" I noticed that the bootloader is locked so I got ABD and fastboot. Once I setup the tablet to register in fastboot devices, I then use 'fastboot oem unlock' like it says to from the Nvidia support forums, but it fails and gives this command. Can anyone help me out to figure out what is wrong?
.... > fastboot oem unlock
(bootloader) Showing Options on Display.
(bootloader) Use device keys for selection.
(bootloader) erasing userdata...
(bootloader) erasing userdata done
(bootloader) erasing cache...
(bootloader) erasing cache done
(bootloader) unlocking...
FAILED (remote: '(')
fastboot: error: Command failed
Any advice would be helpful
Click to expand...
Click to collapse
What happens when fastboot flashing unlock