Database Users

[Q] How (im)possible is it to brick the N4?

As long as you can get into fastboot mode, you haven't bricked your device
Click to expand...
Click to collapse
Is this statement true?
I know it isn't impossible to brick your device to the point of no return. I've actually done it myself (huray!) with my Nexus S. It was declared dead even by AdamOutler himself, the maker of the Unbrickable Resurrector. After trying to unbrick it myself, I sent it to him. Apparently I screwed up the radio, a mistake which is impossible to recover from. Don't ask me how I did it... I did flash something before, but my phone worked fine for a while. Only then the battery drained really quickly. When it was dead and I plugged in the charger, it booted up fine, but the moment I started the browser my Nexus S died. Forever. RIP.
I guess it's no different with the N4. If you screw up the radio, you have a problem. Can somebody confirm this? And are there other ways to brick your phone to the point of no return?
I think it's kind of stupid that you are able to brick your phone. You can't brick a PC, can you? That's just impossible. You can ALWAYS completely reset everything. Well, not with Android apparently. I think it's weird that even with Nexus devices, there's still a way to brick it. I guess you need to be stupid like me to brick a Nexus device, but still... it shouldn't be possible.

Yes as long as bootloader mode is able to be started! You cannot brick. Just flash google stock factory images.
Sent from my Nexus 4 using xda premium

Its because Android phones are dependant on the Bootloader, whereas a PC is dependant on the BIOS and CMOS. If you fail at flashing a BIOS then you brick the motherboard. So you technically can brick a PC.

Hah, I've bricked PC's with BIOS flash fails.
But as for the phone, as long as you can enter fastboot, you are able to recover.

Harry GT-S5830 said:
Its because Android phones are dependant on the Bootloader, whereas a PC is dependant on the BIOS and CMOS. If you fail at flashing a BIOS then you brick the motherboard. So you technically can brick a PC.
Click to expand...
Click to collapse
You can? Ah, then I rest my case.
I did screw up the radio though, and not the bootloader. I was able to get into download mode using the resurrector tool, only the screen stayed black.\
by the way, I don't think the Bootloader is the same as the BIOS. If it was, then you would technically be able to flash anything on your phone, even Windows. It isn't split up like the BIOS and Windows. Correct me if I'm talking nonesense by the way ;p.

You could think of it as the bootloader = the BIOS and Android = Windows

Androyed said:
[snip]
by the way, I don't think the Bootloader is the same as the BIOS. If it was, then you would technically be able to flash anything on your phone, even Windows. It isn't split up like the BIOS and Windows. Correct me if I'm talking nonesense by the way ;p.
Click to expand...
Click to collapse
You technically could flash anything on your phone, assuming you had the right bootloader and partition table and the right drivers. The issue is that the bootloader on an Android device is designed to boot (i.e., load into RAM ) a Linux kernel. It isn't designed to (and hence, won't) boot a Windows, or any other, kernel.

You could always delete your bootloader, thall brick your device pretty fast

efrant said:
You technically could flash anything on your phone, assuming you had the right bootloader and partition table and the right drivers. The issue is that the bootloader on an Android device is designed to boot (i.e., load into RAM ) a Linux kernel. It isn't designed to (and hence, won't) boot a Windows, or any other, kernel.
Click to expand...
Click to collapse
Very true. For an example, Check out the HD2 phone and the various bootloaders available for it. I have booted Windows Mobile 6 and 7, Ubuntu, oh.. and Android on it. It was originally a WM6 phone. It also has the ability to change partition sizes, and has an sBoot partition so it can do a true dual boot. One from Nand memory and one from SD card with just a reboot.
I waiting to see if we get a way to flash unsigned bootloaders on Nexus 4 (or get a key).

I seem to recall a few devices being bricked in the few days after release. There was a problem with the faux kernel that caused the device to totally and irreparably brick if one overclocked (to 1.8Ghz I think) and then ran an antutu benchmark.
The few could not recover from the brick despite a lot of suggestions thrown around and some even from the dev of the kernel. Ultimately, they RMA'd.

Have a look at this thread: http://forum.xda-developers.com/showthread.php?t=2011328
Many users seen to have bricked their devices by overclocking their CPUs and running benchmarks.
Heck, I even see people talking about the red LED problem daily. Something's clearly not right...
Sent from my Nexus 4 using Tapatalk 2

The red led problem clearly appears too frequently... it really has to be cleared up what the heck is causing it.

