Database Users

[Solved] NEED HELP! Bricked? No SDcard in Recovery - no Restore - no adb

Hi all!
I have a big problem...
My Hero wan't boot so I go in the Recovery Console.
But if i want to restore a Backup this message appears:
E:Can't mount /dev/block/mmcblk0p1 (or /dev/block/mmcblk0)
E: Can't mount SDCARD:
I tried several SDCARDs... same message.
I've wiped all several times. Reformat the SDCARD...
Access via ADB brings:
error: device not found
Fastboot mode is possible... but
fastboot boot cm-hero-recovery.img
in the konsole brings: "downloading 'boot.img'... FAILED (remote: not allow)"...
What can i do?

This might help?.....
http://forum.xda-developers.com/showthread.php?t=681583
then go to .....
http://android.modaco.com/content-page/299174/no-adb-no-sd/page/80/

Thanks for the links...
I could re-flash the T-Mobile ROM (2.73.111.26)... The Hero starts and now it works with Android 1.5 ...
I have access to the SDCARD ... but the USB Connectivity doesn't work...
No ADB and no storage Device in Windows...
"fastboot oem eraseconfig" doesn't work... think about the false HBOOT (HBOOT-1.76.0007)...
flashrec also doesn't work... there comes "Flash FAILED: could not run command"
Any ideas?

Had exactly the same.
Forget about the rom, it doesn't matter (i.e. flash whatever you like).
You already got your SD card support back, for the rest you need to update the SPL (search for an unlocked version for your hero, double-check because it can _really_ brick your device if this fails). After that fastboot oem eraseconfig works and your usb is back to normal.
Did that yesterday, worked like a charm and actually makes sense (unlike other suggestions like "reflash N times", "unplug and replug usb or change the cable" and "send in for service"). Your USB is fine (as seen in fastboot), it's just not working after your kernel booted -> Due to messed up configuration parameters in the flash area. Basically the kernel commandline, if you will..

Wich version of SPL I do you flash?
How do you flash it? Like...
fastboot oem rebootRUU
fastboot flash zip SPL_image.zip
in the fastboot konsole?
RecoveryConsole is not useable to me... My Hero is not rooted anymore... And it seems to be very difficult to get root again :-/

What do you mean by?
Swerner1975 said:
I have access to the SDCARD ... but the USB Connectivity doesn't work...
Click to expand...
Click to collapse
According to BTDAGs guide, flashing 2.73.61.5 should enable you to use flashrec to do the custom recovery again.

[solved] NEED HELP! Bricked? No SDcard in Recovery - no Restore - no adb
Thanks for your help. I have solved the problems...
- first I flashed the T-Mobile D ROM like described in the Link (extract rom.zip and flash)
http://android.modaco.com/content-page/299174/no-adb-no-sd/page/80/
- then I have detected, that flashrec does'nt work on the ROM
- then I created a GOLD Card
- with this I flashed in the OEM fastboot Mode (described here) the HTC Update ROM (_HTC_Hero_RUU_Hero_HTC_WWE_2.73.405.5_WWE_release_signed_NoDriver.exe)
- then flashrec was working and I was able to flash a Recovery Image
- in the Recovery Console I flashed the unlocked Modaco SPL (from here)
- now it was possible to erase the config, which locked the USB after Kernel Boot (fastboot oem eraseconfig)
- after that I restored the last Nandroid Backup...
- Now I'm happy

Re: NEED HELP! Bricked? No SDcard in Recovery - no Restore - no adb
Excellent news.
-------------------------------------
Sent via the XDA Tapatalk App

[Tutorial] Restoring Recovery Mode while working only Fastboot Mode*ALL METHODS HERE*

