Database Info

After flashing stock ics, phone dont boot, help please

first of all, sorry for my bad English, try to be as clear as possible
Accidentally i flash a rom in system 1 with bmm..... a warning appeared when I rebooted the phone
"bmm menu would not be available in the next reboot" then I went to the system keeper option and reinstall bmm ..... when i tried to reboot the phone the same message appeared on the screen again .... "bmm menu would not be ..."
then i decided to flash ics stock (as I always do when i have a problem) , i put the phone in ap FastBoot .. Select the firmware and started the rsd process
all ended well ... unplug the phone and restart
ohh surprise! ... The phone does not boot, i cant even see the motorola logo, the phone just stuck there
Additional detail: this is the first time i flash firmware after losing my cid
Can someone help me?
Thanks in advance

Boot by bp tool
Steps
1. Press power button ,vol+ & vol- simultaneously
2. Select bp tool here and it will boot.
Best of luck
Sent from my MB865 using XDA Premium 4 mobile app

Thanks mithun23, i will try that

I've tried that and it did not work ... now the phone reboots, shows the motorola logo and keeps restarting(bootlooping)
if i re flash the firmware with rsd, the procces finish well, but the phone do the boot loop again
i dont know what else i can do :crying:
I've been thinking about buying a nexus 4 ... maybe it's time to do it.

jualros said:
I've tried that and it did not work ... now the phone reboots, shows the motorola logo and keeps restarting(bootlooping)
if i re flash the firmware with rsd, the procces finish well, but the phone do the boot loop again
i dont know what else i can do :crying:
I've been thinking about buying a nexus 4 ... maybe it's time to do it.
Click to expand...
Click to collapse
Try Factory Reset and Clear Cache from Stock Recovery.

I've tried that too, but nothing happens ...
Again I clarify the symptoms:
Point 1 - When the phone starts, shows the motorola logo and the message "Error CustomerID Contact Dealer Boot to Suspend / MDCT mode: 0000:00000000:000000 cc.". Then the screen gets black and nothing happens
Point 2-If I turn on the phone by holding down the volume keys (+ / -) and the power button (boot mode selection menu) and select any of the options ... the screen goes black and nothing happens
Point 3 - If I turn on the phone by holding down the volume key (-) and the power button (ap fastboot flash mode) ... I can connect the phone, start and finish the flashing process correctly. When the process ends it happens again point 1 or point 2
It may be a hardware failure?

jualros said:
I've tried that too, but nothing happens ...
Again I clarify the symptoms:
Point 1 - When the phone starts, shows the motorola logo and the message "Error CustomerID Contact Dealer Boot to Suspend / MDCT mode: 0000:00000000:000000 cc.". Then the screen gets black and nothing happens
Point 2-If I turn on the phone by holding down the volume keys (+ / -) and the power button (boot mode selection menu) and select any of the options ... the screen goes black and nothing happens
Point 3 - If I turn on the phone by holding down the volume key (-) and the power button (ap fastboot flash mode) ... I can connect the phone, start and finish the flashing process correctly. When the process ends it happens again point 1 or point 2
It may be a hardware failure?
Click to expand...
Click to collapse
Last, but not the least, I hope you are using the correct FXZ file for your region?

EDIT
@mithun23
after flashing attempt number six:
I could enter the bp tools mode, the phone boot, and it works.What i can do in this mode?
Why I still can not boot normally?

XploitMachine said:
Last, but not the least, I hope you are using the correct FXZ file for your region?
Click to expand...
Click to collapse
I'm using the same FXZ file that I've always used (is not for my region, but always work for me with no issues)

jualros said:
EDIT
@mithun23
after flashing attempt number six:
I could enter the bp tools mode, the phone boot, and it works.What i can do in this mode?
Why I still can not boot normally?
Click to expand...
Click to collapse
Good man u booted...
Well since ur cid is lost u cannot boot normally..u can boot only using bp tool.
Install bmm from Google play..then u will be able to boot normally.
Sent from my MB865 using XDA Premium 4 mobile app

