174 replies to this topic

[coma621]

Just wondering if anyone out there can help me.

Tmobile G1
CM 5.0.8
Danger SPL

Okay so i used the clockwork rom app to get the clockwork recovery.  After that finished i accidentally hit fix permissions.  After about a minute of running fix permissions the whole phone froze up and stayed that way for 22min when i pulled the battery.

Now i can only access bootloader. No recovery no boot and adb can not find my phone.  Any help or suggestions would be appreciated.

Thanks

[Olson.dev]

coma621, on 24 June 2010 - 05:21 PM, said:

Just wondering if anyone out there can help me.

Tmobile G1
CM 5.0.8
Danger SPL

Okay so i used the clockwork rom app to get the clockwork recovery.  After that finished i accidentally hit fix permissions.  After about a minute of running fix permissions the whole phone froze up and stayed that way for 22min when i pulled the battery.

Now i can only access bootloader. No recovery no boot and adb can not find my phone.  Any help or suggestions would be appreciated.

Thanks

I'm in the same exact situation -- same exact thing froze my phone. I, too, would appreciate help and/or suggestions. Thanks!

[coma621]

Wow i was able to restore my device.  I cant believe it. I formatted an sd card i had lying around to fat32 and placed DREAIMG.nbh on the root of that card.  I then booted into the bootloader and followed the instructions to install the update.  I had originally thought this would completely brick my phone but to my surprise everything went through okay and my phone rebooted just fine even if it was RC29 1.0 i am now about to root and restore my old setup.  Hope this helps anyone in the same situation.

[PsychoI3oy]

Nuking from orbit with DREAIMG.nbh is an option, but it's never ideal. If you can get to bootloader, you can fastboot flash stuff (on DangerSPL or magics with eng SPLs), and that is the ideal solution.

[Olson.dev]

coma621, on 26 June 2010 - 10:17 AM, said:

Wow i was able to restore my device.  I cant believe it. I formatted an sd card i had lying around to fat32 and placed DREAIMG.nbh on the root of that card.  I then booted into the bootloader and followed the instructions to install the update.  I had originally thought this would completely brick my phone but to my surprise everything went through okay and my phone rebooted just fine even if it was RC29 1.0 i am now about to root and restore my old setup.  Hope this helps anyone in the same situation.

Good deal. I'll give this a try! In case anyone's interested in the Fix Permissions log, I've attached it to this post.

Attached Files

•  fix_permissions.log.txt   7.74K   3 downloads

[Olson.dev]

My phone is fixed! Woot! Though, ugh! I was looking for an excuse to upgrade. :-P So, I threw DREAIMG.nbh on my SD, flashed it. Downloaded Clockwork Recovery, telnetd-copied it over and flash_image'd it, rebooted twice with the second time going into Recovery... flashed the newer radio, rebooted, flashed the DangerSPL, rebooted, flashed CM 5.0.8 and Google Apps, rebooted. Back in business!

[coma621]

PsychoI3oy, on 26 June 2010 - 11:08 AM, said:

Nuking from orbit with DREAIMG.nbh is an option, but it's never ideal. If you can get to bootloader, you can fastboot flash stuff (on DangerSPL or magics with eng SPLs), and that is the ideal solution.

Does that require ADB? Cause I couldn't get it to recognize phone.  If thats not how you do could you please tell me how I would really appreciate it. Thanks.

[cintronius]

Not sure if this is the thread I need, but here is my problem. I have been using the 4.2.xx cyanogen mod and today I booted into the console using Home+power and I accidently flashed some old eclair rom that was on my SD card. At anyrate now I can not go back into my recover console and the phone freezes at the splash screen. What I ended up doing was pushing Camera+Power that got me to some screen that was all white and had 3 lil aliens bellow and one way or another It ended up reverting my phone back to the 1.0v of Android. Now here is my problem, no matter what I do I cant get into my recovery so I can reflash my cyanogen 4.2.xx, when ever I push home+power I get taken to a screen with a "!" inside a triangle and a phone displayed and thats all.

Ideas on what to do?

I can pull the battery out and just hit power to load as ver. 1.0...

[PsychoI3oy]

cintronius, follow the g1 rooting instructions starting after the DREAIMG.nbh flash (e.g. telnetd/telnet/flash_image recovery.../ 2.x radio / dangerspl / cm5/gapps ) from the wiki.

[samkash]

Hey, so i'm having the no recovery problem... for the second time...

