Related
what the hell is Samsung doing? I did not update last time with broken firmware and I tried this time with kies.
Now the problem came again.. It only appears Downloading... Do not turn off target and in Kies , it says fail to convert into safe mode...
Now Tablet stayed at the screen with "Downloading ... Do not turn off target!!!" No any response!
-------------------------------------
BTW, I never rooted.
Update. Thank you for everyone in this post for response.
After google from internet, I found a solution.
1) first, after you had "Downloading ... Do not turn off target!!!" screen, Please do not panic ( I did when it happened and really said f*^@ word to Samsung..forgive me...).
2) Press power button + volume down, and hold until it turns off.
3) say "god bless me" or "Mom, please save me." and press whatever combination of buttons you can.
4) It suddenly reboot after that and please use OTA to update. not kies.
5) as far as I can tell, works fine now. However, connect to Kies with wifi does not work.
Were you on a custom rom prior or rooted? If so, did you reset your tab to factory before doing the OTA?
Get back in recovery and flash your back up. If it fails you will have to ODIN your rom in
No problems here using kies, I was only rooted though and I still have root
Do I have to be connected to a PC to get this update? Isn't wifi enough?
You can use wi-fi for OTA update. OP's issue is that even though the tablet went into Download mode, Kies still didn't think it is in download mode. The firmware update hasn't even started to push down to tablet yet.
Based on the earlier problems, you're better off using Kies. If it fails, like it did for OP, it's smart enough to know that and when you disconnect and reconnect the Tab it should automatically go in to emergency recovery mode. What happened to OP happens occasionally with Kies updates. A lot has to do with the PC it's running on and what else is running on that PC. Kies is far from perfect and I'm guessing OP's issue isn't with the new ROM it's with Kies.
I didn't get the update OTA, but just updated with Kies. Had to re-flash CWM and root, but everything works just fine.
Changing to another USB port solved the problem for me. The drivers for the download stage to the tablet could not been loaded for the port I was connected first.
BR
Sent from my GT-P7510 using Tapatalk
flyingstore said:
what the hell is Samsung doing? I did not update last time with broken firmware and I tried this time with kies.
Now the problem came again.. It only appears Downloading... Do not turn off target and in Kies , it says fail to convert into same mode...
Now Tablet stayed at the screen with "Downloading ... Do not turn off target!!!" No any response!
Click to expand...
Click to collapse
exactly the same problem. no solution for me yet...
I repeat this: if you think Samsung's firmware and firmware updates are buggy, Kies is even worse.
foxbat121 said:
I repeat this: if you think Samsung's firmware and firmware updates are buggy, Kies is even worse.
Click to expand...
Click to collapse
Quite true. Kies is terrible. My Galaxy 10.1 wifi won't connect to it at all -- it just sits there attempting to connect. No indication of what's wrong, no log files, nothing. I wasted over an hour last night trying to figure out what was wrong -- removed all "ghost" USB devices, installed Intel INF driver updates, de-installed all active USB hubs & devices, etc.
I even updated Kies to 2.1 ... nothing. Very frustrating.
still no luck with upgrading with kies. it connects to tab, downloads the update to the pc,
the tab goes into download mode in order to install the update, and then connection between kies and tab is lost....
i have the latest kies, i have the drivers, i tried another usb port, i have done a factory reset, but still nothing.
A bit of an SOS situation if anyone knows the right steps please
Well, I restored a Titanium Backup and mistakenly toggled the "restore system apk". It ran fine, all restored and then when I rebooted got stuck.
By "stuck", it re-boots constantly. It shows the LG animation, then all I can see is two messages before it starts booting again:
1) "Unfortunately, Google Play Services Has Stopped"
2) "Unfortunately, System UI has stopped
... and then it does the entire boot sequence, animation, again, and again.
Here is what I can do:
* It is in USB debug mode.
* I have drivers on laptop
* I am able to connect with adb and also shell into phone.
* With adb, I have output to the file an "adb bugreport" as well as an "adb logcat".
* I have several backups:
a) The modemsst1.img and modemsst2.img created by Titanium Backup
b) Titanium backups (full apps and data)
c) an "adb backup - all" backup
* I managed to get it into firmware update mode by pressing the volume up button and the power button and then when it flashed red a few times, just the up button. So, I can get it into Firmware update mode.
Of course, I have never really used adb before, except to dabble a bit. So, I am encouraged that I can somehow get into with shell.
I am not unplugging it until I know what to do!
Since then I have been able to turn the phone off and also put it into charging on USB.
This is what worked:
* Hold down power and volume down button until booting stops and phone turns off completely.
When it does shut down, I kept buttons down until it flashes logo again and then shuts down again. Then I let go. Phone is off and when I plugged in the charger it shows charging animation.
Now, after inspecting the bugreport, I noticed a lot of these messages for all the system apps like this one:
"I/PackageManager(21318): Expecting better updatd system app for com.lge.sizech"
I think the cause of all this shralp is this, I did a LG Mobile Support Tool "Upgrade Recovery" and then in Titanium Backup I restored an older backup (incl system apks). At least that makes sense seeing all the "Expecting better apdat system app" messages in the bugreport.
Still not sure what to do next
I tried the very good instructions here:
[Guide] Unroot/Unbrick - flash official factory firmware with LG Launche
http://forum.xda-developers.com/showthread.php?t=2471370
The update succeeded. However, when I rebooted the phone it is in the same boot-loop with message that it was before.
I used the BELL D803B10D_00.kdz file. Now I will try with the earlier version BELL D803BA_00.kdz file.
We will see what happens ...
do you have nandroid backup from previous rom?
I have three backups:
1) Titanium Backup (full)
* This was my first backup performed right after rooting device and installing Titanium Backup.
2) Titanium Backup (full)
* Did this 2 days ago. Device was working OK and did as precaution.
3) ADB BACKUP. I did this one before my Titanium restore.
I restored the first titanium backup and that (ooooppps!) was after I did an LG Firmware update.
ALSO:
I am on Windows 7 64 and although adb works fine, fastboot does not. I understand that might be a problem with windows 7 64.
So, unless anyone objects, I am going to redo on my windows 32 machine and also "fastbook oem unlock".
Since firmware is OK, if I do the fastboot oem unlock, that will wipe everything. But I can still boot and re-setip the phone, right?
Just checking before I fudge everything up here ..
ALSO ALSO:
I had antivirus/theft security installed and I disabled it partway through last restore.
Maybe that has somethng to do with this all .
But I am still cool because I can ADB and also firmware install seems ok.
ADB works and that is the one good sign.
or you can follow ADB Sideload method
http://forum.xda-developers.com/showthread.php?t=2318497
zekurosu said:
or you can follow ADB Sideload method
http://forum.xda-developers.com/showthread.php?t=2318497
Click to expand...
Click to collapse
I don't (didn't) have TWRP installed. How can I sideload without it?
Also, should I adb oem unlock to get it wiped at this point?
I'm having a similar problem on a Bell D803. Just happened very randomly today. I turned my phone off for an exam, then turned it back on after.. initially had no signal and a black background. Settings for factory reset wouldn't work. My phone is rooted and has TWRP. I went into recovery and formatted.
Bootloop.
Bootloop.
Bootloop x 20.
I however, don't get the same two messages. I just keep bootlooping.
Got home, tried to go through download mode to unbrick it, but for some reason my computer isn't picking it up. I have all the drivers, and before this incident, it was recognized.
Any solutions?
I'm thinking of buying an OTG USB and then just flashing a stock zip from recovery. Would that be a possible viable solution?
asdfvtn said:
I'm having a similar problem on a Bell D803. Just happened very randomly today. I turned my phone off for an exam, then turned it back on after.. initially had no signal and a black background. Settings for factory reset wouldn't work. My phone is rooted and has TWRP. I went into recovery and formatted.
Bootloop.
Bootloop.
Bootloop x 20.
I however, don't get the same two messages. I just keep bootlooping.
Got home, tried to go through download mode to unbrick it, but for some reason my computer isn't picking it up. I have all the drivers, and before this incident, it was recognized.
Any solutions?
I'm thinking of buying an OTG USB and then just flashing a stock zip from recovery. Would that be a possible viable solution?
Click to expand...
Click to collapse
Well, I am able to connect with adb fine on my laptop (Win 7 64) but not on my desktop (Win 7 32)
But on my Win 7 64 I cannot get into fastboot.
I am wondering if the driver install on my desktop went foo-bar and needs reinstall. Also, I noticed that the website drivers are more recent USB drivers than some of the ones linked on this site.
I used adb uninstall package for many user packages and it was success. But I still see the packages listed in the bugreport?
For example: I already uninstalled "com.benhirashima.skiplock" and also "com.lookout".
Why? What to do to really zap them for good?
Sorry, I posted the wrong link earlier.
This was the guide I used which succeeded but made no difference to the boot-loop.
LG G2 Stock Firmware (Go Back to Stock)
http://forum.xda-developers.com/showthread.php?t=2432476&highlight=d803
Just figured out how to do a factory reset.
http://www.youtube.com/watch?v=3ogBvzbPikc
The hard reset worked and now I am configuring the phone settings!
So, again, this is what I did:
1) http://forum.xda-developers.com/showthread.php?p=45293512
2) http://www.youtube.com/watch?v=3ogBvzbPikc
Not sure if it all worked but I am setting the phone up as we speak (or as I type)
natureburger said:
Well, I am able to connect with adb fine on my laptop (Win 7 64) but not on my desktop (Win 7 32)
But on my Win 7 64 I cannot get into fastboot.
I am wondering if the driver install on my desktop went foo-bar and needs reinstall. Also, I noticed that the website drivers are more recent USB drivers than some of the ones linked on this site.
Click to expand...
Click to collapse
Hmm that's strange. Unfortunately for me, I'm already on 64-bit and it still isn't picking it up.
ALL FIXED UP
WORKING 110%
:good:
natureburger said:
ALL FIXED UP
WORKING 110%
:good:
Click to expand...
Click to collapse
I have followed this to a t.
Succesfully flashed the stock firmware that came with the phone when sold.
Did hard reset using the the power button and volume down
= phone rebooting every 10 seconds, no wifi, imei = null
adb devices = offline.
Really depressed right now. If anybody can help me I would appreciate it.
zprovo said:
I have followed this to a t.
Succesfully flashed the stock firmware that came with the phone when sold.
Did hard reset using the the power button and volume down
= phone rebooting every 10 seconds, no wifi, imei = null
adb devices = offline.
Really depressed right now. If anybody can help me I would appreciate it.
Click to expand...
Click to collapse
Press the power button down and hold it.
It should turn off, then look like it is turning on, (flash logo very briefly) and then turn off.
Let go of power button and it should stay off.
Do that. Now, does it work to turn off completely?
Let's see if you can do that first.
Then .. do hard reset, exactly like this:
http://www.youtube.com/watch?v=3ogBvzbPikc
Does the hard reset screen show and give you hard reset options?
natureburger said:
Press the power button down and hold it.
It should turn off, then look like it is turning on, (flash logo very briefly) and then turn off.
Let go of power button and it should stay off.
Do that. Now, does it work to turn off completely?
Let's see if you can do that first.
Click to expand...
Click to collapse
Yup. I totally understand what you are saying and have done it many times. I had to use that method to get into download mode and also had to use it to do hard reset.
I just reflashed the phone all over again a second time succesfully.
Reboots every 5 seconds. Keyboard came up for a few seconds for the first time in 48 hours during the initial setup phase. 5 seconds later as I was trying to input a wifi code it would not appear. then it rebooted as usual.
I really appreciate any input right now. :cyclops::crying:
zprovo said:
Yup. I totally understand what you are saying and have done it many times. I had to use that method to get into download mode and also had to use it to do hard reset.
I just reflashed the phone all over again a second time succesfully.
Reboots every 5 seconds. Keyboard came up for a few seconds for the first time in 48 hours during the initial setup phase. 5 seconds later as I was trying to input a wifi code it would not appear. then it rebooted as usual.
I really appreciate any input right now. :cyclops::crying:
Click to expand...
Click to collapse
1) Are you able to completely turn it off using my instructions?
2) When you hard reset (2nd half of this video), http://www.youtube.com/watch?v=3ogBvzbPikc
a) Does the hard reset screen show?
b) Does it give you the hard reset options?
3) Before it was bricked, was it in 'usb debug mode' in developer options?
4) Which kpz version did you restore to?
5) Did your "adb devices" ever work? Did your "adb shell" ever work?
natureburger said:
1) Are you able to completely turn it off using my instructions?
2) When you hard reset (2nd half of this video), http://www.youtube.com/watch?v=3ogBvzbPikc
a) Does the hard reset screen show?
b) Does it give you the hard reset options?
3) Before it was bricked, was it in 'usb debug mode' in developer options?
Click to expand...
Click to collapse
1) Yes absolutely. It is sitting next to me right now doing nothing at all because I turn it off when I am not trying to fix it, otherwise it keeps rebooting relentlessly.
2) a) Yes, same as the video. b) Yes it says the same exact thing as the video. I press power key twice and it begins. The stock recovery android appears with a loading bar on the bottom for ~1 minute then it goes to the boot "lg animation".
3) Yes it was. Before it was bricked I essentially always had it in debug mode because I successfully rooted it and simply left it on debugging mode after having to activate it to root.
4) D801V11B_00.kdz The EXACT same as the original. This is a Videotron (canadian) phone. I can clearly remember without a doubt going into about phone and this is what it was running before all of this happened.
5) I am having a bit of memory strain here, but I do believe it also said adb devices before any of the issues came. It is a good point I will try "adb device" from another trusted computer.
Other notes: I can browse the android os for a few seconds. Sometimes sound does not work, wifi is non functional (even though the keyboard never appears, I managed to have a security free wifi in my proximity and it would not connect (was saying: temporarily avoiding bad signal)) and also I do have modemstat1.img and modemstat2.img backups for EFS.
adb devices consistently shows "offline" but it is definitely recognizing the phone. I have also tried using usb debugging activated and still "offline". Drivers are up to date and all.
The upper drawer in the usual g2 user interface is strange now. it doesnt have anything except for the date (1970 something...) and a "gear" icon for system settings. I am talking the drawer you drag down from the top of the screen.
This phone was working with absolutely no problems 2 days ago.
Thank you so much for looking into this. I have certainly exhausted my repairing capacities. I am entirely dependent upon the knowledgeable individuals in here from here on out.
zprovo said:
1) Yes absolutely. It is sitting next to me right now doing nothing at all because I turn it off when I am not trying to fix it, otherwise it keeps rebooting relentlessly.
2) a) Yes, same as the video. b) Yes it says the same exact thing as the video. I press power key twice and it begins. The stock recovery android appears with a loading bar on the bottom for ~1 minute then it goes to the boot "lg animation".
3) Yes it was. Before it was bricked I essentially always had it in debug mode because I successfully rooted it and simply left it on debugging mode after having to activate it to root.
4) D801V11B_00.kdz The EXACT same as the original. This is a Videotron (canadian) phone. I can clearly remember without a doubt going into about phone and this is what it was running before all of this happened.
5) I am having a bit of memory strain here, but I do believe it also said adb devices before any of the issues came. It is a good point I will try "adb device" from another trusted computer.
Other notes: I can browse the android os for a few seconds. Sometimes sound does not work, wifi is non functional (even though the keyboard never appears, I managed to have a security free wifi in my proximity and it would not connect (was saying: temporarily avoiding bad signal)) and also I do have modemstat1.img and modemstat2.img backups for EFS.
adb devices consistently shows "offline" but it is definitely recognizing the phone. I have also tried using usb debugging activated and still "offline". Drivers are up to date and all.
The upper drawer in the usual g2 user interface is strange now. it doesnt have anything except for the date (1970 something...) and a "gear" icon for system settings. I am talking the drawer you drag down from the top of the screen.
This phone was working with absolutely no problems 2 days ago.
Thank you so much for looking into this. I have certainly exhausted my repairing capacities. I am entirely dependent upon the knowledgeable individuals in here from here on out.
Click to expand...
Click to collapse
Hmmmm..... why your adb devices is not working? But the re-pair works and you can then do hard reset.
But that is good information you shared.
Maybe someone else can chime in.
From my experience:
1) adb usb access seems spotty. My win 7 64 connected fine and it even kept the shell through the reboot cycle. But on my win 7 32 machine it was only detecting device and then not able to shell.
2) I was also able to use from the LG website LG MOBILE SUPPORT TOOLS.
Download the LG MOBILE SUPPORT TOOL
I downloaded the most recent one from the LG website and make sure to select your options >> country and then the correct phone model at the upper right hand corner of the tool.
Then install USB driver for correct phone model.
Then see if USB works, "adb device" should return the device code.
"adb shell" should show the shell prompt.
3) There is always fastboot. But I an noob and know 0% about how to properly connect and use it.
Some others please chime in and help this droid bro!
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!
Good evening! I hope you can help me.
I flashed LineageOS 14.1, but I wanted to go back to EMUI. I made all the wipes and tried to flash different stock firmwares through a forced update (volume buttons + power button), but it never worked. At that point, I read about a guy in this forum who suggested to create a flashable zip with Huawei Update Extractor: I followed the suggestion and tried to flash it with TWRP. No error was given, but when I tried to restart, TWRP told me I had no OS installed. I thought it was strange, so I tried to restart anyway. That's when I got in rescue mode. I can't get into the recovery and I can't use fastboot. What rescue mode shows me is:
RESCUE MODE
Attention!
Please update system again
Update User Guide:
*link*
*android avatar*
Error!
Func NO: 10 (boot image)
Error NO: 2 (load failed!)
Pressing the three buttons, I'm able to force an update. The problem is I can't find a firmware that doesn't get rejected. With Lollipop firmwares, it starts to install, but it fails at 12%. With Marshmallow ones, the installation process doesn't even start.
What can I do to make it work again? I'm very sad because this phone was gifted to me a couple of days ago and I already messed it up. I don't even know how to turn it off.
What can I do to get in fastboot mode? At that point, what should I do to flash the stock firmware? Or maybe do I need to find the first stock firmware ever installed into this phone to make the forced update work?
Please, I need help. Thank you in advance!
P.S. The phone's model is ALE-L21. I live in Italy, so I assume it's a European version.
Did you managed to fix this?
Jhon_Locke said:
Did you managed to fix this?
Click to expand...
Click to collapse
Not yet, but I'm working on it. I found out that the device is recognized by my PC if I follow these steps:
1. Connect the phone to the PC and wait for it to go in rescue mode;
2. Wait until the notification LED stops to blink;
3. Disconnect the USB cable;
4. Press volume - and power button;
5. Reconnect the cable.
At that point, the screen turns black and the phone is recognized as "㌲㔴㜶㤸". I installed the drivers and now it's recognized as "HUAWEI USB COM 1.0". I should be able to reflash the partitions and make my phone work again, but I'm still trying to understand how to do it correctly.
Any help is appreciated!
ErikChimello said:
Not yet, but I'm working on it. I found out that the device is recognized by my PC if I follow these steps:
1. Connect the phone to the PC and wait for it to go in rescue mode;
2. Wait until the notification LED stops to blink;
3. Disconnect the USB cable;
4. Press volume - and power button;
5. Reconnect the cable.
At that point, the screen turns black and the phone is recognized as "㌲㔴㜶㤸". I installed the drivers and now it's recognized as "HUAWEI USB COM 1.0". I should be able to reflash the partitions and make my phone work again, but I'm still trying to understand how to do it correctly.
Any help is appreciated!
Click to expand...
Click to collapse
fastboot detects your device when you plug it into your computer?
I mean, if you run "fastboot devices" it shows your phone?
I've had this same problem but with an P8 Lite 2017, after flashing some ROM that supposedly was the stock one and trying to flash recovery I ended up with my phone bootlooping into rescue mode, I was able to "bypass" this thing rebooting my phone like crazy, seriously like after 20 reboot it finally booted into the damn ROM and I never touched the phone again. Sometimes when the phone ran out of battery and tried to power it on the phone booted into rescue mode and again after some reboots it booted to Android but now I want to install a custom ROM or at the very least root this damn phone so that's why I'm asking you if you have solved this, if you do then probably if I follow the same steps I would be able to fix that screen, hopefully.
If you are able to flash something start with flashing all recoveries your update.app has, maybe that's the problem (at least in my phone it is).
Jhon_Locke said:
fastboot detects your device when you plug it into your computer?
I mean, if you run "fastboot devices" it shows your phone?
I've had this same problem but with an P8 Lite 2017, after flashing some ROM that supposedly was the stock one and trying to flash recovery I ended up with my phone bootlooping into rescue mode, I was able to "bypass" this thing rebooting my phone like crazy, seriously like after 20 reboot it finally booted into the damn ROM and I never touched the phone again. Sometimes when the phone ran out of battery and tried to power it on the phone booted into rescue mode and again after some reboots it booted to Android but now I want to install a custom ROM or at the very least root this damn phone so that's why I'm asking you if you have solved this, if you do then probably if I follow the same steps I would be able to fix that screen, hopefully.
If you are able to flash something start with flashing all recoveries your update.app has, maybe that's the problem (at least in my phone it is).
Click to expand...
Click to collapse
No, it doesn't show anything if I write that command...
I guess mine won't ever boot into the rom because it seems like there's no system installed. I made some researches and found out there are some softwares that let you reflash the partitions IF the phone is recognized as "HUAWEI USB COM 1.0". I'm still trying to figure out how to do it correctly though. I feel like if I do something wrong, then my phone won't probably turn on again.
In your case, you should be able to flash a custom rom without any issue. You just have to be very careful and inform you as much as you can: I don't want your phone to end up like mine?. Anyway, it seems pretty hard to go back to the stock rom, so think about it before you flash a custom rom. Also, make a Nandroid Backup is very important.
History:
I have a samsung tab S6 lite LTE version. The tablet freezed out of nowhere when I was working and restarted but stuck in bootloader. After a while, and after removing the sd card, the tablet functioned properly. The tablet had more 80% of battery charge.
I thought the new update might fix the issue. I installed the update. it restarted and stuck in bootloader again. Power and Volume Down buttons will restart the tab, but it never went past the bootloop.
Left it for 12 hours without charging, and then the tablet went into recovery mode. I wiped the cache and when figuring out the other options in recovery it switched off and did nothing. When connected to a charger, a circle with lighting icon showed up. No combination of buttons worked.
Took it to the service center, and was told the motherboard needs to be replaced. I knew it was a software problem so I came home without replacing the motherboard.
I put the tablet on charge for a while and pressed volume up and down button and connected it to the computer. The tablet went into download mode. I immediately downloaded Odin and stock firmware and tried to flash only the BL file to the tablet. It failed few times, maybe because of faulty cable. I used another working cable and tried to flash the full firmware and the tablet disconnected again from the pc.
But now the tablet showed "an error occured while updating and use smart switch for emergency recovery". Smart switch on pc did not detect the tablet, but Odin did. The device manager detected the device as samsung mobile usb composite device. I used a new usb cable and flashed the stock firmware using Odin. The process was success but the tablet died.
It does nothing when connected to a charger or pc. No display and no buttons worked.
I opened the tablet by removing the display, and disconnected the battery physically. But nothing happened.
I tried several times to connect to pc, and for once it was detected by the pc.
This time I flashed the stock firmware using odin with nand erase and repartition. extracted the pit from csc file and added it to Odin.
The flash was a success but the tablet remains unresponsive. I checked the display to see if I had cracked or damaged it while opening, but it is good.
Now Sometimes, the tablet gets detected by pc as samsung mobile usb composite device and I could even flash the firmware with success. But the tablet displays nothing and is unresponsive.
Can Anybody advice What I can do now?
PS. I used the correct firmware meant for s6 lite LTE version every time I flashed.
Disconnect devices from PC USB port & uninstall official Samsung USB drivers. Reboot & re-install drivers. Connect to another USB port preferably at the rear PC.
Flashed latest Android 10 instead of the latest Android 11 stock firmware (AP *super.img.tar file ONLY) using Odin (I used official Odin3_v3.14.4) with Auto-Reboot, Nand Erase and Re-Partition. Input *.pit file. Flashing process might take 'years' but be patient until it ended & auto boot up successfully. Try another USB port if it failed. Therafter, flash the rest of stock WITHOUT Nand Erase & ONLY Re-Partition, Auto Reboot & F. Reset Time.
Once it successfully got flashed & auto reboot, wait patiently as it might also take a longer time than normal to boot up. Charge the device to optimal. Done!
Optional (Remove Knox Guard)
Connect to the internet. Login to your Google & Samsung account to update everything & reboot upon further updates. Thereafter, boot to Download Mode & flashed AP (Magisk Patched *boot.img, blank *vbmeta.img & patched *vbmeta_samsung.img) + BL (Blank *vbmeta.img) WITHOUT Nand Erase & Re-Partition. After successful boot up, reboot back to Download Mode & ensure there's no 'KG State' on the list before deleting('root delete' not ADB) Knox Guard or app named Payment Service as in Android 10.
Thanks. I will try.
7GHz said:
Disconnect devices from PC USB port & uninstall official Samsung USB drivers. Reboot & re-install drivers. Connect to another USB port preferably at the rear PC.
Flashed latest Android 10 instead of the latest Android 11 stock firmware (AP *super.img.tar file ONLY) using Odin (I used official Odin3_v3.14.4) with Auto-Reboot, Nand Erase and Re-Partition. Input *.pit file. Flashing process might take 'years' but be patient until it ended & auto boot up successfully. Try another USB port if it failed. Therafter, flash the rest of stock WITHOUT Nand Erase & ONLY Re-Partition, Auto Reboot & F. Reset Time.
Once it successfully got flashed & auto reboot, wait patiently as it might also take a longer time than normal to boot up. Charge the device to optimal. Done!
Optional (Remove Knox Guard)
Connect to the internet. Login to your Google & Samsung account to update everything & reboot upon further updates. Thereafter, boot to Download Mode & flashed AP (Magisk Patched *boot.img, blank *vbmeta.img & patched *vbmeta_samsung.img) + BL (Blank *vbmeta.img) WITHOUT Nand Erase & Re-Partition. After successful boot up, reboot back to Download Mode & ensure there's no 'KG State' on the list before deleting('root delete' not ADB) Knox Guard or app named Payment Service as in Android 10.
Click to expand...
Click to collapse
By chance is it going to work for KG:Locked status device? I'm on F62, i bought this (second hand) few days ago from another city. Tapping on build number doesn't give any response, When i try to flash any firmware I'm getting response "All binaries are not allowed to be flashed" I'm pretty much confused what's happening here
Rolith Rtw said:
By chance is it going to work for KG:Locked status device? I'm on F62, i bought this (second hand) few days ago from another city. Tapping on build number doesn't give any response, When i try to flash any firmware I'm getting response "All binaries are not allowed to be flashed" I'm pretty much confused what's happening here
Click to expand...
Click to collapse
Did you solved it?