What is the difference between the first FXZ file and targa_cdma_targa-user-2.3.4-5.5.1_84_DBN-55-110814-Verizon-US.tar? The other one is 500 megs more but I'm not totally sure why since the firmware versions are the same. Do you cut a lot of the crap out?
This weekend I ripped out Backup Assistant (hate that application) with Titanium Backup but it caused a plethora of issues in various settings menus. After failing to restore it I decided the best thing to do was to re-flash it back to factory using the giant FXZ I mentioned above. Now I see this post and a much smaller FXZ file and I am wondering if I should do it again with the smaller file... what would I gain from it (or lose.... like freaking backup assistant).
I apologize in advance for any ignorance I may be guilty of.
Thanks
Last edited by HyperGig; September 19th, 2011 at 08:51 AM.
What is the difference between the first FXZ file and targa_cdma_targa-user-2.3.4-5.5.1_84_DBN-55-110814-Verizon-US.tar? The other one is 500 megs more but I'm not totally sure why since the firmware versions are the same. Do you cut a lot of the crap out?
This weekend I ripped out Backup Assistant (hate that application) with Titanium Backup but it caused a plethora of issues in various settings menus. After failing to restore it I decided the best thing to do was to re-flash it back to factory using the giant FXZ I mentioned above. Now I see this post and a much smaller FXZ file and I am wondering if I should do it again with the smaller file... what would I gain from it (or lose.... like freaking backup assistant).
I apologize in advance for any ignorance I may be guilty of.
Thanks
That id the full restore with radios and things like that that most users don't need to fix their phones. I actually list that one later on the guide if the minimal FXZ doesn't work.
That id the full restore with radios and things like that that most users don't need to fix their phones. I actually list that one later on the guide if the minimal FXZ doesn't work.
Just follow the guide and you will be all good.
Oh ok, so your still getting all the bloatware with the minimal, bummer.
If an App needs the latest .NET it automatically sparks a dialog box stating that.
I think there is more to it than that - try a different USB cable and / or different USB port.
Also, uninstalling and reinstalling the Motorola Drivers would probably be beneficial, as those in this thread are brand new BETA drivers not available from Moto's website yet.
It's pretty much pointing to a new cable, then, or else your phone is screwed.
it's one of the two, since you've done pretty much all of the rest.
Just as a failsafe, I'd try another computer, or, at the very least, make a new user profile on your computer and try from it, just in case something is blocking it from your current profile. With a new user profile, you will not need to reinstall drivers, nor will you need to reinstall RSDLite (if you allowed it to install for all users). If, in the new profile, you cannot find RSDLite, then be sure to reinstall it again.
Also, if you're Vista, be sure to run RSDLite as administrator
To help rovrhys along in this process, the troubleshooting of his problem continues here:
I flashed the full version, was successful. When my phone rebooted everything looked the same. It was like i install the latest rom without wiping. When i flashed the minimal it was like i wiped. Is this normal?
__________________
Please support BabyBlues - or someone you know - to fight breast cancer - here's her pledge button -
I flashed the full version, was successful. When my phone rebooted everything looked the same. It was like i install the latest rom without wiping. When i flashed the minimal it was like i wiped. Is this normal?
I flashed the full version, was successful. When my phone rebooted everything looked the same. It was like i install the latest rom without wiping. When i flashed the minimal it was like i wiped. Is this normal?
If everything looked the same, then no, it was not successful.
that is expected - it's a byte-by-byte replacement of everything on your phone back to complete stock.
That's what I thought, so I was a little surprised when my home screens were all the same and I didn't have to sign in to my google account again. Could it have installed like an ota where everything in the back ground changes but what you "see" stayed the same. Just a thought. I don't know enough about what goes on in the background yet to fully understand what happens.
If said person were to remove bloatware (delete) and backup is nonexistent, will the recovery process restore the bloat like blockbuster, golf game, etc.? Also will the minimal do it or the large file only?
Yes, recovery would restore everything - but the phone would not be connected to any accounts- this is like a Factory Reset only larger, b/c it not only wipes data and cache but restores the phone to exactly how it was when you first opened the box.
Both files should do it, but dfib reported that the large file did not work for him, whereas the minimal file did.
The Following User Says Thank You to johnlgalt For This Useful Post:
Yes, recovery would restore everything - but the phone would not be connected to any accounts- this is like a Factory Reset only larger, b/c it not only wipes data and cache but restores the phone to exactly how it was when you first opened the box.
Both files should do it, but dfib reported that the large file did not work for him, whereas the minimal file did.
Thank you for the response! No issues at this time but good to know in case I do start running into problems.
One small thing,
Under the Backup and Restore guide, the 2nd part, the restore procedure, still has the title "How to Backup your Bionic". Should be "How to Restore your Bionic" correct?
The Following User Says Thank You to SNeitzel For This Useful Post:
Hey all, good to see that so much has been done since this phones recent release!
I just purchased mine today, and so far all my attempts at rooting have been unsuccessful. I followed the instructions, yet Pete's tool gets stuck at "SEARCHING FOR THE PHONE..."
I have USB debugging enabled, and selected Charge Only mode. The phone is charging, but I'm still hanging at this screen.
I'm running Win7 x64, and have the x64 drivers installed.
Hey all, good to see that so much has been done since this phones recent release!
I just purchased mine today, and so far all my attempts at rooting have been unsuccessful. I followed the instructions, yet Pete's tool gets stuck at "SEARCHING FOR THE PHONE..."
I have USB debugging enabled, and selected Charge Only mode. The phone is charging, but I'm still hanging at this screen.
I'm running Win7 x64, and have the x64 drivers installed.
Any ideas?
Same thing for me. There is a manual way to do it through adb however. I just haven't gotten around to doing it yet.
Using the guide for mac/linux. Im using my Mac and every time I enter ./fastboot flash system system.img I get permission denied. I cant even get pass the first step
Using the guide for mac/linux. Im using my Mac and every time I enter ./fastboot flash system system.img I get permission denied. I cant even get pass the first step
Using the guide for mac/linux. Im using my Mac and every time I enter ./fastboot flash system system.img I get permission denied. I cant even get pass the first step
When I try and root my phone, this is what comes up. I was unable to download Pete's tools to my computer, so I downloaded them to my phone and then moved them to my computer if that makes a difference. I followed all of the other steps. Any suggestions?
See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.
************** Exception Text **************
System.ComponentModel.Win32Exception: The system cannot find the file specified
at System.Diagnostics.Process.StartWithCreateProcess( ProcessStartInfo startInfo)
at System.Diagnostics.Process.Start()
at Petes_Motorola_Root_Tools.Main.TaskKill(String sCommand)
at Petes_Motorola_Root_Tools.Main.RestartADB()
at Petes_Motorola_Root_Tools.Main.btnRoot_Click(Objec t sender, EventArgs e)
at System.Windows.Forms.Control.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnMouseUp(MouseEventAr gs mevent)
at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ButtonBase.WndProc(Message& m)
at System.Windows.Forms.Button.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.O nMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.W ndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
When I try and root my phone, this is what comes up. I was unable to download Pete's tools to my computer, so I downloaded them to my phone and then moved them to my computer if that makes a difference. I followed all of the other steps. Any suggestions?
See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.
************** Exception Text **************
System.ComponentModel.Win32Exception: The system cannot find the file specified
at System.Diagnostics.Process.StartWithCreateProcess( ProcessStartInfo startInfo)
at System.Diagnostics.Process.Start()
at Petes_Motorola_Root_Tools.Main.TaskKill(String sCommand)
at Petes_Motorola_Root_Tools.Main.RestartADB()
at Petes_Motorola_Root_Tools.Main.btnRoot_Click(Objec t sender, EventArgs e)
at System.Windows.Forms.Control.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnMouseUp(MouseEventAr gs mevent)
at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ButtonBase.WndProc(Message& m)
at System.Windows.Forms.Button.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.O nMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.W ndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
Thanks, I saw that. I don't know anything about adb so I am a bit reluctant to go that route. I was excited about the one click method, but am a bit worn out at this point.
Well, after about 4 hours of trying many different things and getting nowhere, I finally got it to work. I went to Pete's Motorola Root Tools, and clicked on "Switch to Windows XP" (I have XP on my computer). I downloaded the file, followed the on-screen directions, and I am now rooted! It didn't even change any of my settings on the phone, unlike when I had rooted my X.
Hope this helps others who are not too computer savy. Trying to work through the SDK stuff was a bit of a nightmare for me.
I havent seen this yet. But why when i reboot or battery pull i lose root?
No, you only lose the root if you use the FX
Quote:
Originally Posted by nofxdan
Hey all, good to see that so much has been done since this phones recent release!
I just purchased mine today, and so far all my attempts at rooting have been unsuccessful. I followed the instructions, yet Pete's tool gets stuck at "SEARCHING FOR THE PHONE..."
I have USB debugging enabled, and selected Charge Only mode. The phone is charging, but I'm still hanging at this screen.
I'm running Win7 x64, and have the x64 drivers installed.
Any ideas?
Try running the 1 click app as administrator.
Quote:
Originally Posted by rovrhys
Same thing for me. There is a manual way to do it through adb however. I just haven't gotten around to doing it yet.
Yeah, I'm not really sure what is causing the error. What are your UAC settings, rovrhys?
The Following User Says Thank You to johnlgalt For This Useful Post:
For Linux and OS X – NO UNROOT
Unzip “Droid Easy Root V7D”
On your phone: Settings > Applications > Development > USB debugging(check box)
Plug phone into computer and select "Charge Only" mode
Navigate to wherever you extracted it and run the "run_to_root_your_droid3.sh" (Yes, it works on the Bionic)
Follow the instructions in the command window and unlock the phone after each reboot.
8Likes
What to do now?
