Will installing the small update kill my root? - OnePlus 3T Questions & Answers

Well the small update kill my root, if not, what can or will it do?

possible, but just root again after your first start up.

LicQuyd said:
Well the small update kill my root, if not, what can or will it do?
Click to expand...
Click to collapse
Hi,
As usual, some research in "guides.." section and you'll find a nice topic with all explanations you need to make your update...
Cheerz
Sent from my OnePlus3T using XDA Labs

when you update the bootloader might relock just flash it through TWRP and flash SuperSU again after.

Related

[Q] Simple root for Nexus One

Noob here. I've searched the forums and have tried to piece together what I need to know for what I would like to do. I think I have a general understanding, but was hoping someone could verify or clarify.
I've got a Nexus 1 running 2.3.3. Never been rooted. All OTA updates.
What I would like is to root it so that I can delete crap like Facebook and Amazon and make room on the built-in memory. I don't want to unlock the boot-loader, and I don't want to flash custom ROMs. I do want control of what is stored where, the ability to move things to SD (even if they aren't marked for that (and yes, aware that that can cause problems sometimes)), and the ability to run Titanium backup.
As I understand it, all of that can be done with just root permission. But it seems that simple root for the N1 under 2.3.3 isn't available. Can anyone comment?
Thanks,
DT
Depends what you call simple...
Since you don't want to unlock the bootloader, you can try using the passimg method to revert to an earlier build of android, and then use any "simple root" available.
Unfortunately, a small percentage of users don't seem to be able to use the passimg method, and if you get an "main version is older" error, then it means you are among them...
Passimg method can be found in the wiki, under the unroot/restore guide (passimg method, using FRG33):
http://forum.xda-developers.com/wik...des_&_Tutorials#Unroot_.2F_Restore_your_Nexus
Sent from my Nexus One using XDA Premium App
Good luck rooting, without trying to unlock the bootloader. It's simply not available atm I belive. Any particular reason you don't want to unlock the bootloader, beside the warranty?
root without unlocking bootloader
I'm still coming up to speed on this, so it's quite possible that I don't understand all the subtleties.
What I want to do is uninstall space-wasting preinstalled junk, and to run Titanium backup. I'm not interested (for now) in custom ROMs. I think I want to avoid unlocking the bootloader both for the warranty (a minor issue), convenience (another minor issue that could be overcome...), and because I want to retain as much of a "stock" device as possible, mostly to allow for future OTA updates. From what I've read, it sounds like a root would accomplish all that. Hence I'd rather avoid all the additional complications if a simple root were in fact available.
Thanks for the help,
DT
Unlocking the bootloader does not affect you device's ability to receive/install OTA updates, but removing "space-wasting preinstalled junk" will certainly prevent you from installing the OTA...
Sent from my Nexus One using XDA Premium App
efrant said:
Unlocking the bootloader does not affect you device's ability to receive/install OTA updates, but removing "space-wasting preinstalled junk" will certainly prevent you from installing the OTA...
Click to expand...
Click to collapse
Totally agree. If you check the threads that were active during the OTA onslaught, many people could not install stock Gingerbread due to removing stock system apps (Facebook, Amazon, Twitter, etc...)
...but, if you have a custom recovery, you can still install the updates in a modified form.
Sent from my Nexus One using XDA Premium App
danger-rat said:
...but, if you have a custom recovery, you can still install the updates in a modified form.
Sent from my Nexus One using XDA Premium App
Click to expand...
Click to collapse
Really? I was unaware of that. Would you mind posting a link to an OTA (say, Gingerbread for example) that I would be able to install on a stock Froyo ROM, which I had removed say, Amazon and Facebook?
Thanks.
Thanks for the info. I hadn't thought about the OTA being affected by removal of unwanted programs.
DT
I would just passimg back to stock 2.2 and then root it with z4root
Sent from my GT-I9000 using XDA Premium App
efrant said:
Really? I was unaware of that. Would you mind posting a link to an OTA (say, Gingerbread for example) that I would be able to install on a stock Froyo ROM, which I had removed say, Amazon and Facebook?
Thanks.
Click to expand...
Click to collapse
I said modified - meaning rooted, or even just having the verifications taken out of the update script...
Sent from my Nexus One using XDA Premium App
danger-rat said:
I said modified - meaning rooted, or even just having the verifications taken out of the update script...
Sent from my Nexus One using XDA Premium App
Click to expand...
Click to collapse
I was just asking if anyone has done this (or does this), as I would certainly love to remove apps, as long as I can install future updates as they become available. (Doing that is beyond my knowledge...) I like my stock ROM, and I would certainly remove certain apps if I know someone would provide a "modified" update.zip for a stock ROM that doesn't check if Amazon, etc are installed.
What I don't want is to flash a new ROM every time an update came out...
It is very simple. If you remove stuff from the stock rom the ota will fail.
You will then need flash the same way as you would for any of the custom roms for updates.
Or you could manually put the stuff you removed back but that is probably more work then you want to do.
Sent from my Nexus One using XDA App
Easiest approach would probably be to take a backup of the stock image before you remove any apps, and restore it when you hear that an update is available...
Sent from my Nexus One using XDA Premium App
danger-rat said:
Easiest approach would probably be to take a backup of the stock image before you remove any apps, and restore it when you hear that an update is available...
Sent from my Nexus One using XDA Premium App
Click to expand...
Click to collapse
Restoring a NAND backup is essentially the same thing as flashing a new ROM, which is what I don't want to be doing. What would be good is to be able to install a modified/repacked/whatever-you-want-to-call-it OTA update file that has the check (which checks to see if apps are installed) disabled.
If it is just a line in a script that needs to be removed in an OTA, so that it will flash (with a custom recovery of course) with Amazon removed, it is surely doable, no? If it is doable, I am surprised that no one has done it for any of the updates... (at least I haven't seen any).
albundy2010 said:
It is very simple. If you remove stuff from the stock rom the ota will fail.
You will then need flash the same way as you would for any of the custom roms for updates.
Or you could manually put the stuff you removed back but that is probably more work then you want to do.
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
Thanks, but my question was: is it possible to modify an OTA zip file in such a way that it disables checking for installed apps like Amazon?
This would be helpful, and I had never thought of it until danger-rat mentioned it, but I may have misunderstood his post - he was probably talking about just flashing a new ROM, but that is not what I am interested in.
Yes, it's possible.
The update script is pretty big though, so you'd have your work cut out making sure you covered everything...
The other option would be to build an restore zip, that just reinstalled the apps you remove. Just add the apps to a zip as you restore them...
Sent from my Nexus One using XDA Premium App
danger-rat said:
Yes, it's possible.
The update script is pretty big though, so you'd have your work cut out making sure you covered everything...
The other option would be to build an restore zip, that just reinstalled the apps you remove. Just add the apps to a zip as you restore them...
Sent from my Nexus One using XDA Premium App
Click to expand...
Click to collapse
That sounds like a good idea.
This is what I'd like to do as a test:
1) Restore a stock Froyo ROM
2) Remove the Amazon.apk (and possibly others) from my ROM and save it somewhere (and whatever other files would be needed).
3) Create an update.zip file that would place the Amazon.apk file back to the correct directory in a stock ROM (i.e., odexed).
4) Flash that update.zip
5) Flash the Gingerbread OTA and see if it works.
Would you be able to point me to a guide on how to create a flashable zip? Again, I would need to be able to do this for an odexed ROM.
Thanks.
EDIT: Nevermind. I found it here: http://www.londatiga.net/it/how-to-create-android-update-zip-package/
ameedi600 said:
I would just passimg back to stock 2.2 and then root it with z4root
Sent from my GT-I9000 using XDA Premium App
Click to expand...
Click to collapse
I agree this is what I did had no problems at all

