Database Develop

[Q] weird problem with my milestone trying to root, booted like crazy

Greetings everyone!
I'm trying to root my Motorola Milestone, the current OS aparently is 2.1 and the carrier is movilnet from venezuela, and I tried to root it so I could have Wifi tethering.
I practically got stucked trying to root it, and in one of the firts steps (loading the ADBrecovery on to the SD card). when I loaded the files to the phone, I tried to load the exclamation point pressing holding camera and on button, it didn't open the exclamation point, so I tried it like 5 times trying to load it. since i couldn't, read some more, and saw that I had to press X and On button, and it worked. when I tried to load the file, it told me that it failed.. since it failed, I pressed the boot the phone and it turned off. then I turned on the phone and it repeatedly started to turn off.
I've got so confused and since the only thing that I changed was adding the files, I deleted them as fast as I could. and well, the phone is stable now. but I'm somewhat scared of damaging my phone.
can someone tell me how to root my phone or tell my why did it go crazy? what could i have done wrong? could a virus in my laptop affect my cellphone? (I somewhat doubt this since the phone works on linux, but, then what could have caused the crazy booting?)
thanks in advanced people

sorry for the shameless bump, but I'd love to get some help so i could finally tether the wifi.

Hi.
To put phone into recovery mode:
Turn phone off.
Press and hold X while pressing power button.
Release power button keeping pressed X.
Use pad to select update.zip.
To put phone into BootLoader mode:
Turn phone off.
Press UP on pad and hold until pressing power button.
Release power button and keep holding UP on pad until You see "Bootloader blah,blah" on screen.
That's about modes.
For problem You have, first of all, You must to find sbf file for Your bootloader version (try google for vulnerable_recovery_only_RAMDLD90_78.sbf ) and flash with rsd lite on windows or proper program for linux. Next, after flash sbf file, find update.zip (google for milestone_root.zip), save to pc and put phone into SD card mode when connecting to usb.
Copy update.zip from PC to / (root) of Your memory card, turn phone off and apply first thing I wrote above for recovery mode, then apply update.zip.
Note that for rooting, depend of Your bootloader version, You must to apply correct version of file. So if You have for example bl 90.78, You must to apply 90.78 sbf and so on.
If You still have problems with rooting, please post back.
PS, don't forget to CHECK BL VERSION!
Cheers
EDIT: DOH... phone is not going crazy. You was probably use wrong files.

Thanks a lot dude, I'll try this as soon as i can, I've been really busy with work lately

No problem.
Cheers
Sent from my Milestone using XDA App

By the way, any reason for not using the Universal Androot tool ?

What is universal androot tool?

See: forum.xda-developers.com/showthread.php?t=747598
Supported Devices:
.....
Dell Streak (2.1)
Motorola Milestone (2.1)
Motorola XT701
.....

[Q] Botched Gingerbread install

So, I went to install gingerbread on my captivate, ripped from the nexus s, but I accidentally flashed the wrong thing. now my phone turns on to the att logo, then it goes away, then about 20 seconds later it comes back. I have been looking for hours on how to get to download mode, and I think that somehow I crippled my chances of using the 3 button combo. I know how to use abd to get to download mode, and my computer shows that my phone is connected when I plug it in at the att logo, but, my PC thinks its a nexus s and it can't find drivers for it. I updated my SDK but it still wont find drivers. is there anyway to install nexus s drivers or to get my phone into download mode without a jig?

Just take the battery out and plug in usb cable while holding volume up and down. (I had the same problem until someone suggested this)

that didn't do anything. if it matters, my phone wont even get to the battery charging screen with the usb cable plugged in, the spinning circle thing comes up for about 2 seconds, goes away, then comes back but its frozen the whole time, nothing else happens. My PC still sees that its plugged in, but, like I said, it thinks its a nexus s, and wont install drivers :/
PS: as to exactly what happened, I forgot to do the voodoo lagfix before trying to install the gingerbread dump from the nexus s, so I got into download mode and went back to 2.1. it was right after that when I realized that my three button combo wasnt working, so I was going to fix that by updating the bootloader, but accidentally loaded nsongs.tar instead of the tar that would fix my download mode combo, so in Odin, I had phone bootloader update checked when I flashed that

