Develop Bugs

Hard bricked VS985 after ROM flash failure

Sorry, I'm relatively new to rooting and I looked through the threads and found similar problems, but none that seem to exactly match mine.
I have a rooted VS985 that I was trying to flash with the AndroidNow HD 6.1 ROM using TWRP and I guess the flash tool crashed. It was stuck on a black screen for an hour or two so I hard reset it and after that, the phone will only flash the LG logo for a second before the screen turns off and the indicator light alternates flashing red and blue. As far as I can tell, the computer does not detect it when it is in this mode (seems similar to the secure boot issue that some people have been having). I cannot enter download mode (the LG logo flashes on and the indicator light flashes blue once and then both turn off) but I can still boot into TWRP Recovery. When I try to boot into download mode, even while the screen is off, my computer detects the phone as QHSUSB_BULK. Also, when in recovery mode, my computer can detect the phone as a G3 and I can access it with adb tools but I don't know where to go from here. I have tried using the LGFlashTool but I can't seem to access the phone because it will not enter download mode and I've tried reflashing AndroidNow HW 6.1. The flash completes and says it is successful, but the phone still will not boot properly.
Luckily, I got the phone a few days ago from Costco, so there is a good chance I can still return it, but I would like to fix it if I can.
Any help would be greatly appreciated.

pyroguy3590 said:
Sorry, I'm relatively new to rooting and I looked through the threads and found similar problems, but none that seem to exactly match mine.
Any help would be greatly appreciated.
Click to expand...
Click to collapse
You said you have adb working.
Did you make a backup of your stock download mode at anypoint of time? (Iaf.img)
I guess it can be pushed back using adb, but am not very sure. Even if not, maybe you can take the stock Iaf.img from someone else and try pushing it via adb using this command:
Code:
dd if=/storage/external_SD/stock-laf.img of=/dev/block/platform/msm_sdcc.1/by-name/laf
Then you can boot into the download mode using the command:
Code:
fastboot boot stock-laf.img

It doesn't look like I have the stock laf.img backed up. I'll try to get it from someone. Thanks, I'll let you know what happens when I get it.

I need this tooi fi h
had a nandroid backup but accidentatlly delted it when i formatted my internal memory now im stuck on liquidsmooth custom rom cant get into download mode so kdz/tot will not work for me... I have twrp installed and that works though. I need to use adb to flash those files or have a stock vs985 that i can flash with twrp... I have vs985 i like the liquid smooth room but the camera and video camera doesnt work as good as it did with stock...
Any help or ideas would bee aprraciedated ive tried everything

just Switch off your mobile.. and put out bettery from it,
And In Pc Download Any Official Tot rom For Your lg g3 vs985 than Open LG Flash Tool 2014
download it from Xdadevelopers any version
Than Put back your bettery In Your Mobile And dont press any button Just put your usb in,your pc and Same time Put Pin in your mobile and press Volume up button And Your Mobile goes in Download Mod Automaticly..
Than Just Flash any Tot Software in It..
Its Working Like Charm,,
Try it It is Working for me Also

[Q] Bricked Tablet - Downloading only

Hi Guys,
After playing with a lot of different roms on this tablet, i was content with CM12. I thought also now would be a good time to update TWRP from the ROM itself. So, i downloaded the TWRP manager, told it my device and told it to update. It asked me if the location for recovery was ok, and i (assumed....so its me being stupid) told it it was.......
Now my tablet wont boot anymore, i only get to see the "downloading" screen with the android dude. I love the android dude, but not so much that he's all i want to see
I tried using odin to re-apply the TWRP file from there, but it just is stuck at "initialization". I tried doing the same with the stock firmware from Sammobile, but the same thing happens.
I know there HAS to be a way to get it working again as it is still powering on...but i am running out of ideas. Can anyone please help me? If you're in town i will treat you to a nice Jopen bier
Thanks guys,
Yves

yvessparks said:
Hi Guys,
After playing with a lot of different roms on this tablet, i was content with CM12. I thought also now would be a good time to update TWRP from the ROM itself. So, i downloaded the TWRP manager, told it my device and told it to update. It asked me if the location for recovery was ok, and i (assumed....so its me being stupid) told it it was.......
Now my tablet wont boot anymore, i only get to see the "downloading" screen with the android dude. I love the android dude, but not so much that he's all i want to see
I tried using odin to re-apply the TWRP file from there, but it just is stuck at "initialization". I tried doing the same with the stock firmware from Sammobile, but the same thing happens.
I know there HAS to be a way to get it working again as it is still powering on...but i am running out of ideas. Can anyone please help me? If you're in town i will treat you to a nice Jopen bier
Thanks guys,
Yves
Click to expand...
Click to collapse
What Device you have? When you flash TWRP with Odin, do you uncheck Auto Reboot? I always uncheck it then power off then press Power, Home and Vol up to boot TWRP. Maybe no help.

