Related
Hello there,
I'm using a vodafone bloated version of the i9505 and wanted to flash CM or a clean stock 4.3 because I don't want to wait for vodafone to release updates.
I downloaded Odin and CWM for my device and followed the instructions correctly. All went as it should. But when I tried to boot into recovery, I got the boot logo and in the upper left corner it said in small blue text "booting recovery..." but it would just give me a black screen after a while and restart into normal mode. I tried flashing different versions of CWM via Odin. My next approach was to root the phone with cf auto root which succeeded. After that, I tried all of the above again, and still didnt get any results. I even tried the Cyanogenmod desktop intsaller and after a while it said: "cant communicate with your phone"
Please help!
I believe I had the same issue once. When you flash the recovery true Odin, make sure Auto Reboot is not selected in Odin. That fixed it for me. After the flashing is done, you need to remove the battery and insert it again. Then it should probably work.
Lennyz1988 said:
I believe I had the same issue once. When you flash the recovery true Odin, make sure Auto Reboot is not selected in Odin. That fixed it for me. After the flashing is done, you need to remove the battery and insert it again. Then it should probably work.
Click to expand...
Click to collapse
I tried what you suggested, and hat the same thing as before but after the second restart I kept holding the volume up key as someone suggested on the internet and got a CM boot screen with on screen buttons like in CWM. after a brief pause I got a violet screen with nothing on it. I am now very confused and have no idea how to fix this. The phone itself can be booted normally though.
It seems to be that something remained from the failed CM installation.
Any suggestions?
What version of Odin do you use? Try version 1.85.
TWRP
Lennyz1988 said:
What version of Odin do you use? Try version 1.85.
Click to expand...
Click to collapse
Hello again, I flashed TWRP and it worked! I had to hold the volume up button even after the logo with the small blue print showed up in order to boot into recovery. Still couldnt get it to boot into CWM though. But thank God there is no need for that anymore!
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...
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 flashed xposed framework. It booted a few times crashed and then I could still get to recovery twrp. I then flashed the original rom I was using it booted up and started completely but again crashed. So I booted recovery and flashed the original rapture 5.1.1 rom and it booted completely but after a few minutes it also crashed.
After that I was in a bootloop. In a weird way I'd have to take out the battery wait a few minutes then the power button would work (on battery). It'd try to boot vibrate, show the samsung note 4 letters and then shutdown.
Weird part is if I plug the wall charger in it just vibrates and tries to boot indefinitely. If I long hold the power button nothing happens. If I pull the usb cable out it cuts power even though I have a fully charged battery.
I've flashed twrp reovery via odin first, no luck. I've flashed the original cod6 firmware without luck. Then the original kernel and recovery. Nothing seems to work. Is my power button dead. My problems are similar to this also but it worked fine before I flashed xposed framework wanam.
http://forums.androidcentral.com/sa...battery-then-turns-off-after-two-seconds.html
The reason I think it might not be the power switch is if I take out the battery wait 15 and plug it back in the phone does not auto restart itself. I have to hold the power button to start it. After Odin flash of COD6 firmware I only get to recovery img message at the top and then it turns off.
Very similar to this problem
http://forums.androidcentral.com/sa...k-recovery-booting-screen-how-can-i-past.html
flash stock recovery, twrp, cwm recovery and still can't get to it. Only thing I haven't flashed it the modem.
Thanks for any replies
Sounds like a hardware r
Problem if odin is not flashing correctly and it has done correctly in the past. I had similar but could boot into download mode and flash nut it failed flashing . Had to reflash root, then reflash a stock rom which boot looped, then root, then flash recovery, then flashed a custom rom cmw2.1 which worked. Then to male sure I reflashed origianl 5.0 rom which then worked. Then started again rooting recovery and flash cm12.1 and all is fine. As long as u have download mode there should be a way to fix it try my method as I thought I had a paper weight for about 3 hours while I figured out the above.
Thanks
Steve
Digipro said:
Sounds like a hardware r
Problem if odin is not flashing correctly and it has done correctly in the past. I had similar but could boot into download mode and flash nut it failed flashing . Had to reflash root, then reflash a stock rom which boot looped, then root, then flash recovery, then flashed a custom rom cmw2.1 which worked. Then to male sure I reflashed origianl 5.0 rom which then worked. Then started again rooting recovery and flash cm12.1 and all is fine. As long as u have download mode there should be a way to fix it try my method as I thought I had a paper weight for about 3 hours while I figured out the above.
Thanks
Steve
Click to expand...
Click to collapse
Thanks I will try, I've tried everything odin cod6, cog2, bootloader, baseband, rom, kernel, flash reports good now but still bootloop, even tried Kies3, it completely said everything is good rebooted and just booted at the top left saying recovery... booting then shuts off.
Really weird part is as soon plug power to micro usb port it starts booting without me pressing any buttons?
First thing I do if it goes wrong is reflash original stock rom to create a clean sheet. I always find the simplest solution is usually the best, f
Aching modems, kernels, well u know what windows is like with registry errors cross link .dll files. Like with windows keep backups and reload and start afresh sometimes going too deep to fix something can make it worse :s
Yea it shouldn't boot just from inserting power cable it should goto charge screen.. If charge screen is corrupt then that could explain why It boots to go to charge screen but can't so hence the behavior. Makes sense to me .
Thanks
Steve
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.