Related
Hey guys I was wondering what I can do to unroot my droid 3 and also revert it back to completely stock. I had frozen and removed some apps due to this being my first time using titanium back up and I'm wondering what I can do to do this. The reason I want to do this is so that I can go back to verizon and get a replacement phone because mine has just been messing up too much. I removed or froze all the apps that were safe to remove but it'll keep pressing space or backspace, it will stop with its service and not send calls or receive texts, it will have half a green screen when I push back and it's all just really annoying.
So please if anyone has any suggestions please tell me. I've tried to restore from titanium back up but it ends up just "clocking" when I try to restore sometimes. Also I dunno how to unroot.
here
i did the same thing... lol check out this link
http://rootzwiki.com/showthread.php?5103-SBF-Droid-3-Fastboot-files-(5.5.959-and-5.6.890)
good luck its easy
More power to you but from my experience I bought the d3 when it came out 2 days later I got the same problems green blobs when it redraws screen, space and backspace buttons sticking so I called verizon they sent me a new one, this was about 15 days ago guess what's back to affecting my phone?
I know that there have been reports of the green screen thing from people that use youtube a lot. But out of curiosity, have you flashed any of the ota's? Because I noticed the same thing until I went to 5.6.890
Sent from my STEELdroid3
I haven't done anything more then remove / freeze some apps. I was thinking of trying to use the steel droid and I wasn't sure what the difference was from using 5.6.890. I'm still pretty new to all this so I was worried about what to do. Ill read up on how to do it today and possibly try upgrading to 5.6.890 and changing to steel droid.
I haven't yet installed the ota but my first glitches happened when I was unrooted completely stock and now their back and im rooted with bloat gone.................................................... < just spammed the period button damn phone
I was on 5.9.904 with Eclipse 2.2 and flashed back to 5.9.902 and upgraded to 5.9.905 then installed Eclipse 3 for 5.9.905 and now my 4G sucks.
Keep in mind I'm in a solid 4G area where it never switches to 3G.
Sometimes the icon is blue and it works but most of the time its white and doesn't work.
I have to set my phone to airplane mode and back for it to work again and sometimes that doesn't work.
If I go back to 5.9.902 and upgrade to 5.9.904 will that change the radio back to the old version or not? If nothing works I'm just going to get a replacement of hopefully a new phone from Verizon.
Thanks
If you had better connection with .902 then just FXZ back to that and don't install the official update when it ask you to. That is why there are different FXZ files so that you have the option to use what is best for you.
I had better connection on 5.9.904.
I just don't know if radio updates are permanent or not.
Will going back to 904 fix it?
Wow I dropped data while typing this message.
I haven't upgraded to 905 yet, but I've been having all sorts of problems with 4g for the past 2 days. I'm on 904 and eclipse
Sent from my DROID BIONIC using Tapatalk 2
scottocs said:
I had better connection on 5.9.904.
I just don't know if radio updates are permanent or not.
Will going back to 904 fix it?
Wow I dropped data while typing this message.
Click to expand...
Click to collapse
Radio updates are not always permanent. If you are on 5.9.905 you can FXZ back to 5.9.902 (which will put in the 5.9.902 radios) and then go find the 5.9.904 update.zip, and flash that in stock recovery to get back on the 5.9.904 radios.
Im starting to think it is something wrong with Eclipse 3 because the connection on stock 5.9.905 is working fine.
Me too - I ran the OTA - didn't lose root (am running SafeStrap w/.902 Pathsaver). I first noted the problem while in Beverly Hills - normally a full 4G area with few problems save the occasional network problem.
My network weather settings would not refresh though 4G icon appeared in blue - Also email was silent for too long.
The problem again appeared when accessing The Market (Play). The phone responded with No Connection/Retry. The connection would not return despite going to A/P mode or switching between CDMA/LTE. Finally, I restarted and 4G returned for long enough to download an app and listen to a podcast on BeyondPod.
This weekend, while listening to BeyondPod - the stream just stops and will not restart until the phone is fully restarted (ON BUTTON with -+ volume pressed).
I will revert to 902 and try flashing 905 from the SD card tomorrow.
Will report results -
This seems to be fairly uncommon as such, I'm hoping that the above will restore.
From all I've read - 4G is supposed to be ENHANCED with .905.
C'est la vie.
I think that I am not in a hurry to get the .905 OTA.
with all the issues with the last couple of radio updates im sure they will push out another one soon to fix those issues lol. it's best just to stick to a stable radio version until confirmed issues are solved.
Amendment to original post
Lemmy Caution said:
Me too - I ran the OTA - didn't lose root (am running SafeStrap w/.902 Pathsaver). I first noted the problem while in Beverly Hills - normally a full 4G area with few problems save the occasional network problem.
My network weather settings would not refresh though 4G icon appeared in blue - Also email was silent for too long.
The problem again appeared when accessing The Market (Play). The phone responded with No Connection/Retry. The connection would not return despite going to A/P mode or switching between CDMA/LTE. Finally, I restarted and 4G returned for long enough to download an app and listen to a podcast on BeyondPod.
This weekend, while listening to BeyondPod - the stream just stops and will not restart until the phone is fully restarted (ON BUTTON with -+ volume pressed).
I will revert to 902 and try flashing 905 from the SD card tomorrow.
Will report results -
This seems to be fairly uncommon as such, I'm hoping that the above will restore.
From all I've read - 4G is supposed to be ENHANCED with .905.
C'est la vie.
Click to expand...
Click to collapse
On further troubleshooting - assumed that root was not broken. It seemed that all of my apps were working as they should but when I attempted a SafeStrap restart and restore my UnSafe installation, The SafeStrap prompts would not appear. So, I checked root -found that it was in fact broken so, I ran Voodoo, restored root, ReInstalled Safestrap Recovery from the app and, restored my unsafe system to .905.
Since it was the weekend, I haven't had much of a chance to test 4G but while I was at the gym, I did listen to some podcasts. Email seems to be pushing. Today (weekday) should give me ample opportunity to test the update.
Hopefully, the restore fixed the problem.
This entire thread Sounds like bad hardware our user error
Sent from my Xclipsed Bionic
I am in the same boat here. I took the .905 update last weekend and my 4g has been terrible since. It stays 'white' most of the time and when it is blue and I open an application it instantly turns back to white and I get no connectivity...does anyone have a suggestion? Also, I was rooted and had safestrap. After the update...I guess I am not sure if I have root anymore? a root check app says I do not but I was still able to reinstall safestrap apk and then boot into eclipse.
Thanks in advance
I think this is a network issue. With last couple of days, my LTE has been showing white and wont connect to network. I still have 5..9.902.
Sent From Droid-Bionic
Using Xparent Blue Tapatalk
My phone is 5.9.904. Does that mean I can't get the 905 update?
So is it the update or a network issue?
ronaldheld said:
So is it the update or a network issue?
Click to expand...
Click to collapse
On my personal use, I was trying to see if the MAX batt saver option had something to do with the data connecting. Since setting it on nighttime save, I havent had too much of an issue.
these are from the eclipse forum
I take no credit, but used them both (despite not having any data issues at all) and others claim these work:
A:
1. Power down
2. Remove the back cover, battery, SD card and SIM card.
3. Power back up, let the phone come all the way back up and tell you that you can only do "emergency calls only"
4. Power down
5. Reinstall SIM card, SD card, battery and back cover.
6. Power back on and let the phone boot normally.
B. in settings, Battery, Battery Mode, do not use "maximum battery saver". use nightime saver. (I use custom battery saver, which just slightly adjusts the nighttime hours).
no harm in trying these.
Link to 905
Anyone have a solid link to 905? The one DROIDMODDERX posted here (http://www.sendspace.com/file/xo8f4g) won't download to my phone. Not sure if it is my phone or the link. I can pull stuff off of Google Play all day long though.
Juroid said:
I think this is a network issue. With last couple of days, my LTE has been showing white and wont connect to network. I still have 5..9.902.
Sent From Droid-Bionic
Using Xparent Blue Tapatalk
Click to expand...
Click to collapse
x2 on network issue. I've noticed 4g issues many times lately on my phone and also on stock .902
Not network issues....the leaked .905 is flawed.
My wife and I did a test. I did t his because for the 3 days I used the leak I noticed white data drops happening a helluva lot.
We were in the same room standing less than a foot apart in the same house.
We hit the same app/icons on our bionics at the same time even.
I had the .905 leak....it went white 5 times for roughly 15-120 seconds each time in a 15 minute window.....my wife's stock .902? NEVER.
Nuff said...or not. lol
So I learned about rooting mid last year around the time the Bionic was released and I decided to get the phone and root it. It sounded great and it has been, but not entirely. For instance I'm still on 5.5.886 because as far as I know the only way to update is to revert to stock? Which I honestly haven't felt like doing. I guess I really don't mess with my phone enough, or even know enough to take advantage of some of the major things that make rooting worthwhile.
There are a few things I have done though that I really like, though. So my questions are:
Without root, is there anyway to have a percentage battery display without a tacky looking app? Remove the clock from the taskbar? Remove Verizon's bloatware?
What data can I expect to lose if I do a FXZ back to stock?
Will ICS have toggle icons for WiFi, GPS, etc. that appear in the "pulldown menu"? Or is that more of a feature for certain phones?
And lastly would you recommend I unroot or look into other options?
I'm still weighing the pros and cons of being rooted so I'm just looking for some further insight to push me in one direction or the other.
Murdoc419 said:
So I learned about rooting mid last year around the time the Bionic was released and I decided to get the phone and root it. It sounded great and it has been, but not entirely. For instance I'm still on 5.5.886 because as far as I know the only way to update is to revert to stock? Which I honestly haven't felt like doing. I guess I really don't mess with my phone enough, or even know enough to take advantage of some of the major things that make rooting worthwhile.
There are a few things I have done though that I really like, though. So my questions are:
Without root, is there anyway to have a percentage battery display without a tacky looking app? Remove the clock from the taskbar? Remove Verizon's bloatware?
What data can I expect to lose if I do a FXZ back to stock?
Will ICS have toggle icons for WiFi, GPS, etc. that appear in the "pulldown menu"? Or is that more of a feature for certain phones?
And lastly would you recommend I unroot or look into other options?
I'm still weighing the pros and cons of being rooted so I'm just looking for some further insight to push me in one direction or the other.
Click to expand...
Click to collapse
This is my first smart phone and bought it October last year. I educated myself and rooted a month later. To me, this is just a mini PC and I want full control over it. Just like buying a Dell, or HP, I want to remove all of the junk software that uses up computer resources.
I also started on. 886. Then 43v3r rooted. First loaded Bionic Bootstrap and made a backup. Then downloaded Titanium Backup and started freezing programs. At some point I had deleted color note and didn't even realize it was a stock application. So when I went to Upgrade to .901 leaked, it failed. Ended up restoring the .886 bootstrap back up. Then .901 leaked installed fine.
Here are the reasons I like to have my phone rooted: Remove bloatware. Maintain full system back ups. Remove ads from applications, unless donating remove the ads. Have access to applications that require a rooted system. And finally, since I have control issues, I do not want someone telling me what I can and cannot do with my "mini PC".
So now, I have gone from .901 leaked, to .902 OTA update, now running .905 OTA update. In between, I had frozen bloatware with titanium backup and thawed before the next OTA update.
Other answers:
I use Sense Snalog Clock application that has a battery monitor on it. Not sure how accurate it is, but it works for me. Also, it is a very nice customizable clock that you can add to your home page.
I am pretty sure you can use titanium backup to backup all of your applications and data before you FXZ to stock.
I am unsure of what you mean about the toggles in the "pull down" menu. I use on/off widget pack by curvefish. Not sure about ICS yet, as I have not upgraded to it. Pretty happy with the phone as it is right now with .905.
Being that I am a novice user, I am not sure of the best process to utilize to get you back to stock. But, I would go back to stock 886. Then forever root. Dhacker29's (if I wrote his use name correctly) procedures works very well for me. I manually forever rooted. His processed kept me rooted through all of the upgrades.
As you probably have gathered by now, if you are willing to tinker with your phone a little bit more, I would suggest that you stay rooted.
I hope this helps. Good luck.
Sent from my DROID BIONIC using Tapatalk 2
So I've been looking at some of the more recent ROMs and like a couple of them pretty well so I think I'm gonna stay rooted. However I have to be on system version 905 to install any of them. Is the best way to get to 905 to use RSD to get back to 902 stock unrooted then forever root and upgrade to 905?
Pretty much, yes. However I can't speak for the 4ever root as I've never used it. I've only used zergrush and/or Pete's 1 click to get root on 902, then used voodoo root keeper to temporarily unroot so I could take the 905 OTA and reroot.
Murdoc419 said:
So I've been looking at some of the more recent ROMs and like a couple of them pretty well so I think I'm gonna stay rooted. However I have to be on system version 905 to install any of them. Is the best way to get to 905 to use RSD to get back to 902 stock unrooted then forever root and upgrade to 905?
Click to expand...
Click to collapse
Here's the link to manually forever root.
http://forum.xda-developers.com/showthread.php?t=1312555
This procedure allowed me to maintain root from .893, to leaked .901, OTA .902, and now OTA .905. Forgot to mention in my previous post that I went from .886, to .893, then to .901. Not .886 to .901.
Use Root Explorer and e sure to select "Mount R/W" before you open mount_ex3.sh to add the text at the bottom. After you add the text, hit the back button once and select "Mount R/O". Otherwise the text you add will not stay in the file.
Here's a screen shot of my mount_ex3.sh file. The last three lines of text are what I added for forever root. This was easier to me than hooking up to a PC and running one of the root programs.
Sent from my DROID BIONIC using Tapatalk 2
Ok so I used RSD to get back to stock .902. Then upgraded to .905 and used MotoFail to root. I ended up installing Eclipse 3.0. Now I'm having some problems with my phone. I don't want to submit a bug report until I know if it's the ROM or my phone. I figured I'd just post what's going on in here instead of creating a new topic.
I was texting a couple people last night and they both stopped replying at the same time. It was kind of late though so I thought maybe they fell asleep. Then today at work my ringtone started going off. No one was calling me though and the only way I got the ringtone to stop was to power off the phone. So I sent a text to one of the people I was talking to the night before and asked if she got my texts. She told me she didn't and I sent another text that she didn't get. When I got home I sent a text to my mom to see if my phone was alright and she got it so I had her reply to make sure I was receiving messages. I received her reply 15 times. I'm not sure if this has something to do with the ROM or the phone itself. What do you guys think?
In preparation for upgrading to a Moto X I had them replace my wife's old D3 (with another D3, if you can picture the dusty warehouse that must have THESE spares..) Anyway, what's the more straight-forward way to move from the old one to the new one? The only thing wrong with the old one was a flaky keyboard, so it's accessible for the process.
The old one is rooted and has a 32gb microSD card. Both the old & new are running 5.7.906
The one thing I haven't done yet is activated the new phone (did the four corners green guy skip). The SIM card is not inserted in either phone at the moment. I'm loathe to spend the likely HOUR on the phone it'd take with Verizon and then if the new phone "doesn't work" I'd have to do the dance all over again. Let me get the phone set up first...
I thought I was headed in the right direction by first rooting the new one (via the motofail method) which seemed to work. I then bought and loaded the $3 CWM tool. I used that to create a backup on the old phone to it's SD card. Also, seemed to work. Also downloaded the CWM app onto the new phone, powered off, brought the SD card over, powered up, used the app to reboot into recover and reloaded the backup. Seemed OK. Lots of stuff 'looked like' it was present and usable. I wanted to then go and whack out the bloatware.
But now the new phone reboots. Not right away, it takes a few minutes but then, with no messages on the screen, it just spontaneously reboots. It only seems to do this if the USB cable is connected and USB debugging mode is selected.
It does not reboot unless USB debugging is enabled.
Ok, so perhaps I've missed some critical steps or something. It's been a while since I had to do this sort of thing and this is a pretty old phone. I'm inclined to think there's and ADB driver issue here. But I'd like to be sure to head in the right direction before making a bigger mess.
Suggestions?
Random reboots after moving CWM backup to new D3?
Just when I thought everything was done... bam, it reboots randomly.
I had a D3 with a flaky keyboard. Got a replacement since it's been covered. Going to decommission it next week with a Moto X.
Got the replacement D3 (hoped for a D4 but they STILL have stock of replacement D3's). Old one was rooted and had the D3 Bootstrap app on it. Booted into CWM and made a backup to a blank 4GB microSD card.
Rooted the new D3 using motofail. Loaded the D3 Bootstrap app and restored the backup made from the old Droid3. Seems to 'take'.
But then I started getting random reboots. Thought it might be just related to the USB debugging, so I turned that off. Seemed to stop rebooting.... for a while. STFW said WiFi networks can be problematic, so I deleted all the old networks and turned off WiFi. No love, still reboots.
In fact, while I've been typing this it's rebooted twice.
Ok, so before I subject myself to the utter nonsense that is Verizon support, what steps should I take to narrow down whether it's an issue with the phone or the way I did the restoration to it?
HELP!
I'm thinking I would have taken the old motherboard, and slapped it in the new phone. Just an idea....
Dougnsalem said:
I'm thinking I would have taken the old motherboard, and slapped it in the new phone. Just an idea....
Click to expand...
Click to collapse
Given it was insured there wasn't really any need, other than the possible quicker turn-around. They sent the replacement's replacement in just two days more, so it wasn't a big wait. That one has been fine.
Meanwhile the Moto X was shipped Fedex signature-required, and the driver didn't wait long enough for me to get out of the shower. Nor did they respond to a phone request asking the truck to circle back around later. So presumably it'll be delivered later today.
I posted this in an older thread but figured I would just go ahead and make a separate post about it.
Ever since I updated the phone to 5.1 it has crashed repeatedly, super laggy, battery life is significantly worse than kitkat, Turbo charge seems to take longer than on kitkat, my texts and calls won't go through, and on a rare occasion my phone will reboot by itself. I've cleared the cache regularly and have factory reset a couple of times and the problems will go away for about a week, but only to return again. I'm going to Verizon tomorrow to see if they can do anything.
Anybody else have these issues with their Turbo?
Sent from my XT1254 using XDA Forums
I'm not experiencing any of this. Have you troubleshot apps that you have downloaded as possible culprits? Also, did you upgrade via OTA or did you manually flash the 5.1 update via rootjunky? I've heard multiple people having issues with the flashed one.
Maybe it's one of the apps you have installed. Try a FDR and install your apps a few at a times. Try to pinpoint which app is constantly taxing your phone. If all else fails make verizon give you another 4.4.4 Turbo
So I went to Verizon yesterday and they couldn't do anything for me. I just took the OTA that came out yesterday and I am hoping it fixes more than the stage fright exploit. If not I guess I will be migrating back down to my old Galaxy S4.
Murd0c said:
So I went to Verizon yesterday and they couldn't do anything for me. I just took the OTA that came out yesterday and I am hoping it fixes more than the stage fright exploit. If not I guess I will be migrating back down to my old Galaxy S4.
Click to expand...
Click to collapse
If you haven't already, try using the Verizon Upgrade Assistant (that annoying thing that pops up every time you plug your phone into a computer) and select repair. This will do the cleanest wipe possible, reflash everything and bring you up the the latest firmware version. If you still have problems after that, chances are you're using an app that lollipop doesn't like, or you have a physically defective unit.
I ended up with what I think was a physically defective unit, and I got a warranty replacement straight from Motorola. The process was painless, and as long as the phone doesn't have any physical damage and was never exposed to water (in most modern phones, there's a water-sensitive sticker on the inside that changes color when exposed to water, so they can tell if you're lying), you basically just have to ask for it.
In fact, forget what I said in my first paragraph. Just get the Motorola replacement.
https://motorola-global-portal.cust...sion/L3RpbWUvMTQ0NDMzNDc3Mi9zaWQvWDgyS2RzeW0=
OK guys quick update I sucked it up and got the Motorola replacement and it works perfectly now, turns out I had a factory fault or something
My phone isn't laggy, but my Turbo charging is definitely slower, my WiFi is hit or miss at times, and the battery does seem to drain a bit faster but isn't too awful.
Sent from my Droid Turbo using XDA