Related
Hey Guys,
I need some help! I used RSD lite 4.8 and the new sbf (2.3.15) and I get all the way to the end and then it fails....Here is the error log:
Failed flashing process. Interface BP: Error sending RAM download for bootloader. Device API Error: 0xE0030009 Address: 0x18F000 Command ADDR (0xE0231009); phone connected.
Any ideas?
I am using the OTA 2.2 update and was rooted using BigDX theme.
I have tried the sbf 2x, and both times, would up in the same spot...
When the phone reboots, I have all my contacts and apps...
The reason I wanted to use the sbf is gmail keeps force closing so I'm not getting my emails over push...
So you didnt do a nandroid backup before you installed themes/roms?
I know this is a stupid question so sorry in advance- did you enable USB debugging on your phone? If so- have you tried it in different modes? Media Sync or USB mass storage?
I have heard reports of having to be in a different mode.
And you are sure it was the new sbf...
VRZ_MB810_2.3.15_1FF_01
Not the system sbf...
SHADO_X6_2.3.13_SYSTEM-ONLY
thepolishguy said:
I know this is a stupid question so sorry in advance- did you enable USB debugging on your phone? If so- have you tried it in different modes? Media Sync or USB mass storage?
I have heard reports of having to be in a different mode.
And you are sure it was the new sbf...
VRZ_MB810_2.3.15_1FF_01
Not the system sbf...
SHADO_X6_2.3.13_SYSTEM-ONLY
Click to expand...
Click to collapse
To SysadmNJ,
Yes I did a nandroid backup, so I have a place to go back to...but gmail was still force closed... So that is why I wanted to do the SBF.
Polishguy,
yes I have USB debugging enabled, and had thrown the phone in PC mode so it was detected. I'm stumped as to why it is failing at the end. Yes, I grabbed the SBF from rootz wiki. Would like to have a full SBF work so I can get the gmail service working again.
did you place the patch in rsd lite folder?
mob87 said:
did you place the patch in rsd lite folder?
Click to expand...
Click to collapse
Yes, the patched pst_flash.ini file?
Is there a new one for RSD 4.8?
Just trying to figure out what else might be going wrong...
there isnt a new one just wanted to make sure. maybe you got a bad download of the sbf.
mob87 said:
there isnt a new one just wanted to make sure. maybe you got a bad download of the sbf.
Click to expand...
Click to collapse
Tried the original that was hosted here before it got pulled by the mods, and also grabbed the one from rootz wiki as well. Got the same result with both. I will try putting the phone in charge only mode as well as media sync mode later and retry the sbf.
If anyone has done this successfully, can you please list the steps you took?
Thanks
SysAdmin-X said:
Tried the original that was hosted here before it got pulled by the mods, and also grabbed the one from rootz wiki as well. Got the same result with both. I will try putting the phone in charge only mode as well as media sync mode later and retry the sbf.
If anyone has done this successfully, can you please list the steps you took?
Thanks
Click to expand...
Click to collapse
You are suppose to be in bootloader when you flash the sbf.
mob87 said:
You are suppose to be in bootloader when you flash the sbf.
Click to expand...
Click to collapse
Ok. Will give this a try. I read you could do it with the phone on or off.... That it would put the phone into bootloader...which it looks like it did.
I will try putting it into bootloader prior to running the sbf.
EDIT:
I put the phone into bootloader mode, and have run the sbf 2 more times...still with the same error. Just wind up with different values on the error codes....
Yes holding the volume down, camera, and power button for a few seconds will make the screen flash then release the buttons and you will be in bootloader mode.
Sent from my DROIDX using XDA App
Try a different USB port or even a different PC.
Have tried the above suggestions.... I noticced each time it would make it slightly farther (or so it seemed) that there were device druvers being installed along the way.
Anyone have the driver p package they used if they got the sbf to work?
I'm using the 4.7 drivers
Sent from my DROIDX using XDA App
I recently got the same error message, I asked a few developers and P3 told me its the radio that is not being changed. he said it is not a problem unless you are not happy with the radio. This was about a week agao and i have been flashing Rom's/Themes all week and my phone is running great. I wouldn't worry much about it.
Just an FYI I am on the leak and used the first sbf.
FSRBIKER said:
I recently got the same error message, I asked a few developers and P3 told me its the radio that is not being changed. he said it is not a problem unless you are not happy with the radio. This was about a week agao and i have been flashing Rom's/Themes all week and my phone is running great. I wouldn't worry much about it.
Just an FYI I am on the leak and used the first sbf.
Click to expand...
Click to collapse
Hm...interesting. So the radio doesn't really matter unless its already messed up... I guess I should have thought of that...
ON ur x, it does look like everything else is back to stock tho?
did you do a battery pull ; and/or clear data/cache and do a factory reset after the process seemingly completes (never mind the error) - coz I got some error when I tried flashing using sbf - but I was on the 1st leak - and used the original (2.1) sbf - rsdlite said 100% - but error - mentioned somethin abt bootloader - I did a battery pull - phone went into loop of death - I cleared data/cache and also did a factory reset by going into recovery - and my phone was as good as new... just a thought..
EDIT: Actually, all your questions seem to be answered in the other thread in this very forum by name " Droid X Full SBF Release" posted by catalystsupreme2 - read through all the posts - esp. abt the radio etc which someone here also mentioned in this thread
chiaroscuro7 said:
did you do a battery pull ; and/or clear data/cache and do a factory reset after the process seemingly completes (never mind the error) - coz I got some error when I tried flashing using sbf - but I was on the 1st leak - and used the original (2.1) sbf - rsdlite said 100% - but error - mentioned somethin abt bootloader - I did a battery pull - phone went into loop of death - I cleared data/cache and also did a factory reset by going into recovery - and my phone was as good as new... just a thought..
EDIT: Actually, all your questions seem to be answered in the other thread in this very forum by name " Droid X Full SBF Release" posted by catalystsupreme2 - read through all the posts - esp. abt the radio etc which someone here also mentioned in this thread
Click to expand...
Click to collapse
I read through this, and I haven't done the battery pull, or clear..... trying to avoid it if possible...but will if needed.
As for the answer about the BP, it didn't seem like the post really answered the question per say...just gave an explanation about it overall
thank you for the help
Hey guys,
wahoo! new droid-x user here! Picked up a used on craigslist and so far everything seems to check out. ESN is clean and so far functioning pretty well.
One thing is that the previous user still has a lot of his stuff on there, his email, some stock and bank stuff are still on there. I want to clean up and start from a factory reset so I can start clean and I don't mess with his stuff.
I did a search and it looks like there are 2 methods, but the thing that I'm worried about is that one of the threads, http://forum.xda-developers.com/showthread.php?t=740285, it mentions that if some apps are removed beforehand DO NO do a reset or it will brick it.
---------------------------------------------------------
Also if you've removed or renamed Back-Up Assistant and do a reset, you'll end up with a semi-bricked phone.
---------------------------------------------------------
NO. DO NOT WIPE IF YOU REMOVED ANY BLOAT APPS.
If you do this you can kiss your phone goodbye.
Read this thread to tell you how to put back the apps the RIGHT way before you wipe, otherwise, you will be without a phone.http://www.droidxforums.com/forum/dr...otlooping.html
==================
My first question, how do I verify that it is okay to do a factory reset?
My second queestion is which method should I use?
Thanks in adv!
Here are the two methods I've found, which is the correct one?
Method 1:
To do a proper factory reset follow these: 1.Go to Settings 2.Scroll to Privacy 3.Click Factory Data Reset 4. Confirm action by clicking Reset Phone.
Method 2:
1)Turn off the phone
2)Hold the Power Button and the Home Button. The Moto logo will pop up followed by a triangle with the Android symbol next to it.
3)Press the Search button to display the menu.
4)4 options will pop up, use the Volume Rocker to move the selection up or down.
5)Select “Wipe Data to Factory Default.” Select the option by using the Camera hard key.
6)Confirm choice by using the camera key.
7)It will take you back to the original menu, select "Reboot Device"
You will have to re-program your phone with OTA updates.
hamachiaddict said:
Hey guys,
wahoo! new droid-x user here! Picked up a used on craigslist and so far everything seems to check out. ESN is clean and so far functioning pretty well.
One thing is that the previous user still has a lot of his stuff on there, his email, some stock and bank stuff are still on there. I want to clean up and start from a factory reset so I can start clean and I don't mess with his stuff.
I did a search and it looks like there are 2 methods, but the thing that I'm worried about is that one of the threads, http://forum.xda-developers.com/showthread.php?t=740285, it mentions that if some apps are removed beforehand DO NO do a reset or it will brick it.
---------------------------------------------------------
Also if you've removed or renamed Back-Up Assistant and do a reset, you'll end up with a semi-bricked phone.
---------------------------------------------------------
NO. DO NOT WIPE IF YOU REMOVED ANY BLOAT APPS.
If you do this you can kiss your phone goodbye.
Read this thread to tell you how to put back the apps the RIGHT way before you wipe, otherwise, you will be without a phone.http://www.droidxforums.com/forum/dr...otlooping.html
==================
My first question, how do I verify that it is okay to do a factory reset?
My second queestion is which method should I use?
Thanks in adv!
Here are the two methods I've found, which is the correct one?
Method 1:
To do a proper factory reset follow these: 1.Go to Settings 2.Scroll to Privacy 3.Click Factory Data Reset 4. Confirm action by clicking Reset Phone.
Method 2:
1)Turn off the phone
2)Hold the Power Button and the Home Button. The Moto logo will pop up followed by a triangle with the Android symbol next to it.
3)Press the Search button to display the menu.
4)4 options will pop up, use the Volume Rocker to move the selection up or down.
5)Select “Wipe Data to Factory Default.” Select the option by using the Camera hard key.
6)Confirm choice by using the camera key.
7)It will take you back to the original menu, select "Reboot Device"
You will have to re-program your phone with OTA updates.
Click to expand...
Click to collapse
Both methods will work actuqlly. If you truly want to go to a fresh state... I would recommend an sbf. Go to settings-->about phone. What does it say for android version?
I can point you to the correct files depending on what version you are on.
Sent from my DROIDX using XDA App
Thanks SysAdmin ... it says Android version 2.2.1
What is a sbf?
hamachiaddict said:
Thanks SysAdmin ... it says Android version 2.2.1
What is a sbf?
Click to expand...
Click to collapse
Sbf is a file that motorola uses to reflash a phone to out of the box state. Just to double check, power off your phone, then hold volume down + camera button while holding the power button (this is known as bootloader). If it says 30.04 for the bootloader version, then you are definitely on the most recent update.
Try this link if you are confident with technical details:
http://www.droid-life.com/2010/12/09/droid-x-2-3-340-system-sbf-released-for-2-3-320-leak-users/
If you prefer to flash files through bootstrap, then use this link:
http://www.droidforums.net/forum/droid-x-rooted-help/112152-maderstcok-ota-2-3-340-update-zip.html
Sent from my DROIDX using XDA App
Thanks! I'll do some reading to see which one to use.
One more question, which one of these usb drivers should I download?
http://www.motorola.com/Support/US-...tware_and_Drivers/USB-and-PC-Charging-Drivers
PC Driver 1 (W370, W375, W376g, W377)
PC Driver 2 (W216, W230, W230x, W23x, W259, W270, W270x, W27x, W388, W396, W397, W397v)
PC driver 1 or driver 2?
edit:
Also do you have link to RSD lite? I found a link for 4.9 but their password is not working
hamachiaddict said:
Thanks! I'll do some reading to see which one to use.
One more question, which one of these usb drivers should I download?
http://www.motorola.com/Support/US-...tware_and_Drivers/USB-and-PC-Charging-Drivers
PC Driver 1 (W370, W375, W376g, W377)
PC Driver 2 (W216, W230, W230x, W23x, W259, W270, W270x, W27x, W388, W396, W397, W397v)
PC driver 1 or driver 2?
edit:
Also do you have link to RSD lite? I found a link for 4.9 but their password is not working
Click to expand...
Click to collapse
Personally, I would use the link titled Motorola 4.8.0 Driver with MotoConnect. It keeps your driver's up to date and automatically identifies just about any Motorola device. I always use it for my gf's OG Droid and my DX.
If you can't get RSD Lite 4.9 to work, I still use 4.8. You can download the zip here.
Ben's said:
Personally, I would use the link titled Motorola 4.8.0 Driver with MotoConnect. It keeps your driver's up to date and automatically identifies just about any Motorola device. I always use it for my gf's OG Droid and my DX.
If you can't get RSD Lite 4.9 to work, I still use 4.8. You can download the zip here.
Click to expand...
Click to collapse
Thanks, I'll install the Motorola 4.8.0 Driver.
I got RSD Lite 4.9 to install, wahoo!
I noticed there was a disclaimer on there that says once you upgrade to 2.3.340, you cannot downgrade.
Is this an issue, and what is the main reason to upgrade to 2.3.340?
And how is this different from doing a:
menu > privacy> factory reset
Thanks in adv!
hamachiaddict said:
Thanks, I'll install the Motorola 4.8.0 Driver.
I got RSD Lite 4.9 to install, wahoo!
I noticed there was a disclaimer on there that says once you upgrade to 2.3.340, you cannot downgrade.
Is this an issue, and what is the main reason to upgrade to 2.3.340?
And how is this different from doing a:
menu > privacy> factory reset
Thanks in adv!
Click to expand...
Click to collapse
Well, this is no real "issue" but more of a disclaimer because once you upgrade to newer software version, you can not go back to previous hardware versions because of the files it flashes to your phone. I don't know how much of this is true seeing that your can do a full SBF to .320
I'm sure people can go plenty in depth about this but it's irrelevant either way.
340 is just the newest software version. Newer software fixes bugs, updates files and other components of your phone.
If you go to settings, about phone, and it already said Android Version 2.2.1, Baseband version BP_C_01.09.07P and Kernel version 2.6.32.9-g55626e1, then you are already up to date. Just go to Privacy and factory data reset the phone.
Doing a SBF with RSD Lite is in extreme cases that you soft brick your phone when it’s a must just to get it back to stock. It’s optional in your case.
Reset and you should be all good
Ben's said:
Well, this is no real "issue" but more of a disclaimer because once you upgrade to newer software version, you can not go back to previous hardware versions because of the files it flashes to your phone. I don't know how much of this is true seeing that your can do a full SBF to .320
I'm sure people can go plenty in depth about this but it's irrelevant either way.
340 is just the newest software version. Newer software fixes bugs, updates files and other components of your phone.
If you go to settings, about phone, and it already said Android Version 2.2.1, Baseband version BP_C_01.09.07P and Kernel version 2.6.32.9-g55626e1, then you are already up to date. Just go to Privacy and factory data reset the phone.
Doing a SBF with RSD Lite is in extreme cases that you soft brick your phone when it’s a must just to get it back to stock. It’s optional in your case.
Reset and you should be all good
Click to expand...
Click to collapse
ah, thanks ben, the only reason I'm hesitant of doing the reset is because on the thread listed in OP, people mentioned that doing a reset can brick your phone and since I don't know what was removed from this phone, I didn't want to risk bricking it.
hamachiaddict said:
ah, thanks ben, the only reason I'm hesitant of doing the reset is because on the thread listed in OP, people mentioned that doing a reset can brick your phone and since I don't know what was removed from this phone, I didn't want to risk bricking it.
Click to expand...
Click to collapse
Well, is your phone rooted? Did the person tell you if they removed apps and all that? More then likely no unless they specified. The OP is correct in stating that if you go to update or factory reset with missing apps, root and all that jazz...you will end up with a bootloop and have to SBF with RSD Lite.
The previous owner might have deleted apps here and there but without root, he could not have removed the apps that would make your phone brick. I think paranoia is getting the best of you lol.
Ben's said:
Well, is your phone rooted? Did the person tell you if they removed apps and all that? More then likely no unless they specified. The OP is correct in stating that if you go to update or factory reset with missing apps, root and all that jazz...you will end up with a bootloop and have to SBF with RSD Lite.
The previous owner might have deleted apps here and there but without root, he could not have removed the apps that would make your phone brick. I think paranoia is getting the best of you lol.
Click to expand...
Click to collapse
How do I tell whether it's rooted or not?
I asked and he said no, but I just want to err on the safe side ... and yes I think you're right, I'm getting super paranoid about this.
hamachiaddict said:
How do I tell whether it's rooted or not?
I asked and he said no, but I just want to err on the safe side ... and yes I think you're right, I'm getting super paranoid about this.
Click to expand...
Click to collapse
Look for an app called SuperUser. If it's not on the device, you're not rooted.
Sent from my DROIDX using Tapatalk
hamachiaddict said:
How do I tell whether it's rooted or not?
I asked and he said no, but I just want to err on the safe side ... and yes I think you're right, I'm getting super paranoid about this.
Click to expand...
Click to collapse
Download wireless tether for.root on the market and try to run it... If it works you are rooted, if you arent, then it will let you know the app does not.have superuser permissions
Sent from my DROIDX using XDA App
SysAdmin-X said:
Download wireless tether for.root on the market and try to run it... If it works you are rooted, if you arent, then it will let you know the app does not.have superuser permissions
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
Thanks, that's what I tried and nope it's not rooted. Did the factory reset and it's all good now.
I thought all the old apps would get wiped out too but it didn't.
Thanks guys! now to decide whether to root or not
hamachiaddict said:
Thanks, that's what I tried and nope it's not rooted. Did the factory reset and it's all good now.
I thought all the old apps would get wiped out too but it didn't.
Thanks guys! now to decide whether to root or not
Click to expand...
Click to collapse
Glad to hear you got things working. I would recommend if you are technically competent, and able to follow directions to a 'T' you should root your phone...it opens lots of possibilities on the X. If you are nervous about any mods (not trying to be mean...but it sounds like you're nervous) then I would recommend reading up on threads and guides before rooting and modifying your phone. A $600 paperweight for a phone never did anyone ever good.
Here is a guide I have put together and am adding to as I can. It should be a good place to start reading and get you covered for basics.
http://forum.xda-developers.com/showthread.php?t=940986
Enjoy and good luck!
SysAdmin-X said:
Glad to hear you got things working. I would recommend if you are technically competent, and able to follow directions to a 'T' you should root your phone...it opens lots of possibilities on the X. If you are nervous about any mods (not trying to be mean...but it sounds like you're nervous) then I would recommend reading up on threads and guides before rooting and modifying your phone. A $600 paperweight for a phone never did anyone ever good.
Here is a guide I have put together and am adding to as I can. It should be a good place to start reading and get you covered for basics.
http://forum.xda-developers.com/showthread.php?t=940986
Enjoy and good luck!
Click to expand...
Click to collapse
Awesome, thanks, I definitely give that a read.
yeah, I was prob. on the nervous side cause I just got it yesterday, but I'm pretty ok technically, rooted the nook color a few weeks ago
glad I'm able to get so much help here
hamachiaddict said:
Awesome, thanks, I definitely give that a read.
yeah, I was prob. on the nervous side cause I just got it yesterday, but I'm pretty ok technically, rooted the nook color a few weeks ago
glad I'm able to get so much help here
Click to expand...
Click to collapse
No problem, most people on here are more than happy to help! If you have any more questions, feel free to post in my thread, I'll be more than happy to help you out... and then prob throw that tid-bit into my guide =)
I flashed the Eclipse ROM via safestrap and then restored the Eclipse ROM onto the stock ROM slot. For some stupid reason, instead of restoring the stock ROM slot before resetting the phone back to stock, I opted to use RSD Lite 6.1.4 and tried to flash the JB firmware (yes, I got into fastboot). When I tried to do this, the phone reboots past the Motorola M insignia, to the droid startup screen (with the flashing red light/circle), but does not get past the startup screen (yes, I gave it 30+ minutes to no avail). I also tried to reflash the JB firmware, but no matter what, I ended up stuck at the bootup screen.
For this reason, I tried to flash the ICS firmware instead (per instructions on XDA and other websites, I removed the lines in the XML file that had the word var, getvar, and oem). This did work! However, after RSD flashed the firmware, rather than restarting into the OS, the phone reboots into a black screen w/ the phrase "Fastboot Reason: Sticky bit factory_fastboot" at the very bottom. Anytime I try to restart the phone, it automatically boots into this screen. If I hold the volume up and down buttons, together w/ the power button, I am able to get back to the option to start normally.
When I tried to do the OTA JB update, the phone downloads the necessary files, but when the phone tries to reboot to install the OS update, it goes back into that black screen and does not install the update. Also, when I finally do get back into the OS, the phone then constantly reboots as if it were trying to install the OTA JB update.
Does anyone know what "Fastboot Reason: Sticky bit factory_fastboot" means? Also, if anyone knows how to "fix" this issue, I'd greatly appreciate it. If the fix requires command line work (like in this thread), I'd greatly appreciate if someone could walk me through it step-by-step, as I am not familiar w/ the command line process.
Thanks!
Edit 1: The next step I will try is to get root back on my phone, install Safestrap, and see whether I can flash a backup that I previously had.
Edit 2: In some threads for other Moto phones, there is some discussion regarding using ADB to fastboot/flash the stock ROM. Anyone know how this is different from using RSD? Also, can anyone walk me through HOW to ADB? I have zero knowledge in this regard.
Have you tried holding the buttons down to enter fast boot again and reflash? Worth a shot if you haven't. You could also attempt a factory reset from the boot menu. Maybe the corrupt file would correct itself.
You should definitely take the time to learn some ADB; at least a working understanding. It helps down the road.
Here's a good tutorial on ADB commands. http://mobile.tutsplus.com/tutorials/android/android-adb-quick-guide/
And to install ADB without Android SDK (app production software) http://mobilecon.info/install-adb-in-windows.html
Sent from my Nexus 7 using xda app-developers app
skippid said:
Have you tried holding the buttons down to enter fast boot again and reflash? Worth a shot if you haven't. You could also attempt a factory reset from the boot menu. Maybe the corrupt file would correct itself.
You should definitely take the time to learn some ADB; at least a working understanding. It helps down the road.
Here's a good tutorial on ADB commands. http://mobile.tutsplus.com/tutorials/android/android-adb-quick-guide/
And to install ADB without Android SDK (app production software) http://mobilecon.info/install-adb-in-windows.html
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Yes, I attempted to reflash on multiple occasions, both using the stock ICS and the stock JB roms. I must have reflashed close to 10x at this point. In any case, no matter how often I have reflahsed (including after doing a factory reset from within the OS as well as from within recovery), I still get the error. The good news is that I was successfully able to flash the JB ROM and have the phone OS actually start up, whereas, a few days ago, it would be stuck at the red circle/eye thing.
Furthermore, I attempted the command fastboot flash system [system.img], and I got the error:
(bootloader) Variable not supported!
target reported max download size of 31457280 bytes
error: cannot load '[system.img]': no error
I saved the system.img in both c:\android, as well as the internal SD card of the phone.
The other good news is that I am still able to use the phone if I get into the boot menu and ask the phone to boot normally. However, I am now unable to get root, and anytime I need to restart the phone, it gives me that error message.
I have also tried the command fastboot reboot bootloader but continue to get the same error message.
OK. Find a JB leak zip or current stock JB zip, access the screen where it asks for AP Fast boot and recovery, choose recovery, then volume up I believe when the phone shows the android with the red exclamation point.. Then choose update with zip. Search your SD card and install. It's worth a try in this manner in case you haven't already.
That's odd that your phone didn't respond well with RSD.
Sent from my XT907 using xda app-developers app
You need to use an updated fastboot binary for the new larger images in these devices.
http://db.tt/AveMC40y
skippid said:
OK. Find a JB leak zip or current stock JB zip, access the screen where it asks for AP Fast boot and recovery, choose recovery, then volume up I believe when the phone shows the android with the red exclamation point.. Then choose update with zip. Search your SD card and install. It's worth a try in this manner in case you haven't already.
That's odd that your phone didn't respond well with RSD.
Sent from my XT907 using xda app-developers app
Click to expand...
Click to collapse
Skippid, thanks for the suggestions. I tried your method as well. Went into recovery, selected to update from external SD (or something to that effect), selected the JB zip file, and let it flash that way. Unfortunately, I still received the same error message regarding the sticky bit factory_fastboot.
cellzealot said:
You need to use an updated fastboot binary for the new larger images in these devices.
http://db.tt/AveMC40y
Click to expand...
Click to collapse
cellzealot, thank you for the link. I've downloaded the file that you linked to. Could you be so kind as to now give me a step-by-step on how to re-attempt the flashing process?
Quick update - I was able to get root back, installed safestrap, and flashed the nandroid that I had made back when I first flashed Eclipse. However, I am still having the same issue:
Whenever I restart the phone, I get the sticky bit factory_fastboot error. If I use the command fastboot continue, the phone boots up as normal; however, it would be great to not have to do this each and every time I reboot the phone. Any help would be greatly appreciated. Thanks!
More updates (still not fixed):
After getting root, I reflashed my nandroid, factory reset (both within the OS and in recovery), and then tried flashing both the ICS and JB stock ROMs. I tried flashing both using mfastboot, as well RSD Lite. The files flash successfully; however, whenever I restart the phone, I continue to get the stick bit factory_fastboot error.
Also, when I get into recovery, I try to flash via "update from external SD". When I do so, recovery simply restarts without flashing the stock ROM.
Here's my last update as to this issue:
After trying all of the methods that I could think of (RSD Lite, flashing via fastboot and mfastboot, flashing from external), the problem did not correct itself.
I brought my phone into a Verizon store, where they told me that they had never seen that problem before. They agreed to replace my phone pursuant to the one-year warranty (I received my phone in December), which I received today. I've again rooted my phone, but have opted to not screw around w/ safestrap and custom ROMs this time around, as I find the stock JB experience to actually be quite good.
Found the soultion!!!!!!
Ok guys so after serching a while I found out similar moto phones have the same issue. I found in a latin forum and in a Droid forum people ponting to the same issue. So the solution that worked for my Razr HD xt925 was:
1) Enter fastboot mode in your phone (very easy since every time you restart the phone you end there anyways)
2) Write this command on the computer: fastboot oem fb_mode_clear
there will be a dialogue with the time take and OK
You are done!
Thought someone might find it useful
Thank you!
cerafio said:
Ok guys so after serching a while I found out similar moto phones have the same issue. I found in a latin forum and in a Droid forum people ponting to the same issue. So the solution that worked for my Razr HD xt925 was:
1) Enter fastboot mode in your phone (very easy since every time you restart the phone you end there anyways)
2) Write this command on the computer: fastboot oem fb_mode_clear
there will be a dialogue with the time take and OK
You are done!
Thought someone might find it useful
Click to expand...
Click to collapse
Thank you! This was the answer I needed after searching and searching trying all the different things for over 3 hours, this 2 second fix worked!
Namanati said:
Thank you! This was the answer I needed after searching and searching trying all the different things for over 3 hours, this 2 second fix worked!
Click to expand...
Click to collapse
#8 > http://forum.xda-developers.com/droid-razr-m/general/guide-faq-how-to-root-boot-unlock-t2869432
ATTACK said:
#8 > http://forum.xda-developers.com/droid-razr-m/general/guide-faq-how-to-root-boot-unlock-t2869432
Click to expand...
Click to collapse
Thanks, but that didn't come up when I googled AP Fastboot: flash failed, and since I didn't get it from rooting or unlocking my phone I didn't think to look for that.
cerafio said:
Ok guys so after serching a while I found out similar moto phones have the same issue. I found in a latin forum and in a Droid forum people ponting to the same issue. So the solution that worked for my Razr HD xt925 was:
1) Enter fastboot mode in your phone (very easy since every time you restart the phone you end there anyways)
2) Write this command on the computer: fastboot oem fb_mode_clear
there will be a dialogue with the time take and OK
You are done!
Thought someone might find it useful
Click to expand...
Click to collapse
Oh my god dude thank you so much. That fixed my bootloader issue that was plaguing me for weeks
Thanks again!!!
cerafio said:
Ok guys so after serching a while I found out similar moto phones have the same issue. I found in a latin forum and in a Droid forum people ponting to the same issue. So the solution that worked for my Razr HD xt925 was:
1) Enter fastboot mode in your phone (very easy since every time you restart the phone you end there anyways)
2) Write this command on the computer: fastboot oem fb_mode_clear
there will be a dialogue with the time take and OK
You are done!
Thought someone might find it useful
Click to expand...
Click to collapse
Thanks Man You really saved my razr.:good:
Edit : Sorry I asked stupid question!
Pierro29 said:
Edit : Sorry I asked stupid question!
Click to expand...
Click to collapse
there are no stupid questions if you question its because you dont know something and would like to fulfill the empty space where a reasonable answer could go. and s thanks for the solution to this error.
Okay, I have a "stupid"/newbie question. I flashed an image and I am getting the sticky boot thing. How to a get to a window to type the lines in?
Thanks!
cerafio said:
Ok guys so after serching a while I found out similar moto phones have the same issue. I found in a latin forum and in a Droid forum people ponting to the same issue. So the solution that worked for my Razr HD xt925 was:
1) Enter fastboot mode in your phone (very easy since every time you restart the phone you end there anyways)
2) Write this command on the computer: fastboot oem fb_mode_clear
there will be a dialogue with the time take and OK
You are done!
Thought someone might find it useful
Click to expand...
Click to collapse
Hey dude ! You save my life
Awesome trick
Hi all. In advance, please don't flame me. I am new to Android, and don't understand all of the technical jargon. I have a problem that I hope will be a simple fix - if there is an answer already on the forums perhaps someone can point me in the right direction.
I was given a Samsung S4 by a friend that works for Samsung. Apparently it was some kind of demo model or something - typically given out for promotional purposes (which may or may not be relevant). The phone is factory unlocked. It is running on the AT&T version of the firmware. Here is the "About Device" info:
Model #: Samsung-SGH-I337
Android version: 4.2.2
Baseband ver: I337UCUAMDB
Kernal ver: 3.4.0-440216
My problem: I cannot update firmware. I tried OTA and via Samsung Kies. When I try OTA, it searches for an update (and finds one available), but then says that the update was interrupted and I there is no update available - try again in 24 hours (GRRR!). When I try to update via Kies, it finds the update and goes through a lengthy download process. Once it begins to install it (my screen goes black and green characters flash on the screen - so apparently it is trying to install the new firmware) - it hangs. Eventually I get a message stating that the update failed (or something along those lines) and I need to do emergency recovery. When I start emergency recovery it just hangs....eventually I just restart the phone and it is right back to normal.
I have tried this process 6 or 7 times-no luck. I really want the recent update, which allows moving apps to SD. Again - I am new to Android-everything. I understand that I likely need to manually install a ROM package - if someone could point me toward some step by step directions I would REALLY appreciate it. Thanks in advance for your help!
-TJ
To try to update more often, try moving the time and date of the phone ahead and try again. If you want to flash ROMS, don't update, because there is no bootloader unlock for it yet
Sent from my SAMSUNG-SGH-I337 using Tapatalk 4
r8revealed said:
To try to update more often, try moving the time and date of the phone ahead and try again. If you want to flash ROMS, don't update, because there is no bootloader unlock for it yet
Sent from my SAMSUNG-SGH-I337 using Tapatalk 4
Click to expand...
Click to collapse
Thx for the reply...and for the tip about adjusting the date/time. :good: I am fine with the stock AT&T ROM - but for whatever reason, my phone simply will not update. I tried resetting it - still no dice. If anyone could help me to reinstall the stock or newer AT&T rom manually, I think that would be ideal. Any ideas?
I don't know much about this, but maybe you could flash the stock AT&T firmware again via ODIN. It's basically "unooting" the device, even though your device isn't rooted. it'll wipe all your data and reinstall everything again. I did this often on my S3 but I'm not sure if it's the same for the S4. Maybe someone else would know better because I don't know the .tar files needed for unrooting the S4.
Sent from my SAMSUNG-SGH-I337 using Tapatalk 4
antjefferson said:
Hi all. In advance, please don't flame me. I am new to Android, and don't understand all of the technical jargon. I have a problem that I hope will be a simple fix - if there is an answer already on the forums perhaps someone can point me in the right direction.
I was given a Samsung S4 by a friend that works for Samsung. Apparently it was some kind of demo model or something - typically given out for promotional purposes (which may or may not be relevant). The phone is factory unlocked. It is running on the AT&T version of the firmware. Here is the "About Device" info:
Model #: Samsung-SGH-I337
Android version: 4.2.2
Baseband ver: I337UCUAMDB
Kernal ver: 3.4.0-440216
My problem: I cannot update firmware. I tried OTA and via Samsung Kies. When I try OTA, it searches for an update (and finds one available), but then says that the update was interrupted and I there is no update available - try again in 24 hours (GRRR!). When I try to update via Kies, it finds the update and goes through a lengthy download process. Once it begins to install it (my screen goes black and green characters flash on the screen - so apparently it is trying to install the new firmware) - it hangs. Eventually I get a message stating that the update failed (or something along those lines) and I need to do emergency recovery. When I start emergency recovery it just hangs....eventually I just restart the phone and it is right back to normal.
I have tried this process 6 or 7 times-no luck. I really want the recent update, which allows moving apps to SD. Again - I am new to Android-everything. I understand that I likely need to manually install a ROM package - if someone could point me toward some step by step directions I would REALLY appreciate it. Thanks in advance for your help!
-TJ
Click to expand...
Click to collapse
I'm not flaming you, I am giving you advice that will help you. Try to use the search function to find answers before posting a question that has already been posted several times. It is possible, the help you need has already been posted in those other threads several times. Also, did you see "similar" threads appear while you were posting your question? Take the time to read those first. It couldn't be easier because they are listed for you. You should also read the "pinned" threads in the "general" section. There is a lot of information there that will help you understand things, if you take the time to read it. If you don't understand the "technical jargon" take some time to learn about it before you do anything to your phone or you are guaranteed to mess it up. If you really don't want future flaming, follow the XDA rules and search for answers first. Good luck.
Hi all. New poster and completely non-tech savy. Over the last few days I've been tinkering with my phone trying to learn about various roms and related. I had successfully flashed the CM11 update to my droid X but found that the OS was running extremely slow. example ( while trying to talk through hangouts it would take 2-3 seconds for each letter to not only to show up but also register so I could type my next letter.) This having been the case I tried to downgrade the OS to stock or some older rom. Since going through the steps I find myself in alot of trouble! I am now able to load stock recovery and bootloader only! I am unable to get into Twrp or CWM at all. The phone if loaded regularly will only go as far as the Motorola logo and no further. It will stay on that logo until the battery is taken out. I am unable to power down or reboot otherwise. Unfortunatley I am unable to supply official information like Build and the related but I can say before flashed to CM11 it was the standard Droid X 2.3.4.621 M810 and the CM 11 build was the most recent CM 11 (shadow) build as of 5/18/2015. I need help to load into Twrp or whatever I can do to just load past the motorola logo screen. Oh lastly, I have installed the Motorola Driver program but my computer doesnt seem to be able to find the connection. It does show on device manager and states it is fully upto date driver wise. However it isnt found in RSD Lite run as admin. PLEASE help and or let me know of any information you need to assist me further. Keep in mind though at this time the info i have access to is very limited because of the access i dont have to the phone.
lessthansavy said:
Hi all. New poster and completely non-tech savy. Over the last few days I've been tinkering with my phone trying to learn about various roms and related. I had successfully flashed the CM11 update to my droid X but found that the OS was running extremely slow. example ( while trying to talk through hangouts it would take 2-3 seconds for each letter to not only to show up but also register so I could type my next letter.) This having been the case I tried to downgrade the OS to stock or some older rom. Since going through the steps I find myself in alot of trouble! I am now able to load stock recovery and bootloader only! I am unable to get into Twrp or CWM at all. The phone if loaded regularly will only go as far as the Motorola logo and no further. It will stay on that logo until the battery is taken out. I am unable to power down or reboot otherwise. Unfortunatley I am unable to supply official information like Build and the related but I can say before flashed to CM11 it was the standard Droid X 2.3.4.621 M810 and the CM 11 build was the most recent CM 11 (shadow) build as of 5/18/2015. I need help to load into Twrp or whatever I can do to just load past the motorola logo screen. Oh lastly, I have installed the Motorola Driver program but my computer doesnt seem to be able to find the connection. It does show on device manager and states it is fully upto date driver wise. However it isnt found in RSD Lite run as admin. PLEASE help and or let me know of any information you need to assist me further. Keep in mind though at this time the info i have access to is very limited because of the access i dont have to the phone.
Click to expand...
Click to collapse
See my
Using RSD Lite to flash a .SBF to restore (Stock Rom)
on Droid X (Shadow-MB810)
Sent from my XT907 using Tapatalk
Thats actually the guide I was following. Followed everything and started getting caught up at the RSD lite part. Tried all the provided solutions but phone still isn't found by RSD lite. Please help me get over that hump. Hoping it will be all down hill from there. Device manager is showing phone as "Motorola USB Device > Motorola Flash Interface" Not what your guide shows. Have tried updating drivers from manager but it claims I have the most up to date. Using Windows 8.1 dont know if thats relevant, Thanks for the help btw.
OMG! I DID IT!!! Thanks for the help. After searching for an answer/fix for DAYS I figured it out. Your Guide is AWESOME and very helpful but the one thing it didn't mention which is what I did to make it all finally work was to download VMplayer and do everything in a Windows 7 OS. You might want to add that to your guide as a troubleshooting step. Otherwise, THANK YOU!!!