Rooted i747 said:
What Device you have? When you flash TWRP with Odin, do you uncheck Auto Reboot? I always uncheck it then power off then press Power, Home and Vol up to boot TWRP. Maybe no help.
Click to expand...
Click to collapse
Sorry, Samsung galaxy tab pro 10.1, sm-t520 aka picassowifi.
Auto reboot does not change anything... Still stops at 'initialization'.
I cannot get anywhere else but the downloading screen...
Thanks so far

I know you can't take the battery out but I been reading to let it die. Then plug it in works for some.
Note 4 Port Evolution 3.0

I drained it...when I get home I will try the Odin method. I'm starting to worry though....
Thanks again

Thanks for your help guys! The battery drain did the trick! I successfully installed the new TWRP and new CM 12.1
Thanks guys!
Yves

yvessparks said:
Thanks for your help guys! The battery drain did the trick! I successfully installed the new TWRP and new CM 12.1
Thanks guys!
Yves
Click to expand...
Click to collapse
Glad it's working! :good:

How to drain battery?
Good to hear it worked for you but how did you drained the battery. I dont know how to drain it if I cant use the tablet ( and I believe my tablet is fully charged)

I am in a similar situation.
I have SM-T900 (Galaxy Tab PRO 12.2) and when I flashed TWRP 2.8.7.0 (for v2wifixx) for the first time over the stock recovery. It was successful and booted into recovery, but then it was not able to wipe any data. It gave some errors which I do not remember right now.
Then I tried re-flashing the same but it is not booting back into recovery, anymore after more than 5 attempts. When am re-flashing the TWRP, it is showing SUCCESS in Odin but the device is not booting into recovery. Current situation is that I cannot power it off nor boot into recovery. All it is allowing me is to get into download mode. Also, I have Kies 3/Smart Switch installed and NONE of them is recognizing the device in download mode either. However, am able to login to the download mode and reflash the twrp recovery image file.
Currently, opened the back cover and removed the battery connector and re-connected it and that is only way I could get the power off. I will try to re-flash TWRP again in the evening today.
I am posting here to ask for any other ideas. Is there anything else that I can try?
Thanks.
yvessparks said:
Thanks for your help guys! The battery drain did the trick! I successfully installed the new TWRP and new CM 12.1
Thanks guys!
Yves
Click to expand...
Click to collapse

Finally fixed the issue.
I downloaded the firmware from www.sammobile.com for SM-T900 (Cellular South) having the PDA version as T900UEUBOI2 and this is for US. I downloaded the latest (v5.1.1) as of this writing.
I switched ON the tab in download mode and connected to computer using the USB. It appeared in Odin (I used v3.10.7). I flashed the firmware file downloaded (link in above para) and it roughly took 3 mins to show SUCCESS. Since, I selected the Auto Reboot in Odin, it tried to reboot but the device has been going through bootloop. At this point, I powered OFF the device and tried to boot into recovery. After couple of trials, it booted into recovery. I did a "wipe data - factory reset" an rebooted the device and it worked guys. I finally happy to see the device coming back to life.. however with the stock rom. However, I did not root the device as of this writing.
It worked finally. Hope this would help others.
uresh.kuruhuri said:
I am in a similar situation.
I have SM-T900 (Galaxy Tab PRO 12.2) and when I flashed TWRP 2.8.7.0 (for v2wifixx) for the first time over the stock recovery. It was successful and booted into recovery, but then it was not able to wipe any data. It gave some errors which I do not remember right now.
Then I tried re-flashing the same but it is not booting back into recovery, anymore after more than 5 attempts. When am re-flashing the TWRP, it is showing SUCCESS in Odin but the device is not booting into recovery. Current situation is that I cannot power it off nor boot into recovery. All it is allowing me is to get into download mode. Also, I have Kies 3/Smart Switch installed and NONE of them is recognizing the device in download mode either. However, am able to login to the download mode and reflash the twrp recovery image file.
Currently, opened the back cover and removed the battery connector and re-connected it and that is only way I could get the power off. I will try to re-flash TWRP again in the evening today.
I am posting here to ask for any other ideas. Is there anything else that I can try?
Thanks.
Click to expand...
Click to collapse

