Database Users

Samsung Galaxy On5 bricked, Odin doesnt work, Kies doesnt work, any options?

The only thing I can successfully do with odin is flash the bootloader. I have the full firmware file, but whenever I try flashing anything but the bootloader, FRP Lock blocks it or it fails in odin. I know the exact reason that the phone is bricked, my OEM Unlock setting in developer settings got turned off and I have a rooted binary, so now whenever it trys to boot up, a little red message shows up in the top left for the first few seconds of boot, then the phone shuts off completely. No other thread provides any solution for my situation. Odin wont flash any firmware and I cant get into TWRP anymore as well. Does anyone know what to do? I have a replacement coming from T Mobile in a few weeks but I want to try and fix this thing.

In first use srktool and if does not work use sp flashtool and download on5 scatter files for flash
sent from Farzad's mate

what and where to find scatter file?
Farzad37 said:
In first use srktool and if does not work use sp flashtool and download on5 scatter files for flash
sent from Farzad's mate
Click to expand...
Click to collapse
I think this is very helpful to my situation.....but what is a scatter file as oppossed to the stock firmware....and is it something I can extract or get from the stockfirmware.zip? I have a samsung On5 (sm-g550t) thats bricked...thanks in advance!

Farzad37 said:
In first use srktool and if does not work use sp flashtool and download on5 scatter files for flash
sent from Farzad's mate
Click to expand...
Click to collapse
That's for mtk devices only, and will probably brick op's device even more

Retry Kies.
In the back of phone under battery look for make name (Sould look like SM-G5xxxx) and S/N
Make copy on windows txt file
Boot phone into Download Mode but dont plug into usb yet.
Open Kies on Windows select tools, then firmware upgrade and initialization. Enter your make click ok then enter your S/N click ok. Plug phone into usb and keep clicking ok untill you see downloading firmware

(Help needed) Soft bricked Tmobile Note 4 with way way WAY too many error messages.

So, I have here a great old Note 4.
It has the generic mmc errors that cause it issues when booting and sleeping so I decided to give it a new rom. I bumped it into developer options, enabled usb debugging and fastboot and turned it off. I opened up odin, found the right twrp file to flash as well as a stock rom. I loaded it up and fired. The issue then was that the PIT partition had issues. Pit partition failed on odin's side, and flash read failure as well as a pit error of some sort on the phone's side. So I did my homework. I then tried to flash a new .pit file, I made sure the boxes were filled out correctly, had the right pit file as well as a correct stock rom, and the right drivers. It failed again with exactly the same errors. I don't know how you can manage saying that you can't flash the file your trying to fix but whatever. So I did more research and continued to change the usb cable to the original one that came with the phone, change the usb port, change versions of odin, use administrator privileges, find another .pit file, and change the pc. None of these worked, they all gave the same errors no matter what I did. So I moved on to see what else I could do, there was only one more issue though, the phone wouldn't boot up to an OS, if I tried to boot up normally it would boot into recovery, and if I booted into recovery it would boot into download mode with a message saying that the mme error caused it to. SO I couldn't do anything like flashfire or rom manager nor could I do something like root the device! So I did more homework, I turned to adb, because I saw something about an alternative to odin. Unfortunately, the phone has to boot up so you can connect it properly before you boot into download mode. So I did more homework and can't get anywhere, I am completely lost as to what to do because I can't flash odin or adb and sd card can only flash .zip files. I have no idea where to find a .zip for cwm or twrp that will work for my phone and the 2 files that I thought would work only gave me errors. I definitely am drowning in error messages and hope someone who knows what in the world is going on can help me get out of this mess.
Sincerely,
TiffPiff

I have bricked asus ZenFone max pro m1. Please help me unbrick it!!!

While flashing pixel experience plus rom, the device did not boot up correctly causing a google loading screen which did not change even after an hour. At that time i realised that the rom didn’t flash correctly, or the rom might have some faults. So I rebooted my mobile in custom recovery mode to flash the stock rom, but it did not complete the flash, it generated error 7. So I tried to install havoc rom and I encountered the same problem. Not just that I have tried installing at least 5 rom which gives me the same problem. I can’t even flash my recovery rom. It generates the same errors which include error 7 and invalid zip file. So I tried solving this problem by unzip the rom and editing the assert script and re zipping the file, and I encounter the same errors. I have even tried using a different custom recovery like TWRP and red wolf (latest updated version), but I face the same errors. The mobile has no os installed and it doesn’t allow me to install any rom. It only allows me to install stock recovery and other custom recovery by using Fastboot mode. I have tried add sideload through the custom recovery and the mobile gets detected, but it gives the same errors.
So I tried using QFIL application as the mobile was a Qualcomm device. The mobile gets detected as 9008. And I tried to download the program files on the mobile, but then it gives me a Sahara fail error.
I have tried to do it multiple times and I end up getting the same error.
The device has a unlocked boot loader but it was never rooted.
Please help me.

Can’t post it in the developer forum for this device as I don’t meet the requirements for posting it

