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
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
Hello guys,
A friend of mine gave me his S6EDGE+ because it didnt boot anymore after he woke up. The night before that he installed an update but the phone worked fine after that.
The phone showed this message: http://imgur.com/a/cwLyM
I thought that it was easily fixed by flashing original 7.0 firmware but as you can guess i was wrong... It keeps rebooting right after the "Samsung Galaxy S6 Edge+" screen
So i tried to flash original 6.0.1 firmware but the same result
After that i flashed 7.0 again and after that twrp 7.0 but it never booted into twrp
So i flashed android 6.0.1 and the newest twrp for 6.0.1 but it still didnt booted into recovery and i am not able to boot in recovery.
After that i tried some older versions of twrp for 6.0.1 and it sometimes gave me the error: Recovery is not seandroid enforcing. I tried the same with 7.0 and older twrp versions, same results.
I also tried to flash 5.1.1 but i couldnt flash it.
What i also tried is to flash 7.0 bootloaders and after that 7.0 firwmare and the same for 6.0.1
I'm really desperate and dont know what to do anymore..
Current status: bootloop
I can enter download mode: http://imgur.com/a/XiS6Z
When you say you flashed original firmware, did you use odin to do it? Did you use the firmware from sammobile?
Apologies if it's shows in the pictures, but they aren't showing up on my phone.
1. how about if you try to reflash twrp, full wipe and install a rom?
2. Try fix it with Smart Switch with emergency frimware recovery / emergency device recovery. ?
kdogguk said:
When you say you flashed original firmware, did you use odin to do it? Did you use the firmware from sammobile?
Apologies if it's shows in the pictures, but they aren't showing up on my phone.
Click to expand...
Click to collapse
i can see that the images aren't working, ill fix that in a sec.
Yes i used odin and downloaded everything from sammobile because ive actualy paid them for de downloadspeed
justanpotato said:
1. how about if you try to reflash twrp, full wipe and install a rom?
2. Try fix it with Smart Switch with emergency frimware recovery / emergency device recovery. ?
Click to expand...
Click to collapse
ive flashed several versions of twrp but it never boots in recovery or i get the message recovery is not seandroid enforcing.
I also tried the Smart Switch method but without succes
no, u need learn some things about Binary Vercion, ima sure u have a B3 in this moments, so , download any firmware with Binary 3, if need more infor about that, check here http://forum.gsmhosting.com/vbb/f68...combination-compatibility-w-o-errors-2189001/
ruubs said:
ive flashed several versions of twrp but it never boots in recovery or i get the message recovery is not seandroid enforcing.
I also tried the Smart Switch method but without succes
Click to expand...
Click to collapse
You've never stated the results of your stock firmware flashing, using Odin. This is key, this tells you whether the firmware was flashed correctly or not.. If you picked the wrong stock firmware to flash, Odin will show it "Failed."
If your buddy just updated firmware, then it's likely he's on the newest one, but check in SamMobile to verify if it's accurate. If shows the most current firmware was updated in January or something then he might not be on the most current one, as this shows that he's behind on updating his phone, so it's uncertain which it last updated to.
If I were you, I'd verify first whether the Odin flash passed or not, prior to attempting any custom flashing.. After Odins finished flashing in the upper right corner will either show "Pass" or "Fail," it needs to show "Pass" before you can proceed to do anything else, as this confirm whether the stock firmware flashed correctly or not.
If it doesn't Pass, you have flashed the wrong firmware. Might be good to verify with your buddy, which carrier he had originally. If you indeed have a Samsung S6 Edge+, with the larger 5.7 inch screen, the model numbers begin as so, "SM-G928x" with difference being the "x" at the end, which coincides with whichever carrier it's on, (e.g. "A" for AT&T, "T" for T-Mobile" - U.S. carriers).
It wouldn't be a bad idea to confirm whether you're using the most up to date version of Odin, either. Don't remember what that is but a quick Google search under this topic would do it.
Just for shyts and giggles, you did verify that your PC recognizes the phone, right? And that it lists under "Device Manager" correctly, as well as Odin recognizing it after you plugged it in?
If it does "Pass," it should reboot by itself into the stock firmware since prior to flashing you selected "autoreboot" and "reset time" if it doesn't reboot correctly or gets stuck on the splash screen, unplug it from the PC and manually boot it into stock recovery. Do this by first pressing the following buttons at the same time and holding them till the phone powers off, power button, home button, volume up and volume down.. After it powers off, push and hold, power button, home button and volume up, till the phone boot to stock recovery, amd of course you can let go of the buttons/keys. Then using volume buttons to select factory reset and pressing the power button to confirm the selection. After it factory resets you can then select reboot to system and it should boot normally and you've recovered the phone.
The upper left corner in Odin will show the results of the flash, there shouldn't be a reason for it not booting if it indeed shows "Pass," cuz this confirms firmware flashed correctly, if it shows "Fail" then you flashed the incorrect firmware. You'll need to locate the right one so that Odin shows "Pass," otherwise you wont ever recover your phone, regardless of anything else you find interesting to flash, bootloaders, TWRP, root, ect.. Don't flash anything else till you get the stock firmware flashed correctly. If you're unable to accomplish this then, I'd recommend calling Samsung or your carrier, is it still under warranty? My charging port broke after 2+ years, I have insurance though w/ T-Mobile, called them to see what my options were, was planning on fixing it myself to avoid the $175 insurance deductible, if I made a claim, but as it turns out, since I have insurance, the phones still under warranty and per the CSR, it will continue to hace warranty as long as I pay the $7/month insurance. Thought most warranties are 12 months but I wasn't going to correct her if she was wrong so I went ahead with it and 2 days later new phone came and I sent my broken one back! Old phone has lil scratches on the screen, couple lil dings along the sides, obviously an older phone but now I gotta new one, ita flawless!
It won't to try if this don't work out..
Good luck
i have read through these forums for weeks and followed steps perfect but no version of Odin will succeed in doing a factory rom flash. i had the s4 rooted and uninstalled the touchwiz not realizing it was the launcher required to boot phone. since this happened i cant do a factory reset and odin will not work. in fact last time i tried odin it put my phone in a bootloop where as soon as i put the battery in it boots and continues to reboot. this phone has a locked bootloader and come stock with 4.4.2 i dont want to post a really long post with a bunch of info thats probably not needed so if more info is needed please ask. thanks in advance
If the phone constantly auto-reboots, then your power button is malfunctioning.
As for the other cases, use a different PC, Windows and/or USB ports. A cable switch is advisable too. And make sure you have the right firmware for the phone.
Any of those factors can make a change.
Also, unless it's a Verizon or AT&T phone, there's absolutely no possible way that thing has a locked bootloader.
I have a bootloop on the Samsung first logo with "Recovery Booting..." in blue on the top left (Samsung GT-I95026)
I have flash TWRP recovery, the phone don't want to boot on recovery, it's just bootlooping, flashed stock firmware with Kies, still bootloop, Odin, same thing
So after searching everywhere can't seem to find anything that can help, I assume it's dead then?..
bootloop stopped
Pwnycorn said:
If the phone constantly auto-reboots, then your power button is malfunctioning.
As for the other cases, use a different PC, Windows and/or USB ports. A cable switch is advisable too. And make sure you have the right firmware for the phone.
Any of those factors can make a change.
Also, unless it's a Verizon or AT&T phone, there's absolutely no possible way that thing has a locked bootloader.
Click to expand...
Click to collapse
phone has been sitting like 2 weeks with no battery and after your post i tried to boot to factory reset. it shows the recovery boot at the top of the screen but just goes to a half lit screen and does nothing.this phone wasnt even 2 weeks old when i bricked it. i use the factory oem cord plus have tried others. i have even tried a fresh install of win7 on my second hdd in this laptop with no changes to anything got my firmware here :sammobile.com/firmwares/search/sgh-1337
and yes this is an at&t phone factory unlocked with locked bootloader
soft brick fixable
Bastidn said:
I have a bootloop on the Samsung first logo with "Recovery Booting..." in blue on the top left (Samsung GT-I95026)
I have flash TWRP recovery, the phone don't want to boot on recovery, it's just bootlooping, flashed stock firmware with Kies, still bootloop, Odin, same thing
So after searching everywhere can't seem to find anything that can help, I assume it's dead then?..
Click to expand...
Click to collapse
i have read through these forums a lot trying to fix my s4 and im under the impression that if you can get to odin mode then the phone is "softbricked" and can be fixed.
freezes at at&t screen
galaxys4bricked said:
phone has been sitting like 2 weeks with no battery and after your post i tried to boot to factory reset. it shows the recovery boot at the top of the screen but just goes to a half lit screen and does nothing.this phone wasnt even 2 weeks old when i bricked it. i use the factory oem cord plus have tried others. i have even tried a fresh install of win7 on my second hdd in this laptop with no changes to anything got my firmware here :sammobile.com/firmwares/search/sgh-1337
and yes this is an at&t phone factory unlocked with locked bootloader
Click to expand...
Click to collapse
since that post i tried the factory reset and the phone just boots then stays frozen on the at&t screen
flashed and fixed
galaxys4bricked said:
i have read through these forums for weeks and followed steps perfect but no version of Odin will succeed in doing a factory rom flash. i had the s4 rooted and uninstalled the touchwiz not realizing it was the launcher required to boot phone. since this happened i cant do a factory reset and odin will not work. in fact last time i tried odin it put my phone in a bootloop where as soon as i put the battery in it boots and continues to reboot. this phone has a locked bootloader and come stock with 4.4.2 i dont want to post a really long post with a bunch of info thats probably not needed so if more info is needed please ask. thanks in advance[/QUOTE
i got my s4 flashed with stock rom from this thread:
forum.xda-developers.com/showthread.php?t=2674223
if anyone has the same issues i had with odin not working try that rom.....thanks for those of you who helped me
Click to expand...
Click to collapse
galaxys4bricked said:
if anyone has the same issues i had with odin not working try that rom.....thanks for those of you who helped me
Click to expand...
Click to collapse
Is there any way to unlock bootloader in ODIN? I have I9506 with 4.4.2 that was on it at first. Then i have updated it to 5.0.1 in OTA. So you say that I need to flash it in ODIN with 4.4.2 to make it work?
None of the Galaxy s4 phones have a locked bootloader except for the AT&T, Sprint, Verizon versions.
GT-I9506
S/N: RF8F20W841T
PDA: PL2 / PHONE: OJ2 / CSC: OK1 (NEE)
CAN'T BOOT IN TO THE SYSTEM (no matter what I can't make it to boot properly)
CAN'T ENTER RECOVERY (it's showing that's booting in to the recovery but instead of recovery it just restart)
CAN ENTER DOWNLOAD MODE (no problem with entering DM)
What I have done so far:
- Kies recovery with phone model number and serial number (still bootloop).
- Odin flashing STOCK rom from SamFirm download (still bootloop) (single and 4 files flash).
- Re-partitioning (flashing PIT file).
- Reflashing bootloder (still nothing).
- Tryed CWM, TWRP and other Recovery, non of them boot up.
Using those files to flash:
AP_I9506XXSDPL2_CL6069869_QB11747892_REV03_user_lo w_ship.tar
BL_I9506XXSDPL2_CL6069869_QB11747892_REV03_user_lo w_ship.tar
CP_I9506XXUDOJ2_REV00_CL1318424.tar
CSC_NEE_I9506NEEDOK1_CL6069869_QB7017077_REV03_use r_low_ship.tar
I would really appreciate help from someone more skilled then me.
Hello everyone,
I have problem with my s7, after trying to flash stock several times using odin, I am always getting s7 logo, and than blue screen with Erasing... , than it would restart with same pattern two or tree times and than shut down. I can only go in download mode, cant boot into recovery.
My phone is SM-G930F. I am pretty sure that I downloaded correct firmware. Maybe I did mess up something, any help is welcome.
Thanks in advance.:fingers-crossed:
LuDi_GliSa said:
Hello everyone,
I have problem with my s7, after trying to flash stock several times using odin, I am always getting s7 logo, and than blue screen with Erasing... , than it would restart with same pattern two or tree times and than shut down. I can only go in download mode, cant boot into recovery.
My phone is SM-G930F. I am pretty sure that I downloaded correct firmware. Maybe I did mess up something, any help is welcome.
Thanks in advance.:fingers-crossed:
Click to expand...
Click to collapse
Have you tried flashing with the same file?
Maybe the file is corrupt. Try redownloading and then trying
LuDi_GliSa said:
Hello everyone,
I have problem with my s7, after trying to flash stock several times using odin, I am always getting s7 logo, and than blue screen with Erasing... , than it would restart with same pattern two or tree times and than shut down. I can only go in download mode, cant boot into recovery.
My phone is SM-G930F. I am pretty sure that I downloaded correct firmware. Maybe I did mess up something, any help is welcome.
Thanks in advance.:fingers-crossed:
Click to expand...
Click to collapse
I'm having the same problem. Using the binary U5 "combination" file, I was able to access the system and enable OEM unlocking, so I could install TWRP and then a Custom ROM. But that's it, I can't use ROM Stock anymore, my phone only works if it's in a Custom ROM. I wanted to solve the problem so I could use Stock again. Bottom line: In ROM Stock, the phone is locked under the name SAMSUNG GALAXY S7 EDGE, enters recovery and appears "ERASING" then erases and repeats everything again, never starting the system or having access to Recovery.
Sorry for the bad english, I used translate ...
Hey! Look this video, he works for me!!
https://www.youtube.com/watch?v=l8-ccufk4Q0