Root Xperia Z and still get OTA?

Hi. New to Xperia phone, coming from S3. So far loving it! just wondering if I can root and still have the option to get OTA from Sony? Don't want to loose bravia engine 2 (yet) so only need root to remove som bloatwares and install some apps. Also, if that is possible to get OTA with root, will updating the phone remove root?
Thanks!
Sent from my C6603 using xda app-developers app
UnLucky12 said:
Hi. New to Xperia phone, coming from S3. So far loving it! just wondering if I can root and still have the option to get OTA from Sony? Don't want to loose bravia engine 2 (yet) so only need root to remove som bloatwares and install some apps. Also, if that is possible to get OTA with root, will updating the phone remove root?
Thanks!
Sent from my C6603 using xda app-developers app
Click to expand...
Click to collapse
Use pro features of SuperSU or OTA Rootkeeper to protect your root, then when you OTA update you should be fine. Try not to modify anything in the System partition otherwise OTA will probably fail (is my understanding), or if you do (i.e. renaming various apks/odex files to .bak), make sure you put them back before OTA updating, in case they need to be patched.
Thanks for the reply! I was only thinking of installing adaway, also the whitecontroll mod to the Xperia. How do I then remove them like the whitecontroll app witch is intergrated in to the system?
If it removes root, I can always reroot the device
Sent from my C6603 using xda app-developers app
UnLucky12 said:
Thanks for the reply! I was only thinking of installing adaway, also the whitecontroll mod to the Xperia. How do I then remove them like the whitecontroll app witch is intergrated in to the system?
If it removes root, I can always reroot the device
Sent from my C6603 using xda app-developers app
Click to expand...
Click to collapse
I'm not sure about the WB control, I imagine that would likely prevent OTA due to libs inserted in to /system, perhaps if you were to perform the installation manually, take note of all files inserted, and backup any (if any) files it overwrites you could restore it before OTA.
As for AdAway, it only changes your host file, which shouldn't affect OTA, since I doubt Sony will make any changes to it OTA, but AdAway can be "undone" from within the app, so you can do that easily anyway.
It's hard to say really and depends on the OTA, but generally, from my experience, if the OTA contains a patch for a particular file, it will MD5 it, and if that fails, OTA will fail, if you have modified files that aren't patched as part of the OTA you shouldn't have a problem.
That said, I have little experience with Sony OTA files, and without looking at the script for any particular OTA you can never tell what they might check or change.
The only recommendation I can give really, is that if you want to OTA, change as LITTLE as possible in the /system partition, and make sure to revert any changes before attempting to apply an OTA.
If that is too much effort, and all you're really concerned about is you data, use Titanium Backup to keep everything safe, modify anything you want in system, then flash a stock ROM before you OTA update. You could also just flash a stock system partition, perhaps from a nandroid? before you OTA, and that should also solve the problem.
As you don't unlock your bootloader you're safe.
But OTA doesn't always works even in locked bootloader, tried yesterday to OTA update my locked bootloader Xperia T to .140 fw but it failed because of root, even after unroot with superSU option it failed.
Backup everything, update with SUS or PCC and reroot with binary tool using goroh_kun exploit included in the tool..
alias_neo said:
I'm not sure about the WB control, I imagine that would likely prevent OTA due to libs inserted in to /system, perhaps if you were to perform the installation manually, take note of all files inserted, and backup any (if any) files it overwrites you could restore it before OTA.
As for AdAway, it only changes your host file, which shouldn't affect OTA, since I doubt Sony will make any changes to it OTA, but AdAway can be "undone" from within the app, so you can do that easily anyway.
It's hard to say really and depends on the OTA, but generally, from my experience, if the OTA contains a patch for a particular file, it will MD5 it, and if that fails, OTA will fail, if you have modified files that aren't patched as part of the OTA you shouldn't have a problem.
That said, I have little experience with Sony OTA files, and without looking at the script for any particular OTA you can never tell what they might check or change.
The only recommendation I can give really, is that if you want to OTA, change as LITTLE as possible in the /system partition, and make sure to revert any changes before attempting to apply an OTA.
If that is too much effort, and all you're really concerned about is you data, use Titanium Backup to keep everything safe, modify anything you want in system, then flash a stock ROM before you OTA update. You could also just flash a stock system partition, perhaps from a nandroid? before you OTA, and that should also solve the problem.
Click to expand...
Click to collapse
So I can make a nandroid backup with only root? Using Rom Manager app. Or do I need to unlock the bootlocker? If I can, then I can just recover from nandroid that are stock, update then backup again, change systemlibs etc?
Sent from my C6603 using xda app-developers app
babylonbwoy said:
As you don't unlock your bootloader you're safe.
But OTA doesn't always works even in locked bootloader, tried yesterday to OTA update my locked bootloader Xperia T to .140 fw but it failed because of root, even after unroot with superSU option it failed.
Backup everything, update with SUS or PCC and reroot with binary tool using goroh_kun exploit included in the tool..
Click to expand...
Click to collapse
I see! Hmmm. But SUS?
Sent from my C6603 using xda app-developers app
UnLucky12 said:
I see! Hmmm. But SUS?
Sent from my C6603 using xda app-developers app
Click to expand...
Click to collapse
I believe SUS is Sony Update Service.
Technically, you should be able to nandroid with recovery for locked bootloader then restore system before OTA, but if Sony OTA checks somehow prevent it because of an md5 on the entire partition or some such, you will have to re flash a totally stock System, perhaps a custom FTF(?), update then root again.
Next time we get an OTA I'll test the process myself, but until then I can only speculate. Hopefully someone else has more concrete information.
Sent from my C6603 using Tapatalk 2
alias_neo said:
I believe SUS is Sony Update Service.
Technically, you should be able to nandroid with recovery for locked bootloader then restore system before OTA, but if Sony OTA checks somehow prevent it because of an md5 on the entire partition or some such, you will have to re flash a totally stock System, perhaps a custom FTF(?), update then root again.
Next time we get an OTA I'll test the process myself, but until then I can only speculate. Hopefully someone else has more concrete information.
Sent from my C6603 using Tapatalk 2
Click to expand...
Click to collapse
Thanks man! But Stock rom for the XZ. How or where can I download it? Supposed to use SUS or PCC? What is best?
Sorry for being such a noob. Don't want to totally destroy my phone hehe.
Sent from my C6603 using xda app-developers app
UnLucky12 said:
Thanks man! But Stock rom for the XZ. How or where can I download it? Supposed to use SUS or PCC? What is best?
Sorry for being such a noob. Don't want to totally destroy my phone hehe.
Sent from my C6603 using xda app-developers app
Click to expand...
Click to collapse
No problem, I, and I imagine others prefer to answer questions from cautious users than those all gung-ho, brick their devices then come crying for help. Ask first, flash later
As for which tool, I hope someone else can comment, I've always been a Samsung man until now so I've never used either tool yet.
As for stock firmwares, there are loads in the Dev section. Just pick the right one and flash it however they recommend.
Sent from my C6603 using Tapatalk 2
alias_neo said:
No problem, I, and I imagine others prefer to answer questions from cautious users than those all gung-ho, brick their devices then come crying for help. Ask first, flash later
As for which tool, I hope someone else can comment, I've always been a Samsung man until now so I've never used either tool yet.
As for stock firmwares, there are loads in the Dev section. Just pick the right one and flash it however they recommend.
Sent from my C6603 using Tapatalk 2
Click to expand...
Click to collapse
Yeah, and thanks for the help Hope your answers will also help other that also wonders about the same thing
Arent there a program or website to download the official firmwares? Or using SUS automatically update it to stock?
Sent from my C6603 using xda app-developers app
UnLucky12 said:
Yeah, and thanks for the help Hope your answers will also help other that also wonders about the same thing
Arent there a program or website to download the official firmwares? Or using SUS automatically update it to stock?
Sent from my C6603 using xda app-developers app
Click to expand...
Click to collapse
I believe so. Buy don't quote me on that, like I said, never used it.
Sent from my C6603 using Tapatalk 2
It's the same if you use Sony Update Service or PC Compagnon, PCC contain other tool, while SUS only update. Also you can use Flashtool by Androxyde (here on XDA) to flash firmware converted in ftf format. Sony also relased it's own tool named flashtool to flash unlocked bootloader mobile because you can't use SUS/PCC when it's unlocked.
Read this thread "All the info you need before you begin" http://forum.xda-developers.com/showthread.php?t=2153167

