Database Info

When I turn my phone on, it reboots over and over again, HELP PLEASE!

So I used my galaxy note edge SM-N915F for 6 months with no problem, but I did the Marshmallow 6.0.1 update and now it doesn't work. As I said in the title when I try to start it reboots over and over again.
Any suggestions?? It opens only downloading mode and I flashed a rom(official russian Marshmallow 6.0.1 rom) with Odin and it didn't work.
Please help me! Thanks in advanced!

gazeL_ said:
So I used my galaxy note edge SM-N915F for 6 months with no problem, but I did the Marshmallow 6.0.1 update and now it doesn't work. As I said in the title when I try to start it reboots over and over again.
Any suggestions?? It opens only downloading mode and I flashed a rom(official russian Marshmallow 6.0.1 rom) with Odin and it didn't work.
Please help me! Thanks in advanced!
Click to expand...
Click to collapse
When using the correct button combination are you able to enter recovery or does it continue to bootloop? Power, Home and Volume Up is used to enter recovery. When you attempted to flash the stock firmware through Odin, where did you download the stock firmware from?
Sent from my Nexus 6 using XDA-Developers mobile app

fast69mopar said:
When using the correct button combination are you able to enter recovery or does it continue to bootloop? Power, Home and Volume Up is used to enter recovery. When you attempted to flash the stock firmware through Odin, where did you download the stock firmware from?
Click to expand...
Click to collapse
Yes, it continue to bootloop even when I try to open in recovery mode. I succesfully entered recovery mode only one time and was able to full wipe, full cache the phone. This is after the flashing. I flashed the stock firmware a week ago and I actually don't remember where I downloaded it from. Thanks for your interest.

gazeL_ said:
Yes, it continue to bootloop even when I try to open in recovery mode. I succesfully entered recovery mode only one time and was able to full wipe, full cache the phone. This is after the flashing. I flashed the stock firmware a week ago and I actually don't remember where I downloaded it from. Thanks for your interest.
Click to expand...
Click to collapse
Most firmwares are available from sammobile.com. Which version of Odin are you using? Also, when you performed the flash through Odin, did Odin show the flash to be successful on the progress window? Was your Note Edge rooted or did you have a custom recovery installed before the bootloop issue started?

fast69mopar said:
Most firmwares are available from sammobile.com. Which version of Odin are you using? Also, when you performed the flash through Odin, did Odin show the flash to be successful on the progress window? Was your Note Edge rooted or did you have a custom recovery installed before the bootloop issue started?
Click to expand...
Click to collapse
I used Odin3. Yes, Odin showed me the flash to be successful. My Edge didn't rooted before and I didn't have a custom recovery. I had an official software. I actually want to add an screenshot but XDA doesn't let me.

gazeL_ said:
I used Odin3. Yes, Odin showed me the flash to be successful. My Edge didn't rooted before and I didn't have a custom recovery. I had an official software. I actually want to add an screenshot but XDA doesn't let me.
Click to expand...
Click to collapse
Have you tried a different version of Odin to perform the flash? I have 3.07 and 3.10 and sometimes one version will work perfectly and the other will show a successful flash but the device will still bootloop. Check which version you have and then download a different one to test with. That may be your issue.
Also, can you enter recovery at all anymore? If you try to enter recovery several times in a row during the bootloop process you may be able to access it after a few attempts. If you can enter recovery, wipe data/factory reset for me. Then attempt to boot. If it loops again, download the official firmware from sammobile.com and flash it with your original version of Odin. If it still loops, then flash it again with the different version of Odin. Lemme know how it goes. I'll do what I can to help.

fast69mopar said:
Have you tried a different version of Odin to perform the flash? I have 3.07 and 3.10 and sometimes one version will work perfectly and the other will show a successful flash but the device will still bootloop. Check which version you have and then download a different one to test with. That may be your issue.
Also, can you enter recovery at all anymore? If you try to enter recovery several times in a row during the bootloop process you may be able to access it after a few attempts. If you can enter recovery, wipe data/factory reset for me. Then attempt to boot. If it loops again, download the official firmware from sammobile.com and flash it with your original version of Odin. If it still loops, then flash it again with the different version of Odin. Lemme know how it goes. I'll do what I can to help.
Click to expand...
Click to collapse
I tried different Odin versions but it didn't work. I can flash rom succesfully but after the flashing it doesn't open in recovery mode. It bootloops. Once, it opened in recovery mode and I did wipe data/factory reset after first flashing and it didn't work. Now, it still doesn't open anyway except Downloading Mode.

gazeL_ said:
I tried different Odin versions but it didn't work. I can flash rom succesfully but after the flashing it doesn't open in recovery mode. It bootloops. Once, it opened in recovery mode and I did wipe data/factory reset after first flashing and it didn't work. Now, it still doesn't open anyway except Downloading Mode.
Click to expand...
Click to collapse
Are you flashing the exact same ROM version you were using before this problem started? We're you using 5.1.1 before you accepted the MM OTA?
Sent from my Nexus 6 using XDA-Developers mobile app

