yashsingh1/xdaforums huggingface dataset:
[Droid Turbo 2 Q&A, Help & Troubleshooting] roweboat56:
Alright same here. I had originally manually flashed to https://xdaforums.com/droid-turbo-2/general/rom-moto-x-force-lte-android-7-0-npks25-t3661132, but was having issues with Xposed.

So formated, then manually installed "XT1580_KINZIE_RETEU_6.0_MPK24.78-8_cid7_subsidy-DEFAULT_CFC.xml", then accepted OTAs all the way up to Nougat 7.0 *June 1st OTA*.

Then I had some issues with xposed modules & Force closes and thought... since it worked once, I would do a full wipe then simply flash 6.0 again and take OTAs once more.

WRONG.

as first OTA from 6.0 was flashing, that's when it bricked.

*Lesson learned is, never do a full wipe through twrp unless you have a full image of the version you are wiping*
[Droid Turbo 2 Q&A, Help & Troubleshooting] hygorlayondj:
FILES Moto X Force Modded Blankflash.tar.gz and Blankflash.rar

Just like my part of our friend trying to solve our cell phone.

https: // mega .nz/ fm / 0ZQQTSoT

then take the spaces from the link
[Droid Turbo 2 Q&A, Help & Troubleshooting] DashBox:
Another thing I've noticed

The qboot.exe in the Moto X Force Blankflash folder is version 3.40

The qboot.exe in the Moto X Force Modded Blankflash folder is version 2.4
[Droid Turbo 2 Q&A, Help & Troubleshooting] ParanoidCobra:
Here: https: // mega .nz / #F!JGYRGIKK!gWwySaQjXXkBBjvBTo0wgw

Get rid of the spaces and you will be able to access the folder
[Droid Turbo 2 Q&A, Help & Troubleshooting] roweboat56:
I've also been informed by user [MENTION=8544004]philoucheli[/MENTION] that

"Moto X Force Blankflash.rar & Moto X Force Modded Blankflash.tar.gz are fakes.

The moto x force requires at least two files for a blankflash :

MPRG8994.hex and MSM8994_bootloader_singleimage.bin.

8994 corresponds to the moto x force.

In your files, we can see 8926 or 8626, and i'm afraid these files are for "moto g" phones."
[Droid Turbo 2 Q&A, Help & Troubleshooting] Rawdog.dll:
How can we build our own blankflash files?... how it's builded?
[Droid Turbo 2 Q&A, Help & Troubleshooting] roweboat56:
From what I've heard, the blankflash files require a cyrpo key to be read by the phone correctly and those keys aren't given out by motorola (they have been leaked by motorola employees in the past).

But without the correct key, there isn't much we can do.
[Droid Turbo 2 Q&A, Help & Troubleshooting] brgroover:
any solution??
[Droid Turbo 2 Q&A, Help & Troubleshooting] CrashXXL:
https://xdaforums.com/general/paid-software/moto-x-droid-maxx-razr-m-hd-atrixhd-sim-t3360022
[Droid Turbo 2 Q&A, Help & Troubleshooting] roweboat56:
I don't see the Moto X Force as an option. Are you able to service/ fix the Moto X Force Hard Brick?
[Droid Turbo 2 Q&A, Help & Troubleshooting] CrashXXL:
I can serve Moto X Force

the list of models is changing, it is not always possible to correct it,

so you can clarify
[Droid Turbo 2 Q&A, Help & Troubleshooting] roweboat56:
I've already sent my phone in for repair. But hopefully others here can make use of your services. Plus I might neet it in the near future if I do it agian (haha)
[Droid Turbo 2 Q&A, Help & Troubleshooting] Passerati:
The same thing happened to me with a Moto X Force XT1580 reteu. The bootloader was open. The phones will only be recognized in 9008er mode.

Where can one send in the device for repair? In Germany, nobody repairs because of the open bootloader. Also out of warranty not at your own expense.
[Droid Turbo 2 Q&A, Help & Troubleshooting] roweboat56:
sent a PM to CrashXXL, he's said he can repair it for a small fee.
[Droid Turbo 2 Q&A, Help & Troubleshooting] QTeknology:
I wrote him and he doesn't helped me.......
[Droid Turbo 2 Q&A, Help & Troubleshooting] Passerati:
I did, unfortunately received no answer.

