[HACKS] Root Droid 1 - regardless of OS version

[mightyfighty]

Need help plz.

Rebooted holding up key, D1 is plugged in w/ USB. Windows is searching for a driver SE Flash OMAP3430 MI. Was this supposed to be in RSD Lite? Where can I find it?

See item 3 in "things you're going to need" in the OP.

Thanks, still getting used to the forums. Didn't see that it was a link until now.

 

[richhowe]

Try renaming the sbf file using a shorter name like MC1.sbf and also make sure the sbf file is on the root of your drive (i.e. C:\MC1.sbf) this worked for me.

I managed to read through all 24 pages of this topic tonight and I had to register just to say thanks to the OP. I will doing this on my Droid when I get off work in an hour.

Edit: Unfortunately I can't seem to get past step 9... the 'start' button stays greyed out. I am running it as administrator and the phone does show in the grid below...

Edit again: I should mention I'm on Win7x64 Ultimate... I'm updating drivers to 4.6.5 now and will try again after I've gotten some sleep. Phone battery needs to charge a bit too... only at 25%.

 

[MotoCache1]

Try renaming the sbf file using a shorter name like MC1.sbf and also make sure the sbf file is on the root of your drive (i.e. C:\MC1.sbf) this worked for me.

Edit: Unfortunately I can't seem to get past step 9... the 'start' button stays greyed out. I am running it as administrator and the phone does show in the grid below [...] I should mention I'm on Win7x64 Ultimate

Hi Rich. I've read people mention (in other SBF topics) moving SBF files to the root and/or renaming them to shorter names. I cannot duplicate this issue on my Windows XP machine using RSD Lite 4.6.

I think the max path length in Windows is 260 characters. As named, my file is 56 characters, so that should leave at least 204 characters for the file path portion. So I'd think that if you moved the file to the root you'd never have to rename it. If you were using the original filename you'd be OK unless the path to the folder was more than 204 characters. Even then, on XP anyway, you can't even put the file in the directory if the path is too long.

To test this, I created this folder:

C:\data\droid\ineedaverylongpathsoicanreplicatethe260characterlimitthingthiswilltakequiteabitofdoingsince260charactersisahelluvalotofcharacterstohaveinapathbutiknowthaticandoitgeezdoessomeonereallyhavetheirfolderthislong\

That is 221 bytes including the trailing slash and Windows will not allow me to put a file whose name is 56 bytes in there (because the complete file path would be too long).

If I rename the folder to:

c:\data\droid\ineedaverylongpathsoicanreplicatethe260characterlimitthingthiswilltakequiteabitofdoingsince260charactersisahelluvalotofcharacterstohaveinapathbutiknowthaticandoitgeezdoessomeonereallyhaveth\

Then I can put the file in there.

Maybe the newer version of Windows allows longer paths but RSD Lite can't handle it?

On my machine, even if the full filename is:

c:\data\droid\ineedaverylongpathsoicanreplicatethe260characterlimitthingthiswilltakequiteabitofdoingsince260charactersisahelluvalotofcharacterstohaveinapathbutiknowthaticandoitgeezdoessomeonereallyhaveth\MC1_A855_1282081087_Recovery-Only_SPRecovery_0.99.3b.sbf

RSD Lite 4.6 can choose it and my Start button is available to be pressed.

Could you verify the circumstances that required you to rename or move the file for it to work, and see if they comport with anything above? If so, I'd appreciate it. I'd like to validate my hypothesis so I can include a note in my instructions if warranted.

Thanks!

 

[bazar6]

