Database Info

Rsd lite can't detect my phone

Currently, my phone is on central europe rom with jit, apps2sd and open recovery 1.46 installed. I had previously used rsdlite 4.5.3 to flash my phone but now it won't detect my phone after i installed jit, apps2sd and open recovery 1.46. Anyone can help? Thanks.

put your device into bootloader mode by pressing vol down + camera key + on button
before that you must install motorola usb driver first

i managed to get it to work..problem was caused by my pc and not the phone..zzz..anyway thanks for the help!

make sure you are in bootloader mode but not in recovery mode
recovery mode: a "!" sign will appear
bootloader: dark backgroud and just some numbers and letters
when you connect your phone to computer, not your phone name but the name of the cpu (OMAP3440)will be identified

Same problem
I am having the same problem as you do. I had a stock Milestone. I fully rooted it through SuperOneClick. I wanted to install CyanogenMod so I had to flash it with the recovery SBF.
I have installed the latest motorola drivers and RSD. I boot it using Up on D-Pad and power, plugs it to computer. The flash drivers shows a successful installation.
I open up RSDLite with administrator rights. Still, it doesn't recognize my phone. I tried it on every way I could imagine. Open RSD first, after; plug first, after.
My battery is fully loaded.
My device is a rooted Milestone running on Android 2.2.1.
Kernel 2.6.32.9
It has superuser installed and has been flashed with ClockworkMod 3.1.0.2 using ROM manager. That was because I wanted to backup my stock ROM aswell. It doesn't work either. After booting it shows the yellow exclamation mark and freezes.
What else could it be? :/
Thanks in advance

Solved.
I figured it out. I wiped out all my data from the phone (back to factory settings option) and it is now flashing fine through RSD Lite.
Pretty simple.