I turned to Aryktech and paid. Today came an email, whether they should unlock me, or if I want a refund.

The Unbrick project is currently only able to run if the Moto X Force Android 6 was installed. The update for Android 7 is delayed for a few days. I let myself be unlocked, I just have to wait a bit.

Fingers crossed...
[Droid Turbo 2 Q&A, Help & Troubleshooting] elfrufra200:
solution?

solution?
[Droid Turbo 2 Q&A, Help & Troubleshooting] aditya.addi:
You only need to dump a file from working moto x force using the following command

dd if=/dev/block/mmcblk0 of=/sdcard/Loader.img bs=1024 count=168960

---------- Post added at 01:38 AM ---------- Previous post was at 01:12 AM ----------

Hi friends, I somehow hard bricked my moto x force (xt1580).

To fix it I just need a file called loader.img. that may be dump from a working moto x force using the following command

dd if=/dev/block/mmcblk0 of=/sdcard/Loader.img bs=1024 count=168960

In fastboot mode.

So if anyone may help then I would be highly thankful to him
[Droid Turbo 2 Q&A, Help & Troubleshooting] Passerati:
https://xdaforums.com/showpost.php?p=74650419&postcount=131

Here is the Guide to make a LOADER.IMG with an functional XT1580... I hope, anyone can share a Loader.img for waking up my old phone.
[Droid Turbo 2 Q&A, Help & Troubleshooting] jegrha:
Hard Brick

I hope someone will provide it:D:D
[Droid Turbo 2 Q&A, Help & Troubleshooting] aditya.addi:
Here is the Guide to make a LOADER.IMG with an functional XT1580... I hope, anyone can share a Loader.img for waking up my old phone.[/QUOTE]

Here the link for loader.img, extracted by commands

dd if=/dev/block/mmcblk0 of=/sdcard/Loader.img bs=1024 count=168960

Link

https://drive.google.com/file/d/1KC0nhQqE6XG2jkCrlkGcqkEuLVvxXeUt/view?usp=drivesdk
[Droid Turbo 2 Q&A, Help & Troubleshooting] wWan:
hello guys,

I'm new on xda-dev community....

And I'm stuck with hardbrick on my xt1580 too....

thanks for all information in this thread.

I had hope with the blankflash file...

however, now we have the loader.img file! I am curious.... but how exactly can we use it to bring back our device to life ?
[Droid Turbo 2 Q&A, Help & Troubleshooting] gyarados025:
i can make a loader.img but can it be made on a locked device..?

i have XT1580. btw what does loader.img do for a hardbricked device.

I think the only solution to revive a HARDBRICKED DEVICE from 9008-LOADER is with atf jtag or something like that.
[Droid Turbo 2 Q&A, Help & Troubleshooting] wWan:
no one can help us ? :confused:

i don't know what to do with my device.... is it completely dead ? :crying:

thx
[Droid Turbo 2 Q&A, Help & Troubleshooting] gyarados025:
If the boot of your device is dead ,,then it cant be just repaired with just USB INTERFACE thats only possible only when we have blankflash files which are not available for MXF. I think u must go to a cell phone repair centre/shop and thay should be able to fix with BOX (ATF,MIRACLE,Z2F...etc.:confused:.) just for a small amount :confused: its because a HARD BRICKED phone required proper JTAG connections and USB Connections to revive the boot(loader).
[Droid Turbo 2 Q&A, Help & Troubleshooting] TeljoMadassery:
Anybody find the solution?

I also purchase the blank flash files and those are not working.. my phone stucks at

< waiting for device >

opening device: \\.\COM5

OKAY [ 0.006s]

greeting device for command mode

OKAY [ 0.004s]

identifying device

...serial = 0x20D15E7

...chip-id = 0x940 (MSM8994)

...chip-rev = 0x0

...sv-sbl = 0x0

OKAY [ 0.014s]

finding files

...programmer = programmer.mbn

...singleimage = singleimage.bin

OKAY [ 0.012s]

switching to download mode

OKAY [ 0.004s]

