Database Info

[Q] Sprint Nexus S 4g bricked: HELP!

Welp, tried to root the Nexus S 4g.
On rebooting, it gets stuck at the Nexus S bootscreen, pauses, keeps going, etc.
Got CWM 3.0.0.5, and can fastboot, get into CWMRecovery.
From there, I'm at a loss. Tried to restore Nandroid backup, but it says a whole bunch of stuff, basically saying E: failed to find "cache" partition, Can't mount /cache/recovery/last_log, etc.
Tried to apply zip from CWM backup, it says "No files found."
Tried going into mounts/storage to mount USB storage, but nothing appears on desktop of either Mac or PC, so I can't get move files onto the SD card.
Now, when I just power up, it just says "Google," and there's a unlock icon at the bottom. Nothing else.
Anyone have any solutions?

Yeah stop using that old version. Of ClockworkMod recovery
Seriously use 3.0.2.4. Its in the clockwork thread in the dev section.
Sent from my Nexus S using XDA App

Would if I could, but I can't get anything on the SD card!
Trying to mount USB storage from CWM-- no drive shows up on Mac or PC for me to move stuff onto it.

Boot into fastboot by turning off phone, turn back on while holding volume rocker up. Leave it at the screen where you could select reboot, recovery etc. Download the above mentioned clockwork recovery image from the thread to your computer. Flash using fastboot command. No need to copy anything to SD card.
Sent from my Nexus S using XDA App

Having the exact same issue. Nothing appears in the nandroid folder now either after replacing the recovery image with 3.0.2.4 and I can't mount the USB storage or get anything onto the SD card. Phone won't boot. Unsure of the folder structure on this phone to try pushing a file with adb or fastboot.

Same issues here. I was able to flash CWM recovery 3.0.2.4, but when I go to "mounts and storage" and "mount USB storage", I the drive does not appear on both Mac and PC. I'd like to transfer the stock NS4G image onto the phone so I can install the zip from the sdcard...
When I try to use the command, "adb push", it can't find the SD card.

Same problem
I flashed it , and since then i cannot mount the device , i have a good image to push but the device is not opening up the storage for me to push the image.

I had the same problem. Got it all fixed up.
peabody42 said:
Welp, tried to root the Nexus S 4g.
On rebooting, it gets stuck at the Nexus S bootscreen, pauses, keeps going, etc.
Got CWM 3.0.0.5, and can fastboot, get into CWMRecovery.
From there, I'm at a loss. Tried to restore Nandroid backup, but it says a whole bunch of stuff, basically saying E: failed to find "cache" partition, Can't mount /cache/recovery/last_log, etc.
Tried to apply zip from CWM backup, it says "No files found."
Tried going into mounts/storage to mount USB storage, but nothing appears on desktop of either Mac or PC, so I can't get move files onto the SD card.
Now, when I just power up, it just says "Google," and there's a unlock icon at the bottom. Nothing else.
Anyone have any solutions?
Click to expand...
Click to collapse
I had the same problem this morning:
I posted a workaround that worked well for me in Post #35
http://forum.xda-developers.com/showthread.php?t=1072698&page=4
If it works for you click 'Thanks'

Figured it out
Alright , this is what i did to fix the problem, i booted up the system with the bad image i had, connected to wifi and downloaded the Nexus S 4G deoxed image that is out there directly from the internet to the phone. Then i moved it from the download folder to the root using file manager.
I rebooted into recovery and was able to wipe and then flash the recovery image and reboot. Once i rebooted i regained control over the usb and memory card. hope it helps you guys.

How Do I Fix "REALLY" Bricked and DEAD Nexus S4g?
All posts on this thread presuppose a working Nexus S 4g. When I use the term bricked, I mean dead. About a month ago I followed directions on one of these threads on how to easily and with one click route my jellybean running phone. For some reason the process never completed, and all I was able to accomplish was unlocking the phone. When I ran the check to see if it was truly rooted, the response showed the phone was still unrooted. About 30 days later it was deader than a brick. Somewhere I read that Jellybean on Sprint might be the culprit. Anyway, I have a dead phone. Sprint wouldn't even check it because the screen was cracked. Fortunately, I bought a new one, new to me anyway, on eBay for $37. It is still running android 2.3.7(Gingerbread), and the phone is attempting to push the Ice Cream Sandwich update. I am fighting the update until I figure out what killed my phone.
Just wondering whether there is anything I can do with my old phone, even if I only use it like an old iTouch for music and surfing via Wi-Fi. Anyone?
I attempted the one click method described here, but my desktop cannot find any devices. So it truly is dead. Comments appreciated. I have used several different cables, unsuccessfully.

