Database Users

[Q] Is fastboot possible?

I know fastboot isn't possible on the SG3, but the posts i found give the suggestion that it's not impossible. just not implemented yet. so my questions are:
1: is fastboot possible at all?
2: how hard would it be to implement it?
3: can i expect it to happen sometime?
thanks in advance.

Metalcookie said:
I know fastboot isn't possible on the SG3, but the posts i found give the suggestion that it's not impossible. just not implemented yet. so my questions are:
1: is fastboot possible at all?
2: how hard would it be to implement it?
3: can i expect it to happen sometime?
thanks in advance.
Click to expand...
Click to collapse
What exactly do you mean by fastboot?

neo1691 said:
What exactly do you mean by fastboot?
Click to expand...
Click to collapse
this:
"Fastboot is a command line tool used to directly flash the filesystem in Android devices from a host via USB. It allows flashing of unsigned partition images. It is disabled in production devices since USB support has been disabled in the bootloader."
from the CyanogenMod wiki

Metalcookie said:
this:
"Fastboot is a command line tool used to directly flash the filesystem in Android devices from a host via USB. It allows flashing of unsigned partition images. It is disabled in production devices since USB support has been disabled in the bootloader."
from the CyanogenMod wiki
Click to expand...
Click to collapse
i havent read any of these in forum section as yet..
Acid lestitious 2.0. Fugumod 2.2

I've seen some people talk about it, but can anyone answer the questions?

I think Fastboot is HTC only... and we already flash ROMs via Odin / CWM

zajkit said:
I think Fastboot is HTC only... and we already flash ROMs via Odin / CWM
Click to expand...
Click to collapse
some Samsung devices have fastboot, so it's not just HTC only..
and with fastboot you can do some stuff you can't with other methods, like change the boot splash (default it's the screen that says "GT-I5800 SAMSUNG")..

After some searching, it looks like very few people were able to get into Fastboot/Forced upload mode on Galaxy S. Other than that, only couple of older Samsung phones could do that. You could call your provider support and ask for directions on how to get into fastboot, but I dont think they would share that information.

zajkit said:
After some searching, it looks like very few people were able to get into Fastboot/Forced upload mode on Galaxy S. Other than that, only couple of older Samsung phones could do that. You could call your provider support and ask for directions on how to get into fastboot, but I dont think they would share that information.
Click to expand...
Click to collapse
hah, i don't think my provider would know. they don't even know the data usage of somebody, they always mess up things like that. i'd guess i'd get a response regarding garancy or something else irrelevant.

unlocked bootloader?

when i held volume down + power i was prompted with enabling the ability to install a custom OS...
does this effectively unlock the bootloader?

onicrom said:
when i held volume down + power i was prompted with enabling the ability to install a custom OS...
does this effectively unlock the bootloader?
Click to expand...
Click to collapse
That's called "Odin" mode or "Download" mode. No, at the moment and (probably not in the future either) it will not unlock bootloader.
This device is quite different from previous Samsung tablets, as I can't find the key combination nor the adb command to boot it in bootloader mode.
Any devs can shed some light on this issue?

im trying to figure out how to use this odin business ive only ever had fastboot enabled devices!
i used osx and when i boot into odin mode and spin up heimdall its not detecting my device should it?

onicrom said:
im trying to figure out how to use this odin business ive only ever had fastboot enabled devices!
i used osx and when i boot into odin mode and spin up heimdall its not detecting my device should it?
Click to expand...
Click to collapse
You have the proper drivers installed?

onicrom said:
im trying to figure out how to use this odin business ive only ever had fastboot enabled devices!
i used osx and when i boot into odin mode and spin up heimdall its not detecting my device should it?
Click to expand...
Click to collapse
Heimdall should find the device if you the latest drivers installed.
You can root the device from recovery and yes the boot loader here is "unlocked " .
Sent from my GT-P6800 using xda premium

Samsung devices do not have "fastboot" mode.
They have "download" mode. Which you can flash firmwares, kernels, modems and such with Odin and heimdall.
Also Every since the SGS2 the "bootloaders" have not been locked.

thanks to the both of you.
ive installed heimdall 1.3.1 tried both the gui and cli mode no luck finding my device. i dont have a windows machine so no odin for me
is there anything that needs to be done inside honeycomb to unlock something?