i.am.the.best said:
While flashing pixel experience plus rom, the device did not boot up correctly causing a google loading screen which did not change even after an hour. At that time i realised that the rom didn’t flash correctly, or the rom might have some faults. So I rebooted my mobile in custom recovery mode to flash the stock rom, but it did not complete the flash, it generated error 7. So I tried to install havoc rom and I encountered the same problem. Not just that I have tried installing at least 5 rom which gives me the same problem. I can’t even flash my recovery rom. It generates the same errors which include error 7 and invalid zip file. So I tried solving this problem by unzip the rom and editing the assert script and re zipping the file, and I encounter the same errors. I have even tried using a different custom recovery like TWRP and red wolf (latest updated version), but I face the same errors. The mobile has no os installed and it doesn’t allow me to install any rom. It only allows me to install stock recovery and other custom recovery by using Fastboot mode. I have tried add sideload through the custom recovery and the mobile gets detected, but it gives the same errors.
So I tried using QFIL application as the mobile was a Qualcomm device. The mobile gets detected as 9008. And I tried to download the program files on the mobile, but then it gives me a Sahara fail error.
I have tried to do it multiple times and I end up getting the same error.
The device has a unlocked boot loader but it was never rooted.
Please help me.
Click to expand...
Click to collapse
1. 1st try to flash fastboot rom,
after install fastboot rom if the phone stuck on asus logo or any other error then
2.Try to install Qfll file (select ww_no_fsg.xml file) after successful installation , boot your phone.
3. again connect your phone fastboot mode and flash fastboot rom
If every installation is successfully done then i am sure that your phone is boot properly in stock rom with lock bootloader.
because I faced same issue,
remember 1st try to install stock fastboot rom and then try to flash Qfil files
Wish you good luck :good:

Try flashing fw063 before flashing your custom rom.(that fixed for me)
if it didn't work try this (rooted):-
https://forum.xda-developers.com/showthread.php?t=2522762

Thanks bro. I have successfully unbricked my mobile

Asus Zenpad Z380M Wont turn on or boot to any mode after attempted magisk root with locked bootloader

Okay, Let me explain exactly what I did here... I first flashed Twrp using SP flash tool which worked without too much problem. Then I attempted to install the latest super su zip which told me the boot.img was already patched and it could not find a ramdisk... So I moved on and flashed the latest Magisk zip which flashed no problem. Rebooted the device and it came up with a red boot state telling me it would boot in 5 sec. It did not boot at all. Turned off the tablet and rebooted into twrp again. I then flashed the OTA update system.img, boot.img, and re-flashed twrp from twrp itself instead of the SP flash tool. It booted into twrp no problem, however now it said it could not mount the system partition. I did a full data wipe, factory reset, rebooted into twrp again. Same issue. So I attempted to re-flash the firmware with SP flash tool. Did not notice i had it set to format and download and not only download. It said formatting for maybe 2 sec and gave me an error. Now the device will not turn on at all... no screen whatsoever, no recovery, etc... I have had no luck getting the asus flash tool to even recognize a com port however SP flash tool seems to be able to flash the device no problem. I extracted the .raw firmware file I have for the latest firmware, modified the scatter file to allow flashing all partitions, and I did a full firmware flash of the device using SP flash tool. However it still does not turn on... it does nothing... So I'm assuming that I accidentally formatted over the bootloader... And I cannot find a bootloader flash file for this device anywhere... So I'm stuck with an Asus ZenBrick... Does anyone know a way to fix this issue? When I plug the device into my computer and open device manager it switches between the preloader and mtk serial port very quickly not staying on either one very long. I'm assuming this is why I cant get the asus flash tool to work and SP flash tool works off just the initial preloader. I just bought this tablet from someone and managed to hard brick it in less than a days time... Any help at all with a way to revive this device will be greatly appreciated. Thank You in advance to anyone who tries to help me fix my mess up.

Samsung galaxy A sm-t585 stuck in bootloop

I tried rooting my tablet and I'm using arch linux on my computer, so I had to use Heimdall and Jodin to root it. I got the Heimdall to say "flashed succesfully", but I still didn't have twrp on my tablet.
Then I found Jodin and tried to use that to flash twrp on my tablet, but I really didn't got it to work. It usually said failed, because tablet would disconnect during the flash and reconnect right after.
Right now the tablet is stuck in "bootloop" it just boot's into the black screen where it says "Samsung galaxy tab a etc.". I can boot into download mode, but I really don't know how to fix this. When I boot into download mode, both jodin and heimdall detects the phone. Any tips how to fix this?

Try go to download mode by mtp from windows or micro USB with resistance
If you want to download twrp for root so you can make root with out it
Just by eftus and flash file from site or magisk apk with AP file same ver on your phone

I guess I wrote pretty confusing post. I can go to download mode, but not boot to the android. Right know I got it saying "could not do normal boot invalid kernel length"
Jodin says this when trying to flash:
<ID:0/008> Added!!Device Connected
Device Removed
Device Connected
/usr/bin/heimdallDevice Removed