[HELP] Can't flash Shield Tablet - Stock Firmware 4.4.2 i think topic

Hey guys,
I have been trying to flash my Tablet for a few hours now. I would constantly get problems trying to flash. I'd reboot and go into fastboot again and then it would flash successfully. This works for everything (boot.img, recovery.img, system.img) however i can never get userdata.img to flash correctly. I am using the steps from nVidia to do this. Ill post the steps here as well as the exact error im getting.
Steps:

Code:

---

SHIELD TABLET RECOVERY IMAGE FLASHING INSTRUCTIONS

To follow the instructions in this guide, you will need adb and fastboot.
These tools are provided as part of the Android SDK:
http://developer.android.com/sdk/index.html

Before flashing this recovery image to your SHIELD TABLET, connect your SHIELD TABLET
via USB to the PC where you downloaded this recovery image.

Next, put your SHIELD TABLET into fastboot mode using one of the following methods:
SW method:
- Boot to android home screen
- Connect the device to linux/windows system
- Open terminal (on linux); command prompt (on windows).
- Type "adb reboot bootloader" in terminal/command prompt

HW method:
- Turn off the device
- Press "Volume Down" -> "Power", hold "Volume Down" and leave Power buttons till device boots

To flash this recovery image to your SHIELD TABLET, run the following commands from
the directory where you extracted the recovery image package. If this is the
first time you have done this procedure, you must unlock the bootloader (see
below):

fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot flash staging blob
fastboot flash dtb tegra124-tn8-p1761-1270-a04-e-battery.dtb

Unlocking the Bootloader
Your SHIELD TABLET may have shipped with a locked bootloader. To update the device,
you must unlock the bootloader using the following:
- fastboot oem unlock
- Press the "Volume Down" button to select "Unlock bootloader" option on device
- Press the "Power" button to confirm the unlock. Your device's bootloader is now unlocked.

---

My CMD window:

Code:

---

C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase userdata
******** Did you mean to fastboot format this partition?
erasing 'userdata'...
OKAY [ 12.593s]
finished. total time: 12.594s

C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot reboot
rebooting...

finished. total time: 0.022s

C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash userdata userdata
.img
target reported max download size of 570425344 bytes
erasing 'userdata'...
OKAY [ 12.548s]
sending sparse 'userdata' (557052 KB)...
OKAY [ 23.951s]
writing 'userdata'...
FAILED (remote: (FileWriteFailed))
finished. total time: 46.546s

C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery recovery
.img
target reported max download size of 570425344 bytes
sending 'recovery' (9758 KB)...
OKAY [  0.425s]
writing 'recovery'...
FAILED (remote: (FileWriteFailed))
finished. total time: 10.476s

C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase recovery
erasing 'recovery'...
OKAY [  5.034s]
finished. total time: 5.034s

C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery recovery
.img
target reported max download size of 570425344 bytes
sending 'recovery' (9758 KB)...
OKAY [  0.416s]
writing 'recovery'...
FAILED (remote: (FileWriteFailed))
finished. total time: 10.463s

C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery recovery
.img
sending 'recovery' (9758 KB)...
FAILED (command write failed (Invalid argument))
finished. total time: 0.004s

C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery recovery
.img
target reported max download size of 570425344 bytes
sending 'recovery' (9758 KB)...
OKAY [  0.414s]
writing 'recovery'...
FAILED (remote: (FileWriteFailed))
finished. total time: 10.462s

C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase recovery
erasing 'recovery'...
OKAY [  0.030s]
finished. total time: 0.031s

C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery recovery
.img
target reported max download size of 570425344 bytes
sending 'recovery' (9758 KB)...
OKAY [  0.428s]
writing 'recovery'...
OKAY [  0.281s]
finished. total time: 0.711s

C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash boot boot.img
target reported max download size of 570425344 bytes
sending 'boot' (7608 KB)...
OKAY [  0.339s]
writing 'boot'...
OKAY [  0.226s]
finished. total time: 0.567s

C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img

