Database Develop

[Q] Need help with restoring backup from ROM Manager

I've been searching, and reading, and my eyes hurt. I normally don't like to post threads, but I'm left with no choice. If this topic has been covered, then I guess my searchin' skillz are stating to lack. Here is my delimna:
Rooted, Lagfix, enabled Side-loading, recently installed ClockworkMod, stock firmware. I ran a backup using ROM Manager/ClockworkMod. I was attempting to install the Mobile AP fix for WiFi Hotspotting from designgears. I downloaded the new kernel per instructions (Mobile AP ony). I first tried installing it using ROM Manager's boot option into Clockwork without renaming MobileAP.zip. Still received black screen when I open the Mobile AP settings that the new kernel was trying to fix. So I thought that the flash didn't work, so this time I renamed the kernel file to update.zip and did the standard method of flash using stock recovery mode.
Now the phone boots to the Galaxy S screen, then just a black screen. The bottom row buttons seem to be active, but nothing happens. Holding power....nothing. I have to pull the battery; however, I can boot into stock recovery.
Now here's the delimna. I can boot into recovery, but the update.zip file is NOT the one for ClockworkMod, its the modified kernel. Is there a way that I can browse the files on the phone so I can change the update.zip file? I want to put Clockwork's in place so I can restore using my backup made yesterday....It's not a huge order if I have to flashback to stock and lose everything as I usually do that everynow and again anyways (usually I'm prepared). I won't lose anything important that isn't already backed up except maybe some pictures....
BUT, I can't help but try. It's just me I like to break stuff and fix 'em. I want to try to run that backup I made. I have Odin, and I tried flashing the kernel back to stock (i had one hell of a time finding information on how to use it). As a matter of fact, I found instructions on HOW to use it, but I gave up trying to find useful information on how the program runs (like a user guide, what else can it do, that sort of thing....). I spent hours reading thread after thread........information overload I guess.
I figured someone might point me in the right direction. How can I browse/edit the contents of the phone while in Recovery or Download mode?

You could try letting the phone boot up, yes I know it's only a black screen, then plug in the usb to your PC and see if ADB works.
If so then just adb shell into it and work with command line.
I'm not sure if ADB would work in stock recovery mode but that's worth a shot too.

Excellent idea, but no luck. I can get the computer to recognize the phone in recovery mode, but ADB shows the device offline, and Windows Explorer shows 2 drives with the whole "insert disk into drive ..." message. Can't boot phone to enable "development mode", that might have something to do with it......unless I'm missing something?

swedishcancerboi said:
Excellent idea, but no luck. I can get the computer to recognize the phone in recovery mode, but ADB shows the device offline, and Windows Explorer shows 2 drives with the whole "insert disk into drive ..." message. Can't boot phone to enable "development mode", that might have something to do with it......unless I'm missing something?
Click to expand...
Click to collapse
Wasn't sure if that would work or not.
So, if you turn it on and just let it sit as long as a normal boot, then try adb does anything work?

I actually let it sit for ~15 minutes. computer doesn't even register the usb being plugged in. I'm going to give it another go or two, but in about an hour I'm going to have to call it quits and just flash it with Odin. Don't want to give up yet, but I am driving out of town later this afternoon and must have my phone for the trip. Maybe I'll break it again tomorrow and play with it over the weekend!
Let me know if you have any other ideas. I'll let you know when I give up.

While on that subject (watch someone tell me to move my post after this.....), maybe I'll experiment with a new ROM. Any recommendations? (without OC, device is fast enough). I haven't read much on the different flavors available at the moment (I think I read something about a 2.2 from I9000 or something?).

swedishcancerboi said:
While on that subject (watch someone tell me to move my post after this.....), maybe I'll experiment with a new ROM. Any recommendations? (without OC, device is fast enough). I haven't read much on the different flavors available at the moment (I think I read something about a 2.2 from I9000 or something?).
Click to expand...
Click to collapse
Hybrid from eugene is pretty fast especially if you add the voodoo kernel to it. Thats what I heard tho. Because when i tried it out it was pretty quick with out a lagfix and without autokiller. Only used it for 20 min tho as i couldn't get Titanium backup to work. I think the titanium problem is a hit or a miss.

well, I guess I'm going to have to load stock and wipe everything...oh well. Let's see how this goes. Then I'll start playing with ROMs this weekend. Thanks anyway!

swedishcancerboi said:
well, I guess I'm going to have to load stock and wipe everything...oh well. Let's see how this goes. Then I'll start playing with ROMs this weekend. Thanks anyway!
Click to expand...
Click to collapse
Well, if your going to do that take an extra 2 minutes and load Eugenes Hybrid R3 while your at it. It's extremely easy to do and in my opinion the fastest thing we can put on these phones right now.

