Related
Hello, been lurking a long time, reading a long time, but now it seems I need to reach out for help.
I have searched and read through many many posts and still cannot get my captivate to enter download mode. Ive read posts that say its unbrickable and others that say if its got a soft brick your toast.
Currently no matter what I do i am constantly stuck at the "phone---!---pc" screen.
Ive tried the vol+ and pwr, vol- and pwr, vol- and vol+ and pwr, middle vol button and pwr, all three vol buttons and power. Ive tried every variation of releasing and holding different buttons after a power cycle. Nothing seems to work.
Ive also tried making a jig. Ive got a micro usb plug ive chopped up, soldered on (3) 100k ohm resistors - no go. Tried (3) 100k and (1) 1k - no go. The value jumps between 295k ohms to 300k ohms. Does it need to be 301k exactly? That would require more than (3)100ks as they are usually +/-5%.
Backstory: was running stock, flashed to Cognition 3.02. Didn't have any issues with cog, just decided to try something different. Decided to go with Serendipity 4.1.
Used odin (I897UCJF6-final-OCD-REV0, the only one i could find, all the links are dead) to flash back to stock. Stock ran fine for the 10 minutes it was on there.
Then used the one click root
downloaded rom manager, used rom manager to add clockwork.
Used clockwork to enter recovery mode
installed from zip (serendipity 4.1) - this failed the first time and it took me quite a while to re-enter download mode.
After serendipity was flashed it would consistently lock up around the 2min mark.
Got back into download mode via clockwork/rom manager in attempt to use odin again. This is where it all fell apart. Odin froze the first time around, pulled battery, did the whole show again. Flash attempt #2 failed again also. This is where I am currently at. Now all ive got is the ----!---- screen and nothing seems to work.
Am I toasted? Or is there something I simply missed during my grief stricken panic after being without a phone for 2 days.
Search jig go to radio shack
Same recommendation as above poster.
Go to Radioshack, spend a $1 and get it done.
Did it just this morning.
http://www.youtube.com/watch?v=D0aoabVtPJ8
What build is your phone, located under battery, mine is 1008
Just got it working.
I had made several jigs earlier. Followed several youtube videos and still couldnt get it. I had to fine tune it to 301k ohms exactly. Required about 5 resistors. Using three 100k ohm resistors did not work...
(model 1008 also)
jhaury said:
Used odin (I897UCJF6-final-OCD-REV0, the only one i could find, all the links are dead) to flash back to stock. Stock ran fine for the 10 minutes it was on there.
Then used the one click root
downloaded rom manager, used rom manager to add clockwork.
Used clockwork to enter recovery mode
installed from zip (serendipity 4.1) - this failed the first time and it took me quite a while to re-enter download mode.
After serendipity was flashed it would consistently lock up around the 2min mark.
Got back into download mode via clockwork/rom manager in attempt to use odin again. This is where it all fell apart. Odin froze the first time around, pulled battery, did the whole show again. Flash attempt #2 failed again also. This is where I am currently at. Now all ive got is the ----!---- screen and nothing seems to work.
Click to expand...
Click to collapse
I had the same issue, if you used that version of odin and you have a 1012 version of the phone then that's what caused the issue. I am on xda app so I cannot look through my posts, but click on my name and look at the posts and you will find some in a thread about brinking and I told some details that might help.
Sent from my Samsung Captivate with ParagonRC3 using XDA App
So whats the best thing to do here?
Your saying I cannot use Odin to revert to stock, I must use froyo 2.2. any other 2.2 rom (or something more specific)?
Or is it something to do with Serendipity?
jhaury said:
So whats the best thing to do here?
Your saying I cannot use Odin to revert to stock, I must use froyo 2.2. any other 2.2 rom (or something more specific)?
Or is it something to do with Serendipity?
Click to expand...
Click to collapse
If you are build 1008 you should be able to use odin, try another rom
Easy
1. Pull battery out.
2. Put battery in.
3. Hold volume buttons.
4. Plug in the usb cable.
5. Done.
Jordan, that wont work if he is in a restart loop like I was. The only way to get it working is to make a jig with 3 100k watt resistors and jig pins 4 and 5. Once it is in download mode, flash to froyo if you have a 1010 or higher version phone (This can be found under the battery, my version is 1012). If you have an older version then you can flash back to stock. There is an odin flasher that will flash you to froyo, I will just have to look for it.
I personally use paragonrc3 myself and it works great. My issue was very similar to yours. Once you get it in dl mode, try out stock froyo and see if it works. If that does then you can most likely use any up to date ROM.
Sent from my Samsung Captivate with ParagonRC3 using XDA App
I was able to get into download mode, it had to be 301k exactly.
I tried it again and my phone does not like Serendipity 4. Serendipity hangs completely and every time around the 2 1/2min mark. I went back to Cognition.
Version 1008, originally the 3 buttons and the usb cable worked, then they didn't, and now they still don't. But I've got the jig now so eh.
okay guys here's my issue. I was flashing over to liberty and I forgot to wipe everything so as liberty was going through its stuff through bootstrap I pulled the battery hoping to stop the process.
HOWEVER, I am not stuck at the "liberty" logo. I have tried to sbf and I am getting....
failed flashing process: Phone (0000): Phone did not re-enumerate after RAM-downloader was sent. (0x703E) phone was disconnected.
Can someone please help me?
I've seen people have sucess with SBF errors by renaming the SBF file, trying a diff comp, and if ya vista or win7 ya have to be running as Admin. Give any of those a try that ya can while I'm looking over google to see if I can find anything more directly relevant to the errors you are getting.
Luckily I still have my x sitting around. I'm using macbook pro with vmware running windows 7. I have sbfed successfully on my x using the same setup.
Sent from my DROIDX using Tapatalk
I should also note that I tried booting into recovery and wiping data and cache still didn't help.
I do have a backup of stock from that I made. However, I just don't think its possible for me to access that backup to restore?
Sent from my DROIDX using Tapatalk
I'm not sure then. I've looked over quite a few different articles were people have had this problem, and have had it solved, and everytime it was some type of comp issue that was causing it. Some people fixed by changing USB ports, some by reinstalling the Moto RSD software (Also, with RSD, make sure you are using version 4.8 or 4.9), or using a completely different computer or OS. Past that the only other thing I can suggest is make sure you have the correct SBF file, and maybe try re-downloading it incase it somehow got corrupted during the download.
EDIT: Which recovery are you using? The stock recovery, or Clockwork? If ya using stock, then as far as I am aware you don't have the ability to backup/restore.
-Gilgamesh- said:
I'm not sure then. I've looked over quite a few different articles were people have had this problem, and have had it solved, and everytime it was some type of comp issue that was causing it. Some people fixed by changing USB ports, some by reinstalling the Moto RSD software (Also, with RSD, make sure you are using version 4.8 or 4.9), or using a completely different computer or OS. Past that the only other thing I can suggest is make sure you have the correct SBF file, and maybe try re-downloading it incase it somehow got corrupted during the download.
EDIT: Which recovery are you using? The stock recovery, or Clockwork? If ya using stock, then as far as I am aware you don't have the ability to backup/restore.
Click to expand...
Click to collapse
I am using rsd 4.9. I tried everything you stated except a new computer.
I have droid 2 bootstrapper installed and clockwork. However, whenever I boot into recovery it keeps bringing me to the stock one so I can't restore. If I can figure out how to restore maybe I would be good?
Sent from my DROIDX using Tapatalk
Likely you got far enough into SBF to erase clockwork. Though you can try pulling you battery during boot while its on the moto logo, and if clockwork is still installed it will then boot directly to it.
Yupp nothing. Stuck at the liberty boot logo where it says "liberty"
Sent from my DROIDX using Tapatalk
I donno then. I would try a diff comp and see if that helps. Or maybe someone else will see this thread and have some other ideas. You may could also try posting directly in the SBF thread, maybe someone with more experance with it will see it there? Just a thought.
Thanks for the help.
If anyone else can help I am all ears!
Sent from my DROIDX using Tapatalk
Ok, the bad news...
The first thing Liberty does when installing is format the /system directory. I dont know at what point you pulled the battery but, while you did at one time have bootstrapper and clockwork mod installed, you no longer do. Your only option at this point is to SBF.
I have had, as have others, lots of issues with getting it to go through on Windows 7. It will get to a point where it tries to switch modes (unfortunately I don't recall the name of that mode right now), then it wont find the driver fast enough and fail. If you can get that driver installed when it tries to switch modes, it should work, and cause no problems in the future. The problem for you though, may be even greater given that Windows 7 is bad enough and being run in VMware probably will just compound those issues.
If at all possible, try from a windows XP machine.
OK so im not sure about the Liberty ROM however I have had to SBF when I tried installing Fission 2.4.3 on my D2G.
My process was turning the phone on boot mode. This is done but holding the +- Volume button and then hitting the power button.
Next I got RSDLite 4.9 and lastest drivers from motorola. Next is restart computer! This was important as RSD wasn't finding my phone until I did. Once I restarted ran RSD hooked up the phone in boot mode found the sbf file and hit start. Took about 15 min to finish.
Not sure if this helps.
Rsd is finding my phone no problem right away. I suppose I should try it on a different computer though, one that's running xp.
Sent from my DROIDX using Tapatalk
buryboi said:
Ok, the bad news...
The first thing Liberty does when installing is format the /system directory. I dont know at what point you pulled the battery but, while you did at one time have bootstrapper and clockwork mod installed, you no longer do. Your only option at this point is to SBF.
I have had, as have others, lots of issues with getting it to go through on Windows 7. It will get to a point where it tries to switch modes (unfortunately I don't recall the name of that mode right now), then it wont find the driver fast enough and fail. If you can get that driver installed when it tries to switch modes, it should work, and cause no problems in the future. The problem for you though, may be even greater given that Windows 7 is bad enough and being run in VMware probably will just compound those issues.
If at all possible, try from a windows XP machine.
Click to expand...
Click to collapse
Do you know what driver your talking about or where to find it?
Okay guys I tried doing it on Windows XP and I am still getting the same exact message it wont' re-enumerate.
I am scared beyond belief right now and don't know what to do. If someone can suggest something I would really appreciate it.
Not sure if this helps, but this is what "my device" info says while in rsd lite...
IMEI/ESN/MEID:
N / A
Technology:
N / A
Software Version:
N / A
Flex Version:
N / A
Bootloader Version:
v0x00D011
DRM Version:
N / A
AP Die ID:
14b0001391953a0a0000d8ff0100
BP Die ID:
0000000000000000cd6932890485
AP Public ID:
6df40c77da38d6f01bc27cc2f40c041ee4491ae2
BP Public ID:
040000000500000002000000ffff0000ed153289
If you are on Win7 64 then try the drivers in the attached zip file.
It is the BP passthrough mode that fails at the end of the flash because it needs to load a separate interface to flash the baseband radio partition.
That interface is a Motorola Flash device MDM6600 and not the S-Flash OMAP3460 device.
If you are having trouble with the drivers loading during the flash cycle re enumeration then you can try this trick to get them to load.
Turn off the phone and then power on holding the Volume Up + Power.
The phone will boot to the M Logo and just stay there like it is hung.
It is now in BP passthrough mode and will enumerate as a Motorola MDM6600 flash device and Windows will attempt to load those drivers when you connect the USB cable. Point the New Hardware Found wizard to the folder where you extracted the zip and it should load them. If not, you may have to manually force it to load them in the Have Disk dialog.
Now pull the battery and reboot the phone normally and try flashing in RSD Lite again. You will already have the BP passthrough interface drivers loaded now and it should re enumerate and complete the flash of the baseband(CG5) and reboot the phone at the end. Wait at least a minute after it reboots for all the post boot initializations to complete and RSD Lite should eventually say Pass and allow you to disconnect without the error warning about damaging the attached device.
If none of this works, get an XP box and it will all work without any issues 99% of the time.
Good luck!
Okay... So I downloaded the drivers, connected via USB and it did show up as what you said it would. However, I then ran the sbf and it says "The Motorola AP flash interface could not be found and kept failing.
What do I do?
Also, another thing it now says my battery is low. If I just plug it into the wall, will it charge or do I need to USB it? I can't tell if its charging or not
nickb2005 said:
Also, another thing it now says my battery is low. If I just plug it into the wall, will it charge or do I need to USB it? I can't tell if its charging or not
Click to expand...
Click to collapse
It won't charge in the bootloader until you have software on your phone you need to use another D1 or D2 to charge. Or use an external charger.
If windows isn't working there are ways to flash in linux that usually yield better results.
Sent from my DROID2 using XDA App
Hello, i recently bought a xoom (wifi only) and now im in a quite frustrating situation.
When i got it first i flashed CWM recovery and rooted it successfully, it worked all fine for a few days.
yesterday i left the xoom on charger over night and today morning it was stuck on the red M logo saying "Dual Core Technology".
well, my situation is like:
- i can restart the xoom using power + volume up, but every time it stucks on the M logo again
- i can boot into RSD with volume up while starting
- i can boot into fastboot with volume down while starting
- i can NOT boot into recovery, when i try it gets stuck at "Reading ODM fuse: 1"
i reflashed the original ROM from MOTODEV, but the device still behaves the same like before..
normal boot gets stuck at the M logo, recovery gets stuck on Reading ODM fuse: 1, just fastboot working fine (unlocking & flashing works fine)
i also searched for similar problems on the forums, but any promising solution links to filesonic links wich are not working/down
any ideas what i can do now? any help is appreciated
thanks
unlock the bootloader and flash Rogue Recovery v1.3.0
then try to enter cwm
are u on stock? or customrom? and have u tried to lock the bootloader using a customrom? cauz locking the bootloader with customrom = not good
hi, thanks for your reply.
im on stock rom and my bootloader is unlocked. i did relock the bootloader once, but only after flashing the original ROM from MOTODEV to my device, now it is unlocked again.
i first flashed the CWM 3.2.0.0 wich is available as .img via fastboot, but it does not start (Stuck on "Reading ODM Fuse: 1").
now i flashed the recovery.img inside of Rogue Recovery 1.3.0 (since i read in the corresponding thread that it works also this way), but again: Stuck on "Reading ODM Fuse: 1"
Maybe u r 2 quick? Turn on your xoom - if u see the M wait 3 sec then press vol down and then vol up
But as i said wait 3 secs - if u r 2 quick it will stuck at entering recovery
okay, so you flashed a new recovery image (did you verify the images md5-sum?) and without trying to reboot into android you cannot get into recovery? That is really odd.
If so, I suspect that something has really screwed up your internal memory. You might be able to fix it using a factory cable.
Btw: after flashing the recovery image, does the xoom say that it succeeded in writing the recovery image to its memory?
There should be a command to reboot the device to recovery? A function reboot to recovery is possible on eos 1.0 maybe theres a adb or fastboot command 4 that?
llama-power said:
okay, so you flashed a new recovery image (did you verify the images md5-sum?) and without trying to reboot into android you cannot get into recovery? That is really odd.
If so, I suspect that something has really screwed up your internal memory. You might be able to fix it using a factory cable.
Btw: after flashing the recovery image, does the xoom say that it succeeded in writing the recovery image to its memory?
Click to expand...
Click to collapse
after flashing the recovery, i can read
"Flashing StorMgr partition recovery STATUS: done!" on the xoom
the recovery image is fine, and until today i was able to boot into CWM 3.2.0.0
what is the thing with the factory cable?
about the factory cable: seems to be a modified usb-cable with two terminals on the micro-usb end being connected with each other. As far as I read, it should enable you to write to the xooms memory as long as the hardware is still okay, no matter how much you f***ed up your software I haven't had to use yet, though.
@what Unholy said: sure, adb reboot recovery will boot your xoom into recovery, but only if you have a working android running and usb-debugging enabled.
Reading ODM Fuse: 1, according to my information, means that the thing is trying to boot into recovery. Why nothing else shows up: I have no clue.
here is a thread where some us-users had a similar problem. They tried to root their xoom after getting the 4g-upgrade and ended up with the red M-Logo. After some screwing around, they even managed to wreck the fastboot-mode, thus only enabling rsd access. So no help on that side.
What especially bothers me about your problem is that it just appeared on its own. Right before your xoom showed its issues, you weren't flashing anything. Just charging shouldn't cause any of this.
I am beginning to suspect a hardware failure that can naturally be only fixed by motorola. But that's only my current opinion.
If I was you, I would try downloading the files from motorola again, check their md5-sums and then flash those using fastboot using these instructions.
If that still doesn't help, there may be a way to get a .sbf file from motorola for your xoom. That is a file which can be flashed using the windows software rsd-lite, but I haven't used that in a long time and it has been reported to not work really well with the xoom.
Next, I'd research a little on the factory cable thing, but I'd be careful with that.
As a last resort, I'd send the xoom to my dealer. Unluckily, there is a way to determine if you have had your bootloader unlocked, at least as long as fastboot is still working...
About the factory cable - with that cable u can flash your xoom if nothing else is working anymore (adb or cwm)
To build a factory cable u have to tie pin 1 (+) to pin 4 on the micro usb plug
I build one but never used it and hope i will never have to
i did download the original ROM from motodev again, checked the md5, and flashed according to the tutorial posted by llama-power, but the device still wont boot neither the rom nor into recovery.
since its now on 15% battery i think i will let it run out of power and then try to boot again...
The_Revenge said:
i did download the original ROM from motodev again, checked the md5, and flashed according to the tutorial posted by llama-power, but the device still wont boot neither the rom nor into recovery.
since its now on 15% battery i think i will let it run out of power and then try to boot again...
Click to expand...
Click to collapse
does the xoom charge when connected to ac power? I know that other devices (cellphones) wouldn't charge without working os.
However, I do not think that letting the battery run low will help you. Lithium ion batteries should not be low discharged as that will most likely destroy them and lead to a massive risk of explosion upon the next charge. Because of that, devices powered by a lithium ion battery will power down before depleting the battery, the xooms mainboard itself will most likely still be supplied with some power.
If you really want to cut the power supply to the mainboard, you'll have to open the xoom (two screws) and unplug the battery (the connector is held down by another two screws) for a couple of seconds. (here is a teardown of the xoom with pictures)
by the way, if you want to track your battery status without booting android (as that would obviously not work), you can use fastboot getvar battery-status.
well my xoom actually charges when i connect it to power, and the LED also lights up, so (thinking of what you said) it seems like the os and everything still is present, just like the bootloader cant load it or something?! is there maybe any way to update the bootloader itself?
yeah, i can also check the battery status when i'm booting with power and volume up (RSD) =)
well i'm actually thinking about disconnecting the battery, but i'm a bit unsure, i will study that now..
The_Revenge said:
well my xoom actually charges when i connect it to power, and the LED also lights up, so (thinking of what you said) it seems like the os and everything still is present, just like the bootloader cant load it or something?!
Click to expand...
Click to collapse
not neccessarily. Maybe the xoom just doesn't need any software to charge the battery.
The_Revenge said:
is there maybe any way to update the bootloader itself?
Click to expand...
Click to collapse
don't know, but since fastboot works I suspect that the bootloader itself is still fine.
The_Revenge said:
well i'm actually thinking about disconnecting the battery, but i'm a bit unsure, i will study that now..
Click to expand...
Click to collapse
have fun, but I wouldn't get my hopes up too high. I still suspect some sort of a hardware failure... Also, opening the device might leave some traces (botched screws, etc) that could lead motorola to say that you messed with your xoom if you should finally decide to send it in
well thats the same i thought about opening the device..
do you know any way to dump the partitions to the pc (maybe with fastboot?)
The_Revenge said:
do you know any way to dump the partitions to the pc (maybe with fastboot?)
Click to expand...
Click to collapse
nope, not without a working recovery.
fastboot erase partition_name should be able to clear your partitions, though. Replace partition_name with boot, system, userdata, cache or recovery
http://www.xoomforums.com/forum/xoo...ery-stuck-red-m-logo-fastboot-works-help.html
apparently that user seems to have had the same problem, he says he fixed it using 1.35 Everest Bootloader (SBF).
i also had that idea some time earlier and found a thread with the SBF files here on xda, also for the wifi model, but the only links i could find to SBF files were filesonic links wich are not working ._.
i'm now up to googling for SBF files (for the wifi only model), if i cant find anything promising i'll send it back tomorrow.
btw, erasing the partitions does not help, i've already tried that
Have u done the lte update?
UnholyX said:
Have u done the lte update?
Click to expand...
Click to collapse
he's got an wifi-only model (as stated in post #1) and is from germany (at least that's what his location and flag says). LTE upgrade is neither available in germany, nor for wifi-only-xooms. So I'd say no
@OP: that sounds quite promising. .sbf-files still seem to be available on some sites, downloading one for my xoom right now, just in case that site goes down in the future...
Yes he got the wifi version like me but something must happened ,-)
I also charge my xoom and nothing happens. He got wifi version but he maybe flashed a false update or so
There r people flashing stingray instead of the wingray version etc. - just asking what happened before - thats the reason - something must happened before ;-)
it seemed promising, but i cannot find any usable sbf file
i think i'll send the unit back tomorrow
I flashed an unofficial cm 10.1 port for the razr v on slot 1 in BMM without making a nandroid backup (stupid, I know) on JB 4.1 with a locked boot loader and it wouldn't boot into CM. I wiped cache and data and it still didn't work. I tried flashing other Roms in slot 3, didn't work. I erased the CID without backing it up (bad mistake after bad mistake:crying as well. Then I had it connected to rsd lite and tried to flash an ICS SBF which obviously didn't work(failed check or something, no flashing occurred) and I exited the program even though it warned me that it would mess something up. Now I get an error and can't even get to the recovery anymore. And the battery has died (non-removable). Now I was thinking I should flash the JB 4.1 Chinese SBF for this phone but I would need a motorola factory cable. What should I do? ( Ik I posted this before, but no one has replied).
Leafs99 said:
I flashed an unofficial cm 10.1 port for the razr v on slot 1 in BMM without making a nandroid backup (stupid, I know) on JB 4.1 with a locked boot loader and it wouldn't boot into CM. I wiped cache and data and it still didn't work. I tried flashing other Roms in slot 3, didn't work. I erased the CID without backing it up (bad mistake after bad mistake:crying as well. Then I had it connected to rsd lite and tried to flash an ICS SBF which obviously didn't work(failed check or something, no flashing occurred) and I exited the program even though it warned me that it would mess something up. Now I get an error and can't even get to the recovery anymore. And the battery has died (non-removable). Now I was thinking I should flash the JB 4.1 Chinese SBF for this phone but I would need a motorola factory cable. What should I do? ( Ik I posted this before, but no one has replied).
Click to expand...
Click to collapse
Sorry for late answer. But, yes you'll need Motorola factory cable to bypass battery check.
1. You'll need to reflash stock JB with RSD.
2. Then reboot your phone (screen turns black) you'll need to press both vol buttons, bootmenu will appear.
3. Then with voldown choose bp tool & select it with volup. You'll boot to android.
4. Then you'll need to root your phone with Razr rooting stuff.
5. Then rooting program reboot your phone (screen turns black) you'll need press both vol buttons & choose with vol down bp tools & select with vol up.
6. Then you'll be rooted install Boot Menu Manager from Play Store. BMM have 2ndinit so you wont need to start phone with BP tool anymore.
To try fix CustomerID error completely you should refer to this post - http://forum.xda-developers.com/showthread.php?t=2406867
Actually, battery IS removable, albeit u'll need a very smalle torx screwdriver (m4 or m5 if my memory is correct). But that still won't do much good since even if it's out, there no easy way to recharge it. Although if you have a scrap battery just to get the connector and have some soldering skills, you can redneck up yourself some AA batteries in a project battery holder and solder the leads to the scrapped battery's connector to at least pass the batt check. As for the softbrick though, i'm used to motorola phones yet, i've mostly fiddled with soft and hard bricked samsungs and my own LG optimus g E971, so i might not be much help on that side YET. But i DO have a razr xt885 here that belonged to a friend of mine which had the great idea of trying to fit his microSIM in there cause he was too eager to get the phone started and didn't wanna wait for me to have time to check everything out and unlock the carrier on the phone so he could use it... So now the SIM holder on the board is dead cause he ripped out the metal contacts trying to pull out his microSIM from there........ Phone still turns on though and software has not been modified in any way and everything works except for the SIM holder, so if you need backups or files from a working model, i can definetly help you there. Only thing i don't have anymore is the stock USB wire cause that one got hacked up later on to be used as a USB jig... but the battery and software are all good and i have plenty of microUSB wires to connect phones here. Plus i also live in the province just east of you So it's still a few hours drive but if all else fails and you feel like a roadtrip to Quebec, i'd be happy to help in any way possible Just let me know if you need anything
I'm stumped with this issue of my Motorola Razr HD LTE XT925 Rogers version 4.1.2 being in a boot loop. It started when I did a factory reset to try and fix some camera issues that I was having it started up with the Motorola red M icon then went to proceed with the factory reset with the android icon with the spinning blue object then restarts and just does a loop I have tried some steps that I found that I will list but all are unsuccessful and I did try them several times. It is stock firmware but was rooted with one click rooting program can't remember the name I did nothing else to the firmware.
Power + volume down for 10 seconds (simulates a battery pull)
Stock recovery tried wiping data and cache and then rebooting
Tried to use the boot menu normal start up and factory options
I did however get it to boot to the Rogers logo screen once but it just froze and had to restart it
I am currently trying get ADB tool to installed and get it working to see my phone as well as RDS Lite 6.1.6 it wont show any info about the phone but when in fastboot mode RDS Lite see it as connected in fastboot but no info about the phone shows up in the top left box as it has shown before also tried Super ADB Tool it show nothing at all I will continue to try and get the tools working.
Any help in getting the phone to boot normally is greatly appreciated.
I was also wondering if any body knows a good way to completely wipe the razr XT925 and restore the stock firmware that would also help.
OK so I have ADB installed and working I think put my XT925 in fast boot mode then I put in code adb devices in to the windows command console but show nothing listed and my phone says it is in fastboot mode and usb is connected and windows sees it as well but not ADB. There is no errors ether I am so confused as to why ADB and RSD show no info about my phone? I will see if its any of my drivers that are missing.
I went ahead and tried to flash my phone with RSD lite 6.1.6 with no luck the boot loop is preventing it from proceeding with the flash is this just a lost cause and there is no fix for it. The only thing I can think of is that I have to unlock the boot loader is that even an option when I can't even get boot into android? Any one got any ideas?
I was messing a round with my phone and try to get it working with any of the tools and had turned of the phone to stop it from constantly showing the red M icon and the android icon with the blue spinning object over and over but still had the phone plugged in to the computer and was looking in device manger in windows and seen this QHUSB_DLOAD with no drivers for it and looked at the VID & PID ids (USB\VID_05C6&PID_9008
) and searched for drivers thinking that is what is missing for my phone as I have never see it before and it is Qualcomm modem flashing port I don't know what to do did really mess up my phone by just doing a factory restore?
Some help or clarification would help a lot now as it is a bit troubling that I am unable to fix the Motorola Razr XT925 and might be bricked just by doing a factory restore. :silly:
OK I am getting desperate here I will do anything to stop it from looping I have even tried house of motos way just the same thing still if I can stop it from looping I can get it to work but does anyone knows a way to wipe the phone completely or stop it from this infuriating loop???
Just as a side note I found that forcing it in to normal start up with the wall charger plugged in it will charge when done then it will show the rogers logo like its booting but does nothing.
I have searched the forms and google now for 2 days about any way to fix the boot loop but all just say to do things that I have tried many different ways many times and the tools don't work or will work like RDS but it is unable to continue do to the loop of it doing a factory restore then restarts.
If any body has any ideas at all or can at least point me in the right direction would be a life saver I will even jtag the phone if i have to, if even that's possible
Have you booted into fastboot mode?
Have tried to rsd to stock from fastboot?
Darbness said:
Have you booted into fastboot mode?
Have tried to rsd to stock from fastboot?
Click to expand...
Click to collapse
Thanks for the reply, I have gone into fastboot mode and used RSD to try and flash the stock rom but when it restarts the phone its unable to countiue becuse it is uable to get past the bootloop
If your phone is bootloader locked you can always take it back to the carrier, that's it if you have guarantee. I suggest you try a earlier version of RSD lite, 6.1.4 for example, and see how it goes.
Sent from my RAZR HD using xda app-developers app
Hydr0id said:
If your phone is bootloader locked you can always take it back to the carrier, that's it if you have guarantee. I suggest you try a earlier version of RSD lite, 6.1.4 for example, and see how it goes.
Sent from my RAZR HD using xda app-developers app
Click to expand...
Click to collapse
OK, not able to take it to Rogers some issues with doing that but will try RSD lite 6.1.4 besides that no other ways?
I had the same issue yesterday. Received a phone call and my phone shut off and started looping on the red M logo, but no further. I did everything in my power to get RSD Lite and ADB to recognize my phone in fastboot mode. Nothing. Then, I moved the USB port to another port on my laptop, and viola, RSD Lite picked it up, but ADB never did. Using the stock firmware available for my 926, I was able to revert back to the latest version of JB for my phone. I did also have to run RSD Lite in *administrator mode* in order to get success. Hope any of these tips helps you out.
Also, even though I was successful in flashing, I was still in loop mode until... I had to wait for the battery to die and the phone to shut all the way off. Then after powering up, it came up. I tried the volume down + power key, but it would only reset the phone, it would not completely power it off like it needed. This is not something I have seen on any forum anywhere, so hopefully it helps.
xaneth said:
I had the same issue yesterday. Received a phone call and my phone shut off and started looping on the red M logo, but no further. I did everything in my power to get RSD Lite and ADB to recognize my phone in fastboot mode. Nothing. Then, I moved the USB port to another port on my laptop, and viola, RSD Lite picked it up, but ADB never did. Using the stock firmware available for my 926, I was able to revert back to the latest version of JB for my phone. I did also have to run RSD Lite in *administrator mode* in order to get success. Hope any of these tips helps you out.
Also, even though I was successful in flashing, I was still in loop mode until... I had to wait for the battery to die and the phone to shut all the way off. Then after powering up, it came up. I tried the volume down + power key, but it would only reset the phone, it would not completely power it off like it needed. This is not something I have seen on any forum anywhere, so hopefully it helps.
Click to expand...
Click to collapse
Thanks for the reply, I was thinking along the same lines as that but trying it on a freshly installed windows plus on different computer and just have RSD lite 6.0 and my Motorola drivers for my phone installed. I was thinking that it was my current motherboard that has a Intel usb 3.0 controller on it and my old motherboard did not as I manually updated my phone from 4.0.4 to 4.1.2 before on my old motherboard and had no issues and will fallow the instructions to the letter and will triple check as well. I will see how this goes and hope it works as its my last option to get it working.
OK so trying to reflash the phone from a different computer with a fresh install of windows buy did not work.
I was looking though the options in the android system recovery menu and two options stood out are:
apply update from external storage
and
apply update from ADB (wont work as ADB does not see the phone)
would doing an update with an SD card with the firmware on it work or is it for some other purpose?
osalot said:
OK so trying to reflash the phone from a different computer with a fresh install of windows buy did not work.
I was looking though the options in the android system recovery menu and two options stood out are:
apply update from external storage
and
apply update from ADB (wont work as ADB does not see the phone)
would doing an update with an SD card with the firmware on it work or is it for some other purpose?
Click to expand...
Click to collapse
I'm not sure, never flashed that way. If it isn't too much to ask, can you tell me the process you are following to flash the stock rom step by step?, to see if I can somehow help you out, it's really odd It doesn't work.
Sent from my RAZR HD using Tapatalk
Hydr0id said:
I'm not sure, never flashed that way. If it isn't too much to ask, can you tell me the process you are following to flash the stock rom step by step?, to see if I can somehow help you out, it's really odd It doesn't work.
Sent from my RAZR HD using Tapatalk
Click to expand...
Click to collapse
Thanks for the reply, The steps I take to flash my phone is to first put my phone in to fast boot mode then connect my phone to the back of my pc then start up RSD Lite and add the latest firmware for my XT925 in RSD then let it load the firmware and it restarts the phone. it starts up to the non animated red M icon then the android with the spinning blue object in its chest comes up but then shuts off and restarts and have left it for several hours until it died and had to recharge it up.If I can I will post a video of how I flash it and what the phone does.
also is it normal for RSD Lite not to show the imei number of the phone or any thing about it in the top left box (Device properties) when you click on the modal?, all I get is N/A in Device properties box.
Yes, that is completely normal, that only appears when the flash is succesful and you get past the "select language" screen, but seeing that you're stuck in the M logo means that you haven't got there yet, in the mean time it will still appear no imei and no info.
Sent from my RAZR HD using xda app-developers app
---------- Post added at 04:08 PM ---------- Previous post was at 04:01 PM ----------
Here, try this: http://www.android.gs/unroot-droid-razr-hd-xt926-downgrade-stock-firmware/
The RSD process following the exact same instructions found there on a Windows with USB 2.0, and it is preferred you use RSD 6.1.4 (if you don't have it I can post it here if you want)
Your build to flash is found here: http://sbf.droid-developers.org/
Search for the one the phone brought when it was just bought, it has to be from your carrier.
Btw: did the flashing gives you any errors at all or not? Also, do you have bootloader unlocked? Just some details I'm curious, but seeing your phone does finish the process and restarts means it probably doesn't get any errors, anyway I'm just curious.
Sent from my RAZR HD using xda app-developers app
Hydr0id said:
Yes, that is completely normal, that only appears when the flash is succesful and you get past the "select language" screen, but seeing that you're stuck in the M logo means that you haven't got there yet, in the mean time it will still appear no imei and no info.
Sent from my RAZR HD using xda app-developers app
---------- Post added at 04:08 PM ---------- Previous post was at 04:01 PM ----------
Here, try this: http://www.android.gs/unroot-droid-razr-hd-xt926-downgrade-stock-firmware/
The RSD process following the exact same instructions found there on a Windows with USB 2.0, and it is preferred you use RSD 6.1.4 (if you don't have it I can post it here if you want)
Your build to flash is found here: http://sbf.droid-developers.org/
Search for the one the phone brought when it was just bought, it has to be from your carrier.
Btw: did the flashing gives you any errors at all or not? Also, do you have bootloader unlocked? Just some details I'm curious, but seeing your phone does finish the process and restarts means it probably doesn't get any errors, anyway I'm just curious.
Sent from my RAZR HD using xda app-developers app
Click to expand...
Click to collapse
thanks for the reply, I have just tried the the steps in the link you provided and I used RSD lite 6.1.4 and got the 4.0.4 Rogers firmware for my XT925 that it originally came with and waited an hour but just did the same thing, I don't get any errors when flashing although RSD displays to start the phone up manually and I have a locked boot loader (Device is LOCKED: Status Code: 0) I can how ever get it to go to the animated red M icon and then the rogers logo by selecting normal power up from the boot menu but doesn't boot in to android.
osalot said:
I was also wondering if any body knows a good way to completely wipe the razr XT925 and restore the stock firmware that would also help.
Click to expand...
Click to collapse
http://theunlockr.com/2012/01/24/how-to-restore-the-motorola-droid-razr-using-fastboot-files/
Ok, so I think I maybe doing something incorrectly so I will put all the steps I did to reflash my phone and will add some pics and a video if possible.It took me a few days to get another phone to use for vids and pics the phone I used to for video and pics Samsung Captivate, unbrickable ya can't kill it.
1. I have installed RSD Lite 6.1.4
2. Installed the latest Motorola drivers by down loading the Motorola Device Manager
3. Down loaded the firmware for my phone android 4.1.2 full file name ---> 9.8.2Q-8-XT925_VQL-12.2_CANADA_VANQJBLTEFRCI_P004_CFC_fb.xml.zip
4. Put my phone in fast boot mode then connected my phone to my netbook on the side or on the back usb 2.0 port on the PC with the original Motorola usb phone cable tried both to be sure
5. Started up RSD Lite 6.1.4 and load the firmware and selected Decompress only
6. Checked RSD Lite to make sure my phone is connected and showing up and RSD Lite shows (Fastboot VQUISH_U S USB N/A Connected)
7. I then selected start button on RSD Lite and it flashed the firmware with out issues or errors
8. phone restarts fine from fastboot left it for 1:30 RSD displays to reboot the phone manually but the phone does not do anything else but reboot constantly left the phone doing that until it ran out of battery
Pic of XT925 in fastboot mode not connected
Pic of RSD with phone connected in fastboot mode ready to be flashed
Video of phone restarting after being flashed and looping (click the link below)
http://s1295.photobucket.com/user/Osalot-Ruin/media/RSDandphonevideoCapture_zpsff85211b.mp4.html
Pic of RSD after leaving the phone for 1 hour and 30 minutes
In the steps I don't see the XML file editing, did you deleted the getvar line in the XML file?
Sent from my RAZR HD using XDA Free mobile app