[Q] Bootloop on recovery - Galaxy Note II Q&A, Help & Troubleshooting

Hi.
After a reboot a got a bootloop in the recovery. (TWRP) recovery. I can't enter the recovery anymore to fix anything. I can only use the download mode. This happened after I switched to F2FS file system using Resurrection ROM with the AGNI Kernel. The ROM was okay in the F2FS mode, the bootloop occured after rebooting in the TWRP from the ROM..
I have tried Odin in various versions, I tried to reflsh the recovery but it failed. I also tried to reformat using the PIT file. This indicated PASSED but still i was not able to flash a recovery thereafter.
What else could i try????
Many thanks!

offti1 said:
Hi.
After a reboot a got a bootloop in the recovery. (TWRP) recovery. I can't enter the recovery anymore to fix anything. I can only use the download mode. This happened after I switched to F2FS file system using Resurrection ROM with the AGNI Kernel. The ROM was okay in the F2FS mode, the bootloop occured after rebooting in the TWRP from the ROM..
I have tried Odin in various versions, I tried to reflsh the recovery but it failed. I also tried to reformat using the PIT file. This indicated PASSED but still i was not able to flash a recovery thereafter.
What else could i try????
Many thanks!
Click to expand...
Click to collapse
Flash the PIT file together with a 4.1.2 stock firmware downloaded from SamMobile. Root and do whatever you want after.

My mix is CyanogenmodX (by UtkarshGupta)+f2fs+agni. It's kinda weird and I did not found someone else with this problem except this topic. I did a lot of reflashing to nail it down to the following:
I'm stuck with a twrp loop (twrp logo appears and then reboots) when using f2fs (/data only) and the system is installed. This problem is now for some months, before it worked fine with the same setup. Also complete wipes of all partitions and even repartition did not help.
-It works as long as there is no OS present or not booted for the first time.
-To fix it, I can either format /system or /data (to ext4). To do that, I have to flash an other recovery.
-It does not matter if I use the format script (as provided in the OT), or with twrp advanced wipe/change partition type (which only works if TWRP is not newer than 2.8.1.0 - newer versions give an error: unable to wipe data).
-The OS itself runs fine.
A strange thing to note: there was a time, where this problem occurred, to fix it, I had to flash an other recovery via odin, boot into that recovery, do nothing(!), reflash twrp with odin again, and I could access twrp again until I booted the OS again. This suddenly stopped and the only fix is the way I described above.
And a site note: the "loop" only occurs when using the advanced reboot options from the OS (or any other tool from the OS to boot into recovery), as it sets a recovery flag. When using volup+home to access recovery, it only happens once, still allowing the workaround to flash another recovery to remove the flag, and able to reboot system afterwards again (but no access of twrp anymore).
I also tried updating bootloader (and modem) with no success.
Process on installing: wiping everything except externalSD, change /data to f2fs, reboot recovery, install CMx, gapps, supersu, agnikernel.
Aaaaany input that might help to resolve this is really appreciated.

Related

[Q] Helping with bootloop

Hi guys! I have a problem. I had paranoid android as rom and it worked great! Some days ago while i was using Facebook app there was an overloading of memory (i think) and there was the reset of the Nexus. From that moment the cellphone is in bootloop. I can access in the recovery (CWM). I tried some methods:
1)in recovery mode i tried to wipe everything but nothing
2) i used nexus root toolkit but nothing... also enabling the option softbrick/bootloop
3)using gnex toolkit... the same
4)using Odin too but nothing to do
What can i do ??
Thanks
PS: all these methods that i tried seem to work but when i turn on the phone it is always in bootloop -.-
try flashing the system in recovery or in fastboot mode?
vaanus said:
try flashing the system in recovery or in fastboot mode?
Click to expand...
Click to collapse
I tried both without good results i think it is bricked...
Same problem here
Am facing the same problem here.
Was on cm11 and one fine day without any issues got into a boot loop. My phone is encrypted, so during boot, it asks the password and even logs into the phone, but within 5 seconds, it goes into a reboot.
Tried almost everything i could find.
erasing/formatting from fastboot - shows success but logs into cm11 again with bootloop
Trying to flash stock - everything shows success but still back to cm11 when rebooted
trying to format mke2fs -t ext4 /dev/block/mmcblk0p12 from recovery- still nothing
flashing through odin - no change.
The crazy part is, everywhere it shows success and when it finally boots system, its booting cm11 and asks for password to decrypt data. And after booting goes into a reboot.
The only place i see any failure is when trying to format /data from twrp. It says its not able to mount the partition.
Any pointers anybody? Can't think of anything else which i can do to fix this issue. :crying:
I had same probleme after install lollilop rom:
[ROM][5.0.1/LRX22C][AOSP] AOSP Lollipop: a wee better than stock.
1 day use and bootloops, everything i do seems ok but it always bootloop without changes !!!
1)in recovery mode i tried to wipe everything but nothing
2) i used nexus root toolkit but nothing... also enabling the option softbrick/bootloop
3)using gnex toolkit... the same
4)using Odin too but nothing to do
If anyone get a solution ?
I had same probleme
I had same probleme after install lollilop rom FML-AOSP-5.0-20141207 Recovery: CWM V6.0.5.1
I've tried everything from wiping erasing and reflashing & reflashing data, wiping cache, davlik cache, system, internal storage. I did the factory reset in CWM recovery to wugfresh toolkit's "flash stock+unroot" with odin mode All finished successfully according to fastboot , recovery , odin but a reboot showed the system in the same state as before.

