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 downloaded rom manager and bootstrap on my droid x. I downloaded flyx rom and then after it was suppose to apply it after it booted, it became stuck on the logo, going from the "droid to red eye" over and over until I pull the battery. So every time I turn it on it does the same thing. I then tried to wipe my phone by putting it into recovery mode. It says can't open/cache/recovery/command. I tried to figure out the rsdlite solution but I couldn't figure out or find a good explanation on how to use it. My bootloader is 30.04. If there is an answer to this in this forum any where please point me to it.
flyx is an ancient rom for older version of android.
if doing a factory reset doesnt help, i suggest sbf. instructions here http://forum.xda-developers.com/showpost.php?p=11118819&postcount=2
Ok thanks, I thought I knew what I was doing but i'm pretty positive i failed ...I'll try this out then.
you're welcome. if you need any help with sbf or anything, dont hesitate to ask.
Hi guys, you are my last hope!
Bought my Defy early 2011 and regularily updated with custom ROMs, so you could say I know a thing about rooting, RSD Lite, fixed sbfs, ...
Or at least I though I knew, but I still managed to kill my phone I think.
Here's what happend:
I tried to install Epsylon3s nightly from may 8th (http://defy.wdscript.fr/defy-cm9/). Before that, I was on CM 7.1
After installing the zip and rebooting, I saw the bootlogo, then i was asked for my pin code. As soon as i entered it, again to the bootlogo, again the pin, and so on.
So i realized something was wrong.
Could not get into recovery, so I flashed
JORDN_U3_97.21.51.sbf
as this often helped me in the past.
I then tried this one:
http://forum.xda-developers.com/showthread.php?t=1498843
Also didn't start.
So back to
JORDN_U3_97.21.51.sbf
But here it might be, that I misclicked (I have quite some SBFs in that folder, cause I wanted to be prepared in case something went wrong), as after that, I never got my Defy to work again.
I was stuck at the Motorola M logo.
Coudln't get into recovery, so no zips for me anymore, only flashing of sfb.
That's basically when I entered panic mode. As I didn't know what I just flashed, I could only guess the problem. So I tried the Ginger2Froyo (http://forum.xda-developers.com/showthread.php?t=1486731) in case I went to BL6. Also tried http://forum.xda-developers.com/showthread.php?t=1552152
But in this process, my RSD Lite started to behave strange:
when flashing, it's building the image, uploads it, checks checksum. But once it says "rebooting" it immediately jumps to 100% and pass. Phone how ever stays black and white LED.
Of course I can still flash other SBFs, and I tried various (JRDNEM_U3_3.4.3-36-1.7. sbf for example). But I either get the instant PASS, which tells me something didn't work, or sometimes I get the neverending bootlogo and RSD telling me to start the phone manually.
So... that's my story.
I can't seem to find a single SBF that would work for me. I screwed up big time.
To make this clear: at this point I don't care about downgradeability or anything thelike. Whatever makes my Defy work again, is fine. Froyo, Ginger, ICS, or whatever.
So if anybody still has any advice for me, I'll love you forever! Promise!
Thanks a lot in advance for any help you sure will offer,
Clock
Try this if you haven't :
Go into stock recovery and make a factory reset
Sent from my MB526 using XDA App
As I said, i cannot even enter recovery.
I'd be really happy to find an sbf, that at least lets me reset my phone.
Have u tried this thread:
http://forum.xda-developers.com/showthread.php?t=1486731&highlight=bl6+downgrade
Clock1999 said:
As I said, i cannot even enter recovery.
I'd be really happy to find an sbf, that at least lets me reset my phone.
Click to expand...
Click to collapse
Im sorry , thought you mean custom recovery when you say you can't enter recovery.
I was in the nearly same situation but i never changed my bootloader...., by me out works to power up my phone with pressed volume button down to enter stock recovery ...
So I'm sorry i couldn't help you
Sent from my MB526 using XDA App
You just like to play with your defy, don't ya
Have you tried the suggestions under Common problems/questions in this guide?
Thanks for all the responses.
However all the guides seem to point to two options only:
1) Flash this one Eclair (which I already mentioned that I did, that it used to work, but since the "instant 100% on rebooting" doesn't anymore.
2) Factory Reset/Wipe. Which I cannot, as I don't get into Recovery Mode. All I can do atm, is flash SBFs. Defy won't enter Recovery Mode (which I guess is a pretty bad sign)
But the way I always understood it, was that you only need to be careful what you install, so you don't lose downgradeability. And that, once lost, you wouldn't be able to flash "older" roms, but newer ones would always be possible.
So shouldn't there always be a rom, that saves me?
What about Defy+ roms? Any advice on that? Which best to try first? So far, I haven't touched Defy+ roms at all.
Thanks for the support!
Did you try this:
When Off, press Vol. down and power.
You'll get an exclamation mark inside a triangle.
Press both Vol. up and down at the same time.
Now you suppose to be in stock recovery and you can do factory reset.
Do the above after flashing stock SBF.
Hello again!
In the meantime, I flashed some 30 different SBFs, and at least I learned something:
when the bootloader verson is 6, I get stuck at Motorola Logo. I can enter bootloader mode, but not Stock Recovery.
When bootloader is below 6, RSD Lite doesn't get the Dey to reboot, but shows instant 100% PASS.
Okay, maybe this was to be expected, but I didn't realize how very similar sounding ROMs have very different bootloaders...
So: can anybody guide me on whether installing a BL7 ROM would repair my problem?
I read elsewhere, that my green lense definitely will not work. Is this true, or are there fixes? And if it's true: if I'm sure the rest will be working again, I'll take that. If I just rob myself of future chances, I'll pass.
And hints here?
Thanks in advance so much! One week without a phone is pure horror!
Clock
If you haven't flashed BL7, then check this http://forum.xda-developers.com/showthread.php?t=1486731&highlight=bl6+downgrade&page=2
Clock1999 said:
Hello again!
In the meantime, I flashed some 30 different SBFs, and at least I learned something:
when the bootloader verson is 6, I get stuck at Motorola Logo. I can enter bootloader mode, but not Stock Recovery.
When bootloader is below 6, RSD Lite doesn't get the Dey to reboot, but shows instant 100% PASS.
Okay, maybe this was to be expected, but I didn't realize how very similar sounding ROMs have very different bootloaders...
So: can anybody guide me on whether installing a BL7 ROM would repair my problem?
I read elsewhere, that my green lense definitely will not work. Is this true, or are there fixes? And if it's true: if I'm sure the rest will be working again, I'll take that. If I just rob myself of future chances, I'll pass.
And hints here?
Thanks in advance so much! One week without a phone is pure horror!
Clock
Click to expand...
Click to collapse
If you flash any of the defy+ roms, camera won't work..there isn't a fix or patch for that..
Doesn't matter from where I send it, what matters is written above
corrinti said:
If you haven't flashed BL7, then check this http://forum.xda-developers.com/showthread.php?t=1486731&highlight=bl6+downgrade&page=2
Click to expand...
Click to collapse
Hi,
as I mentioned above, I already tried this ROM but it gives me the same result as all the others: stuck at bootlogo.
Maybe there is a special trick on which ROM I should flash before flashing this one?
Sorry, I do not know how to help. Just no idea now, try to dig the forum.
Once I had very similar problem - whatever I flashed I was stuck at bootlogo. And in my case I found out that just before flash my internal memory had been filled with some mess, which was not removed by any wipes (cache, dalvik cache, cache partition) and after any flash memory was too filled to start the system.
But finally I could flash Chinese eclair (CG5), which at last started horribly laggy, and I could wipe private data from a system - it gave me more than 1GB of internal memory back (from 40MB after all wipes and clean system install) and a way to flash whatever I wanted without a problem.
So even if it is also your problem, my way is not available to you now. Maybe you can find as small sbf file as possible and try then.
I'm sorry, but I don't quite get, which ROM saved you, and why that is no option to me. Can you please clearify? Thanks a lot!
Clock1999 said:
I'm sorry, but I don't quite get, which ROM saved you, and why that is no option to me. Can you please clearify? Thanks a lot!
Click to expand...
Click to collapse
I could use CG5 full sbf which will not boot for you as you put BL6 and maybe BL7.
To boot from flashed sbf it cannot be lower BL version.
I suppose that now you have a memory problem - flashing sbf do not wipe the memory.
At first I would try getting into stock recovery (even several times, just pull battery out, wait a minute, power, vol -, battery in) - if successful then do a factory reset and reboot.
If not I would try to find out a smallest sbf with proper BL version - just to give it more chance to boot with small memory available, if not then again try to get into stock recovery.
I'm the happiest guy around, as I finally revitalized my Defy.
For all you guys, who already tried everything: here's what worked for me.
Just let it rest a few days.
After I hadn't touched my phone for a couple of days, I thought about giving it one last try. So I flashed the Defy+ SBF (4th in this list: http://sbf.droid-developers.org/umts_jordanplus/list.php), like I've done multiple times before.
But this time, when rebooting, I wasn't stuck at the M-logo, but in a bootloop. And that gave me the smiles as I knew, that now I should be able to enter Stock Recovery again. From there on, it was no problem to get to a stable base again. After flashing the BL6 Froyo, I'm now on CM9 and everything is fine.
Thanks for all you help.
Sometimes, you just have to give it a rest...
Clock
It is a next such case I see in moto forums ;-) but it is really hard to give a tip: leave it for few days and check again
Use the sbf_flash for Linux
Sent from my MB526 using Tapatalk 2
Very long story short, I got a new phone, tried to install a custom ROM onto it, screwed up during the process, then found out that this phone won't work on my cell network as it is an international phone, not a US phone. I've spent the better part of my week trying to fix this phone so I can get it refunded and buy a phone that works on US networks.
With all the effort I've put into this, I've managed to get it where it'll reach a loading screen, but it gets stuck on it. Anything and everything that I have tried so far has yet to work for me.
Any help would be much appreciated.
Edit: Somehow didn't think to specify model. Moto G7 XT1962-6.
I have tried a factory reset multiple times, not working for me.
I have tried flashing both a custom ROM and the stock ROM, very limited success. At one point I got the custom ROM working, but I need the stock ROM on it so that I'd better qualify for getting the phone refunded.
At the moment, it is stuck on a boot loop where it loads up to a custom loading screen, not the stock loading screen, and it stays there without any progress. Before, it would just loop the "this device is unlocked" screen.
If you specify what phone it is, you might get more users who can help
@CaptainNurbles
Already tried a Factory Reset ?
mattgyver said:
If you specify what phone it is, you might get more users who can help
Click to expand...
Click to collapse
Apologies! In my stress I completely forgot to mention it. It is a Moto G7 XT1962-6.
jwoegerbauer said:
@CaptainNurbles
Already tried a Factory Reset ?
Click to expand...
Click to collapse
Multiple times to no avail.
CaptainNurbles said:
Apologies! In my stress I completely forgot to mention it. It is a Moto G7 XT1962-6.
Click to expand...
Click to collapse
Moved to the Moto G7 Q&A subforum.
Here's a link to the stock rom(as long as My Google-Fu is still on point): https://motostockrom.com/motorola-moto-g7-xt1962-6
mattgyver said:
Moved to the Moto G7 Q&A subforum.
Here's a link to the stock rom(as long as My Google-Fu is still on point): https://motostockrom.com/motorola-moto-g7-xt1962-6
Click to expand...
Click to collapse
The weird thing is, I've been to this site and I've downloaded this before, didn't work before. For some reason though it worked this time! Many thanks, pal!