Develop Bugs

[760] Fastboot mode started

Hello all. I was trying to root my LG G3 d855hkg and I did succeeded in that. But afterwards, when trying to install the TWRP I seem to have messed up with something, because when I try to boot up in recovery mode I only get this single line :
[760] Fastbood mode started
and that's it. I can see that other people have the same issue but non of the things that helped them works with me. Do you have any suggestions what could I do from this point on. My main goal is to install Lollipop 5.1 or a Cyanogenmod 12 (and to remove the current KitKat). Any help will be appreciated.

ste4o said:
Hello all. I was trying to root my LG G3 d855hkg and I did succeeded in that. But afterwards, when trying to install the TWRP I seem to have messed up with something, because when I try to boot up in recovery mode I only get this single line :
[760] Fastbood mode started
and that's it. I can see that other people have the same issue but non of the things that helped them works with me. Do you have any suggestions what could I do from this point on. My main goal is to install Lollipop 5.1 or a Cyanogenmod 12 (and to remove the current KitKat). Any help will be appreciated.
Click to expand...
Click to collapse
Does it still boot into
A) Download Mode or
B) Normal OS?

1 ) Yes
2) Yes
The phone is working just fine, I just cannot make it boot in recovery...

Deleted

ste4o said:
1 ) Yes
2) Yes
The phone is working just fine, I just cannot make it boot in recovery...
Click to expand...
Click to collapse
Reflash the KitKat firmware using LG Flash Tool and after that root and install TWRP using Flashify
Just keep in mind that when your flashing it use Normal Flash and NOT CSE

LG G4 boot loop into TWRP

Hello everyone,
yesterday I flashed a new Cyanogenmod 14 nightly (12062016) for my G4 from earlier nightly in TWRP. After reboot the phone keeps going back to TWRP and I can't seem to get it to boot to system..
I tried factory reset, reflashing back to old nightly, flashing stock.. but nothing seems to work.
Also tried doing this in the TWRP terminal:
dd[space]if=/dev/zero[space]of=/dev/block/platform/f9824900.sdhci/by-name/fota
Didn't fix the loop, I guess because it wasn't the OTA update that caused the problem in the first place.
If anyone has an idea, I would greatly appreciate the help!
Thanks.

If you can reach download mode you could try reflashing back to stock then starting again.....Hope you get yours fixed - Sorry to say this but mine did a very similar thing only 24 hours before you posted!!! Only mine was on stock FW and was in use at the time - I've now had to swap it as valuebasket who sold me the phone have ceased trading. If yours is a UK model you may be able to get it replaced under warranty - believe that LG guarantee their phones for 2 years and a ruling by the European court said that flashing a custom rom doesn't invalidate any warranties.

I have the same exact issue, I also flashed the latest CM14 nightly and cannot get the device to boot any rom.
I have even tried flashing stock rom but I get the same problem.
From what I have read, the bootloop issue happens once the device boots but I don't seem to be getting that far.
Any ideas?

Ran into the same problem 3 days ago. This is the first time I have encountered a non-revertible issue in 3 years as a cyanogenmod user. This changes my opinion on how safe it is to make use of a custom ROM. I tried to wipe everything, reinstall TWRP, change TWRP with another recovery, reinstall a safe NAND backup of mine.....nothing.....it went into boot loop. Before I read this post, I was convinced my phone encountered the infamous G4 bootloop problem.....now I see there are other examples, so it shouldn't be the case. Long story short, I had to check my device in at the LG assistance, with 25 days as time forecast.
The guilty nightly was 20161205.
I have never seen anything like this...

This has solved it for me - I installed LG Bridge and flashed the factory firmware using the tool. Now it seems I'm back on stock but at least it's working.

got mine working. I had to install LGUP and flash stock ROM. Once flashed I installed CM14 and I am back up and running again.

I tried LGUP but it could not recognize the device while this was looping.....a bad experience......