fast69mopar said:
Are you flashing the exact same ROM version you were using before this problem started? We're you using 5.1.1 before you accepted the MM OTA?
Click to expand...
Click to collapse
I used 5.1.1 to before I accepted the MM OTA and I didn't have any p roblem with 5.1.1. I tried to flash different type of 6.0.1 after the problem. Just, problem started with the MM OTA. I will try to flash 5.1.1. So, I guess I need to enter recovery to wipe data/factory reset before flashing 5.1.1 but I can not because it still bootloop. How can I do wipe data/factory reset?
Edit1: And I readed somewhere, they said that it is about the kernel? Is it possible?
Edit2: A few minutes ago, I succeeded to enter recovery mode, I did factory reset and phone still bootloop. It doesn't open. Now, I am downloading the 5.1.1. I will try to flash 5.1.1.
Edit3: I tried a lot of times but it is still same. I flashed the 5.1.1 with different versions of Odin. I successful with flashed it but phone wants to enter in recovery mode after flashing and it bootloops. It is trying to enter recovery mode all time but it doesn't work. Sometimes, on charge, it close to enter the recovery mode. I said in edit2 I succeeded to enter recovery mode, but I didn't say that it was on charge because I discover this now. So, I don't know what I have to do, I am waiting for your suggestions.

gazeL_ said:
I used 5.1.1 to before I accepted the MM OTA and I didn't have any p roblem with 5.1.1. I tried to flash different type of 6.0.1 after the problem. Just, problem started with the MM OTA. I will try to flash 5.1.1. So, I guess I need to enter recovery to wipe data/factory reset before flashing 5.1.1 but I can not because it still bootloop. How can I do wipe data/factory reset?
Edit1: And I readed somewhere, they said that it is about the kernel? Is it possible?
Edit2: A few minutes ago, I succeeded to enter recovery mode, I did factory reset and phone still bootloop. It doesn't open. Now, I am downloading the 5.1.1. I will try to flash 5.1.1.
Edit3: I tried a lot of times but it is still same. I flashed the 5.1.1 with different versions of Odin. I successful with flashed it but phone wants to enter in recovery mode after flashing and it bootloops. It is trying to enter recovery mode all time but it doesn't work. Sometimes, on charge, it close to enter the recovery mode. I said in edit2 I succeeded to enter recovery mode, but I didn't say that it was on charge because I discover this now. So, I don't know what I have to do, I am waiting for your suggestions.
Click to expand...
Click to collapse
Let's see if we can get your Note Edge into safe mode without bootlooping. Use these steps:
Turn on safe mode
Turn the device off.
Press and hold the Power and Volume down key.
Continue to hold the Volume down key until the device finishes restarting.
Safe mode will display in the bottom left corner of the screen.
Release the Volume down key when you see Safe Mode.
I have read a few forums and notes about booting into safe mode can stop the bootloop. Once it's successfully booted into safe mode we can attempt to boot normally. Give it a shot and I'll keep researching. Good luck.
Sent from my Nexus 6 using XDA-Developers mobile app

fast69mopar said:
Let's see if we can get your Note Edge into safe mode without bootlooping. Use these steps:
Turn on safe mode
Turn the device off.
Press and hold the Power and Volume down key.
Continue to hold the Volume down key until the device finishes restarting.
Safe mode will display in the bottom left corner of the screen.
Release the Volume down key when you see Safe Mode.
I have read a few forums and notes about booting into safe mode can stop the bootloop. Once it's successfully booted into safe mode we can attempt to boot normally. Give it a shot and I'll keep researching. Good luck.
Click to expand...
Click to collapse
I tried a lot of times but it didn't work. I tried on charge, without charge, with different cables but still bootloop. It is just like a joke.
I tried with Kies but Kies didn't see my edge. It didn't connect. On the Kies window, it said "connecting..." so I waited about 2 hours and it didn't connect. Then, I tried to emergency firmware recovery, it didn't see my edge again.

Download Samsung Smart Switch and see if it recognizes your device.
Sent from my Nexus 6 using XDA-Developers mobile app

I have the same problem with my friend's phone (SM-N915F) , I tried all the suggested solutions to no avail.

Qaseeh said:
I have the same problem with my friend's phone (SM-N915F) , I tried all the suggested solutions to no avail.
Click to expand...
Click to collapse
Do you have your friends device with you and a PC to use? Was your friend trying to root the device or install a custom recovery or a custom ROM when this happened?
Or, did your friend accept the OTA for 6.0.1 MM and then ended up in a bootloop after installing the OTA?

