Related
Please forgive me for having to ask what I'm sure sounds like a stupid question, but I have no idea how to accept the OTA update Verizon is attempting to send me to version 4.4.4 on my HTC One M8 now that I have used Sunshine to attain S-Off and have TWRP and SuperSU installed.
I have used ADB, but am not very familiar with it at all.
I saw threads talking about flashing ROMS, but for the most part it really seems like Greek to me.
I had only gone down the Sunshine road because I wanted root access mainly for one app--Lightflow. In retrospect I'm feeling like I opened a can of worms. But the can is open, and the worms are out there, so now I need to learn how to handle them.
I know I am supposed to keep S-off, no matter what I do. I think perhaps I'm supposed to revert back somehow to a "stock" bootloader (instead of TWRP--is that right?) but I don't have any idea how to do that (though I expect ADB is involved), and I also don't know what effect that would have on SuperSu, as I vaguely recall TWRP may have been required for SuperSU to work.
I'm really lost.
Any help, in very easy to understand terms (pretend you're trying to explain this to your grandmother) would be appreciated.
Thanks!
Andyw2100 said:
Please forgive me for having to ask what I'm sure sounds like a stupid question, but I have no idea how to accept the OTA update Verizon is attempting to send me to version 4.4.4 on my HTC One M8 now that I have used Sunshine to attain S-Off and have TWRP and SuperSU installed.
I have used ADB, but am not very familiar with it at all.
I saw threads talking about flashing ROMS, but for the most part it really seems like Greek to me.
I had only gone down the Sunshine road because I wanted root access mainly for one app--Lightflow. In retrospect I'm feeling like I opened a can of worms. But the can is open, and the worms are out there, so now I need to learn how to handle them.
I know I am supposed to keep S-off, no matter what I do. I think perhaps I'm supposed to revert back somehow to a "stock" bootloader (instead of TWRP--is that right?) but I don't have any idea how to do that (though I expect ADB is involved), and I also don't know what effect that would have on SuperSu, as I vaguely recall TWRP may have been required for SuperSU to work.
I'm really lost.
Any help, in very easy to understand terms (pretend you're trying to explain this to your grandmother) would be appreciated.
Thanks!
Click to expand...
Click to collapse
Taking the OTA is simple, you'll need your stock 4.4.3 recovery installed not TWRP. If you try to take it as you are right now it will fail everytime because of TWRP. I'm going to assume you haven't modified your stock ROM in anyway so accept the OTA and let it install. You will not lose S-OFF so rooting is simple. Reinstall TWRP and flash the latest SuperSU zip file.
The Stig 04 said:
Taking the OTA is simple, you'll need your stock 4.4.3 recovery installed not TWRP. If you try to take it as you are right now it will fail everytime because of TWRP. I'm going to assume you haven't modified your stock ROM in anyway so accept the OTA and let it install. You will not lose S-OFF so rooting is simple. Reinstall TWRP and flash the latest SuperSU zip file.
Click to expand...
Click to collapse
Thanks for the response.
So the question is how do I go back to my stock recovery instead of TWRP?
And then after taking the update, what do I need to do to reinstall TWRP and then flash the latest SuperSU.zip file?
I realize I should know this stuff, but I had help from the Sunshine folks last time, so I really don't remember everything that went on, or exactly what I did vs. what they did, etc.
Thanks again!
Andyw2100 said:
Thanks for the response.
So the question is how do I go back to my stock recovery instead of TWRP?
And then after taking the update, what do I need to do to reinstall TWRP and then flash the latest SuperSU.zip file?
I realize I should know this stuff, but I had help from the Sunshine folks last time, so I really don't remember everything that went on, or exactly what I did vs. what they did, etc.
Thanks again!
Click to expand...
Click to collapse
You don't need to do any of that.
Download the exe from this thread: http://forum.xda-developers.com/showthread.php?p=56211035
run it and you will be on stock 4.4.4.
To get TWRP back you have to flash it fastboot (lots of tutorials all over the forum for that) and with the recovery installed you can just flash SuperSU in recovery to gain root again.
The Stig 04 said:
Taking the OTA is simple, you'll need your stock 4.4.3 recovery installed not TWRP. If you try to take it as you are right now it will fail everytime because of TWRP. I'm going to assume you haven't modified your stock ROM in anyway so accept the OTA and let it install. You will not lose S-OFF so rooting is simple. Reinstall TWRP and flash the latest SuperSU zip file.
Click to expand...
Click to collapse
berndblb said:
You don't need to do any of that.
Download the exe from this thread: http://forum.xda-developers.com/showthread.php?p=56211035
run it and you will be on stock 4.4.4.
To get TWRP back you have to flash it fastboot (lots of tutorials all over the forum for that) and with the recovery installed you can just flash SuperSU in recovery to gain root again.
Click to expand...
Click to collapse
Thanks. That thread says that using that .exe is going to wipe my phone, which would then mean I need to restore it from a backup. I think I'd really just rather take the OTA update to 4.4.4, since in the future I'm going to want to take other OTA updates as well. So if I can learn how to return to my stock recovery now, and the rest of it for this OTA update, I should be good to go for future OTA updates.
Thanks, though.
So my questions above remain about how to revert to the stock recovery, and then how to reinstall TWRP and SuperSU.
Thanks!
Andyw2100 said:
Thanks. That thread says that using that .exe is going to wipe my phone, which would then mean I need to restore it from a backup. I think I'd really just rather take the OTA update to 4.4.4, since in the future I'm going to want to take other OTA updates as well. So if I can learn how to return to my stock recovery now, and the rest of it for this OTA update, I should be good to go for future OTA updates.
Thanks, though.
So my questions above remain about how to revert to the stock recovery, and then how to reinstall TWRP and SuperSU.
Thanks!
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2723159
Download the file "Stock Recovery 4.4.3" from the thread above. Flash that using ADB, once you take the OTA and are on 4.4.4 Flash TWRP using ADB again.
http://forum.xda-developers.com/showthread.php?t=1538053
Download SuperSu from the thread above and place that in your SD Card. Boot into recovery and install it. Though you should already have this on your computer or SD Card.
Edit: I believe there is an even easier way, just have never done it/tried it so I don't wanna lie and act like I know what to do.
The Stig 04 said:
http://forum.xda-developers.com/showthread.php?t=2723159
Download the file "Stock Recovery 4.4.3" from the thread above. Flash that using ADB, once you take the OTA and are on 4.4.4 Flash TWRP using ADB again.
http://forum.xda-developers.com/showthread.php?t=1538053
Download SuperSu from the thread above and place that in your SD Card. Boot into recovery and install it.
Click to expand...
Click to collapse
You have to flash the stock recovery in fastboot - not ADB. And you gotta make sure all the bloatware that comes with the original stock rom is in place or the OTA will fail (it does a "system integrity check" prior to applying the OTA). That can be a headache if you do not have a backup of apps you may have removed...
Each future update will be available within days of release here on XDA, either as a standalone firmware update or stock rooted rom or both. I would not take OTAs - ever.
Develop a solid backup routine and restoring your device is a 20 minute exercise...
Thanks to both of you.
I don't believe I removed any bloatware, so I think the OTA update should work.
How do I flash the stock recovery in fastboot?
Again, many thanks!
I just checked my ADB folder, and see a fastboot.exe there, so I imagine it's just a command like ADB. I'll give this a shot later. Again, many thanks to both of you for the assistance. I will post again with, hopefully, my good results, or with additional questions.
Thanks!
berndblb said:
You have to flash the stock recovery in fastboot - not ADB. And you gotta make sure all the bloatware that comes with the original stock rom is in place or the OTA will fail (it does a "system integrity check" prior to applying the OTA). That can be a headache if you do not have a backup of apps you may have removed...
Each future update will be available within days of release here on XDA, either as a standalone firmware update or stock rooted rom or both. I would not take OTAs - ever.
Develop a solid backup routine and restoring your device is a 20 minute exercise...
Click to expand...
Click to collapse
Sorry I thought fastboot and ADB was kinda that same thing seeing as it was refereed to as "fastboot/adb directory"? If not my bad! Also this is the method I always use to take OTA's and have never ever had a problem.
Andyw2100 said:
I just checked my ADB folder, and see a fastboot.exe there, so I imagine it's just a command like ADB. I'll give this a shot later. Again, many thanks to both of you for the assistance. I will post again with, hopefully, my good results, or with additional questions.
Thanks!
Click to expand...
Click to collapse
Put the recovery image into the same folder with your fastboot.exe
Open a command prompt from that folder (shift + right click > open cmd window here)
check connection with
Code:
fastboot devices
if successful
Code:
fastboot flash recovery <name of recovery>.img
Would you need to remove root before taking the OTA? Just curious.
Sent from my GT-N5110 using xda app-developers app
mumbles202 said:
Would you need to remove root before taking the OTA? Just curious.
Sent from my GT-N5110 using xda app-developers app
Click to expand...
Click to collapse
No. You will lose root after the ota so it doesn't matter but you can always get it back as long as you are S-OFF by flashing a custom recovery like TWRP and then flashing SuperSu.
Well, I have run into a snag right off the bat.
While the command "ADB Devices" sees the phone, "Fastboot Devices" does not.
Any ideas as to how to rectify this?
Thanks!
I did some googling, and this problem I solved on my own.
I had to use adb to get into fastboot USB mode or something with adb reboot bootloader, and then fastboot devices worked.
I'm now continuing on.
Well, so much for this being easy.
I believe I successfully flashed my stock recovery.
But apparently I no longer have the OTA update ready to install, as at some point I tried to run it again just to get TWRP up, and now it's not showing as available. And when I try to check for updates in Settings/Software update/Check new I get an error message that says Download Unsuccessful. We were not able to download this update.
For now I guess I'll wait and see if Verizon tries to send me the update again, or if it works if I check for it myself some other time. (Or if anyone here has any suggestions.)
Also, I still seem to have root access. I thought that I wouldn't, since I believe I have replaced TWRP with the stock recovery.
I'm also now getting a constant error message about Google Play Services having stopped. And my wi-fi doesn't seem to be connecting properly.
I'm really wondering just what the heck I've done.
Well, for anyone still following my saga...
Things are somewhat better, but not totally resolved.
I kept checking, and eventually I was able to download the OTA update to 4.4.4. I did, I updated, and all went smoothly. I then was able to flash TWRP and then install Super SU and I have root access again. So on that front, all is well.
The problems that remain, though, are that I still am having issues with Google Play Services quitting and my Wi Fi not connecting. Could these things be related somehow? I've tried clearing the cache and then actually all data from Google Play services, but that has not helped. I have deleted my networks, and then tried reconnecting to them, but that also has not helped. It shows my networks in range as "saved" or "disabled" but won't connect to any of them.
Any ideas for me?
Thanks.
And thanks for the help in getting the 4.4.4 OTA update. At least that worked!
I realize I am basically having a conversation with myself at this point, but just to wrap things up, in case anyone does come along and read any of this...
I have solved all my issues.
The Google Play Services issue must have been related to the Wi-Fi not connecting, and the Wi-Fi not connecting was due to my main network actually having an issue and the fact that I had never authorized the phone on the other networks. I guess this is what happens after being up almost 24 hours. At least I think everything is OK now.
Again, thanks to those that helped!
Andyw2100 said:
I realize I am basically having a conversation with myself at this point, but just to wrap things up, in case anyone does come along and read any of this...
I have solved all my issues.
The Google Play Services issue must have been related to the Wi-Fi not connecting, and the Wi-Fi not connecting was due to my main network actually having an issue and the fact that I had never authorized the phone on the other networks. I guess this is what happens after being up almost 24 hours. At least I think everything is OK now.
Again, thanks to those that helped!
Click to expand...
Click to collapse
Not sure why I stopped receiving notifications from your thread. But at least you got your phone in working order! lol
This is an upgrade pathway that worked well for me in upgrading to 5.0.1 originally from KK as I described in THIS post. All the same thanks go out for the original ideas and guidance to: dottat, Dees Troy, and Darth.
The same method works. Even if you're S-OFF, the trick is following the S-ON instructions...that's it.
Find the latest S-ON RUU and instructions HERE.
The latest TWRP (for the HTC One M8) HERE.
The latest SuperSU per the instructions HERE.
Install the S-on 5.0.1 RUU by whatever method you chose from the link above. I used the fastboot method and it did a great job upgrading the stystem. Most importantly, it did NOT wipe my data. You can also use the htc_fastboot.exe in it's extraction directory for all subsequent fastboot operations [highly recommended]. It will reboot and take at least 5 minutes to update all of your applications. At first, it looks like it hangs on the Verizon splash for a minute or three, then it shows you the upgrade of your applications with a count up. How long it takes depends on how many applications you have and how large they are.
Follow the guides to install TWRP and reinstall SuperSU for root. (step 5) I went to the new TWRP page (step 2) and loaded mine by fastboot, then used the new TWRP to flash SuperSU as described.
If you haven't taken the OTA, that should take care of the upgrade nag screens and keep your data intact. If you have, keep reading.
REMINDER: to reflash any tweaks. My favorite package is HERE at the bottom of the links list. It has just about everything I like.
ADDITIONAL INFO FROM dotatt
You also would be wise to note if the user was already getting nagged for the ota they will still be nagged about it even after upgrading this way. Couple more steps needed
Click to expand...
Click to collapse
AND HIS DESCRIPTION VIA PM
If the user doesn't download the OTA and defer it they might be able to get away with it. Once the file is downloaded (and it goes in /cache) the user will need to wipe cache to delete the actual file as well as go into app manager and clear data on the htcdm app. When they enter the software update screen again it should check and show no updates available instead of asking when to install the deferred update.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
If you need to get rid of the nag screen, the update files, and clear htcdm data, you may be able to use THIS (M8vzw OTA Killer updated for Lollipop) tool.
I have a problem and need help, maybe you can help. I was stock but was s-off and took the stage fright update and phone did all the update and when the phone booted it did not go past the Verizon bootup screen, can anybody help me with this? Thanks you.
Sent from my Nexus 6 using Tapatalk
luvtorev01 said:
I have a problem and need help, maybe you can help. I was stock but was s-off and took the stage fright update and phone did all the update and when the phone booted it did not go past the Verizon bootup screen, can anybody help me with this? Thanks you.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
I answered your other post. Please only post for help in one thread. Thanks.
Sent from my Nexus 6 using Tapatalk
Thanks for keeping your eyes open, dottat. Good reminder that he'll have to reflash TWRP and SuperSU though. And, he'll have to reflash any tweaks.
homers1 said:
Thanks for keeping your eyes open, dottat. Good reminder that he'll have to reflash TWRP and SuperSU though. And, he'll have to reflash any tweaks.
Click to expand...
Click to collapse
You also would be wise to note if the user was already getting nagged for the ota they will still be nagged about it even after upgrading this way. Couple more steps needed ?
Sent from my Nexus 6 using Tapatalk
Hey guys. I think I, pretty familiar with what I need to do, but I haven't done it before. Currently I'm on the FEBRUARY security update (7.1.1) and have root. I am hoping to upgrade to 7.1.2 without losing any of my personal data and apps. I am weary to try flash fire, so could someone more experienced help me out?
I know I need to download the full OTA image and flash it and remove some -W flag, but I don't want to brick my device or lose my data, so I'll let you guys steer me. Thanks in advance, by the way!
P.S. I never fully installed TWRP.
Every time, I download the full factory image and flash via flash fire.
Everything is good, except losing twrp, but i do not mind. root still available
bush911 said:
Every time, I download the full factory image and flash via flash fire.
Everything is good, except losing twrp, but i do not mind. root still available
Click to expand...
Click to collapse
I have tried to stay away from flash fire because I know a couple buddies who soft-bricked by using it.
xxbilxx said:
Hey guys. I think I, pretty familiar with what I need to do, but I haven't done it before. Currently I'm on the FEBRUARY security update (7.1.1) and have root. I am hoping to upgrade to 7.1.2 without losing any of my personal data and apps. I am weary to try flash fire, so could someone more experienced help me out?
I know I need to download the full OTA image and flash it and remove some -W flag, but I don't want to brick my device or lose my data, so I'll let you guys steer me. Thanks in advance, by the way!
P.S. I never fully installed TWRP.
Click to expand...
Click to collapse
Second post in the thread below. Just get the 7.1.2 image.
https://forum.xda-developers.com/pixel/help/stupidly-bootloop-help-t3554242/page2
TonikJDK said:
Second post in the thread below. Just get the 7.1.2 image.
https://forum.xda-developers.com/pixel/help/stupidly-bootloop-help-t3554242/page2
Click to expand...
Click to collapse
I don't have to sideload the March security patch first?
xxbilxx said:
I don't have to sideload the March security patch first?
Click to expand...
Click to collapse
No you don't, because my way is flashing the whole 7.1.2 image, except data (reminder, remove the -w from flash-all.bat).
TonikJDK said:
No you don't, because my way is flashing the whole 7.1.2 image, except data (reminder, remove the -w from flash-all.bat).
Click to expand...
Click to collapse
Alright thanks dude. Which version of 7.1.2 should I get. I know some are made for different carriers but I'm in the U.S. and have a Google Store Pixel (non-XL) and using it on Verizon prepaid. I assume that should grab N2G47E, but I just want to be sure.
The other 7.1.2 is for Dutch Telecom? I just don't want to flash the wrong one on lol.
xxbilxx said:
Alright thanks dude. Which version of 7.1.2 should I get. I know some are made for different carriers but I'm in the U.S. and have a Google Store Pixel (non-XL) and using it on Verizon prepaid. I assume that should grab N2G47E, but I just want to be sure.
The other 7.1.2 is for Dutch Telecom? I just don't want to flash the wrong one on lol.
Click to expand...
Click to collapse
Correct, you want N2G47E.
TonikJDK said:
Correct, you want N2G47E.
Click to expand...
Click to collapse
After, I can just root like normal? I haven't had to do this yet, so that's why I'm asking all these questions. Sorry if I'm being nooby!
xxbilxx said:
After, I can just root like normal? I haven't had to do this yet, so that's why I'm asking all these questions. Sorry if I'm being nooby!
Click to expand...
Click to collapse
No problem at all. Second to the last post in the same thread I linked you to before. It all still works fine on 7.1.2. Did all of this myself yesterday afternoon.
Sideload did not work, used flash-all.bat deleted out the -w. When the device booted up it automatically wiped everything anyways
Download the OTA, Flash it from TWRP, reflash twrp and reboot
mikeprius said:
Sideload did not work, used flash-all.bat deleted out the -w. When the device booted up it automatically wiped everything anyways
Click to expand...
Click to collapse
Did you save the file after you edited it? Take a look at the flashall you used and see if the -w is still in there. Willing to bet it is. I've done this for every update since November. Never had a problem. The only thing I can think of that would cause your data to get wiped is that you didn't save the changes after you edited it.
robocuff said:
Did you save the file after you edited it? Take a look at the flashall you used and see if the -w is still in there. Willing to bet it is. I've done this for every update since November. Never had a problem. The only thing I can think of that would cause your data to get wiped is that you didn't save the changes after you edited it.
Click to expand...
Click to collapse
yeah saved it. There was only one section that had the w- and it was right before the update image. I can try it again at some point later on but that's what I did. I tried to sideload adb the OTA first which does not wipe data but kept getting an error saying device not found and emulator.
robocuff said:
Did you save the file after you edited it? Take a look at the flashall you used and see if the -w is still in there. Willing to bet it is. I've done this for every update since November. Never had a problem. The only thing I can think of that would cause your data to get wiped is that you didn't save the changes after you edited it.
Click to expand...
Click to collapse
Your instructions worked perfectly for me. I'm nor sure what setup the other guy had, but I did make sure I removed the -w like 20 times.
Juli112 said:
Download the OTA, Flash it from TWRP, reflash twrp and reboot
Click to expand...
Click to collapse
are you on the latest twrp rc2 or rc1?
Has anyone received the update ota on a stock google pixel XL for verizon. Mine keeps telling me I am current?
Hey all,
I've restored my girlfriends pixel using the original android 8 image. (It was using PureNexus before). However, she just got the update notification (september update?) but it doesn't do anything when she taps it. The phone should not be rooted, as I used the original clean factory image.
Any suggestions? I've looked at this thread https://forum.xda-developers.com/pixel/help/taking-september-security-update-rooted-t3672586 and so am prepared to download the latest update and remove the "-w" part, but shouldn't it allow her to take the update anyway? Am I going to have to always do this every time they release an update?
Thanks!
It should work, so long as you restored everything to stock - system, bootloader, recovery (dunno if radio matters).
If it's not working most likely there's something custom hanging around somewhere...
I believe it will also fail to update if the bootloader is unlocked. Not sure if you have a VZW device but that's how it works for them. I just update by flashing the full factory image, not an OTA file. Removing the -w will retain user data.
FernBch said:
I believe it will also fail to update if the bootloader is unlocked.
Click to expand...
Click to collapse
Nope, not true. I unlocked my bootloader (not a Verizon phone, bought it from Google), but I've have my phone 100% stock most of the time and I've taken many OTA updates. Including the recent Oreo Sept security update a couple of days ago.
jss2 said:
Nope, not true. I unlocked my bootloader (not a Verizon phone, bought it from Google), but I've have my phone 100% stock most of the time and I've taken many OTA updates. Including the recent Oreo Sept security update a couple of days ago.
Click to expand...
Click to collapse
I think that's the point they're trying to make. Its the Verizon version that is having the update problem if the bootloader is unlocked.
I am having the same issue (have a Verizon Pixel) but am on the ProjectFi network and can't update. I think I'll have to reset and lock the bootloader in order to get the update.
joeyfeffer said:
I think that's the point they're trying to make. Its the Verizon version that is having the update problem if the bootloader is unlocked.
I am having the same issue (have a Verizon Pixel) but am on the ProjectFi network and can't update. I think I'll have to reset and lock the bootloader in order to get the update.
Click to expand...
Click to collapse
Wait wait no. Just download the full image, edit the flashall bat file and remove the-w from it with a text editor. That will flash you back to stock and not wipe your data. Then reroot and so on.
Do not relock it, ever. If something goes wrong and you brick you are toast.
TonikJDK said:
Wait wait no. Just download the full image, edit the flashall bat file and remove the-w from it with a text editor. That will flash you back to stock and not wipe your data. Then reroot and so on.
Do not relock it, ever. If something goes wrong and you brick you are toast.
Click to expand...
Click to collapse
Oh gotcha gotcha.
Weird issue though I couldn't get update to the latest image. I was only able to flash the bootloader and radio. When I tried updating the image it said it couldn't find some of the files. Do I still need to keep the line as "fastboot -w update" when updating the image? won't the "-w" do the wipe?
Nevermind I figured it out. I guess I was inputting the wrong command.
Hey Guys,
So, I've got an A8 2018 (jackpotlte) and currently have it rooted and TWRP installed.
I'd like to update the firmware using Odin to the latest version, but I don't want to lose my app setups etc. The firmware I want to flash is from the same CSC (EVR) that I have currently.
I've got a full TWRP backup incase anything goes wrong, and all data such as photos is backed up separately as well.
My question is, what do I need to do to get this update installed without losing my settings etc?
Will I need to reflash TWRP to the recovery after the update? And if so, I'm assuming I'll have to re-apply the no-verity and opt-encrypt patches?
Thanks for your help!
Last paragraph is correct.
Will I need to reflash TWRP to the recovery after the update? And if so, I'm assuming I'll have to re-apply the no-verity and opt-encrypt patches?
Yes
You can try backing up apps and settings in Samsung Cloud.
Also, this app here may work for you. It keeps all your settings intact. Not sure how it'll work after an update, but I've used it while switching ROMS and if anything, it'll save you loads of time on your downloads after updating.
https://forum.xda-developers.com/an...ation-tool-t3862763/post78060823#post78060823
AntMUK said:
Hey Guys,
So, I've got an A8 2018 (jackpotlte) and currently have it rooted and TWRP installed.
I'd like to update the firmware using Odin to the latest version, but I don't want to lose my app setups etc. The firmware I want to flash is from the same CSC (EVR) that I have currently.
I've got a full TWRP backup incase anything goes wrong, and all data such as photos is backed up separately as well.
My question is, what do I need to do to get this update installed without losing my settings etc?
Will I need to reflash TWRP to the recovery after the update? And if so, I'm assuming I'll have to re-apply the no-verity and opt-encrypt patches?
Thanks for your help!
Click to expand...
Click to collapse
IF YOU FLASH STOCK FIRMWARE, YOU WILL LOSE ROOT. wITH THE NEWER FIRMWARE, YOU WILL HAVE TO USE THAT SPECIFIC VERSION OF THE FIRMWARES ROOT METHOD. yOU WILL HAVE TO FLASH THE csc TO DO WHAT YOURE WANTING TO DO, WHICH WILL FACTORY RESET.
Crap, all in caps. Im not gonna retype it, just know i wasnt yelling lol
there are app backup apps you can get like titanium backup that will restore most of your stuff including personalization.
youdoofus said:
IF YOU FLASH STOCK FIRMWARE, YOU WILL LOSE ROOT. wITH THE NEWER FIRMWARE, YOU WILL HAVE TO USE THAT SPECIFIC VERSION OF THE FIRMWARES ROOT METHOD. yOU WILL HAVE TO FLASH THE csc TO DO WHAT YOURE WANTING TO DO, WHICH WILL FACTORY RESET.
Crap, all in caps. Im not gonna retype it, just know i wasnt yelling lol
there are app backup apps you can get like titanium backup that will restore most of your stuff including personalization.
Click to expand...
Click to collapse
I seriously thought you were angry. I was waiting for the part that... never came.
I re-tried the migrate app (also in zee store).
It's better than i remembered.
BUT IF YOU READ THE PREVIOUS POST, IT IS ALSO CORRECT. THERE. THAT SHOULD GIVE YOU PLENTY OF OPTIONS. (Couldn't help it).
mindlery said:
i seriously thought you were angry. I was waiting for the part that... Never came.
I re-tried the migrate app (also in zee store).
It's better than i remembered.
But if you read the previous post, it is also correct. There. That should give you plenty of options. (couldn't help it).
Click to expand...
Click to collapse
well, just so ya know, i had something funny as a response here and it was in all caps. Well, xda un-capped the whole thing except for the beginning of sentences and so forth where it would have been correct to do so. I was just gonna go back and correct it, but i found this explanation to be even funnier than the original post, so here we are LOLOL!!!