Ok, so i am reposting this hoping that someone could help me with my problem. maybe I have not explained it enough the last time.
I am still not able to update my g7102 to 4.4.2 kitkat, it always goes well everytime i try to update it via Odin (from Sammobile) or OTA (450mb). but here's the problem, It always gets stucked at the screen where I get the phone model with "Rebooting Recovery" in blue. I had to wait for around 20mins before it go to android animation where it has a green line below showing that its applying the update, then it goes to the setup wizard but touchscreen doesnt work. I tried turning it off an on but I had to wait for another 20mins and touchscreen still doesnt work.
I want to try anything first before going to the service center and pay since I got this from a different country and dont think if it still has warranty.
I really want kitkat on my phone. I hope someone could help me with this.
Thanks guys!
Related
Hey everyone!
I've got an interesting predicament here. A little back story: a while back I installed TowelRoot, and then Xposed Framework. Everything was kosher until I got an OTA update (I believe the NG3 update) and it killed the root. No problem, I'm fine without root. But now that Lollipop has come out, I want to update but can't. My buddy applied the same root, but did not do Xposed. The difference between our phones after that OTA update: mine says "Custom" with an unlocked padlock at the Samsung boot screen; his does not.
I read in another thread that someone took their phone to Best Buy and the guys at the Samsung booth were able to fix the problem because they can pull updates and apply them via USB. So we went there yesterday and they had no problem getting Lollipop on my buddy's S5 Active. Mine, however, would not take the update. The Samsung S.M.A.R.T. tool they use on the PC was saying that "my device is running an unauthorized operating system", even though I have never flashed a custom ROM.
When I go into download mode, the Knox flag does not appear to be tripped. I've also performed a clean factory reset with a data wipe and that still didn't allow me to update. Whenever I try to update, it downloads the entire 4.4.4 update (which needs to be done first, before the 5.0 update) and it starts to install, failing at 25%, without hesitation, every single time.
I've attached a couple of screenshots that I hope will help. Any ideas will be greatly appreciated.
MGArcher007 said:
Hey everyone!
I've got an interesting predicament here. A little back story: a while back I installed TowelRoot, and then Xposed Framework. Everything was kosher until I got an OTA update (I believe the NG3 update) and it killed the root. No problem, I'm fine without root. But now that Lollipop has come out, I want to update but can't. My buddy applied the same root, but did not do Xposed. The difference between our phones after that OTA update: mine says "Custom" with an unlocked padlock at the Samsung boot screen; his does not.
I read in another thread that someone took their phone to Best Buy and the guys at the Samsung booth were able to fix the problem because they can pull updates and apply them via USB. So we went there yesterday and they had no problem getting Lollipop on my buddy's S5 Active. Mine, however, would not take the update. The Samsung S.M.A.R.T. tool they use on the PC was saying that "my device is running an unauthorized operating system", even though I have never flashed a custom ROM.
When I go into download mode, the Knox flag does not appear to be tripped. I've also performed a clean factory reset with a data wipe and that still didn't allow me to update. Whenever I try to update, it downloads the entire 4.4.4 update (which needs to be done first, before the 5.0 update) and it starts to install, failing at 25%, without hesitation, every single time.
I've attached a couple of screenshots that I hope will help. Any ideas will be greatly appreciated.
Click to expand...
Click to collapse
Have you resolved this issue, if so, would you mind sharing how you did it. I've been combing the net for a few days trying to discover what is going on and your issue appears to be exactly what I am experiencing. I've read about flashing back to my stock firmware using Odin but I cannot get into download mode, when I try and get there, the phone only says "recovery reboot" in blue small font on the top of the screen and reboots.
Thanks
Ladies and gents, I apologize for abandoning this thread. I forgot exactly how I got to get the phone to update, but if I recall correctly, it had to do with me putting the phone in download mode, downloading the original firmware and using ODIN to flash it. Afterward, the "unlocked" padlock symbol disappeared and the phone was able to get the OTA update from AT&T.
I have since moved from an LG G4 to a V20 and that is what I am currently playing with. I also have a Samsung Galaxy S6 Edge (which T-Mobile replaced my G4 with when the touch screen stopped responding). I was quite stoked to find out that there is a way to root it and (seemingly) unlock the bootloader, so I'll be toying with that this weekend to see what I can do. I'd love nothing more than to just wipe that Samsung-ified Android and install a vanilla Android or CM.
Good luck to anyone who is still trying to fix this issue. Again, my apologies. I'll dig through my archives and see if I can piece together what I did to get it going again. I still have the S5 Active. Best phone by far. It's a great backup phone for when the new stuff goes kaput.
Hi people. As you may imagine, i've been trying to update to Lollipop since it was released for my device like a month ago (i have a SM-G530M, LTE version in Argentina), but i'm experiencing, like some people, a weird problem whenever i try to flash the last firmware through ODIN ( G530MUBU1BPH2_G530MUUB1BPH2_G530MUBU1BPG1_HOME.tar.md5 ).
>>I'll give details about my issue to make myself clear
The thing is that, Odin shows me the "Passed" message, and when the phone should reboot and make a fresh start (i made sure to wipe /data, /cache and dalvik), it shows the initial "Samsung Galaxy Grand Prime - Powered by Android" screen (which i must tell..., shows up for many seconds, and then, the screens turns gray with many bars, so after a couple of minutes, it restarts again.
In this scenario, i can't access the recovery mode, though i can still fortunately get into download mode, so i had to stick in kitkat searching for a solution.
After some googling, i came across with this:
htcmania. com/showthread .php?t= 1067200
Effectively, the problem is caused by owning a NON-original touchscreen replacement, and to make sure, i asked for help to my friend to disconnect the screen while trying to boot into Lollipop. The idea behind this was to wait for the typical startup sound since the system didn't even show the boot animation during the failure (and the phone would get warm too). So, with the display and digitalizer disconnected, we could hear the startup sound! and the heat was gone. So my problem is that i have the touchscreen of another Grand Prime variant, made for the G530H "Duos". It works ok, but only in Kitkat.
I tried to get the original replacement specifically for my variant (G530M), but i can't get it even on the internet.
In the meanwhile, i thought about installing lollipop and then, restoring/installing the previous Kitkat bootloader over, but i suspect this may be dangerous.
Would this brick my device? I'm aware that Lollipop brought changes to the bootloader so the problem is to make the system boot in the first place.
Just that, thanks a lot in advance!
alpha-ro said:
Hi people. As you may imagine, i've been trying to update to Lollipop since it was released for my device like a month ago (i have a SM-G530M, LTE version in Argentina), but i'm experiencing, like some people, a weird problem whenever i try to flash the last firmware through ODIN ( G530MUBU1BPH2_G530MUUB1BPH2_G530MUBU1BPG1_HOME.tar.md5 ).
>>I'll give details about my issue to make myself clear
The thing is that, Odin shows me the "Passed" message, and when the phone should reboot and make a fresh start (i made sure to wipe /data, /cache and dalvik), it shows the initial "Samsung Galaxy Grand Prime - Powered by Android" screen (which i must tell..., shows up for many seconds, and then, the screens turns gray with many bars, so after a couple of minutes, it restarts again.
In this scenario, i can't access the recovery mode, though i can still fortunately get into download mode, so i had to stick in kitkat searching for a solution.
After some googling, i came across with this:
htcmania. com/showthread .php?t= 1067200
Effectively, the problem is caused by owning a NON-original touchscreen replacement, and to make sure, i asked for help to my friend to disconnect the screen while trying to boot into Lollipop. The idea behind this was to wait for the typical startup sound since the system didn't even show the boot animation during the failure (and the phone would get warm too). So, with the display and digitalizer disconnected, we could hear the startup sound! and the heat was gone. So my problem is that i have the touchscreen of another Grand Prime variant, made for the G530H "Duos". It works ok, but only in Kitkat.
I tried to get the original replacement specifically for my variant (G530M), but i can't get it even on the internet.
In the meanwhile, i thought about installing lollipop and then, restoring/installing the previous Kitkat bootloader over, but i suspect this may be dangerous.
Would this brick my device? I'm aware that Lollipop brought changes to the bootloader so the problem is to make the system boot in the first place.
Just that, thanks a lot in advance!
Click to expand...
Click to collapse
Did you ever try to buy it at Samsung Store? They maybe have it
I didn't consider that, i'll see if i can contact them directly, hopefully i can get the replacement i need. Thanks friend!
hi. i have a brand new phone s7 edge sm-935f to be more specific if this helps
got it in june. and now from a few days my phone started to freeze during gaming lets say that is a bigload or something and sometimes even when i wanna browse the gallery or even do simple stuff like calling someone..... i don`t know what happend...
this happend since i did the update on december? doesn`t matter the last big update.... i`m on forums 3 days now.... aand since this happend i knew that people are having problems like this... but still so i did the big damn update... and this happend
and now i`m trying to downgrade my phone... dld the firmware from sammobile? the site that everyone says... don`t know
i don`t know what to tell you more guys. i need some help i can`t do this on my one.
as i understand if i can enter in recoverymode blabla it`s not hard bricked? so that`s a very good thing so this means that this problem can be fixed.
i can load the phone by doing some forced resets.
i did hard factory reset.
i did try to flash stock firmware with odin... and kinda still nothing... after doing this i installed nfs no limits to test the phone and still the phone frooze and bam samsung logo we meet again.
i really don`t know what to do anymore.
does it has an importance if the phone came with " hungary firmware " and i dld the uk version ? maybe this could be the problem the language? don`t know
i need some help please i`m desperate.
thank you very much
p.s sorry for my bad english
edit1: didn`t root my phone didn`t try to install a custom thing on it, i started having this problems like 3-4-5 days ago after i did the last update in december can`t remember it.
edit2: dld the romanian (orange version ) gonna see if this works.... but after odin finished flashing the firmware i had to force restart the phone so it can boot... i quess this doesn`t work, i`m gonna dld the 2 versions of firmware of " hungary " and gonna try with those 2... will update when i`m done. in the meanwhile please tell me how i can fix this faster
edit3: i did manage to play a little bit of nfs no limits with this romanian (orange version ) but it frooze and restarted... i will try to install the hungary firmware and see then.
odin stock firmware, get TWRP, flash a custom rom, problem solved. If that dint solve it, you might have a hardware issued which means you are out of luck, need to send in the phone.
i really don`t want to loose my warranty by installing a costum rom on my phone....
as i know if i do that will **** up my waranty right?
any other suggestions?
You mentioned in initial post you would be trying certain stuff. What's the phone status now?
Try the APB1 of 2016.03.11 from SamMobile
phone status right now is still in the same status... tried to flash the 2 hungarian versions.. nothing.... even if it boots if i try to do something it goes in bootloop again... i`m trying to run an antutu benchmark....
some guy that works in a phone service place told me this: he things because of the update samsung rolled out the phone rams cpu is starting to break... because the update wasn`t tested enough,,,, don`t know what to say anymore. right now i don`t have time for the phone. i replaced it with other phone till next year then i`m gonna try to make it work again.
jonrayne i`m gonna try that firmware next yeah.
thanks
up. i think i have to change my phones motherboard.... because of the new update i think becuz of the bugs maybe it ****ed up my phones components i don`t know. if nothing works i will have to do this change. it will cost me 120-130$.... do you guys know any other option to try and fix my phone? i need to try everything before i will spend this money
Recruter said:
up. i think i have to change my phones motherboard.... because of the new update i think becuz of the bugs maybe it ****ed up my phones components i don`t know.
Click to expand...
Click to collapse
Hah, sitting in exactly the same boat as you after the last FW update, my thread is here:
http://forum.xda-developers.com/s7-edge/help/s7e-suddenly-bootlooping-dying-t3528827
up
any more suggestions?
or do i really have to go and change my mobo?
edit1: is there a way to test any part of the phone ? to see what part of the phone is fckd up? i tried to run an antutu benchamark when the phone worked a little bit but the phone went in bootloop at cpu test and ram test don`t know.
hey guys. i think i might have a fix for this sh1t
found on some forum i don`t know if it`s safe to post smt from another phone android related stuff if it`s safe i will paste here the post on that forum.
i found out that a guy with the same problems just like me and the same problems routine.... installed a nougat beta firmware and his phone worked after that. now i don`t have time to find and search a " valid " nougat beta firmware because i`m not home... can you guys please tell me if this is true or if somebody tried this option to fix this sh1t?
found out that many people have the same problem just like me after doing that update from samsung.
now my question is where can i find an " official " nougat update firmware to download. and try this because i don`t wanna go and pay 120$ to switch the mobo and then have the same problems.
saw a guy saying that there is one on sammobile but i don`t really have time right now to search for it. can smb tell where i can dowload one?
thanks
please smb reply
edit1: sorry for my bad english.
up
tried to update the nougat beta fw but nothing... it gets stuck at " erasing blue screen " think after odin finishes to upload the fw to the phone....
after that i flashed stock fw again... still gets stuck on erasing blue screen... or i get the exclamation mark.... tried to whipe cache etc... nothing
Recruter said:
up
tried to update the nougat beta fw but nothing... it gets stuck at " erasing blue screen " think after odin finishes to upload the fw to the phone....
after that i flashed stock fw again... still gets stuck on erasing blue screen... or i get the exclamation mark.... tried to whipe cache etc... nothing
Click to expand...
Click to collapse
Same problem here! What is your phone status now?
sound like a strategic move by samsung to force u replace motherboard again and again until u decided to give s8 a try. then u realise , **** it. get a cheaper phone with similar spec.
Hi guys, today I made a big mistake by thinking that it would be so easy to root on my S5 +, I was wrong, because it appear that I had the bootloop problem, i resolved it by mistake i was so lucky, I tried to put a BootLoader on Odin on AP section, an error occured on my phone, It reset it and it did come back to life Yeah WTF right ? So now that i've got my phone back ! I'm happy but still, I'm worry about my sim and I want to know if someone is listening to me (because strange things happened lately), that's why I did some research and It appear that an app does exist to prevent such thing ! it's called Snoopsnitch, Amazing isn't it ?
I've got hope that you might be able to help me to root my phone properly this time and avoiding the loopboot issue. If you can led me to do it, it would be amazing.
There is my config. I wish you a good day, night or whatever you are doing on this planet. Kiss. :victory:
https:// ibb.co/FqssRkM
https:// ibb.co/5BPrc7p
Sorry i'm new and i'm not allowed to share my image link so I had to trick the system ><
Thanks for your time and your answers guys. :highfive:
Oh hi, im having the boot loop / logo problem too.
could you explain more clearly what you did to resolve that and is it still good to this day?
ive already used odin3 v3.11 and put the latest stock firmware successfully but the phone still boot loops or if lucky it will get passed the carrier screen (O2) but then as soon as i restart the phone it will boot loop again. (or boot loop randomly, if i dont restart it myself, eventually).
I havent tried TWRP or PIT as im a basic user and just wanted the stock rom.
Any updated advice? ...im worried its the memory/emmc/hardware prob
thanks
Hi guys and gals
I am probably duplicating a thread for which I apologise in advance, but I have no clue for what key words I should be using to search for to find an existing answer, assuming there is one!?
I have the s8+ (SM-G955f) purchased in the UK via Vodafeon.
The battery died some weeks ago and I've had no money to be able to buy a replacement until now. I did try to use it now and again, but it last no more than a minute, but what did seem to happen is what is referred to as the boot loop saga.
I have followed other threads for instructions and downloaded Odin v.3.13 along with the varoius files (BL,AP,CP,CSC) from a zip file (G955FXXU9DTF1_G955FOVF9DTF1_VOD.zip) I was doing this late last night and do no remember which website I got it from, it took sooo long to download.
I am now at the point where I have connected the phone via USB and I have run the program and the status went to green, said 'pass' and the phone rebooted, however it is back to the Samsung welcome screen and sometimes keeps rebooting, other times, just stays there.
Where do I go from here? would it be that I have used the wrong firmware? I have never done this stuff before and have no clue, but am desperate to have a working phone as I have no money to replace it
Any advice, very welcome
If the battery went bad why flash firmware. Replace the battery
TheMadScientist said:
If the battery went bad why flash firmware. Replace the battery
Click to expand...
Click to collapse
I guess the issue was when the battery had issues, it would last maybe a minute or 2 before shutting down and then having to wait a full day before trying again. I did this for about a week as needed to get phone numbers from the phone along with some other info.
On the last occassion the phone turned on before the battery finally gave up, it seemed to go into the bootloop.
So now, I have tried various versions of Firmware via Frija and using Odin 3.13 to instal, but the phone doesn't seem to want to accept it.
The phone was originally purchase via Vodafone in the UK. I have tried VOD and BTU.
I am now in Asutralia, so have also tried TEL and VAU as have had sims from them also.. if that makes a difference?
I cannot get into the recovery mode at the moment, no clue why, just the download screen. The last time it went into recovery it kept mentioning about ATT which I don't understand as the phone has never had an AT&T connection which I think is in the USA and the phone has not been there..
Does anyone have any other suggestions? Would it be crazy to try and instal a custom OS and then revert back, or does the phone always remember the original firmware? I hope this all makes sense as this is all new to me..
Thanks in advance.