sexynexy said:
All posts on this thread presuppose a working Nexus S 4g. When I use the term bricked, I mean dead. About a month ago I followed directions on one of these threads on how to easily and with one click route my jellybean running phone. For some reason the process never completed, and all I was able to accomplish was unlocking the phone. When I ran the check to see if it was truly rooted, the response showed the phone was still unrooted. About 30 days later it was deader than a brick. Somewhere I read that Jellybean on Sprint might be the culprit. Anyway, I have a dead phone. Sprint wouldn't even check it because the screen was cracked. Fortunately, I bought a new one, new to me anyway, on eBay for $37. It is still running android 2.3.7(Gingerbread), and the phone is attempting to push the Ice Cream Sandwich update. I am fighting the update until I figure out what killed my phone.
Just wondering whether there is anything I can do with my old phone, even if I only use it like an old iTouch for music and surfing via Wi-Fi. Anyone?
I attempted the one click method described here, but my desktop cannot find any devices. So it truly is dead. Comments appreciated. I have used several different cables, unsuccessfully.
Click to expand...
Click to collapse
Hi,
What method did u use to root? What thread? Cuz it may need to newest version of the recovery.
anyways...
Try charging up a battery on newer phone and put in dead phone... but instead if turning on normally, boot into recovery.
If it worked then use a back up to flash it back to stock. Assuming u were able to back it up b4 root.
If not plug into computer. See if it turns on or can go into either recovery or boat loader mode and if so perhaps computer will recognize it.
Vs Nexus S4G using tapatalk2

Something went wrong when flashing

So I rooted my phone a few months ago but there weren't many mods out yet, so I waited until just today. I saw this one http://forum.xda-developers.com/showthread.php?t=1157593
I followed everything until I got to the part where I had to go into recovery mode, but before I was supposed to reinstall packages to get into CWM I accidently clicked on delete all user data and delete cache date because I misunderstood. So I got into CWM after and followed it and rebooted but nothing happened and the SGS4G screen just goes on and off. I didnt know what to do so I gave this a try. http://forum.xda-developers.com/showthread.php?t=1001759
I thought it would bring my phone back to stock and rooted because I couldnt recover or restore anything. It just put me in a more confused situation. When I reboot in recovery or just turn the power button on, the SGS4G screen goes on and off still.
So all I can do is this. Go to recovery. reboot,reinstall,delete user data or cache data. It says "signature verification failed" then "installation aborted" when I reinstall packages. And like I said, when I reboot the system all it does is the SGS4G screen problem.
Is there a way to start me fresh to a stock and rooted point? I dont think I have any files or anything on my phone anymore(if that is possible). I wanted to try this over again, but correctly obviously
Thanks for any help. I really need my phone soon

Were you in download mode when you used Odin? It should have worked. Make sure that it shows a yellow symbol with the android alien holding a shovel.
Sent from my SGH-T959V using XDA App

Thanks for the reply! And yeah i was in download mode. Odin said it went through and it lead my phone into recovery phone. After that I rebooted but I'm still experiencing the SGS4G screen going on and off still. Nothing else loads.

How did you set up Odin? You got the correct file loaded into the PDA box?
Sent from my SGH-T959V using XDA App

