Database Info

Samsung Galaxy J7 SM-J700F (MT6572 Chipset) hard bricked

Dear Developers,
I am a noob here & want your help for that device running Android 5.1.1 LP
1. Drivers were installed correctly.
2. The phone unable to be detected on my PC (Windows 10 X64) and on Laptop (Windows 7 X64) too while in download mode, didn't make a sound when plug in the USB cable, worked while it's turned on and in recovery mode with adb sideload.
3. Unable to be detected by ODIN 3.10.7, ODIN 3.10.6 .. Followed all instructions by threads here.
4. Rooted using kingoroot then replaced with SuperSU, unable to be installed in normal mode.
5. My phone now won't start & boot up, i bet emmc is hard bricked.
6. I tried to solve it with SP Flash Tool v5.1524 (Latest) but with no success as no scatter file found in the ROM Official Package.
I need your help to make this phone work again

Mt boards doesnt detected by odin as they are clone not orignal ones.. Use sp flash tool too unbrick it, get the proper rom first then Google how to flash rom with sp tool.. You will make it run again.

Yes that's true, i need the full Rom with scatter file to be able to flash it, found some roms but not officials, can't find the official stock rom with scatter file

Problem solved after flashing the emmc by SP Tool with the full rom image found at http://bdandroidfirmware.blogspot.com.eg/2016/01/samsung-j700fds-mtk6572-v511-100tested.html?m=1
Thanks for your help Salik, highly appreciated.
Regards
BG
Don't hesitate to reply if anyone face a problem with that issue to help ^_^

Pudiste solucionar el problema avisame
Un abrazo
Gustavo

PASSWORD
What is te password of that file please?

The password of this file will be decrypted by the upload owner by remote application, contact him on yahoo as mentioned in the website.
Regards
BG

lBGl said:
The password of this file will be decrypted by the upload owner by remote application, contact him on yahoo as mentioned in the website.
Regards
BG
Click to expand...
Click to collapse
thank you

Do you have other firmware for Samsung clone j700f/ds mt6572?

sir that person is not responding COULD YOU HELP with boot.IMG file or full rom if you can plz.

stuck in bootloader
i root the j700f ,but when its rebooting it stucks in bootloader
what can we do?
I rooted the device from odin
it is rooted succesfully but it cant reboot successfull..
why it cant start?

How to Unbrick j700f
Hello
I have installed TWRP with odin but when i reboot my phone it turns to black screen aftwr showing the samsung j7 icon.
I have tried to flash with odin but the all time fails.
I have also tried smart switch but all time at 69 % downloading is failed
Plese help me

lBGl said:
Problem solved after flashing the emmc by SP Tool with the full rom image found at http://bdandroidfirmware.blogspot.com.eg/2016/01/samsung-j700fds-mtk6572-v511-100tested.html?m=1
Thanks for your help Salik, highly appreciated.
Regards
BG
Don't hesitate to reply if anyone face a problem with that issue to help ^_^
Click to expand...
Click to collapse
You are liar and spammer , you should be banned from this forum, and and rest gypsies always make spam and password protected files......... losing members time , damn scammers
darkside15 said:
What is te password of that file please?
Click to expand...
Click to collapse
Friend dont lose time with those bad persons hat post password protected files and says add me to yahoo , skype whats app.
Bad people with very bad attitude . Fight them till end
lBGl said:
The password of this file will be decrypted by the upload owner by remote application, contact him on yahoo as mentioned in the website.
Regards
BG
Click to expand...
Click to collapse
Still hear ? Go wanitsh , dont lose forum space and spam this gr8 forum
CGUNLOCKER said:
sir that person is not responding COULD YOU HELP with boot.IMG file or full rom if you can plz.
Click to expand...
Click to collapse
Dont expect , those are liars and spammers , a good member will post non password protected file or if archive pass protected they will immediately post on thread. Call me , add me , visit me those are thieves are spammers.
No Regards for liars and spammers

[Completed] Saving a bricked Alcatel Pixi