Hello!
Yesterday I found myself in a very terrible situation. I spend about 6-7 hours...
It just happened that I deleted the recovery (through fastboot), and before that deleted firmware of the phone. That is, there remained only mode HBOOT (fastboot). Around the internet and google there are no guides on how to return
recovery by the alternative methods or how to flash a new ROM through
fastboot.
Thats why i want to present to you my little guide... Coz i think it will be very useful for some ppls like me with the same trouble.
So, if you're in a situation where you do not have Recovery, and the phone is not started in boot ROM then first try a standard way to flash a new Recovery through fastboot mode
Standart way of flashing new recovery via fastboot​
1.Connect your phone with PC via USB and power off your phone (if it up).
2.Than start up in fastboot mode - (in my situation, fastboot mode is CAMERA+POWER, then button "send") in all other (as i know) this is starting the phone while pressing button BACK.
3.Open -> Start->Run->cmd (open command prompt in windows*) and write:
Code:
fastboot devices
Than you must see your device serial number like this:
Code:
H94XTGAMSHDY
and should say "fastboot".
If all right - go next. If not - check fastboot mode (is on?) and USB cable.
4.Than change directory via cmd to where you have saved your recovery image (NEW recovery.img !!! ALWAYS CHECK MD5 SUM)
5. Than type this :
Code:
fastboot flash recovery recovery.img [enter]
(while you are stay in the same dir where you saved recovery.img)
(if you got some error about previously version or smth like this you can try to use this: fastboot erase recovery and only than try to flash new recovery from step №5)
6.Check your phone's display, as recovery is being sent and flashed to your device. And check your command prompt/shell to make sure the process is over.
7.Reboot into recovery by holding Home and Power (before it power off device).
Thats all! You can use any recovery, all what you like. I use Amon_RA's recovery.
IF WHILE FLASHING YOU GOT :
Code:
sending 'recovery' <4594kb>... OKAY [ 1.734s]
writing 'recovery'... INFOsignature checking...
FAILED <remote: signature verigy fail>
finished. total time: 3.125
Use next steps (my Alternative method)
And IF you can't flash recovery by this method it is not big trouble as you think now
Alternative way of BOOTING new recovery via fastboot​ checked and founded by me
Everything here is much easier and faster!
Do not be scared as I did it yesterday
Only what you need it :
Change directory via cmd to where you have saved your recovery image (NEW recovery.img !!! ALWAYS CHECK MD5 SUM)
And than TYPE:
Code:
fastboot boot recovery recovery.img
And your phone will be rebooted about 2 seconds in RECOVERY MODE. Yes!
After this you can use your old Nand Back up (restore it) and start up your old ROM. Or you can wipe all and try to flash new ROM and many operations what you can use via recovery. When you will get working ROM and flash it - you can flash recovery via adb. Or Use Rom Manager (Not recommended!)
Why we use this method? Because if you got error while flashing - FAILED <remote: signature verigy fail> you CAN'T FLASH ANY .img. Why? I Don't know, i hope some android guru's help us with it theory
(ALL AFTER THIS LINE ALL TEXT COPYED FROM WIKI.CYANOGEN.COM CREDITS GOES TO Cyanogen. Thx you, god)
If you want to flash recovery via adb (using power on phone with working firmware) (This method working 100% but strongly need working phone with working ROM)
Working only with HTC DREAM (G1) - Attention.
adb method by cyanogen version
Restoring the custom recovery image
Download the flash_image tool (HERE LINK
Next, place the file on your desktop
Change the directory to where "flash_image" is located, e.g. in Windows: cd C:\<path-to-flash_image-location>, in Linux: cd /home/USERNAME/path/to/flash_image on a Mac: cd /Users/USERNAME/path/to/flash_image)
IMPORTANT: Turn on USB debugging. Settings -> Applications -> Development -> check the box "USB Debugging"
Open up and adb shell
With your phone booted, type the following command
s:
Code:
adb root
This will start ADB as root, or notify if it is already running as root.
Code:
adb remount
This will mount the system partition (/system) as writable, allowing the following
Code:
adb push flash_image /system/bin
This will send the flash_image script into the /system/bin, so we can use it from within the shell
Code:
adb shell chmod 0755 /system/bin/flash_image
Finally, change the permissions of the script to allow it to perform the desired action.
Now that the script is installed, we are ready to proceed with flashing the custom recovery, saved on the root of the SD card earlier:
Code:
adb shell flash_image recovery /sdcard/recovery.img
P.S. If you want i can post here method by flashing original 1.6 ADP Rom via fastboot (but as i think it is on htc dev web... But i can post here cut version of this - coz original version have many not needed things.)
Credits:
Cyanogen
all xda cool ppls
ANtiHazarD