TWRP problem with flashing.

I downloaded TWRP from google play and it installed ok but when I try to install I swipe but it just reboots the phone.
Any suggestions?
Sent from my C6603 using xda app-developers app
List everything you've done to your Phone right up to installing it.
XperienceD said:
List everything you've done to your Phone right up to installing it.
Click to expand...
Click to collapse
I rooted my phone and tried to install CWM on locked bootloader but it doesnt install but I can flash zips when trying to install from pc.The phone reboots into CWM recovery and I can flash this way. I do this each time I want to flash.
I installed TWRP manager from playstore and tried to flash but everytime I swipe the phone just turns off.
Sent from my C6603 using xda app-developers app
TWRP Manager requires that you have TWRP installed already. It is just an interface to use functions of the recovery that you already flashed. It does not install TWRP for you. It uses openrecovery scripts that are not compatible with CWM recovery, so that's why nothing happens when you try to install zips via the manager.
I don't mean this in a bad way at all, but by seeing some of the threads you have created in this forum, perhaps it's best that you go back to stock and don't mess with your phone in this way. It seems that you are unable or unwilling to research what you're doing before jumping in with both feet and just run here afterwards expecting to get your problems resolved by people that do bother to read up on these things.
This is just meant as a friendly piece of advice before you manage to permanently brick your expensive phone
Sent from my C6603 using Tapatalk 2
kingvortex said:
TWRP Manager requires that you have TWRP installed already. It is just an interface to use functions of the recovery that you already flashed. It does not install TWRP for you. It uses openrecovery scripts that are not compatible with CWM recovery, so that's why nothing happens when you try to install zips via the manager.
I don't mean this in a bad way at all, but by seeing some of the threads you have created in this forum, perhaps it's best that you go back to stock and don't mess with your phone in this way. It seems that you are unable or unwilling to research what you're doing before jumping in with both feet and just run here afterwards expecting to get your problems resolved by people that do bother to read up on these things.
This is just meant as a friendly piece of advice before you manage to permanently brick your expensive phone
Sent from my C6603 using Tapatalk 2
Click to expand...
Click to collapse
Thanks for your reply.
I have searched and read up but asking questions and getting a reply helps a lot when I am unsure on certain things.
I have rooted my phone without any problems and it was easy and have many apps running which are only available on root.
Hardly without problems!
http://forum.xda-developers.com/showthread.php?t=2372435
Don't forget that anyone can look at your post history
Anyway, my point is that you should research more thoroughly before proceeding with modding your expensive device. It is possible that you could do something that will cause an unrecoverable brick.
Sent from my C6603 using Tapatalk 2
kingvortex said:
Hardly without problems!
http://forum.xda-developers.com/showthread.php?t=2372435
Don't forget that anyone can look at your post history
Anyway, my point is that you should research more thoroughly before proceeding with modding your expensive device. It is possible that you could do something that will cause an unrecoverable brick.
Sent from my C6603 using Tapatalk 2
Click to expand...
Click to collapse
That was my own error and using a pc which has a mind of it's own, used my new one and it was resolved instantly.
I do jump in without reading, I will not do so anymore.

