yashsingh1/xdaforums huggingface dataset:
[General Questions and Answers] cosim:
Thank you for feedback!

Could you please provide a bit more details about which version you flashed?

I tried several versions for different regions but got the same negative result...
[General Questions and Answers] marvinalnashi:
What I can see is that you've done a messy job with getting the correct drivers.

Uninstall everything and only install the minimalistic adb+fastboot package, which you can find here on xda.

Plug in your phone to your pc with usb debugging enabled and select mtp mode instead of charging mode.

Then go to windows device manager and check if there's an exclemation mark next to your phone driver.

Then open up an adb cmd and type adb reboot bootloader to reboot to fastboot, in device manager there should be a new detected fastboot device.

If this has an exclemation mark too, you will have to right click and update the driver manually by selecting the device from the list.

There should be a lot of device, including 2 or 3 adb devices.

Choose one to update to and you're good to go.

---------- Post added at 03:59 PM ---------- Previous post was at 03:58 PM ----------

As for the .ftf, I think you've converted it using an outdated method. I will upload my own .ftf tonight.

---------- Post added at 04:04 PM ---------- Previous post was at 03:59 PM ----------

I'm going to upload my .ftf today or tomorrow, the one which fixed all the problems for me.

Yes it's the latest version .156 (R4A) and if even this doesn't work, it'll mean you haven't flashed it the right way. Don't forget to disable sim provider additions by excluding them from the TA part.

I'll post the link after the upload is finished, it's a huge file so it's obviously going to take some time :p
[General Questions and Answers] IrvingWash:
Thank you for help. I will reinstall Windows on my laptop to have an absolutely clean OS and will install the drivers anew. Any clues where I could get wrong? Maybe links to the actual drivers?
[General Questions and Answers] IrvingWash:
After some manipulations I have no exclamation mark in the menu (which means drivers are ok), the problem is that .23 flashtool doesn't see my ftf which I got from a user who actually used this combination and it worked for him.
[General Questions and Answers] ch3mn3y:
[MENTION=8098883]IrvingWash[/MENTION]

Are You sure it's not an archive which need to be unpacked? Is it in the right directory (C:\Users\<user>\.flashTool)? Did You try to start Flashtool with admin rights?
[General Questions and Answers] IrvingWash:
I'm positive and tried everything you wrote. I also tried to move the . ftf in another folder and set flashtool to look for it there - despair.

---------- Post added at 09:06 PM ---------- Previous post was at 08:54 PM ----------

I downloaded an older version of flashtool (.18), it sees the .ftf but doesn't recognize the phone (syncing with github fails,"no device" error (drivers are ok), when I'm flashing, device selector window appears and it's totally empty.
[General Questions and Answers] marvinalnashi:
I've never seen anyone with your case before.

Download my own made .ftf, the one you've got might be corrupted or bundled in a wrong way.

Download my .ftf from here and start all over again on a different pc or laptop.

Don't modify anything in the .flashtool folder, leave it all as it is.

I've made a guide here on xda, follow the steps precisely and nothing should go wrong.

And always use the latest version of flashtool, if it still doesn't work try using flashtool64 instead. If that doesn't work run flashtool64 as an administrator. If it still doesn't work please check if your adb and fastboot are working (assuming you know how to use and boot them up).

If not, take a screenshot of your windows device manager and send it to me, you're most likely doing something wrong but it's hard to figure out without knowing the cause of that git error.
[General Questions and Answers] IrvingWash:
What I have done on a freshly reinstalled Windows:

1. Downloaded and installed Xperia Companion

2. Checked the "exclamation mark", as you said, with my phone turned on in MTP mode and after rebooting via adb in fastboot mode - everything is fine.

3. Downloaded latest flashtool with .ftf which was used by other guy

4. Installed flashtool, installed drivers from ft's folder (with turned off driver signature checker (i'm not sure how it is called in english, the thing you need to do in Windows 8.1 to install them properly), and with vista sp2 compatibility mode).

5. Opened ft to let it create ".flashtool" folder in "User", placed in "firmwares" the ftf

6. As a result - ft doesnt recognize the file