target reported max download size of 570425344 bytes
erasing 'system'...
OKAY [  0.637s]
sending sparse 'system' (556772 KB)...
OKAY [ 24.041s]
writing 'system'...
OKAY [ 20.876s]
sending sparse 'system' (555305 KB)...
OKAY [ 24.219s]
writing 'system'...
OKAY [ 19.289s]
sending sparse 'system' (56409 KB)...
OKAY [  2.431s]
writing 'system'...
OKAY [  1.964s]
finished. total time: 93.461s

C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash userdata userdata
.img
target reported max download size of 570425344 bytes
erasing 'userdata'...
OKAY [ 10.050s]
sending sparse 'userdata' (557052 KB)...
OKAY [ 23.801s]
writing 'userdata'...
FAILED (remote: (FileWriteFailed))
finished. total time: 43.929s

C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash userdata userdata
.img
target reported max download size of 570425344 bytes
erasing 'userdata'...
OKAY [  5.048s]
sending sparse 'userdata' (557052 KB)...
OKAY [ 23.702s]
writing 'userdata'...
FAILED (remote: (FileWriteFailed))
finished. total time: 38.796s

C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot staging blob
usage: fastboot [ <option> ] <command>

C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash staging blob
target reported max download size of 570425344 bytes
sending 'staging' (17491 KB)...
OKAY [  0.742s]
writing 'staging'...
FAILED (remote: (FileWriteFailed))
finished. total time: 10.807s

C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot reboot
rebooting...

finished. total time: 0.003s

C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash staging blob
target reported max download size of 570425344 bytes
sending 'staging' (17491 KB)...
OKAY [  0.752s]
writing 'staging'...
OKAY [  0.495s]
finished. total time: 1.249s

C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash dtb tegra124-tn8-
p1761-1270-a04-e-battery.dtb
target reported max download size of 570425344 bytes
sending 'dtb' (68 KB)...
OKAY [  0.027s]
writing 'dtb'...
OKAY [  0.011s]
finished. total time: 0.039s

C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash userdata userdata
.img
target reported max download size of 570425344 bytes
erasing 'userdata'...
OKAY [ 12.662s]
sending sparse 'userdata' (557052 KB)...
OKAY [ 23.825s]
writing 'userdata'...
FAILED (remote: (FileWriteFailed))
finished. total time: 46.542s

C:\Program Files (x86)\Minimal ADB and Fastboot>

---

[Q] I think there is a problem with my touch screen topic

Every time when my finger suddenly stops sliding , the trail left on the screen seems to be a little bit longer, and then it just jumped back to my finger. That's annoying. Is there anybody else who's experiencing this as well? How can i fix it?

[Q] Bootloop after flashing stock ROM via Odin. I think I've tried everything. topic

