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.
Related
Hey XDAers,
I need your help. I think my phone's eMmc chip is dead. Today my phone's screen didnt turn on, I suspected it to be just a buggy kernel or ROM so as any other person would do, I removed the battery and rebooted. Well it did reboot although the boot animation (of Vanir) was lagging. Then I got to my lockscreen but when i was entering my passcode it was extremely laggy and it continued that way for like a min or 2 just freezing for like 5 seconds then continuing until it finally froze for like a min and I decided to reboot. Same thing happened, I kept trying to reboot sometimes it would just freeze others it would reboot on its own. Then I went into recovery and fixed permissions... same thing. Then I wiped dalvik cache, same results. I finally decided to connect it to the PC and pulled everything from the phone using adb and made a nandroid backup to my USB flash drive using my OTG cable and CWM, because when I tried backing up normally to the internal memory I was faced with errors. So then as a last resort I just was gonna flash to stock using fastboot (by the Nexus toolkit). While flashing I got an error telling me that the baseband version I have is different than the one required. even though the baseband from the .tgz or whatever file was successfully flashed. So apparently my radio is UGLL1 (I think) and the radio included in .tgz package was XXLJ1 and even though it was flashed, it didnt change. I tried manually flashing the radio and it also didnt change. So i went in the .tgz file and edited the android-info.txt file inside so that it doesnt require the XXLJ1 baseband to be present and instead just the UGLL1. It started flashing but got stuck at flashing the system partition after it was "sent". At this point I started paniking because normally flashing stock solves everything. So I tried using ODIN (my first time with it) and it took 30 mins to flash everything (25 mins just for flashing system. I was feeling optimistic since it was successfully completed.
Then it rebooted and I see the Vanir boot animation >_> WHATTT??? after all these system flashes and wipes Vanir is still present?? Then after it boots it takes my right to my same lockscreen, like the data and system partition weren't even touched!!! And its still lagging and freezing. So I go to TWRP recovery and try deleting everything from /data/media which works then I reboot again in recovery and everything is back ??? I cant wipe anything. I can add things because I remember earlier during this process I pushed a zip file.
I AM DYING HERE OMG MY PHONE IS LIKE MY LIFE. PLEASE HELP!!!!!!!! I THINK ITS DEAD BUT I'LL TRY ANYTHING :crying:
Same issue I had; unfortunately that is describing the painful EMMC death. Had to buy another GNEX (http://forum.xda-developers.com/showthread.php?t=1909331 and http://forum.xda-developers.com/showthread.php?t=2354641)
jhonnyx said:
Same issue I had; unfortunately that is describing the painful EMMC death. Had to buy another GNEX (http://forum.xda-developers.com/showthread.php?t=1909331 and http://forum.xda-developers.com/showthread.php?t=2354641)
Click to expand...
Click to collapse
This is devastating me... I've been crying for the past half hour about this. I never thought this could happen, that this device could be bricked
Do you know if Samsung could help me with this, like if they could replace the motherboard maybe. Hopefully it doesn't cost much trying to think of any under-$100 options.
yasir.97 said:
This is devastating me... I've been crying for the past half hour about this. I never thought this could happen, that this device could be bricked
Do you know if Samsung could help me with this, like if they could replace the motherboard maybe. Hopefully it doesn't cost much trying to think of any under-$100 options.
Click to expand...
Click to collapse
You can try Samsungs warranty. Once I bricked my motherboard and got it replaced.
Sent from my Galaxy Nexus using Tapatalk
aaron13 said:
You can try Samsungs warranty. Once I bricked my motherboard and got it replaced.
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
They said it would cost about $300 in total. The employee advised me to buy a new phone which I'm going to do. I'll get the Nexus 5 now .
I'm gonna miss this Galaxy Nexus community
yasir.97 said:
They said it would cost about $300 in total. The employee advised me to buy a new phone which I'm going to do. I'll get the Nexus 5 now .
I'm gonna miss this Galaxy Nexus community
Click to expand...
Click to collapse
If your screen is in good shape, you may be able to sell your Gnex for parts.
Sent from my Nexus 7 using xda app-developers app
ive tried the lg flash tool with both the files it worked before last time i got soft bricked well i flashed that stock kit kat for the f whatever series that is on the e980 dev it flashed a diff recovery on my phone now i cant get to revcovery and download mode fails after it not being a e890 device anymore sorry i have been up all night trying to fix this and now im completly stuck.download mode fails after it not being a e890 device anymore sorry i have been up all night trying to fix this and now im completly stuck. download failed 5 sec says the pid number imei number and then device model is different check phone or dll f0000002
What Rom did you install the stock 4.4 zdk or the sphinx 4.4 flashable Rom?
_________________
Beavers & Ducks!
i flashed the sphinx 4.4 flashable Rom idk why it installed a recovery with it couldnt see sd card then when tried flashing another e980 rom it wouldnt let me said i had the wrong device or something idk im pissed about to smash it
_________________
Beavers & Ducks![/QUOTE]
i was on a cwm before but it ended up flashing a new one and thats when i started having problems now no recovery stuck at lg logo and i know my battery is low
The first thing I would do is pull your battery, wait a few minutes, put the battery back in and connect the charging cable. It may not want to boot but it will charge the battery while the phone is off. Get your battery charged first, then worry about getting it up and running again.
Keep in mind I'm not picking at you or anyone. But why would someone choose to flash a Rom designed for one version to another version? I know our devs make tweaks to allow one to run on the other but it's a chance I wouldn't take. If you have the E980, stick to E980 Roms. It's risky enough flashing Roms as it is because no two devices are the same. You know what I mean? And don't smash you phone. There are many smart people here that can get you up and running again. Smash the phone and you will be upset with yourself later....trust me. I did it and I was pissed at myself later when I found out it was easy to fix....stay calm....lol
i know i knew i should not have idk ive been flashing zips for a very long time guess it happened to still get the best of me even though i read through the thread and i seen a couple e980 users saying it worked haha well not for me i just hope i can get her back up and going soft bricks are ok its when i cant fix this that makes me crazy. slammed around my dual monitors and almost went after my evga build which would not have been good. Man i can not thank u enough i even had to make another account my old one was lows10 and i guess it was inactive for to long but been here since 07 only place i trust to exploit my devices.
Well I'm not the smartest person here. I just got this phone about a month ago and I haven't even got flashing it back to stock down pat yet. It's a work in progress....lol. But just get your battery charged for now. Then you will most likely have to flash it back to stock. I don't know if you have done this process yet on that phone but if you have then you know basically what you need to do. Just don't go flashing any more Roms made for other versions of the g pro....lol
this will be my 3rd time flashing back to stock but with my phone not being read as a e980 i cant get back to stock.
Did you use the Lg Flash Tools method?
Yes lg flash tool has worked perfect until now after that ROM
Sent from my d2lte using xda app-developers app
Ok. Give this method a try....http://forum.xda-developers.com/showthread.php?t=2459825....I don't know if it will work for ya as it didn't work for me. But hey, you gotta try something and maybe you will get luck and it will work for you. Give it a go and see what happens.
Lol idk it thinks its a g2 then it FCS
Sent from my d2lte using xda app-developers app
Tricky bugger it's gonna be ah? Did you try running it in Administrator mode? Be sure to follow the steps exactly as he lays them out.
Well in the left it says lge988at maybe thats why it isnt working with the lg flash? Grrrr idk this sucks and it keeps stopping working and its not in english
It has to be on com 41. I have noticed the lg flash tools method can be hit and miss with allot of people. I finally got it down pat enough to get it to work every time. You could try doing it this way........http://forum.xda-developers.com/showthread.php?t=2432476........He gives a link to a newer lg flash tools. Maybe you will have better results.
damn it still closes with that its right after it gets done loading my phone i guess i cant flash a e988 stock and see if that works? thats what it reads it as right before it closes idk maybe its cause 8.1 but dont think so the app doesnt even open in english idk seems like everyone elses is.
Honestly I don't know why it isn't in English. It is for me but I'm on the stock E980 FW. All I can think is you, somehow, flashed the Korean version of the F240. Just as a precaution I keep a flashable stock 10k on my sd card just in case the need for it arises. But not being able to get into recovery isn't helping your cause here. Keep an eye on the battery as well. If it starts draining down too far just power it off and let it charge more so you don't get so involved with the phone you forget. The problem for me is I'm more of a hands-on person. it's harder for this type of person to walk someone through fixing a gadget.....lol.
An honestly man, I don't know how else to help you. Hopefully someone allot smarter than me is gonna come along any minute now that will know exactly how to fix this issue. All I can suggest now is to keep searching the forum for this type of problem and find a solution. Just don't lose your temper or give up. The solution is here somewhere. I'll search around too. See what I can dig up.
exactly what i thought man ahhh and idk why its not in english either i mean im on my pc there should be no reason for it not to work. Idk I appreciate all your help. havent been in trouble like this since back years and years ago on the old first gen g1 hahahah. and ya flashing the Korean version of the F240 is what i did i really hope there is a way to fix this i had a backup but external sd card quit working so tranfered it on the phone when it still worked flashed back seemed fine went to try flash the e980 baseband and still no good now im just stuck. tempted to try and see if the e988 will work since it wont flash the stock e980 sorry for keep on talking im just going crazy.
It's all good man. I understand your frustration. I have been doing this for a long time now as well. Most of my experience is with moto's and Samsungs. Now I'm learning all over again with another phone myself. But anywho, yeah, give that a try. Flash the e988 if you can. At least if it works you can get into your recovery and sd card to try and flash it back to stock from there and be back on the E980 fw. It's like going around your ass to get to your elbow but hey, if it works who cares right?.....lol. And if you get it working again I suggest putting a flashable stock zip on your sd card just in case. But as I said before, It doesn't help if you cant get into recovery. But when you can it can be a life saver.
I do remember reading there are permission issues if you're running windows 8 or 8.1 on that last method I linked you to. You may want to look into how to overcome that issue and try again. If you haven't already that is.
Hmm at least it says e980 now but can't get past this
Sent from my d2lte using xda app-developers app
Attempted to go back to stock ROM. From TWRP, I wiped everything except external and shutdown. Attempted to restart and nothing. Deader than or door nail. Pulled the battery and held down the power button for over a minute with no affect. Battery was 75% charged with I performed the wipe. I connect to phone to my pc and get a "USB Device Not Recognized"
Is the phone a lost cause?
Thanks,
Jeremy
gimmezell said:
Attempted to go back to stock ROM. From TWRP, I wiped everything except external and shutdown. Attempted to restart and nothing. Deader than or door nail. Pulled the battery and held down the power button for over a minute with no affect. Battery was 75% charged with I performed the wipe. I connect to phone to my pc and get a "USB Device Not Recognized"
Is the phone a lost cause?
Thanks,
Jeremy
Click to expand...
Click to collapse
If you wipe everything but extSdCard, you must flash something. Either flash stock tar update in Odin or flash a custom ROM in recovery.
Help any?
Sent from my SM-N920P using Tapatalk
Yes, I know. I was going to go into download mode to Odin stock ROM but the phone will not even turn on anymore.
gimmezell said:
Yes, I know. I was going to go into download mode to Odin stock ROM but the phone will not even turn on anymore.
Click to expand...
Click to collapse
OK. Did you try a long battery pull and try again?
Edit: I may have misunderstood you but you did say you tried to restart. Did you mean download mode with long press of volume up, home plus power button combination.
Sent from my SM-N920P using Tapatalk
Sorry for any confusion. I pulled the batter for a good ten minutes and still unable to turn the phone on. Plugged the phone into a charger has no effects on it either.
So download and recovery key sequence fails for both? Plugging in charger or USB to PC, no beep or display?
What version of TWRP were you using? If 3.0, did you get it from official site? How did you install it?
Sent from my SM-N920P using Tapatalk
Yes, both download and recovery key sequences fail. Plugging into charger, no charge LED comes, no haptic feedback, no beep or display. When I plug it into my computer it says "USB Device Not Recognized".
EDIT - I'm pretty sure my bootloader is hosed.
gimmezell said:
Yes, both download and recovery key sequences fail. Plugging into charger, no charge LED comes, no haptic feedback, no beep or display. When I plug it into my computer it says "USB Device Not Recognized".
Click to expand...
Click to collapse
Just curious about the TWRP version. There's been a couple or more cases like yours and it seemed to show up about the time users reported issues with TWRP update.
I think you should get the phone checked by a tech or engineer. Sprint has been helpful to users having hardware failure with issues like updates bricking the phone. With flagship phones not selling well and carrier wars, retention is key and nearly economical right now.
Sent from my SM-N920P using Tapatalk
Yeah, TWRP 3.0 did come up on my searches. I did have TWRP 3.0 installed that I got from their official site.
I did see the below post on how to unbrick that tells me it may be possible to a Note 4 image onto an sd card.
http://forum.xda-developers.com/showthread.php?t=2660566
Did this work for you? I also have twrp 3.0 and hope to not run into an issue like this.
Alakazamm said:
Did this work for you? I also have twrp 3.0 and hope to not run into an issue like this.
Click to expand...
Click to collapse
I'm using 3.0 too but I waited for the official version that worked and flashed in Odin. No issues for me. Hoping it stays that way.
Sent from my SM-N920P using Tapatalk
gimmezell said:
Yeah, TWRP 3.0 did come up on my searches. I did have TWRP 3.0 installed that I got from their official site.
I did see the below post on how to unbrick that tells me it may be possible to a Note 4 image onto an sd card.
http://forum.xda-developers.com/showthread.php?t=2660566
Click to expand...
Click to collapse
Alakazamm said:
Did this work for you? I also have twrp 3.0 and hope to not run into an issue like this.
Click to expand...
Click to collapse
I did not attempt what was done in the link I posted in my previous post. Today, I mailed the phone off to someone that offers a de-bricking service. Hopefully, they can recover it. I will I knew exactly happened as I did the same procedure many times before. Right now I'm retro-ing it and rocking my Note 2 with STOCK firmware and everything works. :good: :laugh:
@samep mentioned that there were other TWRP 3.0 users that experienced to the something I did or similar. I'm just curious where those threads/posts are.
gimmezell said:
I did not attempt what was done in the link I posted in my previous post. Today, I mailed the phone off to someone that offers a de-bricking service. Hopefully, they can recover it. I will I knew exactly happened as I did the same procedure many times before. Right now I'm retro-ing it and rocking my Note 2 with STOCK firmware and everything works. :good:[emoji23]
@samep mentioned that there were other TWRP 3.0 users that experienced to the something I did or similar. I'm just curious where those threads/posts are.
Click to expand...
Click to collapse
First, I want to acknowledge that what yourself and others have experienced is personal and disappointing. eMMC flash is not the most reliable, efficient and cutting edge memory but it's common to cell phones of previous generations like ours.
It's not easy making an argument that UFS 2.0 used in 2015 Samsung phones is more reliable and less prone to failure but it is faster, lower voltage and far less prone to heat buildup with increased data transfer. So I think that makes a point in favor of the newer tech. Building ART/dalvik-cache can generate a lot of heat as well as 4k recording. The eMMC NAND contributes to that and could also be its undoing.
http://m.tech.firstpost.com/news-an...move-next-gen-ufs-2-0-memory-2015-242072.html
Interesting to see if UFS memory is any more reliable in the months ahead and if Samsung continues to use it this year with micro sdcard making a return to S7. But flashing alone, we know is risky. Proving an application or particular flash causes such would be difficult to prove and it wasn't my intent to point at a particular shared development that is shared freely on XDA. I could have worded that better when I said I hoped my phone continues with no issues- not meaning it to sound like the concern because I flashed the new TWRP. I was merely pointing to the increase of flashing lends to more hardware failure in this forum. We've seen this also with updates and increased flashing when users are confused about which stock tar to flash or thinking they can just go back to KitKat through Odin of KitKat tar. Not blaming users for their failures; anyone of us can the victim with a single flash, not to mention the many flashes and extended boots that are added to a rooted phone's life. To add to that, Samsung still has fixes pending and concerns with download mode.
http://www.slashgear.com/samsung-galaxy-smartphones-receive-security-update-25424269/
Rooted phones may not be getting these updates until another stock tar is released.
Anyway, related or not, here's some other recent failures. There may be others but I'm not trying to prove anything other than saying it seems we have more memory failures than we should on the Note 4.
http://forum.xda-developers.com/note-4-sprint/help/hard-brick-sudden-death-mobo-fried-t3316335
http://forum.xda-developers.com/note-4-sprint/help/screen-pit-partition-firmware-install-t3316162
http://forum.xda-developers.com/showthread.php?p=65018833
I do hope you get a successful and economical repair. It's good that you have a backup phone. And I hope you'll update this thread with progress and result. Best wishes.
Sent from my SM-N920P using Tapatalk
Thank for the info and links @samep.
Update
I sent my phone off last Wednesday to hopefully have it de-bricked and I am happy to report that I will have it back tomorrow. Apparently, some how the custom recovery wiped the boot partition. I'm tempted to keep it stock as my backup phone is stock, uprooted and it just works. Ha
I've ordered a pair of Acker batteries because I was told by Joe, the person who un-bricked my phone, that the battery would drop from 100% to 80% within five minutes.
Needless to say I'm happy to get my Note 4 back tomorrow.
Sent from my SPH-L900 using Tapatalk
Hey guys,
got a big issue: My LG G3 D855 International Version is not working properly. I was using Fulmics Rom (6.5 I believe).
At some point phone just turned off. I was rebooting and then there were some weird noses from the speaker after rebooting into the system, like cracking.
This happened twice. Afterwards it did not boot at all (Not sure if it bootlooped or went just straight black).
I then went into TWRP recovery and wanted to wipe and flash Fulmics.
Everytime I want to do this i get through Aroma Installer and then at the Installation part at around 10% it goes black again.. (first time I was afraid I bricked it but it happens exactly like this all time)-
Same thing happens when I want to restore an old Backup file. It goes to around 200 MB and then dies.
Already changed the battery to a new one, so that's not the deal. I'm afraid this is an hardware issue? Hope you can help!
Edit: Reproducable when I'm doing tasks so that CPU heats up (as shown in TWRP).
Does the phone work properly on stock? If it does not, it sounds like a hardware problem.
Well, problem is I can't flash anything so impossible to tell. As I said, everytime I do something more that just moving through TWRP phone dies..
theFUNKY**** said:
Well, problem is I can't flash anything so impossible to tell. As I said, everytime I do something more that just moving through TWRP phone dies..
Click to expand...
Click to collapse
Did you try flashing a KDZ or TOT firmware?
Saratoga79 said:
Did you try flashing a KDZ or TOT firmware?
Click to expand...
Click to collapse
That sounds like a really bad idea if the phone keeps turning off when processing ramps up. If it quits during the flash, he'd be screwed.
Oven trick to prolong the life by a little bit, maybe?
Yeah, I'm afraid KDZ TOT firmware flashing would screw me up even more.
If there are no other ideas I'll go with some rougher methods like trying to cool down the CPU with heatpaste-trick or in the end oven.
Ordered a new phone anyway and got nothing to lose. I'll let you guys know!
theFUNKY**** said:
Yeah, I'm afraid KDZ TOT firmware flashing would screw me up even more.
If there are no other ideas I'll go with some rougher methods like trying to cool down the CPU with heatpaste-trick or in the end oven.
Ordered a new phone anyway and got nothing to lose. I'll let you guys know!
Click to expand...
Click to collapse
Plug your phone to the charger when you install Fulmics.
If you see any difference's then it's your battery and you'll need to replace it.
It is working now!
What did I do: Baked the Mainboard for 10 minutes at 200° C. Additionally i applied thermal paste on the CPU.
Running like a charm for two weeks now.
I request all to first please understand the problem and give me suggestions as this gets slightly bonkers.
Thanks in advance.
So I had my OnePlus3 A3003 repaired for water Damage from a professional non OnePlus service called Yaantra. They basically replaced the Mother Board is what they say.
I have no reason to doubt, the Phone works flawlessly, everything is working nicely, from the camera to the battery performance and charging and SOT, the performance is as expected.
Only it runs on Oxygen OS 3.1.2.
Now I first got an OTA update notification for 4.5.1 and I immediately started downloading and attempted install. It went through the whole cycle of installing smoothly and after the first reboot, it splashed a linux Penguin Logo and then turned off, never turned back on. I manually pressed the power button after a long time but it again showed the Penguin for a few seconds and powered off. I figured that the phone is bricked. (this time my boot loader was Locked)
I had to follow the 2nd Method of the Mega Unbrick guide and got my phone up and running back on 3.1.2
I still get the OTA update but this time i thought I'll download the latest stable build of 5.0.1 and install it via ADB sideload. with the appropriate recovery
The phone got bricked again.
Then I thought of Installing regular TWRP after unlocking bootloader and flashed 5.0.1, No luck. had to unbrick it again.
Then I tried bluspark.
Then I flashed Experience OS with the latest firmware. It went through the entire cycle and installed but this time after it turned off and on again I was greeted to a new error.
it was in red saying "Battery does not match" in English and then in some Asian language. I was able to unbrick from that state as well.
After that I have tried Lineage OS but with same result. I get "Battery does not match"
Then I unbricked the device and i tried #*808# and checked Charger option. it says "itech_3000mah" that doesn't sound original, is it?
Basically no matter what I flash my phone gets bricked.
With Custom ROMs I get the "Battery does not match error"
With Official ROM I get the penguin Logo.
I've tried all sorts of Combination of Recovery and ROMs to no luck.
So far the only thing I haven't tried is flashing another Kernal.
Have to come back to 3.1.2 after unbricking which works flawlessly every time with no problems AT ALL. I wish to upgrade to the latest Official build of OOS (but i am ok with unofficial as well)
Alright, this is a new one.
Have you checked your system information with the app "AIDA64"? Download that app, and post a screenshot of what's under the System tab.
thes3usa said:
Alright, this is a new one.
Have you checked your system information with the app "AIDA64"? Download that app, and post a screenshot of what's under the System tab.
Click to expand...
Click to collapse
Thanks for the eyeball
AbhiM7 said:
Thanks for the eyeball
Click to expand...
Click to collapse
Okay, although AIDA64 doesn't indicate that your Motherboard is a Chinese mockup Mobo, I still suspect that the "Penguin" logo is some kind of third-party under the hood software.
Have you tried the unbrick tool which includes 5.x.x?
thes3usa said:
Okay, although AIDA64 doesn't indicate that your Motherboard is a Chinese mockup Mobo, I still suspect that the "Penguin" logo is some kind of third-party under the hood software.
Have you tried the unbrick tool which includes 5.x.x?
Click to expand...
Click to collapse
Oh I thought there was only the 3.1.2 available in the unbrick tool.
I would appreciate a link for the 5.x.x unbricking tool.
Which should hopefully include all he required firmware and recovery stuff.
What are other ways I can know if my Mobo is a Chinese mock-up?
AbhiM7 said:
Oh I thought there was only the 3.1.2 available in the unbrick tool.
I would appreciate a link for the 5.x.x unbricking tool.
Which should hopefully include all he required firmware and recovery stuff.
What are other ways I can know if my Mobo is a Chinese mock-up?
Click to expand...
Click to collapse
Hi firstly, you shouldnt have trusted your OnePlus3 with 3rd party service like Yaantra. After service they will deny any changes to your hardware and ask stupid questions "isn't your phone receiving call when we gave it back?"
After seeing your posts, it seems that they didn't flash the device properly. I seriously doubt your battery has been Jacked and replaced with some 3rd party mockup.
A simple search in forums can lead you to 5.x.x unbricking tool.
And your final question. If your phone doesn't bootup even after this, most probably you're dealing with some kind of mockup in the chipset.
Did you solve this issue? If so post how here so that others can use it later.
Thanks
SivaMaxwell said:
Hi firstly, you shouldnt have trusted your OnePlus3 with 3rd party service like Yaantra. After service they will deny any changes to your hardware and ask stupid questions "isn't your phone receiving call when we gave it back?"
After seeing your posts, it seems that they didn't flash the device properly. I seriously doubt your battery has been Jacked and replaced with some 3rd party mockup.
A simple search in forums can lead you to 5.x.x unbricking tool.
And your final question. If your phone doesn't bootup even after this, most probably you're dealing with some kind of mockup in the chipset.
Did you solve this issue? If so post how here so that others can use it later.
Thanks
Click to expand...
Click to collapse
I am downloading this msm recovery
https://forum.xda-developers.com/on...k-phone-msmdownloadtool-v3-0-6-t3575801/page2
and try for now.
I'll post my experience soon.
An official technician from OnePlus told me that fake batteries don't work well / won't find with OnePlus at all so there is 99% chance that it's not a mock-up.
thes3usa said:
Okay, although AIDA64 doesn't indicate that your Motherboard is a Chinese mockup Mobo, I still suspect that the "Penguin" logo is some kind of third-party under the hood software.
Have you tried the unbrick tool which includes 5.x.x?
Click to expand...
Click to collapse
The penguin is the old school linux kernel panic screen. It used to come on when kernel panic prevented the device from booting.
What I am thinking is that is not the right board for that device, which explains the battery error. The custom rom battery error could be gotten around I am sure. Just so it boots.
zelendel said:
The penguin is the old school linux kernel panic screen. It used to come on when kernel panic prevented the device from booting.
What I am thinking is that is not the right board for that device, which explains the battery error. The custom rom battery error could be gotten around I am sure. Just so it boots.
Click to expand...
Click to collapse
I see, do you know how can I get around the battery error?
And should I flash a new kernal to get around the Linux penguin warning?
What are my options other than the mega unbricking with a newer version of OOS
AbhiM7 said:
I see, do you know how can I get around the battery error?
And should I flash a new kernal to get around the Linux penguin warning?
What are my options other than the mega unbricking with a newer version of OOS
Click to expand...
Click to collapse
Sure. You will have to hook up the device to the pc while it is trying to boot and grabbing a logcat. This will tell you exactly what is failing. The build a rom that goes around the issue.
To be honest. I don't know what will work for sure but the logcat will tell you just what you need to know.
Piece of advice. If you are gonna do repairs like this. Do them yourself. Even if you fail you will be sure of the parts at least which you can't be with amature repair techs. Too many use knock off parts.
zelendel said:
Sure. You will have to hook up the device to the pc while it is trying to boot and grabbing a logcat. This will tell you exactly what is failing. The build a rom that goes around the issue.
To be honest. I don't know what will work for sure but the logcat will tell you just what you need to know.
Piece of advice. If you are gonna do repairs like this. Do them yourself. Even if you fail you will be sure of the parts at least which you can't be with amature repair techs. Too many use knock off parts.
Click to expand...
Click to collapse
Am not that much of an expert. I don't know about using logcat but I just read a little about it and am going to try.
I'll post my experience soon.
Should I also take the phone to an official OnePlus technician and ask them to check if the chipset/battery is a mock up, they should be able to tell right?
AbhiM7 said:
Am not that much of an expert. I don't know about using logcat but I just read a little about it and am going to try.
I'll post my experience soon.
Should I also take the phone to an official OnePlus technician and ask them to check if the chipset/battery is a mock up, they should be able to tell right?
Click to expand...
Click to collapse
That depends on how good they are but to be honest if it is a really good fake then it may fool even the best. But it cant hurt.
Actually I got stuck in the same situation. I also tried different ROMs but with custom ones I get the Replace Battery error and with official Roms I get the penguin. Is there any way to get rid of the Battery error by modifying the kernel or something?
You've a motherboard of OP3T not OP3
Try oneplus 3t full ota
Cheers