Database Develop

help, update, now stuck on android flash screen(fastboot?)

can anyone tell me if they know how to push a update through fastboot? i just did a update and nandroid isnt working, so can anyone provide help on doing a push through fastboot?
errors i get trying to re apply update.zip of jf1.5
the original rc29file? what should i do?
cmd error
Code:
Microsoft Windows [Version 6.0.6001]
Copyright (c) 2006 Microsoft Corporation. All rights reserved.
C:\Users\Kiefer Anderson>cd desktop
C:\Users\Kiefer Anderson\Desktop>cd fastboot
C:\Users\Kiefer Anderson\Desktop\fastboot>fastboot flashall update.zip
error: neither -p product specified nor ANDROID_PRODUCT_OUT set
C:\Users\Kiefer Anderson\Desktop\fastboot>fastboot update update.zip
archive does not contain 'boot.sig'
archive does not contain 'recovery.img'
archive does not contain 'system.img'
error: update package missing system.img
C:\Users\Kiefer Anderson\Desktop\fastboot>fastboot update {update.zip}
error: failed to load '{update.zip}'
C:\Users\Kiefer Anderson\Desktop\fastboot>fastboot update update.zip
archive does not contain 'android-info.txt'
archive does not contain 'android-product.txt'
error: update package has no android-info.txt or android-product.txt
C:\Users\Kiefer Anderson\Desktop\fastboot>fastboot update {update.zip}
error: failed to load '{update.zip}'
C:\Users\Kiefer Anderson\Desktop\fastboot>
I tried two different update files, one i added the two .txt files then it asks for the img files, i dont get it.. anyone HELP plzzzzz, if you help ill donate money to your paypal i swear

why dont you just do it through the recovery ?
To mount the sdcard in recovery type the following in adb
echo /dev/block/mmcblk0 > /sys/devices/platform/usb_mass_storage/lun0/file
thanks to JesusFreke for figuring this out.

dpgc213 said:
why dont you just do it through the recovery ?
Click to expand...
Click to collapse
i dont have anything to connect my phone to another usb device..
im not very good at this stuff, but for some reason im stuck at the android loading screen, i think theres something wrong with the 2nd loading screen, idk what to do, i tried doing recovery with nandroid but i get an error, then i tried re apllying the update.zip file and still something wrong, im stuck and need help
so to do recovery, i do home + end button, which brings up everything right? alt stuff..
so what do i do from there, im sorry, but i fyou help me through this, ill do anything.. how do i enter those commands in the recovery?

1. fastboot doesn't work on recovery update zips. It is used on images made from nandroid backup (or img files made from building the source). In other words, fail.
2. Dev forum is not for troubleshooting.

u can mount your phone to your computer in recovery mode but using the code in my above post

dpgc213 said:
u can mount your phone to your computer in recovery mode but using the code in my above post
Click to expand...
Click to collapse
Microsoft Windows [Version 6.0.6001]
Copyright (c) 2006 Microsoft Corporation. All rights reserved.
C:\Users\Kiefer Anderson>echo /dev/block/mmcblk0 > /sys/devices/platform/usb_mas
s_storage/lun0/file
The system cannot find the path specified.
C:\Users\Kiefer Anderson>
still cant figure it out.. im in recovery mode, i did that echo thing, but yeh..
when i had my phone working and connected, it would connect as f:/ sooo what do i do

press alt x and then type that in on the phone

dpgc213 said:
press alt x and then type that in on the phone
Click to expand...
Click to collapse
hmm didnt work, i just get a
"
/ #
"
didnt work i dont think :/
i dont see my sdcard connected, ill try again

not sure then sorry, u sure u copied exactly how it is? or maybe u hav to type su 1st, not sure tho

dpgc213 said:
not sure then sorry, u sure u copied exactly how it is? or maybe u hav to type su 1st, not sure tho
Click to expand...
Click to collapse
uhm in device manager its connected as HTC dream instead of mass usb
gonna try both thanks for helping, if i figure this out, ill be contacting you
gonna cry now
lol sh: su: not found
so su not working idk

ok i got my dads phone, gonna try re installing jf 1.5 i hope it works :/
EDIT update
im sorry to bother you guys, i just want to say thanks for trying to help, withouut you i would be no where, i might of just went in my closet and cryed myself to death..
used my dads nokia to help
thanks guys

