Perfect way to get updates on rooted Lenovo A7000 phone

[archz2]

What is the perfect way to get a Lenovo a7000 firmware updates on a rooted phone? I recently unrooted my Lenovo a7000 which had a maxritz cwm recovery installed. I installed stock recovery on it. Then while installing update my phone rebooted and I got the following error.

I messed up my phone big time when I fetched the update using OTA snatcher and tried to force install it using TWRP and bricked my device. However things are normal now after I wiped off my phone and installed stock ROM. I am getting update alerts now and want a fool proof way to install OTA updates. Please advise. I have xposed installed too with gravity box and youtube adaway modules.

 

[Hadron]

OTA plus rooted phone is a bad idea full stop. The more you modify the ROM (e.g. xposed) the more likely an OTA will cause problems. Either use custom ROMs to update, revert to stock to accept updates, or you can take your chances, but the a safe, reliable way of applying OTAs to modified ROMs that you seek doesn't exist.

 

[mikedt]

Problem with a Lenovo, it will let you OTA update a rooted modified device, resulting in the inevitable "install failed" message. Many devices won't do that, like Samsung, they'll tell you it's modified and just won't even attempt to update. And usually you can't apply manufacturer OTA updates with TWRP either.

 

[archz2]

OTA plus rooted phone is a bad idea full stop. The more you modify the ROM (e.g. xposed) the more likely an OTA will cause problems. Either use custom ROMs to update, revert to stock to accept updates, or you can take your chances, but the a safe, reliable way of applying OTAs to modified ROMs that you seek doesn't exist.

If I uninstall xposed, do an unroot, install a lenovo a7000 stock recovery,then? What do you say?

Earlier when I failed I remember, I did not uninstall xposed from my device which might have caused trouble.

 

[mikedt]

It may work, as long as the firmware is in an exact unmodified state. Incremental OTA updates do expect the firmware to be as the manufacturer intended it, to guarantee success, i.e. in a known state, no files changed, modified, missing etc, otherwise there can be problems, like boot-looped or completely bricked. If it's not, you might have to flash a complete ROM clean,

 

[Hadron]

"unrooting" is harder than it sounds. These days rooting tools often do more than just install a superuser binary and a superuser app, so it's not so simple to revert the ROM to its pre-rooted state. That's why I suggested a full return to stock as safer.

 

[DeadDude]

Ota update = completely stock ROM

Xposed was active and you got the device to turn on again?? Go buy a lottery ticket! LoL

 

[archz2]

Hehe.. Lottery ticket. Okay, clear my doubt. I always used to think, if the device gets bricked, one can always unbrick it using the sp flash tool installation of a stock rom.

 

[DeadDude]

All I can speak of from experience:
Xposed even being installed (Not active) can cause hard bricks during any updates.

Hard brick means it's a paperweight if you aren't an employee of the company that made the device.

I don't own a Lenovo android, so I can't be of much help here.



Just read what I wrote. No disrespect intended.

 

[archz2]

All I can speak of from experience:
Xposed even being installed (Not active) can cause hard bricks during any updates.

.

And what is your opinion about unrooted devices that had xposed uninstalled from them prior to getting updates?

 

[DeadDude]

And what is your opinion about unrooted devices that had xposed uninstalled from them prior to getting updates?

Shouldn't be a problem.

I disable ask modules, uninstall the runtime, then freeze the app Xposed itself. Remove supersu and update. Make sure you can flash supersu back, and you're all set.

 

[archz2]

But you must be installing stock recovery also prior to updates. Yes?

 

[DeadDude]

Yes

 

[Hadron]

I don't know how you rooted or what Android version you have, but this thread explains some of the problems with applying an OTA to a rooted device running a recent version of Android.

 

[scary alien]

I don't know how you rooted or what Android version you have, but this thread explains some of the problems with applying an OTA to a rooted device running a recent version of Android.

Shucks..., I didn't think anyone had noticed .

Cheers, @Hadron!

 

[archz2]

Thanks for this thread