mrchovee said:
So I rooted my phone a few months ago but there weren't many mods out yet, so I waited until just today. I saw this one http://forum.xda-developers.com/showthread.php?t=1157593
I followed everything until I got to the part where I had to go into recovery mode, but before I was supposed to reinstall packages to get into CWM I accidently clicked on delete all user data and delete cache date because I misunderstood. So I got into CWM after and followed it and rebooted but nothing happened and the SGS4G screen just goes on and off. I didnt know what to do so I gave this a try. http://forum.xda-developers.com/showthread.php?t=1001759
I thought it would bring my phone back to stock and rooted because I couldnt recover or restore anything. It just put me in a more confused situation. When I reboot in recovery or just turn the power button on, the SGS4G screen goes on and off still.
So all I can do is this. Go to recovery. reboot,reinstall,delete user data or cache data. It says "signature verification failed" then "installation aborted" when I reinstall packages. And like I said, when I reboot the system all it does is the SGS4G screen problem.
Is there a way to start me fresh to a stock and rooted point? I dont think I have any files or anything on my phone anymore(if that is possible). I wanted to try this over again, but correctly obviously
Thanks for any help. I really need my phone soon
Click to expand...
Click to collapse
signature verificaton failed means u dont have a modified recovery record
u can get that out of the cwm final thread and push it to system/bin folder overwrite the one dont replace it that will solve that issue for u

I did exactly what the thread for Odin said. I already had the 64bit drivers installed. I downloaded the link that was provided for the ROM and then Odin. The rom took a while to download but it finally did. After that I held both volume buttons and then plugged in the usb and then it went into download mode. After that I opened odin and then clicked on PDA. The only thing that I could click on was the non-extracted rom that I downloaded aforementioned above.Gave it time to download and it said successful. Then I rebooted once it sent me to recovery mode. It also states to try and do it without sim and sd card in the phone which i just tried. It went through as well, but still has the SGS4G going on and off

RaverX3X said:
signature verificaton failed means u dont have a modified recovery record
u can get that out of the cwm final thread and push it to system/bin folder overwrite the one dont replace it that will solve that issue for u
Click to expand...
Click to collapse
I would try that but idk how i would be able to push it into the system/bin folder when all my phone is letting me do is go into recovery mode

Did u flash ext4 yet?

A suggestion for you.
If you can get into Down load mode which it sounds like you can, I would use ODIN to flash KC1 with its pit, PDA, Phone and CSC files and let it fully load up. Then ODIN Whitehawk's deoxed KD1 + root and try to flash your other ROM again.
It is very hard to hard brick these phones. Always take care to make sure the mount points in recovery are set to unmount, mount, mount and finally unmount when instructed to do so.
If your getting stuck with the ext4 section which causes this boot loop alot, what I have done is to disable voodoo lagfix, reboot into the newly flashed ROM then go back into recovery and enable voodoo. Has always worked for me.
This is my first post so I apologize if I don't make any sense lol. I develop android apps for a medical software company and I'm wanting to start creating ROMs to help out this great community.
I forgot to mention: http://forum.xda-developers.com/showthread.php?t=1117554 - [REF]{BIBLE} Galaxy S 4G (7/24/11) <5:00pm cst> is your best friend

icbinb is a great rom. you will definitely have to odin, as bytesfree says. you should use kc1 by raver. after you odin kc1, boot up normally and let the rom settle in for 10 minutes. then get a root manager, such as super manager or root explorer. download the 2 files from krylons final cwm thread. move both to the proper location using the root manager. make sure the recovery file is named properly. if it has the extra .bin extension in the filename, remove it. then shut down the phone, reboot into recovery, go to reinstall packages and the orange cwm will load. once that loads up, factory reset, wipe cache, go to mounts and check the mounts (u,m,m,u), go to install from sd card, flash the ext4 converter immediately followed by icbinb. all of these zip files should be on the root of your sd. let me know how it goes.
if you get it to flash, remember to leave the phone sitting for 10-15 minutes in order for it to settle in.
also, bytefree, welcome to xda. glad to have you contributing.

As Jager said, ICBINB and others such as Black Ice are great ROMS with lots of tweaks and features. The guys that create these ROMs are awesome in their intellect and programming abilities. Mrchovee, once you get the hang of the steps required to flash a ROM it becomes second nature, just keep at it and don't let a gimped flash bring ya down man. As I said before, these little phones are hard to brick.

G2x Unroot Major Issues