hey ANtiHazarD i have a desire so im not sure if this is suppose to work but all 3 methods fail for me, any advice, thanks in advance

Nice steps! man hope this gets a good stick or added to the rom bible, you do know though fastboot method is a common way to flash recovery

ilostchild said:
Nice steps! man hope this gets a good stick or added to the rom bible, you do know though fastboot method is a common way to flash recovery
Click to expand...
Click to collapse
That's what I was thinking... Seems almost pointless for a guide since there's instructions how to fastboot on every recovery thread.
Either way, nicely written guide. Someone will probably find this useful.

pablo34 said:
hey ANtiHazarD i have a desire so im not sure if this is suppose to work but all 3 methods fail for me, any advice, thanks in advance
Click to expand...
Click to collapse
With a desire this is quite different, as it has an activated nand flash protection (s-on), so no fastboot flash recovery here. Although this should prevent you from not having a recovery at all...
* note: I don't have a desire (yet) so this is speculation *
Best is probably something similar to this http://forum.xda-developers.com/showthread.php?t=750852
I guess if you get the correct PB99IMG.zip for exactly your device/brand you will not need a goldcard, so don't follow the howto blindly (it is for the newer SLCD versions, but the basics will still be applicable to AMOLED devices). Best would be a PB99IMG.zip that still has a hboot version < 0.92, otherwise you will need to downgrade to root. If you already have 0.92, then just take the newest image, as older ones are normally not flashable.
After step 7 of the howto, you are either done, or you will need to find instructions to downgrade if you want to root.
As soon as you have a working system, with a 0.8* hboot you can just use unrevoked to root and flash a custom recovery.
Enough OT... @ANtiHazarD: Very useful overview. Thanks.

WAY WAY WAY more complicated than it should be...
It is a simple matter of:
fastboot flash recovery recovery.img
Done.

lbcoder said:
It is a simple matter of:
fastboot flash recovery recovery.img
Done.
Click to expand...
Click to collapse
Its not quite that simple,
1) if eng spl use fastboot instructions from RA recovery post (fastboot flash recovery recovery.img)
2) if older stock spl with fastboot ruu modes (1.33.000*) where the * is

lbcoder said:
WAY WAY WAY more complicated than it should be...
It is a simple matter of:
fastboot flash recovery recovery.img
Done.
Click to expand...
Click to collapse
maybe so
but i want to post here ALL known methods thats why so much text is here
why? coz it was a trouble and the method with
fastboot flash recovery recovery.img
not working! thats why - all ways is here.
(all pre-info into 1st post in the top)

pablo34 said:
hey ANtiHazarD i have a desire so im not sure if this is suppose to work but all 3 methods fail for me, any advice, thanks in advance
Click to expand...
Click to collapse
oh... i want to give to you some advice, but don't know what exact. because i don't have desire at my hands... and can't test.
so... thats why only - sorry
maybe there is some guide in the same way in desire section?
p.s. and thanks one more time to ezterry for old support

Can you please help me,
I have stuck here with the G1 phone,
it starts up and stucks on the G! logo.
I can get into fastboot bet have the same problem :
writing 'recovery'... INFOsignature checking...
FAILED <remote: signature verigy fail>
I get into fastboot with thre android logos on skates,
even tried to restore nandroid using fastboot but I get the same error? could you help me out?
I have HTC DREAM with 1.33.0013d and radio 2.22.27.08
I am really frustrated,
I tried all you gave up here but none worked for me.

Also when I try to get into recovery I see a G1 logo with a fastboot usb written on top left in red.