mithun23 said:
Good man u booted...
Well since ur cid is lost u cannot boot normally..u can boot only using bp tool.
Install bmm from Google play..then u will be able to boot normally.
Sent from my MB865 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I installed bmm, but there is a problem ... boot menu manager requires root ...
when I try to root the phone, the process automatically restarts the phone and gets stuck on the motorola logo (since it no longer resets normally) ... then the root process can never be completed :crying:
I will continue doing more tests

when the phone starts normally, something similar to the root process of jelly bean leak happens ...
the method for jelly bean leak was something like this (the swapp method):
1 - the phone began in ap fastboot mode
2 - using a command line, the ics boot.img sends to the phone
3 - then the phone is unplugged from the usb cable and restarted
4 - the phone boots and gets a black screen
5 - plug the phone to the usb cable again and run the root tool for ics
5 - the phone restart 3 times (the root process is done)
6 - restart the phone in ap fast boot again
7 - using a command line, the jelly bean boot.img sends to the phone
8 - restart the phone and all is done
so....what is happening with my atrix 2 is something like step 4, is like boot.img is missing or corrupted

SOLVED : I boot using bp tools, then i found a root method that works , finally i get my phone rooted...so i've installed bmm and booted fine again....thx to those who takes the time to answer in this post
Sent from my MB865 using XDA Premium 4 mobile app

jualros said:
SOLVED : I boot using bp tools, then i found a root method that works , finally i get my phone rooted...so i've installed bmm and booted fine again....thx to those who takes the time to answer in this post
Sent from my MB865 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Which root method did u use ?
Sent from my MB865 using XDA Premium 4 mobile app

I download 2 scrips here in xda atrix 2 forum, 1 of those doesnt work (the process reboot the phone and get bootlooping), the other one works. I don't remember the post, but i can upload it and give you the link if you need it.
Sent from my MB865 using XDA Premium 4 mobile app

jualros said:
I download 2 scrips here in xda atrix 2 forum, 1 of those doesnt work (the process reboot the phone and get bootlooping), the other one works. I don't remember the post, but i can upload it and give you the link if you need it.
Sent from my MB865 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
your phone att atrix 2 on 4.0.4, if so please post that link here so i can use it. im totally stucked with this 4.0.4

Golhaaboa said:
your phone att atrix 2 on 4.0.4, if so please post that link here so i can use it. im totally stucked with this 4.0.4
Click to expand...
Click to collapse
Were you asking him whether his device is att or not? I don't think so. Seems like he has been flashing jb leak on his. And were you asking for att ics fxz file? Sorry got confused for a while. Here you go. Be sure to choose the right one
http://sbf.droid-developers.org/phone.php?device=17

Heelpp..! BMM not appear, and the phone stayed restarting does nothing but nothing out of the motorola logo screen goes black for a minute and not start, should show BBM but no longer does, and prior to the reboot when installation is complete and I gave keeper system option "Install bmm to main system" not only told me BBM started after reboot and so did not know what to do now ..: S can not access the system 3 is where I have q my other system help please.. had stock 4.0.4 att in system 1 and LiquidSmooth v3.0 (4.4.2) in system 3 what can i do? I was trying to install on your system 1 LiquidSmooth 3.1 (4.4.3) step by step pls..

saga02 said:
Heelpp..! BMM not appear, and the phone stayed restarting does nothing but nothing out of the motorola logo screen goes black for a minute and not start, should show BBM but no longer does, and prior to the reboot when installation is complete and I gave keeper system option "Install bmm to main system" not only told me BBM started after reboot and so did not know what to do now ..: S can not access the system 3 is where I have q my other system help please.. had stock 4.0.4 att in system 1 and LiquidSmooth v3.0 (4.4.2) in system 3 what can i do? I was trying to install on your system 1 LiquidSmooth 3.1 (4.4.3) step by step pls..
Click to expand...
Click to collapse
If BMM is not appearing at startup, then FXZ is only option !!
FXZ (with your region)---->>root--->> install BMM---->> flash ROM.
Watch BMM video tutorial available in general section, for proper BMM usage