greeting device for image downloading

OKAY [ 0.006s]

sending programmer

OKAY [ 0.073s]

flashing singleimage

...protocol = firehose

Waiting 2 seconds for target to get ready...

please help me...:crying::crying:
[Droid Turbo 2 Q&A, Help & Troubleshooting] xgimp:
XT1580 wont turn on

Hello friends, I have a xt1580 from Brazil, I can not boot Android to check the option "alow OEM unlock" so I can unlock the BL, that is with the bootloader blocked, please help me, I need a means to unlock BL so I can install some ROM. Also note that my device is without a baseband
[Droid Turbo 2 Q&A, Help & Troubleshooting] hunnoren:
moto x force hardbrick

my device I enter qdloader after a software attempt that did not work before I tried other rons and did not pass the device erased and did not call but I need help to revive my device someone has the solution for me and other colleagues who are in the same problem?
[Droid Turbo 2 Q&A, Help & Troubleshooting] Glaucio silva:
Tenta dar esse comando fastboot flash boot boot.img
[Galaxy Note II Q&A, Help & Troubleshooting] Ya_yam:
So I have a Samsung Galaxy Note II and it doesn't seem to work with my unbranded headphones (which do work). Is it because the headphones have to be Samsung to be compatible with their phones? Why is this, and is there a way around this?

I was thinking of getting some high quality over-ear headphones, however I'd obviously like them to work with my phone too! Any help appreciated!! :D
[Galaxy Note II Q&A, Help & Troubleshooting] CarlosPlays:
It doesn't have to be.

I've been using Apple EarPods for weeks (just got the Note 2) and it doesn't have any problem. Does the original Samsung earphones the only thing works on your device?
[Galaxy Note II Q&A, Help & Troubleshooting] rickyroma:
I regularly use Beyerdynamic DT250 headphones which have a 3 pole minijack, and recently purchased a pair of soundmagic e10c which has a 4 pole minijack, both work flawlessly, before that I was using xiaomi piston.
[Galaxy Note II Q&A, Help & Troubleshooting] phatox:
Do you have the original Samsung Note II Cover Protection Shell? It allows only for very slim headphone minijacks. Most headphone plugs are to wide behind the threepole, thus they do not enter the headphone jacket far enough. Try Your headphones without the Samsung Cover Case. If they work, then widen the entry of the Cover Case with a pair of Scissors or something similar.
[Galaxy S 4 Mini Q&A, Help & Troubleshooting] Blaze25:
Hi xda team..,i have a questions about the shv-e370k korean version.

I have own a shv-e370k and i notice that no LTE signal found and i search that shv-e370k have a LTE.

i saw the post of WINMACX.COM but not free ..

What is the truth?

Thanks in advance for your answers.
[Galaxy S 4 Mini Q&A, Help & Troubleshooting] demen.gratisan:
its true bro [IMG="this my s4"]https://m.facebook.com/photo.php?fbid=1976640855900397&id=100006635044772&set=pcb.1739796112711954&source=48&refid=18&__tn__=EH-R[/IMG]
[Galaxy S 4 i9505 Original Android Development] side:
more reserved
[Galaxy S 4 i9505 Original Android Development] robertogl:
Thanks! I was waiting for this :)

P.S. There is an EXPERIMENTAL build for jfltexx? I think it is necessary in order to upgrade from CyanogenMod. Just asking ;)
[Galaxy S 4 i9505 Original Android Development] Mittaa:
I tried to dirty flash from Benlue unofficial ROM to this official ROM using TWRP.

I get ZIP Signature Verification Fail and don't know if I dare to turn OFF ZIP Signature Verification :rolleyes:
[Galaxy S 4 i9505 Original Android Development] Feedmeeeee:
woowww thanks [MENTION=5968293]side[/MENTION]
[Galaxy S 4 i9505 Original Android Development] Rhoban:
Then do not dirty flash.
[Galaxy S 4 i9505 Original Android Development] Mittaa:
Ok I will wait for EXPERIMENTAL build for jfltexx ;)
[Galaxy S 4 i9505 Original Android Development] shoxieJESUS:
[MENTION=5968293]side[/MENTION]