Lownita said:
The red led problem clearly appears too frequently... it really has to be cleared up what the heck is causing it.
Click to expand...
Click to collapse
The red led bug is most likely hardware related.
Just think about it. Overclocking draws significantly more power. The nexus 4 isn't even able to supply the power for USB host, so it might be some kind of power failure.
Or simply a shorted circuit.

Nuu~ said:
The red led bug is most likely hardware related.
Just think about it. Overclocking draws significantly more power. The nexus 4 isn't even able to supply the power for USB host, so it might be some kind of power failure.
Or simply a shorted circuit.
Click to expand...
Click to collapse
There is the point.
Bricking by software alone will be almost impossible. I have seen a few flashing bricks recovered already.
Bricking by damaging the hardware, well, that is probably unrecoverable. Over Clocking or O/C + Over-Heat is causing what seems to be permanent damage in some phones.

fastboot mode on nexus 4 says "secure boot: on" --- anyone knows what that means? afair i havent seen that on my old gnex and nex7.
and is it possible to use download mode to flash a new bootloader in case the old one is corrupted?

I don't think anyone has the QCOM_USB_DLD mode figure out yet and I don't think anyone knows what secure boot does either, I know originally people blamed it for custom recoveries being reverted, but that's just a script that's called on bootup.

molesarecoming said:
fastboot mode on nexus 4 says "secure boot: on" --- anyone knows what that means? afair i havent seen that on my old gnex and nex7.
and is it possible to use download mode to flash a new bootloader in case the old one is corrupted?
Click to expand...
Click to collapse
I've seen that on my Nexus S... after I had bricked it completely ;p. I don't think it had anything to do with the brick though. It's something from HTC devices: http://www.addictivetips.com/mobile...on-htc-android-phones-with-unrevoked-forever/. At least I think so.
When I tried to repair my bricked Nexus S, I asked if it had something to do with secure: on. They didn't know what it was exactly, so maybe it isn't the same as s-on on HTC devices.

molesarecoming said:
fastboot mode on nexus 4 says "secure boot: on" --- anyone knows what that means? afair i havent seen that on my old gnex and nex7.
Click to expand...
Click to collapse
Pure speculation on my part: I think that the "secure boot: on" relates to the boot chain of the Snapdragon SoC. When it's on, I think that it will not boot an unsigned bootloader, and hence you cannot boot the device. Similar to, but not quite the same as, S-ON for HTC devices as was mentioned above.
molesarecoming said:
and is it possible to use download mode to flash a new bootloader in case the old one is corrupted?
Click to expand...
Click to collapse
More speculation: I haven't had much time to look into it yet, but I'm guessing that you should be able to flash a .tot file (an LG "factory image" I think like the ones found here) while you are in download mode. I think it requires something like the LGNPST tool with the right .dll. This is my first LG device (and my first Snapdragon SoC), so I'm still in the reading/learning stages.

Advent tegra note 7 stuck on boot

Hi, I recently got my brand new advent tagra note 7 and I updated the system to 4.4.2 (OTA) and then used the super tool 2.1 to root the device and also have flashed the CWM recovery.
Every thing was ok for a while, but when i noticed the tablet some how got freezed so I forced a reebot holding the power button.
Since then, i'm stuck on boot.
I've tried to restore with super tool with no success. I still have fastboot ad CWM recovery, but I can't "adb sideload"
Can anybody help me, since I'm about to return the tablet and I'm affraid they won't accept it since i have unlocked the bootloader hence garanty is voided

747170 said:
Hi, I recently got my brand new advent tagra note 7 and I updated the system to 4.4.2 (OTA) and then used the super tool 2.1 to root the device and also have flashed the CWM recovery.
Every thing was ok for a while, but when i noticed the tablet some how got freezed so I forced a reebot holding the power button.
Since then, i'm stuck on boot.
I've tried to restore with super tool with no success. I still have fastboot ad CWM recovery, but I can't "adb sideload"
Can anybody help me, since I'm about to return the tablet and I'm affraid they won't accept it since i have unlocked the bootloader hence garanty is voided
Click to expand...
Click to collapse
I don't know much about rooting the Tegra 7. Can you use Odin with it?

spookme said:
I don't know much about rooting the Tegra 7. Can you use Odin with it?
Click to expand...
Click to collapse
I don't think we can use Odin with this tablet, since it's for samsung devices...

spookme said:
I don't know much about rooting the Tegra 7. Can you use Odin with it?
Click to expand...
Click to collapse
I'm sorry but where in the earth have you seen people using Odin with non-samsung devices? You're basically begging for a brick.

