Related
so i have searched quite a bit and have not found a similar issue. My main goal is to get my razar to the .173 build and maintain root. I was at .748 and wanted to flash back to stock (.744) to start from a "fresh starting point" after downloading the the most current version of rsdLITTE (5.6 anyways), the most current moto drivers, and the applicable sbf files. I tried flashing the fast boot files per the instructions that are available on various droid forums. My problem is RSD does not recognize my phone when my phone is in fastboot mode. When my phone is in normal ops. RSD see's my phone. If I start the flashing process RSD will say "switching the phone to fastboot mode" and I watch it physically see it happen on my phone (it switches to fastboot) after a period of time RSD says "phone failed to switch to fastboot". I asked around all over the place and no one has heard of this or had an idea of how to fix. So I ended up learning bit about ADB and found the files to manually (through command prompt) flash to744. I cant find the files to manually update to build .748 or .173. I tried to update via OTA to .748 several times all resulting in failures. Ive tried different downloads of the sbf files, rsdlite, and the moto drivers. I am running xp pro and tried two different machines and several different cables all of the combinations resulting in the same issues as described above when attempting to flash with RSD. From what I gather XDA is my best chance of resolving my anal cranium inversion so hopefully the brain trust here can shed some light on my problems..........please?
Note: Im quite positive this is not a usb cable problem as every other razr/pc interface works, i can transfer files, use pda, adb, charge my phone, etc........
Really......nothin huh? ugh
This must be where threads go to die.
and BEFORE do that, do you read at least 1 minute the DEV section ???....
http://forum.xda-developers.com/showthread.php?t=1453660
pick the right ROM for you here then flash using this method.
xTremePower said:
and BEFORE do that, do you read at least 1 minute the DEV section ???....
http://forum.xda-developers.com/showthread.php?t=1453660
Click to expand...
Click to collapse
Ugh....i cant post over there yet its not working properly for me i get a string of "example" is signed. Error.......theres a couple other people with the same issue. The really weitd thing is after trying a couple times it updated the radio but everything else still errored out. This phone has cause me headaches since day 1 and this is my second phone.
this place is a hot bed of info 0_o
My droid x2 freezes on the dual core start up screen every time i try to turn it on, i pulled the battery out the first time this happened, and I've already went into recovery mode and did the (wipe data/factory reset) option, and i also wiped my cache partition, but still my phone freezes on boot. my phone started doing this when i was using "mcTweaker" and a notification popped up and it said i need to reboot, but as the same time i hit reboot system in the options menu. when i did this the phone cut off and since then it always freezes on the dual core screen when i start it up. i am also still on the stock rom and am rooted. any help or tips on how to fix this is highly appreciated.
if you can still can get to recovery, and have a backup, restore it
as you have wiped data, that is unlikely, unless you flashed re-recovery
sbf is your last option
:/
sd_shadow said:
if you can still can get to recovery, and have a backup, restore it
as you have wiped data, that is unlikely, unless you flashed re-recovery
sbf is your last option
Click to expand...
Click to collapse
im not quite sure how to sbf this phone, once again your help is appreciated... do you know how to? ill check around the forums and see if i can find anything too
Oops
sneaker14 said:
im not quite sure how to sbf this phone, once again your help is appreciated... do you know how to? ill check around the forums and see if i can find anything too
Click to expand...
Click to collapse
Ok my bad, i feel lyk such a noob... i just wasnt waiting long enough for the starting RSD protocol support thing. Problem solved
great, just don't flash wrong sbf
Droid x2 and Milestone x2 have different sbfs, because they are different devices, different radios
ok for some reason it stays on the (Starting RSD Protocol Support) screen and never advances onto anything else D: is there a fix for this or is my completely screwed. i thought since the thread i read said it takes 3-5 minutes to start it up thats what my problem was, but i was wrong, the thing just simply wont start up... sorry for false assumption
yes that's it "Starting RSD Protocol Support"
is all is does, till you start rsd lite, doesn't change till half way through sbf or more
Ok thank you sooo much, this was frustrating me since last friday and i think the rsd lite i had was the problem, i went and downloaded a different one and now its working ... once again thanks for your help, ill get back to ya if i mess anything else up haha
sd_shadow said:
yes that's it "Starting RSD Protocol Support"
is all is does, till you start rsd lite, doesn't change till half way through sbf or more
Click to expand...
Click to collapse
now when i try to do it it says (error switching phone to BP Pass through mode) idk what to do or why its doing this
its a driver issue
a couple of options
use the moto drivers program
or ezSBF for x2, no drivers needed
both in my list of stuff
sd_shadow's list of links for Droid FAQs, SBF, Rooting, ROMs.... https://docs.google.com/document/d/1Goawxdx_UBF4Y8lqzHYWf8Ha3yUcRK4faq0UWIlXLWA/edit
also the fix for the d2 was
" Note: Under certain circumstances (especially when using Windows Vista and Windows 7) there might be a problem with not all device drivers being installed correctly. In such case, the flashing process will abort, and your phone won't be able to boot normally. RSDLite shows the following error message:
Error switching phone to BP Pass through mode
To get around this issue, once you get a Device driver could not be installed message from Windows, don't close RSDLite nor power off the phone. Start Motorola Driver Installer once again, and let it finish. Then if RSDLite didn't timeout yet, head to Device Manager, find the Unknown device, and in its properties' Driver tab click Update driver…. It should now install normally. If RSDLite timed out and you got an error from it, just repeat the SBF process. The driver should now be present, and the flashing process will finish normally.
Once the flashing process is complete, RSDLite will tell you to “power the phone up manually”. In most cases you won't be able to do this straight as instructed: the phone will be bootlooping. Take the battery out, and then place it back in. Press the lock/power button: the phone should boot normally. Close RSDLite. Disregard the warning about flashing not being completed since your phone has already booted into Android.
In case you still get bootloops after pulling the battery, wipe data in Android Recovery. "
Sent from my DROID X2 using xda premium
sd_shadow said:
its a driver issue
a couple of options
use the moto drivers program
or ezSBF for x2, no drivers needed
both in my list of stuff
sd_shadow's list of links for Droid FAQs, SBF, Rooting, ROMs.... https://docs.google.com/document/d/1Goawxdx_UBF4Y8lqzHYWf8Ha3yUcRK4faq0UWIlXLWA/edit
also the fix for the d2 was
" Note: Under certain circumstances (especially when using Windows Vista and Windows 7) there might be a problem with not all device drivers being installed correctly. In such case, the flashing process will abort, and your phone won't be able to boot normally. RSDLite shows the following error message:
Error switching phone to BP Pass through mode
To get around this issue, once you get a Device driver could not be installed message from Windows, don't close RSDLite nor power off the phone. Start Motorola Driver Installer once again, and let it finish. Then if RSDLite didn't timeout yet, head to Device Manager, find the Unknown device, and in its properties' Driver tab click Update driver…. It should now install normally. If RSDLite timed out and you got an error from it, just repeat the SBF process. The driver should now be present, and the flashing process will finish normally.
Once the flashing process is complete, RSDLite will tell you to “power the phone up manually”. In most cases you won't be able to do this straight as instructed: the phone will be bootlooping. Take the battery out, and then place it back in. Press the lock/power button: the phone should boot normally. Close RSDLite. Disregard the warning about flashing not being completed since your phone has already booted into Android.
In case you still get bootloops after pulling the battery, wipe data in Android Recovery. "
Sent from my DROID X2 using xda premium
Click to expand...
Click to collapse
so i installed the device manager 2.2.28 and installed the drivers, and im using rsd lite 5.7 and im still getting the error D: so do u know why its still doing this?
sd_shadow said:
its a driver issue
a couple of options
use the moto drivers program
or ezSBF for x2, no drivers needed
both in my list of stuff
sd_shadow's list of links for Droid FAQs, SBF, Rooting, ROMs.... https://docs.google.com/document/d/1Goawxdx_UBF4Y8lqzHYWf8Ha3yUcRK4faq0UWIlXLWA/edit
also the fix for the d2 was
" Note: Under certain circumstances (especially when using Windows Vista and Windows 7) there might be a problem with not all device drivers being installed correctly. In such case, the flashing process will abort, and your phone won't be able to boot normally. RSDLite shows the following error message:
Error switching phone to BP Pass through mode
To get around this issue, once you get a Device driver could not be installed message from Windows, don't close RSDLite nor power off the phone. Start Motorola Driver Installer once again, and let it finish. Then if RSDLite didn't timeout yet, head to Device Manager, find the Unknown device, and in its properties' Driver tab click Update driver…. It should now install normally. If RSDLite timed out and you got an error from it, just repeat the SBF process. The driver should now be present, and the flashing process will finish normally.
Once the flashing process is complete, RSDLite will tell you to “power the phone up manually”. In most cases you won't be able to do this straight as instructed: the phone will be bootlooping. Take the battery out, and then place it back in. Press the lock/power button: the phone should boot normally. Close RSDLite. Disregard the warning about flashing not being completed since your phone has already booted into Android.
In case you still get bootloops after pulling the battery, wipe data in Android Recovery. "
Sent from my DROID X2 using xda premium
Click to expand...
Click to collapse
I installed the drivers and im still getting the error for some reason D: i used motorola device manager 2.2.28 to install the drivers. and am using rsd lite 5.7
use ezSBF for x2, no drivers needed
sd_shadow said:
use ezSBF for x2, no drivers needed
Click to expand...
Click to collapse
alrighty im bout to try that, but if that doesnt work is it the last option for me... and if i brought it back to the store would they fix it?
unlikely that verizon would fix, rooting voids warranty
they may replace, if you tell them you don't know what happened
if you bought insurance, that will cover it
Sent from my DROID X2 using xda premium
sd_shadow said:
unlikely that verizon would fix, rooting voids warranty
they may replace, if you tell them you don't know what happened
if you bought insurance, that will cover it
Sent from my DROID X2 using xda premium
Click to expand...
Click to collapse
all right, if this dont work ill take it back and tell em i dont know what happened. but a problem is it says "failed to boot 1" as soon as you tun the phone on so hopefully they wont know
Whoa are you telling us ezsbf didn't work?? Is this the first "actual" bricking of a x2?
Sent from my MB870 using xda app-developers app
sneaker14 said:
all right, if this dont work ill take it back and tell em i dont know what happened. but a problem is it says "failed to boot 1" as soon as you tun the phone on so hopefully they wont know
Click to expand...
Click to collapse
your holding volume up, when powering on, to boot to 'starting rsd support'?
I really screwed up my droid x2. As soon as it turns on it gives me an error
"Sorry!
The process com.motorola.service.main has stopped unexpectedly. Please try again.
Force Close"
After taping on force close all I see is a black screen with the status bar. I am able to access recent apps long pressing home screen. I am also able to use Google search by long pressing search key and speaking into it. I tried going into android recovery and wiping data and cache but it did not help. I wanted to SBF but it gets stuck on "starting RSD protocol support" screen.
Any help to just get the phone running will be appreciated. Thank you folks.
PS: The phone is rooted with stock android 2.3.5. Also USB debugging got disabled since I did factory restore prior to this mess up
-------------------------------
UPDATE 6/24/13
-------------------------------
Successful SBF ed without USB debugging on using windows 7
Phone works but shows a grey triangle outline in notification bar (seems network issue since phone is not activated)
Its been a while since I have done an SBF on this phone. But When it says "starting RSD protocol" I think thats when you run the SBF on your computer.
Also, what were you trying to do when this happened? Flash a ROM? If so, which one? If it was a Cyanogenmod ROM, you need to be on 2.3.4. Not 2.3.5. That may have caused your problem.
jsgraphicart said:
Its been a while since I have done an SBF on this phone. But When it says "starting RSD protocol" I think thats when you run the SBF on your computer.
Also, what were you trying to do when this happened? Flash a ROM? If so, which one? If it was a Cyanogenmod ROM, you need to be on 2.3.4. Not 2.3.5. That may have caused your problem.
Click to expand...
Click to collapse
I had rooted my phone few days back, and I had frozen my bloatwares. But I noticed that I wasn't able to access my contacts it forced closed, and so i unfroze my bloatware but it did not work. Then I did factory reset after which this problem started.
I am using RSDlite 5.3.1 on windows 8, but since my USB debugging is disabled, I don't think I can SBF and RSD lite doesnt recognize my device. I am not sure tho
kinuser said:
I had rooted my phone few days back, and I had frozen my bloatwares. But I noticed that I wasn't able to access my contacts it forced closed, and so i unfroze my bloatware but it did not work. Then I did factory reset after which this problem started.
I am using RSDlite 5.3.1 on windows 8, but since my USB debugging is disabled, I don't think I can SBF and RSD lite doesnt recognize my device. I am not sure tho
Click to expand...
Click to collapse
I think Windows 8 may be your problem. I think I remember people having problems with it. I dont think USB debugging matters with SBF. Once you start the RSD Protocol, it should open it up to start the SBF.
Did you also make sure you had the motorola drivers on your computer?
jsgraphicart said:
I think Windows 8 may be your problem. I think I remember people having problems with it. I dont think USB debugging matters with SBF. Once you start the RSD Protocol, it should open it up to start the SBF.
Did you also make sure you had the motorola drivers on your computer?
Click to expand...
Click to collapse
Windows 8 is the problem. I remember rsd lite would never work on my windows 8 laptop.
Sent from my XT907 using xda premium
now that i have successfully SBF'd it to 2.3.4 and applied OTA updates it is still showing tht gray triangle outline, and for some reason it keep getting errors while trying to root it. I tried petes tools and other one click methods. In petes tools i get error sayin phone rooted but cannot push superuser.apk while in other one click method it tell me adb server is out of date
kinuser said:
now that i have successfully SBF'd it to 2.3.4 and applied OTA updates it is still showing tht gray triangle outline, and for some reason it keep getting errors while trying to root it. I tried petes tools and other one click methods. In petes tools i get error sayin phone rooted but cannot push superuser.apk while in other one click method it tell me adb server is out of date
Click to expand...
Click to collapse
Don't update. Sbf back to 2.3.4 then root. Stay on 2.3.4 if you want to use a custom rom
Sent from my SCH-I535 using xda premium
I've looked at over 30 different posts on this site and other sites on this topic and tried several things, but nothing is working so I'm hoping someone can take this noob under their wing to try to walk me through restoring my Razr Maxx. Many of the posts I tried had broken links to files or other issues.
I rooted the phone but was unsuccessful in loading a bootloader. The phone goes to the "Encryption unsuccessful" screen on boot up. "Reset phone" does not work. I can get into AP Fastboot fine.
I installed the Google USB drivers and Moto drivers from the SDK. Downloaded and ran Motohelper.
Installed RSD Lite 5.7 but it does not recognize the phone, even when the phone is in Fastboot mode and plugged in via USB. The phone indicates "USB Connected" but RSD doesn't show the phone.
I downloaded VRZ_XT912_6.5.1-73_DHD-11_TA-3_1FF_02.xml.zip
I have no idea what to do now.
Please keep in mind, I'm a total noobie, so very explicit instructions would be a GREAT HELP! Links to other threads that don't really address my particular situation or that have old broken links will not really help.
Thanks!
John
Get into fastboot mode and use this utility: http://www.droidrzr.com/index.php/t...xt912-jellybean-windows-mac-linux-all-in-one/
Thanks for the link -- that worked!!
jwiltse said:
I've looked at over 30 different posts on this site and other sites on this topic and tried several things, but nothing is working so I'm hoping someone can take this noob under their wing to try to walk me through restoring my Razr Maxx. Many of the posts I tried had broken links to files or other issues.
I rooted the phone but was unsuccessful in loading a bootloader. The phone goes to the "Encryption unsuccessful" screen on boot up. "Reset phone" does not work. I can get into AP Fastboot fine.
I installed the Google USB drivers and Moto drivers from the SDK. Downloaded and ran Motohelper.
Installed RSD Lite 5.7 but it does not recognize the phone, even when the phone is in Fastboot mode and plugged in via USB. The phone indicates "USB Connected" but RSD doesn't show the phone.
I downloaded VRZ_XT912_6.5.1-73_DHD-11_TA-3_1FF_02.xml.zip
I have no idea what to do now.
Please keep in mind, I'm a total noobie, so very explicit instructions would be a GREAT HELP! Links to other threads that don't really address my particular situation or that have old broken links will not really help.
Thanks!
John
Click to expand...
Click to collapse
jwiltse said:
OK, I thought I had the Moto drivers installed, but apparently I did not. I installed the Motorola Device Manager and now my phone shows up in RSD Lite, but when I tried to flash a rom, I got this message: "Please check input file. Either XML format is wrong or image files associated with it are missing." I tried 3 different ROMs that supposedly work with this phone and got the same error. Any ideas?
Click to expand...
Click to collapse
My XT912 Razr bricked a while ago and I fixed it thanks to this program!
Download it here: http://forum.xda-developers.com/showthread.php?t=2192467
This utility will restore your Razr.
NOTE: If your battery on your phone is dead, then you need to purchase a Motorola factory cable off ebay. They're relatively cheap. So after you charge it with the factory cable, you can then run the program and follow the instructions.
Hope this helped. Happy 4th
I recently got my new Verizon Galaxy S4 and decided to play around with it. I got it rooted fine and got a few apps on there (like Titanium backup) and decided that, since I would eventually want to play around with ROMs, I would want to unlock the phone.
I looked around and found there were some options for me, the one I chose being the "all in one" option that roots, unlocks and installs a custom recovery mode for you. I went through this process and now get nothing but the Downloader Mode (could not do normal boot). Even if I pop out the battery and try to reboot it, I get this screen.
I later found that apparently the ME7 model currently will not accept attempts to unlock the phone and install a custom ROM or recovery menu. How do I fix this? I tried using Odin, but it doesn't recognize the phone as being connected. I am currently trying other methods like Kies, to see if there is any way to at least to an emergency recovery and get it back to normal.
EDIT: Ran into the same issue with Kies as I did with Odin, it does not see anything connected to the computer.
Do you have the correct drivers installed? Does adb recognize the device? You're in Odin mode when you try to use Odin to push something? I believe with ME7 you can Odin back to the official stuff.
Sent from my SCH-I545 using Tapatalk 4
TheColdOne said:
I recently got my new Verizon Galaxy S4 and decided to play around with it. I got it rooted fine and got a few apps on there (like Titanium backup) and decided that, since I would eventually want to play around with ROMs, I would want to unlock the phone.
I looked around and found there were some options for me, the one I chose being the "all in one" option that roots, unlocks and installs a custom recovery mode for you. I went through this process and now get nothing but the Downloader Mode (could not do normal boot). Even if I pop out the battery and try to reboot it, I get this screen.
I later found that apparently the ME7 model currently will not accept attempts to unlock the phone and install a custom ROM or recovery menu. How do I fix this? I tried using Odin, but it doesn't recognize the phone as being connected. I am currently trying other methods like Kies, to see if there is any way to at least to an emergency recovery and get it back to normal.
EDIT: Ran into the same issue with Kies as I did with Odin, it does not see anything connected to the computer.
Click to expand...
Click to collapse
You need to make sure you have the drivers for the phone and have a solid USB connection (I prefer the rear of a tower)
sent from my GE gs4
I ended up getting it to work. I had to go here:
http://www.intel.com/support/chipsets/inf/sb/CS-013541.htm
and get files to get the computer to recognize the device. Even afterwards, Keis had no idea what was going on, and Odin saw it and was able to install a stock firmware I downloaded earlier, saving the phone.
For now I will be satisfied with just root access and will wait for ROM capabilities.
I hate to hijack a thread but I'm stuck here. My GS 4 (Vzw) was supposedly successfully rooted using TWRP, but now I have no way to enter any sort of recovery. The package I downloaded for the root does not have an Odin version to run. I've been getting the endless prompts to install the 4.3 update but there is no way to do this on my phone. I get the same "Could not do normal boot. Odin mode. Write protection enabled" message with the downloading screen. I try to boot into recovery via CWM or Goomanager but it always goes to the same screen. I can't make any backups or restore now either or I would just do a factory reset. Any ideas? I'm on VRUAME7.
Um.... there's no recovery available with ME7.... are you on the MDK bootloader?
Sent from your mom's smartphone
I don't think so but how would I confirm? I'm just trying to get the 4.3 update installed but at every attempt it goes into Odin Mode and gets stuck.
BoltsRUs said:
I don't think so but how would I confirm? I'm just trying to get the 4.3 update installed but at every attempt it goes into Odin Mode and gets stuck.
Click to expand...
Click to collapse
You're said that you're on ME7 - what you need to do is to flash the "No wipe" ME7 ROM onto your phone. It's in the Development forum.
http://forum.xda-developers.com/showthread.php?t=2301259
You've got to update to MI1 before you can install the 4.3 update (MJ7).
ONLY flash files intended for whatever release you're running. You can't mix and match, can't go backwards, and can't skip updates.
Theres also an ml1 factory image in the dev section.
Hit thanks if I helped you out. Doing a little bit of reading goes a long way. Sent via tapatalk.
TheColdOne said:
I ended up getting it to work. I had to go here:
and get files to get the computer to recognize the device. Even afterwards, Keis had no idea what was going on, and Odin saw it and was able to install a stock firmware I downloaded earlier, saving the phone.
For now I will be satisfied with just root access and will wait for ROM capabilities.
Click to expand...
Click to collapse
Hi! Sorry to kind of "butt in" on your thread, but I'm somewhat of a noob and have the same exact problem as you. If you don't mind, can you explain what you downloaded from Intel and what you did afterwards that fixed your problem? I'd really appreciate it, since my phone's been dead to me for more than a week now....
nyankat said:
Hi! Sorry to kind of "butt in" on your thread, but I'm somewhat of a noob and have the same exact problem as you. If you don't mind, can you explain what you downloaded from Intel and what you did afterwards that fixed your problem? I'd really appreciate it, since my phone's been dead to me for more than a week now....
Click to expand...
Click to collapse
On that page I linked to, look for this:
Solution:
Download and run the Intel® Chipset Software Installation Utility so Windows* properly recognizes the SMBus controller.
Get the proper driver download according to your OS, then install it. This should allow Odin to see the phone for you to install a clean copy of the stock ROM onto the phone.
If you want more details I am sorry to say I cannot provide them. When things involve me fixing my own technology, it is a lot of rapid-fire troubleshooting and I just go with what sticks without really memorizing what I did (so if I run into this issue again, I have to re-research).
TheColdOne said:
On that page I linked to, look for this:
Solution:
Download and run the Intel® Chipset Software Installation Utility so Windows* properly recognizes the SMBus controller.
Get the proper driver download according to your OS, then install it. This should allow Odin to see the phone for you to install a clean copy of the stock ROM onto the phone.
If you want more details I am sorry to say I cannot provide them. When things involve me fixing my own technology, it is a lot of rapid-fire troubleshooting and I just go with what sticks without really memorizing what I did (so if I run into this issue again, I have to re-research).
Click to expand...
Click to collapse
Thanks! Finally Oden recognizes my phone
my amazing method
the same problem was with me 3-4 weeks ago...
follow the url-
dbloo dbloo dbloo dot autoroot dot chainfire dot eu
(i cant post the URL because the website is not allowing me.....understand and use the code)
1) choose your samsung model and download the recovery file
2) download and open odin on a dekstop
3) connect your device to the dekstop
4) press the volume down, home button and power button together till the screen changes
5) press the volume down button again
6) odin will show the message "attatched or connected"
7) click pda
8) attatch the file you downloaded
9) your device will be fixed and will be restarted
ur welcome
hai i am stuck at download mode with message as could not normal boot how to fix it