I have the same issue. My phone was updated to 20i via the original stock firmware, then I put twrp 3.0.2-0 and cyanogenmod on. I did a cyanogenmod update from within cyanogenmod, which just booted into twrp, then I manually installed the update zip that cyanogenmod had downloaded, then it always boots into twrp. I wonder if initiating the update from within cyanogenmod was the cause. The phone is not detected by LGUP or LG Bridge. I've tried this on a win10 machine, and a win7 vm from linux. I have access to twrp, and download mode by doing the reboot into bootloader from within twrp.
If those people who have fixed this could give more details about how they did it, that would be good. What exact steps did you take? What stock firmware version did you have before installing a custom rom? What OS version were you using? What twrp version?

Well. Mine got stuck in bootloop for the second time today. What is going on? In between the two bootloops I had one good update with CM. Using TWRP 3.0.2.1. Steps to reproduce failure: updating CM from within CM, it autoreboots into TWRP and after that nothing happends, no autoinstall. Then after a manual install of the new CM the bootloop starts.
Resolve the problem:
* Install LGUP 8994 DLL Ver 0 0 3 23, Install LGUP Install Ver 1 14, get the latest KDZ
* Get the phone into download mode with usb cable and after that in firmware update mode
* Startup LGUP and choose refurbish and select the kdz file.
* After that you can boot into your stock LG firmware again, reinstall TWRP an CM. If you want so.

Read that it is advised to manual update cm from within TWRP. TWRP will get an update in the future to solve this bootloop problem.

iankelling said:
I have the same issue. My phone was updated to 20i via the original stock firmware, then I put twrp 3.0.2-0 and cyanogenmod on. After a cyanogenmod update, it always boots into twrp. The phone is not detected by LGUP or LG Bridge. I've tried this on a win10 machine, and a win7 vm from linux. I have access to twrp, and download mode by doing the reboot into bootloader from within twrp.
If those people who have fixed this could give more details about how they did it, that would be good. What exact steps did you take? What stock firmware version did you have before installing a custom rom? What OS version were you using? What twrp version?
Click to expand...
Click to collapse
I second that. Same issue and neither LG Up nor LG Bridge will recognize my device. Looking in device manager there are no serial interfaces. Do I need a special driver that provides a com port for a phone in recovery or fastboot mode?
---Edith 2016-12-12: Found a solution for my issue:
The phone has to be in _download_ mode, not in recovery or fastboot. After realizing that I have to boot the phone in a different manner, it will be recognized by LG UP.
Here is how to boot the pone in download-mode:
- Power off your LG device.
- Press and hold Volume Up button.
- Connect your device to PC with a USB cable while holding the Volume Up button.
- You’ll boot into download mode with “Firmware Update” written on top of the screen.
Now everything is fine again.

croclacrimae said:
Hello everyone,
yesterday I flashed a new Cyanogenmod 14 nightly (12062016) for my G4 from earlier nightly in TWRP. After reboot the phone keeps going back to TWRP and I can't seem to get it to boot to system..
I tried factory reset, reflashing back to old nightly, flashing stock.. but nothing seems to work.
Also tried doing this in the TWRP terminal:
dd[space]if=/dev/zero[space]of=/dev/block/platform/f9824900.sdhci/by-name/fota
Didn't fix the loop, I guess because it wasn't the OTA update that caused the problem in the first place.
If anyone has an idea, I would greatly appreciate the help!
Thanks.
Click to expand...
Click to collapse
I was able to get out of that by also wiping by-name/misc. Don't do that, though, because then your wifi mac address will get messed up and you'll spend all day looking for a permanent fix for that.
I suggest reflashing a stock KDZ using LGUP, as others have said. You can get the usb drivers from LG Bridge.

I will release a fix for that soon. Check the twrp thread for updates on this.

