Develop Bugs

[Q] Soft Brick,TWRPvsClockwork-Avoiding same mistakes

Dodged a bullet yesterday. FreeGee unlock, chose TWRP and then went to flash stock v9 odex. Wiped Cache/Dalvick and then flashed. Upon reboot I saw LG screen then black and nothing. Tried to LGPNST from download mode with LG driver and could not detect phone. After messing around in TWRP for about 2 hours where I performed about every function available (just before throwing the phone into the fireplace), I queued the z9 odex twice let TWRP flash it twice and everything worked. Here's the thing, my wife's phone is incessantly prompting to update, so I need to flash her phone. Should I use clockwork? Anyway to avoid a similar issue and near total bricking of her phone?

Same thing using Clockwork on wife's phone. Now I'm trying everything to get it back. Still have recovery, but unable to complete system reboot. Black screen. Used to flash evo all the time, never an issue. Now I'm 0 for 2 with a miraculous boot and update on my phone. This one doesn't look like I'm going to get as lucky. CWM is a bigger pain too. Frustrated. Not looking forward to lgpnst (still not sure how it all works) and then trying this mess again.

I had a similar problem to yours last night to. Except I didn't really do anything to it. It was just sitting there charging and I took it off the charger and it was doing some kind of boot loop, But every so often it would just stop on a black screen. I lgnpst about six times back but after running root and freegee I would try to get into bootloader and it would do it again. Eventually I tried doing freegee with clockwork instead and it did it again, Than I forced the phone off and pluged it in to my computer to get ready to lgnpst again so I could at least use the phone. All of a sudden I look at the screen and there was a battery charging animation. And then unpluged it and for kicks turned it on and it booted up no problem. Then I tried booting into bootloader and all works now. It was really strange, I did put twrp back though. I like it better then clockwork. I think I sore you asking questions in irc while I was in there asking question to ha.
-Frank

MikeDroid said:
Same thing using Clockwork on wife's phone. Now I'm trying everything to get it back. Still have recovery, but unable to complete system reboot. Black screen. Used to flash evo all the time, never an issue. Now I'm 0 for 2 with a miraculous boot and update on my phone. This one doesn't look like I'm going to get as lucky. CWM is a bigger pain too. Frustrated. Not looking forward to lgpnst (still not sure how it all works) and then trying this mess again.
Click to expand...
Click to collapse
I had the same thing happen and couldn't figure it out so I took it back to sprint told them I did the update and it messed up so they gave me a new phone for 35 bucks and from now on im staying STOCK.........................

DId you try to lgnpst back yet? That may help you.
-Frank

Frank...yup that's how mine worked. Just not sure how to do this. I don't think my failed lgpnst attempts did anything, b/c mine took the update eventually. I'll keep trying. This phone is so temperamental. Does Shellnut have some input on this problem? I can't figure out why some phones take and others don't when doing the same thing.

Talk to Shelnut2 over pm or find him in irc. I just found out there is a special version of freegee that may fix the problem. I seem to have fixed mine but I sent him a pm asking some questions about the problem. I think you are going to need to lgnpst back. Then root and run the special version of freegee. You have to get it from him because it does some things different that may brick the phone permanently. Thats why you have to ask for it. From what I understand it fixes that kind of problem.
-Frank

I will. I'm going to see if this thing will self correct. Otherwise I will check with him on that. The LGPNST is something I'm not looking fwd to doing.

LGPNST is not detecting phone in dl mode but does detect when in recovery. This SUCKS. Frustrated and out of ideas.

When you installed lgnpst did you install the file that says auto-lgnpst? Also did you run install.bat as administrator?
-Frank

frankt2012 said:
When you installed lgnpst did you install the file that says auto-lgnpst? Also did you run install.bat as administrator?
-Frank
Click to expand...
Click to collapse
Not sure if I ran as administrator. Assumed that I did. As a casual hack, I'm in over my head.
Sent from my LG-LS970 using xda app-developers app

Ok. Ran as admin. Won't even detect device. Anyone in DFW area proficient in this stuff who I could pay to lgpnst this thing?

Bricked OG
MikeDroid said:
Ok. Ran as admin. Won't even detect device. Anyone in DFW area proficient in this stuff who I could pay to lgpnst this thing?
Click to expand...
Click to collapse
I've been working on mine for a day and a half. I can't figure out the thing with renaming the ".tot" file to ".bin" because I don't even see a .tot file. After I unzipped the big ZV7 there was only one file without an extension so I can't figure out if thats the one I'm supposed to rename. Can you point me in the right direction?:crying:
[ I figured it out, I had to go into Preferences on my file explorer and set it to show all file types...DUHHH ]