Strange issue with mi5s not booting flashed rom

Hi,
My Mi5s was in a bootloop between recovery mode and Mi logo.
I was able to get to fastboot via cmd, phone is unlocked, and I also flashed TWRP, then Vol + and power to load TWRP.
From there Ive tried installing multiple roms, but each time I reboot system it goes back into TWRP.
I've tried many ways of installing new roms, like wiping all data/factory reset/formatting before flashing supersu + lineage os or cm13 and then gapps, after flashing it says flash was successul...
I've also been able to use xiaomiflash to flash official latest global stable which puts phone back into bootloop.
I also flashed latest chinese dev which loads Mi Recovery 3.0, from there I'm still unable to install the rom, after showing the rom loading, just a few seconds in, the phone reboots.
Quite confused and unsure of what to do now... New to forum, not sure where to post this.
goatlad said:
Hi,
My Mi5s was in a bootloop between recovery mode and Mi logo.
I was able to get to fastboot via cmd, phone is unlocked, and I also flashed TWRP, then Vol + and power to load TWRP.
From there Ive tried installing multiple roms, but each time I reboot system it goes back into TWRP.
I've tried many ways of installing new roms, like wiping all data/factory reset/formatting before flashing supersu + lineage os or cm13 and then gapps, after flashing it says flash was successul...
I've also been able to use xiaomiflash to flash official latest global stable which puts phone back into bootloop.
I also flashed latest chinese dev which loads Mi Recovery 3.0, from there I'm still unable to install the rom, after showing the rom loading, just a few seconds in, the phone reboots.
Quite confused and unsure of what to do now... New to forum, not sure where to post this.
Click to expand...
Click to collapse
I had the same issue when I first installed some ROMs for this phone and it got me really confused since I was doing everything right. This is what worked for me
MAKE SURE YOU HAVE OFFICIAL TWRP FIRST BEFORE ANYTHING
Go into fastboot and type
fastboot format userdata
Go back to TWRP and go into wipe/advanced wipe.
Select data and then select repair or change partition
Then go into change filesystem and choose either F2FS or ext4. If one gives an error try the other one, after that format to which ever
If you're on AOSP/LOS ROMs I'd recommend F2FS since its a bit faster and makes your storage last way longer
crzykiller said:
I had the same issue when I first installed some ROMs for this phone and it got me really confused since I was doing everything right. This is what worked for me
MAKE SURE YOU HAVE OFFICIAL TWRP FIRST BEFORE ANYTHING
Go into fastboot and type
fastboot format userdata
Go back to TWRP and go into wipe/advanced wipe.
Select data and then select repair or change partition
Then go into change filesystem and choose either F2FS or ext4. If one gives an error try the other one, after that format to which ever
If you're on AOSP/LOS ROMs I'd recommend F2FS since its a bit faster and makes your storage last way longer
Click to expand...
Click to collapse
tried official twrp 3.1.1-0, did these steps only, maybe I've missed something:
installed twrp 3.1.1-0 then went into fastboot and typed fastboot format userdata
rebooted into TWRP, i was promted whether to keep system read only, I tried first swiping to allow mods, and also keep read only then proceeded:
changed data to F2FS (didn't wipe or factory reset anything else)
rebooted system
copied lineage and gapps zip files to phone
installed latest lineage then gapps 7.1 arm64
rebooted system, back into twrp

Always boot into recovery mode

Today I wanted to upgrade to OOS 5.1.1. But after flashing and reboot, my 5t went into recovery mode again. Then after that, the phone always reboot into recovery mode.
I tried flash stock recovery, blue spark recovery, tried to flash oos 5.0.4, none works.
What can I do to save my 5T? TIA.
I noticed that I have this error in my twrp codeworkx recovery:
failed to mount /vendor (invalid argument)
This happened to mine as well. I did a full wipe and flashed the stock recovery and then flashed the most recent Stock OOS.
What do you mean by a full wipe?
cache+davlink+system+data? I did.
Internal storage needs to be wiped too?
Floss0324 said:
This happened to mine as well. I did a full wipe and flashed the stock recovery and then flashed the most recent Stock OOS.
Click to expand...
Click to collapse
lyrebird said:
Today I wanted to upgrade to OOS 5.1.1. But after flashing and reboot, my 5t went into recovery mode again. Then after that, the phone always reboot into recovery mode.
I tried flash stock recovery, blue spark recovery, tried to flash oos 5.0.4, none works.
What can I do to save my 5T? TIA.
I noticed that I have this error in my twrp codeworkx recovery:
failed to mount /vendor (invalid argument)
Click to expand...
Click to collapse
First thing, the error about /vendor in TWRP can be ignored because you will not have that partition if you have not installed a trebelized ROM (MOKEE treble rom).
Next is your issue:
There are two approaches I can Think of:
Approach 1) - Download official full rom from this thread
- Boot into TWRP and copy this ROM to your phone
- Wipe Clean (standard TWRP clean flash step) keeping internal storage intact
- Install ROM and try to boot.
- Sometimes it will boot back into recovery, you can try to install again.
- If it boots up fine, then follow this guide to install TWRP correctly again.
- If it didnt boot up and you are ok to wipe everything, Boot into TWRP
- Wipe Everything (you will lose all data, photos everything)
- Boot back into twrp
- Now follow install steps again.
Approach 2) if 1 didnt work:
- use this guide to unbrick your device
- You can then ROOT, install recovery etc by following this thread
I have recently experienced this problem, there was little help and finally I have to wipe all data on the phone. It was a pain in the ass and i hope you wont have to go through it !
Did many rounds of flashing of recovery and rom, tried many combinations. It eventually worked.
While I am not 100% sure, i think what makes it work is to use compatible recovery (8.0 or 8.1) with rom, and wipe both cache, system, and data after (?) flashing.
Thanks!
krispuniq said:
First thing, the error about /vendor in TWRP can be ignored because you will not have that partition if you have not installed a trebelized ROM (MOKEE treble rom).
Next is your issue:
There are two approaches I can Think of:
Approach 1) - Download official full rom from this thread
- Boot into TWRP and copy this ROM to your phone
- Wipe Clean (standard TWRP clean flash step) keeping internal storage intact
- Install ROM and try to boot.
- Sometimes it will boot back into recovery, you can try to install again.
- If it boots up fine, then follow this guide to install TWRP correctly again.
- If it didnt boot up and you are ok to wipe everything, Boot into TWRP
- Wipe Everything (you will lose all data, photos everything)
- Boot back into twrp
- Now follow install steps again.
Approach 2) if 1 didnt work:
- use this guide to unbrick your device
- You can then ROOT, install recovery etc by following this thread
I have recently experienced this problem, there was little help and finally I have to wipe all data on the phone. It was a pain in the ass and i hope you wont have to go through it !
Click to expand...
Click to collapse
What TWRP were you using? Had basically the same problem with "twrp-3.2.1-x_blu_spark_v8.74_treble-op5_op5t.img", flashed an older version and it worked fine.
Seeing "failed to mount /vendor (invalid argument)" as you mentioned happened to me too. I think it means it's only for treble compatible ROMs.
if you were rooted with magisk, you have to flash the magisk uninstaller before flash the rom.
I had the same problem after flashing XXXnolimits rom (bluespark recovery 8.73). I just power off the phone pressing the power button for a while (10-20 seconds). It worked for me and the rom was succesfully flashed. Hope this help for the future.
i will keep this in mind and will try it next time when we have an update! Thanks.
caluz78 said:
if you were rooted with magisk, you have to flash the magisk uninstaller before flash the rom.
Click to expand...
Click to collapse

