[solved, see 5th post]
my tablet was rooted, then i uninstalled some system apps, but i figured out some features won't work, so i unrooted, and did a factory reset, now all system apps are gone,
i thought a factory reset will restore it back to the original stock with all system apps no matter that i uninstalled them. now i can't even go to settings->accounts and syncs, it force closes, i guess i uninstalled an app that manage accounts,
is there a way to go back to stock with all system apps without unlocking bootloader, i don't want to do that.
i also do not have any knowledge about unlocking,flashing,roms,...
or can i just reinstall all system apps and do a factory reset, then it will be fine? (but i don't have backups of those system apps)
i'm on firmware .30 ICS
now i just want a clean system, i don't want it to be messed up like this
After researching i found that factory reset does not restore system apps, so no surprise here.
now i have 2 ways to have a "fresh/clean" system:
1. root and copy all missing system apks to /system/app. But can i root now (using the 1 click transformer root tool) because i uninstalled many system apps and i don't know what they are, can this affect the root?
if this way is ok, can someone on firmware .30 ICS please upload all the files in /system/app. Thanks a lot.
2. flash the stock rom. but i don't want to unlock bootloader, (i don't want to void warranty), how can i flash the stock rom? (and where can i download the stock rom .30 ICS? is it the .zip file on asus support website?) i heard some people say "you can flash a STOCK rom with a locked bootloader" but in another device, not tf300.
i think this way is best because it restores everything, which is what i want, i'm hoping i can do this without unlocking my bootloader.
I guess if i can solve this problem, from now i will never delete any system apps. if i knew factory reset does not restore system apps i did not uninstall them . but it just does not make sense, it's called "factory reset", so shouldn't restore to "factory" state?
Please help. Thank you.
nooktablet said:
After researching i found that factory reset does not restore system apps, so no surprise here.
now i have 2 ways to have a "fresh/clean" system:
1. root and copy all missing system apks to /system/app. But can i root now (using the 1 click transformer root tool) because i uninstalled many system apps and i don't know what they are, can this affect the root?
if this way is ok, can someone on firmware .30 ICS please upload all the files in /system/app. Thanks a lot.
2. flash the stock rom. but i don't want to unlock bootloader, (i don't want to void warranty), how can i flash the stock rom? (and where can i download the stock rom .30 ICS? is it the .zip file on asus support website?) i heard some people say "you can flash a STOCK rom with a locked bootloader" but in another device, not tf300.
i think this way is best because it restores everything, which is what i want, i'm hoping i can do this without unlocking my bootloader.
I guess if i can solve this problem, from now i will never delete any system apps. if i knew factory reset does not restore system apps i did not uninstall them . but it just does not make sense, it's called "factory reset", so shouldn't restore to "factory" state?
Please help. Thank you.
Click to expand...
Click to collapse
If you are on ICS you can still root using the debugfs method aka the one click.
Yes you can still download the firmware from Asus. You can try to put the zip within the zip into /sdcard and see if it installs it full but not sure if that would replace the system apps. I don't think there would be harm trying it.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
funnel71 said:
If you are on ICS you can still root using the debugfs method aka the one click.
Yes you can still download the firmware from Asus. You can try to put the zip within the zip into /sdcard and see if it installs it full but not sure if that would replace the system apps. I don't think there would be harm trying it.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
Click to expand...
Click to collapse
ok, i think i'll go the rooting way.
so can someone on .30 ICS please upload ALL the files in system/app? i need all of them because i don't know what files i deleted and what i did not delete.
Thank you a lot.
UPDATE: Problem solved.
i downloaded .30 firmware from asus website, did a manual update, after updating it restored the system apps. so it solved the problem. thanks funnel71.
to get a "clean" system i did a factory reset, now back to the beginning lol.
so when you accidentally (or purposely) delete system apps, just do a manual update and it will restore, make sure to download the right firmware.
Related
after upgrade to 4.2.2 and reboot, N7 3G went TWRP automatically ....
after reboot from TWRP, it still 4.2.1 ......
what happened ?? how to fix it ??
Thanks
williamlaw said:
after upgrade to 4.2.2 and reboot, N7 3G went TWRP automatically ....
after reboot from TWRP, it still 4.2.1 ......
what happened ?? how to fix it ??
Thanks
Click to expand...
Click to collapse
you probably need stock recovery to complete the update... I would just wait for someone to root the update and then flash it that way
williamlaw said:
after upgrade to 4.2.2 and reboot, N7 3G went TWRP automatically ....
after reboot from TWRP, it still 4.2.1 ......
what happened ?? how to fix it ??
Thanks
Click to expand...
Click to collapse
While your post doesn't make much sense, I assume you ran into the same issue I did on my N73G.
If so, you have a 90% upgraded tablet. All of the system and kernel patches applied, but it got stuck on the radio firmware update. For some reason, this also breaks the bootloader update (for me at least) right before the radio, even though it said it worked. The reason why your tablet still shows 4.2.1 is because the build.prop change, which shows what version you are on, is after radio and didn't get applied.
Without going into too many details, you are a bit stuck. You can't reapply the OTA because it will fail the system asserts now that they were already patched. I would suggest downloading the FULL 4.2.2 IMAGE from Google here:
https://developers.google.com/android/nexus/images#nakasig
And do the following:
adb reboot-bootloader
fastboot flash bootloader (new bootloader file)
fastboot reboot-bootloader
fastboot flash recovery (new recovery file)
fastboot flash radio (new radio file)
Then reboot into recovery mode and let the stock recovery apply the radio firmware update.
You need the stock recovery to apply the radio firmware. Custom recoveries (at least some/most/all) don't support the bach_update.modem function. You can go back to TWRP after you upgrade.
The instructions above will fix everything BUT the build.prop file, which will still be the 4.2.1 version. You can either fastboot flash system with the 4.2.2 system image, or get a copy of a 4.2.2 build.prop file and replace yours with that. Or if you are creative, you can modify the OTA update, remove everything BUT the build.prop patch and apply that manually (but I wouldn't suggest this unless you know what you are doing).
Also, in the future, [Q}s should go in the Q/A section.
phonic said:
While your post doesn't make much sense, I assume you ran into the same issue I did on my N73G.
If so, you have a 90% upgraded tablet. All of the system and kernel patches applied, but it got stuck on the radio firmware update. For some reason, this also breaks the bootloader update (for me at least) right before the radio, even though it said it worked. The reason why your tablet still shows 4.2.1 is because the build.prop change, which shows what version you are on, is after radio and didn't get applied.
Without going into too many details, you are a bit stuck. You can't reapply the OTA because it will fail the system asserts now that they were already patched. I would suggest downloading the FULL 4.2.2 IMAGE from Google here:
https://developers.google.com/android/nexus/images#nakasig
And do the following:
adb reboot-bootloader
fastboot flash bootloader (new bootloader file)
fastboot reboot-bootloader
fastboot flash recovery (new recovery file)
fastboot flash radio (new radio file)
Then reboot into recovery mode and let the stock recovery apply the radio firmware update.
You need the stock recovery to apply the radio firmware. Custom recoveries (at least some/most/all) don't support the bach_update.modem function. You can go back to TWRP after you upgrade.
The instructions above will fix everything BUT the build.prop file, which will still be the 4.2.1 version. You can either fastboot flash system with the 4.2.2 system image, or get a copy of a 4.2.2 build.prop file and replace yours with that. Or if you are creative, you can modify the OTA update, remove everything BUT the build.prop patch and apply that manually (but I wouldn't suggest this unless you know what you are doing).
Also, in the future, [Q}s should go in the Q/A section.
Click to expand...
Click to collapse
is this problem caused by flashed kernel ??
williamlaw said:
is this problem caused by flashed kernel ??
Click to expand...
Click to collapse
Did you not bother to read anything I wrote?
I had the same problem. If you have a TWRP backup from a previous android version that allowed the ota to work just flash that and you'll still receive the ota for 4.2.2
Sent from my Nexus 7 using Tapatalk HD
This happened to me too, though I have the wifi-only version. So it's not just the radio.
I got the same problem with my Wifi version. Is there any fix yet? I only rooted the device but the rest is still stock. How come the update failed?
the same here - stock and rooted only WIFI version.
During install gave ERROR and after manual reboot - now is shows 4.2.1 version and there are not new system updates.
any solution ?
rexxxxx said:
the same here - stock and rooted only WIFI version.
During install gave ERROR and after manual reboot - now is shows 4.2.1 version and there are not new system updates.
any solution ?
Click to expand...
Click to collapse
Got the same problem and I think it was caused by stick mount.
The app seems to modify the "debuggerd" file in system/bin.
Problem solved by replacing the file by the original one.
spiou said:
Got the same problem and I think it was caused by stick mount.
The app seems to modify the "debuggerd" file in system/bin.
Problem solved by replacing the file by the original one.
Click to expand...
Click to collapse
finally flashed back to stock 4.2.1 then OTA update 4.2.2
spiou said:
Got the same problem and I think it was caused by stick mount.
The app seems to modify the "debuggerd" file in system/bin.
Problem solved by replacing the file by the original one.
Click to expand...
Click to collapse
how ? I indeed have the mount stick installed for the OTG cable !
rexxxxx said:
how ? I indeed have the mount stick installed for the OTG cable !
Click to expand...
Click to collapse
Someone posted the original file here : http://forum.xda-developers.com/showthread.php?t=2145265
You can replace the file simply with es file explorer
I'm also in the same boat as the OP.
OTA came down, installed fine, rebooted which went into twrp, tablet still says 4.2.1.
So, is there any way of doing this without doing a wipe ? Or losing any of your data ?
What about putting the update, downloaded from google, on a USB stick and booting into twrp then flashing from there ?
I don't mind losing root, although I have rootkeeper installed, and I don't mind losing custom recovery, all of this can be fixed.
I also have the trinity kernel installed, so will I lose this as well ? Again, don't mind since I am about to test the m-kernel, anyway.
What I don't want to do is lose my data. I have plenty of full twrp backups done, but then these are 4.2.1 backups. Backing up my apps isn't really feasible at the moment because of their sheer size. Horn, NOVA 3, the GTA games, bards tale, all gigs and gigs of data. Infact, I only have 1 gig left on a 32Gb N7, and I just don't have anywhere left to put a full backup of apps on to. I also don't want to download them all again, NOVA 3, for example, took me 6 hours to download on wi-fi.
I have read a lot of advice and help on here, plenty of googling which simply sends you back here anyway, and most advice centers around losing your data in some way. So, any help without losing data would be most appreciated,
spiou said:
Someone posted the original file here : http://forum.xda-developers.com/showthread.php?t=2145265
You can replace the file simply with es file explorer
Click to expand...
Click to collapse
Done this but the problem remain.
About menu shows 4.2.1 and there is no system update for me.
I think update go trough and it changed some files and now these files tells the system update that I am with newest version.
Any solution for this. How to make the system update think that I need an update?
Sent from my Nexus 7 using xda app-developers app
After reading many threads and articles, I finally upgraded to 4.2.2 with stock recovery. Your mileage may vary.
Based on the discussions on http://forum.xda-developers.com/showthread.php?t=2148456, the failure may be caused by an app you installed
that corrupted some system files. Therefore, you have to flash 4.2.1 stock system and boot images back. The nice thing is your data and settings remain intact.
Although you lost root, it can be easily re-rooted using nexus root toolkit.
Now you're back to 4.2.1 which is allowed to upgrade, use OTA RootKeeper to keep su and then upgrade thru OTA. If you can not longer get OTA, you can clean data/stop/start Google Framework service, Google play service, and Google play store, and then re-check update. The last tip I read it somewhere but I forgot where I read it. Sorry.
Good luck. :laugh:
williamlaw said:
after upgrade to 4.2.2 and reboot, N7 3G went TWRP automatically ....
after reboot from TWRP, it still 4.2.1 ......
what happened ?? how to fix it ??
Thanks
Click to expand...
Click to collapse
JohnRM said:
I'm also in the same boat as the OP.
OTA came down, installed fine, rebooted which went into twrp, tablet still says 4.2.1.
I also have the trinity kernel installed, so will I lose this as well ? Again, don't mind since I am about to test the m-kernel, anyway.
Click to expand...
Click to collapse
Which part of STOCK is unclear? You cannot use OTAs unless you are STOCK. That means stock ROM contents. Stock kernel. Not twiddled with, not renamed, not deleted, not modified, not OverAmplifiedWithSuperBaseBoostLOLZKewlBeatsified, etc.....
rexxxxx said:
Done this but the problem remain.
About menu shows 4.2.1 and there is no system update for me.
I think update go trough and it changed some files and now these files tells the system update that I am with newest version.
Any solution for this. How to make the system update think that I need an update?
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
You must clear the data of the Google framework (in the list of apps) and reboot immediately the tablet. Then the update will be proposed again.
One more thing : when you replace the file, check that the permissions are identical.
khaytsus said:
Which part of STOCK is unclear? You cannot use OTAs unless you are STOCK. That means stock ROM contents. Stock kernel. Not twiddled with, not renamed, not deleted, not modified, not OverAmplifiedWithSuperBaseBoostLOLZKewlBeatsified, etc.....
Click to expand...
Click to collapse
Exactly. I don't understand why we need to see posts like that over and over and over again. Hell, the OTA update will even tell the user what failed, and yet people still complain and ask what's wrong.
Also, while in most cases a custom recovery is OK (though the update will overwrite it), with the N73G unit, you need to use the stock recovery, otherwise it will fail without warning ahead of time.
spiou said:
Got the same problem and I think it was caused by stick mount.
The app seems to modify the "debuggerd" file in system/bin.
Problem solved by replacing the file by the original one.
Click to expand...
Click to collapse
Can you elaborate? E.g., where do you get the original debuggerd from, how do you replace it (adb push?), etc.
I just rooted my nexus 6p and installed TWRP custom recovery, and instead of letting be read-only root, I let it modify system settings. I then looked at the superSU thread and it said to keep root as read-only. Is there any way I can make it read-only? Also, if I were to update my phone by flashing factory images since I cannot take OTA's, does the fact that I allowed TWRP modify system settings prohibit me from flashing factory images?
fruitytoilet said:
I just rooted my nexus 6p and installed TWRP custom recovery, and instead of letting be read-only root, I let it modify system settings. I then looked at the superSU thread and it said to keep root as read-only. Is there any way I can make it read-only? Also, if I were to update my phone by flashing factory images since I cannot take OTA's, does the fact that I allowed TWRP modify system settings prohibit me from flashing factory images?
Click to expand...
Click to collapse
I chose to modify system within root and am having no issues ... Its more of a preference I believe ... You can always go back to stock and redo it to read only just in the process you'll wipe the phone out to brand new state which just means you will have to set it up again ... But yes you can always flash factory images to go back to stock no worries
Stranger_84 said:
I chose to modify system within root and am having no issues ... Its more of a preference I believe ... You can always go back to stock and redo it to read only just in the process you'll wipe the phone out to brand new state which just means you will have to set it up again ... But yes you can always flash factory images to go back to stock no worries
Click to expand...
Click to collapse
Would I be able to flash factory images of new updates?
I would think you should if you flashed everything which still wipes the phone clean ... I believe if it's read only you can flash new updates without wiping it clean ... But I'm just saying what I think or have read so don't take that as a concrete answer until you find out otherwise ... I do know you can flash all images and go back to complete stock tho
fruitytoilet said:
Would I be able to flash factory images of new updates?
Click to expand...
Click to collapse
Of course... Do it and see, also don't freak about this systemless root crap. It's mostly fluff. Go old fashioned and profit...
Sent from my Nexus 6P using Tapatalk
I have a problem with Nougat, and that is - i can`t deinstall system apps. I tried it with system app remover, but it fails on every app. Next i tried with a file manager, but that doesn`t work either. The folders + apk`s just won`t go away, even after a restart. Then i tried to deinstall some stuff via TWRP file explorer, but got a blank screen without any apps after loading into system again.
It wasn`t anything critical for the system to work (i know what i`m doing) so i don`t get where the problem is. I then tried to install Marshmallow, but got into a bootloop and had to reinstall Nougat.
So, if someone knows how to get rid of system apps on Nougat, or if you know how to downgrade, please tell me both. Thanks.
are you root? if so, i've had luck modifying system with Root Explorer. (not sure which explorer you were using)
tysoncrypto said:
I have a problem with Nougat, and that is - i can`t deinstall system apps. I tried it with system app remover, but it fails on every app. Next i tried with a file manager, but that doesn`t work either. The folders + apk`s just won`t go away, even after a restart. Then i tried to deinstall some stuff via TWRP file explorer, but got a blank screen without any apps after loading into system again.
It wasn`t anything critical for the system to work (i know what i`m doing) so i don`t get where the problem is. I then tried to install Marshmallow, but got into a bootloop and had to reinstall Nougat.
So, if someone knows how to get rid of system apps on Nougat, or if you know how to downgrade, please tell me both. Thanks.
Click to expand...
Click to collapse
I've had luck removing system apps with FX explorer, but I had to remount system R/W before it would let me. Also I'm rooted.
I'd advise against tying to downgrade from Nougat at this point, it has caused bricks for many people.
tysoncrypto said:
I have a problem with Nougat, and that is - i can`t deinstall system apps. I tried it with system app remover, but it fails on every app. Next i tried with a file manager, but that doesn`t work either. The folders + apk`s just won`t go away, even after a restart. Then i tried to deinstall some stuff via TWRP file explorer, but got a blank screen without any apps after loading into system again.
It wasn`t anything critical for the system to work (i know what i`m doing) so i don`t get where the problem is. I then tried to install Marshmallow, but got into a bootloop and had to reinstall Nougat.
So, if someone knows how to get rid of system apps on Nougat, or if you know how to downgrade, please tell me both. Thanks.
Click to expand...
Click to collapse
If you wish to get rid of system apps, simply flash via recovery, the lastest supersu vip; system[less], whichever your preference. If you haven't already flashed twrp after flashing Nougat, do so first.
Install Titanium Backup, and you're all set; I've done it myself and works as it should.
If you were trying to downgrade to Marshmallow, you'd need to do a backup + full wipe, and install the M bootloader, boot, system, etc, then you could restore a custom ROM backup, if you had one.
Heisenberg said:
I'd advise against tying to downgrade from Nougat at this point, it has caused bricks for many people.
Click to expand...
Click to collapse
At this point i would wait unless he signs up for the beta. Dozen of us have restored our phones
We flashed that it's over custom rom/ wrong steps to upgrade.
rbouza1 said:
At this point i would wait unless he signs up for the beta. Dozen of us have restored our phones
We flashed that it's over custom rom/ wrong steps to upgrade.
Click to expand...
Click to collapse
So can i downgrade to MM again? I'm on beta N7.0 ... No root.. No unlocked bootloader.. everything stock.. What do you think i should do to get back?? Can i root and flash MM over it..idk
Thanks in advance!!!
RidinNerdy said:
So can i downgrade to MM again? I'm on beta N7.0 ... No root.. No unlocked bootloader.. everything stock.. What do you think i should do to get back?? Can i root and flash MM over it..idk
Thanks in advance!!!
Click to expand...
Click to collapse
With out unlocked bootloader I don't really know. I guess you might be able to run a factory image . The latest from googles developers site .
spunks3 said:
are you root? if so, i've had luck modifying system with Root Explorer. (not sure which explorer you were using)
Click to expand...
Click to collapse
Thank you all for your answers. I didn`t bother trying another root explorer as i thought they`re all the same, but i will try the ones suggested here. And yes, the phone is of course unlocked and rooted with the latest twrp and supersu installed.
teh roxxorz said:
If you wish to get rid of system apps, simply flash via recovery, the lastest supersu vip; system[less], whichever your preference. If you haven't already flashed twrp after flashing Nougat, do so first.
Install Titanium Backup, and you're all set; I've done it myself and works as it should.
If you were trying to downgrade to Marshmallow, you'd need to do a backup + full wipe, and install the M bootloader, boot, system, etc, then you could restore a custom ROM backup, if you had one.
Click to expand...
Click to collapse
Thanks. I flashed the latest twrp and supersu before upgrading to Nougat, and they both made it through, so it`s all set up.
I think i`ll try to downgrade since i don`t see the big Deal with N as of now + i have a much worse mobile data signal after updating to it. It`s almost constantly on H instead of 4g /LTE.
If someone is interested in downgrading, here`s an exact instruction that i found here on XDA:
"Download the MM stock firmware and extract all of it to a folder. Then open a cmd/terminal in the download folder (shift and right click in windows I believe, just right click and there will be a option in linux).
Then do these steps in order BACK UP YOUR APPS!!"
fastboot flash bootloader bootloader.img
fastboot flash radio radio.img
fastboot reboot-bootloader
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
The names will be a little different, and if you want twrp put it in place of the stock recovery!
PS: Don't flash userdata
If that fails, i`ll install titanium backup to at least get rid of all the google stuff, like music, photos etc.
Heisenberg said:
I'd advise against tying to downgrade from Nougat at this point, it has caused bricks for many people.
Click to expand...
Click to collapse
@Heisenberg Do you know of a safe way to downgrade our 6p from Nougat 7.1.1 on Pure Nexus to Marshmallow?
jt1998 said:
@Heisenberg Do you know of a safe way to downgrade our 6p from Nougat 7.1.1 on Pure Nexus to Marshmallow?
Click to expand...
Click to collapse
When I got my phone back after RMA from the BLOD it was on 7.0 and the first thing I did was flash a 6.0.1 factory image. I picked the same build number as the last Pure Nexus build in MM. I don't think flashing factory images through fastboot is a big risk as long as you are paying attention and following a good plan. Any other opinions are welcome.
Sent from my Nexus 6P using XDA-Developers Legacy app
tysoncrypto said:
Thanks. I flashed the latest twrp and supersu before upgrading to Nougat, and they both made it through, so it`s all set up.
I think i`ll try to downgrade since i don`t see the big Deal with N as of now + i have a much worse mobile data signal after updating to it. It`s almost constantly on H instead of 4g /LTE.
If someone is interested in downgrading, here`s an exact instruction that i found here on XDA:
"Download the MM stock firmware and extract all of it to a folder. Then open a cmd/terminal in the download folder (shift and right click in windows I believe, just right click and there will be a option in linux).
Then do these steps in order BACK UP YOUR APPS!!"
fastboot flash bootloader bootloader.img
fastboot flash radio radio.img
fastboot reboot-bootloader
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
The names will be a little different, and if you want twrp put it in place of the stock recovery!
PS: Don't flash userdata
If that fails, i`ll install titanium backup to at least get rid of all the google stuff, like music, photos etc.
Click to expand...
Click to collapse
Dude, does it fixes your lte issues? Because i am facing the same problem with my nexus 6p + android 7.1.1.
I personally have never had lte issues on any build, 6.x.x or 7.x.x on any custom rom or stock.
Sent from my Nexus 6P using XDA-Developers Legacy app
https://developers.google.com/android/images You need a complete factory image flash, including /data.
I had LTE problems from 7.1.2b to 7.1.1 (while I didn't have them on 7.1.1 before switching to 7.1.2b) and they were solved by factory reset.
My objective is to find a way to regularly apply updates without having to rebuild each time. I know there is TiBu, but it is still a lot of work to rebuild my setup. Titanium does not restore some settings, frozen apps, widgets, or blocked broadcast receivers/services. They take a long time to reestablish.
Ideally, I can simply restore from a FlashFire /data backup after an update. Unfortunately, it has not worked out. While on PF1, I made a full backup. After updating to PF2, re-root, and restoring /data with FlashFire, the phone boots, but IMS and other core processes FC while the CPU stays at near 100% constantly. I don't know why.
I am looking for a way to either 1) update without wiping the /data partition, or 2) restore from FlashFire and have the phone boot/work properly afterwards.
Any ideas??
On a related note--I know I can 'go back to stock' and take the OTA. Question is--how 'stock' do I have to be? Do I have to flash the stock package or is removing root from SuperSU enough? I was thinking that if I can somehow take the OTA while keeping my /data partition intact, I can then just re-root.
I would appreciate any input.
Thanks.
You can always try it yourself... I have returned to pf2 via the guide in the Verizon forum then ota'd from there, then rerooted. No issues until playstore auto updated supersu on me.
twizt3d said:
You can always try it yourself... I have returned to pf2 via the guide in the Verizon forum then ota'd from there, then rerooted. No issues until playstore auto updated supersu on me.
Click to expand...
Click to collapse
I have tried every combination, but nothing panned out. The last thing I tried was to use FlashFire to flash the PF2 update package. The phone boots, but constant IMS Service Stopped error, no radio, etc.
Updating via OTA or Odin and rerooting is not the problem. The problem is you need to rebuild the phone. TiBu is not a sufficient solution for me. Unless I can dirty flash (or restore from FlashFire after an update), it is unsustainable.
I believe I have done what you're asking before. You'll have to flash the kernel and system partitions back to stock any way you'd like, take the OTA, and then reroot. You may need to uninstall superSU before doing that also, I don't think just turning it off works.
DeadlySin9 said:
I believe I have done what you're asking before. You'll have to flash the kernel and system partitions back to stock any way you'd like, take the OTA, and then reroot. You may need to uninstall superSU before doing that also, I don't think just turning it off works.
Click to expand...
Click to collapse
Are you saying that I would:
1) Leave the current apps, data, and config in place
2) Flash /system back to stock and uninstall SuperSU
3) OTA will work
4) Re-root
Thanks.
snovvman said:
Are you saying that I would:
1) Leave the current apps, data, and config in place
2) Flash /system back to stock and uninstall SuperSU
3) OTA will work
4) Re-root
Thanks.
Click to expand...
Click to collapse
Yup. I have not tested that on this phone, but I have done this on the S4. Make sure you also restore the original kernel too since I doubt OTAs will work with the engboot kernel. If you've disabled any system apps you may have to unfreeze those as well
DeadlySin9 said:
If you've disabled any system apps you may have to unfreeze those as well
Click to expand...
Click to collapse
Thank you. I've read something like this--that there are implications related to frozen system apps. Why does that matter?
For me, instead of taking the OTA, I was able to FlashFire the updated /system with /data intact, but upon reboot, I kept getting IMS process stopped error and no radio service. I wonder if this had something to do with frozen system apps. Mind you, I did not freeze IMS, I only froze all the bloat.
Hi Everyone,
I might have a problem now after tried to root my Axon 7 A2017 B27 (using the instruction http://forum.xda-developers.com/axon-7/development/wip-axon-7-root-bootloader-unlokced-t3441204). Unfortunately, the phone seems rooted partially after that.
Root Checker told me it's unrooted. But when i tried to upgrade to B29 package today, after downloaded and rebooted, it went to TWRP and couldn't be installed itself. The system indicated my phone has been rooted.
Now i'd like to unroot it back. Anyone could help and provide the detail step i should do? Thank you very much!
liuyiji said:
Hi Everyone,
I might have a problem now after tried to root my Axon 7 A2017 B27 (using the instruction http://forum.xda-developers.com/axon-7/development/wip-axon-7-root-bootloader-unlokced-t3441204). Unfortunately, the phone seems rooted partially after that.
Root Checker told me it's unrooted. But when i tried to upgrade to B29 package today, after downloaded and rebooted, it went to TWRP and couldn't be installed itself. The system indicated my phone has been rooted.
Now i'd like to unroot it back. Anyone could help and provide the detail step i should do? Thank you very much!
Click to expand...
Click to collapse
2 choices.
1. http://forum.xda-developers.com/axon-7/development/rom-guide-updates-to-stock-files-via-t3469484 best option. Use TWRP to install the B29 bootstack and B29 system. It worked for me.
2. Use the backups you made from the axon7backup.exe - move the files to the same folder you have the axon7root.exe, delete the boot and recovery files there, rename your backup files accordingly, and the axon7root.exe program will flash those files when you run the axon7root.exe program.
I really recommend using option 1. Much easier and quite frankly DrakenFX made it idiotproof.
tabletalker7 said:
2 choices.
1. http://forum.xda-developers.com/axon-7/development/rom-guide-updates-to-stock-files-via-t3469484 best option. Use TWRP to install the B29 bootstack and B29 system. It worked for me.
2. Use the backups you made from the axon7backup.exe - move the files to the same folder you have the axon7root.exe, delete the boot and recovery files there, rename your backup files accordingly, and the axon7root.exe program will flash those files when you run the axon7root.exe program.
I really recommend using option 1. Much easier and quite frankly DrakenFX made it idiotproof.
Click to expand...
Click to collapse
Thanks so much @tabletalker7. I just noticed this new post. Will try the option 1 for sure. When you did that, did all the data wipe out? If so, would you mind tell me which tool you use to backup the apps? Thanks again.
You do have to wipe data so I assume you lose everything - I have nothing important on the phone storage so I can wipe my phone all I want all I need is my sd card. Don't know of any way to not lose apps, but google did restore everything when I set up the phone on B29.
tabletalker7 said:
You do have to wipe data so I assume you lose everything - I have nothing important on the phone storage so I can wipe my phone all I want all I need is my sd card. Don't know of any way to not lose apps, but google did restore everything when I set up the phone on B29.
Click to expand...
Click to collapse
Thanks, will try some way to backup first then
liuyiji said:
Hi Everyone,
I might have a problem now after tried to root my Axon 7 A2017 B27 (using the instruction http://forum.xda-developers.com/axon-7/development/wip-axon-7-root-bootloader-unlokced-t3441204). Unfortunately, the phone seems rooted partially after that.
Root Checker told me it's unrooted. But when i tried to upgrade to B29 package today, after downloaded and rebooted, it went to TWRP and couldn't be installed itself. The system indicated my phone has been rooted.
Now i'd like to unroot it back. Anyone could help and provide the detail step i should do? Thank you very much!
Click to expand...
Click to collapse
Something to keep in mind for next time: you cannot apply official OTA updates if you have a modified boot.img (systemless root), modified recovery.img (TWRP), or have modified the /system partition (some root apps do this). You need to be completely stock (sans unlocked bootloader) in order to apply official OTA updates.
xtermmin said:
Something to keep in mind for next time: you cannot apply official OTA updates if you have a modified boot.img (systemless root), modified recovery.img (TWRP), or have modified the /system partition (some root apps do this). You need to be completely stock (sans unlocked bootloader) in order to apply official OTA updates.
Click to expand...
Click to collapse
Thx, @xtermmin. I'm just switching from iphone to android, need more time to study. Seems it would not easy for me to get the phone unrooted as well, lol