Man, u are god, big thanks to u
[Galaxy S 4 i9505 Original Android Development] dj3d:
Why is that not included

You must separately install a root package with default lineage now, it is not included.

Default line is here: https://download.lineageos.org/extras

addonsu-arm-signed.zip
[Galaxy S 4 i9505 Original Android Development] side:
it is already said to the first post mister :)
[Galaxy S 4 i9505 Original Android Development] rapid_rabbit:
[MENTION=5968293]side[/MENTION] - So does this replace the "[JDCTeam][7.1.1][12 March]Optimized LineageOS 14.1-Stable1[Dev by Poll]" build ?
[Galaxy S 4 i9505 Original Android Development] side:
No way....!!!

'' [OFFICIAL][WEEKLY][7.1.1] LineageOS 14.1 for i9505'' <---this is one is pure LineageOS ROM ,with no custom tweaks,no custom kernel no nothing.its like the Official CM13.0.it has got all features that LineageOS support

"[JDCTeam][7.1.1][12 March]Optimized LineageOS 14.1-Stable1[Dev by Poll]" <---this is MY rom...my custom rom...my edits...my tweaks...the base of that rom is the official lineageOS.i added some stuff etc
[Galaxy S 4 i9505 Original Android Development] lekiaM:
[MENTION=6148485]dj3d[/MENTION] I think the developers decided it that way to make a nice "stock" lineage os without "all singing all dancing" stuff. Just to keep it clean and pure.
[Galaxy S 4 i9505 Original Android Development] Gringo49:
Thanks a lot !

Works great
[Galaxy S 4 i9505 Original Android Development] Mittaa:
Next question would be ... when do we have a EXPERIMENTAL build?

EXPERIMENTAL build use to come before the first official :confused:
[Galaxy S 4 i9505 Original Android Development] side:
there will be NO experimental...

builds will stay labeled as they are...

'experimental 'snapshot' etc was CM stuff

do NOT expect ANY change to this ROM's title
[Galaxy S 4 i9505 Original Android Development] The_Voice_70:
[MENTION=5968293]side[/MENTION]:

I think he means the EXPERIMENTAL Build for dirty installation from unofficial to official ;)
[Galaxy S 4 i9505 Original Android Development] side:
meeeh...if u want to run official release u have to fully wipe...

NEXT builds will be able to be dirty installed over previous official release
[Galaxy S 4 i9505 Original Android Development] glarage:
Official?? So you are THE Jfltexx's maitainer...after so long time, that's good to me?
[Galaxy S 4 i9505 Original Android Development] 7adm:
Can confirm that auto update still wouldn't work when i updated the system with yesterday's build..
[Galaxy S 4 i9505 Original Android Development] LinkinParkBoy:
My bad :rolleyes: Yes 7.1.2 in tha house :p
[Galaxy S 4 i9505 Original Android Development] SalimPS:
Bugs

For people who haven't used this rom yet..

These are the bugs that I faced with the last 2 builds 12/4 and 19/4 :

- Proximity censor randomly stops working.. A reboot or two fixes it.. I noticed that face unlock breaks it and breaks the camera too.

- Google camera doesn't take front facing pictures at all it just freezes.. A reboot fixes that too. (stock camera and apps like whatsapp work fine)

- SIM Card removed happens randomly.. I heard that's a hardware issue but it's worth mentioning.

- Slow charging.. the phone actually charges really slowly.. offline charging is faster tho but as fast as stock rom.

- Auto update doesn't work.

- Automatic timezone not working. (fixed in 19/4 build)
[Galaxy S 4 i9505 Original Android Development] 7adm:
I also have problems with the proximity sensor from time to time.

I don't have any issues with fast charging, however the phone always reports that it's 'charging slowly' on the lock screen, even though it's clearly not the case (this bug has been around since cm13).

I think everybody has that auto update issue.

Regarding that sim card removed issue:

Be sure to use the xxuhpk2 modem, not the latest for the Nordic countries. Also do a full clean install! Especially when you previously came from an unofficial release. This has fixed that issue for me..
[Galaxy S 4 i9505 Original Android Development] SalimPS:
thanks bro I will try that modem :D