perez6991 said:
I'm sorry but where in the earth have you seen people using Odin with non-samsung devices? You're basically begging for a brick.
Click to expand...
Click to collapse
Ha - only ever had Samsung devices before the Tegra 7, hence the silly question! I now feel better educated. It's a shame because it helped me get out of a few sticky situations with my S2 and 7.7. Thanks 747170 for your polite correction. Also thanks perez6991 for your offer of a brick, but I think I'll pass.

spookme said:
Ha - only ever had Samsung devices before the Tegra 7, hence the silly question! I now feel better educated. It's a shame because it helped me get out of a few sticky situations with my S2 and 7.7. Thanks 747170 for your polite correction. Also thanks perez6991 for your offer of a brick, but I think I'll pass.
Click to expand...
Click to collapse
You're welcome. odin also saved me a cople of times in the past with my samsung s2/s4 tab10.1

[Q] Unsuccessful reflash of Homecare Fly One Note7

Hello guys.
I would like to ask you for help with my bricked Homecare. I apparently cocked up the flashing process and now I don't know, how to proceed.
What I did:
At first I used the Russian (translated) version of supertool designated for Homecare Note 7. But the process wasn't 100 % successful. The bootloader has been unlocked, CWM recovery has been flashed, ROM 4.3 has been flashed. The tablet was able to boot, but it always froze after a few minutes of operation. Most probably there was a wrong boot flashed. No idea.
So, I checked the forums and RootJnky's videos and decided to use CWM to flash a deodex 4.3 stock ROM.
Flash process was successful, but after restart the tablet remains in boot-loop.
Now, I was NEVER able to enter the Recovery or Bootloader using the button combination. Don't ask me why, but it wasn't possible. I could however access recovery or bootloader using ADB.
Right now the only status except a boot-loop is the APX mode. Is there still a chance how to unbrick the tablet???
Thanks for any advice.
Jaro

jardam.cz said:
Now, I was NEVER able to enter the Recovery or Bootloader using the button combination. Don't ask me why, but it wasn't possible. I could however access recovery or bootloader using ADB...Jaro
Click to expand...
Click to collapse
At worse case scenario you need to use APX mode to reflash. You can get the download references for the APX files, particularly the package from Advent UK. The package is setup for Windows but it's easy to use in Linux with their executables.
The APX mode does reflash your tablet in whole, but the end result may not be perfect, but should allow a stepping stone to fastboot mode.
If you can obtain 'fastboot' mode then your can reflash partitions. The 'adb' mode in recovery level or system level will allow for updates with 'sideload' command.
Hope that helps.

e8hffff said:
At worse case scenario you need to use APX mode to reflash. You can get the download references for the APX files, particularly the package from Advent UK. The package is setup for Windows but it's easy to use in Linux with their executables.
The APX mode does reflash your tablet in whole, but the end result may not be perfect, but should allow a stepping stone to fastboot mode.
If you can obtain 'fastboot' mode then your can reflash partitions. The 'adb' mode in recovery level or system level will allow for updates with 'sideload' command.
Hope that helps.
Click to expand...
Click to collapse
@e8hfff I managed to sort him out yesterday using the APX method the use has now got it working, with no issues at all (WiFi works as well).
The only thing different for him is that his Generic bootanimation which Xolo Tegra Note 7's have is now showing advent.
I will send you a PM in a bit out the bootanimation as i have a idea LOL.

