Related
It sucks I have to ask this. I actually left XDA because of people who decided it was no longer good enough to do it for the community and they needed to get their bills paid, but screw it, I don't feel like buying a new phone. Hardbricked after flashing the MM ROM like everyone else, tried the willcracker diag thing, looked on Google until my eyes turned red, now I'm just aggravated and ready to get this fixed... Just point me and my wallet in the right direction.
However, if you know a way that doesn't involve me having to spend my last it would be greatly appreciated. I'm hoping a good Samaritan on XDA will come to aid instead of someone looking to make a quick buck but my hands are tied here...
Sent from my draconis using Tapatalk
Oh no...
mingolianbeef said:
It sucks I have to ask this. I actually left XDA because of people who decided it was no longer good enough to do it for the community and they needed to get their bills paid, but screw it, I don't feel like buying a new phone. Hardbricked after flashing the MM ROM like everyone else, tried the willcracker diag thing, looked on Google until my eyes turned red, now I'm just aggravated and ready to get this fixed... Just point me and my wallet in the right direction.
However, if you know a way that doesn't involve me having to spend my last it would be greatly appreciated. I'm hoping a good Samaritan on XDA will come to aid instead of someone looking to make a quick buck but my hands are tied here...
Sent from my draconis using Tapatalk
Click to expand...
Click to collapse
You can't boot into a custom recovery? Otherwise you could just flash a different rom...
hallosup said:
You can't boot into a custom recovery? Otherwise you could just flash a different rom...
Click to expand...
Click to collapse
Thanks for the reply bro. The issue is that it's hard bricked, though. Nothing happens, though, not even a charge light. I'm by far no stranger to this modding gaming lol, been doing it since I was 15 and I hard bricked my Evo 3D back in the day. It goes into the QCOM 9008 mode and that's about it. The only other screen it goes to is that if I short it sometimes the screen will come on with a battery icon and a triangle with an exclamation point.
Like I said, hours of Google pointed to me having to blow money because nobody has successfully unbricked the D851 yet. Which is why I asked for the above solution. However, again, if you know another way that doesn't involve spending money please share ?
Sent from my draconis using Tapatalk
mingolianbeef said:
Thanks for the reply bro. The issue is that it's hard bricked, though. Nothing happens, though, not even a charge light. I'm by far no stranger to this modding gaming lol, been doing it since I was 15 and I hard bricked my Evo 3D back in the day. It goes into the QCOM 9008 mode and that's about it. The only other screen it goes to is that if I short it sometimes the screen will come on with a battery icon and a triangle with an exclamation point.
Like I said, hours of Google pointed to me having to blow money because nobody has successfully unbricked the D851 yet. Which is why I asked for the above solution. However, again, if you know another way that doesn't involve spending money please share
Sent from my draconis using Tapatalk
Click to expand...
Click to collapse
don't mean to get on your case or anything but why would you flash mm rom for your d851 if it's not even out for our phones yet?....
Still_living714 said:
don't mean to get on your case or anything but why would you flash mm rom for your d851 if it's not even out for our phones yet?....
Click to expand...
Click to collapse
Here's my logic...
I'm no stranger to modding/devving/etc. Used to have ROMs and stuff myself, but back in the day with my old phones partition layouts were device specific (i.e. the "boot" partition would have a path of /blah/blah/blah/mmcblk0p##), and you absolutely could not flash that to any device other than your own. With my most recent devices, I've noticed that the partition layout would go as follows:
/dev/block/platform/msm_sdcc.1 (or similar)/by-name/boot
And they all have that generic path setup which has rendered many of my devices unbrickable (from a basic ROM flashing standpoint). I have a ROM for the ZTE ZMAX, and someone else from a different device altogether flashed it with only minor issues like WiFi, but it booted. I flashed a moto G ROM to the phone just to live a little dangerously and it simply didn't boot and I flashed a ZMAX ROM.
So... You are reading this and saying "I still don't understand why you did it"
I did it because I figured worse case scenario it wouldn't boot and that the partition layout for the boot/userdata/system partitions that these phones use would be the same since they are the same phone sans a couple partitions for the modem and bootloader and stuff. I didn't bank on a hard brick from a default partition layout that [shouldn't] flash to lower level partitions.
Sent from my draconis using Tapatalk
mingolianbeef said:
Here's my logic...
I'm no stranger to modding/devving/etc. Used to have ROMs and stuff myself, but back in the day with my old phones partition layouts were device specific (i.e. the "boot" partition would have a path of /blah/blah/blah/mmcblk0p##), and you absolutely could not flash that to any device other than your own. With my most recent devices, I've noticed that the partition layout would go as follows:
/dev/block/platform/msm_sdcc.1 (or similar)/by-name/boot
And they all have that generic path setup which has rendered many of my devices unbrickable (from a basic ROM flashing standpoint). I have a ROM for the ZTE ZMAX, and someone else from a different device altogether flashed it with only minor issues like WiFi, but it booted. I flashed a moto G ROM to the phone just to live a little dangerously and it simply didn't boot and I flashed a ZMAX ROM.
So... You are reading this and saying "I still don't understand why you did it"
I did it because I figured worse case scenario it wouldn't boot and that the partition layout for the boot/userdata/system partitions that these phones use would be the same since they are the same phone sans a couple partitions for the modem and bootloader and stuff. I didn't bank on a hard brick from a default partition layout that [shouldn't] flash to lower level partitions.
Sent from my draconis using Tapatalk
Click to expand...
Click to collapse
well I guess it's a lesson learned lol. I get what you're saying but by doing so you still dont know how the phone might react.
mingolianbeef said:
Here's my logic...
I'm no stranger to modding/devving/etc. Used to have ROMs and stuff myself, but back in the day with my old phones partition layouts were device specific (i.e. the "boot" partition would have a path of /blah/blah/blah/mmcblk0p##), and you absolutely could not flash that to any device other than your own. With my most recent devices, I've noticed that the partition layout would go as follows:
/dev/block/platform/msm_sdcc.1 (or similar)/by-name/boot
And they all have that generic path setup which has rendered many of my devices unbrickable (from a basic ROM flashing standpoint). I have a ROM for the ZTE ZMAX, and someone else from a different device altogether flashed it with only minor issues like WiFi, but it booted. I flashed a moto G ROM to the phone just to live a little dangerously and it simply didn't boot and I flashed a ZMAX ROM.
So... You are reading this and saying "I still don't understand why you did it"
I did it because I figured worse case scenario it wouldn't boot and that the partition layout for the boot/userdata/system partitions that these phones use would be the same since they are the same phone sans a couple partitions for the modem and bootloader and stuff. I didn't bank on a hard brick from a default partition layout that [shouldn't] flash to lower level partitions.
Sent from my draconis using Tapatalk
Click to expand...
Click to collapse
Well, i am in the same or almost the same pot as you. I flashed Fulmics ROM which was supposed to give me MM. But after downloading the almost 2GB rom, i noticed that my device wasnt part of the supported devices in Aroma Installer. But i went ahead and flashed the D855 version thinking that it might work with my D851 and incase it didnt work, the worst that could happen would be the device getting stuck on the LG Splash Logo. And when that happened, all i would have to do would be to boot into recovery and restore my backup. Little did i know that the ROM dev had added tz.img,rpm.img,boot.img and modem.img to the ROM. And what this means is that, the ROM wasnt just replacing my stock KK with Fulmics, but it was also overwriting and patching my D851 tz.img,rpm.img,boot.img and modem.img with that of the D855. The ROM flashed smoothely without an error and when it finnished, i hit the reboot button. Waiting for the device to bootup up into MM, but sadly, the the device never booted again. All i get now is Battery notifications.
For example, if i connect a USB to the phone without battery inserted, i get an empty battery with a yellow triangle with an exclamation mark in the middle of the yellow triangle. And when i exhaust the battery, and i press the power button, i get presented with an empty battery notification on the screen. Thats all i ever get.
I have tried shorting the pins... which gets me into QDownloader 9008 mode but Board Diag tool doesnt seem to work on the D851. My reasons for saying this is because i helped someone who had a D855 with the Board Diag process and it was able to flash all the files. The only pain was that, after every flash with board diag, we had to disconnect the device and re-short the pins and flash the files till we flashed all the files.
But for some unkown reason, this tool wont work on our device (D851). Apparently, the D851 motherboard is different from the D855. As i compared mine with the D855.
I just hope someone makes a tool to unbrick our D851.
Complete list of methods to "fix" or preventing the G4 bootloop
First of all: this is just a link list / index of methods !
I take no credits or responsibility of those methods its just that I hate to search things again and again and the idea here is to keep the methods in 1 single place
If I missed one please let me know!
Disclaimer:
It's your choice and on your own responsibility if using any of those linked methods!
Click to expand...
Click to collapse
About
What is the ILAPO / Bootloop?
LG Electronics has been made aware of a booting issue with the LG G4 smartphone that has now been identified as resulting from a loose contact between components. Customers who are experiencing booting issues with their LG G4s should contact their local carrier from where the G4 was purchased or a nearby LG Service Center (www.lg.com/common) for repair under full warranty.
Customers who purchased their G4 devices from non-carrier retailers should contact an LG Service Center with the understanding that warranty conditions will differ. LG Electronics is committed to providing the highest standards of product quality and customer service and apologizes for the inconvenience caused to some of our customers who initially received incorrect diagnoses.
Click to expand...
Click to collapse
Read more about it here:
https://www.androidauthority.com/lg-admits-g4-bootloop-problem-hardware-fault-669603/
https://en.wikipedia.org/wiki/LG_smartphone_bootloop_issues
https://forum.xda-developers.com/showpost.php?p=65511137&postcount=2
https://www.change.org/p/lg-mobile-launch-a-replacement-program-for-defective-lg-g4s
Backup
If you can still get into download mode I would recommend to do a full real nandroid backup before anything else: https://bit.do/SALTatXDA
Current state
There are only two real fixes available for the G4 bootloop and one advanced one:
1. Replace the mainboard or
2. send it to LG for warranty repair
3. Disassemble device for soldering/heat paste
For those out of warranty:
1. Replace the mainboard on your own in ~20 minutes: https://www.ifixit.com/Guide/LG+G4+Motherboard+Replacement/51202
2. All the other methods described here can bring back some life back to your device but no one can say if that means minutes, hours, days, weeks or even months (all these are reported time ranges).
the baking/oven method is clearly the one with the best chance of success and the longest life expectancy but it has one important limitation: toxic fumes.
Read the corresponding hint on that method with care!
Precautionary measure (unlocked devices only)
(skip to the next topic for locked devices)
Disabling the Big Cores reducing heat and so reducing the chance to bootloop.
There are users reporting that this method even works when it actually bootloops but its meant as a precautionary measure mainly:
https://forum.xda-developers.com/g4/general/fix-lg-g4-bootloop-issue-t3647538
and to create your own boot image read on here for the ultimative "X cores guide"
I have also created an ilapo TWRP version with the big cores disabled here so if TWRP bootloops try those first:
Ilapo TWRP
Locked & Unlocked devices
If you do not want to fight with LG support about warranty I would try this first: aboot TOT flashing or hair dryer method A) and if that doesn't worked and even when there is a little risk on using it: the freezer method
The recommended order on fixing the ILAPO would be like this:
aboot TOT method -> pressure method -> hair dryer method A) -> hair dryer method B) -> baking method (as long as u have an oven which is not used for food anymore) -> ironing method (take care of the unknown temperature issue this has) -> freezer method
Low chances of voiding your warranty (depends on the LG customer service)
1) aboot TOT flashing
Disabling the Big Cores reducing heat and so reducing the chance to bootloop.
There are users reporting that this method even works when it actually bootloops but its meant as a precautionary measure mainly
you need to choose the CORRECT aboot TOT file and you need to check your ARB!
If you flash a lower ARB aboot file you WILL BRICK YOUR DEVICE!
http://leech.binbash.rocks:8008/unbricking/max4cores/
High(er) chances of voiding your warranty (depends on the LG customer service)
The following methods MAY get detected by LG customer service and so they MAY reject service on it (warranty void) due to detection of an unauthorized opened device:
2) pressure method:
https://forum.xda-developers.com/g4/help/lg-g4-bootloop-quick-fix-try-baking-t3633595
(as u need to open the device it may be rejected by LG support for repair - but loosen the screws carefully and open the back cover even more carefully will usually work without being detected)
3) hair dryer method:
A) https://forum.xda-developers.com/g4/help/temporary-boot-loop-solution-to-files-t3554469
B) https://forum.xda-developers.com/showpost.php?p=71647715&postcount=41 (checkout the video and the last comments of the writer in the XDA thread)
(as u need to open the device it may be rejected by LG support for repair - but loosen the screws carefully and open the back cover even more carefully will usually work without being detected)
4) ironing method:
s-X-s reported here this method as its working for him: https://www.youtube.com/watch?time_continue=2&v=TM9umec5aeo
While I personally would prefer this method over the baking method its very very risky to use it. The reason is that you have no temperature indicators on an iron and so you may overheat in the worst case..
(as u need to open the device and disassemble the board it may be rejected by LG support for an eventually warranty repair)
5) baking method:
(as u need to open the device and disassemble the board it may be rejected by LG support for an eventually warranty repair)
nitrous² said:
I highly recommend doing this ONLY if you have no other option (or when you do not want to use the oven again!)
Remember that heating a logic board to high temperatures can release toxic fumes. Don't use an oven you use for food preparation! Toxic fumes can leave residue in the oven and will be re-released upon reheating over many cycles
Click to expand...
Click to collapse
Details regarding toxic fumes:
(READ THIS TO UNDERSTAND THE HEALTH RISK!)
nitrous² said:
Here's a nice PDF from Techni-Tool, a company supplying the electronic production industry with soldering stuff, chemicals, tools and what not. It's not necessarily a paper from a scientific institution but I'd still take their word for it.
Click to expand...
Click to collapse
https://forum.xda-developers.com/g4/help/solution-lg-g4-bootloop-issue-story-t3322382
or:
https://forum.xda-developers.com/g4/help/diy-h815-usa-variant-hardware-boot-loop-t3311623
6) freezer method: (100% a temporary fix only - e.g. just for taking a backup)
https://forum.xda-developers.com/tmobile-g4/help/how-to-recover-data-boot-loop-defect-t3297766 (~1 hour at least in freezer)
(The freezer does not require to open the device BUT: it could be possible that LG may reject such devices for repair due to a water damage (depends on several things so this might or might not happen))
UPDATE:
Take out the battery before putting it in the freezer!
An easy way to prevent any damage is to use a plastic bag which can be closed with a zipper or similar.
7) Advanced disassemble method(s):
The following thread contains several methods to fix the mainboard issue without LG but may require some technical skills to handle but not is the best choice you have when you can't get a new mainboard. Ensure you read all posts there to fin your best choice:
https://forum.xda-developers.com/g4/general/lg-g4-bootloop-fix-t3488449
Backup
Once booted up backup your data as fast as you can.
Btw if any of the above succeeds its very very likely that you have a defective hardware again.
If thats the case you may try another method but the chances to bring it back to life a second time - especially when you used the baking method is at 1% ...
Final destination - R.I.P. 9008 mode
Sooner or later you may reach this.
lets say u tried all or almost all of the above (especially the baking method) and it still does not work or its the second time you are here then your device is likely completely dead now.
If you turn on your phone and just seeing a black screen and nothing else happens the device is likely in EDL / QDL 9008 mode which is the final end of the journey for your device.
You can verify this by connecting the device to your PC and watch the device manager while doing so. You should see a new unknown device here named QHUSB...
This has nothing to do with those 9008 unbrick guides u can find here and elsewhere as the hardware fault goes deeper. Of course u can try out those guides (try my PoC unlock guide first..)
Its hard to say but you're gonna have to put up with burying this device.
Sell it as spare parts and say goodbye..
Credits
The above methods are created or reported by:
@celsius0010 (freezer)
@rogconnect (baking)
@gub1 (baking)
@s-X-s (ironing)
@nick camel (hair dryer)
@Minchan_5 (hair dryer)
@sloscotty (pressure)
@Martin Elias (aboot TOT)
.
Hi, greetings @steadfasterX
I am posting in this thread, because it's somehow related (i think)
I have 2 lg g4 H815 & H811 devices.
Anyway...
-h811: * rooted
It had ILAPO and died.
-h815: * not rooted
Cellular network problems. (used as a small tablet ..)
Months later, Flickering on the right half of the screen (split screen glitch), after some time of use (disappears on screen on / off, comes back very quickly as far as I can remember)
My goal here is to have a functional device.
I was just wondering if this is a sign of a future ILAPO for the h815 device ... as some users say they replaced the screen/front-panel to fix it (screen/connector related issue).
So I'm thinking of replacing the h811 motherboard with the h815 one (also try to replace the cellular network component with the one that works).
-To finish with the combination of a good:
motherboard (h815) + screen (h811)
(achieved by replacing h811 motherboard...)
Can anyone have any further suggestion or clear up any misunderstanding regarding the "flicker" issue?
(I could also flash a pre-rooted firmware for the locked bootloader and disable the 2 big cores if needed to prevent ILAPO if that could happen, as I cannot root my h815 device. Wrong device id, changed the motherboard once)
Thank you
PS: I didn't use the device for years now...
reserved.
I've tried freezing method ( keeping phone in deep freezer while connected with a pc using cable) and it helped me to backup all important files. I've managed to keep phone alive for an hour or so, and then it was dead. Since phone was under warranty, mobo was replaced..
Regarding baking method, is it possible to repair motherboard that way permanently, or is it just one more temporary solution. How long will phone be in working condition after baking mobo?
draskome said:
I've tried freezing method ( keeping phone in deep freezer while connected with a pc using cable) and it helped me to backup all important files. I've managed to keep phone alive for an hour or so, and then it was dead. Since phone was under warranty, mobo was replaced..
Regarding baking method, is it possible to repair motherboard that way permanently, or is it just one more temporary solution. How long will phone be in working condition after baking mobo?
Click to expand...
Click to collapse
It has the most potential to extend the life most. The reason lays in the hardware issue itself. Read this good explanation here:
https://forum.xda-developers.com/g4/help/solution-lg-g4-bootloop-issue-story-t3322382/post65511137
If you have luck that means it lives months to years but it depends on several facts which can be different from phone to phone as the hw fault may be in different states.
sfX
Edit:
Do not forget to vote
Sent from my LG-H815 using XDA Labs
I think the best one is the quad core fix, sadly it hasnt been released for H810 models (at&t)
Hi friends, my brother's G4 just caught the bootloop problem... It's still under LG official warranty, but the local service in charge of the device told my brother they won't repair it for free since the guy saw the oxidation cap being red, meaning the phone was oxidated...
I've heard that to be a recurrent problem among LG user. The question is : have you heard of someone who went through that and made his phone reach the customer service for a free repair ?? Or do you think it's possible to replace the battery with a non-oxidated cap before sending it ?
Thank for your help
Copying this from my thread!
First off, I know a bit about electronics (far from an expert) but I still know how to do basic troubleshooting with a multimeter etc.
But since every part in a phone is so smal + I don't own a microscope I need some help)
With that said, The issue I'm having is bootloop, I start the phone, get to the LG Life's Good for about 5 seconds, screen goes black, LG logo again over and over again. I also read that this is a known issue with the G4. So I read a few threads and some said to try using a heatgun on the CPU/the chips. So I took my unregulated heatgun which blows at around 380 degress celsius (it is the only heatgun I have). So very carefully I blew air on the chips for about 3 seconds from far away, I then carefully pressed on the chip to make sure that all the solder joints made contacts with the SMD chips. I started the phone and guess what.. it started up!
So first thing I did was to unlock the bootloader, Installed TWRP + Linage ROM. so far so good, then suddenly after looking around in the settings the screen froze, same thing happend again = bootloop. So I took apart the phone again, blew some air, and it started again (i had to blow multiple times so that the chip got pretty hot). then the phone started again.
My first thought was that the CPU (or something else) get's too hot so that some solder joint jumps off, that's why the hot air works. But when I turned it on the second time, I kept the CPU/Battery under 28 Degrees Celsius, just looking at some pictures. After abount 5 - 10 minutes. Same thing.
I'm getting tired on blowing air on it and I really want to use this phone.
I looked at some videos about installing some heatsinks on it (which I can do). But I'm unsure that the CPU is the issue since I still got the bootloop/freeze when the CPU was cold..
And btw, I can't get into TWRP either when the bootloop is ongoing. The screen just freezes right before I enter recovery.
Got anyone give me some pointers on what I can test? Thanks!!
P.S the reason why the text isn't visible on the chips is because of the heat. i have heated the chips up a LOT of times to get the phone to boot so the text has started to disappear.
Edit: I put some heatsinking tape on the memory + CPU with cooling paste. As usual, worked for a few hours, then bootloop again.
Check thread for pics: https://forum.xda-developers.com/g4/help/lg-g4-h815-bootloop-hardware-issue-help-t3715164
Any help is appriciated!
psrkallez06 said:
Copying this from my thread!
First off, I know a bit about electronics (far from an expert) but I still know how to do basic troubleshooting with a multimeter etc.
But since every part in a phone is so smal + I don't own a microscope I need some help)
With that said, The issue I'm having is bootloop, I start the phone, get to the LG Life's Good for about 5 seconds, screen goes black, LG logo again over and over again. I also read that this is a known issue with the G4. So I read a few threads and some said to try using a heatgun on the CPU/the chips. So I took my unregulated heatgun which blows at around 380 degress celsius (it is the only heatgun I have). So very carefully I blew air on the chips for about 3 seconds from far away, I then carefully pressed on the chip to make sure that all the solder joints made contacts with the SMD chips. I started the phone and guess what.. it started up!
So first thing I did was to unlock the bootloader, Installed TWRP + Linage ROM. so far so good, then suddenly after looking around in the settings the screen froze, same thing happend again = bootloop. So I took apart the phone again, blew some air, and it started again (i had to blow multiple times so that the chip got pretty hot). then the phone started again.
My first thought was that the CPU (or something else) get's too hot so that some solder joint jumps off, that's why the hot air works. But when I turned it on the second time, I kept the CPU/Battery under 28 Degrees Celsius, just looking at some pictures. After abount 5 - 10 minutes. Same thing.
I'm getting tired on blowing air on it and I really want to use this phone.
I looked at some videos about installing some heatsinks on it (which I can do). But I'm unsure that the CPU is the issue since I still got the bootloop/freeze when the CPU was cold..
And btw, I can't get into TWRP either when the bootloop is ongoing. The screen just freezes right before I enter recovery.
Got anyone give me some pointers on what I can test? Thanks!!
P.S the reason why the text isn't visible on the chips is because of the heat. i have heated the chips up a LOT of times to get the phone to boot so the text has started to disappear.
Edit: I put some heatsinking tape on the memory + CPU with cooling paste. As usual, worked for a few hours, then bootloop again.
Check thread for pics: https://forum.xda-developers.com/g4/help/lg-g4-h815-bootloop-hardware-issue-help-t3715164
Any help is appriciated!
Click to expand...
Click to collapse
Thx for sharing your thoughts here!
Do you have read what's mentioned in the OP?
Advanced disassemble method(s):
The following thread contains several methods to fix the mainboard issue without LG but may require some technical skills to handle but not is the best choice you have when you can't get a new mainboard. Ensure you read all posts there to fin your best choice:
https://forum.xda-developers.com/g4/general/lg-g4-bootloop-fix-t3488449
Sent from my LG-H815 using XDA Labs
steadfasterX said:
Thx for sharing your thoughts here!
Do you have read what's mentioned in the OP?
Advanced disassemble method(s):
The following thread contains several methods to fix the mainboard issue without LG but may require some technical skills to handle but not is the best choice you have when you can't get a new mainboard. Ensure you read all posts there to fin your best choice:
https://forum.xda-developers.com/g4/general/lg-g4-bootloop-fix-t3488449
Sent from my LG-H815 using XDA Labs
Click to expand...
Click to collapse
Thanks for your answer! yes i have, and i have tried that method but i have a small update!
I installed a file to disable two of the cores. i can now enter TWRP without any issues but i have another problem, the file i downloaded doesn't support linage rom which i have. a user called Agimax wrote this:
Why not just edit the files below for the two large cores (if you have root):
/sys/devices/system/cpu/cpu4/online (open file and change from a one to a zero)
/sys/devices/system/cpu/cpu5/online (open file and change from a one to a zero)
and this is what I'm currently trying to do, but i just can't change the files.. I tried launching TWRP, then using adb to push the file to the location, it does change to 0, but after i restart recovery it's back to 1 again.
I also tried aroma file manager but i always get error 1 when i try to remove/move/rename the file. And i have used chmod 755 before messing with it. any tips on how i can FORCE those two files to change to 0?
Thank you!
psrkallez06 said:
Thanks for your answer! yes i have, and i have tried that method but i have a small update!
I installed a file to disable two of the cores. i can now enter TWRP without any issues but i have another problem, the file i downloaded doesn't support linage rom which i have. a user called Agimax wrote this:
Why not just edit the files below for the two large cores (if you have root):
/sys/devices/system/cpu/cpu4/online (open file and change from a one to a zero)
/sys/devices/system/cpu/cpu5/online (open file and change from a one to a zero)
and this is what I'm currently trying to do, but i just can't change the files.. I tried launching TWRP, then using adb to push the file to the location, it does change to 0, but after i restart recovery it's back to 1 again.
I also tried aroma file manager but i always get error 1 when i try to remove/move/rename the file. And i have used chmod 755 before messing with it. any tips on how i can FORCE those two files to change to 0?
Thank you!
Click to expand...
Click to collapse
No this is not the correct way to achieve what you want. you need to modify the boot image and not changing dynamic files like mentioned there.
We already have a thread where I provide several boot images which have the big cores disabled:
https://forum.xda-developers.com/g4/general/fix-lg-g4-bootloop-issue-t3647538
Sent from my LG-H815 using XDA Labs
steadfasterX said:
No this is not the correct way to achieve what you want. you need to modify the boot image and not changing dynamic files like mentioned there.
We already have a thread where I provide several boot images which have the big cores disabled:
https://forum.xda-developers.com/g4/general/fix-lg-g4-bootloop-issue-t3647538
Sent from my LG-H815 using XDA Labs
Click to expand...
Click to collapse
I already tried that, When i flash it it stops the bootloop BUT i can't enter the rom. Instead of getting a bootloop the Linage Rom keeps loading. I never get past that "/
i first flashed: lgg4_twrp_4cores_3.1.1-1.zip
then i tried all of the other ones for the h815, 20p, 20r 20g. Still same issue, (also what is the difference betweel p, r and g?) it keeps loading over and over again. Did i do something wrong?
psrkallez06 said:
I already tried that, When i flash it it stops the bootloop BUT i can't enter the rom. Instead of getting a bootloop the Linage Rom keeps loading. I never get past that "/
i first flashed: lgg4_twrp_4cores_3.1.1-1.zip
then i tried all of the other ones for the h815, 20p, 20r 20g. Still same issue, (also what is the difference betweel p, r and g?) it keeps loading over and over again. Did i do something wrong?
Click to expand...
Click to collapse
Well..
You need to flash a compatible boot image not just some..
If you flash stock firmware 20g you need a 20g boot image..
If you flash LOS 14 you need a LOS 14 boot image..
If you flash RR you need a RR boot image..
... and so on
Give me the link of your exact LOS version flashed and I can prepare it if you like.
( using the thanks button is more welcomed by many ppl then saying )
Sent from my LG-H815 using XDA Labs
steadfasterX said:
Well..
You need to flash a compatible boot image not just some..
If you flash stock firmware 20g you need a 20g boot image..
If you flash LOS 14 you need a LOS 14 boot image..
If you flash RR you need a RR boot image..
... and so on
Give me the link of your exact LOS version flashed and I can prepare it if you like.
( using the thanks button is more welcomed by many ppl then saying )
Sent from my LG-H815 using XDA Labs
Click to expand...
Click to collapse
I see! Well not sure which version i have.
as i said I'm using Linage ROM, what info etc do you need to make one for me? And of course i will spam that thank you button for helping me! haha
https://download.lineageos.org/h815
nightly 14.1 lineage-14.1-20171107-nightly-h815-signed.zip
sha256 sha1 474.35 MB 2017-11-07
Is the one i have!
Also i wrote in the IRC chat!
psrkallez06 said:
I see! Well not sure which version i have.
as i said I'm using Linage ROM, what info etc do you need to make one for me? And of course i will spam that thank you button for helping me! haha
https://download.lineageos.org/h815
nightly 14.1 lineage-14.1-20171107-nightly-h815-signed.zip
sha256 sha1 474.35 MB 2017-11-07
Is the one i have!
Also i wrote in the IRC chat!
Click to expand...
Click to collapse
Ok great that's all I need and pls remove the screenshot with your imei!! Don't share this in public..
I may can do that tomorrow or Monday latest.
Btw: You can click on every post which is useful for you (not just mine but in general) as you can not use a thanks multiple times on the same post
Sent from my LG-H815 using XDA Labs
steadfasterX said:
Ok great that's all I need and pls remove the screenshot with your imei!! Don't share this in public..
I may can do that tomorrow or Monday latest.
Btw: You can click on every post which is useful for you (not just mine but in general) as you can not use a thanks multiple times on the same post
Sent from my LG-H815 using XDA Labs
Click to expand...
Click to collapse
Sorry i removed the picture, I'm new at this stuff! haha. Thanks for the warning! Got it! Atm I'm looking into on how to unpack the boot.img, gonna try some stuff myself in the meantime hehe
Edit: Do you know a tutorial where is shows how i can modify the boot.img myself? or maybe if you can explain? or is it advanced/complicated to do?
Edit2: I know how to unpack and pack the boot.img, but not sure which file and line to edit etc!
@steadfasterX Do you still have time to make the boot.img from the Linage Rom? i would really appriciate it! Cheers.
psrkallez06 said:
@steadfasterX Do you still have time to make the boot.img from the Linage Rom? i would really appriciate it! Cheers.
Click to expand...
Click to collapse
ah sorry but I forgot..
see here
Cheers
steadfasterX said:
ah sorry but I forgot..
see here
Cheers
Click to expand...
Click to collapse
Thank you very much! I will try that
How long did you guys manage to extend the life of the phone?
hello .. ı have h815 V20l bootloop device... ı flashed your marshmellow tot file but ı got secure device but unsecured image error
So, I made a bit of dumb mistake after getting the TA-1050 TWRP installed and accidentally wiped the system partition and I'm kinda freaking out at how I'm going to get this phone functional again. If not in download or TWRP recovery mode, it is in a constant boot loop (which sucks) but it's hope that I haven't completely messed up.
So, to the point, is there firmware flying about that I can use to help dig myself out of this hole or will I need to rely on a backup phone until said firmware is brought to light?
Lesson to learn: Don't touch anything that doesn't need to be touched :good:
Edit: My phone now only reboots into download mode. Not sure what that's all about but it still at least works, so there is hope.
Going to bump this and say that if anyone can provide how I can flash it with the firmware (well, once I can get it) in a step by step format.
Either numbered or bulletin would be fine but just something that's clear and get's right to the point of how I can reverse this issue.
Anyone got anything?
Only firmware files i'm aware of is https://forum.xda-developers.com/no...-to-flash-global-firmware-pl2-222e-0-t3831764
who knows what models it works on and if its legit though
really sucks nokia doesn't provide factory images
I had the same problem several days ago and the only way I was able to fix it was using the stock 1043 (I have a 1045) system images to get a functional device. My device still registers as a 1045 so give it a try. I do advise using fastboot to erase and format both the A and B partitions before flashing.
Ozonethegreat said:
I had the same problem several days ago and the only way I was able to fix it was using the stock 1043 (I have a 1045) system images to get a functional device. My device still registers as a 1045 so give it a try. I do advise using fastboot to erase and format both the A and B partitions before flashing.
Click to expand...
Click to collapse
which thread did you get the 1043 image from?
prg318 said:
which thread did you get the 1043 image from?
Click to expand...
Click to collapse
I cannot remember nor find it, lol. Give me a sec, I'll upload them
https://drive.google.com/open?id=1fMySPkJSj8VGiFkUj5t3DMz3yDZdrI2L
if your model has android one softwear (( global version )) follow my thread to get your stock firmware
good luck
https://forum.xda-developers.com/no...pl2-222e-0-t3831764/post77389130#post77389130
Thanks guys, I'll see what I can do with what you've provided. Will report back if it works or fails.
So I didn't intend to get back so much later than I have, uni studies can get pretty hectic.
Unfortunately, it didn't work. I have no idea how much damage I've actually caused but even the daemon can't pick it up when I try to run it in ADB or running powershell to run ADB. Because it's not being detected, I don't have much confidence I'll get this fixed.
Has anyone got any solutions? If you need a video of what I'm dealing with, I'll see what I can do if that'll help.
Hello users, I have my Mi Max Hydrogen 3/32 bricked since time ago, I tried all the threads out there to revive my device, as a hard bricked no fastboot, no download mode responsive, of course no recovery.
I guess that bootloader is messed due to a bad flashing of a file uploaded by error.
I found a method, idea is to force device to enter to download mode restoring bootloader or turn on responsive again to allow a new flashing cycle.
I´m now using a Redmi 5 Plus and I did this method to prevent any trouble in the future, one never knows.
If some user wants to help just I need that this zip should be flash it through recovery and the file just will dump/backup the first 125MB aproximately of system and it will kept in sdcard with the name of debrick.img and kindly can upload it to the cloud. This will be greatly appreciated and I hope that also can help to other users with same/similar issue now. If things go fine I´ll explain in details to accomplish that
View attachment Partial_Sys_Dump_for_debrick.zip
Reserved.
A brief explanation:
I have found this tutorial https://forum.xda-developers.com/showthread.php?t=2369125 (applying concerning to this model) among several of the same type, the idea behind this is that in a cell phone bricked because the bootloader is damaged and trying to boot it does not find that partition readable, so burning/writing the first lines of the operating system in a sdcard, then putting it in the device then it will search these files to try to boot. If the emmc/motherboard is not totally damaged or the measurement of the files is sufficient for it to do it then after this it will come to turn on, stay or spend a little more of the bootlogo and that will indicate that it is in a condition of flashing all the system files again through the fastboot or MiFlash to make it functional back and bring it back to life.
In my case I have damaged the buttons, the back cover opened in the repair shop and this may have a negative influence to try it properly, therefore I could not recover it yet, or the size of the files is not completely sufficient since the tutorial is based on a Galaxy S3 with a memory lower than This device or plainly emmc is definitely damaged.
However, each case is different and I think that this explanation can help others who are in similar cases.
There you go: deleted
Please, explain what you are doing even if it didn't work.
nijel8 said:
There you go: hydrogen_3-32_debrick.img
Please, explain what you are doing even if it didn't work.
Click to expand...
Click to collapse
A great thanks, my device has sleeping maaaany time. I will try it and I´ll report even if this doesn´t work.
nijel8 said:
There you go: hydrogen_3-32_debrick.img
Please, explain what you are doing even if it didn't work.
Click to expand...
Click to collapse
If you want to give me a second chance, I explained the idea behind this. It´s based on a device the half of ram/rom than this so I think that maybe it´s needed at least 200 mb to find working files to let it run. i´m not sure that if you are running in a custom rom and non miui rom it works anyway.
Your help is greatly appreciated and I recommend any user that can keep the zip dumper and Debrick image in a safe place just in case in the future could need it.
View attachment Partial_Sys_Dump_for_debrick-200MB.zip
hydrogen_3-32_debrick.img
Don't think this is going to work...
nijel8 said:
hydrogen_3-32_debrick.img
Don't think this is going to work...
Click to expand...
Click to collapse
Why do you think so? difference in sizes between 128 and 200 doesn´t matter? or plainly this method can´t work in this device in your opinion? I saw this method in other non Samsung devices like Lenovo totally bricked and cause is a similar device I thought that maybe..... and of course one don´t want resign.
Google sent a confirmation to grant access to your file. Thanks for support.
Hello Everyone,
Today a friend gave me a phone that I would like to use, but it has a screen lock passcode on it that she doesn't know. The phone was given to her, but she couldn't use because it's AT&T and she is on T-Mobile so she passed it on to me. I checked the IMEI number on several sites and it's clean so i shouldn't have any issues. Is there a way I can remove the passcode from this phone?
My apologies if this is in the wrong section.
adrian0883 said:
Hello Everyone,
Today a friend gave me a phone that I would like to use, but it has a screen lock passcode on it that she doesn't know. The phone was given to her, but she couldn't use because it's AT&T and she is on T-Mobile so she passed it on to me. I checked the IMEI number on several sites and it's clean so i shouldn't have any issues. Is there a way I can remove the passcode from this phone?
My apologies if this is in the wrong section.
Click to expand...
Click to collapse
Hi, do you still have the phone on you? I've basically hard brick mine and now I need a full mtk dump to get it back as it was. so if you do, can you upload this files? don't worry if you don't know how to do that, I can walk you through the process
i can help you , if your device still soft break
Osamaaj03 said:
Hi, do you still have the phone on you? I've basically hard brick mine and now I need a full mtk dump to get it back as it was. so if you do, can you upload this files? don't worry if you don't know how to do that, I can walk you through the process
Click to expand...
Click to collapse
sahelkhan022 said:
i can help you , if your device still soft break
Click to expand...
Click to collapse
it is, I think the problem is with the super image but I'm not 100% sure. so if you can share a full mtk client backup it would be awesome. if not, a super image will do
your device stuck on logo ? or deadboot ?
842.92 MB file on MEGA
mega.nz
sahelkhan022 said:
your device stuck on logo ? or deadboot ?
Click to expand...
Click to collapse
every time I try to turn it on it bootloops to fastboot mode, I suspect that the issue is a super image I found online, flashed not knowing that it was corrupted (which I discovered later), and I foolishly didn't create a backup (why I went and downloaded the corrupted image in the first place) thinking that I will never go back to the stock rom but now after I have used a couple gsi's for a while found out that the og rom performance was much better and decided to go back
sahelkhan022 said:
842.92 MB file on MEGA
mega.nz
Click to expand...
Click to collapse
so this is just a bunch of .bin files that I have to flash using mtk client to said partitions? just making sure
and just to let you know I might not be able to download the file today, the internet is pretty sucky where I'm rn, so I hope you don't have a problem keeping the file up till tomorrow. and just wanted to thank you for the incredible help, I've been trying to fix this phone for the last two weeks which was headache inducing say the least.
you can flash this with lots of free tools .. if secure boot on you can't flash directly but i will help you . you just need to share your screen with me ..
sorry for the late response, but yeah I've flashed all of the files using mtkclient and it didn't work Idk if I have messed things up, I thought reflashing all of the stock firmware would fix everything but it seems that there's still something wrong
sahelkhan022 said:
you can flash this with lots of free tools .. if secure boot on you can't flash directly but i will help you . you just need to share your screen with me ..
Click to expand...
Click to collapse
I've unlocked the bootloader and disabled boot verification, tried fastboot -w and fastboot format userdata and non of it worked, and I'm really sorry but I can't share my screen because as I've mentioned before my internet is bad and I had to go somewhere else to get the files. can I share anything else with you that might help, I have some recovery log files
IT WORKED!!!!! I don't know what was the problem, I've tried flashing the files again but this time using the terminal instead of the gui AND IT WORKED. THANK YOU THANK YOU THANK YOU
I'm going to upload the files later in case someone else encountered the same problem