Vibrant ROM? is that safe? I mean, I know they are all Galaxy S, but is the hardware really that identical?

I don't think eugenes captivate hybrid is actually a vibrant rom. I think he just borrowed some of the better parts.
Sent from my SAMSUNG-SGH-I897 using XDA App

Got it! I used the one click stock down loader to get the phone to boot. I then noticed that many of my files were still there, music, zips.....so I thought....maybe my backup is still there.
Instead of using my original root, I decided to try Unleash the Beast.applied it so I could load Rom Manager.i opened Rom manager and it showed my backup!
I tried restoring then without success (no update.zip) and had to flash clockwork (even though it showed it already loaded, guess it needed to be refreshed, makes sense since it is a fresh firmware), selected my restore and it ran like a charm.
I am just surprised. I thought the act of flashing the Rom would wipe everything. Apparently not if you never do the "master clear."
Thankfully I had just installed Rom Manager the day before and had a fresh backup. Looks liked I'm gonna have to start shelling out more beer money to the devs!
Now I can prepare to break it again and again. Let the fun begin!
Sent from my SAMSUNG-SGH-I897 using XDA App

Nice. Yeah, stuff you have stored on your "internal SD" is safe between flashes. Of course apps, contacts, etc get wiped, but that's an easy fix.

"the more you know," eh? Ha!
Sent from my SAMSUNG-SGH-I897 using XDA App

Update.zip for . 340 Kernel, Radio Image, Bootloader, and System!

Hey all, Team Black Hat have released a series of update.zip’s that will allow you to easily flash the newest kernel, radio, system, and bootloader. Thought some might wanna download ASAP in case they get pulled.
Article About it here:
http://www.gizmoninja.com/2010/12/1...date-your-kernel-system-radio-and-bootloader/
Direct link To Team Black Hat Thread and Downloads:
http://www.mydroidworld.com/forums/...ystem-baseband-2-3-340-kernel-bootloader.html
Cheers! And all credit and thanks foes to Team Black Hat!

If I flash the system.zip from recovery will it take me from Tranquility 3.6 back to stock? What's the best way to go from Tranq back to stock? Thanks.

Flashing the kernel and radio as I type.

aaaaand SBF time lol.

Sorry.. just trying to understand...
I have downloaded these 4 files. Now I go to Bootstrap/Recovery and use the Update.zip option for these files one at a time? (in a particular order?) OR do I re-name them update.zip one at a time?
Secondly, I have ApeX 1.2.1 installed... it's working with .320 and I wonder if it will work with the new files?
Any advice on these 2 things. (please)
Thanks.

romanvail said:
Sorry.. just trying to understand...
I have downloaded these 4 files. Now I go to Bootstrap/Recovery and use the Update.zip option for these files one at a time? (in a particular order?) OR do I re-name them update.zip one at a time?
Secondly, I have ApeX 1.2.1 installed... it's working with .320 and I wonder if it will work with the new files?
Any advice on these 2 things. (please)
Thanks.
Click to expand...
Click to collapse
To answer your first question, we don't need to rename them. We can got o bootstrap and update them one by one. I don't think there's a particular order, however, I do think that we can only do one at a time (install one and then reboot)
I'm not sure about coming from Apex, i'm personally coming from Fission 2.3.1, and I am a little scared to do these....

zeavott said:
To answer your first question, we don't need to rename them. We can got o bootstrap and update them one by one. I don't think there's a particular order, however, I do think that we can only do one at a time (install one and then reboot)
I'm not sure about coming from Apex, i'm personally coming from Fission 2.3.1, and I am a little scared to do these....
Click to expand...
Click to collapse
Yeah no renaming is needed.
I am on fission 2.3.1 as well, flashed the Kernel, Bootloader, and Radio Image all one after another while in clockworkmod recovery, and had 0 issues.
U will have to *228 again after radio, but other than that u its fine.

So I just got a question..is this the file that is downloaded ota or put together by these guys? I only ask cause trying to understand why we can't just throw in our own stuff in this update.zip and resign it..but I am sure there is some kind of keys we will be missing

Did the 2.3.340 SBF also update the radio or should I use the .zip to update that?