The Wifi on my phone wasn't turning on, even after factory reset, so I reflashed stock ROM via Odin (v3.07)
I got stuck in a bootloop, and after factory reset via the stock recovery + wipe of cache partition, it was still stuck.
I then re-flashed the stock ROM. Still stuck.
Tried using Kies 3, with the firmware upgrade and installation tab. Said something about not supporting my phone when I was prompted to plug it in. (SM-G355H; Samsung Galaxy Core II Duos)
I then found an unofficial version of CWM v6 for my phone (there's no official support), and quickly flashed that (via Odin 3.09; which is what I use from this point on), forgetting that my phone was no longer rooted. I wiped davlik cache and data. Still stuck. Then I rooted my phone. Stuck.
Then I reflashed stock ROM (this time, I downloaded from another website) (to test my luck, I tried seeing if simply a factory reset and cache wipe would work. It did not) rooted my phone, and flashed CWM. Wiped davlik cache. Still stuck.

By the way, when I wipe davlik cache it says:
Warning: no file_contexts
E:unknown volume for path [/sd-ext]
Davlik Cache wiped.

Any ideas on what to do now? I can't send it to a manufacturer / repair store where I live. I'm thinking maybe I should untick Auto Reboot and/or F. Reset Time when flashing, use an earlier version of Odin or the ROM itself, or maybe there is something I can do with ADB? I'm not very familiar with it, but I'm more than willing to learn. I just need some direction...

I was just trying to fix my WiFi... :crying:

[Q] Bootloop after flashing stock ROM via Odin. I think I've tried everything. topic

The Wifi on my phone wasn't turning on, even after factory reset, so I reflashed stock ROM via Odin (v3.07)
I got stuck in a bootloop, and after factory reset via the stock recovery + wipe of cache partition, it was still stuck.
I then re-flashed the stock ROM. Still stuck.
Tried using Kies 3, with the firmware upgrade and installation tab. Said something about not supporting my phone when I was prompted to plug it in. (SM-G355H; Samsung Galaxy Core II Duos)
I then found an unofficial version of CWM v6 for my phone (there's no official support), and quickly flashed that (via Odin 3.09; which is what I use from this point on), forgetting that my phone was no longer rooted. I wiped davlik cache and data. Still stuck. Then I rooted my phone. Stuck.
Then I reflashed stock ROM (this time, I downloaded from another website) (to test my luck, I tried seeing if simply a factory reset and cache wipe would work. It did not) rooted my phone, and flashed CWM. Wiped davlik cache. Still stuck.

By the way, when I wipe davlik cache it says:
Warning: no file_contexts
E:unknown volume for path [/sd-ext]
Davlik Cache wiped.

Any ideas on what to do now? I can't send it to a manufacturer / repair store where I live. I'm thinking maybe I should untick Auto Reboot and/or F. Reset Time when flashing, use an earlier version of Odin or the ROM itself, or maybe there is something I can do with ADB? I'm not very familiar with it, but I'm more than willing to learn. I just need some direction...

[Q] Help!! I think my phone got brick topic

Hello i was running CM 11 on my gt-i9500 then i installed the alpha i think it was chinese of lolipop 5.0 stock version
yesterday sammobile released official version russian of 5.0 so i downloaded it , and i think something went wrong because this message show when i turn on my phone Firmware upgrade encountered an issue please select recovery mode in kies and try again
i tried every thing flashing old stock new stock using recover and all things every time i try to install it using odin tried most version of odin
it give me fail in system this msg show
and i tried removed kies and installation tried while its on and while its off !!

Quote:

<ID:0/004> Added!! <OSM> Enter CS for MD5.. <OSM> Check MD5.. Do not unplug the cable.. <OSM> Please wait.. <OSM> I9500XXUHOA7_I9500SERHOA7_I9500XXUHOA7_HOME.tar.md 5 is valid. <OSM> Checking MD5 finished Sucessfully.. <OSM> Leave CS.. <ID:0/004> Odin v.3 engine (ID:4).. <ID:0/004> File analysis.. <ID:0/004> SetupConnection.. <ID:0/004> Initialzation.. <ID:0/004> Get PIT for mapping.. <ID:0/004> Firmware update start.. <ID:0/004> sboot.bin <ID:0/004> NAND Write Start!! <ID:0/004> boot.img <ID:0/004> recovery.img <ID:0/004> system.img <ID:0/004> FAIL! <OSM> All threads completed. (succeed 0 / failed 1) <ID:0/004> Removed!!

Please HELP FAST!!

I think I need a jtag topic

I accidentally flashed a rom called Blekota_Note4_Lite_I9300_V3_Aroma for my Galaxy S3 T-Mobile T999L and now it won't boot. Nothing happens. Whatever that rom did it must have written over a lot of files. I made my own jig that doesn't work for my S3 but does work for my S2. So a jig isn't the solution. Tried to make a SD card using this guide but that doesn't work. Though that maybe because I had PacMan rom on it, and before that I had stock 4.1. Also the T999L Sd card debrick did make the phone act different to my computer, as it would usually find QHSUSB_DLOAD but won't with that SD card. I've tried the "SGH-T999 ***NOT FOR 4.3*** Debrick Image" and it would show the QHSUSB_DLOAD on my Windows PC. So that SD card is kinda working but the image isn't for my issue.

Can someone give me a image that will allow me to Odin my phone? If not can someone recommend me a cheap Jtag? :D

[Q] Help think my lg g2 died! (No blicked) topic

I put the lg g2 to reload and on waking he was discharged (he turns on and off) tested other chargers and have failed to recharge it.

I made the switch from USB Charging Port, changed the battery with a new one, and continued on and off, it will be problem in moherboard?

pics anexxed.


detail: it comes in downloading mode however can not spend any rom.

Attached Thumbnails

 


 


 


 

{Q}This is not allowed i think but still topic

Hello everyone,
i own a z ultra ever since it was released screen even broke and i was without it for months till i fixed it. Now that i got it back 2 months ago i been trying every single rom out there but i always have a problem.

monxdified is outdated and one time it didnt want to boot no more so i changed to Stone HD3 which random restarts/freezes its slow when i run my games compared to how monxdified was. Then we have the Dirty Unicorn and Cyanhacker both 2 great roms like monx and stone but completely different also both with bugs like for example no hd playback or screen too dark issues/bluetooth issues.

Now im really stuck and idk what to do im looking for a stable rom but everytime there is something that just messes up with me.

So my actual question is which rom do you guys use for daily use? Like listening to music/heavy gaming/reading/browsing/calling ofcourse atm im again back to Stone HD3 experiencing the random reboots but i have no idea where to go to this time.

Was messing around with my bueld.prop I think I need a LG LS620 stock recovery topic

I was messing around with the build.prop on my Boost LG Realm. As far as I know there is no way to make a backup to this phone, so I did the next best thing and made a copy of the build.prop and saved the original. Somehow though when I copied and pasted it back into sys file using ES explorer, something went terribly wrong. the phone gets a black screen of death right after the boot screen. I am able to get into the stock recovery, but no further. I'm thinking that a copy of the stock firmware is my only help but I can't find a copy of it anywhere. I do have a second Realm that is my son's that still works (probably because I haven't touched it yet) if that helps at all.

[Q] CM12, Skype (I think) deleting my phone contacts topic

I thought it would just happen randomly while using my phone, I would go to make a call/check a message and my contacts would be deleted. One by one I could see the names turn to numbers on the call list. Happens a few times a week, have to reimport each time (also imports are glitched, so I get loads of import notifications that don't go away until I restart).

I've now noticed it seems to randomly happen after using Skype. So, is Skype deleting my contacts? Why? How do I fix it (other than removing Skype?).
I've tried googling, but it seems to just be threads asking how to remove skype contacts from android contacts list.

[Q] Please Help - Think i bricked my phone topic

Hello, i wanted to update my Moto G, bought in Spain, from 4.4.4 to 5.0.2 so i followed this thread:

http://forum.xda-developers.com/moto...tured-t3002674

i was stupid and did not read everything before doing it. A friend of mine told me to go to the bootloader and apply the update from sdcard. Midway the update stopped and the phone did not responde to anything, so my friend told me to hold de power button until it turned off.

Now my phone won't turn on, only bootloader, and i can't do anything. Can someone please help me?!

i had everything stock. no rom, no unlocked bootloader, nothing.

T-Mobile Z3 connected to Band 12 (I think) topic

Hi Folks,

I've been talking to a few people on Howard Forums who think this is impossible, but now on several different occasions, LTE Discovery has shown my phone as being connected to Band 12. This is a stock, D6616 which is currently showing Bands 2 and 4 as active in the service screen and NOT Band 12. Can this be possible? I was able to pull over, stay connected and run a speed test on Band 12 which showed 10mbps download, which sounds about right given that it's just a 5mhz channel. Oh, and this was in San Jose, CA and then Cupertino/Saratoga, CA. Another weird issue is that, I don't believe the Channel 51 interference has been solved here.

So, I'm not trying to spread misinformation but could it be that the T-Mobile Z3 actually has Band 12 out of the box? Or, is LTE Discovery simply inaccurate and this is all just a dream? :)













Any thoughts welcome!

-Collin-