Can i Mount Nexus s without enabling USB debugger from Phone(as I cant go past google logo on nexus s)

jashsu said:
1. fastboot doesn't work on recovery update zips. It is used on images made from nandroid backup (or img files made from building the source). In other words, fail.
2. Dev forum is not for troubleshooting.
Click to expand...
Click to collapse
So you can only use the .img files from AndroidSDK to update in fastboot? Im trying to fix an HTC G2 Vision (T-Mobile) for a friend, it doesnt boot and is NOT rooted, it will not seem to accept any official T-Mobile update or any i try to push or flash through fastboot. I have the nandroid backup images from another HTC G2 Vision (both phones stock rom) as well as the official T-Mobile updates yet they wont flash through fastboot or Hboot, ADB wont recognize it,fastboot will, i get failed to verify whole-file signature on most updates, but have gotten Main Version is older! mesage from 1 of the OTA updates i got from T-Mobile, and one that said something like failed to stat sytem/build.prop no such file or directory E:error in /tmp/sideload/package.zip (status7) everytime i boot her phone into recovery i get E:set_bootloader_message_block: emmc_read_data_fail! I thought if i could reflash bootimg or hboot or flashall i could fix it? am i wrong in this aassupmtion? I have reached out over half a dozen sites/forums for help and have not got any real help, if anyone can assist id appreciate it, u can alway pm me instead of dirtying the thread, Thank you!
C:\Users\roger>C:\AndroidSDk\tools\fastboot flash boot C:\AndroidSDK\tools\boot.img
sending 'boot' (2560 KB)...
OKAY [ 0.446s]
writing 'boot'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 0.770s

IVXX said:
So you can only use the .img files from AndroidSDK to update in fastboot? Im trying to fix an HTC G2 Vision (T-Mobile) for a friend, it doesnt boot and is NOT rooted, it will not seem to accept any official T-Mobile update or any i try to push or flash through fastboot. I have the nandroid backup images from another HTC G2 Vision (both phones stock rom) as well as the official T-Mobile updates yet they wont flash through fastboot or Hboot, ADB wont recognize it,fastboot will, i get failed to verify whole-file signature on most updates, but have gotten Main Version is older! mesage from 1 of the OTA updates i got from T-Mobile, and one that said something like failed to stat sytem/build.prop no such file or directory E:error in /tmp/sideload/package.zip (status7) everytime i boot her phone into recovery i get E:set_bootloader_message_block: emmc_read_data_fail! I thought if i could reflash bootimg or hboot or flashall i could fix it? am i wrong in this aassupmtion? I have reached out over half a dozen sites/forums for help and have not got any real help, if anyone can assist id appreciate it, u can alway pm me instead of dirtying the thread, Thank you!
C:\Users\roger>C:\AndroidSDk\tools\fastboot flash boot C:\AndroidSDK\tools\boot.img
sending 'boot' (2560 KB)...
OKAY [ 0.446s]
writing 'boot'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 0.770s
Click to expand...
Click to collapse
http://forum.xda-developers.com/forumdisplay.php?f=508
try the G2 forum
Make a new topic there

[How-To] Unbrick HTC Tattoo(CLICK) after bad recovery