TWRP cannot mount /data or /system

I finally got unlocked, installed ADB/Fastboot on my computer, and flashed TWRP. (Followed this guide)
TWRP starts up with no problem, and flashed Magisk 'successfully', however I don't have root and I can't install any ROMs.
The problem appears to be TWRP cannot mount /system or /data. I've tried reflashing it to no avail. What am I doing wrong?
Edit: Since the reflash attempt it won't boot into anything other than TWRP. That's inconvenient.
Edit Edit: After letting the phone sit for ~5 minutes doing nothing, I was suddenly able to mount /data and flash a ROM. Unfortunately, my device still only boots to TWRP, and once again I can't mount /data or /system.
zurginator said:
i finally got unlocked, installed adb/fastboot on my computer, and flashed twrp. (followed this guide)
twrp starts up with no problem, and flashed magisk 'successfully', however i don't have root and i can't install any roms.
The problem appears to be twrp cannot mount /system or /data. I've tried reflashing it to no avail. What am i doing wrong?
Edit: Since the reflash attempt it won't boot into anything other than twrp. That's inconvenient.
Edit edit: After letting the phone sit for ~5 minutes doing nothing, i was suddenly able to mount /data and flash a rom. Unfortunately, my device still only boots to twrp, and once again i can't mount /data or /system.
Click to expand...
Click to collapse
format data
Mackay53 said:
format data
Click to expand...
Click to collapse
Data has been formatted, problem persists.
Zurginator said:
Data has been formatted, problem persists.
Click to expand...
Click to collapse
If it doesn't work after typing yes to format, then flash another twrp
Zurginator said:
Data has been formatted, problem persists.
Click to expand...
Click to collapse
Are you sure you formatted data? That's different than a wipe. Try rebooting into fastboot mode, connecting your phone to a computer and typing the command "fastboot format userdata" (fastboot is 1word) and then rebooting (unless you have already tried this). If you have make sure you are using the latest official TWRP for this device (not a modded one) and try flashing your ROM again. Also, some custom ROMs won't boot up if you flash Magisk at the same time. You need to flash the ROM and Gapps (if desired) and then fully boot into the system. After you have successfully booted into the ROM you can go back into recovery and flash Magisk.
Sir, I believe you can benefit from this:
https://forum.xda-developers.com/mi-mix-2/how-to/mix-pack-simple-user-twrp-adaway-supersu-t3792753
Even if you are not intending on using MIUI, this should bring your phone to stock (with unlocked bootloader).
jhs39 said:
Are you sure you formatted data? That's different than a wipe. Try rebooting into fastboot mode, connecting your phone to a computer and typing the command "fastboot format userdata" (fastboot is 1word) and then rebooting (unless you have already tried this). If you have make sure you are using the latest official TWRP for this device (not a modded one) and try flashing your ROM again. Also, some custom ROMs won't boot up if you flash Magisk at the same time. You need to flash the ROM and Gapps (if desired) and then fully boot into the system. After you have successfully booted into the ROM you can go back into recovery and flash Magisk.
Click to expand...
Click to collapse
That did the trick. I am 100% sure I was formatting data though. I'm up and booting custom ROMs now. Problems abound, of course, but that's what makes it fun.
Thanks everyone for helping out!
Try flashing the official TWRP from https://dl.twrp.me/chiron/twrp-3.2.1-0-chiron.img
I had the same problem. Just download the latest version from web or play store to fix the issue.