tortugasthebest said:
Just take the battery out and plug in usb cable while holding volume up and down. (I had the same problem until someone suggested this)
Click to expand...
Click to collapse
i had a successful install.....but my problem came when trying to revert to stock.
PC wouldn't recognize device and for the first time ever i couldn't get into download mode using method above or a 3 button method that worked for me (a slight variation to method stated above).
Finally the following worked:
1. open odin 1-click JF6
2. remove battery (and any external sd) from phone
3. plug phone into pc via USB (without battery in phone)
4. Hold Vol + / - toggle down simultaneously.
5. While holding the buttons down insert the battery. When i did this my phone entered DL mode almost immediately and i was able to use odin to get back to stock.
build 1007

I'd try the above method to get into DL mode.. if that doesn't work you can try the JIG and see if that works.
But a requirement before flashing was to verify that your buttons worked on your phone.

the buttons were working, but I didn't have a lagfix installed. I flashed back to stock and noticed that my buttons weren't working after that. I went to fix them but flashed nsongs.tar by accident, and I had the "phone bootloader update" box checked, so I'm thinking thats why my buttons aren't working now. I've tried that method above a couple times and nothings happened...

Hmm.. you can try and update using the Nexus S USB drivers.. if they are different from ours that is .. go to that forum and poke around to look for them.
At this point.. can't hurt trying anything.

Where would I find the nexus s drivers? I installed the samsung mobile phone drivers, but my computer still says "found new hardware - nexus s" anytime I plug in, and it shows up in device manager with a big yellow question mark.

avgjoegeek said:
I'd try the above method to get into DL mode.. if that doesn't work you can try the JIG and see if that works.
But a requirement before flashing was to verify that your buttons worked on your phone.
Click to expand...
Click to collapse
same as the poster
when i did my install my buttons were working as well....i have the 1007 build and never had any problem getting to recovery or dl using 2-button and 3-button combo's.
After the gingerbread flash was a different story though. Luckily for me the method i posted almost like jumpstarted me into DL mode....when i did that it went into DL faster than it ever had with the normal methods....the DL screen popped up almost the instant the battery connectors hit.

yea, none of the methods I've found have gotten me into download mode. Is there anyway to get the nexus s drivers so I can do this through adb? I don't have a car so getting to radioshack to buy resistors is kinda hard :/

ok, so I updated my sdk again and it now I have the drivers installed, I can use adb now, but whenever I do, adb reboot download, it reboots, but not to download mode, i goes right back to the boot loop. I was wondering if there was anyway to push a new bootloader onto my cappy using adb. that would be awesome

[Q] No Downloading mode

Hi
I bought my unlocked samsung captivate recently and it had pre installed continuum rom on it. I tried to install CM7 on it, but things went downhill pretty fast after that.
This is what I did:
- Read the thread "read before flashing" got the cm7 mod and got the phone into downloading mode using the volume buttons and usb
- Then I read that I can use ROM Manager and used that to first backup and then selected the cm7 package in the install rom (I checked all 3 boxes to wipe data, both caches)
- After it rebooted it showed the Cyanogen screen but after that it kept going in loops - restarting and installing (for 3 seconds hardly)
- I put the phone again in the download mode (it went to the mode fine)
- After that, when I removed the USB cable or the battery I forgot which one : it booted back with random dots on black screen
Here is what I have tried:
- The 3 button combos and everything else just shows a blank white screen or a black screen with random dots
- I have installed the heimdall suite and installed the drivers using that
- my phone is recognized as "USB mass storage device" but nothing else works
- I have also tried the Odin method to detect the phone but it doesnt get detected
- I know about the USB jig but it will take 3-4 days before I can procure the mini usb jig
Please let me know what else I can try to get to download mode (I sincerely hope there is still a method left). As you all can see this is my first post here, so please let me know what other details I can provide.