behzadbayat said:
Can you please help me,
I have stuck here with the G1 phone,
it starts up and stucks on the G! logo.
I can get into fastboot bet have the same problem :
writing 'recovery'... INFOsignature checking...
FAILED
I get into fastboot with thre android logos on skates,
even tried to restore nandroid using fastboot but I get the same error? could you help me out?
I have HTC DREAM with 1.33.0013d and radio 2.22.27.08
I am really frustrated,
I tried all you gave up here but none worked for me.
Click to expand...
Click to collapse
Did you read everything before you flashed the 1.33.0013d SPL?
If yes, you would have noticed, that this SPL is not able to flash a recovery or radio using fastboot. You have to flash the orange-...nbh file to get back a full engineering SPL, but you will loose everything you have installed on the phone ...
Send from my G1 with HTCClay's UNOFFICIAL Superfly 1.6 D/S ADS using XDA App

i don't know about this spl, but all what you can do (what i know) you can use this method which named in prev. post. with RC29 or RC7 stock firmware *.nbh
after flashing all data, radio, recovery will be reflashed by a stock data. All must be fine after this... i hope
ezterry can give for your advanced advice, may be

ANtiHazarD said:
i don't know about this spl, but all what you can do (what i know) you can use this method which named in prev. post. with RC29 or RC7 stock firmware *.nbh
after flashing all data, radio, recovery will be reflashed by a stock data. All must be fine after this... i hope
ezterry can give for your advanced advice, may be
Click to expand...
Click to collapse
Don't use RC29.. its once of the most annoying NBH files to need to re-root for the dream.
If you have 1.33.0013d note the orange.nbh posted on the new radio OP post: here
ezterry said:
If you find yourself stuck without recovery!!
Dream
1) Download: orange-1.58.73.2.nbh (MD5: aca4dee0c1ece7e9773f2ecbdfbba7c0) (mirror)
2) enter fastboot and run 'fastboot flash nbh orange-1.58.73.2.nbh'
3) wait for the entire nbh to flash
4) boot into the bootloader again (it will be an engineering SPL 1.42.2000)
5) You can now re-flash the radio/hboot/recovery via fastboot that you wish to have installed.
​
Click to expand...
Click to collapse
basically if you intend to still use the new radio; after installing 1.58.73.2 you can reboot-bootloader; and use my fastboot installation steps at the top of that post
You can do this without a goldcard because I bypass various checks in 1.33.0013d
(It will let you install any other signed NBH but that will still wipe the phone completely; and if it fails to flash cleanly it will leave you without an engineering SPL thus make it harder to make android go again)

hey i tried to flash the MTD too and now i keep getting "E:cant open CACHE:recovery/log" when i go into recovery . I can flash roms but when i reboot my phone my phone stays in the G1 Logo . and when it does make it to the rom i can not get my market or gapps no matter what i do . please help me guys .
EDIT: theres times when i get past the g1 logo but itll just stay on the roms boot screen forever until the phone dies . does anyone have any ideas ?

try to 'fastboot wipe system -w'
after
wipe all (data/cache, cache, dalvik, ext, stats)
and move log to sd

ANtiHazarD said:
try to 'fastboot wipe system -w'
after
wipe all (data/cache, cache, dalvik, ext, stats)
and move log to sd
Click to expand...
Click to collapse
ive never really done fastboot tho . is there any other way ?

breezy169 said:
ive never really done fastboot tho . is there any other way ?
Click to expand...
Click to collapse
It's worth learning to use it ...
Really, especially when using the 14MB-hack or CustomMTD and it's not so difficult. There should be a tutorial on adb and fastboot here in the forum.

AndDiSa said:
It's worth learning to use it ...
Really, especially when using the 14MB-hack or CustomMTD and it's not so difficult. There should be a tutorial on adb and fastboot here in the forum.
Click to expand...
Click to collapse
i agree but i just finished reading the forum that shows how to do it but it sounds so complicated .
EDIT: i ended up flashing another recovery and that solved the problem . that was the weirdest thinq ive ever seen . and honestly i thought i bricked my phone but it was a simpleee fix lol . thanks for the advice tho

I am hanging at booting while trying to do this any ideas?

