Database Develop

[MOD] Fix for hardware locked phones / cant access recovery without adb.

NOTICE 10/18/2010:
I just captured the JI6 OTA update files from one of my phones and found that T-mobile is
updating the SBL with the same file found in this thread, I'm using the same method as T-mobile
to install the new SBL so the chances for a brick are the same but if you are completely
stock just wait for the OTA update and have the phone swapped under warranty in the
event of a brick.
WARNING:
INSTALLING THIS CAN BRICK YOUR PHONE
this is safer than the odin method, but when messing with the phones bootloader
there is always a chance that you could end up with a paper weight (I bricked
one phone messing with this stuff).
Updated 10-15-2010
this is the fix for hardware locked phones in update.zip form
install the phone drivers which can be found at:
http://forum.xda-developers.com/showthread.php?t=728929
put update.zip on the internal sd card (the 12 gb one)
turn on USB debugging in Settings-->Applications-->Development
reboot into recovery, use the RebootRecovery.bat in adb.zip if you dont know
how to do that.
when in recovery use the vol up and down buttons to navigate and power button to
select reinstall packages
install will take about 20-30 seconds and will pause at "writing secondary bootlader" don't panic
the phone will reboot you should be unlocked (or bricked).
update.zip md5=3b32fab99049530d2185014340840a47

I can vouch for this. It worked exactly as described.
Thanks!

Just to make sure after I do this I can flash any rom through odin without problem?

bobby915 said:
Just to make sure after I do this I can flash any rom through odin without problem?
Click to expand...
Click to collapse
I have flashed JFD, JI6, JI6 unofficial, JI6 OTA after flashing this and have had
no problem's
in general these files are written to parts of the phone that are usually never
written again after manufacturing and are responsible for getting the hardware
ready to load the kernel and then loading the kernel and booting the phone and
should not have any issues loading any ROM you care to flash.

Right now I can access download mode intermittently (maybe 1/10 times) by holding vol-up-down + power with usb plugged in. I cannot access recovery mode at all. Will this flash ruin my ability to access download mode? I feel like download mode is more important than recovery in case of a brick, but I would like the ability to go to recovery without adb or rom manager.

I've tried this 5 times, ODIN says failed everytime,EDIT Apparently 3rd times the 3rd time is the charm cause the 9th time it worked, Second Edit, The 9th time it started but its been 10 minutes so I assume it froze, Dammit.

Persanity said:
I've tried this 5 times, ODIN says failed everytime, Apparently 3rd times the 3rd time is the charm cause the 9th time it worked
Click to expand...
Click to collapse
So your recovery works now? Can you also get into download mode?

I'll add my Vibrant to the list of previously hardware locked phones, fixed by this.
I'd like to send out a HUGE thanks. Recovery and Download mode work every single time now. I can start playing around with roms safely.
Thank you so much

STEP BY STEP GUIDE
**UPDATE**10/14/10
STOCK RECOVERY VERSION OF HWLOCK FIX
untermensch has created a UPDATE.ZIP version of the fix
1) Download UPDATE.ZIP from OP or here http://www.megaupload.com/?d=2R2XOZ0X
2) Place UPDATE.ZIP in root of /sdcard not /sd
(If you have a previous UPDATE.ZIP file in root of /sdcard move it to another folder untill you have unlocked)
3) Use ADB to get into recovery
(use step posted below if you dont know how to use ADB)
(use command "adb reboot recovery")
4) Use vol down to navigate to reinstall packages press power to select
ODIN VERSION OF HWLOCK FIX
**NEW**
untermensch test file
(download from OP)
Everything you need minus drivers(or download individually in steps below)
http://www.megaupload.com/?d=66SSG9VR
step 1) go here and get the drivers and install them
http://forum.xda-developers.com/showthread.php?t=728929
step 2) download this zip file
http://forum.xda-developers.com/attachment.php?attachmentid=415810&d=1286579010
(load tar file from this zip in PDA section of odin after step 4)
step 3) go here download and follow guide to setup adb
http://forum.xda-developers.com/showthread.php?t=502010
(use "adb reboot download" to get to download mode)
step 4) go here get odin v 1.3
http://forum.xda-developers.com/showthread.php?t=790026
(run odin load tar in PDA make sure com4 or similar pops up click start)
FOR THOSE WHO NEED ADB HELP
REBOOT TO DOWNLOAD MODE WITH ADB
*must have drivers installed*
1) download androidSDK from here http://developer.android.com/sdk/index.html
2) extract the folder to root of your harddrive and rename it something short like ADB
3) on phone go to settings , applications , development and click USB debugging
then plug your phone into the computer
4) open windows command prompt and type this (hit enter after each line)
cd c:\
cd ADB\ (or whatever you renamed the folder in step 2)
cd tools\
adb reboot download
5) flash tar with odin
Sent from my SGH-T959 using XDA App