The white screen or black screen can be download mode. The image might have gotten corrupted. I recommend reflashing to stock an reinstalling either heimdall or regular samsung drivers. You can't have both since one mess the other one up.

Check my sig. Link to a thread on how to get download mode.

Hi
Thanks a lot for the prompt response. Something weirder than the last 5 hours happened:
- I connected the phone to the comp and launched kies just to try. It didnt do anything but it was recognizing the device
- I tried for it to connect left it for 10 minutes. Disconnected the phone since nothing was happening
- Then I disconnected again and powered off/battery out. Then connected usb then connected to comp and let go of the volume buttons (which I was holding before connecting to the USB)
- Win7 installed some driver and then somehow....somehow....it was detected in the "Odin3 One-Click Downloader and Drivers CAPTIVATE ONLY" - it showed added
- After this I just clicked on it and all went smoothly from there on
- Now I am on the At&t stock firmware
Can anybody explain/think why this worked? Was it just a miracle ?
Also, any suggestions as to :
- what I did wrong the first time round which I can avoid this time when I install the mod.
- why was the cyanogen mod installation stuck in the reboot/install loop?
- Once I am in the download mode what is the safest mode to exit it? Battery out? USB out?
- Should I use ROM Manager or is it not a good software?

Sometimes you just get lucky. Most likely kies repaired the drivers, restarting phone got the ball rolling. I guess. Just be happy it worked.