btw does optimized LOS 14.1 has the same bugs? if I doesn't I will switch to it..

I never used i9505 I used to have i9500.
[Galaxy S 4 i9505 Original Android Development] k3loo:
is it only me or battery consumption is much faster in 19/4 build vs. 12/4 build
[Galaxy S 4 i9505 Original Android Development] TwoBobWatch:
I have posted about this before and it has been ignored.

I also have an LG G2 (D802) with LineageOS 14.1 installed and the battery life is brilliant. Charged fully at 4:00pm one day, after nearly no use it had 96% charge 25 hours later. It was still connected to wi-fi and updating all of the apps. If I did the same with the 9505, it would not be anywhere that level. There must be an issue with the hardware the OS cannot properly manage.
[Galaxy S 4 i9505 Original Android Development] anhminhon:
I was try a lot of AOSP ROM on my I9505, so i can confirm all AOSP Base have same issue: Very very SLOW charging. :good:
[Galaxy S 4 i9505 Original Android Development] Rhoban:
Your LG G2 has a newer generation SoC. Therefore it's probably more power efficient than the SoC of the S4. Your LG also has a slightly bigger battery.

So you can't really say it's a fair comparison.
[Galaxy S 4 i9505 Original Android Development] TwoBobWatch:
This does not account for 96% versus less than 50%.

I am not attacking either the phone or the contributors but there is a problem that must be recognised before it can be fixed. I would like nothing better than to keep using my S4 for another couple of years, however, this problem may well prevent that happening.
[Galaxy S 4 i9505 Original Android Development] 7adm:
again, I have not experienced this issue on lineage (or cm for that matter). connecting the i9505 with the battery at around 5% and using the original samsung charger, the phone hits a full charge in under 2 hours (last 10% are the slowest) - which i believe is just about what the official specs say.

For my car I have bought a dual fast-charger from wicked-chili and it has a similar charging characteristic.

But, as mentioned before, the lock screen still says "charging slowly" whenever connected to a fast charger. weirdly enough, when connected to a slow charging port (like usb2) the lock screen will just say "charging"... my guess is that the prompts aren't linked to the charging state correctly, triggering the wrong message on the lock screen.
[Galaxy S 4 i9505 Original Android Development] SalimPS:
I also face slow charging bug.. in stock rom my s4 fully charges in approximately 2hours from 15% to 100%

in this rom it takes from 5 to 7 hours to fully charge so that's a huge difference.

ps: Im using the original samsung charger

ps2: I used my dad's s7 cable just to make sure and the results were the same

---------- Post added at 01:53 PM ---------- Previous post was at 01:51 PM ----------

Thanks dude I used XXUHPK2 modem and the problem partially fixed.. it happens waaay less than it was before but it still happens tho.

I live in Morocco located north of africa so do you have any idea which is the best modem for my region?
[Galaxy S 4 i9505 Original Android Development] Kippy51:
[MENTION=4218365]7adm[/MENTION] and [MENTION=5358184]SalimPS[/MENTION] You two should install an app like Ampere and measure the charging rate. If its 1900 mah it is perfect. Time doesn't mean anything.

Sent from one of my Sammy devices
[Galaxy S 4 i9505 Original Android Development] guitar1238751:
To everyone still experiencing proximity sensor issues even after trying various software fixes: If none of the software side fixes you've tried work, it's because the proximity sensor itself is dirty. I ended up taking the back panels off and then manually removing and then cleaning the proximity sensor module next to camera with compressed air and a lint free cloth. There was a thick cluster of dust and grime on and around the proximity sensor. This solved the issue and the device no longer has any proximity sensor related issues. Remember: this is an old device and it needs to be periodically cleaned out.
[Galaxy S 4 i9505 Original Android Development] forfriends:
Thanks for posting this bug list. I find these types of posts very helpful.

I am still using cm13... wondering when I should make the switch.
[Galaxy S 4 i9505 Original Android Development] Simon_29:
Does anyone face issues with youtube? For me sometimes the video stucks and only the audio goes on.
[Galaxy S 4 i9505 Original Android Development] nothingman1976:
Same problem on my phone....

