Database Info

Looping at boot screen, due to the last firmware update?

Hi folks, it seems that I may use some help right now. Searched around, but so far no luck is found. My rooted TF700 runs with the latest firmware and not unlocked (stock). Today she went nowhere but showing the ASUS logo and circling dots.
First, as usual, I tried to have a cold boot. Still, she didn't go further. Then I decided to wait patiently, and I think one hour is a reason to try helping her out of there. Next step, as some of you may already had in mind: RCK. Picked it up, the green robot showed up, but only few seconds before it went to sleep accompanied by that... yes, that red triangle.
Not so long afterwards, I downloaded the firmware ZIP file from ASUS's website. Extracted it once, renamed it the "usual" way, put the file at a MicroSD root and got the TF700 installing it. Installation was complete, the robot wasn't shown sleeping, and then it rebooted. At this moment I took the MicroSD from the slot so it doesn't interrupt the process.
But then what? Still the same old eight dots making the runabout form under ASUS logo. Tried cold boot once again, no luck. Then, I borrowed my children's A100 to type this help request.
I have no idea what to do. Still have the warranty valid but I want to try another thing before sending it out. It might be due to the new firmware (25 I think, I'm not memorizing firmware numbers) but it seems that I'm the only one suffering it so far. The last thing I remembered was the TF700 went sudden reboot when I click the bluetooth icon to activate it, while I'm trying to connect to a portable speaker.
I never flash any custom ROMs, it has been always the stock. Random reboots, yes, I think I'm not the only one. But now I'm getting suspicious since this happens one day after the last firmware update. The looping at boot screen.
In case anyone has suggestions or thoughts, please kindly share that here. Thanks in advance.
Sent from my A100 using XDA Premium HD app

Maybe your data partition is corrupted. Did you try "wipe data" in the bootloader menu?

_that said:
Maybe your data partition is corrupted. Did you try "wipe data" in the bootloader menu?
Click to expand...
Click to collapse
Hi, thanks. Doesn't install a fresh firmware do further? I mean, it also removes the data, right? Or am I wrong here?
Sent from my A100 using XDA Premium HD app

suroboyo said:
Hi, thanks. Doesn't install a fresh firmware do further? I mean, it also removes the data, right? Or am I wrong here?
Click to expand...
Click to collapse
"Wipe data" deletes your data, right. I never did it myself, so I can't say what exactly will be deleted. Installing a firmware only replaces the firmware, not your data.
Alternatively you can try if you can connect via adb shell while the boot screen dots are spinning.

_that said:
"Wipe data" deletes your data, right. I never did it myself, so I can't say what exactly will be deleted. Installing a firmware only replaces the firmware, not your data.
Alternatively you can try if you can connect via adb shell while the boot screen dots are spinning.
Click to expand...
Click to collapse
Wipe data is factory reset. If you reset your device from setting-> factory reset, it will boot into "wipe data" mode and wipe all your apps, bring everything back to factory default. At this point if you don't have a backup, I see you only have one option which is wipe data.

OK guys, thanks a lot. If you read my footer now, you know I already have access to my TF700.
I did it as you suggested, chose "Wipe Data" after several times failing with firmware recovery. Losing data in SD is not a very big deal since I always keep my "real data" in an external MicroSD, anticipating such things exactly like I just "suffered". I also backed up my most of apps and their data to the MicroSD using Titanium Backup, so it's very close to the previous state... only snappier.
So I wiped the data and got into the stock of everything, without root. Then I rolled back to ICS firmware (30), rooted it using Debugfs, installed OTA Rootkeeper, protected a copy of the root access, updated the firmware, restored root, installed TB, restore all apps and data. Then it's the matter of replacing some widgets and little "here-and-there" settings. No more than two hours overall, could be way less if the number of apps are smaller.
What was really missing is just a few downloads and some "not really important" winter photos. Movies and maps kept in the internal storage, well, I have the backup. I wouldn't say this was caused by the new firmware, but somehow I feel like I should have a suspicion at it.
Thanks again!
Sent from my ASUS Transformer Pad TF700T using XDA Premium HD app

[Q] Need Help!...Hope this isn't a brick...

I finally got the tf700t rooted/unlocked and thought everything was working well. I downloaded a ROM from GooManager and started to see what difference it would make on the tablet. For a few hours it seemed to be working fine. Then I noticed the screen was black and would not come back on. I then did a cold boot and that's when the tablet started power cycling. Please tell me this can be fixed. When I tried to restore the TWRP backup file it said "Restore Failed", and went back to power cycling/resetting. Have I bricked it?

mrchocklit said:
I finally got the tf700t rooted/unlocked and thought everything was working well. I downloaded a ROM from GooManager and started to see what difference it would make on the tablet. For a few hours it seemed to be working fine. Then I noticed the screen was black and would not come back on. I then did a cold boot and that's when the tablet started power cycling. Please tell me this can be fixed. When I tried to restore the TWRP backup file it said "Restore Failed", and went back to power cycling/resetting. Have I bricked it?
Click to expand...
Click to collapse
It is more likely that you have a bootloop.. As long as your bootloader is working, you can do a lot of things that can bring your tablet back..

Also sounds like /data is corrupted.
Choose the wipe button in twrp and then format data.
Be warned you will lose everything on the tab but it will get you booting again.
Which kernel combination did you flash on CROMi-X 5?

sbdags said:
Also sounds like /data is corrupted.
Choose the wipe button in twrp and then format data.
Be warned you will lose everything on the tab but it will get you booting again.
Which kernel combination did you flash on CROMi-X 5?
Click to expand...
Click to collapse
I didn't use CROMi-X. I downloaded a ROM from GooManager. How can I get CROMi-X and should I no longer use GooManager? I took your advice however and everything worked out well- thanks for that. I was still rooted and unlocked but I'd like to know exactly what I need to do in order to enjoy the tablet without 'messing' it up again.

mrchocklit said:
I didn't use CROMi-X. I downloaded a ROM from GooManager. How can I get CROMi-X and should I no longer use GooManager? I took your advice however and everything worked out well- thanks for that. I was still rooted and unlocked but I'd like to know exactly what I need to do in order to enjoy the tablet without 'messing' it up again.
Click to expand...
Click to collapse
Just follow the instructions in the CROMi-X first post
I don't know how other ROMs set themselves up.

[Q] after installing 4.4.1 - no cellular + data - SOLVED

SOLVED! see solution in the first comment.
I really need some help...
I installed manually 4.4.1 version using this guide: http://forum.xda-developers.com/showthread.php?t=2523217
(I am having a rooted device with TWRP without any modifications or deletions - used section B)
after the install successfully worked, i chosed to wipe. it was stuck and i used the powerbutton to reload device.
when the device turned on it used emulated storage which means no imei and no efs.
using the twrp (in recovery mode) i can see my full data and efs files.
when i am trying to rewipeqinstall update i get this error: "E:/Unable to mount /cache"
please help me.

hbhc123 said:
I really need some help...
I installed manually 4.4.1 version using this guide: http://forum.xda-developers.com/showthread.php?t=2523217
(I am having a rooted device with TWRP without any modifications or deletions - used section B)
after the install successfully worked, i chosed to wipe. it was stuck and i used the powerbutton to reload device.
when the device turned on it used emulated storage which means no imei and no efs.
using the twrp (in recovery mode) i can see my full data and efs files.
when i am trying to rewipeqinstall update i get this error: "E:/Unable to mount /cache"
please help me.
Click to expand...
Click to collapse
Do not turn the device off while clearing the cache.
Reboot to recovery, go to TWRP settings and enable rm -rf option, go back and wipe the cache/dalvik. If THAT doesn't work, you will need to flash the cache.img from the factory image found here http://forum.xda-developers.com/showthread.php?t=2513701
After you do that, make sure you have the latest version of TWRP installed (2.6.3.4) If you don't you can also choose to install that via ADB before clearing the cache.

Synyster06Gates said:
Do not turn the device off while clearing the cache.
Reboot to recovery, go to TWRP settings and enable rm -rf option, go back and wipe the cache/dalvik. If THAT doesn't work, you will need to flash the cache.img from the factory image found here http://forum.xda-developers.com/showthread.php?t=2513701
After you do that, make sure you have the latest version of TWRP installed (2.6.3.4) If you don't you can also choose to install that via ADB before clearing the cache.
Click to expand...
Click to collapse
First of all - thanks for help.
already tried the rm -rf option unsuccessful.
2 question before I'm starting the flash process:
1. Is there a way dumping the efs folder to my computer before?
2. is this the command i should use: "fastboot flash cache C:/image-hammerhead-krt16m/cache.img"?
thanks a lot.

hbhc123 said:
First of all - thanks for help.
already tried the rm -rf option unsuccessful.
2 question before I'm starting the flash process:
1. Is there a way dumping the efs folder to my computer before?
2. is this the command i should use: "fastboot flash cache C:/image-hammerhead-krt16m/cache.img"?
thanks a lot.
Click to expand...
Click to collapse
1. Use TWRP to back up your EFS data if you would like. You won't lose any data by just flashing the cache though. All your apps and everything should still be there.
2. If you installed the drivers correctly and that is the correct directory for the file on your computer, that is right! I put mine on the desktop for simplicity.

clearing cache/dalvik is very slow on N5, I found, and so is resetting the phone in recovery. though the progress bar may not move the process isn't stuck, it's still going on in background.

chi_heng said:
clearing cache/dalvik is very slow on N5, I found, and so is resetting the phone in recovery. though the progress bar may not move the process isn't stuck, it's still going on in background.
Click to expand...
Click to collapse
Flash the newest version of TWRP. The issue is fixed.

Synyster06Gates said:
1. Use TWRP to back up your EFS data if you would like. You won't lose any data by just flashing the cache though. All your apps and everything should still be there.
2. If you installed the drivers correctly and that is the correct directory for the file on your computer, that is right! I put mine on the desktop for simplicity.
Click to expand...
Click to collapse
I have done what you said and it worked perfectly
many thanks!

hbhc123 said:
I have done what you said and it worked perfectly
many thanks!
Click to expand...
Click to collapse
No problem! Glad you got it taken care of.

What should one do if fastboot flash cache doesnt fix it? im having same issue and i have tried restoring stock, flashing cache, etc. still no imei showing in settings and sim doesnt get reconized. Hangouts fc, google search fc and i cant access sd card in windows or the phone.

any one else
benbailey84 said:
What should one do if fastboot flash cache doesnt fix it? im having same issue and i have tried restoring stock, flashing cache, etc. still no imei showing in settings and sim doesnt get reconized. Hangouts fc, google search fc and i cant access sd card in windows or the phone.
Click to expand...
Click to collapse
I guess me and you are screwed I tried every suggestion on the forums but nothing works I'm just gonna RMA mine and pray that Google doesn't say its my fault I wish someone could help us I gotta send mine off as fast as possible im already looking at two weeks minimum for the RMA so every day I wait is just more time I won't have a phone thanks

ddloco said:
I guess me and you are screwed I tried every suggestion on the forums but nothing works I'm just gonna RMA mine and pray that Google doesn't say its my fault I wish someone could help us I gotta send mine off as fast as possible im already looking at two weeks minimum for the RMA so every day I wait is just more time I won't have a phone thanks
Click to expand...
Click to collapse
yeah i have a rma out for mine. Luckly i have a spare phone (its a damn $15 go phone) but mine is already shipped. biggest issue is the $440 is tied up in my account until they get the bad phone back. basically i would suggest to anyone that if they are going to flash a rom first thing they should do is back up their efs to their pc and also some sort of could (dropbox, drive, mega, box, etc).

benbailey84 said:
yeah i have a rma out for mine. Luckly i have a spare phone (its a damn $15 go phone) but mine is already shipped. biggest issue is the $440 is tied up in my account until they get the bad phone back. basically i would suggest to anyone that if they are going to flash a rom first thing they should do is back up their efs to their pc and also some sort of could (dropbox, drive, mega, box, etc).
Click to expand...
Click to collapse
Well in our case I have my efs on my PC from weeks ago restoring it doesn't fix whatever the ROM changed lol

Need Help

I had just downloaded the latest firmware to upgrade to lolipop, I did a titanium backup, then a nandroid with TWRP.
Upon reboot I can only get to the default recover screen (The one with the android on the skateboard). I can boot into TWRP and have tried clearing cache and delvik cache, and now doing a factory reset but I'm still having the problem. sometimes when rebooting from TWRP the phone boots to the lock screen (or to setup screen after factory reset), then a few seconds later reboots back to the screen with the android on the skateboard.
I haven't even started installing the new firmware, all I did was backup with TWRP and it seems to have semi bricked the phone.
I also tried restoring the backup and I get an error "E:\ No Partition selected for restore."

Justintoxicated said:
I had just downloaded the latest firmware to upgrade to lolipop, I did a titanium backup, then a nandroid with TWRP.
Upon reboot I can only get to the default recover screen (The one with the android on the skateboard). I can boot into TWRP and have tried clearing cache and delvik cache, and now doing a factory reset but I'm still having the problem. sometimes when rebooting from TWRP the phone boots to the lock screen (or to setup screen after factory reset), then a few seconds later reboots back to the screen with the android on the skateboard.
I haven't even started installing the new firmware, all I did was backup with TWRP and it seems to have semi bricked the phone.
I also tried restoring the backup and I get an error "E:\ No Partition selected for restore."
Click to expand...
Click to collapse
You flashed twrp either by twrp manager or allowed flashify to download the image for you. Try flashing the firmware zip I posted in tigerstowns thread that has twrp in it. If that doesn't work you will need to ruu and then install twrp and restore. Do not use twrp manager.

dottat said:
You flashed twrp either by twrp manager or allowed flashify to download the image for you. Try flashing the firmware zip I posted in tigerstowns thread that has twrp in it. If that doesn't work you will need to ruu and then install twrp and restore. Do not use twrp manager.
Click to expand...
Click to collapse
I beleive I flashed twrp origionally from fastboot, that was months ago though when we got the 4.4.4 update.
Do you mean I need to flash that zip from fastboot?
I'm worried about trying to flash firmware with the phone in a strange state. I'm almost thinking that something went bad inside the phone, but not convinced yet. It has been doing strange things lately, constant searching for location, pausing itself durring playback of music, and some random restarts. I haven't been messing it it so it seems strange to all of a sudden have these issues after many months.

Justintoxicated said:
I beleive I flashed twrp origionally from fastboot, that was months ago though when we got the 4.4.4 update.
Do you mean I need to flash that zip from fastboot?
I'm worried about trying to flash firmware with the phone in a strange state. I'm almost thinking that something went bad inside the phone, but not convinced yet. It has been doing strange things lately, constant searching for location, pausing itself durring playback of music, and some random restarts. I haven't been messing it it so it seems strange to all of a sudden have these issues after many months.
Click to expand...
Click to collapse
Nah man. Just reflash the firmware zip that contains twrp and report back. The older twrp are not safe to use on the newer firmware. I have a pda thread stickied in the general section that explains. Phone is likely fine.

dottat said:
Nah man. Just reflash the firmware zip that contains twrp and report back. The older twrp are not safe to use on the newer firmware. I have a pda thread stickied in the general section that explains. Phone is likely fine.
Click to expand...
Click to collapse
Ok, yea, I flashed the new firmware (with twrp) using fastboot , I'm still stuck on the same screen though. I did not install lolipop because I need to get the phone to USB mode to copy it over, which I cannot do because it will not start up.

Justintoxicated said:
Ok, yea, I flashed the new firmware (with twrp) using fastboot , I'm still stuck on the same screen though.
Click to expand...
Click to collapse
Ok...so follow me...if you flashed what you thought was cache on the new firmware but using an older twrp you wiped system instead.
Do you have your stuff backed up?

dottat said:
Ok...so follow me...if you flashed what you thought was cache on the new firmware but using an older twrp you wiped system instead.
Do you have your stuff backed up?
Click to expand...
Click to collapse
I don't know, I made a nandroid to my external memory card and immediately after that I was no longer able to start up... I tried to restore the nandroid and I cannot. So I would say no I am probably not backed up. I do still have RDKN rom on the memory card for 4.4.3, should I try to re-install that?
TWRP is now version 2.8.5.0, so apparently it updated correctly (I think before it was 2.8.1)

Justintoxicated said:
I don't know, I made a nandroid to my external memory card and immediately after that I was no longer able to start up... I tried to restore the nandroid and I cannot. So I would say no I am probably not backed up. I do still have RDKN rom on the memory card for 4.4.3, should I try to re-install that?
Click to expand...
Click to collapse
No. Your best bet to get your stuff back would be to downgrade firmware back to 4.4.4 and reflash the latest twrp img only and then restore your nand.

dottat said:
No. Your best bet to get your stuff back would be to downgrade firmware back to 4.4.4 and reflash the latest twrp img only and then restore your nand.
Click to expand...
Click to collapse
Ok my internet is not working on my laptop at work (only of the PC I'm on and no way to transfer files without my phone), so I guess I will try to do this when I get home. At this point I don't even care about my data, I wanted to save my text conversations but other than that everything I need should be saved in my titanium backup.

Justintoxicated said:
Ok my internet is not working on my laptop at work, so I guess I will try to do this when I get home. At this point I don't even care about my data, I wanted to save my text conversations but other than that everything I need should be saved in my titanium backup.
Click to expand...
Click to collapse
And that's what I figured. So flash 4.4.4. Flash latest twrp. Restore nand from ext sd. Boot up. Install this app.
https://www.androidfilehost.com/?fid=95916177934537937
Run it and link to your Google account and make it perform a backup.
It will do your apps/email accounts/texts/even home screen layout. And it will do it once a day for you automatically or on demand whenever.
Once you get a good backup on this app you can simply flash the new ruu and use this app to restore.

dottat said:
And that's what I figured. So flash 4.4.4. Flash latest twrp. Restore nand from ext sd. Boot up. Install this app.
https://www.androidfilehost.com/?fid=95916177934537937
Run it and link to your Google account and make it perform a backup.
It will do your apps/email accounts/texts/even home screen layout. And it will do it once a day for you automatically or on demand whenever.
Once you get a good backup on this app you can simply flash the new ruu and use this app to restore.
Click to expand...
Click to collapse
Update, restarted the computer and I was able to restore the old firmware. I re-installed the old rom afterwards (not my nandroid) and I am unable to get into the OS. Well technically I get prompted to select a language, after which the phone reboots back to the S-off androids with skateboards bootloader. Does this mean my phone is toast?

Hey guys, should I S-on the phone load the stock bootloader and try to return it? It is over a year old so I think I will need to use my insurance ($100). What is the best way to go about doing this?
Also when I get my replacement phone will there still be a way to S-off?
Thanks,
- Jusitn

The problem appears to be something wrong with my micro SD card! I removed the micro SD card and I can boot up fine. I guess I need to find another way to copy the rom to the micro SD install the rom then remove the micro SD card.
edit:
Oh this is worse than paying $100 for a new phone. It appears that creating a backup instead of creating a backup, actually corrupted my memory card. Now all the photos are backed up to the cloud but it will take me hours and hours to get all my apps back to the way they were. Some Security camera settings, Rifle target hand load development all gone. Audio book place holders, all notes taken etc. Nothing life or death but those security cameras will take me forever to figure out. I know I know, why not create a backup right? Well that's what I was trying to do!

So I was able to get back some data using some recovery software, unfortunately I was not able to retrieve the nandroid or the titanium backup files. Pictures were backed up to the could and music licenses and other hting I can add back on from the PC. Very time consuming though.
Anyways, what should I do now? Should I just reformat the SD card and continue to use it or should I assume that this happened because the card is bad and replace it with something else?

Justintoxicated said:
So I was able to get back some data using some recovery software, unfortunately I was not able to retrieve the nandroid or the titanium backup files. Pictures were backed up to the could and music licenses and other hting I can add back on from the PC. Very time consuming though.
Anyways, what should I do now? Should I just reformat the SD card and continue to use it or should I assume that this happened because the card is bad and replace it with something else?
Click to expand...
Click to collapse
I don't know what file system you're using but assuming it's one that windows can read, connect it to a PC and run chkdsk on it. If you don't know how to do that from a command prompt, right click on the drive in windows explorer and choose properties. Then tools and then click on the check now button under Error-checking. A small window will open. A line that says automatically fix file system errors will be checked by default. In your case, I'd suggest also checking the line that says "scan for and attempt recovery of bad sectors". It'll take a while for it to complete with that line checked so be patient. If you're lucky, it might just fix your problem. No promises but it's worth a try.
When it's done you can look in your event viewer to see what it found, if anything. If it finds bad sectors, I wouldn't trust the card. It can be used but there's no guarantee that more problems won't pop up. Maybe, maybe not.
To get to your event viewer, in Win 7 (not sure about Windows 8) click start and in the search box type event.vwr. I'm not sure what category you have to look under in there but perhaps under Winlogon. That's where you'll find it if it requires a reboot to check the card but that's not likely so I'm not sure.

robocuff said:
I don't know what file system you're using but assuming it's one that windows can read, connect it to a PC and run chkdsk on it. If you don't know how to do that from a command prompt, right click on the drive in windows explorer and choose properties. Then tools and then click on the check now button under Error-checking. A small window will open. A line that says automatically fix file system errors will be checked by default. In your case, I'd suggest also checking the line that says "scan for and attempt recovery of bad sectors". It'll take a while for it to complete with that line checked so be patient. If you're lucky, it might just fix your problem. No promises but it's worth a try.
When it's done you can look in your event viewer to see what it found, if anything. If it finds bad sectors, I wouldn't trust the card. It can be used but there's no guarantee that more problems won't pop up. Maybe, maybe not.
To get to your event viewer, in Win 7 (not sure about Windows 8) click start and in the search box type event.vwr. I'm not sure what category you have to look under in there but perhaps under Winlogon. That's where you'll find it if it requires a reboot to check the card but that's not likely so I'm not sure.
Click to expand...
Click to collapse
exFat for the card, and yes I am on windows 7. I tried to run a check as it was detected as having problems when I plugged the card into my laptop. Then it said I needed to dismount the drive and I said ok. Then it would just hang up. I reformatted the card and then ran the checkdisk again and it tells me that there are no problems now. I guess the card is ok and the issue was caused by TWRP? Not very cool when creating a back delete all your titanium backups and your nandroid that you were trying to create. Unfortunately I have to start from scratch on everything now. I even tried restoring to an older nandroid from May that was saved on my computer but that failed as well. for different reasons.

Justintoxicated said:
exFat for the card, and yes I am on windows 7. I tried to run a check as it was detected as having problems when I plugged the card into my laptop. Then it said I needed to dismount the drive and I said ok. Then it would just hang up. I reformatted the card and then ran the checkdisk again and it tells me that there are no problems now. I guess the card is ok and the issue was caused by TWRP? Not very cool when creating a back delete all your titanium backups and your nandroid that you were trying to create. Unfortunately I have to start from scratch on everything now. I even tried restoring to an older nandroid from May that was saved on my computer but that failed as well. for different reasons.
Click to expand...
Click to collapse
What reason did the restore fail for? And don't ever s-on unless you have let me have a crack at a phone. Not one thing you have said so far makes me think its phone. Unfortunately I have ended up with corrupt exfat discs before too. Sucks.

dottat said:
What reason did the restore fail for? And don't ever s-on unless you have let me have a crack at a phone. Not one thing you have said so far makes me think its phone. Unfortunately I have ended up with corrupt exfat discs before too. Sucks.
Click to expand...
Click to collapse
I don't remember, probably missing a file or something.

Need help on how to flash TWRP properly (Exynos) (SM-G930F)

Hi there. Recently (just yesterday) I tried flashing TWRP 3.1.0-0-herolte via Odin V3.12.3.0. However I ran into a little issue. Bootloop. TWRP seemed to work fine, but the phone wouldn't boot into android (stock touchwiz), exhibiting the 'samsung galaxy S7' logo periodically, but not going past that. Firstly I'll give some details on the phone and how I 'tried' to to flash TWRP. The phone I have is an Exynos variant SM-G930F running Android 7.0 and the recent update from late March. It is an Australian model (otherwise known as the 'international' version I think). Anyway as for what I was using as a guide, it was this. Before attempting this I enabled 'OEM unlocking' within the developer options but not 'USB debugging' (not sure if this contributed to the issue, but thought I'd mention it anyway). Later on I downloaded the Samsung Mobile Drivers and the tar file for TWRP. Installed the drivers, opened up Odin, entered download mode on the S7. I placed the tar file in AP and connected via micro usb. Almost everything, including auto-reboot, was turned off except F. Reset Time. Though chances are I probably left it on because I'm a doofus. After all that I pressed 'start' without doing any button combinations. Then after the screen went blank I pressed volume up + home hey + power button, roughly all at the same time. And then I entered TWRP. I then swiped to 'allow system modifications'. However as I didn't want to root the phone at the time, I decided to power it off through the menu. The next time I pushed the power button however, it was stuck in a bootloop. I then went back into TWRP and noticed that when I went into the install menu and was looking at the internal storage it appeared as 0mb (I thought that twrp had deleted all my files at the time), and I couldn't access the files I normally do like the downloads folder or app folders. However it seemed like most of the system folders were there like 'root' and 'data' etc. I then formatted the data and then did a factory reset as I thought it might fix the problem but it didn't. I swiped to install the twrp app but unchecked the two boxes. I then did some research and found out that if I ever were to run into an issue like this that I should flash the stock firmware, which is what I did. And viola! It worked again! I was slightly stressed at the time, lol. Luckily the apps and data I had previously were stored in the cloud.
After all this I have a question, what do you guys think I did wrong? Have you ran into this issue before? And what do you think may have caused the bootloop. I eventually want to start rooting my S7 and perhaps flash a rom, but I don't want to run into the issue again. Cheers!
P.S. I'm probably the biggest tech noob I know so go into a little bit of detail if you know what I did wrong so I don't make the same mistake again

Sounds like you hit the problem listed in step 9 & 10.
At this point, you will reach the screen asking you if you want to allow system modifications.
By swiping right, you will trigger dm-verity, and if you don't follow the next step you will be unable to boot
Click to expand...
Click to collapse
You swiped to allow system modifications, but you chose not to root and turned it off.
I don't see any mention of you flashing the dm-verity and force encryption disabler zip in TWRP which is required even if you're not rooting.

Beanvee7 said:
Sounds like you hit the problem listed in step 9 & 10.
You swiped to allow system modifications, but you chose not to root and turned it off.
I don't see any mention of you flashing the dm-verity and force encryption disabler zip in TWRP which is required even if you're not rooting.
Click to expand...
Click to collapse
Hm, that might actually be it. As a question how would be able to do that? Do I need to download that separately or something ( the dm-verity and encryption disabler zip I mean)?
EDIT
Actually never mind, it seems to say it right within the guide lol. So the problem should go away if I do that first yeah?

Yep just download it and put it on an SD card or transfer to the phones internal storage (I think TWRP lets you USB transfer) and go install zip in TWRP and select it.
That should stop your boot issues after installing TWRP, should even work even if you do it after a failed boot.

Beanvee7 said:
Yep just download it and put it on an SD card or transfer to the phones internal storage (I think TWRP lets you USB transfer) and go install zip in TWRP and select it.
That should stop your boot issues after installing TWRP, should even work even if you do it after a failed boot.
Click to expand...
Click to collapse
Hey bro, just wanted to say thanks. Got it rooted soon after as well. I found out I had to format data first before because it wouldn't let me install any zips. But after doing that it worked without any hiccups.
Cheers.

You should reset/wipe ur device after you have installed twrp through odin. That's a simple that some people wouldn't see in the tutorial. Then if you want root access you can flash SuperSu. Hope your problem will be solved. Good luck.

amalantony said:
You should reset/wipe ur device after you have installed twrp through odin. That's a simple that some people wouldn't see in the tutorial. Then if you want root access you can flash SuperSu. Hope your problem will be solved. Good luck.
Click to expand...
Click to collapse
Already did that before bro. Works as swell as a bell.

TheNickleS said:
Hey bro, just wanted to say thanks. Got it rooted soon after as well. I found out I had to format data first before because it wouldn't let me install any zips. But after doing that it worked without any hiccups.
Cheers.
Click to expand...
Click to collapse
Glad it's all working.
First time I installed TWRP I installed a ROM straight after which said to to format data, so never knew TWRP install alone needed the format data too.

Beanvee7 said:
Glad it's all working.
First time I installed TWRP I installed a ROM straight after which said to to format data, so never knew TWRP install alone needed the format data too.
Click to expand...
Click to collapse
From what I understand that's because the ldm-verity triggers. And so formating the data removes any encryption allowing for things to be flashed. But because I didn't do all of that first my S7 wouldn't boot up past flashing twrp.