Hi everyone
Just want to get some thoughts on my problem. Not sure if its completely bricked, or able to be saved
Unit is a Alcatel Pixi 3 (4) model 4013X
When trying to flash the recovery with SP tools, I think I have played around too much and formatted the phone.
I do not have a backup of the rom however did find a exact one online and downloaded it.
When I try and flash in SP tools, it comes up with a error
BROM ERROR : S_NOT_ENOUGH_STORAGE_SPACE (1011)
Is there anything I can do to save the phone? It does get recognised in windows so I am guessing the hardware is still fine
Thanks

tez1 said:
Hi everyone
Just want to get some thoughts on my problem. Not sure if its completely bricked, or able to be saved
Unit is a Alcatel Pixi 3 (4) model 4013X
When trying to flash the recovery with SP tools, I think I have played around too much and formatted the phone.
I do not have a backup of the rom however did find a exact one online and downloaded it.
When I try and flash in SP tools, it comes up with a error
BROM ERROR : S_NOT_ENOUGH_STORAGE_SPACE (1011)
Is there anything I can do to save the phone? It does get recognised in windows so I am guessing the hardware is still fine
Thanks
Click to expand...
Click to collapse
The Assist section is where we guide new users(read the stickies). The Assist section is not for senior members as they should know where to post and ask for help when they have problems with their device.
Sorry but thread closed

[Completed] how to open fastboot?

Like the title said . I can open fastboot before ,and after flashing i cant open it.
When flashing via SP FLASH TOOL, I'M NOT REPLACING CWM RECOVERY.IMG with STOCK RECOVERY, why? Cause sp flash tool will say erorr blahblahblah if i changing that.
Used ago, I'm pretty sure if i can open Fastboot when my phone still on factory setting. So, anybody can help me?
Btw the phone have no problem right now (except this one) and working perfectly. But you know , i just want to try something new . Really thanks if you can help me.
My phone is ADVAN S5E Pro with MTK6572 inside

Kuzsczack said:
Like the title said . I can open fastboot before ,and after flashing i cant open it.
When flashing via SP FLASH TOOL, I'M NOT REPLACING CWM RECOVERY.IMG with STOCK RECOVERY, why? Cause sp flash tool will say erorr blahblahblah if i changing that.
Used ago, I'm pretty sure if i can open Fastboot when my phone still on factory setting. So, anybody can help me?
Btw the phone have no problem right now (except this one) and working perfectly. But you know , i just want to try something new . Really thanks if you can help me.
My phone is ADVAN S5E Pro with MTK6572 inside
Click to expand...
Click to collapse
Hello and welcome to xda-assist,
we actually don't do technical support, we're here to guide you to the most suitable board on xda, unfortunately the phone you're using has no specific device Forum, make sure you give proper information
https://forum.xda-developers.com/general/general/guide-how-to-question-t3464199
and ask here again
http://forum.xda-developers.com/android/help
Good luck

How to fix SP flash tool error?

Hello everyone.
I faced a problem while flashing stock firmware on my leeco le 1s eco (x509).
I wanted to flash stock firmware because after flashing a custom rom i had lost my imei no. and baseband. So i searched the internet for a fix and found that i have to flash stock firmware.
Now when I was flashing my firmware from sp flash tool i selected format all + download.
The flash tool started and it formatted my firmware and then started flashing the firmware. But it stopped at 6 % and showed this error :
BROM ERROR : S_DA_UART_DATA_CKSUM_ERROR
I tried flashing it again 3-4 times but it would always stop somewhere between 3-6% and show this error.
Now my phone is not starting or showing anything because of the formatting, only its LED is working when i plug it in for charging.
Is my phone hard bricked?
How can I fix this error?
Please help.
Thanks in advance for your time.

yashbajpai13 said:
Hello everyone. I faced a problem while flashing stock firmware on my leeco le 1s eco (x509)...
Click to expand...
Click to collapse
I don't have this device but, the following threads are specific to your device and may be helpful for what you are looking for.
https://forum.xda-developers.com/showthread.php?t=3719617
https://forum.xda-developers.com/showthread.php?t=3706172
https://forum.xda-developers.com/showthread.php?t=3700132
https://forum.xda-developers.com/showthread.php?t=3458777
https://forum.xda-developers.com/showthread.php?t=3594054
Good Luck!
~~~~~~~~~~~~~~~
I DO NOT PROVIDE SUPPORT VIA PM UNLESS ASKED/REQUESTED BY MYSELF.
PLEASE KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE

I tried these methods but sadly none of them is working.

nomu m8 dead?

hey, i think my phone is just dead
i used sp flash tools to flash my nomu m8
i cant find the custom rom for it, is it possible to use one from a similar phone?
if not i hope someone can upload it ;/

sethas32 said:
hey, i think my phone is just dead
i used sp flash tools to flash my nomu m8
i cant find the custom rom for it, is it possible to use one from a similar phone?
if not i hope someone can upload it ;/
Click to expand...
Click to collapse
That is what happens when you flash things that were not meant/built for your specific model number.
You need the firmware that is specific to your model number.
Sent from my SM-S767VL using Tapatalk

Thanks for the reply.
I mean i have a firmware for the device ( isnt the same as a custom rom right, excuse me when im wrong)
It contains a flash -all batch file, bootloader, boot file, system file etc. but no a scatter file.
I tried making a scatter file using mtk droid but it doesn't detect the phone. It is recognized by my pc though

sethas32 said:
Thanks for the reply.
I mean i have a firmware for the device ( isnt the same as a custom rom right, excuse me when im wrong)
It contains a flash -all batch file, bootloader, boot file, system file etc. but no a scatter file.
I tried making a scatter file using mtk droid but it doesn't detect the phone. It is recognized by my pc though
Click to expand...
Click to collapse
If you have bricked your device you need to do some research on how to unbrick Mtk devices.

Droidriven said:
If you have bricked your device you need to do some research on how to unbrick Mtk devices.
Click to expand...
Click to collapse
I did but I only got the factory image of the phone. I cant find a custom rom for the phone so i cant flash it with sp flash tools. It only works for roms with a scatter file.
I tried to flash trough cmd with fastboot and amd but it doesnt detect the device. When i connect the (dead bricked) phone my pc keeps connecting and disconnecting the driver over and over again.
Any advice will be appreciated, if there is a way... Maybe someone at this forum also got a nomu m8 and could clone it?
I think thats the only option, or flash it with a simular rom from another model? idk ;/

sethas32 said:
I did but I only got the factory image of the phone. I cant find a custom rom for the phone so i cant flash it with sp flash tools. It only works for roms with a scatter file.
I tried to flash trough cmd with fastboot and amd but it doesnt detect the device. When i connect the (dead bricked) phone my pc keeps connecting and disconnecting the driver over and over again.
Any advice will be appreciated, if there is a way... Maybe someone at this forum also got a nomu m8 and could clone it?
I think thats the only option, or flash it with a simular rom from another model? idk ;/
Click to expand...
Click to collapse
The connect/disconnect/connect issue is normal, you have to get the order of operations and the timing correct, if you do it right at exactly the right time, it should work.
There are plenty of threads and posts that discuss the connection process and the timing involved.
SP flashtool is primarily used to flash stock firmware, not custom ROMs. The problem is your firmware didn't come with a scatter file in the firmware file.
I know you tried to create a scatter file but did you try the method in the video linked below?
https://m.youtube.com/watch?v=BNlXT4EMUtY
Or maybe you can use just the scatter file from another device that is similar to yours, if you find a scatter file from a device that has the same partition structure as yours, it should work. The scatter file is only used to tell SP flashtool which partitions to flash the imgs to.
Sent from my SM-S767VL using Tapatalk

Droidriven said:
The connect/disconnect/connect issue is normal, you have to get the order of operations and the timing correct, if you do it right at exactly the right time, it should work.
There are plenty of threads and posts that discuss the connection process and the timing involved.
SP flashtool is primarily used to flash stock firmware, not custom ROMs. The problem is your firmware didn't come with a scatter file in the firmware file.
I know you tried to create a scatter file but did you try the method in the video linked below?
https://m.youtube.com/watch?v=BNlXT4EMUtY
Or maybe you can use just the scatter file from another device that is similar to yours, if you find a scatter file from a device that has the same partition structure as yours, it should work. The scatter file is only used to tell SP flashtool which partitions to flash the imgs to.
Sent from my SM-S767VL using Tapatalk
Click to expand...
Click to collapse
Thanks for the info! I tried the miracle tool, but it stuck at downloading boot. the other thing is the driver stays connected. Now i got a new problem, after a few times trying my pc couldn't find the phone anymore.
In the device manager it says 'Unknown USB device (Device descriptor request failed) ' I tried to update the driver with the MTK65xx vcom usb driver and a got a new error: 'The folder you specified doesnt contain a compatible software driver for your device. If the folder contains a driver, make sure it is designed to work with windows for 64x-based systems. ( i tried multiple, all the same error) its so hopeless.. now its official DEAD bricked. I think i stay with my old redmi phone