sameerm02 said:
If BMM is not appearing at startup, then FXZ is only option !!
FXZ (with your region)---->>root--->> install BMM---->> flash ROM.
Watch BMM video tutorial available in general section, for proper BMM usage
Click to expand...
Click to collapse
thank you ..! I resolved the problem already doing that

Pull storage from damaged device

So I accidentally dropped my nexus 5 and I need to replace my display but unfortunately I haven't backed up my data (mostly pictures I'm worrying about the most). So is there a way to pull the storage from it? I've tried with adb and it doesn't work because it doesn't list my device.
I really hope there is a way to do it.

If USB works and its not detecting adb, then its set up wrong. Adb is the only way if both touch and display are broken.
Please click the link in my signature and read the adb and fastboot thread. It will tell you how to set it up properly
Sent from my Nexus 5 using Tapatalk

Does it matter if I had an unlock code for my lockscreen?

dndwanted said:
Does it matter if I had an unlock code for my lockscreen?
Click to expand...
Click to collapse
Yes it does.
Don't suppose you have a custom recovery do you?
Sent from my Nexus 5 using Tapatalk

My phone was rooted and I had latest TWRP with latest Paranoid Android,

dndwanted said:
My phone was rooted and I had latest TWRP with latest Paranoid Android,
Click to expand...
Click to collapse
Adb in recovery then. See the thread i previously told you about
Sent from my Nexus 5 using Tapatalk

I can't seem to make it work.
In "adb devices", it shows a device listed but in "fastboot devices" it doesn't show any device. When I tried to boot into fastboot mode I couldn't tell if I booted correctly because it shows the same thing as when I boot it normally.
I tried using the command "adb pull data/media/0 C:\adb\sdcard_25082014" and it gave me the error "remote object data/media/0 does not exist".
What should I do?

dndwanted said:
I can't seem to make it work.
In "adb devices", it shows a device listed but in "fastboot devices" it doesn't show any device. When I tried to boot into fastboot mode I couldn't tell if I booted correctly because it shows the same thing as when I boot it normally.
I tried using the command "adb pull data/media/0 C:\adb\sdcard_25082014" and it gave me the error "remote object data/media/0 does not exist".
What should I do?
Click to expand...
Click to collapse
You've not read my thread properly. Try again
Sent from my Nexus 5 using Tapatalk

I installed the adb in 15 seconds thing and then I followed this thread http://forum.xda-developers.com/google-nexus-5/general/noob-read-adb-fastboot-how-hep-t2807273
Please tell me what have I done wrong because I can't seem to figure it out.

Unfortunately I don't know a solution to your problem, but your data shouldn't get lost when you replace the screen.
I replaced mine a week ago. Actually it was very easy. The most difficult part was removing the backcover.
The parts inside of the device are fixed with a little bit of glue which is not strong at all.
The whole replacement took me around 20 Minutes and I have never done something like that before.
After that everything was still on my phone.
And if your device doesn't get recognized from your computer in fastboot mode you should try the universal adb driver. This works perfectly for my Nexus 5.

@rootSU
I get this: http://imgur.com/ccw4lJ6
:/

ChickenNugget said:
Unfortunately I don't know a solution to your problem, but your data shouldn't get lost when you replace the screen.
I replaced mine a week ago. Actually it was very easy. The most difficult part was removing the backcover.
The parts inside of the device are fixed with a little bit of glue which is not strong at all.
The whole replacement took me around 20 Minutes and I have never done something like that before.
After that everything was still on my phone.
And if your device doesn't get recognized from your computer in fastboot mode you should try the universal adb driver. This works perfectly for my Nexus 5.
Click to expand...
Click to collapse
He doesn't need fastboot mode, only recovery and adb seems to be working fine.
OP, try adb pull /data/media/0/ c:\blah blah
Sent from my Nexus 5 using XDA Free mobile app