No, It did not work, The 9th time it actually started instead of saying failed immediately, But after 20 minutes nothing had changed and then odin cr5ashed and now my phone is soft-bricked/bricked whatever it is. All I know is im ****ing pissed. Can somebody point me in the direction of a complete restore thread? EDIT: Yeah I finally got it, Thank god I have never had a problem getting into download mode, When I say got it I mean restoring my phone to work not getting recovery to work, If I flash J14 first then J16 am I gonna lose the ability to go into recovery mode if the J14 update does actualy let my phone go into recovery?

untermensch said:
The leaked JI4 firmware contained the files needed to get the our phones unlocked
attached is an odin flashable tar with sbl.bin, boot.bin when flashed your phone wont ignore
the vol up + vol down + power buttons and you will be able to access recovery.
if you haven't used odin before follow AgentFour20's instructions http://forum.xda-developers.com/showpost.php?p=8541107&postcount=35
note:
1. the port wont be com4 for everyone as long as odin shows a com port you should be fine.
2. you might not need adb this method worked on my locked phone http://www.youtube.com/watch?v=rqxearzXrVY
you can flash this over any ROM or firmware and will probably never have to flash it again because boot.bin, sbl.bin are rarely included in firmware.
as usual use caution when flashing your phone, I am not sure if you can get back into download mode if this flash fails, So flash at your own risk!
for more info check out the I9000 thread:
http://forum.xda-developers.com/showthread.php?t=785201
and the original thread:
http://forum.xda-developers.com/showthread.php?t=802763&page=3
Good Luck!
md5 for tar file = d18f9d23d3060260a4e7edc1b6321941
Click to expand...
Click to collapse
Gonna put in my vote for one recommendation for you people who have a dickens of a time getting into download mode and are afraid of Odin3 leaving you stranded.
Try using Odin3 v1.30 instead of Odin3 v1.00 (it's linked in the Bible thread). My failure rate on flashing with v1.30 so far is zero. My failure rate when I was flashing with v1.00 was more to the tune of 50% of the time. I'm not hardware locked, so this is less scary for me than it is for you.
Just a safety tip...Best of luck!

sounds like solution is simple, but why did this occur on some vibrants in the first place?

SamsungVibrant said:
sounds like solution is simple, but why did this occur on some vibrants in the first place?
Click to expand...
Click to collapse
My guess would be that there are different internal JFD firmware images floating around wherever Samsung manufactures these, and one had the bugtastic sbl. We've already seen in the case of JI6 (where there were actually two versions of this firmware, with the leaked version from Kies having a nearly week older build date) that Samsung isn't necessarily consistent with their versioning.
Just a guess though..

Awesome....used odin 1.3 and this took a few seconds and worked flawlessly
if you follow the instructions in the posts above, don't see how you can go wrong
I can now access download mode and recovery...and I can sleep a lot easier knowing that if something happens I can fix it now

Yes! Masterotaku thank you so much for posting about odin3 v1.3, 1st time it work for J14 over J16, I can now boot into download and recovery mode. Sweet.

masterotaku said:
My guess would be that there are different internal JFD firmware images floating around wherever Samsung manufactures these, and one had the bugtastic sbl. We've already seen in the case of JI6 (where there were actually two versions of this firmware, with the leaked version from Kies having a nearly week older build date) that Samsung isn't necessarily consistent with their versioning.
Just a guess though..
Click to expand...
Click to collapse
hmmm interesting, seems like samsung isn't consistent with their screen tints also. They need to get quality control under quality control

Wanted to add that this worked for me as well. Thanks for the info.

Worked on first try, Odin 1.3. Thank you so much for this fix! I knew holding out on replacing my vibrant would pay off =)
Now I got into recovery by both vol + power then release power, but how do you guys get into download mode? I used to be able to get there occasionally by doing that same key combo, but with usb attached.
EDIT: Wow that was easy.
RECOVERY MODE: Hold both volume buttons and power, once vibrant logo shows up, release power.
DOWNLOAD MODE: Hold both volume buttons (no power) and plug in USB. Instant!
EDIT: Honestly I can't thank you enough. This is so amazing!