Hi
I also have this problem
I installed cm-14.1-20161201-NIGHTLY-h815 successfully and was running it for almost 2 weeks without issues, today I updated to cm-14.1-20161213-NIGHTLY-h815 from cmupdater and I have been ending up in recovery every time I rebooted.
I tried flashing the latest cm recovery and reflashing the rom, with full wipes but no luck.
Full steps of recovering would be appreciated (for example, there are comments about flashing the latest stock rom, but a link to this rom would be helpful)
Thanks

Good news regarding this:
http://forum.xda-developers.com/showpost.php?p=70082901&postcount=213
The above will fix TWRP bootloop issues as well and I also released a first h811 version which should allow installing CM etc as it should.
Keep in mind that this is a BETA and not an official TWRP release.
Please report back in the above thread!
.

Does your twrp beta really fix the boot loop even it is already happening. What do I have to wipe? I have not managed to get out of the boot loop despite intalling it.
Is using using LG Up to flash to the stock rom really the only option?
Edited 2017-01-25 2:45 pm:
Well, sometimes you just have to be patient. Powered down the phone and when th H815 restarted CM did boot. Great. :good:

Hey, I just want to share a small detail, possibly a fluke that helped me overcome the bootloop.
So...I started with a fresh, stock H815, I don't quite remember the firmware version..it was something like version "20g"..
OK, I looked up several guides and tried to get the newest stable versions of each tool. I went through with the official bootloader unlock, then moved on to rooting: Kingroot didn't work for me so I went on installing twrp in fastboot mode so I could afterwards install supersu and root.
I got there eventually but first I was stuck in bootloop - kept ending up in twrp interface. I found the 2 dd commands but those didn't work for me as the msm_sdcc folder did not exist, but instead there was a "f9824900.sdhci". Tried to overwrite this one ...but as others have stated as well, it didn't work.
At that point, I had nothing to lose, I was starting to accept that I had soft-bricked my precious G4 so..I went on installing the DU 10.6 7.1.1 rom and the stock gapps, wiped dalvik, rebooted and held my breath...not literally
About 12 minutes later, after an endless red, spinning logo, my shiny ping pong paddle showed me a different screen, a fresh start welcome screen .
Almost 24h / 10-12 reboots (twrp included) / 70+ apps installed and removed later, the new OS holds around 2G ram average, a bit better battery life, smoother transitions, flawless navigation, flush streaming over both 3G/LTE & 2.4/5 G wifi.
FYI the reboots were intended, wanted to see consistency in boots - we're in the green . Now testing long term stability with moderate/high usage.
There is 1 aspect I noticed, there are a couple of contexts when the interface burps (several menus, various situations, never in apps) and resets back to homescreen...but I think that's more of a launcher topic than an OS one.
Other than that, so far I'm happy with the mod.
Hope my experience helps others that might be in the same spot I was or at lest boosts their confidence to try out a decent idea they might be pondering.

Secure booting error after Hidden menu test

Hello,
i dropped my phone last night and at first boot phone clock changed and i could not connect wifi. i tried to connect wifi today but it did not worked. Thats why i opened hidden menu by using *#546368#*855# test my phone if there is a hardware problem or not. i clicked first option then second option my phone got reset but i got Secure booting error after that and it stuck. Then i opened twrp by using factory data reset option. i got backup of my data from twrp menu.
What should i do now?
Notes:
- i use twrp + android 6.0 rooted firmware
- i dont know if can can install apk since i cant open android system
- i dont want to install stock rom by a pc because i think i will lose all info on phone and ont be able to get them back without twrp.

juba08 said:
Hello,
i dropped my phone last night and at first boot phone clock changed and i could not connect wifi. i tried to connect wifi today but it did not worked. Thats why i opened hidden menu by using *#546368#*855# test my phone if there is a hardware problem or not. i clicked first option then second option my phone got reset but i got Secure booting error after that and it stuck. Then i opened twrp by using factory data reset option. i got backup of my data from twrp menu.
What should i do now?
Notes:
- i use twrp + android 6.0 rooted firmware
- i dont know if can can install apk since i cant open android system
- i dont want to install stock rom by a pc because i think i will lose all info on phone and ont be able to get them back without twrp.
Click to expand...
Click to collapse
Hello,
You need to install Mr.Bump (click on it to download it) and move it to your Phone (Go to TWRP,connect your phone with your PC,move the file to your phone)Then click install and select "Mr.Bump.zip" file.
Greetings.