Hey guys. I a having same problems as described above. Namely, I succesfully installed moto , instaled RSD, and have the sbf. The problem is that though my phone is running bootloader, and displays that there is a USB connection, the cpu doesnt show that a phone is connected. Therefore, RSD is blank and doesnt show device (so i cant START the sbf flash. Any suggestions? One note, when I go into Recovery to wipe my data there is the following two lines of text on the bottom of the screen :
"E:Can't open /cache/recovery/command
E: an't open /cahe/recovery/caller"

Those errors in recovery are harmless. Recovery is basically saying that it cannot find a downloaded OTA package to automatically apply.
Unfortunately I don't flash in windows, but based on threads in the past, these seem to be driver or permissions problems (maybe you need to be admin when running RSD, dunno). FWIW I use sbf_flash on Linux
Sent from my Milestone XT720 using xda premium

[SOLVED] gt-i9023 help please - no usb,adb,fastboot access

I am a beginner at this so please excuse me.
I successfully rooted my phone, installed clockwork, super user was working, could connect like a dream with usb to the phone. Flashed stuff using fastboot in command line - all was good.
When I say successfully it did take a long time, the phone didnt work for a while but I flashed clockwork on then flashed the rom for my phone from here http://forum.xda-developers.com/archive/index.php/t-1063664.html
I used this one:
Android 2.3.3/GRI40/KB1 Radio/KA3 Bootloader (http://android.clients.google.com/p...2cf141e6a.signed-soju-ota-102588.f182cf14.zip)
Works on: I9020T, I9023
Official, signed, can flash with ClockworkMod or stock recovery. Contains recovery, radio and bootloader.
Which was great - sorted the phone a treat - I had the super user working - I installed the clockwork rom app - worked a treat - even did a backup (I think)
Then the phone tried to update to 2.3.4 which failed - right now I should of check the forums but thought I know I'll just flash the update from the above page - which failed - not to be defeated I tried harder using different roms through clockwork recovery or clockwork rom mod until sucess 2.3.4 GRJ22 build.
Then I find the super user app doesnt work or the clockwork rom - no problem boot into clockwork recovery - uh oh thats gone as well though i can get to android recovery.
I'll just flash clockwork recovery on but I cant as I've no access with adb or fastboot the phone is not connecting to the pc in fastboot mode with the android logo and phone details.
When I'm trying to use USB connection on the phone normally the USB man goes orange then back to green - and the phone prepares the USB storage again.
I can use a app to get files on to the sd card for use with android recovery so i try to reflash the 2.3.3 rom above that worked but I get the status 7 error with a long number 1297306095
I try the update again and this is where i realise that the update ROM i put on was the wrong one.
I flashed this: Android 2.3.3 (Build GRI54/KB3 Radio/KA3 Bootloader) (whole rom)
I should of flashed this Android 2.3.3 (Build GRI40/KB1 Radio/KA3 Bootloader) (smaller update)
I can flash the correct update above but it doesnt change anything.
I have spent a few days now trawling the forum with little success and having got all the correct drivers on the pc and had it connecting fine I am assuming it is a phone issue now
the base band details have changed from XXKB1 to XXKD1 and the build from GRI40 to GRJ22
I am at my wits end here and before I put a hammer to my phone and send it back as an insurance job I'd like to mend my stupid mistakes.
Thanks
Acne

it doesnt matter if you flashed the whole rom. (provided you didnt use odin)
first thing, try to format sd card through the phone,
then enable usb debugging and try using adb n fastboot.
also, try to flash a newer recovery.img ( be careful no to use one not meant for ur phone e.g ns4g...)
post ur results.
good luck

can't find an option from within the phone to format the SD card - found an app on the store that is called "format sd" which did something and allowed me to connect to the USB once but it was very flaky and took a few attempts at the "turn on usb" screen to get it to connect. I'm not sure that it wasnt just deleting the data from the sd rather than formatting as it took maybe 10 seconds first time and now its done straight away if I try again.
Edit - i've used the stock erase usb command within the phone and the USB connection within the phone seems to becoming more stable - I can read and write data to it from the pc but it still struggles to connect first time.
No change with command line commands abd or fastboot neither are connecting.
I've come to the conclusion that maybe I need to flash a newer recovery image (ROM?) myself but where do I find one? And how do i check that it really is the correct one for my phone - which of the details are important - should i use the original stock details? I'm confused, remembering all I can use is the "Android system recovery <3e>" that only gives me the option of reboot, apply update from sd card, wipe data/factory reset, & wipe cache partition.
I flashed the wrong ROM with the clockwork rom app from within the phone I dont know what odin is.
Thanks for the pointer anymore ideas or direction appreciated.
Acne

Try to wipe from the stock recovery and then install this
http://android.clients.google.com/p...2cf141e6a.signed-soju-ota-102588.f182cf14.zip
It is the full 2.3.3. It will return your phone to complete stock 2.3.3
P.s sorry i am not being able to help more. I am myself in a far bigger trouble

I tried that rom but got the status7 error. That one worked before under clockwork but won't reflash now. I can do a factory reset under stock but will that make a difference? I thought all that did was reset user data not the system data. I think l need to wait for a new stock Tom to be issued.
Acne

Tried the reset phone from within the phone and reset using stock recovery, still cant flash the old 2.3.3 rom above getting the status 7 error:
assert failed ! less_than _int(1297306095. getprop(ro.build.date.utc"))
so the usb works fine from within the phone when the phone is running normally, when I connect the phone in fastboot mode it shows as an Android ADB interface on the "safely remove hardware" window but i cant use any command prompt instructions on the phone - using fastboot devices to show connected devices I get no reponse.
Any ideas?
Any pointers to a later rom that will correct my problems?
Thanks
Acne

After a bit of experimenting I find that when the phone is switched on normally I can use the ADB devices command to return the ID of the phone. The fastboot devices command still returns a blank.
Is this normal?
Does this mean I could flash the clockwork recovery image onto the phone? or can all that malarkey only be done in fastboot mode?
thanks
Acne

You need the fastboot devices command to return your phone info then you can fastboot flash recovery in order to try flashing a recovery that will allow you to flash the rom you are getting a failed message from. The stock recovery can only flash official updates put out by Google iirc.
I am thinking you are having driver issues on the PC you are using. Try another PC with fresh drivers or uninstall and reinstall the drivers on the one you have been using.
sent from the nexus of the 4g universe

I've read up on the driver problems, I tried the phone on two different pcs using two different methods on each to install the correct drivers. none work. The phone used to connect fine which is how i rooted the phone. I'm using the same pc, same supplied cable and can see the ADB mounted in the "safely remove hardware" window
The adb command works when the phone is switched on normally, but not fastboot command.
When in fastboot mode neither works. Looking in device manager the android adb interface is listed fine under android phone.
I'm pretty sure its not the drivers.
Doesn't the above prove that the pc connects fine but the phone is broken in fastboot mode?

You could still flash the latest 2.3.4 full ROM with ODIN. The Phone will be restored completely and then you can root it again.

Thats great Odin looks like it will be the way forward, just so I dont make another noob error could someone point me in the right direction for the correct version of odin and a guide on how to use it. I have looked around the forum but am struggling to find the relevant thread
I have tried the usb/2 button and it enters download, the version od odin that i found (1.81) does see the phone but I think that version is for the 9020 only I have the GT-i9023 so dont want to use the wrong programme/rom
Thanks
Acne

Ok took a chance and flashed the phone with odin - great it worked reset all the fastboot mode values back to their original ones when i got the phone. (seems I chose the correct rom) the only difference is that the Carrier info is now EUR not VDF as it was when I first got the phone.
Applied the auto update to 2.3.4
Tried at every step but I still have no fastboot or ADB access the phone just doesnt connect. Tried different leads, tried different usb ports - nothing.
I'm stumped now unless there are any advanced settings in odin I should try.
Acne
The

Discovered after the auto update to 2.3.4 that the USB connection from within the phone was "broken" again, To sort this i did a format cache and reset phone from the stock recovery which sorted the usb connection. so thats that one solved then.
tried again to connect via command prompt, unistalled drivers - reinstalled drivers - no change still no devices detetcted.
Any good ideas?

Solved
using the usbdeview mentioned here I uninstalled all the usb drivers on my pc that looked like they could be anything remotely connected to the nexus and samsung.
I ran and updated/download pretty much everything i could through SDK
Then I did everything I read in this thread
Up till then I had been using the fastboot command found and downloaded through this thread
That continued not to work but when i tried the fastboot in the android-sdk/tools folder I finally got fastboot access.
Solved Solved Solved
to get my phone unlocked and updated I did an odin restore to 2.3.3 let it auto update to 2.3.4 copied the su(superuser zip) to the sd card. flashed clockwork recovery and then installed the su.zip with clockwork. after that I installed the rom manager from the android shop and Inow have the phone just how i want it.
To all those that have helped with their ideas here many many thanks.
Acne

[Q] failure after root and tried to recovery

Hi there I have a Nexus S with 4.04 on it, so the other day I followed the instruction online and tried to root the phone, I have phone driver installed, and able to unlock my bootloader, the LOCK STATE is UNLOCKED. and I was able to flash Clockworkmod recovery v5.0.2.0.
But after this step, and I tried to reboot, my phone just stuck at the google logo with the unlock sign at the bottom, and wouldn't do anything afterward. (seems like a root loop?)
I tried pulling off the batt a few times but no good. I am still able to lock and unlock bootloader through cmd.(just like in normal state)
I tried to install factory img as shown in the thread http://forum.xda-developers.com/showthread.php?t=1572307. but when I type in the first line "adb reboot bootloader", it says adb devices not found.
so, any idea on how I can restore back to the factory img?
bootloader version i9020xxkl1
model GT-i9020T or if any more info is needed I will be here.....>.<

Did you correctly installed the recovery?
Hi.
First at all let me tell you that I'm not an expert. So, I understand that you should double check this.
I think that you should try to:
- If you have successfully installed the ClockworkMod recovery, you should turn on the device on recovery mode. Vol up + on pushbutton to go inside bootloader. Going down with Vol down, go to recovery and select with on pushbutton.
- Download the correct superuser app for your version. I would double check the md5sum of the file that you have downloaded on your computer.
- Mounting the usb storage of the device on your computer, add the superuser app on /sdcard.
- Umount the usb storage.
- Flash the superuser app, installing from /sdcard from your recovery menu.
- Download a custom kernel on your computer, once that you are unlocked. I'm using CyberGR, and I'm happy with it. You can see all the intallation instructions in the Nexus S development part.
- I that works, I would try to install the kernel in a clear way. For installing the CyberGR ROM, you need to wipe everything and format all. After that, you mount the device on the computer, and try the installation.
Then, if everything is ok, the device will turn on.
Again, I'm not an expert, and I don't know how you can be in contact with the developers that are posting in the developers area. I'm not responsible if your device doesn't works or get bricked.
However, I understand that all that I have described, should not put your device in a worst situation.
And is it doesn't turn on, if it doesn't do anything, then, you can use the linux tooll for bicked devices explained on the developers area.

How to turn on Pantech Discover USB debugging? (via CMD, Recovery, ADB)

I have problems with my pantech discover magnus P9090, the problem is that the phone is completely bricked and dead. When i turned on the phone, it simply just shows BLACK SCREEN ( No Logo and nothing else). My assumption is that there is no OS inside or something causes it to be bricked. I have done almost everything by using Android Recovery (Not custom recovery) to do factory reset and wipe cache. I rebooted it and it doesn't work either. So i found a solution which is by using apply update from ADB. I understand the process but the only problem is
The device is not detected by ADB when i type "adb devices" it could be two problems:
a. No drivers for this phone installed (While i try to update driver, it fails)
b. USB Debugging off (Since phone can't get into OS, so im confused how to turn it on via other ways)
I got the Custom rom and CWM recovery image but how can i install the recovery and ROM if ADB isn't detecting the phone. I can't even use sideload command.
My plan to fix this is by installing CWM with the command "fastboot flash recovery [filename]" and then using CWM to push the file ROM into phone and install zip in SD card. However, it links back that i need the phone to be detected first. Anyone can help me? Thank you so much. Im so badly want to revive this phone. :good:

There's no other way until pantech usa release pdl file for restore discover..
Sent from my ZTE N986 using XDA-Developers mobile app

Install Stock Recovery on Unrooted Phone That Cannot Connect to a PC

Hey,
I own a WileyFox Storm that runs Cyanogen OS (kipper) as stock. A while back, I tried to root it, but failed so gave up. As it turns out, I forgot to get rid of the TWRP CR (which was an edition specifically designed for the Storm). There is now an update which I would like to install, but obviously it does not work because I do not have stock recovery.
MY PHONE IS NOT ROOTED!!!
I was going to flash the stock recovery using ADB fastboot, however my phone is now refusing to be recognised by my PC. Yes;
- I have the correct drivers installed.
- I have enabled USB debugging (I have also tried disabling it).
- I have tried rebooting both my phone and PC.
- I have tried rebooting my phone and wiping Cache and Dalvik Cache.
- I have tried with a different USB cable, and tried using a different USB port.
- I have tried removing my SD card.
My phone says that it is charging (which is is) when it connects to my PC, but nothing comes up, anywhere. No notifications (on both devices), ADB nor fastboot recognises it, no *chime* sound on my PC.
I cannot try using a different PC (I only have one). So, how can I replace the TWRP recovery with stock recovery???
Thanks )