My DX is on the OTA 2.3.340 with 30.04 bootloader, rooted with Droid X Bootstrap. The touch screen stops responding randomly and I want to restore it to factory to see if it fixes it. If not I'll return it to VZW. Whats the best way to do this? SBF with RSDlite or use Maderstcok or ...?
tr6coug said:
My DX is on the OTA 2.3.340 with 30.04 bootloader, rooted with Droid X Bootstrap. The touch screen stops responding randomly and I want to restore it to factory to see if it fixes it. If not I'll return it to VZW. Whats the best way to do this? SBF with RSDlite or use Maderstcok or ...?
Click to expand...
Click to collapse
It's really your choice. Some will say RSD Lite, some will say maderstcok. If you don't want to do neither, just do a factory reset from the phone and see if that solves your problem, just make sure to un-root first. Using the maderstcok, make sure you re-name the file to the official VZW file like a full system 340 file that you would use with RSD Lite before taking it back to VZW.
Personally, RSD Lite is easy and it's what Motorola's techs use as a tool. It wipes and flashes everything so you know you are starting with a clean slate. Maderstcok is for ease of use so you can do the same thing as RSD Lite does but with no computer.
Maderstock is easier, but if you sbf it will unroot and get rid of superuser icon and bootstrapper, iwould sbf before I took it to vzw. You could always try madEratock first to see if it resolves your problem.
Sent from my DROIDX using XDA App
OK. Just did the 2.3.340 SBF with RSDlite. Hopefully this fixes it. Thanks.
The 2.3.340 SBF did nothing to fix the touch screen problem. What did fix it was doing a factory data reset from the privacy settings menu.
Related
Exactly what the title says, I need to do an exchange for a blown earpiece speaker, but the guy said I need to unroot first, otherwise his store will get a 'chargeback' (nice guy imo)
Can somebody provide me with instructions?
Are you aware how to sbf your phone? Best way to get rid of everything in my opinion
I looked up the files for SBF, but not sure if i have the right ones for .340
kinda stuck atm... got a few files i downloaded, not sure where to go from here
just used RSD LITE and the latest SBF to reload my phone.. and i still have root and clockwork.. lol
You must not have done it properly. Before you flash your phone, in clockword mod makes sure to do a factory reset and also wipe cache. You can find the sbf from mydroidworld
anom69 said:
just used RSD LITE and the latest SBF to reload my phone.. and i still have root and clockwork.. lol
Click to expand...
Click to collapse
Loading the SBF by itself will not unroot your phone. After that process completes, power off the phone and enter Motorola's recovery by holding Home while turning the phone. Hold Home + Power until the Motorola logo comes up, then release Power and keep holding Home. Once you get a folder icon with an "!". Press the Search button, and do a factory reset/format cache. Once the phone comes back up, all of your data, and more importantly the root, will be gone.
-Edited to correct the key combination needed-
I am pretty certain the SBF files for .320 and the .340 Patch are already rooted.
Factory reset won't take that away.
I Don't think a 'True' SBF for .340 has been released (and likely won't be).
Zaphod-Beeblebrox said:
I am pretty certain the SBF files for .320 and the .340 Patch are already rooted.
Factory reset won't take that away.
I Don't think a 'True' SBF for .340 has been released (and likely won't be).
Click to expand...
Click to collapse
The files released by TBH are not rooted. I've used them several times, and I always had to run z4root to regain root access afterwards.
Used Boot Straper from Market flashed .320 from .315 everything went correctly verified update in settings. Booted with bootstraper again cleared all the partitions like cache installed
2.3.340 Kernel Updater (2.6.32.9-g55626e1) .zip
BP_C_1.09.07P Baseband Updater .zip
2.3.340 System Updater .zip
ApeX 1.3.1 .zip
note none where sbf files rebooted the system and im stuck in bootleader and reads
Bootloader
30.04
err:A5,69,35,00,27
Battery OK
OK to Program
USB connected
Data Cable
Nothing I do can avoid botloader. After Finaly getting RSD Loader 4.9 to reconize my device I tried to cure it by flashing Droid Life 2.3.340 .sbf file and RSD give err 0x700
Try the .320 SBF, then .340 SBF. If that fails you will have to wait until you can get a hold of the next full SBF.
I went to a new computer and I flashed .15 SBF I belive full bc it was like 400mb with success on flash but my cute little android man pissing on craple is gone and boots immedieately into BL saying no system. So Now flashing .340 SBF and see what happens. If this don't work I am fresh out of ideas
That won't work. Flash the full .320 SBF then the system only .340 SBF and you'll be fine.
mlclm said:
That won't work. Flash the full .320 SBF then the system only .340 SBF and you'll be fine.
Click to expand...
Click to collapse
This worked for me. You should do it this way.
Sent from my DROIDX using XDA App
iceblue11 said:
I went to a new computer and I flashed .15 SBF I belive full bc it was like 400mb with success on flash but my cute little android man pissing on craple is gone and boots immedieately into BL saying no system. So Now flashing .340 SBF and see what happens. If this don't work I am fresh out of ideas
Click to expand...
Click to collapse
If you are on stock 2.3.15 now, then just go to Settings>About Phone>System Updates. This should do the OTA update and bring you to 2.3.340. No Need to flash the 2.3.320 full sbf and then the 2.3.340 sbf.
Your right that won't work. Its stuck in loader so no system will boot. So I need to go find the 320 sbf in order to get out of this. I'm asuming its the 30.04 bootloader preventing the 315 sbf from bringing me out and why the 340 system sbf won't rescue me. Ok ill try it thanks
iceblue11 said:
Your right that won't work. Its stuck in loader so no system will boot. So I need to go find the 320 sbf in order to get out of this. I'm asuming its the 3040 bootloader preventing the 315 sbf from bringing me out and why the 340 system sbf won't rescue me. Ok ill try it thanks
Click to expand...
Click to collapse
Yeah, I think I remember reading if you have 30.04 bootloader, the 2.3.15 sbf will not work, but I can't remember for sure.
To check what bootloader you have, power off your phone. Now press and hold both volume keys; keep pressing the volume keys as you power the phone back up. The phone will proceed to enter bootloader mode and show you what bootloader you have.
Sorry for the pore responses and spelling. I was sneaking posts at the Verizon store while fighting with the manager to please charge my battery so I could flash my phone. Battery died on me apparently it will not accept any type of charge from the phone when stuck in boot loader.
bouchigo - Thanks you been a big help bud, Finally! Someone says how to put the X into that bootloader I couldn't figure it out so went with the clockworks .zip 340 system flash instead of the sbf. Had to google for the 320.sbf couldn't find much on here for this so it is downloading now and see what happens after that. I did find during my search that if the bootload was 30.04 the phone would not accept a 315 system so that is indeed accurate.
mlclm - Thank you
w00t phone just booted out of the dead with the 320.sbf!
Curious thing is what in my method caused the phone to do this?
Well no matter if im on 320 or 340 the phone wont activate over air programming and thus cant go anywhere past that damn droid icon, coincidence of bad timing was an outage in service on my area life is peachy now
iceblue11 said:
w00t phone just booted out of the dead with the 320.sbf!
Curious thing is what in my method caused the phone to do this?
Well no matter if im on 320 or 340 the phone wont activate over air programming and thus cant go anywhere past that damn droid icon
Click to expand...
Click to collapse
Strange. I have had the ota programming fail and I had the option to skip. Then open dialer and do *22899 to program.
Sent from my DROIDX using XDA App
iceblue11 said:
w00t phone just booted out of the dead with the 320.sbf!
Curious thing is what in my method caused the phone to do this?
Well no matter if im on 320 or 340 the phone wont activate over air programming and thus cant go anywhere past that damn droid icon
Click to expand...
Click to collapse
Try doing a "data/factory reset" and "wipe cache", after that reboot and see if fixes your problem.
1. Power off your phone
2. Press and hold the home key (the button with the little house on it).
3. While holding the home button down, power up the phone. Once phone starts to power up, you can let go of the power button, but keep holding the home button until you see a triangle with an exclamation mark in the middle with a little android underneath the triangle.
4. Now, press the search button (the magnifying glass button).
5. Scroll to "wipe data/factory reset" (with the volume up and down buttons) and select it with the camera button.
6. Now scroll to "wipe cache partition" and do the same as you did previously.
7. Reboot and hope it solved your problem.
Yeah I did all that to try and skip the programming. I could do emergency dial and do *22898 and get to customer rep who found a outage in my area after that was fixer the phone programmed like it should and all was good.
Im about to post on Apex thread about a small issue. But all together the setup is working so much better faster cleaner then the old setup so 5 *'s.
For some reason if you hold power button and select restart the phone will boot into clockworks recovery every time. Uninstalled clockworks app and still does it. And currently have 2 SMS apps and wont let me uninstall any of them and its causing all SMS to be duplicated. Only bugs so far
iceblue11 said:
Yeah I did all that to try and skip the programming. I could do emergency dial and do *22898 and get to customer rep who found a outage in my area after that was fixer the phone programmed like it should and all was good.
Im about to post on Apex thread about a small issue. But all together the setup is working so much better faster cleaner then the old setup so 5 *'s.
For some reason if you hold power button and select restart the phone will boot into clockworks recovery every time. Uninstalled clockworks app and still does it. And currently have 2 SMS apps and wont let me uninstall any of them and its causing all SMS to be duplicated. Only bugs so far
Click to expand...
Click to collapse
I had that service problem too when I SBF'd. When I was on .15 I tried to use the
system updater on droid world (stupidly) to .340 and the patches. So after I got
stuck on the bootloader like you did, I just SBF'd to .320 and then went back
to droid world and then installed the system updater (.340) with bootstrap and
then the following patches. I had to go outside to get at least one bar of service
in order to activate the phone. After about 20 minutes or so I started getting
signal back the way it was before. I *228 again a few times to get rid of the
roaming icon. Sometimes it takes a few programs to get you to the correct towers.
Here's the droid world thread.
http://www.mydroidworld.com/forums/...ystem-baseband-2-3-340-kernel-bootloader.html
Note: I of course activated the phone before using the system updater and patches.
Gain your signal back first before you get onto .340
iceblue11 said:
Yeah I did all that to try and skip the programming. I could do emergency dial and do *22898 and get to customer rep who found a outage in my area after that was fixer the phone programmed like it should and all was good.
Im about to post on Apex thread about a small issue. But all together the setup is working so much better faster cleaner then the old setup so 5 *'s.
For some reason if you hold power button and select restart the phone will boot into clockworks recovery every time. Uninstalled clockworks app and still does it. And currently have 2 SMS apps and wont let me uninstall any of them and its causing all SMS to be duplicated. Only bugs so far
Click to expand...
Click to collapse
Open droid x bootstrapper and hit the bootstrap recovery button. This should stop you booting to ce everytime you restart.
Sent from my DROIDX using XDA App
So being a n00b, I forgot the ever so important unroot before I accepted the newest update to .340. I have tried everthing in the forums that I have read over the last few days. Have I forever lost my ability to root my DX?
Any help greatly appreciated! Sorry if this is in the wrong spot, I have never posted a thread b4!
Try z4root. Should root you just fine. Easily.
http://www.addictivetips.com/mobile...root-app-for-samsung-galaxy-s-android-phones/
And if you're running into any trouble using it, refer to this thread
http://forum.xda-developers.com/showthread.php?t=867694
FYI, you don't have to unroot for an OTA anyway.
O...I did not know that...I though u have to unroot for all updates...now I am even more confused. I lost my root privelages after the udate and have not been able to regain access. I have tried z4, rageagainstthecage, and a couple other methods. I am going to try using rsd lite next to flash, but some forums say this will work and others say u can not flash with the .340
SBF
could always do a 2.3.320 sbf and do the ota update again correct?
Haven't had to SBF in a while, but last I checked 2.3.320 was the last full SBF released. so while a there is a .340 System SBF if I were trying to make sure it wiped everything out of there, i'd go with the full sbf.
dnice102 said:
I am going to try using rsd lite next to flash, but some forums say this will work and others say u can not flash with the .340
Click to expand...
Click to collapse
Since you are running the newest update, (.340) make sure you don't use the 2.3.15 sbf since it will no longer work with your bootloader and your phone will be stuck until you flash a newer SBF. That is probably what you are hearing from other posts, with .340 you cant flash 2.3.15.
There are patches to go from .320 to .340, but for me, nothing is more simple than clicking accecpt update and going to make a sandwich.
If he SBF's to .320 he won't be able to get .340 with the OTA. Verizon doesn't
recognize .320 so the OTA won't happen. He can just go SBF .320 and use the
patches after that. It's what I did.
http://www.mydroidworld.com/forums/...ystem-baseband-2-3-340-kernel-bootloader.html
update.zip
ah, didn't know that, what about this?
http://forum.xda-developers.com/showthread.php?t=906191
update.zip to .340.
haven't tried this yet, just ran across it.
Thanks for everyone's help. The flash to .320 did the trick. However after the phone's battery died n I recharged, I am stuck on the motorola screen during boot. I can get into the factory recover, but that didnt help. Also, I can no longer access the bootloader. Am I permanantly bricked or is this a possible battery problem?
When you get into motorola recovery (holding the home button down until the android with triangle shows up), clear your cache and wipe data to factory. This might do the trick. You're just gonna have to add your google account again.
Sent from my DROIDX using XDA App
Yeah... I wiped the data and the cache a couple times...no luck. The device will not do anything unless its plugged in, so I am hoping its just the battery. I will find out later today!
Thanks for the support!
went to verizon. the rep said the last .340 update had corrupt files in it. they are overnighting a new phone at no charge!
thanks again for everyones help!
I got this phone from eBay as "stuck in M" and thought I might give it a try to SBF it back to stock. So I tried SBFing to 4.5.605 and it works great but after the first reboot, it boots straight to stock recovery.
I read some threads online and some mention to wipe data/cache. I do that and reboot and it still keeps going back to recovery no matter what. I have complete access to the phone with RSD Lite but I cannot get it to boot to the OS. It just keeps booting back to stock recovery.
I would really appreciate some help here. It would be great if I can get this phone working again. Am I doing something wrong? Something specific about the Droid X I'm not aware of?
open1your1eyes0 said:
I got this phone from eBay as "stuck in M" and thought I might give it a try to SBF it back to stock. So I tried SBFing to 4.5.605 and it works great but after the first reboot, it boots straight to stock recovery.
I read some threads online and some mention to wipe data/cache. I do that and reboot and it still keeps going back to recovery no matter what. I have complete access to the phone with RSD Lite but I cannot get it to boot to the OS. It just keeps booting back to stock recovery.
I would really appreciate some help here. It would be great if I can get this phone working again. Am I doing something wrong? Something specific about the Droid X I'm not aware of?
Click to expand...
Click to collapse
sounds like its bricked it is possible that your sbf file is slightly corrupted or its the wrong one altogether try redownloading the sbf file or try .602 sbf dont reboot it if you can help it root it and put a different rom on it may just solve your trouble the linux method of sbf is more sound look into that instead of rsdlite if you have to use rsdlite make sure its is the newest leaked version of the program. Always make sure the program completes to the end and it says passed. pull the battery afterwards and do a factory restore hard reset should be good to go
I must have done something wrong while trying to install a custom ROM on my phone and it became bricked. I tried to flash with RSD Lite, but I didn't realise the SBF I used was for the Defy, I have the Defy+. It flashed then the screen became blank and I couldn't turn it on, but it still connects to RSD Lite. I then found an SBF that looked promising and tried to flash it on, some text came on the screen saying what it was doing, then the flash completed and the phone reset.. then went back to blank.
Does anyone have any idea what I should do?
Would it help to go back to the original SBF? If so, where would I find it? It's an Australian Defy+ running on the Telstra network.
Have you installed CM9 karnel????
If you done this then there is only one option for you to flash DFP 231 STOCK SBF which is not rootable yet.
That means no downgrade/custom ROM via CWM recovery......
I tried installing a WIUI ROM. I can deal without root, I just want it to work.
grisher said:
I tried installing a WIUI ROM. I can deal without root, I just want it to work.
Click to expand...
Click to collapse
Download sbf from the link below and flash it via RSD lite.
Do it at your own risk. Finally post the report here...
sbf.droid-developers.org/umts_jordanplus/DEFYPLUS_U3_4.5.1-134_DFP-231_CN_SIGN_UCADEFYEMARAB1B50AA009.0R_PDS03C_USAJRDNGIBRIRD15_P015_A030_Service1FF.sbf.gz
Click to expand...
Click to collapse
grisher said:
I must have done something wrong while trying to install a custom ROM on my phone and it became bricked. I tried to flash with RSD Lite, but I didn't realise the SBF I used was for the Defy, I have the Defy+. It flashed then the screen became blank and I couldn't turn it on, but it still connects to RSD Lite. I then found an SBF that looked promising and tried to flash it on, some text came on the screen saying what it was doing, then the flash completed and the phone reset.. then went back to blank.
Does anyone have any idea what I should do?
Would it help to go back to the original SBF? If so, where would I find it? It's an Australian Defy+ running on the Telstra network.
Click to expand...
Click to collapse
Don't worry flash your original SBF. Note it Defy+ is practically almost unbrickable!!! Go here and check the SBF that suits you. Since you could root your phone earlier I am sure your SBF would have been one with DFP-891 or DFP-1231 since DFP-231 is not yet rootable. So check the link I gave you and search for the SBF that suits you. I suggest flash the SBF with DFP-891 first(if that exists in the thread. Indian version is not there!!). Now if your previous version was DFP-1231 you will again get black screen!! If you do flash DFP-1231. Do a data wipe from stock recovery and your phone now should be alive!!
Steps:
Flash SBF:
1.) After flashing or before flashing, go to stock recovery(vol down+power) do full data wipe.
Warning: Never flash SBF with DFP-231, its unrootable and has BL7!!!
parth0 said:
Have you installed CM9 karnel????
If you done this then there is only one option for you to flash DFP 231 STOCK SBF which is not rootable yet.
That means no downgrade/custom ROM via CWM recovery......
Click to expand...
Click to collapse
Nope bro its not like that!!!
@pranks1989
Thanks for the tips! I actually ended up using 2311 (I hope that it's rootable?), and it boots now and works right. The only problem I can see is that now when I go to download apps from the Play store it tells me I have insufficient space available.
grisher said:
@pranks1989
Thanks for the tips! I actually ended up using 2311 (I hope that it's rootable?), and it boots now and works right. The only problem I can see is that now when I go to download apps from the Play store it tells me I have insufficient space available.
Click to expand...
Click to collapse
Well you got the bad news!!! Its not rootable yet!! Welcome to the league! Did you do a data wipe from stock recovery?? If not try doing that and check in settings>storage how much empty space you have. If that do not work do a data wipe from stock and flash SBF again!!! Anyways you don't have many options to try since you can't even root it!!
I wiped the data/cache and now I can download apps again.
So seeing as this SBF isn't rootable is it possible to just flash another SBF that is rootable and root that or will I have to wait until my SBF is rootable?
Thanks for the help, by the way!
grisher said:
I wiped the data/cache and now I can download apps again.
So seeing as this SBF isn't rootable is it possible to just flash another SBF that is rootable and root that or will I have to wait until my SBF is rootable?
Thanks for the help, by the way!
Click to expand...
Click to collapse
You can't flash any other rootable SBF since this SBF has BL7 and all rootable SBFs had BL6! No downgrading.....! So wait