Hi I am in a similar situation. I flashed CM12 on my Tab pro 8.4 wifi. Left it untouched for a month or 2. That mean battery fully drained. Then I tried to charged but no luck. The tab only shows a hollow grey battery icon with a static circle in the middle. Cannot boot to recovery mode but only download mode. No charging at all.
I tried the button combo like holding down power + vol up 20s, etc. No luck. I then bought a battery and changed it....shxt, same!
Then I used KIES to flash stock rom. A bit better now I can see the samsung text but freezed there. Anyone can help?

Phone no longer bricked (yay!), but not fastboot

The backstory: I have no experience with rooting and or flashing custom ROMs. Prior to today my ze551ml was completely stock, running on the official android M update. I had a need to do a factory reset, but the phone would simply reboot. I assumed this was a problem with the update so I download and attempted to install the downgrade to l. Naturally it crashed mid downgrade and I thought it to be bricked. So, I started Googling and realized I was able to get into fastboot mode, but not recovery. Following a guide I located I attempted to flash the preroot ROM located at the link below:
http://forum.xda-developers.com/zenfone2/development/rom-pre-root-img-t3079590
Well, it appeared to have worked, but now the phone refused to boot at all after being turned off. So, more Googling and I proceeded to follow the full unbricking guide below:
http://forum.xda-developers.com/zenfone2/help/thead-bricked-phone-updating-to-mm-tips-t3452785
Partway through step 1.3 the phone restarted itself and booted right up into Android L! Success I thought to myself, but it was not to be. I proceeded to download the FOTA L update and it downloaded fine, but when I clicked to install it simply rebooted the phone. Tried a couple of other times with the same result. I realized that Supersu was installed so I did the full unroot assuming that was the problem, but to no avail. It appears that the updates can't install because the phone is incapable of entering fastboot or recover mode. Anytime I attempt to enter fastboot via hard key or through adb the phone hangs on the ASUS logo. Adb detects the phone when it's connected via USB, but of course fastboot can't because I can't get it into fastboot mode at all.
Any tips on how to get fastboot operational again so I can start applying updates again? Every guide I've located has started with "boot into fastboot/recovery" which simply isn't an option. Any help is appreciated.
Edit: Well, I think I've reached the end of the internet trying to google for a solution. The phone works, but it looks like it's stuck on build 2.13.40.13 until the end of its life. If anybody has any ideas I'm still hoping for a solution, but I can't find anything describing how to restore fastboot if the OS is intact.

kidnova said:
The backstory: I have no experience with rooting and or flashing custom ROMs. Prior to today my ze551ml was completely stock, running on the official android M update. I had a need to do a factory reset, but the phone would simply reboot. I assumed this was a problem with the update so I download and attempted to install the downgrade to l. Naturally it crashed mid downgrade and I thought it to be bricked. So, I started Googling and realized I was able to get into fastboot mode, but not recovery. Following a guide I located I attempted to flash the preroot ROM located at the link below:
http://forum.xda-developers.com/zenfone2/development/rom-pre-root-img-t3079590
Well, it appeared to have worked, but now the phone refused to boot at all after being turned off. So, more Googling and I proceeded to follow the full unbricking guide below:
http://forum.xda-developers.com/zenfone2/help/thead-bricked-phone-updating-to-mm-tips-t3452785
Partway through step 1.3 the phone restarted itself and booted right up into Android L! Success I thought to myself, but it was not to be. I proceeded to download the FOTA L update and it downloaded fine, but when I clicked to install it simply rebooted the phone. Tried a couple of other times with the same result. I realized that Supersu was installed so I did the full unroot assuming that was the problem, but to no avail. It appears that the updates can't install because the phone is incapable of entering fastboot or recover mode. Anytime I attempt to enter fastboot via hard key or through adb the phone hangs on the ASUS logo. Adb detects the phone when it's connected via USB, but of course fastboot can't because I can't get it into fastboot mode at all.
Any tips on how to get fastboot operational again so I can start applying updates again? Every guide I've located has started with "boot into fastboot/recovery" which simply isn't an option. Any help is appreciated.
Edit: Well, I think I've reached the end of the internet trying to google for a solution. The phone works, but it looks like it's stuck on build 2.13.40.13 until the end of its life. If anybody has any ideas I'm still hoping for a solution, but I can't find anything describing how to restore fastboot if the OS is intact.
Click to expand...
Click to collapse
You have to use full unbrick method(xfstk + raw) to restore ur device fully
xfstk will restore ur fastboot image