This, was an awesome post, thank you very much MotoCache1. Now, where do I go next? haha. I'm new to the whole rooting world, have had my phone since November '09 and just now rooting it (did it last night). When booting holding the X key down, I get the "Patched by SirPsychoS (0.99.3b)", so I know I've modified my phone. I have 2.2 FRG22D on it, and this patch is the only mod I've done so far. I want to overclock, add custom kernals and ROMs, and maybe a custom theme. Where do I go first? Even if its just a link to another post, it'd be greatly appreciated. I've been thru the Hacking section looking at custom ROMs (thinking about ChevyNo1 ROM, even tho I'm a Ford guy lol), but how to go about installing, etc, is beyond me. Thanks for any info!

BTW - I did it on Vista, thru Boot Camp, but I'd love to be able to do this completely from my phone or my Mac. Using Vista is a last resort for me. Thanks!

 

[richhowe]

I cannot duplicate this issue on my Windows XP machine using RSD Lite 4.6.

Hi MotoCache1!

I agree with you , this is not an issue with Windows XP. On my Windows XP machine I can run RSDLite with no issues and using long file names. However, on my Windows 7 64-bit PC I cannot. Until I read about moving the file to root and renaming the file, I had to use my XP PC. Once I tried moving and renaming the file I was able to successfully (start button not greyed out) use my Windows 7 64-bit PC. I've seen multiple people report this problem running Windows 7 and this worked for me.

I think the change in security in Windows 7 causes issues. The file name length really baffles me because the path (including the file name) is definitely under Windows limits.

Thanks,
Rich

 

[MotoCache1]

Now, where do I go next? [...] I want to overclock, add custom kernals and ROMs, and maybe a custom theme. Where do I go first? Even if its just a link to another post, it'd be greatly appreciated.

For overclocking, assuming you want to understand what you're doing, I'd start here. For custom kernels, each kernel maker will have their own instructions. That is a trial and error thing where you have to find one that has the features you want and also has speed slots and voltage that your phone will like (every phone is different). I run the one in my sig and along with SetCPU to calm it down if it starts to get too hot (which doesn't happen often) it's great. I don't really do the ROM thing. I "themed" my battery icon as a separate item and might tweak other things here or there if I feel they give me a functional improvement, but I really prefer to keep the main OS as close to stock as possible. That's just me though.

BTW - I did it on Vista, thru Boot Camp, but I'd love to be able to do this completely from my phone or my Mac. Using Vista is a last resort for me. Thanks!

Well, the SBF part pretty much has to be done from a PC if you're not already rooted. If you're already rooted then there are various other ways to update your recovery partition. SBF's can pretty much only be written to the phone using a PC running Windows or Linux. The sbf_flash (Linux) tool is not open source and although the author (mbm) has compiled it for Mac there's a bunch of extra things that have to be installed on the Mac to make it work and it's too much hassle to support. Good news is you generally only have to do it once unless you install an OTA again someday.

 

[MotoCache1]

I agree with you , this is not an issue with Windows XP. On my Windows XP machine I can run RSDLite with no issues and using long file names. However, on my Windows 7 64-bit PC I cannot. Until I read about moving the file to root and renaming the file, I had to use my XP PC. Once I tried moving and renaming the file I was able to successfully (start button not greyed out) use my Windows 7 64-bit PC. I've seen multiple people report this problem running Windows 7 and this worked for me.

I think the change in security in Windows 7 causes issues. The file name length really baffles me because the path (including the file name) is definitely under Windows limits.

Thanks for the followup Rich. I guess I'll fire up Windows 7 in a VM and see if I can reproduce the issue. Assuming I can, then I'll see what the path length limit is before it chokes. What version of RSD Lite are you using on Windows 7? Maybe just a bug in that version if it's not 4.6.

 

[richhowe]

Hi MotoCache1!

Initially, I tried to use RSDLite 4.6 but was unsuccessful. I then installed 4.7 hoping it would fix my issue but it didn't. I then read about moving the file and using a shorter file name and that worked for me after I had already installed RSDLite 4.7.

Thanks,
Rich

 

[bazar6]

Thanks for the quick response MotoCache1! That is tons of help!

 

[SlammedDime]

Edit: Unfortunately I can't seem to get past step 9... the 'start' button stays greyed out. I am running it as administrator and the phone does show in the grid below...

On mine, the only time the Start button is grayed out is when I have not yet chosen the SBF file I want to flash. Be sure you didn't miss Step #8 of the detailed instructions.

Nope, didn't miss any steps... attached is a screenshot...

Edit: I shortened the file name to 'recovery.sbf' and stuck it in c:\ and that did the trick... now have a start button... off we go...

Edit2: Rooting complete....

 

[furbearingmammal]

@SlammedDime

greeknasty had the same issue with the same OS, etc. He posted his experiences earlier in the thread, I believe, and what he did to get it working.

Someone correct me if I'm wrong, please, I'd hate to be passing along false information!

 

[richhowe]

Edit: I shortened the file name to 'recovery.sbf' and stuck it in c:\ and that did the trick... now have a start button... off we go...

Edit2: Rooting complete....

Glad it worked for you! It worked for me but I wasn't sure if it would work for everyone.

 

[bhughesiii]

Excellent work! I flashed back to 2.0.1 then manually updated to 2.1-update1 hoping to get FRG01B, I woke up this morning and ended up with FRG22D! So, obviously I was miffed because I wanted to try Universal Androot. But then I found this guide and my FRG22D was rooted in no time!

so you were at stock 2.1-update1, and woke up this morning with an update that changed you to FRG22D? Was it a single large file?

Ya know what I didn't even check, it was 5:30 AM and my brain wasn't functioning properly, I just clicked install. Honestly I was expecting it to be FRG01B. But, when it rebooted and I checked about phone it said FRG22D.

 

[jntdroid]

Excellent work! I flashed back to 2.0.1 then manually updated to 2.1-update1 hoping to get FRG01B, I woke up this morning and ended up with FRG22D! So, obviously I was miffed because I wanted to try Universal Androot. But then I found this guide and my FRG22D was rooted in no time!

so you were at stock 2.1-update1, and woke up this morning with an update that changed you to FRG22D? Was it a single large file?

Ya know what I didn't even check, it was 5:30 AM and my brain wasn't functioning properly, I just clicked install. Honestly I was expecting it to be FRG01B. But, when it rebooted and I checked about phone it said FRG22D.

But, you know for sure that you were on 2.1-update1 before you woke up at 5:30? These seems somewhat likely as I would think Verizon would want one big file to update to 22D if needed...

 

[fetchman]

This may just confuse the matter but for 2 weeks prior to this thread being posted, I had tried numerous times to install SPRecovery. I have 32 bit Windows 7 and was using RSD 4.6. I was never able to get the Start button active using the downloaded name in the root directory. I read in one of the threads to try putting the download on my desktop and trying it from there. Still no-go until I tried another suggestion which was to put 3 or 4 spaces at the end of the extension and then backspace them out. That enabled the Start button and I was able to flash SPR. Of course, that only worked until I re-booted. The next time trying to flash SPR, I did the same thing and I couldn't get the Start button doing the spaces trick. So I tried changing the name to something else which was shorter (4 characters). That worked once and then the same problem and the same 4 character name would not give me the Start button. So I downloaded RSD 4.7 and tried more things. Nothing seemed to be consistant - sometimes a shortened name would work, sometimes not. Sometimes spaces at the end or anywhere in the middle of the name and then backed out would work - sometimes not.

Then came this wonderful thread and solution to our troubles. I took Moto's suggestion to use a specfic RSDlite 4.6. It was not the same zip that I had originally used (was a 7zip file rather than zip). I uninstalled RSDlite 4.7 and installed this 7zip RSDlite. The very first time I followed the OP instructions, everything worked. No problem what so ever with the file name Moto supplied and I have not had any more problems with any file name using RSDlite.

Don't know for sure what this all means, but it leads me to think that it had something to do with my original installation of RSDlite 4.6 that 4.7 didn't fix and it was only the total removal of RSD and reinstalling a different RSD download that corrected the problem.