Ok so I have been trying to unroot my G2x to acquire the new OTA update and I followed everyone's unrooting instructions perfectly, but what keeps happening is I try and hold down volume and power to access recovery mode and the first thing to happen is it does not show that little Android text like normal before you can access recovery, but instead shows the LG symbol with a blue striped bar which disappears after a few seconds and then displays an Android character and a box with an arrow with an arrow coming out of it and a status bar, then it flashes the LG symbol again without the blue bar and it just restarts the phone with all my data wiped and starts over fresh from the "Welcome to LG-P999 Touch the Android to Begin." But preserves the root and mod.
All that aside I tried accessing the recovery through rom manager which worked but every single time I try and restore the stock rom it tells me I have an md5 mismatch despite every attempt I've made to fix the md5 problem (Changing folder names/following internet help guides.) nothing seems to work. Please help me

umbral said:
Ok so I have been trying to unroot my G2x to acquire the new OTA update and I followed everyone's unrooting instructions perfectly, but what keeps happening is I try and hold down volume and power to access recovery mode and the first thing to happen is it does not show that little Android text like normal before you can access recovery, but instead shows the LG symbol with a blue striped bar which disappears after a few seconds and then displays an Android character and a box with an arrow with an arrow coming out of it and a status bar, then it flashes the LG symbol again without the blue bar and it just restarts the phone with all my data wiped and starts over fresh from the "Welcome to LG-P999 Touch the Android to Begin." But preserves the root and mod.
All that aside I tried accessing the recovery through rom manager which worked but every single time I try and restore the stock rom it tells me I have an md5 mismatch despite every attempt I've made to fix the md5 problem (Changing folder names/following internet help guides.) nothing seems to work. Please help me
Click to expand...
Click to collapse
You're trying to unroot to get the OTA update? Are you on stock 2.2? If you are then you shouldn't need to unroot.

I'm on CM7 nightly with 2.3.3 but I would prefer the more official update plus I need to send my phone into t-mobile.
Can someone plz help.

umbral said:
I'm on CM7 nightly with 2.3.3 but I would prefer the more official update plus I need to send my phone into t-mobile.
Can someone plz help.
Click to expand...
Click to collapse
I found this video helpful. I know you said you looked for help/info and probably saw this already, but I thought I would throw it out there anyway.
http://www.youtube.com/watch?v=ryGIv8KQVIE

umbral said:
I'm on CM7 nightly with 2.3.3 but I would prefer the more official update plus I need to send my phone into t-mobile.
Can someone plz help.
Click to expand...
Click to collapse
I'm helping, don't worry lol. I just needed more info. (Oh and CM7 is 2.3.4 by the way.) But anyways you said you can get into clockworkmod recovery right? Download this file from TGA_Gunnman: http://www.multiupload.com/RNN8X15ETU
Extract it using 7zip or winrar so that you have a folder called LG-P999-v10f with system.img, boot.img, etc. directly inside it
Plug your phone into your computer and mount USB mass storage, then go to the clockworkmod folder then the backup folder
Move the LG-P999-v10f folder into the backup folder on your sdcard, so now it should be (from the root of your sdcard) clockworkmod->backup->LG-P999-v10f->system.img,boot.img,etc.
Now reboot into clockworkmod recovery and restore the LG-P999-v10f backup!

Thanks for advice I did that but whenever I hit restore it says checking md5 sums then it says "md5 mismatch" and the phone stays in the menu unless i restart it and when it reboots I still have the rom.

umbral said:
Thanks for advice I did that but whenever I hit restore it says checking md5 sums then it says "md5 mismatch" and the phone stays in the menu unless i restart it and when it reboots I still have the rom.
Click to expand...
Click to collapse
You have to delete the backup that's on your sdcard right now, download from the link I posted above, and copy it over. MD5 mismatch means that the checksum file in the backup doesn't match the images. You either have a bad download or something went wrong when you copied the files over. Just try again with a new download.

Ok cool so ur saying I need to delete the clockworkmod backups and transfer the new one over?

umbral said:
Ok cool so ur saying I need to delete the clockworkmod backups and transfer the new one over?
Click to expand...
Click to collapse
Yes. Download the backup from the link I posted and transfer that over and don't change any of the files around or anything like that.