yakub234go said:
You have to use full unbrick method(xfstk + raw) to restore ur device fully
xfstk will restore ur fastboot image
Click to expand...
Click to collapse
Thanks for the response. I've tried this a dozen times, but unfortunately (this is going to sound weird) since it's not completely bricked it is only detected as Moorefield for a few seconds when started. This allows the xfstk tool to detect it and begin the download, but not long enough to complete the process so it times out. The only development access I have to the phone now is via adb, but since I don't have root I'm very limited in what I can do via command line. Since I can't access fastboot I can't achieve root. It's just a comedy of errors now.

kidnova said:
The backstory: I have no experience with rooting and or flashing custom ROMs. Prior to today my ze551ml was completely stock, running on the official android M update. I had a need to do a factory reset, but the phone would simply reboot. I assumed this was a problem with the update so I download and attempted to install the downgrade to l. Naturally it crashed mid downgrade and I thought it to be bricked. So, I started Googling and realized I was able to get into fastboot mode, but not recovery. Following a guide I located I attempted to flash the preroot ROM located at the link below:
http://forum.xda-developers.com/zenfone2/development/rom-pre-root-img-t3079590
Well, it appeared to have worked, but now the phone refused to boot at all after being turned off. So, more Googling and I proceeded to follow the full unbricking guide below:
http://forum.xda-developers.com/zenfone2/help/thead-bricked-phone-updating-to-mm-tips-t3452785
Partway through step 1.3 the phone restarted itself and booted right up into Android L! Success I thought to myself, but it was not to be. I proceeded to download the FOTA L update and it downloaded fine, but when I clicked to install it simply rebooted the phone. Tried a couple of other times with the same result. I realized that Supersu was installed so I did the full unroot assuming that was the problem, but to no avail. It appears that the updates can't install because the phone is incapable of entering fastboot or recover mode. Anytime I attempt to enter fastboot via hard key or through adb the phone hangs on the ASUS logo. Adb detects the phone when it's connected via USB, but of course fastboot can't because I can't get it into fastboot mode at all.
Any tips on how to get fastboot operational again so I can start applying updates again? Every guide I've located has started with "boot into fastboot/recovery" which simply isn't an option. Any help is appreciated.
Edit: Well, I think I've reached the end of the internet trying to google for a solution. The phone works, but it looks like it's stuck on build 2.13.40.13 until the end of its life. If anybody has any ideas I'm still hoping for a solution, but I can't find anything describing how to restore fastboot if the OS is intact.
Click to expand...
Click to collapse
seems like you did not install droidboot.bin correctly... only way is use xFSTK again.i have updated the link to latest raw firmware 2.20.40.194 and use the same guide and commands..

sukhwant717 said:
seems like you did not install droidboot.bin correctly... only way is use xFSTK again.i have updated the link to latest raw firmware 2.20.40.194 and use the same guide and commands..
Click to expand...
Click to collapse
The problem is that it's only recognized as Moorefield for a few seconds which isn't enough time for xFSTK to complete the install. Do you know of a way to force the device to stay connected as Moorefield?

kidnova said:
The problem is that it's only recognized as Moorefield for a few seconds which isn't enough time for xFSTK to complete the install. Do you know of a way to force the device to stay connected as Moorefield?
Click to expand...
Click to collapse
Plug the phone to the PC, be sure the phone is completely off and then hold power + vol- for a few seconds. You must see the "Moorefield" driver permanent in the device manager.
Btw... I got the same problem (four lines, not bootloader, not OS; xFSTK FW+OS failed) and I'm stuck in this step :/

mrperalta said:
Plug the phone to the PC, be sure the phone is completely off and then hold power + vol- for a few seconds. You must see the "Moorefield" driver permanent in the device manager.
Btw... I got the same problem (four lines, not bootloader, not OS; xFSTK FW+OS failed) and I'm stuck in this step :/
Click to expand...
Click to collapse
I've tried this many times, but it only shows Moorefield for a few seconds. I'm assuming this is because it has a fully operational OS so it doesn't stay in the generic USB device mode.
EDIT: I misread your original post. Holding power and volume DOWN does keep connect it in Moorefield. Thanks so much for that. The problem now is that once xFSTK gets to downloading the OS it reboots the phone which takes it out of USB mode and disconnects the tool. I'm still stuck where I was before, but that's a little progress. Any other thoughts?

New update. I'm able to get to the point of loading the OS from xFSTK by skipping the FW part, however it continuously fails. My assumption is because it can't overwrite the existing OS. Any other ideas?

