I just received an update on my Z2Play. I'm rooted and was wondering if it was safe to update?
Thanks
First of all, what update is it ? February security patch ?
Yes it is.
Don't do it or u will be stuck in boot loop as I did the same...make a complete backup including EFS before trying
For me it failed for some reason (maybe because of twrp or magisk was installed), and spent half day to unbrick and restore everything. Haven't tried again since then.
failed for me then would only boot to twrp for me...i used a pattern to unlock on my back ups, somehow that doesnt work now. Had to start from scratch
I froze it with Titanium Backup. No more reminder.
cuban11182 said:
I froze it with Titanium Backup. No more reminder.
Click to expand...
Click to collapse
That's what I did, as soon as I rooted, but not wanting to go past the firmware that was available at the time and preventing oreo was my motivation.
The best is to first flash the original oreo rom. Then install the updates, then flash TWRP again and magisk. Then your are new and up to date. I did it it was not so hard to do it takes some but well oke.....its a hobby ....
Related
Guys, I had been rocking it with an Unrevoked S-OFF root + OTA update. Everything was great. Then I got careless and tried to flash some mod .zip files today and got caught in a splash screen loop. All I could do was nandroid restore from Clockwork. It got me out of the loop, but my phone is now back to 2.1 and all my apps are gone etc etc. But I'm almost certain that I did the backup AFTER I applied the OTA, so I don't understand why I reverted.
The good news is that I'm still S-OFF and I should have Titanium backups on my SD card. The bad news is two fold.
A) I'm not sure the proper steps to take to get back to OTA w/o any issue.
B) when I go to Market, I can't install any apps (getting a download error failure everytime)
Please help! Thanks!
EDIT: RESOLVED!
flash the 2.2 update.zip again
dirtydozen said:
flash the 2.2 update.zip again
Click to expand...
Click to collapse
Hey thx for responding. Not sure what you mean - I used the OTA to get to 2.2 last time. Since I'm still S-OFF, do you think it's safe to take the update again?
These are the instructions I followed the first time.
http://forum.xda-developers.com/showthread.php?t=755035
Other note: The only apps I still have installed are the stock apps AND Superuser. Not sure how/why SU survived while the others did not, but it's there.
If your already rooted, which there's no reason you shouldn't be, grab a 2.2 ROM and flash it. Even a stock rooted 2.2 ROM.
Occum's Razor says you didn't back up after the update and restored with a 2.1 backup.
fr4nk1yn said:
Occum's Razor says you didn't back up after the update and restored with a 2.1 backup.
Click to expand...
Click to collapse
... well I know someone that is damn sure making a 2.2 backup when I get this issue resolved!
I think I found the solution (using OTA).
First I had to data wipe my hard drive, because until I did that i could not access any market downloads and basically the OS was behaving like it was crapped up. Data wipe fixed all that and put me back to stock 2.1. Of course then I couldn't apply the OTA because i was rooted. So I moved the OTA zip to SD card and renamed it update.zip, and launched it from Clockwork. Looks like it worked
PS. No offense to the ROM guys on here, but I'm just not really into custom ROM's. Mostly b/c I don't understand them. But in any event, I just like having the "official" ROM, and then tweaking it to the Nth degree.
Hi. I backed up my phone using the backup method found here: http://android.stackexchange.com/questions/28296/full-backup-of-non-rooted-devices
This method uses CMD and creates an android backup file (.ab) I want to unlock my bootloader and add the custom clockwork recovery. Of course unlocking the bootloader wipes everything. So if i were to restore everything with the .ab file, then do the custom recovey with the superuser thing, would that give me root, and would all of my apps and data be restored as they are right now?
Probably a stupid question, but i want to be completely 100% sure i won't mess up my phone. I know its going to void warranty, which would be a problem if i dropped it of course
Thanks
It should work yes, you can also backup apps with an app called carbon. Free in the playstore.
Then unlock the bootloader,flash a custom recovery and make a backup of the stock rom in there right away too (needed when you want to go back to full stock for future updates) its called a nandroid backup.
Then root it and restore, or install a brand new custom already rooted rom
Thanks a lot
If it was a custom rom i chose to install, will it still restore? or would it need to be the original stock for the restore to work properly?
Danw20 said:
Thanks a lot
If it was a custom rom i chose to install, will it still restore? or would it need to be the original stock for the restore to work properly?
Click to expand...
Click to collapse
Afaik know you can restore apps on any rom with carbon. Watch out with restoring system data, it can crash the rom.
Because some custom roms have more changes and if you restore system parts it will break the rom. But apps should not be a problem. The most important thing is that you do a nandroid backup of the stock rom. The rest is easy to setup new in the worst case.
Brilliant. Thanks for the help, much apreciated.
Was half expecting an answer like that, i think i will give root stock a go, then probably when HTC stop updating i will be very tempted to give a custom a go.
Cheers
I have unlocked the bootloader, i think i have flashed the recovery, downloaded nandroid and still says i need root, so i downloaded the superuser thing and when i try to install the binary thing it says there is an error. Anything i can do?
Update: I have learnt Its all good now.
Good mate ! Have fun with your rooted phone
CASE CLOSED !
[SOLVED]
Hello guys, hope that someone could help me.
I had a 4.4.2 rom (note4neo 2.0) and i wanted to try 5.1.1 so first of all i mad a full Nandroid Backup through TWRP and also a titanium bkp. Later on i installed lollipop original rom through ODIN and everything was ok. I then followed a guide from Noble Rom for rooting and installing TWRP. Everything went ok, but i had problems with some rooting app (like titanium) and so i decided to revert back to 4.4.2.
At first I rebooted into recovery, made a full wipe (even system) then restored previously backup. Seemed to be ok, but then when rebooted it stucks on boot logo (i left booting for 28 minutes, so....).
Then i tried to wipe cache, dalvik and data and reboot again: no changes.
I then decided to reflash previously twrp (the one that i used for bkp). Flashes went ok, but i have "recovery is not seandroid enforcing" message on the top (even with the lollipop twrp: maybe is this the key of my problem?!?).
Restoring backup from older twrp didn't work as well...
Of course i can enter both Download and Recovery mode.
Now i flashed back the original 5.1.1 through ODIN in order to go back to original lollipop and see what u guys can tell me to do to restore backup i made..
Thank you very much for your help
I was thinking that maybe i should flash a stock 4.4.2 before restore the backup...
Now i'm downloading it and see what happens...tell me if i may be right
Yes you should first restore a 4.4.2 firmware before flashing TWRP and then you'll be able to restore your backup
lennon123 said:
Yes you should first restore a 4.4.2 firmware before flashing TWRP and then you'll be able to restore your backup
Click to expand...
Click to collapse
Update: Flashed 4.4.2, all ok. Then rooted, twrp and all ok again
After i restored Backup and stuck on boot.
Then i made again all the steps: STOCK, ROOT, TWRP, then Base version of the Rom and all ok.
At this point i was thinking it was done and restoring would have been just fine...unfortunatley it doesn't. Stuck on boot again.
So i reflashed the Base version of the mod rom and: it started with my restored app Btw i'm encountering problems like no home button, no volume icon, no settings shortcut. Now i made a cache and dalvik wipe but problems still remain..
Any idea?
After some attempts to solve those problems i stucked again on boot..
So now my plan is to: Flash STOCK rom, Root, Twrp, Base mod rom (everything always ok so far) and then restore JUST DATA from backup... Not touching system and boot should let the rom works just fine...at least i hope so :'D
Ok, as i was expecting the problem is solved. I did not restored System and Boot and all apps works just fine. Even though i miss some settings i made now i'm happy to be 90% back to origin ^^
Well alright, your solution will probably help other people in your situation. I presume your porblem is solved, if so you can add [SOLVED] in your first post in the title.
lennon123 said:
Well alright, your solution will probably help other people in your situation. I presume your porblem is solved, if so you can add [SOLVED] in your first post in the title.
Click to expand...
Click to collapse
Yes, it's solved I'll mod the title
Since i am kind of a moron here let me lay down the issue:
Flashed TWRP + SuperSU, decided to try Magisk, didn't work due to modded boot.img, so i tried factory resetting the device.
Somehow that killed my stock themes and now themes will not apply.
I tried related methods from the 6x forums but that was to no effect.
So i'm asking if anybody here could provide me with a nandroid backup of the stock firmware :S
Rommco05 said:
Try unroot phone then check if Themes work, if yes make again root. Unlock bootloader is necessary step after restore my backup
Click to expand...
Click to collapse
Unrooting did not seem to work due to the modified boot image. So i guess i'll just have to be patient then. Thank you anyway
I have an unlocked Pixel XL that I flashed back to stock July 2018 security patch in order to take the OTA Aug 2018 security patch that updates to Pie. Upon doing so, the update downloaded and installed, but when it said to restart to finish installing, my phone soft bricked. =[
I tried flashing the factory imagine a few times but it is still not working. I am able to get into recovery and bootloader screens and boot TWRP if necessary so I have hope but don't know what to do.
What happens as far as the bootloop is it goes to loading screen then after a while, around when it would normally load the home screen, the screen turns black for a few seconds then it restarts, and the second time around it says my data is corrupt and gives me the options to either try again or factory reset. I do not want to factory reset because I do not have a backup.
Is it possible that this bootloop has to do with an app not being compatible with pie? Is it possible to boot into safe mode without the phone being on and fully loaded (that's the only way I know how to boot into safe mode)?
Anyone have any ideas or suggestions?
smithilberry said:
I have an unlocked Pixel XL that I flashed back to stock July 2018 security patch in order to take the OTA Aug 2018 security patch that updates to Pie. Upon doing so, the update downloaded and installed, but when it said to restart to finish installing, my phone soft bricked. =[
I tried flashing the factory imagine a few times but it is still not working. I am able to get into recovery and bootloader screens and boot TWRP if necessary so I have hope but don't know what to do.
What happens as far as the bootloop is it goes to loading screen then after a while, around when it would normally load the home screen, the screen turns black for a few seconds then it restarts, and the second time around it says my data is corrupt and gives me the options to either try again or factory reset. I do not want to factory reset because I do not have a backup.
Is it possible that this bootloop has to do with an app not being compatible with pie? Is it possible to boot into safe mode without the phone being on and fully loaded (that's the only way I know how to boot into safe mode)?
Anyone have any ideas or suggestions?
Click to expand...
Click to collapse
Why wouldn't you just flash the Pie factory image? There's no need to flash back to stock Oreo and take an OTA when you can just fastboot flash the Pie factory image.
Phalanx7621 said:
Why wouldn't you just flash the Pie factory image? There's no need to flash back to stock Oreo and take an OTA when you can just fastboot flash the Pie factory image.
Click to expand...
Click to collapse
Oh man, I thought I read a while back that for some reason you couldn't flash to upgrade major releases 7.x to 8, 8.x to 9, etc.
Well I guess I was wrong about that. Thanks for the info! Knowing I can will make life easier in the future.
You can also flash full ota in twrp.
Not sure why this is never mentioned.
Sent from my Pixel XL using Tapatalk
lafester said:
You can also flash full ota in twrp.
Not sure why this is never mentioned.
Click to expand...
Click to collapse
the OP has tried flashing the factory image and it hasn't worked.
@smithilberry, are you using the latest sdk platform tools from google? there was an update to them this month. the latest revision is 28.0.1. if you have those, then i suggest trying to flash the factory image to both slots.
if that doesn't work, the only other thing i can suggest is to factory reset. since you can boot twrp, you can backup your data before resetting. run a nandroid backup or use adb pull commands to copy your files. if you run a nandroid backup, at minimum, backup your internal storage partition so you have a copy of your data. i don't know if it's worth backing up the system partition since it seems like something's wrong with it. or you can backup everything and then restore just internal storage. after you've backed up your data and copied the backup files to a computer, do a factory reset or flash the factory image and let it do a data wipe(keep the -w option in the flash-all script). hopefully a reset gets your phone working again.
good luck1
altwu said:
the OP has tried flashing the factory image and it hasn't worked.
@smithilberry, are you using the latest sdk platform tools from google? there was an update to them this month. the latest revision is 28.0.1. if you have those, then i suggest trying to flash the factory image to both slots.
if that doesn't work, the only other thing i can suggest is to factory reset. since you can boot twrp, you can backup your data before resetting. run a nandroid backup or use adb pull commands to copy your files. if you run a nandroid backup, at minimum, backup your internal storage partition so you have a copy of your data. i don't know if it's worth backing up the system partition since it seems like something's wrong with it. or you can backup everything and then restore just internal storage. after you've backed up your data and copied the backup files to a computer, do a factory reset or flash the factory image and let it do a data wipe(keep the -w option in the flash-all script). hopefully a reset gets your phone working again.
good luck1
Click to expand...
Click to collapse
Yes using newest platform tools. I ended up factory resetting, which worked. I was just hoping to avoid that cuz it seemed it was fixable otherwise. Thanks for advice!