fast69mopar said:
Do you have your friends device with you and a PC to use? Was your friend trying to root the device or install a custom recovery or a custom ROM when this happened?
Or, did your friend accept the OTA for 6.0.1 MM and then ended up in a bootloop after installing the OTA?
Click to expand...
Click to collapse
Yes i still have my friend's phone with me and I have a PC .. he wasn't trying to root it or anything .. he said that the phone was too slow then it rebooted by itself then the bootloops started. i have tried several time to get to the recovery but I couldn't I can only put it on download mode that's where I tried to flash a 6.0.1 MM stock rom using odin and didn't succeed

Qaseeh said:
Yes i still have my friend's phone with me and I have a PC .. he wasn't trying to root it or anything .. he said that the phone was too slow then it rebooted by itself then the bootloops started. i have tried several time to get to the recovery but I couldn't I can only put it on download mode that's where I tried to flash a 6.0.1 MM stock rom using odin and didn't succeed
Click to expand...
Click to collapse
What version of Odin are you using to flash the factory firmware? Try to flash the firmware with a different version of Odin.
Also, you said the flash was unsuccessful using Odin. Was there an error message in Odin at the bottom left corner of the screen? If so, what was the error? I have had several flashes fail using one version of Odin but pass with a different version.
Also, what version of Android was your friends device using before you tried to flash the 6.0.1 firmware? If the device was running 5.1.1, have you tried to flash a 5.1.1 firmware with Odin?
Sent from my Nexus 6 using XDA-Developers mobile app

fast69mopar said:
What version of Odin are you using to flash the factory firmware? Try to flash the firmware with a different version of Odin.
Also, you said the flash was unsuccessful using Odin. Was there an error message in Odin at the bottom left corner of the screen? If so, what was the error? I have had several flashes fail using one version of Odin but pass with a different version.
Also, what version of Android was your friends device using before you tried to flash the 6.0.1 firmware? If the device was running 5.1.1, have you tried to flash a 5.1.1 firmware with Odin?
Sent from my Nexus 6 using XDA-Developers mobile app
Click to expand...
Click to collapse
I have used Odin version 1.85 then tried with Odin v3.11.1 , the flash succeeded no errors but the phone stayed as is .. Actually, he doesn't know the android version of his phone before it bricked. Are u suggesting that I should try to flash a 5.1.1?

Qaseeh said:
I have used Odin version 1.85 then tried with Odin v3.11.1 , the flash succeeded no errors but the phone stayed as is .. Actually, he doesn't know the android version of his phone before it bricked. Are u suggesting that I should try to flash a 5.1.1?
Click to expand...
Click to collapse
Search for Odin 3.07 and 3.10. I use both of these versions. When all else fails for me I use 3.07 and it always seems to work for me. Also, I'm betting it was running 5.1.1 because 6.0.1 hasn't been out that long for the Saudi Arabian Note Edge. I would flash the 5.1.1 stock firmware using Odin 3.07 and see if it will allow you to boot normally. Let me know how it goes. Good luck.
Sent from my Nexus 6 using XDA-Developers mobile app

fast69mopar said:
Search for Odin 3.07 and 3.10. I use both of these versions. When all else fails for me I use 3.07 and it always seems to work for me. Also, I'm betting it was running 5.1.1 because 6.0.1 hasn't been out that long for the Saudi Arabian Note Edge. I would flash the 5.1.1 stock firmware using Odin 3.07 and see if it will allow you to boot normally. Let me know how it goes. Good luck.
Sent from my Nexus 6 using XDA-Developers mobile app
Click to expand...
Click to collapse
I tried flashing android stock rom 5.1.1 like u suggested using Odin 3.07 and 3.10 but still nothing changed ... I think it's totally bricked.
Thank you fast69mopar I appreciate your inputs :good:

Qaseeh said:
I tried flashing android stock rom 5.1.1 like u suggested using Odin 3.07 and 3.10 but still nothing changed ... I think it's totally bricked.
Thank you fast69mopar I appreciate your inputs :good:
Click to expand...
Click to collapse
Dammit man. Ill keep looking through my Samsung stuff and see what I can find. I sent my cousin an email yesterday who works for Samsung in their Tier 3 Technical Support/Case Management Group and asked her for some help. I'm really curious as to what she has to say on the subject. When it comes to a Samsung Galaxy or Note device she is a PRO. When I run into an issue with any of my Samsung devices that I can't fix, I call or email her. Keep working on it and we will find a solution.

Stuck at Boot Loop, Need Help..

Here's the story,
This is my dad's phone. He just recently bought it. Out of nowhere, it stuck in bootloop (screen only show phone's model). He asked me if I can fix it.
I tried recovery mode and failed. It can't enter recovery mode. So I should fix it via download mode, right?
The thing is, I don't even know the firmware's phone. So I'm assuming it is Indonesian, cause I live in Indonesia.
I flash using odin and it passed but the phone still stuck.
When rebooting, the boot screen flashing 3-5 times (show phone's model - black screen - show phone's model - black screen - and so on), then stuck at boot screen again.
This is weird. So I thought maybe wrong firmware. I tried India and Phillipines (global) firmware too but the problem still exist.
I don't know how to solve it. Please help.
Phone's model: SM-J700F/DS

