Related
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
I was trying to upgrade from CM11 to CM12, which went smooth except for GAPPS closing constantly. I read online that this was caused by an old version of the recovery, so I tried to update TWRP to 2.8.4.0. I first tried using the TWRP app from the Play Store (after recovering my Nandroid backup), which locked the phone where it would only try booting into recovery, but couldn't get there. Holding the power button to turn it off would result in a reboot right back into recovery, which of course never went anywhere. Now I am trying to re-install TWRP using ODIN but It fails every time [Complete(Write) operation failed.] I have an early S4 from AT&T and it has never had an official update. I can't remember which firmware it is using, but it is the original so I shouldn't have any problems there. Can anybody help me get this thing up and running with either TWRP or CWM and CM12 please?!
If someone here can help you, they will. But you might have better luck asking over at http://forum.xda-developers.com/galaxy-s4-att as this is the International S4 section.
Sorry, I didn't catch that. Thank you.
Just for the record, I have been able to get the phone to boot by first booting into Download mode, then hitting the Volume Down button to cancel. This has twice booted it back into the OS. Still no recovery though.
Solved
I was able to install TWRP 2.8.4.0 from the app after getting the device to boot. It worked correctly this time and all appears to be well. Odd that ODIN didn't work though.
Just a quick suggestion...
You just need to hold down both VOLUME buttons + POWER button + HOME key to REBOOT. No need to CANCEL, etc. This is how to reboot at any stage.
I've spent all day fighting with the boot loop on my A500f.
I had the phone running really well with Ahmed's Resurrection Remix ROM on this post:
https://forum.xda-developers.com/sa...om-resurrection-remix-5-8-2-sm-a500h-t3572062
He doesn't detail TWRP installation, so I used DeadSquirrel's 3.1.0 post here:
https://forum.xda-developers.com/sa...overy-twrp-3-0-2-0-samsung-galaxy-a5-t3439233
I hadn't seen that TWRP can be installed without root, so I rooted with Chainfire first. I'm not sure, but I think I got the Chainfire file from this post:
https://forum.xda-developers.com/sa...-to-root-galaxy-a5-a500fu-lollipop-5-t3137613
The file I downloaded for the A500f is "CF-Auto-Root-a5lte-a5ltexx-sma500f.zip" (contains tar.md5)
The post says it is for Lollipop, but the instructions say this is a Chainfire root zip for Android 4.4.4. One post suggested this might be the cause of my boot loop.
The instructions say that this Chainfire Auto Root solution also contains a recovery file, but I was never able to boot into this recovery, so I went directly to installing DeadSquirrel's TWRP. I was able to boot into this recovery. From there I installed the Resurrection Remix ROM. WIthin the ROM, I installed SuperSU from the Play Store, but SuperSU informed me the phone was not rooted, so I flashed the SuperSU root zip from their website, which I believe was the file, A500FXXS1CQC2_A500FOJV1CPH3_XFE.zip
SuperSU now reported root was present, so I installed WiFi Connection Manager from the Play Store, granted it root access in SuperSU, and used the Fix Problems menu item to repair the wifi shutting off the phone problem that I was originally working on. That fix worked well, so I left the wifi on and ran YouTube on Autoplay for about 4 hours. Deciding the problem was solved, I gave the phone back to my son, and he brought it back to me dead 5 minutes later. I'm not sure if it already that the boot loop problem at that point.
The phone would no longer boot. I noticed a seandroid enforcing notification, and thought it might be a security issue preventing boot. I found a thread that said I needed that flashing back to a Samsung ROM would remove the seandroid notice and that I needed to update to Android 6.0.1 before installing TWRP to solve the boot loop issue. I went to Sammobile and found the newest ROM for my A500f was the A500FXXS1CQC2_A500FOJV1CPH3_A500FXXU1CPH2_HOME.
I installed this in Odin, and the phone has never come back to me since then. I've made endless retries throughout the day, trying different combinations of the Chainfire root, different versions of TWRP, and different root methods, but all to no avail. One post even suggested that if you flash factory ROM from Odin just once, it will create a boot loop, but if you flash twice, it solves it, but it didn't work for me. It's also gotten increasingly difficult to get into recovery. Whether in stock ROM or TWRP, I was only able to get in about 10% of the time. Boot loop behavior has varied between boot logo - vibration - black screen and battery charge logo - vibration - black screen.
I found this thread that is supposed to address the boot loop problem, and I tried these versions of root and TWRP, but it didn't help:
https://forum.xda-developers.com/sa...overy-samsung-galaxy-a52015-sm-a500f-t3360802
At the moment, I'm on stock ROM. On power up, you get the Galaxy A5 screen, then it vibrates and goes black, then the lightening battery logo comes up, it vibrates, and goes black, and then the green battery status logo comes up, and then the phone goes black. It's also booting into stock recovery okay, and I can do the recovery functions. I just can't boot the phone.
So now, I try the instructions again in ashyx's TWRP post. Now I can get into TWRP. I power up and the phone sticks on the Galaxy A5 boot screen for a long time. Then it vibrates and repeats. It's basically the same as above, but there is a long delay before rebooting instead of instantly as before. Now I go back into TWRP and flash the Resurrection Remix ROM and the behavior is the same. Power up and get the Galaxy A5 boot screen for 8 seconds (this time sporting a warranty bit: kernal notice), 2 seconds of black screen, vibration, battery/lightening logo blinks on, then off, vibration, battery/lightening logo blinks on then off. Black screen, then standard battery charging percent indicator. I did that three or four times to make note of the behavior. Then the power switch wouldn't work, so I used the technique to press the volume up and down key together with the power key to turn it back on. Now it is in a non-stop 5 second cycle of vibrate - flash the icon - black screen that won't quit. Throughout the day I've been stuck with this in both stock and custom ROM. Only once during the day did I see the custom ROM boot all the way through. The stock ROM has never booted.
Now the recovery key combination won't boot TWRP either. The key combination just makes the Galaxy A5 screen flash instead of the battery icon. But I can get into TWRP by rebooting with the recovery key combination on leaving Download mode.
If anyone understands what's wrong here, I'd appreciate it.
Thanks
If I were you, I'd flash an older version of stock ROM with Odin, reboot with factory reset then I will let Samsung Smart Switch to upgrade my phone. After that I will notice the CORRECT version of ROM...
MoshPuiu said:
If I were you, I'd flash an older version of stock ROM with Odin, reboot with factory reset then I will let Samsung Smart Switch to upgrade my phone. After that I will notice the CORRECT version of ROM...
Click to expand...
Click to collapse
Thank you. That did the trick. Going back to the original factory ROM of Android 5.0.1 brought the phone back to being bootable again. I wish I understood what is going on on the low level to cause these things!
MoshPuiu said:
If I were you, I'd flash an older version of stock ROM with Odin, reboot with factory reset then I will let Samsung Smart Switch to upgrade my phone. After that I will notice the CORRECT version of ROM...
Click to expand...
Click to collapse
Samsung Smart Switch what is it?
Faraz_74 said:
Samsung Smart Switch what is it?
Click to expand...
Click to collapse
Samsung app:
http://www.samsung.com/us/smart-switch/
Same Issue
Hello PJK2011 . I'm having the same problem can you please help me to find the link of the Stock ROM you installed?
xoein said:
Hello PJK2011 . I'm having the same problem can you please help me to find the link of the Stock ROM you installed?
Click to expand...
Click to collapse
I believe Sammobile is the standard location to download stock Samsung ROMS:
https://www.sammobile.com/firmwares/galaxy-a5/SM-A500F/
xoein said:
Hello PJK2011 . I'm having the same problem can you please help me to find the link of the Stock ROM you installed?
Click to expand...
Click to collapse
you can download in here also updato.com
Sent from my SM-A500F using xda premium
I had to reboot my device due to problems with my speaker. Now i'm not able to boot anymore.
I'm only able to get into ODIN Mode, and flashing new FW or TWRP does nothing. It'll flash correctly, but as soon as it sends the reboot command the device powers off and does not boot, and no, it does not reach the "Galaxy s8, powered by android screen".
It does not want to power on, and only responds to the odin button combo, can't boot into recovery either since nothing works.
I was running the latest version of Renovate Ice if that matters.
I've searched trough some other threads, but it seems like i'm the only one that's having this problem.
Any help or thoughts would be greatly appreciated!
Edit 1: I've tried flashing both AQK7 and AQG5. Both flash fine, but as soon as odin sends the reboot command to my phone, it turns off and does not turn on.
Auto Reboot is ticked. Same goes for any version of TWRP, it will flash, but when it has to reboot the device turns off and does not turn on. There's nothing on the screen, its completely black and the only thing that does work is Download Mode. I've also tried ereasing nand, and repartitioning storage. Both seem to have 0 effect. As stated in one of my replies, i was running the latest build of renovate-ice with magisk, no other mods, or themes installed.
Im a bit confused - you can only boot into download mode (not into twrp?) and the phone is in bootloop? Have you flashed anything (mod?) before or activated a substratum theme which could cause this?
The only thing I can think of is a) you delete in twrp file manager the corrupted file, if there is something like this or b) a twrp restore from a backup. Boot into download mode and then do not press vol up to go into odin mode but press vol down to reboot - then immediately press the combo for twrp and you will get to the recovery. This helped my s8 many times when I was in a bootloop and couldnt boot up twrp
FloM94 said:
Im a bit confused - you can only boot into download mode (not into twrp?) and the phone is in bootloop? Have you flashed anything (mod?) before or activated a substratum theme which could cause this?
The only thing I can think of is a) you delete in twrp file manager the corrupted file, if there is something like this or b) a twrp restore from a backup. Boot into download mode and then do not press vol up to go into odin mode but press vol down to reboot - then immediately press the combo for twrp and you will get to the recovery. This helped my s8 many times when I was in a bootloop and couldnt boot up twrp
Click to expand...
Click to collapse
Thanks for the reply! Other than using the Renovate-Ice rom, and running magisk the thing was pretty much stock. wasn't messing around in twrp either. Its not stuck in a bootloop either, it just refuses to do anything other than go in and out of DL mode. The phone does not respond to any button imputs other than DL mode. As stated in the OP it does not boot at all, just a black screen. i've already tried to reflash a stock FW and TWRP, but that does not seem to work...
try the method I did - this is the last thing I could think of, before reflash the whole phone with odin
More info about your speaker problem
popmpopm said:
More info about your speaker problem
Click to expand...
Click to collapse
There isn't much to say about the problem ,it just stopped working, hence why i rebooted the phone, and ran in to the problem i'm having right now.
FloM94 said:
try the method I did - this is the last thing I could think of, before reflash the whole phone with odin
Click to expand...
Click to collapse
Doesn't work sadly, but thanks for the help anyways!
but you havent installed Viper4Arise or anything like that?
Because of this my speaker also stopped working a few weeks ago
if you can get into download mode then get into download mode and leave phone, then download samsung smart switch for your pc (older version like 4.1.17022_20 from here http://www.filehorse.com/download-samsung-smart-switch/29268/ that allows phone based recovery), once installed open it, then click on more at top right, (do not update the software if you get a prompt) select emergency device recovery...., then click on right tab (device initialisation) and fill in your phone details etc., connect your phone (in download mode) and follow the process, maybe it works, you'll need to root and install TWRP again but thats no big issue.
Jostian said:
if you can get into download mode then get into download mode and leave phone, then download samsung smart switch for your pc (older version like 4.1.17022_20 from here http://www.filehorse.com/download-samsung-smart-switch/29268/ that allows phone based recovery), once installed open it, then click on more at top right, (do not update the software if you get a prompt) select emergency device recovery...., then click on right tab (device initialisation) and fill in your phone details etc., connect your phone (in download mode) and follow the process, maybe it works, you'll need to root and install TWRP again but thats no big issue.
Click to expand...
Click to collapse
I've tried this just now, and it still gives me the same result, it goes trough the process, but as soon as it has to reboot it doesn't boot anymore.
Thanks for the suggestion though!
FloM94 said:
but you havent installed Viper4Arise or anything like that?
Because of this my speaker also stopped working a few weeks ago
Click to expand...
Click to collapse
i think phone is damaged by water or dropped s8 so fragile phone ! its happen to me with s5 the phone dead after speaker problem !!
popmpopm said:
i think phone is damaged by water or dropped s8 so fragile phone ! its happen to me with s5 the phone dead after speaker problem !!
Click to expand...
Click to collapse
I've had a case on the phone since day one, and I've checked for water damage, but there is non. The tab that is supposed to indicate it is untouched. But thanks for your input! I appreciate it
I have the same problem. Its look like is bootloader issue. try flash this soft :
G950FOWA1AQCC_Recovery
But if you are on newest rom it wont work.
Hello, you can solve this problem?
Hi,
I've looked everywhere before writing this so please forgive me as I saw there are a number of threads similar to this but couldn't find an answer.
Have rooted the phone a few days ago and flashed the Alexis Rom Oreo2.1S9PORT. As I had several apps that where acting up (no MIcrosoft Active Sync, no Outlook notifications among other things) I made a bit of a mess of it and decided to reset the phone by erasing all contents. As I went to boot up again the phone was in loop.
It goes on download mode and have tried with ODIN to reflash AP, BL, CP, CSC read everywhere looked on youtube but Odin fails each time. I've downloaded samsung drivers and firmwares to have Samsung Oreo back but to no avail.
Could someone please give me a hand in restarting the phone somehow? It's now in loop and I will wait until it dies down from battery failure as suggested in some threads in here.
Sorry to pester you.
Newbie...:crying:
latest ODIN screenshot. I don't know what more to try...please help...
Can you boot into Recovery Mode?
(Power off your phone, than hold: Bixby + volume up + power on button until you see the recovery mode)
Norup58 said:
Can you boot into Recovery Mode?
(Power off your phone, than hold: Bixby + volume up + power on button until you see the recovery mode)
Click to expand...
Click to collapse
No unfortunately. NOw the phone is battery drained.
THis is the Downloading mode. I can't think of what to do unfortunately. I've tried 3 or 4 firmwares as well.
Since I deleted through the phone system reset and not through TWRP (which I've now lost obviously) what would be the best way to reflash the mod (or the original Samsung one for that matter)?
ok I thought I made some progress, I've managed to reinstall TWRP and flashed again the Rom, Rom fix, and AOD fix. I was able to check the options of the Rom and the ROm installed succesfully. As I went to reboot I got stuck again in a loop with the SAMSUNG logo flashing continuosly. I can feel I'm close to a solution, could you point me in the right direction please?
The continuosly boot-loop could be the firmware doesnt match the Rom.
If you are game, try installing Renovate Ice: https://forum.xda-developers.com/ga...ovate-ice-g950-g955-android-7-0-aqdg-t3598040
Click the orange colored RENOVATE ICE WEBPAGE link.
From the menu choose FIRMWARE, download and flash.
Then download and flash R.Ice rom - follow the How to Flash guide
Norup58 said:
The continuosly boot-loop could be the firmware doesnt match the Rom.
If you are game, try installing Renovate Ice: https://forum.xda-developers.com/ga...ovate-ice-g950-g955-android-7-0-aqdg-t3598040
Click the orange colored RENOVATE ICE WEBPAGE link.
From the menu choose FIRMWARE, download and flash.
Then download and flash R.Ice rom - follow the How to Flash guide
Click to expand...
Click to collapse
Thanks a lot. I managed alone 5 minutes ago. Reflashed the TWRP, then the Oreo ROM, and then the samsung firmware... result now I have a working fresh empty Samsung S8 with all Samsung apps... I now know how to do it. :laugh::laugh::laugh: