Database Users

How to WIPE without CWM / NO recovery / only download

Hey guys.
I have been doing a lot of researches before creating this new thread.
Here is my problem with a Samsung Galaxy s3 I9300T (Australia - Vodafone build). I was given the phone, since it was stuck in a boot loop after a software update issue with Kies (I think from memory 4.2 or something).
The phone boots up, displays the Vodafone logo, and is stuck on the Samsung logo. The phone doesn't restart but stays idle there.
It is impossible to reach the download mode with the use of the 3 buttons, but a USB JIB I bought on ebay does the trick.
Odin recognizes the phone, I can flash a stock Kernel from Samsmobile or root/install the CWM.
BUT, there is no way (so far?) to reach the recovery mode.
I tried to flash a new boot loader, tried to check any physical issue with the buttons, but nothing seems wrong.
I have been looking for tools such a android toolbox/toolkit etc, in the hope one would be able to wipe/flash the nand or even unbrick or whatsoever, from a download mode and not ADB, since I there no fast boot available.
I am ready to try anything, since there's nothing to loose here.
I'm running windows 7 from Parallel desktop.
Thanks mates.
Anthony

tonythrash69 said:
Hey guys.
I have been doing a lot of researches before creating this new thread.
Here is my problem with a Samsung Galaxy s3 I9300T (Australia - Vodafone build). I was given the phone, since it was stuck in a boot loop after a software update issue with Kies (I think from memory 4.2 or something).
The phone boots up, displays the Vodafone logo, and is stuck on the Samsung logo. The phone doesn't restart but stays idle there.
It is impossible to reach the download mode with the use of the 3 buttons, but a USB JIB I bought on ebay does the trick.
Odin recognizes the phone, I can flash a stock Kernel from Samsmobile or root/install the CWM.
BUT, there is no way (so far?) to reach the recovery mode.
I tried to flash a new boot loader, tried to check any physical issue with the buttons, but nothing seems wrong.
I have been looking for tools such a android toolbox/toolkit etc, in the hope one would be able to wipe/flash the nand or even unbrick or whatsoever, from a download mode and not ADB, since I there no fast boot available.
I am ready to try anything, since there's nothing to loose here.
I'm running windows 7 from Parallel desktop.
Thanks mates.
Anthony
Click to expand...
Click to collapse
after flashing newfirmware using download mode+odin the phone cant reboot?have you tried diff version firmware from sammobile .

nainaabd said:
after flashing newfirmware using download mode+odin the phone cant reboot?have you tried diff version firmware from sammobile .
Click to expand...
Click to collapse
I tried 2 different firmware from SAMSmobile, after flashing in Odin, nothing changes. The phone reboots (if the case is ticked) and stays stuck on the samsung logo, after the vodafone splash screen.

tonythrash69 said:
I tried 2 different firmware from SAMSmobile, after flashing in Odin, nothing changes. The phone reboots (if the case is ticked) and stays stuck on the samsung logo, after the vodafone splash screen.
Click to expand...
Click to collapse
maybe something went wrong in partition table during kies upgrade, do you tried a full system reinstall comprensive of pit image?
myabe this get phone back to life but i think you will lose efs.

Well normaly after flashing your right Firmware you should be able to acces recovery...

franco853 said:
maybe something went wrong in partition table during kies upgrade, do you tried a full system reinstall comprensive of pit image?
myabe this get phone back to life but i think you will lose efs.
Click to expand...
Click to collapse
How can I perform what you call a "full system reinstall comprehensive of PIT image"?
I have stock firmware, but no PIT file or CSC or whatsoever.
what do you mean by losing EFS? (encryption ??)
Any help is much appreciated.

