Hi,
There has been an issue that riddles me, and I can't understand why it happens.
I've use Evolution X A13 (from here XDA), then try to switch to crdroid 9.3 (also here from xda)
Since I'm not encrypted, the usual steps I take were
1. clear fingerprints + pattern
2. reboot twrp
3. wipe from twrp
4. flash the rom
5. flash the DFE
6. reboot system
I rarely root. Even if I root, I always do it after first or many reboots after.
Now the weird thing happened.
crdroid 9.3 + nikgapps passed the boot until the setup wizard appeared, but then it's automatically rebooted by itself. Not hard reboot, it's similar like soft reboot (it's showing crdroid logo, back to setup wizard). Then it keeps soft rebooting (showing setup wizard for a moment then goes soft reboot again), so I never able to pass the google setup wizard.
I tried to clean addon.d with survival script removal, it didn't help as well. It kept soft rebooting a moment after setup wizard showed up.
I thought it was nikgapps problem. However it's not.
I do the usual wipe, now with system + vendor + metadata wipe
Flash crdroid alone without gapps, same problem. Made it to lineage wizard, then it's never ending soft reboot again.
I tried with several another rom not listed in here XDA (derpfest, ancientos), same problem. Made it to google setup wizard, a very short moment after, it enters never ending soft reboot.
The weird thing is, if I flash EvoX (latest now is 7.8) again, the issue doesn't occur, so it's the only rom which allows me to finish setup and I can use right now.
Things I haven't tried:
1. Format data and flash without DFE (I'm sure it's not DFE problem, usually problem already arose before the rom logo showed up)
2. Use adb to skip the setup wizard (I don't think it will help since crdroid without gapps also ends up soft reboot)
3. Vanilla official lineage (tried vanilla crdroid, same issue)
4. Revert back to original miui 12.5
My device is redmi note 8T.
Is there anyone facing the same issue before?
x3r0.13urn said:
Hi,
There has been an issue that riddles me, and I can't understand why it happens.
I've use Evolution X A13 (from here XDA), then try to switch to crdroid 9.3 (also here from xda)
Since I'm not encrypted, the usual steps I take were
1. clear fingerprints + pattern
2. reboot twrp
3. wipe from twrp
4. flash the rom
5. flash the DFE
6. reboot system
I rarely root. Even if I root, I always do it after first or many reboots after.
Now the weird thing happened.
crdroid 9.3 + nikgapps passed the boot until the setup wizard appeared, but then it's automatically rebooted by itself. Not hard reboot, it's similar like soft reboot (it's showing crdroid logo, back to setup wizard). Then it keeps soft rebooting (showing setup wizard for a moment then goes soft reboot again), so I never able to pass the google setup wizard.
I tried to clean addon.d with survival script removal, it didn't help as well. It kept soft rebooting a moment after setup wizard showed up.
I thought it was nikgapps problem. However it's not.
I do the usual wipe, now with system + vendor + metadata wipe
Flash crdroid alone without gapps, same problem. Made it to lineage wizard, then it's never ending soft reboot again.
I tried with several another rom not listed in here XDA (derpfest, ancientos), same problem. Made it to google setup wizard, a very short moment after, it enters never ending soft reboot.
The weird thing is, if I flash EvoX (latest now is 7.8) again, the issue doesn't occur, so it's the only rom which allows me to finish setup and I can use right now.
Things I haven't tried:
1. Format data and flash without DFE (I'm sure it's not DFE problem, usually problem already arose before the rom logo showed up)
2. Use adb to skip the setup wizard (I don't think it will help since crdroid without gapps also ends up soft reboot)
3. Vanilla official lineage (tried vanilla crdroid, same issue)
4. Revert back to original miui 12.5
My device is redmi note 8T.
Is there anyone facing the same issue before?
Click to expand...
Click to collapse
Battery issue maybe? Is it fine when the device connected to the charger? If yes, then 100% the battery, to be exact its the fuse on the bms.
Edit: already answer your question about battery before lol, you already replaced your battery right so isnt the battery then.
Maybe you can try take a logs with adb and see what's going on
SkyFlex said:
Battery issue maybe? Is it fine when the device connected to the charger? If yes, then 100% the battery, to be exact its the fuse on the bms.
Edit: already answer your question about battery before lol, you already replaced your battery right so isnt the battery then.
Maybe you can try take a logs with adb and see what's going on
Click to expand...
Click to collapse
lol, man, I've replaced the battery, it's like new again now. The back covered got replaced as well since I was sloppy removing the old glue.
Anyway, isn't adb logcat useless since every restart it's resetting? And dmesg was supposed to help debug kernel related issue? I'm not sure whether this is a kernel issue since flashing other kernel didn't help and one rom made it successfully (evox).
I tried to access adb while it's soft rebooting, but it won't recognise my phone (my guess because I haven't enabled the usb debugging, but how do I enable it while having a soft reboot?)
x3r0.13urn said:
lol, man, I've replaced the battery, it's like new again now. The back covered got replaced as well since I was sloppy removing the old glue.
Anyway, isn't adb logcat useless since every restart it's resetting? And dmesg was supposed to help debug kernel related issue? I'm not sure whether this is a kernel issue since flashing other kernel didn't help and one rom made it successfully (evox).
I tried to access adb while it's soft rebooting, but it won't recognise my phone (my guess because I haven't enabled the usb debugging, but how do I enable it while having a soft reboot?)
Click to expand...
Click to collapse
Yea probably usb debugging isnt enabled since you just reflash the rom. If usb debugging is enabled, you can get log when the phone boot up ( start capturing at boot animation )
There is kmesg, but nowdays I think its console-ramoops in /sys/fs/pstore, you need to get it when the phone restarted and not easy to read compare to dmesg/logcat
In evox there is no problem at all? No random reboot or some apps get force closed?
Are you using latest firmware? But again, you successfully flash the rom and boot up to the setup screen.
SkyFlex said:
Yea probably usb debugging isnt enabled since you just reflash the rom. If usb debugging is enabled, you can get log when the phone boot up ( start capturing at boot animation )
There is kmesg, but nowdays I think its console-ramoops in /sys/fs/pstore, you need to get it when the phone restarted and not easy to read compare to dmesg/logcat
In evox there is no problem at all? No random reboot or some apps get force closed?
Are you using latest firmware? But again, you successfully flash the rom and boot up to the setup screen.
Click to expand...
Click to collapse
Yes, of course at the latest firmware, the device has stopped receiving update long ago.
No, evox has no problem at all. My guess some rom uses the same device tree, which causes the soft reboot, while evox use their own device tree which has no issue.
I tried to disable setup wizard but it's not avail since I can't access adb while the device soft rebooting. If I do that in twrp adb, these commands yielded error, stating "settings" is unknown
adb shell settings put global setup_wizard_has_run 1
adb shell settings put secure user_setup_complete 1
adb shell settings put global device_provisioned 1
- Formatting data, always, either before of flashing the ROM or previously to reboot.
- Check if the vendor is based on Miui or AOSP, given the case, it would be needed to wipe it previously to flash the ROM.
- Updating the firmware to the latest version.
- Flashing the stock ROM as based prior to flash the ROM.
Found 2 other roms which works without soft rebooting. Unfortunately, they're not on XDA neither. It's risingos and alphadroid. Unfortunately, NFC is broken in risingos and it has serious gcam issue. Alphadroid seems work like EvoX.
Related
Hello,
I flashed a CustomROM and gapps, tried to reboot into system, but my phone does not react anymore since that attempt. The screen is black.
ROM: http://forum.xda-developers.com/mi-max/development/rom-cm13-unoficial-2016-06-14-universal-t3473016
Gapps: core package from 07-16-16 (arm)
Is there a way to recover it?
Tsd560ti said:
Hello,
I flashed a CustomROM and gapps, tried to reboot into system, but my phone does not react anymore since that attempt. The screen is black.
ROM: http://forum.xda-developers.com/mi-max/development/rom-cm13-unoficial-2016-06-14-universal-t3473016
Gapps: core package from 07-16-16 (arm)
Is there a way to recover it?
Click to expand...
Click to collapse
You have hydrogen or helium?
Which TWRP image did you install exactly?
My device is a Helium 64-3GB bought in China (June/16)
Recovery was flashed using Flasher Toolkit from "en.miui.com" -> /thread-301971-1-1.html
(Link not allowed)
file name: "twrp-3.0.2-2-hydrogen"
I remember that I might have seen Hydrogen in the text box during installation, if you aim on the detection during the installation.
Tsd560ti said:
My device is a Helium 64-3GB bought in China (June/16)
Recovery was flashed using Flasher Toolkit from "en.miui.com" -> /thread-301971-1-1.html
(Link not allowed)
file name: "twrp-3.0.2-2-hydrogen"
I remember that I might have seen Hydrogen in the text box during installation, if you aim on the detection during the installation.
Click to expand...
Click to collapse
Yeah... Wrong recovery and the install detected your helium as hydrogen leaving you a brick.
My bad... I just added the warning about that in the thread after seeing your question... Should of thought about this scenario but since we have helium twrp for a long time now I I assumed nobody is isuing hidrogen... I knew what you did just wanted to make sure.
Never been in a brick myself but read this thread and you should be back booting in no time
http://forum.xda-developers.com/mi-max/how-to/guide-install-global-miui8-root-t3435594
And install proper twrp, please... or you won't be able to install any helium rom.
The device gets recognized in MiFlash, but after flashing the twrp and the stock rom, the device still does not boot.
Any proposes on my mistake?
EDIT: I just started the procedure again, unplugged the battery, connected the "jumper" and the phone booted properly.
After some failed reboots, it randomly booted into TWRP (now the right one, at least i hope so. gonna check this later) and I installed the latest RR (love the design).
So now, its just the ugly 3G-bug left and a little OC would be nice
Tsd560ti said:
The device gets recognized in MiFlash, but after flashing the twrp and the stock rom, the device still does not boot.
Any proposes on my mistake?
EDIT: I just started the procedure again, unplugged the battery, connected the "jumper" and the phone booted properly.
After some failed reboots, it randomly booted into TWRP (now the right one, at least i hope so. gonna check this later) and I installed the latest RR (love the design).
So now, its just the ugly 3G-bug left and a little OC would be nice
Click to expand...
Click to collapse
Great job:good:
LG G4 815
S/N=511
tl;dr: Bootloop, did a lot of fiddling, finally ended up with installing a "somewhat" working setup in this order (Everything installed via TWRP, TWRP was via fastboot):
1. TWRP (SteadfasterX's) /O version
2. V29a Firmware, keep TWRP
3. Disable big cores kernel (From above V29a firmware thread, first reply by kessaras)
4. LineageOS 15.1
5. Mindthegapps
Having troubles getting it to boot past the LG bootscreen (Once it boots completely, it seems to work fine).
---------------------------------------------------
So yesterday I was browsing my phone when it suddenly restarted. It had done this before multiple times and it always has gotten back to working just fine. Only this time was different, after the LG bootscreen went away, it appeared again. I'm aware of the bootloop issues the device has and was hoping I would get lucky but apparently not.
Configuration when bootloop happened:
-LineageOS14.1
-Stock kernel
-TWRP (3.1.1?, cant remember exact version it was 3+ anyway).
I noticed I could still access TWRP (Although it did crash few times back to LG bootscreen), so I first tried wiping caches etc (No luck). Anyway, I was quite close to just giving up at this point, but decided to fiddle around with the thing. I found out about the issue with one of the "big cores" heating too much and that it was possible to disable those. I decided to give it a try, and while I was at it, wanted to try out the newer LOS15.1. Downloaded titan kernel (no big cores), installed and went onto install LOS. First issue, my TWRP wasn't new enough to install the LOS15.1 (Error code 7). Did some searching and found out about "unofficial TWRP" installations that allowed me to install LOS15.1 (Used SteadfasterX's TWRP, O/ version).
After this I got a few kernel crashes (Green screen with a lot of text, different error codes each time), all searches pointed to my own error during installing stuff (I had older firmware while LOS required newer), and I believe these crashes had nothing to do with the actual bootloop issue. To fix this I went and grabbed the V29a firmware and the big cores disabled kernel which is in the first reply of that v29a thread. After this I managed to install LOS15.1+Mindthegapps (Also rooted it) just fine and it booted up past the LG bootscreen. I grabbed Kernel Auditor to check if the big cores had been disabled and I could only see 4 cores (max 1,44ghz).
Now the phone seems to run fine when I actually get it booted up. I tried restarting the phone and I was stuck in the loop again (Did multiple restarts). I tried booting into recovery (I got into the "factory reset" dialogs just fine which takes you to TWRP) but after that instead of TWRP it went back to the LG bootscreen (Tried again like 3 times). After this I plugged in my phone to my computer and got into TWRP first try(I wonder if there's an actual reason for this, I know it could be just pure luck). Then I went onto the reboot options in TWRP and booted into system. First time I got past the bootscreen but it crashed when asking for my SIM pin code. Second time after booting the same way, I got it working just fine and now the phone seems to be working happily again.
Is there anything I can do myself to trace this issue and improve the chances of booting up the phone or am I forced to just rely on luck and hope it boots completely without crashes (In the case of a crash/I need to restart the phone)?
I was trying to flash vanilla AOSP GSI and everything was going as expected.
After that, I flashed "disable force encryption" and the fingerprint gestures files among with magisk and pico gapps and the phone started rebooting after a single freeze of 2 or 3 seconds right after the initial boot.
Actually I made several tries with different combinations trying to figure out what was causing that behaviour and I noticed that it used to happen patching "fstab.qcom" file in "/vendor/etc" path as stated in this guide, always keeping a backup of the original "fstab.qcom".
At some point my device started rebooting even after restoring the old "fstab.qcom" so I flashed the stock rom via fastboot but it didn't solve the problem, then I also tried to flash in edl mode (enabled with "fastboot oem edl") but no way, the phone keeps rebooting without letting me finish even the initial setup.
I can access fastboot, edl and recovery. I can also flash TWRP but I can't turn off the phone.
I don't know what else to do, please help me
Sorry for me being a big noob and for my unclear english.
Yesterday I took some time to attempt to upgrade my OnePlus to Android Pie after finding out earlier that it's not as simple as just installing an update when your boot loader is unlocked. After a bit of searching I found this guide which I followed to upgrade OxygenOS to version 9.0.5. After some initial problems (I didn't pay enough attention and TWRP was set to auto-reboot which complicated matters a little) I managed to finish the upgrade and the device booted.
After confirming everything worked well I figured I should flash Magisk back onto the device so that I would have root access again. I flashed Magisk 19.3 and tried to boot the phone but it got stuck on the spinning OnePlus logo during boot. Left it running for over an hour, nothing happened so eventually I decided to flash the OTA update and the BL/KM patch again, which made my phone boot again but without Magisk, obviously.
After that I tried flashing Magisk 19.2 and Canary (19.4), both with the same results: a spinning logo, nothing more.
I'm not sure what else I can try. In a particular braindead moment I thought I should just try to take a look at Magisk's log file but of course that's not accessible without root access. I've got a feeling that the patch to the bootloader is causing issues with Magisk's firmware patch but I'm not familiar enough with this kind of problem to figure out what is going on exactly.
Does anyone recognize this problem or can one of you tell me what I could try to get Magisk running again?
I had this problem. Turns out after each flash: twrp, magisk, a reboot/ power off is required.
Here's what I do.
1) flash recovery using fastboot
2) reboot to recovery
3) on home screen of TWRP > reboot > power off
4) wait 5 seconds, turn phone back on and go to TWRP right away
5) flash magisk > TWRP home screen > reboot > power off
6) wait 5 seconds, turn phone back on and go to TWRP directly
7 TWRP home screen > reboot > reboot phone
Should get you to boot
dpj52190 said:
I had this problem. Turns out after each flash: twrp, magisk, a reboot/ power off is required.
Here's what I do.
1) flash recovery using fastboot
2) reboot to recovery
3) on home screen of TWRP > reboot > power off
4) wait 5 seconds, turn phone back on and go to TWRP right away
5) flash magisk > TWRP home screen > reboot > power off
6) wait 5 seconds, turn phone back on and go to TWRP directly
7 TWRP home screen > reboot > reboot phone
Should get you to boot
Click to expand...
Click to collapse
Thanks, I'll give it a go later tonight!
dpj52190 said:
I had this problem. Turns out after each flash: twrp, magisk, a reboot/ power off is required.
Click to expand...
Click to collapse
I tried it just now. Sadly I get the same end result. Thanks anyway though.
I have an ADB log of the crash that happens that causes the phone not to boot, maybe that's familiar to someone around here? I uploaded it here.
Hello can I ask a question why do you need root
OP, I just upgraded the battery in my OP3 and, due to some software quirks with a certain custom ROM, decided to switch to Havoc which I liked a lot on my OP6. I flashed Magisk with no issue. Here are the steps I took:
Starting with unlocked BL
Boot into the newest official version of TWRP via fastboot.
Flash OOS 9.0.5 and boot into it, completing device setup.
Reboot into OnePlus recovery, then from within, reboot into fastboot
Flash TWRP to recovery in fastboot, then shut down device (do not attempt to fastboot reboot recovery, it will boot into OOS and overwrite TWRP)
Boot device, use volume key to interrupt startup, boot into recovery (TWRP)
Follow installation instructions from Havoc thread, do not wipe cache/dalvik after flashing, do not boot before flashing all zips (I flashed ROM -> gapps -> Magisk in that order)
OP, I'm not familiar with OOS's current status. My recommendation is to try a different ROM to see whether it is a compatibility issue with the ROM itself. Alternatively, try flashing OOS then Magisk one after the other in TWRP without interruptions, like I did. From the wording of your OP it sounds like you booted into the newly flashed OOS, then flashed Magisk after, which may be the source of your problems.
kallum7 said:
Hello can I ask a question why do you need root
Click to expand...
Click to collapse
I work on an app that uses location data and it's pretty convenient to be able to test it on a real device but with a joystick instead of real location data. To make matters more complicated it's my personal phone and I use that to play Pokémon Go too. Without cheating I might add, the root is not for PG but because I do want to be able to play it on the same phone that I use to test my app I need Magisk to hide the fact that it's rooted or the game won't start.
LunarisDream said:
OP, I just upgraded the battery in my OP3 and, due to some software quirks with a certain custom ROM, decided to switch to Havoc which I liked a lot on my OP6.
Click to expand...
Click to collapse
Thanks for the suggestion but I'd rather keep using OOS on this phone as long as I don't have a new phone for daily use. I don't really want to modify this thing too much without having a replacement ready in the likely case that I screw something up.
OP, I'm not familiar with OOS's current status. My recommendation is to try a different ROM to see whether it is a compatibility issue with the ROM itself. Alternatively, try flashing OOS then Magisk one after the other in TWRP without interruptions, like I did. From the wording of your OP it sounds like you booted into the newly flashed OOS, then flashed Magisk after, which may be the source of your problems.
Click to expand...
Click to collapse
I tried both flashing the OTA, the modded firmware and Magisk in one go and separately after confirming that the OTA/FW were working. Sadly both methods resulted in the same problem.
If anyone's wondering I did a clean flash and factory reset, then installed Magisk again after that. Everything's working again now. Thanks for trying to help!
Hi all,
I'm coming back to Android after an absence and would like to run Lineage on a new US unlocked 9P. I followed the directions in the Lineage OS website and unfortunately the phone now is stuck in a constant animation of the blue circle moving left over the arc, and there isn't much I think I will be able to do about it until the battery runs out.
Here's what I did as per the directions:
-got and installed adb and fastboot from the Windows zips from Google
-added the install location to the path enviro variable
-installed the Universal ADB driver from Github
-activated USB debugging and OEM unlocking on the phone
-got the phone repeatedly into fastboot mode but then got stuck since 'fastboot devices' didn't show anything
-got bailed out by another thread here that one needs to check for updates with phone connected and Win will download the relevant USB drivers. Thanks!
-unlocked the bootloader
-downloaded and flashed the 18.1-20210803 recovery img
-sideloaded the copy-partitions 20210323 zip and it got stuck at 47% just like the website said
-did the factory reset
-sideloaded the the LOS 2020210803 zip to the phone and rebooted
When I rebooted it just plays the animation I mentioned at the beginning, so it looks like it's stuck in a permaloop.
I should mentioned that after I flashed recovery and booted into the normal Oxygen mode it would take much longer to boot so perhaps there was something already creating the loop.
I am grateful for any assistance.
Thanks,
How long have you left it? First install of Lineage spins for ages
I think I left it for an hour or so. Thanks for the info - I just turned it on and will let it spin for a while and see what happens.
I let it run until the battery died. I fully recharged it and am letting it run again. Same result of blue circle tracing arc to the left.
Success!
I tried to install the prior version (0720) which was then rejected for being too old. I wiped the storage and then tried 0803 again and it installed. I turned it on, the circle moved for a while and then the Lineage logo came up. I just finished setup, and it looks beautiful.
So far so good!
lexcimer said:
Success!
I tried to install the prior version (0720) which was then rejected for being too old. I wiped the storage and then tried 0803 again and it installed. I turned it on, the circle moved for a while and then the Lineage logo came up. I just finished setup, and it looks beautiful.
So far so good!
Click to expand...
Click to collapse
Everytime you flash a new rom you need to wipe data after
Anytime that happens you just go back into recovery and wipe data a few times and it should work after that.
It would've been due to encryption. Each time you flash a new rom you need to wipe userdata which removes your lock and also removes encryption. If you try to install a rom without doing this first, the rom cannot access that partition, because it doesn't yet know the unlock code/pattern, which is why it just gets stuck trying to do so.
Thank you to the 3 posters above, and I appreciate DJ Sub's explanation, makes sense in hindsight and I'll keep it in mind for the future.
PS - I'm glad to be back to the Android modding community, it's refreshing to be able to steer what OS my phone is running
I had the same problem (also a couple of different boot loop problems) when flashing LineageOS.
I did many things, so can't say for sure which one helped me to fix that, but the things I did were:
Restore from boot loop via MSM tool flashing EU image.
Updating that OxygeneOS to the latest using internal updater.
Repeating the LOS installation process several times in different conditions to isolate the source of the problem. I was changing LineageOS package, OpenGapps package, etc.
One of the problems I've found was that latest OpenGapps package (July 28th if I'm correct) was causing the boot loop on first start (very similar to what you're describing):
Phone tries to boot showing the LOS animation.
It goes for several minutes.
Then the phone vibrates, reboots and it continues from the start.
If I'm not mistaken, it was fixed by using the version from July 24th. The latest package also were removed from the OpenGapps page later AFAIR.
Second problem was after the successful boot. The phone was rebooting from the first setup wizard, booting to recovery (or some other partition) and proposing to make a factory reset.
Not sure which of my steps solved this, but I was updating back to the last LOS package watching closely that I'm flashing the same slot on each step and also making sure that slots are properly copied from one to another with the corresponding script.
Even in the most stable setup I was probably having some setup wizard loop problems, so I was skipping account setup steps and doing that manually later.
I'd say that installing LOS on OnePlus 9 Pro was most difficult and problematic installation in my experience and I did that a lot previously: HTC Wildfire S, THL 5000, Zuk Z1, Xiaomi Mi 5s, Xiaomi Mi 9T (Redmi K20) and several other devices.