My phone has been somewhat glitchy since updating, various force closes and such. I'm fairly experienced with rooting, so doing it won't be a challenge, but my question is whether to try a factory reset first, or since i'll be re-setting the phone anyways, find a good ROM and flash over?
Just don't want to lose my factory warranty if possible :-/... Although I read that HTC's warranty can still cover some defects even if rooted... So is this a moot point?
Related
Is this possible?
I am a noob to android and rom flashing in general or even rooting so I am partly hesitant to even root my phone without reading a really good how to on it....
The only reason I wish to remove it is because of a disconnect issue another poster had and fixed by removing it is identical it seems to mine.
Thanks
Hi so I just heard that the D3 was rooted two days ago (been keeping up until a week ago). I'm not exactly a pro in this area or have ever rooted a device before but I have spent quite a few hours today reading up on the process and any info I could find.
Basically I just want to know if I should root my D3 or wait out another week or so? I heard that a SBF (?) hasn't been found yet so the stock rom can't be recovered and there is really no recovery net yet so should anything go wrong, there aren't a lot of options.
There is a one-click method to root but I'm going to try the original method using the adb shell (lol still researching what on earth to do with that still, just installed the android sdk :x). I'm not concerned about the process of rooting my droid, it's what comes after that makes me hesitant in doing so.
I read that there is a (seemingly simple) method to unroot the D3 by deleting the su file in some directory and rebooting (can't remember, it seemed legit however). Would "unrooting" have any consequences or would your device be back to the exact same state it was in right before you rooted? I'm not planning to drastically mess around with my D3 should I root it. Just want to take a few screenshots in an app to help out a dev, freeze any bloatware that won't cause problems, do a complete nand backup, and... thats about all that comes to mind right now.
I guess what I'm trying to ask is if rooting my D3 tonight would have any irreversible consequences and if there is any benefit in holding off the root?
Oh! Btw the OTA, I know that rooting won't affect ones ability to receive the update but that it will unroot your device and keep it that way. Would the rooting-discovery process have to start anew for people who update using the OTA (Thinking Verizon might patch the root-exploit) ? I know that updating via OTA isn't too bright anyway because devs just take the update and build on it before releasing it on their own custom ROMs and whatnot, but I feel official updates are somehow more stable (most likely flawed thinking, feel free to correct me on that lol).
Yes - SBF is an important component which would guarantee 100% pre-root configuration.
Removing the su binary and the superuser app would however put the phone back in factory state for this exploit. But anything you do while rooted inside /system is your responsibility to correct. Motorola patches usually verify only file existence/checksums and not creation/modification dates, so you should be fine with simple push of the removed (or renamed) stuff back. I remember I was able to update my D2G without unrooting in the past, but that's not necessarily granted for any other updates of that or any other Motorola phone. Ideally, you want phone in factory state to guarantee update will pass.
Another issue is nand backup you mentioned. Custom recovery isn't yet available for this phone. You can't do nand backups. So even this "safety net" isn't here. Installing custom recovery is a "100% secure way" to have OTA updates fail to apply since it messes up with phone's /system files. Un-doing CWM is a bit more complex than unrooting only and if not done carefully - a sure way for a soft brick. SBF is what we all want before start messing with anything, IMO.
So if an OTA updates fails for whatever reason, your phone will get soft bricked or?
I don't think ill be updating anway, but its good info to know for the future.
Sent from my DROID3 using Tapatalk
I would say root the device and don't worry about unrooting. If you have to return it to the store or something, unfreeze the apps and delete su. Once you mess with it though, it will be very difficult (impossible?) to ever make /system binary identical to the factory image without an sbf. That said, I doubt VZW takes the time to investigate this very closely.
But I don't see any other reason to ever unroot. When the OTA update comes down, just don't install it. In a few days after its first released, the community developers will tell you how to install it with root and not botch anything up.
Dmw017 said:
So if an OTA updates fails for whatever reason, your phone will get soft bricked or?
I don't think ill be updating anway, but its good info to know for the future.
Sent from my DROID3 using Tapatalk
Click to expand...
Click to collapse
No - fortunately not. It will just say "Update failed" and phone will reboot back to normal.
Regarding updates - you may want to reconsider - updates usually fix bugs, bugs like the bluish camera or the wrong geotagging. Or stuff like phone shooting at max brightness after removal from HD dock.
But as the other poster mentioned - the community would do the hard work for you 'back-porting' the update to a rooted phone. Sure enough - we need custom recovery to be made before we can install any 'backported' updates or other customizations.
But all will come with time.
If you need to use an app that requires root (like openvpn or VPNC), or if you want to remove some of the unwanted apps Verizon stuck on the phone, you should root of course, but if you don't care about such stuff and want to be 'compliant' with stock software - stay as is, until at least SBF comes.
Yeah I rooted already but should an update come, I could always unroot my device. An update would be really welcome too. Yeah the bluish tint on the cam is bad but there are soft fixes for that. What I really really want out of the update is the huge improvement in battery life I've heard about. Im using the extended battery right now and straight up, it sucks. I've heard good things about the extended battery but mine lasts ... maybe 10 hours under light - medium usage, playing music for several hours and having the display on for about an hour. I expected a lot more. Numerous people have reported getting 24-48 hrs of life while others got 15 under normal/heavy use.
There have been a few reports of peope already receiving an OTA update (devs/testers most likely) but have said many pf the d3s current issues were fixed with it, primarily the blue tint on cam and the battery life.
Honestly, with root, I figured my battery would outlast a day like a champ, but there have been no/minimal improvements, even with every piece of bloat frozen. I even froze google Maps because it constantly showed up as using cpu (and therefore battery), have my radio set to cdma, and only have 1 gmail account syncing.
Sent from my DROID3 using Tapatalk
Hello!
I had purple tint on my old HTC One, so I sent it for repairs under warranty and I got a completely new unit. It was working for a day, but today it couldn't connect to the network. At first I thought it was a HW issue, but I realized that Dialer was crashing with a message: "com.htc.htcdialer is not responding.". That made me think it was a software problem, so I tried doing a factory reset in HBOOT, but now htcdialer is still crashing, and I can't even go through initial setup, it just keeps rebooting when I try to unlock it for the first time. Is there any other way to flash a ROM, without being able to boot the phone?
Everything is completely stock, bootloader is locked and phone is not rooted. I updated it to the latest available version, 4.4.2 with Sense 5.5, I'm unsure what version it exactly is. I would like to keep it stock for at least a couple of days in case there is a hardware failure and I have to send it back to service, but I can do anything if it's necessary.
Thank you very much.
HBOOT image, if it is of any help: http://i.imgur.com/3XKC6Br.jpg?1
Since its completely stock and you just got the phone, I wouldnt bother going through and installing a custom rom, its too much of a hassle and if it ends up being a hardware problem its an even bigger issue.
I'd contact HTC again and see if they can do anything about it, or just send it back again under warranty. Flashing a custom rom in your situation isnt worth it imo.
Bhavpreet said:
Since its completely stock and you just got the phone, I wouldnt bother going through and installing a custom rom, its too much of a hassle and if it ends up being a hardware problem its an even bigger issue.
I'd contact HTC again and see if they can do anything about it, or just send it back again under warranty. Flashing a custom rom in your situation isnt worth it imo.
Click to expand...
Click to collapse
That's exactly what I've been thinking.
I was actually able to get it to go through initial setup between reboots and I was able to install a RUU, a the same thing is happening again, so I'm pretty sure it's HW related. And it still isn't getting any signal. It's a bit of a problem because I have to bring it to a store 150km away, but I'll have to do it :crying:
[email protected] said:
That's exactly what I've been thinking.
I was actually able to get it to go through initial setup between reboots and I was able to install a RUU, a the same thing is happening again, so I'm pretty sure it's HW related. It's a bit of a problem because I have to bring it to a store 150km away, but I'll have to do it :crying:
Click to expand...
Click to collapse
Ahh that sucks. Call them and make some excuse about how you cant come to the store and see if you can ship it to them.
I looked around, but couldn't find a definitive answer to this. My friend's phone is acting very strangely lately and he Verizon has been of no help. It will occasionally get stuck in a bootloop, or when it does finally boot, one half of the screen will be pixelated, while the other half is perfectly fine. Other times it will work just fine for a while. His phone is completely stock and he is wondering if there is anyway to do a factory reflash, without voiding the warranty.
Thanks!
Certainly. Follow section 0 of my guide: http://forum.xda-developers.com/droid-turbo/general/guide-how-to-unlock-bootloader-install-t3292684. The warranty will not be affected by this process.
I tried an OTA of Android Pie tonight, this was from EE UK.
First the system update couldn't verify, so I had to hard power off the phone, on powering on it re-installed and loaded up.
I unlocked the phone from the lock screen and it went to "Android Starting" and after a few moments rebooted.
Now the phone loads up but I can't unlock it, I just get constant PIN incorrects. It's a software issue because you never get to the limit of pin attempts, or the forgotten password option.
Contacted Sony, they've heard of it numerous times today, can't do anything about it.
They'll tell you to use Sony Companion to backup and restore, which you can't do unless the phones unlocked. So basically demand a full reset all data lost.
Update at your own risk, maybe consider removing device pin before the update if you can.
Same problem here in France.
There's a thread on talk.sonymobile: https://talk.sonymobile.com/t5/Xperia-XZ1-Compact/Can-t-access-phone-after-updating/td-p/1351581/page/2
So far no working solution.
The french sonyxperia twitter account is also useless.
No problem with the update here. Although, I don't have a device PIN, but a password.
After the update, some apps seem to run less stable than before...
zwan33 said:
No problem with the update here. Although, I don't have a device PIN, but a password.
After the update, some apps seem to run less stable than before...
Click to expand...
Click to collapse
backup ur photos/videos and make a factory reset, everything works flawlessly for me.
rideti.me said:
So basically demand a full reset all data lost.
Click to expand...
Click to collapse
It's a painful lesson, but backing up everything before doing anything is a must, even when doing something like an OTA update which you expect to work. I'm just waiting for a customized UK ftf to become available and will be doing a complete wipe which alleviates any unforeseen conflicts.
I had full backup, the corruption was in the pincode, therefore encryption control is lost. The backups are encrypted, I've recovered apps, messages, contacts etc.... But none of the appdata was recoverable without de-crypt.
I feel lucky: I used the repair function because I did not want to have all those small issues usually coming with a big OTA update. I did not expect such a big problem though.
Not to shove it in the face of all the people having this annoying issue, but I can confirm that with a fresh install everything is smooth and I haven't experienced any "big" bug as of yet. The phone seems even faster than with Oreo.
To be honest, besides the long process to reactivate the app of my bank, I don't even mind resetting all my apps every now and then, I noticed that it preserves battery life and performances. But I do understand that this may not be an option to some of you...
TechIntrigue said:
Just curious, why wait for the customized UK version? Does that have any benefits over the other firmware releases?
Click to expand...
Click to collapse
TBH, I'm not so sure, about either. Having read yesterday that the Singapore fw only has the Amazon app as bloat I'm going to install it today.
EDIT: Going back to Oreo as Substratum doesn't work without root.
Has anyone affected managed to do a full reset ?