jd1639 said:
He doesn't need fastboot mode, only recovery and adb seems to be working fine.
OP, try adb pull /data/media/0/ c:\blah blah
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Unfortunately I get the same error.

dndwanted said:
Unfortunately I get the same error.
Click to expand...
Click to collapse
Are you SURE you're in recovery?
You got an error when you mounted data
Edit, well you got 2 errors...
The first error you got was the "usage" line. That means it thinks you typed "mount data" as an incomplete command. It IS incomplete if you're booted into android. Its not incomplete if you're in recovery. So I dont think you're in recovery.
The second error is "remote object doesnt exist". That's because you haven't mounted data.
To ensure youre in recovery, either:
1) Boot into android and then "adb reboot recovery"
2) From off, hold vol down and press power to get to bootloader. Press vol up TWICE then press power
Sent from my Nexus 5 using Tapatalk

rootSU said:
Are you SURE you're in recovery?
You got an error when you mounted data
Edit, well you got 2 errors...
The first error you got was the "usage" line. That means it thinks you typed "mount data" as an incomplete command. It IS incomplete if you're booted into android. Its not incomplete if you're in recovery. So I dont think you're in recovery.
The second error is "remote object doesnt exist". That's because you haven't mounted data.
To ensure youre in recovery, either:
1) Boot into android and then "adb reboot recovery"
2) From off, hold vol down and press power to get to bootloader. Press vol up TWICE then press power
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
http://imgur.com/KCoHxg8

dndwanted said:
http://imgur.com/KCoHxg8
Click to expand...
Click to collapse
Unless you can get recovery to show up, you're screwed.
I don't know anything about twrp so I can't help there.
Sent from my Nexus 5 using Tapatalk

Looking at my phone, I can't tell whether I'm in recovery or just booting normally or whatever because it doesn't show anything.
I guess I'll just have to wait until someone who knows TWRP can help me.
But thank you anyways

dndwanted said:
Looking at my phone, I can't tell whether I'm in recovery or just booting normally or whatever because it doesn't show anything.
I guess I'll just have to wait until someone who knows TWRP can help me.
But thank you anyways
Click to expand...
Click to collapse
Try manually option 2
Otherwise you can fastboot flash philz recovery - which is a recovery I know.
Sent from my Nexus 5 using Tapatalk

Doesn't work.

dndwanted said:
Doesn't work.
Click to expand...
Click to collapse
In more descriptive terms please
Sent from my Nexus 5 using Tapatalk

[Q] Can't unlock bootloader

Hi, I recently bought a N5 from another guy. The previous owner told me that it bootlops, and it does. So I tried to format and install stock Lollipop from fastboot: the phone is locked, so when I type "fastboot oem unlock" the phone shows the red line "LOCK STATE - unlocked", then, when I type "fastboot reboot-bootloader" the phone reboots again into bootloader and shows me "LOCK STATE - locked" so I'm not able to perform any wipe or flash. You can also see it from the attached pics. What can cause this?

scleone1987 said:
Hi, I recently bought a N5 from another guy. The previous owner told me that it bootlops, and it does. So I tried to format and install stock Lollipop from fastboot: the phone is locked, so when I type "fastboot oem unlock" the phone shows the red line "LOCK STATE - unlocked", then, when I type "fastboot reboot-bootloader" the phone reboots again into bootloader and shows me "LOCK STATE - locked" so I'm not able to perform any wipe or flash. You can also see it from the attached pics. What can cause this?
Click to expand...
Click to collapse
Instead of using the command line, try rebooting into the boot loader manually with the power and bottom volume key.
Sent from my Nexus 7 using XDA Free mobile app

TBH, no device should be able to lock and unlock itself upon reboot. I'm pretty sure it's borked

EverDawn4 said:
Instead of using the command line, try rebooting into the boot loader manually with the power and bottom volume key.
Sent from my Nexus 7 using XDA Free mobile app
Click to expand...
Click to collapse
Tried now but nothing. Still "LOCK STATE - locked" after reboot.