Hello all,
PROBLEM
I while ago I had flashed my tattoo with a ROM that came with ROMmanager (wich is able to flash a custom recovery within Android) and the result was that my recovery was corupted and I couldn't flash another rom anymore, since I have a locked SPL.
POSSIBLE SOLUTION
What you can try is to download the latest RUU for your device and try to update the tattoo. However, I know that alot of people will get the error code 170 or 171: USB not connected. Don't panic, I have found after so many days of searching the solution to this problem.
WHAT WILL YOU NEED ?
The correct RUU for your device forum.xda-developers.com/showthread.php?t=591746"]
Procmon, this is a Process Monitor. You will need this to extract the rom.zip file from the RUU. technet.microsoft.com/en-us/sysinternals/bb896645.aspx"]
The android SDK and ADB set up correctly ( just search it on Google, and you'll find it).
LETS GET STARTED
The first thing you'll need to do is to open your prefered RUU you just downloaded from the link above, and wait till it says "welcome to the htc update..."
Just click next once, and leave the RUU open.
NOTE: The RUU can't be minimalized, so I sugest to slide it down to the taskbar.
Next, open the Procmon application, it will show you all open tasks (don't start searching like a fool, there are too many processes running to find the file we're searching for!).
Still in the Procmon, search in the for a filter button (the sixth button, white with a bleu thing above it), and click on it, now there will popup a screen.
Change the first tab (Architecture) to Path, and the seccond one (is) to contains, then in the box type rom.zip, and leave the Include tab how it is.
Now press add, and then press apply and ok. And search to one of the path's that ends with rom.zip in the list.
Right-click on it, and select Jump To, now you will see the rom.zip file in a temporary windows folder. Copy the rom to whereever you want (e.g. on your desktop) and close the RUU and Process Monitor.
Now, we have found and extracted the original rom that comes with the tattoo, so we're ready to flash this rom manually to our tattoo:
Open up command prompt, and cd to adb (where you have installed the SDK).
Now connect the tattoo to your pc and make sure its recognized under ADB Devices in device manager in windows.
Go back to the command prompt, and type
Code:
adb devices
If ADB is setup how it should, then you'll see the tattoo there (a long number)
Now type:
Code:
adb shell
adb reboot oem-78
The tattoo is now going to reboot in RUU mode, so we can do fastboot commands. (You will see only HTC logo on the tattoo)
Copy the rom.zip you extracted from the RUU to the tools folder of your SDK.
Now type:
Code:
fastboot flash zip rom.zip
(rom.zip is the name of your extracted rom, if you renamed it, then use the name of your rom).
Wait for the flashing procedure to finish, you'll see some message of completed or done or something, and unplug your tattoo, it should be in the bootloader screen (with 3 skateboards) and in the middle you should see RUU in orange.
Reboot your device, and hold the HOME + END button till the tattoo screen comes up, and wait till you see a screen with an exlimation mark, now shortly press on the HOME+END butten and you should be able to see the recovery menu now!
OPTIONAL
Redoo the 'root the tattoo in one click', and you'll get a custom recovery and root acces. IF YOU DO SO, I STRONGLY RECOMMEND YOU TO FLASH ANOTHER CUSTOM RECOVERY TO THE TATTOO, JUST SEARCH ONE ON THE FORUM HERE AND YOU'LL ALSO FIND HOW TO DO SO TROUGH ADB COMMANDS.
Once you have a custom recovery, you can flash rom's again from the recovery.
Hope this tread was helpfull !

Very usefull tnx
Sent from my Tattoo using XDA App

Now I'm even less afraid of flashing my a.. of. :-D
Thanx man!
Sent from my Tattoo using Tapatalk

MOdel ID checl Failed
Hi ,
I am getting this error
C:\androidtools\tools>fastboot flash zip "C:\My Folder\Datas\Mobile\Tattoo\rom.z
ip"
sending 'zip' (88968 KB)... OKAY [ 12.422s]
writing 'zip'... INFOadopting the signature contained in this i
mage...
INFOsignature checking...
INFOzip header checking...
INFOzip info parsing...
INFOchecking model ID...
FAILED (remote: 41 model id check fail)
finished. total time: 40.079s
C:\androidtools\tools>

soulaiman said:
Hello all,
PROBLEM
I while ago I had flashed my tattoo with a ROM that came with ROMmanager (wich is able to flash a custom recovery within Android) and the result was that my recovery was corupted and I couldn't flash another rom anymore, since I have a locked SPL.
POSSIBLE SOLUTION
What you can try is to download the latest RUU for your device and try to update the tattoo. However, I know that alot of people will get the error code 170 or 171: USB not connected. Don't panic, I have found after so many days of searching the solution to this problem.
WHAT WILL YOU NEED ?
The correct RUU for your device forum.xda-developers.com/showthread.php?t=591746"]
Procmon, this is a Process Monitor. You will need this to extract the rom.zip file from the RUU. technet.microsoft.com/en-us/sysinternals/bb896645.aspx"]
The android SDK and ADB set up correctly ( just search it on Google, and you'll find it).
LETS GET STARTED
The first thing you'll need to do is to open your prefered RUU you just downloaded from the link above, and wait till it says "welcome to the htc update..."
Just click next once, and leave the RUU open.
NOTE: The RUU can't be minimalized, so I sugest to slide it down to the taskbar.
Next, open the Procmon application, it will show you all open tasks (don't start searching like a fool, there are too many processes running to find the file we're searching for!).
Still in the Procmon, search in the for a filter button (the sixth button, white with a bleu thing above it), and click on it, now there will popup a screen.
Change the first tab (Architecture) to Path, and the seccond one (is) to contains, then in the box type rom.zip, and leave the Include tab how it is.
Now press add, and then press apply and ok. And search to one of the path's that ends with rom.zip in the list.
Right-click on it, and select Jump To, now you will see the rom.zip file in a temporary windows folder. Copy the rom to whereever you want (e.g. on your desktop) and close the RUU and Process Monitor.
Now, we have found and extracted the original rom that comes with the tattoo, so we're ready to flash this rom manually to our tattoo:
Open up command prompt, and cd to adb (where you have installed the SDK).
Now connect the tattoo to your pc and make sure its recognized under ADB Devices in device manager in windows.
Go back to the command prompt, and type
Code:
adb devices
If ADB is setup how it should, then you'll see the tattoo there (a long number)
Now type:
Code:
adb shell
adb reboot oem-78
The tattoo is now going to reboot in RUU mode, so we can do fastboot commands. (You will see only HTC logo on the tattoo)
Copy the rom.zip you extracted from the RUU to the tools folder of your SDK.
Now type:
Code:
fastboot flash zip rom.zip
(rom.zip is the name of your extracted rom, if you renamed it, then use the name of your rom).
Wait for the flashing procedure to finish, you'll see some message of completed or done or something, and unplug your tattoo, it should be in the bootloader screen (with 3 skateboards) and in the middle you should see RUU in orange.
Reboot your device, and hold the HOME + END button till the tattoo screen comes up, and wait till you see a screen with an exlimation mark, now shortly press on the HOME+END butten and you should be able to see the recovery menu now!
OPTIONAL
Redoo the 'root the tattoo in one click', and you'll get a custom recovery and root acces. IF YOU DO SO, I STRONGLY RECOMMEND YOU TO FLASH ANOTHER CUSTOM RECOVERY TO THE TATTOO, JUST SEARCH ONE ON THE FORUM HERE AND YOU'LL ALSO FIND HOW TO DO SO TROUGH ADB COMMANDS.
Once you have a custom recovery, you can flash rom's again from the recovery.
Hope this tread was helpfull !
Click to expand...
Click to collapse
If this post does what it says it does, it should maybe be made a sticky so that everyone who bricks their device knows EXACTLY what to do to fix it.........

This metod work,excelent

nkaderfe said:
Hi ,
I am getting this error
C:\androidtools\tools>fastboot flash zip "C:\My Folder\Datas\Mobile\Tattoo\rom.z
ip"
sending 'zip' (88968 KB)... OKAY [ 12.422s]
writing 'zip'... INFOadopting the signature contained in this i
mage...
INFOsignature checking...
INFOzip header checking...
INFOzip info parsing...
INFOchecking model ID...
FAILED (remote: 41 model id check fail)
finished. total time: 40.079s
C:\androidtools\tools>
Click to expand...
Click to collapse
Hmm, seems like adb can't verify the model of your phone. Try a different ROM or Reinstall the sdk tools. If that doesn't make sense, then try to recreate your goldcard, but I don't think that that would make some difference at all.

soulaiman said:
WHAT WILL YOU NEED ?
The correct RUU for your device forum.xda-developers.com/showthread.php?t=591746"]
Procmon, this is a Process Monitor. You will need this to extract the rom.zip file from the RUU. technet.microsoft.com/en-us/sysinternals/bb896645.aspx"]
The android SDK and ADB set up correctly ( just search it on Google, and you'll find it).
Click to expand...
Click to collapse
Well, the rom.zip is always located in %tmp% (Start->run->%tmp% and then enter). Search the folders and somewhere you will find the rom.zip then...procmon is a little over-engineered
nkaderfe said:
Hi ,
I am getting this error
C:\androidtools\tools>fastboot flash zip "C:\My Folder\Datas\Mobile\Tattoo\rom.z
ip"
sending 'zip' (88968 KB)... OKAY [ 12.422s]
writing 'zip'... INFOadopting the signature contained in this i
mage...
INFOsignature checking...
INFOzip header checking...
INFOzip info parsing...
INFOchecking model ID...
FAILED (remote: 41 model id check fail)
finished. total time: 40.079s
C:\androidtools\tools>
Click to expand...
Click to collapse
Then you have a vendor specific build - Vodafone? Orange? You have to flash this in order to get the flashing started...
/EDIT: Did u create a goldcard?

Getting stuck.
When I type adb shell it responds with: -exec '/system/bin/sh' failed: No such file or directory <2> -
adb reboot oem-78
fastboot flash zip rom.zip
<waiting for device>
My phone is plugged in but doesn't want to boot past tattoo screen.
Plz help if you know the problem.

timlambo said:
Getting stuck.
When I type adb shell it responds with: -exec '/system/bin/sh' failed: No such file or directory <2> -
adb reboot oem-78
fastboot flash zip rom.zip
<waiting for device>
My phone is plugged in but doesn't want to boot past tattoo screen.
Plz help if you know the problem.
Click to expand...
Click to collapse
Hi,
You have to boot your phone first in bootloader mode, to do so you have to pull out battery, put it back in, hold in the down volume button while pressing power, it wil bring you in a white screen with at the bottom three androids on skeatboards.
Hope this helps you.

soulaiman said:
Hi,
You have to boot your phone first in bootloader mode, to do so you have to pull out battery, put it back in, hold in the down volume button while pressing power, it wil bring you in a white screen with at the bottom three androids on skeatboards.
Hope this helps you.
Click to expand...
Click to collapse
I know. That is where I were. I think the problem were with my rom, found old backup om pc and restored to that, but now it is working again.
Thanks for the help.

Nexus ONE bricked?

Phone unlocked
Clockwork mod installed and working
Phone stucks at boot - i think /system partition has no data
No nandroid backups in sdcard
no adb shell
no adb, only fastboot
when i try fastboot flash system system.img, i get this error
C:\android-sdk-windows\tools>fastboot flash system system.img
sending 'system' (155194 KB)...
OKAY [ 24.396s]
writing 'system'...
FAILED (remote: Write Fail)
finished. total time: 24.401s
Anyone can help me?
Thanks

Amritttt said:
Phone unlocked
Clockwork mod installed and working
Phone stucks at boot - i think /system partition has no data
No nandroid backups in sdcard
no adb shell
no adb, only fastboot
when i try fastboot flash system system.img, i get this error
C:\android-sdk-windows\tools>fastboot flash system system.img
sending 'system' (155194 KB)...
OKAY [ 24.396s]
writing 'system'...
FAILED (remote: Write Fail)
finished. total time: 24.401s
Anyone can help me?
Thanks
Click to expand...
Click to collapse
Is your bootloader unlocked?

if you have working clockworkmod, then just flash a rom from clockworkmod recovery.

yes bootloader is unlocked and at the moment my phone does not go beyond "X" but it goes in bootloader mode and recovery i have tried both the recoveries.rom is not flashing

Go to www.shipped-roms.com and download the frg33 shipped rom. Extract the zip within the zip and rename it PASSIMG.zip. Place it in the root of your sdcard and boot into the boatloader.
Sent from my Nexus One using XDA Premium App

Or download cm7 and let the fireworks begin
Sent from my Nexus One using XDA Premium App

From past experience if you can get to recovery your phone is not bricked. You need to download a rom from off these forums. Download CM7 and flash it

Bootloader is not detecting the passimg and I have tried cm 7 and the stock to flash through recovery after flashing it gives me a weird error:
E:cant symlink /system/dumpcrash Error
Sent from my Nexus S using XDA Premium App

Looks like your internal memory has crashed. I'll get back to you when i have more details.

Amritttt said:
Bootloader is not detecting the passimg and I have tried cm 7 and the stock to flash through recovery after flashing it gives me a weird error:
E:cant symlink /system/dumpcrash Error
Sent from my Nexus S using XDA Premium App
Click to expand...
Click to collapse
Try the newer shipped rom from here: http://forum.xda-developers.com/showthread.php?t=1059116
Rename to PASSIMG.zip and place on the root of your sdcard.

efrant said:
Try the newer shipped rom from here: http://forum.xda-developers.com/showthread.php?t=1059116
Rename to PASSIMG.zip and place on the root of your sdcard.
Click to expand...
Click to collapse
no my bootloader is not even flashing this rom

Amritttt said:
no my bootloader is not even flashing this rom
Click to expand...
Click to collapse
Could you give us some more details? When you place the renamed PASSIMG.zip file in the root directory of your sdcard and boot into the bootloader, what happens? Does it search for a PASSIMG file? Does it give you an error? What?

efrant said:
Could you give us some more details? When you place the renamed PASSIMG.zip file in the root directory of your sdcard and boot into the bootloader, what happens? Does it search for a PASSIMG file? Does it give you an error? What?
Click to expand...
Click to collapse
When i restart phone it go to fastboot usb then i press power button and the phone goes in bootloader mode "HBOOT"
When i m in hboot it scans my memory card
sd card checking
[loading Passimg.zip]
no image
no image or wronge image

Amritttt said:
When i restart phone it go to fastboot usb then i press power button and the phone goes in bootloader mode "HBOOT"
When i m in hboot it scans my memory card
sd card checking
[loading Passimg.zip]
no image
no image or wronge image
Click to expand...
Click to collapse
Are you renaming the image to PASSIMG.zip (using the correct case), and not PASSIMG.zip.zip?

efrant said:
Are you renaming the image to PASSIMG.zip (using the correct case), and not PASSIMG.zip.zip?
Click to expand...
Click to collapse
yes i m renamed it as passimg not passimg.zip

well if u want i could send u a nandroid from my n1 and u could try restoring that (as long as u delete the contacts straight away) although i dont know if that works or not anyway.

send me if u can that will be really helpfull and no worries mate i wont mess around with ur contacts i will delete it asap if u want i will click a picture while deleting it

Right I can get back to my computer later tonight to send u it. Sorry for the delay.

Change your sdcard. Some sdcards can't read passimg.
Sent from my Nexus One using XDA Premium App

Sorry!
addam360 said:
Right I can get back to my computer later tonight to send u it. Sorry for the delay.
Click to expand...
Click to collapse
Right sorry once again I've had no access to my computer but if you still need the nandroid I'm on now so just message me or something and ill arrange you getting it.

[REQ] 10.1 System Dump (.img)

Hi,
Could someone please dump a system image for the 10.1? It's reeeealy easy
There are a few soft-bricks already due to people flashing the wrong image or to the wrong partition ( you know who you are, people! ) and you would be doing them a massive favour if you did.
If you already have busybox, all you have to do is run this:
Code:
dd if=/dev/block/mmcblk0p4 of=/sdcard/system.img
Then you can pick it up the system.img from /sdcard
Code:
adb pull /sdcard/system.img
ZIP it and upload it somewhere ( Dropbox ) and you're done!
TIA
BC

Http://droidbasement.com/galaxy/sys-backup
The system_extra backup contains extra stuff (from the 'tools' compilation).

Thanks. There are a couple of people who will really appreciate that
OT: I just repacked your su/busybox update with the boot.img from the Voda 10.1 and it works fine. Link to the Voda boot.img is here

Would it be possible to get the original system image without the extra tools? I am trying to flash this image however I keep getting a remote error when I do so. Could it have something to do with the fact that this image is 600MB compared to other system images that are around 200 MB like for the gt 10.1v? Thanks again for posting it.

the extra stuff is not making it 600mb (maybe 10-20). It is quite big on the IO.
In order to fastboot flash it you must have an unlocked bootloader to do so (which in unlocked by default on the IO).

Ok so my bootloader is unlock however every time I try flashing this image i get the following:
sending 'system' (591872 KB)...
FAILED (remote: (00000006))
finished. total time: 0.002s
I am able to flash other system images no problem however, this one seems to be giving me some issues. Any other ideas to flash this image successfully? Thanks.

nadewad said:
Ok so my bootloader is unlock however every time I try flashing this image i get the following:
sending 'system' (591872 KB)...
FAILED (remote: (00000006))
finished. total time: 0.002s
I am able to flash other system images no problem however, this one seems to be giving me some issues. Any other ideas to flash this image successfully? Thanks.
Click to expand...
Click to collapse
ill retake the dump and upload it. ill do it tonight. maybe some corruption ocurred, etc.

It might be the same trick where you have to create a sparse ext4 image instead of ripping the image straight, because fastboot transfers the entire image in RAM before flashing it...
Try
Code:
make_ext4fs -l 512m -s /sdcard/system.img /system

If anyone has created a system image but isn't quite sure if it is the correct one, I'll be glad to try it out as I am one of those people who soft bricked their device. Just PM me and I'll be more than happy to flash my device and verify the stability of the system image. Thanks.
Nader

bump? Did anyone end up getting a system image? Thanks.
Nader

Ok so I was able to get a hold of another system image however, it still failed with the same error.
ydaraishy mentioned something about using make_ext4fs to make a sparse image? How is this done exactly? Is this through the adb shell or is this a separate tool that can be used on a linux machine. Any help on bringing my device back to life would be greatly appreciated. Thanks.

nadewad said:
Ok so I was able to get a hold of another system image however, it still failed with the same error.
ydaraishy mentioned something about using make_ext4fs to make a sparse image? How is this done exactly? Is this through the adb shell or is this a separate tool that can be used on a linux machine. Any help on bringing my device back to life would be greatly appreciated. Thanks.
Click to expand...
Click to collapse
Run it on the device instead of using dd on the device.

ydaraishy said:
Run it on the device instead of using dd on the device.
Click to expand...
Click to collapse
He has a soft-bricked device so that's not an option unfortunately.
You can do a MD5 checksum of the file and get pershoot to check it against the original.
Otherwise, in the mean time, you can try this tool:
http://www.diskinternals.com/download/
You want the tool called "Linux Reader 2.0". It says it can only read ext2 and ext3, but I just tried it on my 10.1v system image which I created using the same method as pershoot, and it works fine.
...and see if you can mount it in Windows. If you can, the image is (probably) OK.

bcmobile said:
He has a soft-bricked device so that's not an option unfortunately.
Click to expand...
Click to collapse
Well, obviously, someone _else_ has to provide that image from a working device.

Same error here, while trying to flash the system.img. Any alternatives?
Thanks,
Eduardo.

I just received another system image from a friend of mine who created it using make_ext4fs. It does flash successfully however, it still leaves my device in a boot loop. Whats the button combination to get the device into recovery mode?
I find it funny that the boot, recovery and system images for the galaxy tab 10.1v actually work and the device runs. Although the accelerometer, camera and usb don't work though.
Eduardo if you would like, you can PM me and I can share with you the dropbox folder of the system image that actually flashed to see if it would work on your device.
I think at this point I may just throw in the towel and send my device back to Samsung to get repaired :/
Thanks to everyone on the xda forums who tried helping me out. You guys are truly awesome

nadewad said:
I just received another system image from a friend of mine who created it using make_ext4fs. It does flash successfully however, it still leaves my device in a boot loop. Whats the button combination to get the device into recovery mode?
I find it funny that the boot, recovery and system images for the galaxy tab 10.1v actually work and the device runs. Although the accelerometer, camera and usb don't work though.
Eduardo if you would like, you can PM me and I can share with you the dropbox folder of the system image that actually flashed to see if it would work on your device.
I think at this point I may just throw in the towel and send my device back to Samsung to get repaired :/
Thanks to everyone on the xda forums who tried helping me out. You guys are truly awesome
Click to expand...
Click to collapse
Samsung may charge you for the repair
Before you send it back, just have one more go at flashing the boot.img which smaskell provided from here. Just do a:
Code:
fastboot flash boot boot.img
The boot loop may be due to a different (incompatible) kernel if you still have the boot partition from the 10.1v
Failing that, if you're still up for it, do a:
Code:
adb logcat > %userprofile%\desktop\logcat-out.txt
...then open the locgat-out.txt file on your desktop and post the contents here or just zip and attach the file. That might give us something to work with

I am also not able to flash this system.img file. I get the same error.

I did remember to flash the boot image of the 10.1 over the 10.1v. However, even when the device is booting up I still can't get access to the adb shell. Any ideas as to why I cannot access the adb shell?
I did notice though that when I had typed in:
fastboot getvar product
It had returned GT-P7100 which is the product number for the Galaxy Tab 10.1v, however the Galaxy Tab 10.1 has the product number GT-P7510.
Could this be because I had accidentally flashed the 10.1v rom or that these devices both use the same version of fastboot etc?

nadewad said:
I did remember to flash the boot image of the 10.1 over the 10.1v. However, even when the device is booting up I still can't get access to the adb shell. Any ideas as to why I cannot access the adb shell?
I did notice though that when I had typed in:
fastboot getvar product
It had returned GT-P7100 which is the product number for the Galaxy Tab 10.1v, however the Galaxy Tab 10.1 has the product number GT-P7510.
Could this be because I had accidentally flashed the 10.1v rom or that these devices both use the same version of fastboot etc?
Click to expand...
Click to collapse
My tablet is showing P7100 as well. I tested with my employee's GT LE, and it shows the same. So, this is not the problem...
adb is not accessible to me as well.

help please !!

i posted this thread in the Development section
http://forum.xda-developers.com/showthread.php?t=1315953
I need some help and suggestions regarding this thread
Thanks in advance

santhoshpirate said:
i posted this thread in the Development section
http://forum.xda-developers.com/showthread.php?t=1315953
I need some help and suggestions regarding this thread
Thanks in advance
Click to expand...
Click to collapse
OK I found this thread yesterday for creating a goldcard using adb commands. Maybe it can help you get the goldcard created. In looking at your getvar values, you have the right RUU/ROM that you are attempting to flash.
http://forum.xda-developers.com/showpost.php?p=18748766&postcount=6
The only other thing that was mentioned in that thread was did you follow the instructions completely.
Here are the series of commands you need to try:
fastboot oem rebootRUU
fastboot erase cache
fastboot flash zip [path to ROM.zip]
fastboot reboot

i tried but im unable to hav a gold card and flash through RUU also didnt work

santhoshpirate said:
i tried but im unable to hav a gold card and flash through RUU also didnt work
Click to expand...
Click to collapse
What happen when you tried that method to create the goldcard?
What messages did you get trying to Fastboot flash the ROM.zip?
You keep asking for help but you are not giving us a lot of information to work with.

tpbklake said:
What happen when you tried that method to create the goldcard?
What messages did you get trying to Fastboot flash the ROM.zip?
You keep asking for help but you are not giving us a lot of information to work with.
Click to expand...
Click to collapse
Ya,so true...keep seeing his post,we need more information to be able to help..
Sent from my HTC Incredible S using Tapatalk

tpbklake said:
What happen when you tried that method to create the goldcard?
What messages did you get trying to Fastboot flash the ROM.zip?
You keep asking for help but you are not giving us a lot of information to work with.
Click to expand...
Click to collapse
Im unable to boot my phone to install goldcard helper to create the goldcard
C:\Users\Sumo the Rider>fastboot flash zip C:\PG32IMG.zip
sending 'zip' (261186 KB)... OKAY [ 44.011s]
writing 'zip'... INFOadopting the signature contained in this i
mage...
INFOsignature checking...
INFOzip header checking...
INFOzip info parsing...
INFOchecking model ID...
INFOchecking custom ID...
FAILED (remote: 42 custom id check fail)
finished. total time: 91.077s
I get the above info when i try to flash the zip using FASTBOOT

tpbklake said:
OK I found this thread yesterday for creating a goldcard using adb commands. Maybe it can help you get the goldcard created. In looking at your getvar values, you have the right RUU/ROM that you are attempting to flash.
http://forum.xda-developers.com/showpost.php?p=18748766&postcount=6
The only other thing that was mentioned in that thread was did you follow the instructions completely.
Here are the series of commands you need to try:
fastboot oem rebootRUU
fastboot erase cache
fastboot flash zip [path to ROM.zip]
fastboot reboot
Click to expand...
Click to collapse
santhoshpirate said:
Im unable to boot my phone to install goldcard helper to create the goldcard
C:\Users\Sumo the Rider>fastboot flash zip C:\PG32IMG.zip
sending 'zip' (261186 KB)... OKAY [ 44.011s]
writing 'zip'... INFOadopting the signature contained in this i
mage...
INFOsignature checking...
INFOzip header checking...
INFOzip info parsing...
INFOchecking model ID...
INFOchecking custom ID...
FAILED (remote: 42 custom id check fail)
finished. total time: 91.077s
I get the above info when i try to flash the zip using FASTBOOT
Click to expand...
Click to collapse
Check out the thread post above ^^^^^^^. attn1 has a goldcard app and script that can be run using adb commands. You don't have to use the Goldcard Helper app. Just boot your phone into bootloader mode and then you should be able to run the script from a cmd window on your PC.

tpbklake said:
Check out the thread post above ^^^^^^^. attn1 has a goldcard app and script that can be run using adb commands. You don't have to use the Goldcard Helper app. Just boot your phone into bootloader mode and then you should be able to run the script from a cmd window on your PC.
Click to expand...
Click to collapse
=.=, true, he totally ignore what you said, continue to do what he want and complaint that he unable to proceed....
Try the method attn1 provided, it should be able to help you create gold card without using gold card helper.

Hi guys thnx for all the help
My phone is now working and s-on
Really thnx!
Sry for responding late i had exams!
I apologize to you guys for not giving you the correct info about my process, because im a learner!