sethas32 said:
Thanks for the info! I tried the miracle tool, but it stuck at downloading boot. the other thing is the driver stays connected. Now i got a new problem, after a few times trying my pc couldn't find the phone anymore.
In the device manager it says 'Unknown USB device (Device descriptor request failed) ' I tried to update the driver with the MTK65xx vcom usb driver and a got a new error: 'The folder you specified doesnt contain a compatible software driver for your device. If the folder contains a driver, make sure it is designed to work with windows for 64x-based systems. ( i tried multiple, all the same error) its so hopeless.. now its official DEAD bricked. I think i stay with my old redmi phone
Click to expand...
Click to collapse
Unknown USB device is also a common issue, even with devices that are fully functional. This isn't due to being bricked, it is because Windows has "forgotten" your device. That error usually corrects itself, you just have to keep trying to connect your device. There are some solutions that can be found on the internet if you do some searching for:
"Device descriptor request failed"
You might find a way to correct that error. There are more if you search for them.
Here is one possible solution.
https://m.youtube.com/watch?v=hKwRUdfRN2s
Sent from my SM-S767VL using Tapatalk

Droidriven said:
The connect/disconnect/connect issue is normal, you have to get the order of operations and the timing correct, if you do it right at exactly the right time, it should work.
There are plenty of threads and posts that discuss the connection process and the timing involved.
SP flashtool is primarily used to flash stock firmware, not custom ROMs. The problem is your firmware didn't come with a scatter file in the firmware file.
I know you tried to create a scatter file but did you try the method in the video linked below?
https://m.youtube.com/watch?v=BNlXT4EMUtY
Or maybe you can use just the scatter file from another device that is similar to yours, if you find a scatter file from a device that has the same partition structure as yours, it should work. The scatter file is only used to tell SP flashtool which partitions to flash the imgs to.
Sent from my SM-S767VL using Tapatalk
Click to expand...
Click to collapse
Thanks, but the driver problem fixed itself. I think using miracle box to create a scatter isn't an option because I formatted the phone, didn't make that clear
Now I try to find a similar scatter file with the same partition info. How do I get info about the partition list, cant find anything about it.
the only thing is I got the IMEI code.
this is the image file :
https://ibb.co/hX59FMc
https://ibb.co/64GFzmz

Hello
Maybe I am late, but the official stock ROM incl. the Scatter file, is available on
ROM Nomu M8 | [Official] add the 11/13/2020 on Needrom
I have uploaded it on Nov 2020 - myabe you can get your Nomu M8 back to life.
It's a nice phone by the way, by rooting it with Magisk you can erase the terrible startup sound.
And with Greenify the battery life is much longer.

Napfgeist said:
Hello
Maybe I am late, but the official stock ROM incl. the Scatter file, is available on
ROM Nomu M8 | [Official] add the 11/13/2020 on Needrom
I have uploaded it on Nov 2020 - myabe you can get your Nomu M8 back to life.
It's a nice phone by the way, by rooting it with Magisk you can erase the terrible startup sound.
And with Greenify the battery life is much longer.
Click to expand...
Click to collapse
You can help install magisk tutorial?
I try another rom?

Napfgeist said:
Hello
Maybe I am late, but the official stock ROM incl. the Scatter file, is available on
ROM Nomu M8 | [Official] add the 11/13/2020 on Needrom
I have uploaded it on Nov 2020 - myabe you can get your Nomu M8 back to life.
It's a nice phone by the way, by rooting it with Magisk you can erase the terrible startup sound.
And with Greenify the battery life is much longer.
Click to expand...
Click to collapse
Thank you! It worked now finding a proper OS for the device, think LineageOS would do a good job