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.
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:
Couple of days ago I got this OTA notification that Android 7.1 preview is available for update. As my phone is rooted I started the manual update procedure. After the flashing was finished, I restarted the phone and then I saw it was stuck at the Google screen. Just stuck, no response. Seemed unusual to me.
Let me tell you that I have been modding my Nexus 5 for about two years. I am familiar with most of the tweaks that can be done to a Nexus device. Nexus 5 served me amazingly. I bought Nexus 5x 3 months ago.
So, after it was stuck I restarted. Still stuck. I will tell you step by step what I did then:
1. Flashed the OS 7.1 again (I dunno why, the flash.all script doesn't work for me, so I always do that manually) - result is the same.
2. Last October update (NBD90W) was available in the folder so I flashed that - same result.
3. I downloaded the previous one (NRD90S) and flashed that - same result.
4. I locked the phone and unlocked again to erase everything (not sure if that's a good idea), then flashed the OS again - same result.
5. Then I tried LGUP and the tot files to give it the factory version. LGUP detects the phone, started installing. When the installation is finished and the phone restarted - same result.
6. Now that I gave it the factory version the phone got locked!
7. I searched google for hours but couldn't find a way to unlock it as the OS is not booting and I cannot turn USB debugging on!
8. Then I tried the default recovery mode (Android recovery, from the recovery screen Power + volume up) as it doesn't require unlocking the device. Wiped the cache and restarted - same result.
9. My phone is detected by the pc and ADB. So, I wiped everything and tried ADB sideload and get this error E: footer is wrong
10. I tried Nexus root toolkit. It detects the phone in fastboot mode, then restarts it and then it again is stuck on the Google screen.
I am extremely depressed!
I am from Bangladesh and there is no authorized LG servicing center here. So, I can't ask for there help.
All that I did over the past two years was the awesome threads of xdadevelopers. So, a big thumbs up for you guys :good:.
I learnt from the web that phone can be hard bricked if a wrong bootloader is flashed. That's impossible for me as I always remove the factory image extracted files after flashing is done from the ADB>platform-tools folder.
Now, is the phone hard-bricked? If it is, what to do with it? Any kind of suggestion will be very much appreciated.
Hello everyone,
yesterday I flashed a new Cyanogenmod 14 nightly (12062016) for my G4 from earlier nightly in TWRP. After reboot the phone keeps going back to TWRP and I can't seem to get it to boot to system..
I tried factory reset, reflashing back to old nightly, flashing stock.. but nothing seems to work.
Also tried doing this in the TWRP terminal:
dd[space]if=/dev/zero[space]of=/dev/block/platform/f9824900.sdhci/by-name/fota
Didn't fix the loop, I guess because it wasn't the OTA update that caused the problem in the first place.
If anyone has an idea, I would greatly appreciate the help!
Thanks.
If you can reach download mode you could try reflashing back to stock then starting again.....Hope you get yours fixed - Sorry to say this but mine did a very similar thing only 24 hours before you posted!!! Only mine was on stock FW and was in use at the time - I've now had to swap it as valuebasket who sold me the phone have ceased trading. If yours is a UK model you may be able to get it replaced under warranty - believe that LG guarantee their phones for 2 years and a ruling by the European court said that flashing a custom rom doesn't invalidate any warranties.
I have the same exact issue, I also flashed the latest CM14 nightly and cannot get the device to boot any rom.
I have even tried flashing stock rom but I get the same problem.
From what I have read, the bootloop issue happens once the device boots but I don't seem to be getting that far.
Any ideas?
Ran into the same problem 3 days ago. This is the first time I have encountered a non-revertible issue in 3 years as a cyanogenmod user. This changes my opinion on how safe it is to make use of a custom ROM. I tried to wipe everything, reinstall TWRP, change TWRP with another recovery, reinstall a safe NAND backup of mine.....nothing.....it went into boot loop. Before I read this post, I was convinced my phone encountered the infamous G4 bootloop problem.....now I see there are other examples, so it shouldn't be the case. Long story short, I had to check my device in at the LG assistance, with 25 days as time forecast.
The guilty nightly was 20161205.
I have never seen anything like this...
This has solved it for me - I installed LG Bridge and flashed the factory firmware using the tool. Now it seems I'm back on stock but at least it's working.
got mine working. I had to install LGUP and flash stock ROM. Once flashed I installed CM14 and I am back up and running again.
I tried LGUP but it could not recognize the device while this was looping.....a bad experience......
I have the same issue. My phone was updated to 20i via the original stock firmware, then I put twrp 3.0.2-0 and cyanogenmod on. I did a cyanogenmod update from within cyanogenmod, which just booted into twrp, then I manually installed the update zip that cyanogenmod had downloaded, then it always boots into twrp. I wonder if initiating the update from within cyanogenmod was the cause. The phone is not detected by LGUP or LG Bridge. I've tried this on a win10 machine, and a win7 vm from linux. I have access to twrp, and download mode by doing the reboot into bootloader from within twrp.
If those people who have fixed this could give more details about how they did it, that would be good. What exact steps did you take? What stock firmware version did you have before installing a custom rom? What OS version were you using? What twrp version?
Well. Mine got stuck in bootloop for the second time today. What is going on? In between the two bootloops I had one good update with CM. Using TWRP 3.0.2.1. Steps to reproduce failure: updating CM from within CM, it autoreboots into TWRP and after that nothing happends, no autoinstall. Then after a manual install of the new CM the bootloop starts.
Resolve the problem:
* Install LGUP 8994 DLL Ver 0 0 3 23, Install LGUP Install Ver 1 14, get the latest KDZ
* Get the phone into download mode with usb cable and after that in firmware update mode
* Startup LGUP and choose refurbish and select the kdz file.
* After that you can boot into your stock LG firmware again, reinstall TWRP an CM. If you want so.
Read that it is advised to manual update cm from within TWRP. TWRP will get an update in the future to solve this bootloop problem.
iankelling said:
I have the same issue. My phone was updated to 20i via the original stock firmware, then I put twrp 3.0.2-0 and cyanogenmod on. After a cyanogenmod update, it always boots into twrp. The phone is not detected by LGUP or LG Bridge. I've tried this on a win10 machine, and a win7 vm from linux. I have access to twrp, and download mode by doing the reboot into bootloader from within twrp.
If those people who have fixed this could give more details about how they did it, that would be good. What exact steps did you take? What stock firmware version did you have before installing a custom rom? What OS version were you using? What twrp version?
Click to expand...
Click to collapse
I second that. Same issue and neither LG Up nor LG Bridge will recognize my device. Looking in device manager there are no serial interfaces. Do I need a special driver that provides a com port for a phone in recovery or fastboot mode?
---Edith 2016-12-12: Found a solution for my issue:
The phone has to be in _download_ mode, not in recovery or fastboot. After realizing that I have to boot the phone in a different manner, it will be recognized by LG UP.
Here is how to boot the pone in download-mode:
- Power off your LG device.
- Press and hold Volume Up button.
- Connect your device to PC with a USB cable while holding the Volume Up button.
- You’ll boot into download mode with “Firmware Update” written on top of the screen.
Now everything is fine again.
croclacrimae said:
Hello everyone,
yesterday I flashed a new Cyanogenmod 14 nightly (12062016) for my G4 from earlier nightly in TWRP. After reboot the phone keeps going back to TWRP and I can't seem to get it to boot to system..
I tried factory reset, reflashing back to old nightly, flashing stock.. but nothing seems to work.
Also tried doing this in the TWRP terminal:
dd[space]if=/dev/zero[space]of=/dev/block/platform/f9824900.sdhci/by-name/fota
Didn't fix the loop, I guess because it wasn't the OTA update that caused the problem in the first place.
If anyone has an idea, I would greatly appreciate the help!
Thanks.
Click to expand...
Click to collapse
I was able to get out of that by also wiping by-name/misc. Don't do that, though, because then your wifi mac address will get messed up and you'll spend all day looking for a permanent fix for that.
I suggest reflashing a stock KDZ using LGUP, as others have said. You can get the usb drivers from LG Bridge.
I will release a fix for that soon. Check the twrp thread for updates on this.
Hi
I also have this problem
I installed cm-14.1-20161201-NIGHTLY-h815 successfully and was running it for almost 2 weeks without issues, today I updated to cm-14.1-20161213-NIGHTLY-h815 from cmupdater and I have been ending up in recovery every time I rebooted.
I tried flashing the latest cm recovery and reflashing the rom, with full wipes but no luck.
Full steps of recovering would be appreciated (for example, there are comments about flashing the latest stock rom, but a link to this rom would be helpful)
Thanks
Good news regarding this:
http://forum.xda-developers.com/showpost.php?p=70082901&postcount=213
The above will fix TWRP bootloop issues as well and I also released a first h811 version which should allow installing CM etc as it should.
Keep in mind that this is a BETA and not an official TWRP release.
Please report back in the above thread!
.
Does your twrp beta really fix the boot loop even it is already happening. What do I have to wipe? I have not managed to get out of the boot loop despite intalling it.
Is using using LG Up to flash to the stock rom really the only option?
Edited 2017-01-25 2:45 pm:
Well, sometimes you just have to be patient. Powered down the phone and when th H815 restarted CM did boot. Great. :good:
Hey, I just want to share a small detail, possibly a fluke that helped me overcome the bootloop.
So...I started with a fresh, stock H815, I don't quite remember the firmware version..it was something like version "20g"..
OK, I looked up several guides and tried to get the newest stable versions of each tool. I went through with the official bootloader unlock, then moved on to rooting: Kingroot didn't work for me so I went on installing twrp in fastboot mode so I could afterwards install supersu and root.
I got there eventually but first I was stuck in bootloop - kept ending up in twrp interface. I found the 2 dd commands but those didn't work for me as the msm_sdcc folder did not exist, but instead there was a "f9824900.sdhci". Tried to overwrite this one ...but as others have stated as well, it didn't work.
At that point, I had nothing to lose, I was starting to accept that I had soft-bricked my precious G4 so..I went on installing the DU 10.6 7.1.1 rom and the stock gapps, wiped dalvik, rebooted and held my breath...not literally
About 12 minutes later, after an endless red, spinning logo, my shiny ping pong paddle showed me a different screen, a fresh start welcome screen .
Almost 24h / 10-12 reboots (twrp included) / 70+ apps installed and removed later, the new OS holds around 2G ram average, a bit better battery life, smoother transitions, flawless navigation, flush streaming over both 3G/LTE & 2.4/5 G wifi.
FYI the reboots were intended, wanted to see consistency in boots - we're in the green . Now testing long term stability with moderate/high usage.
There is 1 aspect I noticed, there are a couple of contexts when the interface burps (several menus, various situations, never in apps) and resets back to homescreen...but I think that's more of a launcher topic than an OS one.
Other than that, so far I'm happy with the mod.
Hope my experience helps others that might be in the same spot I was or at lest boosts their confidence to try out a decent idea they might be pondering.
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)?
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.