Before the forums wiped, when I first updated to 5.0.7 stable, I used rom manager and ended up killing my recovery, which was RA 1.6.2 I think. I came into the forums and from chatting with firerat and i think  PsychoI3oy, I was able to figure out how to use fastboot to erase the non functioning recovery and then flash RA 1.7.0. Things were good.

Fast forward a month or so to 5.0.8 stable, I decide i've been avoiding rom manager for long enough and I'd like to jump back on it... big mistake apparently. Again I have no recovery. For some reason fastboot is not working, here are the threads I've been reading over for the last ~6 hrs:

this one i'm replying to
http://forum.cyanoge...h__1#entry15696
http://forum.cyanoge..._1116#entry1116
http://forum.cyanoge..._3137#entry3137
http://webcache.goog...lient=firefox-a
http://forum.cyanoge...-lost-recovery/
http://forum.cyanoge...ccess-recovery/

I know listing them seems dumb, but its just so no one points me to another thread that I've already checked out.

I've tried just about every method in all those threads except some kind of goldcard (i have a G1, i thought thats for mt3G dunno), a complete re-root, and some script that firerat wrote, because i'm not sure how to use it really...

Now to ask if someone can tell me why fastboot won't work the second time around?

I go to fastboot, I check

fastboot devices

and its shows my device, so I know it sees me. Then

fastboot erase recovery

now, it says recovery erased. cool

fastboot flash recovery recovery-RA-dream-v1.7.0.img

now (unlike before when it worked) it says "error: cannot load recovery-RA-dream_v1.7.0.img"
I've already tried deleting the image and putting a new one in there. yes, it is in the root of my sdcard. i have also tried RA 1.6.2, with the same results.

What i did find interesting is if I try to flash a file that does not exist on my sd, just to see what the response is, it returns the exact same response as when i try to flash RA recovery. So, what does this mean? the fastboot said it saw my phone, but at the same time it is acting like it can't see my sd card.


this was super long... i had alot to say after 6hrs... sorry

edit: couple things I should've said: when using terminal to flash the recovery over... and over... and over ~20+ times, it always failed with errors about not enough memory. and I can boot CM5.0.8 no probs. its just I have no recovery

[pbelcomp]

samkash, on 29 June 2010 - 07:32 AM, said:

fastboot flash recovery recovery-RA-dream-v1.7.0.img

now (unlike before when it worked) it says "error: cannot load recovery-RA-dream_v1.7.0.img"
I've already tried deleting the image and putting a new one in there. yes, it is in the root of my sdcard. i have also tried RA 1.6.2, with the same results.

I am pretty sure that recovery-RA-dream-v1.7.0.img needs to be on your computer in the same folder that fastboot runs from, not on your sd card.

[samkash]

pbelcomp, on 29 June 2010 - 08:00 AM, said:

I am pretty sure that recovery-RA-dream-v1.7.0.img needs to be on your computer in the same folder that fastboot runs from, not on your sd card.

oh so with a one liner you think you are so smart and make me out to be some kind of idiot?

/attempts what you say because that DOES sound kinda familiar...
/facepalm

so... maybe i'm an idiot. Thanks a lot dude. hopefully the forums don't wipe away my answer and make me look like a fool again...

edit: hopefully i don't kill my recovery again, requiring me to use fastboot like this, causing me to look tha foo again

[PsychoI3oy]

samkash, on 29 June 2010 - 08:20 AM, said:

oh so with a one liner you think you are so smart and make me out to be some kind of idiot?

/attempts what you say because that DOES sound kinda familiar...
/facepalm

so... maybe i'm an idiot. Thanks a lot dude. hopefully the forums don't wipe away my answer and make me look like a fool again...

edit: hopefully i don't kill my recovery again, requiring me to use fastboot like this, causing me to look tha foo again

just leave the recovery.img in your sdk/tools dir so you'll see it next time

[barenaked]

THAAAAAAAAAAAANK YOU SO MUCH!!!!

It worked for meeeeeeeee!!!!

THANK YOU!

-Stevo-, on 04 June 2010 - 07:02 PM, said:

I have something for all of you:
flashrecoveryscript.zip


Flash this zip from recovery and you will now have an easy option for flashing recovery in terminal, you will need to rename the recovery image you downloaded to recovery.img and place in the root of your sdcard, then in terminal run:

flashrecovery

expect errors mtd errors and in some cases if you are real low on memory you can see a bit of a freeze. Be Patient. there will be a message and a prompt to reboot if you wish when the script has finished.

I was planning on putting this together before the great forum crash, and although i've been going through the cached google pages, i completely forgot that firerat and i's discussion had led to his nifty little script to help out. so thanks for the reminder skrki.

