Hello, I bought the phone 3 months ago and it worked perfectly since I unlocked the bootloader. So what I wanted to do is just replace the crap poco rom with xiaomi.eu rom. I did unlock the bootloader after waiting (it's not my first xiaomi device nor my first unlock) then i've downloaded the rom from xiaomi.eu, reboot phone into fastboot and flash the rom just with the .bat file in the rom folder (windows_fastboot_first_install_with_data_format.bat) instead of using Miflash tool (dunno if that help solve the problem but every info metter). if i don't remberber wrong the first two time the installation was in progress but it got stuck (i've waited like 15 min but it was just blocked) so i had to close the cmd, restart to fastboot and reinstall the xiaomi.eu rom, and this time everything went good. After that the phone sometimes reboot, sometimes it shutdown, sometimes i see the same apps open in the background like 3-4 time (and they work in different istance, for example: if i open facebook app then scroll down or check a profile, then go back to my phone homescreen and lock the phone, when i unlock it and open facebook app it will open like i've never opened it before and if i check my opened app i see 2 different facebook app showing me different things. ps i never saw a thing like this) and it's more hot then usual sometime just by watching a video it became really hot. So i tought it was the rom and i flashed back the stock rom, but i had the same problem with the installation and everything else i mentioned before. last thing i've done is trying to flash the rom with miflash tool but it wasn't working, so i reflashed the rom and locked the bootloader with the cmd command and now the 2 problem are persisting, 1 the phone gets hot quick by just using it (no gaming or heavy app), 2 the phone shutdown randomly even if it's not hot(i've tested with genshin impact max settings with performance mode in game app and the phone was really hot but no shutdown even after 40 minutes), and one time the phone rebooted itself.
I haven't done any modification to kernel, voltage, frequency, battery is 98% 4.415 mah and haven't installed custom recovery.
I really want to solve all these problem, and also the miflash tool not working, only cmd work (and last time i've installed the rom it wasn't finishing because it got stuck at some point like the data interrupt but no error on cmd, so i had to install the rom inputting the command to install it one by one), THANK YOU SO MUCH IF YOU READ ALL THE POST, I WILL APPRICIATE ANY HELP
Just open bootloader,install twrp and flash stock rom again.
Andreasgbrv2 said:
Just open bootloader,install twrp and flash stock rom again.
Click to expand...
Click to collapse
how sure you are about this?
Try to reflash and do a factory reset from system before using (clean install from fastboot, boot into rom and complete setup, and do factory reset from settings)
Related
Hi everyone,
today I woke up and as usual i turned on my Gnex GSM (that has TWRP 2.8.0.0 and PA 4.6 beta 3 release1) and after a few minutes it started rebooting. i tried to remove battery at first but nothing happened; every time I put in the battery it starts, ask me for PIN, seems everything ok but reboots again.
I tried to enter in recovery mode to do a factory reset and even if TWRP says successful wipe nothing happens because when i reboot everything is like before. Itried to change recovery from TWRP to CWM but I can't even do that it "stucks" with TWRP. Fortunately I made a backup recently so I don't mind losing everything but if everyone has a solution please tell me because I don't know what to do!!
Another thing that compared in the log of TWRP during wipes was some strange ( for me, I'm not a developer) errors like "E: enable to stat '/data/media/.....'
If anyone can help I'll appreciate a lot!!! :laugh::laugh::laugh:
Thanks all!!
Same thing happened to me too....
Everything was working butter smooth when **** hit the fan.
I own GSM Gnex, rooted with stock 4.3 with Xposed installed. Custom recovery was TWRP
One fine day I was sitting with a friend in an restaurant when my phone suddenly started rebooting after reaching the homescreen. Mind you I can unlock my phone but after a couple of seconds, it would reboot
For two days, I did everything I could, used Wugs NRT, did a factory reset using TWRP, used ODIN, Flashed stock using toolkit and did that again manually using ADB. Nothing happened.
It says 'successful' when I flash using NRT, but nothing really changes and it freezes halfway while using ODIN and 'FAIL' error shows up.
After two days, I gave it to the shop from where I bought the device and its fourth day today but he still isnt able to repair my phone.
Mind you, I can access TWRP and all the functions, even factory reset but nothing happens.
At first I thought it might be moisture but it wasnt the case. I think it has to be an hardware issue
Hi.
I have a problem with my D855. My phone is rooted and runs the fulmics ROM. Everything was working fine, , on Fulmics 5.3, except than one day, I was using my phone normally and then it crashed. I saw the phone rebooting, but for some reason it got stuck. The phone tried to boot unsuccessfully until the "firmware update" went through, after what it reboots again (unsuccessfully) and so on.
At that time, I was able to access twrp, do some backup, and flash properly with a downgraded version of fulmics (from 5.3 to 4.1).
It was able to boot again and use my phone like before. Yet, after one month of usage, the same problem happened on version 4.1. The phone crashed and now cannot boot.
Any idea of where it is coming from? Should I go back to stock? Should I contact customer service?
What did you do before the phone crashes ?
I think you probably should flash the stock ROM and wait for an other crash... or not.
Jb-kun said:
What did you do before the phone crashes ?
I think you probably should flash the stock ROM and wait for an other crash... or not.
Click to expand...
Click to collapse
I haven't done anything special. I think that the first time I was playing on candy crush. The second time I was just looking at pictures in my gallery.
I was using the ROM without any tweaks or extra modules such as Xposed. Just regular use.
Update on my situation: I switched back to stock ROM and it seems to work OK for now (it has been 4 days). So I will wait and see if new problems happen. By the way, it was extremely difficult for me to get back to Stock directly from fulmics ROM. I tried several methods that I have found on xda based on LGUP or LG Flash tool without success. For some reason I was not able to connect the phone to my PC in download mode.
The only way that I found was to use a nandroid backup that I did just after rooting the phone and that was based on stock ROM.
shewshain said:
I haven't done anything special. I think that the first time I was playing on candy crush. The second time I was just looking at pictures in my gallery.
I was using the ROM without any tweaks or extra modules such as Xposed. Just regular use.
Update on my situation: I switched back to stock ROM and it seems to work OK for now (it has been 4 days). So I will wait and see if new problems happen. By the way, it was extremely difficult for me to get back to Stock directly from fulmics ROM. I tried several methods that I have found on xda based on LGUP or LG Flash tool without success. For some reason I was not able to connect the phone to my PC in download mode.
The only way that I found was to use a nandroid backup that I did just after rooting the phone and that was based on stock ROM.
Click to expand...
Click to collapse
You can also use the Stock rom flashable from twrp. So you can wipe the system partition and get a "better situation" than a nandroid backup that should be with an old version.
Or use this that has also root and other improvements.
shewshain said:
Hi.
I have a problem with my D855. My phone is rooted and runs the fulmics ROM. Everything was working fine, , on Fulmics 5.3, except than one day, I was using my phone normally and then it crashed. I saw the phone rebooting, but for some reason it got stuck. The phone tried to boot unsuccessfully until the "firmware update" went through, after what it reboots again (unsuccessfully) and so on.
At that time, I was able to access twrp, do some backup, and flash properly with a downgraded version of fulmics (from 5.3 to 4.1).
It was able to boot again and use my phone like before. Yet, after one month of usage, the same problem happened on version 4.1. The phone crashed and now cannot boot.
Any idea of where it is coming from? Should I go back to stock? Should I contact customer service?
Click to expand...
Click to collapse
Same problem here. Normal usage suddenly started to reboot and now it's stuck in boot loop
Coming from Fulmics too - stopped working one fine day.
Now, continues to boot-loop at the initial LG screen. Trying to get into the recovery shows me the the 'Factory Reset' screen, but beyond that leads to boot-loops again. Even the Download mode loops!
I'm at my wits end without a solution in sight.
Blysterk said:
You can also use the Stock rom flashable from twrp. So you can wipe the system partition and get a "better situation" than a nandroid backup that should be with an old version.
Or use this that has also root and other improvements.
Click to expand...
Click to collapse
Thank you for this advice. I was able to update my stock ROM after the Nandroid backup through LGUP, but your method would have been faster.
But anyway, I am waiting to see if I am stuck with bootloops again, using non-root stock version, so I can send it to customer service if this happen again.
AhmadAlmousa said:
Same problem here. Normal usage suddenly started to reboot and now it's stuck in boot loop
Click to expand...
Click to collapse
abourdeau said:
I have the exact same problem, I even bought a second battery with no success.
Click to expand...
Click to collapse
Are you using Fulmics ROM as well? Can you have access to TWRP? I was able to connect to a PC in the recovery mode and to transfer files before flashing, in case you need some basic backup...
prakhargr8 said:
Coming from Fulmics too - stopped working one fine day.
Now, continues to boot-loop at the initial LG screen. Trying to get into the recovery shows me the the 'Factory Reset' screen, but beyond that leads to boot-loops again. Even the Download mode loops!
I'm at my wits end without a solution in sight.
Click to expand...
Click to collapse
Silly question, but are you sure that you selected "Yes" when the screen asks you about factory reset? you have to press "volume down" and the "power button", since the default answer is no.
shewshain said:
Silly question, but are you sure that you selected "Yes" when the screen asks you about factory reset? you have to press "volume down" and the "power button", since the default answer is no.
Click to expand...
Click to collapse
Yes, of course I was able to access TWRP successfully earlier.
Curiously enough, the phone boot-loops in regular startup, Download mode and trying to get to recovery. However, it doesn't restart itself and fall into a loop, while on the Factory Reset menu. Am I correct in assuming that the battery could not be the root cause of the overall problem? Because if it was, it would likely loop even on this Factory Reset menu as well as far as I understand.
Unfortunately, the phone restarts as soon as it lands in the Download mode so I cannot even restore to stock.
EDIT: Okay, weirdly enough it just booted and reached the homescreen before restarting again. What I did was let it charge to a 100% and tried booting while plugged in. Could it be the battery after all? Though this exact set of steps hasn't been helpful before.
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:
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.
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.