Hi! I have lineage os 17.1 by ivanmeler installed on my S7 flat , I was using opera browser to download a 1GB file, As soon as the download started my phone shut down and got stuck in a bootloop, I booted to the TWRP recovery, And tried to restore a backup that I had done before, but I got an error that says (extractTar error 255), Then I decided to just wipe data and system and flash the rom again, the rom gets flashed, I reboot into system and the phone gets stuck in a bootloop again, what is going on withmy phone, Please someone help!
Thanks in advance.
zariouh said:
Hi! I have lineage os 17.1 by ivanmeler installed on my S7 flat , I was using opera browser to download a 1GB file, As soon as the download started my phone shut down and got stuck in a bootloop, I booted to the TWRP recovery, And tried to restore a backup that I had done before, but I got an error that says (extractTar error 255), Then I decided to just wipe data and system and flash the rom again, the rom gets flashed, I reboot into system and the phone gets stuck in a bootloop again, what is going on withmy phone, Please someone help!
Thanks in advance.
Click to expand...
Click to collapse
Wipe cache before reboot.
cooltt said:
Wipe cache before reboot.
Click to expand...
Click to collapse
I have already tried wipping cache and dalvik cache, I even wiped system and data and installed the ROM again but the phone's still stuck in a bootloop.
Now I'm about to flash through Odin back to stock and see if the phone turns on.
Hm... While I was downloading the stock firmware to flash the phone, I thought of checking the data folder inside the TWRP recovery, And turns out The data is still there, It never got wiped, that's why the phone is stuck in a bootloop, Now what could be preventing the data from getting wipped? I don't get any errors when I wipe the data partition, And this is also strange because usually you get a bootloop when you flash some kind of zip file through the recovery (mods or something like that), but I was just using the browser to download a file , And phone suddenly shutdown and got stuck in a bootloop, Could someone pls help me figure out what's causing the problem
zariouh said:
Hm... While I was downloading the stock firmware to flash the phone, I thought of checking the data folder inside the TWRP recovery, And turns out The data is still there, It never got wipped, that's why the phone is stuck in a bootloop, Now what could be preventing the data from getting wipped? I don't get any errors when I wipe the data partition, And this is also strange because usually you get a bootloop when you flash some kind of zip file through the recovery (mods or something like that), but I was just using the browser to download a file , And phone suddenly shutdown and got stuck in a bootloop, Could someone pls help me figure out what's causing the problem
Click to expand...
Click to collapse
That ROM is in BETA mode, which means it could be lost of things. Your question should be asked on the LOS 17 thread itself but when a ROM is in BETA mode it's very difficult to tell what the problem is. Ask the developer @ivanmeler he might be kind enough to answer you.
Help Me too !!!!
No Lineage based android Q roms booting on my S7 too. I restored stock but then also bootloop.
Pls Help
I'll try to help
Ayushskull said:
No Lineage based android Q roms booting on my S7 too. I restored stock but then also bootloop.
Pls Help
Click to expand...
Click to collapse
Hi! Can you describe the steps that you tried to revert back to stock? Did you use the repair firmware (5 files) or one file firmware?
zariouh said:
Hi! Can you describe the steps that you tried to revert back to stock? Did you use the repair firmware (5 files) or one file firmware?
Click to expand...
Click to collapse
Bro I used these files AP, BL, CP, CSC
Also when I try to boot rom (Aicp) with Cronos Kernel which is for Oneui 2.0 my phone somehow booted but wifi is not working. So can you tell me exact problem as a OneUI based kernel is booting AOSP while when I use morokernel no AOSP based rom boots
Ayushskull said:
No Lineage based android Q roms booting on my S7 too. I restored stock but then also bootloop.
Pls Help
Click to expand...
Click to collapse
Ayushskull said:
Bro I used these files AP, BL, CP, CSC
Also when I try to boot rom (Aicp) with Cronos Kernel which is for Oneui 2.0 my phone somehow booted but wifi is not working. So can you tell me exact problem as a OneUI based kernel is booting AOSP while when I use morokernel no AOSP based rom boots
Click to expand...
Click to collapse
Sorry but I don't have enough knowledge to help with kernels, Now from what I understand is that you tried flashing stock ROM and your phone got stuck in a bootloop, Right? And just to confirm could you mention the model of your s7?
Ayushskull said:
Bro I used these files AP, BL, CP, CSC
Also when I try to boot rom (Aicp) with Cronos Kernel which is for Oneui 2.0 my phone somehow booted but wifi is not working. So can you tell me exact problem as a OneUI based kernel is booting AOSP while when I use morokernel no AOSP based rom boots
Click to expand...
Click to collapse
Flashing stock rom will restore stock kernal. Firmware must be correct for device and region.
Bootloop after Odin Flash.
1. After flash boot into stock recovery
2. How to>>> In this sequence hold volume down+home+power. As soon as phone goes off move finger to volume up while still holding home and power. It may take several attempts as you have to time it just right when the screen goes black.
3. Once in stock recovery choose wipe data/ factory reset. Then choose reboot device
4. Can take 5-10 minutes on first boot. Updating and erasing screens are normal during this process as well as rebooting. Just leave it finish.
If this does not work Reflash stock with Odin but this time uncheck "auto reboot" in Odin options before you start.
Once Flash finish, disconnect from pc and follow 1-4 as above.
Kernel Problem
Pls help as I figured out that all the kernels after v3.18.140.5 are not booting on my phone. Can someone help me with this.
Model No: SM-G930FD
Device: Galaxy S7 Flat
BL: 8 (Latest)
File System: ext4
I have already restored stock many times and formatted my device many times. I used firmware from samfw to go to stock.
That is why no Aosp was booting on my phone
Pls Help
Related
Phone started boot looping on stock firmware late last year. My wife bought another phone and I haven't been able to get to it till now. Warrantee void due to tiny crack. Wipe cache and factory reset did not work.
I tried loading stock rom upgrade to 5.1.1 using Odin3 This was successful. Still boot loop. Shows Samsung Galaxy S6... turns black for a second then shows Samsung Galaxy S6... in a loop. I guess it is a hardware issue? Anything else I can try?
Of note.. everytime I boot into recovery it says "installing system update..." Then. "no command". Then it goes into recovery.
-Mike
Try this:
1. Boot to recovery.
2. Do a factory reset.
3. Reboot to Download mode from recovery mode.
4. Reflash newest stock rom.
5. Let it auto reboot and see if it still boot loops.
Or try this:
After step 3 reflash stock rom with pit file.
If that doesn't work then I have no idea.
You can also try flashing TWRP and wiping everything (system,data,internal,cache,art) and then flashing a new rom.
Oh and my friend two days ago dropped her phone on the concrete, and her phone started boot looping. She couldn't even get to recovery or anything. She dropped her phone again (her idea, don't try this). And it booted to android without any problems!
Seems like something was shorting the motherboard (?).
Good Luck.
I did as you said above twice already. (without pit) I will try TWRP next. Would flashing a new kernel be helpful?
-Mike
TWRP keeps failing with ODIN. Will it not work with 5.1.1? Or am I missing something. I'm using the AP button, is that right?
Thanks!
what was the stock firmware you flashing, 5.1.1 or have you flashed 6.0.1 already ?
JohnnyGT said:
what was the stock firmware you flashing, 5.1.1 or have you flashed 6.0.1 already ?
Click to expand...
Click to collapse
st.ock did not try 6.0.1
berrmich said:
st.ock did not try 6.0.1
Click to expand...
Click to collapse
i saved my phone by going to 6.0.1 so up to u if you want to try
JohnnyGT said:
i saved my phone by going to 6.0.1 so up to u if you want to try
Click to expand...
Click to collapse
I'm really in the wrong section. I have an ATT phone. There is no 6.0.1 yet for those. I think my phone is not recoverable.
-Mike
I keep getting crashes when trying to flash zips in TWRP. the phone reboots as soon as i start to flash any rom or even the magisk zip. Using the boost version of the J7 perx. latest twrp 3.2.1 any help would be greatly appreciated.
J727P
IsaiahWade said:
I keep getting crashes when trying to flash zips in TWRP. the phone reboots as soon as i start to flash any rom or even the magisk zip. Using the boost version of the J7 perx. latest twrp 3.2.1 any help would be greatly appreciated.
Click to expand...
Click to collapse
OK it's time for you to flash stock firmware threw Odin 3.12.5 an start over !
when you install twrp you have to factory reset first then flash twrp in download mod an boot right into recovery an flash superSU zip or magisk !
peter couniaz said:
OK it's time for you to flash stock firmware threw Odin 3.12.5 an start over !
when you install twrp you have to factory reset first then flash twrp in download mod an boot right into recovery an flash superSU zip or magisk !
Click to expand...
Click to collapse
Okay thanks for the reply!
I realized i was using an old version of odin.. maybe thats why it wasnt completely flashing the firmware before.. it would get to almost a full bar and fail. then i would have to flash BL or twrp to get it to boot again.. got the latest odin and it flashed fully this time.
still waiting on my phone to boot up though idk if its stuck on bootloop or not..
Edit *looks like im stuck in bootloop now* ill try formatting and flashing again
Edit #2: I booted into default recovery and wiped data & cache and the phone booted up just fine we'll see how this goes *fingers crossed* lol
IsaiahWade said:
Okay thanks for the reply!
I realized i was using an old version of odin.. maybe thats why it wasnt completely flashing the firmware before.. it would get to almost a full bar and fail. then i would have to flash BL or twrp to get it to boot again.. got the latest odin and it flashed fully this time.
still waiting on my phone to boot up though idk if its stuck on bootloop or not..
Edit *looks like im stuck in bootloop now* ill try formatting and flashing again
Edit #2: I booted into default recovery and wiped data & cache and the phone booted up just fine we'll see how this goes *fingers crossed* lol
Click to expand...
Click to collapse
Tried it still not working.. i even factory reset before flashing twrp. it still reboots immediately when trying to flash anything
Step 2
I presume you're flashing from an SD card. Please backup its data and format it.
Then re-download one of the zips and test flash in TWRP.
dodo2244 said:
Step 2
I presume you're flashing from an SD card. Please backup its data and format it.
Then re-download one of the zips and test flash in TWRP.
Click to expand...
Click to collapse
Correct. Thanks ill try that.
is it normal that my carrier switches to sprint when i flash the stock rom? when i flash CSC it switches back to boost
IsaiahWade said:
Correct. Thanks ill try that.
is it normal that my carrier switches to sprint when i flash the stock rom? when i flash CSC it switches back to boost
Click to expand...
Click to collapse
The memory card thing worked! i forgot i had formatted it as adoptable storage before.
after formatting it actually let me flash the zip this time
only thing is i got an error right at the very end
Unable to repack boot image!
-unmounting partitions
Updater process ended with ERROR: 1
Error installing zip file '/sdcard/Magisk-v16.0.zip
updating partition details
. . . done
J727P
IsaiahWade said:
Tried it still not working.. i even factory reset before flashing twrp. it still reboots immediately when trying to flash anything
Click to expand...
Click to collapse
Ok do the firmware thing then factory reset in the stock recovery ! Then flash twrp in Odin with auto reboot unchecked in options ! Then pull an replace battery ! Then boot right into twrp an flash superSU SR5 2.8.2 zip an reboot ! Or you can boot twrp an Rom instead !
Glad to be of help. Peter's tricks should solve your final hurdles.
Sent from my SM-J700F using Tapatalk
Today I tried to finally update to the latest version of crDroid, but ended up having a bunch of issues doing so, and after a lot of troubleshooting and trying to fix it, I ended up putting it into a bootloop of some sort instead.
I'm pretty sure the last thing I tried was installing a different version of TWRP to see if that version would let me properly install the rom, and stop my phone from always rebooting into recovery mode.
Trying to turn it on normally or boot into TWRP leaves it hanging on the "Redmi" boot screen, it can boot into fastboot mode though.
I'm guessing that the only way to recover my phone at this point is to flash the Official MIUI rom back onto the phone, but that also involves wiping Data and losing pretty much everything I've put on the phone.
I was smart enough to make a TWRP of the Data folder, but while making the backup, the console said it doesn't include all personal files or something.
How much of my personal data and files can I rescue from the phone in this state, and how can I do that before it gets wiped when fixing it?
Also, I think I really need some help in actually restoring my phone and flashing the custom rom properly.
No matter how much effort I put into figuring out how to do this stuff, unexpected issues always seem to happen, and turns something that initially seemed so simple into multiple hours of troubleshooting.
The only way I think i've gotten rom flashing to work at all was by wiping everything and installing the official MIUI rom, but I don't want to be losing my data every month when an update comes out.
So, could someone please help me get my phone working again?
Edit: I ended up fixing my own issue by ADB flashing on a different release of TWRP, and then installing fcrypt disabler after the rom but before everything else.
Sanarise said:
Today I tried to finally update to the latest version of crDroid, but ended up having a bunch of issues doing so, and after a lot of troubleshooting and trying to fix it, I ended up putting it into a bootloop of some sort instead.
I'm pretty sure the last thing I tried was installing a different version of TWRP to see if that version would let me properly install the rom, and stop my phone from always rebooting into recovery mode.
Trying to turn it on normally or boot into TWRP leaves it hanging on the "Redmi" boot screen, it can boot into fastboot mode though.
I'm guessing that the only way to recover my phone at this point is to flash the Official MIUI rom back onto the phone, but that also involves wiping Data and losing pretty much everything I've put on the phone.
I was smart enough to make a TWRP of the Data folder, but while making the backup, the console said it doesn't include all personal files or something.
How much of my personal data and files can I rescue from the phone in this state, and how can I do that before it gets wiped when fixing it?
Also, I think I really need some help in actually restoring my phone and flashing the custom rom properly.
No matter how much effort I put into figuring out how to do this stuff, unexpected issues always seem to happen, and turns something that initially seemed so simple into multiple hours of troubleshooting.
The only way I think i've gotten rom flashing to work at all was by wiping everything and installing the official MIUI rom, but I don't want to be losing my data every month when an update comes out.
So, could someone please help me get my phone working again?
Click to expand...
Click to collapse
can u boot into twrp?
if u can boot, while in twrp, connect your phone via usb cable to pc. u can copy everything on pc
Simoom Sadik said:
can u boot into twrp?
if u can boot, while in twrp, connect your phone via usb cable to pc. u can copy everything on pc
Click to expand...
Click to collapse
Unfortunately, I can't.
Trying to boot into TWRP just gets stuck on the 'Redmi' boot logo.
I just remembered that you can install TWRP over ADB, and that Peter's one says it works even when the system partition is empty, so maybe the issue is the TWRP I installed and could possibly undo this part of the issue over ADB.
It won't fix the issue preventing my from updating my rom, but recovery only is still better than a soft brick.
Edit: That worked, i've put Peter's TWRP back on, and it's launching into recovery mode/TWRP again now
twrp not boot after successfully flash in this rom
Sanarise said:
Unfortunately, I can't.
Trying to boot into TWRP just gets stuck on the 'Redmi' boot logo.
I just remembered that you can install TWRP over ADB, and that Peter's one says it works even when the system partition is empty, so maybe the issue is the TWRP I installed and could possibly undo this part of the issue over ADB.
It won't fix the issue preventing my from updating my rom, but recovery only is still better than a soft brick.
Edit: That worked, i've put Peter's TWRP back on, and it's launching into recovery mode/TWRP again now
Click to expand...
Click to collapse
flash latest twrp download from github, install twrpbuilder img twrp ,it boot fine and you will copy your data to pc and then install any other twrp img which u want , dont wipe anything from phone before phone boot.flash only original twrp builder 3.2.3.1 official,it boot only on latest updates.
Why nobody use orangefox?
is your issue solve or not tell,
Simoom Sadik said:
can u boot into twrp?
if u can boot, while in twrp, connect your phone via usb cable to pc. u can copy everything on pc
Click to expand...
Click to collapse
if your problem is not solve then tell me you need to flash a fastboot rom first with save user data.bat file and when it installed then you can install twrp builder 3.2.1. and then boot to twrp this methods working fine,if you recently flashed any android 10 rom then first you need to flash a miui fastboot rom,or flash it via command mode direct only 3 files
first click on extract a fastboot rom and copy boot system and vender file with flash.all bat file and make a new folder then click on flash.bat save user data file to flash these images
or you can do this manually
fastboot flash system system.img
fastboot flash vender vender.img
fastboot flash boot boot.img
then reboot device to fastboot again
now flash latest official twrp builder 3.2.3.1 img twrp and take all your data backup,
in fastboot flash latest miui do not downgrade direct otherwise you lost your data,
after this if you sucess then you can flash your old rom which is running before issue of boot loop of redmi logo
it will deincrypt your data safely and then root device and boot normally, if you lost anything then contact me with mail or whatsapp i will help you,7009197673 india
and this twrp work on all version from chines to global beta stable and indian stable
joke19 said:
Why nobody use orangefox?
Click to expand...
Click to collapse
In the end, I did try orangefox, and it might have been part of why it worked.
However, the crDroid installation instructions specifically mentions using Peter's TWRP, so I initially used that one.
anmoltinder said:
if your problem is not solve then tell me you need to flash a fastboot rom first with save user data.bat file and when it installed then you can install twrp builder 3.2.1. and then boot to twrp this methods working fine,if you recently flashed any android 10 rom then first you need to flash a miui fastboot rom,or flash it via command mode direct only 3 files
Click to expand...
Click to collapse
Thank you for the effort you put into typing up a guide to help me, but I ended up fixing my own problem.
I was able to use fastboot to flash on a better TWRP release, and then get the rom to install properly by installing fcrypt-disabler just after it.
Sanarise said:
Today I tried to finally update to the latest version of crDroid, but ended up having a bunch of issues doing so, and after a lot of troubleshooting and trying to fix it, I ended up putting it into a bootloop of some sort instead.
I'm pretty sure the last thing I tried was installing a different version of TWRP to see if that version would let me properly install the rom, and stop my phone from always rebooting into recovery mode.
Trying to turn it on normally or boot into TWRP leaves it hanging on the "Redmi" boot screen, it can boot into fastboot mode though.
I'm guessing that the only way to recover my phone at this point is to flash the Official MIUI rom back onto the phone, but that also involves wiping Data and losing pretty much everything I've put on the phone.
I was smart enough to make a TWRP of the Data folder, but while making the backup, the console said it doesn't include all personal files or something.
How much of my personal data and files can I rescue from the phone in this state, and how can I do that before it gets wiped when fixing it?
Also, I think I really need some help in actually restoring my phone and flashing the custom rom properly.
No matter how much effort I put into figuring out how to do this stuff, unexpected issues always seem to happen, and turns something that initially seemed so simple into multiple hours of troubleshooting.
The only way I think i've gotten rom flashing to work at all was by wiping everything and installing the official MIUI rom, but I don't want to be losing my data every month when an update comes out.
So, could someone please help me get my phone working again?
Edit: I ended up fixing my own issue by ADB flashing on a different release of TWRP, and then installing fcrypt disabler after the rom but before everything else.
Click to expand...
Click to collapse
help.I woke up yesterday and I turned on my phone and it is stuck on the Mi logo.All i can do is get it to fastboot thing.It seems like you and I have the same problem and I would love to have some help from you
Fcsubxrhi said:
help.I woke up yesterday and I turned on my phone and it is stuck on the Mi logo.All i can do is get it to fastboot thing.It seems like you and I have the same problem and I would love to have some help from you
Click to expand...
Click to collapse
If you can access fastboot, then flash TWRP.... Enter recovery, wipe your system partitions and then flash the Stock MIUI ROM or use the MiFlash tool. Make sure you aren't flashing an older version of the ROM than the onle already installed.
CongestedHangman said:
can u boot into twrp?
if u can boot, while in twrp, connect your phone via usb cable to pc. u can copy everything on pc
Click to expand...
Click to collapse
I have the same problem that stated after installing the update for derpfest and I can boot into twrp. Any solution for me?
Hello, some days ago i found a Samsung Galaxy Ace Style (SM-G310HN/heatnfc3g) and i decided to mod it, i installed TWRP via Odin and all was ok, but when i tried to install CyanogenMod 12.1 it didn't work. Since it didn't work, i decided to flash stock ROM. It worked once, but now it doesn't work anymore. I suspect it's the PIT file, because when i reflashed stock ROM another time with a PIT file now it doesn't work anymore, let me try to explain:
When i try to flash anything (Stock ROM or recovery, custom or stock), it... doesn't, Odin says it flashed but when i reboot to recovery or reboot to stock, it stays at the Samsung logo or doesn't flash the recovery, even if it says that it flashed. What should i do? Is my phone bricked? How can i unbrick it if it's bricked?
Michy234 said:
Hello, some days ago i found a Samsung Galaxy Ace Style (SM-G310HN/heatnfc3g) and i decided to mod it, i installed TWRP via Odin and all was ok, but when i tried to install CyanogenMod 12.1 it didn't work. Since it didn't work, i decided to flash stock ROM. It worked once, but now it doesn't work anymore. I suspect it's the PIT file, because when i reflashed stock ROM another time with a PIT file now it doesn't work anymore, let me try to explain:
When i try to flash anything (Stock ROM or recovery, custom or stock), it... doesn't, Odin says it flashed but when i reboot to recovery or reboot to stock, it stays at the Samsung logo or doesn't flash the recovery, even if it says that it flashed. What should i do? Is my phone bricked? How can i unbrick it if it's bricked?
Click to expand...
Click to collapse
Have you tried booting into stock recovery and selecting the factory reset option and the wipe cache partition option? It is sometimes necessary after flashing via Odin, I've had to do it a few times to solve a bootloop.
Droidriven said:
Have you tried booting into stock recovery and selecting the factory reset option and the wipe cache partition option? It is sometimes necessary after flashing via Odin, I've had to do it a few times to solve a bootloop.
Click to expand...
Click to collapse
Well the problem is... i cant reboot into stock recovery. Its stuck in twrp, and it's not really a "bootloop", it stays stuck at the Samsung logo. I tried to wipe cache and dalvik on Twrp but nothing.
I cant even flash the stock recovery since as i said in the original post, if i try to flash EVERYTHING Odin says it flashed but on the phone nothing happened.
Michy234 said:
Well the problem is... i cant reboot into stock recovery. Its stuck in twrp, and it's not really a "bootloop", it stays stuck at the Samsung logo. I tried to wipe cache and dalvik on Twrp but nothing.
I cant even flash the stock recovery since as i said in the original post, if i try to flash EVERYTHING Odin says it flashed but on the phone nothing happened.
Click to expand...
Click to collapse
Could please someone help me?
Michy234 said:
Could please someone help me?
Click to expand...
Click to collapse
I revive this post even if its pretty old. Could someone please help?
resolved​
I was trying to flash a gsi but when I boot into twrp it just goes back to the booting screen again when I press anything, I tried reformatting in wipe before it went back to booting but after that it's even worse. I went into odin and reflashed twrp but same thing. I flashed its firmware from samfx but one ui doesn't even want to boot, it just shows an endless charging logo. The only thing I can boot to currently is the default recovery and download mode. I really need help quick because I need to do some work on my phone.
iintc said:
I was trying to flash a gsi but when I boot into twrp it just goes back to the booting screen again when I press anything, I tried reformatting in wipe before it went back to booting but after that it's even worse. I went into odin and reflashed twrp but same thing. I flashed its firmware from samfx but one ui doesn't even want to boot, it just shows an endless charging logo. The only thing I can boot to currently is the default recovery and download mode. I really need help quick because I need to do some work on my phone.
Click to expand...
Click to collapse
When you install a GSI, the only partitions you should be messing with are /system and /data.
Did you mess with anything else?
Use Odin to perform a clean flash of the firmware, including a data wipe.
V0latyle said:
When you install a GSI, the only partitions you should be messing with are /system and /data.
Did you mess with anything else?
Use Odin to perform a clean flash of the firmware, including a data wipe.
Click to expand...
Click to collapse
No I don't think I messed with anything else. Also flashing stock firmware again works somehow even though I already tried flashing it before, anyhow, I greatly appreciate your help
PS still not sure what caused twrp to bootloop