hacktrix2006 said:
@e8hfff I managed to sort him out yesterday using the APX method the use has now got it working, with no issues at all (WiFi works as well).
The only thing different for him is that his Generic bootanimation which Xolo Tegra Note 7's have is now showing advent.
I will send you a PM in a bit out the bootanimation as i have a idea LOL.
Click to expand...
Click to collapse
Hi hacktrix2006.
Thanks for the help again. The tablet is working like dream. All my Chinese colleagues are staring at it. The poor guys know only the products of the fruit company (Apple).
I saw the boot animation is a set of pictures in the flash package from Advent. It is ZIPed.
Is there any way how to make and flash a boot animation without reflashing the whole thing? (I know the answer already, but I don't know how to do it DD)

jardam.cz said:
Hi hacktrix2006.
Thanks for the help again. The tablet is working like dream. All my Chinese colleagues are staring at it. The poor guys know only the products of the fruit company (Apple).
I saw the boot animation is a set of pictures in the flash package from Advent. It is ZIPed.
Is there any way how to make and flash a boot animation without reflashing the whole thing? (I know the answer already, but I don't know how to do it DD)
Click to expand...
Click to collapse
The bootanimation.zip is in /lbh partition under media. Should be a easy enough to copy and paste in if not then i will have a look for a way of doing it without flashing all of it again.

Docs on Homecare Fly One rom update
Hi jardam.cz AND hacktrix2006
I see you guys have a working method to update the Homecare Fly One - do you have any documentation on how to root and update the rom for this model? Jardam mentioned a Russian rom, but it caused problems. I really don't want to brick this, as I live and breathe with this tablet every day! But I can't stand the limitations of no root.
Almost all the YouTube videos show EVGA solutions, and lots of people have Homecare Fly One problems - what's the solution please?

They are all the same base nvidia model which is p1640 the lbh partition is wrote when flashing via apx mode which can be risky. However there is a twrp recovery for our device and a stock 4.4.2 image from tom you can use to flash a generic version if the os.

Potential To Recover Note 4 Bootloader After Flashing Retail Firmware

***Updated: 04/09/2015
First, thank you BeansTown106 and ryanbg for previously sharing the information and technical expertise that has led to successful development of the "tool" that ultimately provides the means to recover a locked bootloader on the Note 4 Developer Device. Without your help and expertise this "tool" may never have been developed.
UDATE: 04/09/2015---There is now a step by step guide that will take you through a process that produces a flashable aboot recovery file for the Developer Edition bootloader if it becomes locked (by flashing retail firmware for instance). This backup MUST be done BEFORE your bootloader becomes corrupted and locked. It is strongly recommended that if you own a Developer Edition Note 4 that you take the time to make a backup of your aboot. This link will take you to a step by step process with links to the couple of files you will need.: http://forum.xda-developers.com/note-4-verizon/general/guide-vzw-note-4-backup-developer-t2962911. Thank you radionerd for the guide and again to BeansTown106 and ryanbg.
Most of us have heard or read about Developer Edition owners of the S4 or S5 that inadvertedly flashed a retail firmware or ROM that was not intended (safe) for the Developer Edition consequently turning their Developer Edition phone into a retail edition phone...locked bootloader. I want to emphasize that this method of recovering a Developer Edition bootloader has been tested and has recovered several Note 4 DE devices whose bootloaders were locked (purposely or inadvertently).

I always found it amazing that people flash ROMs for the wrong device. saw it a lot in Note 2 forums.
Can't believe people can be that careless...especially someone that goes so far as to buy a developer edition. Measure twice...cut once.

tfly212 said:
I always found it amazing that people flash ROMs for the wrong device. saw it a lot in Note 2 forums.
Can't believe people can be that careless...especially someone that goes so far as to buy a developer edition. Measure twice...cut once.
Click to expand...
Click to collapse
Yep, I don't understand either, but it happens.

jpcalhoun said:
Yep, I don't understand either, but it happens.
Click to expand...
Click to collapse
Yeah my Dev edition note 3 got ruined with running "nvbackup" so as a last resort i purposely flashed a retail rom hoping that would just make it work even though it would be locked...

This makes one start to wonder if we could then take a retail version and make it dev as well. If all the hardware is identical and the main difference is the unlocked bootloader..
Fastboot option is not available, but again, hardware being identical, this theoretically should be possible.

gatesjunior said:
This makes one start to wonder if we could then take a retail version and make it dev as well. If all the hardware is identical and the main difference is the unlocked bootloader..
Fastboot option is not available, but again, hardware being identical, this theoretically should be possible.
Click to expand...
Click to collapse
Ive tried to push a DE aboot to the retail Note 4. I can not get it to even write. Ive tried ODIN and ABD to push it. Any suggestions?

mrlaigle said:
Ive tried to push a DE aboot to the retail Note 4. I can not get it to even write. Ive tried ODIN and ABD to push it. Any suggestions?
Click to expand...
Click to collapse
Well, that's kind of my whole point I was being a little sarcastic. With a locked bootloader, lets just say Read-Only, you cannot really overwrite something RO that has already been loaded per say... You would have to be able to fastboot, from my experience, in order to be able to do that. Now if they are signing it, if we could somehow impersonate the key and resign with a newer version number that might work, because they probably have allowances for signed updates.
To me, that might be the only way of resolving this whole locked bootloader issue in general. They obviously have the ability to update them, so we need to figure out how to sign it somehow and or understand their conditions. Meaning, what if they are already planning the next planned bootloader version coming within the existing one. So in this case, if it doesn't match what is expected on the check it will fail along with the fact the signature is not correct.

mrlaigle said:
Ive tried to push a DE aboot to the retail Note 4. I can not get it to even write. Ive tried ODIN and ABD to push it. Any suggestions?
Click to expand...
Click to collapse
Have you tried it from the phone useing Terminal Emulator and the su command?

I could only copy aboot.bak via terminal emulator. I couldn't get through with CMD in windows 7. (I have only copied the file.)

It will not work... The tell tale sign is all of the capable devs of possibly accomplishing this moved on to Tmo or quit developing all together. Loosing Hashcode was a major blow to the dev community.

droidstyle said:
It will not work... The tell tale sign is all of the capable devs of possibly accomplishing this moved on to Tmo or quit developing all together. Loosing Hashcode was a major blow to the dev community.
Click to expand...
Click to collapse
Not all have given up yet ... I am still hard at it.. Ye of little faith..

If anyone wants to send me an image of their aboot for research purposes, it'd make my day

ryanbg said:
If anyone wants to send me an image of their aboot for research purposes, it'd make my day
Click to expand...
Click to collapse
PM sent

wy1d said:
PM sent
Click to expand...
Click to collapse
anyway i can one too/??

larrycjr said:
anyway i can one too/??
Click to expand...
Click to collapse
I'm not certain that p6 is the aboot. I'm thinking it may be p7. I've asked for verification in the other thread.

is there an odin file for the developer edition device? if so will someone direct me there??

larrycjr said:
is there an odin file for the developer edition device? if so will someone direct me there??
Click to expand...
Click to collapse
No there isn't. That is what we are all looking for. Samsung hasn't released one and I'm not sure how to make one from the retail version by replacing the aboot.

wy1d said:
No there isn't. That is what we are all looking for. Samsung hasn't released one and I'm not sure how to make one from the retail version by replacing the aboot.
Click to expand...
Click to collapse
Well, we could do a dd if, blah blah blah and back up the partition once rooted, but this is not really what we want, because we want a factory clean, fresh partition. Not a modified boot, root, recovery etc... Can you guys connect to Kies on the developer addition and do a firmware upgrade and reinitialization option on the tools menu. Because this, would in fact, call out and download the whole image for the phone where you could snag it before it started trying to commit it to the phone. That is essentially what I did to get the factory image for the retail phone.

gatesjunior said:
Well, we could do a dd if, blah blah blah and back up the partition once rooted, but this is not really what we want, because we want a factory clean, fresh partition. Not a modified boot, root, recovery etc... Can you guys connect to Kies on the developer addition and do a firmware upgrade and reinitialization option on the tools menu. Because this, would in fact, call out and download the whole image for the phone where you could snag it before it started trying to commit it to the phone. That is essentially what I did to get the factory image for the retail phone.
Click to expand...
Click to collapse
I've tried that. It says there is no image available for the phone. I've also gone to the Mosaic kiosks (Samsung inside Best Buy) and they use a different tool called Samsung Smart tool to reflash phones. They also do not have an image for the DE Note 4. I've also talked to Support and Advanced Tech at Samsung - both do not have the image. Finally I've talked to the Samsung repair depot and they also do not have the image. On a whim, I also got pretty high up in Verizon tech support asking them if they had an image. They do not support the DE device (as we know) and also didn't have an image.

wy1d said:
I've tried that. It says there is no image available for the phone. I've also gone to the Mosaic kiosks (Samsung inside Best Buy) and they use a different tool called Samsung Smart tool to reflash phones. They also do not have an image for the DE Note 4. I've also talked to Support and Advanced Tech at Samsung - both do not have the image. Finally I've talked to the Samsung repair depot and they also do not have the image. On a whim, I also got pretty high up in Verizon tech support asking them if they had an image. They do not support the DE device (as we know) and also didn't have an image.
Click to expand...
Click to collapse
Well....... I would say you covered all the bases... lol

Can't see in Fastboot Mode the Tablet listed in Fastboot devices.

Sry, can you help me?
I've got the Samsung Galaxy Tab A 8 (2019) and I wanted to flash TWRP on it.
When It's on System, it's easy to Code: "adb devices", but after "adb reboot bootloader" i can't show it listen in by typing Code "fastboot devices".
Mfg JonnyBoy1984

JonnyBoy1984 said:
Sry, can you help me?
I've got the Samsung Galaxy Tab A 8 (2019) and I wanted to flash TWRP on it.
When It's on System, it's easy to Code: "adb devices", but after "adb reboot bootloader" i can't show it listen in by typing Code "fastboot devices".
Mfg JonnyBoy1984
Click to expand...
Click to collapse
That is because Samsung devices don't support fastboot. There are some custom recovery modules that add it, but you need to use Odin or Heimdall to flash from download mode on stock devices.

Can somebody help me to flash twrp with this guide?
TWRP - ROOT - WETAmod for SM-T295 (Tab A 8.0 2019)[Updated 22 February 2022]
THIS THREAD IS DISCONTINUED - AM GETTING TOO OLD TO CONTINUE WETAmod FOR T295 I see people still trying to patch files to get root. If you flash the TWRP posted by @Talich52, with reboot unchecked you can install Magisk from TWRP. Tested on...
forum.xda-developers.com
?
I am German and I Always to the steps wrong.
Maybe in German, or so that I can understand, please.
JonnyBoy1984

It could be your fastboot isn't the newest. It's been a while but I had the same problem, once you get the correct fastboot files it should work.

lewmur said:
That is because Samsung devices don't support fastboot. There are some custom recovery modules that add it, but you need to use Odin or Heimdall to flash from download mode on stock devices.
Click to expand...
Click to collapse
Some Samsung deviecs have fastboot as well.

mfn003 said:
Some Samsung deviecs have fastboot as well.
Click to expand...
Click to collapse
I have been putting customs ROMs on Samsung devices for close to ten years. I currently have a T500 and an S6 Lite. The S6 has fastboot but only because of the custom recovery. There might be some of the very latest ones that Samsung included fastboot in order to support GSI, but I haven't seen one. And the SM-T295 isn't one of them

lewmur said:
I have been putting customs ROMs on Samsung devices for close to ten years. I currently have a T500 and an S6 Lite. The S6 has fastboot but only because of the custom recovery. There might be some of the very latest ones that Samsung included fastboot in order to support GSI, but I haven't seen one. And the SM-T295 isn't one of them
Click to expand...
Click to collapse
I know, but some Samsung devices have fastboot along with download mode, so saying "no Samsung devices have fastboot" would be wrong. And no, it's also with some A series devices as well, I don't know why, it's very weird as well

mfn003 said:
I know, but some Samsung devices have fastboot along with download mode, so saying "no Samsung devices have fastboot" would be wrong. And no, it's also with some A series devices as well, I don't know why, it's very weird as well
Click to expand...
Click to collapse
I can only go by what I've experienced and don't think it is wrong. Of all of the threads in the Tab A, XDA forums, I've never heard of a single mention of the use of fastboot. ADB, yes, but fastboot, no. If you think that is wrong, link to a thread that says otherwise.
edit: I just googled "Do any Samsung Android devices support fastboot?" and every response I see says NO, except for some of the very latest models. No Tab A devices. BTW, there is a difference between the Galaxy Tab A and the Galaxy Axx models. This thread is for the Tab As. Tab As are tablets/phablets and not plain phones.

lewmur said:
I can only go by what I've experienced and don't think it is wrong. Of all of the threads in the Tab A, XDA forums, I've never heard of a single mention of the use of fastboot. ADB, yes, but fastboot, no. If you think that is wrong, link to a thread that says otherwise.
edit: I just googled "Do any Samsung Android devices support fastboot?" and every response I see says NO, except for some of the very latest models. No Tab A devices. BTW, there is a difference between the Galaxy Tab A and the Galaxy Axx models. This thread is for the Tab As. Tab As are tablets/phablets and not plain phones.
Click to expand...
Click to collapse
Yes, as I said, only some devices (mostly Galaxy Axx and M) have fastboot. Therefore the statement "Samsung devices don't support fastboot" is misinformation.

lewmur said:
I can only go by what I've experienced and don't think it is wrong. Of all of the threads in the Tab A, XDA forums, I've never heard of a single mention of the use of fastboot. ADB, yes, but fastboot, no. If you think that is wrong, link to a thread that says otherwise.
edit: I just googled "Do any Samsung Android devices support fastboot?" and every response I see says NO, except for some of the very latest models. No Tab A devices. BTW, there is a difference between the Galaxy Tab A and the Galaxy Axx models. This thread is for the Tab As. Tab As are tablets/phablets and not plain phones.
Click to expand...
Click to collapse
SM-T225 TAB A 7 LITE SUPPORTS IT BRO