How to upgrade from rooted 1.5 to 2.2 on MT3G?

So...I'd really like to update to the 2.2 froyo mod but I get a script error when I'm trying. I can't even upgrade to cyanogen's 5.8 or whatever mod for some reason it gets stuck after installing on the boot up vodafone screen. I have a mytouch 3g 1.0 32b phone...do I need to update the radio or SPL in order to get any of these newer roms to work...how do I figure out which ones I need and what order should this be done in??

I have the exact same configuration (except I had 1.6 and had to downgrade to 1.5 first). I did not need to update the SPL or radio. Once I flashed 5.0.8, I got stuck at the boot screen. Then I wiped (on recovery screen Wipe --> All) and reflashed. This time, it worked like a charm. Which file are you using to flash?

anilo said:
I have the exact same configuration (except I had 1.6 and had to downgrade to 1.5 first). I did not need to update the SPL or radio. Once I flashed 5.0.8, I got stuck at the boot screen. Then I wiped (on recovery screen Wipe --> All) and reflashed. This time, it worked like a charm. Which file are you using to flash?
Click to expand...
Click to collapse
I don't remember off the top of my head...can you link me to the one you used? I had to do the same thing you did (downgrade from 1.6 to 1.5) so whatever you used should work for me...

Since I am a newb, the forum does not let me post URL's. I will send you a PM.

anilo said:
Since I am a newb, the forum does not let me post URL's. I will send you a PM.
Click to expand...
Click to collapse
I got your PM but I'm still having problems...I don't think have the right recovery thing installed (amonra or whatever?) because the only options I have when I reboot holding power + home are:
reboot system now
apply sdcard:update.zip
wipe data/factory reset
nandroid v2.1.1 backup
nandroid 2.1.1 restore
I can't upgrade from zip files not named update.zip...and I can't even update the 5.0.8 file you linked me to even if I rename it to update.zip, it keeps giving me this error:
"e:cant mount /dev/block/mmcblk0p1 (or /dev/block/mmcblk0) (no such file or directory) e: cant mount sdcard:update.zip installation aborted."
I know when I had a G1 I was able to select a lot more options so my guess is I still need to change the amonrecovery? Do you know which one you're using or can you PM me a link to it?

Okay...so I found the recovery-RA-sapphire-v1.7.0G.img and am trying to upgrade it via the terminal by typing flash_image recovery /sdcard/recovery-RA-sapphire-v1.7.0G.img and the first time I did this I didn't get a message or anything. I tried rebooting by holding down the power + the menu button but it just got stuck at the vodafone screen...
So I tried rebooting and going back into terminal emulator and doing it again, except now I get a long list of these errors:
mtd: read error at 0x00000000 (out of memory)
mtd: read error at 0x00020000 (out of memory)
and it just keeps going for like a page before it stops with different addresses...and now I can't get into a recovery at all....help!

colonelcack said:
Okay...so I found the recovery-RA-sapphire-v1.7.0G.img and am trying to upgrade it via the terminal by typing flash_image recovery /sdcard/recovery-RA-sapphire-v1.7.0G.img and the first time I did this I didn't get a message or anything. I tried rebooting by holding down the power + the menu button but it just got stuck at the vodafone screen...
So I tried rebooting and going back into terminal emulator and doing it again, except now I get a long list of these errors:
mtd: read error at 0x00000000 (out of memory)
mtd: read error at 0x00020000 (out of memory)
and it just keeps going for like a page before it stops with different addresses...and now I can't get into a recovery at all....help!
Click to expand...
Click to collapse
install it via fastboot. that's a known issue with cm 5 and cm 6 roms.

Binary100100 said:
install it via fastboot. that's a known issue with cm 5 and cm 6 roms.
Click to expand...
Click to collapse
How do I actually install it onto my phone? I know the command to boot off an img file but whats the command to install it permanently so its always my recovery and I don't have to use fastboot every time?

