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!
Related
So i have a roted droid x running rubix 1.9.0. I went back all the way to stock 2.2.1 so i could do the ota from verizon. downloaded it and installed it and was good. when my phone was rebooted by the download, i went back to rooting it with z4. i am not a noob but in no way an expert and was occupied with something else at the moment and didnt think about what i was doing and flashed a backup of exactly what i was running before the update. now i cant figure out how to get back to 2.3.340 on my phone. am i going to have to wait until a sbf file comes out for it because now in my about phone it reads like the photo i posted. now i dont know if i can go back because i never made a backup after i installed the ota and all the backups i have are from 2.2.1. and im pretty sure ill brick my phone if i sbf back to 2.2 through rsd lite. so now im not sure what i can or should do if i have any options or not or if i have to wait for a real 2.3.340 sbf.
please help!!!! thanks
im dumb and figured out everything.....but i love to learn and figure things out....reading and trying things out from this site deserves all the thanks!!
Post your fix
Post your fix "Always" so if anyone has the same problem, they will have the answer.
Thanks
spywiz said:
Post your fix "Always" so if anyone has the same problem, they will have the answer.
Thanks
Click to expand...
Click to collapse
no problem....i was able to do everything that TBH had shown
mydroidworld.com/forums/droid-x-discussion/5789-tbh-patches-2-3-340-system-baseband-2-3-340-kernel-bootloader.html
i just cleared data/cache and then went into clockwork and applied the 2.3.340 system updater and i was back to stock. now ive gone back to root and already am rocking out with tranq 3.6.0 thanks TBH!!!
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.
Ok guys, I have a good one for you. Tuesday I SBF'd my phone from my version of the .340 build to the factory VRZ_MB810_2.3.34_1FF_01 build that's on here. Reasoning was that I wanted to play with the OTA update to 2.3 and I was rooted and running Rubix 2.0 on it at the time.
That went fine and the OTA went without a hitch as well.
Now comes the fun part. Being the tinkerer that I am, I decided that I couldn't live without root access so I decided today that I would just SBF back to the VRZ_MB810_2.3.34_1FF_01 build and I was going to flash P3Droid's rooted GB release.
So I ran RSD, located my sbf file just I like I had, put the phone into bootloader (30.04 didn't change with the update) Let th SBF do it's work and now I'm bootlooping...
I wondered if this was just a Windows issue because I had to SBF a few times the other day just to get it to work. With that in mind, I exited my Windows virtual machine and tried it on my Linux box but to no avail.
I'm running out of options here...
Ideas?
Laramie1997 said:
Ok guys, I have a good one for you. Tuesday I SBF'd my phone from my version of the .340 build to the factory VRZ_MB810_2.3.34_1FF_01 build that's on here. Reasoning was that I wanted to play with the OTA update to 2.3 and I was rooted and running Rubix 2.0 on it at the time.
That went fine and the OTA went without a hitch as well.
Now comes the fun part. Being the tinkerer that I am, I decided that I couldn't live without root access so I decided today that I would just SBF back to the VRZ_MB810_2.3.34_1FF_01 build and I was going to flash P3Droid's rooted GB release.
So I ran RSD, located my sbf file just I like I had, put the phone into bootloader (30.04 didn't change with the update) Let th SBF do it's work and now I'm bootlooping...
I wondered if this was just a Windows issue because I had to SBF a few times the other day just to get it to work. With that in mind, I exited my Windows virtual machine and tried it on my Linux box but to no avail.
I'm running out of options here...
Ideas?
Click to expand...
Click to collapse
Boot into stock recovery and do a factory reset...
Sent from my DROIDX using XDA App
Nope, can't do that. There isn't a recovery to go back to. I don't have clockworks on this phone anymore.
Laramie1997 said:
Nope, can't do that. There isn't a recovery to go back to. I don't have clockworks on this phone anymore.
Click to expand...
Click to collapse
Its stock recovery...power off phone and then hold power and home button until you get the Android with the exclamation point. Then hit the search button
Sent from my DROIDX using XDA App
That wasn't quite what I was looking for since I don't have /sdcard/update.zip still on the card anymore. What IT DID allow me to get in and do was wipe cache which allowed a clean SBF.
THANKS!
Ok so as my previous post stated I just got my droid x and rooted it. I am in the process of installing a rom but have failed at this point.
For starters I have the droid x bootstrap installed and "running". Buy "running" I mean I can get to the clockwork recovery but only buy the bootstrap button or battery pull for 1min then boot. Booting while holding the home button stops at the exclamation android guy. I cant get past it no matter how hard I push the search button . So thats one of my problems but not a big one.
When I went to install liberty 1.5 I did a data factory reset and catch wipe then installed the rom. It got stuck on the liberty logo. So I tried again this time following the guide on these forms on how to install a rom correctly. Same thing. I tried three more times following three different guides and still was stuck at the liberty logo. So I gave up and followed the install guide on these forms again, but just restored from my backup. I am good and running again but I still have the liberty logo, which from what I read is normal.
When I got home from work I started digging into why it didn't work and found several things that may cause it. Now this is where I get lost. I have read the sometimes it just fails and you need to try again. But I also read the doing a SBF will also fix this. So I dug into what a SBF is and how to do it since this seams to be the #1 fix for everything. WHAT, UHH, MMMMM, K. So I read you will need to flash 2 files to SBF successfully. I have no problems with the RSD lite as it is only one file and you cant screw that up. But then I comes to choosing the right SBF file for your phone I get lost. All the versions listed are WAY below what I have. I am currently on 4.5.588. So I jumped over to androidforms to see if theirs anything their. They list x.x.596 as the most recent OTA but when I go to check for updates it says there are none.
SO, my questions are:
Is the reason I cant flash the liberty rom because I am running 4.5.588?
What do I flash if I need to SBF?
What am I missing about this OTA update? Is it being rolled out now or is my rom the most recent OTA?
Is their anything else I need to know that might help me in the future? Like I said I am new to this area of the forms and have not clew whats being released, changed, rooted, or what ever else.
I came from a rooted eris so Im not root dumb. But their is a big difference between the eris and the X.
ANY HELP WOULD BE AWESOME THANKS!!!!!!!!
BrownEye02 said:
Ok so as my previous post stated I just got my droid x and rooted it. I am in the process of installing a rom but have failed at this point.
For starters I have the droid x bootstrap installed and "running". Buy "running" I mean I can get to the clockwork recovery but only buy the bootstrap button or battery pull for 1min then boot. Booting while holding the home button stops at the exclamation android guy. I cant get past it no matter how hard I push the search button . So thats one of my problems but not a big one.
When I went to install liberty 1.5 I did a data factory reset and catch wipe then installed the rom. It got stuck on the liberty logo. So I tried again this time following the guide on these forms on how to install a rom correctly. Same thing. I tried three more times following three different guides and still was stuck at the liberty logo. So I gave up and followed the install guide on these forms again, but just restored from my backup. I am good and running again but I still have the liberty logo, which from what I read is normal.
When I got home from work I started digging into why it didn't work and found several things that may cause it. Now this is where I get lost. I have read the sometimes it just fails and you need to try again. But I also read the doing a SBF will also fix this. So I dug into what a SBF is and how to do it since this seams to be the #1 fix for everything. WHAT, UHH, MMMMM, K. So I read you will need to flash 2 files to SBF successfully. I have no problems with the RSD lite as it is only one file and you cant screw that up. But then I comes to choosing the right SBF file for your phone I get lost. All the versions listed are WAY below what I have. I am currently on 4.5.588. So I jumped over to androidforms to see if theirs anything their. They list x.x.596 as the most recent OTA but when I go to check for updates it says there are none.
SO, my questions are:
Is the reason I cant flash the liberty rom because I am running 4.5.588?
What do I flash if I need to SBF?
What am I missing about this OTA update? Is it being rolled out now or is my rom the most recent OTA?
Is their anything else I need to know that might help me in the future? Like I said I am new to this area of the forms and have not clew whats being released, changed, rooted, or what ever else.
I came from a rooted eris so Im not root dumb. But their is a big difference between the eris and the X.
ANY HELP WOULD BE AWESOME THANKS!!!!!!!!
Click to expand...
Click to collapse
im no pro but hopefully this info will help you, it did me.
http://forum.xda-developers.com/showthread.php?t=1073841 liberty info
http://forum.xda-developers.com/showthread.php?t=1085323 sbf'ing
The new 2.3.3 OTA is stable and very nice looking on my DX, OTA not rootable yet but give it time.
Biggest life saver about the DX is the the part of the phone that ppl mess up and turn their phones to bricks is extremely safe on the X, not bulletproof but all the info in these forums I believe can bring them back regardless of what happens. I was very overwhelmed at first with my X but very comfortable now that ive successfully managed the sbf.
Yeah that's one of the things I really noticed. If you brick your phone it seams its not the end. So im still a little confused with your explanation on SBFing. You say that 2.3.3 is the latest OTA but its not rootable. So am I looking at the wrong number when I say my version is 4.5.588.
Sent from my Rooted DROIDX.
Reading the noobs guide to droid x allowed me to figure out that I have the 30.04 bootloader and I will need to flash the 2.3.34 file. But I would still like to know why my version is so much higher then 2.3.34.
By far, this is the easiest way to sbf back to stock froyo
http://www.droidxforums.com/forum/d...-solution-your-windows-rsd-lite-problems.html
Sent from my Xoom using XDA Premium App
chbennett said:
By far, this is the easiest way to sbf back to stock froyo
http://www.droidxforums.com/forum/d...-solution-your-windows-rsd-lite-problems.html
Sent from my Xoom using XDA Premium App
Click to expand...
Click to collapse
WOW that is easy. To bad you cant select what version it flashes. But still EASY. Ill keep that in mind if I need to SBF. THANKS!
http://droidmodderx.wordpress.com/how-to-sbf-your-droid-x-full-2-3-340/
Good video tutorial there... It also has files there as well
Sent from my DROIDX using XDA App
Well I gave liberty 1.5 another try and it still got stuck on the liberty screen. Any ideas?
Sent from my Rooted DROIDX.
Was able to flash the liberty gingerbread rom tonight! I am kind of wondering if the version of ota/bootloader I have is the reason liberty 1.5 wouldn't work for me.
BrownEye02 said:
Reading the noobs guide to droid x allowed me to figure out that I have the 30.04 bootloader and I will need to flash the 2.3.34 file. But I would still like to know why my version is so much higher then 2.3.34.
Click to expand...
Click to collapse
your looking at the version of the software build, complete jargon here but say your on android 2.2.1 version blah blah blah, what i was referring to was although you may have a higher version of 2.2.1 than what you are reading, a lower version of a higher android software such as 2.3.3 is better than a higher version of 2.2.1 same page?
I've been running Liberty on my Droid X for some time now and love it compared to the stock Blur interface. But it's gotten to the point where I'd like to update from Froyo to one of the more modern versions and see if that can liven up the phone again. So my question is this - from what I've read before I can update Liberty (or any other ROM for that matter) from a Froyo based version I need to restore the phone to a semi-stock state, update via an official OTA release, re-root and go from there. Is that true? If so, any convenient guide on how to do so? I did a bit of searching and couldn't find much and while I'm pretty technically inclined my skills do not extend into the phone region and back when I originally modified the phone there were many handy guides and videos to walk me through it.
Any help would be greatly appreciated.
Nate
If your bootloader version is 30.04, SBF to 4.5.602. From there you can flash any Gingerbread or ICS rom of your choice.
If your bootloader version is 30.03, SBF to 2.3.15 and take the OTA update.
Sent from my Transformer TF101 using Tapatalk
Let the stupid questions begin...
Ok, I confirmed that I'm running 30.04 and I found a site that maintains the correct 4.5.602 file so I downloaded that. Is there anything that I need to back up before installing? Also, I read that a special program is required to install the SBF files so any assistance there would be appreciated as well.
Thanks!
Ok, so I managed to track down RSD-Lite and got it to recognize the device and start loading the sbf file however the phone couldn't get past the "manually power up the phone" phase (or something like that). It just kept showing the boot animation over and over again regardless of what I did - it would cycle between the red eye and the DROID text. I tried pushing and holding the power button, no good and none of the other buttons did anything either. Nothing worked. So I'm rerunning it again and we'll see if the second time is a charm...
Well crap, I got through the SBF install process and got the pass message from RSD but now my phone is stuck at the animation and won't go any further. I've left it running for the better part of 10 minutes and it just hangs. I'm now performing a manual factory data wipe to see if that will help.
EDIT: It appears that the factory data wipe got me through the locked animation. Still having minor issues getting through the programing and setup phase but I think it'll work eventually.
Thanks again for the help.
infazzdar said:
If your bootloader version is 30.04, SBF to 4.5.602. From there you can flash any Gingerbread or ICS rom of your choice.
If your bootloader version is 30.03, SBF to 2.3.15 and take the OTA update.
Sent from my Transformer TF101 using Tapatalk
Click to expand...
Click to collapse
Minor question/problem for you, sir.
Wouldn't the OTA take you all the way to .621?
Wonderful...yet another thing we need to worry about that damn update <_<
OP:
Glad you got it worked out.
Well, it's sort of worked out.
Everything is up and running but ROM Toolbox isn't able to load any ROMs. It gets granted Superuser permission so I'm pretty sure that I've got the X rooted correctly but when it tries to boot into Clockwork it appears to get an error (icon with an exclamation point) and reboots into the regular Blur interface. I'm going to have a go at loading something like Liberty Gingerbread or 3.0 via zip file but it makes me nervous that the Toolbox Pro App can't get this done.
After determining that the Toolbox App was not booting into Clockwork I downloaded and installed the Droid X Bootstrapper App and got that running. It was able to correctly boot into recovery from which allowed me to install the Liberty 3 ROM. I'm now going back through the process of setting the phone up with the new ROM so we'll see how that goes. It appears to be working, but only time will tell if it's stable. One thing is for sure, a few hours on Blur'd Gingerbread and I was ready for something else again.
Jubakuba said:
Minor question/problem for you, sir.
Wouldn't the OTA take you all the way to .621?
Wonderful...yet another thing we need to worry about that damn update <_<
OP:
Glad you got it worked out.
Click to expand...
Click to collapse
I was actually wondering whether it would or not, but I can't think of another way to update the bootloader.
Sent from my DROIDX using Tapatalk
Ok, so here's an issue that I'd appreciate some guidance on. After installing Liberty 3.0 it appears as if the phone can't fully charge. It was plugged in for 10hrs last night and yet this morning the battery only reads 61%. I don't know if it would be best to boot into recovery and wipe the battery stats not knowing if it's fully charged or not.
Thoughts?