I have just received a s4 with a really confusing problem . When you power the phone on normally it displays a weird semi solid green screen but when you boot into download mode everything displays perfectly. Also while phone is off if you connect charger it displays the battery icon perfectly. Phone is 100% stock dont know what rom/baseband version was installed. Green screen also in recovery mode. Phone does not have usb debugging enabled nor is it rooted. Can anyone help?
Download Mode says
ODIN MODE
PRODUCT NAME SCH-I545
CURRENT BINARY Samsung Official
SYSTEM STATUS Official
KNOX KERNEL LOCK 0x0
KNOX WARRANTY VOID 0x0
CSB-CONFIG-LSB 0x30
WRITE PROTECTION Enable
eMMC BURST MODE enabled
If you're able to get into download mode, download the latest stock firmware and install it to see if that corrects the problem. There should be a link for the stock firmware in the Verizon Galaxy S4 forums, along with other aids that may be of use to you. Installing the firmware is a must, because it will either correct the problem you're having, or it will reveal the problem to be deeper, and likely hardware related.
In the unlikely event that the stock firmware is not available on the forums, you can get a copy from either sammobile.com or samsung-updates.com.
I dont know what version was previously installed I tried flashing twrp via odin it comes back as failed because of a auth error. I think the bootloader may be locked if it isnt I dont want to upgrade only to learn bootloader was previously unlocked and I just locked it up by updating. It seems to me if this is a hardware related problem I would think the phone would be green screen in download mode and while charger plugged in? Any suggestions on which android version to try first?
You clearly didn't read my previous post. That pisses me off, because now I'm having to repeat myself when I should NEVER have to.
If you want to brick the S4, then continue doing what you were doing. Otherwise, pay attention, because at no point did I ever mention downloading and installing TWRP. I did however mention downloading and installing the STOCK Verizon S4 ROM from the Verizon S4 forums. You will use Odin to install the ROM. If the Verizon S4 forums do not have a link to the stock Verizon S4 ROM, you are to download the latest copy of the ROM from either sammobile.com or samsung-updates.com. It doesn't matter one whit what was on there before, because by installing the stock ROM you were supposed to have downloaded, you will have the S4 at a known starting point so you can truly diagnose the problems it may have.
AT&T and Verizon bootloaders are locked, thus you cannot just install a recovery and expect it to work. Installing a stock ROM however will work since all the components are verified by Verizon. In installing the stock Verizon S4 ROM through Odin, you will make sure you are using a proper cable, do not have the S4 connected through a hub, will make sure the Samsung USB drivers are installed (available at Samsung's website), and either do not have Kies installed, or have Kies disabled.
Sorry I have flashed the latest official verizon firmware and odin said pass, everything went perfect. Phone restarted and again hazy green screen returned. Still cannot veiw anything in recovery or normal mode, safe mode does not help either. Download mode and battery charging still show up perfectly fine. Any help would be greatly appriciated.
It's hard to think of this as a hardware issue, but I believe you have one. As strange as it may seem, the issue is not with the screen itself, but the GPU.
Using Windows equivalents, Download Mode is "Safe Mode with Command Prompt" while Safe Mode is just like Windows' "Safe Mode". "Safe Mode with Command Prompt" dumps you to the command line, i.e. DOS. It doesn't need a GUI so it doesn't have drivers loaded to support it. "Safe Mode" has a GUI so it has to load drivers to support that.
On the S4 the concept is similar, only the drivers are called "libraries". Download mode doesn't use a GUI as it's part of the bootloader, so it doesn't need the GPU, thus it doesn't need the GPU library. This is why download mode functions. The other modes all have a GUI, which requires the GPU and a library for the GPU loaded. Since the GPU has failed you get the green screen instead of what you should see. The library itself isn't the culprit because if it were, loading a new ROM as you had would have fixed the problem. The screen isn't the culprit because the screen works correctly in download mode. If it were the screen, the green would appear in Download Mode as well as the other modes. Therefore the GPU is most likely the problem.
Unfortunately, that means a new motherboard, on top of trying to remove the glass for replacement.
PROBLEM ALMOST FIXED!!.. Well kind of, i seperated the broken glass from the screen and placed the phone in the freezer. An hour or so later i pulled the phone back out of the freezer and switched it on everything worked perfect i switched on usb debugging and rooted the phone using towelroot and safestrapped it. when i updated supersu i had to reboot the phone and then again green screen i also noticed the phone had gotten really hot. I tried the freezer trick again and the phone turned on like normal no green screen. Does anyone know what maybe causing this issue???
Thank you very much for all the help and info you have given me i really do appriciate it
Bad GPU, as previously stated, though there are two other possibilities I can think of. The first is that GPU has a bad connection to the motherboard that manifests when heated. Or else the motherboard has a stress fracture that manifests when heated. The latter has happened with other devices but is not common. A solder reflow of the GPU could cure the former problem.
Before I give the reflow a shot I wanted to mention another piece to this puzzle. When the phone is working fine as long as the screens backlight is on the phone will display everything correctly as soon as it turns off and you turn it back on green screen. It doesn't matter if you wait two minutes or 20 minutes. Dont know if thathelps narrow down culprit
It doesn't narrow things down any.
the solution
you need to change your battery than you install the firmware using odin than you download antivirus. :good:
Related
The main Samsung Approved Service Center here in Kenya has just given up on my SGS 1900 UK Model Nov 2010, originally 2.1 firmware upgrade via KIES to Froyo 2.21 in March 2011. They have handed it back unfixed after a week. Cant find a problem like this on any forum/google. Can find one that is fixable with the resistor jig, but Samsung dealer says his jigs don't help:
1) Press power, on comes B&W Samsung GT I900 screen, then the mosaic graphic that resolves to the glowing big "S". Then it buzzes feebly. Eventually it goes black but keeps buzzing now and then. Power off works.
If you poke around trying to get it into 3 touch reset, the Menu and Back keys light up and stay lit.
2) 3 Touch reset will not work. Dunno if it ever did as never tried before.
3) Plug into USB charger, it charges fine and shows the charger icon.
4) Plug into KIES and after a lot of attempts, KIES identifies it + firmware and connects. I can see and save my contacts and it displays CONTACTS, INTERNAL SD and CALENDAR folders in KIES. No more
5) ODIN ( which I dunno how 2 use but have) sees the SGS's COM when I plug it to my comp.
6) The dealer claims to have tried to resart/reflash with Samsung jigs. He has handed it back with a "cant fix".
What the heck is going on here? Looks like I have lost a few hundred bucks and have to throw it away.
When did this start? Phone was working perfectly. Suddenly a solid red icon with large white star labelled "Web Page" appeared on home page but no such App was found in SETTINGS>ETC. In any case, "Web Page" just led me to a totally innocuous page I use all the time as a homepage on INTERNET app. A few starts and shutdowns after that ( the battery was getting low so swx'd on and off like 3 times over an hour), it just went into (1) above.
Phone is STOCK, no mods, no reflashes,no rooting etc
Thanks
Peter in Darkest Africa
if odin can 'see' you handset, have you tried flashing the ROM again? find a stock froyo rom from one of the threads here in the general section (click here) or download from samfirmware.com .
Once you have the rom files, kill all the KIES tasks using the task-manager in windows. Get your phone into download mode by pressing volume down+menu button+power button until you get the yellow screen showing the android working. then open odin 1.7 and connect your handset. once odin connects, click on the buttons for PDA,PHONE and CSC in odin and browse to the appropraite file which you've download in the rom. also click on the PIT button, browse to the odin folder and select the 512.pit file. Once this is done, check the main odin window to make sure the check-box next to 're-partition' is checked. click start and it should flash the new firmware for you.
Disclaimer: I do not take responsibility for any harm that may come to your phone during the flashing process. The instuctions above are accurate but are to be performed at your own risk.
flash Darky Rom 10.1 with JVO Modem . Best GPS i´ve ever had, and my GPS was really bad.
frostygenius said:
if odin can 'see' you handset, have you tried flashing the ROM again? find a stock froyo rom from one of the threads here in the general section (click here) or download from samfirmware.com .
Once you have the rom files, kill all the KIES tasks using the task-manager in windows. then open odin and connect your handset. once odin connects, click on the buttons for PDA,PHONE and CSC in odin and browse to the appropraite file which you've download in the rom. also click on the PIT button, browse to the odin folder and select the 512.pit file. Once this is done, check the main odin window to make sure the check-box next to 're-partition' is checked. click start and it should flash the new firmware for you.
Disclaimer: I do not take responsibility for any harm that may come to your phone during the flashing process. The instuctions above are accurate but are to be performed at your own risk.
Click to expand...
Click to collapse
@frostygenius
I don´t think that your instrunctions ARE accuarate. You don´t even mention that he has to be in Download mode if he wants to use Odin. Also you advise to connect phone right after opening Odin and than insert the files, but some versions of Odin are known that they malfunctioning if you do this in this order, You should first insert files and set odin and after that plug in your phone.
And if he claims that he is on stock since bought the phone, so maybe he never used it before.
@peterg123
I´m not exactly following what happens to your phone. If I understand correctly the Samsung released defective ROM via KIES and after a week turn it down? But you already updated and now your phone is broken? If yes, I think that Samsung service center should repair your phone or if its serious damage than even replace it.
Is the phone able to boot-up and work properly? Is your recovery mode and/or download mode working? If the download mode (use 3-button combo - VolDown+Home+Power) is working then you can try recover on your own, but be careful, dont do anything before you are sure that you know what you are doing. You can go through this post before start [HOWTO] [REF] [FAQ] [Guides] [Tutorials] Flash/Root/ADB/ROM [MUST READ!].
Also go through the forum or samfirmware.com and find your official version of rom (Eclair 2.1) to be sure that you can anytime revert to this one because of warranty.
EDIT: Also can you please post some photos or video showing what happens to your phone?
Ok, I dunno if this is gonna help but I had a very similar issue when I first got my phone, within a week of owning it.
Points 1-3, exactly what happened mine.
Points 4 & 5 I didn't try, (was fairly new to Android)
Left it in to my local Vodafone shop & within 5 days I had it back in perfect working order, the maintenance report stated faulty hardware, the display module had to be replaced. Maybe worth mentioning to the service guy?
R34L2Pac said:
@frostygenius
I don´t think that your instrunctions ARE accuarate. You don´t even mention that he has to be in Download mode if he wants to use Odin. Also you advise to connect phone right after opening Odin and than insert the files, but some versions of Odin are known that they malfunctioning if you do this in this order, You should first insert files and set odin and after that plug in your phone.
And if he claims that he is on stock since bought the phone, so maybe he never used it before.
@peterg123
I´m not exactly following what happens to your phone. If I understand correctly the Samsung released defective ROM via KIES and after a week turn it down? But you already updated and now your phone is broken? If yes, I think that Samsung service center should repair your phone or if its serious damage than even replace it.
Is the phone able to boot-up and work properly? Is your recovery mode and/or download mode working? If the download mode (use 3-button combo - VolDown+Home+Power) is working then you can try recover on your own, but be careful, dont do anything before you are sure that you know what you are doing. You can go through this post before start [HOWTO] [REF] [FAQ] [Guides] [Tutorials] Flash/Root/ADB/ROM [MUST READ!].
Also go through the forum or samfirmware.com and find your official version of rom (Eclair 2.1) to be sure that you can anytime revert to this one because of warranty.
EDIT: Also can you please post some photos or video showing what happens to your phone?
Click to expand...
Click to collapse
Thanks for the heads-up I forgot to mention those points. I've updated my original post.
Sent from my GT-I9000 using Tapatalk
Thanks, it is not possible to get into download mode, or I would have done all that. As explained, the phone will not go past the giant "S" logo ( 3rd screen after power on). This problem has happened to many people, worldwide.
As explained the three button default firmware does not work.
The Samsung repair agent claims to have used the 301k resistor method to restart the phone and even that failed. I am not sure if this is true but he said so.. not sure because everybody reports success with this.
ODIN, as I said ( 1.8) recognises the COM connection just as does KIES. The problem is, I am not in download mode so can't reflash if I tried.
I have used the phone for 10 weeks since firmware upgrade from 2.1 to 2.2 during which I had no problems except the occasional process stopped errors.
Hope this help, thanks for trying for me
Yes you are correct, I can't get download mode. The phone has never been reflashed or messed with. It came with 2.1 and using KIES in March I reflashed to 2.2 and it worked perfectly for 10 weeks until it semi-bricked.
There is the Black Screen of eath...then there is the pulsasing S screen of limbo! That's what I have.
The only harwdare clue I have is the SGS blew the fuse in my car charger shortly before "expiring"...yet if connected to USB or other charger, it charges the battery and displays the logo.
peterg123 said:
Thanks, it is not possible to get into download mode, or I would have done all that. As explained, the phone will not go past the giant "S" logo ( 3rd screen after power on). This problem has happened to many people, worldwide.
As explained the three button default firmware does not work.
The Samsung repair agent claims to have used the 301k resistor method to restart the phone and even that failed. I am not sure if this is true but he said so.. not sure because everybody reports success with this.
ODIN, as I said ( 1.8) recognises the COM connection just as does KIES. The problem is, I am not in download mode so can't reflash if I tried.
I have used the phone for 10 weeks since firmware upgrade from 2.1 to 2.2 during which I had no problems except the occasional process stopped errors.
Hope this help, thanks for trying for me
Click to expand...
Click to collapse
..But download mode doesn't display the S logo or even the first Galaxy S 1900 logo...it goes straight in.
Try looking up in the Development section - I'm sure there is a jig method in there and it might be worth trying yourself, you've not got mush to lose now.
If you can get into download mode eventually, search for and flash Ezbase, that will get you onto a rooted firmware and it works EVERY single time for me. Good luck.
@R34L2Pac
Hi, thanks. As posted, the stock UK model SGS 1900 with 2.1 Eclair worked perfect from Nov to March 2011, was firmware upodated by KIES in March 2011 to 2.2.1 Froyo and worked like a dream until it went "semi-bricked" with the "Logo of Limbo" screen ( the pulsating giant S) for no reason.
A week before this, I changed SIMs when I changed countries and for some reason lost all added apps. I had to re-install them and even then, sometimes twice as I got many "android process stopped" errors --- even on some of the Sansung installed ones like Layar. That is the only problem I ever had.
The phone has only had apps from Market and never been modded whatsoever. Many thanks
Hi,
You said that you can see a pulsating S logo, sound to me like your phone is bootlooping. But you didnt mention if you can get at least to recovery(VolUp+Home+Power)? If you can get into recovery, you could try just factory reset your phone from recovery and reboot your system.
Also in the development forum you can find some kernels which can be flashed via recovery (like speedmod K13 for Froyo), so you can try to flash this kernel and after reboot into CWM recovery you could try to connect phone to ADB and type the command "adb reboot download".
I read on the forum that the home-made jig method worked for everyone, so looks like the samsung technician was doing something wrong. It is worth trying to made one a see what it does. Also found this thread, where user cuperus claims that even with charger can be simulated the jig by heating-up your device. So you can also try it, just plug your phone to a charger, let it charge for 1hour and than try use 3-button combo to go to download mode.
R34L2Pac said:
Hi,
You said that you can see a pulsating S logo, sound to me like your phone is bootlooping. But you didnt mention if you can get at least to recovery(VolUp+Home+Power)? If you can get into recovery, you could try just factory reset your phone from recovery and reboot your system.
Also in the development forum you can find some kernels which can be flashed via recovery (like speedmod K13 for Froyo), so you can try to flash this kernel and after reboot into CWM recovery you could try to connect phone to ADB and type the command "adb reboot download".
I read on the forum that the home-made jig method worked for everyone, so looks like the samsung technician was doing something wrong. It is worth trying to made one a see what it does. Also found this thread, where user cuperus claims that even with charger can be simulated the jig by heating-up your device. So you can also try it, just plug your phone to a charger, let it charge for 1hour and than try use 3-button combo to go to download mode.
Click to expand...
Click to collapse
Sorry I should have mentioned that it will not get into 3 button recovery mode, that has zero effect or rather, just sends it to the "Logo of Limbo" ( pulsating "S") just as does the power button.
Will maybe try a long charge time and see if that helps! Many thanks
Try en carefully learn hw to use odin coz I gt tha same exact model. I hav flashed mine many tyms en am on 2.3.4 XXJVP. if u do gt into download mode odin will sort u. Regards frm K.poly.
Sent from my GT-I9000 using XDA Premium App
peterg123 said:
Sorry I should have mentioned that it will not get into 3 button recovery mode, that has zero effect or rather, just sends it to the "Logo of Limbo" ( pulsating "S") just as does the power button.
Will maybe try a long charge time and see if that helps! Many thanks
Click to expand...
Click to collapse
how long have you tried holding down the 'volume down+menu+power' keys? a simple quick press of the three buttons does not work. you have to keep holding them all down for a bit (sometimes upto to 15-20 seconds) for it to go into download mode.
Sorry for the fast answer but I'm at work atm... I think he needs to do the 3 combo button fix on his phone first. I know it's on the forum somewhere... Can anyone check it for him? I lost the 3 combo the first time I updated with Keys from 2.1 to 2.2 and I had to fix it using a program that I can't remember to go on download mode and apply that fix.
Then he can use Odin to flash a stock rom as he needs, plus having 3 combo fixed!
Good luck mate!
Sent from my GT-I9000 using XDA App
Possible fix for your problem
Hi peterg,
I was looking through the general forum and found this post, where user beamzuk1 describes method how he fixed his semibricked phone. Symptoms are the same (not booting, glowing soft-keys, vibrating, no recovery and no download mode). So he used 'adb reboot recovery', I would say that proper command is 'adb reboot download', but you can try both. Also go through guide HOWTO use ADB, which I posted here the link in earlier post.
Hope this will help.
PS: Try follow beamzuk1 step-by-step, because if you start phone earlier than you connect it to pc, adb might not recognize the phone. Also be sure that you have correctly installed drivers and android-sdk before you try this.
These phones come with a 2 year warranty. Why don't you contact Samsung directly yourself - telling them that the local repair centre wouldn't fix/replace it for you. If you did nothing besides what you described, then I would have thought you were entitled to have it fixed or replaced by Samsung.
LiverpoolFCfan said:
These phones come with a 2 year warranty. Why don't you contact Samsung directly yourself - telling them that the local repair centre wouldn't fix/replace it for you. If you did nothing besides what you described, then I would have thought you were entitled to have it fixed or replaced by Samsung.
Click to expand...
Click to collapse
+1
Also think that Samsung should repair it or replace it.
The fact your repair center has done nothing to fix your phone, in several occasions, now entitles you to brand new replacement or your money refunded in full, contract terminated and expenses paid for your losses incurred as a result of their negligence.
Why not hit them up for the SGS 2.
I had the same issue with my first Galaxy S...wifi stopped working at first, I turned it off then on again but nothing changed. So I rebooted to see if it would correct itself. Bootloops and no 3 button combo (download or recovery)
Sent it off to Samsung through the Carphone Warehouse in the UK. I'd contact a Samsung Service Centre directly if I were you.
I rooted my galaxy s7 edge (snapdragon) and everything was fine and working except I couldn't get SuperSU to install properly. I would get the app screen, but nothing else. A couple of apps would show up (Root Checker, Flashfire) after I had run them but I didn't get the typical SU screen with settings. I'm not including the softwares used (I did have debugging enabled in Develper options on the phone, secure boot unchecked, and the correct Samsung USB drivers installed) because I don't think it's relevant to my question - if not so, let me know and i'll be glad to provide the info - I'm a newbie at this so please bear with me). I read about the warning to not update the 2.74 version of SuperSU but then I saw the update beta for 2.77 so I tried that. It appeared to run ok; I could see all the commands being executed and then ending and then the phone rebooted, as it's suppose to do. This is when the problem emerged; a screen came up saying "start up failed" and at the top left of the screen it said 'Custom binary blocked by secure boot (boot.img). I rebooted to TWRP recovery mode and tried rebooting which again resulted in the start up failure screen. I then tried the wipe data\factory reset setting and the same thing happened. I then booted to maintenance mode and got the warning screen about a custom OS installation can cause problems but if you want to proceed press volume up key which I did and got the usual Downloading page. At the top of the Downloading page I noted it said, among other identifying info: Odin mode (high speed), FRP lock: off, QUALCOMM Secure Boot: enable, and Secure Download: enable.
But, when connecting the usb cable to the phone and pc, my computer (Win 10) doesn't even see it. Not sees and doesn't recognize, but doesn't even see it. I tried a second USB cable and different ports but got the same results. I tried a second computer and got the same thing.
I am guessing that if I could still access the phone to run rooting apps I could get past the lock. If not now, maybe later on when someone figures our a way to do so. But without a working connection to the phone I am helpless. I am wondering if Verizon disables USB intentionally, so that the phone essentially becomes useless. Or, is it a coincidence and perhaps there is something wrong with the usb hardware.
Is there a way out of this other than having to pay for it to be fixed (which Samsung won't do - I called - and maybe Verizon not either).
Thanks in advance -
j-brah
Hi all !
I have a Samsung A8 (model SM-A800F) which was working great. I ran Kingo Root to try to install Youtube ad free. The next time I restarted it, it didn't load, and restarted in an endless loop to where "Samsung" logo appears (then restarted again). I booted into System Recovery and chose to reset to factory, but it didn't help. Then I tried flash it using Odin in Download mode. I installed the Windows drivers, downloaded the 6.0.1 firmware for Vietnam (where it was purchased), loaded the file into the AP field, and once verified clicked Start. The progress was frozen when reaching mid-way every time I tried, until it said "an error occured while updating the device software. Use the Emergency recovery function in the Smart Switch PC software"...
I downloaded Smart Switch and installed in Windows, but the drivers were not able to install correctly, and failed on the component referring to the ID or something... while Modem driver was installed correctly and the phone appeared in Device Manager. Smart Switch didn't recognize my phone and said "unsupported device".
Now I cannot get the phone stay constantly ON, and the screen shuts down and loads in an endless loop, to the "Error occured" screen... When trying to boot to the ODIN Download page, it loads, I press UP for Continue, and then it again shuts down and loads to "Error Occured".
I tried to charge over night but it didn't help. It does the same thing when the phone is connected to the charger...
However it seems that by IMEI it is sill under warranty. I'm not sure if I voided it :/
Here's what the Download mode page says:
ODIN MODE
PRODUCT NAME: SM-A800F
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
FAP LOCK: ON
Secure Download: Enabled
KNOX WARRANTY VOID: 0
AP_SWREV: 1
Would appreciate any help, this phone is almost new but now it's dead :/
Your warranty is not voided. Your Knox E-Fuse still intact.
Also this is for S8 not A8 forums.
Paradoxxx said:
Your warranty is not voided. Your Knox E-Fuse still intact.
Also this is for S8 not A8 forums.
Click to expand...
Click to collapse
Thanks,
I just couldn't find any A8 forum, and thought there would be more people here who can help.
Would appreciate any help on this... thanks in advance
wurlitzer99 said:
Thanks,
I just couldn't find any A8 forum, and thought there would be more people here who can help.
Would appreciate any help on this... thanks in advance
Click to expand...
Click to collapse
No worries, your phone is not dead.
Try to find a firmware that correspond to the one you got :
http://updato.com/firmware-archive-select-model?exact=1&q=SM-A800F
and use ODIN : http://dl.sammobile.com/Odin3-v3.12.7.zip
You should be good to go.
EDIT : Also for that error occurred thing, try to be faster than it by starting odin flash before it appears.
Thanks,
The problem is that neither the error nor the Odin page would stay on for more than a few seconds. Once they appear, the screen would go dark after 5-10 seconds and then the "error" page would load again (after being darks for another 10 seconds or so). So I can never have ODIN or Smart Switch connecting to the device (the drivers won't connect in Windows)... making it impossible to upload any firmware.
wurlitzer99 said:
Thanks,
The problem is that neither the error nor the Odin page would stay on for more than a few seconds. Once they appear, the screen would go dark after 5-10 seconds and then the "error" page would load again (after being darks for another 10 seconds or so). So I can never have ODIN or Smart Switch connecting to the device (the drivers won't connect in Windows)... making it impossible to upload any firmware.
Click to expand...
Click to collapse
Could you take a picture of that error ? I've never heard/seen such thing
Hi, thanks for the help !
The error is this:
http://statics1.grupoandroid.com/up...1850.jpg.d2bb2a8b77e4fba5fc6467f3d1547886.jpg
I *think* I have some direction... here's what I did/found:
- I installed Smart Switch on my Mac, and chose "Reinstall Device Driver" from the menu. Then restarted the MAC
- I loaded Smart Switch, and Chose "Emergency Software Recovery and Initialization". Then chose the "Device Initialization" tab
- Added the model number "SM-A800F" and the device's serial number (which are physically written on my device).
Smart Switch determined the firmware version to be used for initialization, as:
PDA:QC3 / PHONEG3 / CSCH4(XXV)
- Smart Switch asked to:
1. Power the device down
2. Load recovery mode by pushing Power+Vol Down+Home, then connect the device to the MAC and choose "Continue" to start the initialization...
The problem/s:
My device won't turn on at all, if I do not connect it to either the charger or the MAC (which acts as a supply source?) - which makes me think the battery is fully drained ? i.e when not connected at all, it won't power on.
But when connected to either the charger or MAC, it would bootloop endlessly. i.e it will load the "error" page mentioned above, shut down itself, reload again, shut down and so on.
(I have to mention, that when I first noticed the bootloop, I reset everything to factory settings, cleared cache etc, and it still bootlooped on the Samsung logo).
If when it shuts down during the loop, I push Power+Vol Down+Home, it would boot to ODIN recovery page, where I can push UP for the Download page, but it will still reboot and will again load into the "error" page, which will again reboot endlessly. If I take the charger off the device, it powers off and won't load with any combination of button push.
I also cannot just make it shut down when the charger is connected, using any of the possible button combinations...
I wonder:
- Is there there's a problem which prevents the battery from being charged at all ?
What's strange is that the original problem which made me get into this whole issue, was that is was endlessly booting to the "samsung" logo - but when I booted to System Recovery or Download/ODIN modes, it stopped rebooting endlessly and stayed on... it was also showing the charging indication when powered off... the battery was charging well ever since.
- Why would it bootloop when connected to the charger ? is it possible that the bootloader went bad during my attept to install firmware using ODIN ? I know it always went through the boot.img and recovery.img successfully and only got stuck at about 50% when installing system.img...
I think the current bootloop problem began only once the battery ran out of power. But why wouldn't it charge at all now ??? It's supposed to still charge in this state, isn't it ?
wurlitzer99 said:
Hi, thanks for the help !
The error is this:
http://statics1.grupoandroid.com/up...1850.jpg.d2bb2a8b77e4fba5fc6467f3d1547886.jpg
I *think* I have some direction... here's what I did/found:
- I installed Smart Switch on my Mac, and chose "Reinstall Device Driver" from the menu. Then restarted the MAC
- I loaded Smart Switch, and Chose "Emergency Software Recovery and Initialization". Then chose the "Device Initialization" tab
- Added the model number "SM-A800F" and the device's serial number (which are physically written on my device).
Smart Switch determined the firmware version to be used for initialization, as:
PDA:QC3 / PHONEG3 / CSCH4(XXV)
- Smart Switch asked to:
1. Power the device down
2. Load recovery mode by pushing Power+Vol Down+Home, then connect the device to the MAC and choose "Continue" to start the initialization...
The problem/s:
My device won't turn on at all, if I do not connect it to either the charger or the MAC (which acts as a supply source?) - which makes me think the battery is fully drained ? i.e when not connected at all, it won't power on.
But when connected to either the charger or MAC, it would bootloop endlessly. i.e it will load the "error" page mentioned above, shut down itself, reload again, shut down and so on.
(I have to mention, that when I first noticed the bootloop, I reset everything to factory settings, cleared cache etc, and it still bootlooped on the Samsung logo).
If when it shuts down during the loop, I push Power+Vol Down+Home, it would boot to ODIN recovery page, where I can push UP for the Download page, but it will still reboot and will again load into the "error" page, which will again reboot endlessly. If I take the charger off the device, it powers off and won't load with any combination of button push.
I also cannot just make it shut down when the charger is connected, using any of the possible button combinations...
I wonder:
- Is there there's a problem which prevents the battery from being charged at all ?
What's strange is that the original problem which made me get into this whole issue, was that is was endlessly booting to the "samsung" logo - but when I booted to System Recovery or Download/ODIN modes, it stopped rebooting endlessly and stayed on... it was also showing the charging indication when powered off... the battery was charging well ever since.
- Why would it bootloop when connected to the charger ? is it possible that the bootloader went bad during my attept to install firmware using ODIN ? I know it always went through the boot.img and recovery.img successfully and only got stuck at about 50% when installing system.img...
I think the current bootloop problem began only once the battery ran out of power. But why wouldn't it charge at all now ??? It's supposed to still charge in this state, isn't it ?
Click to expand...
Click to collapse
Hmmm, the thing is, the battery charging process is actually held on some kind of "mini-boot" OS on Samsung I believe, where the phone boots into a certain state, with that said mini-os to display the battery charging info and this kind of things.
My guess is that you *might* have, or more likely your phone did corrupt the flash at some point for x or y reason.
What I'd do is :
Let the phone on a charger a whole night doing its bootlooping thing. And see from there if the battery would charge.
I'd try another computer with Odin just to be sure something is not triggering the reboot process at some point.
And if all the above fails, you still have the warranty, so beside time, you would not be losing any money..
I'm going to write a long post. But I believe it will help a lot of people having a similar problem.
Long story short - problem solved! but it took much of my nerves (and time).
I'll start with the "warranty". The so-called Samsung "warranty" which basically worths nothing!
Calling Samsung international service center, they "informed" me that I must contact Samsung Vietnam, where I bought the device, although I am not there anymore... Needless to say the local dealer in my country refused to take care of this situation, saying Samsung's warranty is regional based, rather than international... which means, only Samsung in the original country where the device was sold in, are responsible for the warranty (and therefore repair!). I had a chat with a Samsung Vietnam representative, who just kept saying "I'm sorry", and refused to let me sent the device out to them for repair! asking me to "bring it to them", although I noted him a few times that I bought it as a tourist and I am not in Vietnam anymore.... Thank you Samsung !! From now on every traveler in the world will know they basically have NO WARRANTY if they buy any Samsung device in a "foreign" country while traveling abroad!
Now for the solution:
I started by letting the device staying connected to the charger overnight, which didn't help. With the OS now installed, I realize that the battery was NOT CHARGED ! it was completely drained, although connected to a charger for long hours... So, know from now on that if your boot data is corrupted, it may cause the device NOT TO CHARGE THE BATTERY at all. Luckily, my desktop PC could use the device while connected to it although the battery was empty, until the problem was sorted out. I did get a crash on my MAC tough (Log said it was USB related), while using Smart Switch, so one option is that it could not supply enough power to the device to keep it keep working at all, or working correctly... So my suggestion is to use a desktop Windows PC in this case, which can potentially provide more power to a device with 0% battery power.
After scratching my head, and considering removing the front panel for replacing the battery (a very risky procedure) I decided to keep on investigating....
I followed a youtube video who suggests that you should install Smart Switch on a PC, choose "reinstall driver" from the menu, restart the PC, then use Emergency Recovery and Initialization, enter the phone model number in the search box (as appearing on the back of the device) , and once it recognizes the model, also to enter its serial number. Here's the video:
https://www.youtube.com/watch?v=1yXQUFrEWg4
This basically brings up a popup message saying Smart Switch detects a compatible firmware for this device, and is about to download and install it. It then asks the user to do the Power+Vol Up+Home push combination trick + pushing UP once the page is loaded in order to "Continue" and bring up the ODIN Download screen, which worked for me if did that as soon as the device shuts down (in the middle of the bootloop). As I couldn't make it load at all with no charger connected, I had it connected to the charger, and once I saw the Smart Switch message asking to do the push combination, I quickly connected it to the computer using another cable which was already connected to the PC USB port on its other end.
Somehow, I could at last make Smart Switch finally start downloading the firmware from the web, and the device again disconnected (bootlooped), but luckily Smart Switch didn't care about it disconnecting, and kept on downloading the firmware. At about 85% of the progress bar state, I could find the downloaded firmware on the temp folders, which are described in this thread:
http://forum.gsmhosting.com/vbb/f777/samsung-firmware-download-belongs-his-serial-number-2038404/
I had to make sure it wasn't still downloading, and watched the "last modified" state of the file to make sure they are not being downloaded anymore. CAUTION: although the AP was not downloading anymore, I know it was probably not good as ODIN couldn't verify it when I tested it. USE ONLY SMART SWITCH !
I quickly copied the folder to which the app extracted the BL and AP files it downloaded, and finally had an officialy bootloader (BL) image, which I could use in ODIN in order to reupload a correct, "official" bootloader to the device....
I hoped the device won't bootloop in the middle, but luckily ODIN was fast enough to send the image successfully, with a "PASSED" status, and the device booted with a nice "Samsung" logo directly to a System Recovery page!
What I exactly did, was loading ODIN, then loading ONLY the BL file into the BL field in ODIN, having it verifying it, and once verified I connected the device, and as soon as ODIN recognized it, pushed START. It managed to upload the image into the device in a few seconds! It seems then, that the bootloop was not caused by a bad battery, but as a result of a corrupt upload of an AP image through ODIN - or because I possibly was using an incorrect version when I tried to upload an AP files to the device on my first attempt to flash it.
Note that I did search for the correct, compatible AP file, by country and model (on Sammobile) but it didn't' work (stuck at 50% in ODIN) ! so I really suggest everyone TO ONLY USE SMART SWITCH if they want to be sure that the correct firmware is being used, and avoid similar situations...
I then deleted the temp files from the PC (the actual ones which were in the temp folder), reinstalled the drivers from inside Smart Switch (just in case), booted the device to Download mode (WHICH DIDN'T BOOTLOOP this time), let Windows installing the drivers (checked in Device Manager), then restarted the PC, and ran Smart Switch again. I repeated the procedure of loading Emergency and Initialization, entering the model and serial number, having it fully downloading the firmware (again) from the web, and installing the firmware into the device. This time it completed the process, and I finally had the device installing and booting into a fresh version 6.0.1 of Android!
Hope it helps!
Hi, I'm using a Galaxy Tab A 10.1 with Spen (SM-P580) (gtanotexlwifi)
I was using a custom rom (SamBones) with TRWP installed, and I was messing around in the developer options trying to get a usb device to work, and ended up toggling developer options and rebooting. I think the issue is that after I toggled developer options, I forgot to re-enable OEM Unlock. Once the device rebooted, I was met with something along the lines of "device blocked by frp lock" or something like that. I've been looking online trying to find a fix but I can't figure out what I'm supposed to do. I was going to try flashing the stock recovery but I can't seem to find it anywhere for the SM-P580.
Any help would be appreciated...
I honestly don't know what to do at this point and the device is completely useless... I can't find the original firmware/system stuff to flash with odin... and I can't boot into twrp at all...
If someone could link me to the right original stock firmware I can flash with odin or something maybe that will work? I can get into download mode but I can't re-flash twrp or do anything other than stare at a bootloop or get into download mode. This is driving me crazy and I'm scared my device is gone for good!
It's so stupid that this can even happen in the first place. I've been using the rom and twrp without issue from the day I bought it a few weeks ago, and now because of one small mistake in settings, the entire device is completely soft bricked and I can't even find the right firmware to flash to it to fix it.... why samsung, why...
I was looking at the firmwares available on sammobile, but the US isn't listed for countries so I don't know which one I should download if any....
I've been freaking out in a panic for the last two hours or so. I'm fine with installing stock everything and then just redoing all of the custom recovery/system flashing afterwards, data loss isn't too big of a deal to me as I've had to wipe it a few times over the last week while fixing/doing stuff. I'm worried my nearly $300 device is going to just become a brick which is unthinkable. I love this tablet and use it for so much.
Please help
donwload tool (for faster firmware download)
download firmware https://www.sammobile.com/firmwares/galaxy-tab-a-with-s-pen/SM-P580/
and flash via odin.
(you can install any firmware no matter what country i think )
Rawwrius01 said:
(you can install any firmware no matter what country i think )
Click to expand...
Click to collapse
Are you sure? It seems weird that they would have different versions for different countries if there wasn't a difference.... I'm just worried I'm going to break something if I don't install the right firmware...
Edit: I found the "USA" version on other sites but their download times are saying things like 16 hours. Though I think Cellular South (XAR) is the USA version on sammobile as the same firmware shows up as USA (XAR) on the other two sites. Going to download it and hope it works, but just putting this here in-case someone else is in the same boat...
Sceleratis said:
Are you sure? It seems weird that they would have different versions for different countries if there wasn't a difference.... I'm just worried I'm going to break something if I don't install the right firmware...
Edit: I found the "USA" version on other sites but their download times are saying things like 16 hours. Though I think Cellular South (XAR) is the USA version on sammobile as the same firmware shows up as USA (XAR) on the other two sites. Going to download it and hope it works, but just putting this here in-case someone else is in the same boat...
Click to expand...
Click to collapse
you can use the tool i posted (samfirm) to get the download faster.
Rawwrius01 said:
you can use the tool i posted (samfirm) to get the download faster.
Click to expand...
Click to collapse
I'll check it out, thanks. Also I don't see the link for it in your post, just says (download tool) so I wasn't sure what that meant lol.
https://forum.xda-developers.com/galaxy-tab-s/general/tool-samfirm-samsung-firmware-t2988647 im sorry
So one additional question... I'm waiting for the firmware to download, and the tablet is off, and has been off for the last 10 minutes or so.. and it seems to be overheating where it hurts to touch the screen in the top left corner... Is this normal? Is it trying to do something while it's off? Never had a device do either of these things... I swear if the battery explodes or something when the download completes I'm just going to scream qq
you can try to hold the vol - power and home button to force turn of the device. and try to turn of the light in the room. Maybe the phone is on but the screen is black then you can only see the backlight of the display when its dark
Rawwrius01 said:
you can try to hold the vol - power and home button to force turn of the device. and try to turn of the light in the room. Maybe the phone is on but the screen is black then you can only see the backlight of the display when its dark
Click to expand...
Click to collapse
Maybe, firmware finished download. One last question before I try to flash this, there seems to be multiple tar.md5 files in the archive samfirm downloaded, which one should I flash or does it not matter?
Edit: Nevermind ignore me I feel dumb, I just realized they match up with Odin's options
in odin select the ap file in ap
the bl file in bl
and csc in csc ( the difference in these two files are that it is possible to keep your user data like pictures when you flash the home csc file instead of csc only)
Rawwrius01 said:
in odin select the ap file in ap
the bl file in bl
and csc in csc ( the difference in these two files are that it is possible to keep your user data like pictures when you flash the home csc file instead of csc only)
Click to expand...
Click to collapse
Well... I flashed it and I think the device might be completely bricked now.... it installed everything, started up sortof and said installing system update, then when that was done it it showed the samsung logo and the backlight started turning on and off rapidly and it kept reconnecting and disconnecting from the laptop... now I don't think I can even turn it on....
Now when I boot into download mode, it stays on for a few seconds then starts flashing and turns off completely...
Sceleratis said:
Well... I flashed it and I think the device might be completely bricked now.... it installed everything, started up sortof and said installing system update, then when that was done it it showed the samsung logo and the backlight started turning on and off rapidly and it kept reconnecting and disconnecting from the laptop... now I don't think I can even turn it on....
Now when I boot into download mode, it stays on for a few seconds then starts flashing and turns off completely...
Click to expand...
Click to collapse
you know how to enter the download mode, can you enter it ? vol - power and home button. you can also try samsung switch. its the official samsung tool.
Rawwrius01 said:
you know how to enter the download mode, can you enter it ? vol - power and home button. you can also try samsung switch. its the official samsung tool.
Click to expand...
Click to collapse
When I enter download mode, it stays on for a few seconds, then the backlight flashes a little and the device turns off like it's losing power or something. Download mode was at least working before the flash....
It seems like it won't even turn on unless it's plugged in now. However, when I plugged it in after letting it sit for a minute, now it seems it's telling me it's charging and the battery is at 0%, but I know it should be at least at around 50% and was plugged into the laptop the entire time I was researching online so it shouldn't be dead. Maybe it's not reading the battery level correctly or something? It didn't do this till after it finished the "installing updates" screen. Also just noticed the flash turned itself on even though the device is "off"???
Also, I tried samsung switch but it said the device wasn't supported...
That's strange. I had the same issue like you today but I donwload the latest German firmware from sammobile and flashed it via Odin. It was working.
Maybe your battery was low? You said that it got hot. It won't charge when flashing via USB. Also it charge veeeery slow over USB .... You should try to charge it a bit and try to flash only the AP (firmware) files with Odin. Also use Odin the newest Odin version.
Btw. You should use a the NEWEST version of your country. It's possible that you flash an older one over your current system that could cause problems because of downgrade bootloader.
Sceleratis said:
When I enter download mode, it stays on for a few seconds, then the backlight flashes a little and the device turns off like it's losing power or something. Download mode was at least working before the flash....
It seems like it won't even turn on unless it's plugged in now. However, when I plugged it in after letting it sit for a minute, now it seems it's telling me it's charging and the battery is at 0%, but I know it should be at least at around 50% and was plugged into the laptop the entire time I was researching online so it shouldn't be dead. Maybe it's not reading the battery level correctly or something? It didn't do this till after it finished the "installing updates" screen. Also just noticed the flash turned itself on even though the device is "off"???
Also, I tried samsung switch but it said the device wasn't supported...
Click to expand...
Click to collapse
Gesendet von meinem ONEPLUS A3003 mit Tapatalk
Rawwrius01 said:
That's strange. I had the same issue like you today but I donwload the latest German firmware from sammobile and flashed it via Odin. It was working.
Maybe your battery was low? You said that it got hot. It won't charge when flashing via USB. Also it charge veeeery slow over USB .... You should try to charge it a bit and try to flash only the AP (firmware) files with Odin. Also use Odin the newest Odin version.
Btw. You should use a the NEWEST version of your country. It's possible that you flash an older one over your current system that could cause problems because of downgrade bootloader.
Gesendet von meinem ONEPLUS A3003 mit Tapatalk
Click to expand...
Click to collapse
Thanks for your help. Surprisingly samsung said they might be able to fix it as I had a moment where I just gave up an contacted them to see if there was anything that could be done. Sent it out to them, but if they can't do anything or don't do anything (because custom firmware should void the warranty and all that) I'll have to try just letting it charge longer. Only issue was that while it was charging, it turned on the flash and became very hot very fast so I would need to leave it in front of an airconditioner vent or something. Next time around I'm going to have to make sure I take a full backup of the stock recovery and system somehow...
Hello, i need help, when i flashed with odin my sm-p580 and started the tablet (with the files ap,bl and csc) i cant remove my google account, i dont remember what account had in the tablet, please help!
Hi all,
So my J7 2017 (SM-J730FZKDLUX) basically soft-bricked itself after an official update. Everything on this phone is stock and I never installed anything suspicious on it either.
The current situation is as follows:
Booting the phone normally doesn't work as it gets stuck on the first Android/Samsung screen.
Recovery and safe modes don't work at all: nothing happens.
Download/Odin mode works.
Samsung Smart Switch says my device is not supported while it's supposed to be...
Samsung Kies does not want to start on my PC and says "Update in progress. Unable to run Kies".
Even though it is still under the standard warranty, I've been told I would have to pay for the screen to be changed since the current screen has a scratch on it...
Since Download mode works, I've tried flashing the phone by following this guide from SAMmobile (https :// www(d0t)sammobile(d0t)com/firmwares/galaxy-j7/SM-J730F/LUX/download/J730FXXU3BRL3/247119/) as well as this guide from updato (https :// updato(d0t)com/firmware-archive-select-model?record=0E6D53429C5B11E89F15FA163EE8F90B).
Both result in Odin getting stuck on the "Initialzation" phase. I've searched on the Internet and people said to remove the SD card (I don't have one in that phone), remove the battery (impossible), use a different USB port (tried all of them), be quick (I click on the "Start" button as soon as the phone is "Added" in Odin), enable Debugging mode (well... I can't boot the phone...), make sure to install the Samsung drivers (done from https :// developer(d0t)samsung(d0t)com/galaxy/others/android-usb-driver-for-windows (official Samsung site), but that didn't change anything), using an older version of Odin (but which am I supposed to use? There are tens of them), make sure that Kies is not running at the same time as Odin (Kies was not even installed at the time), running Odin as admin (this is actually required otherwise it doesn't get passed the "SetupConnection" step unless I'm quick enough), use the original USB cable the phone came with (impossible, it was destroyed by my dog however the cable I'm using fits well in the USB port of phone)...
So what am I doing wrong? What can I do? Please help me!
PS: You'll note that my links are a bit weird, it's because I'm new to xda, sorry about that.
Blagatt said:
Hi all,
So my J7 2017 (SM-J730FZKDLUX) basically soft-bricked itself after an official update. Everything on this phone is stock and I never installed anything suspicious on it either.
The current situation is as follows:
Booting the phone normally doesn't work as it gets stuck on the first Android/Samsung screen.
Recovery and safe modes don't work at all: nothing happens.
Download/Odin mode works.
Samsung Smart Switch says my device is not supported while it's supposed to be...
Samsung Kies does not want to start on my PC and says "Update in progress. Unable to run Kies".
Even though it is still under the standard warranty, I've been told I would have to pay for the screen to be changed since the current screen has a scratch on it...
Since Download mode works, I've tried flashing the phone by following this guide from SAMmobile (https :// www(d0t)sammobile(d0t)com/firmwares/galaxy-j7/SM-J730F/LUX/download/J730FXXU3BRL3/247119/) as well as this guide from updato (https :// updato(d0t)com/firmware-archive-select-model?record=0E6D53429C5B11E89F15FA163EE8F90B).
Both result in Odin getting stuck on the "Initialzation" phase. I've searched on the Internet and people said to remove the SD card (I don't have one in that phone), remove the battery (impossible), use a different USB port (tried all of them), be quick (I click on the "Start" button as soon as the phone is "Added" in Odin), enable Debugging mode (well... I can't boot the phone...), make sure to install the Samsung drivers (done from https :// developer(d0t)samsung(d0t)com/galaxy/others/android-usb-driver-for-windows (official Samsung site), but that didn't change anything), using an older version of Odin (but which am I supposed to use? There are tens of them), make sure that Kies is not running at the same time as Odin (Kies was not even installed at the time), running Odin as admin (this is actually required otherwise it doesn't get passed the "SetupConnection" step unless I'm quick enough), use the original USB cable the phone came with (impossible, it was destroyed by my dog however the cable I'm using fits well in the USB port of phone)...
So what am I doing wrong? What can I do? Please help me!
PS: You'll note that my links are a bit weird, it's because I'm new to xda, sorry about that.
Click to expand...
Click to collapse
You should use the latest odin (3.13.1) and use an official samsung USB cable if possible. Not all cables (although it fits) are wired the same.
If the problem is hardware related at least you have warranty.
Blagatt said:
Hi all,
So my J7 2017 (SM-J730FZKDLUX) basically soft-bricked itself after an official update. Everything on this phone is stock and I never installed anything suspicious on it either.
The current situation is as follows:
Booting the phone normally doesn't work as it gets stuck on the first Android/Samsung screen.
Recovery and safe modes don't work at all: nothing happens.
Download/Odin mode works.
Samsung Smart Switch says my device is not supported while it's supposed to be...
Samsung Kies does not want to start on my PC and says "Update in progress. Unable to run Kies".
Even though it is still under the standard warranty, I've been told I would have to pay for the screen to be changed since the current screen has a scratch on it...
Since Download mode works, I've tried flashing the phone by following this guide from SAMmobile (https :// www(d0t)sammobile(d0t)com/firmwares/galaxy-j7/SM-J730F/LUX/download/J730FXXU3BRL3/247119/) as well as this guide from updato (https :// updato(d0t)com/firmware-archive-select-model?record=0E6D53429C5B11E89F15FA163EE8F90B).
Both result in Odin getting stuck on the "Initialzation" phase. I've searched on the Internet and people said to remove the SD card (I don't have one in that phone), remove the battery (impossible), use a different USB port (tried all of them), be quick (I click on the "Start" button as soon as the phone is "Added" in Odin), enable Debugging mode (well... I can't boot the phone...), make sure to install the Samsung drivers (done from https :// developer(d0t)samsung(d0t)com/galaxy/others/android-usb-driver-for-windows (official Samsung site), but that didn't change anything), using an older version of Odin (but which am I supposed to use? There are tens of them), make sure that Kies is not running at the same time as Odin (Kies was not even installed at the time), running Odin as admin (this is actually required otherwise it doesn't get passed the "SetupConnection" step unless I'm quick enough), use the original USB cable the phone came with (impossible, it was destroyed by my dog however the cable I'm using fits well in the USB port of phone)...
So what am I doing wrong? What can I do? Please help me!
PS: You'll note that my links are a bit weird, it's because I'm new to xda, sorry about that.
Click to expand...
Click to collapse
Tru using portronics cable it will right fit into your jack . Try it