colonelcack said:
How do I actually install it onto my phone? I know the command to boot off an img file but whats the command to install it permanently so its always my recovery and I don't have to use fastboot every time?
Click to expand...
Click to collapse
what the hell are you talking about???
Just fastboot flash recovery /computer/directory/recoveryfile.img
fastboot reboot

HEEEEEEEEEEEEEELP ME - Can't able to go in fastboot mode

Hi All. During a upgrading phase I don' know what appened but:
- The device start only in recovery mode
- I don't able to go in fastbbot mode, both pressing keys on startup of device or by fastbbot command line
- the command "fastboot devices" give me any device attached, or other fastboot cmmand < waiting for device>
- command adb devices give me:
C:\Temp\android-sdk-windows\tools>adb devices
List of devices attached
HT936NG00644 recovery
- I am able to push .zip on Dream (adb push ...) and install it by ALT+S on Dream
- On the Dream I reach this error:
- E:Can't read MISC: (No space left on device)
- E:Can't open /cache/recovery/command
- any other adb command by command line, give me the follow error:
C:\Temp\android-sdk-windows\tools>adb shell
- exec '/system/bin/sh' failed: No such file or directory (2) -
HELPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPP, Its 4 days I didn't able to solve.
Can anyone help me ?
Thanks
Pippapeppa

pippapeppa said:
Hi All. During a upgrading phase I don' know what appened but:
- The device start only in recovery mode
- I don't able to go in fastbbot mode, both pressing keys on startup of device or by fastbbot command line
- the command "fastboot devices" give me any device attached, or other fastboot cmmand < waiting for device>
- command adb devices give me:
C:\Temp\android-sdk-windows\tools>adb devices
List of devices attached
HT936NG00644 recovery
- I am able to push .zip on Dream (adb push ...) and install it by ALT+S on Dream
- On the Dream I reach this error:
- E:Can't read MISC: (No space left on device)
- E:Can't open /cache/recovery/command
- any other adb command by command line, give me the follow error:
C:\Temp\android-sdk-windows\tools>adb shell
- exec '/system/bin/sh' failed: No such file or directory (2) -
HELPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPP, Its 4 days I didn't able to solve.
Can anyone help me ?
Thanks
Pippapeppa
Click to expand...
Click to collapse
What buttons are you holding while you bootup?

Hi JAguirre1231,
Thanks for the response.
I Hold Back+Power or Camera+Power. In any way I boot the Dream always go in Recovery Mode.
Thanks again for Your Help.
Pippapeppa