mdhaliwal said:
So I just got a question..is this the file that is downloaded ota or put together by these guys? I only ask cause trying to understand why we can't just throw in our own stuff in this update.zip and resign it..but I am sure there is some kind of keys we will be missing
Click to expand...
Click to collapse
Lol, if only it were that simple, unfortunately we can't because of the bootloader being locked, it wont pass security, so we can only modify or use their kernels.
Sunblood said:
Did the 2.3.340 SBF also update the radio or should I use the .zip to update that?
Click to expand...
Click to collapse
If u did the .340 sbf u should be all up to date, this is more for .320 users and such. U can double check ur kernel, radio version in about phone though as well.

ive recently upgraded from my Eris to an X so im having a hard time understanding all of what i need to do, ive downloaded these files and saved them cuz im sure ill need them as soon as i learn everything can anyone point me to a cut and dry tutorial or some kind of explanation? thanks!!!!! loving the x already
edit: i am searching while im waiting for an answer, my bootloader says 30.04 but i dont understand the whole sbf stuff and i can get into clockworkmod recovery im not completely helpless just a little lost after playing with my eris so much.

Confused
I downloaded each file then rebooted into recovery. I installed each file one by one. I reboot system out of recovery and I get a black screen that says:
Bootloader
30.04
Err: A5, 70, 39, 00, 27
Battery OK
OK to Program
Transfer Mode:
USB

btw as far as i can see by the numbers my version is the .340 and the 1.09.07P baseband....i updated mine yesterday

acidbath5546 said:
If u did the .340 sbf u should be all up to date, this is more for .320 users and such. U can double check ur kernel, radio version in about phone though as well.
Click to expand...
Click to collapse
The .340 sbf is system only so no he wouldn't be up to date. His system would but not anything else. Still have to apply the patches if you want to be 100% up to date with everything.

mob87 said:
The .340 sbf is system only so no he wouldn't be up to date. His system would but not anything else. Still have to apply the patches if you want to be 100% up to date with everything.
Click to expand...
Click to collapse
k thanks guys updating now

mob87 said:
The .340 sbf is system only so no he wouldn't be up to date. His system would but not anything else. Still have to apply the patches if you want to be 100% up to date with everything.
Click to expand...
Click to collapse
Oh yeah ur right...forgot .340 is system only...haven't had to SBF in a long time...lol
Thanks for catching that.

I am on Fission 2.2.2 (FRG83), would these updates work for me?

So I am somewhat familiar and want to make sure. I can not get my 2.3. 340 update to go will these files let me do this
Sent from my DROIDX

im at the same screen what to do??

[Q] SGS user urgently need help!!

Firstly guys, I'd like to apologise for this being my first post. I'm usually a regular over at the SGS forums but am yet to have had a response. I'm ****ting bricks currently, so here goes...
ARGH wtf. Just as I thought I had the perfect phone, it messes up! Darky's ROM went mad on me. Kept rebooting the phone. Kept vibrating throughout. No idea what's wrong with it. Tried to do a wipe install of the ROM again, but the bloody thing has disappeared from the SD card! What am I going to do now? Reflash back to my previous firmware and start all over again, AGAIN? Ffs.
Just for the record, I'm basically stuck in recovery mode. It's either that or staring at the Nexus S logo as it attempts to boot, over and over and over... I'm so angry right now! I didn't do anything to the phone for this to happen! Bad luck or what. Really hope there is a solution to this. I don't suppose there's anyway of accessing the device's SD memory when in recovery mode? I just need to plant the update.zip on the SD card again so I can reflash it!
Click to expand...
Click to collapse
I would massively massively appreciate any help you guys could give me. I've had nothing but bad luck with my Galaxy S
[EDIT] Oh and by the way, I still have full access to my three-button combo modes. Clockwork recovery console and Download mode still fully accessible.

Hi
I'm also new here and got my SGS yesterday, but i had a HTC Desire before.
If you can get in to Clockworkmod recovery you should be able to push the file via adb to the sdcard. That was possible on the Desire at least.

vippe said:
Hi
I'm also new here and got my SGS yesterday, but i had a HTC Desire before.
If you can get in to Clockworkmod recovery you should be able to push the file via adb to the sdcard. That was possible on the Desire at least.
Click to expand...
Click to collapse
Hey there, thanks for your response! What may I ask is 'adb'?

Android development....something
Just flash back to eclair again. The time it took you to get an answer on a forum is longer tham the time it takes to flash.
Sent from my GT-I9000 using XDA App

I'm guessing you screwed up without diabling lagfixes or something, just install JM8 with repartition enabled and using pit 512 file again then install clockwork update.zip then install whatever rom (but in this case darkys). It starts to become habbit when testing new roms to do all of them steps, The first time something happens you **** bricks but soon relize the SGS is alot more brick poof then you think (unless you are one of the poor souls with broken recovery modes)
But anyways, calm the hell down. Everything is fine.