Inviato dal mio GT-I9505 utilizzando Tapatalk
[Galaxy S 4 i9505 Original Android Development] dartoumi:
Anyone else having random reboots with this Rom?
[Galaxy S 4 i9505 Original Android Development] forfriends:
YouTube video stuck happens in cm13 as well. I'd say probably a YouTube app issue but not sure.

Random reboots also happen cm13 but it's infrequent enough.
[Galaxy S 4 i9505 Original Android Development] Rhoban:
That's because the video is at 60 FPS.
[Galaxy S 4 i9505 Original Android Development] dj3d:
2017-04-26 11:19:26 firmewareAgain the error not fixed

And again that it does not go the update

Automatic update still does not work

Do you get the time

Which it updates with TWRP 3.1.0

Always remains with TWRP 3.1.0 destop the automatic update
[Galaxy S 4 i9505 Original Android Development] claudiobar:
Hi guys! Is cam quality on par with stock?

Or are the blobs not there?

Thanks!
[Galaxy S 4 i9505 Original Android Development] Rhoban:
People say it isn't, but I don't know.

Camera quality is decent, haven't used stock in some years so I can't compare.

However, I do think people exaggerate when they say it's a lot worse than stock.
[Galaxy S 4 i9505 Original Android Development] dj3d:
firmeware from 2017-05-03 10:03:10

Again the error not fixed

And again that it does not go the update

Automatic update still does not work

Do you get the time

Which it updates with TWRP 3.1.0

Always remains with TWRP 3.1.0 destop the automatic update


[Galaxy S 4 i9505 Original Android Development] Mittaa:
Use CyanDelta ... ;)
[Galaxy S 4 i9505 Original Android Development] dj3d:
[MENTION=1501232]Mittaa[/MENTION]

Use CyanDelta ...

Why should it use something else?

Should be fixed times in the frimeware
[Galaxy S 4 i9505 Original Android Development] Mittaa:
First of all, you should feel happy that we got LineageOS support at all!

Second... don't yell at the maintainers. Updates comes when they comes.

So if you can't live with manual flashing... just use CyanDelta. It works perfectly together with TWRP.
[Galaxy S 4 i9505 Original Android Development] alialb:
what about lineage downloader? which is the best of 2 of these, cyandelta or lineage d. what is your opinion
[Galaxy S 4 i9505 Original Android Development] LinkinParkBoy:
Btw, new modem\bootloader released: XXUHQC1
[Galaxy S 4 i9505 Original Android Development] guitar1238751:
While Cyandelta fetches "delta downloads" (only recent changes), the built in Lineage downloader fetches the most recent "complete build" that is available for your device. This "complete build" is the latest build the device maintainer for your specific device has built and uploaded. I would avoid Cyandelta as it is not officially supported and often does not work as well on lineage os as did in the days of CyanogenMod. Just use the built in updater or flash the latest build yourself. Or if you really want updates as quick as possible, just do a home build.
[Galaxy S 4 i9505 Original Android Development] alialb:
I meant for lineage downloader, former cm downloader from play store. The built in DL does download the update but does not install it, starts and around 20 percent switches to TWRP recovery and the same doesnt do anything, have to go to data/user/0/lineage and manually install the update cause automatic update is not working.
[Galaxy S 4 i9505 Original Android Development] patriot16:
anybody knows why my twrp recovery delete every time i update my linega. is there any solution for this. i know that when i had Samsung Galaxy S2 there was so called Isorec: Isolated Recovery so when u install new rom or update one....recovery always stay installed on phone
[Galaxy S 4 i9505 Original Android Development] Xenotrumpet:
Holy crap, I thought I was the only one with this issue. This low-current charging happens on my T-Mo variant of the S4. It never goes above 500 mA. I have no idea why, but it refuses to charge at full speed, even with a compatible charger.
[Galaxy S 4 i9505 Original Android Development] dj3d:
lineage-14.1-20170510-nightly-jfltexx-signed.zip

Again the error not fixed

And spared me to point to APP

That should ever go without a tool on the normal user

And again that it does not go the update

Automatic update still does not work

Do you get the time

Which it updates with TWRP 3.1.0

Always remains with TWRP 3.1.0 destop the automatic update