Could you flash a factory image right after you unlock it?
Sent from my Nexus 7 using XDA Free mobile app

If it immediately re-locks, 99 times out of 100 means NAND is fried.

EverDawn4 said:
Could you flash a factory image right after you unlock it?
Sent from my Nexus 7 using XDA Free mobile app
Click to expand...
Click to collapse
If I try to flash the new bootloader "fastboot flash bootloader..." after performing "fastboot oem unlock" and trying NOT to reboot, it sends the bootloader and when trying to write it shows up "FAILED (remote: flash write failure) as you can see from the screen.

rootSU said:
If it immediately re-locks, 99 times out of 100 means NAND is fried.
Click to expand...
Click to collapse
+1
Sent from my Nexus 9 using XDA Free mobile app

Can I change the NAND flash? Or let somebody make it for me?

scleone1987 said:
Can I change the NAND flash? Or let somebody make it for me?
Click to expand...
Click to collapse
You can buy a new motherboard.

rootSU said:
You can buy a new motherboard.
Click to expand...
Click to collapse
Can I find a cheap one somewhere on the internet? Like no more than 50 euros

scleone1987 said:
Can I change the NAND flash? Or let somebody make it for me?
Click to expand...
Click to collapse
If the NAND is fried it's a nearly hopeless case. You would have to replace a lot of your phone's components.
Sent from my Nexus 7 using XDA Free mobile app

My nexus 5 bootloops and stuck in startup animation
Hi could you solve that problem. I am in the same situation. My nexus 5 bootloops and stuck in startup animation. Please let me know, if you found a way to solve the problem.
scleone1987 said:
Hi, I recently bought a N5 from another guy. The previous owner told me that it bootlops, and it does. So I tried to format and install stock Lollipop from fastboot: the phone is locked, so when I type "fastboot oem unlock" the phone shows the red line "LOCK STATE - unlocked", then, when I type "fastboot reboot-bootloader" the phone reboots again into bootloader and shows me "LOCK STATE - locked" so I'm not able to perform any wipe or flash. You can also see it from the attached pics. What can cause this?
Click to expand...
Click to collapse

In my case the sdcard was fried. I had to sell the phone to another guy.

Hi , how can i confirm the NAND is fried ? I am in the same position as above.

I have the same situation, and would also like to know if there is a way to tell/test failed NAND. Is anyone can enlighten us? I'll really appreciate any help!

i have a nexus 5x that had a motherboard replaced under warranty but now it seems the nand is dead too cos i cant open the bootloader, it sets itself back to locked, could i complain and get it fixed under warranty?

I would complain because an unlocked bootloader is needed to flash a stock rom.

Recovery only..

I have a Oneplus One here and tried to install a rom onto it after wiping everything.
When I plug it in the charger it goes to recovery, when I reboot to bootloader it does the same, after flashing too.
How can I recover it?

Did you install TWRP or CWM ? If so try another rom , if not read up on adb and install custom recovery first and find out if your bl is unlocked , if not start there , theres alot of reading you need to do
Sent from my A0001 using XDA-Developers mobile app

Vintage144 said:
Did you install TWRP or CWM ? If so try another rom , if not read up on adb and install custom recovery first and find out if your bl is unlocked , if not start there , theres alot of reading you need to do
Sent from my A0001 using XDA-Developers mobile app
Click to expand...
Click to collapse
I have TWRP. I had a rom installed so the bootloader is unlocked. All the guides suggest fixing it via fastboot but I cannot access that.. I think the partitions are messed up...

mrgnex said:
I have TWRP. I had a rom installed so the bootloader is unlocked. All the guides suggest fixing it via fastboot but I cannot access that.. I think the partitions are messed up...
Click to expand...
Click to collapse
Hey I think you have same problem as me. It's the volume button. It's stuck at Volume - (down). So every time you start your phone, it think you want to go to Recovery. What I did was, I tap the phone little hard on my hand sideways when I boot it up. That unstucks the volume button.
It works for me but not sure if it is the correct way. Just a suggestion. Don't hold me responsible if it breaks anything else.