onicrom said:
thanks to the both of you.
ive installed heimdall 1.3.1 tried both the gui and cli mode no luck finding my device. i dont have a windows machine so no odin for me
is there anything that needs to be done inside honeycomb to unlock something?
Click to expand...
Click to collapse
Why no Odin for you? I have Odin on my Win 7 64x machine and Odin works fine. Make sure you are using odin 1.85. To my knowledge was the latest release.
Here is it attached so you do not have to search for it. Just unzip and use it Make sure you have drivers installed of course.

thanks for the link but no odin for me because i dont have a windows machine. only osx

Odin/Heimdal download mode is the be all-end all preventer for borkage for Samsung phones/devices. (I've had a Captivate & Infuse)
Heimdal should only show recognition when trying to flash something. Hmm. May need to look into other things if it doesn't work. :/

onicrom said:
thanks for the link but no odin for me because i dont have a windows machine. only osx
Click to expand...
Click to collapse
www.virtualbox.org

antiochasylum said:
Why no Odin for you? ...
Here is it attached ...
Click to expand...
Click to collapse
I have a feeling this attachment is no longer reachable now that Megaupload has been disabled. Do we have alternate places to host attachments now?

antiochasylum said:
Samsung devices do not have "fastboot" mode.
They have "download" mode. Which you can flash firmwares, kernels, modems and such with Odin and heimdall.
Also Every since the SGS2 the "bootloaders" have not been locked.
Click to expand...
Click to collapse
I believe only some of the original 7" Tabs had truly locked bootloaders.
The closest newer devices have is the "custom binary counter" - It trips a flag/warning if you flash something unsigned, but does not prevent it from executing.
Note that some newer Samsung devices changed the download mode protocol and broke Heimdall, although it seems to more typically be "non-Hummingbird/Exynos devices" that have issues. Heimdall won't talk to anything Tegra or Snapdragon based, but will talk to the new Tab 7 Plus. Don't know about the 7.7.
Note that some newer devices are "middle" cases where Heimdall will sort-of work but won't actually flash anything - the Galaxy Player 5.0 (and maybe 4.0 too?) are examples of this.

i havent been able to get heimdall to recognize the device... but i may be doing something silly as ive never used odin before.

I have flashed my 7.7 with odin 1.85 already and it has worked... just a heads up..
Sent from another Galaxy...
Tab 7.7

onicrom said:
i havent been able to get heimdall to recognize the device... but i may be doing something silly as ive never used odin before.
Click to expand...
Click to collapse
You have to be in download mode - if it still doesn't recognize the device in cases where Odin works, I guess that the 7.7 uses one of the newer protocols.

Entropy512 said:
I believe only some of the original 7" Tabs had truly locked bootloaders.
Click to expand...
Click to collapse
Actually this is not correct. The original 7" Tab was never in the wild with locked bootloaders. Only some leaked test firmwares had locked bootloaders - that is what all the fuss was about back then, because once you had them installed, flashing a newer or older official firmware did not remove the lock. There has never been a P1000 firmware on device in-store or an official KIES upgrade with locked bootloaders. All official firmwares have completely unlocked bootloaders.
The 8.9" and 10.1" Tab family do have unlockable bootloaders, most of them unlockable with fastboot, but on the 10.1v specifically that is only possible with some bootloader versions. There is firmware update to unlockable bootloaders, but still the device comes locked by default.
Interestingly, the Samsung-built Nexus family has an unlockable bootloader, but any use of Odin automatically unlocks the bootloader (same as fastboot oem unlock would). This is something the 8.9" and 10.1" Tab family does not do, you need to unlock first (if I'm not mistaken).
The 7.7" is based on the SGS2/SGNote family of device, which is a completely different heritage from the 8.9 and 10.1 family. The other Exynos based devices are completely unlocked out of the box - I assume the same is true for the 7.7 ?
(Note the subtle differences in this comment between: (a) locked bootloader (b) unlockable bootloader and (c) unlocked bootloader)

OK, I had my history wrong on the original Tabs.
I haven't seen any way to unlock the 10.1 once you got SBK-locked - but the SBK lock only affects flashing with nvflash. So maybe that would be a "locked flasher?" I have never seen the 10.1 perform any enforcement of code signing when booting stuff that has already been flashed.

Entropy512 said:
OK, I had my history wrong on the original Tabs.
I haven't seen any way to unlock the 10.1 once you got SBK-locked - but the SBK lock only affects flashing with nvflash. So maybe that would be a "locked flasher?" I have never seen the 10.1 perform any enforcement of code signing when booting stuff that has already been flashed.
Click to expand...
Click to collapse
Exactly that is what has happened to my 10.1v, it seems, just yesterday as luck would have it.
(Might be only the v variant does that, though)

Chainfire said:
Exactly that is what has happened to my 10.1v, it seems, just yesterday as luck would have it.
(Might be only the v variant does that, though)
Click to expand...
Click to collapse
Maybe - as I understand it the v is quite different from the stock 10.1.
The 10.1 non-v has its own set of annoying variants though - Wifi, 3G, Verizon LTE, and one other one. Plus the Google I/O versions had some slight differences from the Wifi (I think they have a slightly different .pit, which is why fastboot can't easily be flashed on non-I/O wifi units.)
For the non-v - You can get SBK-locked if you're not careful. What's annoying is that SBK-locking actually makes Samsung MORE likely to have to offer warranty service - if a device isn't SBK-locked, it's completely unbrickable, as nvflash capability is built into the CPU itself (Just like GalaxyS phones with Unbrickable Mod, and the 5 inch Galaxy Player/Galaxy S Wifi units). If it's SBK-locked - well, if you corrupt the bootloaders and disable Odin mode you're toast, since nvflash won't work. Somewhere around 50% of the initial 10.1 wifi units shipped without SBK locks, but all of them shipped locked eventually and then if you weren't careful, various OTA updates would burn the eFuses for SBK locking if they weren't already burned.

Xiaomi Redmi Note 5.5 2Gb ram 2014 dual sim 3 G. Bricked with no excuse: xposed

It happened long ago in a foggy noon....leaving xiaomi, uncle tools. Miui to an hour of persistence.
Never mastered any Chinese phone. Visited Xiaomi foruns but never solve the brick. Today tried a method involving a "fastboot flash recovery recovery.img" wich should allow twrp img to unbrick by installing a file uninstalling any remains of xposed framework. and recovering. Pdanet involved could not conect with one end...:crying: Last but not the least, it was a solution directed towards a redmi 1 S, not a redmi Note. When decided to photograph for parts, it appeared a menu at the top. Stock recovery? Miui? Sorry for the inconvenience. Xiaomi are great devices. Any suggestions, a qualified opinion, is there a path to recover functionality, considering the level of complexity...
Thank you. Compliments and sorry for the inconvenience

The photo is a typical MTK chipset Engineering mode, nothing useful for you there.
Follow the instructions in the following page: http://en.miui.com/thread-64425-1-1.html
Except download the latest fastboot rom for your device from here: http://en.miui.com/thread-262691-1-1.html

http://en.miui.com/thread-64425-1-1.htmlhttp://en.miui.com/thread-262691-1-1.html Both should answer the question, and I believe they did, Flashtool scattered the FastbootRom and all, except the driver question, went well. Using the tool developed at xda foruns, connecting the phone, one item remained_usb debugging. And that, considering the existence of a flashtool for Linux, is another tour. http://en.miui.com/thread-262691-1-1.html The fact of legacy drivers in Windows 10 were not certified, lead to another path...Options it must exist for a device that turns on, just? does not boot...

bjpafa said:
involving a "fastboot flash recovery recovery.img"
Click to expand...
Click to collapse
As I see you didn't flash recovery at all. Can you tell me what and how did you flash that recovery.img? Which recovery did you use, where did you put recovery.img file? Maybe to paste full trace from your console?

Blade A3 Prime (Visible)

Doing anything listed here will void your warranty. I don't know the laws where you are so assume it makes you a criminal. These things are posted here for educational purposes only. Never follow any guide if you don't understand the commands.
Enough BS, let's jump in.
For windows users. Installing drivers:
1. Plug USB cable into PC.
2. On the A3 prime, instead of using USB as charging, select use USB as Updating Firmware (i forget actual wording)
3. A prompt will come up on Windows, install those drivers.
4. Reboot.
Install adb and fastboot on your PC, it is up to you to do this.
Enable developer options on your phone, and enable USB debugging and OEM Unlocking.
In your CMD/Shell/Whatever you have.
adb reboot bootloader
fastboot flashing unlock (use volume up to confirm)
fastboot flashing unlock_critical (use volume up to confirm)
Congrats you've unlocked the bootloader.
Use 'fastboot reboot' to reboot if you haven't done so already.
-----
this is where the progress on this device comes to a halt.
The kernel source is available from opensource.ztedevices.com
The device codename is Z5157V, the Kernel they have is listed under Z5157V Q(10) Kernel(4.4.185)
What needs to happen next? Someone needs to compile the kernel from source.
Once that is done, they can extract the boot.img from it, use Magisk, and make a modified boot.img
Whoila, they will now have root. Once this person has root, they can extract recovery.img from the device, and we can begin making a custom TWRP, or who knows, maybe Team Win will pick it up (unlikely).
Once we have a custom recovery and working Magisk, it's just a matter of time before we start seeing custom ROMS.
If someone will sign up to be a guinea pig, or has an extra A3 Prime laying around I will continue development. I bricked mine because I was impulsive and honestly, kinda stupid. (browse through thread to see my idiocy)
Until such a time that I come to possess another A3 Prime OR someone steps up to provide a firmware dump, I am unable to help.
Good luck developing!

Only managed to unlock the bootloader but can't seem to find any information on rooting it.
The structure is indeed different than what you would normally expect to find. 'recovery' isn't a valid partition when trying to flash under fastboot for example.
The only reason I'm interested in trying to root this device is because The mtk engineering mode app doesn't work on this phone, at least not the visible version, so band locking doesn't seem possible without root and a different rom.

Yeah, I bricked my device by flashing a universal MTK TWRP.
Came here to say this, do not flash universal MTK.
It is a soft brick, bootloops with no access to stock or TWRP recovery.
The phone's model number is Z5157V and the stock firmware is Z5157VV1.0.0B17 for google indexing reasons. Only place that MAY have it is behind a $40 pay wall.

Managed to get the kernel from opensource.ztedevices.com, just beginning to work on it now (not sure how I'm gonna get my phone out of bootloop mode, but I'll solve it later)

I have never compiled a kernel from source, but I'm eager to learn, I have two days in the wilderness planned ahead of me. If anyone would compile the kernel, that is great. If not? I'll get it done when I get back.
Been playing around with the phone and key combinations, I think I have found a way to use SP Flash Tool in it's current soft brick state.
If I am successful in compiling the kernel, I will share it.
If I am able to unbrick this phone, I will write a guide.
If those two things happen, I'll be moving forward to make an AOSP based custom ROM for this phone. Maybe a first for a $100 device, but I like root.
If anyone else knows HOW to compile the kernel, you'd put me a few steps ahead when I get back.
Either way, nearly 200 lurkers on this thread, I hope to have answers soon.

ORANGE
zaduma said:
I was able to unlock the bootloader. Confirmed with a boot message on boot.
Click to expand...
Click to collapse
how does that bootmessage read?
does it say : "ORANGE STATE" et cetera ?

s4goa said:
how does that bootmessage read?
does it say : "ORANGE STATE" et cetera ?
Click to expand...
Click to collapse
Yeah
Orange State
Device can't be trusted
Booting in x seconds

1st.
zaduma said:
to make an AOSP based custom ROM for this phone. Maybe a first for a $100 device, but I like root.
Click to expand...
Click to collapse
why do you think you are first ? their are literally tons of €100 phones in circulation!

s4goa said:
why do you think you are first ? their are literally tons of €100 phones in circulation!
Click to expand...
Click to collapse
Who knows, guess I don't have much experience in this area. (Cheap phones) Figured it's usually not worth it to do all this work for a throwaway phone.
That said, I've been wrong before!

zaduma said:
Yeah
Orange State
Device can't be trusted
Booting in 5 seconds
Click to expand...
Click to collapse
same here after
Code:
fastboot flashing unlock_critical
(bootloader) Start unlock flow
FAILED ()
Finished. Total time: 21.830s

s4goa said:
same here after
Code:
fastboot flashing unlock_critical
(bootloader) Start unlock flow
FAILED ()
Finished. Total time: 21.830s
Click to expand...
Click to collapse
Strange it fails, try flashing unlock first, then flashing unlock_critical, make sure to press volume up on phone when prompted.

fastboot
dude, in order to avoid fuqqing confusion you ought not abbreviate a shell command like you do.
Anyhow, since we two guys have different phones, it makes sense only for me to generally discuss the rooting strategy on a ZTE Spreadtrum phone, as the specifics will differ too much.
I have fastboot on a Lumigon T3 as my "ZTE blade A5 2019" does not have fastboot.
---------- Post added at 16:07 ---------- Previous post was at 15:55 ----------
rooters, come join https://forum.xda-developers.com/group.php?groupid=1925

s4goa said:
dude, in order to avoid fuqqing confusion you ought not abbreviate a shell command like you do.
Anyhow, since we two fuys have different phones, it makes sense only for me to generally discuss the rooting strategy on a ZTE Spreadtrum phone, as the specifics will differ too much.
I have fastboot on a Lumigon T3 as my "ZTE blade A5 2019" does not have fastboot..
---------- Post added at 16:07 ---------- Previous post was at 15:55 ----------
rooters, come join https://forum.xda-developers.com/group.php?groupid=1925
Click to expand...
Click to collapse
Sorry, for clarity if on Linux type su and your root password, or use sudo to escalate your permissions if you don't have permission to use fastboot as a regular user.
If you're on windows, consider a free upgrade, but also leave out sudo and once in fastboot mode on a3 prime, type
1. (sudo) fastboot flashing unlock
2. (sudo) fastboot flashing unlock_critical
Press volume up when prompted and congrats your warranty is now void, bootloader unlocked. I'm not responsible for your choices.
__________
Also yeah, the phones even have different chipsets the Z5157V is a MTK phone

fastboot
this "orange state unlock bootloader" has - however - nothing or little to do with "Developer Menu option UNLOCK BOOTLOADER"
do you know more about this?
on my Lumigon these 2 unlockings are independent of each other, never mind the identical name "unlock bootloader".

s4goa said:
this "orange state unlock bootloader" has - however - nothing or little to do with "Developer Menu option UNLOCK BOOTLOADER"
do you know more about this?
on my Lumigon these 2 unlockings are independent of each other, never mind the identical name "unlock bootloader".
Click to expand...
Click to collapse
Yeah, you'll need to toggle that option to on in Developer Settings before entering the bootloader/fastboot mode and running the unlock commands or they will fail.

we're screwed !
dude, dammit! they cryptosign bootloaders now LINK
if that is true we're done for! how to hack those cryptochips?
its for Unisoc SC9863A Spreadtrum but also other CPUs.
zaduma said:
:crying:
Click to expand...
Click to collapse

s4goa said:
Click to expand...
Click to collapse
Well, I am terribly sorry to hear that, but at least the A3 prime is on mediatek chipsets which I don't believe has any such protection.

Spreadtrum SC9832E, 64bit
zaduma said:
the A3 prime is on mediatek chipsets
Click to expand...
Click to collapse
if you are sure that boot.img can be "modded" then the A3 is a superior phone, let me tell you.
---------- Post added at 22:54 ---------- Previous post was at 22:50 ----------
anyway... its kewl u posted at https://www.gizmochina.com/2020/07/01/zte-blade-a3v-key-specs-leak/

s4goa said:
if you are sure that boot.img can be "modded" then the A3 is a superior phone, let me tell you.
---------- Post added at 22:54 ---------- Previous post was at 22:50 ----------
anyway... its kewl u posted at https://www.gizmochina.com/2020/07/01/zte-blade-a3v-key-specs-leak/
Click to expand...
Click to collapse
Keep checking for updates, once I'm back in town that's exactly what I'll be working on.

Sorry to anyone following this thread, I will continue working on building the kernel, extracting boot, and getting this phone rooted. I will need a volunteer to test the root solution once it is built, and then if possible follow a few steps and extract recovery.img on your newly rooted device and send that to me.
I just don't have the time today even though I said I would be doing it. If there are any volunteers with an A3 prime let me know!

SM-P613. Error vbmeta image.

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.