S7 Edge Hero2lte Exynos SM-G35F bricked device - Samsung Galaxy S7 Edge Questions and Answers

Hi Guys,
Today I think I bricked my phone and I would appreciate any help.
I will describe the whole situation.
So around 2019 May, I rooted my device and decided to flash a stock based,debloated custom rom. Everything work just fined including downloading mode and recovery menu. Today, I decided to try out [S7/S7 Edge][OneUI Pie][JetBlackUI] LightROM, however strangely I was not able to boot either to TWRP neither to downloading mode via key combination.
However I had install TWRP app and from there i was able to boot to recovery mode,install the new rom and try it out.
For some reason root was not enabled in the new rom, so i figured I will try to do it via TWRP however I was unable to boot, since root access is needed to boot from TWRP app + key combo still did not work.
After searching on google, I found a poprgram which can do the trick. (Recovey-Download (CMD)
With this I was able to boot to recovery mode. Now I thought, since all this mess up was started with the new roms, I decided to restore my original stock rom, which I had a back up of. It booted up first and seemed okay, but I was curious if this solved the issues with the key comb, so I tried it going downloading mode, but it only worked with the program ((Recovey-Download (CMD)), and I saw that it is probably not gonna be good, since it only had the blue screen, but no data in the upper left corner.
Then I restarted the device and now it say " Custom binary blocked by FRP lock". and turns off itself.
I saw that FRP lock could be solved easly with Odin fresh install, problem is I have no idea how to go downloading mode. ( Assuming at this point I still can).
Sorry for the long essay but i think the more detail the easier to diagnose. Also, thank you for reading.
I would greatly appreciate any help.
BR
Csaba

Managed to solve it with USB JIG.

Is your phone an Exynos/Snapdragon variant?
csesztes said:
Managed to solve it with USB JIG.
Click to expand...
Click to collapse
Hey, how did you manage to get your phone into dl mode with an USB jig? I want to try this out, but you're the only one here who's confirmed that you were able to do this on an S7 Edge.

Related

asus tf300t bricked

kinda of a new at this. basically my tablet boots with asus logo and top left says "the device is UnLocked"
tried to flash cyanogen mod and put some wrong files.
i know its bricked but cant do much. Vol- + Pwr doesnt get me anywher
Vol+ + Pwr makes some recognition on my computer but cant do much. like fastboot wont recognize as a device.
pls help\
UPDATE: Got it to go in APX mode. and got drivers installed. dont know whats next...
thanks in advance
Few questions first... (I am an Android n00b, but have had issues and flashed custom ROMs about 9 times now.)
Did you make sure to see if the device was properly detected in your OS of choice beforehand? Installed all the software to do so?
Did you install either CWM or TWRP to the device?
Make a recovery in case of issue?
I followed the topic (in this very forum) about flashing. I had some issues being new and all, but got it right... BEFORE I did an actual flash.
[GUIDE] TF300T Unlock/Root/Flash for Factory JB Devices (newbie friendly)
I am using the latest TWRP instead of the guides CWM advice. Due to CWM failing to create a backup for me. I felt not having a backup plan, was something similar to going to a redlight district without a rubber. Which means... What if something goes wrong, how will I fix it?
Does the device detect? Can you move files to the device from your computer?
techknewz1 said:
kinda of a new at this. basically my tablet boots with asus logo and top left says "the device is UnLocked"
tried to flash cyanogen mod and put some wrong files.
i know its bricked but cant do much. Vol- + Pwr doesnt get me anywher
Vol+ + Pwr makes some recognition on my computer but cant do much. like fastboot wont recognize as a device.
pls help\
UPDATE: Got it to go in APX mode. and got drivers installed. dont know whats next...
thanks in advance
Click to expand...
Click to collapse
Hey there, just curious as to how you managed to 'put some wrong files', what exactly did you do to achieve this?
If you can still get into recovery and you have fastboot hooked up, you can proceed to either:
re-flash the correct CWM version if your recovery is broken, or
upload the CyanogenMod package you want to install to your device and simply wipe & flash!
I don't recommend installing last week's nightlies, rotation is still broken. Not sure as to what version last worked.
Good luck!
Xynergy said:
Hey there, just curious as to how you managed to 'put some wrong files', what exactly did you do to achieve this?
If you can still get into recovery and you have fastboot hooked up, you can proceed to either:
re-flash the correct CWM version if your recovery is broken, or
upload the CyanogenMod package you want to install to your device and simply wipe & flash!
I don't recommend installing last week's nightlies, rotation is still broken. Not sure as to what version last worked.
Good luck!
Click to expand...
Click to collapse
So here is what happened. Basically i tried flashing files and put it for the wrong tablet. Now i can only get into apx mode and fastboot doesnt recognize it and neither does adb recognize it.

Zte axon 7 mini edl backup needed - lost stock recovery!

Hi Guys,
I would greatly appreciate any help. I have somehow lost the TWRP & Stock recovery to my ZTE ANXON 7 MINI.
I had a custom rom and decided to flash a stock update zip and that rendered my phone unusable. I have managed to get it too boot to 6.0.1 B9 Spanish rom. However i have NO RECOVERY to flash the original update for the UK B12 Rom.
Im using the EDL Tool to flash. If anyone has the stock recovery to the B9 6.0.1 Rom that would be a big help. Or a EDL full backup.
All links to the ZTE website are down as they are no longer allowed to use ANDROID.
Also to note i have tried to reinstall TWRP however im left with either a white screen or nothing just bootloop.
Unable to unlock bootloader also as i have no fastboot option as recovery is dead
Thanks.
This are (full flash)EDL roms(need to extract to folder "flash\full ",and flash(not recovery ))B12.6Android.EDL.EU.Version
B13.Android7.EDL.EU.Version
A18xcn said:
Hi Guys,
I would greatly appreciate any help. I have somehow lost the TWRP & Stock recovery to my ZTE ANXON 7 MINI.
I had a custom rom and decided to flash a stock update zip and that rendered my phone unusable. I have managed to get it too boot to 6.0.1 B9 Spanish rom. However i have NO RECOVERY to flash the original update for the UK B12 Rom.
Im using the EDL Tool to flash. If anyone has the stock recovery to the B9 6.0.1 Rom that would be a big help. Or a EDL full backup.
All links to the ZTE website are down as they are no longer allowed to use ANDROID.
Also to note i have tried to reinstall TWRP however im left with either a white screen or nothing just bootloop.
Unable to unlock bootloader also as i have no fastboot option as recovery is dead
Thanks.
Click to expand...
Click to collapse
If you have white screen or ZTE logo then I know how to solve it.
Funny enough, hook the phone to the pc, open adb command and type adb devices.
You will see you pc recognises the phone in adb as recovery.
If this happens let me know and I'll show you how to push the entire bootstack to data/media, then write all these files to each partition. After that your twrp will work and you are done.
These happened to me about 10 times now and I even created a bat file which I double click and it does all the operations at once then reboots straight into twrp. Quite cool actually.
Nevertheless I'm also interested in an edl ROM to umbrick another axon 7 mini I have which is totally, utterly bricked.
I have opened the phone (still opened) and I managed once to get the test point to work and connect to qcn configurator but since then I never got it to be recognised again.
Good luck
Cheers
bius88 said:
This are (full flash)EDL roms(need to extract to folder "flash\full ",and flash(not recovery ))B12.6Android.EDL.EU.Version
B13.Android7.EDL.EU.Version
Click to expand...
Click to collapse
Mate, you don't know how helpful this post was.
I have bricked this [nasty] phone about 10 times.
but yesterday I learn yet another lesson, after trying to flash a new splash screen, the phone went totally dead, connecting directly in DFU mode.
I sort of panicked because I didn't have a fresh data backup and there aren't full EDL ROM for this phone easily found on the web.
After focusing in making sure my laptop had the correct drivers (loader/bulk/adb) and after I got confident to use the deepflash cable to move from DFU to EDL, bulk device recognised, right click on it and update the driver to show the loader (901D) then I though what would be the next step.
I did not understand the MIflash tool and the version I had didn't seem to work at all I scratched my had for a while.
I then used the EDL tool, placed your files into the FULL folder and ran through the steps...….mate.....that was beautiful.
I ended up flashing the full B13 on top of the B09 and the system works perfect without any loss of data.
Having learnt all this, I went brave and confident I could rescue my other axon 7 min, which had been dead for over 2 months. Although I had to open it to access the test point, after about 50 or more attempts, I had tried lots of combinations, test point again etc.
It turned out I have left the phone plugged in to the PC with every plug disconnected except the usb board and went to do the washing up. 2-3min later my pc gave a sound, loader 901D was already ready and I repeated the exact process.
You basically saved both of my phones!!!! THANK YOU

Stuck in rescue mode after tried flashing stock firmware

Good evening! I hope you can help me.
I flashed LineageOS 14.1, but I wanted to go back to EMUI. I made all the wipes and tried to flash different stock firmwares through a forced update (volume buttons + power button), but it never worked. At that point, I read about a guy in this forum who suggested to create a flashable zip with Huawei Update Extractor: I followed the suggestion and tried to flash it with TWRP. No error was given, but when I tried to restart, TWRP told me I had no OS installed. I thought it was strange, so I tried to restart anyway. That's when I got in rescue mode. I can't get into the recovery and I can't use fastboot. What rescue mode shows me is:
RESCUE MODE
Attention!
Please update system again
Update User Guide:
*link*
*android avatar*
Error!
Func NO: 10 (boot image)
Error NO: 2 (load failed!)
Pressing the three buttons, I'm able to force an update. The problem is I can't find a firmware that doesn't get rejected. With Lollipop firmwares, it starts to install, but it fails at 12%. With Marshmallow ones, the installation process doesn't even start.
What can I do to make it work again? I'm very sad because this phone was gifted to me a couple of days ago and I already messed it up. I don't even know how to turn it off.
What can I do to get in fastboot mode? At that point, what should I do to flash the stock firmware? Or maybe do I need to find the first stock firmware ever installed into this phone to make the forced update work?
Please, I need help. Thank you in advance!
P.S. The phone's model is ALE-L21. I live in Italy, so I assume it's a European version.
Did you managed to fix this?
Jhon_Locke said:
Did you managed to fix this?
Click to expand...
Click to collapse
Not yet, but I'm working on it. I found out that the device is recognized by my PC if I follow these steps:
1. Connect the phone to the PC and wait for it to go in rescue mode;
2. Wait until the notification LED stops to blink;
3. Disconnect the USB cable;
4. Press volume - and power button;
5. Reconnect the cable.
At that point, the screen turns black and the phone is recognized as "㄰㌲㔴㜶㤸". I installed the drivers and now it's recognized as "HUAWEI USB COM 1.0". I should be able to reflash the partitions and make my phone work again, but I'm still trying to understand how to do it correctly.
Any help is appreciated!
ErikChimello said:
Not yet, but I'm working on it. I found out that the device is recognized by my PC if I follow these steps:
1. Connect the phone to the PC and wait for it to go in rescue mode;
2. Wait until the notification LED stops to blink;
3. Disconnect the USB cable;
4. Press volume - and power button;
5. Reconnect the cable.
At that point, the screen turns black and the phone is recognized as "㄰㌲㔴㜶㤸". I installed the drivers and now it's recognized as "HUAWEI USB COM 1.0". I should be able to reflash the partitions and make my phone work again, but I'm still trying to understand how to do it correctly.
Any help is appreciated!
Click to expand...
Click to collapse
fastboot detects your device when you plug it into your computer?
I mean, if you run "fastboot devices" it shows your phone?
I've had this same problem but with an P8 Lite 2017, after flashing some ROM that supposedly was the stock one and trying to flash recovery I ended up with my phone bootlooping into rescue mode, I was able to "bypass" this thing rebooting my phone like crazy, seriously like after 20 reboot it finally booted into the damn ROM and I never touched the phone again. Sometimes when the phone ran out of battery and tried to power it on the phone booted into rescue mode and again after some reboots it booted to Android but now I want to install a custom ROM or at the very least root this damn phone so that's why I'm asking you if you have solved this, if you do then probably if I follow the same steps I would be able to fix that screen, hopefully.
If you are able to flash something start with flashing all recoveries your update.app has, maybe that's the problem (at least in my phone it is).
Jhon_Locke said:
fastboot detects your device when you plug it into your computer?
I mean, if you run "fastboot devices" it shows your phone?
I've had this same problem but with an P8 Lite 2017, after flashing some ROM that supposedly was the stock one and trying to flash recovery I ended up with my phone bootlooping into rescue mode, I was able to "bypass" this thing rebooting my phone like crazy, seriously like after 20 reboot it finally booted into the damn ROM and I never touched the phone again. Sometimes when the phone ran out of battery and tried to power it on the phone booted into rescue mode and again after some reboots it booted to Android but now I want to install a custom ROM or at the very least root this damn phone so that's why I'm asking you if you have solved this, if you do then probably if I follow the same steps I would be able to fix that screen, hopefully.
If you are able to flash something start with flashing all recoveries your update.app has, maybe that's the problem (at least in my phone it is).
Click to expand...
Click to collapse
No, it doesn't show anything if I write that command...
I guess mine won't ever boot into the rom because it seems like there's no system installed. I made some researches and found out there are some softwares that let you reflash the partitions IF the phone is recognized as "HUAWEI USB COM 1.0". I'm still trying to figure out how to do it correctly though. I feel like if I do something wrong, then my phone won't probably turn on again.
In your case, you should be able to flash a custom rom without any issue. You just have to be very careful and inform you as much as you can: I don't want your phone to end up like mine?. Anyway, it seems pretty hard to go back to the stock rom, so think about it before you flash a custom rom. Also, make a Nandroid Backup is very important.

Un-debrickable state ?

Hello guys,
I'm fairly certain I'm stuck in an un-debrickable state but I'll ask just in case. My phone is F800K.
I was toying around with LGUP in order to downgrade and root my phone. So far, so good.
I then tried to update to the latest android 9 again, but keep the root active. That's where things started to go south, so I decided to go back.
I followed a couple of "back to stock" guides but now I'm screwed.
- The phone does not boot.
- Download mode is broken, the phone doesn't connect to my computer while in download mode, so it's unusable.
- TWRP is gone. When I try to boot to recovery after yes both times I get nothing. Not the stock recovery and not TWRP, it just tries to boot as usual.
- Can't seem to go back into fastboot either. I tried VOLDOWN + plug-in the phone about 200 times now, to no avail.
Is there another way that I'm missing ?
Thanks.
growiel said:
Hello guys,
I'm fairly certain I'm stuck in an un-debrickable state but I'll ask just in case. My phone is F800K.
I was toying around with LGUP in order to downgrade and root my phone. So far, so good.
I then tried to update to the latest android 9 again, but keep the root active. That's where things started to go south, so I decided to go back.
I followed a couple of "back to stock" guides but now I'm screwed.
- The phone does not boot.
- Download mode is broken, the phone doesn't connect to my computer while in download mode, so it's unusable.
- TWRP is gone. When I try to boot to recovery after yes both times I get nothing. Not the stock recovery and not TWRP, it just tries to boot as usual.
- Can't seem to go back into fastboot either. I tried VOLDOWN + plug-in the phone about 200 times now, to no avail.
Is there another way that I'm missing ?
Thanks.
Click to expand...
Click to collapse
It does sound like a hard brick... you said fastboot is hosed, do you have access to adb in any way?
Sent from my moto g(6) play using Tapatalk
None that I know of, that's the issue. If I had access to either fastboot, adb or download mode, I could most likely salvage this, but I can't seem to be able to.
The weirdest thing is the broken download mode, I couldn't find anybody with the same issue...
growiel said:
None that I know of, that's the issue. If I had access to either fastboot, adb or download mode, I could most likely salvage this, but I can't seem to be able to.
The weirdest thing is the broken download mode, I couldn't find anybody with the same issue...
Click to expand...
Click to collapse
On my lg tribute HD (ls676) fastboot was removed by lg themselves on Android 6.0.1 quietly with a security update and download mode never worked right for me. Without access to fastboot, adb or even diag mode it really sounds like you have a hard brick. if i can find a solution of some kind, I'll definitely let you know.
Sent from my moto g(6) play using Tapatalk
What would "diag mode" be and how can I check if I can access it ?
Small update for people who stumble upon this thread, I managed to save my phone by using the Qualcomm Test Point, see here: https://forum.xda-developers.com/showpost.php?p=81697447&postcount=128

Phone acting strange - Bricked?

Hi
My phone stopped working a couple of days ago, I had been running a custom rom for 2 mths. I tried to restart and boot to recovery TWRP as I was going to reflash the rom. It charegs with no lights, for a day I couldnt boot to TWRP if it did it stayed on the start screen with no options. Today I can get options in TWRP so I tried to start fresh install but intstallation stops at step 1 ?
I have no idea what happened to the phone or why it just died, but dont understand why I can get into TWRP but cant flash rom etc. Also sometimes it say system destroyed message? but still can get into TWRP ?
Any ideas or help will much appreciated really would like to fix this rather than write the phone off.
Thanks
i think flashing firmware is the only option
ranjodhricky said:
i think flashing firmware is the only option
Click to expand...
Click to collapse
Hi, yeah I think thats what I try, is this flashing stock rom via MI flash or a different process?
try miflash if doesn't work try QFil
update
ranjodhricky said:
try miflash if doesn't work try QFil
Click to expand...
Click to collapse
Hi, been playing with this when i have time over the last few weeks.
I have been trying to flash firmware, I dont seem to be able to get QFIL to work for me, it wont reconsise the port. However MIFlash does but I get errors, sometimes it flashes but doesnt end? other times i have had error flashing modem_a or error flashing modem_b (maybe device is locked).
In ADB it says already unlocked. Also I can only boot into fastboot, not recovery so i cant intall anything from adb sideload, it wont boot into bootloader just powers off if i try this. I guess theres no recovery on it now as I cannot boot into it.
Any ideas on where to go from here , EDL? I really didnt want to attempt to open the phone.
Thanks
Try miflash 2019 with stock rom pie latest with edl mode
if bootloader unlocked You can enter edl mode via fastboot with the command 'fastboot oem edl'
Yincen said:
Try miflash 2019 with stock rom pie latest with edl mode
if bootloader unlocked You can enter edl mode via fastboot with the command 'fastboot oem edl'
Click to expand...
Click to collapse
Thanks, tried this, says success then just carries on , so i have to disconnect. However when then trying to boot the device it shows Android one logo and if im lucky after a few attempts it goes to the screeen saying Hi There, where you choose your language to set up the phone. However it nows seem to be unresponsve and frozen on that screen.
Im beginning to think its could be hardware issue and phone is just faulty, i really dont want to bin it as its imacculate condition seems a real shame, but it is 3 years old i guess.
Any further help or ideas much appreciated.
healy2k said:
Thanks, tried this, says success then just carries on , so i have to disconnect. However when then trying to boot the device it shows Android one logo and if im lucky after a few attempts it goes to the screeen saying Hi There, where you choose your language to set up the phone. However it nows seem to be unresponsve and frozen on that screen.
Im beginning to think its could be hardware issue and phone is just faulty, i really dont want to bin it as its imacculate condition seems a real shame, but it is 3 years old i guess.
Any further help or ideas much appreciated.
Click to expand...
Click to collapse
try doing a factory reset from Recovery , good luck

Categories

Resources