Hi, I'm hoping to find some help with rescuing a TB-x304f that will not boot past the bootloader. I was trying to root it and got TWRP installed but when I flashed SuperSU it will no longer boot to the OS. I've tried booting the stock recovery and doing a factory reset and it says it is completed but when I reboot it just keeps going to the bootloader and choosing Start to load the OS doesn't make a difference, it reboots back to the bootloader. I've downloaded TB-X304F_S000038_170703_ROW_QFIL.zip and tried using QFIL but it fails with
Download Fail:FireHose Fail:FHLoader Fail:The system cannot find the file specified
Click to expand...
Click to collapse
I also downloaded system-tb-x304f-s000038-sparse.img that I found in a thread and flashed it using ADB and it said everything completed successfully but it still just boots to the bootloader.
Any help would be greatly appreciated!!! Thanks.
kingzfn said:
Hi, I'm hoping to find some help with rescuing a TB-x304f that will not boot past the bootloader. I was trying to root it and got TWRP installed but when I flashed SuperSU it will no longer boot to the OS. I've tried booting the stock recovery and doing a factory reset and it says it is completed but when I reboot it just keeps going to the bootloader and choosing Start to load the OS doesn't make a difference, it reboots back to the bootloader. I've downloaded TB-X304F_S000038_170703_ROW_QFIL.zip and tried using QFIL but it fails with
I also downloaded system-tb-x304f-s000038-sparse.img that I found in a thread and flashed it using ADB and it said everything completed successfully but it still just boots to the bootloader.
Any help would be greatly appreciated!!! Thanks.
Click to expand...
Click to collapse
QFIL is such a pain to work with. I was in a similar situation with my TB-8704V, and spent days trying to work with QFIL and TWRP.
But the simplest solution is to use the 'Lenovo Smart Moto Assistant'. It's such a powerful tool. The firmware can be downloaded and flashed with a few clicks. The tab was back to life in a few minutes. The way it worked, seems like it also used the edl mode. I don't see any reason to use QFIL on a Lenovo device again.
https://support.lenovo.com/us/en/downloads/ds101291
https://support.lenovo.com/us/en/solutions/ht501876
suhridkhan said:
QFIL is such a pain to work with. I was in a similar situation with my TB-8704V, and spent days trying to work with QFIL and TWRP.
But the simplest solution is to use the 'Lenovo Smart Moto Assistant'. It's such a powerful tool. The firmware can be downloaded and flashed with a few clicks. The tab was back to life in a few minutes. The way it worked, seems like it also used the edl mode. I don't see any reason to use QFIL on a Lenovo device again.
https://support.lenovo.com/us/en/downloads/ds101291
https://support.lenovo.com/us/en/solutions/ht501876
Click to expand...
Click to collapse
suhridkhan thank you, you are a lifesaver!!
Lenovo Smart Moto Assistant worked perfectly! It's crazy that after some hours of searching I came across QFIL, Lenovo Downloader, MiFlash, Qualfast but never saw anything about Lenovo Smart Moto Assistant. Thanks again and hopefully this will benefit other people in my situation!
kingzfn said:
suhridkhan thank you, you are a lifesaver!!
Lenovo Smart Moto Assistant worked perfectly! It's crazy that after some hours of searching I came across QFIL, Lenovo Downloader, MiFlash, Qualfast but never saw anything about Lenovo Smart Moto Assistant. Thanks again and hopefully this will benefit other people in my situation!
Click to expand...
Click to collapse
How you did that , can you explain it briefly and in a noob friendly manner, I am the same condition but with x304l model
Related
Long story short, my phone only displays the n/a screen and won't boot up.
I got the phone from Sprint, and it is the Qualcomm version. (The box says that anyway.) I wanted to root the device, so I unlocked the bootloader and attempted to flash SuperSU. This didn't work, as the app didn't show after the flash. I then tried to use Magisk, but I received Error 1 (boot image patched by other programs). To fix this issue, I downloaded a similar stock ROM and tried to install that. I ended up just wiping all the data on the phone, including the OS. Luckily I did make a nandroid backup.
The phone currently has no OS, due to me wiping all my data on it. I made a backup of when it did work (said earlier), with all partitions excluding Data. I have restored it, but it doesn't boot up. TWRP says nothing about there being no OS on the phone. I can't find a stock ROM of this particular phone, but there are some close ones. (sperry XT1768 I believe.) If anyone could help me restore my phone or possibly provide me the stock ROM I would be beyond grateful. I would also be also be okay with posting any logs or things you need.
Thanks much!
Go here:
https://firmware.center/firmware/Motorola/Moto E4/Stock/
This is the Boost XT1766 firmware :
https://firmware.center/firmware/Mo...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
I did a dumb and was rewarded
So, I ended up flashing the sperry XT1768 ROM that I had downloaded. Keep in mind I already lacked an OS, so I had nothing to lose.
PLEASE NEVER FLASH A ROM THAT DOESN'T BELONG TO YOUR DEVICE. THIS COULD CAUSE YOUR PHONE TO BE BRICKED.
Against the above statement, I literally had nothing to lose. I got my phone to boot up, and it has all of its functionality. Thank you for posting the correct software amarc78, I'll have to flash the correct ROM at a later time.
Moral of the story, please know what you are doing before you do something dumb. Use proper forums (such as the one you are on...) to do such tasks as rooting your phone.
Zachery Calahan said:
So, I ended up flashing the sperry XT1768 ROM that I had downloaded. Keep in mind I already lacked an OS, so I had nothing to lose.
PLEASE NEVER FLASH A ROM THAT DOESN'T BELONG TO YOUR DEVICE. THIS COULD CAUSE YOUR PHONE TO BE BRICKED.
Against the above statement, I literally had nothing to lose. I got my phone to boot up, and it has all of its functionality. Thank you for posting the correct software amarc78, I'll have to flash the correct ROM at a later time.
Moral of the story, please know what you are doing before you do something dumb. Use proper forums (such as the one you are on...) to do such tasks as rooting your phone.
Click to expand...
Click to collapse
Hmmmm, sounds intriguing. I soft bricked my xt1766 a few days ago and have found multiple fixes, but nothing that sticks. That above firmware? Took me two days to realize I needed RSD Lite to flash it. What was that RSD Lite? You play funny with Windows 10, no worries, I'll create my own batch file to manually flash this firmware.........WHAT!!!!!!! Why is there a multi colored ring saying "erasing" at the bottom and rebooting every 30 seconds?????? So after further research and "multiple error 7s" as well as "cant mount cache/data" errors, I came to another fix, lo and behold, im in a TWRP bootloop. Long story short, FML!!!!! Im glad you found a fix. Happy flashing.
TeamAndro08 said:
Hmmmm, sounds intriguing. I soft bricked my xt1766 a few days ago and have found multiple fixes, but nothing that sticks. That above firmware? Took me two days to realize I needed RSD Lite to flash it. What was that RSD Lite? You play funny with Windows 10, no worries, I'll create my own batch file to manually flash this firmware.........WHAT!!!!!!! Why is there a multi colored ring saying "erasing" at the bottom and rebooting every 30 seconds?????? So after further research and "multiple error 7s" as well as "cant mount cache/data" errors, I came to another fix, lo and behold, im in a TWRP bootloop. Long story short, FML!!!!! Im glad you found a fix. Happy flashing.
Click to expand...
Click to collapse
I used this rsdlite, and it works on my PC with Windows 10. Just make sure you have Motorola drivers installed.
madbat99 said:
I used this rsdlite, and it works on my PC with Windows 10. Just make sure you have Motorola drivers installed.
Click to expand...
Click to collapse
Im at work now, but when I get home, I'll definitely give that pony a whirl! Thanks man.
TeamAndro08 said:
Im at work now, but when I get home, I'll definitely give that pony a whirl! Thanks man.
Click to expand...
Click to collapse
For the Twrp loop, try selecting reboot bootloader, then in bootloader, select start. That should get you into system.
There is a fix for that, I'll find the link. Some twrp build aren't wiping something properly and causes a recovery loop after formatting data.
madbat99 said:
For the Twrp loop, try selecting reboot bootloader, then in bootloader, select start. That should get you into system.
There is a fix for that, I'll find the link. Some twrp build aren't wiping something properly and causes a recovery loop after formatting data.
Click to expand...
Click to collapse
Definitely appreciate the info brother, I havent been able to get to it cuz of work. But tonight, I will try all things youve mentioned.
TeamAndro08 said:
Hmmmm, sounds intriguing. I soft bricked my xt1766 a few days ago and have found multiple fixes, but nothing that sticks. That above firmware? Took me two days to realize I needed RSD Lite to flash it. What was that RSD Lite? You play funny with Windows 10, no worries, I'll create my own batch file to manually flash this firmware.........WHAT!!!!!!! Why is there a multi colored ring saying "erasing" at the bottom and rebooting every 30 seconds?????? So after further research and "multiple error 7s" as well as "cant mount cache/data" errors, I came to another fix, lo and behold, im in a TWRP bootloop. Long story short, FML!!!!! Im glad you found a fix. Happy flashing.
Click to expand...
Click to collapse
THIS! Have you ever found a solution? I have the EXACT SAME PROBLEM
steevo398 said:
THIS! Have you ever found a solution? I have the EXACT SAME PROBLEM
Click to expand...
Click to collapse
So you're in a TWRP loop now?
madbat99 said:
So you're in a TWRP loop now?
Click to expand...
Click to collapse
You're just all over the place, kudos to your dedication.
Basically in trying to fix the bad key/erasing boot loop I flashed twrp and tried to format data/unencrpyt which in turn throws errors which require manually reformatting /data until errors are gone and then formatting/unencrypting again which upon rebooting turns into twrp loop. Then tried to flash no-verity, the twrp loop persists.
steevo398 said:
You're just all over the place, kudos to your dedication.
Basically in trying to fix the bad key/erasing boot loop I flashed twrp and tried to format data/unencrpyt which in turn throws errors which require manually reformatting /data until errors are gone and then formatting/unencrypting again which upon rebooting turns into twrp loop. Then tried to flash no-verity, the twrp loop persists.
Click to expand...
Click to collapse
Used to have a couple of these phones .
If you're stuck in a TWRP loop
The quick workaround is to reboot to bootloader, then proceed from there to Start. However, you'll need to do this *every* time until the BCB is cleared.
To clear the BCB manually, issue this command in TWRP terminal:
Code:
dd if=/dev/zero of=/dev/block/bootdevice/by-name/misc bs=1M
have you tried formatting data, then flashing.magisk?
Hello. First i would like to state that i am a newbie on android. A few days ago i unlocked bootloader as described on this forum. Installed magisk and twrp. Everything went well, except i lost my wifi. So i googled around, and found a fix somewhere around the internet that i could install the latest firmware from Asus via twrp. So i did. No backup ofcourse? Now my phone only boots to Asus logo. Can get to fastboot menu, recover does not work, neither twrp. So i googled some more, and i am able to connect to phone with adb and fastboot commands. Also got Twrp running fastboot boot twrp.img. But i am stuck here and don’t know what to do anymore. Is my phone a lost case? Anybody out there who can guide me with solution would be apreciated?
sniken76 said:
Hello. First i would like to state that i am a newbie on android. A few days ago i unlocked bootloader as described on this forum. Installed magisk and twrp. Everything went well, except i lost my wifi. So i googled around, and found a fix somewhere around the internet that i could install the latest firmware from Asus via twrp. So i did. No backup ofcourse Now my phone only boots to Asus logo. Can get to fastboot menu, recover does not work, neither twrp. So i googled some more, and i am able to connect to phone with adb and fastboot commands. Also got Twrp running fastboot boot twrp.img. But i am stuck here and don’t know what to do anymore. Is my phone a lost case? Anybody out there who can guide me with solution would be apreciated
Click to expand...
Click to collapse
IF you're still in trouble - PM me .... will try to help
vital21 said:
IF you're still in trouble - PM me .... will try to help
Click to expand...
Click to collapse
Thanks, but i fixed it ?
sniken76 said:
Thanks, but i fixed it
Click to expand...
Click to collapse
Then you may provide a short guide here for future users who will face the same problem....
Guide?
sniken76 said:
Thanks, but i fixed it
Click to expand...
Click to collapse
Dealing with the same issue and was wondering what you did
sniken76 said:
Thanks, but i fixed it
Click to expand...
Click to collapse
guide please
Hi there. I am a a bit of a root-moron and have bricked my brand new Oneplus 6T while rooting it. Now I am stuck in a bootloop that ONLY cycles through the fastboot.
I can no longer enter into recovery mode from fastboot.
I can not use the MSM Download tool because the phone will not go into MSM Mode. Whenever I connect to the USB the phone automatically “wakes up” and immediately goes into fastboot.
When I hold the power button + volume up it just cycles through all the fastboot options and when it does eventually power down / screen goes black, it immediately powers back up and does the exact same thing.
So I simply cant get into MSM mode or recovery mode. I don’t know what to do and fear that the phone may be totally f#cked.
I welcome assistance from anyone here who actually knows what they are doing vs me who knows close to nothing. Help please!
OP6TNewb said:
Hi there. I am a a bit of a root-moron and have bricked my brand new Oneplus 6T while rooting it. Now I am stuck in a bootloop that ONLY cycles through the fastboot.
I can no longer enter into recovery mode from fastboot.
I can not use the MSM Download tool because the phone will not go into MSM Mode. Whenever I connect to the USB the phone automatically “wakes up” and immediately goes into fastboot.
When I hold the power button + volume up it just cycles through all the fastboot options and when it does eventually power down / screen goes black, it immediately powers back up and does the exact same thing.
So I simply cant get into MSM mode or recovery mode. I don’t know what to do and fear that the phone may be totally f#cked.
I welcome assistance from anyone here who actually knows what they are doing vs me who knows close to nothing. Help please!
Click to expand...
Click to collapse
First question, what exactly did you try to flash so we can get you the correct help on what to do from here.
Problem SOLVED!!!
justibasa said:
First question, what exactly did you try to flash so we can get you the correct help on what to do from here.
Click to expand...
Click to collapse
Thanks for your follow up.
Just want to let you now that I fixed it using the Stock Fastboot tool posted here
https://forum.xda-developers.com/oneplus-6t/how-to/rom-stock-fastboot-roms-oneplus-6t-t3862516
I just did exactly as instructed; my phone was already stuck in fastboot so I plugged to my PC and ran the flash-all.bat file. I really didn't think it would work because the phone did not seem to respond or do anything. I went to the toilet, came back and it was reset to factory!!!! Amazing.
Thank you so much @mauronofrio for posting this amazing tool. You saved my bricked phone! I sent you a donation for your assistance. Thanks again.
Just for future reference, as long as you can get this phone into fastboot, you should be fine. For now that's where all the flashing happens until we get a custom recovery.
But I'm glad to hear you fixed it lol
Can I just point out how bad*** of a "newb" the OP is. Dude signs up to XDA, literally makes his account name "OP6TNewb" then proceeds to give zero f**** and immediately jumps into flashing his brand new phone (as we all did once!). THEN he fixes the issue on his own using a tool he found by SEARCHING and THEN HE DONATED TO THE DEV WHO CREATED THE TOOL!!!!!
Kudos to you @OP6TNewb. All "newbs" should aspire to be like you.
Pain-N-Panic said:
Can I just point out how bad*** of a "newb" the OP is. Dude signs up to XDA, literally makes his account name "OP6TNewb" then proceeds to give zero f**** and immediately jumps into flashing his brand new phone (as we all did once!). THEN he fixes the issue on his own using a tool he found by SEARCHING and THEN HE DONATED TO THE DEV WHO CREATED THE TOOL!!!!!
Kudos to you @OP6TNewb. All "newbs" should aspire to be like you.
Click to expand...
Click to collapse
Thank you for the kind words. Donating was an easy choice because the tool saved me $650. If a guy in my situation doesn't stand up and donate to rewards you guys then who will???
Thanks again to @mauronofrio for the amazing tool and thank you to this community for allowing newbs like me to somewhat safely explore the world of android rooting & modifications.
OP6TNewb said:
Thank you for the kind words. Donating was an easy choice because the tool saved me $650. If a guy in my situation doesn't stand up and donate to rewards you guys then who will???
Thanks again to @mauronofrio for the amazing tool and thank you to this community for allowing newbs like me to somewhat safely explore the world of android rooting & modifications.
Click to expand...
Click to collapse
Out of mere curiosity, what exactly did you do to cause the device to go into bootloop anyhow?
Pain-N-Panic said:
Out of mere curiosity, what exactly did you do to cause the device to go into bootloop anyhow?
Click to expand...
Click to collapse
They probably have gone off to brag to their friends about what happened. Lol
I, too, am curious about what he did. It's been so long since I first began tinkering, but certainly remember some times I goofed.
Sent from my ONEPLUS A6013 using Tapatalk
Pain-N-Panic said:
Out of mere curiosity, what exactly did you do to cause the device to go into bootloop anyhow?
Click to expand...
Click to collapse
Hi Pain & Panic.
I was attempting to root my device following the instructions here https://www.xda-developers.com/oneplus-6t-unlock-bootloader-root/ by Adam Conway.
I was successful up to flashing the twrp img file but I made the error of flashing the wrong zip file. (blu_spark_r54-oos-pie_op6-6t_12869fe.zip ). This is bc when you follow the link to the twrp download page in Adam's instructions, the actual twrp zip file you need as per the instructions is the 10th file down the list and I didn't realize that this was important vs using the 1st zip file on the page which is the one I used. I assumed that the other files were older versions and the 1st was the most recent update that I should use. For a newb like me, this was VERY confusing.
Once I flashed the zip and rebooted to system, I got stuck in the fastboot bootloop.
While I am not 100% sure that this is what caused the problem, and maybe you will tell me that the zip file shouldn't have made a difference, but these are the steps I took.
FYI - after restoring my device using @mauronofrio's tool, I have successfully rooted my phone by following Adam Conway's steps and using the EXACT files he screenshots on the tutorial. So after a painful but educational experience, I rooted my device. Thanks again!
OP6TNewb said:
Hi Pain & Panic.
I was attempting to root my device following the instructions here https://www.xda-developers.com/oneplus-6t-unlock-bootloader-root/ by Adam Conway.
I was successful up to flashing the twrp img file but I made the error of flashing the wrong zip file. (blu_spark_r54-oos-pie_op6-6t_12869fe.zip ). This is bc when you follow the link to the twrp download page in Adam's instructions, the actual twrp zip file you need as per the instructions is the 10th file down the list and I didn't realize that this was important vs using the 1st zip file on the page which is the one I used. I assumed that the other files were older versions and the 1st was the most recent update that I should use. For a newb like me, this was VERY confusing.
Once I flashed the zip and rebooted to system, I got stuck in the fastboot bootloop.
While I am not 100% sure that this is what caused the problem, and maybe you will tell me that the zip file shouldn't have made a difference, but these are the steps I took.
FYI - after restoring my device using @mauronofrio's tool, I have successfully rooted my phone by following Adam Conway's steps and using the EXACT files he screenshots on the tutorial. So after a painful but educational experience, I rooted my device. Thanks again!
Click to expand...
Click to collapse
I forgot to mention one thing which may also be the reason. Initially, before using Adam Conways instructions, I started with the steps on High on Android (Max Lee) for the OP6 but on their download page, I mistakenly downloaded the twrp zip for the 5T and I flashed it. This initially cause the device to brick but I got it back into fastboot and into recovery and thats when I flashed the OTHER twrp file above. After I did this, I could no longer get into recover and was stuck in fastboot only.
So you can see that I made multiple errrors and I am not sure which one lead to what. Thank goodness OnePlus is friendly to rooting so I could save the phone!
OP6TNewb said:
Hi Pain & Panic.
I was attempting to root my device following the instructions here https://www.xda-developers.com/oneplus-6t-unlock-bootloader-root/ by Adam Conway.
I was successful up to flashing the twrp img file but I made the error of flashing the wrong zip file. (blu_spark_r54-oos-pie_op6-6t_12869fe.zip ). This is bc when you follow the link to the twrp download page in Adam's instructions, the actual twrp zip file you need as per the instructions is the 10th file down the list and I didn't realize that this was important vs using the 1st zip file on the page which is the one I used. I assumed that the other files were older versions and the 1st was the most recent update that I should use. For a newb like me, this was VERY confusing.
Once I flashed the zip and rebooted to system, I got stuck in the fastboot bootloop.
While I am not 100% sure that this is what caused the problem, and maybe you will tell me that the zip file shouldn't have made a difference, but these are the steps I took.
FYI - after restoring my device using @mauronofrio's tool, I have successfully rooted my phone by following Adam Conway's steps and using the EXACT files he screenshots on the tutorial. So after a painful but educational experience, I rooted my device. Thanks again!
Click to expand...
Click to collapse
Ah, I see. Looks like you flashed a kernel zip instead.
Im not a noob, but have been so out of practice with the latest Android ROMS and flashing and the changes in the partition arrangements. I managed to soft brick my phone as well and this post totally saved the day! Mauronofrio totally deserves a donation and I also gave one.
Thanks XDA! This place has saved me many times and helped me get the most of all my Android devices!
Hey guys. i am also no noob in flashing/rooting my devices.
Don thishundres of times.
Today my OP6T has shown an Magisk update (before it was 21.4 + Magisk Manager) and now it showed the popup to update -> done and error "bad image format" (i think for the kernel). Rebooted and now i am stuck in the same fastboot bootloop.
Tried to boot up TWRP with "fastboot boot tmrp.img" sadly it doesnt boot.
Any hints how i can recover my phone without wiping everything?
maybe @mauronofrio has an idea?
thx a lot
Other users facing the same issue with magisk 22, see here: https://forum.xda-developers.com/t/...oot-roms-for-oneplus-6t.3862516/post-84553217
Hi all,
I've been a silly boy and jumped into the world of rooting etc with no experience of knowledge and appear to have screwed over my phone
To cut a long story short, I updated my phone to Pie and have lost TWRP and ended up with a non-booting phone (stuck in the boot loop).
After many hours of trying to get it working, this is the latest situation -
Phone will not unlock bootloader via Mi Unlock or Fastboot command.
Can get into Fastboot and recovery (standard Android) fine.
I've cracked the phone open and can get to EDL fine and can also reapply the Pie ROM with MiFlash but after the phone has encrypted it goes back into the boot cycle.
I would really appreciate some help here as this is my daily phone and am screwed without it.
I have learnt a very important lesson here and promise never to do it again
Try latest 10.0.4.0
Mi A1 has bootloop problem try latest
tissot_images_V10.0.4.0.PDHMIXM_20190104.0000.00_9.0_2cee840c96
it has been fixed in this update. or you can try lower than 9.5.9.0, set will boot on normally but will be in bootloop if you reset or update via OTA
flash android 7.1 images via edl
get try this official android pie firmware
http://bigota.d.miui.com/V10.0.4.0.PDHMIXM/tissot_images_V10.0.4.0.PDHMIXM_20190104.0000.00_9.0_2cee840c96.tgz
Thank you all so much! The solution was to flash with the suggestion ROM.
I am very grateful and so happy that such a great resource such as this site is available.
:good:
FullMetalJumper said:
Thank you all so much! The solution was to flash with the suggestion ROM.
I am very grateful and so happy that such a great resource such as this site is available.
Click to expand...
Click to collapse
Hello!
I was recently gifted a Samsung Galaxy Tab S6 SM-P13. I only use my tablet to watch chess videos on Youtube, so I was happy to get a tablet to mess around a bit with it. I did not know much about rooting, but I thought installing Lineage OS and learning from it would be exciting.
I'm good at following instructions, but with some overenthusiasm, I realized that Lineage OS did not support my model a bit too late. So I reached step 5 of "Installing a custom recovery using heimdall" in the official instructions (https://wiki.lineageos.org/devices/gta4xlwifi/install).
But I could not do step 6 as it could not boot into recovery mode. It will stay in download mode with the following message:
<!>
_partition recovery
Reason recovery: Error verifying vbmeta image: invalid vbmeta header(6)
CUSTOM recovery
VBMETA P613XXU1AVG5, 54410278R
I have looked around to see fixes, but I have felt slightly overwhelmed. So I have installed Odin, and at this moment, as Lineage OS is not an option, I don't care which ROM to install (stock, lite, etc...).
Can someone guide me on what to do now so I won't worsen things?
Thank you for your help in advance!
Hey Pablosky000, have you tried using odin to flash stock firmware to fix it back to how it orignally was?
oFluffy said:
Hey Pablosky000, have you tried using odin to flash stock firmware to fix it back to how it orignally was?
Click to expand...
Click to collapse
Hi. Liked I said, I feel a bit overwhelmed and risk-averse at the moment. I have Odin installed and a the stock lite version downloaded. Was hoping for a "Try Odin with stock first" before making any further mistakes.
Pablosky000 said:
Hi. Liked I said, I feel a bit overwhelmed and risk-averse at the moment. I have Odin installed and a the stock lite version downloaded. Was hoping for a "Try Odin with stock first" before making any further mistakes.
Click to expand...
Click to collapse
I don't fully understand whether or not you are wanting to return it to normal or not here, but I do know about the S6 lite. I have my own S6 lite, and I noticed no one has been updating the patched files for it. A recent update forces it to have the file it was talking about, and unless someone makes a specific twrp for that device specifically, we won't be able to use a custom recovery to flash a rom.
If your issue is getting it into recovery mode however, you aren't alone. The Samsung tablet's usually have the same method for launching, but this one specifically was weird.
You have to:
1.Unplug it
2.Hold power and volume down
3. As soon as it turns off plug it back in and begin holding the recovery key buttons
4.If it isn't in recovery you may have just missed the small window you had to do it, which is fine just start from step one until it works.
If you did flash your own recovery and expected it to show the stock Samsung recovery menu, that won't happen since you overwrote it by flashing a recovery. You should be able to find your device model on https://sfirmware.com/
In odin "AP" is where you flash your recovery files. If the device isn't working you may have to also flash the "BL" or binaries for your device. I usually do anyway just to make sure it is going to work correctly. Make sure you have adb, and any Android drivers needed for it to work. Let me know if you need more help! Thanks.
oFluffy said:
I don't fully understand whether or not you are wanting to return it to normal or not here, but I do know about the S6 lite. I have my own S6 lite, and I noticed no one has been updating the patched files for it. A recent update forces it to have the file it was talking about, and unless someone makes a specific twrp for that device specifically, we won't be able to use a custom recovery to flash a rom.
If your issue is getting it into recovery mode however, you aren't alone. The Samsung tablet's usually have the same method for launching, but this one specifically was weird.
You have to:
1.Unplug it
2.Hold power and volume down
3. As soon as it turns off plug it back in and begin holding the recovery key buttons
4.If it isn't in recovery you may have just missed the small window you had to do it, which is fine just start from step one until it works.
If you did flash your own recovery and expected it to show the stock Samsung recovery menu, that won't happen since you overwrote it by flashing a recovery. You should be able to find your device model on https://sfirmware.com/
In odin "AP" is where you flash your recovery files. If the device isn't working you may have to also flash the "BL" or binaries for your device. I usually do anyway just to make sure it is going to work correctly. Make sure you have adb, and any Android drivers needed for it to work. Let me know if you need more help! Thanks.
Click to expand...
Click to collapse
Perfect!!! Thanks a lot. I didn't have much expectation apart from "not bricking it". I just wanted to make sure I did not do anything stupid. Follow your instructions. And it worked perfectly! Thanks a lot for the help! I truly appreciated. I am usually alright at a lot of these things, but I ended up being a bit lost, and just wanted to make sure I stopped doing stupid stuff!
Million thanks!!!!
I am facing a similar issue, but I can't seem to find a recovery image, so can you please help with that? I went to the sfirmware website, but can't locate the recovery image for sm-p613, though I did find it for other models such as p610. At this point, I'm fine with going stock os if it means I haven't bricked the tablet.
mr_scientific127 said:
I am facing a similar issue, but I can't seem to find a recovery image, so can you please help with that? I went to the sfirmware website, but can't locate the recovery image for sm-p613, though I did find it for other models such as p610. At this point, I'm fine with going stock os if it means I haven't bricked the tablet.
Click to expand...
Click to collapse
I softbricked mine with Snapdragon last night. See the fix and link to a working recovery image here. Developer says there's no hope for Snapdragon support for the S6 Lite Wifi now or in the future. Samsung doesn't even support the firmware reload for this device in their own Smart Switch Windows app.
deckardsdream1988 said:
I softbricked mine with Snapdragon last night. See the fix and link to a working recovery image here. Developer says there's no hope for Snapdragon support for the S6 Lite Wifi now or in the future. Samsung doesn't even support the firmware reload for this device in their own Smart Switch Windows app.
Click to expand...
Click to collapse
Thank you, I managed to get my tablet working. Really wish samsung made the firmware more available.