Database Info

Stock Recovery zip

Hi, am looking for the stock recovery file/zip p[ease.

The stock recovery is contained in the full firmware download (inside the blob), available on the Asus support site.

_that said:
The stock recovery is contained in the full firmware download (inside the blob), available on the Asus support site.
Click to expand...
Click to collapse
Thanks.

_that said:
The stock recovery is contained in the full firmware download (inside the blob), available on the Asus support site.
Click to expand...
Click to collapse
I got the firmware and extracted the blob, but I only have fastboot, how do I flash it to get stock recovery back?
I tried this:
fastboot -i 0x0B05 flash staging blob
fastboot -i 0x0B05 flash system blob
but nothing works, except I lost /system partition now (I was able to boot Android before). Any help appreciated.

3c said:
I got the firmware and extracted the blob, but I only have fastboot, how do I flash it to get stock recovery back?
I tried this:
fastboot -i 0x0B05 flash staging blob
fastboot -i 0x0B05 flash system blob
but nothing works, except I lost /system partition now (I was able to boot Android before). Any help appreciated.
Click to expand...
Click to collapse
Sorry, if that doesn't work I have no more idea how to fix your locked tablet, if you don't have the blob for wheelie and nvflash.

_that said:
Sorry, if that doesn't work I have no more idea how to fix your locked tablet, if you don't have the blob for wheelie and nvflash.
Click to expand...
Click to collapse
Thanks anyway for helping. All I could figure out is that the blob doesn't actually get written to any partition. I've seen some users be successful doing that (what you suggested), so I'll keep trying, maybe reverting the driver. Wondering if using naked driver works well for such method.
In any case, thanks, and I'll post a reply if I can make it work.

3c said:
Thanks anyway for helping. All I could figure out is that the blob doesn't actually get written to any partition. I've seen some users be successful doing that (what you suggested), so I'll keep trying, maybe reverting the driver. Wondering if using naked driver works well for such method.
In any case, thanks, and I'll post a reply if I can make it work.
Click to expand...
Click to collapse
Try this, download stock recovery here http://www.mediafire.com/download.php?pdipp4h2qyqka63
then execute this:
fastboot -i 0x0B05 flash recovery recovery.blob
boot directly into recovery and see if you have recovery back.

buhohitr said:
Try this, download stock recovery here http://www.mediafire.com/download.php?pdipp4h2qyqka63
then execute this:
fastboot -i 0x0B05 flash recovery recovery.blob
boot directly into recovery and see if you have recovery back.
Click to expand...
Click to collapse
Big progress: blob flashed without a glitch. I was happy until I tried to reboot with fastboot: tablet frozen! Reboot, still no recovery
I guess this is it. Got a nice folding brick now! Will try RMA, but from Cambodia not sure it's worth it. Maybe next month when I'm in France.
Can't believe this happened while tablet is locked! Now I hate Asus for this.

3c said:
Big progress: blob flashed without a glitch. I was happy until I tried to reboot with fastboot: tablet frozen! Reboot, still no recovery
I guess this is it. Got a nice folding brick now! Will try RMA, but from Cambodia not sure it's worth it. Maybe next month when I'm in France.
Can't believe this happened while tablet is locked! Now I hate Asus for this.
Click to expand...
Click to collapse
I have asked you to flash the recovery zip, but once done you should boot directly into the recovery, don't boot up. Let me know if you still can fastboot the recovery to your device, but once done, hold the power until device turn off, then right away hold both power button and volume down button to boot into recovery. If you could do this we still have hope. Once in recovery let me know we can proceed to next step.

buhohitr said:
I have asked you to flash the recovery zip, but once done you should boot directly into the recovery, don't boot up. Let me know if you still can fastboot the recovery to your device, but once done, hold the power until device turn off, then right away hold both power button and volume down button to boot into recovery. If you could do this we still have hope. Once in recovery let me know we can proceed to next step.
Click to expand...
Click to collapse
I cannot actually do anything past flashing a blob. the tablet is "frozen" from the moment it enters fastboot, then after flashing any blobs, any further fastboot command are "non-responsive", here is the actual output. At the end the reboot command succeeds but nothing actually happened on the tablet. Still showing the 4 icons (RCK/Android/USB/WIPE) and the top white text. Tried with original Asus driver, with Google driver and now naked driver. no difference, can only be the tablet ;(
C:\Android\android-sdk\platform-tools>fastboot devices
015d2a5088641a08 fastboot
C:\Android\android-sdk\platform-tools>fastboot -i 0x0B05 flash recovery recovery.blob
sending 'recovery' (6260 KB)...
OKAY [ 1.862s]
writing 'recovery'...
OKAY [ 2.432s]
finished. total time: 4.297s
C:\Android\android-sdk\platform-tools>fastboot reboot-bootloader
rebooting into bootloader...
FAILED (command write failed (Unknown error))
finished. total time: 0.642s
C:\Android\android-sdk\platform-tools>fastboot continue
resuming boot...
FAILED (command write failed (Unknown error))
finished. total time: 0.569s
C:\Android\android-sdk\platform-tools>fastboot reboot
rebooting...
finished. total time: 0.549s
EDIT: Kinda lame I'm sure, but desperate as I am, I tried that too:
C:\Android\android-sdk\platform-tools>fastboot -i 0x0B05 boot recovery.blob
creating boot image...
creating boot image - 6414336 bytes
downloading 'boot.img'...
OKAY [ 1.857s]
booting...
FAILED (remote: ()
finished. total time: 1.861s
I suppose I need a kernel blob... But I couldn't find any stock to flash? Would you also happen to have that handy too?

3c said:
I cannot actually do anything past flashing a blob. the tablet is "frozen" from the moment it enters fastboot, then after flashing any blobs, any further fastboot command are "non-responsive", here is the actual output. At the end the reboot command succeeds but nothing actually happened on the tablet. Still showing the 4 icons (RCK/Android/USB/WIPE) and the top white text. Tried with original Asus driver, with Google driver and now naked driver. no difference, can only be the tablet ;(
C:\Android\android-sdk\platform-tools>fastboot devices
015d2a5088641a08 fastboot
C:\Android\android-sdk\platform-tools>fastboot -i 0x0B05 flash recovery recovery.blob
sending 'recovery' (6260 KB)...
OKAY [ 1.862s]
writing 'recovery'...
OKAY [ 2.432s]
finished. total time: 4.297s
C:\Android\android-sdk\platform-tools>fastboot reboot-bootloader
rebooting into bootloader...
FAILED (command write failed (Unknown error))
finished. total time: 0.642s
C:\Android\android-sdk\platform-tools>fastboot continue
resuming boot...
FAILED (command write failed (Unknown error))
finished. total time: 0.569s
C:\Android\android-sdk\platform-tools>fastboot reboot
rebooting...
finished. total time: 0.549s
EDIT: Kinda lame I'm sure, but desperate as I am, I tried that too:
C:\Android\android-sdk\platform-tools>fastboot -i 0x0B05 boot recovery.blob
creating boot image...
creating boot image - 6414336 bytes
downloading 'boot.img'...
OKAY [ 1.857s]
booting...
FAILED (remote: ()
finished. total time: 1.861s
I suppose I need a kernel blob... But I couldn't find any stock to flash? Would you also happen to have that handy too?
Click to expand...
Click to collapse
Seems like when you flashed the blob file it wipe out everything. But I tried to boot into recovery so it's a good sign that your tablet is not brick ....yet!!
Here is the stock kernel I created for you http://www.mediafire.com/download.php?16fji3z1nghr6th
fastboot -i 0x0B05 flash boot boot.blob
Possible we may need the bootloader too, but will see.

buhohitr said:
Seems like when you flashed the blob file it wipe out everything. But I tried to boot into recovery so it's a good sign that your tablet is not brick ....yet!!
Here is the stock kernel I created for you http://www.mediafire.com/download.php?16fji3z1nghr6th
fastboot -i 0x0B05 flash boot boot.blob
Possible we may need the bootloader too, but will see.
Click to expand...
Click to collapse
I guess I'm ready for bootloader flashing. Either it bricks it for good or it works or else
Nothing has changed. Just to give you more info, booting RCK, results in booting failed - unrecoverable bootloader error (0x000..).
Booting android: cold-booting linux - signature match. Then screen is frozen, but Windows 7 recognize the tablet fine. As if a kernel was there, right?
So I tried flashing boot.blob and recovery.blob and the JB update blob to system again, but it hangs at the end, still have to reboot manually. It's like fastboot is not actually flashing anything, writing in below output is abnormally low or could it be that fast!?: It's the same time for boot, recovery of a 800Mb system file!?
C:\Android\android-sdk\platform-tools>fastboot -i 0x0B05 flash system blob
erasing 'system'...
OKAY [ 2.329s]
sending 'system' (800199 KB)...
OKAY [141.653s]
writing 'system'...
OKAY [ 2.932s]
finished. total time: 146.920s
But the behavior of the bootloader seems quite strange, all this hanging at end of flashing, could this be a corrupted bootloader or worse a corrupted partition table?

3c said:
I guess I'm ready for bootloader flashing. Either it bricks it for good or it works or else
Nothing has changed. Just to give you more info, booting RCK, results in booting failed - unrecoverable bootloader error (0x000..).
Booting android: cold-booting linux - signature match. Then screen is frozen, but Windows 7 recognize the tablet fine. As if a kernel was there, right?
So I tried flashing boot.blob and recovery.blob and the JB update blob to system again, but it hangs at the end, still have to reboot manually. It's like fastboot is not actually flashing anything, writing in below output is abnormally low or could it be that fast!?: It's the same time for boot, recovery of a 800Mb system file!?
C:\Android\android-sdk\platform-tools>fastboot -i 0x0B05 flash system blob
erasing 'system'...
OKAY [ 2.329s]
sending 'system' (800199 KB)...
OKAY [141.653s]
writing 'system'...
OKAY [ 2.932s]
finished. total time: 146.920s
But the behavior of the bootloader seems quite strange, all this hanging at end of flashing, could this be a corrupted bootloader or worse a corrupted partition table?
Click to expand...
Click to collapse
Let try the bootloader http://www.mediafire.com/download.php?u6bwnaao6khcdaf

3c said:
Then screen is frozen, but Windows 7 recognize the tablet fine. As if a kernel was there, right?
Click to expand...
Click to collapse
Define "Windows recognizes the tablet". If you have ADB access, you should be able to recover.

buhohitr said:
Let try the bootloader http://www.mediafire.com/download.php?u6bwnaao6khcdaf
Click to expand...
Click to collapse
Actually how do you flash bootloader? I did this: fastboot -i 0x0B05 flash bootloader loader.blob ?
But anyway, I just read fastboot doesn't flash anything when device is locked! So this piece of s**t doesn't flash but will erase any partition you wish! How's that for a crappy software! I wish I never tried to update to JB!
_that said:
Define "Windows recognizes the tablet". If you have ADB access, you should be able to recover.
Click to expand...
Click to collapse
No ADB, just the name of the tablet appears in Device Manager, sort of the SD card access, but no actual access. I updated the driver manually and was proposed some MTP device. No adb or fastboot when this is available.
Here is the input from another thread: I copy it because I believe the information is very important and identify another way to brick the TF700:
Pretoriano80 said:
ICS bootloader had the fastboot option disabled if the device's bootloader was still locked and the USB icon wasn't showing at all.
With the JB bootloader Asus made the USB icon available even if the device was locked so you can access fastboot mode but you can't flash anything (yes,it doesn't make sense, but this is Asus).
Anyway, if you are able to boot in recovery you should be able to restore you device easily,just follow my guide from the general forum.
Click to expand...
Click to collapse
That's exactly what's happening! I can go in fastboot, but it doesn't flash anything! Though it erase any partition you wish! How smart is that? So I have one thing to say to locked owner: never go in fastboot, ever, it's useless and can actually brick your tablet!!!
I bricked the tablet on my own sure enough, but without this ridiculous fastboot I wouldn't have been able to mess up the tablet in the first place! Sorry for those who love their tablet and Asus, but I find their strategy ridiculous. Except if it's main goal is to make money on RMA.
Thanks Asus for this nice brick!

3c said:
But anyway, I just read fastboot doesn't flash anything when device is locked! So this piece of s**t doesn't flash but will erase any partition you wish!
Click to expand...
Click to collapse
I'd still expect the locked bootloader to flash correctly signed blobs. But who knows what Asus were thinking...
One more idea you can try: Get the 10.4.4.23 dlpkgfile and extract the blob from there.
This blob contains the 10.4.4.23 bootloader, stock recovery and stock kernel, and an orignal Asus signature. My WW version is 13573093 bytes, so it is much smaller than the full firmware blob - try to flash that via fastboot, maybe you are lucky and it works.

_that said:
I'd still expect the locked bootloader to flash correctly signed blobs. But who knows what Asus were thinking...
One more idea you can try: Get the 10.4.4.23 dlpkgfile and extract the blob from there.
This blob contains the 10.4.4.23 bootloader, stock recovery and stock kernel, and an orignal Asus signature. My WW version is 13573093 bytes, so it is much smaller than the full firmware blob - try to flash that via fastboot, maybe you are lucky and it works.
Click to expand...
Click to collapse
Will do, thanks. How would you flash such blob? Onto "staging" or "system"? I've seen users flash the JB update blob to system and be successful. Also seen some posts mentioning staging?

3c said:
Will do, thanks. How would you flash such blob? Onto "staging" or "system"? I've seen users flash the JB update blob to system and be successful. Also seen some posts mentioning staging?
Click to expand...
Click to collapse
I don't really know - all I know is:
- TF700's fastboot implementation only supports blobs, no raw partition images
- blobs are usually always written to the staging partition first, then the contained partition images are flashed to the correct partition(s) by the bootloader
I've seen both variants of the fastboot command, so maybe the target partition doesn't matter when sending blobs. I'd try staging first.

[Q] HTC One S can't pass the HTC logo

Hello
a few days ago I used "HTC ONE S AIO KIT" to install Jelly bean 4.2.2 on my HTC ONE S
I successfully installed the jelly bean and everything was fine
during the process, I created a backup from my phone in the ClockworkMod
today, I booted to ClockworkMod recovery > backup and restore > restore > and selected the backup file I created
the phone restarted and got stuck on the HTC ONE logo
I did everything I could in the past 2 hours, searching everywhere
even tried this command "fastboot flash boot "C:\...\boot.img"" but nothing worked - after doing this, the ClockworkMod gave me an error that said "can't mount /sdcard"
appreciate any help

Ok , I just updated to latest version of clockwork and still can not fix "can't mount sdcard" error
I have been doing this for 6 hrs now
can someone please help me ?

dnotoco some
jimlee2 said:
Ok , I just updated to latest version of clockwork and still can not fix "can't mount sdcard" error
I have been doing this for 6 hrs now
can someone please help me ?
Click to expand...
Click to collapse
install ruu original and unlok again is the most easiest for you

ZALACAYN2 said:
install ruu original and unlok again is the most easiest for you
Click to expand...
Click to collapse
thanks for the reply
I can't find the RUU for Fido/Rogers HTC ONE S
I searched for factory every where, I made a backup before but now I can't access the SD card to see if it it still there or not

jimlee2 said:
thanks for the reply
I can't find the RUU for Fido/Rogers HTC ONE S
I searched for factory every where, I made a backup before but now I can't access the SD card to see if it it still there or not
Click to expand...
Click to collapse
Well that is a pickle. Not having a RUU to fall back on.
Good news is you can still fastboot in bootloader.
So you can try different roms until one works. So at least you have a phone that works.
Push a rom to your phone
http://forum.xda-developers.com/showthread.php?t=1667929&highlight=adb+push
Flash a boot.img
http://forum.xda-developers.com/showthread.php?t=1752270&highlight=fastboot
fixing sd card mounting
http://forum.xda-developers.com/showthread.php?t=1630459

tivofool said:
Well that is a pickle. Not having a RUU to fall back on.
Good news is you can still fastboot in bootloader.
So you can try different roms until one works. So at least you have a phone that works.
Push a rom to your phone
http://forum.xda-developers.com/showthread.php?t=1667929&highlight=adb+push
Flash a boot.img
http://forum.xda-developers.com/showthread.php?t=1752270&highlight=fastboot
fixing sd card mounting
http://forum.xda-developers.com/showthread.php?t=1630459
Click to expand...
Click to collapse
I followed all these steps but I am not able to get it fixed
is it possible to help me via google talk or something? thanks

I get this error now when I try to flash a recovery
Code:
C:\Fastboot>fastboot flash recovery op
enrecovery-twrp-2.4.1.0-ville.img
sending 'recovery' (7820 KB)... OKAY [ 1.426s]
writing 'recovery'... INFOsignature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.251s
I searched the forum and tried different methods to fix it but still no luck
I am going crazy over this problem

jimlee2 said:
I get this error now when I try to flash a recovery
Code:
C:\Fastboot>fastboot flash recovery op
enrecovery-twrp-2.4.1.0-ville.img
sending 'recovery' (7820 KB)... OKAY [ 1.426s]
writing 'recovery'... INFOsignature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.251s
I searched the forum and tried different methods to fix it but still no luck
I am going crazy over this problem
Click to expand...
Click to collapse
Where did you download that recovery from?
Sent from my Nexus 7 using Tapatalk HD

khan.orak said:
Where did you download that recovery from?
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
from the original twrp site

Ok. Are you flashing the boot. img from the extracted rom zip that you are installing. I never used the c:/ blah blah. I always put the boot.img file in the same folder as adb and fastboot then with the phone in fastboot usb type fastboot flash boot boot.img in the command prompt on the computer. It sounds like you might have a bad recovery. Have you tried to flash a new recovery?
Sent from my HTC One using xda app-developers app

CWM flashing not possible

Hey guys,
my bootloader is unlocked - so far, so good. however though, when I want to flash cwm, I'm getting this result:
C:\xyz>fastboot flash recovery cwmrecovery.img
(bootloader) Variable not supported!
target reported max download size of 31457280 bytes
sending 'recovery' (6632 KB)...
OKAY [ 0.558s]
writing 'recovery'...
OKAY [ 1.838s]
finished. total time: 2.397s
so it looks successful. But I still have the stock recovery. When I'm trying the rom manager from the playstore alternatively, I'm getting an error right aways after the cwm download (looks as if nothing happened in between). Error message is simply "An error occurred while flashing your recovery"
Any suggestions?
Thanks!

After you fastboot flash recovery, IMMEDIATELY reboot to recovery. Do not reboot to Android.
Take a backup. Then boot to Android... should stick.

Yeah, I learned that the hard way....
Sent from my SPH-D700 using Tapatalk 2

jeffreyjicha said:
Yeah, I learned that the hard way....
Sent from my SPH-D700 using Tapatalk 2
Click to expand...
Click to collapse
Weird! I had the similar issue as described above. I'm able to successfully flash the CWM flash to the SPH-710 for me. However, can't boot INITIALLY to the CWM boot; It's able to successfully go into normal boot; But Volume-UP, Center button Power button, just blinks the custom boot screen once then the screen becomes blank for some time.
Can't get out of the Stock ROM boot up to CWM;

[Q] bricked? not sure

Got a phone from a friend. Said it was bricked.
In bootloader:
*** unlocked ***
doubleshot pvt ship s-on rl
hboot-1.45.0013
microp-0353
emmc-boot
When click recovery, get 3 skateboarders and back to menu.
Tried to load a recovery:
C:\Android>fastboot flash recovery recovery-clockwork-5.0.2.7-doubleshot.img
sending 'recovery' (4754 KB)...
OKAY [ 0.888s]
writing 'recovery'...
FAILED (remote: image update error)
finished. total time: 2.348s
Received above error, should I perform another step first?

Somehow finally got cwm 5.0.2.7 into recovery.
Found this thread and did basically the same thing.
http://forum.xda-developers.com/showthread.php?t=2665472
Downloaded cm-9-1-(3-0-97)-r13.zip
Checked md5sum
Extract contents of ROM to PC(boot.img)
Put the full zip and gapps on SD card
Boot to recovery
Wipe data/factory reset, wipe cache partition
Flash ROM cm-9-1-(3-0-97)-r13.zip. Install successful.
Pulled battery, boot direct to bootloader
Flash kernel with fastboot <<<<< here I get the below error
fastboot flash boot boot.img
sending 'boot' (16384 KB)...
OKAY [ 2.624s]
writing 'boot'...
FAILED (remote: image update error)
finished. total time: 4.085s
Any suggestions?

Try miktouch or another stock based ROM so you don't need to flash kernel
Sent from my Nexus 4 using XDA Premium 4 mobile app

Is there a particular miktouch I should try? Would the below link be good to try?(for some reason having hard time finding)
"cx.com/mycx/share/jzvMU-erEeGfjBICOBql1A/MikTouch-0.7-signed.zip"
And just follow the steps and flash it vs cm9, correct?

Any stock based ROM is easier to flash as you don't need to flash the kernel afterwards through fastboot. Also cm9 is one of the few Roms I have seen issues for people when trying to flash, granted it is one of the better Roms out there, but right now you are just trying to get this working again, so stick with easy.
And I would think that's a good link, but didn't check
Sent from my Nexus 7 using XDA Premium 4 mobile app

installed miktouch 07...i installed the zip from sdcard and it installed and then it rebooted the phone. Stuck at mytouch4g logo screen, left it on this screen 20+ minutes. I took battery out and turned on with the same result.

any suggestions on trying something else?

waynebattle said:
installed miktouch 07...i installed the zip from sdcard and it installed and then it rebooted the phone. Stuck at mytouch4g logo screen, left it on this screen 20+ minutes. I took battery out and turned on with the same result.
Click to expand...
Click to collapse
What ROM were you on before? If its non stock, I would try to fastboot flash the boot.img
Sent from my Nexus 4 using Tapatalk

unfortunately got it from a friend like this, not sure what he had on it.
I flashed boot.img and this is what I received:
C:\Android>fastboot flash boot boot.img
sending 'boot' (3438 KB)...
OKAY [ 0.770s]
writing 'boot'...
FAILED (remote: image update error)
finished. total time: 2.229s
Any ideas?

waynebattle said:
unfortunately got it from a friend like this, not sure what he had on it.
I flashed boot.img and this is what I received:
C:\Android>fastboot flash boot boot.img
sending 'boot' (3438 KB)...
OKAY [ 0.770s]
writing 'boot'...
FAILED (remote: image update error)
finished. total time: 2.229s
Any ideas?
Click to expand...
Click to collapse
On some of my Linux distros I would have to use fastboot flash with a ./ before it would work.
./fasboot flash boot boot.Img
I have no idea why it was like this but it helped me a fee times on the DS. If its anything else I'd have no idea, I haven't messed with this since I sent mine off to a XDA user here.
Sent from my Nexus 4 using Tapatalk

Thanks. Not using linux, but tried .\fastboot with no difference in results. Thanks for trying. Anyone else have any other ideas?

waynebattle said:
Thanks. Not using linux, but tried .\fastboot with no difference in results. Thanks for trying. Anyone else have any other ideas?
Click to expand...
Click to collapse
You said you are able to get into recovery? Try factory resetting there

Download this 1.44.1107 S-Off PG59IMG Hboot. Rename it to PG59IMG.zip. Send it to the sdcard, and reboot into the bootloader. It will then be installed automatically. This may or may not solve the problem. Try flashing a ROM now.

abe5 said:
Download this 1.44.1107 S-Off PG59IMG Hboot. Rename it to PG59IMG.zip. Send it to the sdcard, and reboot into the bootloader. It will then be installed automatically. This may or may not solve the problem. Try flashing a ROM now.
Click to expand...
Click to collapse
dont you need to be locked to do this? i've tried "fastboot oem lock" but it has an error about too many links and the phone shuts off and it shows that it is still unlocked. I tried the PG59IMG.zip anyway and it said parsing and went right back to hboot within a second.. Flashed miktouch rom. Restarted phone, still just stuck on logo screen.

What do you see in the bootloader? Has something changed? Try flashing a recovery this time. The latest Clockworkmod should be fine. Then see what happens.

abe5 said:
What do you see in the bootloader? Has something changed? Try flashing a recovery this time. The latest Clockworkmod should be fine. Then see what happens.
Click to expand...
Click to collapse
I don't see any differences in the bootloader. Is there something specific you think may have changed.
Do you want me to try to reflash the cwm 5.0.2.7 version(currently loaded) or a different version(I didn't see a newer version for 4g slide)?

waynebattle said:
I don't see any differences in the bootloader. Is there something specific you think may have changed.
Do you want me to try to reflash the cwm 5.0.2.7 version(currently loaded) or a different version(I didn't see a newer version for 4g slide)?
Click to expand...
Click to collapse
Alright. This version: http://forum.xda-developers.com/showthread.php?t=2085842
Clockworkmod 6.0.4.6

abe5 said:
Alright. This version: http://forum.xda-developers.com/showthread.php?t=2085842
Clockworkmod 6.0.4.6
Click to expand...
Click to collapse
No luck, (md5 check sum verified) get error when try to flash it:
C:\Android>fastboot flash recovery cwm.img
sending 'recovery' (6338 KB)...
OKAY [ 1.285s]
writing 'recovery'...
FAILED (remote: image update error)
finished. total time: 2.745s

Unfortunately my friend, I believe your emmc is severally corrupt. If you are able to get adb working from within recovery you may be able to try a few more things to bring this back to life but as it stands, with s-on, you may be sol
Sent from my Nexus 7 using XDA Premium 4 mobile app

demkantor said:
Unfortunately my friend, I believe your emmc is severally corrupt. If you are able to get adb working from within recovery you may be able to try a few more things to bring this back to life but as it stands, with s-on, you may be sol
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
When you say adb working from within recovery, I am able to mount usb storage within recovery and then on pc I can do 'adb devices' and I see the device, is that what you are referring to? Thanks.

Bricked shield Tablet, fastboot only works.

Going through some of the threads here got me as far as being able to use fastboot on my bricked Shield.
I would like to ask if anyone can give me some pointers what to try next.
The previous owner tried to flash Lineage OS onto the Tablet using CWM but this failed and he probably wiped some needed partition.
I tried to flash new partitions and this works but I can not start the Shield and it won't boot into CWM. The strange thing is that I tried flashing TWRP and even though that started it did not boot through. And after a simple Shield reboot the CWM logo popped upmagain.....:confused
I was convinced I could fix this but I am beginning to think that this Tablet is a goner...
Any thoughts would ne appreciated.

What happens if you download an original recovery image from Nvidia for your model, and flashboot flash all 5 (recovery, boot, system, userdata, blob)? Do you get any fastboot errors? If the partition structure is corrupted, you'll see some sort of error message.
If the blob is messed up sometimes TWRP won't start. I suggest getting a factory image and trying again, then giving it a long time to boot. Once mine took 20 minutes at the Nvidia screen.

I did try flashing the original image from Nvidia including the other 4 images. One of the first things I tried. I woyld like to get it back to factory default. This went without issues an no errors. I might not have given it enough tine to but but still CWM seems to be on.
Will give it another try and post a screenshot.
Sent from my SM-G935F using Tapatalk

Here is a dump of the flash log. After flashing I reboot and the CWM logo pops up after a few minutes and gets stuck.
D:\Downloads\Shield Fix\Drivers\ADB FastBoot\Minimal ADB and Fastboot>fastboot flash recovery recovery.img
target reported max download size of 100663296 bytes
sending 'recovery' (9758 KB)...
OKAY [ 0.384s]
writing 'recovery'...
OKAY [ 0.320s]
finished. total time: 0.709s
D:\Downloads\Shield Fix\Drivers\ADB FastBoot\Minimal ADB and Fastboot>fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.394s]
booting...
OKAY [ 0.017s]
finished. total time: 0.417s

Think it is done for, after flashing TWRP numerous times it let me get to the start screen for TWRP it then hangs. When you reboot the Shield and want to go to the recovery again you get the dead android.
PS. I can sometimes get into TWRP but it fails on everything I do. Would there be a terminal solution for this? Like re-creating partitions?

Unlock your bootloader?
Sent from my ZTE A2017U using Tapatalk

It is already unlocked I am afraid.
Sent from my SM-G935F using Tapatalk

sn0r said:
It is already unlocked I am afraid.
Sent from my SM-G935F using Tapatalk
Click to expand...
Click to collapse
Try to flash the attached file. Remember to unzip it first! Flash with:
"fastboot flash dtb tegra124-tn8-p1761-1270-a04-e-battery.dtb"

Flashed the battery file and did another flash of NVIDIA's recovery image and even-tough it says everything is flashed correctly when I reboot I get the CWM logo and nothing more. When I do get into TWRP and try to flash a ROM I get messages errors like attached.

sn0r said:
Flashed the battery file and did another flash of NVIDIA's recovery image and even-tough it says everything is flashed correctly when I reboot I get the CWM logo and nothing more. When I do get into TWRP and try to flash a ROM I get messages errors like attached.
Click to expand...
Click to collapse
Then my guess would be some problems with the internal storage which may not be repairable.

Using fastboot try the following
Fastboot erase cache
Fastboot format cache
Fastboot format userdata
Make sure your tablet is in bootloader mode first though.
Sent from my pa_osprey using Tapatalk