After that, I've tried absolutely the same steps with older version of flashtool. It sees the .ftf, but doesn't recognize my phone. To be said, I've did these steps on another laptop with Win 8.1, one with Win 7 and another one with Win 8.1 with english localization (because I thought that there is an issue because of cyrrillic letters). I have tried different usb ports (2.0, 3.0)

No bloody difference.

Everywhere possible I was running things as administrator. Used only flashtool64.

Tomorrow I will try to use the latest ft to see if it would recognize my phone though (because I forgot to do that earlier) and the "x32" version of the tool.

I appreciate all the help, guys, I'm sorry for my english, probably it's hard for you to understand what I have wrote because of my linguistic skills, perhaps my messages looks disrespectfully, but I assure you I'm thankful and I respect your time.
[General Questions and Answers] IrvingWash:
After some research I've noticed that my flashtool says "Loaded 0 devices" after github syncing. I thought it's my internet provider issue (because it's really bad one but I can't change it). Asked my friend to check the tool (because he is a subscriber of one of the best providers), so he's got "Loaded 94 devices", which means that all my troubles are because of my internet connection and it explains why you guys never heard of such a problem. I'm going to the friend tomorrow with my E5, hopefully everything will be fine.
[General Questions and Answers] victhor343:
It's great found a root method, but I wanted with locked bootloader for Xperia E5 f3313
[General Questions and Answers] jan.zogmund:
Hi guys. I was wondering if anybody from experienced developers tried porting lineage os rom for our device. We do not have official support because of mediatek chipset I guess. Here I found one link where developes ported lineage os rom for device which has identical hardware to our E5. Would it be possible to create something for us from this? Thanks https://xdaforums.com/android/software/lineage-14-1-1-intex-aqua-4g-t3563679
[General Questions and Answers] Lucatechno:
Sorry,but modified kernel has a many problem: (i have the last firmware italian r5a....)

- work only stock camera app (any other camera ex. whatsapp web don't work)

-bluetooth don't work fine whit ANY hands'free! (no problem bluetooth audio protocol)

- the torch work fine one time only!

-touch screen problem on the left part of screen.

Regards

Luca
[General Questions and Answers] victhor343:
Hey guys, I accidentally deleted my default pictures in internal storage on Xperia E5 I can't find it, I want it please!
[General Questions and Answers] marvinalnashi:
I and some other users are using the custom kernel too, without having any of the by you mentioned problems.

I'm sorry to have to tell you that you might be having a faulty device.

EDIT: DON'T USE THE KERNEL ON AN F3313, IT'S FOR F3311 ONLY.

---------- Post added at 11:08 AM ---------- Previous post was at 11:05 AM ----------

Hey, just wanted to tell you guys that I've managed to set up Ubuntu correctly and I've gathered all of the available sources.

I only need the proprietary vendor bassoon blobs, before I can compile the first LineageOS 14.1 testing build for this device.

Can anyone link or extract those blobs for me? I'm almost ready to compile roms.
[General Questions and Answers] Othinus:
The kernel is only for F3311, no there are for F3313
[General Questions and Answers] AlphaShadow88:
How i can unlock bootloader?

As I can unlock the bootloader if you tell me this.

Bootloader unlock allowed: No

Help me please :crying:
[General Questions and Answers] marvinalnashi:
It indicates that you haven't unlocked your bootloader successfully, use the official bootloader unlock method provided by Sony and use the code for the Xperia E4 or E4g on their site.

Also make sure to enable oem unlocking in developer settings.
[General Questions and Answers] MAREK10747:
If you are interested custom rom try this rom https://xdaforums.com/android/development/clean-os-xperia-e5-f3311-f3313-stable-t3651455/post73284574#post73284574
[General Questions and Answers] victhor343:
I want root without unlock bootloader if I unlock the bootloader could get boot loop, looks like risky
[General Questions and Answers] hpdebug:
Does this TWRP support Xperia E5 F3311 Build Number 37.0.A.2.108 ?

I tried several times and get same error.

Installing customized BOOT.IMG with command :

fastboot flash boot boot.img

Result:

target reported max download size of 134217728 bytes

sending 'boot' (9302 KB)...

OKAY [ 0.900s]

writing 'boot'...

FAILED (remote: Command not allowed)

finished. total time: 0.910s

Installing TWRP Recovery with command :

fastboot flash recovery twrp.img

Result:

target reported max download size of 134217728 bytes

sending 'recovery' (11974 KB)...

OKAY [ 1.159s]

writing 'recovery'...

FAILED (remote: Command not allowed)

finished. total time: 1.168s

This device is unlocked, with build Number : 37.0.A.2.108

Should I upgrade/downgrade firmware to work with all this Rooting ang twrp stuff?

Does somebody here has firmware ver.156's link?

Need help for this Xperia :_/|\_
[8125, K-JAM, P4300, MDA Vario ROM Development] jwzg:
Here's a modified 15342 ROM for cooking. No tweaks or anything, just a stable base.

Changes:

1) No Windows Live