Also, this is another option, albeit useless (and bulky) if you just use the easier method above. the only difference is that you will not need to download any recovery images seperately. This kit contains ra-recovery 1.7.0 images for the magic/mt3g dream/rogers-dream. the images and scripts are placed on your sdcard for easy removal, so 25 mb of free space is required. like my other simplified scripts just follow the simple prompts and you *should* have a new working recovery.

Flash Recovery Kit

The above recovery kit gives you two commands in terminal:

flashrecovery - See above
recflash - options for device type/brand.


Let me know if there are any issues. i tested all the scripts on my device with sucess on all (couldn't verify the 32A recovery or the Rogers ones BOOT but that's cause i'm on a 32B magic. all recovery images at least FLASHED correctly.

-----------------------------------------------------------------------------------------------------
recflash.png
Script only - flashrecoveryscript.zip
Kit - http://www.mediafire...php?zmjdm3m52mt
-----------------------------------------------------------------------------------------------------

And it has now occured to me that unless you already have a working recovery image these will do you no good. so installation for the flash recovery script is as follows:

Download the above flashrecoveryscript.zip (3kb)

Extract the file flashrecovery from the /bin folder. place this file on your sdcard root and open terminal:

su
mount -o remount,rw /system
cp -f /sdcard/flashrecovery /system/bin
chmod 755 /system/bin/flashrecovery
mount -o remount,ro /system

Then when ready

flashrecovery

[mathenge]

Thank goodness these forums are so active with people willing to lend their time.

I have MT3G, cyanogenmod 5.0.7, Perfect SPL. Lost recovery trying to flash clockworkmod.

I have tried firerat's script, have tried manually spamming the flash_img script, tried clockworkmod to flash an older recovery. Can't use fastboot because I have perfect SPL. I am hoping someone has an idea that might help me. I have done a lot of reading, and still have no luck.

1) Is my only option to keep trying firerat's script over and over again?

2) If re-rooting is an option, can someone take pity and talk me through that in a way that will not lead to brickness? (All I know is to put sappimg.nbh on root of sdcard, then reboot holding volume down). After that will I have cupcake and be able to flash a recovery image using recovery flasher?

Standard n000b apologies apply, and thanks so much for your help!

-M

[PsychoI3oy]

mathenge, on 02 July 2010 - 12:17 AM, said:

Thank goodness these forums are so active with people willing to lend their time.

I have MT3G, cyanogenmod 5.0.7, Perfect SPL. Lost recovery trying to flash clockworkmod.

I have tried firerat's script, have tried manually spamming the flash_img script, tried clockworkmod to flash an older recovery. Can't use fastboot because I have perfect SPL. I am hoping someone has an idea that might help me. I have done a lot of reading, and still have no luck.
....

get the sdk installed and with the phone plugged in and running the normal os try

adb shell
stop
flash_image recovery /sdcard/nameofrecocery.img

reboot recovery


the screen will go black after the 'stop' but that just cleared a crapton of ram out by stopping Android and just leaving the Linux kernel and the basic command line stuff. If it works, send zinx a beer, 'twas his idea.

[mathenge]

Solid, thanks so much for the reply. I'll give it a try, it looks promising! By running the normal OS, you mean with the phone on and booted up as normal, right?

-M

PsychoI3oy, on 02 July 2010 - 11:48 AM, said:

get the sdk installed and with the phone plugged in and running the normal os try

adb shell
stop
flash_image recovery /sdcard/nameofrecocery.img

reboot recovery


the screen will go black after the 'stop' but that just cleared a crapton of ram out by stopping Android and just leaving the Linux kernel and the basic command line stuff. If it works, send zinx a beer, 'twas his idea.

[mathenge]

no luck. I also tried "stop" before -Stevo- 's method above, got the "We -may- be in business" but still hangs on boot to recovery. I have tried stop->flashrecovery a few times.

Is re-rooting the next step, and is that as simple as rebooting into sappimg.nbh?

Thanks again,

-M

PsychoI3oy, on 02 July 2010 - 11:48 AM, said:

get the sdk installed and with the phone plugged in and running the normal os try

adb shell
stop
flash_image recovery /sdcard/nameofrecocery.img

reboot recovery


the screen will go black after the 'stop' but that just cleared a crapton of ram out by stopping Android and just leaving the Linux kernel and the basic command line stuff. If it works, send zinx a beer, 'twas his idea.

[djkonflikt]

just reroot xD

[mathenge]

Thanks everybody.

-M

djkonflikt, on 04 July 2010 - 06:34 AM, said:

just reroot xD