ickyboo said:
I'm guessing you screwed up without diabling lagfixes or something, just install JM8 with repartition enabled and using pit 512 file again then install clockwork update.zip then install whatever rom (but in this case darkys). It starts to become habbit when testing new roms to do all of them steps, The first time something happens you **** bricks but soon relize the SGS is alot more brick poof then you think (unless you are one of the poor souls with broken recovery modes)
But anyways, calm the hell down. Everything is fine.
Click to expand...
Click to collapse
I've absolutely no idea what files to flash... I'm a bit of a noob when it comes to flashing with the SGS. Quite embarrassing actually because I used to flash my old Omnia HD with no problems whatsoever! Don't suppose you could link to files.

Don't worry, your Galaxy is not bricked. Please see here how to reflash from a PC.

I've downloaded all necessary files... I've got a CODE a MODEM the 512.pit but no CSC? Am I okay to flash with no CSC?

Eddzz!! said:
I've downloaded all necessary files... I've got a CODE a MODEM the 512.pit but no CSC? Am I okay to flash with no CSC?
Click to expand...
Click to collapse
CSC contains all carrier-related (like APNs) data.
Depending on the type of packaging some CODE files are complete with CSC.
In any case, you can flash a CSC (like ITV or XEU) even later.
Before to go with flash, I'd like to advise you to backup /efs folder on your SD and/or your PC. This is the only folder with information (like your IMEI configuration) that cannot be recovered in case of a total data loss.

After a long gruelling process of flashing and reflashing, I'm back on Darky's ROM. Problem though - App market is messed up. I can't download anything from the Market and it's also the 'old' Market theme... I think has something to do with the fact that I've flashed from Eclair straight to Darky's? (Which I was advised to do...) - How can I get my Market working again?! Everything is fine besides that!
[EDIT] I now have the new market interface but still cannot download a thing!

Is it simply impossible to get cyanogenmod for Milestone?

Hi there,
Before anyone gets angry: I don't want to start a 1000st repetition of questions asked right 2 posts before, nor am I too lazy to use google or read the articles themself.
I just want to know, if there's somebody out there, who succeeded with exactly the same circumstances I failed.
I own a German Motorola Milestone . It is a Milestone, not a Droid! I guess, this is important, since I've read tons of these threads, which all ended in that way, that one tells that the Milestone is a lot stronger protected than the Droid from Verizon is, because it uses Signatures and stuff, to prevent anwanted development for the device.
I always was too shy to apply something like cyanogen to my phone or even root it, because I spend some hope to the (at last) shipped Froyo Update for the device, to make things better. But since Motorola not even raised the CPU clock (which runs only at 550, but 1200 MHz are reported to work without negative issues) to even 800 MHz and I can feel this with Froyos animations and Flash, I decided to give cyanogen a try. I tried to root the device (which succeeded) and tried also all overclocker apps on the market which made the device reboot instantly when applying (but did not raise the speed).
Now I'm trying to install cyanogen since several days, but all guides fail for me.
It all fails when it comes to applying the update.zip: Clockworks's rom Manager, which tells me that the recovery Programm couldn't be found at the boot prompt, opening the update.zip directly gives a message about something's failing with the certificates, ... an endless story
I come more and more to the guess, that all success messages for applying cyanogen to a milestone are only hoaxes, because someone couldn't tell the difference between a milestone and a droid on ebay and such.
I would be very thankfull for any answers, may they tell me that this is true, or that they have succeeded (and how!) Or even hand me the right guide. I have the feeling that I've allready read all the false ones
Sent from my Milestone using XDA App