[ODIN][TAR] 4.4 I9505GUEUBMKG Full Rooted Restore

MKG is released.
WARNING: Stop asking if you can flash this on other phones. You can NOT. It is meant for the I9505G ONLY. This is NOT a "rom". This is a system image for the I9505G. Flashing to any other phone will brick it.
Kernel Source:
http://opensource.samsung.com/reception/receptionSub.do?method=search&searchValue=GT-I9505G
OTA zip (must be flashed in stock recovery) [Thanks @Danvdh for the link]:
http://android.clients.google.com/p...SS-I9505GUEUBMH5-to-UCMKG_Update_FWD_user.zip
Root method (does not overwrite stock recovery):
http://www.mediafire.com/download/tnzz95y5847z587/S4_GPE_ROOT.zip
ODIN FULL RECOVER IMAGE (root is built in):
Shamelessly stealing @MJHawaii instructions from this thread (THANK YOU):
http://forum.xda-developers.com/showthread.php?t=2398217
(DISCLAIMER) Please read and follow the instructions carefully. I nor anyone else on this forum is responsible if you brick your phone, lose your job, or life as you know it ends. Make sure you fully Understand what you're doing before you do it. Modifying any phone comes with a risk.
INSTRUCTIONS:
WARNING: Please do not flash this if you're low on battery...go charge your phone!
o) Download the I9505GUEUBxxx_FULL_ROOTED.tar.md5.gz package from below
o) Make sure you have the USB Drivers installed and you have Odin 3.09 from below
o) Put your phone in download mode and connect it to USB:
-Disconnect the phone from USB
-Power OFF your phone
-Hold Volume Down, Home, and Power
-When the "WARNING!!!" screen comes up, release the buttons
-Volume up to enter download mode
-Connect the phone to USB
o) Open Odin
o) Click on AP, then select the I9505GUEUBxxx_FULL_ROOTED.tar.md5.gz package you downloaded
o) Odin will extract the tar md5 file from the gzip archive, and this will take a while...be patient
o) Once the tar md5 is loaded, make sure you have a COM PORT in Odin ( any )
o) Click Start and wait till it finishes flashing...your phone should reboot when it's done
NOTE: If your phone does not boot, then boot into stock recovery and Wipe Data Factory Reset.
DOWNLOADS:
ODIN 3.09
I9505GUEUBMKG_FULL_ROOTED.tar.md5.gz
A GIANT thank you to @MJHawaii for helping me learn this process!!!
This might be a stupid thing to ask but is there Knox on the Google play edition?
Sent from my GT-I9505 using XDA Premium 4 mobile app
Not to my knowledge. But that's far from a definitive answer.
screenshot
Loaded up and running great so far. Gotta remember that the icons for connections are white. Thought I had a problem at first. Will test and let you know if I find issues.
THANKS for the quick work.
Great, thanks for testing!
You guys have no idea how badly I wanna flash that baby in my i337m.
Guess I have to wait for MjHawaii
Sent from my SGH-I337M using xda app-developers app
Root after 4.4 OTA
Thanks SamuriHL!
This may be an easy question. Actually, I hope it is...
I want to sideload the 4.4 OTA zip and then get Root back after the update. How do I root the phone after I sideload the OTA? I already downloaded the s$_GPE_ROOT.zip file. Thanks in advance.
crzygrmn said:
You guys have no idea how badly I wanna flash that baby in my i337m.
Guess I have to wait for MjHawaii
Sent from my SGH-I337M using xda app-developers app
Click to expand...
Click to collapse
I do, but DON'T. It will brick your phone. My wife has one, too. She'll be waiting.
calidroidguy said:
Thanks SamuriHL!
This may be an easy question. Actually, I hope it is...
I want to sideload the 4.4 OTA zip and then get Root back after the update. How do I root the phone after I sideload the OTA? I already downloaded the s$_GPE_ROOT.zip file. Thanks in advance.
Click to expand...
Click to collapse
The S4_GPE_ROOT has an older SuperSU zip file in it. Grab the latest one from chainfire as they've done updates for 4.4 recently. Just delete the one from the S4_GPE_ROOT directory and drop in the new one. The script will automagically pick it up. After that, just run the script and follow directions. That's all there is to it. Make sure you have Koush's ADB driver installed. It's included in the S4_GPE_ROOT zip.
SamuriHL said:
I do, but DON'T. It will brick your phone. My wife has one, too. She'll be waiting.
Click to expand...
Click to collapse
I know I cant. If it was just as easy as 9505 roms where I can just flash away
Sent from my SGH-I337M using xda app-developers app
crzygrmn said:
I know I cant. If it was just as easy as 9505 roms where I can just flash away
Sent from my SGH-I337M using xda app-developers app
Click to expand...
Click to collapse
MJ will get something out soon, I'm sure. He's been waiting for this release and I know he's got some stuff cooking for it. Hang in there.
silly question probably, can I flash it on a regular I9505 (not a GE)?
CoLiran said:
silly question probably, can I flash it on a regular I9505 (not a GE)?
Click to expand...
Click to collapse
NO
We have to wait.
Sent from my SGH-I337M using xda app-developers app
crzygrmn said:
NO
We have to wait.
Sent from my SGH-I337M using xda app-developers app
Click to expand...
Click to collapse
bummer :good:
Battlehero said:
This might be a stupid thing to ask but is there Knox on the Google play edition?
Sent from my GT-I9505 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
No KNOX on Google Play Edition.
SamuriHL said:
The S4_GPE_ROOT has an older SuperSU zip file in it. Grab the latest one from chainfire as they've done updates for 4.4 recently. Just delete the one from the S4_GPE_ROOT directory and drop in the new one. The script will automagically pick it up. After that, just run the script and follow directions. That's all there is to it. Make sure you have Koush's ADB driver installed. It's included in the S4_GPE_ROOT zip.
Click to expand...
Click to collapse
Sweet. Thanks. I'm now updated to 4.4 and rooted. I did receive a couple error messages that Calendar Storage had stopped responding right after the update. Hopefully that won't be a recurring issue.
thx i'll extract blobs
Great Job SamuriHL thank you for your hard work. Updating sticky tonight
Sent from my Nexus 5 using Tapatalk
I suppose the GE launcher from Nexus 5 isn't part of the ROM or is it?

