Hi,
I have unlocked MI 5S Plus with TWRP 3.1.1.0 recovery and custom ROM lineage-14.1-20170518-nightly-natrium-signed.
Few days ago some water got inside the phone, just some (the phone didn't fall into the water). From that time I have a bootloop.
I can't boot the system, but TWRP recovery and bootloader mode is working perfectly fine.
I treid many times to load different zip ROMs from TWRP.
I also tried stock rom *.tgz via bootloader - stable and dev - still bootloop.
I opened the phone and cleaned the PCB with isopropyl alcohol, but no change.
What else can I do to get rid of bootloop and boot the system?
Regards
Bernard
have you tried running FSCK on the partitions? that may help determine if the chip is bad.
Failing that, we'd need some logcat or something to diagnose the problem. Can you get a logcat using ADB during boot?
Related
Hi,
I've got a Oneplus One that's stuck in a twrp recovery boot loop, and I'm wondering if anyone can help. I just had my screen replaced and when I got it back it was stuck in a twrp recovery bootloop, and I couldn't boot into fastboot mode- not via recovery, and not via holding the power/volume buttons down. By wiping the system in twrp I was able to get into fastboot mode, and flash the latest stock Cyanogen rom cm-13.1-ZNH2KAS254-bacon-signed-fastboot-d194f46bee. Everything booted up fine, and at that point the phone had been restored to stock. After that, I installed the latest cyanogenmod snapshot cm-13.0-20160419-SNAPSHOT-ZNH0EAO2O0-bacon, and everything booted up fine. Next I flashed the latest twrp 3.0.2-0 and rebooted the system. At that point everything seemed to be okay. I took the back cover off again to try and line up the speaker grill a little bit better, and now I'm stuck in a recovery bootloop again, except this time I can't get back to fastboot mode by wiping the system, and I don't have consistent internet access to research how to fix this (I'm posting this from the library). I was able to install the cm snapshot again via twrp thinking that it would just undo whatever it is that was causing the problem, but the phone still boots into twrp every time. Twrp does detect that I have indeed installed the zip, it's just I can't boot into anything other than twrp. Even when I plug the phone in powered off as if to charge it, it boots straight into recovery. I am able to put files on the phone via mtp, and it shows up under adb devices as serial# recovery when I mount mtp, so if there is a magic file that I can install, or an adb command that I can run, or if you know of the solution please lend me a helping hand.
Apparently the issue is that I wiped data via twrp instead of formatting data, and that wipe data is a feature of the stock recovery that twrp doesn't carry out, and as a result there is a command written somewhere on a partition that is forcing the phone into an endless twrp bootloop. Apparently this command <dd if=/dev/zero of=/dev/block/mmcblk0p3 bs=64 count=1> worked for a person that had a asus tf700 that was doing the same thing. How would I modify this command to get it to work on the OPO, or should it work as is?
This didn't work. I WAS able to use the colorOS flashing tool to install colorOS onto the phone, but it's still stuck in a recovery boot loop, and still can't get to fastboot, or get to the lock screen. I think that it may be a problem with the volume button since the colorOS boot seems to work, except for the recovery boot looping part. Any ideas?
Hey guys,
I got a moto g here which has a bootloop (cyanogenmod is installed).
I tried to boot TWRP but it also doesnt boot up fully - only showing the TWRP splash screen.
So I went and got the factory image and flashed that with fastboot - but even though there were no error messages it seems that nothing actually sticked on the phone.
When I try to boot it still booting CM and when I try to enter stock recovery its still the TWRP?!
Tried flashing CWM but its still TWRP..
Any ideas on how to fix it, or is this problem "known" or smth?
Seems like this is a hardware failure - like internal memory broken.
zroice said:
Hey guys,
I got a moto g here which has a bootloop (cyanogenmod is installed).
I tried to boot TWRP but it also doesnt boot up fully - only showing the TWRP splash screen.
So I went and got the factory image and flashed that with fastboot - but even though there were no error messages it seems that nothing actually sticked on the phone.
When I try to boot it still booting CM and when I try to enter stock recovery its still the TWRP?!
Tried flashing CWM but its still TWRP..
Any ideas on how to fix it, or is this problem "known" or smth?
Seems like this is a hardware failure - like internal memory broken.
Click to expand...
Click to collapse
Try using the mfastboot package, install the Motorola USB drivers if you haven't done so and flash the ROM, as per the instructions here:
https://forum.xda-developers.com/showpost.php?p=71328823&postcount=915
Seeing as I assume your phone responds to key presses, you can ignore the dismantling part of the instructions provided.
aha360 said:
Try using the mfastboot package, install the Motorola USB drivers if you haven't done so and flash the ROM, as per the instructions here:
https://forum.xda-developers.com/showpost.php?p=71328823&postcount=915
Seeing as I assume your phone responds to key presses, you can ignore the dismantling part of the instructions provided.
Click to expand...
Click to collapse
thanks for your reply!
unfortunately I already tried to install the stock rom with fastboot and mfastboot - every step would be processed, but in the end the phone was just in the same state - with twrp and cyanogenmod on it - both not booting,
Funny thing is that when i boot to twrp i can actually adb to the phone while it bootloops twrp - I tried placing and removing files in data but they would just disappear or reapper aka the device was still just as before.
Whats weird though is that I never get a single error message - it just takes all commands and stuff but they dont stick?! never had a phone like that. Usually the flashes fail or smth if the memory is broken,
zroice said:
thanks for your reply!
unfortunately I already tried to install the stock rom with fastboot and mfastboot - every step would be processed, but in the end the phone was just in the same state - with twrp and cyanogenmod on it - both not booting,
Funny thing is that when i boot to twrp i can actually adb to the phone while it bootloops twrp - I tried placing and removing files in data but they would just disappear or reapper aka the device was still just as before.
Whats weird though is that I never get a single error message - it just takes all commands and stuff but they dont stick?! never had a phone like that. Usually the flashes fail or smth if the memory is broken,
Click to expand...
Click to collapse
That's massively odd - have you tried unbricking the device by forcefully bricking it then unbricking it here:
http://forum.xda-developers.com/moto-g/help/how-to-revive-hard-bricked-moto-g-t2833798
https://forum.xda-developers.com/moto-g/help/how-to-unbrick-moto-g-falcon-t3394788
If you have tried everything, then I cannot help you any further sadly.
@zroice
try
Code:
fastboot boot TWRP.img
maybe flashed TWRP can't mount /data or other partition
I flashed TWRP through Minimal ADB and Fastboot. It said the install went fine. Now my phone is stuck in a bootloop at the "your device is booting now" screen. What do I do?
I had the same issue with twrp-3.2.1-1-berkeley.img. Using twrp-3.2.1-0-berkeley.img flashes fine but reboots into fastboot after about 8 seconds. Either I'm doing something incorrectly (??) or maybe a bit more work needs to be done with our twrp images.
EDIT: You need to use the "unofficial" TWRP image. Complete solution here.
I was trying to get lineageos on my s6 edge+ but it is stuck in a samsung logo loop after being unable to flash the rom and now it won't go back into TWRP either.
Initially I flashed the official TWRP for the zenlte which worked fine, it just did not want to install the rom due to apparently not having any device data. (Rom is for zenlte, this device is . (or something along those lines))
after a few attempts and doing a quick wipe I flashed an unofficial twrp and thats when it started looping without being able to get back into recovery mode.
Download mode does still work after a power off but flashing the official twrp again makes no difference.
This is a little beyond me and I'm not entirely sure what is going on.
The last phone I installed a custom rom on was an s4 so I'm a bit out of the loop with this new security stuff. I would have expected to at least be able to boot back into twrp.
Ok some progress:
Recovery mode worked again after leaving phone off (but still attached to computer) for a while. (I had given up but decided to try again after a few hours)
Partitions were missing / corrupted. Did a full format.
Installing rom still gave the 'device type is .' message.
Edited the rom zip to allow "" and " " ( in META-INF\com\google\android\updater-script )
Flashed rom + gapps + magisk in 1 go.
This ended up in LineageOS trying to start but rebooting into recovery after about 5 minutes.
Re-instralled just the rom, this gave a few errors about Magisk missing, re-installed Magisk as well before wiping cache and rebooting.
Now it came up with the welcome screen rather quickly.
Weird, but problem solved any ways.
Thanks! That was also my problem.
My Phone was running Android 11 perfectly fine. Has been for about a week and a half, and I've decided that I don't like the OS. I was going to flash a custom ROM and went to create a nandroid before flashing. Literally all I did was boot into recovery and TWRP got stuck in a bootloop, the TWRP splash screen appears, crashes and then reappears about 2 seconds later, now when I try to boot back into system, TWRP appears instead and continues to bootloop. I can enter fastboot mode but that's all.
So far I've tried
Booting TWRP through fastboot. Failed another bootloop.
Rebooting through ADB. Boots into TWRP.
Rebooting Bootloader. Seems to do nothing.
Does anyone have any ideas on how to fix this ? It seems strange to me that something as simple as booting recovery could do this much harm. I also have a nandroid backup stored on the device from about a month ago, so the data loss wouldn't be THAT major, but I'm also not sure how I could access it without system or recovery access.
Hi , Which version of TWRP use? I think there is an update a new version TWRP 3.5.2 , Try to flash it. if its still not booting try to boot the original Boot of OOS11.
May be this threads will help you.
OnePlus Community
Introducing our new OnePlus Community experience, with a completely revamped structure, built from the ground-up.
forums.oneplus.com
humood96 said:
Hi , Which version of TWRP use? I think there is an update a new version TWRP 3.5.2 , Try to flash it. if its still not booting try to boot the original Boot of OOS11.
May be this threads will help you.
OnePlus Community
Introducing our new OnePlus Community experience, with a completely revamped structure, built from the ground-up.
forums.oneplus.com
Click to expand...
Click to collapse
New version does not work as well. Flash the stock boot img to get out of bootloop.
Jacobo123 said:
My Phone was running Android 11 perfectly fine. Has been for about a week and a half, and I've decided that I don't like the OS. I was going to flash a custom ROM and went to create a nandroid before flashing. Literally all I did was boot into recovery and TWRP got stuck in a bootloop, the TWRP splash screen appears, crashes and then reappears about 2 seconds later, now when I try to boot back into system, TWRP appears instead and continues to bootloop. I can enter fastboot mode but that's all.
So far I've tried
Booting TWRP through fastboot. Failed another bootloop.
Rebooting through ADB. Boots into TWRP.
Rebooting Bootloader. Seems to do nothing.
Does anyone have any ideas on how to fix this ? It seems strange to me that something as simple as booting recovery could do this much harm. I also have a nandroid backup stored on the device from about a month ago, so the data loss wouldn't be THAT major, but I'm also not sure how I could access it without system or recovery access.
Click to expand...
Click to collapse
Did your problem got solved?As i updated to A11 a few days ago and am facing the same problem since.Did flashing the new version of twrp worked for you?
Jacobo123 said:
My Phone was running Android 11 perfectly fine. Has been for about a week and a half, and I've decided that I don't like the OS. I was going to flash a custom ROM and went to create a nandroid before flashing. Literally all I did was boot into recovery and TWRP got stuck in a bootloop, the TWRP splash screen appears, crashes and then reappears about 2 seconds later, now when I try to boot back into system, TWRP appears instead and continues to bootloop. I can enter fastboot mode but that's all.
So far I've tried
Booting TWRP through fastboot. Failed another bootloop.
Rebooting through ADB. Boots into TWRP.
Rebooting Bootloader. Seems to do nothing.
Does anyone have any ideas on how to fix this ? It seems strange to me that something as simple as booting recovery could do this much harm. I also have a nandroid backup stored on the device from about a month ago, so the data loss wouldn't be THAT major, but I'm also not sure how I could access it without system or recovery access.
Click to expand...
Click to collapse
At first.- Stable TWRP is not available til now for OOS11
For TWRP to work your device must be decrypted.
This link will help you, will get full details
- https://forum.xda-developers.com/t/...-oneplus-7-pro.3931322/page-152#post-84727891
For more questions and help, please post in that twrp thread only
Regards