viny2cool said:
Hey I think you have same problem as me. It's the volume button. It's stuck at Volume - (down). So every time you start your phone, it think you want to go to Recovery. What I did was, I tap the phone little hard on my hand sideways when I boot it up. That unstucks the volume button.
It works for me but not sure if it is the correct way. Just a suggestion. Don't hold me responsible if it breaks anything else.
Click to expand...
Click to collapse
I wish it was that easy. I didn't have the back cover on it when I tried this.

Did you have a backup of the previous rom (if one) that would save you the trouble, if not , adb
Sent from my A0001 using XDA-Developers mobile app

Hi, were you able to find a solution for this? I'm getting same issue now. PFA dmesg output http://pastebin.com/dKqm9e0c

I've hardbricked my mt6737

Hi,
I decided to flash an another rom to my mt6737 (Wieppo s8 clone) and I got a pmt error in sp flash tool. Until this, my phone was working well and when I looked for a way to fix that pmt error in flashing on sp flash tool, my phone just D I E D in my hands when I applied this "fix".
(no more life signs: no charging animation, no bootanimation, nothing except a black screen).
To be more specific : I was looking to install twrp with a rom that is incompatible with my phone (it was too late when I knew it) and I had the error "pmt changed for the rom it must be downloaded please select format all+download scene and try again" so I went to the "format" tab and I chose the option "format whole flash except bootloader" and from there, my phone died
After this, I found an another rom with the same chip and alléuia, when I flash it, it says "Download Ok" with the green thing and the yellow bar. My phone just vibrate now but still dead, when I push the power button, vibrations only happens but nothing more, just a black screen. What can I do now ?,
PS : my phone is a ECHO HORIZON Lite +
More info for this phone here : https://www.lesnumeriques.com/telephone-portable/echo-horizon-lite-p41185/test.html

help pls

Noel97 said:
Hi,
I decided to flash an another rom to my mt6737 (Wieppo s8 clone) and I got a pmt error in sp flash tool. Until this, my phone was working well and when I looked for a way to fix that pmt error in flashing on sp flash tool, my phone just D I E D in my hands when I applied this "fix".
(no more life signs: no charging animation, no bootanimation, nothing except a black screen).
To be more specific : I was looking to install twrp with a rom that is incompatible with my phone (it was too late when I knew it) and I had the error "pmt changed for the rom it must be downloaded please select format all+download scene and try again" so I went to the "format" tab and I chose the option "format whole flash except bootloader" and from there, my phone died
After this, I found an another rom with the same chip and alléuia, when I flash it, it says "Download Ok" with the green thing and the yellow bar. My phone just vibrate now but still dead, when I push the power button, vibrations only happens but nothing more, just a black screen. What can I do now ?,
PS : my phone is a ECHO HORIZON Lite +
More info for this phone here : https://www.lesnumeriques.com/telephone-portable/echo-horizon-lite-p41185/test.html
Click to expand...
Click to collapse
Most MTK devices can be unbricked using a "test point" method that involves opening the device and using a jumper to short certain pins to force the device into a state that can be used to recover/flash the device to unbrick it.
See if you can any information about this in regard to your specific model number.
Sent from my SM-S767VL using Tapatalk

Hey, thanks for your reply.
I can't open my phone dude.
There's not an another method ?

Noel97 said:
Hey, thanks for your reply.
I can't open my phone dude.
There's not an another method ?
Click to expand...
Click to collapse
The device was assembled, it can be disassembled. Find a breakdown video of your specific model number on YouTube. It has to be made in such a way that it can be disassembled to make repairs to the hardware. I didn't say that getting the device open would be easy.
Sent from my SM-S767VL using Tapatalk

Droidriven said:
The device was assembled, it can be disassembled. Find a breakdown video of your specific model number on YouTube. It has to be made in such a way that it can be disassembled to make repairs to the hardware. I didn't say that getting the device open would be easy.
Sent from my SM-S767VL using Tapatalk
Click to expand...
Click to collapse
I...I just don't know how to do even with a video. I've never did earlier, I just can't open my phone