thanks you but i bricked my phone last night now it does not even open or charge. Thats i have done so far:
i used auto rec on my lg g3 d855 phone. https://forum.xda-developers.com/lg-g3/development/stock-d855-30b-images-kdz-flashables-t3282012 i had stock lg 6.0 30b firmware provided in this topic. it said succsfull and after the reset phone did not open and it does not respod to any button also dont get charge there is just black screen. is there there any way yo fix this?
do you think something like this topic help this issue?
https://forum.xda-developers.com/verizon-lg-g3/general/how-to-hardbrick-guide-using-test-t3276928

juba08 said:
thanks you but i bricked my phone last night now it does not even open or charge. Thats i have done so far:
i used auto rec on my lg g3 d855 phone. https://forum.xda-developers.com/lg-g3/development/stock-d855-30b-images-kdz-flashables-t3282012 i had stock lg 6.0 30b firmware provided in this topic. it said succsfull and after the reset phone did not open and it does not respod to any button also dont get charge there is just black screen. is there there any way yo fix this?
do you think something like this topic help this issue?
https://forum.xda-developers.com/verizon-lg-g3/general/how-to-hardbrick-guide-using-test-t3276928
Click to expand...
Click to collapse
It would be better not to flash those kdz files.
You could have asked here before proceeding,but it doesn't matter now.
For the topic that you sent,I'm not sure that it will work.
So,can enter in Download mode (Click on it to see how to enter)
If you can,please reply.

Sotiris02 said:
It would be better not to flash those kdz files.
You could have asked here before proceeding,but it doesn't matter now.
For the topic that you sent,I'm not sure that it will work.
So,can enter in Download mode (Click on it to see how to enter)
If you can,please reply.
Click to expand...
Click to collapse
i have done everything on that topic i went ok until last steps but at last i still got black screen and cant enter download mode or boot. but pc recognizes the phone as lge androidnet usb now in device manager. it was Qualcomm 9008 at start.

