Hi, I recently bought this new phone (Galaxy A50) from the official Samsung Store (11/7). The phone came with a software version:
PDP: A505FDDU1ASBD
CSC: ASB7
Security Patch: 1 February 2019
After sometime, I decided to start rooting my Galaxy A50 following the steps in a thread on XDA (created by @geiti94). Unlocked my bootloader and rebooted to the system, I setup the phone without my Samsung and Google Acc, and I switched off the phone then entered the download mode. I put the TWRP Magisk Patched file at the AP section in Odin and unticked everything except Flash Lock. Warranty void (Knox tripped). Everytime I restarted the device, I have to boot rooted with Magisk (Recovery) or else I will lose magisk. It turned out to be true and bricked my device:
"Only official released binaries are allowed to be installed".
I then downloaded the stock firmware files (ASBD) from Sammobile.com and reflashed it back to the device. Success flashing stock without any problem then I set up the device, plugged in and went to sleep. I didnt know what did happen while I was sleeping and when I woke up, my phone had the OVERHEATING WARNING (device was hot) and the system was already switched off my device automatically. I took off my phone casing and I found out that my phone casing was wet. I didnt know where the water came from and I didn't even know when it got there. I'd never thought that the water could flow into the phone since it was very little. I switched on my device without hesitation. Right after it switched on, moisture has been detected in my usb port. I switched on the device and took out my sim card and ext mmc, I put it in front of the fan and let it sit for like 5 hours. The phone was okay. Phone rebooted normally and I didnt face any unusual behavior from my device.
Within 30 minutes of using the phone, I received Device Overheating Warning again, apps were closing and device was shutting down (physically the device wasn't really hot). It was warm. I let it cool and I received no more overheating warning. Suddenly, the device was being abnormal. It went to:
1. Screen locked itself and display lockscreen. I unlocked it back and it locked itself back. It happens frequently.
2. Screen locked itself and display lockscreen and the screen will on off like something was playing with the power button. It got crazier when I tried to charge the device, the 'display on off' went faster. Then, i could no longer use my power button to unlock since device didnt let me get to my unlock screen.
When it happened, I couldnt shut down my device using the normal way. I had to hold my power button and (-) volume button to restart my device. Device rebooted, 3 minutes and it went strange again.
I was frustrated and clueless. Went into safe mode and getting the same result. I tried reflashing the firmware again and it was being normal until i finished device setup then it happened again. I thought it happened because I tripped my Knox.
Tried different method. This time I downloaded and flashed stock firmware (A505FDDU2ASH3).
PDP: A505FDDU2ASH3
CSC: A505FDDU2ASH1
Security Patch: 21 August 2019
And same issues occured. This time:
1. From getting locked itself and display will 'on off', this time it eventually went locked itself (noticed 'screen lock sound') and nothing i could do to unlock it because the power button had no function! But I could reboot manually by holding (-) volume and power button! Stock recovery mode everything was okay. Display, power button and volume up and down button is okay. No issue in that mode.
2. Attempted factory reset and tried setting up again. Right after it displayed 'Phone is starting' it locked itself again. Reboot again. I quickly swiped my finger trying to not let it locked itself again. It worked and prevented the device from locking again. I realized that my UI didnt respond when I used the volume button to increase/decrease the volume. Power button only responded to lock screen and didnt respond to unlock it back but the device was still on.
Since Knox had tripped, I tried another solution. I rooted the device just like how I done it before. I still believed that it was firmware error not caused by any faulty in my hardware component. I installed TWRP w Magisk Patched, multidisabler, and flashed a stable custom kernel (SkyKernel V1.2 by @AlexGeek3) that worked w my device, and yes device worked normally. Magisk installed. Safety net verified. I disabled some pre installed Samsung Apps and Services (e.g. Find My Mobile and screen lock service) that maybe would be the caused. Just when I set up my Google Acc, the issues occured again. When I checked my CPU and battery temperature using kernel tweaker (installed alongside SkyKernel V1.2) and noticed that the temperature reading was so high (70°C-90°C) but device wasnt even hot. This had become very strange ?
Then I decided to bring it to the mobile repair shop. He said it may happened when I downloaded the firmware files using Mobile Data, so the files downloaded weren't accurate since the network is unstable and told me to bring it to the Samsung Service Center. Then I tried to get help from Samsung Official:
1. Chat through Live Support: He told me that Sammobile.com wasn't authorized by Samsung. He told me that maybe hardware faulty issues because it had contact with water. Told me to bring it to Samsung Service Centre.
2. Called Samsung Hotline: She told me it happened when device had been root. And nothing I could do to unroot it back and asked me to go to Service Center instead.
3. Called Samsung Hotline: He told me that it might occured since I downloaded the files using Mobile Data and even that I had successfully flashed the firmware, the problems existed because the downloaded files had corrupt. He told me to just go to official service centre and tell them to flash the official stock firmware and check if the issues persisted.
4. Called Samsung Hotline: He told me since device had been rooted, warranty was voided and there would be NO WAY TO UNROOT THE DEVICE. Hence, I would have to replace the motherboard to be able to use the device again.
Each time I called the hotline, I spoke to a different staff. I explained thoroughly to each of them the issues I was currently facing at the moment and how/when it started to occur. All of them had a different explanation and the same solution. I called them again & again because I wanted to find the most least solution I could find to the major solution to fix the device. I was trying to make sure if the issues still happen after clean flash install official stock firmware, only then I will take further actions to check on my hardware.
Concluded myself to bring it to the Samsung Service Center and flash the official stock firmware for my device. (60 Km away from my place). I called them a day before going to the SSC to ask about the process and cost to do it. Next day I went to the SSC. Cut it short, I explained to the staff from the beginning. I wasnt really satisfied because she didnt pay attention to what I was explaining. And because of that, she printed out the agreement and asked me to sign it. I read it patiently and I was confused when I looked at the Details of Problems section and my warranty status was still VALID but device stated that my Warranty was already voided ?
Problems: Phone can't switched on. Scratch on the side housing. Water damaged.
I looked at her again and asked her if she really confirm about the problems. She said that the technician will check the hardware and told me to wait an hour for them to check the hardware. She called me again within 1 hour and I was really disappointed by the fact that they said my hardwares were water damaged and the repair cost is 3/4 the price if I buy a new same device. If that would be the cost, it would really better if I just buy a new phone ? I disagreed for it and asked if they could reflashed the official firmware for my device. She said yes but my warranty status will be discontinued, and they would take no responsibility if the problem still occured. But if I agree w them to repair it and pay 3/4 for the replacement, my warranty will be extended ? such a an idiotic way to make your customer pay you such costs.
W/out further due I told them to reflash/clean installation full official firmware for my device and they kept repeating the same thing again that they took no responsibility blablabla and I just nah just do it la haih ? and ended the call.
Arrived SSC later after 30 mins, I thought that they had done the job. No. Another disappointment, most stupidest reason that I had to accept from them. They were telling me that if I flash the official firmware, my warranty will be voided and they take no responsibility for it. What the heck? I already allowed them to do so, and that was the reason why I came to the SSC, and even my warranty was voided because I had tried customization using unauthorized firmware for my device. I asked them to take a picture of my device hardware or maybe bring it to me because I wanted to have a look at it but they denied my request (That repair cost is to replace new motherboard, new usb charging port, new lcd display and new battery).
Exhausted, angry, and disappointed by them, I requested them once again to flash the official firmware and I didn't care about what would happen afterwards. They told me to wait a couple minutes until their technician completed the flashing process. Such an utter bull****, they told me that my device couldn't being detected by the PC since my USB Port was damaged. I took the device, left with frustration. I have wasted my time, energy and money and didn't even get what I wanted.
To sum up everything:
Samsung Service Centre:
1. SSC: Phone couldnt boot/switched on.
Truth:
But even until today I still can switch on my device.
2. SSC said the charging port had been damaged but until today I still can charge the phone. Its only couldn't be charged when it is switched on because device will detect overheating and stopped the charging progress.
3. SSC: Charging port is damaged so USB data transfer to the PC cannot be used. PC won't detect device.
Truth:
But still, up until this day I could still make a data transfer, flash firmware using odin.
4. SSC: LCD Display is damaged thats why it doesnt display correctly.
But recovery mode and download mode didnt have the same issues only. Issues happen when device boot the system.
Firmware:
1. Firmware wasn't downloaded correctly using Mobile Data.
2. Security services provided by Google and Samsung could be the reason.
3. Knox had tripped (e-fuse) and forced the firmware to crush itself causing damage to the system. (I am not sure abt this, based on what I had read)
4. Replace a new motherboard because the current motherboard could no longer be used after device has been rooted (?)
Hardware:
1. The water may have caused little damaged to the hardware.
2. Flex cable connectors (LCD Connector, Charging Connector, Power/Volume Connector) need to be replaced.
3. Check the CPU and properly apply a thermal paste and check if the problems solved.
Any help is really helpful and appreciated ???
that's one wall of text if i ever seen one.
post a very concise tl'dr at the bottom if you want people to help my man
who tf gon read this mf frfr ??
Hi,
A sensor will probably have been damaged, since the A50 does not have any IP protection in that case I cannot help you
hi guys
I need help. I have a galaxy a50 with firmware version as A505FDDS9CUI4(android 11) but recently after an OTA update I have started getting issue where in the device restarts automatically and sometimes even gets stuck in the booting process. So I thought of downgrading the device for fix but I am not able to downgrade as the firmware that I wanna downgrade to, is A505FDDS7BUB5(android 10) and the binary number for both the firmwares is different so I am getting error in odin. So if I root my phone and install custom recovery(TWRP) and flash custom rom, will it work? or will it get bricked in the process? is there any way that can fix this issue because as of now samsung has not recognised this issue officially and many other samsung device owners of A and M series are facing this issue. Any help would be appreciated guys. Thanks.
Related
Hi,
My Sony Xperia Arc S (LT18a) has been stuck in SAFE MODE, i.e. none of the apps installed explicitly from Google Store are showing up. Only the ones those are default with the handset are working. Apart from this, the phone is working perfectly fine.
Though, the Menu key isn't working at all.
About 2 weeks back, it started with flickering of the menu options as if the menu key has been stuck. So I restarted my phone and since than it is in safe mode.
NOTE: The phone was bought from US and is currently being used in India since around 1 year. Also, the phone was upgraded to ICS using Sony PC companion.
Here are the things that I've tried:
1. Taking the battery out for sometime and than trying rebooting.
2. Rebooting the phone with Volume Down key.
3. Rebooting the phone with Volume Up key.
4. Rebooting the phone with Back key.
5. Reseting the phone to Factory Settings
and ...
6. Taking it to SONY Service Centre.
NONE of the above has been a success.
The Sony Service Centre guys kept the phone for 3 days and I guess that they must have checked the hardware for any faults, but didn't reported any. They updated/flashed the software and the phone started working (NOTE: they MENU key also started working in normal mode, so it might not be a hardware issue) but its again going back in the Safe Mode. And they don't know why. Moreover they told that USB cable is not detecting my phone, so it took them more time to flash it. Since they couldn't help further and they returned it back.
(The phone is getting detected by USB on my machine though)
Am I left with any other options that I could try? Any help would be great.
Somebody asked me to Try the Update Service executable from Sony website.. Will let you guys know if it worked.
I'm not sure about India's laws, but in certain countries, law says, that if the repair is not finished and problem still exists, you may proceed to file a complaint against them towards certain agency. As I said, I am not sure, if such things exist outside EU.
Now, if you said that Menu button does not work even after repair nor flashing firmware, then it is hardware level issue, which means you can not do anything about it.
Well, first of all many thanks for your reply.
The law do exists over here too, but since this was bought from US and I tried to get it repaired with the Indian service center; they might not consider it as case an International warranty (or support) kind of a thing.
My model is LT18a (a for America), where as their International version of Arc S is said be as LT18i. Not sure if I can file any complaint for this.
I'll check that scenario.
BTW, I think you missed it:
"They updated/flashed the software and the phone started working (NOTE: they MENU key also started working in normal mode, so it might not be a hardware issue) but its again going back in the Safe Mode."
Someguyfromhell said:
I'm not sure about India's laws, but in certain countries, law says, that if the repair is not finished and problem still exists, you may proceed to file a complaint against them towards certain agency. As I said, I am not sure, if such things exist outside EU.
Now, if you said that Menu button does not work even after repair nor flashing firmware, then it is hardware level issue, which means you can not do anything about it.
Click to expand...
Click to collapse
Phone goes into Safe Mode only, if Menu button is pressed during boot. If you are not pressing it, it is hardware level issue, because it does detect the press, although not being pressed.
Well, I'll ask the Service Center guys to give it another try with the hardware thing (which might be the root cause of it), but was just curious to know how things became normal (for a while) when they flashed my phone?
Someguyfromhell said:
Phone goes into Safe Mode only, if Menu button is pressed during boot. If you are not pressing it, it is hardware level issue, because it does detect the press, although not being pressed.
Click to expand...
Click to collapse
BlindDreamz1091 said:
Hi,
My Sony Xperia Arc S (LT18a) has been stuck in SAFE MODE, i.e. none of the apps installed explicitly from Google Store are showing up. Only the ones those are default with the handset are working. Apart from this, the phone is working perfectly fine.
Though, the Menu key isn't working at all.
About 2 weeks back, it started with flickering of the menu options as if the menu key has been stuck. So I restarted my phone and since than it is in safe mode.
NOTE: The phone was bought from US and is currently being used in India since around 1 year. Also, the phone was upgraded to ICS using Sony PC companion.
Here are the things that I've tried:
1. Taking the battery out for sometime and than trying rebooting.
2. Rebooting the phone with Volume Down key.
3. Rebooting the phone with Volume Up key.
4. Rebooting the phone with Back key.
5. Reseting the phone to Factory Settings
and ...
6. Taking it to SONY Service Centre.
NONE of the above has been a success.
The Sony Service Centre guys kept the phone for 3 days and I guess that they must have checked the hardware for any faults, but didn't reported any. They updated/flashed the software and the phone started working (NOTE: they MENU key also started working in normal mode, so it might not be a hardware issue) but its again going back in the Safe Mode. And they don't know why. Moreover they told that USB cable is not detecting my phone, so it took them more time to flash it. Since they couldn't help further and they returned it back.
(The phone is getting detected by USB on my machine though)
Am I left with any other options that I could try? Any help would be great.
Click to expand...
Click to collapse
Flash it with stock firmware using flashtools. if it is hardware error cant help. if not flashing always helps
I have been using my n2 for 1 year. but, I found my note 2 not turning on two days back. I just kept it fully charged and the next morning its not turning on. It was first stuck on the boot logo. then, I pulled the battery out and try to factory reset from stock recovery. but, I couldn't enter. then I tried installing the stock rom via odin. but, no luck. my android version was 4.1. can anyone tell me where is the problem and how I can solve?
oh one thing, now its not even turning on. just going to download mode. if I connect it to charger a battery icon shows up with a refresh circle on middle.
Sorry for hear that, mine have died on Sunday night u_u after flashing Agni kernel but I don't think the fault was for the kernel, the days before flashing it was already showing an erratic behavior like freezing and rebooting by it self. I thought it was because an undervolt or something like that (some custom roms do it) so i tried changing the kernel =( to see how it will die.
I took my phone to an external service center on yesterday morning (It doesn't have warranty anymore), and there they used Riffbox and Jtag to trying come back to life :laugh: and it worked for a couple of hours. They told me it had the bootloader bricked. I have my doubts because I have not even touched the bootloader just once when I rooted it after bought It (if it was touched after it, should be on an update or custom rom flashing, I don't know).
But last night was died again, so I started to search on web and I found this SDS, all the stuff described are the same that my phone suffered (but It was on 4.3 Ditto Note 3 soooo I though it was already solved since 4.1.2).
Is very sad but now I'm going back to the Service Center to tell them what I found. Maybe they will need to change the emmc or the motherboard =S I hope it doesn't cost a lot.u_u
Whatever, maybe yours one can have the bootloader broken, because yours turn on into download, mine doesn't turn on to recovery/samsung logo/download. Perhaps you can have luck and a chip solution just trying to flash another bootloader with odin and if you can get back working your Android, don't forget to download the "emmc check" app from playstore. It will give you any clue about this, if it says your emmc is vulnerable you will need to do the same as me changing emmc or motherboard but if you have luck and says it is not a bad batch you will no have problems again just flashing a good bootloader.
Service Center in Slovenija
badtzo said:
Sorry for hear that, mine have died on Sunday night u_u after flashing Agni kernel but I don't think the fault was for the kernel, the days before flashing it was already showing an erratic behavior like freezing and rebooting by it self. I thought it was because an undervolt or something like that (some custom roms do it) so i tried changing the kernel =( to see how it will die.
I took my phone to an external service center on yesterday morning (It doesn't have warranty anymore), and there they used Riffbox and Jtag to trying come back to life :laugh: and it worked for a couple of hours. They told me it had the bootloader bricked. I have my doubts because I have not even touched the bootloader just once when I rooted it after bought It (if it was touched after it, should be on an update or custom rom flashing, I don't know).
But last night was died again, so I started to search on web and I found this SDS, all the stuff described are the same that my phone suffered (but It was on 4.3 Ditto Note 3 soooo I though it was already solved since 4.1.2).
Is very sad but now I'm going back to the Service Center to tell them what I found. Maybe they will need to change the emmc or the motherboard =S I hope it doesn't cost a lot.u_u
Whatever, maybe yours one can have the bootloader broken, because yours turn on into download, mine doesn't turn on to recovery/samsung logo/download. Perhaps you can have luck and a chip solution just trying to flash another bootloader with odin and if you can get back working your Android, don't forget to download the "emmc check" app from playstore. It will give you any clue about this, if it says your emmc is vulnerable you will need to do the same as me changing emmc or motherboard but if you have luck and says it is not a bad batch you will no have problems again just flashing a good bootloader.
Click to expand...
Click to collapse
Service Center in my country told me, that i have modified the software and that there is no warranty to it even if it was SDS, for which they know...
New motherboard and that's it...:crying:
U should have done factory reset by stock recovery and bring binary count to 0 by that. I had same problm. Went to service centre there they told to replace motherboard which was almost costing very high. Luckily I had made everything on phone normal before going to service centre so I had done all in warranty《free》
Sent from my GT-N7100 using XDA Premium 4 mobile app
starlut said:
I have been using my n2 for 1 year. but, I found my note 2 not turning on two days back. I just kept it fully charged and the next morning its not turning on. It was first stuck on the boot logo. then, I pulled the battery out and try to factory reset from stock recovery. but, I couldn't enter. then I tried installing the stock rom via odin. but, no luck. my android version was 4.1. can anyone tell me where is the problem and how I can solve?
oh one thing, now its not even turning on. just going to download mode. if I connect it to charger a battery icon shows up with a refresh circle on middle.
Click to expand...
Click to collapse
if you can go into download mode try flashing a stock rom via ODIN and report back. If it says NO PIT PARTITION in ODIN then you need to flash the pit file and then a stock rom .
zeeshanonlyme said:
if you can go into download mode try flashing a stock rom via ODIN and report back. If it says NO PIT PARTITION in ODIN then you need to flash the pit file and then a stock rom .
Click to expand...
Click to collapse
i tried to flash the stock rom. its not flashing the kernel. and, I don't know whats wrong with it.
I don't have warranty and I am stuck in it.
aNtRx said:
Service Center in my country told me, that i have modified the software and that there is no warranty to it even if it was SDS, for which they know...
New motherboard and that's it...:crying:
Click to expand...
Click to collapse
Sorry to hear that, but they told you nonsense. If it's really SDS they have to repair for free. Ask a friend in your country who is envolved in legal things, a lawyer best.
One in general: As long as one can start eg. download mode, it is no SDS, mostly a software prob.
Hi!
So earlier today I was using the phone as usual and I decided to update some apps because I had wifi available for once.
I go to the Xposed installer and updated a youtube addon and Gravitybox, about 20 seconds later the phone freezes and turns off (before I even get to reboot myself).
Since then it continues to bootloop - I try to access TWRP and the phone just freezes on the kernel bootscreen, or restarts.
My computer won't recognize the phone and there's nothing I can do.
Sometimes my phone actually goes further than just the kernel bootscreen, it acctually boots the system, but it always freezes before I get to do anything (but the time is random)
Although the phone doesn't freeze when I'm in the recovery menu (the white one, but as soon as i click yes for twrp, it gets stuck)
I have a regular H815, BL is unlocked and im using the Genysis Rom. (Marshmallow)
What I've tried:
Access TWRP through ADB
Access TWRP through the phone ( vol down etc)
Access Download Mode, computer won't recognize the device.
Boot normally.
Remove SD/Sim and do the above.
I'm stumped guys. So I came here. Any help would be apprecieted.
Deciding to bump this popular thread by updating my progress.
I managed to make download mode work, I flashed a KDZ matching my current rom, it was successfull according to the LGUP program, but the phone is still rebooting, I cleared data, but it's still not booting up.
I later tried downgrading and wiping the whole phone. Flashed the original rom i had when I bought the device... The screen with Lg and (Bootloader is unlocked) is still the only screen I get, anything I do doesn't seem to work and I'm starting to lose hope.
Although I've noticed, that everytime I flash KDZ, it still shows the same rom of origin, even if i just flashed another, meaning the flash wasn't effective. Is there any other programs than LGup? the LG flashtool won't find it, although Up will
It seems like the phone broke completely, yet it's still actually starting up. After googling I found that there was a common flaw with it actually bootlooping because of hardware issues - which I'm starting to think is the issue.
What S/N is it? ..if its starts with 505-509 it definitely has the hardware problem that causes the device to bootloop which you can read about in reddit(there are tons of reports there) also by quick searching in this same forum you can see threads of report of same issue... this is a known issue and LG themselves announce that there was a solder of some kind that causes the bootloop...if its still on warranty I suggest you go with that. They usually change the mobo itself to latest 601-60* and probably the screen if your having burn ins on the lcd..goodluck
innocence07 said:
What S/N is it? ..if its starts with 505-509 it definitely has the hardware problem that causes the device to bootloop which you can read about in reddit(there are tons of reports there) also by quick searching in this same forum you can see threads of report of same issue... this is a known issue and LG themselves announce that there was a solder of some kind that causes the bootloop...if its still on warranty I suggest you go with that. They usually change the mobo itself to latest 601-60* and probably the screen if your having burn ins on the lcd..goodluck
Click to expand...
Click to collapse
It's definetly a 505... lol.
y bootloaders been unlocked, meaning warranty is void. How would you reccomend hiding the fact its UBL?
Perhaps I could dirtyflash it with the wrong kernel, making it completely bricked. And just cluelessly leave it for warranty, but although I feel like that's a risk.
As far as I know there is no going back once you Unlock your bootloader and no warranty will be given whatever you do as IMEI of your phone is sent to LG when you unlock the device thru their site so when you do claim your warranty they will check to see if yours are unlock/lock. If you still push for a warranty they will charge you 200-250 dollars(estimated cost in our country) for the mobo replacement. Friendly advice, since its a paperweight now you could just sell it on ebay for 80-100 so dollars and buy a new phone.
Well, my GF's G4 started bootlooping a few days ago, the local store she bought it from doesn't honor the warrenty and says it may be something we did. I didn't like hearing that and decided to take legal action.
In the meanwhile, she asked if the data can be restored, I started playing with it and reading online. The phone bootlooped anytime I took the battery out and reinserted it, then go off. I decided to put it in the freezer after reading about many successful attempts to boot the device. The first time I put it in a plastic bag for 5-10 minutes (when I took it out it had humidity on it which I wiped), it turned on! and went into Android app optimization and we were thrilled, It went off after 2 minutes so I decided to put it in again for 30-40 minutes in a sealed plastic bag (as many recommended), when I took it out it didn't turn on at all no matter how many tries I tried switching batteries, connecting to the charger etc. (it had humidity on it again when taken out of the freezer).
From then on, the phone won't turn on at all, I put it in a bag of rice in get rid of humidity/water but that didn't help and the device won't bootloop at all.
Now, I have no case as it doesn't bootloop and the store can claim there's damage not governed by warrenty, I can't claim it bootloops as it is a brick.
I'm worried the water caused corrosion which totally cancels her warrenty.
Hope someone can help me fix this out, cant believe I hope it will bootloop again.
Thanks.
What version of G4 have you ? H815 ? or other ?
you can try to flash official firmware with LG UP with .kdz file or if you have another G4 with .tot file
You must have computer with drivers installed and LG UP installed
Watch tutorial
It's H815, SN: 505***
How can I flash it if its not booting at all? Can you elaborate on how flashing the official kdz will help? The phone is not rooted.
Is there a way to restore the bootloop? I want to claim my warrenty but without the bootloop scenario Im screwd.
YSAndroid said:
It's H815, SN: 505***
How can I flash it if its not booting at all? Can you elaborate on how flashing the official kdz will help? The phone is not rooted.
Is there a way to restore the bootloop? I want to claim my warrenty but without the bootloop scenario Im screwd.
Click to expand...
Click to collapse
1. volume up and connect to pc
2. flash the "core disable" kdz/tot (whatever it is)
3. it should boot but it won´t be as fast as i has been
YSAndroid said:
It's H815, SN: 505***
How can I flash it if its not booting at all? Can you elaborate on how flashing the official kdz will help? The phone is not rooted.
Is there a way to restore the bootloop? I want to claim my warrenty but without the bootloop scenario Im screwd.
Click to expand...
Click to collapse
To be honest with you pal i very much doubt you'll get it back working as the serial is a 505 which means it's included in the bad batch of faulty motherboards on the phone and its that which is causing the bootlooping , you need to tell the place where you got it that the hardware has failed out of your control if they don't help try contacting LG directly you could be lucky....
YSAndroid said:
Now, I have no case as it doesn't bootl
Thanks.
Click to expand...
Click to collapse
When I did the following steps, I was able to get back into the phone with all my apps and internal data right where it was. It only fixed the corrupt system files. It seemed to work like startup recovery on Windows. But as a warning, I've only done this once so cannot guarantee you the same.
i) Make sure you have the LG Drivers installed from here: http://oceanhost.eu/e4h2px4e0hkd/LGM..._4.0.4.exe.htm
ii) Download the LG Bridge software from here: http://www.lg.com/us/support/product...reinstall-apps
iii) Remove the battery and reinsert it so the device it is fully off.
iv) While holding the up volume button, insert your USB cable.
v) You should enter download mode. Go to the Software Update tab of the LG Bridge. It will say connecting and then should say your device is up to date. Click on the recovery text on the bottom right and then follow the instructions. The software will download the system image for you and this is roughly 1.6GB so make sure your firewall doesn't block this connection.
I was lucky and this didn't remove any of my data.
If you have problems with LG Bridge detecting your device:
i) Make sure you have the drivers installed and are using a reliable cable and USB port.
ii) Open up device manager and look for your phone. It should be named [...... COM#].
iii) Right click and go to the ports tab and click advanced. Select COM41. This seemed to work for me.
So, My device got bricked. I didn't do root or anything. Recently the device got Android 7.1.2 update so I started the installation via OTA but (I DONT KNOW WHY) something gone wrong and the device gone into bootloop. My device was fully stock and had a locked bootloader but the device was still in 7.1.1 so I downloaded the 7.1.2 Update from the Google Developer page and sideloaded via ADB. The device finally rebooted into Home screen. So I was setting it up but suddenly it hanged and rebooted and the device was boot looped again but now its on a different case. Before, I was able to get the device back by Sideloading via ADB in recovery mode. But now when I tried to go into recovery mode the recovery mode DOESN'T EVEN APPEAR. It goes straight into the Google logo and goes to bootloop. Now I can't even access the recovery mode to sideload.
Please someone help
Dipto509 said:
So, My device got bricked. I didn't do root or anything. Recently the device got Android 7.1.2 update so I started the installation via OTA but (I DONT KNOW WHY) something gone wrong and the device gone into bootloop. My device was fully stock and had a locked bootloader but the device was still in 7.1.1 so I downloaded the 7.1.2 Update from the Google Developer page and sideloaded via ADB. The device finally rebooted into Home screen. So I was setting it up but suddenly it hanged and rebooted and the device was boot looped again but now its on a different case. Before, I was able to get the device back by Sideloading via ADB in recovery mode. But now when I tried to go into recovery mode the recovery mode DOESN'T EVEN APPEAR. It goes straight into the Google logo and goes to bootloop. Now I can't even access the recovery mode to sideload.
Please someone help
Click to expand...
Click to collapse
I believe you have the infamous bootloop issue.
Try to unlock bootloader if you can and flash everything manually. If that does not help, claim warranty or approach the place you purchased the device.
Dipto509 said:
So, My device got bricked. I didn't do root or anything. Recently the device got Android 7.1.2 update so I started the installation via OTA but (I DONT KNOW WHY) something gone wrong and the device gone into bootloop. My device was fully stock and had a locked bootloader but the device was still in 7.1.1 so I downloaded the 7.1.2 Update from the Google Developer page and sideloaded via ADB. The device finally rebooted into Home screen. So I was setting it up but suddenly it hanged and rebooted and the device was boot looped again but now its on a different case. Before, I was able to get the device back by Sideloading via ADB in recovery mode. But now when I tried to go into recovery mode the recovery mode DOESN'T EVEN APPEAR. It goes straight into the Google logo and goes to bootloop. Now I can't even access the recovery mode to sideload.
Please someone help
Click to expand...
Click to collapse
How did you manage to sideload without unlocking the bootloader?
Did you try just holding power and volume down while it was off until it booted and entered fastboot mode?
If you enter fastboot mode, use the arrow keys and power button to enter recovery mode.
ADB
Omnitrix4m3 said:
How did you manage to sideload without unlocking the bootloader?
Did you try just holding power and volume down while it was off until it booted and entered fastboot mode?
If you enter fastboot mode, use the arrow keys and power button to enter recovery mode.
Click to expand...
Click to collapse
I sideloaded via ADB in the recovery. But now the recovery wont even showing
indian84 said:
I believe you have the infamous bootloop issue.
Try to unlock bootloader if you can and flash everything manually. If that does not help, claim warranty or approach the place you purchased the device.
Click to expand...
Click to collapse
Ok the device suddenly boot up. I acted fast and unlocked the bootloader. But when everything is going fine. THE DEVICE BOOTLOOPED AGAIN. But now my bootloader is unlocked. So I flashed 6.0.1 it booted up and again bootlooped :crying:
Same here.
Are you part of the Beta program? Because I am, and after the latest "June 2017" update I suddenly started to have bootloops.
I can only reach bootloader but Recovery isn't starting at all, it just reboot and get into the loop again.
I've tried with the Nexus Root Toolkit, but the phone always get lost after the first reboot the toolkit requests to the device.
Any help here? It NEVER had any issues like that one, I've heard LG claimed it to be hardware related, but I got it after a software update.
This sounds like the infamous bootloop that many other people have encountered with the 5x. It is a problem with the actual hardware and isn't really permanently fixable by messing with the software. If your device is still under warranty, contact LG and they might be able to repair it. I had the infamous bootloop and they replaced the main board (free with warranty).
iSimon said:
Same here.
Are you part of the Beta program? Because I am, and after the latest "June 2017" update I suddenly started to have bootloops.
I can only reach bootloader but Recovery isn't starting at all, it just reboot and get into the loop again.
I've tried with the Nexus Root Toolkit, but the phone always get lost after the first reboot the toolkit requests to the device.
Any help here? It NEVER had any issues like that one, I've heard LG claimed it to be hardware related, but I got it after a software update.
Click to expand...
Click to collapse
LG never claimed it was a hardware issue for the 5X officially. Though due to some lawsuits they are extending the warranty on a case by case basis. The did acknowledge a hardware issue for the G4, which started production around the same time as the 5X.
What seems to happen is the later OS updates expose a hardware issue. Maybe by running a bit hotter. Some people, like me, had slightly reduced battery life after 7.1.2, which means the phone was drawing more power and heating up slightly more than before. My phone was on 7.1.2 for about 2 weeks before it just died while I was using it. Didn't seem to be a bootloop issue at first, but after fiddling around with it, and trying to fix it, that's what it ended up doing. Mine would never get into recovery either, until I used a hair dryer to heat the CPU on the motherboard since I didn't have a heat gun. I managed to reinstall the OS, but it took a heat gun to actually to get it to boot again. However, it lasted 9 hours then started bootlooping.
synesthete said:
This sounds like the infamous bootloop that many other people have encountered with the 5x. It is a problem with the actual hardware and isn't really permanently fixable by messing with the software. If your device is still under warranty, contact LG and they might be able to repair it. I had the infamous bootloop and they replaced the main board (free with warranty).
Click to expand...
Click to collapse
well I guess if it has been rooted ever then that voids any warranty. [excuse my language] god ****ing dammit then it's not fixable, christ LG are ****s.
aerolock said:
well I guess if it has been rooted ever then that voids any warranty. [excuse my language] god ****ing dammit then it's not fixable, christ LG are ****s.
Click to expand...
Click to collapse
I had mine fixed for free under warranty, so you should too, as long as it doesn't have significant other damage from drops or water, etc. I had rooted, unlocked and flashed many times. I did send it in stock, though, by flashing the stock factory images (mainly to clear personal data). I don't know what the official rules are about rooting and warranties, but I think that usually the Nexus phones allow you to unlock the bootloader and flash third party software without completely voiding the warranty. They are partly made as affordable developer units, anyway. Obviously, if you brick the phone by doing that stuff it is your fault, but if it is due to a defective part in your device, then they should be responsible to fix it. Even in the past I have been able to get an HTC phone repaired that was fully rooted/unlocked, because it had nothing to do with the hardware issue. Even if they say that your warranty is voided in the fine print from unlocking, sometimes companies will do the right thing and remedy issues that they are at fault for. Contact them, be polite, explain the problem/symptoms and ask if there is something they can do to help. When I contacted LG on their web chat system, I basically told them that the symptoms were most likely caused by a hardware issue and it seemed that the flash chip was failing. I told them that Google recognized the issue and has been refunding customers with the problem. I asked LG if they could repair, replace or refund my phone. The process went as smoothly as it could have gone for a situation like that (Other than unrelated issues with Fedex).
I would recommend just contacting LG, if you device is otherwise in good condition (aside from the bootloop). It can't hurt to try. Just know that the process of shipping it out, repairing, and shipping back might take about a week. Good Luck!
Ok, so when I went to the store I bought it from I said it was the nexus 5x bootloop issue thats with the hardware, then he asked me if I had done anything to the phone like rooting and I said I had rooted it once then removed the root, all he basically said then was dont waste our time asshole go somewhere else, so the previous root is the reason I can't get it fixed. But are you saying that if I call LG and dont mention anything about root then they'll fix it if I send it in? Luckily I found a spare phone so Im not handicapped but I love my 5x.
aerolock said:
Ok, so when I went to the store I bought it from I said it was the nexus 5x bootloop issue thats with the hardware, then he asked me if I had done anything to the phone like rooting and I said I had rooted it once then removed the root, all he basically said then was dont waste our time asshole go somewhere else, so the previous root is the reason I can't get it fixed. But are you saying that if I call LG and dont mention anything about root then they'll fix it if I send it in? Luckily I found a spare phone so Im not handicapped but I love my 5x.
Click to expand...
Click to collapse
I bought mine brand new on eBay. I rooted, Rommed, and otherwise tinkered with it unapologetically then ran into this bootloop issue almost a year later. I was able to contact LG support, send them a copy of my invoice from eBay showing that it was bought new and the date. I sent it off and they fixed it for free (replaced the main board) under warranty. Just go through LG support and they will almost certainly get you taken care of. It took a little over a week, but it sounds like you have a phone you can use during that time.
I purchased a 5x through Amazon over year ago and it is now bootlooping. I have tried all known fixes. I am in the US and I purchased the international version unknowingly. The LG US support site does not recognize my H791 version and I doubt that I can send it overseas. Am I out of luck getting this phone fixed?
Sent from my Nexus 6P using XDA-Developers Legacy app