Um if you bought it from a samsung store, then take it back there.

my sasmsung galxy sm-j700f suddenly reboot to samsung lable
my mobile unable to open it flash to me "sasmung galaxy j7 powered by android" and it refuse to open then i flash the custom firmware by odin many times but it did not work then it try to flash twrp recovery and wibe data (factory reset )it did not work
Help please

gitompak said:
Here's the story,
This is my dad's phone. He just recently bought it. Out of nowhere, it stuck in bootloop (screen only show phone's model). He asked me if I can fix it.
I tried recovery mode and failed. It can't enter recovery mode. So I should fix it via download mode, right?
The thing is, I don't even know the firmware's phone. So I'm assuming it is Indonesian, cause I live in Indonesia.
I flash using odin and it passed but the phone still stuck.
When rebooting, the boot screen flashing 3-5 times (show phone's model - black screen - show phone's model - black screen - and so on), then stuck at boot screen again.
This is weird. So I thought maybe wrong firmware. I tried India and Phillipines (global) firmware too but the problem still exist.
I don't know how to solve it. Please help.
Phone's model: SM-J700F/DS
Click to expand...
Click to collapse
try this guide I made for restoring stock firmware from Samsung sever with the smartswitch app for Windows.
http://forum.xda-developers.com/galaxy-j7/j700t-development/how-to-restore-j700t1-model-to-t3423455
but you NEED YOUR SERIAL# AND MODEL # of that phone!

Fix # I dont know - if it works
Try this if it helps....
You will need ( link unavailable due to my little amount of posting and not using this account):
Galaxy J7 USB Drivers for the phone
The stock ROM for the phone (exact firmware)
Odin
First install Samsung Galaxy J7 USB drivers on Windows PC. Then Download the Samsung Galaxy J7 Stock Firmware from the link above and extract the folder on your desktop.
Download ODIN flash tool to flash the firmware on your phone. Extract the folder and you will see the ODIN.exe file in the folder.
Now Turn off your Galaxy J7 and Boot in download mode.(Hold down Volume Down + Home + Power button at the same time)
Once your Galaxy J7 is in download mode. Connect it to the PC with USB cable and run the ODIN.exe file on your desktop.
If everything is right and drivers are working properly. You will see the blue box on the ODIN screen, if not reinstall the drivers again and reboot your PC.
Now select the AP option from the ODIN screen and select the firmware file that you extracted
Hit the Start button from the ODIN screen to start the flashing process.
Once completed you will see the PASS messages on the ODIN and Phone will reboot automatically. Now you can disconnect your phone.
IMPORTANT:. If your phone is still stuck on the boot loop or in the Samsung Android Logo, then turn off the phone and reboot in recovery mode. TO do this Hold down Volume Up + Home + Power button at the same time. Now from recovery select Wipe Data/Factory Reset and after that Wipe cache partition. Now reboot you phone. If you are using a custom recovery, just wipe data/factory reset and wipe cache partition again.
DONE!!!! You unbricked your Galaxy J7. Now your Phone is running the stock ROM. Check it on the setting. ENJOY..

What is the recommended firmware for
SM-J700F/DS?? Can I flash it with any SM-J700F ?
Thanks!

hazembadr00 said:
my mobile unable to open it flash to me "sasmung galaxy j7 powered by android" and it refuse to open then i flash the custom firmware by odin many times but it did not work then it try to flash twrp recovery and wibe data (factory reset )it did not work
Help please
Click to expand...
Click to collapse
Can you not hijack threads and make your own please?

Samsung J6 Touch Not Working
J6 touch not working after official update

gitompak said:
Here's the story,
This is my dad's phone. He just recently bought it. Out of nowhere, it stuck in bootloop (screen only show phone's model). He asked me if I can fix it.
I tried recovery mode and failed. It can't enter recovery mode. So I should fix it via download mode, right?
The thing is, I don't even know the firmware's phone. So I'm assuming it is Indonesian, cause I live in Indonesia.
I flash using odin and it passed but the phone still stuck.
When rebooting, the boot screen flashing 3-5 times (show phone's model - black screen - show phone's model - black screen - and so on), then stuck at boot screen again.
This is weird. So I thought maybe wrong firmware. I tried India and Phillipines (global) firmware too but the problem still exist.
I don't know how to solve it. Please help.
Phone's model: SM-J700F/DS
Click to expand...
Click to collapse
Try to install TWRP on the phone, then try to wipe out the stock firmware that installed. And of course, reinstall the original stock firmware that come on that region. Its actually came from Indonesia, so be sure to install the right one.