Damn I did everything but now I have a new problem now my rom manager wont take me to recovery just starts the android guy and the tmobile jingle and the volume down and power option factory resets my phone every time. Any ideas?
EDIT: Ok I had to flash it for my phone then it worked but the MD5 mismatch is still showing up

umbral said:
Damn I did everything but now I have a new problem now my rom manager wont take me to recovery just starts the android guy and the tmobile jingle and the volume down and power option factory resets my phone every time. Any ideas?
EDIT: Ok I had to flash it for my phone then it worked but the MD5 mismatch is still showing up
Click to expand...
Click to collapse
Mount your phone as USB mass storage again and make sure the image files aren't 0 bytes. It could be your SD card, your computer not copying the files over right, or it could be clockworkmod recovery. You may want to try the nvflash version of clockworkmod recovery.

Ok im confused though do I store it to the SD card or the internal memory? Cause all the clockworkmod backups are internal.

I used the LG Update tool on a rooted G2x that had a NVFlashed CWM running a GB leak. It worked flawlessly.
I did have to NVFlash again to get CWM again and flash a rooted ROM over it.
If you are just opposed to using the Update tool, then go through the pain of unrooting and waiting, but personally, I didn't have the patience.

Tried that the updater says my phone cannot connect to it despite the first screen saying it is connected. Oh well I guess im screwed.
Thanks for the help guys imma try more stuff then give up cause ive been trying to figure this out forever.

[Q] A CHallenge for Developers (partial brick) Please Help

