Database Develop

Any way to undo OTA update block?

My g1 is stuck at original 1.0 firmware&i was trying to root it but my pc died. I got as far as going into the terminal and doing the script with devblock&im trying to find a way to undo it via a terminal script so i can atleast get ota updates from tmobile again.
All help is greatly appreciated

you are going to have to un root...but that will require a pc.

actually you can find the OTA for cupcake on the t-mobile forums along with instructions on how to manually update it but you are going to HAVE TO UN ROOT before you do that otherwise you will BRICK.
here is the link for the t-mobile forums and the thread that i was talking about.
http://forums.t-mobile.com/t5/Opera...A-Android-15-Cupcake-Manual-Update/m-p/100646

That's a part of the issue. I would just finish downloading the zip files to get to the latest cm update but any zip file I download it says its corrupted when I try to apply it from the sdcard

OTA will not take, (mac osx, 4.4.4, small update)

Forgive me here. I have a VZW dev edition.
Currently running 4.4.4 stock rom. I had it rooted before and I think I recently lost root. Forgot why but I didn't really need it.
EDIT: I remember now. I did a factory reset. Did I lose root?
anyways the OTA that came a few weeks ago the small one will not install. I have enabled my apps again that I had disabled. I do not remember if I did a tether hack before which was just replacing a file. Bootloader is unlocked still.
So after the OTA downloads and reboots the android shows up the bar starts to move and then red exclamation mark.
Update unsuccessful.
What do I need to do? I also do not want to wipe data.
The OTA alert is annoying me to no end.

It sounds like the pre-flash validation checks are failing for some reason.
A few things don't add up in your post...
You have a Dev Edition, so to root you unlock the bootloader, flash TWRP, boot into it, and when it prompts you too, allow it to root (or if you don't get rooted, install SuperSU while booted to TWRP). IN that state, a Factory reset doesn't remove root. So did you root by some other method? If so, that is why the OTA is failing.
Next.. you say you did a tether hack that was just replacing a file. Did you put the ORIGINAL file back? If no, that will cause the OTA to fail.
The only way to really know exactly why is to NOT install the OTA, instead just download it. Move the OTA zip from /cache to your /SDCard (which takes root) after it finished downloading. Again Do NOT install it the "normal way". Make sure you have a working STOCK Recovery on your phone. Manually boot to stock recovery and apply the update zip via the menu options. When it errors, it will pause and tell you why, what caused the issue. You need to correct it and try again.
One final option... See -> http://forum.xda-developers.com/moto-x/general/faq-how-to-prepare-ota-update-carriers-t3126425 you can take some time and read the first post... then skip to Post #2, and use the Requirements section, and Option 2.

January ota update help needed

OK I got the notification to update today it's MMB29S, I am on K. I am rooted but stock, unlocked using systemless root for root. I've always been rooted and expected it to fail and have to install manually but this time because I'm not rooted like the old way. So i downloaded and went to install to my surprise dead Android with the triangle didn't show but it went to custom recovery screen twrp. I just hit restart because I've never not had a fail and never seen it do this before. Well when it restarted I was not updated and still on K. I also for the life of me can't get it to redo the ota. Tried to clear system service in apps and recheck but nothing.
So my question is since I'm new to systemless root what should I have done when it went to custom recovery? So that way if I can get it to pop up again I can be updated. Thank you in advance for any help and it would be awesome if possible to update this way without having to manually do it.

My best guess, based on what Chainfire replied to me when I asked about OTA, is that because you're somehow rooted the OTA will refuse to install. He said that using the "unroot" function in v2.63 (and I suppose in subsequent versions) he was able to apply the OTA and then just had to re-root.
As to the OTA, I read in the long-distant past that once it's been provided to your device you sort of go to the back of the queue, and even pressing the "check for system update" button has no effect. One day your turn will come again. When it happens, before you press the "install now" button, use the unroot function, reboot, and give it another go.
And I would really appreciate it if you could report back on the success or failure, just so we all know - thanks...
And before I close... your alternative is just to download the full ROM from Google, unzip everything in sight (including the zip within the zip), copy system.img to a convenient folder, and use Fastboot to flash system. After that you'll need to re-root (simple flash) and when you reboot everything will be as it was, apart from the version and security update date. I did it myself to MMB29S a week or so ago.
But my lawyer advises me to advise you to take a full backup first and store it off your device before you do anything to your device - just in case, you know?

I will definitely reply if I get the update again in a few days. If it doesn't I'll probably do it manually. I was just really surprised I hadn't gotten the error, just so used to it. Thank you for the info though.

Correct me if I'm wrong, but to install an OTA don't you need to be completely stock, including recovery?

If I'm not mistaken but since 4.3 (I'm probably wrong) if your rooted (before systemless root) when you try to the ota you will always get the dead Android because rooting changes the system files causing the update when it does is checks to think your system is corrupt.
Also it was really bad when people tried going from 5.x.x to 6.x even doing it manually some of us got bootlooped or when starting the phone up after updating manually saying system is corrupt but still starting up fine. Leaving like me having to completely clear out everything and installing the factory image just to not be corrupt and able to use Android pay.
Systemless root though I've not had a single problem and still able to use AP. And is also the first time in years I've gotten as far as I did with the OTA.