Sijaygamer said:
What is the recommended firmware for
SM-J700F/DS?? Can I flash it with any SM-J700F ?
Thanks!
Click to expand...
Click to collapse
i need to know the answer for this please
i"ve tried every j700f rom out there nothing worked for me
is there any OFFICIAL firmware for the j700f/ds model ?

MATE 7 not booting

Hi, need some urgent help here.
I was trying to install a custom rom, so I unlocked first the bootloader, then flashed twrp 3.0.2 for Android 5.1 and with it I flashed KangVip rom (porto from honor 6).
Problem was it didn't boot, just black screen.
So I supposed the problem was with the rom so I flashed via fastboot the aosp 6, obviously with same results.
I tried lot of stuff (twrp 2.8.x.x, reinstall stock firmware, restore twrp backup of stock full firmware and so on - I did almost everything I could do) and now I'm with a Huge problem: no huawei logo at start, just a white screen and nothing happen. I have twrp 3.0.2 for 5.1 installed right now but I can't install stock recovery.
Please help me, what do I gotta do?
[emoji30]

the ported rom is based on Android 6.0 you have Android 5.1 youk should flash 5.1 based rom..
it's good to flash stock and update official to b560 or b571 depending on which region to have then flash twrp recovery and then flash desire rom..

fazi2015 said:
the ported rom is based on Android 6.0 you have Android 5.1 youk should flash 5.1 based rom..
it's good to flash stock and update official to b560 or b571 depending on which region to have then flash twrp recovery and then flash desire rom..
Click to expand...
Click to collapse
Thx for this.
But I have a problem, I can't install stock recovery and if I try to flash the .img files extracted from update.app nothing happens.
Also, I still have that problem with huawei logo disappeared and a blank white screen instead.
Sent from my HUAWEI GRA-L09 using Tapatalk

boot into bootloader and flash stock recovery but if you know what exactly firmware was you have(bxxx) then no need to flash recovery just put update.app to your sd card and then force update three buttons combination (volume both and power) turn off it remove data cable then press these three buttons it'll go in recovery sometime but try two or three times(in recovery turn off device) and try again if that method not work you should flash stock recovery to do so and if it didn't go to bootloader(fastboot) then connect data cable and then press vol- and power it'll go to bootloader in bootloader flash stock recovery then force update your device....

fazi2015 said:
boot into bootloader and flash stock recovery but if you know what exactly firmware was you have(bxxx) then no need to flash recovery just put update.app to your sd card and then force update three buttons combination (volume both and power) turn off it remove data cable then press these three buttons it'll go in recovery sometime but try two or three times(in recovery turn off device) and try again if that method not work you should flash stock recovery to do so and if it didn't go to bootloader(fastboot) then connect data cable and then press vol- and power it'll go to bootloader in bootloader flash stock recovery then force update your device....
Click to expand...
Click to collapse
Solved, thanks!
Sent from my HUAWEI GRA-L09 using Tapatalk

fazi2015 said:
boot into bootloader and flash stock recovery but if you know what exactly firmware was you have(bxxx) then no need to flash recovery just put update.app to your sd card and then force update three buttons combination (volume both and power) turn off it remove data cable then press these three buttons it'll go in recovery sometime but try two or three times(in recovery turn off device) and try again if that method not work you should flash stock recovery to do so and if it didn't go to bootloader(fastboot) then connect data cable and then press vol- and power it'll go to bootloader in bootloader flash stock recovery then force update your device....
Click to expand...
Click to collapse
Hope you can help me out here...I had just gotten my HAM7 for a couple of days. Was on 4.4.2 B120, was able to get it up to B326. Just yesterday I attempted to flash up to B331 and it succeeded according to the "local update" option. Then it went on boot loop. I tried doing the force 3-button option and that worked to the point of saying it succeeded and will reboot. Now I'm stuck on Ascend Mate logo. I can no longer get into factory option mode (V+Power), only fastboot mode. Also, I can't do force update no more so I can't try any other "update.app" unless I'm missing something here.
Any help in getting this unit at least back to working condition will be a BIG help. I just received this two days ago.
Thx!!!!

jfer671 said:
Hope you can help me out here...I had just gotten my HAM7 for a couple of days. Was on 4.4.2 B120, was able to get it up to B326. Just yesterday I attempted to flash up to B331 and it succeeded according to the "local update" option. Then it went on boot loop. I tried doing the force 3-button option and that worked to the point of saying it succeeded and will reboot. Now I'm stuck on Ascend Mate logo. I can no longer get into factory option mode (V+Power), only fastboot mode. Also, I can't do force update no more so I can't try any other "update.app" unless I'm missing something here.
Any help in getting this unit at least back to working condition will be a BIG help. I just received this two days ago.
Thx!!!!
Click to expand...
Click to collapse
are you have unlock bootloader or not..