Help doing Ota updating on rooted device!

Got a problem here... Wanted to ota to 4.4 in my rooted, s-off on stock rom.
Flashed stock recovery and downloaded the Ota but it turns to red triangle as its installing.
My question is would this be happening due to having Xposed framework and having Flashed some zips for ad blocking and such? Any feedback is much appreciated!
Also, if that is the issue, would flashing an old backup work if that was prior to using Xposed and such?
Please help! Thanks!
irtrueno said:
Also, if that is the issue, would flashing an old backup work if that was prior to using Xposed and such?
Please help! Thanks!
Click to expand...
Click to collapse
In order to take the ota you have to be on a stock rom
Sent from my HTCONE using Tapatalk
luigi311 said:
In order to take the ota you have to be on a stock rom
Sent from my HTCONE using Tapatalk
Click to expand...
Click to collapse
yes I am on stock rom. Would having xposed cause issues? Or anything that edits the system?
irtrueno said:
yes I am on stock rom. Would having xposed cause issues? Or anything that edits the system?
Click to expand...
Click to collapse
Maybe. The ota might check what's in the system partitions such as apps and such and if there's anything that usually isn't there when the phone is stock it might not update. I asked on the Verizon forum if it's possible to update after deleting some system apps and they said no but I've never tried it.
Sent from my HTCONE using Tapatalk
luigi311 said:
Maybe. The ota might check what's in the system partitions such as apps and such and if there's anything that usually isn't there when the phone is stock it might not update. I asked on the Verizon forum if it's possible to update after deleting some system apps and they said no but I've never tried it.
Sent from my HTCONE using Tapatalk
Click to expand...
Click to collapse
I eventually was able to update. I restored a backup I did before root, right after unlocking bootloader.
also, I used an old stock recovery. I found the most recent stock recovery and used that and it worked. so still unsure what exactly caused my problems but using the latest stock recovery and using unmodified stock rooted rom worked.
thanks for the response though, much appreciated. definitely soft bricked my phone few times before getting it done. phew...

Categories

Resources