Hi, guys, I am really needing help.
I have bougth a chinese android tablet model tb128fu. I was worried with the safety of the tablet's ROM, I was suspecting it was a shop ROM. So, I downloaded LMSA (Lenovo Rescue and Smart Assistant) to flash an another ROM (even I have read in LMSA app that flashing ROM mustn't be done in chinese devices - I was very stupid) and it bricked my tablet. Tablet entered into a reboot mode loop: any chosen option was conducting to lenovo's logo and, after it, reboot menu again.
I have posted a question about it here in forum and people suggested to use ROM2box app. I tried to use it and I think it would solve my problem, but during ROM flashing in ROM2box my pc turned off (due to a residencial blackout) and now my tablet is completely died. VOL UP and DOWN and power off buttons are not working, and the screen doesn't show anything, in any situation (even during battery charging).
Please, help me!!! I think I have lost my tablet.
In PC's devices manager tablet is showed as Qualcoom HS-USB QDLoader 9008 (COM3). Does it help anything to solve my problem?
I have also tried to flash some chinese ROM in tablet using QFIL, but all times it shows the follow error:
"Download Fail:Sahara Fail:QSaharaServer Failrocess fail"
I am thankful anyway. Thank you for your attention.
Re-flash tablets Stock ROM.
BTW:
Tablet isn't hardbricked but softbricked, IMO
With the "hardbrick" usually a part of the low-level firmware is damaged, e.g. the bootloader, the "radio firmware" or other firmware, which is necessary for the operation of the SoC (System-on-Chip). To re-install this firmware, special hardware (usually JTAG) is required, as well as expert knowledge and corresponding image files are often not publicly available (at least not officially). It's like "shooting" the BIOS/EFI on a PC.
With a "softbrick," only the operating system is damaged, e.g. the Android kernel or the system libraries. You can reflash the device.
xXx yYy said:
Re-flash tablets Stock ROM.
BTW:
Tablet isn't hardbricked but softbricked, IMO
With the "hardbrick" usually a part of the low-level firmware is damaged, e.g. the bootloader, the "radio firmware" or other firmware, which is necessary for the operation of the SoC (System-on-Chip). To re-install this firmware, special hardware (usually JTAG) is required, as well as expert knowledge and corresponding image files are often not publicly available (at least not officially). It's like "shooting" the BIOS/EFI on a PC.
With a "softbrick," only the operating system is damaged, e.g. the Android kernel or the system libraries. You can reflash the device.
Click to expand...
Click to collapse
Ah, ok. I am really sorry for my mistake. It's clear now what is the difference between hard and soft brick.
May you help me to reflash my device? I have no idea how to do that.
Thank you for you reply
joaovitorjvbjvb said:
Ah, ok. I am really sorry for my mistake. It's clear now what is the difference between hard and soft brick.
May you help me to reflash my device? I have no idea how to do that.
Thank you for you reply
Click to expand...
Click to collapse
I might try the website linked below -- there's also a "How to Flash" tutorial step-by-step guide in the page
DISCLAIMER: I am not completely sure if it will help or make this worse! Being that your device is a Chinese variant and you've already bricked it messing with it because it is that variant, there's no guarantee the files and steps below will do any better or not make things worse. I also have not personally vetted the validity or accuracy of the site. Proceed at your own risk!
Lenovo Tab M10 TB128FU Stock Firmware ROM (Flash File)
Download the official Lenovo Tab M10 TB128FU Stock Firmware ROM (Flash File) for your Lenovo Mobile. We also provide all other Lenovo Stock Firmware for free.
firmwarefile.com
simplepinoi177 said:
I might try the website linked below -- there's also a "How to Flash" tutorial step-by-step guide in the page
DISCLAIMER: I am not completely sure if it will help or make this worse! Being that your device is a Chinese variant and you've already bricked it messing with it because it is that variant, there's no guarantee the files and steps below will do any better or not make things worse. I also have not personally vetted the validity or accuracy of the site. Proceed at your own risk!
Lenovo Tab M10 TB128FU Stock Firmware ROM (Flash File)
Download the official Lenovo Tab M10 TB128FU Stock Firmware ROM (Flash File) for your Lenovo Mobile. We also provide all other Lenovo Stock Firmware for free.
firmwarefile.com
Click to expand...
Click to collapse
OWWWW DUDE!!!
I am really thankful . Thank you very much )
Using your download link I got it! I could flash ROM (using QFIL) in my tablet again. My tablet is finally back. Thank you!!!
Related
Hi, long time lurker, but it's been a while.
So, I received 2 (brand new) Tab 2's and immediately found they both had/have the ancient 4.0.4 and wouldn't be updated OTA by Sammy to anything much newer.
I haven't needed to root or flash a custom rom in *years*, so I am def. rusty....but I quickly did my research, found that CM has been replaced by Lineage, and that there were Tab 2 roms up to 6.0. Enticing enough.
I root'd both with TowelRoot, then installed TWRP manager on one. I also went through and compared the differences for p5100/5110/p5113 models, but all I really found was with/without 3g, with/without IR blaster...so I found (thought) that mine should be the expresso3g p5110.
BIG MISTAKE. I read LATER that the 5110 is an international model, and the VZW is almost identical but SPECIAL (with a custom/locked bootloader?) and not to be confused with the former (unless you're stupid like me).
So I installed the p5110 TWRP...it rebooted and...volia! Instantly (my first ever) hard brick. It appears to have trashed the bootloader/partition layout: It recognizes as "qhsusb_dload" which after drivers comes up as "Qualcomm HS-USB QDLoader 9008 (COM9)" ....no light, no downloader, no recovery, nada.
I searched/read a lot, and find that there is no love/tutorials for this model, everyone appears to have the 7" or non-VZW models. But I did read lots of conflicting info, and a couple *possible* options (since I have an identical rooted working unit):
I can *maybe* make a jig to get into downloader mode (but I can't find the pinout since tab 2 is 30pin)....I read from different ppl this will (or definitely will not) work
Since it reads as QDLoader 9008 COM then QPST will likely recognize it, but ODIN won't
I can therefore (possibly) use QPST and extract the image of the working unit, and flash it to the bricked one
I can also (possibly) use terminal emu on the good unit to extract a "debrick.img" (of just the downloader partitions) and boot them off of the microsd to flash back the stock rom
It appears that if any of these are possible, there is no custom love for my model, period. And that even I can extract/flash with QPST, I will end up cloning the working unit, copying device specific info, which is also not ideal.
Also, there doesn't appear to even be stock rom files available for this.
Add to that that I read that with a locked bootloader I won't be able to flash anything. Which also begs the question, if the bootloader was "locked"...how did TWRP overwrite/trash it to begin with?
Please would someone much more knowledgeable chime in here? Am I barking up the wrong tree? Is anything listed above viable? I hate to just scrap this unit, it is LITERALLY brand new (still has the plastic on it!)
Thanks in advanced for anyone with any options or suggestions!
I guess I will answer my self. If you are like me and just screwed up the bootloader (and all the other partitions are intact), the debrick image will do the trick. It is explained HERE. The bootloader debrick for a VZW stock 4.0.4 is uploaded HERE, hope it helps someone!
Hi,
I am a little new and don't really know about this subject but :
I purchased a new phone : a Gome K1.
This is not tablet but phone. This is a new brandt. This a MTK (MT6757).
For the story, it came to me with chinese ROM, all menus in chinese
I asked to the seller to give me a ROM with playstore and french. They done it.
I flashed their new ROM with a proprietary flash tool. Now I have a android 6 ROM with Playstore, french menus. Well !
But I'd like to know if there is a way to root it, and install a TWRP :
The ROM came with bootloader locked and no recovery. It is entirely blocked.
No way to unlock bootloader via the general way (fastboot oem unlock --> unknown command)
I read some articles that deal with spflashtool and porting TWRP, but I'm new to this and I don't think I will be able to make all these steps correctly to flash a TWRP ...
Does someone has an idea ?
Is my post on the good topic ?
Up, does someone have an idea of how to root it ?
Hello,i also have a Gome K1 phone and I am also interested at rooting it.
There is an ' OEM unlocking option' under the developers option in the settings, have you tried that yet?
If you managed to import twrp and rooted the phone can you pls send here the steps, Thanks
Hello, happy to not be alone with this phone ...
Yes I tried everything, after enabling unknown source, OEM unlocking and USB Debugging developer options :
- All root apks
- all existing root kits using ADB
- Method with a linux distro to access Phone filesystem as root ( cannot see my phone ... )
Now I'm trying to use SP flashtool last version, but even that cannot correctly access the phone to Readback my recovery : there is BROM error, so I think that phone is not compatible with the phone (seen on a forum ...)
So if someone has an idea, he is welcome
Inveds said:
Hello,i also have a Gome K1 phone and I am also interested at rooting it.
There is an ' OEM unlocking option' under the developers option in the settings, have you tried that yet?
If you managed to import twrp and rooted the phone can you pls send here the steps, Thanks
Click to expand...
Click to collapse
When I contacted them, they send me a non rooted custom ROM which embed Google Apps and All language, AND another flash tool.
This flash tool seems to be based on SP flash tool. It seems to have restrictions (no readback ability ...).
I'm not able to backup anything with this tool or with SP flash tool.
Whis spflashtool, when clicking ReadBack, I power off my phone, and plug USB cable.
It begins the process but I immediatly encounter a BROM error :
ERROR: status_brom_cmd_send_da_fail (0xC0060003)
I read a post which indicate to try to plug usb cable when pressing Power plus Volume Up, but I don't think it can work, because I know that their tool works without that operation.
So now I'm still stuck here. Does someone have an idea ?
Hi
On the Russian forum 4pda, the topic GOME K1 we are also discussing and trying to solve the problem of a locked bootloader. So far no results. ROOT is also not yet possible to get.
I've also ported twrp for GOME K1, but there's no point in installing it until the bootloader is unlocked. Otherwise we will get a brick.
Hi
In Developer options there is a setting to unlock bootloader, it's the third toggle down.
Hope this helps.
Amagram said:
Hi
In Developer options there is a setting to unlock bootloader, it's the third toggle down.
Hope this helps.
Click to expand...
Click to collapse
No, it's not working. This switch does not affect the boot loader state.
vsxby said:
Hi
On the Russian forum 4pda, the topic GOME K1 we are also discussing and trying to solve the problem of a locked bootloader. So far no results. ROOT is also not yet possible to get.
I've also ported twrp for GOME K1, but there's no point in installing it until the bootloader is unlocked. Otherwise we will get a brick.
Click to expand...
Click to collapse
Hello vsxby,
I was successful in flashing custom ROM that vendor uploaded for me.
So I thing I can flash just the recovery with their tool. I'm not an expert, so I'm just a little affraid to follow a guide to port a TRWP for Gome K1 and try to flash it, since it can brick the phone.
If you want, I can't send you a copy of their tool they sent to me (SPMultiPortFlashDownloadProject.exe) ...
z2x said:
Hello vsxby,
I was successful in flashing custom ROM that vendor uploaded for me.
So I thing I can flash just the recovery with their tool. I'm not an expert, so I'm just a little affraid to follow a guide to port a TRWP for Gome K1 and try to flash it, since it can brick the phone.
If you want, I can't send you a copy of their tool they sent to me (SPMultiPortFlashDownloadProject.exe) ...
Click to expand...
Click to collapse
Thank you, but I already have this tool. As I wrote before flashing TWRP we need to unlock the bootloader. While this is not impossible to do. But one of our users on 4pda is going to ask the manufacturer to unlock bootloader. In case of success, I will inform you.
If you want to experiment and flash TWRP with a locked bootloader, I can give you the TWRP I made, but I warn you, it's not safe.
Bro,Can you upload the firmware and tools to google drive or something like? It will be very helpful for dealing with this mediatek replica phone(aus6757_66_m),i got some possible factory test MTK AOSP,but the link expires ：（
@Vortex said:
Bro,Can you upload the firmware and tools to google drive or something like? It will be very helpful for dealing with this mediatek replica phone(aus6757_66_m),i got some possible factory test MTK AOSP,but the link expires ：（
Click to expand...
Click to collapse
It's link GD to multi firmware and tool
vsxby said:
Thank you, but I already have this tool. As I wrote before flashing TWRP we need to unlock the bootloader. While this is not impossible to do. But one of our users on 4pda is going to ask the manufacturer to unlock bootloader. In case of success, I will inform you.
If you want to experiment and flash TWRP with a locked bootloader, I can give you the TWRP I made, but I warn you, it's not safe.
Click to expand...
Click to collapse
Ok, hope manufacturer will accept to give bootloader unlock procedure
z2x said:
Ok, hope manufacturer will accept to give bootloader unlock procedure
Click to expand...
Click to collapse
We were unable to contact the manufacturer and the moderators of the official GOME forum do not have this information. At the moment, there are no solutions to this issue.
z2x said:
Hello vsxby,
I was successful in flashing custom ROM that vendor uploaded for me.
So I thing I can flash just the recovery with their tool. I'm not an expert, so I'm just a little affraid to follow a guide to port a TRWP for Gome K1 and try to flash it, since it can brick the phone.
If you want, I can't send you a copy of their tool they sent to me (SPMultiPortFlashDownloadProject.exe) ...
Click to expand...
Click to collapse
could you please post here what is the procedure you took to flash the rom. Seller sent me with multi language rom. i want to downgrade the rom to its original one. I used your tools in the windows 10 lap. and also in the windows 7 lap but it was useless. I am going to try the procedure in the windows 8.1 lap. can you tell me exactly how you flash your phone with that tool ?
Hey Bro,
I get my new Gome K1 with Global ROM
but have some issues with my new Gome K1 >> the GPS doesn't work proper for Google Maps / Waze, it doesnt show accurate position most of the time, but it seems work well with "offline GPS" (but offline GPS most of the time not able to find location that I ahead for meeting). Any recommendation/solution?
Thanks in advance
Hi, is there any modem file for this phone ? MDDB....
original eom (china rom).
Hello every one i buy thise phone and come with multilanguage firmware but i like the origin one, can anyone help me the link of the firmware of origin!!
vsxby said:
We were unable to contact the manufacturer and the moderators of the official GOME forum do not have this information. At the moment, there are no solutions to this issue.
Click to expand...
Click to collapse
After some time ... is there any news about his root? I wouldn' t like to change the rom, but just do the root thing would be useful ..... tks
i've disabled the google app in the settings and now the phone is stuck on boot logo... any ideas how to fix this?
---------- Post added at 06:51 PM ---------- Previous post was at 06:30 PM ----------
driska said:
i've disabled the google app in the settings and now the phone is stuck on boot logo... any ideas how to fix this?
Click to expand...
Click to collapse
found the answer on 4pda, can't post link.
Greetings, everyone! Usually I have good knowledge regarding rooting, custom recovery and flashing a new system. But this time I tried to downgrade the Samsung Xcover 3 of my friend and flashed the Android 4.4.4 sboot.bin with Heimdall - unfortunately I forgot to tick the "no reboot" option. The moment it rebootet, I know do not have any access to the phone anymore.
When trying to bring it into download mode, it vibrates, but nothing else. Neither Linux nor Windows recognizes the phone. Is it dead? How to gain access so that I can flash the correct sboot.bin? Any tricks you recommend?
back2nature said:
Greetings, everyone! Usually I have good knowledge regarding rooting, custom recovery and flashing a new system. But this time I tried to downgrade the Samsung Xcover 3 of my friend and flashed the Android 4.4.4 sboot.bin with Heimdall - unfortunately I forgot to tick the "no reboot" option. The moment it rebootet, I know do not have any access to the phone anymore.
When trying to bring it into download mode, it vibrates, but nothing else. Neither Linux nor Windows recognizes the phone. Is it dead? How to gain access so that I can flash the correct sboot.bin? Any tricks you recommend?
Click to expand...
Click to collapse
If you can find a "debrick.img" or "debrick.bin" for your specific model number, there is a method that uses your external sdcard to boot the phone then repair it while it is booted.
But, first, you need to find a debrick.img or debrick.bin for your specific model number. If you can't find a copy for your model number, you can try finding another member here that has a rooted Xcover 3 with the exact same firmware as your device had and have them pull a copy of debrick.img or debrick.bin from their device then upload it for you to download.
If you can't find that, the only other options are to send the device to a repair shop for JTAG service or replace the motherboard.
Sent from my SM-S767VL using Tapatalk
Droidriven said:
If you can find a "debrick.img" or "debrick.bin" for your specific model number, there is a method that uses your external sdcard to boot the phone then repair it while it is booted.
But, first, you need to find a debrick.img or debrick.bin for your specific model number. If you can't find a copy for your model number, you can try finding another member here that has a rooted Xcover 3 with the exact same firmware as your device had and have them pull a copy of debrick.img or debrick.bin from their device then upload it for you to download.
If you can't find that, the only other options are to send the device to a repair shop for JTAG service or replace the motherboard.
Click to expand...
Click to collapse
I did not even expect that someone would answer here. THANK YOU SO MUCH, @Droidriven! That gives me hope to rescue the phone instead of having o buy a new one for my friend. Here is what I actually did wrong: In my attempt to "downgrade" from 5.1.1 Lollipop to Android 4.4.4 Kitkat (downgrade needed to be able to root the phone) I flashed the sboot.bin of Android 4.4.4 Kitkat with Heimdall and forgot to tick the NO REBOOT option.
That being said, the phone now only vibrates when using my JTAG (yes, I actually have one and the phone vibrates, but does not boot into download mode and is not recognized by neither Windows nor Linux). So, how to build this unbrick image? Could you help me with that? Both firmwares are to be found here:
Code:
https://samsungfirmware.net/samsung-galaxy-xcover-3-sm-g388f-stock-firmware
Another thread with sadly no file uploaded was to be found here:
Code:
https://forum.xda-developers.com/general/help/search-g388f-xcover3-debrick-img-sdc-t3399231
As for the creation of the unbrick image, do you recommend this tool? I currently have no Windows at hand but can provide you with the original PIT file if you can run this tool to create it:
Code:
http://forum.gsmhosting.com/vbb/f609/atf-v12-70-update-31-mar-2017-a-937102/index5.html#post10127092
DOWNLOAD LINK ATF_v12.70_Full_Installer:
Code:
http://www.mediafire.com/file/l1c9o7ibv2jypfv/ATF_v12.70_Full_Installer_%2528xdarom.com%2529.rar/file
Furthermore, I actually wanted to install LineageOS on that phone. Not sure if you have a Google-foo so strong that you are able to find a working one for me?
Thanks a lot for your help. May god return your efforts in helping me!
back2nature said:
I did not even expect that someone would answer here. THANK YOU SO MUCH, @Droidriven! That gives me hope to rescue the phone instead of having o buy a new one for my friend. Here is what I actually did wrong: In my attempt to "downgrade" from 5.1.1 Lollipop to Android 4.4.4 Kitkat (downgrade needed to be able to root the phone) I flashed the sboot.bin of Android 4.4.4 Kitkat with Heimdall and forgot to tick the NO REBOOT option.
That being said, the phone now only vibrates when using my JTAG (yes, I actually have one and the phone vibrates, but does not boot into download mode and is not recognized by neither Windows nor Linux). So, how to build this unbrick image? Could you help me with that? Both firmwares are to be found here:
Code:
https://samsungfirmware.net/samsung-galaxy-xcover-3-sm-g388f-stock-firmware
Another thread with sadly no file uploaded was to be found here:
Code:
https://forum.xda-developers.com/general/help/search-g388f-xcover3-debrick-img-sdc-t3399231
As for the creation of the unbrick image, do you recommend this tool? I currently have no Windows at hand but can provide you with the original PIT file if you can run this tool to create it:
Code:
http://forum.gsmhosting.com/vbb/f609/atf-v12-70-update-31-mar-2017-a-937102/index5.html#post10127092
DOWNLOAD LINK ATF_v12.70_Full_Installer:
Code:
http://www.mediafire.com/file/l1c9o7ibv2jypfv/ATF_v12.70_Full_Installer_%2528xdarom.com%2529.rar/file
Furthermore, I actually wanted to install LineageOS on that phone. Not sure if you have a Google-foo so strong that you are able to find a working one for me?
Thanks a lot for your help. May god return your efforts in helping me!
Click to expand...
Click to collapse
Sorry, I'm just now seeing this. Did you ever make any progress? Yes, I think there are some reliable methods to create debrick.img/debrick.bin files, there is one such method posted here at XDA in a random post in a thread here but I can't remember exactly what thread it is.
the boot.img file was loaded into my phone in order to get root after that it could not detect imei numbers. Although they are in fastboot. I tried many different firmwares for this phone, but there is no result! I ask for your help. I was left without communication (sorry for not being very clear. I don't understand Russian and don't understand English at all, that's why I'm writing through a translator
The first thing you want to do is STOP FLASHING random images. It sounds like you are going to cause more harm than good if you keep going.
Figure out which firmware you started on (WW, EU, CN) and get the raw firmware for it. Follow the instructions to flash the raw firmware.
If that doesn't work, then you may need to contact the manufacturer, BUT at least you will be restored to stock. I cannot promise they will help you, but it sounds like you did more than flash a boot image. The IMEI is not stored there.
twistedumbrella said:
The first thing you want to do is STOP FLASHING random images. It sounds like you are going to cause more harm than good if you keep going.
Figure out which firmware you started on (WW, EU, CN) and get the raw firmware for it. Follow the instructions to flash the raw firmware.
If that doesn't work, then you may need to contact the manufacturer, BUT at least you will be restored to stock. I cannot promise they will help you, but it sounds like you did more than flash a boot image. The IMEI is not stored there.
Click to expand...
Click to collapse
Tell me where you can find the pure CN firmware? This phone was presented to me in this form already. And they told what happened to him. I doubt that ASUS support will help me, since in addition to everything according to the owner, the EMMCCDL_GUI utility was used. So I ask for help from knowledgeable people here.
And most importantly, what to flash and how?
Repair your ASUS ROG Phone 5 with EDL mode
If your phone can only enter EDL mode (9008 mode) this firmware is glad to help you. It can be flashed in through the miflash tool. The firmware is made through the official package...
forum.xda-developers.com
RAW Firmware Collection and Guide
All fastboot / adb commands require using the side USB-C port https://developer.android.com/studio/releases/platform-tools.html#download Make sure you have fastboot installed Add platform tools to PATH (post 2) Make a backup of anything...
forum.xda-developers.com
twistedumbrella said:
Repair your ASUS ROG Phone 5 with EDL mode
If your phone can only enter EDL mode (9008 mode) this firmware is glad to help you. It can be flashed in through the miflash tool. The firmware is made through the official package...
forum.xda-developers.com
RAW Firmware Collection and Guide
All fastboot / adb commands require using the side USB-C port https://developer.android.com/studio/releases/platform-tools.html#download Make sure you have fastboot installed Add platform tools to PATH (post 2) Make a backup of anything...
forum.xda-developers.com
Click to expand...
Click to collapse
did not help(
What? So no one will help ???
Return the phone or wait until the methods exist.
Those are the only quick answers left.
twistedumbrella said:
Return the phone or wait until the methods exist.
Those are the only quick answers left.
Click to expand...
Click to collapse
It was opened. This is not an option either
If you purchased it used and the seller refused a return, it sounds like they were trying to recover what they could by selling their problem to someone else. It's likely they knew there wasn't a self-service fix right now.
Just to be clear, what you need is a low-level EDL restore. As it stands, one of the files required is not available to the public. If you have a local repair shop, they may be able to do it (and will likely charge a fee).
Do NOT pay someone over the internet. It CANNOT be done remotely.
Hello
I've been reading forums and downloading files for days. Many of the links in the posts no longer work. Posts are 5 years and older. There are no new ones. At least not one that actually works. Downgrade I mean. That's why I wrote this question and I'm asking for help - how to really downgrade my Galaxy S6 G920F.
Thanks for the help.
PSA: Downgrading WILL void your warranty!
What have you already done (what method, software) have you already tried?
The 100% surefire way to downgrade your phone (or any android phone really), is to:
1. Backup your phone data.
2. Switch the phone into download mode, connect to PC, boot into TWRP recovery through fastboot
3. Wipe your 7.0 firmware and all data
4. Flash android 5.02 ROM
For a samsung phones ODIN + Freya is also an option. Odin is a samsung's firmware flashing tool, Freya is a 3rd party program that can download the stock firmware android for you. All of these tools are available online, and you can ask on a samsung subsection of XDA about how to use them - people can give you up to date links.
I'm laughing because you write quite a lot in three days. Of course, this method does not work.
Is there anyone willing to help?
Totesnochill said:
PSA: Downgrading WILL void your warranty!
What have you already done (what method, software) have you already tried?
The 100% surefire way to downgrade your phone (or any android phone really), is to:
1. Backup your phone data.
2. Switch the phone into download mode, connect to PC, boot into TWRP recovery through fastboot
3. Wipe your 7.0 firmware and all data
4. Flash android 5.02 ROM
For a samsung phones ODIN + Freya is also an option. Odin is a samsung's firmware flashing tool, Freya is a 3rd party program that can download the stock firmware android for you. All of these tools are available online, and you can ask on a samsung subsection of XDA about how to use them - people can give you up to date links.
Click to expand...
Click to collapse
That is assuming they have TWRP.
Also, the part you mention about "boot into download mode, connect to PC then boot to TWRP via fastboot" is not correct because Samsung is not compatible with fastboot, adb works but fastboot does not. Some Samsung devices technically have a "fastboot mode" but it isn't functional, it doesn't respond to fastboot commands, it's basically useless.
Also, you can't flash a firmware that has a lower binary than the currently installed firmware so if the binary of the downgraded firmware is lower than the binary of the currently installed firmware, the downgraded firmware can't be flashed.
Samsung is making it harder and harder to downgrade their devices.
OK. I'm afraid I'm missing the point of what's being said.
I know it is possible and there are also posts about it, but they are old, the links in them do not work. I'm asking for an expert who knows how to do this, philosophizing about what it would be like if it somehow doesn't really help me and I'm not interested either
I'm only interested in a positive thought, help and not brainstorming, if you understand me?
No offense