Thanks so much, this really works, my 1st time ever using odin 1.3
and finally figure out what adb is. Before even pulling the battery would
not get me into download,and the only way to get into recovery was using
clockworkmod. This really works!!! thanks you thanks you.

Everything is not as good as it seems. I managed to flash the fix all right and now I have download mode. But my friend had done the same steps as myself but odin FAILED to flash the fix. It just said:
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/006> Removed!!
And his phone is totally bricked now.
It is really dangerous to use ODIN on hardware locked phones... Too high chance of failure to flash. ((

Odin successful, but still stuck in boot loop

TL;DR - Stuck in boot loop, can't enter recovery mode, but can enter download mode. Odin says it is successful, but the phone is still in the boot loop.
I've had Cognition 2.3 for a few months now and decided to update to Cognition 4.3. I used the AIO toolbox 2.5 to Odin one-click back to stock, rooted, and flashed to 4.3. Everything went well and I restored all my apps with Titanium and loaded some music.
At some point later the screen was completely blank and the only way I could get any response out of it was to hold the volume buttons and power buttons. Instead of going into recovery, though, it would boot to the Cognition boot screen and hang indefinitely.
I was able to get it into download mode by removing the sim and battery and holding the volume buttons while plugging it into USB and replacing the battery. I ran Odin one-click again, it said it was successful, but the phone was stuck in either a battery screen or AT&T screen boot loop (depending on whether or not it was plugged into USB).
I've tried using regular Odin with both the ROM included with AIO 2.5 (JF6*) and JH2 (from http://forum.xda-developers.com/showpost.php?p=10056254&postcount=36) to no avail. Every time Odin shows that it is successful, but it always ends up in a boot loop with no ability to enter recovery mode.
What can I do? Will getting a jig help me in any way?
*Edited for correct ROM

Use the normal ODIN (v1.7 or v1.8), a full stock JF6 ROM and PIT file. Make sure "repartition" is selected and if possible, do a master clear with ODIN first (though shouldn't be critical.........then start over with Cog 4.3 if that's your ROM of choice (good choice by the way).

I tried the JF6 ROM again with the same results (using http://forum.xda-developers.com/showthread.php?t=818439#8802897). It looks like AIO 2.5 used this ROM all along.
I can't master clear because I can't boot past the AT&T screen. The only way for me to get Odin (or Windows for that matter) to recognize the phone is by putting it in download mode. From what I understand you don't master clear from download mode.

bharden said:
I tried the JF6 ROM again with the same results (using http://forum.xda-developers.com/showthread.php?t=818439#8802897). It looks like AIO 2.5 used this ROM all along.
I can't master clear because I can't boot past the AT&T screen. The only way for me to get Odin (or Windows for that matter) to recognize the phone is by putting it in download mode. From what I understand you don't master clear from download mode.
Click to expand...
Click to collapse
Are you using the PIT file and selecting repartition?
When I get home today, I will upload the ROM and PIT that I use to flash to stock and see if that helps but you do need to use the PIT and repartion which will only help if you have a FULL copy of JF6 that reloads the bootloaders.

Just out of curiosity, what is your build number?

I am using the PIT and selecting repartition. I've done this every time I've tried Odin (besides when using one-click of course) Is the PDA.tar listed in that link not a full copy of JF6?
My build number is 1008.

May sound crazy, but you could try using a different computer. I ran into a lot of problems using odin on my pc. Switched to laptop (more ram and windows 7 64 bit ) with great success. Also make sure you have the right drivers. Your build# should allow you to use odin one click.
Sent from my GT-I9000 using XDA App

I've actually already tried it from both my PC (Windows 7 x64, 4 GB ram) and my laptop (Windows Vista x86, 2 GB ram). In both cases I used the drivers in the AIO toolbox 2.5 (http://forum.xda-developers.com/showthread.php?t=944418)
Are those the correct ones? If not, could you point me to a resource with the latest drivers? There are quite a few versions floating around and I'm not sure which ones I should be using.
Any other suggestions?

Those should be the correct drivers
Also, make sure odin is completely open before connecting your phone.
That'd all I can think of.
Sent from my GT-I9000 using XDA App

I definitely did that.
Since I'm able to get into download mode, I should be able to un-brick it right? I can't figure out why Odin says it's successful but I still can't boot.
Does anyone else have any ideas?

You may have to give it a few minutes or so as I am uploading now but the link for the PDA and PIT is:
http://dl.dropbox.com/u/24576569/ATT%20ROM%202.1.rar
Try using this version of ODIN:
http://dl.dropbox.com/u/24576569/Odin3%20v1.7.rar
Hope this helps otherwise I am out of ideas except flashing a kernel with a recovery included through ODIN, going into the recovery and formatting and wiping absolutely everything and then reflashing JF6. But try the files I linked first.
Good luck.

It's been 30 minutes and the ROM link still isn't up. Is it working?
Also, I'd like to change what I said slightly. When using regular Odin 1.81 it says PASS when it's finished. When using Odin one-click it gets to the point of cache.rfs and then says removed. The box turns blue and says Reset. Meanwhile, the phone is busy rebooting indefinitely on the battery screen.
I'll try your ROM and Odin version as soon as the link works. Also, do you have a ROM with built in recovery that you would suggest? Thanks!

bharden said:
It's been 30 minutes and the ROM link still isn't up. Is it working?
Also, I'd like to change what I said slightly. When using regular Odin 1.81 it says PASS when it's finished. When using Odin one-click it gets to the point of cache.rfs and then says removed. The box turns blue and says Reset. Meanwhile, the phone is busy rebooting indefinitely on the battery screen.
I'll try your ROM and Odin version as soon as the link works. Also, do you have a ROM with built in recovery that you would suggest? Thanks!
Click to expand...
Click to collapse
Drop box seems to be running slow. So the JF6 that I am uploading may take a bit. The version of ODIN that You are running should be fine.
Try this Kernel. It's not a complete ROM just the kernel. If it works, you will have to flash a ROM too. Cognition is a good start. You can find it in the Dev section and actually, even if it's not the recommended way of flashing, I moght try flashing a custom ROM anyway just to rule out ODIN and your phone. If you can successfully flash a custom ROM then it's probably the version of JF6 that you are using.
Anyway, let's start with the kernel first:
Onix by existz:http://forum.xda-developers.com/showthread.php?t=930679
make sure you download 2.0.3 "tar" file for ODIN
you know how to get into recovery after you flash right? From powered off, hold the up and down volume buttons and then power all at the same time for about 5 second......

Ok, so there seems to be some progress. I flashed the kernel and the phone rebooted to what I'm assuming is the Onix splash screen and hangs. The power button won't turn the phone off, but at least the softkeys do seem to respond, even if they don't do anything.
Odin now recognizes the phone in both download mode and at the splash screen. Although, to reach download mode I now have to take the battery out, whereas I did not have to before.
I'm still unable to enter recovery. The only way to get any response out of the phone at the splash screen is to hold both volumes and the power button, but the phone just reboots back to the splash. It also does this when attempting to enter recovery from a power off state.

bharden said:
Ok, so there seems to be some progress. I flashed the kernel and the phone rebooted to what I'm assuming is the Onix splash screen and hangs. The power button won't turn the phone off, but at least the softkeys do seem to respond, even if they don't do anything.
Odin now recognizes the phone in both download mode and at the splash screen. Although, to reach download mode I now have to take the battery out, whereas I did not have to before.
I'm still unable to enter recovery. The only way to get any response out of the phone at the splash screen is to hold both volumes and the power button, but the phone just reboots back to the splash. It also does this when attempting to enter recovery from a power off state.
Click to expand...
Click to collapse
The three button combo should work to reset the phone when it's stuck as well as getting into recovery. It sounds like you aren't holding the buttons for long enough. If the phone is frozen, you have to hold the button combo for quite a while to get the phone to reset. Weh trying to get into recovery, push both volume buttons and then hold down the power button and don't let go till yoiu get past the AT&T screen.
If that still doesn't work, then try and load up the ROM and see if at least you can get a working phone back in the meantime. Like I said, I recommend Cog 4.3 but serendipity is a good choice too.

Awesome. I must have been holding the buttons for half a second too little. Now I can get into the Onix Recovery, but I'm getting:
"E:Can't mount /dev/block/mmcblk0p1 (or /dev/block/mmcblk0) (No such file or directory)"
when trying to mount the SD card.
Searching around I've found these two threads:
http://forum.xda-developers.com/showthread.php?t=563298
http://forum.xda-developers.com/showthread.php?t=792708
but I'm not exactly sure what to do with the information. I don't particularly want to go guessing at what to do next and ruin my progress. Could you give me a little guidance on what steps to take next?
From "adb shell mount /sdcard" I'm getting:
mount: can't find /sdcard in /etc/fstab

bharden said:
Awesome. I must have been holding the buttons for half a second too little. Now I can get into the Onix Recovery, but I'm getting:
"E:Can't mount /dev/block/mmcblk0p1 (or /dev/block/mmcblk0) (No such file or directory)"
when trying to mount the SD card.
Searching around I've found these two threads:
http://forum.xda-developers.com/showthread.php?t=563298
http://forum.xda-developers.com/showthread.php?t=792708
but I'm not exactly sure what to do with the information. I don't particularly want to go guessing at what to do next and ruin my progress. Could you give me a little guidance on what steps to take next?
From "adb shell mount /sdcard" I'm getting:
mount: can't find /sdcard in /etc/fstab
Click to expand...
Click to collapse
OK, so I've never had to mount SD from those options so not too familiar with this problem but, i am going to guess that we shouldn't have to play with this right now. Onix will let you install a zip from your external SD, so i recomend finding a recovery flashable ROM (almost all custom ROMs come this way....it'll be a ZIP file) Again I recomend using Cog 4.3 or serendipity (both of these may change your kernel but it's ok because they will both have a custom recovery).
Follow these steps:
1. Remove your external SD and insert it into your computer.
2. Remove any files you want to keep and place them somewhere on your computer for future recovery (Titanium backups, music, pics, etc....)
3. Format your sd (FAT32 should be default)
4. Download the ROM of your choice, copy it to the root of your external SD using your computer
5. Replace the SD into your phone power up into recovery
6. From the Onix recovery menu select "advanced options"
7. Pick wipe dalvik/cache and confirm
8. Select go back untill you get to the first recovery menu
9. Select install zip from SD and NOT "install update.zip"
10. Navigate to your external SD (it should look something like "/extsd" in the file menu
11. Pick the zip you put on the external SD and confirm
12. Wait till the recovery indicates instalation done
13. Navigate back to the first recovery menu and select reboot phone
14. Sit back and relax, your phone will likely take 3-5 min to boot up the first time
If after 10 min of waiting you get no response from your phone, use the 3 button reset to get into the custom recovery and select advanced features again, format absolutely everything you can format (you'll have to do it one at a time) and do that. Then repeat the steps above.
Installing a custom ROM isn't normally this complicated but I am trying to eliminate as many variables as possible here that might cause complications with instalation.
Let me know how it turns out.

FYI: Continuum v4 has the Onix kernel in it (recovery is a blue color)

ROM Files
This is the link to the good JF6 stock ROM. You will have to download it and the ODIN version. All you need is the PDA.tar and the PIT that comes with the ODIN package in the thread. You can still use ODIN 1.8 once you get the PIT file out of the ODIN ZIP.
So, after all is said and done. When you feel like trying this:
1. Open ODIN
2. Phone into download mode (with phone off hold down both volume buttons and plug in USB)
3. Make sure phone is recognised by ODIN
4. Select PIT file that you downloaded
5. Select PDA file that you downloaded
6. Make sure "repartition" IS selected
7. Hit start and sit back and relax
http://forum.xda-developers.com/showthread.php?t=818439
Again, let me know how it all works out.......

Ok, I'll try flashing Cog 4.3 after I get off this afternoon. I'll have to buy an external SD, but that's better than buying a new phone.
I skimmed those threads on the internal SD problem and it looks like there's either some corruption on the SD or it's not formatted correctly or something. How can I fix this problem? Doesn't the ROM need that internal SD card space? Or can it use the external SD card as a replacement? If it does need the internal SD card then won't the ROM fail to install if that SD is corrupted?
Thanks for all your help by the way. When Odin wasn't fixing the problem I was afraid it was completely bricked.

[Q] Broken Recovery Menu on Rooted Milestone

Hey everyone,
So this is definitely a noob problem and I would like to apologize in advance for taking up your time. I am extremely new to rooting and would be extremely appreciative of some advice!
I bought my phone (a Motorola Milestone) already rooted and running G.O.T. 2.2.1 back in November. I wanted to upgrade to the latest CyanogenMod 7 and, in my own stupidity, I followed a Droid tutorial instead of a Milestone tutorial. This led me to install Clockwork ROM Manager and flash their Recovery Menu - which, I've now learned, is not compatible with the Milestone.
So, I now have no access to the Recovery Menu (the phone simply boots up normally). I still have Superuser Permissions and can access the Bootloader.
What I would like your input on is the steps I should take to regain access to the Recovery Menu. I feel like, since I have root access, I shouldn't need to start from scratch (e.g. completely re-root the device), but I don't know for sure.
Is it possible to somehow just flash OpenRecovery? Or do I need to do all ofthe steps listed at addictivetips.c0m/mobile/how-to-root-motorola-milestone/?
I saw one tutorial for flashing a new recovery program (theunlockr.c0m/2009/10/15/how-to-flash-a-new-recovery-image-if-you-are-already-rooted/) and it seems easy enough. My only issue then is that OpenRecovery is not distributed as an .img file but rather as an "update.zip" and a folder.
Again, I'm sorry for using up your time with what probably is a ridiculously simplistic question. I require the phone for my work and the thought of accidentally bricking it is enough to give me pause from doing anything else. Suggestions would be really welcome!

You can flash GOT again which already has the Vulnerable Recovery in it... or just flash the vulnerable recovery itself.
Good luck.
Sent from my Milestone using XDA Premium App

The main issue there is that I never did the initial flash of GOT or vulnerable recovery (I bought the phone pre-rooted) so I don't know how exactly to go about that. In light of the end goal (I want to upgrade the phone to the latest CyanogenMod 7), what would be the least amount of steps to accomplish this?
I think if I could flash the recovery and then flash CM7 (with a backup of all my stuff somewhere in between) that would do the trick?

Can't you try that sbf flash thing? Or is that only for droids?
Sent from my Droid using XDA App

twitchcity said:
The main issue there is that I never did the initial flash of GOT or vulnerable recovery (I bought the phone pre-rooted) so I don't know how exactly to go about that. In light of the end goal (I want to upgrade the phone to the latest CyanogenMod 7), what would be the least amount of steps to accomplish this?
I think if I could flash the recovery and then flash CM7 (with a backup of all my stuff somewhere in between) that would do the trick?
Click to expand...
Click to collapse
Try this:
1) Download RSD Lite - http://uploaded.to/file/pifx1b
2) Download Vulnerable recovery for MM - http://www.mediafire.com/?jzzjmmrvwkz
3) Unpack and install RSD Lite, then unpack vulnerable recovery.
4) Open RSD Lite and click on '...' button, chose sbf file with vulnerable recovery (unpacked in 3rd step).
5) Power on your Milestone in bootloader mode (power + d-pad up).
6) Connect usb cable to Milestone, RSD lite will show that phone is connected
7) Press start in RSD lite and wait until RSD lite end procedures (it will boot when process will be done). Shutdown phone.
8) Turn on Milestone by pressing power + x on the keyboard. It should get you to recovery mode.

