sort of unique problem with droid after attempted flash image installation?

[boristhebladexx]

ok so i have a problem that i have not been able to find anywhere else on this site.

i was attempting to install the SP/sholes recovery image so i could install 2.1, but something did not quite go right. because adb wasn't working for me, i used terminal emulator to enter the commands, and now when i hold x at power up, i get the /!\, but when i press the volume up and camera button, it no longer goes to the boot screen thing that it did before when i rooted the phone.

at first i was freaked out, but i realized that everything still works perfect and no other aspects of my droid were harmed.

so after swearing off doing anything to my phone, i saw the 'noob guide' to installing 2.1, so i installed droidroothelper and followed the steps, but mounting mtdblock3 or 4 does not work for me, and it just freezes, and i think it has something to do with the attempted flash_image installation.

so in conclusion, does anyone have any idea what i did to my phone, and if it's fixable?

thanks in advance

[Berzerker]

ok so i have a problem that i have not been able to find anywhere else on this site.

i was attempting to install the SP/sholes recovery image so i could install 2.1, but something did not quite go right. because adb wasn't working for me, i used terminal emulator to enter the commands, and now when i hold x at power up, i get the /!\, but when i press the volume up and camera button, it no longer goes to the boot screen thing that it did before when i rooted the phone.

at first i was freaked out, but i realized that everything still works perfect and no other aspects of my droid were harmed.

so after swearing off doing anything to my phone, i saw the 'noob guide' to installing 2.1, so i installed droidroothelper and followed the steps, but mounting mtdblock3 or 4 does not work for me, and it just freezes, and i think it has something to do with the attempted flash_image installation.

so in conclusion, does anyone have any idea what i did to my phone, and if it's fixable?

thanks in advance

You might want to try waiting a couple seconds then make sure you're pushing the volume up/camera buttons pretty well, I remember it took me a few tries to get it to recognize the button pushes. Once you install sprecovery, the button sequence is not needed as it automatically loads the selection menu.

[boristhebladexx]

i was under the impression that after i installed the sprecovery that it would load a different picture instead of the /!\, and that didn't happen.

also, is it possible that i could've disabled the default recovery, but failed to install the sprecovery, which is now denying me access to the menu that i would normally get upon holding x at bootup?

[SLiKoNe27]

ok so i have a problem that i have not been able to find anywhere else on this site.

i was attempting to install the SP/sholes recovery image so i could install 2.1, but something did not quite go right. because adb wasn't working for me, i used terminal emulator to enter the commands, and now when i hold x at power up, i get the /!\, but when i press the volume up and camera button, it no longer goes to the boot screen thing that it did before when i rooted the phone.

at first i was freaked out, but i realized that everything still works perfect and no other aspects of my droid were harmed.

so after swearing off doing anything to my phone, i saw the 'noob guide' to installing 2.1, so i installed droidroothelper and followed the steps, but mounting mtdblock3 or 4 does not work for me, and it just freezes, and i think it has something to do with the attempted flash_image installation.

so in conclusion, does anyone have any idea what i did to my phone, and if it's fixable?

thanks in advance

did you follow these instructions exactly?
Installation | Sholes

It worked for me the first time

[boristhebladexx]

i used instructions on this site, but even if i got those to work, i can't access the screen to load the backup. pushing the camera + volume up buttons doesn't work

[Bear in NM]

Boris,

I am not sure this is gonna help, but here goes. I am currently helping another user here sort his phone problems after he got a fouled up system using the root helper ap.

We figured out last night that while he went through the steps with the root helper, he fuggered something up before he got his new recovery image to stick. If you are still getting the stock recovery triangle like he is, then your flash did not work, or the next step where the recovery-from-boot-image.p gets renamed.

Not sure if you have a program that will let you see the system files, but you might need one, like Astro to try and troubleshoot. You might want to check on your phone files in /system to see if you have a recovery-from-boot.p If you have this file, in this location, and it is not renamed recovery-from-boot.old or some variation that IS NOT recovery-from-boot.p then you might have a similar problem, a recovery flash without the disabling of the stock recovery program. Also from the person I am helping, he mentioned that the developer of the Root Helper program is pretty responsive to requests for help. Might try that. And, DO NOT RENAME this file if you find it intact, as doing so without first flashing might brick your phone if you try recovery with no recovery image. What I am suggesting is non-fatal ways to trouble shoot.

I will be helping him shortly on the phone, so I may not be able to follow here, but please check for this file, and if anyone here reading this has gone through the Root Helper Ap, if you could check to see what was done to your recovery-from-boot.p file it might help us help others here who fugger up with the Root helper ap.

Craig

[boristhebladexx]

i checked in the /system/bin folder, then used astro to search for recovery-from-boot.p but i couldn't find it... possibly deleted?

[SLiKoNe27]

i used instructions on this site, but even if i got those to work, i can't access the screen to load the backup. pushing the camera + volume up buttons doesn't work

try following the instructions on the link I posted. if you do and it works there will be no need to hold the camera and volume button. it will go straight into SPrecovery

[Bear in NM]

i checked in the /system/bin folder, then used astro to search for recovery-from-boot.p but i couldn't find it... possibly deleted?

Boris,

On a stock phone, this file should be in the /system folder, not the /system/bin. If you are sure this file is no where to be had, this could be a "clew". Unfortunatley this is over my head as to what happens with this file being completely absent, but if you can confirm that this file is nowhere, and you did not get a sprecovery menu, I would suggest staying out of recovery until either perhaps the Roothelper Developer or another here with more knowledge than I can shed some light. Perhaps the flash did not happen correctly, but the next step, renaming or erasing this file happened. Again, I stayed way clear of the Root Helper program, so I do not know if this file was to be renamed or deleted.

I seemed to recall reading something here on the forum about something like this, describing the boot loading and recovery sequence. Perhaps a seach by "boot loader" might help. Sorry man, trying.

Craig

[Bear in NM]

Boris,

Just an update in case you are still "stuck"

I went through the Roothelper last night with the user I mentioned, and we were able to get his phone recovered and backed up using the Roothelper. The problem could be the sequence of steps as they are laid out in your Root Helper menu v. the way they should be done while actually doing it. there is a post over on alldroid where one of the users spells out the proper sequence of steps for those who are doing them but do not understand. When i found this post it cleared up for me (not using the program) what could be causing confusion. And, we mounted 4 when we did his phone.

I also confirmed that the root helper program should only be renaming recovery-from-boot.p to .old, not deleting it. I do not know how this would affect your steps if you attempt a retry with your root helper, but the obvious thing that jumps out at me would be to not use the command to rename the file, if you are truely sure the file does not exist on your phone. My thinking being that if the file does not exist, no sense testing the program logic and programming by attempting a command that will at least return an internal error message in Root Helper.

Craig