Try to reflash radio and SPL but be careful. I can't give you warranty that you will not broke your phone completely. You have damaged data in ROM (radio & SPL) and I think that reflashing it should help you but also can damage it completly (but I think that it shouldn't happen). The risks increase fact - you must flash radio & spl from recovery but this method is strongly discouraged because of risks to broke phone (read topics about dangerSPL and why you shouldn't use recovery to flash it).
http://forum.xda-developers.com/showthread.php?t=831139

Hi Gerdal,
Whitch version of Radios and SPL have I to reflash.
Which procedure can I follow ?
Thanks again, there are to many information and I understand that if we can chach procedure, sequence and version we can total brick the phone.
Regards
Pippapeppa

Radio - http://forum.xda-developers.com/showthread.php?t=640535
SPL - in attachments
Flash RADIO, reboot, wait - phone will reboot automatically to recovery, flash SPL, reboot and again wait before phone automatically rebot to recovery. If everything goes correct you can reboot and try to boot in fastboot.

Hi Gerdal,
I just done the two updated without errors.
I didn't resolve The dream start only in recovery mode .
I am desperate
I don't understand this thing, if I run by PC with Dream connected by USB the command:
C:\Temp\android-sdk-windows\tools>adb devices
I obtain:
List of devices attached
HT936NG00644 recovery
The devices is visisible and accesible by PC,
If I run:
C:\Temp\android-sdk-windows\tools>fastboot devices
Nothing is the response, I presume that the tool fastboot don't see the Dream.
Any Hel is appriacied
Regards Pippapeppa

fastboot devices will see phone only if phone is running in fastboot mode. Are you sure you pressing camera+power when you powering on phone? Can you try to flash any ROM in recovery, reboot (do not press any buttons) and try to boot to android? Maybe camera button is broken?
Actually I'm trying to find possibility to flash entire ROM (everything what is in nbh file) through recovery. This should repair everything. Maybe someone know what to do this and will write how to do that?

Hi
Gerdal said:
fastboot devices will see phone only if phone is running in fastboot mode. Are you sure you pressing camera+power when you powering on phone? "Can you try to flash any ROM in recovery", reboot (do not press any buttons) and try to boot to android? Maybe camera button is broken?
Click to expand...
Click to collapse
I haven't find any botton to switch off the Dream, the only way is reboot (HOME+BACK or PHONE+POWER+MENU). So immediatly after I press HOME+bACK I press CAMERA+POWER. Should be that the mapping of the keys are not correct ?
How can perform "Can you try to flash any ROM in recovery", I understood that this operation should be only in fastmode. If I can do it and You can tell me how should be a good way.
Thanks again
Pippapeppa

Which recovery are you using? Have you flashed once a custom recovery for example AmonRa Recovery or ClockWork recovery? If you have one of them you can flash any zip that contains ROM for example cyanogenmod. If you flash this and reboot, the phone should boot into this system. If not we need to find answer why it don't do that.
You are pressing rights buttons when you try to boot in fastboot so I don't understand why it don't works...

Sorry Gerdal I am a beginner on this space.
I explane you the context because I am very frustrated.
The device is of my collegues and I am test it for potential purchase. I have attempted to upgrade it to appreciate al the functionalities and I have done the trouble !
So I don't know which recovery I am using I know that the Dream has been rooted.
If You can be kind to explain me the major step to execute and the reference to the persion of files I will be grateful ... forever.
Thanks again
Pippapeppa

Hi Gerdal,
I have flashed with ionr1-signed.zip, the ROM installed before the Hang.
I have attempt to install and run this (http://forum.xda-developers.com/showpost.php?p=9221440&postcount=39), but without result. seems the internal partition are all broke / unconfigured and any script on this partitation are unavailable.
Always the same behavior
Thanks for any help

Sorry but I can't help you. I don't understand why these ways don't work for you.

[SOLVED] i9020t - Hard bricked! bootloader not flashing - need ops file

Mistakenly I replaced /dev/mtd/mtd0 partition with dd command.
Now phone is not booting.
Am able to get into fastboot mod by using AdamOutler's Unbrickable mod applcation. But flashboot flash bootloader giving error
Code:
sending 'bootloader' (1536 KB)...
OKAY [ 0.210s]
writing 'bootloader'...
FAILED (remote: Write Fail)
finished. total time: 0.318s
Even tried with ODIN (without re partitioning) , but it also failed when flashing bootloader.
I think I need to re-partition my device. Any one have (or know to generate) odin partition system file ?
Any other way or work around ?
* Am in india, and I dont think samsung sells I9020T here.
* I saw the post http://forum.xda-developers.com/showthread.php?t=947950
but i couldnt find necessary files there.
EDIT:
I able to fix it.
If you want to know how I fixed it, here is it.
1. Boot into fastboot mod via unbrickable mod application.
2. fastboot boot stock-recovery.img
3. flash stock rom
4. everything will be fixed.

What did you do to get your phone "bricked?" So you cannot get into the bootloader at all? Are you sure its download mode you are getting to? It is really really hard to brick a Nexus s...
Sent from my Nexus S 4G using xda premium

As long as you can get into download mode and your computer will recognize the phone you're not bricked. From download you can reflash all the files to get the phone back up and running through Odin.

I am not able to flash bootloader. Even odin fails to flash it. I think I need to re partition my device. But OPS file is not available any where. If you know how to make it, plase help me.
Is there any way to format the bootloader partition ? (using fastboot) ?

Rem3Dy said:
What did you do to get your phone "bricked?" So you cannot get into the bootloader at all? Are you sure its download mode you are getting to? It is really really hard to brick a Nexus s...
Sent from my Nexus S 4G using xda premium
Click to expand...
Click to collapse
I mistakenly replaced /dev/mtd/mtd0 with dd command. :'(
Can any one give me a copy of /dev/mtd/mtd0 ?
(you can make that by 'dd bs=4096 if=/dev/mtd/mtd0 of=/sdcard/filename')

jishnu7 said:
My phone is now in completely bricked form. Am only able to get into download mod.
I saw a post http://forum.xda-developers.com/showthread.php?t=947950
but i couldnt find necessary files there.
Please share odin/ops and other necessary files.
Click to expand...
Click to collapse
Why you can not use AdamOutler resurector ? It's really really worked ...just try it and you'll see
Take a look here , it was my problem => http://forum.xda-developers.com/showthread.php?t=1474539
Good luck!

surdu_petru said:
Why you can not use AdamOutler resurector ? It's really really worked ...just try it and you'll see
Take a look here , it was my problem => http://forum.xda-developers.com/showthread.php?t=1474539
Good luck!
Click to expand...
Click to collapse
I am using that to bootup my device. But am not able to flash bootloader.

jishnu7 said:
I am using that to bootup my device. But am not able to flash bootloader.
Click to expand...
Click to collapse
OK!
B : try again ...and wait for image UnBrickable to change..than press ...Downloade Mode ...... you'll see ( where it was Device not found, No device detected ) fastboot fastboot mode ...right now tape into terminal :
# ./fastboot flash bootloader bootloader.img
...you will see that copy something
# ./fastboot flash boot boot.img
..you will see that copy something
# ./fastboot flash recovery recovery.img
...you will see that copy something
- now you can go into recovery to flash your favorite system....100% works !!!
A : ( attention! you do not need to touch any key in your device : just open Ubuntu....and in terminal comm write :
>$ sudo su
passw : ( write your password)
># java -jar UnBrickableResurrectorR40.jar
- Select "S5PC110 (Nexus S)"
- connect USB cable
- put the battery back
and wait ....after a few seconds you will see img. UnBrickable changed , now follow the above instructions ..(B)....).
Good luck ! for me it works very nice !
If this does not work , you have only solutions : remove the battery from your phone , and leave it two or three days , than you can go to (A) than (B)

surdu_petru said:
OK!
B : try again ...and wait for image UnBrickable to change..than press ...Downloade Mode ...... you'll see ( where it was Device not found, No device detected ) fastboot fastboot mode ...right now tape into terminal :
# ./fastboot flash bootloader bootloader.img
...you will see that copy something
# ./fastboot flash boot boot.img
..you will see that copy something
# ./fastboot flash recovery recovery.img
...you will see that copy something
- now you can go into recovery to flash your favorite system....100% works !!!
A : ( attention! you do not need to touch any key in your device : just open Ubuntu....and in terminal comm write :
>$ sudo su
passw : ( write your password)
># java -jar UnBrickableResurrectorR40.jar
- Select "S5PC110 (Nexus S)"
- connect USB cable
- put the battery back
and wait ....after a few seconds you will see img. UnBrickable changed , now follow the above instructions ..(B)....).
Good luck ! for me it works very nice !
If this does not work , you have only solutions : remove the battery from your phone , and leave it two or three days , than you can go to (A) than (B)
Click to expand...
Click to collapse
I used 'flash bootloader' earlier also, it is not flashing. Giving some write failed error. That is my problem.

I've had the same thing happen... no matter what degree of flashing, which steps taken, NONE of the so called 100% working fixes take... phone gets stuck and hangs in the google bootloader screen.... NO RECOVERY AT ALL....
All the packs and ODIN techniques over the web seem to fail and NOTHING else but the proper files seem to be the last hope...
Once in awhile, one can get into fastboot... but any attempts to load recovery directly land flat and hard back on the google boot screen and don't budge... it's like the fastboot flash operations never happened... or some other error of enigmatic mystery thwart all attempts to get this rather expensive paperweight to revive...
There's gotta be some way to fix this!!
Anyone? please and thanks!