[SOLVED]
MESSAGE TO DEVELOPERS/ANYONE WHO CAN HELP
Long story short, i edited my build.prop incorrectly and reset (yes i know very stupid) now my motorola cliq opens up to the motoblur screen but repeated messages saying "Sorry! the process X has shut down" show up.
Literaly, nearly nothing can open up but i am able to enter usb mode if i fight with the endless popups. i can also enter recovery mode because my phone was rooted before this. The problem is that my recovery image doesnt have any options that could help me
(reboot, apply sd card:update.zip, and wipe data/factory reset)
i've tried putting an official motorola update.zip onto my sd card then running the apply.. but like i told you before my build.prop is messed up a little so an error shows up saying:
Installing update...
E/:Failure at line 1: assert file_contains("SYSTEM:build.prop", "ro.build.fingerprint=motorola/morrison_two_us/morrison/morrison:1.5/CUPCAKE/1.4.8:user/rel-keys" == "true" || file_contains("SYSTEM:build.prop", "ro.build.prop", "ro.build.fingerprint=MOTO/morrison_two_us/moInstallation aborted
Press Menu+Back to reboot
All i need to do is fix the line of code i messed up but i cant reach my systems files,...i attached my original build.prop and a copy of my corrupted one to show you.. I also cannot use the phone service or network service (even wifi) because like i said, nearly ALL the services are unable to stay on, they immediately shut off at startup.
Ways to fix this would be to REACH/EDIT THE SYSTEMS FILES
1. I cant use an app like root explorer since i cant access any apps on my phone even things like my settings
2. Turn on usb debugging somehow (I cant access my settings app so im lost on this one)
1. ingenious DESKTOP program that can somehow access my phone's system files without adb (if it can access the sd there has to be a way..)
3. Ive looked around to maybe find a custom image recovery that had options like editing system files (shouldn't be hard to make..) but ive found none with that option and im not sure how i would install it without adb...
What i CAN do
1. ENTER USB MODE (that has to count for something so Developers Please help me)
2. I can play with the motoblur intro screen to some degree to make it go away, then a blank black home menu appears. If i wait a while for the popups to stop at the motoblur screen, i follow the instructions but it gets stuck at registering a new account or existing one since you need network access.
3. ENTER REVOVERY MODE (but the only option that looks helpful is the sdcard update which gave me an error...) I havent tried the wipe data/factory reset because the factory reset doesnt touch the build.prop so its pointless
WHat should I do? WHoever sees this please give me advice or direct me somewhere to get it... THANK YOU
[EDIT]
BTW what i was trying to do on the build.prop was replace this line (ro.build.fingerprint=generic/sdk/generic:3.2/HTJ85B/140714:eng/test-keys)
with (ro.build.fingerprint=verizon/voles/sholes/sholes:2.1-update1/ESE81/29593:user/release-keys)
but i messd up and put
(ro.build.fingerprint=verizon/voles/sholes/sholes:2.1-update1/ESE81/29593:user/rel)
youll see this in the attachments...what this does is unlock my 1.5 firmware market to ALL the apps (updating to the official 2.1 using recovery wouldve handled this but i didnt even know of this update till after my mistake)
I just thought id mention...

if you have adb abilities you can push the old build.prop. If you do not know a out this then post back and I will help you.You said you can enter recovery, but that is stock original recovery that anyone can get access to. If you ever bootstrapped your phone you can try pull the battery out, wait about 10 seconds, then plug your phone charger in without the battery in. If your bootstrappped this will pull you into a more advanced recovery mode. The last option is to use rsd lite to flash an sbf to your phone if nothing else works. If you have never done this just look up sbfing motor cliq to stock.
Good luck, and remember to thank me if this helped

SOLVED!!
I fixed my phone on my own but THANKS to rootfan for being the first to answer.
HERES HOW:
I was able to access recovery mode and from there i discovered the sd update option.
It took hours of research and work but i learned alot about adb,motorola, cliq, etc.
Anyway, i originally found the Blur_Version.2.1.5.MB200.T-Mobile.en.US.zip and i tried to put that in my sd card (i could get into it from the phone) but when i tried to update using recovery it gave me an error so i decided to try the "latest 1.5 with Blur 1.6.1" which was actually very hard to find... you can get it here
motorola. com/staticfiles/Support/Experiences/sdcards/US-EN/tmo/cliq/downgrade-to-cupcake .html
Lastly, i put that on my sd as update.zip, went into recover, and the update was SUCCESSFUL! MY PHONE REBOOTED AND NOW IS ACTING NORMAL AGAIN. Now, im trying to update to the Android™ 2.1 (Eclair):
motorola. com/staticfiles/Support/Experiences/sdcards/US-EN/tmo/cliq/2-1_index. html
but im still getting that error whether i update using recovery or the settings/about phone/system update option... Thats strange but my phone is still working normally and ill find a way to update to 2.1...
ONCE AGAIN THANKS TO ROOTFAN AND HOPEFULLY THIS POST WILL WORK FOR SOMEONE ELSE WHO MAY BE HALF-BRICKED (no adb, no usb debug, no root explorer) THERS STILL HOPE IN RECOVERY+USB DRIVE+BLUR VERSION SOFTWARES

Thanks man, now this is probabaly a redicilous reply, since im sure you would have already tried this, but you can try going into settings, about phone, and click on update and see if the 2.1 eclair ota update will work on your phone.

i've got a simila problem on my samsung Galaxy S5570...
... and i need to prepare an update.zip .
Can you help in this, or you only downloaded a new rom ?

stepph said:
i've got a simila problem on my samsung Galaxy S5570...
... and i need to prepare an update.zip .
Can you help in this, or you only downloaded a new rom ?
Click to expand...
Click to collapse
You can reflash a stock rom back if you wanna get it done easily - or even a updated gingerbread one from samfirmware.com
Search for S5570 in these fora for some guides

[RESOLVED] Screwed up - Recovery will not load, neither will RSDLite - stuck

My phone is a Motorola Milestone A853.
I was testing out the new CM9 mod by kabaldan when I found myself running into a huge screw-up. No, not one that I believe is not reparable. Just one that is hard to get out of. Let me explain:
Having a wi-fi problem on multiple versions of the CM9 alpha ROM for the Milestone, I found myself trying to debug the situation in many ways. i.e. reflashing the ROM, wiping data/caches repeatedly... and trying a purported fix in the CM7 thread that did not work. In the middle of things, I decide do to format my SD card.
Bad idea.
Since the SD card pretty much contains OpenRecovery among other things it got wiped. Now I pretty much cannot access my recovery (which is Androidiani OpenRecovery).
I actually had the OpenRecovery folder backed up onto my hard drive, but copying it back has resolved nothing. It gets to that icon, stays there for a second, then fails and reboots back into the main OS.
This has happened to me before during about when I just got into modding the phone ROM (recovery screw up), which I recovered from using RSDLite to reflash a recovery. But now RSDLite does not even recognize my phone - this may have to do with the fact that it's running the CM9 ICS alpha ROM. So I can't repair the recovery, and I can't get my phone back to where it previously was and solve the wi-fi problem.
Thank goodness this has happened on a free long weekend. My phone is actually okay to use when I turn it on(can make calls, messages) but has none of my apps and whatever on it and I cannot fix anything with recovery, so on-the-go usage is near-useless. At the least I have a backup (Novo 8 tablet) for on-the-go stuff. But I want to get my phone back right away.
I know that there is another way to do this (sbf_flash I believe). I have access to a laptop running Xubuntu Linux (my old laptop, which was replaced by my tablet) to use sbf_flash, but is it possible to use it from Windows? (I think so).
Thanks to anyone that can help. I've done a lot of searching so far but I haven't found a huge amount plus I want to focus on getting this done and fixed sooner. I'm looking forward to full-fledged use of ICS on my Droid; from my experience so far, it's much faster than what I have moved from (latest version of MIUI).

What os do you have now?
You've been flashing stock roms. This restores stock recovery. Hence the need to flash vulnerable recovery or OpenRecovery will not work.
Along with OpenRecovery folder you need update.zip file.
Try to reinstall drivers since RSDLite shouldn't care what OS is on the device. Maybe it'll solve pc->device conectivity.
RSD won't detect device unless in bootloader mode.
If recovery won't boot automatically press volume up + camera.
Everything you might need is on this thread! Look for it.
1) "My phone is a Motorola Milestone A853"
2) "I'm looking forward to full-fledged use of ICS on my Droid"
The second is a pet talk I guess?

I thought RSD required that Phone portal USB connection option through the phone be working for recognition. Nothing happens in bootloader mode, pretty much. But I'll look into it. If RSD really shouldn't care about the OS on the device then I def have some driver reinstalling to do; is that true?
Current OS installed is the CM9.0 (ICS Android 4.0.3) alpha by kabaldan.
Same occurs when doing volume up + camera. Loads for a second, then quits (i.e. files not present, cannot complete loading).

You use RSDLite to flash .sbf files. That works only in bootloader mode.
When in bootloader mode and when you plug in usb cable the device should respond with something like USB OK, don't remember anymore, as should rsd give some info that the device is connected (left and right parts of main window provide info about device and the sbf file, respectively).
RSD finishes, phone boots, you reboot in bootloader, flash vulnerable recovery, prevent booting to OS and instead boot to recovery (OpenRecovery by now) by pressing hw keyboard X, verifiy that /system/etc/install-recovery.sh does not exist but if there delete it! or system will restore stock recovery.
More detailed instructions can be found on this forum and this thread.
Prior doing any of above: verify that you have openrecovery folder and corresponding update.zip in the root of your sdcard. Then try to boot to OpenRecovery as it seems to me that your main (or only) problem is that recovery on sdcard is broken.

or get another sdcard with recovery on it,insert on your phone and tadaa

Actually I tried returning the OpenRecovery folder and files (which I backed up onto my hard drive) onto the SD card and it did not work. I did not, however, move back the update.zip file. Perhaps the update.zip file had something to do with the boot ability? Because when I restored that (I didn't earlier), it finally went into recovery. So, problem solved everyone thanks!

xd_1771 said:
Actually I tried returning the OpenRecovery folder and files (which I backed up onto my hard drive) onto the SD card and it did not work. I did not, however, move back the update.zip file. Perhaps the update.zip file had something to do with the boot ability? Because when I restored that (I didn't earlier), it finally went into recovery. So, problem solved everyone thanks!
Click to expand...
Click to collapse
Just to prevent anyone else from having the same problem, I'm going to point out this:
update.zip from any of the recovery packages is needed every time you boot into recovery. It's a "special" update that is designed to crash the bootloader's update function and run unsigned code, such as a 3rd party recovery. Nothing ever actually gets flashed when this update is run.
Without the update.zip, you have no way to tell your device to launch the custom recovery, as we can not flash a replacement directly to the phone's memory because of Motorola's stupid signed-code-only checks.