juba08 said:
i have done everything on that topic i went ok until last steps but at last i still got black screen and cant enter download mode or boot. but pc recognizes the phone as lge androidnet usb now in device manager. it was Qualcomm 9008 at start.
Click to expand...
Click to collapse
Hmm Try this guide Unbrick guide (it's officially for D855)

thanks it worked in second time now i can enter download mode i am flashing with lg flash tool. the problem is i could not install twrp before. i tried 5 roms + autorec, twrp manager and twrp offical app. and all resulted failing to open clock work mode. now i will try with D85530B_00_1217_32G.kdz
i have twrp backup in my sd card that why i am trying to boot into twrp for more than 24 hours. i hope i can do this. i winn never use eutorec i will use offical twrp app next time.
i can open android but i cant open twrp i got error boot vefication failed. i can use phone like that but i want to get my backup. if i cant i will have to install apps one by one and i will also lose some files, contacts, data etc.

TWRP BOOT LOOP has anyone found a solution (OTA update)

i tried installing the lastest ota update while i had twrp installed, i have tried everything to get out of this loop.
tried flashing the updated rom off the oneplus website and if gave me errors
just looked at my phone and now it wont turn on what so every getting really stressed please help
[SOLVED]
went back to stock recovery and side loaded the full 1.4 gb rom i will leave a link for tutorial that i used, i wanted to get back to complete stock and this was the one use
"https://forums.oneplus.net/threads/guide-how-to-unroot-your-oneplus-3-and-go-back-completely-to-stock.456232/"

When you have TWRP you have to install full zip, not simply the eval OTA zip

bob_cheeseman5 said:
i tried installing the lastest ota update while i had twrp installed, i have tried everything to get out of this loop.
tried flashing the updated rom off the oneplus website and if gave me errors
just looked at my phone and now it wont turn on what so every getting really stressed please help
Click to expand...
Click to collapse
Flash the stock recovery.
Get stock recovery from downloads.oneplus.net

I cant seem to flash the stock recovery. The device is not visible in adb devices or fastboot devices. im facing the same issue.

If you are using TWRP 3.0.4-0 - try a hard boot...hold down the power button for 20s...wait 20s, power it back on.

bob_cheeseman5 said:
i tried installing the lastest ota update while i had twrp installed, i have tried everything to get out of this loop.
tried flashing the updated rom off the oneplus website and if gave me errors
just looked at my phone and now it wont turn on what so every getting really stressed please help
Click to expand...
Click to collapse
easy solution. Boot into fastboot
download this tool.
https://forum.xda-developers.com/oneplus-3/development/toolkit-oneplus-3-toolkit-unlock-t3398799
if newest version isnt working, download an older version with older twrp
than unzip the tool and run the .bat file and install twrp.
Thats it

There are many posts on Nougat not working with official TWRP (based on 6.0 build). Try booting into stock recovery. performing a system settings reset, then booting into fastboot and run the adb command, <fastboot boot TWRP-3.0.2-1.28.img>. From there you can do virtually anything you need to do. I recommend at least using a modified version of TWRP (such as 1.28). This has been posted many times before, please try and do a search for the answers first, it will help tremendously. Thanks

recovery
i had the same problem on my rooted OP3 when i used TWRP 3.0.2-1 , it worked to flash the full 4.0.1 rom but failed for everything else, flashing latest verion of twrp fixed it for me

Got the same problem (unrooted phone + device state locked, cannot access recover, but can access fastboot) with an added "benefit", USB debugging mode was off before it all went crashing and burning.
How to access my phone via PC? (all the guides I've found assume I had USB debugging mode on before the phone got soft-bricked, but as a normal phone user who never installed anything custom, I've never figured it is A MUST BE ON function).
Or simpler question - what tool to use to turn on the USB debugging mode? (if that is at all possible?)

Aislandas said:
Got the same problem (unrooted phone + device state locked, cannot access recover, but can access fastboot) with an added "benefit", USB debugging mode was off before it all went crashing and burning.
How to access my phone via PC? (all the guides I've found assume I had USB debugging mode on before the phone got soft-bricked, but as a normal phone user who never installed anything custom, I've never figured it is A MUST BE ON function).
Or simpler question - what tool to use to turn on the USB debugging mode? (if that is at all possible?)
Click to expand...
Click to collapse
I have tried doing the installing of the newer twrp but cant find a newer version of it, i am on 3.0.2-1. i have the same problem as you that my USB debugging isnt on i dont think so when trying to use the op3 tool kit i can get it to pick up fast boot but nothing else.
have you found a solution to your problem yet?

bob_cheeseman5 said:
I have tried doing the installing of the newer twrp but cant find a newer version of it, i am on 3.0.2-1. i have the same problem as you that my USB debugging isnt on i dont think so when trying to use the op3 tool kit i can get it to pick up fast boot but nothing else.
have you found a solution to your problem yet?
Click to expand...
Click to collapse
Noted that you solved your issue, but this post is about the new version of TWRP. Version 3.0.3 is available on twrp.me and it works with Nougat.

bob_cheeseman5 said:
I have tried doing the installing of the newer twrp but cant find a newer version of it, i am on 3.0.2-1. i have the same problem as you that my USB debugging isnt on i dont think so when trying to use the op3 tool kit i can get it to pick up fast boot but nothing else.
have you found a solution to your problem yet?
Click to expand...
Click to collapse
Gave up trying and booked a session with OP technicians Will see how it goes in a week.

[Solved] Alternating between TWRP and Samsung logo

Hi,
I was running LineageOS on my Galaxy Tab S tablet (SM-T800). I tried to update LineageOS. I went into the settings and downloaded the lastest version. However, the installation didn't go through. The download was successful, but an error message told me to try and manually install the update. I tried to go into TWRP mode to install manually the update. Instead of going in the recovery mode, I saw a TWRP app on the Google Play store. I tried and install that app. It went ok, however, I needed to reboot my tablet to finish. I did so, but after that, I got stuck in booting mode, between the TWRP logo and the Samsung logo. So the tablet was trying to boot in TWRP mode, but after about 5 seconds on the splash screen of TWRP, the spalsh screen disapear and then the tablet tries to boot in normal mode. It doesn't work, and the tablet reboots in TWRP mode, but, again, unsuccessful. It's a loop, alterning between the two splash screens.
I tryed to go into download mode and flashed the stock ROM (found on Updato) while using Odin on my computer. It worked. However, after the process, my tablet got stucked on the Samsung logo only. Now, it doesn't go in recovery mode (TWRP). I can only go in download mode or regular mode (but not working). Only the download mode works.
I don't really know waht to do. I tryed to redo the process with Odin and the custon ROM, but it didn't work better.
What can I do?
Thank you very much for your help!

Blaccko said:
Hi,
I was running LineageOS on my Galaxy Tab S tablet (SM-T800). I tried to update LineageOS. I went into the settings and downloaded the lastest version. However, the installation didn't go through. The download was successful, but an error message told me to try and manually install the update. I tried to go into TWRP mode to install manually the update. Instead of going in the recovery mode, I saw a TWRP app on the Google Play store. I tried and install that app. It went ok, however, I needed to reboot my tablet to finish. I did so, but after that, I got stuck in booting mode, between the TWRP logo and the Samsung logo. So the tablet was trying to boot in TWRP mode, but after about 5 seconds on the splash screen of TWRP, the spalsh screen disapear and then the tablet tries to boot in normal mode. It doesn't work, and the tablet reboots in TWRP mode, but, again, unsuccessful. It's a loop, alterning between the two splash screens.
I tryed to go into download mode and flashed the stock ROM (found on Updato) while using Odin on my computer. It worked. However, after the process, my tablet got stucked on the Samsung logo only. Now, it doesn't go in recovery mode (TWRP). I can only go in download mode or regular mode (but not working). Only the download mode works.
I don't really know waht to do. I tryed to redo the process with Odin and the custon ROM, but it didn't work better.
What can I do?
Thank you very much for your help!
Click to expand...
Click to collapse
Have you tried to reflash twrp via odin ? If that works go into twrp reformat your partitions, then flash a custom rom.

Hi,
Thanks for your answer. I tried to reinstall TWRP with Odin on my computer. The process went well, but the reboot of my tablet that occurs at the end of the process got stuck again on the Samsung logo. It didn't get to TWRP mode. I tried to go manually into recovery mode by holding power+vol up+home, but it didn't work.
What else can I try? Thank you,

Blaccko said:
Hi,
Thanks for your answer. I tried to reinstall TWRP with Odin on my computer. The process went well, but the reboot of my tablet that occurs at the end of the process got stuck again on the Samsung logo. It didn't get to TWRP mode. I tried to go manually into recovery mode by holding power+vol up+home, but it didn't work.
What else can I try? Thank you,
Click to expand...
Click to collapse
Are you trying to get to twrp from powered off state ? If not , get to power off state, then use key combo again to try to get into twrp.
Also when you flash twrp, in odi , there is a setting to prevent auto reboot, use that and try to get to twrp via key combo from download. Mode., finally tripple chech the key combo you are using is correct

Hi,
Thanks for the help. I tried to get to TWRP from power off state. The TWRP splash screen appears, and stays on for about 5-10 sec. After that, the splash screen disappear and the tablet reboot to get stuck on the Samsung logo again. It's like if the TWRP booting process doesn't go through...
Thanks again for your help,

Ouch !!
Looks like you got a real problem , and getting into territory I'm not expert in, Ashyx is the real authority with twrp for this device, you can try to pm him and hope he takes pity on you ( he has been helping guys on this qa thread tirelessly for over a year, and is prob taking a well deserved break ).
Otherwise a few more suggestions,
Maybe your PIT is messed up , ( but you prob would not make it to twrp splash screen in that case )
Twrp may still be trying to execute the script from the original linage update and not finding something bails ( total guess ).
Try flashing a stock ( downloaded from sammobile or somwhere you trust ) rom via odin, and see if you can get into the stock recovery. From there do a factory reset and see if you can get stock running.
Try getting into twrp with device connected to pc ( helped in some wierd cases, you never know lol ).
When TWRP splash screen comes up, try some key combos , maybe twrp checks for a script abbort key combo ?
Checkout the TWRP github issues page, see if your bug is there and a solution, create a bug report or mail a dev directly.
Have a look at the TWRP code, maybe some clues ??

Hi,
So not much development here...
I tried to download the stock ROM for my device from Sammobile and tried flashing it with Odin (JOdin actually, I'm on Mac), but it says it need a PIT file. I let Casual fin the PIT file and it finds it. Only, after that my device does not reconnect to Odin even though it's still plugged in my computer. I tried to unplug it then plug it back, but then Odin says the PIT file is corrupted. I tried to restart my device, but still not connecting to Odin...
I tried getting into TWRP with my device connected to my computer. Still the same problem of rebooting while TWRP is booting (while it's on splash page).
No combo key seems to work to keep TWRP open and loading...
Didn't find anything on TWRP github and I'm not saavy enough to look into TWRP code.
So, I'm still stuck with my initial problem. Do any of ou have some advices/suggestions or can help me with my problem please? At this point, I've been without my tablet for more than a month and it S**KS!!
Thanks in advance everyone,

Blaccko said:
Hi,
So not much development here...
I tried to download the stock ROM for my device from Sammobile and tried flashing it with Odin (JOdin actually, I'm on Mac), but it says it need a PIT file. I let Casual fin the PIT file and it finds it. Only, after that my device does not reconnect to Odin even though it's still plugged in my computer. I tried to unplug it then plug it back, but then Odin says the PIT file is corrupted. I tried to restart my device, but still not connecting to Odin...
I tried getting into TWRP with my device connected to my computer. Still the same problem of rebooting while TWRP is booting (while it's on splash page).
No combo key seems to work to keep TWRP open and loading...
Didn't find anything on TWRP github and I'm not saavy enough to look into TWRP code.
So, I'm still stuck with my initial problem. Do any of ou have some advices/suggestions or can help me with my problem please? At this point, I've been without my tablet for more than a month and it S**KS!!
Thanks in advance everyone,
Click to expand...
Click to collapse
Use ODIN via Windows or a VM on your Mac.
Flash stock firmware then boot to recovery and factory reset.
Reboot and wait ten minutes.

Hi, thanks a lot for your time.
I will try that at work tomorrow as I don't have Windows at home. However, I did try to flash stock ROM with Windows initially (see first post for more info) and it didn't solve my problem. I wasn't able to access recovery mode after the stock ROM was flashed. Hope it's gonna work now and I'll be able to factory reset.
I'll let you know tomorrow afternoon.
Thanks,
ashyx said:
Use ODIN via Windows or a VM on your Mac.
Flash stock firmware then boot to recovery and factory reset.
Reboot and wait ten minutes.
Click to expand...
Click to collapse

WOW!!! Thank you so much Ashyx. I can now finally use my Tab S. I'm so grateful!!! Thousand time thank you! I deeply appreciate your help for resolving my problem.
ashyx said:
Use ODIN via Windows or a VM on your Mac.
Flash stock firmware then boot to recovery and factory reset.
Reboot and wait ten minutes.
Click to expand...
Click to collapse