2) New OEMAPPS (all control panel icons are now WM6 style)

3) WiFi activates on first tap

4) 8 button comm manager with flight mode

5) HTC Comm Manager now appears in connections control panel instead of the Wireless Manager

6) Windows Update is now a control panel icon instead of a program icon

7) Office 2007 included with zip and fax viewer

This is as clean as the original 15342 build. You may extract and use as you wish.

Link
[8125, K-JAM, P4300, MDA Vario ROM Development] nottoosmart:
Have you been running this? Can you post the issues it has?
[8125, K-JAM, P4300, MDA Vario ROM Development] jwzg:
Just a few days. No issues so far other than the typical .318 limitations. Drivers are all the same. I took out the Windows Live stuff because there are newer versions available and even the factory ROM for the Hermes doesn't have it. This is pretty much the same thing as we did with the AKU 3.3. Just cleaned up for someone to cook. Kind of like raw meats and veggies.
[8125, K-JAM, P4300, MDA Vario ROM Development] jwzg:
One issue just discovered: If you activate the AutoSingleLineDatePlugin through the registry, you cannot make any changes to the today screen without resetting the PPC. Wierd, but I think this may be related to the registry editor. I've never had this issue before.
[XDA Assist] trysten711:
Zte N9515 Boost Mobile Warp Sync

I've had the zte phone for about a year. It was rooted through king root, no custom recovery and stock ROM. I received an OTA update one day and unrooted the phone to do the update, which soft bricked the phone. I have done everything I've read from other people on how to fix the issue. I've done flash tools, zte updates, contacted zte... Who, I might add, isn't very friendly with the answer to my issue without paying 100$... The errors I get on zte open is a partition mbn error. Adb sideload errors are E:2 footer[2]=0x00 footer[3]=0x00 E:signature verification failure installation aborted. I've downloaded zip files, pit files, bin files, flashing tools, zte open, android studio- which gives me an adb rejected shell command error- and I haven't come up with a way to fix this issue. I need help getting the zte n9515 working again please
[Galaxy S6 Edge Q&A, Help & Troubleshooting] N3xusNe0n:
Hello,

after i tried to root my phone, it just stucks with the message that no recovery is installed...

I can't go in the Download mode because, i figured out that my vol+ and vol- buttons aren't working.

My pc isn't recognizing my phone either...