Rbh50815 said:
OK I got the notification to update today it's MMB29S, I am on K. I am rooted but stock, unlocked using systemless root for root. I've always been rooted and expected it to fail and have to install manually but this time because I'm not rooted like the old way. So i downloaded and went to install to my surprise dead Android with the triangle didn't show but it went to custom recovery screen twrp. I just hit restart because I've never not had a fail and never seen it do this before. Well when it restarted I was not updated and still on K. I also for the life of me can't get it to redo the ota. Tried to clear system service in apps and recheck but nothing.
So my question is since I'm new to systemless root what should I have done when it went to custom recovery? So that way if I can get it to pop up again I can be updated. Thank you in advance for any help and it would be awesome if possible to update this way without having to manually do it.
Click to expand...
Click to collapse
These small ota's can be done with boot modifications because they don't include any boot.img changes and if they do then they just blanket overwrite what's already there. The only part that is checked is /system. However TWRP won't ever install an ota update for compatibility reasons. Even if you reflash the stock recovery then you'll fail the ota because when you installed TWRP it protected itself (by modifying /system) from being overwritten by the stock recovery which is what unmodded stock android will always do on boot by default. And there are 2 things the ota verification looks for when updating: 1. It looks for whether /system has been ever mounted as Read/Write. 2. It hash checks the /system, if it finds any mismatch it fails. As for the update not showing up again, the ota checker hides the update after a failure to stop from flooding the download server. If you want to extract the update zip you can look in /cache for the zip. But since you don't have an unmodded /system you might as well just download the newest factory image and manually flash the system.img

You can use Wug NRT, unroot with MMB29S provided in the NRT , then root.

Need Update Advice (KitKat to Lollipop)

I currently have an LG-D415 running KitKat 4.4.2 that's rooted. I've never had a need to upgrade to Lollipop 5.0 until now. I just bought a new truck that has Android Auto which requires 5.0. My phone has been giving me a message that there's a system update available for quite a while now but I have been reluctant to do it because my phone is rooted and I'm not sure what would happen. Should I just let it do the update or do I need to unroot the phone first. It's been so long I'm not even sure what method I used to root the phone.

If you have rooted phone i recomend you installing latest twrp recovery and flashing lollipop ROM for lg l90d415. the stock ROM van ne found on t
his site

OTA update will fail if device is rooted. If you want to keep root enabled, then follow lgl90 suggestion. If you remove root to update it may work but you will have to root again. A backup is always a good move.

I'm kind of a novice at this so I'm looking for the most painless method of getting Lollipop. I'm not sure I'm comfortable installing twrp and flashing the rom. Also, I've read the bootloader needs to be unlocked which it isn't. Can I use SuperSu to unroot, let the OTA update do its thing and then reroot?

the bootloader is unlocke by deafult on lg l90d415 all you habe to do is download flashify app from play store download the latest twrp for d415 and wipe system,dalvikcache and cache the flash te lollipop stock tom by going to install and chouse the rom file where you have downloaded it inernal or external sd card and the swipe to flash the firsr boot will take maximaly 5-10 minuts .. lollipop is waaay diferent than the kitkat thats why will take to boot longer

So I unrooted the phone downloaded the OTA update and tried installing it. It made it halfway through then the phone restarted without completing the update. The phone is still at 4.4.2 and I no longer get any message to update. When I check for updates it thinks its up to date. When I tried manually updating using the LG Mobile Support Tool it initially said an update was available then changed to the phone is up to date. Why does it think the phone is up to date when obviously it's not?

zippster1 said:
So I unrooted the phone downloaded the OTA update and tried installing it. It made it halfway through then the phone restarted without completing the update. The phone is still at 4.4.2 and I no longer get any message to update. When I check for updates it thinks its up to date. When I tried manually updating using the LG Mobile Support Tool it initially said an update was available then changed to the phone is up to date. Why does it think the phone is up to date when obviously it's not?
Click to expand...
Click to collapse
HI i told you what is the best solution to update your phone.. you could successfuly hard brick your phone(why did it not update well you didnt had enough of battery life) do what i told you so the best solution is to download the official lollipop rom for lg l90 d415 its same stock rom from lg but it comes pre rooted and all of that good stuff

lgl90 said:
HI i told you what is the best solution to update your phone.. you could successfuly hard brick your phone(why did it not update well you didnt had enough of battery life) do what i told you so the best solution is to download the official lollipop rom for lg l90 d415 its same stock rom from lg but it comes pre rooted and all of that good stuff
Click to expand...
Click to collapse
zagreb - as I stated I'm a novice so I chose the path that I thought would be the easiest. My phone was fully charged so I do not believe that was the reason for the update not completing. Is there a thread or link you know of that provides a step by step (from beginning to end) tutorial of what you're proposing. Thanks for your help.

UK Nougat update help needed

Hi. I'm currently on C432B166 and have previously contact Huawei and was told that the update rollout will run until the end of June for the UK.
I would like to update manually but not sure what i need to do and what i need to download. I do not want to root my phone or anything like that. I do not have access to a computer for anything. So my only way is to do everything via my phone. I would be very great full in any help or guidance offered. Thanks in advance.

boroleigh said:
Hi. I'm currently on C432B166 and have previously contact Huawei and was told that the update rollout will run until the end of June for the UK.
I would like to update manually but not sure what i need to do and what i need to download. I do not want to root my phone or anything like that. I do not have access to a computer for anything. So my only way is to do everything via my phone. I would be very great full in any help or guidance offered. Thanks in advance.
Click to expand...
Click to collapse
Harder without a pc... But not impossible, especially if you don't want to root.
You'll need to download the c432b182 update, & install using the dload method. Then the c432b361 update the same way. The phone should auto update itself at that point to b378
I'm not going to post links to the updates as they can change, but not too difficult to find in the stock firmware thread and elsewhere.
The dload method is easy as well... Extract the update zip you downloaded. Copy the extracted dload folder and all contents to your microSD card, turn off the phone and turn it back on holding both volume buttons.
You should be able to use the firmware finder app as well, don't use it myself, but don't think it needs root.