Noel97 said:
I...I just don't know how to do even with a video. I've never did earlier, I just can't open my phone
Click to expand...
Click to collapse
Good luck then.
Sent from my SM-S767VL using Tapatalk

Hey, I forgot to say that I can still flash roms with the green mark (Download OK) but my phone won't boot

Noel97 said:
Hey, I forgot to say that I can still flash roms with the green mark (Download OK) but my phone won't boot
Click to expand...
Click to collapse
Try booting to recovery mode and factory reset and wipe cache. You probably have user data still on the device that is conflicting with the new system.
Sent from my SM-S767VL using Tapatalk

Droidriven said:
Try booting to recovery mode and factory reset and wipe cache. You probably have user data still on the device that is conflicting with the new system.
Sent from my SM-S767VL using Tapatalk
Click to expand...
Click to collapse
The screen is black,my phone won't boot, I can't go into recovery mode even after I flashed the rom.
So I can't do a factory reset and i can't wipe cache.What should I do now ?

Noel97 said:
The screen is black,my phone won't boot, I can't go into recovery mode even after I flashed the rom.
So I can't do a factory reset and i can't wipe cache.What should I do now ?
Click to expand...
Click to collapse
Can you get to fastboot mode?
Can you flash the individual img/partition files?
Sent from my SM-S767VL using Tapatalk

Droidriven said:
Can you get to fastboot mode?
Can you flash the individual img/partition files?
Sent from my SM-S767VL using Tapatalk
Click to expand...
Click to collapse
How to enter in fastboot mode ?
What do you mean by " flash the individual img/partition files" ?
Thanks

Noel97 said:
How to enter in fastboot mode ?
What do you mean by " flash the individual img/partition files" ?
Thanks
Click to expand...
Click to collapse
Boot, recovery, system, etc....
Using fastboot or SPFT, whichever you can get working on your device.
Sent from my SM-S767VL using Tapatalk

Yes, I think
I am using SPFT

Okay guys, I give up now.
Thank to everyone for their help.

Noel97 said:
Okay guys, I give up now.
Thank to everyone for their help.
Click to expand...
Click to collapse
Take it as a learning lesson and don't make the same mistakes twice. Don't just assume that you can flash or modify your device without issues and don't assume that something that worked on another device with the same device name will work on yours, plenty of devices have the same device name but have different model numbers, the model number is what matters, not the device name.
Always use your specific device's model number in your searches to find what you can and can not do to your device, find what is safe and what isn't, find what has been confirmed to work on your specific model number. Also remember that your android version or specific stock firmware build number can change whether or not what you find will work on your device. For example, just because you find instructions for modifying a device that has the same model number as yours, does not mean those instructions will work for you if your device's android version or stock firmware build number is different than the android version or build number than what is in the instructions that you find.
Don't just research what "can" be done on your device, also research what you "shouldn't" do, do research to find out what can go wrong and how others have screwed their devices up when trying to modify their device and what they had to do to fix it. This will help you avoid the issues they had or will help you fix it if you have the same issue they had.
Your first mistake was assuming that you could just modify your device without issues. Your next mistake was not researching to see what could possibly go wrong in the process.
Sent from my SM-S767VL using Tapatalk

Droidriven said:
Boot, recovery, system, etc....
Using fastboot or SPFT, whichever you can get working on your device.
Sent from my SM-S767VL using Tapatalk
Click to expand...
Click to collapse
UPDATE : I found the exact firmware and I flashed it (with the green ring "Download OK" but I still get a black screen but nevertheless, compared to before my phone vibrates, You have an idea ?

Yeah I learned my lesson, I will never try to mod my phone again, thank you for this reminder.
If we fix my phone, then I won't do it again.
So please help as much you can, thank you.

I also have a grey screen when I try to switch to recovery mode, by grey screen I mean it's like the phone starts but with nothing in it, no text, nada