I can't speak as what exactly went wrong, and I haven't used CM7 in a long while BUT Rom Manager is trash for our Galaxy S phones. =( sad truth but don't waste your time with it.

Thanks, yeah I am definitely happy that it worked but now I want to try and understand the things I did wrong so that I can do it correctly this time.

Don't use Rom manager next time. Do it from CWM (update.zip) or a kernel that has it baked. Do it manually is the best advice I can give you.

could you guide me to where i can read what a cwm is?

CWM= Clockwork recovery mod. What version of android are you running?

prbassplayer said:
Don't use Rom manager next time. Do it from CWM (update.zip) or a kernel that has it baked. Do it manually is the best advice I can give you.
Click to expand...
Click to collapse
This. Rom manager sucks. I would use odin to flash one of the leaked gingerbread builds, and then flash a custom kernel, also with odin (boogs kernel comes to mind), which has clockworkmod built in. Place the cyanogenmod install file, along with google apps, on the internal sd card. Then it's just a matter of holding power and both volume buttons until the phone reboots, when you see the white at&t screen release the power button but keep holding the volume buttons. You should eventually come to a black screen with green writing if memory serves me correctly, this is clockwork mod. I actually don't remember what color the writing is, but it should say CWM recovery at the top. choose the options to wipe data/factory reset (navigate with volume keys, select with power key), wipe cache, then go into advanced, and wipe the dalvik cache. once this is complete, go back to the main cwm menu, and select "install from sd card", then just find the cyanogenmod zip, select it, and let it go. it will reboot once to repartition to the mtd file format, and then it will automatically continue the install. Welcome to CyanogenMod. Use the same method to flash the google apps package. It sounds more complicated than it actually is.

build.prop mistake

Hey all My friend gave me his Droid Bionic running ICS update and he said he was trying to get it to work with att BUT while in the process he tried to put in a different build.prop but he deleted the one out of his system folder. The phone boots on a black screen and will not connect to the pc he said he also tried doing the recovery thing to it,
So. No build.prop
Black screen boot.
And no way to mount.
Any ideas?

midgetgnome said:
Hey all My friend gave me his Droid Bionic running ICS update and he said he was trying to get it to work with att BUT while in the process he tried to put in a different build.prop but he deleted the one out of his system folder. The phone boots on a black screen and will not connect to the pc he said he also tried doing the recovery thing to it,
So. No build.prop
Black screen boot.
And no way to mount.
Any ideas?
Click to expand...
Click to collapse
do you still have the original rom zip?
if have then copy the zip in sd card using another phone or card reader and then do the fresh flash again.
if dont have then re download the zip and do the fresh flash..
hit thanks button if i helped you somehow.
and u need to be more specific on what device you are talking about..
you havent mention the device you are using..

midgetgnome said:
Hey all My friend gave me his Droid Bionic running ICS update and he said he was trying to get it to work with att BUT while in the process he tried to put in a different build.prop but he deleted the one out of his system folder. The phone boots on a black screen and will not connect to the pc he said he also tried doing the recovery thing to it,
So. No build.prop
Black screen boot.
And no way to mount.
Any ideas?
Click to expand...
Click to collapse
If the data on this phone is no longer needed, you could alway flash a stock JB 4.1.2 using RSD.
That'll surely fix all the problem except data loss.

the hellboy said:
do you still have the original rom zip?
if have then copy the zip in sd card using another phone or card reader and then do the fresh flash again.
if dont have then re download the zip and do the fresh flash..
hit thanks button if i helped you somehow.
and u need to be more specific on what device you are talking about..
you havent mention the device you are using..
Click to expand...
Click to collapse
I dont have anything I did download the ICS SBF but RSD wont see the device for some reason. And I did tell you what device I said DROID Bionic in my first post. Any other specifics I cant give because I cant get into my phone to see them.

midgetgnome said:
I dont have anything I did download the ICS SBF but RSD wont see the device for some reason. And I did tell you what device I said DROID Bionic in my first post. Any other specifics I cant give because I cant get into my phone to see them.
Click to expand...
Click to collapse
You didn't state that you did this. So, I'll start with the obvious.
1. Fully charge and then power off the phone.
2. Press & hold the volume + and volume -.
3. Power on the phone.
4. Once the boot menu comes up, use volume - to move to AP Fastboot & select wit volume +.
5. Plug in the phone to your PC and run RSD Lite. Click Config>Flash modes>Fastboot Mode.
6. Flash the phone with ICS or JB.
If you choose BP SBF Flash, on the menu, RSD may not work right. If you try to downgrade it, you can brick it.
Let me know how it goes.

pmrmx774 said:
You didn't state that you did this. So, I'll start with the obvious.
1. Fully charge and then power off the phone.
2. Press & hold the volume + and volume -.
3. Power on the phone.
4. Once the boot menu comes up, use volume - to move to AP Fastboot & select wit volume +.
5. Plug in the phone to your PC and run RSD Lite. Click Config>Flash modes>Fastboot Mode.
6. Flash the phone with ICS or JB.
If you choose BP SBF Flash, on the menu, RSD may not work right. If you try to downgrade it, you can brick it.
Let me know how it goes.
Click to expand...
Click to collapse
I would definitely not recommend flashing JB. Stay with ICS.
Once you go to JB you are locked down with lots of restrictions.
If you stay with ICS you can root easier, and you have more choices of custom roms that you can use.
If you go JB, you can only use JB custom roms.
You can use either safestrap or bootstrap if you stay with ICS. If you do JB, you are stuck with safestrap.
Stay with ICS! If you want JB, only use custom JB roms, don't flash them through RSD.

pmrmx774 said:
You didn't state that you did this. So, I'll start with the obvious.
1. Fully charge and then power off the phone.
2. Press & hold the volume + and volume -.
3. Power on the phone.
4. Once the boot menu comes up, use volume - to move to AP Fastboot & select wit volume +.
5. Plug in the phone to your PC and run RSD Lite. Click Config>Flash modes>Fastboot Mode.
6. Flash the phone with ICS or JB.
If you choose BP SBF Flash, on the menu, RSD may not work right. If you try to downgrade it, you can brick it.
Let me know how it goes.
Click to expand...
Click to collapse
RSDLite does noto see the phone at all. Making it impossible to flash. I have tried 6 different cords including the one that came with the phone. And if you read one of my earlier posts you will see where I said rsd isn't working. I cant seem to figure out how to get it to work either. Ive done the drivers several times along with new cords..

midgetgnome said:
RSDLite does noto see the phone at all. Making it impossible to flash. I have tried 6 different cords including the one that came with the phone. And if you read one of my earlier posts you will see where I said rsd isn't working. I cant seem to figure out how to get it to work either. Ive done the drivers several times along with new cords..
Click to expand...
Click to collapse
Do you see a device in Windows Device Manager? Can you get to the menu I talked about on the phone. RSD won't see the phone if Windows doesn't load the drives correctly. Do you have the Android SDK loaded? That can help w/ manual flashing... and drivers. It's important to get the phone in the AP Fastboot mode to get the proper connectivity.

Cannot get into recovery

I have a LG Thrill that is stock ICS. If I boot the phone and check all the buttons the buttons work, however when I try to boot into recovery the phone just boots or turns off. I hold the 3d and volume down button then push the power button until a vibration and lg logo then release the power button. I've tried to go thru adb to reboot into recovery but I cannot see the device in adb.

Have you actually installed cwm recovery?
Sent from my LG-P920 using xda app-developers app

No, I'd love to be able to install CMW or TWRP but the guides I have found all say that I need to be able to boot into recovery.

You can install CWM (or TWRP) by flashing it with Fastboot, but you will need to place a recovery image file named "cwm.img" in the CWM folder in the Fastboot pack. Some available packs (check the Optimus 3D dev section, same device, Euro flavor) have the image files already included, I think.
The method I have mostly used is to flash xbsall's rooted ICS with recovery.
http://forum.xda-developers.com/showthread.php?t=2195753
His rooted ICS uses a type of recovery that is in system partition (not recovery partition). So if you want that, or you do not want to flash your device, use Fastboot (or one of the customized variants)

First, thanks for the help. I now have superuser available and couldn't be happier. The reason I decided to do this was that I couldn't get the wifi to switch on and even with the super user access it won't. Should I assume that this is a problem with the phone or is this something that would work if I were to roll back to gingerbread?

It's most likely a problem with the ROM/kernel you're using. I'd switch to another.
Sent from my LG-P920 using xda app-developers app

I can't say thanks enough for holding my hand so far. Is there a good guide that you would recommend for me to look at. Some of the ones I've viewed here have different information for each of them. Is the reason that thus phone is so different from what I'm used to due to the omap processor?
Sent from my SGH-I727 using Tapatalk

I had the wifi problem a while back; it was due to me installing a custom ROM without doing required wipes in recovery before installing it. Not sure how you got to ICS, but if you follow the guide I linked above it should solve your problem. You don't have to install the custom ROM if you don't want. Just stop after installing rooted ICS. Be advised that driver install for pc is fiddly, hence the detailed install instructions.

Can anyonne throw me a line here. When I install the omap drivers for the phone (step f4.1-4.5) the phone still keeps disappearing from the device drivers. Even disconnecting and reconnecting with the volume up button pressed isn't helping. Any ideas? I've tried uninstalling all of the drivers, using system restore to roll back, different cables. It used to work, now it doesn't any ideas?

If you mean the way it keeps blinking on and off, be ready with the mouse. Watch for when it appears and quickly right click on it, you kind of have to catch it. Then point it to the driver in the Fastboot folder (not the one in the omap4flash installer folder) as described. Once that is done you unplug phone, then replug, volume up, and let the two LG drivers install. All LG stuff on pc should be uninstalled and pc rebooted before beginning with all this. Also, some antivirus software can mistake the driver as being malicious and delete it when unraring the Fastboot folder, without it notifying you. And if you have a custom bootloader on your phone you may need to skip running omap4flash installer; they seem to not agree somehow.