fazi2015 said:
are you have unlock bootloader or not..
Click to expand...
Click to collapse
Yes, bootloader is unlocked. FYI, I can't do Vol+ Power or 3-button force. I have no idea what went wrong after the B331 update.app flash. It said successful then boot loop after. I have looked all over the forums and tried everything from flashing C900B300 rollback to try and get 4.4.2 that I started out with, but I really don't know which firmware to start with. The last update.app files I was using was the European variants. Phone was originally locked to Ecuador MoviStar network at B120SP04, then I flashed up to B324 5.1.1. Rooted and then wanted to upgrade to B331 so I unrooted and flashed. Now I'm stuck.

jfer671 said:
Yes, bootloader is unlocked. FYI, I can't do Vol+ Power or 3-button force. I have no idea what went wrong after the B331 update.app flash. It said successful then boot loop after. I have looked all over the forums and tried everything from flashing C900B300 rollback to try and get 4.4.2 that I started out with, but I really don't know which firmware to start with. The last update.app files I was using was the European variants. Phone was originally locked to Ecuador MoviStar network at B120SP04, then I flashed up to B324 5.1.1. Rooted and then wanted to upgrade to B331 so I unrooted and flashed. Now I'm stuck.
Click to expand...
Click to collapse
now you should flash twrp recovery in fastboot mode and then flash a custom rom like kangvip I'll send you link soon...

fazi2015 said:
now you should flash twrp recovery in fastboot mode and then flash a custom rom like kangvip I'll send you link soon...
Click to expand...
Click to collapse
Thank you very much....hope that will solve the boot issue and bring this unit back to life

Alright, so I've given up complete hope that I can get my unit back up and running again. I've tried so many ways already with no success (fastboot/adb, force upgrade, etc.,), and even tried to copy my second HAM7 images (via sdk tools) and to no avail.
The thing I'm trying to understand is where exactly do I start with trying to revive? When I first got this device from eBay, it was apparently still on "MoviStar" Telefonica-Spain network so my network bars showed "R" for roaming. Somehow, I was able to flash it from being on V100R001C00B120SP04a and upgrade to B127>B145>B324 which made me able to use my own service normally. It worked fine and I was even able to root it. Decided to do a last upgrade to B331 and while the local update option showed it as successfully installed, it went into boot loop ever since. Hence, I used European firmwares for most of the flashing. My second mate was on B145 and I was able to get that to B331, which is running fine right now.
ATM, I am ONLY able to do Volume-/Power to get into fastboot.
Doesn't work:
- V+/Power (stock recovery)
- V-+/Power (3-button force)
What works:
- V-/Power with USB for fastboot
*Bootloader is unlocked, but I do believe that after flashing the last firmware of B331, I may have done a factory wipe, which probably reset the USB debugging option as well. So, I'm sure I'm stuck with a device that just might be flashed on the wrong firmware and is factory reset which prevents me from flashing a custom rom or even the stock rom???
Any last advice I would be so thankful for...still waiting on the link for KangVip rom from (fazi2015)
All the best...

jfer671 said:
Alright, so I've given up complete hope that I can get my unit back up and running again. I've tried so many ways already with no success (fastboot/adb, force upgrade, etc.,), and even tried to copy my second HAM7 images (via sdk tools) and to no avail.
The thing I'm trying to understand is where exactly do I start with trying to revive? When I first got this device from eBay, it was apparently still on "MoviStar" Telefonica-Spain network so my network bars showed "R" for roaming. Somehow, I was able to flash it from being on V100R001C00B120SP04a and upgrade to B127>B145>B324 which made me able to use my own service normally. It worked fine and I was even able to root it. Decided to do a last upgrade to B331 and while the local update option showed it as successfully installed, it went into boot loop ever since. Hence, I used European firmwares for most of the flashing. My second mate was on B145 and I was able to get that to B331, which is running fine right now.
ATM, I am ONLY able to do Volume-/Power to get into fastboot.
Doesn't work:
- V+/Power (stock recovery)
- V-+/Power (3-button force)
What works:
- V-/Power with USB for fastboot
*Bootloader is unlocked, but I do believe that after flashing the last firmware of B331, I may have done a factory wipe, which probably reset the USB debugging option as well. So, I'm sure I'm stuck with a device that just might be flashed on the wrong firmware and is factory reset which prevents me from flashing a custom rom or even the stock rom???
Any last advice I would be so thankful for...still waiting on the link for KangVip rom from (fazi2015)
All the best...
Click to expand...
Click to collapse
https://mega.co.nz/#!3N4RzbJY!saB4NY...Ao5goVNiSXAjEc
I am not 100% sure about this rom but you can try it in fastboot you should flash twrp recovery first..