tonythrash69 said:
How can I perform what you call a "full system reinstall comprehensive of PIT image"?
I have stock firmware, but no PIT file or CSC or whatsoever.
what do you mean by losing EFS? (encryption ??)
Any help is much appreciated.
Click to expand...
Click to collapse
efs is a system partition wich contains your phone's hardware serial numbers, such as imei, wi-fi mac ecc... losing this means you can't connect to phone network until you restore it(i'm not sure you lose it)
i found this guide here on the forum to restore from brick's or similiar, i think you can try this if normal flashing don't work:
http://forum.xda-developers.com/galaxy-s3/help/solved-pit-bricked-dead-problem-gt-t2535367

When you flash full firmware from Samsung (.tar.md5), it includes things such as bootloader, tz, modem, system, cache, preload and the recovery. Just make sure to download it from site such as sammobile, and you can check yourself if your .tar.md5 you're about to flash includes these things using i.e. 7zip.
Untick "auto reboot" option and flash it. After it's done, it won't auto reboot but Odin will change text to "RESET!", this is a signal for you that it's finished.
Hold on Vol-Up+Home+Power for about 7 seconds, until you see Samsung Galaxy S3 logo. It MUST enter stock recovery you've just flashed, unless your hardware is broken. From there you can select Wipe data / factory reset.
Good luck.

JustArchi said:
When you flash full firmware from Samsung (.tar.md5), it includes things such as bootloader, tz, modem, system, cache, preload and the recovery. Just make sure to download it from site such as sammobile, and you can check yourself if your .tar.md5 you're about to flash includes these things using i.e. 7zip.
Untick "auto reboot" option and flash it. After it's done, it won't auto reboot but Odin will change text to "RESET!", this is a signal for you that it's finished.
Hold on Vol-Up+Home+Power for about 7 seconds, until you see Samsung Galaxy S3 logo. It MUST enter stock recovery you've just flashed, unless your hardware is broken. From there you can select Wipe data / factory reset.
Good luck.
Click to expand...
Click to collapse
Yes this is what I did.
But after "RESET" doing it, holding the buttons won't let me reach the recovery.
Is there a way to access it ? like for instance a USB JIG allowed me to access the DOWNLOAD mode; whereas holding the buttons never let me.

tonythrash69 said:
Yes this is what I did.
But after "RESET" doing it, holding the buttons won't let me reach the recovery.
Is there a way to access it ? like for instance a USB JIG allowed me to access the DOWNLOAD mode; whereas holding the buttons never let me.
Click to expand...
Click to collapse
I don't think so. Probably your buttons are broken then.

JustArchi said:
I don't think so. Probably your buttons are broken then.
Click to expand...
Click to collapse
I still do not understand that NO software is able to address the phone, like the recovery mode does.
We can flash from a computer, how come not to wipe from a computer.
assuming that someone has no screen or broken buttons, i'm sure there's a way to access wipe and/or access the recovery to flash a stock rom.
Thanks

tonythrash69 said:
I still do not understand that NO software is able to address the phone, like the recovery mode does.
We can flash from a computer, how come not to wipe from a computer.
assuming that someone has no screen or broken buttons, i'm sure there's a way to access wipe and/or access the recovery to flash a stock rom.
Thanks
Click to expand...
Click to collapse
do you tried the guide i linked some post ago? the one with the repartition file?

franco853 said:
do you tried the guide i linked some post ago? the one with the repartition file?
Click to expand...
Click to collapse
Hey, yes I tried the link, but again I cannot access the recovery to flash the .zip file.
When I hold the buttons as soon as the logo "galaxy s III GTI9300" appears, the screen goes black and the logo comes back again.
If I release one button, the vodafone splash screen appears, and the boot is stuck on the samsung logo.
I assume, the buttons are working because of what I just explained.
But again, I cannot access the recovery.
Last week, for some reason, after flashing I has a "setup wizard" from appeared, and crashed. that was the only time. I could see the lights under the touch buttons coming on. After the crash, I tried to reinstall and couldn't do it.
I am still sure there should be a way to wipe the nand completely or install from the SD card via the download mode.
Any help is welcome

tonythrash69 said:
Hey, yes I tried the link, but again I cannot access the recovery to flash the .zip file.
When I hold the buttons as soon as the logo "galaxy s III GTI9300" appears, the screen goes black and the logo comes back again.
If I release one button, the vodafone splash screen appears, and the boot is stuck on the samsung logo.
I assume, the buttons are working because of what I just explained.
But again, I cannot access the recovery.
Last week, for some reason, after flashing I has a "setup wizard" from appeared, and crashed. that was the only time. I could see the lights under the touch buttons coming on. After the crash, I tried to reinstall and couldn't do it.
I am still sure there should be a way to wipe the nand completely or install from the SD card via the download mode.
Any help is welcome
Click to expand...
Click to collapse
I get same thing(galaxy s3 logo, black screen then normal boot when try accessing recovery) some time ago after installing philz reco, i flashed another recovery and now runs well, it sounds so strange that you still cant get at least stock recovery after a repartition and a full system reinstall... Maybe something get broke in the hardware...

[HELP] SM-G7102 Recovery Mode issue

Hello all, so today I downloaded 4.4.2 KitKat firmware from sammobile site, flashed it without backup or any **** (I've done it before on my tablet and worked like A CHARM) and "finally" got KitKat on my Grand 2 Duos. Then it all started happening after that:
I first started noticing some strange and weird bugs, like I can't lock the screen, notifications never get cleared, it felt like the phone got frozen.
It is known for sure that after I installed the firmware, the recovery mod that I had is gone and replaced with stock one, so I tried flashing a .tar file for rooting my phone (It was actually to use via recovery, not via flash... I lacked information back then), after flashing it, I could boot into recovery mode no more. Even after flashing the 4.4.2 firmware again, I even saw it installing a "recovery.img" file but with no good. When I try to boot into recovery mode it writes at the top "Could not do normal boot" and then "ODIN Mode" and the rest as I used to see before.
Then I started searching the web for solutions relating to the bugs I noticed earlier, found a thread instructing to remove battery, SIM card and microSD card, then re-installing them again except the microSD card... It actually fixed the stated bugs! But I still don't feel relaxed. I want to fix this (idk if this is called "bricked" or no!) issue about recovery mode, and get back to 4.3 as this scared me as f**k.
NOTE: I flashed CWM and TWRP .tar files that I already had, to no avail.

Now does ur mobile boot ? Or is it stuck in the logo ?
Hakuna matata !

Sanjuujosephh said:
Now does ur mobile boot ? Or is it stuck in the logo ?
Hakuna matata !
Click to expand...
Click to collapse
Well I already stated (if you read my whole thread) that it works normally, running 4.4.2 atm without microSD card inserted, it works like the past except for two points:
1- My root access is gone.
2- I can't reboot into recovery mode at all, no matter what I try.

Wow u screwed up ur recovery itself ....wow u r awesome ! Just check if it goes to download mode if it does then flash it again with the latest firmware .... After flashing immediately try going to recovery and if u do ..... do the reset and wipe cache
Hakuna matata !

Sanjuujosephh said:
Wow u screwed up ur recovery itself ....wow u r awesome ! Just check if it goes to download mode if it does then flash it again with the latest firmware .... After flashing immediately try going to recovery and if u do ..... do the reset and wipe cache
Hakuna matata !
Click to expand...
Click to collapse
After I flash the firmware it automatically goes to a recovery screen, a progress bar gets filled then opens the Android system normally. After that when I try to go to recovery mode again it goes back to download mode again with the error text "Could not do normal boot".

Problem.... Fixed? .___.
Well for some reason on the third (and thought it's hopeless) attempt to flash the firmware again, I managed to open recovery mode after it, I was kissing the Reset Factory button.
As long as I find this weird, working on many attemps (maybe Samsung software itself fails?) I find this thread useless, thanks given to Sanjuujosephh! I inserted my microSD and it's working now, rebooted again into recovery and it's working as it should be.

citBabY said:
Hello all, so today I downloaded 4.4.2 KitKat firmware from sammobile site, flashed it without backup or any **** (I've done it before on my tablet and worked like A CHARM) and "finally" got KitKat on my Grand 2 Duos. Then it all started happening after that:
I first started noticing some strange and weird bugs, like I can't lock the screen, notifications never get cleared, it felt like the phone got frozen.
It is known for sure that after I installed the firmware, the recovery mod that I had is gone and replaced with stock one, so I tried flashing a .tar file for rooting my phone (It was actually to use via recovery, not via flash... I lacked information back then), after flashing it, I could boot into recovery mode no more. Even after flashing the 4.4.2 firmware again, I even saw it installing a "recovery.img" file but with no good. When I try to boot into recovery mode it writes at the top "Could not do normal boot" and then "ODIN Mode" and the rest as I used to see before.
Then I started searching the web for solutions relating to the bugs I noticed earlier, found a thread instructing to remove battery, SIM card and microSD card, then re-installing them again except the microSD card... It actually fixed the stated bugs! But I still don't feel relaxed. I want to fix this (idk if this is called "bricked" or no!) issue about recovery mode, and get back to 4.3 as this scared me as f**k.
NOTE: I flashed CWM and TWRP .tar files that I already had, to no avail.
Click to expand...
Click to collapse
Dear friend,
Try my rooting thread at http://forum.xda-developers.com/gal...ps/galaxy-s5-mod-apps-kitkat-grand-2-t2821638
This is made specifically for the KitKat Grand 2.
The message "Could not do normal boot" came as a result of using 4.3 recovery on 4.4.2.
Do not ever attempt to revert to 4.3 as this will HARD BRICK YOUR PHONE'S MOTHERBOARD.
---------- Post added at 06:49 PM ---------- Previous post was at 06:46 PM ----------
citBabY said:
Hello all, so today I downloaded 4.4.2 KitKat firmware from sammobile site, flashed it without backup or any **** (I've done it before on my tablet and worked like A CHARM) and "finally" got KitKat on my Grand 2 Duos. Then it all started happening after that:
I first started noticing some strange and weird bugs, like I can't lock the screen, notifications never get cleared, it felt like the phone got frozen.
It is known for sure that after I installed the firmware, the recovery mod that I had is gone and replaced with stock one, so I tried flashing a .tar file for rooting my phone (It was actually to use via recovery, not via flash... I lacked information back then), after flashing it, I could boot into recovery mode no more. Even after flashing the 4.4.2 firmware again, I even saw it installing a "recovery.img" file but with no good. When I try to boot into recovery mode it writes at the top "Could not do normal boot" and then "ODIN Mode" and the rest as I used to see before.
Then I started searching the web for solutions relating to the bugs I noticed earlier, found a thread instructing to remove battery, SIM card and microSD card, then re-installing them again except the microSD card... It actually fixed the stated bugs! But I still don't feel relaxed. I want to fix this (idk if this is called "bricked" or no!) issue about recovery mode, and get back to 4.3 as this scared me as f**k.
NOTE: I flashed CWM and TWRP .tar files that I already had, to no avail.
Click to expand...
Click to collapse
Dear friend,
Try my rooting thread at http://forum.xda-developers.com/gal...ps/galaxy-s5-mod-apps-kitkat-grand-2-t2821638
This is made specifically for the KitKat Grand 2.
The message "Could not do normal boot" came as a result of using 4.3 recovery on 4.4.2.
Do not ever attempt to revert to 4.3 as this will HARD BRICK YOUR PHONE'S MOTHERBOARD.
اقرأ الموضوع اللي كتبته خصوصي للجراند 2 بنظام كت كات
رسالة Could not do normal boot طلعت بسبب استخدام ريكفري قديم ع الكت كات
الموضوع الجديد فيه ريكفري جديد.

Help me plzz
hey.... wht did u do evn i m stuck there??? plzzz help..got KitKat on my Grand 2 got KitKat on my Grand 2 Duos. Then it all started happening after that:
I first started noticing some strange and weird bugs, like I can't lock the screen, notifications never get cleared, it felt like the phone got frozen.
It is known for sure that after I installed the firmware, the recovery mod that I had is gone and replaced with stock one, so I tried flashing a .tar file for rooting my phone (It was actually to use via recovery, not via flash... I lacked information back then), after flashing it, I could boot into recovery mode no more. Even after flashing the 4.4.2 firmware again, I even saw it installing a "recovery.img" file but with no good. When I try to boot into recovery mode it writes at the top "Could not do normal boot"

citBabY said:
Well I already stated (if you read my whole thread) that it works normally, running 4.4.2 atm without microSD card inserted, it works like the past except for two points:
1- My root access is gone.
2- I can't reboot into recovery mode at all, no matter what I try.
Click to expand...
Click to collapse
i think you should reset your phone
and if it doesn't work then try another country's rom
thankyou

hey bro, I have problem same to u..
Bro...I have same problem..?? I cant go to recovery mode showing Could not boot normally...etc..This happened after I tried CWM using Odin ..I always go download mood and...when i pressed factory reset button ..it didnt rest and go download mode again...plz help me bro...thanks
As long as I find this weird, working on many attemps (maybe Samsung software itself fails?) I find this thread useless, thanks given to Sanjuujosephh! I inserted my microSD and it's working now, rebooted again into recovery and it's working as it should be.[/QUOTE]

Bro, please don't use king root or any other root.
Solution
Please download the stock firmware and then go to download mode flash the stock firmware and root your phone again. Then recovery mode will work.
Thank you
Sorry for errors.
Sent from my SM-G900H using XDA-Developers mobile app

I'm a newbie but I fixed mine...
I've had this happen and it is frustrating to say the least. But I fixed it though. This is what I did: CAVEAT: Please read up all the FAQs, search the right firmware for your phone and the appropriate versions, KitKat vs Jelly Bean, etc. otherwise if your phone is bricked...don't blame me.
I have a 2nd-hand Galaxy Grand 2 and so warranty issues are a non-issue for me. All the files I've found were downloaded on this forum. I flashed ROM with my PC with Odin program installed.
I used Odin3 (v.3.07). (To install Odin program search the this forum). I also reflashed the recovery TWRP file "twrp_ms013g-build2.tar" Including the firmware G7102 Stock. My file was: G7102DDUBOB1_G7102ODDBOB1_G7102DDUBNK1_HOME.tar.md5. (Search for it.) Oh, you may want this file: CF-Auto-Root-ms013g-ms013gxx-smg7102.tar.md5 which may help with rooting your phone if you haven't already done so.
I did the Recovery 3-button Samsung phone groping procedure (you know what I'm talking about Volume Up/Down button + power + home button)... but to no avail...I keep getting that boot loop (Unable to normal boot...etc). You know that stupid "Downloading" Android logo (with the blue worded script on the top left-hand corner) with message ..."Downloading ...Do not unplug source..." Well, I plugged the USB cable to the phone to my computer and Odin program recognized it (it'll read "Added"). The phone didn't give any indications that it was doing anything. Btw, if your Odin program doesn't recognize your device then you should find out why it doesn't. If it recognized it before and you flashed with the Odin program before, I don't see why it won't recognize it now? Some say it's the USB cable but I can't logically accept that kind of superstitious BS. Come on, it's a copper/aluminum wire cable wrapped in pvc -- not a script. A cable is a cable is a cable. If it worked before, it'll work again unless it's cut inside the pvc tubing. You can use a digital multimeter to easily test that for continuity (albeit with really tiny leads to be able to connect to the mini USB side). Anyways, if your Odin program won't recognize your phone, maybe try using a lower version, or re-installing, or another similar type of program that will work. I'm assuming you did install the Samsung USB driver for your PC (e.g. mine is -v1.5.61.0 -search for your appropriate version) so that your computer will recognize your phone when cable is hooked up.
DON'T FORGET TO have the "Auto Reboot" and "F. Reset Time" boxes checked on the Odin program. Then select PAD button and browse for your TWRP file (above) and hit "Start." The Odin will flash it and you'll see a light blue bar under the Android logo (on your phone) that will go from left to right and when finished....whooooohooo the phone auto restarts back to your last OS state without losing any info on the phone. At least it worked for me. Hope that helps. Sorry for the long post.

hi i am in official android 4.3 on my g7102 and i wanna install a recovery file. but every recovery file i tested dosnt work on android 4.3. can you help me?

If u have knox bootloader do not try to downgrade just get kitkat one and in odin check phone bootloader update

Seems like u really guys screwed up the recovery. Somehow on my first try of flashing a zip file (recovery), i got stuck on download mode and wont boot normally. When I fixed the problem, the phone boots normally but the recovery is the only problem I got. I fixed this problem for about 10 days ago, all i did was to reflash the recovery again, orrr flash other version of the recovery (if the downloaded recovery version didnt work) or flash other recovery if the another recovery didnt work. Make sure the recovery is working on the version of you're phone (jelly, kk, lollipop, marshmallow or nougat) and working also on the model version.
I know this is an old thread but I hope this reply helped

hello guys.
first i will start with the beginning. i have a grand 2 duos g7102 phone. i rooted the phone and installed CWM recovery in order to flash custom rom CM 12.1 Lollipop 5.1.1 everything was running well until i upgraded to CM 14 Nougat 7.0 COSMO, i didn't like it and when i wanted to get in recovery mode again it stopped working. Now i can't boot in recovery mode at all. Not showing CWM recovery like before only recovery booting for few second and after that the dead android and No command and there is more writing down the screen like Supported API: 3 but it is hard to read because the screen is always flashing.
i someone faced this problem before please help !!!
thanks in advance

Guys guys i had the same problem with my grand 2 7102.
I rooted my phone and flashed a recovery via odin.
But as i press the button combos it says. Could not do normal boot.
So, i found a solution for it.
Downloaded flashify for play store.
Extracted img. File of twrp recovery provided in the grand 2 thread 😬,
Flashed it with flashify
And guess what i was in the recovery and after that no problem came with the recovery flashing 🙂

If you guys keep having problems with no-pc flashing, try the pc flashing cause this is the better way of flashing other than apps.

I had the could not do normal boot problem
Do this ...
Google cwm test 4.4 ms013g.tar and download it
Put it in PA or PDA uncheck autoreboot keep freset time checked
Flash the file then when you get pass message in odin , remove battery and reinsert it and go to recovery mode directly with vol up + power button.
NOTE : Don't try to normal boot to system

S5 G900F - Infinite Bootloop, can't access bootloader, flashed with stock roms.. HELP

Hi,
**Long Story**
I'm new here - I refrained from posting as I know a repeat post can p*** people off but I can't find my problem or fix it.
My own Sony was stolen a week ago - My brother in law kindly gave me his old S5 as a back up phone.
He has never had any problems with it EVER. I did a factory reset (from the settings menu) to clear his data and straight away I was in a boot loop (Handset vibrates, Samsung logo displays, blue LED, vibrates, handset switches off.. over and over again) the only way to stop this is to remove the battery. I cannot enter recovery mode but I CAN enter download mode. According to the settings the handset was running the latest version of lollipop.
I took the phone home anyway, thinking I could fix it - leaving the battery out in my pocket.
When I got home, I put the battery in and the phone turned on, unfortunately I forgot to put the sim card in - so I removed the battery, put in the sim card and... Boot Loop!
At this point I was really frustrated so I left the battery out and went to sleep. I woke up in the morning, put the battery in and it worked fine, all day, then all of a sudden the phone switched itself off and now I'm back in a boot loop and this time it isn't wanting to work again.
I have:
- Flashed with stock roms using Odin (5.0 & 4.4.2) - Yes, I used the correct firmware for my handset.
- Flashed with Kies to the latest firmware
- In desperation, tried the "Bash your power button against a hard, flat surface" trick
- Shouted at the handset
None of these have worked and every post I have found says to put the phone in recovery mode, I CANT. When I try, the blue "Recovery Booting" text is displayed, but just restarts anyway...
Weirdly and at random times, twice, the phone has powered on while plugged into my laptop, but the screen is blank, I get message sounds and the soft keys below the screen light up, but the screen is blank.
Any body have any idea?!?!! I'm vaguely techy, however not with this kind of thing. Any help would be much appreciated. What confuses me is there was no problem before I did the factory reset.

didscub said:
Hi,
**Long Story**
I'm new here - I refrained from posting as I know a repeat post can p*** people off but I can't find my problem or fix it.
My own Sony was stolen a week ago - My brother in law kindly gave me his old S5 as a back up phone.
He has never had any problems with it EVER. I did a factory reset (from the settings menu) to clear his data and straight away I was in a boot loop (Handset vibrates, Samsung logo displays, blue LED, vibrates, handset switches off.. over and over again) the only way to stop this is to remove the battery. I cannot enter recovery mode but I CAN enter download mode. According to the settings the handset was running the latest version of lollipop.
I took the phone home anyway, thinking I could fix it - leaving the battery out in my pocket.
When I got home, I put the battery in and the phone turned on, unfortunately I forgot to put the sim card in - so I removed the battery, put in the sim card and... Boot Loop!
At this point I was really frustrated so I left the battery out and went to sleep. I woke up in the morning, put the battery in and it worked fine, all day, then all of a sudden the phone switched itself off and now I'm back in a boot loop and this time it isn't wanting to work again.
I have:
- Flashed with stock roms using Odin (5.0 & 4.4.2) - Yes, I used the correct firmware for my handset.
- Flashed with Kies to the latest firmware
- In desperation, tried the "Bash your power button against a hard, flat surface" trick
- Shouted at the handset
None of these have worked and every post I have found says to put the phone in recovery mode, I CANT. When I try, the blue "Recovery Booting" text is displayed, but just restarts anyway...
Weirdly and at random times, twice, the phone has powered on while plugged into my laptop, but the screen is blank, I get message sounds and the soft keys below the screen light up, but the screen is blank.
Any body have any idea?!?!! I'm vaguely techy, however not with this kind of thing. Any help would be much appreciated. What confuses me is there was no problem before I did the factory reset.
Click to expand...
Click to collapse
Who is your service provider? Is the phone unlocked? Where did you get the stock firmware from?

Cryceratops said:
Who is your service provider? Is the phone unlocked? Where did you get the stock firmware from?
Click to expand...
Click to collapse
Thanks for the reply!
Service Provider - o2 UK
Stock from sanmmob
Phone is not unlocked
I did my best to try & get the firmware for my particular service provider but sammob and a few of the other sites use those awful restricted speed file sharing sites.

didscub said:
Thanks for the reply!
Service Provider - o2 UK
Stock from sanmmob
Phone is not unlocked
I did my best to try & get the firmware for my particular service provider but sammob and a few of the other sites use those awful restricted speed file sharing sites.
Click to expand...
Click to collapse
Did you try the one I linked to you or a different one?

Cryceratops said:
Did you try the one I linked to you or a different one?
Click to expand...
Click to collapse
Only just saw that - I didnt - thank you.
I will try now but may take a while to get back to you while I wait to download.

Try flashing the PIT file along with the stock ROM in ODIN
http://forum.xda-developers.com/attachment.php?attachmentid=2721101&d=1399024091
Extract to .pit - add to PIT section in ODIN, add ROM to AP or PDA section, flash them both at the same time

*Detection* said:
Try flashing the PIT file along with the stock ROM in ODIN
http://forum.xda-developers.com/attachment.php?attachmentid=2721101&d=1399024091
Extract to .pit - add to PIT section in ODIN, add ROM to AP or PDA section, flash them both at the same time
Click to expand...
Click to collapse
Thanks, did that, now the phone has started but it stuck at the first "Powered by Android" screen, not restarting but can't go any further and still cant get into recovery.

didscub said:
Thanks, did that, now the phone has started but it stuck at the first "Powered by Android" screen, not restarting but can't go any further and still cant get into recovery.
Click to expand...
Click to collapse
Try flashing just the ROM again, and then try booting into recovery, and factory reset
Or try flashing TWRP 2.8.7.0 with ODIN, and then boot into recovery and factory reset
Use this guide (Don't worry about the SuperSU part if you don't need root, and ignore the reactivation part as you can't boot the phone yet - start at No.3)
http://forum.xda-developers.com/showpost.php?p=64961009&postcount=2
Are you flashing the latest Lollipop ROM too?
https://mega.nz/#!fVhhzRBC!A79uC8Fgg1mGCZOaujQCzBxcUUN9z_ctVVkigD8ffVM

*Detection* said:
Try flashing just the ROM again, and then try booting into recovery, and factory reset
Or try flashing TWRP 2.8.7.0 with ODIN, and then boot into recovery and factory reset
Use this guide (Don't worry about the SuperSU part if you don't need root, and ignore the reactivation part as you can't boot the phone yet - start at No.3)
http://forum.xda-developers.com/showpost.php?p=64961009&postcount=2
Are you flashing the latest Lollipop ROM too?
https://mega.nz/#!fVhhzRBC!A79uC8Fgg1mGCZOaujQCzBxcUUN9z_ctVVkigD8ffVM
Click to expand...
Click to collapse
flashed TWRP 2.8.7.0 - Doesn't go into revovery:
Recovery is not SEANDROID ENFORCING
Set Warranty Bit : Recovery
I was flashing with G900FXXU1BOJ1_G900FOXA1BOJ1_G900FXXU1BOJ1_HOME.tar.md5

didscub said:
flashed TWRP 2.8.7.0 - Doesn't go into revovery:
Recovery is not SEANDROID ENFORCING
Set Warranty Bit : Recovery
I was flashing with G900FXXU1BOJ1_G900FOXA1BOJ1_G900FXXU1BOJ1_HOME.tar.md5
Click to expand...
Click to collapse
Did you follow the guide I linked?
http://forum.xda-developers.com/showpost.php?p=64961009&postcount=2
Pull the battery after flash, do not allow the phone to reboot first etc?
Because that error is usually associated with you allowing the phone to reboot Automatically after flashing TWRP

*Detection* said:
Did you follow the guide I linked?
http://forum.xda-developers.com/showpost.php?p=64961009&postcount=2
Pull the battery after flash, do not allow the phone to reboot first etc?
Because that error is usually associated with you allowing the phone to reboot Automatically after flashing TWRP
Click to expand...
Click to collapse
Pulled as soon as it said Pass.
This is so confusing, is the Stock firmware that you've linked to in Mega the same as the one I have downloaded?
Will retry with TWRP again. BRB

didscub said:
Pulled as soon as it said Pass.
This is so confusing, is the Stock firmware that you've linked to in Mega the same as the one I have downloaded?
Will retry with TWRP again. BRB
Click to expand...
Click to collapse
BOJ1 yea, same one
Try different versions of ODIN, 3.09 up to 3.10.7 (Maybe even 3.07)

*Detection* said:
Did you follow the guide I linked?
http://forum.xda-developers.com/showpost.php?p=64961009&postcount=2
Pull the battery after flash, do not allow the phone to reboot first etc?
Because that error is usually associated with you allowing the phone to reboot Automatically after flashing TWRP
Click to expand...
Click to collapse
Definitely didt let it reboot & pulled the battery. Tried it twice to make sure.
I am downloading the Stock firmware that you have linked and will try that, is there any reason why it started to reboot constantly after I factory reset? It can't be hardware because there was never a HW problem before I reset it. I don't suppose you want to pop down from Durham and fix it?! lol

didscub said:
Definitely didt let it reboot & pulled the battery. Tried it twice to make sure.
I am downloading the Stock firmware that you have linked and will try that, is there any reason why it started to reboot constantly after I factory reset? It can't be hardware because there was never a HW problem before I reset it. I don't suppose you want to pop down from Durham and fix it?! lol
Click to expand...
Click to collapse
To London? wanna pay the plane fare? lol
If you got that firmware from Sammobile, the one I linked you to is the same one, that's where I got it from, you could try some different droid versions, try a KitKat ROM too
Not sure why it would boot loop after you factory reset it, if reactivation lock was left on, you should still have managed to get to the welcome screen, but then be locked out of the phone until you entered his samsung account login
Sounds like something bugged out during the reset, and didn't reset properly, or corrupted one of the partitions, which the PIT file should have fixed
Stock recovery is cr4p though, I've ended up with a bootloop just clearing caches from it before, and had to flash TWRP to clear them properly, then flash stock on top again just to get it to boot

*Detection* said:
To London? wanna pay the plane fare? lol
If you got that firmware from Sammobile, the one I linked you to is the same one, that's where I got it from, you could try some different droid versions, try a KitKat ROM too
Not sure why it would boot loop after you factory reset it, if reactivation lock was left on, you should still have managed to get to the welcome screen, but then be locked out of the phone until you entered his samsung account login
Sounds like something bugged out during the reset, and didn't reset properly, or corrupted one of the partitions, which the PIT file should have fixed
Stock recovery is cr4p though, I've ended up with a bootloop just clearing caches from it before, and had to flash TWRP to clear them properly, then flash stock on top again just to get it to boot
Click to expand...
Click to collapse
OK - Sorry for the delay but unfortunately I had to do stuff - I would have happily sat and tried to fix it all day.
So, I did spend some time on it earlier and a few things happened.
I reinstalled different firmwares, and also tried TWRP 2.8.7.0 a few times with different versions of Odin but nothing would work.
I reinstalled the firmware BOJ1, nothing
Tried PIT again, nothing
Then, after trying PIT I got the Firmware error and connected to Kies... It worked, but now I just have a blank screen (another seemingly common issue with these paperweights) - Unsure what to do now, the phone is on, i can call it, find it with device manager but the screen is just blank. FML.

didscub said:
OK - Sorry for the delay but unfortunately I had to do stuff - I would have happily sat and tried to fix it all day.
So, I did spend some time on it earlier and a few things happened.
I reinstalled different firmwares, and also tried TWRP 2.8.7.0 a few times with different versions of Odin but nothing would work.
I reinstalled the firmware BOJ1, nothing
Tried PIT again, nothing
Then, after trying PIT I got the Firmware error and connected to Kies... It worked, but now I just have a blank screen (another seemingly common issue with these paperweights) - Unsure what to do now, the phone is on, i can call it, find it with device manager but the screen is just blank. FML.
Click to expand...
Click to collapse
OK, so they phone is working, there's just no display...
OK, try resetting the phone remotely from here first
https://www.google.com/android/devicemanager
If it's not connected to the network - try this
http://forums.androidcentral.com/sa...ory-reset-galaxy-s5-computer.html#post4365754
If that still fails, try flashing a stock KitKat ROM from Sammobile, see if downgrading the OS is a big enough change for it to overwrite whatever is causing the problem
Wondering if TWRP has flashed, but the no screen thing is stopping you from knowing one way or another - if we could get into TWRP, we'd have a lot more options, including custom ROMs
---------- Post added at 10:00 ---------- Previous post was at 09:44 ----------
Uploaded the latest KitKat ROM
Code:
https://mega.nz/#!eIQEAQ6a!ztOhVwFuI2MpD6OBhxC-TtgwUJQCxtwnfDQvFOl3g40

*Detection* said:
OK, so they phone is working, there's just no display...
OK, try resetting the phone remotely from here first
https://www.google.com/android/devicemanager
If it's not connected to the network - try this
http://forums.androidcentral.com/sa...ory-reset-galaxy-s5-computer.html#post4365754
If that still fails, try flashing a stock KitKat ROM from Sammobile, see if downgrading the OS is a big enough change for it to overwrite whatever is causing the problem
Wondering if TWRP has flashed, but the no screen thing is stopping you from knowing one way or another - if we could get into TWRP, we'd have a lot more options, including custom ROMs
---------- Post added at 10:00 ---------- Previous post was at 09:44 ----------
Uploaded the latest KitKat ROM
Code:
https://mega.nz/#!eIQEAQ6a!ztOhVwFuI2MpD6OBhxC-TtgwUJQCxtwnfDQvFOl3g40
Click to expand...
Click to collapse
Thanks,
I'll wait for that to download and try.
So - I used accessibility mode to get into settings and do a factory reset... It was difficult, I even thought that the Dark Screen setting might have mysteriously have been turned on but nope.
Rebooted and got the Bootloader screen with the Samsung logo and Recovery Booting text, after a few minutes the screen went blank and the phone vibrated and then nothing!!! :crying::crying::crying:
I have just put it into download mode (I only know this because the many hours I've spent doing this I noticed that the battery and device goes cool when its in download mode) and will try the KitKat flash once its downloaded - Thank you for that btw.
Its so strange - it cant be an issue with the actual screen because it *sometimes* displays the logo.. What can it be?? Its also odd that from when I originally reset it, it could'nt boot into recovery. I'm worried that everything I have done has screwed it up more? Can the Recovery/Bootloader be "Broken"? Its so confusing, I hate tech that doesn't behave.

didscub said:
Thanks,
I'll wait for that to download and try.
So - I used accessibility mode to get into settings and do a factory reset... It was difficult, I even thought that the Dark Screen setting might have mysteriously have been turned on but nope.
Rebooted and got the Bootloader screen with the Samsung logo and Recovery Booting text, after a few minutes the screen went blank and the phone vibrated and then nothing!!! :crying::crying::crying:
I have just put it into download mode (I only know this because the many hours I've spent doing this I noticed that the battery and device goes cool when its in download mode) and will try the KitKat flash once its downloaded - Thank you for that btw.
Its so strange - it cant be an issue with the actual screen because it *sometimes* displays the logo.. What can it be?? Its also odd that from when I originally reset it, it could'nt boot into recovery. I'm worried that everything I have done has screwed it up more? Can the Recovery/Bootloader be "Broken"? Its so confusing, I hate tech that doesn't behave.
Click to expand...
Click to collapse
Does sound like a possible hardware problem, but unlikely or a huge coincidence that it all started after resetting, so I'd be more inclined to think otherwise
Just remembered about this unbrick image / tutorial
http://forum.xda-developers.com/galaxy-s5/general/g900f-debrick-img-lollipop-t3240626
Might be worth giving that a shot

*Detection* said:
Does sound like a possible hardware problem, but unlikely or a huge coincidence that it all started after resetting, so I'd be more inclined to think otherwise
Just remembered about this unbrick image / tutorial
http://forum.xda-developers.com/galaxy-s5/general/g900f-debrick-img-lollipop-t3240626
Might be worth giving that a shot
Click to expand...
Click to collapse
OK - might be a massive chore rooting and installing busybox.. Worth a shot though. Can I not use it with Odin??

didscub said:
OK - might be a massive chore rooting and installing busybox.. Worth a shot though. Can I not use it with Odin??
Click to expand...
Click to collapse
You don't need busybox, that's for creating your own debrick image, the tutorial stops here:
Flash this Debrick file to your 16GB Micro SD card with Win32DiskImager
*Insert your Micro SD card into your computer (backup any information you may have on it we are going to ERASE, FORMAT it to ex FAT
*Open win32DiskImager
*Navigate to the location where you downloaded the correct Debrick file
*Select your Debrick file by double clicking on it
*In the upper right corner of Win32DiskImager you should make sure that the drive letter assigned to your sd card is selected.
***Which ever drive that is listed will be erased, formatted
*Click write in the bottom right hand side
put the Debrick SD card in the Phone, Pull and Replace the Battery
Plug phone in usb and boot into download mode
yout phone should boot into download mode then flash stock firmware via odin
Download link : https://drive.google.com/file/d/0ByA...ew?usp=sharing
You're saying you can't see anything on screen in download mode, just guessing it's there because it cools down - but that could also mean it's not in any mode
With this method, you might get a display to use, then you can flash normally with ODIN with download mode visible on screen

Stuck in "Recovery Booting..." loop after flashing jk's Hybrid TMO rom

Hey guys, long time lurker. I've never needed to post before but this is beyond me. Flashed JK's new hybrid rom, following his post exactly:
https://forum.xda-developers.com/verizon-s7-edge/development/rom-t3569416
It rebooted into aroma, ran, and on reboot showed the samsung lock screen, flashed a few times and now says "recovery booting". It's been trying to "boot" recovery for a day now. Flashes the blue text on and off. I've tried the button presses as much as I can to get it into download mode. It will stop flashing when I press Home+Down Vol, but upon release it comes back flashing again. Nothing seems to work, and it never connects to the PC to try Odin or any ADB method of rebooting/forcing download mode. Maybe I can try to drain the battery and go from there? Although that may take days at this point..
Just trying to avoid going to big red at this point.
Thanks!

nightwolf0829 said:
Hey guys, long time lurker. I've never needed to post before but this is beyond me. Flashed JK's new hybrid rom, following his post exactly:
https://forum.xda-developers.com/verizon-s7-edge/development/rom-t3569416
It rebooted into aroma, ran, and on reboot showed the samsung lock screen, flashed a few times and now says "recovery booting". It's been trying to "boot" recovery for a day now. Flashes the blue text on and off. I've tried the button presses as much as I can to get it into download mode. It will stop flashing when I press Home+Down Vol, but upon release it comes back flashing again. Nothing seems to work, and it never connects to the PC to try Odin or any ADB method of rebooting/forcing download mode. Maybe I can try to drain the battery and go from there? Although that may take days at this point..
Just trying to avoid going to big red at this point.
Thanks!
Click to expand...
Click to collapse
first of all were you trying this with a non verizon phone and did you use firmware in my OP or were you trying to flash verizon firmware. Hold Volume Key Down PWR Button and Home Key you have to press all three this take you to download mode reflash eng boot.img with odin then start over. If that dont work flash full firmware in Odin

jrkruse said:
first of all were you trying this with a non verizon phone and did you use firmware in my OP or were you trying to flash verizon firmware. Hold Volume Key Down PWR Button and Home Key you have to press all three this take you to download mode reflash eng boot.img with odin then start over. If that dont work flash full firmware in Odin
Click to expand...
Click to collapse
Hey jrkruse, I've got the Verizon branded S7 Edge. (bought in store.). I was using everything listed in your OP and made sure I got everything correct (the FlashFire settings and sequence as well). I've been running your roms+tweaks forever now, and was previously running the "Echoe" rom rooted and running well enough. (I think I've been using your stuff since my S3/S5 days a long time ago. Never had any issues following your methods until now. )
This exact setup/rom is what I was coming from:
https://forum.xda-developers.com/ve...t/g935-g930-echoerom-multicarrierusa-t3458535
The problem is the phone doesn't respond any key inputs. I've tried everything I can find for the key presses, and it always goes back to "Starting recovery..." text on a black screen. I let it just go for the entire day, and now that the battery is drained I do get an icon to plug it into the charger (so maybe it's not bricked totally yet?). As soon as I try to plug it in it tries to start the "Recovery" boot again without accepting my button inputs. ADB also still doesn't see the phone at all. I assume that some part of the BL is corrupt and it's stuck trying to start it still.. Is there a key press that I can do WHILE plugging it into the usb of my PC or charger to force download mode no matter what? (Like the HTC and maybe the s3 had?). I get the feeling my issue is just because I can't do a full "battery pull" with the soft keys anymore, so it never actually restarts the actual BL and all.
Would some pictures help explain?
Thanks again for all your work!

Here are a couple of pictures to explain a bit more:
The "Booting Recovery.." text that flashes briefly:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The "Charge your phone" picture I get once it's too low on battery:

nightwolf0829 said:
Here are a couple of pictures to explain a bit more:
The "Booting Recovery.." text that flashes briefly:

The "Charge your phone" picture I get once it's too low on battery:
The "Charge your phone" picture I get once it's too low on battery:

Click to expand...
Click to collapse
Pull your sim and sdcard out. Hold the volume down home and power button while phone is dead then plug in while holding those three

Tried that, still doesn't do anything it seems. The second I let go of home, it tried recovery again. Maybe it's just not fully dead somehow? I make-shifted a zip-tie to make the 'No Power, plug in' flash until it -should- be an otherwise dead phone. Am I right in thinking it should be a brick after this, and plugging in 'should' allow me to use Home,Pwr,and Vol Down to get into Odin mode?
Like suffocating your pc,maybe there is a better way to drain the battery all the way?:
Thanks again!

nightwolf0829 said:
Tried that, still doesn't do anything it seems. The second I let go of home, it tried recovery again. Maybe it's just not fully dead somehow? I make-shifted a zip-tie to make the 'No Power, plug in' flash until it -should- be an otherwise dead phone. Am I right in thinking it should be a brick after this, and plugging in 'should' allow me to use Home,Pwr,and Vol Down to get into Odin mode?
Like suffocating your pc,maybe there is a better way to drain the battery all the way?:
Thanks again!
Click to expand...
Click to collapse
Have you tried holding Volume UP + HOME +PWR

That just brings the "Booting Recovery..." flashing again... I also noticed it also doesn't vibrate at all, like they normally do on a startup. The "bzz" letting you know you can let go of PWR doesn't seem to happen ever either.

nightwolf0829 said:
That just brings the "Booting Recovery..." flashing again... I also noticed it also doesn't vibrate at all, like they normally do on a startup. The "bzz" letting you know you can let go of PWR doesn't seem to happen ever either.
Click to expand...
Click to collapse
Give me a run down on what happened during flash. Including firmware you were on etc. Maybe I can at least keep this from happening too someone else
---------- Post added at 08:41 PM ---------- Previous post was at 08:36 PM ----------
I'm thinking flashfire must have failed in flashing the bootloaders

Makes sense, so this is actually a brick I suppose?
S7 was running your Echoe Rom Port (the AROMA_Version 1.5, as in the OP of that thread.) No updates or changes other than updates to FlashFire and installed apps. Was previously a MM rooted phone before flashing the Echoe Rom. Ran the engineering boot setup from early 2017 (if there are any differences, I can only find the one root method). Sorry I cant open my FlashFire backup in order to check the versions of my BL/Firmware/Modem/etc. I can post the zip somewhere and send you if if there is a way to extract my software versions?
Followed your exact setup to Flash over to your TMO Hybrid rom as in your OP of this thread:
https://forum.xda-developers.com/verizon-s7-edge/development/rom-t3569416
I made sure to have the installs in the correct order and check all of the folders (and uncheck injection of SuperSU).
Phone rebooted up to the "Samsung S7" white unlock logo a couple of times, then rebooted into the "Recovery booting..." loop.
Side note, would the 300 Ohm USB dongle trick possibly work in this case? Or is the BL probably gone/corrupt and I'm fully bricked?
Thanks!

nightwolf0829 said:
Makes sense, so this is actually a brick I suppose?
S7 was running your Echoe Rom Port (the AROMA_Version 1.5, as in the OP of that thread.) No updates or changes other than updates to FlashFire and installed apps. Was previously a MM rooted phone before flashing the Echoe Rom. Ran the engineering boot setup from early 2017 (if there are any differences, I can only find the one root method). Sorry I cant open my FlashFire backup in order to check the versions of my BL/Firmware/Modem/etc. I can post the zip somewhere and send you if if there is a way to extract my software versions?
Followed your exact setup to Flash over to your TMO Hybrid rom as in your OP of this thread:
https://forum.xda-developers.com/verizon-s7-edge/development/rom-t3569416
I made sure to have the installs in the correct order and check all of the folders (and uncheck injection of SuperSU).
Phone rebooted up to the "Samsung S7" white unlock logo a couple of times, then rebooted into the "Recovery booting..." loop.
Side note, would the 300 Ohm USB dongle trick possibly work in this case? Or is the BL probably gone/corrupt and I'm fully bricked?
Thanks!
Click to expand...
Click to collapse
In settings in Flashfire did you check allow flashing bootloader then when you added the zip did you check to mount system

Not that this helps, but my galaxy tab 4 did something similar.
Installed the update firmware in Odin, rebooted, and it didn't get past the Samsung splash screen. Next reboot, exactly what you said... recovery rebooting after that.
The recovery was gone, but I could boot into download mode that gave me an error stating to use kies to install the firmware. Kies wouldn't recognize the device. Any flash attempt of os systems in Odin resulted in fails.
My issue was that the system partition got completely erased and set to 0. Therefore, it had no space to install anything.
Next, I flashed a stock recovery, but had the error on writing system due to the partition corruption. I had to flash twrp and change the system partition from 0 to whatever it should have been. After that, I could Odin firmware and was back in business.
Long story short, this probably doesn't help because we can't flash recoveries, but I wonder if your system partition got corrupted?
Sent from my SM-G930P using XDA-Developers Legacy app

jrkruse said:
In settings in Flashfire did you check allow flashing bootloader then when you added the zip did you check to mount system
Click to expand...
Click to collapse
Pretty sure I did, but I'm honestly unsure at this point. I tried following your post exactly, as always, but it is possible I skipped that step. I really don't think so as I checked it all multiple times.
Sorry I can't recall better.
Does this change any options I may of had for recovery? I'm sure it's super unlikely to repair at this point as Odin, and Windoze never sees the device at any point of any restart. I also opened it up and manually disconnected the battery just-in-case, as I figured it wasn't actually turning off. Still the same, wont boot into Download mode, Recovery just displays the blue booting text.
Let me know if anything I can get from the phone would help before I try to get it replaced one way or another.

lvpre said:
Not that this helps, but my galaxy tab 4 did something similar.
Installed the update firmware in Odin, rebooted, and it didn't get past the Samsung splash screen. Next reboot, exactly what you said... recovery rebooting after that.
The recovery was gone, but I could boot into download mode that gave me an error stating to use kies to install the firmware. Kies wouldn't recognize the device. Any flash attempt of os systems in Odin resulted in fails.
My issue was that the system partition got completely erased and set to 0. Therefore, it had no space to install anything.
Next, I flashed a stock recovery, but had the error on writing system due to the partition corruption. I had to flash twrp and change the system partition from 0 to whatever it should have been. After that, I could Odin firmware and was back in business.
Long story short, this probably doesn't help because we can't flash recoveries, but I wonder if your system partition got corrupted?
Sent from my SM-G930P using XDA-Developers Legacy app
Click to expand...
Click to collapse
I totally think something low-level is corrupt/gone. I bet it's the BL just based on the fact it shows only a black screen when I do the key press. I'm betting it's a brick, but I'm waiting to make sure jrkruse has anything he needs to stop this happening to anyone else before I try to replace it.

nightwolf0829 said:
I totally think something low-level is corrupt/gone. I bet it's the BL just based on the fact it shows only a black screen when I do the key press. I'm betting it's a brick, but I'm waiting to make sure jrkruse has anything he needs to stop this happening to anyone else before I try to replace it.
Click to expand...
Click to collapse
I put a warning and a work around in my thread
---------- Post added at 10:45 PM ---------- Previous post was at 10:43 PM ----------
nightwolf0829 said:
Pretty sure I did, but I'm honestly unsure at this point. I tried following your post exactly, as always, but it is possible I skipped that step. I really don't think so as I checked it all multiple times.
Sorry I can't recall better.
Does this change any options I may of had for recovery? I'm sure it's super unlikely to repair at this point as Odin, and Windoze never sees the device at any point of any restart. I also opened it up and manually disconnected the battery just-in-case, as I figured it wasn't actually turning off. Still the same, wont boot into Download mode, Recovery just displays the blue booting text.
Let me know if anything I can get from the phone would help before I try to get it replaced one way or another.
Click to expand...
Click to collapse
Tell big red that the nougat update fried your phone. Hopefully they will replace. Keep me updated

jrkruse said:
I put a warning and a work around in my thread
---------- Post added at 10:45 PM ---------- Previous post was at 10:43 PM ----------
Tell big red that the nougat update fried your phone. Hopefully they will replace. Keep me updated
Click to expand...
Click to collapse
Will do! Thanks again! Hope my phone was just a fluke thing.

nightwolf0829 said:
Makes sense, so this is actually a brick I suppose?
S7 was running your Echoe Rom Port (the AROMA_Version 1.5, as in the OP of that thread.) No updates or changes other than updates to FlashFire and installed apps. Was previously a MM rooted phone before flashing the Echoe Rom. Ran the engineering boot setup from early 2017 (if there are any differences, I can only find the one root method). Sorry I cant open my FlashFire backup in order to check the versions of my BL/Firmware/Modem/etc. I can post the zip somewhere and send you if if there is a way to extract my software versions?
Followed your exact setup to Flash over to your TMO Hybrid rom as in your OP of this thread:
https://forum.xda-developers.com/verizon-s7-edge/development/rom-t3569416
I made sure to have the installs in the correct order and check all of the folders (and uncheck injection of SuperSU).
Phone rebooted up to the "Samsung S7" white unlock logo a couple of times, then rebooted into the "Recovery booting..." loop.
Side note, would the 300 Ohm USB dongle trick possibly work in this case? Or is the BL probably gone/corrupt and I'm fully bricked?
Thanks!
Click to expand...
Click to collapse
Which version of his Hybrid ROM did you install?
I don't recall if the USB dongle is compatible with the S7, but I have one laying around and will see if it works on the S7.
You are using an S7 Edge, not a flat, right?

I can confirm that the USB jig does not work on my S7 flat.

Try holding down power, BOTH volume and and down and the home key. all at the same time.. dont release any buttons... just wait about 8-10 seconds... that brings up a different boot option screen. (reboot normal, safe boot. wipe
... I was under the impression I could flash the Hybrid mode running any rom if I was rooted and had flashfire.. I tried flashing Hybrid rom running Stang rom.. and also encountered boot loop.. and above it how I stopped the bootloop. Good luck and hope this works for you also.

ronschuck said:
Try holding down power, BOTH volume and and down and the home key. all at the same time.. dont release any buttons... just wait about 8-10 seconds... that brings up a different boot option screen. (reboot normal, safe boot. wipe
... I was under the impression I could flash the Hybrid mode running any rom if I was rooted and had flashfire.. I tried flashing Hybrid rom running Stang rom.. and also encountered boot loop.. and above it how I stopped the bootloop. Good luck and hope this works for you also.
Click to expand...
Click to collapse
Hey thanks for trying but I tried everything on that phone. Had to go to big red and get a replacement. Luckily they got me one without having to go through Assurion.

[Help me] Hard Brick S8?

SM-G950FD
Recently just got the s8 and tried to flash and root to get the batman rom. My attempt was a huge failure. I failed the instructions and even had a friend you had already done this process check if I did anything wrong. Once in Odin and flashed with Twrp my s8 did not boot up to the os homepage nor was it in recovery mode. It was a black screen saying something along the lines of "verification reject" and the only option I got was to reset the phone. Reset the phone and tried to flash it again, same thing happened.
At this point I just wanted to use my s8 stock everything so I tried to go back into recovery mode but now I'm stuck in a boot up loop and I can only go into download mode. I tried flashing it with all stock everything except now one in Odin the process fails. Odin is still able to pick up my phone but once you hit start it will say "fail"
I can't turn off the device I just pretty much left it to die so it's kind of "turned off" but I've tried virtually everything I could think of. Not sure if there is anything else I could do or if this s8 is just literally a brick now. Any help would be gladly appreciated!

I_Love_My_Brick said:
SM-G950FD
Recently just got the s8 and tried to flash and root to get the batman rom. My attempt was a huge failure. I failed the instructions and even had a friend you had already done this process check if I did anything wrong. Once in Odin and flashed with Twrp my s8 did not boot up to the os homepage nor was it in recovery mode. It was a black screen saying something along the lines of "verification reject" and the only option I got was to reset the phone. Reset the phone and tried to flash it again, same thing happened.
At this point I just wanted to use my s8 stock everything so I tried to go back into recovery mode but now I'm stuck in a boot up loop and I can only go into download mode. I tried flashing it with all stock everything except now one in Odin the process fails. Odin is still able to pick up my phone but once you hit start it will say "fail"
I can't turn off the device I just pretty much left it to die so it's kind of "turned off" but I've tried virtually everything I could think of. Not sure if there is anything else I could do or if this s8 is just literally a brick now. Any help would be gladly appreciated!
Click to expand...
Click to collapse
Did you follow the steps exactly as it says here?
https://forum.xda-developers.com/ga...pment/recovery-twrp-galaxy-s8-exynos-t3595102
eg: when you press start in Odin to flash TWRP hold recovery button combo?
I would suggest starting again, go to download mode and start and read the instructions a few times step by step.
Or flash stock firmware and then start again. If you get an error in Odin post it here for help.

Hello
I have the same Problem
No boot, nothing
It only shows the Bootlogo
I cant flash Recovery anymore, only get failed
I can only go to Download Mode
What is this a new block by Samsung
I really hate Samsung!
Hope there is any help
Sent from my SM-G920F using XDA-Developers Legacy app

callumbr1 said:
Did you follow the steps exactly as it says here?
https://forum.xda-developers.com/ga...pment/recovery-twrp-galaxy-s8-exynos-t3595102
eg: when you press start in Odin to flash TWRP hold recovery button combo?
I would suggest starting again, go to download mode and start and read the instructions a few times step by step.
Or flash stock firmware and then start again. If you get an error in Odin post it here for help.
Click to expand...
Click to collapse
I have tried that as well. I tried again this morning and still the same issue. I load up all the files that are need for the stock flash and once in odin and I hit start the process starts but then says fail.

https://forum.xda-developers.com/galaxy-s8/help/stuck-bootloop-flashing-aqg5-fix-t3636857
Try this
Saved my Love
Works like a Charm
OMG....
Sent from my SM-G920F using XDA-Developers Legacy app

Denis Meissner1990 said:
https://forum.xda-developers.com/galaxy-s8/help/stuck-bootloop-flashing-aqg5-fix-t3636857
Try this
Saved my Love
Works like a Charm
OMG....
Sent from my SM-G920F using XDA-Developers Legacy app
Click to expand...
Click to collapse
I'm gonna give this a try!!!
What was the link that you used to get the firmware? I know sammobile the free download servers are down for maintenance

I downloaded the BL from BatMan Rom so there is no need to load the full Firmware
Sent from my SM-G920F using XDA-Developers Legacy app

Denis Meissner1990 said:
I downloaded the BL from BatMan Rom so there is no need to load the full Firmware
Sent from my SM-G920F using XDA-Developers Legacy app
Click to expand...
Click to collapse
I'm able to get into TWRP with the method you just showed me so thank you!!
I keep running into problems every time I move a step forward. Now when I move the batman rom file to the storage it says "failed" or file "corrupted" am I still doing something wrong?
even with TWRP, Magisk and no-verity installed my phone still can not boot up into the phone's OS I'm still stuck with a boot loop.
I've tried to wipe everything already and start over and still I'm in the loop

I_Love_My_Brick said:
I'm able to get into TWRP with the method you just showed me so thank you!!
I keep running into problems every time I move a step forward. Now when I move the batman rom file to the storage it says "failed" or file "corrupted" am I still doing something wrong?
even with TWRP, Magisk and no-verity installed my phone still can not boot up into the phone's OS I'm still stuck with a boot loop.
I've tried to wipe everything already and start over and still I'm in the loop
Click to expand...
Click to collapse
Sry for late answer :/
Have you tried to dl BatManRom again?
Maybe your dl wasn't successful
Try again, should work
I also installed BatManRom ?
Best Rom out there
Install BL and CP from BatManRom via Odin, then boot in TWRP
Advanced wipe all except external and then flash Rom
Choose your Settings, no need to install BL and CP again
after install, Reboot, wait for around 10 mins, then Setup System and all should work fine ?
Cheers
Sent from my SM-G950F using XDA-Developers Legacy app

I_Love_My_Brick said:
SM-G950FD
Recently just got the s8 and tried to flash and root to get the batman rom. My attempt was a huge failure. I failed the instructions and even had a friend you had already done this process check if I did anything wrong. Once in Odin and flashed with Twrp my s8 did not boot up to the os homepage nor was it in recovery mode. It was a black screen saying something along the lines of "verification reject" and the only option I got was to reset the phone. Reset the phone and tried to flash it again, same thing happened.
At this point I just wanted to use my s8 stock everything so I tried to go back into recovery mode but now I'm stuck in a boot up loop and I can only go into download mode. I tried flashing it with all stock everything except now one in Odin the process fails. Odin is still able to pick up my phone but once you hit start it will say "fail"
I can't turn off the device I just pretty much left it to die so it's kind of "turned off" but I've tried virtually everything I could think of. Not sure if there is anything else I could do or if this s8 is just literally a brick now. Any help would be gladly appreciated!
Click to expand...
Click to collapse
Hey same happened to me if you still need help ask me. I can send you my number through email and you can call me.

Hello to day i got an Hardbrick S8+ (HK region its G9550ZHU....) , its only detect by QHUSB 9008 and nothing more (no charge, no downloadmode , nothing .... just 9008 ) . The victim say he is trying to flash Combine file from octoplus box but the file have G9550ZCU , he want to bypass FRP lock. So any one have a idea ?

pardon

kertikhuseyin said:
pardon
Click to expand...
Click to collapse
You need the edl firehose and XML files and the software for recovering from a brick like that.
And frp bypass is not an allowed subject here because people who ask tend to have a device that is likely stolen

Hi guys,
I have big problem with my new G950F. I try to install custom recovery (twrp) via ODIN. I do it like I suposs to do. All was be fine. ODIN pass but now my phone won't turn on. They don't respond to anything , recovery buttons and download butont nothing. They take 0,16 A and computer dont recognize it.
After flashing custom recovery phone was be powered down when samsung logo appears. after that phone doesn't respond to anything.
I was try:
Download combo - 2 min
Recovery combo - 2 min
Restart combo - 5 min
JIG 301K (work on A510F) - also nothing happens.
what I can do?
Someone please help. Thanks