Hi! A couple of weeks ago I let my Galaxy S5 (G900F, Dutch, Vodafone) auto update to lollipop. Problems within a week (spontaneous reboots for instance). Then today my phone went in bootloop. Couldn't get out.
So I started reading/googling: The advice was to use odin to reinstall the latest lollipop version (I check for the G900F one ). Didn't work; still bootloop (with the difference that it had recovery boot or something in the topleft part of the screen). So then I tried installing an older (Kitkat) version: Odin (v3.09) gave out a FAIL. I tried both the kitkat (4.4.2) and the lollipop versions multiple times.
Then I read that I should use a CWM (again, checked for the correct one) and then I get the 'seandroid' message, and then it bootloops again.
Sorry for the wall of text but I just want to get my original lollipop (or preferably kitkat since I liked that one better) back...I don't even want a custom rom
Oh and just to be clear: I can't get into the recovery mode (power, home and vol.up); it just gives me the 'bootloop' screen. I can only get in the download screen (power, home and vol down),
I have the same problem in my G900f. till now there is no solution found for this problem..as per the Samsung technical team member, this is for RAM problem and have to change the mother board to resolve the issue. Motherboard price is same as the new set price. …
Related
Hi guys, got yesterda my Note 3 LTE+ (SM-N9005 - snapdragon SoC)
out of the box it was fine, installed my apps, got my google account up and running, ignored all "sign-up-now-to-our-cloud-stuff"-Samsung stuff requests, dumped the shovelware.
then i got the first OTA update, some 35 MB in size, went fine too
then i got the android 4.4.2 OTA update (~360 MB or so), did reboot.
Things SEEMED fine the first 5-10 minutes. Then I did the "swipe from bottom-edge up to start samsung newreader/media"-thingy (the one that shows a wooden chair, with stool that has newspaper and reading glasses on it, overlooking some grassy landscape vista), system froze-shut. After 1-2 minutes I forced reboot with Volume-Down+Power held, since then I'm stuck in some crazy boot-loop that not even Recovery-mode, forced dalvik-cache flushing, nor factory-reset helped.
A] WHY/WHAT happened to getting stuck in this boot-loop
B] how can I remedy that, that doesn't involve sending it in?
my current stock rom image is KOT49H.N9005XXUENA7
I've got the German T-mobile image N9005XXUENA7_N9005DTMENA2_N9005XXUENA2_HOME.tar.md5 from sammobile.com (that's NOT the one that I updated the phone with, the phone got updated via standard OTA updater)
according to a link here on xda-dev ODIN v3.09 is not compatible with the Note 3 LTE+ (SM-N9005) version - which version should I use and where to get it?
KIES v3 doesn't connect to phone
Is there a way to flash the whole ROM again via ADB (recovery mode seem to have an ADB update push feature)
Will flashing the stock Rom trigger the Warranty/eFuse kill-bit 0x1 flag?
thanks-a-thon in advance guys
atlana said:
Hi guys, got yesterda my Note 3 LTE+ (SM-N9005 - snapdragon SoC)
out of the box it was fine, installed my apps, got my google account up and running, ignored all "sign-up-now-to-our-cloud-stuff"-Samsung stuff requests, dumped the shovelware.
then i got the first OTA update, some 35 MB in size, went fine too
then i got the android 4.4.2 OTA update (~360 MB or so), did reboot.
Things SEEMED fine the first 5-10 minutes. Then I did the "swipe from bottom-edge up to start samsung newreader/media"-thingy (the one that shows a wooden chair, with stool that has newspaper and reading glasses on it, overlooking some grassy landscape vista), system froze-shut. After 1-2 minutes I forced reboot with Volume-Down+Power held, since then I'm stuck in some crazy boot-loop that not even Recovery-mode, forced dalvik-cache flushing, nor factory-reset helped.
A] WHY/WHAT happened to getting stuck in this boot-loop
B] how can I remedy that, that doesn't involve sending it in?
my current stock rom image is KOT49H.N9005XXUENA7
I've got the German T-mobile image N9005XXUENA7_N9005DTMENA2_N9005XXUENA2_HOME.tar.md5 from sammobile.com (that's NOT the one that I updated the phone with, the phone got updated via standard OTA updater)
according to a link here on xda-dev ODIN v3.09 is not compatible with the Note 3 LTE+ (SM-N9005) version - which version should I use and where to get it?
KIES v3 doesn't connect to phone
Is there a way to flash the whole ROM again via ADB (recovery mode seem to have an ADB update push feature)
Will flashing the stock Rom trigger the Warranty/eFuse kill-bit 0x1 flag?
thanks-a-thon in advance guys
Click to expand...
Click to collapse
get odin 1.85
jaythenut said:
get odin 1.85
Click to expand...
Click to collapse
thanks for the help
will that trigger the KNOX Warranty eFuse to 0x1 flag-status?
atlana said:
thanks for the help
will that trigger the KNOX Warranty eFuse to 0x1 flag-status?
Click to expand...
Click to collapse
So long as it's Official firmware and not a downgrade attempt it'll be fine :good:
Hey guys, I'm a novice and I am very distressed at the moment. What should I do? Here's my full story:
About 5 months ago (December 23 2013), I bought a Galaxy Note 3 N900W8 Rogers from eBay (No warranty included. Yep not smart). After having received my phone in the mail, I proceeded to root it and install CWM recovery successfully. Until yesterday (May 11 2014), all was going fine till I decided to try and update my phone to Android 4.4.2. I couldn't get updates OTA since it kept telling me my phone was modified. So I plugged my phone to my computer and opened up Kies and apparently Kies was able to fetch an update for my phone. I started updating and came back later seeing that my phone was stuck on the logo screen "Samsung Galaxy NOTE 3" with the "Recovery Booting" in blue in the top left corner. I knew that after I updated my phone would be unrooted and CWM would be gone too so I decided to install those since I wasn't booted into Android yet. After rooting and installing CWM, I restarted several times but it wouldn't boot. I went into Recovery Mode and I did a factory reset and wiped cache. I restarted again but nothing, still stuck on the Logo screen. I am still able to go into download mode and recovery mode. I should have read the cautions of updating since once you update to 4.4.2, there's no going back.
Please help, I don't know what to do at this moment. Thanks in advance!
My phone is also unlocked. I also had a backup but I didn't know the update would format the memory of my phone so I lost everything.
sugoisooshee said:
Hey guys, I'm a novice and I am very distressed at the moment. What should I do? Here's my full story:
About 5 months ago (December 23 2013), I bought a Galaxy Note 3 N900W8 Rogers from eBay (No warranty included. Yep not smart). After having received my phone in the mail, I proceeded to root it and install CWM recovery successfully. Until yesterday (May 11 2014), all was going fine till I decided to try and update my phone to Android 4.4.2. I couldn't get updates OTA since it kept telling me my phone was modified. So I plugged my phone to my computer and opened up Kies and apparently Kies was able to fetch an update for my phone. I started updating and came back later seeing that my phone was stuck on the logo screen "Samsung Galaxy NOTE 3" with the "Recovery Booting" in blue in the top left corner. I knew that after I updated my phone would be unrooted and CWM would be gone too so I decided to install those since I wasn't booted into Android yet. After rooting and installing CWM, I restarted several times but it wouldn't boot. I went into Recovery Mode and I did a factory reset and wiped cache. I restarted again but nothing, still stuck on the Logo screen. I am still able to go into download mode and recovery mode. I should have read the cautions of updating since once you update to 4.4.2, there's no going back.
Please help, I don't know what to do at this moment. Thanks in advance!
My phone is also unlocked. I also had a backup but I didn't know the update would format the memory of my phone so I lost everything.
Click to expand...
Click to collapse
Get the full firmware for your phone and install it with Odin (in download mode). Also read around the main threads on the N900W8.
xclub_101 said:
Get the full firmware for your phone and install it with Odin (in download mode). Also read around the main threads on the N900W8.
Click to expand...
Click to collapse
Thank you so much! It worked when I flashed the 4.4.2 Rex firmware.
Hi everyone, I´m really pissed about that issue; I´d really appreciate any help and thanks in advance to you all.
Story: I was using Sva´s rom for kitkat, everything normal, then I´ve seen Sasikas´s for lollipop and decided to try it out. I flashed the original firmware and then the custom, both via odin, used them normal as usual. For some reason, I decide to compare the new sva´s, also for lollipop and when I tried to flash, THE ISSUE BEGAN!
Issue: after doing the normal odin process, when the message “complete” shows up and the phone reboots, the bar of updating progress stop about 25% and the phone reboot to the normal mode, but only with a black screen. This is the screen I´m talking about: 3w generacionandroid.com/wp-content/uploads/2014/09/Android_updating.jpg
What I already tried and it didn´t work:
1 – factory reset after the “boot”; I think the problem is that the “system isn´t being write” so …
2 – different roms, both custom and stock; something interesting about this is that the point of the bar that resets the phone varies according to the rom I use, just as follow:
Rom lollipop: at 25% of the bar the system restarts;
Rom kitkat: the bar jumps from 25% to the end and boots the system until Samsung logo. I noticed that the carrier logo sound is cutted in the end.
I can freely install any recovery and enter dl mode.
By the way, the bootloader file must be flashed at pda or bl in odin?
Flash the bootloader file in the BL slot.
about the bootloader...
I´ve installed a bootloader to try the new lollipop in sva´s rom, maybe because of this I can´t flash anymore? I´ve found this info about bootloaders, could someone tell me if I´m thinkg right about it?
"In literal terms, bootloader is code that is executed before any Operating System starts to run. "
This way what I need is a bootloader for kitkat or previous? Where can i find it?
cry for help
almost givin up...
so, happy new year to everyone, I´ll wait until January to check any replies, otherwise selling for parts. ='[.
Shortening: I can enter recovery and dl mode BUT not getting to install roms;
I know I fixed selinux permissions once and installed a bootloader said to be to install a version of lollipop, that´s all new stuff I did.
Hi,
To make everything clear i will start from the very begining. I bought my Galaxy S5 2 years ago. It was on android KitKat back then. Everything was stable and it was working like a charm. When android 5.0 Lollipop was available in OTA i let it update. Still everything was ok. And now, about 1 month ago when android 6.0 Marshmallow came out in OTA for my device i also didnt hesitate. Now i regret it as hell. On 6.0 my phone went from stable as a rock to restarting every 5 minutes. I thought maybe its battery fault so i changed it but unfortunately it didnt change much. I blamed 6.0 for all this thing so i decided to downgrade it to 5.0 Lollipop. I did it thanks to youtube tutorial by android doctor - Samsung Galaxy S5 Downgrade Android 6.0 G900F Marshmallow To 5.0 Lollipop ( i was using ODIN and i flashed XEO rom for my SM-G900F from sammobile website).
For like 3 weeks everything went back to normal but one day i couldnt turn WiFi on my phone (when i pressed the WiFi symbol nothing was changing, when in settings i tried to slide it to ON position it went back to OFF. I thought ok lets reboot the phone then. I did it but from that moment my phone is as useless as a brick. It turns on, shows Samsung Galaxy s5 logo and immediately restarts. I cant even enter recovery mode. I can enter download mode so i tied to flash another rom (6.0) but it didnt work. Phone was still restarting in the same moment. I even tried to install TWRP but cant enter it also.
I had my own small company but it went bankrupt and i have huge debts which i will be paying for next 10 years so i really dont have any money to spend. I live without the phone right now. My life is a misery. Can you guys please help me to unbrick my phone? I will be very grateful and you propably cant imagine how much it will cheer me up to have it working again.
Sorry for such a long post and useless informations about my life but i had to let it all out.
I'd try going back to stock kitkat with odin (install the firmware from sammobile)
im not sure if you can go back to kitkat via odin once youve gone to lollipop, nor am i sure why anyone would. Just get the OK4 tar.md5 from either sammobile.com (very slow servers) or from here (much faster) and flash it in odin. should be god to go. then you can root, flash twrp and youre ready to ROM
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!