Richter_Marc said:
Hi there,
Before anyone gets angry: I don't want to start a 1000st repetition of questions asked right 2 posts before, nor am I too lazy to use google or read the articles themself.
I just want to know, if there's somebody out there, who succeeded with exactly the same circumstances I failed.
I own a German Motorola Milestone . It is a Milestone, not a Droid! I guess, this is important, since I've read tons of these threads, which all ended in that way, that one tells that the Milestone is a lot stronger protected than the Droid from Verizon is, because it uses Signatures and stuff, to prevent anwanted development for the device.
I always was too shy to apply something like cyanogen to my phone or even root it, because I spend some hope to the (at last) shipped Froyo Update for the device, to make things better. But since Motorola not even raised the CPU clock (which runs only at 550, but 1200 MHz are reported to work without negative issues) to even 800 MHz and I can feel this with Froyos animations and Flash, I decided to give cyanogen a try. I tried to root the device (which succeeded) and tried also all overclocker apps on the market which made the device reboot instantly when applying (but did not raise the speed).
Now I'm trying to install cyanogen since several days, but all guides fail for me.
It all fails when it comes to applying the update.zip: Clockworks's rom Manager, which tells me that the recovery Programm couldn't be found at the boot prompt, opening the update.zip directly gives a message about something's failing with the certificates, ... an endless story
I come more and more to the guess, that all success messages for applying cyanogen to a milestone are only hoaxes, because someone couldn't tell the difference between a milestone and a droid on ebay and such.
I would be very thankfull for any answers, may they tell me that this is true, or that they have succeeded (and how!) Or even hand me the right guide. I have the feeling that I've allready read all the false ones
Sent from my Milestone using XDA App
Click to expand...
Click to collapse
OK, lets start over with your phone using some different method using my own guide. Do these steps to install CM 7 on your phone
1. Revert your phone back to stock
2. Install Androidiani OpenRecovery
3. Install Custom ROM
All from my guide: http://forum.xda-developers.com/showthread.php?t=983516
If you got any question ask them in the thread or PM me

