Ok I think I really screwed up here
I tried to upgrade the Kernal and now all I get is
Bootloader
30.03
err:a5, blablalba
Battery Ok
Ok to Program
Transfer Mode
usb
Help please
You're going to have to SBF. Same thing happened to me a couple of weeks ago
when installing the wrong ZIP on the wrong update.
I would use the 2.3.320 file from MyDroidWorld. The .340 sbf that is available is system only and may not solve your problem.
I have been reading and reading, i understand what I have to do.
But my problem is my computer will not install the drivers. I've search, search and search, downloaded like three different files I've found from other forms, even went to the motorola page to download the drivers. I will not find the drivers.
eagle20g said:
I have been reading and reading, i understand what I have to do.
But my problem is my computer will not install the drivers. I've search, search and search, downloaded like three different files I've found from other forms, even went to the motorola page to download the drivers. I will not find the drivers.
Click to expand...
Click to collapse
So you've already connected your device and tried to SBF on RSD lite already?
If so, it's not loading?
What OS are you running? I've read a lot of people having issues on Win7 computers. I've only done it on XP because I heard several people say that RSD Lite is much easier with XP.
Edit
I just installed on my Win7 Computer and when I put my phone into bootloader mode and connected it showed right up. I used the rsd lite and drivers from here when I set up ADB.
No at first I couldn't get the driver to install but I was downloading the wrong drivers.
Ok I got RST lite installed, connected properly to the phone, Install the .sfb and its failing!!!
pjsockett said:
What OS are you running? I've read a lot of people having issues on Win7 computers. I've only done it on XP because I heard several people say that RSD Lite is much easier with XP.
Edit
I just installed on my Win7 Computer and when I put my phone into bootloader mode and connected it showed right up. I used the rsd lite and drivers from here when I set up ADB.
Click to expand...
Click to collapse
I'm gonna download the .sfb file frome here and see what that one does. Thanks
did you unzip the SBF file ??
You have to for the program to reconize it
well this is nice. It fails again, but this time the phone changes screen and says critical error:
febe
0047
:/ ooppss. I downloaded the droid 2 file. eeee
Everything is back up and running.
Quick question, How do you guys like the camera on this phone? I've noticed mine to be very "pixie" like on the screen of the camera. I'm sending a photo to see how it looks like on the computer but it doesn't look very good!
eagle20g said:
Everything is back up and running.
Quick question, How do you guys like the camera on this phone? I've noticed mine to be very "pixie" like on the screen of the camera. I'm sending a photo to see how it looks like on the computer but it doesn't look very good!
Click to expand...
Click to collapse
I've noticed the camera issue too. It looks kind of grainy when taking a pic as compared to when it's stock. But the pics come out fine.
Sent from my DROIDX using XDA App
eagle20g said:
well this is nice. It fails again, but this time the phone changes screen and says critical error:
febe
0047
Click to expand...
Click to collapse
I had the same error. A couple things to try. 1. Make sure you are not putting phone in dock, just hook it straight to phone. 2. For me RSD Lite will only recognize files on the desktop and only if they have a (1) at the end of the file name. You can check a thread I started titled Trouble with all roms. Hope it helps.
Sent from my DROIDX using XDA App
willjohnson said:
I had the same error. A couple things to try. 1. Make sure you are not putting phone in dock, just hook it straight to phone. 2. For me RSD Lite will only recognize files on the desktop and only if they have a (1) at the end of the file name. You can check a thread I started titled Trouble with all roms. Hope it helps.
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
No the error was because I downloaded the wrong file. All is back to stock now. I haven't found a single rom that's worth daily cutie to me so im just gonna keep this baby stock for now
Ive noticed a change in quality for picture in stock rom, but still the camera really disappointed me, takes fantastic close up, but like a geranal distance picture is grainy n just horrible. Video is just as bad but I haven't check the quality on the computer but not what I was expecting
eagle20g said:
No the error was because I downloaded the wrong file. All is back to stock now. I haven't found a single rom that's worth daily cutie to me so im just gonna keep this baby stock for now
Good. Glad you got it working. Didn't see the post about the wrong file. The things I listed may just be quirks from my pc or whatnot.
Ive noticed a change in quality for picture in stock rom, but still the camera really disappointed me, takes fantastic close up, but like a geranal distance picture is grainy n just horrible. Video is just as bad but I haven't check the quality on the computer but not what I was expecting
Click to expand...
Click to collapse
Sent from my DROIDX using XDA App
eagle20g said:
I haven't found a single rom that's worth daily cutie to me so im just gonna keep this baby stock for now
Click to expand...
Click to collapse
Try DarkSlide V4.1 I'm using it now & love it...Tried UD, but since it's still an RC, I didn't want to stay with it. Tried TranQ360 had issues with that as well but to it's credit, I installed it over DarkSlide (which they say is OK, but I'm going to re-try as a clean install). Darkslide can be found at mydroidworld.com
RKramden said:
Try DarkSlide V4.1 I'm using it now & love it...Tried UD, but since it's still an RC, I didn't want to stay with it. Tried TranQ360 had issues with that as well but to it's credit, I installed it over DarkSlide (which they say is OK, but I'm going to re-try as a clean install). Darkslide can be found at mydroidworld.com
Click to expand...
Click to collapse
+1 for darkslide. Definetly daily driver capable. Good eye candy too. They just released update couple of days ago. New black market skin and some even better eye candy in update too.
Sent from my DROIDX using XDA App
Related
Probably another stupid error on my part, but my Android keyboard has disappeared. Apparently I am one of only a few that doesn't like the Swype keyboard.
So I rooted my phone, and also am running LauncherPro. It wasn't until I installed LP that I discovered that my Android keyboard disappeared. When I long hold in a text input box, the keyboard prompt comes up.....but Swype is the only selectable option.
Fwiw, I hadn't touched any apps at all after rooting......when I noticed this. Shortly after, I started disabling some apps (never deleted any)....by changing the file names from APK to BAK. I wonder if maybe I just didn't notice until later.....and possibly have disabled whatever file the Android keyboard is in?
Suggestions? Fwiw, when I go to Setting>keyboards......Swype is the only thing there as well. I have also uninstalled LP and reinstalled, for ****s and giggles.
Help!!!! I hate Swype!!!
Thanks to anyone that gives this a shot.
I'm in the same boat. Also tried flashing from rom manager, with no success. Running dj05/.9 superclean/stupidfast 1.54.
Sent from my SCH-I500 using XDA App
You can reload the Rom if it was there to begin with.
Also, why rename BAK?
In the original thread of rooting over at androidcentral it was recommended to rename them with a .old at the end and not change the APK. This way the file stays but no longer shows in the dock.
Also, if you have the files on your computer to restore your phone you can just nuke the stuff you don't want as long as it doesn't have a necessary purpose for the OS.
I am still new to the hacking stuff. I am halfway wondering if I lost my Android keyboard when I rooted. I followed the AndroidCentral thread for the one click root....and was successful. Fwiw, I cannot successfully install ROM manager either.....so I couldn't fix an earlier problem by running my backup from Clockwork.
Should I remove the root, and install another? Again, I am green to all of this stuff.....so the easier stuff is worded or instructions are given, the better. I guess I'm old.
http://forum.xda-developers.com/showthread.php?t=803682
Use the zip 1.5.5
Read the thread and follow the instructions. Piece of cake to get your root access back.
bwheelies said:
http://forum.xda-developers.com/showthread.php?t=803682
Use the zip 1.5.5
Read the thread and follow the instructions. Piece of cake to get your root access back.
Click to expand...
Click to collapse
I have Windows XP.....
As do I....regarding XP. There instructions for XP.
Do you have superuser? If not, grab it from the market. Also use ODIN and install CWMRecovery.
Sent from my SCH-I500 using XDA App
bwheelies said:
Do you have superuser? If not, grab it from the market. Also use ODIN and install CWMRecovery.
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
U do. I have ODIN as well, but can't get my computer to connect in ODIN to the cell phone. I have installed the correct drivers, but it won't work for the life of me.
LXative said:
U do. I have ODIN as well, but can't get my computer to connect in ODIN to the cell phone. I have installed the correct drivers, but it won't work for the life of me.
Click to expand...
Click to collapse
Remove your battery, hold the volume down button and plug in while still holding the button down. The screen should come up with a yellow android guy and ODIN should show "COM" something or another in the top left box. This is how you get in to Download.
Can never go wrong with digging up old eclair threads.
good day. using xda premium.
I certainly would have waited 6 months for someone to answer my post ::chokes, clears throat::
Oops, I did it again - dug the Eclair thread up yet again
Another Fascinating post by my XDA app...
Have done done searching, but still can't get my phone to connect to my computer. I've tried everything that I've found posted. Doesn't mean I found then all.
I get "usb device not recognized" when I plug on my phone. I'm trying to flash the modem to get my text messaging to work. Windows 7 64bit
DL30 black hole 4.1
Any help would be appreciated.
Sent from my SCH-I500 using XDA App
As most people would say, wrong place. This is a question that belongs in the general section.
Did you install the samsung driver onto your computer?
Kaze105 said:
As most people would say, wrong place. This is a question that belongs in the general section.
Did you install the samsung driver onto your computer?
Click to expand...
Click to collapse
Sorry about that.
Yes divers have been installed a long time. I used to be able to connect. Then about a month ago it decided to stop. I even tried it on a XP system, same thing.
Sent from my SCH-I500 using XDA App
Have you tried using a different USB cable?
mob87 said:
Have you tried using a different USB cable?
Click to expand...
Click to collapse
Yes. Tried my wifes. Tried one from my BB. Tried de-bugging mode. Tried rebooting while connected. Lol
Sent from my SCH-I500 using XDA App
Did you try a different USB port?
Also I would suggest updating to EB01 since DL30 isn't supported by devs and is a less stable Froyo build. Uninstall the Samsung drivers, reboot, reinstall and try it again.
Mine quit working today....i disabled usb debug then did a battery pull. Rebooted..enabled usb all is well...
Sent from my Froyo Fascinate.
I've had this issue and have tracked it down to my BT dongle. Every time I use it on my win 7 64bit box I have to uninstall the Samsung drivers, then reinstall without the phone or the BT dongle plugged in.
Thanks for all the input. It finally started working. I installed another rom and kernel. But now I can't get odin to recognize the phone in download mode. Weird stuff....
Sent from my SCH-I500 using XDA App
ragarm said:
Thanks for all the input. It finally started working. I installed another rom and kernel. But now I can't get odin to recognize the phone in download mode. Weird stuff....
Click to expand...
Click to collapse
I just ran into this myslef, and I believe the Fascinate has a bit of a multiple personality disorder. When I went through the Windows registry, I found entries listing the phone as a phone, as removable storage, as a SD card reader and as a CD drive. Nothing worked - no matter what I did, Windows wouldn't recognize it as anything.
To solve it, I had to uninstall the Samsung drivers and then search through the registry, removing anything that said Samsung. A bunch of keys gave me permission errors, but after finally removing them all, I connected the phone and it was immediately recognized as an Android Device. I reloaded the Samsung drivers and everything is back to normal.
A major PITA, but I'm just glad there was a solution.
If you want to try to do the same, uninstall the Samsung drivers, open regedit and search for Samsung. Delete any key that says Samsung (assuming you don't have any other Samsung peripherals). Hopefully you won't run into the permissions problems, but if you do, let me know and I'll walk you through how to get past them.
ChrisDDD, thank you. I will try that asap. That is some great information. I will report back my findings after I'm finished.
Sent from my SCH-I500 using XDA App
Well finally got around do working on this. And YES it worked. At least on my XP machine. Got some permission problems on my win 7 machine.
Chris, thanks for that bit of info. Only thing I had to do different than most was to reboot my phone in download from the menu that is installed with my kernel. I couldn't get it to work by pulling the batt and hooking up to pc. Funny stuff trying to get this stuff to work.
So I was told to install the deodexed [sp] of the GB leak, so I did on top of my rooted, non deodexed version, without wiping. After this I wiped my data a few times, as I heard it would be best to do. Well, after doing so... my phone won't stop bootlooping. I can't access the bootstrapped bootloader, only the stock Moterola one, and I cleared my data with it hoping it would work too...
Help please? How do I "sbf" back to stock or whatever?
Yeah, I don't think it was possible to go from orginial GB leak straight to the rooted one.
You will need RSDLite 4.8 or higher and 2.3.340 sbf file. Both should be easily findable with a Google search. Follow SBF instructions from there.
I hope its ok to post this link here:
http://www.droidxforums.com/forum/droid-x-rs-guides/12015-complete-droid-x-sbf-flashing-guide.html
I did everything it told me to in that guide, but the spf got to 99% and said it failed. Now my phone says "code corrupt" on the bootloader screen fml
tried flashing it again, same thing happened. It failed at "switching phone to BP pass through" apparently. help me please
thewanton said:
I did everything it told me to in that guide, but the spf got to 99% and said it failed. Now my phone says "code corrupt" on the bootloader screen fml
Click to expand...
Click to collapse
Now just do the system only sbf.it will work
Sent from my DROIDX using XDA App
Do you have the latest drivers installed? Try using RSDlite 4.9!
thewanton said:
I did everything it told me to in that guide, but the spf got to 99% and said it failed. Now my phone says "code corrupt" on the bootloader screen fml
Click to expand...
Click to collapse
Samething happen to me......I didn't want to try and fix it I know I was able to,but i called Verizon and got a new phone the next day
z06mike said:
Do you have the latest drivers installed? Try using RSDlite 4.9!
Click to expand...
Click to collapse
i found rsdlite 4.9 didnt recognize my phone but 4.8 did
itzjen said:
Samething happen to me......I didn't want to try and fix it I know I was able to,but i called Verizon and got a new phone the next day
Click to expand...
Click to collapse
Like what did you say to them?
tyvallely said:
Like what did you say to them?
Click to expand...
Click to collapse
this is totally being lazy AND the reason why everyone is raising their prices on insurance and why ppl like motorola are locking bootloaders. if it is too much or you're too lazy to do it. dont do it in the first place. sbf isnt hard there are a gazillion guides to sbf'ing. not trying to be rude but seriously?
Yeah, I spf'd just fine (twice now cause I'm dumb lol) so problem solved. I would like some help in my other topic though, about GB deodexed.
thewanton said:
Yeah, I spf'd just fine (twice now cause I'm dumb lol) so problem solved. I would like some help in my other topic though, about GB deodexed.
Click to expand...
Click to collapse
you have to sbf to .340 use z4 root to root then install DX bootstraper reboot to recovery flash gbrooted.zip if you get stuck in bootloop go into factory recovery and wipe data reboot download and install D2 bootstrapper yes D2, boot into recovery and flash gbrooteddeodexed.zip and let it try and boot it SHOULD bootup after a couple of minutes, if it doesnt get into stock recovery and wipe data, reboot
also it could bootloop because of corrupt downloads
tyvallely said:
Like what did you say to them?
Click to expand...
Click to collapse
'I was messing with my phone a bit i was going through the settings and i came across the update menu and i seen that i had an update so i went on ahead and tried to update it....so i was waiting for it to download on my status bar andd when it finished it went to another screen were it had triangle with an exclamation mark and the little android thing in the back so i waited for it to finish updated and when it finished it booted up and screen was black saying code corrup"
I don't really talk like that,but I was trying to make it seem as if i don't know much about phones.They have to send you another phone because they will think it's a manufacturing problem...
slfdjgdkkjfh! Damnit! I've been working on this all day and just now realized that the issue was that I wasn't using D2 bootstrap, I was still using the DX one and flashing deodexed right after the rooted one.
itzjen said:
'I was messing with my phone a bit i was going through the settings and i came across the update menu and i seen that i had an update so i went on ahead and tried to update it....so i was waiting for it to download on my status bar andd when it finished it went to another screen were it had triangle with an exclamation mark and the little android thing in the back so i waited for it to finish updated and when it finished it booted up and screen was black saying code corrup"
I don't really talk like that,but I was trying to make it seem as if i don't know much about phones.They have to send you another phone because they will think it's a manufacturing problem...
Click to expand...
Click to collapse
which is a problem that was caused by YOU because you take that and sbf
thewanton said:
slfdjgdkkjfh! Damnit! I've been working on this all day and just now realized that the issue was that I wasn't using D2 bootstrap, I was still using the DX one and flashing deodexed right after the rooted one.
Click to expand...
Click to collapse
most ppl overlook that as a typo
Funnyface19 said:
which is a problem that was caused by YOU because you take that and sbf
Click to expand...
Click to collapse
Yes it was a problem that I caused but at that momment I got scared and wasn't sure what I was suppose to do,and because I have no internet at home because i'm never home I use wireless tether when im there and my phone was messed up so wasn't able to look at guides to fix it.....So the easiest thing I thought of is calling them.I wouldn't have mind fixing it but again I wasn't able to at that momment.
I had the same thing happen. Put the letter p at the end of the file name and move it to c:\ this worked for me on rsd lite 4.8 I just kept pulling the battery and retrying until it went through
Sent from my Xoom using XDA Premium App
meshdub said:
Yeah, I don't think it was possible to go from orginial GB leak straight to the rooted one.
You will need RSDLite 4.8 or higher and 2.3.340 sbf file. Both should be easily findable with a Google search. Follow SBF instructions from there.
Click to expand...
Click to collapse
I'd just like to point out that you don't actually need rsd lite 4.8 or higher. 4.7 has worked perfectly for me the several times I have SBF'ed
I am having issues installing the SBF for 2.2. I am getting an error message about not being able to find initialization value. Did anybody run into this error and find out how to fix it.
zax10 said:
I am having issues installing the SBF for 2.2. I am getting an error message about not being able to find initialization value. Did anybody run into this error and find out how to fix it.
Click to expand...
Click to collapse
a) make sure your sbf is good.
b) what version of RSD lite are you using on what OS?
I got the sbf from the one attached to the thread. I am using rsdlite 4.5. It is the only one that would read that the bravo was connected. I am on windows 7 starter on netbook.
Sent from my X10i TripNMiUI using XDA Premium App
zax10 said:
I got the sbf from the one attached to the thread. I am using rsdlite 4.5. It is the only one that would read that the bravo was connected. I am on windows 7 starter on netbook.
Sent from my X10i TripNMiUI using XDA Premium App
Click to expand...
Click to collapse
You might could try RSD 5.0
Although, I had problems with RSD on my WIN7 Vaio also that I could never get around so I just used an XP to do the job.
I gave up with win7 netbook. Used my XP desktop and it started and finished perfectly.
Sent from my X10i TripNMiUI using XDA Premium App
I flashed the linked version via rsd and have no launcher. It started briefly then went to black. Everything works just can't initiate anything. It said it was ready to dl an update after flash so I clicked yes thinking this might be motoblur...BUT, it's waiting for offpeak hours because I cannot turn on wifi. Any thoughts on the next step?
Also, does anyone have a link to the stock 2.1 sbf just in case? I'm kinda in need of my phone right now. thx
ctcost said:
I flashed the linked version via rsd and have no launcher. It started briefly then went to black. Everything works just can't initiate anything. It said it was ready to dl an update after flash so I clicked yes thinking this might be motoblur...BUT, it's waiting for offpeak hours because I cannot turn on wifi. Any thoughts on the next step?
Also, does anyone have a link to the stock 2.1 sbf just in case? I'm kinda in need of my phone right now. thx
Click to expand...
Click to collapse
re-download the sbf in the other thread and re-flash it. it probably flashed wrong in some minor way that is messing something up.
Nahh still black. Thanks for the thought though. At least I can receive incoming calls and everything else for now. Then use the recent calls list to dial back after calling the bravo. :/
ctcost said:
Nahh still black. Thanks for the thought though. At least I can receive incoming calls and everything else for now. Then use the recent calls list to dial back after calling the bravo. :/
Click to expand...
Click to collapse
There is no 2.1 .sbf so if the 2.2 .sbf isn't working then something is wrong. If you can, do a factory data reset and reboot and then try to flash the 2.2 .sbf. see if that works.
Thanks Mcfarmfresh. Didn't want to go that route but didn't lose anything but some texts. It got me back to factory. Will try the flash again in the am.
Ladies and gentlemen, I'm proud to announce the birth of a brand new baby FroYo. Thx again Mcfarmfresh for pushing me in that direction. With Motoblur, all I lost were apps...no biggie.
ctcost said:
Ladies and gentlemen, I'm proud to announce the birth of a brand new baby FroYo. Thx again Mcfarmfresh for pushing me in that direction. With Motoblur, all I lost were apps...no biggie.
Click to expand...
Click to collapse
Awesome! Good to hear. Glad I could help.
ctcost said:
Thanks Mcfarmfresh. Didn't want to go that route but didn't lose anything but some texts. It got me back to factory. Will try the flash again in the am.
Click to expand...
Click to collapse
HELP! I meet the same problem! How can you resolve it? Please help me!
OK I had CM7 working and then I did something stupid and bricked my phone. When I do the SBF, it goes through and then upon reboot it boot-loops. I used the SBF from the other post and am using RSD 5.0, but am not sure what else could be going wrong. I wish I could have wiped things, but when it bricked it wouldn't get to the point for me to get into recovery. I hope I didn't brick it too bad...
edit: I found a post on how to get to the recovery mode to wipe the data. If you need to wipe data after installing an sbf, press the down volume button and hold then press the power button until you see the moto symbol. after you see the exclamation point, press BOTH the up and down volume buttons together to get to the options. The last post I found was a little confusing because some people say you have to touch the bottom right of the screen, which doesn't work.
dontbejeff said:
OK I had CM7 working and then I did something stupid and bricked my phone. When I do the SBF, it goes through and then upon reboot it boot-loops. I used the SBF from the other post and am using RSD 5.0, but am not sure what else could be going wrong. I wish I could have wiped things, but when it bricked it wouldn't get to the point for me to get into recovery. I hope I didn't brick it too bad...
edit: I found a post on how to get to the recovery mode to wipe the data. If you need to wipe data after installing an sbf, press the down volume button and hold then press the power button until you see the moto symbol. after you see the exclamation point, press BOTH the up and down volume buttons together to get to the options. The last post I found was a little confusing because some people say you have to touch the bottom right of the screen, which doesn't work.
Click to expand...
Click to collapse
Did this end up working for you?
Yes it did. I am back using CM7 on my Bravo
Sent from my MB525 using XDA App
The posts relating to pushing the corner of the screen relate to Eclair, 2.1, recovery menu. Froyo, 2.2 ^ is pushing both Vol ^ and v.
My friends purchased a Droid Pro with CM9 already loaded onto it. He asked for my help because he was experiencing bugs and wanted to go back to a stock ROM.
I installed the Motorola drivers.
I put the phone into clockwordmod recovery and cleared all the caches and battery stats.
I then restarted into the Bootloader and started up a current version of RSD lite on my Win7x64 installation.
Next I got the SBF file loaded up in RSD lite and started flashing.
As it was nearing completion I picked up the phone to "catch the boot" and in the process bumped the USB cable just enough to terminate the connection and the process failed.
Now I can't get passed the Bootloader which says Code Corrupt.
I have spent hours upon hours scouring the internet trying different fixes to fix this problem.
Now when I try to flash it again with RSD lite it gets stuck when switching the phone to PB pass through and FAILS with the error 0x70be because it can't find the driver for MDM6600 and my system labels it as an unknown device.
I have since installed WinXPx84 on my system and tried the SBF process over and over in different ways hoping that it will take.
Any insight is greatly appreciated.
Thank you,
PEZ
PEZ Dispenser said:
My friends purchased a Droid Pro with CM9 already loaded onto it. He asked for my help because he was experiencing bugs and wanted to go back to a stock ROM.
I installed the Motorola drivers.
I put the phone into clockwordmod recovery and cleared all the caches and battery stats.
I then restarted into the Bootloader and started up a current version of RSD lite on my Win7x64 installation.
Next I got the SBF file loaded up in RSD lite and started flashing.
As it was nearing completion I picked up the phone to "catch the boot" and in the process bumped the USB cable just enough to terminate the connection and the process failed.
Now I can't get passed the Bootloader which says Code Corrupt.
I have spent hours upon hours scouring the internet trying different fixes to fix this problem.
Now when I try to flash it again with RSD lite it gets stuck when switching the phone to PB pass through and FAILS with the error 0x70be because it can't find the driver for MDM6600 and my system labels it as an unknown device.
I have since installed WinXPx84 on my system and tried the SBF process over and over in different ways hoping that it will take.
Any insight is greatly appreciated.
Thank you,
PEZ
Click to expand...
Click to collapse
Woah woah woah. Windows x84?
Sent from my Nexus 7 using xda app-developers app
BlackFire27 said:
Woah woah woah. Windows x84?
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
x84 is just another way of saying 32 bit
I think it is x86. Back on topic. So, try downloading another sbf that is from before 4.7.8 Try sbfing that
Sent from my Amazon Kindle Fire using Tapatalk HD
Vlasp said:
I think it is x86. Back on topic. So, try downloading another sbf that is from before 4.7.8 Try sbfing that
Sent from my Amazon Kindle Fire using Tapatalk HD
Click to expand...
Click to collapse
Ah, my bad, yes x86. Like I said I've spent hours and hours on this and missed some sleep.
I will look into and try other SBFs however I have been having trouble locating good links considering the age of the device. Know of any resources?
What do you mean by 4.7.8? I can't find any information on that. The SBF files that I have tried flashing are 2.26.20 and another one I found for the Droid Pro that is just labeled 3087.sbf
PEZ Dispenser said:
Ah, my bad, yes x86. Like I said I've spent hours and hours on this and missed some sleep.
I will look into and try other SBFs however I have been having trouble locating good links considering the age of the device. Know of any resources?
What do you mean by 4.7.8? I can't find any information on that. The SBF files that I have tried flashing are 2.26.20 and another one I found for the Droid Pro that is just labeled 3087.sbf
Click to expand...
Click to collapse
my bad 4.7.3. Try that one by searching on google.
Sent from my Amazon Kindle Fire using Tapatalk HD
Vlasp said:
I think it is x86. Back on topic. So, try downloading another sbf that is from before 4.7.8 Try sbfing that
Sent from my Amazon Kindle Fire using Tapatalk HD
Click to expand...
Click to collapse
ah, I see, 4.7.8 is the blur version. Downloading 4.6.8 now. Hopefully that works.
Have I permanently bricked a phone for the first time?
Ok, so now I have tried 4.6.8, 4.7.3, 4.7.8 and probably also a couple others by now with no luck.
All of them get error switching phone to PB pass through mode (0x07BE). My system cannot find the driver for MDM 6600 and my systems will only see it as an unknown device after RSD light trys to do the PB mode switch. I have tried installing the driver pack after the PB switch, which doesn't work. Extracting the drivers to a location that I then direct device manager to and that doesn't work.
Any other ideas on how to get this good hardware back and going again?
I will try the process on a completely different computer tomorrow, maybe the OS switch wasn't enough and there is a conflict with my machine. I doubt it though because I have used this machine to work on my D3.
PEZ Dispenser said:
Ok, so now I have tried 4.6.8, 4.7.3, 4.7.8 and probably also a couple others by now with no luck.
All of them get error switching phone to PB pass through mode (0x07BE). My system cannot find the driver for MDM 6600 and my systems will only see it as an unknown device after RSD light trys to do the PB mode switch. I have tried installing the driver pack after the PB switch, which doesn't work. Extracting the drivers to a location that I then direct device manager to and that doesn't work.
Any other ideas on how to get this good hardware back and going again?
I will try the process on a completely different computer tomorrow, maybe the OS switch wasn't enough and there is a conflict with my machine. I doubt it though because I have used this machine to work on my D3.
Click to expand...
Click to collapse
now lets go 1 step back on rsd lite and downgrade to the second latest version. and install the Motorola bootloader drivers or normal drivers with that. quick question. can you boot past the error screen into the recovery? It is R and Q and Power button. when the M screen is present.
Sent from my Amazon Kindle Fire using Tapatalk HD
Vlasp said:
now lets go 1 step back on rsd lite and downgrade to the second latest version. and install the Motorola bootloader drivers or normal drivers with that. quick question. can you boot past the error screen into the recovery? It is R and Q and Power button. when the M screen is present.
Sent from my Amazon Kindle Fire using Tapatalk HD
Click to expand...
Click to collapse
I'm using RSD lite 6.1.5, so you say I should try 6.1.4 or another older version?
What is the difference between Motorola bootloader drivers and normal drivers?
I thought it was R and M and the Power button to get into recovery. Anyway, I tried R and Q which does not work either. Doesn't look like I can get into recovery. Can I flash a recovery system onto it with RSD lite and then fix it from there?
Thank you Vlasp for taking the time to help me out with this.
PEZ Dispenser said:
I'm using RSD lite 6.1.5, so you say I should try 6.1.4 or another older version?
What is the difference between Motorola bootloader drivers and normal drivers?
I thought it was R and M and the Power button to get into recovery. Anyway, I tried R and Q which does not work either. Doesn't look like I can get into recovery. Can I flash a recovery system onto it with RSD lite and then fix it from there?
Thank you Vlasp for taking the time to help me out with this.
Click to expand...
Click to collapse
I am getting all of my facts mixed up. It is R and M, and there are no bootloader drivers. and regarding the rsdlite, try the 6.1.4 or something.
Sent from my Amazon Kindle Fire using Tapatalk HD
You can flash the bootloader update, and then try flashing again... 4.04 or something like that... I cant check as my phone got stolen last week, but I think it may solve your problem
donlloreda said:
You can flash the bootloader update, and then try flashing again... 4.04 or something like that... I cant check as my phone got stolen last week, but I think it may solve your problem
Click to expand...
Click to collapse
I haven't been able to find any information on this or any other bootloader update. Can you maybe point me in the right direction?
try turning off firewall and flash it again
Sent from my Motorola MB612 using xda app-developers app
Hot-dog007 said:
try turning off firewall and flash it again
Sent from my Motorola MB612 using xda app-developers app
Click to expand...
Click to collapse
I'm not sure how that is supposed to help and the firewall was already disabled anyway.
When RSD lite finishes flashing and wants to switch the phone to PB pass through mode the system sees my phone as an unknown device and won't install the correct driver correctly. I do have the option to select which driver to install and can find Motorola from the menu but then I am faced with about 10 different options on what specific device driver to install. One of them is Motorola PB interface, one of them is Motorola Flash interface, etc etc. I've tried the PB interface driver and it seems like it installs but it still shows up as an unknown device on my system and the flashing fails.
try sbf_flash using linux