Thank you for the detailed steps and the links! I REALLY appreciate them!
Once I've done those, I should then be able to do a backup through the recovery menu and flash the latest CM7 release? Or are there other steps I need to do?

twitchcity said:
Thank you for the detailed steps and the links! I REALLY appreciate them!
Once I've done those, I should then be able to do a backup through the recovery menu and flash the latest CM7 release? Or are there other steps I need to do?
Click to expand...
Click to collapse
When you will be done, download (from here - http://code.google.com/p/androidiani-openrecovery/downloads/list) and copy to sd card Androidiani Open Recovery (update.zip and OpenRecovery folder should be in / of sdcard, eg.: /sdcard/update.zip ; /sdcard/OpenRecovery).
Then (if you want to flash CM7) you need to download CM from here - https://github.com/downloads/nadlabak/android/update-cm-7.1.0-RC10-11.06.14-Milestone-signed.zip and GApps (http://goo-inside.me/gapps/gapps-gb-20110613-signed.zip) and copy it to /sdcard/OpenRecovery/updates
When you copy AOR and CM7 to your sd card, you need to shutdown your phone and power it on with pressed power + x. It will take you to the recovery (screen with exlamation in background) and then you will need to press vol up + camera button. If you see blue menu, choose from option 'apply update.zip'. It takes you to AOR. From AOR menu choose Apply Update, in next step choose package with CM7 (update-cm-7.1.0-RC10-11.06.14-Milestone-signed.zip) and when update will be over do the same with gapps. Return to the main menu and do 'Wipe dalvik cache' and 'Wipe cache'. Reboot and CM7 should load now.

Awesome! This all makes sense. I will have time later this week to give it a try (I can't wait to update this phone, it has now decided that if I receive a couple calls and also a couple texts, it will freeze completely on me. Not impressed!) - thanks again!
Another simple question: When I copy over CM7 and the Google Apps, do I leave them in .zip format or should I unpack them first?

twitchcity said:
Another simple question: When I copy over CM7 and the Google Apps, do I leave them in .zip format or should I unpack them first?
Click to expand...
Click to collapse
Both - CM7 and Google Apps should be packed and moved to OpenRecovery/updates folder.

Thank you for your awesome instructions!
I ran into a few hiccups (at first, I didn't have the USB drivers installed and then I ran into an issue where the com.android.phone process kept quitting so I did a complete data wipe on top of the cache wipes) but I now have CM7 installed and running.
However, I've run into a new problem: I have no network access! (cellular voice or data!). The only carrier the phone sees is WIND (I am on Fido). It previously had no trouble at all... I think it is because of the Baseband version?
I noticed that, with the flashing and everything, the baseband version has changed from 3GSMEPU91A_U_91.09.00I (which worked) to 3GSMEPU91A_U_91.09.04I (not a big change but maybe the cause of my problem?)
I know that the phone is not meant to be used on Fido but it was previously unlocked and working fine... Did I miss a step somewhere?
As of right now, my phone is useless to me so help would greatly be appreciated!
EDIT1: I did configure the Mobile Networks/Access Point Names settings (as per what I used before the format) so that is not the problem...
EDIT2: Under status, the phone does list my correct phone number but has the network as "unknown".

Have you changed the baseband to Canada in AOR? It's either that or Telus when flashing in AOR.
What exactly did you do with the APN? You shouldn't have any issues configuring it to Fido.
Sent from my Milestone using XDA Premium App

I hadn't changed the baseband in AOR - I thought I might have to but I didn't want to do anything that could be detrimental.
I just applied the "canada.zip" and, indeed, it looks like that did the trick!
As for the APN, I just put in the ones found here: http://forum.xda-developers.com/showthread.php?t=537829 as that is what I had to do to get the data working before.
edit: I've been playing around with the phone and everything seems to be working! (even the AMAZING "Create a 3G Wireless Hotspot" feature!) Honestly, I cannot thank you enough adamz667 and skadude66!

Some Direction on entering Recovery and Flashing Please?

So I have sucessfully rooted the wife's original Verizon Moto Droid and I have installed CWM via ROM Manager. I have performed a backup of her current ROM.
From the looks of things here, I will just load the ROM I want to flash onto her sd card and then flash it via ROM Manager. Is this correct? If it fails half way through the flash, can I still enter CWM via a key sequence to re-flash/restore the phone to its original state using the backup on the card from ROM Manager?
Someone mentioned to me using the project elite ROM due to its stability. I can't find a link to that. Can someone point me in the right direction?
I gave her this phone when I bought my Samsung Droid Charge when it came out back last March. I can flash ROMs & Kernels on that phone all day long but the Moto Droid is an entirely different animal. I want to be sure of my fail-safes before I flash anything here.
Thanx In Advance for Your Help

Okay ... cwm just didn't take the first time I flashed it. I am now able to enter CWM from a powered off state.
[Q] If I flash a rom and it doesn't take half way through the flash, will I still be able to enter cwm and install the backup of her current rom? That ROM is not in a zip format on the sd card. It is a tar file and the other components in a folder.
I want to be sure I can recover the phone if I experience a bad flash before I attempt anything. Remember, this is my WIFE'S phone !!! LOL
Any help appreciated.
Edit: Also, I installed RSD lite on my computer but when I open it and hook the phone up, it doesn't see the phone. At least, from what I can tell it doesn't. I click 'show' device and nothing happens. Is this a flashing tool or do I put the ROM on sd card and flash via rom manager? And the fail-safe !! Gotta have the fail-safe !!!

1.) Make sure you have flashed CWM!
2.) If you have CWM flashed, and you made a nanodroid backup before you started flashing a rom, then yes, if it doesn't "take" halfway through the flash, you can pull the battery, hold the power button + X and then restore to your backup.
3.) The ROM needs to be a Zip file... it won't work if it's a .tar file (at least I don't think...never tried... lol)
4.) Yes you can recover your phone anytime as long as you can get into CWM and have a nanodroid backup. If you are bricked, this is where RSD lite comes in.
5.) RSD Lite is very picky, and there are many things that can go wrong. Make sure you have all the official motorola drivers installed onto your computer (Link:http://www.motorola.com/Support/US-...tware_and_Drivers/USB-and-PC-Charging-Drivers). Make sure you are running as administrator... Make sure that you are following the correct procedure (plug in phone when attached to computer via USB, let drivers install, power down phone, power on phone + UP direction). There are various threads on google on how to perform this if you're having problems.

anton2009 said:
1.) Make sure you have flashed CWM!
2.) If you have CWM flashed, and you made a nanodroid backup before you started flashing a rom, then yes, if it doesn't "take" halfway through the flash, you can pull the battery, hold the power button + X and then restore to your backup.
3.) The ROM needs to be a Zip file... it won't work if it's a .tar file (at least I don't think...never tried... lol)
4.) Yes you can recover your phone anytime as long as you can get into CWM and have a nanodroid backup. If you are bricked, this is where RSD lite comes in.
5.) RSD Lite is very picky, and there are many things that can go wrong. Make sure you have all the official motorola drivers installed onto your computer (Link:http://www.motorola.com/Support/US-...tware_and_Drivers/USB-and-PC-Charging-Drivers). Make sure you are running as administrator... Make sure that you are following the correct procedure (plug in phone when attached to computer via USB, let drivers install, power down phone, power on phone + UP direction). There are various threads on google on how to perform this if you're having problems.
Click to expand...
Click to collapse
And there's the rub... The backup from rom manager is not a zip file, so it has to be restored via rom mgr. That does me no good if I only have recovery !! How do I perform a nandroid backup? So I end up with a zip file?

Hmmm that's odd, no edit button .... maybe it goes away after x amt of time. At any rate, nevermind the above question about zandroid ... I found it ... that calls for a great big duh !!!
I do greatly apreciate you addressing my above questions. I feel I've got the direction now that I should be able to wing it from here.
Thanx Again and All The Best to You and Yours for the coming year.
Steve

[Solved] Stuck in Download Mode?

Hello, been a while since I unlocked and installed custom ROMs. Recently I bought a cheap Note 9 and since it is already out of warranty, might as well get a custom ROM to get rid of Bixby.
I used Odin to flash TWRP as per the instructions and now my phone refuses to get out of it. It reboots in to Download mode no matter what button combination I use. Vol down + Power key gets me back in to download mode, if i press all the buttons, same thing. No matter what combo of buttons I use, it just keeps rebooting in to Download mode.
I cannot even turn the phone off... lolwut
The first time it booted in to TWRP, i flashed my ROM and I wanted to reboot to start it but it just keeps coming back to Download mode.
Any ideas?
===========
Ok i somehow fixed it.
When I tried to flash the stock firmware, it gave me Device 4 Binary 3. Googled it and apparently I flashed a BL that's a higher version.
So I fixed it with this genius post from the S6 Edge+ forums by Samuwelle.
---
RE: sw rev check fail device 4 binary 3 error
For all of you who get a similar error while downgrading:
1. download your firmware
2. download 7-Zip
3. download Odin
4. download tar tool
5. READ the guide to the tar tool
6. create the tar.md5 for boot.img, system.img and modem.bin ONE at a time and always cut the created files into a second folder. (I dont know if you need the .back files but just to be shure put them in, too
7. put your phone into download mode
8. start Odin (make shure phone is connected)
9. navigate to the boot.tar.md5 for "BL", the system.tar.md5 for "AP" and modem.tar.md5 for "CP"
10. press "Start" => DONE
This works for me and might not work for you.
I do not take responsibility for any damage YOU did to your phone.
Feel free to ask questions.
Hope this saves someone's day.
Sam
---
I downloaded the stock beta android 10 ROM, did the above, flashed it with Odin, did it 4 times because the progress bar did not move at all. Finally, the last attempt I just let it run while I played some games, after about 20mins, it still hasn't moved, gave up, pulled out the cable and immediately got an "Error updating, please use Smart Switch Emergency Recovery". SS did not work, did not detect.
Tried the above method again, no dice. I could not get out of the error mode now, so I just opened Reiboot Android and clicked the little button to exit download mode, and for some reason it started booting! LOLOL
I guess it flashed successfully, just that the progress bar for Odin didn't move. Either way, I ain't touching **** now. On Android 10, One UI 2.0, gonna use this til the official thing comes out.