1. Clockworks's rom Manager doesn't work on Milestone. I screwed that up too so don't feel too bad about that lol.
2. Start here http://forum.xda-developers.com/showthread.php?t=784750
You want CM so start with the CM for milestone thread that explains it directly.
From that page, get Androidian Open Recovery and prepare you SD Card.
3. Now follow instructions on this page: http://android.doshaska.net/rootable.
a. Install RSD Lite 4.6
b. Get the vulnerable recovery sbf and apply it with RSD Lite. (It's tiny... about 5mb)
c. Grab the "Disable_recovery_check_by_OTA" script and put it in sdcard/openrecovery/scripts folder.
4. Put CM6 or CM7 update.zip in the sdcard/openrecovery/updates folder.
5. Boot into Open Recovery. Apply the script from step 3
6. Install CM from the Apply Update menu.
edit: I didn't see post#2 when I hit send lol. I had started, went to do something and finished when I got back.

First of all: Thank both of you for your very nice (and unbelievable quick) replies!
Since you two suggest quite equal ways, and report that even this stupid EU-Brick is capable of running cyanogen, I'm quite enthusiastic, that I will succeed in the next days
I'll update the status here as soon as I git a new one.

eXtink said:
OK, lets start over with your phone using some different method using my own guide. Do these steps to install CM 7 on your phone
1. Revert your phone back to stock
2. Install Androidiani OpenRecovery
3. Install Custom ROM
All from my guide: http://forum.xda-developers.com/showthread.php?t=983516
If you got any question ask them in the thread or PM me
Click to expand...
Click to collapse
Hi eXtink,
I followed your guide and succeeded for an impressive long time. All went well:
I ...
applyed the german .sbf succeffully
booted / set up successfully Androidiani OpenRecovery 3.3
gained root
Installed Cyanogen 7 (0.08-11.03.16 RC3)
All these steps ran without displaying any error. But now, when I reboot the device, I only see the blue Cyanogen - Droid, skating within a blue circle. This hasn't changed several times for more than 10 Minutes now.
Can you tell what's wrong here?

do you see the first bounce again and again?
If it does, it's boot looping which isn't good.
But it usually takes a long time to load the first time...
So if it's not bootlooping, and it's going on for like 15 minutes, you can press shift alt delete to reboot and then try again and it should load quicker

No, it's not resetting or such, it just displays a smooth circle , but this rotates for over 10 Minutes (I rebooted it after that and re-issued a standard Froyo image onto the device after that.).
But you think I should wait for it to boot for ~15 minutes and then, while it still displays the loadspinner, reboot it? Did I understand you correct?

yeah, if it's not bootlooping and you're tired of waiting... just reboot it again.
Sometimes it just gags...
Say, did you feel the phone vibrate at all?
If you did, the lock screen was already up but hidden behind the animation

It godamn works !!! O.O Dunno what I've changed to make this habben, but when I try the exact eaqual steps again, it just works. Everything!
You two are my heroes!!! Thank you very much!
Cyanogenmod 7 on EU - Milestone - Working !!!

Cool Beans!
I'm glad that it worked for ya!
Bonus: this thread is a pretty good "how to"!

i must give it a try for my self. i need to install Cyanogenmod too cuz i had enough with the official one

guys i am not able to perform root, im stuch at the Open Recovery stage and it is unable to locate the Update.zip in the SD Card though it is on the root. there is a problem with the Cashe file :s. any help??
and the message is:
E: can't open cache/recovery/command
--install from sdcard..
finding update package..
openinng update package..
verifying update package..
E:EOCD marker occurs after Start of EOCD
E:signature verification failed
Installation aborted
Any Ideas??

3mar84 said:
guys i am not able to perform root, im stuch at the Open Recovery stage and it is unable to locate the Update.zip in the SD Card though it is on the root. there is a problem with the Cashe file :s. any help??
and the message is:
E: can't open cache/recovery/command
--install from sdcard..
finding update package..
openinng update package..
verifying update package..
E:EOCD marker occurs after Start of EOCD
E:signature verification failed
Installation aborted
Any Ideas??
Click to expand...
Click to collapse
Did you flash the vulnerable recovery?
If so, did you copy the openrecovery folder to the root of your sdcard?
Sent from my Milstone running CM7

Just put update.zip and OR on u SD card (directly). Tur off phone launch bootloader by RSD instal vulnarable recovery. Then turn off and then power+X update.zip and u are at home

thanks guys for your posts...
I already have placed the file on the root of the SD. but seems i had a problem with the ROM, when i tried using another ROM it worked. the problem is that when i was about to continuie Rooting the machine the Touch Screen is not working any more!!! seems i lost my piece!!

zeppelinrox said:
1. Clockworks's rom Manager doesn't work on Milestone. I screwed that up too so don't feel too bad about that lol.
2. Start here http://forum.xda-developers.com/showthread.php?t=784750
You want CM so start with the CM for milestone thread that explains it directly.
From that page, get Androidian Open Recovery and prepare you SD Card.
3. Now follow instructions on this page: http://android.doshaska.net/rootable.
a. Install RSD Lite 4.6
b. Get the vulnerable recovery sbf and apply it with RSD Lite. (It's tiny... about 5mb)
c. Grab the "Disable_recovery_check_by_OTA" script and put it in sdcard/openrecovery/scripts folder.
4. Put CM6 or CM7 update.zip in the sdcard/openrecovery/updates folder.
5. Boot into Open Recovery. Apply the script from step 3
6. Install CM from the Apply Update menu.
edit: I didn't see post#2 when I hit send lol. I had started, went to do something and finished when I got back.
Click to expand...
Click to collapse
Hey I'm new here and really want to be able to get Cyanogen 7 on my Milestone (Canadian version) My only question with your how to guide here is how to install open recovery on my phone. sorry I'm very new to this stuff and dont know a whole lot.

Led Head said:
Hey I'm new here and really want to be able to get Cyanogen 7 on my Milestone (Canadian version) My only question with your how to guide here is how to install open recovery on my phone. sorry I'm very new to this stuff and dont know a whole lot.
Click to expand...
Click to collapse
Once you flash the Vulnerable Recovery via RSD Lite, you want to place the AOR files that you can get from the sticky in Milestone development section onto the root of your SD card.

skadude66 said:
Once you flash the Vulnerable Recovery via RSD Lite, you want to place the AOR files that you can get from the sticky in Milestone development section onto the root of your SD card.
Click to expand...
Click to collapse
OK thanks! One more question though. is there a specific sbf I need? I have a vulnerable recovery sbf called "vulnerable_recovery_only_RAMDLD90_78.sbf" would this be the right sbf for a canadian Milestone on telus? if not I found a thread on this forum that has a link to a vulnerable recovery sbf for telus milestones (found here http://forum.xda-developers.com/showthread.php?t=983516 )
also my device wont show up in RSD, why would this be? I've tried hitting the show device button numerous times but nothing happens

Led Head said:
OK thanks! One more question though. is there a specific sbf I need? I have a vulnerable recovery sbf called "vulnerable_recovery_only_RAMDLD90_78.sbf" would this be the right sbf for a canadian Milestone on telus? if not I found a thread on this forum that has a link to a vulnerable recovery sbf for telus milestones (found here http://forum.xda-developers.com/showthread.php?t=983516 )
also my device wont show up in RSD, why would this be? I've tried hitting the show device button numerous times but nothing happens
Click to expand...
Click to collapse
Yes, the SBF that you have (vulnerable_recovery_only_RAMDLD90_78.sbf) is the one that you can use. I used it for rooting my Telus Milestone as well. When you want to revert back to stock, that's when you'll need a Telus-specific SBF.

skadude66 said:
Yes, the SBF that you have (vulnerable_recovery_only_RAMDLD90_78.sbf) is the one that you can use. I used it for rooting my Telus Milestone as well. When you want to revert back to stock, that's when you'll need a Telus-specific SBF.
Click to expand...
Click to collapse
k great thanks! so I got CM7 for milestone installed on my phone, and it loads up and everything but every few seconds i keep getting a message android.phone stopped responding. So I essentially cant do anything cause this message keeps coming up, also I'm getting a no service signal too, its not registering with Telus. Please help

[Q] wrong sbf? need proper one for (RTGB)

first post, yes, i'm new to this... (forum, not flashing, not entirely anyway, i did fiddle with Sony Ericssons and stuff, kindergarden compared to androids)... but not an idiot, to the point:
firmware config. version seems to be RTGB, great britain, right? wrong, a RTUK is not it. I am sort of lost, i bought the phone with 2.1-update1, the 2.2.1 update has not yet been rolled out in my backwards country, so i did an official update over the internet with motorola app etc etc. I have no idea what was the 2.1 fw config. ver., but it strikes me as weird that i have a RTGB one now, the packaging/box/manuals all were German or something that looks like German. And now, i got myself RTUK sbf file, and RDS lite fails to do anything. I require assistance, and an explanation if possible as to why this didnt work? if i chose the wrong sbf, why does it show me having RTGB? and finally which sbf to take and from where (two german one's are available on this forum), but i've seen only one RTGB and it was only 2.1. For comparison, the friend bought the same phone on the same day, but she got one with a qwertz keyboard, mine is normal qwerty, fw config. ver. shows VFDE, did not update hers, it's still 2.1-update1. I can only assume that VF is german for RT and that her phone did not come from an unknows source. The phone company selling these obviously imports them, possibly even from random countries or EU countries at least...
however something did happen, my battery in the notification seems to be not present, there's just a question mark inside what appears to be an empty battery... apps that show battery levels work fine... although, scratch this last one, a reboot fixed it, even though i have not seen it before.
also, help me rack up some posts ^^ ask for info or whatever, i'd like to give a shot at improving my android...

Check the link below. You will get both service and non-service versions of 2.2.1 sbf's.
http://and-developers.com/sbf:milestone221
VF would be vodafone ( service version) while RT would be retail version.
Sent from my Milestone using Tapatalk

Thanks, gonna try asap, will come crying if it explodes in my face...

SuicideTree said:
Thanks, gonna try asap, will come crying if it explodes in my face...
Click to expand...
Click to collapse
It wont. I have done it many times and my face is still intact, as you can see from my avatar.
Sent from my Milestone using Tapatalk

now add a laptop that sometimes, actually recently starts bsoding not when you're gaming but when you're picking your nose... and now a serious question, how screwed am i if the laptop crashes WHILE doing something with RDS Lite or something similar ;]]

SuicideTree said:
now add a laptop that sometimes, actually recently starts bsoding not when you're gaming but when you're picking your nose... and now a serious question, how screwed am i if the laptop crashes WHILE doing something with RDS Lite or something similar ;]]
Click to expand...
Click to collapse
which version of rsdlite and what OS? rsdlite should not cause your OS to crash.

oh no, it's not rsd lite related, it's just laptop hardware being faulty, that's my assumption anyway, this laptop is going to the warranty next monday, it bsods randomly and i mean really randomly... atm i have win7ult x64 and rsd is 4.9... however this is unrelated, i had a linux here and on it was screwing me over from day one.

SuicideTree said:
oh no, it's not rsd lite related, it's just laptop hardware being faulty, that's my assumption anyway, this laptop is going to the warranty next monday, it bsods randomly and i mean really randomly... atm i have win7ult x64 and rsd is 4.9... however this is unrelated, i had a linux here and on it was screwing me over from day one.
Click to expand...
Click to collapse
Try it and see if it works.

Just finished. Seems to be good. Gonna Continue with the guide then ^^ Many thanks.

instead starting a new topic IDIOT QUESTION but... can someone give me a detailed dumbed down version of this instruction bellow:
If you applied an OTA update before, there is a script run at every system boot that checks and re-flashes the recovery when its checksum doesn't match. In such case, you have to avoid booting to android after the vulnerable recovery flash. Boot directly to recovery when RSD Lite restarts the phone (hold camera button) and from there remove the /system/etc/install-recovery.sh file.
rm -f /system/etc/install-recovery.sh
i am getting this
E:Cant open /cache/recovery/command
just upon entering AOR (power+x)
trying to apply the update regardless i get this
- install from sdcard
finding update package
opening update package
verifying update package
E:EOCD marker occurs after start of EOCD
E:signature verification failed
Instalation aborted
what is the meaning of this?
possible solutions:
"It seems that the key to successful recovery flash in some cases is to not let the phone to boot to android or recovery until the RSD Lite will signal PASS. When the RSD Lite is restarting the phone during flash, hold the D-Pad Up, so the phone enters the bootloader again immediately."
does this work? DIDNT WORK, so i still need help
i'm still combing through many threads mentioning this... either please tell me this works or point me in the right direction -_- thanks

Once you flash the official sbf, you need to flash the vulnerable recovery to enable you to run openrecovery which is used to flash custom roms and much more.
There is a script which checks your recovery image everytime it boots and replaces it with the original if it finds any changes. So you need to remove that script.
Procedure would be as follows.
1. Download and extract androidiani openrecovery to the root if your sdcard. You should have a update.zip file and openrecovery folder.
2. Flash official sbf.
3. Flash vulnerable recovery sbf. When the phone restarts and before it displays Moto logo, press and hold the 'x' key on your keyboard. You should see a triangle with exclamation mark. Press volume up + camera button and choose apply update menu option.
AOR should load up. Choose console option and type the following commands.
rm - rf /system/etc/install-recovery.sh
reboot
That's all.
Sent from my Milestone using Tapatalk

okay, so it seems i did all the steps EXCEPT flashing the original sbf... wait, the first link you provided was to a an official sbf - correct? then where do i get the vulnerability? or vulnerable_recovery_only_RAMDLD90_78.sbf is it? so, i have original flashed, when trying the vulnerability now it says failed, 0x7100, phone connected. what does that mean?

SuicideTree said:
okay, so it seems i did all the steps EXCEPT flashing the original sbf... wait, the first link you provided was to a an official sbf - correct? then where do i get the vulnerability? or vulnerable_recovery_only_RAMDLD90_78.sbf is it? so, i have original flashed, when trying the vulnerability now it says failed, 0x7100, phone connected. what does that mean?
Click to expand...
Click to collapse
The RAMDLD90_78 is the Vulnerable Recovery.
RSD Lite is a buggy program sometimes. What you need to do is put the sbf you want to flash on the ROOT of your C:/ drive and try it again.

I suppose there's no harm in trying that, i already had to rename it to something shorter, cause it wouldnt even give me the Start button.... brb

skadude66 said:
The RAMDLD90_78 is the Vulnerable Recovery.
RSD Lite is a buggy program sometimes. What you need to do is put the sbf you want to flash on the ROOT of your C:/ drive and try it again.
Click to expand...
Click to collapse
Buddy, please help him out with the rsdlite problem. I presume you had the same problem and someone helped you out, especially with the Windows 7 x64 error.
@SuicideTree : What is your ultimate goal? You want to have a Official ROM on your phone or you want to flash custom roms.

sileshn said:
Buddy, please help him out with the rsdlite problem. I presume you had the same problem and someone helped you out, especially with the Windows 7 x64 error.
@SuicideTree : What is your ultimate goal? You want to have a Official ROM on your phone or you want to flash custom roms.
Click to expand...
Click to collapse
You helped me out with that sileshn!
Yeah, I'll keep this thread up and I'll see what issues he's got.

sileshn said:
Buddy, please help him out with the rsdlite problem. I presume you had the same problem and someone helped you out, especially with the Windows 7 x64 error.
@SuicideTree : What is your ultimate goal? You want to have a Official ROM on your phone or you want to flash custom roms.
Click to expand...
Click to collapse
oh well, i was going for cyanogenmod, but for starters i'd like root to have some more control over my phone
EDIT: it also appears that once again it wont give me the START button, cant press it, moved files around, renamed and stuff... weird
EDIT2: by the way, is it normal for the vulnerability file not to show any file properties in RSD Lite?

SuicideTree said:
oh well, i was going for cyanogenmod, but for starters i'd like root to have some more control over my phone
EDIT: it also appears that once again it wont give me the START button, cant press it, moves files around, renamed and stuff... weird
Click to expand...
Click to collapse
Once you get VR, rooting and flashing a custom ROM is a piece of cake, so it shouldn't be that bad once you get there.

SuicideTree said:
oh well, i was going for cyanogenmod, but for starters i'd like root to have some more control over my phone
Click to expand...
Click to collapse
If you want to flash CM, just install GOT 2.2.1 from here and forget about VR. GOT has VR injected into it. Use the Retail UK sbf.
Once you have CM, you have root.
@skadude : Didn't know it was me.

is cm7 much better over cm6? cause i was looking into that ^^ however if the end goal can be achieved easier with got cm6 i should give that a try, but, what if i wanna play around with this stuff later or something? i'd like to understand what's happening at the moment... anyway, if i go with got solution what are the steps? flash uk sbf, then got or... then cm?
also, got or is better than aor? except apparently having vulnerability alreay in it... anything else?
thanks for all the help, sorry for being not too enlightened, i'll get there ;]]]