Tablet wont reboot in recovery mode after flashing TWRP

Hi to everyone.
Recently, I wanted to mod my tablet (SM-T805 chagalllite) and install the TWRP, and then a custom ROM. I followed a guide, dowloaded the twrp.img.tar file, dowloaded ODIN (3.13) and continued. I started my tablet in Fastboot/Odin mode, selected the file under the AP checkbox, connected it to the computer and then flashed the recovery. It said PASS and immediatly after it rebooted I pressed the key combo Power+Home+VolUp but it started normally. When I returned to the fastboot mode, it said KNOX WARRANTY VOID 1, so it did something. But simply the recovery wont start up, although I retried another 3 times. I tried with the AutoRoot package, it did the red android thing, the SuperSu app was there but the Root Binary wasn't. Any help?
P.S:
The twrp and odin are both at last version.
Nevermind, I solved my problem. I installed CF Autoroot which reinstalled stock recovery, and flashed TWRP using its official app.:good:
I need help was using twrp 321 some thing for quite a while and had no issues flashing ROMs back up ect. But I tried to do a restore and it failed due to , unable to mount system.
Ok no problem i thought I'll reboot and try again. Only now twrp loads the splash screen then reboots it self. IV tried updating to latest version with Odin still doesn't help. Samsung t805 here please help
t1m0thy001 said:
I need help was using twrp 321 some thing for quite a while and had no issues flashing ROMs back up ect. But I tried to do a restore and it failed due to , unable to mount system.
Ok no problem i thought I'll reboot and try again. Only now twrp loads the splash screen then reboots it self. IV tried updating to latest version with Odin still doesn't help. Samsung t805 here please help
Click to expand...
Click to collapse
Ok I fixed it the back up from twrp curreupted the recovery partition. Even reinstall twrp doesn't work or trying to get the stock recovery. To fix it you need to download the entire stock ROM and install the ap via oden in odin mode. My system didn't even boot stock but this fixed the recovery partition and could flash twrp and install a custom ROM

Categories

Resources