Related
as the title says, after rooting, i am unable to check for any firmware updates. i realize it doesnt mater right now as there is noithing out right now, but i like to check often just in case tmobile releases something or samsung. when i go to check for updates by selecting settings>software update and then a warning message pops up: DM initalisation is not ready, Check network or SIM card
Any ideas would be greatly appreciated
I was about to ask this same question, and yes i am also rooted. Just wanted to post that you are not alone on this one.
thats good to know, i was beginning to wonder if i was the only one having this problem, for now i unrooted and flashed back to stock using odin, but i miss having root and some of the apps i was using. I am not willing to give up the ability to check for new firmware though as my source at work told me that updates are coming in the next 2 weeks and that we should be getting a text message about them in the next week or so. and just so people know, it wasnt a tmobile customer service rep, i work for deutsche telekom so we here things first usually.
I have this same issue, where I'm unable to check for firmware updates. I am not rooted though... I just bought the phone today and when I click the 'Software Updates' option it says 'No firmware' in a pop-up message. This problem is not only associated with rooted devices.
joshuapurcell said:
I have this same issue, where I'm unable to check for firmware updates. I am not rooted though... I just bought the phone today and when I click the 'Software Updates' option it says 'No firmware' in a pop-up message. This problem is not only associated with rooted devices.
Click to expand...
Click to collapse
Read the first post again... yours is the normal message that is displayed when no firmware update is available...
Also, I'm rooted and the update seems to be working fine.
I'm rooted and it pops no firmware.
Sent from my SGH-T959 using XDA App
If I flash back to stock it works fine when I use odin to go back to stock, but if I reroot it says the same thing. Nothing ever stops it from saying what I posted in the OP. I need some help funding a fix or ok won't be able to get the froyo update when it releases.
Sent from my SGH-T959 using XDA App
If I use oclf to root and apply the fix, then unroot using oclf, will the factory ota not work?
Sent from my SGH-T959 using XDA App
Duuude don't worry about it. People will post ROM clockwork backups of the froyo release / stock odin flashes of it / etc.
Anyone will be able to update, however they do so... And just wait til you hear about it THEN unroot and update
yep i'm rooted to and it checks for filmware just fine .
im rooted and get the no firmware message
r0me0ne said:
im rooted and get the no firmware message
Click to expand...
Click to collapse
... *sigh* Because there isn't a UPDATE for the Vibrant.
IF I ROOT, WILL I GET OTA UPDATES?
Yes. Rooting will not prevent this, unless you flash a custom ROM that will block receiving the OTA update. If you do receive and download the OTA update, you will lose root. Typically within hours of the OTA becoming available, thanks to some fine XDA folks you can get the update WITH root. You would simply need to download and flash the update like a normal ROM.
Click to expand...
Click to collapse
Rooting doesn't mess with your OTA updates, when you update with the OTA it will remove your ROOT. The only way to interfere with OTA's are flashing custom ROMs.
But you cannot get the ota update when it releases if the check for update option under settings is not working. All I want to know is why the firmware update option is broken and how to fix it.
Sent from my SGH-T959 using XDA App
When I first got my phone I got the message Check network or SIM card. I rooted the phone and still got that same message. I restored to origanal and got the message'No firmware'. Now again I am getting Check network or SIM card.
tpreludesh said:
But you cannot get the ota update when it releases if the check for update option under settings is not working. All I want to know is why the firmware update option is broken and how to fix it.
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
It seems like your phone was more than just rooted. What method did you use to root?
Note: Yeah, the "No Firmware" message is the normal message you get if there's no update available, aka, your phone is searching for and/or receiving OTA updates just fine.
Leoslick said:
If I use oclf to root and apply the fix, then unroot using oclf, will the factory ota not work?
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
This was my plan. Although, I'm reading posts that imply that even though a phone is rooted, if the user hasn't flashed a custom ROM, they'll still get the OTA update, and getting the OTA update will unroot the phone.
When this happens, root-necessary apps like ryanza's lag fix, titanium backup and android system info won't work anymore right? Will they need to be uninstalled and reinstalled? Or will I just need to re-root?
Sorry, I'm new to Android and don't know the typical process stock ROM root users go through with OTA updates.
Genuinely, thanks for any feedback.
Yes I wanna know this too. I'm holding off on getting apps for root only because I think they might mess something up. Also I thought I read set cpu spook might mess up the vibrant running oclf. Anyone?
Sent from my SGH-T959 using XDA App
Help.
I have a rooted Thunderbolt and I have been able to reject the update from Verizon until this afternoon when my phone started to update on its own. The update didn't go through and I got an error icon. Now my phone just goes through the same cycle of turning it self off and trying to update and crashing.
I am able to get to the Clockwork Mod recovery page but the only option that works is the 'reboot system now', which starts the phone and the whole cycle of trying to update is started.
Does anyone have an idea of how to get my phone working again?
Thanks in advance.
Mike
I'm really sorry to hear that happened, I'm not sure what you can do. Hopefully someone will be able to help you out. But at least I can tell you that you are not alone! I wasn't rooted, but my phone did autoupdate on its own at about 2:30pm today.
I posted about it here: http://forum.xda-developers.com/showthread.php?t=1234844
Pull your SDcard, wipe the pg05img.zip file, and try again. You might have to reflash clockwork.
This is the problem with running rooted stock ROMs. I know flashing a new ROM isn't what a noob wants to do, but it will avoid these very confusing headaches.
whats if you rooted using revolutionary? As far as i know there wont be that pg05img.zip file to delete.
Would you always be in danger is this if you are rooted and stay stock?
Why would someone want to root their phone and stay stock ??????
Sent from my Verizon LTE 4G Thunderbolt
loonatik78 said:
This is the problem with running rooted stock ROMs
Click to expand...
Click to collapse
Nope. One only has to keep up with the current releases, rooted versions of which come out within days of official release.
Are you sure it is the Verizon update?
I have the same behavior on my T-bolt since about 10 pst today. However, just before the phone shuts down to reboot, I see a note about a new version of Clockworkmod Recovery 4.0.1.5.
So I have been working on the assumption that it is CWM Recovery that is doing an automatic update.
I also am running rooted stock, and have not updated to latest release.
OK, it isn't the update to CWM Recovery that is the problem; it is the Verizon OTA update, which they have figured out how to force on us. I fixed my phone using the solution given by Mike later in this thread.
jbh00jh said:
Why would someone want to root their phone and stay stock ??????
Sent from my Verizon LTE 4G Thunderbolt
Click to expand...
Click to collapse
Debloating. Stock is pretty damn nice without all the extra crap.
*Madmoose* said:
Debloating. Stock is pretty damn nice without all the extra crap.
Click to expand...
Click to collapse
This, plus "root while you can" - there's no guarantee that rooting will be possible with each subsequent (unrooted) release, but you can root now and stay rooted to keep your options open. Also, getting full backups of everything is easier when rooted.
Did the fix work?
Mike, did you try what loonatik suggested? Did it work? Waiting breathlessly...
Unless I am misunderstanding the problem wiping cache from Clockwork recovery should clear out the update and it will quit trying to install it. For the future if you go to settings in the about phone or software update section (dont remeber which) there is an option to de-select scheduled update checks.
Sent from my HTC Thunderbolt
Wait.. what? Most ROMs I've seen are debloated.. At the very least they have VZW crap removed
Thanks guys for all your help and interest. I tried the solution offered by lunatic but it did not work. Thanks any way I was still looping through continuous on and off cycle. I did however did find a solution on another site. Here is the solution from Sele.
http://www.thunderboltforums.com/forum/htc-thundebolt-hacking-guides/2257-rs-guide-how-get-rid-ota-forced-reboots-rooted-phone.html
It was easier fix than I thought it would be. Step #1 worked.
I also did this to stop the update from happening again.
"If you are rooted use root explorer or super manager and set system to R/W. Then navigate to /system/etc/security. Find the file named otacerts.zip and rename it to otacerts.zip.bak and reboot. Should fix you up."
I'm sorry I can't remember who offered this solution to give credit to. I haven't had any updates yet but only time will tell.
Good Luck with your phone.
JBO1018 said:
Unless I am misunderstanding the problem wiping cache from Clockwork recovery should clear out the update and it will quit trying to install it. For the future if you go to settings in the about phone or software update section (dont remeber which) there is an option to de-select scheduled update checks.
Sent from my HTC Thunderbolt
Click to expand...
Click to collapse
Yes you are correct wiping the cache fixed the problem.
mjkusa said:
Thanks guys for all your help and interest. I tried the solution offered by lunatic but it did not work. Thanks any way I was still looping through continuous on and off cycle. I did however did find a solution on another site. Here is the solution from Sele.
http://www.thunderboltforums.com/forum/htc-thundebolt-hacking-guides/2257-rs-guide-how-get-rid-ota-forced-reboots-rooted-phone.html
It was easier fix than I thought it would be. Step #1 worked.
I also did this to stop the update from happening again.
"If you are rooted use root explorer or super manager and set system to R/W. Then navigate to /system/etc/security. Find the file named otacerts.zip and rename it to otacerts.zip.bak and reboot. Should fix you up."
I'm sorry I can't remember who offered this solution to give credit to. I haven't had any updates yet but only time will tell.
Good Luck with your phone.
Click to expand...
Click to collapse
Definitely a handy resource.. Every time a new OTA comes out, this is a very frequently asked question.
I suppose you could always use an RUU too
mike.s said:
Nope. One only has to keep up with the current releases, rooted versions of which come out within days of official release.
Click to expand...
Click to collapse
Based on how many of these threads I see, that clearly isn't what's being done.
Hello all,
Just had a quick question. I didn't know what search terms to use to get an accurate answer, since the search seems to pick up any and everything related to any of your search terms. I was wondering what exactly prevents an OTA update from taking. Is it the recovery that is installed? Is it having root? It's been a while since I have accepted an OTA for a device, outside of the Nexus on launch day. I have my Razr Maxx rooted, no custom rom. I tried a few of the ICS leaks but they were in safestrap, my non safe partition remains only rooted. When the OTA actually hits should I be able to accept it fine or will I need to go back to completely stock unrooted?
Things that prevent an OTA: ROMS, Bloatware frozen/uninstalled, custom recoveries (safestrap, bootstrap) so yes, when you want the OTA you'll need to fastboot back to complete stock for it to work. Root won't stop an OTA but OTA's generally break root.
You can try just uninstalling safestrap but I've read cases where just uninstalling it doesn't work and you need to fastboot back to stock.
everything wrong with motorola and Android has to do with idiot upper middle management execs having endless powerpoint presentations babbling corporate gibberish so they can make the next payment on their overpriced overlarge joke of a house and BMW. we are left to sort out the steaming pile of ****. i pray google has the sense to fire every last one of them and give their salaries and bonuses to the engineers!
Freezing bloatware has never prevented me from getting and OTA. Custom ROM and bloatware removal has/will.
tech_head said:
Freezing bloatware has never prevented me from getting and OTA. Custom ROM and bloatware removal has/will.
Click to expand...
Click to collapse
What is the difference between freezing and removal, from a technical standpoint? I rooted my Razr using CASUAL and then installed Titanium Backup Pro and have been zapping the Verizon bloatware. I do want the stock ICS when it comes out. I guess I could reinstall the bloatware from backup and then freeze it rather than uninstalling. I don't care so much if the OTA doesn't install, I can troubleshoot that, but I don't want the OTA to brick my phone, that's the main concern.
The main reason I don't want the bloatware on there is that I don't want there to be any danger of clicking on anything that will make my monthly bill go up. Sometimes I let my girlfriend or other people use my Razr and if they manage to get a $10 monthly charge on my bill because they just had to see NFL Mobile or something similar, I'm gonna be pissed
I'm fairly sure it just changes the extension to .apk.bak, but I could be wrong
So, I have bloatware frozen, but none uninstalled. If ICS /is/ released on the 12th for the Verizon RAZR, I should be able to get it OTA?
Rooted, stock 2.3.6
bpingry said:
So, I have bloatware frozen, but none uninstalled. If ICS /is/ released on the 12th for the Verizon RAZR, I should be able to get it OTA?
Click to expand...
Click to collapse
Yes, at worst case scenario: You might have to unfreeze everything, Install OTA RootKeeper, use OTA RootKeeper to a> Backup your root and B> Temporarily unroot your device.
On the last OTA that I received, I was not able to install the OTA until I ran the Temp Unroot from OTA RootKeeper, then the OTA went smoothly after that.
quarky42 said:
Yes, at worst case scenario: You might have to unfreeze everything, Install OTA RootKeeper, use OTA RootKeeper to a> Backup your root and B> Temporarily unroot your device.
On the last OTA that I received, I was not able to install the OTA until I ran the Temp Unroot from OTA RootKeeper, then the OTA went smoothly after that.
Click to expand...
Click to collapse
Apps in preinstall folder are required by OTAs those are the real bloats. Any other system modification will be verified too, like build.prop, init.d CWM and so on..
Remember an OTA update is an incremental update wich will check any required system piece, especially those I've mentioned.
Cheers
OK. So I have the pull down button mod. Will this get in the way? I've not removed any bloat or yet (was waiting for updates). All I have is pull down mod and root.
MarkyG82 said:
OK. So I have the pull down button mod. Will this get in the way? I've not removed any bloat or yet (was waiting for updates). All I have is pull down mod and root.
Click to expand...
Click to collapse
Yes, it's a system modification. You'll need to flash stock rom to flash an OTA update.
When installing an OTA you can press both volume buttons at the same time to to see dialog, and if anything fails you will have filename and directory of failed checks. And it won't auto reboot until you tell it too. I found the problem files for the ics leak from early April leak and was able to install without wiping.
Sent from my DROID RAZR using xda premium
See I'm not fussed about wiping. Id quite happily have stock ICS and mod it from there. Looks like I'll be hacking some way or other to get the official anyhow as I'm on linux. Unless someone can point me to a UK suitable stock rom I can fast boot or add flash from linux. I have add setup if that helps. My system version is 167.26.
Sent from my XT910 using xda premium
cause they arent bronies, duh.
ExtraDan said:
cause they arent bronies, duh.
Click to expand...
Click to collapse
Sorry, I don't understand.
Sent from my XT910 using xda premium
and you wont...
MarkyG82 said:
Sorry, I don't understand.
Sent from my XT910 using xda premium
Click to expand...
Click to collapse
I don't understand them either, just don't make a big deal about it
Thanks for all the replies. I don't have any bloatware frozen and no system mods done so I guess once the OTA hits, as long as safestrap uninstalled smoothly, I should be good to go. Ill check out ota root keeper here shortly.
Sent from my DROID RAZR using xda premium
So I have read multiple articles on how to unroot and have tried 2 of them with no avail. Can anyone explain to me or point me in the right direction on to a "How to unroot for dummies" or something!? I tried getting a nandroid backup and putting in in TWRP/backups/ but for some reason when I boot into recovery and select "Internal Storage" it doesnt show anything! Then I tried to flash the stock recovery from the toolkit and I get an error. Any help would be appreciated.
CavyS said:
So I have read multiple articles on how to unroot and have tried 2 of them with no avail. Can anyone explain to me or point me in the right direction on to a "How to unroot for dummies" or something!? I tried getting a nandroid backup and putting in in TWRP/backups/ but for some reason when I boot into recovery and select "Internal Storage" it doesnt show anything! Then I tried to flash the stock recovery from the toolkit and I get an error. Any help would be appreciated.
Click to expand...
Click to collapse
There is a step by step guide to do this under the General section of this forum.
Here is a link...
http://forum.xda-developers.com/showthread.php?t=2751011
I would ask why you want to unroot? Unless you are selling/trading the device, its my opinion that once you are rooted, there are few other valid reasons to go back.
scott500 said:
There is a step by step guide to do this under the General section of this forum.
Here is a link...
http://forum.xda-developers.com/showthread.php?t=2751011
Click to expand...
Click to collapse
Yeah that might as well have been written in Arabic. I think that might be one of the methods I tried though?.. Except when I put the Nandroid backup in TWRP/backups then rebooted my phone into recovery the backup wasnt showing in there no matter what I did, and the other way just got an error.
redpoint73 said:
I would ask why you want to unroot? Unless you are selling/trading the device, its my opinion that once you are rooted, there are few other valid reasons to go back.
Click to expand...
Click to collapse
I want to unroot to get the OTA update. And I'm sure I could probably flash the new update or whatever, but I would rather just get the OTA. Just my OCD I guess?..
CavyS said:
I want to unroot to get the OTA update. And I'm sure I could probably flash the new update or whatever, but I would rather just get the OTA. Just my OCD I guess?..
Click to expand...
Click to collapse
I can never ever understand folks that root, than want OTA. As you suggested, the ROM is already available (stock rooted) in a custom recovery-flashable form, supplied graciously just days after the OTA started rolling out. And if you are referring to an upcoming OTA, the same will probably be true; or it will be available earlier for the international version (and isn't that one of the reasons we root?).
If you want the firmware package that came with the OTA, that is available to flash on modded phones, as well.
redpoint73 said:
I can never ever understand folks that root, than want OTA. As you suggested, the ROM is already available (stock rooted) in a custom recovery-flashable form, supplied graciously just days after the OTA started rolling out. And if you are referring to an upcoming OTA, the same will probably be true; or it will be available earlier for the international version (and isn't that one of the reasons we root?).
If you want the firmware package that came with the OTA, that is available to flash on modded phones, as well.
Click to expand...
Click to collapse
Lol I know, idk why I have to have to OTA either. Its just an OCD thing. I think its because I know that what I'm getting from OTA is clean and is a 100% working squeaky clean release by Android. Opposed to a ROM that someones put together themselves. I'm sure there is nothing wrong with the ROM or that there is any kind of malware or viruses in it. But its just an OCD thing were I would never stop thinking about it. And first thing my phone crashes or runs into a bug regardless of the problem I would blame it on the ROM. Lol now I sound like a sociopath
CavyS said:
now I sound like a sociopath
Click to expand...
Click to collapse
Haha, not really.
If a clean, bugfree OS is what you crave, than I would actually strongly disagree with the notion that an OTA is the way to do that. OTA is often a mess, as it only updates some things, and not other (not a complete image) and also keeps user data; which if you will see from any forum thread (here or other places) about bugs after OTAs, keeping user data is often the cause of many issues.
Factory reset plus OTA is one way around this. But if you really are OCD about a "clean" stock install, I would run the RUU. Either get S-off, or relock bootloader beforehand; and backup user data as this will be wiped. RUU is a complete factory released image.
redpoint73 said:
Haha, not really.
If a clean, bugfree OS is what you crave, than I would actually strongly disagree with the notion that an OTA is the way to do that. OTA is often a mess, as it only updates some things, and not other (not a complete image) and also keeps user data; which if you will see from any forum thread (here or other places) about bugs after OTAs, keeping user data is often the cause of many issues.
Factory reset plus OTA is one way around this. But if you really are OCD about a "clean" stock install, I would run the RUU. Either get S-off, or relock bootloader beforehand; and backup user data as this will be wiped. RUU is a complete factory released image.
Click to expand...
Click to collapse
Quick question. I put the Nandroid backup in the TWRP/backups/ folder. It doesnt show up in "Restore" but it shows up in "Install" in TWRP Recovery. When I click on it in "Install" it asks me "Swipe to Confirm Flash" Is it okay to flash Nandroid backup from the "Install" location or does it have to be done through "Restore"?
redpoint73 said:
I would ask why you want to unroot? Unless you are selling/trading the device, its my opinion that once you are rooted, there are few other valid reasons to go back.
Click to expand...
Click to collapse
I unrooted ?. Main reason for me was to use ISIS and be able to play a game me and some buddies play. I had root and ISIS didn't like it, so grabbed rootcloak but game disliked xposed
Sent from my HTC One_M8 using Tapatalk
twiggums said:
I unrooted ?. Main reason for me was to use ISIS and be able to play a game me and some buddies play. I had root and ISIS didn't like it, so grabbed rootcloak but game disliked xposed
Sent from my HTC One_M8 using Tapatalk
Click to expand...
Click to collapse
Yeah I just updated with RUU, I'll re-root again once 4.4.4 gets pushed out.
If anyone is interested, I saw this posted today. A small OTA update released by AT&T today.
http://www.androidcentral.com/att-pushes-out-update-htc-one-m8-brings-android-444-and-hd-voice
scott500 said:
If anyone is interested, I saw this posted today. A small OTA update released by AT&T today.
http://www.androidcentral.com/att-pushes-out-update-htc-one-m8-brings-android-444-and-hd-voice
Click to expand...
Click to collapse
This is merely a rumor. The ATT link is to the old May 2014 update.
Pay no attention.
The link to the att sight yes is for old 1.58 build, does not mean there isnt an update coming...as its being reported with a build number by more and more sights, could just be a rumour but it could also be rolling out.
Well, they finally released the update today. Finally have 4.4.4. On my m8. Now to wait for lollipop
Does anybody know where the OTAPkg file gets downloaded to? I'm trying to preserve the file and not have to download it again and again after a fail update. Thanks.
Edit: n/m found it, it's under the FUMO folder within the internal SD.
Please save a copy. We need it for a custom rom
Sent from my HTC One_M8 using XDA Free mobile app
johnnyutah22 said:
Please save a copy. We need it for a custom rom
Sent from my HTC One_M8 using XDA Free mobile app
Click to expand...
Click to collapse
I'm lost. I installed the 4.4.4 OTA, installed the latest CM12 nightly, and now I have no cell service nor options to select/enter an apn. Under apn it states "access point names not available for this user" HElP?!
ALSO, what custom roms can I run using this 4.4.4 OTA?!
bford152 said:
I'm lost. I installed the 4.4.4 OTA, installed the latest CM12 nightly, and now I have no cell service nor options to select/enter an apn. Under apn it states "access point names not available for this user" HElP?!
ALSO, what custom roms can I run using this 4.4.4 OTA?!
Click to expand...
Click to collapse
I can't help you with CM12, but I just installed Viper One and it seems to work fine.
I updated to the 4.4.4 via OTA yesterday, and Viper installed without a hitch.
NB: Make a Nandroid Backup before flashing please.
Whats the best way to update my girlfriend's rooted M8? Currently running 4.4.2 rooted S-ON. Can she just take OTA and then will have to re-root?
I'm S-OFF on my phone so I haven't had to deal with this. Already updated my firmware months ago and have been running 4.4.4 roms.
Thanks!!
Downloading it now.
You'll have to re-flash stock recovery, take the OTA update, then restore twrp (or other custom recovery) and re-root.
Could someone help me with the OTA update. I'm on stock 4.4.2 rooted and s-off. I placed back all the at&t crap in systems and tried my best to restore everything back to stock even recovery. I'm still getting a red triangle approx like 1/4 the way during the update. What sucks is that I have to download the whole update file again and it's 800+megs versus the prior updates which were a lot smaller. It's just very time consuming and would like to find out the root of the issue is.
I've done so many mods on the phone like the HK mod and various other ones. I'm trying to think back now to see if there is anything else and now I'm stuck. I don't want to restore my stock nandroid cause I would have to install everything all over again which would suck big time. I uninstall the drivers for viper4android, xposed, and even reverted the host file back from adaway. I just feel like there might be something within the system files that isn't suppose to be there. I even got rid of the att boot logo and sound but I had restored that back to stock as well. Please help if you could. Thanks.
Also is there anyway to flash twrp without using a pc? I tried flashify but it doesn't seem to be working cause it would revert back to the fastboot no matter what.
Same situation here I think... stock rom (never changed it yet), rooted, unlocked, s-off. Downloaded OTA then realized I needed to flash original recovery back. Did that, now AT&T sw update is of course telling me to wait 24 hours to check again. Any way around that?
jeremyenos said:
Same situation here I think... stock rom (never changed it yet), rooted, unlocked, s-off. Downloaded OTA then realized I needed to flash original recovery back. Did that, now AT&T sw update is of course telling me to wait 24 hours to check again. Any way around that?
Click to expand...
Click to collapse
Yeah just manually change the date one day ahead and try it again. It might take a couple of secs for it to prompt that there is an update.
I just posted a pre-rooted ruu in the dev section.
Backup data in twrp to your ext sd. Flash ruu via sd card method. Flash twrp using the free app flashify. Reboot to twrp and restore data.
No pc required.
Just make sure you backup files on internal.
volcalstone said:
Could someone help me with the OTA update. I'm on stock 4.4.2 rooted and s-off. I placed back all the at&t crap in systems and tried my best to restore everything back to stock even recovery. I'm still getting a red triangle approx like 1/4 the way during the update. What sucks is that I have to download the whole update file again and it's 800+megs versus the prior updates which were a lot smaller. It's just very time consuming and would like to find out the root of the issue is.
I've done so many mods on the phone like the HK mod and various other ones. I'm trying to think back now to see if there is anything else and now I'm stuck. I don't want to restore my stock nandroid cause I would have to install everything all over again which would suck big time. I uninstall the drivers for viper4android, xposed, and even reverted the host file back from adaway. I just feel like there might be something within the system files that isn't suppose to be there. I even got rid of the att boot logo and sound but I had restored that back to stock as well. Please help if you could. Thanks.
Also is there anyway to flash twrp without using a pc? I tried flashify but it doesn't seem to be working cause it would revert back to the fastboot no matter what.
Click to expand...
Click to collapse
There's a boot loader flashable twrp in the dev section posted by jball
dottat said:
I just posted a pre-rooted ruu in the dev section.
Backup data in twrp to your ext sd. Flash ruu via sd card method. Flash twrp using the free app flashify. Reboot to twrp and restore data.
No pc required.
Just make sure you backup files on internal.
Click to expand...
Click to collapse
I noticed that flashify also will install CWM or Philz. Is your method specific to TWRP or can you use the others. The reason I ask is because I currently use Philz and would need that to restore my backup.
johnnyutah22 said:
I noticed that flashify also will install CWM or Philz. Is your method specific to TWRP or can you use the others. The reason I ask is because I currently use Philz and would need that to restore my backup.
Click to expand...
Click to collapse
You can flash whichever you use.
I thought I read where this update would include the EYE Experience. Did I read that wrong or do I just not know how to use my camera anymore?
volcalstone said:
Could someone help me with the OTA update. I'm on stock 4.4.2 rooted and s-off. I placed back all the at&t crap in systems and tried my best to restore everything back to stock even recovery. I'm still getting a red triangle approx like 1/4 the way during the update. What sucks is that I have to download the whole update file again and it's 800+megs versus the prior updates which were a lot smaller. It's just very time consuming and would like to find out the root of the issue is.
I've done so many mods on the phone like the HK mod and various other ones. I'm trying to think back now to see if there is anything else and now I'm stuck. I don't want to restore my stock nandroid cause I would have to install everything all over again which would suck big time. I uninstall the drivers for viper4android, xposed, and even reverted the host file back from adaway. I just feel like there might be something within the system files that isn't suppose to be there. I even got rid of the att boot logo and sound but I had restored that back to stock as well. Please help if you could. Thanks.
Click to expand...
Click to collapse
I don't think root changes are the issue; as typically it will fail before it even goes into recovery with a message that the system has been modified. It might just be a bad download.
Setting up your phone again is really not that bad a proposition; especially if you use Titanium to restore apps. And it will also restore your Xposed installer and modules. Using Titanium, I can easily be up and fully configured again in about a half hour after a factory reset or RUU. Although, of course this will depend on the amount of customization in settings, etc.
You might consider updating with the new RUU (relocking bootloader required if s-on). Not only will this bypass the OTA install issue you are having, but makes for a cleaner install. Yes, you will have to set the phone up again; and you will also need to backup any data on internal storage, as it will be wiped by RUU.