fazi2015 said:
https://mega.co.nz/#!3N4RzbJY!saB4NY...Ao5goVNiSXAjEc
I am not 100% sure about this rom but you can try it in fastboot you should flash twrp recovery first..
Click to expand...
Click to collapse
Unfortunately, it says the file is no longer available

jfer671 said:
Unfortunately, it says the file is no longer available
Click to expand...
Click to collapse
try this all information is here
https://forum.xda-developers.com/mate-7/orig-development/rom-kangvip-rom-mate7-emui3-1-b351-t3228597

fazi2015 said:
try this all information is here
https://forum.xda-developers.com/mate-7/orig-development/rom-kangvip-rom-mate7-emui3-1-b351-t3228597
Click to expand...
Click to collapse
Okay, so final result is I'm stuck on a frozen logo now. The twrp bat file again showed success in flashing and rebooted the device, but I'm hung on the "Huawei Ascend" logo. I have to pull the battery to shut it off, otherwise it stays on. So I'm now sure that it's a hard bricked device since I did the stupid thing of factory resetting which probably reset the usb debug...making it almost impossible to flash any firmware now.
Thanks for the help anyways...I really appreciate it. Gonna throw this up on eBay and see if anyone wants it for parts

jfer671 said:
Okay, so final result is I'm stuck on a frozen logo now. The twrp bat file again showed success in flashing and rebooted the device, but I'm hung on the "Huawei Ascend" logo. I have to pull the battery to shut it off, otherwise it stays on. So I'm now sure that it's a hard bricked device since I did the stupid thing of factory resetting which probably reset the usb debug...making it almost impossible to flash any firmware now.
Thanks for the help anyways...I really appreciate it. Gonna throw this up on eBay and see if anyone wants it for parts
Click to expand...
Click to collapse
I know it's annoying but last time I research more and guide you I was have same problem don't give up....

I send you recovery flash in fastboot no need of usb debugging usb debugging need for adb not for fastboot in fastboot flash recovery by your self download it
https://mega.co.nz/#!GRw0CZjQ!iZllDkA6yJeWk7iEA4vEVA94r2nM_YjAuiS8B9IZdm0
then extract the zip go to resource and hold shift and left click then select open command port here then power off device completely boot into fastboot (bootloader) connect the device to pc and in command port type
fastboot flash recovery twrp_2_7.img
after that type
fastboot reboot and hold the volume- button of device it'll boot into recovery if you success then reply..

I've noticed two things when flashing KK or LP. On KK, the phone does a constant boot loop with Huawei logo (on off on off), but on LP the Huawei logo hangs...it doesn't boot loop. Is this an indication or just a fault with both OS?

After Odin and Stock Rom stuck on Blue Screen with Erasing.

Hello guys,
after days of reading and trying i decided to open a thread.
I got my Samsung stuck on Erasing Screen after an update.
I tried to Flash Stock Rom via ODIN. The Flash passed but after Booting the device stuck on the Bluescreen with "Erasing" on the bottom.
I tried Flashing with Pit, and without. With Nand erase and without. With Re-partition and without.
I can not access recovery with VOL UP + Home + Power.
Device is not rooted.
I am very thankful for any advice.
Thanks in advance.

What model does your phone say in download mode, and what firmware did you flash?

Beanvee7 said:
What model does your phone say in download mode, and what firmware did you flash?
Click to expand...
Click to collapse
Sorry,
it is a G930F
I downloaded the File from SamFirm (G930FXXU2ERE8_CL13438344_QB18102270_REV00) and used Odin3 v3.13.1.

any solutions?
I have exactly the same Problem.
Did you find a possibility to fix that ?
I´m going crazy with that my device is unrootet and on stock Rom when it came into bootloop , i tried to fix it with Odin a couple of times used the latest Firmware from Samfirm but it doesnt work and gets stuck on erasing Screen and keeps on restarting . I can always get into download mode but i cant open the recovery . Another thingis that my System Status in the download mode says custom ?? i never flashed a custom Rom on it Does anyone know if i can bring it back to Samsung like that because i still have a guarantee
i would be so thankful for your help guys
cheers

Had a similar issue before with an S6, and one of the workarounds that works for a lot of samsung issues is to flash the phone through ODIN with a repair firmware and a pit file. If im remembering right the firmware files are AP, CP, BL and CSC, also the pit file. you gotta check repartition in odin too.

any idea how to fix this ? In the same boat, can't figure out how to solve this.

same thing happened to me, i can't get it to work

spittfire said:
Hello guys,
after days of reading and trying i decided to open a thread.
I got my Samsung stuck on Erasing Screen after an update.
I tried to Flash Stock Rom via ODIN. The Flash passed but after Booting the device stuck on the Bluescreen with "Erasing" on the bottom.
I tried Flashing with Pit, and without. With Nand erase and without. With Re-partition and without.
I can not access recovery with VOL UP + Home + Power.
Device is not rooted.
I am very thankful for any advice.
Thanks in advance.
Click to expand...
Click to collapse
hi have you solved then? I've got the same problem

