Related
Hi,
I've got my good old 9505 I bought right at release on which the Volume UP button (or more likely whatever hardware it's connected to, as the button itself works perfectly normally) has become stuck pressed.
That causes a little problem - I can't enter Download mode anymore (Normal power up enters recovery due to the stuck key, Vol Down cancels Recovery and boots normally).
I had a custom ROM and recovery on it, and in order to send it for repair I obviously want to put it back to stock status, so I have reflashed a stock MI8 image I found using ODIN, using the custom recovery's "Reboot in Download mode" command.
Now the problem is I have bad luck and likely had an incompatible modem, and after booting even with cache/data wiped I have the Samsung keyboard crashing constantly and WiFi won't work.
Of course restoring the stock image wiped my custom recovery, so I can't use the same trick to get back into Download mode and reflash another modem.
I can't use Mobile ODIN or reboot menus with a "Reboot Download" option, as those requires root, but... rooting needs Download mode.
I can connect to Kies, but for my region it unfortunately says the current ROM is already the latest.
Does someone have an idea I didn't think about?
is there a way to reboot to download mode via usb debugging?/adb shell or something like that?
I found something that suggested it, however while I've painfully been able to go enable USB debugging (with the UI that locks and the "Samsung Keyboard has stopped" messages that appear between nearly every tap) adb devices returns nothing. Maybe the same issues cause debugging to fail too...
make sure that all instances of kies are stopped and also try reinstalling the drivers?
OK, found an app called "Kingo Android Root" that works from the PC through adb, and managed to root it again. It took some time to connect, but once it did it went through the procedure OK.
Then I could transfer the apk for "Quick Boot" to the phone through MTP, and its reboot menu worked to reboot in Download mode
Got a new modem flashed, and WiFi is back. The Samsung keyboard is still crashing every 5 secs, but I'll just try reflashing the OS, never know...
now that you can get to download mode, you can just restore everything back to stock? no? should fix any fc's you're getting, unless they are related to the physical fault with the volume up button being stuck?
Yes, it's just a matter of finding the right stock ROM... :\
OK, the MKF ROM for my country I found here works perfectly fine.
Issue closed then, hope this will serve other people who might end up in a similar situation
Now to see how the service center reacts to a stock config but with Knox flag set...
good luck, and don't forget to let us know how you get on with the service centre/knox situation.
Good news, received my S4 after a one week turnaround (shipping included), and it was repaired under warranty even with the Knox bit set and me having dismantled it (thanks Sammy for not putting "warranty void" stickers, pretty much the first manufacturer I see who doesn't!)
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 all!
Here is a little problem that i didn't solved.
i have a N910F Note 4 that likes to boot loop . I received it as it is and don't know what caused it(i suppose that was a rooting issue because had the knox value 1)
During the all time, PC and MAC were unable to recognize the Note 4, despite of repeatedly reinstalled drivers(older and newer versions) , Keys and Smart Switch were unable to recognize the device, PC is failing to install the MTP driver for some reason. I changed the USB ports,restarted,updated drivers,updated windows etc. -NO RESULT. BUT : Somehow Keys is able to run recovery and initialization and install it on the device while saying Connecting device... , phone also doesn't appear in device manager or file explorer as external drive.NOTHING! Odin and Jodin says ''added!'' and starts the job with no comments
1. I tried different versions of boot loaders with different versions of ROM (all for my specific model) with no result.
The end of the boot is when Samsung logo ,sound and graphic appears but freezes before actually starting OS, then restarts. IT keeps restarting until battery goes off(even while connected to pc by usb!!! ). Then starts to charge the battery normally.
It boots in recovery and download mode with no problems, it did every time i flashed it…
2. I tried different versions of boot loaders with stock roms , custom kernels etc...and the problem was the same
3. I tried to flash with Odin the stock 4.4.4 without problems but….the problem was the same
4.I tried Device recovery and initialization with Keys and here something interesting happened:
First time when i did it, it went over the samsung logo and booted. I selected language,i skipped wifi network selection and i accepted the user agreement. No matter how fast i was moving, the boot loop didn't went over the user name selection which is after the user agreement. Then freeze and boot again.
Second time when recovered with Keys (tried more stuff in the mean time) it went over the logo and started to update like…''updating applications 2of 17'' the max reach point was ''3 apps of 17'' and then freeze and reboot
I am out of ideas so i suspect that the battery might be dead because it gets empty even if is charging while phone is ''boot looping''. I ordered a battery,should arrive soon.
If that don't work…i am gonna spend some cash and sent it to Samsung for repairs (i bet that it won't be cheap because they will probably tell me that is the motherboard fried so they make you pay for being a bad boy and tried to root). Far as i know is not a brick as long as download mode and recovery works just fine.
Is here someone that has any new ideas for bringing this phone to life? Any help is well received , maybe i skipped something….
Thank you in advance.
Boot into recovery and perform a factory reset, it will wipe the internal storage.
Battlehero said:
Boot into recovery and perform a factory reset, it will wipe the internal storage.
Click to expand...
Click to collapse
That was the first thing i tried , cache wiped also. After every rom when booting failed.
UPPME said:
That was the first thing i tried , cache wiped also. After every rom when booting failed.
Click to expand...
Click to collapse
Uninstall Kies, and install Samsung USB drivers: https://www.androidfilehost.com/?fid=24052804347849220
Take the battery out, leave it for approximately 10 seconds, enter the battery back in.
Hold volume down key + Home key and power on the device.
Then plug the mobile phone into the computer.
Run Odin as Admin: https://www.androidfilehost.com/?fid=24052804347851815
Then flash the firmware in the AP section.
Make sure that the firmware is for your region, you can download it from Sammobile or SamFirm.
i have the same problem, but mine doesn't let the samsung logo finish when it shows the letter S on samsung logo it goes restart again no sound or anything, recovery is accesible, download mode is also accessible, i can flash official firmware and factory reset but nothing change, still stuck in bootloop no one here in xda knows how to fix it i think.. or they just never encounter something like this
i know how to fix an ordinary bootloops or soft bricked.. but this one is different.. i think there's something with note 4 that causes this..
kerbiii said:
i have the same problem, but mine doesn't let the samsung logo finish when it shows the letter S on samsung logo it goes restart again no sound or anything, recovery is accesible, download mode is also accessible, i can flash official firmware and factory reset but nothing change, still stuck in bootloop no one here in xda knows how to fix it i think.. or they just never encounter something like this
i know how to fix an ordinary bootloops or soft bricked.. but this one is different.. i think there's something with note 4 that causes this..
Click to expand...
Click to collapse
Yes, it doesn't go after the Samsung graphics , mine does sound. Goes to app updates only after Kies recovery but doesn't go more far than updating apps 3/17 for ex…crushes there and starts over….weird.
One time i managed to actually go to setup menu, choose country,wifi, device name, and there crushed and started over…. So i am thinking now that the battery might be wasted because i saw posts saying that after the 5.0.1 update many Note 4's went to boot loop and the battery change solved the problem. Now i have new battery coming by post.
Hi I had a similar problem but I do not know if that works but always worth a try
1. download recovery - "twrp-2.8.1.0-trltexx"(.tar) cant post link fresh in forum
2. flash recovery through Odin (AP) ( run as administrator)
3. unplug the cable
4. Reboot to Recovery (home+power+wolume up)
5. Then go to Wipe/Advanced Wipe/check the boxes - Dalvik Cache,System,Data,Cache and Swipe to Wipe
6. Reboot to Download Mode
7. Open Odin ( run as administrator) choise the rom to flash
8 Connect the phone
7. Flash Your Stock Rom
8. Reboot
always in Odin load the file first to flash and then connect the phone
sorry for my English
UPPME said:
Yes, it doesn't go after the Samsung graphics , mine does sound. Goes to app updates only after Kies recovery but doesn't go more far than updating apps 3/17 for ex…crushes there and starts over….weird.
One time i managed to actually go to setup menu, choose country,wifi, device name, and there crushed and started over…. So i am thinking now that the battery might be wasted because i saw posts saying that after the 5.0.1 update many Note 4's went to boot loop and the battery change solved the problem. Now i have new battery coming by post.
Click to expand...
Click to collapse
if you can stay in recovery mode and download mode for more than 10mins i think its not battery problem, i think i have corrupted system files, i left my note 4 to samsung service center a while ago i will get it tom, i just hope they wont charge me too much for it,
uldyzjan said:
Hi I had a similar problem but I do not know if that works but always worth a try
1. download recovery - "twrp-2.8.1.0-trltexx"(.tar) cant post link fresh in forum
2. flash recovery through Odin (AP) ( run as administrator)
3. unplug the cable
4. Reboot to Recovery (home+power+wolume up)
5. Then go to Wipe/Advanced Wipe/check the boxes - Dalvik Cache,System,Data,Cache and Swipe to Wipe
6. Reboot to Download Mode
7. Open Odin ( run as administrator) choise the rom to flash
8 Connect the phone
7. Flash Your Stock Rom
8. Reboot
always in Odin load the file first to flash and then connect the phone
sorry for my English
Click to expand...
Click to collapse
nah it doesnt work thats the first thing I do, that only work on ordinary bootloop
I was stuck in a boot loop the other day trying to flash a stock ROM to get rid of encryption. I tried all the stuff mentioned in this thread which is just standard procedure but I couldn't get past the samsung logo. What it turned out to be was that you need to go to stock recovery after flashing the stock ROM via odin and do a factory data reset then it will boot to the OS. It worked in my case, maybe you can give it a try.
guts100 said:
I was stuck in a boot loop the other day trying to flash a stock ROM to get rid of encryption. I tried all the stuff mentioned in this thread which is just standard procedure but I couldn't get past the samsung logo. What it turned out to be was that you need to go to stock recovery after flashing the stock ROM via odin and do a factory data reset then it will boot to the OS. It worked in my case, maybe you can give it a try.
Click to expand...
Click to collapse
if you read the above post you will know that we already wipe and factory reset,
btw since i was not able to fix it, it brought it to samsung service center and they also cant fix it so they are changing the motherboard, so far they are not charging me anything and just asking to bring my receipt of purchase so it will be under warranty
kerbiii said:
if you read the above post you will know that we already wipe and factory reset,
btw since i was not able to fix it, it brought it to samsung service center and they also cant fix it so they are changing the motherboard, so far they are not charging me anything and just asking to bring my receipt of purchase so it will be under warranty
Click to expand...
Click to collapse
I read the post; however, it did not appear as though you did a factory reset after flashing the stock ROM only before. At any rate at least you're getting a new mobo out of it and problem solved.
guts100 said:
I was stuck in a boot loop the other day trying to flash a stock ROM to get rid of encryption. I tried all the stuff mentioned in this thread which is just standard procedure but I couldn't get past the samsung logo. What it turned out to be was that you need to go to stock recovery after flashing the stock ROM via odin and do a factory data reset then it will boot to the OS. It worked in my case, maybe you can give it a try.
Click to expand...
Click to collapse
guts100 said:
I read the post; however, it did not appear as though you did a factory reset after flashing the stock ROM only before. At any rate at least you're getting a new mobo out of it and problem solved.
Click to expand...
Click to collapse
yes thats the good thing and its under warranty even though im already rooted, with knox 01 and custom binary haha, i was already expecting to pay a huge amount of money but they said they will cover it, so its a blessing, but i hope the OP fixed his problem.
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
Hi people, I was trying to add lte band to my g530h xxu with Xenon hd rom (it didn't work at the end). First, I used efs tools to access to the modem connection. I used afterwards QPST and QXDM (QXDM didn't work xD) so after I had given up trying to add the new bands. I decided to undone everything restoring a back up I have done before starting. when I started I noticed that while restoring some parts (boot partition) didn't complete with the Mb that where supposed to be restored, but the phone kept working. I wasn't receiving signal after that so I used odin to install this firmware G530HXXU2AOC2_G530HODD2AOA1_G530HDDU2AOA1_HOME.tar everything seemed ok until I flashed the recovery twrp-3.1.1-0-fortuna3g.img.tar. I started receiving "could do not do normal boot" and it showed the download mode, but it wasn't recognized by odin xDDD, with the normal key combo it still works. I tried flashing the lollipop version TWRP_2.8.7.0_Lollipop, I think the other one was not for that firmware xD. Now it is showing a grey screen (it is turned on) and if I press the home button it brightens a little but that's all.
I rooted it using king root, and then I flashed the recovery using the TWRP app, maybe it could work, but it didn't as well xD.
I'd really appreciate if someone could point me in the right direction maybe I'm missing something or there is a magic file that I can push through odin to solve the problem. I really miss my customized cellphone, I had an xperia z2 but it got broken so im starting to optimize this one. its my hobby. anyway I messed it up somewhere and I dont know what to do to recover it(the recovery).
Summary
-tried restore from back up
-flashing firmware through odin
-using TWRP app
What I've been receiving
-black screen (turned on)
-message "could not do normal boot" with download mode interface
the phone still boots into android normally, with signal and everything
any idea is welcome
nevermind xD