Ok I have the system update that was pushed a few weeks ago. Every time I try to update it it will just go to the home screen and I lose the ability to update for a week when its pushed again. It is a rooted phone but no custom roms. Any ideas why? I called VWsupport and they called HTC and HTC said try wifi or a full factory reset... I don't want to do the reset but I will try the wifi unless someone has a better idea.
You don't need the update since I believe you will lose root once it's installed and there is nothing in the update other than changes to verizon's bloatware like VCAST, etc.
That's strange. Although it makes you (temporarily) lose root, it should still install. However, it wont if you've touched any of the stock apps in any way- those have to be returned to 100% stock status for an OTA to install correctly. If you do get it to go, as long as you're s-off, all you have to do is re-flash clockwork and su to reacquire full root status
Related
Hi All, I come begging for help after exhausting all of my options and searches for similar issues.
I have a CDMA Galaxy Nexus Stock 4.0.2 but rooted (I installed CWM).
I woke up to my phone stuck in the boot loading screen; it just kept looping over and over. I shut off the phone restarted it and the phone was practically unuseable, it ran very very slow. Now I haven't done anything recently or installed any apps. The only app I installed was a modified MMS app (one of the Inverted Black ones), but that was 2 weeks ago and everything was running fine since then. (However since I'm not on a deodexed Rom, I knew there could be issues).
Well I of course switched back to the stock MMS app that I had manually backed up and that did not help. Now my phone would load, it would get to my homescreen, but it would then say something along, "service is not working, wait, close, or ok?" I'd hit wait and within 2 minutes my phone would automatically reboot and then go into a a sort-of bootloop (it would just show the boot.img and loop).
I then tried to restore two Nandroid back-ups (which were basically bone stock and made months ago) and both worked, except it would say secure.img not found or something like that. I was still able to boot up and use these back ups, but then within 5 minutes I would get the same error and then the phone would reboot.
After retrying them I decided to to just go bone stock and wipe and do a factory reset. This worked and everything seemed fine until I went to turn on wi-fi.
I would wait for wi-fi to turn on and eventually it would just quit and then reboot the phone. I did this 3 times in a row to confirm that it was indeed wi-fi causing these rebooting issues.
Now here's the thing, right now my phone is working as I have purposely tried not to touch the wi-fi (I need to use my phone) . Data, voice, mms/sms all work. But I literally have no idea why wi-fi would be causing my OS to go crazy?
My last resort is to flash the stock toro.img but I was hoping you guys could help me before I get to that point.
As of right now even though I did a data wipe/factory restore my phone is still rooted (rooted apps all work) and my bootloader is still unlocked. (I renamed the secure.bootloader file as per the instructions when using fastboot to load CWM).
Please help me troubleshoot this, Thanks guys.
I don't know if you have tried but maybe try flashing a rom after a data wipe
angelino0919 said:
I don't know if you have tried but maybe try flashing a rom after a data wipe
Click to expand...
Click to collapse
I'm thinking about doing this as well since I will probably have to flash back to stock. I just want to make sure I can get back to stock since I am still covered by warranty and insurance (assuming they do not check to see if my phone has an unlocked bootloader).
JayBeezy802 said:
I'm thinking about doing this as well since I will probably have to flash back to stock. I just want to make sure I can get back to stock since I am still covered by warranty and insurance (assuming they do not check to see if my phone has an unlocked bootloader).
Click to expand...
Click to collapse
Well you can always relock the bootloader. I doubt you will have to go back to stock though
It seems my phone is stuck on ALJC. I flashed the stock recovery via Odin and did a temp unroot, downloaded the OTA update. The phone rebooted and went to the stock recovery and appeared to be installing the update. Upon reboot, my phone was back in rooted condition (not sure if this is normal for voodoo unroot or not). This has happened twice. The first time it happened I had not noticed it, but now that it has sent a second update request to me today, which I used the same method only to discover that it doesn't seem to work. Now when I request an update it tells me no update is available. Suggestions?
Ignore this thread, I said screw it and just did it all manually.
I just recently rooted my i747 using the No Trip Counter method using ODIN and the stock ROM with root injected into it already. I had a fair amount of stuff frozen with TiBu but nothing on the "unsafe" list. I made sure screen rotation was on, tried to calibrate via the motion settings (little blue dot didn't move at all), even tried battery pulling, reflashing the ROM, wiping the cache, clearing the cache for System UI and Touchwiz. I don't have a custom recovery flashed. I flashed the unrooted stock ROM and called up AT&T. I've got a new device that auto rotate works now but a bit hesitant to re-root. Has anyone heard of this feature being disabled due to something done during/after root? I've Googled my butt off but couldn't find any issues related to rooting.
Note: I got jumped over the weekend and my phone was swiped. It was later returned to an AT&T store but who knows what it went through. That's my guess as far as why it didn't work anymore (probably thrown/dropped/who knows what) but I just wanted to see if there was a possible software issue that I may not have been able to find.
Cheers!
I went through from 4.1.1 to 4.1.2, no problems, phone ran fine after update. Then went to 4.3, same thing. The phone was running fine so I booted back into recovery and removed Knox as well as manually rerooted by flashing SuperSU. Rebooted after that and still no problems, phone was running great. I then make a backup so I have a restore point of stock 4.3, rooted, and without Knox. I then go on and try to flash Dandroid and get a status 7 error and the phone was acting up after I rebooted.
At this point I go back to my backup and simply restore it and reboot again. The phone boots up, so that's a good thing. The problem is the GApps will not run and it continuously has a pop-up notification. The phone is rendered unusable like this. I got lucky once and was able to try and launch ROM Manager to see if fixing permissions would work, but it also closed. I tried flashing a 4.3 GApps package with no success and even tried reflashing the 4.3 update but got a status 6 error.
I'm at a loss here, does anyone have any ideas on this?
Not sure if this will help much, but even when plugged in via USB my computer will not recognize the device. The S3 states that it is connected and it does show up in Device Manager, it just won't show up as any kind of readable memory.
Trying to ADB sideload a rooted stock 4.3 ROM now. Any advice at all would be a help.
EDIT: I took a video (https://www.youtube.com/watch?v=tJ-eaQ_9mVI) of the problem so everyone can see what I'm talking about and I also found a fix.
I'm not sure what was causing it, but after a solid day of researching it online the closest thing I got was resetting app preferences and also trying to clear any data of Google apps. This seemed to sometimes slow the popups down for me or create a longer gap before they just came right back in full force. So, going off that small success I had managed to navigate my way over to Settings -> Accounts -> Backup and reset -> Factory data reset and ran that. The first boot after that took a very long time, I'd say a solid twenty minutes but it did work. No more error and everything has been going smooth for me since. A restore of apps with Titanium Backup also did not bring the problem back up again, so the device seems to be good as new again.
I apologize if any of these is out of line, I just thought I would follow up with a solution in case anyone else has this problem and can't seem to fix it. Maybe this will help them.
hello,
my phone is f240s, running 4.4.2
im trying to get the ota update, but i always get an error message when the instalation should start and a message that the device is suspect to be rooted.
I had supersu installed, but now i cant even get in the app, because the binaries and something about if i upgraded to 4.3 i have to re-root manually.
root checker said that device is not rooted. simply unroot also..
i dont get why i cant install the ota if the phone is not rooted??? I tried to uninstall super su and get the ota, but the same error and suspect to be rooted..
i think the phone is "partially rooted" or something like that, because when i installed supersu i didnt update the binaries right away, but now when i installed it again i cant even get into the app..
what should i do to unroot (if its even rooted) and receive updates normally?
nothing works on this stupid phone. now i cant even get gps signal.. 3g signal is bad. i have to keep it next to my window to get it and my area is covered with 3g properly.. its constant problems...
im thinking about factory reset and i did that just a week or so ago. everything would probably be ok if i didnt install supersu, but im not sure and i dont get why my gps doesnt work now..
come on, someone, what should i do?? i just want the phone to work normally and to receive ota updates normally...
i did the factory reset and gps is working now.. the error that i get after i download and start the instalation is err 0x13e (im not 100% sure, but i think it's this) and then when the phone starts i get the message that the phone is suspect to root so it cant be updated..
anyone know how can i resolve this and get the ota updates normally?