Related
When ever I try either the Fast boot android recovery, or Factory Reset from the Atrix [rooted W locked boot loader, stock gingerbread] it will reboot only to stop at Failed to Boot 2.
Removing the battery usually recovers the phone.
How to I get around th is problem, or do I have to take it back to AT&T for a swap out? [Or is that possible on a rooted phone?
Going in circles here other wise.
Thanks in advance.
I have a botched CWM install attempt and i am at the same screen whenever i turn on the phone. I am going to flash using RSD and see if that recovers it. Ill post once i find out.
Got tired of going in circles, found the OEM ATT stuff, used RSD lite, and installed the SBF
Now I'm back to normal, bloat and all.
jesgrew said:
Got tired of going in circles, found the OEM ATT stuff, used RSD lite, and installed the SBF
Now I'm back to normal, bloat and all.
Click to expand...
Click to collapse
bro, i oso facing same problem w u. the screen only shows "failed to boot 2. starting rsd mode"
would u like plz to give me step by step to recover it? thx so much, i really appreciate it
c1asis said:
bro, i oso facing same problem w u. the screen only shows "failed to boot 2. starting rsd mode"
would u like plz to give me step by step to recover it? thx so much, i really appreciate it
Click to expand...
Click to collapse
I read the NooB guide here on XDA and there are links to get the needed files: RSD Lite, and the AT&T OEM Gingerbread & current firmware SBF file.
I pulled the battery to recover my phone, then fully charged it up.
Made sure it was in USB debug mode.
Then did the Hardware Reset again.
When it stopped at "failed to boot 2. starting rsd mode" I started RSD lite on my PC, Pointed it at the SBF file, and installed.
It took some time, maybe 5~12 minutes?
But it rebooted a few times and I was good to go.
To test it I did several hardware resets, All A Ok.
Peace here till they get Cyanogen stable
jesgrew said:
I read the NooB guide here on XDA and there are links to get the needed files: RSD Lite, and the AT&T OEM Gingerbread & current firmware SBF file.
I pulled the battery to recover my phone, then fully charged it up.
Made sure it was in USB debug mode.
Then did the Hardware Reset again.
When it stopped at "failed to boot 2. starting rsd mode" I started RSD lite on my PC, Pointed it at the SBF file, and installed.
It took some time, maybe 5~12 minutes?
But it rebooted a few times and I was good to go.
To test it I did several hardware resets, All A Ok.
Peace here till they get Cyanogen stable
Click to expand...
Click to collapse
whats ur version before ur device got bricked? i dont know my version.
and if i used atnt unlocked phone, but i used it in singapore. can i use the atnt US version or OEM South East Asia? thx. realy confusing phone.
also when i connect my phone and i open RSD. it won't detect the phone. the device list in the RSD is empty.
c1asis said:
also when i connect my phone and i open RSD. it won't detect the phone. the device list in the RSD is empty.
Click to expand...
Click to collapse
Here is what little I know:
Put the Atrix in USB debugging mode.
Connect the phone to the USB cable, and the PC.
Change the USB mode to none.
Click OK
Start RSDlite, then it should see your phone.
And if you have a None US AT&T phone you will need that providers OEM SBF file.
Next move for me is unlocking the boot loader.
I used Pete's Motorola Tools for rooting.
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
So, I followed everything the briefmobile guide that was linked to from the greyblur xda page.
It said it installed, so I rebooted my Atrix and never made it past the "Dual Core Technology" boot screen.
I went into fastboot, then recovery mode (android guy by the triangle with the "!" in it). I reset the phone. Didn't work.
It was running 2.3.4.
I've read something about romracer, but I don't know what that is, where to download it, or how to use it. Please explain in depth if it is relevant.
Please help me. I just got this phone (my first smartphone) today and was really excited to start messing around with Android. I'm probably going to be too nervous to do anything for a while after this. I just want the stock os back. Anything that could get my phone back to where it was is GREATLY appreciated.
There is a one click batch script created by Alaq to revert phones back to stock 2.3.4. Here is the link:
http://forum.xda-developers.com/showthread.php?t=1421522
If you are not sure how to get into fastboot here is how:
1. Turn off your device.
2. Hold down the power button and downward volume button until you see “Fastboot” on your screen.
3. Push the upward volume button.
Greyblur is only for froyo ROMS. That's why you have a nonbooting phone.
Sent from my MB860 using xda premium
Dark9781 said:
There is a one click batch script created by Alaq to revert phones back to stock 2.3.4. Here is the link:
http://forum.xda-developers.com/showthread.php?t=1421522
If you are not sure how to get into fastboot here is how:
1. Turn off your device.
2. Hold down the power button and downward volume button until you see “Fastboot” on your screen.
3. Push the upward volume button.
Click to expand...
Click to collapse
Thank you! So do I just drop this onto my SD card then?
Njl6705 said:
Thank you! So do I just drop this onto my SD card then?
Click to expand...
Click to collapse
No. Put the phone into fastboot, hook it up to your computer, and run the script from your computer.
Dark9781 said:
No. Put the phone into fastboot, hook it up to your computer, and run the script from your computer.
Click to expand...
Click to collapse
Ok. I ran it, it said it was successful, I restarted it, and now I have:
Failed to boot 4
Starting RSD Mode
That only happens when your phones bootloader isn't unlocked. I assumed it was since you tried flashing a custom rom. You are going to have to flash a sbf file. Here is the link to the instructions.
http://forum.xda-developers.com/showthread.php?t=991072
You can find the 2.3.4 sbf file here:
http://www.fileserve.com/file/6TxJg...OLE-26-release-keys-signed-MERetail-06.sbf.gz
Or you can try the 2.3.6 update found here:
http://atrix.tk/4.5.141/
You are going to need to extract the file from the archive so you will need a zip program. I would go with winrar or 7-zip.
Also there is a newer version of rsd lite out than the one posted on the how to. Here is the link
http://mophoforum.com/the2dcour/RSDLite5.5.rar
This should get you running again. Good luck.
Sent from my ATRIX 4G
...first day of owning this phone... I think I'm done with this stuff after this. >.<
If you are trying to install ROMS you need to unlock the bootloader first... Check out the Noobs Guide in the general section.
Dark9781 said:
That only happens when your phones bootloader isn't unlocked. I assumed it was since you tried flashing a custom rom. You are going to have to flash a sbf file. Here is the link to the instructions.
http://forum.xda-developers.com/showthread.php?t=991072
You can find the 2.3.4 sbf file here:
http://www.fileserve.com/file/6TxJg...OLE-26-release-keys-signed-MERetail-06.sbf.gz
Or you can try the 2.3.6 update found here:
http://atrix.tk/4.5.141/
You are going to need to extract the file from the archive so you will need a zip program. I would go with winrar or 7-zip.
Also there is a newer version of rsd lite out than the one posted on the how to. Here is the link
http://mophoforum.com/the2dcour/RSDLite5.5.rar
This should get you running again. Good luck.
Sent from my ATRIX 4G
Click to expand...
Click to collapse
You're sure that if I flash this it won't get bricked further? SBF is firmware, right? I meant my phone was running OS 2.3.4.
I can't get get into rsd or fastboot now. All it says is
Failed to boot 4
Starting RSD mode.
I plugged that into my computer, it recognized my Atrix as SE Flash Olympus, instead of NS flash olympus, so I tried to flash it anyways and it failed.
Please guys. I'm getting desperate here. Please tell me I don't have a $250 paper weight.
If it says "Starting RSD mode," then you're in RSD mode -- that's okay.
RSD Lite also recognized my phone as "SE" instead of "NS." Not sure why, but it didn't harm anything.
Sometimes the flashing process fails with RSD Lite. (Do NOT EVER unplug your phone in the middle of a flash, by the way.) Which SBF did you try to flash?
sheeparecurious said:
If it says "Starting RSD mode," then you're in RSD mode -- that's okay.
RSD Lite also recognized my phone as "SE" instead of "NS." Not sure why, but it didn't harm anything.
Sometimes the flashing process fails with RSD Lite. (Do NOT EVER unplug your phone in the middle of a flash, by the way.) Which SBF did you try to flash?
Click to expand...
Click to collapse
2.3.4, what my phone was originally running.
Okay, good. Don't try any earlier SBF versions; that's the guaranteed way to brick your phone. (You're not hard bricked until it says "Failed to boot, entering NVFlash" -- if you have any other options, it's possible to pull it back.)
Try to flash the 2.3.4 SBF again. I've heard of some people having to try a couple of times before it takes; RSD Lite can be finicky.
I think the most immediately pressing issue would be your battery's charge, because it can't charge if it can't boot. If the program errors out with "Battery too low to flash", you may need to pick up an external charger and/or ask someone nicely at an at&t store to charge your battery in one of theirs.
sheeparecurious said:
Okay, good. Don't try any earlier SBF versions; that's the guaranteed way to brick your phone. (You're not hard bricked until it says "Failed to boot, entering NVFlash" -- if you have any other options, it's possible to pull it back.)
Try to flash the 2.3.4 SBF again. I've heard of some people having to try a couple of times before it takes; RSD Lite can be finicky.
I think the most immediately pressing issue would be your battery's charge, because it can't charge if it can't boot. If the program errors out with "Battery too low to flash", you may need to pick up an external charger and/or ask someone nicely at an at&t store to charge your battery in one of theirs.
Click to expand...
Click to collapse
Ok. So I'll try flashing it a couple more times. My battery should have a decent charge still, so that shouldn't be a problem.
Thanks.
I really need to just calm down and stop loosing my head over this.
UPDATE: When the flash fails, the phone's screen reads:
Failed to Boot 4
Starting RSD Mode
sec_exception: febe, 35, 35
RSD Lite also says
Flashing failed process. Phone did not re-ennumerate after RAM downloader was sent (0x703e).
What does this mean?
Hmm. I'll admit I don't know what that means, so all I can do is help you troubleshoot.
I did some searching, and another user hit this problem when using a USB port on the front of his PC (which is not powered as strongly as one on the back). Did I mention RSD Lite is a finicky beast?
If you're on a desktop machine, try switching to a USB port at the back. If you're on a laptop, try a different port. I'll keep looking for anyone with a similar problem.
EDIT: One last question. You extracted the file before flashing, right? The extension is .sbf, not sbf.gz?
Hmmm... Yeah, I guess all I can do is keep looking.
My battery is now too low to flash, and I don't have a friend who has an Atrix.
I might just sent this into mobiletechvideo's debricking service. This is my first android phone and I'd rather not mess it up anymore.
Yes, it's an SBF file.
Fair enough. Sorry this wound up being a pain. I know full well that sick feeling when you think something's messed up, but your phone is still only in a "soft brick" at this stage and can be recovered.
Keep in mind these things really can be modded safely, but you have to do a LOT of reading at the outset, and stick with roms made very recently. (Last August? ancient history.) It's an interesting technology intersection; these things are proper computers which should be readily customizable, but they're also phones which tend to be locked down by the manufacturer/carrier. By analogy, I can wipe my computer's hard drive and install XP if I want, even though I'm currently on W7. But if I try to install an earlier Android version on my phone, it bricks.
anyway, good luck with getting your phone up and running again.
Thanks. I actually did a decent amount of reading before I got this phone, but it seems I'm more of a kinesthetic kind of learner. I probably should have gotten an older, cheaper phone to play around with before I went all out and got an Atrix.
It really is an interesting intersection. It's too bad the manufactures feel the need to put any restrictions on.
I guess I'll just read some more n00b guides and try again when I have a little more confidence. $50 doesn't seem so bad to get the phone debricked compared to the $250 I payed for it. I don't really have a choice either, since the only means of charging it is thirty miles away at the nearest AT&T store.
Anyways, thanks for helping me troubleshoot. Hit me up if you have any problems. I'd be happy to dig around in the forums and see if I can find anything.
You could have avoided all these problems if you had read the entire thread about greyblur, because it specifically states that it is only for froyo phones. But, as many say, you live and you learn, then you aren't a noob anymore.
Also, if you have warranty on your phone, you can send it in and Motorola should fix it for you from what I've heard.
Sent from my Xoom using XDA Premium HD app
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 had been running cm10 on my dx2. Started getting really buggie so I tried to flash over with cm10 again, it failed.
I cleared Dalvik cache and hooked to RSD to SBF (not sure if that was the correct approach), but the flash failed with the following error:
"Failed flashing process. Phone[0000]: Error getting subscriber unit information. Device API Error: 0xE0030009 Command: RQHW (0x0832009)"
I left the phone connected and tried to run RSD SBF flash again with the exact same result. I unhooked the usb cable and tried a reboot of the phone. It won't boot. It goes to the red M screen and displays this at the top: "Failed to boot 4, Starting RSD mode". It hangs on this same screen when I power up holding the volume down button. While hanging on that screen I CAN connect to RSD but the flash still fails with the same error I listed above: "Failed flashing process. Phone[0000]: Error getting subscriber unit information. Device API Error: 0xE0030009 Command: RQHW (0x0832009)"
When holding the volume up button when powering up it hangs on red M screen with message at top: "Failed to boot 4 Starting Fastboot protocol support". I can then connect to RSD but the flash fails immediately when I click "start" on RSD. (That's probably exactly what should happen in this case?) Pushing or holding the volume up or down or both while on these red M screens causes nothing to happen.
-- I have tried 2 different usb cables, one is the original moto cable and both have always worked to flash this and other phones in the past.
-- I am using the same laptop that I have always used to flash this and a few other phones.
-- I have re-downloaded the SBF file twice and flashed with the same results.
-- I have done numerous battery pulls.
-- I have tried to get to stock system recovery by removing the battery and plugging into wall charger. I get the same result, red M screen with the following:
"Failed to boot 4"
"Starting RSD mode"
"Battery is too low to flash"
When on this error screen I have (in this order) installed battery, unplugged charger, plugged into computer usb - nothing changes on the phone screen and RSD does not see the phone so does not connect.
Here's what I will be trying later this evening:
Try a different computer.
Burn a Linux easySBF disc and try that.
What am I doing wrong or what else can I try?
Thank you!
So you have done the SBF process successfully before? What SBF file are you using? Do you have all the motorola drivers installed on your computer? Are you using Windows or Linux?
jsgraphicart said:
So you have done the SBF process successfully before? What SBF file are you using? Do you have all the motorola drivers installed on your computer? Are you using Windows or Linux?
Click to expand...
Click to collapse
Yes, I have SBFed this particular dx2 maybe 3-4 times before flashing different custom roms. I am using windows xp. I do also have the current moto drivers installed. The SBF flash with RSD actually progresses part way before the noted error.
tracnet said:
Yes, I have SBFed this particular dx2 maybe 3-4 times before flashing different custom roms. I am using windows xp. I do also have the current moto drivers installed. The SBF flash with RSD actually progresses part way before the noted error.
Click to expand...
Click to collapse
You mentioned it said battery to low to flash. Maybe thats your problem right there. I'm not 100% sure but I dont know if the battery charges without the operating system installed. I think I read that before. If this is the case, you need to charge your battery another way before continuing. If someone else you know has the same phone, you can charge your battery with their phone. Or get another battery. I'm not sure. Its best to have your battery at 100% before doing an SBF.
If I am wrong about the battery not able to charge without the OS, then just leave it charging for a bit and try the SBF again.
I have swapped in a known good and fully charged battery. Without a doubt my battery situation is ok. Keep in mind that the battery low error only shows if I try to get to system recovery by removing the battery and plugging in the wall charger. I had read before that is just another way to get to system recovery, that's why I did that. Otherwise there is no indication that the battery is too low.
In your other reply you asked what SBF file I have tried:
VRZ_MB870_4.5.1A-DTN-150-30_1FF_01
VRZ_MB870_4.5.1A-DTN-200-18_1FF_01
I have downloaded and tried a couple different copies of each of those SBF files. (I realize that one is for 2.3.4 and the other is 2.3.5)
jsgraphicart said:
You mentioned it said battery to low to flash. Maybe thats your problem right there. I'm not 100% sure but I dont know if the battery charges without the operating system installed. I think I read that before. If this is the case, you need to charge your battery another way before continuing. If someone else you know has the same phone, you can charge your battery with their phone. Or get another battery. I'm not sure. Its best to have your battery at 100% before doing an SBF.
If I am wrong about the battery not able to charge without the OS, then just leave it charging for a bit and try the SBF again.
Click to expand...
Click to collapse
Well I have a feeling you are going to stump me on this. lol. I have never had issues with any SBF that I have done so I cant really associate a problem with your situation. The only other thing I can suggest is try a different version of RSD lite or try a different machine if you can. Maybe even a linux machine. I just wouldn't know why it has worked for you in the past and now, all of a sudden, it wont.
Yeah, this stuff normally goes smooth for me too. When it doesn't then I get in the research and learn mode. Been searching and reading for a while now.
I will need to try the linux sbf disc later tonight, possibly tomorrow night, after I get to my machine that I can burn a disc on (don't have a thumb drive with me either right now).
I have heard that you cannot brick a dx or dx2...........wonder how true that is?
Thanks for your help!
jsgraphicart said:
Well I have a feeling you are going to stump me on this. lol. I have never had issues with any SBF that I have done so I cant really associate a problem with your situation. The only other thing I can suggest is try a different version of RSD lite or try a different machine if you can. Maybe even a linux machine. I just wouldn't know why it has worked for you in the past and now, all of a sudden, it wont.
Click to expand...
Click to collapse
tracnet said:
Yeah, this stuff normally goes smooth for me too. When it doesn't then I get in the research and learn mode. Been searching and reading for a while now.
I will need to try the linux sbf disc later tonight, possibly tomorrow night, after I get to my machine that I can burn a disc on (don't have a thumb drive with me either right now).
I have heard that you cannot brick a dx or dx2...........wonder how true that is?
Thanks for your help!
Click to expand...
Click to collapse
It IS really hard to brick the phone due to the SBF files being able to fix everything. But I guess anything is possible. As long as you can still get into RSD mode, you should be fine. Just try other methods like you said. I actually just SBF'd on a Mac the other day and it was surprisingly easy and fast. Sorry I couldnt be more help. Keep checking back here though. Maybe someone will chime in with a better answer.
Success!!
I started thinking about what is different this time.......I'm at my other home where I now need to use an external wifi usb antenna. Apparently I have never flashed a phone while having that antenna connected to a usb port, because when I tried to SBF with it unhooked it all went perfect!
tracnet said:
Success!!
I started thinking about what is different this time.......I'm at my other home where I now need to use an external wifi usb antenna. Apparently I have never flashed a phone while having that antenna connected to a usb port, because when I tried to SBF with it unhooked it all went perfect!
Click to expand...
Click to collapse
Sometimes its the things you would less likely expect. Glad you got it going.
jsgraphicart said:
Sometimes its the things you would less likely expect. Glad you got it going.
Click to expand...
Click to collapse
Appreciate the help, thanks!