Related
So it look like the JB OTA update is here for the USA. Mine is rooted, and has already download the update, but I haven't applied it yet, as I'm rooted and I don't know if I have to do something special first.....
Any one have any info on this?
Same Boat !!
Me too in same boat with P3113.See the post below yours :crying: Hope experts replies soon.
I went ahead and installed it on my daughters tab. CWM protected itself, and root. I'm still poking around, but thus far no issues beyond it says "update failed" but clearly didn't.
I'm wondering if I should remove CWM and unroot it first...
Run a nandroid real quick, back it up to your computer, and let 'er rip. Like I said, it's working perfectly for me. Then again my daughter is 7, so losing all her data isn't really a problem.
Updated with Root ?
sheepdog elite said:
Run a nandroid real quick, back it up to your computer, and let 'er rip. Like I said, it's working perfectly for me. Then again my daughter is 7, so losing all her data isn't really a problem.
Click to expand...
Click to collapse
So if i understand correctly , you allowed the OTA with root and it wiped data ? I am suprised it installed with Custom recovery !!!
I have over 200 user apps. Will i retain those Apps (dont mind data being wiped)
No, it didn't wipe data. I wasn't worried about it "if" it did, because it's my daughters, and I have TIBU for all her games from like last week.
Just to be perfectly clear. NOTHING went wrong. It installed the new O.S., booted fine, said the update failed, but the update didn't fail. Probably because CWM preserved root, and bootloader, so verification failed.
I ran it..... It updated thru CWM... Once done said update failed, but I had a new agreement to agree too. Sys info says its running 4.1.1.
If I have and issue, ill update here.
Failed for P3113
Based on your experience thought I would try too... Unfortunately failed miserably... I have Cwm 6.0.2.3 and attached is the crash log... Maybe some experts can give their views..
I guess I'll post my successful config just for the sake of comparison.
I'm currently running CWM 6.0.1.1. The tab was rooted with a file called gtab2_jellybean_rooter (think I got it from XDA, but i'm not positive) and had no other modifications/roms/etc.
If you're running any sort of ROM you're definitely boned, gotta wait for a ROM update. Beyond that, I'm not really sure what to say
To do the proper update, you should un-root and then re-root once done. That way you get the full support with your update if needed.
I am rooted, running CWM 6.0.2.3. I accepted the update and hit the install thinking that it would fail just as it does on a rooted SIII. The notification said the install had failed, but as others here have indicated, it appears as though the install was successful. I retained root and all seems to be normal; with one exception: It appears that the Tab no longer "sleeps" but shuts down completely. Regardless of whether I turn it off with the power button (short press) or if the screen simply goes to sleep, I have to long press the power button and it goes through a full boot.
Is anyone else experiencing this? Is there a setting I am missing? I am not a noob at rooting, etc. as I have been doing it since my OG Droid on Verizon, but it surprised me when the update seemed to install (even Google Now is working), and I am stumped about this "shut down" that seems to happen.
I experienced the same thing. I was rooted and had installed CM10, went back to original backup, using latest CWM. I hit system update and it downloaded the update, asked me to continue. CWM asked me if I wanted to install unsigned zip, I accepted, and it went through. At first boot it said update failed, but like everyone else, it went through. I have had no issues at all. My tab goes to sleep correctly.
Have peace in mind.
I finished updating (unfortunately, the battery was 9%, so I had to wait for an hour to charge before doing anything) and I got "failed" error like everybody got, but the system shows 4.1.1 and the performance is improved, and I applied root again.
Just for background info, at the time it happened, my Z was running NPL25.86-30 from the following thread;
https://forum.xda-developers.com/moto-z/development/android-nougat-moto-z-versions-t3506342
It was running perfectly fine, then an OTA thing appeared. Well, I made the single big mistake of accepting it, and thus, it encountered an error and while the phone booted fine and even displayed the new build "NPLS-25.86-30-5", it started to randomly reboot when the phone either goes to sleep or when CPU loads are very low.
Well, I was distraught. The phone which was working perfectly fine just a few minutes ago was rendered almost useless as I had to keep turning it off after I used it to avoid it going into a reboot loop. So making calls was difficult enough as the phone would never receive a call as it would be endlessly rebooting anyway.
So, when I returned home, I fired up ADB, connected the Z in Fastboot mode and reflashed the NPL25.86-30 firmware from that link. For a while, it seemed to be fine, but then it started doing it again. I tried again and it still does so.
I was at a loss as I wasn't sure what else to do. Since the OTA update was there, I was afraid that the bootloader may have upgraded and causing me to lose my downgrade. However, when I used the command "fastboot boot xxx", I noticed the Marshmallow boot screen, indicating that the old bootloader was indeed intact and it hasn't changed.
It also happens that I kept the original firmware file which my phone came out of the box with. So I fired up RSDLite, put the entire .zip file in it (including GPT and bootloader) and flashed it right away. After it was done and I did a hasty setup, I left the phone alone to see if it would do so. Over an hour passed, and the phone never rebooted by itself, and would only do so if I was the one doing it.
So, there was light at the end of this very dark tunnel. Fired up ADB yet again and flashed the NPL25.86-30 firmware using the method that does not upgrade the bootloader. I also flashed TWRP and erfanoabdi's TurboZ kernel to disable forced-encryption and dm-verity, along with phh's Superuser for root access as SuperSU somehow does not install right even though the recovery says otherwise.
Booted up and it hasn't rebooted by itself until now. The only time it has rebooted is when I did it. It did necessitate a full data reset, but so far, it has been running well, with the OTA service fully disabled and the processor clocked to its Droid Edition levels.
Only issue I had with it is that the battery drain is a wee-bit high. Though this may be due to the process of installing and optimizing apps over time. If it all goes well, the battery drain should calm itself soon. As of right now, I've downclocked the processor and changed the governor to be as efficient as possible to reduce that battery drain until the phone is fully-set up. The other issue is that after a while, CPU-Z and AIDA64 fails to find the big cores, saying that they're either inactive or "sleeping", but Kernel Adiutor said otherwise. Other than that, I am enjoying it.
Also goes to show that if you have the MM bootloader, you should definitely keep it as it provides a very safe method of returning to a previous build with all your system files intact if anything breaks. It has proved to be extremely useful in this case.
As to the why it all happened,
Did you run the OTA with twrp installed, and/or any other system partition alterations?
Just curious, so others know why this happened to you and Van avoid it themselves. And with either of those things above, the OTA will fail, or worse like in your case.
OTA's are for stock systems, with stock recovery only.
Glad you got it sorted out though! :good:
Darth said:
As to the why it all happened,
Did you run the OTA with twrp installed, and/or any other system partition alterations?
Just curious, so others know why this happened to you and Van avoid it themselves. And with either of those things above, the OTA will fail, or worse like in your case.
OTA's are for stock systems, with stock recovery only.
Glad you got it sorted out though! :good:
Click to expand...
Click to collapse
Stock recovery.
I presume it's either because the build I ran was designed for a different region (same model code, though) or that the Marshmallow bootloader was incompatible with the OTA.
Regardless, it's been working fine for a bit, although one Busybox installer gave me a small scare when it said it was cleaning system/bin, although a later check found that it didn't actually do anything.
Just wanted to share my predicament.
I'm telling you guys something I've never seen before.
I bought a Realme 5 Pro (EU version it seems), and noticed that the installed ROM is quite old (November patched). So I tried looking for updates in the settings app, but there was none. Then I went to realme website:
https://www.realme.com/eu/support/software-update
And downloaded this ROM from that website:
https://download.c.realme.com/osupdate/RMX1971EX_11_OTA_0160_all_gOztiTWijElq.ozip
I went to the default file manager and clicked on it, and the update started right away, finishing after 2-3 minutes.
After the phone booted with the new ROM, everything was okay. The FM radio app went missing, but it was said in the changelog, so that didn't matter to me.
Then the most bizarre thing happened.
I went to the file manager and clicked on the ROM file once again, being damn sure that the update will not take place, because I've already installed this update. But the system accepted the update, rebooted to recovery, and started the whole charade one more time, including showing the percentage. It took exactly the same time as before.
I was half expecting something to go wrong, but to my relief everything was alright. After booting, the ROM version was the same as before (after updating the first time). Nothing changed.
I have never seen anything like this before. I have used phones from many manufacturers, but Everytime I try to update the system with the same ROM version as the one already installed, it would refuse the update, UNLIKE REALME.
Perfectly fine same on other oppo device
Try hard reset
After that,go to settings>update, and update it
Was sideloading my Pixel 4a to the december update, was getting the common failed to read command (closest I got was 94%) and decided to reboot. I expected to get stuck booting or reboot into bootloader, but surprisingly I booted into the new update. Never saw this before so just wanted to ask if this is something I should be warry of (e.g potential crashes and bootloops because I haven't re-rooted yet).
Thanks!
Hey all, I'm not new to this, but I'm looking for some guidance and explanation of the root cause so I don't break my phone worse than it is.
I bought a Pixel 6a last fall, and I have been using it non-rooted since. I have accepted each OTA update since Android 13 was released and as of today I am running on TQ2A.230505.002.
I took the OTA update for May 2023 as soon as it was released before rooting. After it successfully installed, I downloaded the matching factory image zip and extracted the boot.img from the ROM, patched it with Magisk, and then flashed by doing fastboot flash boot magiskboot.img.
It was working fine for a few days, until today when my phone reboot and I was greeted with the "Your device is corrupt" message. If I continue, the phone boots successfully and it works like normal. Magisk says it is loaded and modules are active.
I have reboot my phone several times since I rooted it, and I never received this error. However, the last time I reboot before I received this error was Sunday night. I have not installed any apps since then.
Looking around on this forum and others, I have seen posts from other users who got this error, but their situations are different. In those cases, they received the message only after accepting an OTA on a rooted device or got stuck in a boot loop, but neither of those scenarios apply to me. The solutions in other threads also seem to be a mixed bag of results, so I'm hesitant to do anything until I understand the root cause and ask for guidance.
Since I am unlocked and booting, my hope is that it should be easily recoverable. However, what could cause it to suddenly become "corrupt", and how would I diagnose or remediate the issue with minimal disruption or risk to data? My main concerns at this point are not knowing how it got into this state, and how to quickly recover from it if it happens again.
---- Edit below with more info ----
I found another user with a very similar issue from a month ago. While the issue seems to have been inflicted differently, their symptoms are very similar. The suggested solution is linked here: https://forum.xda-developers.com/t/your-device-is-corrupted-message-on-bootup.4578141/#post-88446647
The other post states the issue is caused by "the bootloader is looking for a new/updated OS without corruption errors so it will go back to restart mode rather than being stuck in the RED eio mode which displays that message."
Since my phone was working, what corruption could I have experienced over the past two days of regular usage? I did not install any updates or make any changes that failed.
Also, what would be the recommended solution in my case? Should I try flashing an older boot.img and then reflash the newest? Or should I do "fastboot --disable verity flash vbmeta vbmeta.img"? Are there any risks with either approach?
Your bootloader is unlocked, hence the message.
dexlemaffo said:
Your bootloader is unlocked, hence the message.
Click to expand...
Click to collapse
This is not the "your bootloader is unlocked" warning. This is the eio message saying the system is corrupt and requires manual intervention to boot.
After doing a bit more research and learning more about the "eio" mode that it was stuck in, I decided to take a stab at it.
Since I have the May update installed, I downloaded the April factory image. I also downloaded platform-tools r33.0.3 because I read there was mixed results with the latest version.
I extracted the boot.img from the bluejay-tq2a.230405.003.e1 April image and flashed it to my phone with fastboot. I then reboot the device. It failed to boot, as expected. However, I immediately noticed the error was gone and I only had the regular unlocked bootloader warning.
I boot into fastboot again and flashed the boot.img from the bluejay-tq2a.230505.002 May image matching my system version. After it flashed successfully, I reboot and the error did not return.
Edit:
I proceeded with rooting again. This time, I did "fastboot boot boot-magisk.img" and flashed from Magisk instead of from fastboot, though I doubt there is any difference.
It reboot successfully. I am back to being rooted without any error message and without any factory reset.
I still don't know what would have caused the bootloader to think there was corruption after it was working for several days. Can anyone reading this can provide some insight?
This whole issue has me very uneasy. I'm worried something else could be wrong - whether it's a bug with Android, or a hardware fault, or a bug in Magisk.
I'm wondering if I should be concerned.
Today, when my phone reboot, it was sudden. I did not initiate the reboot. I thought it was a benign crash as I have experienced many times before. However that was when I saw the "your device is corrupt" message.
I'm reading up on dm-verity and the dm-verity driver here: https://source.android.com/docs/security/features/verifiedboot/dm-verity
I suspect the dm-verity driver is used to hash and verify the system partitions on the fly? If so, could it be that when I was using my phone, it was trying to access some data and the hash failed, the signature mismatched, and it triggered the bootloader to mark the system as corrupt?
If that is what happened, is that cause for concern? Would that be the result of actual system file corruption or bad NAND? Or is it some bizarre Android glitch when running rooted?
Youll likely need to do a factory reset to get rid of that message.
That is incorrect. Based on the other reports of users with the same issue, this is a bootloader message and a factory reset has nothing to do with it. Additionally installing a factory image and wiping the phone would not get rid of the image either. Only an upgrade can supposedly remove the message, unless it is caused by something else.
He said it's the device is corrupt message, not the normal unlocked bootloader one.
afaik thats a bug in Android Verified Boot.
what you did is exactly the "normal" method to solve it, e.g. flash boot.img of the prior version, try to reboot and then flash the correct version again.