kidnova said:
New update. I'm able to get to the point of loading the OS from xFSTK by skipping the FW part, however it continuously fails. My assumption is because it can't overwrite the existing OS. Any other ideas?
Click to expand...
Click to collapse
Kidnova, reading this post I could fixed my problem. The "issue" was in the xFSTK where you put the flag (0x800000807). A guy on the threat said to put "0x80000807" instead of "0x800000807" (note that there is "0" from difference).
"those who are not able to keep device connected. take care of few steps
1. in xFSTK option menu change the flag override value to 0x80000807 not 0x800000807 ( don't forget to click gp value over ride)
2. while connecting to xFSTK attach usb to computer. hold power button for 20 seconds to make sure it power downs completely. then hold the power button down and click power button. wait till device vibrate or computer makes detection sound. leave power button but keep holding the volume button for few seconds"
Click to expand...
Click to collapse
-sukhwant717

mrperalta said:
Kidnova, reading this post I could fixed my problem. The "issue" was in the xFSTK where you put the flag (0x800000807). A guy on the threat said to put "0x80000807" instead of "0x800000807" (note that there is "0" from difference).
-sukhwant717
Click to expand...
Click to collapse
You guys are lifesavers! I've got fast boot again. Now to see if I can continue without screwing it up.
FINAL EDIT: I have a 100% functional stock Zenfone 2. Thanks everybody for your help.

kidnova said:
You guys are lifesavers! I've got fast boot again. Now to see if I can continue without screwing it up.
FINAL EDIT: I have a 100% functional stock Zenfone 2. Thanks everybody for your help.
Click to expand...
Click to collapse
Hi, got the same issues, I've read many posts. Tried all of the million options. What was your final way of doing it, do you remember?

Tab S 8.4 Stuck in recovery loop

Hi Folks,
I have a Tab S 8.4 wifi that I seem to have broken. I was attempting to restore the stock Marshmallow rom and something has gone horribly wrong. This is what I did:
1. I installed the latest stock rom by Odin and booted
2. I then downloaded and installed CF auto root/TWRP for the SM-T700, however, I failed notice that I had left NAND erase checked in the Odin settings so now all I get is the device attempting boot into TWRP which doesn’t work.
The device won’t turn off to allow me to use the buttons to access download mode which I know is what I need. I have tried draining the battery completely but as soon as power is restored it attempts to boot into the failed recovery again and is, in effect, stuck on the TWRP screen, periodically flashing the screen. It its broken TWRP state, the computer recognises it as a USB MTP device but will not recognise with the correct drivers to allow me to use ADB to force it into the download.
Does anybody have any suggestions? Otherwise I have a £250 paperweight!

unsrm said:
Hi Folks,
I have a Tab S 8.4 wifi that I seem to have broken. I was attempting to restore the stock Marshmallow rom and something has gone horribly wrong. This is what I did:
1.I installed the latest stock rom by Odin and booted
2.I then downloaded and installed CF auto root/TWRP for the SM-T700, however, I failed notice that I had left NAND erase checked in the Odin settings so now all I get is the device attempting boot into TWRP which doesn’t work.
The device won’t turn off to allow me to use the buttons to access download mode which I know is what I need. I have tried draining the battery completely but as soon as power is restored it attempts to boot into the failed recovery again and is, in effect, stuck on the TWRP screen, periodically flashing the screen. It its broken TWRP state, the computer recognises it as a USB MTP device but will not recognise with the correct drivers to allow me to use ADB to force it into the download.
Does anybody have any suggestions? Otherwise I have a £250 paperweight!
Click to expand...
Click to collapse
The file you flashed doesn't work on Marshmallow.
Use the updated twrp and supersu in the dev section.

ashyx said:
The file you flashed doesn't work on Marshmallow.
Use the updated twrp and supersu in the dev section.
Click to expand...
Click to collapse
Thanks for the reply ashyx, I don't current have a way to achieve that as I cannot access download mode. Any suggestions on how to do that?

unsrm said:
Thanks for the reply ashyx, I don't current have a way to achieve that as I cannot access download mode. Any suggestions on how to do that?
Click to expand...
Click to collapse
You can access download mode anytime irrespective of the current state the device is in.
Hold POWER + HOME + VOL DOWN until the device boots in to download mode.

ashyx said:
You can access download mode anytime irrespective of the current state the device is in.
Hold POWER + HOME + VOL DOWN until the device boots in to download mode.
Click to expand...
Click to collapse
I did't realise it would work in any mode!
Thought I'd tried it but obviously not held long enough.
You are a star! Thank you so much.
Chris

[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