In Windows, go to control panel, file settings, show file extensions. Something like that.
Sent from my LG-LS970 using xda premium

Finally got bit working. No more issues. Non of this stuff is very intuitive when your in panic mode. All is good now though.
Sent from my LG-LS970 using xda app-developers app

Apps
MikeDroid said:
Dodged a bullet yesterday. FreeGee unlock, chose TWRP and then went to flash stock v9 odex. Wiped Cache/Dalvick and then flashed. Upon reboot I saw LG screen then black and nothing. Tried to LGPNST from download mode with LG driver and could not detect phone. After messing around in TWRP for about 2 hours where I performed about every function available (just before throwing the phone into the fireplace), I queued the z9 odex twice let TWRP flash it twice and everything worked. Here's the thing, my wife's phone is incessantly prompting to update, so I need to flash her phone. Should I use clockwork? Anyway to avoid a similar issue and near total bricking of her phone?
Click to expand...
Click to collapse
Always backup your phone before tinkering with system files, and experimenting with launchers, kernals etc.
Titanium backup in WORTH the investment to upgrade to PRO.
Rom manager is a good one to boot directly into recovery without fiddling in the fastboot menu. And for backing up settings and roms.
Always KNOW what your doing. lol. sometimes even the big guys forget this. RESEARCH!

[Q] HELP I think that I have finally bricked my phone!

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

can only get to download mode on my e980 but now i cant not flash back to stock

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

[Q] Who do I need to pay to get this phone unbricked...

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.

Geethree often wont power on until I do a battery pull

I've had this problem since I purchased the phone new. Often times when I go to restart the phone or if after simply powering it off or needing to do a battery pull the phone wont power up unless I pull the battery again.
I've had a couple different roms but I've never flashed a new kernel.
What do you guys think the problem could be?

cliffordconradsumner said:
I've had this problem since I purchased the phone new. Often times when I go to restart the phone or if after simply powering it off or needing to do a battery pull the phone wont power up unless I pull the battery again.
I've had a couple different roms but I've never flashed a new kernel.
What do you guys think the problem could be?
Click to expand...
Click to collapse
This is the bootstack.
You can extract it from the official kdz or find one on internet for your device and flash it.

Ok, great! I'll figure out how to do this soon.
So to clarify, does it not matter which kdz I extract it from or what ROM I'm running?

Just getting around to this now that my phone is starting to give me more problems.
I think I found the official KDZ for my F400K here
And I'm hoping to extract the boot stack with this KDZ and TOT Extractor by bullghost found here.
If anyone has any pointers I would be much obliged

Ok, well as it turns out have no idea what I'm talking about or doing.
If anyone could point me in the right direction I'd be very grateful.

Try changing the battery ur g3s battery too weak buy geniune or branded higher mAh

jinderation said:
Try changing the battery ur g3s battery too weak buy geniune or branded higher mAh
Click to expand...
Click to collapse
I have 3 batteries, two of which are OEM. That's not the problem.

cliffordconradsumner said:
I have 3 batteries, two of which are OEM. That's not the problem.
Click to expand...
Click to collapse
flash custom kernels i also had this random reboot issue often times my D851 went dead on stock MM with stock kernel 3.4.0 ...i used solid kernel had no random reboots no dead phones battery life was worst used xceed kernel couldnt used xposed battery life was ok reboots yes dead no now gabriels kernel dont know just flashed rit now

jinderation said:
flash custom kernels i also had this random reboot issue often times my D851 went dead on stock MM with stock kernel 3.4.0 ...i used solid kernel had no random reboots no dead phones battery life was worst used xceed kernel couldnt used xposed battery life was ok reboots yes dead no now gabriels kernel dont know just flashed rit now
Click to expand...
Click to collapse
Thanks for the tip...I may try that next, but I want to try what @RapHaeL_4_4_4_ suggested by extracting the boot stack and flashing it.
RapHaeL_4_4_4_ said:
This is the bootstack.
You can extract it from the official kdz or find one on internet for your device and flash it.
Click to expand...
Click to collapse
I was able to extract boot.bin and aboot.bin and am going to attempt to flash them now. Not sure if I can flash a bin file or not as I've never tried but here it goes.

cliffordconradsumner said:
Thanks for the tip...I may try that next, but I want to try what @RapHaeL_4_4_4_ suggested by extracting the boot stack and flashing it.
I was able to extract boot.bin and aboot.bin and am going to attempt to flash them now. Not sure if I can flash a bin file or not as I've never tried but here it goes.
Click to expand...
Click to collapse
You need: dbi.bin, laf.bin, persist.bin, rpm.bin, sbl1.bin, tz.bin from the stock kitkat rom.
Once you have them you can download this, replace all the file listed above and then flash it.