Hi to all, in the last two months i'm trying to update my mi pad 4 plus from Havoc 2.7 to a new verion.
Updating to havoc 2.8 from ota apparently works but then gmail, calendar, note cannot sync and give errors.
I have tried a clean flash, wiped data/system/vendor/cache, formatted internal data, no differences, on the first boot after setting the wifi connection the tablet stay constantly on "Checking for udpates" and no way to go on.
i tested different roms (PixelExperience, Havoc 2.8, Omnirom) but from the august updates nothing works, the only rom is working is the 2.7 Havoc of july (restore backup or clean flash).
I tested every possibile combination, with or without gapps (tried different version and always checked the md5), with or without root but no difference.
When i have writed in differente thread this problem they always answer me to "go back and change wifi", check and re-download rom but also after check this no differences, always hangs on the first "Check updates".
If i skip the wifi connection the tablet try to start but immediatly say "no connection".....
Someone have the same problem and know eventually how to fix?
Thanks
Related
Now this is the weirdest thing I've ever encountered! I have a Samsung Galaxy Note 8.0 tablet (n5110) which runs TWRP recovery and Resurrection-Remix-5.7.4 (CM13 based). Everything used to work beautifully until the end of July when an app called “EPB DVR Manager” (in the Play store) received an update. My tablet had to do a whole bunch of updates, so I gave it the “go” and Play Store started doing its thing, updating one app after the other.
At some point the tablet froze. Dead. Even the clock in the status bar stopped. I had to reset the device by pressing and holding power until it rebooted. The next thing was ... boot loop. It seemed to finish the boot animation and at the point when the main screen is supposed to show up it rebooted!
Tried to wipe dalvik & cache. No go, still boot loop. Had to format data to get the device back to life. From there it took me quite some hours of repeated tries of restoring 100+ apps and crashing the device all over until I figured out that it was this specific app - the “EPB DVR Manager”. After figuring out that this app causes the problem, I did two more attempts to confirm what is going on:
First, I did a wipe of dalvik, cache & data, reboot, android setup wizard (setup Google account). Then, as the first action at all, I tried to install the “EPB DVR Manager”. Boom - device messed up again.
Second, I reverted back to stock firmware (kitkat) and installed the “EPB DVR Manager” - no problem at all. So it has something to do with the Resurrection-Remix ROM, but here's the thing:
I have 3 different devices (a Moto G 3rd Gen, a LG GPAD 7.0 and that Samsung Note 8.0) and all three of them run Resurrection-Remix 5.7.4 and the Samsung is the only device which all in a sudden has these catastrophic problems with the latest version of this app (earlier versions installed/updated fine).
Now I understand that my devices run different kernels with different hardware drivers despite all of them running RR-5.7.4.
I would really like to get a clue about what the heck is going on here. Now before y'all are telling me that RR-5.7.4 is dead because it is based on CM13 - I know that. Still, RR-5.7.4 is a way better daily driver than the newer Nougat builds. So how should I try to get “live logs” because the problem always ends in a crashed installation and Android needs a full wipe to recover. I would like to find out what is going on to be able to let the app developer know about the problem (if the app's apk is at least partially to blame).
Even if it turns out that it is RR's fault (and therefore the bug will not be fixed because RR-5.7.4 is dead) I would still want to learn how such a simple transaction like installing an app can cause such a dramatic (and 100% reproducible) crash of Android's data partition.
Thanks for any suggestions on how to catch logging information for this kind of mystery.
Markus.
Every rom I try flashing gets stuck on checking for updates when I set up my mobile. It happened multiple times before but I went 1 step back and re-tried and It worked. Now It's just always checking for updates. Tried restarting several times, still the same. I fully wiped my mobile, flashed latest firmware for kate(7.12.14 including emmc_appsboot.mbn), latest rom(NOS & RR) and latest gapps(tried nano,micro,mini,aroma, same outcome). That keeps happening on NOS 8.1 and RR 7.1.2. Same flashing procedure followed for both ROMs. I always flashed ROMs this way and never had a problem. Any clue wth is going on? Using TWRP 3.2.1.0
Skipped the set up on NOS 8.1 and I get a message saying I can't connect to google services whenever I open up Play Store or attempt to add a Google Account. Still doesn't fix my issue skipping the set up.
So, to begin with, yesterday Mi A1 got the Android 9 update. As I always do, I went to uptade it with Magisk (it worked with 8.0 to 8.1 and with every security patch, so I, as a newbie, thought, "why the h3ll not?"). Obviously, it didn't work and I got into a boot loop. So, here are the [lot] of things I have tried to do.
-Downloaded MiFlash and the latest OS version from Xiaomi site (8.1 witch november patch). Tried flashing a lot of times, I always get the boot loop after installing it. Wiped all data with TWRP and still didn't work. Always the same problem. Tried with different versions as well.
-Downloaded latest AOSP ROM for the device, flashed it, wiped cache and data, instaled TWRP (3.2.3-0), but the system never initiates. Doesn't even restart (20 minutes after my last try and it still is in a black screen).
-I've tried the same thing with Lineage 15.1 as well. Checked with MD5 in both roms. Doesn't work at all. Followed every tutorial I could, step by step, don't know what I'm doing wrong.
Can any one please help me? I don't know what to do anymore.
EDIT 1: So, I thought nothing happened, but after installing AOSP, I rebootet the phone holding the power buton, and during boot, I can see the "Powered by Android" from the custom ROM for a few seconds, but then the screed turns black and nothing more happens.
Hi,
I flashed the xiaomi.eu rom with magisk for my mi mix 3. The installation was smooth and no problems occurred. The phone booted up after install and showed the Miui 10 set up wizard. I chose the language and then connected to the wifi and it then goes to the screen that says it is checking for updates, and it is just stuck there with the wheel spinning. I had no options to skip it and the same thing happens when I try to connect through cellular data.
Do I just have to wait or is this some kind of bug? I am currently in China, so maybe the internet restrictions in China is affecting it somehow? I don't think I did anything wrong with the install and have no idea why it is like this. I can still access TWRPs so is there a way for me to skip the setup wizard at the start? If I can skip it will it affect the phone in some way or will it just be default settings?
Any help will be much appreciated.
Did you found the solution?
I am facing strange problem on my Redmi Note 4. Custom Roms are getting stuck after language selection screen on first boot. I had been using Resurrection Remix (Official) – Pie Rom on this phone earlier. Due to some reasons, I had to flash the stock MIUI rom. Thereafter, I flashed the latest TWRP 3.3.1 in fastboot mode and installed the latest build of Resurrection Remix (Official) – Pie (7 July 2019) via TWRP. The Rom installed successfully without facing any encryption problem because I had formatted my data partition prior to flashing Rom.
After flashing Rom, the System boots and Set Up Wizard initiates with the screen giving me option to select language. After I select language and press next…the phone goes to next screen ‘Just a Sec…’ and thereafter remains there forever. The screen blinks after some time and goes blank, then it comes back to ‘Just a Sec…’. It simply doesn’t let me go beyond that.
I tried two more builds of Resurrection Remix – Pie, but again the same story.
I tried to flash Pixel Experience (Official) – Pie, but the same story.
I believe, Set Up Wizard is stuck with some thing and doesn’t let me through. The Resurrection Remix (Official) – Pie (20 January 2019) build came to my rescue as this rom doesn’t initiate Set Up Wizard at first boot and simply goes to desktop. Thereafter, Set Up can be completed any time and doesn’t create any problem.
As 20 January 2019 build works fine, I tried to dirty flash the latest build over it with the hope that Set Up Wizard won’t come up. The dirty flash goes without error and phone boots to system. But this time, phone gets stuck while trying to get to desktop screen and message keeps showing forever on the screen ‘Phone is Starting’. I can see the desktop image in the background. The screen goes blank in between and then message keeps showing again. It simply doesn’t let me pass through. In this scenario, I can access the pulldown and go to settings. I did check, phone wasn’t encrypted because I had not used any pin, fingerprint etc. on the working rom prior to dirty flash of latest build.
Can anyone help me as I simply cannot install any Custom Rom due to this problem. I have been left with only two options, either to stick with 20 January 2019 build of Resurrection Remix, which doesn’t initiate Set Up Wizard at first boot or to bloatware loaded MIUI stock rom.
What I tried :
1. Tried to rename the SetupWizard.apk file to SetupWizard.apk.bak in TWRP to evade first time Set Up Wizard but in this case, screen doesn’t show any thing and goes blank at the time just before going to desktop. It didn’t work.
2. I tried TWRP backup of another Redmi Note 4 having latest build and restored backup of four partitions of that phone (vendor, boot, system and data) on my trouble creating phone. The system booted but it also got stuck at ‘Phone is Starting’ Screen while showing me desktop in the background. I could enter the settings through quick pulldown in this scenario.
Please help me resolve this problem.
I have obtained catlog files through adb while my phone was booting after dirty flashing latest RR build (August 2019). Please note that I can't go beyond Just a Second screen, in case I go for clean flash after data format. Therefore, I flashed RR January build first, which works without any problem. Then settled my phone and thereafter updated it with latest RR (August 2019) build by dirty flashing. Phone accepted my pin on startup screen and then went ahead with showing 'Phone is Starting'. The phone never passed through that screen.
I have obtained two files, one with Error option and other is complete log. Please help me understand the problem, so that I may update my phone with latest RR build, else I may remain stuck with January build only.
https://drive.google.com/open?id=1zVXYxdQ5epImYTOiXSs1tIFB8uTwNV2p (Complete Log File)
https://drive.google.com/open?id=1YYXbdq7csCwskCtgtn2uWYG4rXWng4em (Log File with Error Tag only)
I kept trying Rom after Rom and finally, the AOSiP Official Rom is working great on my phone. Every thing went smooth with this Rom.
Moderator, please close this thread.
Thread closed at Op's Request.
Thanks
SacredDeviL666.