Hi Guys,
My Samsung Galaxy S2 SGH-I777 is soft bricked. It only goes into download mode when the usb cable is plugged and the (vol up down + power) buttons are pressed. When the cable is unplugged, it doesn't turn on. I've tried the following steps by creepyncrawly at last but couldn't get it to a working state.
1)Go to this post and download the Tar version of Siyah 2.6.14 Kernel. Flash it in the PDA slot without ticking Re-Partitioning. If you get a pass, it won't boot, so turn the phone off and then back to download mode and...
2) Flash the full stock Gingerbread distribution from the Download Repository, I777UCKH7 including the bootloaders and everything, in the PDA slot.
3) If you get a pass here, then the phone might boot, or you might have to boot into recovery first and perform a wipe data/factory reset. If you're able to boot the phone, then you are back in business, and can flash whatever firmware you want.
If it is not, then:
4) Download the SBL Bootloader from the Download Repository. Flash it as PDA in ODIN, without ticking Re-Partitioning.
5) Flash the Kernel, as in step 1.
6) Flash the full stock Gingerbread distribution, as in step 2.
Even before that I tried many other things from various forum posts.
Please help me to get this working again..
Thanks so much
Okay. The above are steps to overcome nand read-write corruption in the emmc memory. However, these steps should result in a working system installation under almost any circumstances. However, if there is emmc memory failure, not corruption but actual damaged memory, then it will be unrecoverable. Without additional information, it is impossible to say what the actual problem is.
So, since you say the above sequence fails, I need to know exact details of what happens when you follow the above instructions. I need a step by step description, what succeeds, what fails and in which step, and any text from the messages section of Odin. And anything else you can think to add that might be helpful.
Thanks so much for the reply.
The flashing process works fine, no error messages from odin or from the phone,
But
When it comes to the Android System Recovery Screen, I did the factory reset. After it reboots, load the Android System Recovery Screen again.
Then when I select the reboot option, phone reboots to the Android System Recovery Screen until the cable is plugged in, when it is removed, it doesn't reboot anymore.
In the Log there's a message that is suspicious, it says
"--Applying Multi-CSC...
Installing Multi-CSC
Can't access to /system/csc/ATT/system/
successfully applied multi-CSC"
And once i had something weird, when I flashed the secondary bootloader (step 4), phone seemed to load one step further than the samsung screen when onto the AT&T screen, but then suddenly it turned off and heard a few 'tik', 'tik' sounds.
Thanks so much for all the support, looking forward to an answer. Will upload some screens soon.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
You can safely ignore the message "Can't access to '/system/csc/ATT/system/'." This message is often present when the flash is fully successful, and at other times.
The telling message, however, is "Deleting Cryption Meta Data." This seems to indicate nand read/write corruption, and has been successfully repaired in at least a few cases that I am aware of, by using the above sequence.
So, I would suggest that you try going through the sequence again. It is a three step process, really.
1) Flash sbl.tar only using Odin. Tick F Reset Time, but untick Auto Reboot, so that the phone will not attempt to boot into system.
2) Flash the tar version of the Siyah 2.6.14 Kernel using Odin, having returned to download mode without trying to boot into system. Again tick F Reset Time, but untick Auto Reboot, so that the phone will not attempt to boot into system.
3) Finally, flash the stock Gingerbread SGH-I777UCKH7 tar using Odin, and this time tick Auto Reboot as well as F Reset Time.
If it doesn't boot into the system, you may still need to enter recovery and perform a wipe data/factory reset again.
Keep good notes about what happens each step along the way so that if it is not successful, we may get some clues.
Thanks so much for the help you're doing but unfortunately the results are the same as before
Same messages, for example "Deleting Cryption Meta Data" is always on top
Please give me another option.
BTW, I had to press Vol up + Vol down + Power button to get into download mode after the sbl is flashed because it wasn't restarting as per the option we set.
Also phone seemed to load one step further when I flashed the I777UCKH7 and the samsung screen went onto the AT&T screen, but then suddenly it turned off and heard a few 'tik', 'tik' sounds. weird !!!
Thanks so much
I don't have any additional "tricks up my sleeve."
It is possible that the emmc flash memory has become damaged, but this is far from conclusive. It is possible for the emmc flash memory to be damaged without the phone being completely hard bricked. In order to find out conclusively, you would need to send it to someone with equipment capable of testing the memory module.
From my observations of people who have posted about a problem similar to yours, including "deleting cryption meta data," there have been some cases where the phone was recovered, and some cases where it was not.
It is possible that it is a connection problem between the phone and the computer. I know of one case where a person kept trying to flash, and eventually the flash worked, but I don't remember if the problem he had was similar to your or not.
I also remember one case where a person got his phone going after using the pit file from the Download Repository, along with the Gingerbread tar. In that case, he had to flash the pit with the Gingerbread tar, and still wouldn't boot, but after flashing the Gingerbread tar again without the pit, it booted. Again, I don't remember is his problem was similar to yours.
Sorry I can't be of more help.
Thanks so much for trying to help me here. Anyways I'm trying to buy a new phone, I've been using this phone for 3.5 years and I think its time is up now. Thanks again ...
Related
I have tried everything on my wife's I9001 but I cannot get Odin to get past SetupConnection.
Here is a picture:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I have tried:
Redownloading Odin 1.3 and 1.85 and also tried using Multi Downloader 4. (Which says that the .md5 file isn't supported).
Changing USB ports.
Using a Jig to boot Download mode.
Booting into Download mode normally.
Installing MobileODin except that I9001 is not supported.
Trying to flash a different rom other than 'I9001XXKQ1_I9001XXKPI_I9001DBTKP1_HOME.tar.md5'
Rebooting the computer over 9000 times.
Rebooting the phone over 9000 times.
Pulling the battery over 9000 times.
Reinstalling the drivers from Kies.
Turning USB Debugging mode off (was worth a try)
Using a different computer.
Reinstalling my OS (seriously, I had to do that anyway)
Leaving the phone plugged in for 30 minutes anyway just to see if it was working but not updating.
I am unable to boot into 'Recovery Mode' also the phone sh!ts itself and boots into 'RAM Dump' instead... where it requires a battery pull to reboot. So I can't even put the rom file on the internal memory and use recovery mode to flash it from there...
Basically nothing works at all. Odin 1.35 fails, Odin 1.85 fails, Multidownloader fails. I have tried rebooting, restart, and re-bloody everything I can. I have no idea why it won't get past setup connection. I've even tried using my second USB cable. It used to work fine, I used to be able to flash the phone fine.
Kies is NOT running in the background... there are no processes open or anything. I have googled and yahooed and everything to find a solution to this. NOTHING works..
Please help. I need to flash this dhfshfgdshgfshs phone as soon as possible. It's not working properly and it's really unstable..
If someone has any suggestions I am so willing to hear them..
Thanks a lot. - From a really frustrated dude
leijonasisu said:
I have tried everything on my wife's I9001 but I cannot get Odin to get past SetupConnection.
Click to expand...
Click to collapse
When you booted your phone, are you REALLY sure that you go into Download-mode?
When i was doing the same thing as you, i just enter Android Recovery (pressed Home+Vol Up+Power instead of pressing Home-Vol DOWN+Power)
Im not sure what buttons on your phone because im having a Note.
If you find this helpful, you could click Thanks
Thanks mate but I worked it all out. For some reason my I9001 wasn't being flashed in Odin properly like I explained. I accidentally screwed up my download mode. Sometimes I could get into Download mode by holding the corresponding keys. Volume Down + Home + Power. Sometimes the phone would just go black with a white dot at the top left corner.
Using a Jig I was able to boot into download mode without hassle. I then used Multi Flasher 4 to flash my phone seeing as no matter what Odin 1.85 and 1.3 would not work.
After that I did a factory reset so the phone was basically flashed twice. Everything seems to work well now. Before the factory reset the phone would just get into a boot loop.
Thanks anything. FeMod or whatever the clockworkmod for the I9001 is, wasn't working either. It would just go blank when I chose an option.
It's ok now. Thanks anyway but this can be closed.
Make sure Kies is not running. That was preventing me from connecting. :good:
Odin and xdadevelopers suck
Odin is buggy. Works on and off.
xda sucks because the owners of the site will have a single applicatoins dependencies spread across as many pages as possible in order to increase views and click through rates and sell ads to say, Bell Telecom perhaps?
F*n dicks at xda far as I'm concerned.
Wasting everyone's time and polluting the search results space.
Amen.
just do that
just enable usb debbuging
thanks
edwin_chenyh said:
Make sure Kies is not running. That was preventing me from connecting. :good:
Click to expand...
Click to collapse
Thank you alot bro. i was searching problem about half a year. you saved my life
I have the same issue with my Samsung Galaxy s2 (GT-i9100).
- Yes, Its really in download mode
- Have tried alot of diffrent versions of odin
My phone suddenly stopped working, can't start recovery and it doesnt boot at all.
The only thing I can do with it now is to enter download mode.
I might have flash something bad... dont really remember at all.
Had kies installed both the first version and klies3, all uninstalled now without any change...
THX
you're great, thank you very much bro : Iyi:: Iyi:: Iyi:
Hi i have n915f samsonge note edge after last update very restart or frizz when i work whit and go on downloading mode with out i press any key.i go recovery mode and wipes cach drive and restart on factory but Dissolving problem.when i want flash whit odin and turn on debugging mode not turn on my phone but when put cabe onit and hold power+Home +and volum key go on downloading mode.and detects with odin but when start stuck on setup connection.
Please help me.
Yesterday, I got a little too excited with rom flashing, and I ended up bricking my galaxy player. (Please note that I have The Galaxy Player 5.0 YP-G70) When I was done with screwing around with my player, I decided to try re-flashing the stock rom onto it. On odin, I got an error, so I unplugged the phone while it was still in download mode (with the android logo shoveling something) and I came to this screen:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
After trying to go into recovery mode and pressing the side buttons in different combinations to see if it would go into recovery mode or download mode, my galaxy player turned off completely and will not turn back on at all now, even after plugging it into the computer and through the wall charger, it will no longer turn on at all. I'm assuming the battery died, but when I plug it in, nothing happens, it doesn't go back to that screen.
I'm hoping for some help. I can return it to best buy, according to what they told me when I bought it (that the warranty covers ANYTHING except for being lost or stolen)
BrassZeppelin said:
Yesterday, I got a little too excited with rom flashing, and I ended up bricking my galaxy player. (Please note that I have The Galaxy Player 5.0 YP-G70) When I was done with screwing around with my player, I decided to try re-flashing the stock rom onto it. On odin, I got an error, so I unplugged the phone while it was still in download mode (with the android logo shoveling something) and I came to this screen:
After trying to go into recovery mode and pressing the side buttons in different combinations to see if it would go into recovery mode or download mode, my galaxy player turned off completely and will not turn back on at all now, even after plugging it into the computer and through the wall charger, it will no longer turn on at all. I'm assuming the battery died, but when I plug it in, nothing happens, it doesn't go back to that screen.
I'm hoping for some help. I can return it to best buy, according to what they told me when I bought it (that the warranty covers ANYTHING except for being lost or stolen)
Click to expand...
Click to collapse
Hi there, I have exactly the same problem, but my player can turn on and just shows the phone -- ! -- computer logo. On my galaxy s i would take the battery out and then boot into download mode. But i cant figure out how to take out the battery... Any1 help us???
NamNamNom said:
Hi there, I have exactly the same problem, but my player can turn on and just shows the phone -- ! -- computer logo. On my galaxy s i would take the battery out and then boot into download mode. But i cant figure out how to take out the battery... Any1 help us???
Click to expand...
Click to collapse
The phone -- ! -- computer is forced download mode.
Sent from my YP-G70 using xda app-developers app
To ensure its now power, I would recommend leaving it connected to a power source for a day. It could be that since the device is low of power, it won't boot, simply because it might not have enough power to.
Considering how you've installed new roms, it could also be that the device won't charge and want to boot(ie teh firmware doesn't show the charge logo but boots the rom) when its connected to a power source. In doing so, it notices that it can't and loops, unknowingly
Not sure if this helps but hope you resolve it someway.
Please tell me how did you fixed your Galaxy Player 5 Ive the exact the same
UnsignedZero said:
To ensure its now power, I would recommend leaving it connected to a power source for a day. It could be that since the device is low of power, it won't boot, simply because it might not have enough power to.
Considering how you've installed new roms, it could also be that the device won't charge and want to boot(ie teh firmware doesn't show the charge logo but boots the rom) when its connected to a power source. In doing so, it notices that it can't and loops, unknowingly
Not sure if this helps but hope you resolve it someway.
Click to expand...
Click to collapse
Please, my friends, help me!
Samsung Galaxy Player 5.0 YP-G70 (with phisycal home button) bricked.
I accidentally flashed the rom to SGS-I9000B to the SGP 5.0 so it got bricked.
It's status is: doesn't turn on, doesn't enter in dowload mode (Volume down + Home + Power), doesn't show charging icon.
After weeks of exaustive researche, the only way I was able to enter in download mode was using the Adam's Outler procedure: Instaling Linux, Java, Oracle Virtual Box a version of Windows under VBOX, to run Samsung drivers and Odin after using Unbrickable Resurrector R40.
Well, using this procedure SGP 5.0 enters in downloading mode and when I use the PIT file and BootloadersOnly provided by Adam the result in Odin is PASS! Despite that SGP doesn't reboot and keeps the same way: doesn't turn on, doesn't enter in dowload mode (Volume down + Home + Power), doesn't show charging icon.
So I enter in download mode using Unbrickable Resurrector R40 again and try to flash several SGP 5.0 YP-G70 Intl ROMs: Stock Froyo, Stock Ginger Bread and some Customs ROMs most of them PASS in the Odin result BUT SGP 5.0 never reboots or turn on after the procedure.
I have a doubt of marking or not Re-partition in Odin, but the procedure just works if I mark it.
I feel I was close to resurrect it and make it work again but all I've got is frustration.
I'm not an expert as the major of you so I beg some enlightned soul show me the way to make it works: step by step and share with me the right files I have to use to make it works.
I also have installed Heimdall but I was not able to find the appropriate files to use it and SGP 5.0 can not have the batery removed. Someone wrote Adam has developed a tool for SGP full recovery but I didnt find it.
Please, folks, help me and I will share the solution with other people in the same situation.
Thanks and best regards.
As this time-lapsed gif indicates, my phone is stuck in an endless boot logo - recovery loop.
I was on official Sammy 4.3 and decided to reboot to recovery when I encountered this. The recovery at that time was Philz 5.18.5 and I was incidentally rebooting to recovery to flash Philz 6.
The following has no effect:
1. Long press of power button (8 secs) for shutdown and reboot
2. Key combination for reboot to recovery
3. Pulling out the battery and then booting up the phone
4. Connecting the charger with the phone in off mode
I have been able to go in to Download mode which I suppose will enable me to use Odin, but I quite some time away from being able to do that. So any ideas anyone?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sounds like a partition is corrupt, if it won't boot to recovery then nothing else to try except odin.
Sent from my GT-I9300 using Tapatalk
t3chg33k said:
As this time-lapsed gif indicates, my phone is stuck in an endless boot logo - recovery loop.
I was on official Sammy 4.3 and decided to reboot to recovery when I encountered this. The recovery at that time was Philz 5.18.5 and I was incidentally rebooting to recovery to flash Philz 6.
The following has no effect:
1. Long press of power button (8 secs) for shutdown and reboot
2. Key combination for reboot to recovery
3. Pulling out the battery and then booting up the phone
4. Connecting the charger with the phone in off mode
I have been able to go in to Download mode which I suppose will enable me to use Odin, but I quite some time away from being able to do that. So any ideas anyone?
Click to expand...
Click to collapse
Maybe this is SDS, its time to send your SGS3 to Samsung for repair(getting new motherboard)..
Can u go into download mode or not(i did't understood what you said earlier), if you can go into download mode can you please tell what is there in Product Name. if its GT-I9300 and everything else is fine there than try to flash firmware from odin..
suyash1629 said:
Maybe this is SDS, its time to send your SGS3 to Samsung for repair(getting new motherboard)..
Can u go into download mode or not(i did't understood what you said earlier), if you can go into download mode can you please tell what is there in Product Name. if its GT-I9300 and everything else is fine there than try to flash firmware from odin..
Click to expand...
Click to collapse
From what I had read about SDS, the phone ends up being so very dead that it doesn't even show the boot logo. In my case, Download mode is the just about the only thing that I can currently enter in to; so I guess there is no other option now.
t3chg33k said:
From what I had read about SDS, the phone ends up being so very dead that it doesn't even show the boot logo. In my case, Download mode is the just about the only thing that I can currently enter in to; so I guess there is no other option now.
Click to expand...
Click to collapse
In case of SDS boot loop also occurs some times and also some users are able to get into download mode but they find that the product name is blank or something else, have you checked your Product Name, that should be GT-I9300..
i just had the very same problem, although with philz 6.0....
Fortunately in my case (and i can bet in yours too) in download mode the phone model was correctly reported as gt i9300 so it wasn't sds (phew) and i could get my phone running again.
these are the steps i followed:
1) put the phone in download mode
2) open odin and connect the phone to the pc
3) load under pda stock rom of my country
4) let odin do it's magic till it says "pass"
5) at this stage my phone got stuck at the samsuing logo so
6) Turned the phone off and boot in to stock recovery
7) Cleared cache and data/factory reset
8) tada phone up and running again
9) Flashed custom recovery and custom rom again (we will never learn, will we???)
Hope this helped.
amigaoneit said:
i just had the very same problem, although with philz 6.0....
Fortunately in my case (and i can bet in yours too) in download mode the phone model was correctly reported as gt i9300 so it wasn't sds (phew) and i could get my phone running again.
these are the steps i followed:
1) put the phone in download mode
2) open odin and connect the phone to the pc
3) load under pda stock rom of my country
4) let odin do it's magic till it says "pass"
5) at this stage my phone got stuck at the samsuing logo so
6) Turned the phone off and boot in to stock recovery
7) Cleared cache and data/factory reset
8) tada phone up and running again
9) Flashed custom recovery and custom rom again (we will never learn, will we???)
Hope this helped.
Click to expand...
Click to collapse
Yeah, Odin saved the day. A simple flash got the phone going again without the problems that you had with the phone getting stuck at the boot logo. But yeah, we never learn; immediately flashed Philz 6 and Temasek's CM11.
Hey guys
I got really annoyed by not being able to delete photos in Google Images, so I decided to root and fix it.
Now, after having my data wiped in the process of opening the bootloader (had to register on LG dev, etc), I am stuck on the last step - I can't get into TWRP to flash supersu.
I flashed it with the fastboot flash recovery command, but then after doing fastboot reboot, and then using adb reboot recovery, I get into the stock recovery.
I found two fixes, none of which work:
1. after flashing TWRP, turn off, then use HW buttons to get into recovery. On the fifth try, I got to the "erase all data" screen, which allegedly should be ignored. So I ignored it, and it erased all my data again
2. use fastboot boot command to boot TWRP directly. Doesn't work, I get an "unknown command" error.
Any other ideas how can I proceed to rooting my V10 (H960A) would be much appreciated.
Are you sure that you are using the command right for flashing the TWRP?? That should be something like: fastboot flash recovery recovery.img
recovery.img --->twrp
Also you get information whether flashing the recovery was successfull or not. Read the output in the coomand window carefully. Maybe you can post a screenshot or at least the returned message.
Here's a screenshot after going through the process again:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Hi,
flashing the recovery seems ok. Afterwards it seems vitally important that you switch off your phone, otherwise the recovery will be replaced by the stock revovery. Only after flashing SuperSu TWRP will be persistent.
Quote from the TWRP install instructions:
As on Marshmallow some fastboot commands are not working and LG is restoring recovery on every boot (so you cant use "adb reboot recovery" right now) you need to use one trick.
DO NOT REBOOT YOUR PHONE.
When still in fastboot from step 3 you need to turn off your phone completely. You can do that by holding power button or if that is not working take the battery out.
Now (put the battery in) and press POWER + VOL DOWN buttons. When you see LG logo release the POWER button (while still holding VOL DOWN) and press POWER button again. You should see a screen which is asking you if you want to factory reset your phone. Don't worry - if you made everything correctly it should not wipe your phone.
Use volume and power buttons to choose YES (twice) - and you should see a TWRP screen (after a while)
WARNING: IF YOU REBOOTED YOUR PHONE AFTER FLASHING RECOVERY THIS STEP WILL REALLY ERASE ALL DATA. You need to flash recovery again (step 3)
Click to expand...
Click to collapse
Also you tried to boot with the recovery image which is also not supported by LG.
I suggest you just flash TWRP again and do not try to reboot into recovery via fastboot command. Instead remove the battery right after flashing TWRP, wait a couple of seconds and put it in again. Then boot into recovery using the button combination decribed above.
I followed these steps three times with my phone (after updating the firmware) and it worked fine every time.
I tried it again and now I got through the whole rooting process.
Now I got stuck on the "Your device can't be checked for corruption" screen, which has been showing up on every boot since unlocking bootloader between the two animations, but now it's been there for a few minutes already.
Now what do I do?
****e, looks like I deleted my OS, while trying to wipe stuff in order to get through the boot freeze.
EDIT: I reinstalled stock ROM. Any ideas why it got stuck after rooting?
EDIT2: Installed the wrong ROM (some Tmobile branded version). Are there any custom ROMs for H960A running MM?
Hi,
no there are currently no Custom Roms for the H960A.
BTW: You will also get the "Your device can't be checked for corruption" screen with the correct ROM version. This is just a reminder popping up after bootloader unlock. After a couple of seconds the normal boot sequence will start.
I know, but the software version number now says H90110c
Also it's running 5.1.1. I can handle not having Nougat, but not back to 5.1 again...
I am searching for a way to get back my stock MM ROM, but there are apparently no ZIP or even kdz versions that work on the internet
Any help would be appreciated.
Yes, there are Android 6 kdz files for the H960A available, even in this forum:
http://forum.xda-developers.com/lg-v10/general/kdz-download-lollipop-kdz-10c-lg-servers-t3332348
Make sure you select the correct H960A version as there are two available: Europe and United Arab Emirates.
If the download does not work when you click on a link click it with the right mouse button select "copy link" (or similar, exact text depends on browser). Then open a new browser tab/windows and paste the link in the address field. Now the download should work.
You need to flash the kdz with LGUP.
In your case I would recommend the "REFURBISH" option in LGUP as it makes sure that the phone is completely wiped and reset.
As the refurbish option normally only allows tot-files to be selected you need to use a little trick. The below instructions are quoted from the LGUP thread (http://forum.xda-developers.com/g4/help/lgup-install-kdz-mm-lp-t3249803). Please look there if you need further information. You don't need to do the changes in the prop-file described at he beginning of the instructions. If you have not installed LGUP yet you'll find it in that thread as well.
TO DO A FULL WIPE AND INSTALL MM - Open the LGUP on your computer.
Select the option "update" (if not already selected).
FILE PATH: point it towards the MM KDZ file.
IMPORTANT!!!!!!! shut down LGUP!
Now open LGUP again - you will notice that the MM KDZ will still be showing in the FILE PATH section. Select REFURBISH and make sure BIN file is ticked. Press Start. Make cup of tea and be patient
Click to expand...
Click to collapse
Unfortunately, the downloads in that forum don't work, even after copy/pasting the link into Chrome, FF, even MSE...
I got two different kdz files from somewhere on the internet:
Europe H960A20a_00_0316
H960A10c_00_1224
None of them work. I got an error during the initialization phase saying the kdz file is incorrect.
Maybe it's because it says H90110c under version (as I said, I managed to install the wrong ROM after wiping everything)?
This is a nightmare. Please help
First of all, my phone isn't rooted and knox is not triggered.
Today I rebooted my mobile phone because the app adhell wasn't working properly and after that my phone got stuck in the boot loop (samsung letters in the screen).
I've tried wiping the cache and flashing the firmware again with ODIN, didn't work. I can't enter to the safe mode and erase adhell neither. Samsung smart switch doesn't recognise my device so I can't use it.
I run out of ideas, what else can I do to get out of the loop without erasing all the data in the phone?
Thanks in advance.
Same thing here, after update (official from samsung), Mine is stuck in a bootloop too.
Anyone, please help?
---------- Post added at 09:31 PM ---------- Previous post was at 09:29 PM ----------
Same thing here...
If Adhell is the cause, then fixing the bootloop is just as simple as removing it. As for how you go about fixing it, you have a few options.
1) Returning phone to store bought from if still under warranty and getting them to help. They'd most probably wipe it or replace it.
2) Full reset wiping data you don't have backed up
3) Custom recovery that lets you delete the files manually, but will probably trip KNOX
You could always try booting into recovery and see if your PC picks up your phone, then backing up what you can from there. But again, that might not be an option because stock recovery. TWRP lets you access files from your PC, but again trips KNOX.
ProdigyThirteen said:
If Adhell is the cause, then fixing the bootloop is just as simple as removing it. As for how you go about fixing it, you have a few options.
1) Returning phone to store bought from if still under warranty and getting them to help. They'd most probably wipe it or replace it.
2) Full reset wiping data you don't have backed up
3) Custom recovery that lets you delete the files manually, but will probably trip KNOX
You could always try booting into recovery and see if your PC picks up your phone, then backing up what you can from there. But again, that might not be an option because stock recovery. TWRP lets you access files from your PC, but again trips KNOX.
Click to expand...
Click to collapse
The phone is not under warranty and I don't have any data backup. How can I install the TWRP recovery in the situation I am now?
Now it doesn't enter to the recovery mode, and I didn't do anything new.
polema said:
The phone is not under warranty and I don't have any data backup. How can I install the TWRP recovery in the situation I am now?
Click to expand...
Click to collapse
First off, download SkipSoft Toolkit, go through the options it gives you until you're on the model of your phone and Android version. Then if you haven't already installed the drivers, do it. SkipSoft has the ones you need there. SkipSoft also downloads all the files you need to root, to flash TWRP, has a stock recovery if you mess up or want to return to stock for whatever reason after.
Then select the option to flash a custom recovery and root. You don't have to root, it won't do it automatically, that's something you have to flash yourself inside of TWRP if you want to. If you do want to root, look into Magisk. It lets you still use apps that normally don't work on rooted devices (it doesn't trip SafetyNet).
As for flashing the recovery, there's a wall of text that SkipSoft gives you to read which I'd recommend going over to make sure you know what you're doing. If you screw up, 99% of the time there is a fix for it so don't panic.
If all goes well, you should see TWRP loading up when you boot into recovery. Then when you connect your phone to your PC, it should appear as normal and you can copy any files you want to back up. TWRP has a Wipe option that will completely clear all installed apps, all app data, any setting changes and set your phone back to stock without deleting the files you have on it to save you from having to copy them all back again after. I'd also recommend making a complete backup of everything through the option in TWRP at that point for future security, and just in case you want to root.
If you have any more questions, just ask. I don't have an answer for everything, but I'll try my best.
ProdigyThirteen said:
First off, download SkipSoft Toolkit, go through the options it gives you until you're on the model of your phone and Android version. Then if you haven't already installed the drivers, do it. SkipSoft has the ones you need there. SkipSoft also downloads all the files you need to root, to flash TWRP, has a stock recovery if you mess up or want to return to stock for whatever reason after.
Then select the option to flash a custom recovery and root. You don't have to root, it won't do it automatically, that's something you have to flash yourself inside of TWRP if you want to. If you do want to root, look into Magisk. It lets you still use apps that normally don't work on rooted devices (it doesn't trip SafetyNet).
As for flashing the recovery, there's a wall of text that SkipSoft gives you to read which I'd recommend going over to make sure you know what you're doing. If you screw up, 99% of the time there is a fix for it so don't panic.
If all goes well, you should see TWRP loading up when you boot into recovery. Then when you connect your phone to your PC, it should appear as normal and you can copy any files you want to back up. TWRP has a Wipe option that will completely clear all installed apps, all app data, any setting changes and set your phone back to stock without deleting the files you have on it to save you from having to copy them all back again after. I'd also recommend making a complete backup of everything through the option in TWRP at that point for future security, and just in case you want to root.
If you have any more questions, just ask. I don't have an answer for everything, but I'll try my best.
Click to expand...
Click to collapse
Thanks for all the help.
I have android 7 nougat in my phone and it's not among the options, what should I do?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
polema said:
Thanks for all the help.
I have android 7 nougat in my phone and it's not among the options, what should I do?
Click to expand...
Click to collapse
Update SkipSoft, recent version is 1.5.6, 7.0 is in that version.
If you can't update for whatever reasons, you can manually download the TWRP files from here and drop those into C:\Unified_Android_Toolkit\recovery\GalaxyS6Edge, then select any version of Android and follow what it says. Just don't flash the root it provides, use Magisk as I said before.
polema said:
Thanks for all the help.
I have android 7 nougat in my phone and it's not among the options, what should I do?
Click to expand...
Click to collapse
You still having trouble with this?
Finally I managed to repair the phone with smart switch, I've lost my photos/videos but the rest was saved in samsung cloud.
polema said:
Finally I managed to repair the phone with smart switch, I've lost my photos/videos but the rest was saved in samsung cloud.
Click to expand...
Click to collapse
Hi, I am having the same problem as you since yesterday afternoon where it's stuck in a boot loop, my notification light was blinking so when I went to check on it the phone was turned off but the light was still blinking, the light only stopped after the battery drained completely. when I tried to turn the phone on after charging it, it's still stuck in a boot loop, only thing I can do is hold the volume down, power, and home button down to enter the "downloading do not turn off target screen." I downloaded smart switch on my laptop last night to see if I can fix my phone through that but it says unsupported device, and when I try emergency software recovery and initialization option when I enter model name and S/N number and click OK the program closes and nothing happens. polema what did you do to fix your device?
abhi821 said:
Hi, I am having the same problem as you since yesterday afternoon where it's stuck in a boot loop, my notification light was blinking so when I went to check on it the phone was turned off but the light was still blinking, the light only stopped after the battery drained completely. when I tried to turn the phone on after charging it, it's still stuck in a boot loop, only thing I can do is hold the volume down, power, and home button down to enter the "downloading do not turn off target screen." I downloaded smart switch on my laptop last night to see if I can fix my phone through that but it says unsupported device, and when I try emergency software recovery and initialization option when I enter model name and S/N number and click OK the program closes and nothing happens. polema what did you do to fix your device?
Click to expand...
Click to collapse
Flash stock firmware through Odin.
Or try boot your phone to recovery mode (up home and Bixby. If it boots to recovery plug to pc and see if smart switch recognises it.
callumbr1 said:
Flash stock firmware through Odin.
Or try boot your phone to recovery mode (up home and Bixby. If it boots to recovery plug to pc and see if smart switch recognises it.
Click to expand...
Click to collapse
I forgot to mention my phone is a samsung galaxy s6 edge, also I tired the recovery mode but it still does the boot loop. Are there clear instructions to flash stock firmware through Odin?
abhi821 said:
I forgot to mention my phone is a samsung galaxy s6 edge, also I tired the recovery mode but it still does the boot loop. Are there clear instructions to flash stock firmware through Odin?
Click to expand...
Click to collapse
What android version is it and what region and model? Tell me these and I'll post the firmware with the steps to flash.
callumbr1 said:
What android version is it and what region and model? Tell me these and I'll post the firmware with the steps to flash.
Click to expand...
Click to collapse
I got my phone through AT&T in USA model is SM-G925AUCU1AOCE and I not sure what android version I have.