can´t believe there is no solutions for this
i have the same problem with a galaxy A20 SM-A205G
i flahshed diferrent ROMs from diferent countries, with PIT FILE and without it and nothing works
maybe the difference with other posters here is that i can access to recovery mode but i dont find anything about fix this phone from recovery mode or something like that.

Samsung Galaxy S7 SM-G930F boot loop and won't enter recovery mode

My samsung SM-G930F is stuck in a boot loop, and recovery mode won't start., only download mode
i did a flash firmware for XEU carrier (phone bought in UK) and the flash process PASSED, it still goes into boot loop and has the same problem as previously.
Does anybody met this problem before? some suggestions please?
note: Odin v3.13 and Firmware Oreo 8.0 XEU

amig0s said:
My samsung SM-G930F is stuck in a boot loop, and recovery mode won't start., only download mode
i did a flash firmware for XEU carrier (phone bought in UK) and the flash process PASSED, it still goes into boot loop and has the same problem as previously.
Does anybody met this problem before? some suggestions please?
note: Odin v3.13 and Firmware Oreo 8.0 XEU
Click to expand...
Click to collapse
Flash it again with BTU not XEU.

cooltt said:
Flash it again with BTU not XEU.
Click to expand...
Click to collapse
that didn't work either, any others suggestions?

amig0s said:
that didn't work either, any others suggestions?
Click to expand...
Click to collapse
Yeah this happens sometimes, either go through the flash again with a different version of Odin or force reboot into recovery by pressing volume up+home+power while in download mode or as soon as it turns off to reboot.
If you get into recovery wipe/factory reset then reboot.

cooltt said:
Yeah this happens sometimes, either go through the flash again with a different version of Odin or force reboot into recovery by pressing volume up+home+power while in download mode or as soon as it turns off to reboot.
If you get into recovery wipe/factory reset then reboot.
Click to expand...
Click to collapse
I tried to flash with different versions of odin, it gets stuck at NAND partition (smth like that), and runs till the end only with v3.13.1
Problem still exists, and there seems to be no way to get in recovery mode in order to do the factory reset

amig0s said:
I tried to flash with different versions of odin, it gets stuck at NAND partition (smth like that), and runs till the end only with v3.13.1
Problem still exists, and there seems to be no way to get in recovery mode in order to do the factory reset
Click to expand...
Click to collapse
Listen we get this all the time on this board, it is always the user not doing something correctly.
You bought the phone in the UK, what firmware was already on it?
Are you sure it is a genuine G930F?
What is the exact version of the firmware you are trying to install?
Where are you getting it from?
Did you enable "debugging" before flash?
If you flash with Odin and you get a "PASS" the recovery menu is definitely there.

cooltt said:
Listen we get this all the time on this board, it is always the user not doing something correctly.
You bought the phone in the UK, what firmware was already on it?
Are you sure it is a genuine G930F?
What is the exact version of the firmware you are trying to install?
Where are you getting it from?
Did you enable "debugging" before flash?
If you flash with Odin and you get a "PASS" the recovery menu is definitely there.
Click to expand...
Click to collapse
When i bought it there was Android 6.0..
yes, i'm sure, taken directly from the store.
I'm trying to install "SM-G930F BTU UNITED KINGDOM G930FXXU5ESD2 FIRMWARE" downloaded from sammobile.com
No i didn't enable debugging because my phone suddenly crashed and there is no way to boot itup

amig0s said:
When i bought it there was Android 6.0..
yes, i'm sure, taken directly from the store.
I'm trying to install "SM-G930F BTU UNITED KINGDOM G930FXXU5ESD2 FIRMWARE" downloaded from sammobile.com
No i didn't enable debugging because my phone suddenly crashed and there is no way to boot itup
Click to expand...
Click to collapse
Ok well it may be a hardware problem rather than software if the phone crashed.
Try one more thing first.
Flash Nougat from Sammobile not Oreo and see if it boots, sometimes this has to happen first.
**Also have you tried Samsung Smart Switch Emergency software recovery?**

cooltt said:
Ok well it may be a hardware problem rather than software if the phone crashed.
Try one more thing first.
Flash Nougat from Sammobile not Oreo and see if it boots, sometimes this has to happen first.
**Also have you tried Samsung Smart Switch Emergency software recovery?**
Click to expand...
Click to collapse
Samsung Smart Switch doesn't recognize this device, i guess it a hardware problem in the end.
I tried all the solutions mentioned above.
Anyway thank you very much, i will go to a service center.
Peace <3

NO expert, but had similar problem.
While in boot loop, volume down+home+power
when rebooting quickly switch to volume up+home+power
boots into recovery
select mount system, press power button.
worked for me
Although prior to the fix for me, I wiped cache and factory reset while in recovery. Not sure if it was needed.