Is there any option to recover it?
[Galaxy S6 Edge Q&A, Help & Troubleshooting] callumbr1:
Whats wrong with your volume buttons? You cant do anything unless you can get into download/ recovery mode
[Galaxy S6 Edge Q&A, Help & Troubleshooting] sitimber:
just keep holding vol down home button and power until you get into download mode. it took about 15-20 sec
[LG G Flex 2] Iron_Overheat:
hey, nice thorough fix thread. Also, you're the same guy that made the enhanced thermal engine file! Wow, you're really good at this, aren't you XD? I'm gonna try to replace my battery to see if it fixes my bootlooping (my model is the H959 one)... If it doesn't, I'll translate your thread and show it to a technician to see if he can do it, since it would mean the battery's not the problem in my case. Can I do that, or do you not give me permission? Also, I'm not sure if you updated your thermal engine files later on after the first page of the that thread you made, have you made better ones? ALSO (last question, I promise) do you think this bootlooping might have been cause by charging it with a power bank (I'm charging it on the 5V 2.1A port, the other is 5V 1.0A)? Because it wasn't long after I started using it my phone started bootlooping, plus people said in the bootlooping forum (the one you linked to this thread) that using non-LG chargers was what bootlooped their phones, and even one guy said he used a power bank. Sorry for the massive amount of questions, but I would appreciate if you could answer them ~
[LG G Flex 2] probaina:
Yes you can show this to who ever you want if it helps. One way to know if it's your battery is to have it plugged when using the phone and if you still get bootloops then it's most likely the phone not the battery.

I have experimented making some more aggressive and some slightly more conservative thermal files, however I never gained much and sometimes ran worse then my thermal files I originally posted.

No I don't think a powerbank is an issue with causing bootloops. I actually have two G Flex 2 phones. one has the default thermal file and the other is modified. On both phones I've used three different powerbanks including one that charges at 2.1 amps. Yet the phone I used less with the default thermal file is the one that started having problems. I could be wrong but I think even if you had a really bad powerbank I don't think it would damage the phone primarily. I think it could damage the charging regulator and perhaps the battery. The battery and regulator should buffer a lot of the electricity going to the phone.

The fact that I could fix my phone by reflowing the board kind of shows that in my case the problem was with connections not damage from a charger.

I've already heard of quite a few G Flex 2s, V10 and G5s, having bootlopoop issues. Not as many as the G4s but this seems to have have happened to a lot of LG smart phones made within the last year and a half. LG has also admitted that the G4 problem was caused by bad solder connections to the CPU and RAM .

Well I hope you can figure out your phone. Good luck
[LG G Flex 2] probaina:
Here's something else that G4 users say stopped the bootloops. It's not a fix but more of a test. Try disabling all the big cores on the phone. This made G4 users phone work, but at the cost of performance. But it's worth a shot. If it works then you'll know for sure your problem is caused by a solder connection problem.
[LG G Flex 2] Iron_Overheat:
thank you for answering... My phone stops bootlooping when charging, so it must be the battery. Still, thank you very much for responding... I'll try disabling the big cores if after I change the battery the problem still remains.
[LG G Flex 2] JohzyDeMartin:
Hey there mate,

As you can expect my Flex 2 decided to go into the infinite boot loop after 1 year and and a couple months of ownership.

I came upon your re-flux fix guide after countless hours researching for a way to hopefully fix the Flex 2 myself and not forking more $$$ over to the crooks @ LG.

Was hoping you could give me a pretty detailed update as to how the Flex 2 you operated on has been up to date. Crossing my fingers the guide you posted is a pretty long term fix.

Thanks and let me know

:good:
[LG G Flex 2] anikol:
Had random powerdowns with battery not discharged. One morning the phone would not go past LG boot screen. No playing with battery /charging helped. Found this guide, used rosin flux from radioshack, 385F in the oven for 7 minutes, cooled for an hour, cleaned rosin residue with rubbing alcohol. The phone booted and is working. Will post updates if anything goes wrong with it. Thanks OP.

Update:24 hours still going strong. This is good enough to recover data, already.

Update:14 days later, everything was working fien, left the phone in the carin the open sun, for a couple of hours, it must have baked while charging, I came back it was hot and off and wont respond to power, nor power/volume down buttons. Thought it was done, but couple hours later, it booted up, battery almost fully drained. Fix is still in.
[LG G Flex 2] Farqaleet:
Mine also atfirst went to optimising apps and now it doesn't even turn on please

:confused:
[LG G Flex 2] Farqaleet:
Is Your Flex 2 still working.Please help!

:crying::crying:
[LG G Flex 2] probaina:
Thought I'd post an update on this. Recently my GFlex2 started having the same symptoms again which I'm not surprised. I have also done this fix with two LG G4s which actually need a lot more heat to get them working again. On the two G4s I fixed I ended up going up to 435F and those two have been working for over six months now. I plan on raising the temperature on my GFlex 2 motherboard this time and I'll post on how long it lasts this time.

One thing I find really interesting is that on my Gflex 2 running Android 5.01 this crashing and random reboot problem doesn't happen. It only happened when I upgraded my second Gflex 2 to version 5.1. From the very first boot after the upgrade, this problem happened. This seems to be a similar problem that happens with the Nexus 5X as well.
[LG G Flex 2] hbahaie:
Any update please after raising the temperature?
[LG G Flex 2] probaina:
Well my G Flex 2 didn't like raising the temperature very much. The phone seems to not crash any more but I think it damaged battery temperature sensor. Sometimes it thinks the battery is too cold and other times it things it's suddenly way too hot. Oddly enough the battery temperature sensor is on the motherboard or something. I can tell the readings are bogus since the battery temperature suddenly jumps by a lot. Maybe on the G Flex 2 at least it's better to use a heat gun directly on the CPU chip instead of baking it above 385F.

I'm going to try to reflow it again and see if maybe just some sensors need to be reflowed. I think I can also tell the thermal config file to ignore max battery temperatures. Although that probably isn't the safest thing to do.
[LG G Flex 2] fuadhdmini:
Hi all. Has anyone tried this wakelock fix?

Some YouTube users commented the fix helps.

[youtube]QoonRle6Mx0[/youtube]
[LG G Flex 2] probaina:
Looks like I was wrong. I just had some flux in the battery port. I cleaned it up and it's working great again.

So basically the first fix at 385f worked for about 6 months than it started to reboot often and later turned into boot loop.

This time I decided to go set my oven at 410f and using my laser infrared thermometer I kept checking on the CPU temperature until it reached 420f. Took about 10 minutes to get there.

Another thing I tried that I read works well on the G3 boot loop problem, is to use a piece of wood to push down on the processor with a few pounds of force. Once I pulled the board off the oven it quickly cooled to 380f at that point I used a stick with a flat end to push down on the processor. I would recommend to be careful and press down with no side movement for a few seconds. This can hopefully squish all the solder to an even height and hopefully make a more reliable fix.

So far after a few days the phone has been working great.

Also on the LG G4 I baked to 435f so far has been working perfectly fine for 10 months which is actually oddly longer then the three new G4s my wife got lasted before this fix.
[LG G Flex 2] Ishaanian:
Help!!!

Hi I am a big noob when it comes to all of this. Today my phone (G Flex 2 H955) went into a bootloop when I disconnected it from the charger. It has randomly restarted several times in the past few months but this time it was just bad (until I stumbled upon this thread I never even knew it could be a hardware issue, just assumed unstable OS was to blame). I even factory reset the thing while plugged into the charger, but it didn't make a difference. My phone restarts even when plugged into the charger but not as often and doesn't go into a bootloop like it does now when disconnected. I was thinking I'd try out what you have detailed here. I went through the video but found it all a bit lacking in detail for a noob like me. This is the first time I am gonna do anything like this. Initially I thought I'd just go to some repair shop and show them this thread, but here in India, you can't really trust everyone's work ethics and you'd never know, the guy might say yes yes I'll do it, and then botch it up cause he doesn't have the right equipment or the interest. Another thing that is different is the availability of good quality stuff to do the job, and information on what is what (atleast for someone like me who literally has no idea what is what). Could you please help me do this thing on my own. I have to cause I'm in college and just can't afford a new phone or shoddy repairs on this one at the moment. From the video you linked, I surmised that all I would need is a temperature precise heat gun and flux fluid.

Are there any more precautions I need to keep in mind? If that is the stuff I need to buy to do this job properly, then can I just clean out a syringe and use it to extract the flux fluid is it super sensitive to impurities? What kind of air speed should I start off with for how much time? Do I just set it straight to 200C (385F) or do I get there incrementally? Is there anything else I might be missing out? I am super desperate and super interested to get a response. Looking forward to it. Sorry for the annoying questions!

Cheers!
[LG G Flex 2] wmccann2:
Hi,

Had a problem with the Flex 2 where it would not turn on. originally unclipping the battery for a while would get it back working but then even that did not work.

Anyway have tried the oven trick several times and it so far it has worked - get about 3 months before I have to repeat. I don't use flux/remove the heat shield. I just take the main board out, wrap it lightly in tinfoil and put it in a digital over heated to 220 degrees. I "bake" for 20 minutes, take it out and let it cool down. I get another 3 months or so from the phone.

What seems to cause to not to turn on is if it is left on the charger for too long!.

Hope this helps someone.

W.
[LG G Flex 2] PhantasmRezound:
I bought a bootlooping G Flex 2 off eBay, swapped in a new battery, and it ran a month or two just fine. Had issues again though, so I tried a new charging port board - didn't help. Did the "light" baking fix above this morning, 220°F for 15 minutes in foil. Reassembled and successfully booted again. :good: Will save up for flux and do the more intense reflow procedure if bootloops come back.