Epic Screwup. Help needed for unbricking (via adb?)

[Guest gr33nhorn]

Hi! I'm a very happy and satisfied user of a Samsung spica Running CM 6.1

But thats not the story. My roomie decided to get himself a ZTE blade. Through a friend in the UK ( We're in india), he managed to get an orange san fransico running JJ RLS9.

But he wanted more. He wanted to run CM7 very badly, and there begins the sad story of recursive fail driven by coffee and desperation.

He had did a bit of research, and determined that his was a TFT gen1 fone, and that his phone could run 7.03.

So we set out to flash it. First I thought it would be nice to have some recovery installed, just in case, so we installed clockwork recovery 3.0.some version

then we found out that to do a TPT, we need to go back to the stock recovery.

and after attempting to install CM 7.03 on his gen 1 phone, it got stuck at recovery.

So we decided to flash the stock recovery , but even after flashing the stock recovery, the phone did not update to the stuff we had placed in the image folder at root for the TPT upgrade.

Stuck, we found that the phone could get into FTM mode, so we used this thread to try to install a stock firmware, but found that the phone was suddenly booting to Clockwork recovery. (even when you told it to reboot to system). This particular clockwork recovery didnt install any firmware (not even an older 7.02 which was safe for gen 1 devices).

We decided to reinstall clockwork recovery in the hope that that should let us flash *something*. But after rebooting, we get nothing, but after a few tries, we were able to make it show up in my PC as an ADB device and now as a fastboot device, though running adb shell does not list it in the devices list, and using fastboot ends in a FAILED (remote: flash write failure) message.

Update: I can still get to the DFU update method mentioned in the link above, but downloading it is not helping :)

so there we are, and My I feel horrible for having screwed up this phone. Any help in fixing this would be greatly appreciated.

Thanks!

Edited June 21, 2011 by gr33nhorn

[Guest hedgepigdaniel]

Goodness me...

You don't need to have stock recovery to do a TPT. All you needed to do is follow the instructions here. You can upgrade to Gen2 (necessary for CM7), and install CM7 all in one go aswell. Firstly, try that. It may not work, but if it does its the easiest solution.

[Guest hedgepigdaniel]

Assuming that doesn't work, then all is not lost. As long as you can get into DFU mode you can make a full recovery.

Question: when you followed that thread, which set of firmware files did you flash? did you happen to make a backup of the NV memory (in a file called channel1.nvm)?

If you can get into FTM mode, then follow instructions here and choose the custom v5 firmware.

If not, then download the custom v5 firmware package, and use the instructions in that thread you linked to to flash the files in it (partition.mbn etc)

If after doing that it only boots into FTM mode, then you need to restore NV memory. If you have a channel1.nvm from your own phone, restore it using the instructions in that post. If not, follow the instructions to modify the base file with your IMEI, then restore that to your phone. Your phone should now boot into clockworkmod.

Once you've got clockwork working, flash cyanogenmod (I recommend the latest nightly rather than 7.0.3).

[Guest gr33nhorn]

update, it turns out the reason the update via DFU mode wasnt working was because the firmware path was too long. I tried CM7 (and older one) and it booted beautifully (phew!) but no network (the thread said it would happen) but the weird part is when you flash the firmware in the thread itself, it doesnt work. it seems as if it causes clockwork to install in the boot partition ( i mean even when you choose reboot to system, it boots into clockwork again) . Thanks, am going to try with hedgepigdaniel's method

Edited June 21, 2011 by gr33nhorn

[Guest hedgepigdaniel]

update, it turns out the reason the update via DFU mode wasnt working was because the firmware path was too long. I tried CM7 (and older one) and it booted beautifully (phew!) but no network (the thread said it would happen) but the weird part is when you flash the firmware in the thread itself, it doesnt work. it seems as if it causes clockwork to install in the boot partition ( i mean even when you choose reboot to system, it boots into clockwork again) . Thanks, am going to try with hedgepigdaniel's method

It makes sense to put clockwork on the boot partition since there is no ROM on it anyway. In my method it has to because the recovery partition has to have stock recovery.

[Guest gr33nhorn]

i got up till FTM mode, downloaded the channel1.nvm file, put the imei in hex at 1100, and uploaded it back. but when i restart it, it back to the same old :)

EDIT: can someone post a channel1.nvm file for a gen2 phone? the guide above has only a gen1 link ( and using that still yields an IMEI 0 on my phone)

Edited June 21, 2011 by gr33nhorn

[Guest hedgepigdaniel]

i got up till FTM mode, downloaded the channel1.nvm file, put the imei in hex at 1100, and uploaded it back. but when i restart it, it back to the same old :)

EDIT: can someone post a channel1.nvm file for a gen2 phone? the guide above has only a gen1 link ( and using that still yields an IMEI 0 on my phone)

So you flashed the custom v5 firmware and its only booting into FTM mode?

If you use the channel1.nvm posted on that thread, you need to edit offset 0x1215, not 0x1100. If you open it in a hex editor it should have 3A in 0x1215. go ahead and put your IMEI into that, making sure to encode it in hex correctly.

[Guest gr33nhorn]

So you flashed the custom v5 firmware and its only booting into FTM mode?

If you use the channel1.nvm posted on that thread, you need to edit offset 0x1215, not 0x1100. If you open it in a hex editor it should have 3A in 0x1215. go ahead and put your IMEI into that, making sure to encode it in hex correctly.

Did that, starting all over by flashing V5 again. But still no IMEI ( though the phone boots now)

will going back to gen1 help?

[Guest hedgepigdaniel]

Did that, starting all over by flashing V5 again. But still no IMEI ( though the phone boots now)

will going back to gen1 help?

Going back to Gen1 won't help.

Try PMing burstlam with your IMEI and your version of channel1.nvm to see if you've done it right.