yashsingh1/xdaforums huggingface dataset:
[Project Ara General] UserofAndroid1813:
I've read about Project Ara for a while, but how would it perform in the real world? I want to show you all how I imagine this concept out in the public.

Project Ara should have a basic 4, 5 and 6 in Display design. When you are customizing your Ara phone, you can pick three different screen sizes, or have a custom size made.

If you happen to walk into, let's say a Best Buy and just want to get an Ara phone to customize later, I would want this to be in the box of the phone I pick up. It needs to have a basic Ara case to hold all the modules, either in 4,5 or 6 inch format, and all the displays are at 1080p LCD style. The processor would be basic, with a Dual Core Snapdragon 410, coupled with 2 GB of RAM and a Adrenos 210 GPU(if they make that..)all in one module. Then for the back, a basic 8MP camera with a LED flash module would be there too. It would also come with a 2300mah battery module, and a 32GB Storage Module. Now every Ara phone should have to come with a separate 4GB module embedded in the Ara case, which holds the stock Android Lollipop OS and other system files. There would also be a Connectivity module, holding the NFC chip, the WiFi chip and a Bluetooth 4.0 chip. An extra slot for the Radio Band module would be blank, which will later holds the "Sim card" for your provider. It would only be giving out 4G service. There would also be a Speaker module, housing the 3.5mm headphone jack and a simple speaker. The front would house a display module and a 2-in-1 Camera/Speakerphone module, which houses a 2MP front camera and the speakerphone. Every module(or most) can house a microphone, to make voice commands easier and videos clear sounding.

All of this would come in a box with the Ara case, already preinstalled. Also in the box is the MicroUSB charger, some headphone provided by the Speaker module maker and a back case for those who won't change out their modules every day. The phone is allowed to work on any US Carrier, and certain Radio Band modules for specific regions outside the US would be sold for about 20$.

If the phone is then out on a "Ara Plan" (which is a no-comtract plan for the Ara phone, get to that in a minute) you would purchase the US Radio band for that service provider and plug it into your phone, which upon reboot, will activate on the network. You can activate your Radio Band module through the Ara phone itself, and it will be a simple process, depending on the carrier.

The Ara Plan is a separate no contract plan specifically for Ara devices. When put on this plan, ou pay a fee of 30$ for the Radio Module, and have to sign off a contract stating you cannot sell the module or modify it,etc. If you were to leave your service, you would be required to either return the module for 15$ cancelation fee, or pay 50$ for a lost module. It would be that simple.

To buy extra module pieces for your Ara phone, Google Play would have a sperate site to purchase official or third party modules.
[Project Ara General] Conito11:
Basically, what is ara protect? For what i read is something like build your own phone with generic components? What about os and special features from diferentes companies?
[Project Ara General] Sithhy™:
Yes, it is a modular phone - you can change every component of it. Not so long ago they said that they will support OS'es like Sailfish, UbuntuTouch, FFOS & Android. So you won't be having only a modular component phone but you will be able to switch between systems :silly:
[Nexus 5 Q&A, Help & Troubleshooting] ralfonso:
After completely shattering my original screen, I got a replacement from Etrade Supply and it's not working correctly at all. Only half of the screen works and it constantly registers touches all over. The one thing that has me worried that it's not the screen is if I hold the power button to shut the phone down, it starts right back up (as if there's a phantom power btn press)

Any ideas?

[YOUTUBE]fAQCuS8or4s[/YOUTUBE]
[Nexus 5 Q&A, Help & Troubleshooting] gee2012:
Send it back for repair or better yet exchange, serious hardware issues mate. Maybe you got a poorly refurbished phone.
[Nexus 5 Q&A, Help & Troubleshooting] ralfonso:
I did get a refurbished device and it worked fine until I replaced the glass+digitizer after cracking the glass. I'm not sure they'd take it back a second time since I've opened the case and worked on it.
[Nexus 5 Q&A, Help & Troubleshooting] gee2012:
Then either the digitizer is not installed/connected correctly or its faulty.
[Nexus 5 Q&A, Help & Troubleshooting] ralfonso:
That's my hope. The power button thing has me worried that a different component is to blame. I wish I could isolate the problem.
[Verizon LG G3] quadjacks:
Which of the Lollipop ROM's are pure stock?
[Verizon LG G3] iBolski:
All the LP ROMS currently are based off of AOSP, so that's as stock as you are going to get. Stock Android that is.
[One (M7) Q&A, Help & Troubleshooting] D-r-e-a-m-e-r:
Hi All,

I have a bricked HTC One with the QDLoader mode. Under Linux it shows as qualcomm usb modem converter hence I can't use the unbricking tool to revive my phone.

My phone is from US and I have zero support in my country for HTC.

When researched, I have came to know that if somehow I get hold of MPRG8064T.hex and 8064t_msimage.mbn and some other files, I can use QPST to revive my phone. Can the experts at XDA educate me with the possible solution(s) or point me to the files required.

Also as the same SoC is shared by the following devices, can I use the QPST files from any of these (are these files processor specific only)

HTC One Max

HTC One

Asus Padfone Infinity

LG Optimus G Pro

Oppo Find 5

Xiaomi Mi-2S

Samsung Galaxy S4 Active

Samsung Galaxy S4 I9505

ZTE Grand Memo

LG G Pad 8.3

Vivo Xplay

Oppo N1

LG GX

JiaYu S1

InFocus IN810

Oppo Find 5 Review

Amazon Fire TV

Panasonic Eluga P P-03E

Pantech Vega Iron InFocus IN815
[One (M7) Q&A, Help & Troubleshooting] clsA:
it's more likely your motherboard is dead and your SOOL ...sorry
[One (M7) Q&A, Help & Troubleshooting] Poesini:
I am also in this dilemma with a friends phone, but it seems there is no clue about those files... Staying posted & subscribed if something arises...
[One (M7) Q&A, Help & Troubleshooting] G0DKING:
Me, too. I can't find MPRG8064T.bin/.hex anywhere.
[One (M7) Q&A, Help & Troubleshooting] shawnsingh:
Actually I might be able to help hold on will be back in a few hours

Lol

I swear I saw those file on my desktop.
[One (M7) Q&A, Help & Troubleshooting] shawnsingh:
You all should thank for this lol.

Found them going to post in 5 min

---------- Post added at 05:36 AM ---------- Previous post was at 05:31 AM ----------

MBN MSIMAGE FILE

https://drive.google.com/file/d/0B0j1tztDCRGtTnd4VXgxdTZzbkE/view?usp=sharing

MPRG FILE

https://drive.google.com/file/d/0B0j1tztDCRGtRmhELUtSRlctSmM/view?usp=sharing
[One (M7) Q&A, Help & Troubleshooting] G0DKING:
For sure, man. I saw your first reply and immediately thought to myself, "Awesome! I definitely got to thank him when he uploads the files". :)
[One (M7) Q&A, Help & Troubleshooting] shawnsingh:
Lol its all good hopefully QPST emmc program works for you

from my SM-T320 using XDA Free mobile app
[One (M7) Q&A, Help & Troubleshooting] G0DKING:
It didn't work for me; I don't know if my setup is messed or if it's the wrong file, though.

[MENTION=229050]VBlack[/MENTION], can you let me know what's wrong?
[One (M7) Q&A, Help & Troubleshooting] VBlack:
As it is stated - you does not have enough permissions. You either should run script as sudo, or add your user to dialout group and relogin to Ubuntu.
[One (M7) Q&A, Help & Troubleshooting] shawnsingh:
Hey VBlack would you know or can you help us figure out an unbrick method for the Droid RAZR m we are getting so close but can't make ends meet.
[One (M7) Q&A, Help & Troubleshooting] G0DKING:
Sorry about that, I ran it with permissions and it gave me the same error I got before with the MPRG file you supplied:

To be clear, I have 3 different MPRG8064 files (2 .hex and 1 .bin) and all give me this same error. As an experiment, I ran ./qdload.py MPRG8064.bin with NO MRPG file in the folder: same error. Then I ran "./qdload.py MPRG" (i.e. no file number & extension): same error. At this point, I'm not even sure qdload.py is reading the MPRG file. Is there a change I can make to qdload.py to verify/make it show that it's recognizing & reading the MPRG file (i.e. a different error message from when it doesn't recognize the file to when it does but is the wrong .hex/.bin file for that device)?
[One (M7) Q&A, Help & Troubleshooting] VBlack:
G0DKING, try to run it like this:

./qdload.py --verbose MPRG8064.hex

If it couldn't read file there will be an python error with backtrace... If file is ok - it is just send it to device. .bin file should be converted to .hex using some bin2hex utility.
[One (M7) Q&A, Help & Troubleshooting] G0DKING:
Done, the results for each of the 3 different MPRG8064.hex files, plus a non-existant MPRG0000.hex file, are the same:
[One (M7) Q&A, Help & Troubleshooting] VBlack:
Yes, Im' sorry. utility load files on-demand - so it is not even going to read it, because it is not get correct response initially. So your phone in some different state...
[One (M7) Q&A, Help & Troubleshooting] G0DKING:
Is there a way to edit qdload.py so that it correctly loads the files needed?

Regarding my phone being "in some different state", can you elaborate on that?

I'm just wondering what my options are and what my next step should be in unbricking this phone.
[One (M7) Q&A, Help & Troubleshooting] VBlack:
So, since it is not Motorola phone - it could be another protocol,which is not supported by tool. You could try my test tool version with verbose printing - it could tell more about phone state...

http://pastebin.com/hPNaPp15
[One (M7) Q&A, Help & Troubleshooting] G0DKING:
Looks like minor issues with the code:
[One (M7) Q&A, Help & Troubleshooting] VBlack:
You need to specify partition table file with -ptf to script, which contains at least sbl1.mbn
[One (M7) Q&A, Help & Troubleshooting] G0DKING:
I need to do that to fix the qdload.py code?

And doesn't pulling those files require a rooted working identical device?
[One (M7) Q&A, Help & Troubleshooting] VBlack:
You don't need to fix code. You just need to add "-ptf partition.txt" to command line. Partitions.txt should contains information about at least sbl1.mbn
[One (M7) Q&A, Help & Troubleshooting] G0DKING:
Okay, so just to be clear, I run "./qdload.py MPRG8064.hex -ptf partitions.txt", but the only way to make partitions.txt is to grab pt.bin from a working rooted identical device, and parse it with "./gpt_parser.py pt.bin", right?
[One (M7) Q&A, Help & Troubleshooting] VBlack:
Generally - yes, but you already has bricked phone, so you could try to guess... Or just put some dummy record there, pointing to some dummy sbl1.mbn this could show possibility of such loading at all on your phone....
[One (M7) Q&A, Help & Troubleshooting] G0DKING:
First off, thanks for your continued help. If we ever get this phone unbricked, I'm going to personally go back and thank every single post of yours which helped achieve that.

I have no idea what an sbl1.mbn file would look like and wouldn't even know where to begin to guess or to point to a dummy record. Could you help me out with this? Maybe you have an sbl1.mbn file from another device that I can use as a dummy and help me point to it?
[One (M7) Q&A, Help & Troubleshooting] VBlack:
Yes, for the start - you could try to use files from my topic for droid Ultra... There partitions.txt and mbn files..
[One (M7) Q&A, Help & Troubleshooting] SaHiLzZ:
I have a HTC ONE M7, how can I help in generating the partition file?
[One (M7) Q&A, Help & Troubleshooting] shawnsingh:
Why don't you create a blank flash all you need is the hex file and mbn
[One (M7) Q&A, Help & Troubleshooting] G0DKING:
I used your Driod Ultra files:

---------- Post added at 04:27 AM ---------- Previous post was at 04:23 AM ----------

SaHiLzZ, if you could do that, it'd be a big help. Not just for me, but for anyone that needs to unbrick an HTC One M7 in Qualcomm modem mode.

As I understand it, you need a rooted working phone and dd tool.

While you're at it, could you get us the other files we'll be needing down the line, too?

Here's how to get the files:

First, find correct path on same working phone:

adb shell "ll /dev/block"

AND

adb shell "ll /dev/block/platform"

These are the files we need:

sbl1.mbn

sbl2.mbn

sbl3.mbn

rpm.mbn

tz.mbn

hboot.mbn

pt.bin (I'll be able to parse this to make partitions.txt)

Grab the files like this:

1a. adb shell dd if=/dev/block/platform/.../by-name/sbl1 /sdcard/sbl1.mbn

1b. adb pull /sdcard/sbl1.mbn

2a. adb shell dd if=/dev/block/platform/.../by-name/sbl2 /sdcard/sbl2.mbn

2b. adb pull /sdcard/sbl2.mbn

etc.

AND for partition table [pt.bin]:

adb shell dd if=/dev/block/mmcblk0 of=/sdcard/pt.bin bs=1024 count=10

adb pull /sdcard/pt.bin
[One (M7) Q&A, Help & Troubleshooting] SaHiLzZ:
I could only get pt.bin, its attached to the post. Couldn't see sbl1/2/etc, see here:

ViperOne@/dev/block/platform/msm_sdcc.1# ls -la
ls -la
drwxr-xr-x root root 2015-01-23 08:15 by-num
lrwxrwxrwx root root 2015-01-23 08:15 mmcblk0 -> /dev/block/mmcblk0
lrwxrwxrwx root root 2015-01-23 08:15 mmcblk0p1 -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2015-01-23 08:15 mmcblk0p10 -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2015-01-23 08:15 mmcblk0p11 -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2015-01-23 08:15 mmcblk0p12 -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 2015-01-23 08:15 mmcblk0p13 -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 2015-01-23 08:15 mmcblk0p14 -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 2015-01-23 08:15 mmcblk0p15 -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 2015-01-23 08:15 mmcblk0p16 -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 2015-01-23 08:15 mmcblk0p17 -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 2015-01-23 08:15 mmcblk0p18 -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 2015-01-23 08:15 mmcblk0p19 -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 2015-01-23 08:15 mmcblk0p2 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2015-01-23 08:15 mmcblk0p20 -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 2015-01-23 08:15 mmcblk0p21 -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 2015-01-23 08:15 mmcblk0p22 -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 2015-01-23 08:15 mmcblk0p23 -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 2015-01-23 08:15 mmcblk0p24 -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 2015-01-23 08:15 mmcblk0p25 -> /dev/block/mmcblk0p25
lrwxrwxrwx root root 2015-01-23 08:15 mmcblk0p26 -> /dev/block/mmcblk0p26
lrwxrwxrwx root root 2015-01-23 08:15 mmcblk0p27 -> /dev/block/mmcblk0p27
lrwxrwxrwx root root 2015-01-23 08:15 mmcblk0p28 -> /dev/block/mmcblk0p28
lrwxrwxrwx root root 2015-01-23 08:15 mmcblk0p29 -> /dev/block/mmcblk0p29
lrwxrwxrwx root root 2015-01-23 08:15 mmcblk0p3 -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2015-01-23 08:15 mmcblk0p30 -> /dev/block/mmcblk0p30
lrwxrwxrwx root root 2015-01-23 08:15 mmcblk0p31 -> /dev/block/mmcblk0p31
lrwxrwxrwx root root 2015-01-23 08:15 mmcblk0p32 -> /dev/block/mmcblk0p32
lrwxrwxrwx root root 2015-01-23 08:15 mmcblk0p33 -> /dev/block/mmcblk0p33
lrwxrwxrwx root root 2015-01-23 08:15 mmcblk0p34 -> /dev/block/mmcblk0p34
lrwxrwxrwx root root 2015-01-23 08:15 mmcblk0p35 -> /dev/block/mmcblk0p35
lrwxrwxrwx root root 2015-01-23 08:15 mmcblk0p36 -> /dev/block/mmcblk0p36
lrwxrwxrwx root root 2015-01-23 08:15 mmcblk0p37 -> /dev/block/mmcblk0p37
lrwxrwxrwx root root 2015-01-23 08:15 mmcblk0p4 -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2015-01-23 08:15 mmcblk0p5 -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2015-01-23 08:15 mmcblk0p6 -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 2015-01-23 08:15 mmcblk0p7 -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2015-01-23 08:15 mmcblk0p8 -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2015-01-23 08:15 mmcblk0p9 -> /dev/block/mmcblk0p9
[One (M7) Q&A, Help & Troubleshooting] G0DKING:
Thanks for pt.bin.

Regarding the other files: I'm not sure what the problem is; I'm new to all of this. If I had to guess, I'd say try going back a directory to /dev/block/platform and listing all files again from there (maybe it's not in "msm_sdcc.1"). I don't know, I got those commands from [MENTION=229050]VBlack[/MENTION] so he might know more.

---------- Post added at 08:33 AM ---------- Previous post was at 07:44 AM ----------

VBlack, parsing pt.bin gave me the following error, resulting in an empty partitions.txt file:

ubuntu@ubuntu:/media/ubuntu/USB$ sudo ./gpt_parser.py pt.bin > partitions.txt
Traceback (most recent call last):
File "./gpt_parser.py", line 343, in <module>
main()
File "./gpt_parser.py", line 337, in main
header = gpt.read_header();
File "./gpt_parser.py", line 177, in read_header
_validate_header(raw_hdr)
File "./gpt_parser.py", line 59, in _validate_header
raise NameError("GPT partition table not found")
NameError: GPT partition table not found

Looks like it's caused by the raw GPT header value.
[One (M7) Q&A, Help & Troubleshooting] VBlack:
G0DKING, So you have some not so good situation - it is not recognized as Sahara protocol, and not QDL protocol, this is something else... Do you have any tool, which could see at least something in this protocol?

The next thing, we could do - force it to QDL mode, but this method needs disassembly, and does guarantee it's success...
[One (M7) Q&A, Help & Troubleshooting] G0DKING:
Aw, that is not good news. No, I don't have or know about any tool which will tell me which protocol it's in or diagnose the issue.

All I know is that in dmesg it's in QDL modem converter mode but in lsusb, other people with QDL modem converter mode say "ID 05c6:9008 Qualcomm, Inc. Gobi Wireless Modem (QDL mode)", whereas mine only says "ID 05c6:f006 Qualcomm, Inc." I've searched and found a couple of other people with the same lsusb, but different dmesg, and none of them got their devices unbricked.

I'll hold off on this now, but this may be my only option.

---------- Post added at 09:57 PM ---------- Previous post was at 09:24 PM ----------

Guess I was wrong when I said earlier that the files may not be in "msm_sdcc.1". Apparently, you're missing the directory "by-name", which contains all of those files (Ex. /dev/block/platform/msm_sdcc.1/by-name/sbl1/sdcard/sbl1.mbn).
[One (M7) Q&A, Help & Troubleshooting] SaHiLzZ:
Yes, I do not have that directory by-name.
[One (M7) Q&A, Help & Troubleshooting] G0DKING:
Hey SaHiLzZ, just to make sure, can you try find / -name \*.mbn to search the whole system for any .mbn files?
[One (M7) Q&A, Help & Troubleshooting] Danny201281:
Hi ;) thought i'd bring it here to save you jumping from thread to thread, plus it's more on topic here :good: so here are the files sbl1, sbl2 and rpm. The 2 zips labeled with their respective file paths seemingly contain the same 3 files. The /vendor/firmware/ file are possibly just symlinks to the /firmware/mdm/image/ files but I grabed them all just in case :)

https://www.dropbox.com/s/0en83cvrd6km7w7/vendor-firmware.zip?dl=0 < ------ Possibly just symlinks

https://www.dropbox.com/s/krekbkbyz7tseak/firmware-mdm-image.zip?dl=0

And just wanted to add my device is PN071000 not sure if that's important to what your trying to do :) And one more thing out of interest. What does this device show up as in

lsusb

and

dmesg

?????
[One (M7) Q&A, Help & Troubleshooting] G0DKING:
Good thinking.

Hah, mine's a PN071000 too (minus the extra 0).

But [MENTION=3525160]SaHiLzZ[/MENTION], I'd still like you to check please, since Danny didn't have all the files!

Edit: I actually made a post containing that in the other thread, but it was relegated to the Q&A section (because I had less than 10 posts): http://xdaforums.com/showpost.php?p=57672490&postcount=30
[One (M7) Q&A, Help & Troubleshooting] G0DKING:
Thanks man, I appreciate it.

I started with Ubuntu on a liveboot CD, but soon after installed it in its own partition on my computer so I could dual-boot out of convenience. Version 12 or 13.

The only thing I can add to my whole situation is this: The phone was originally my sister's and it bricked under her usage. She left everything stock and claims it bricked due to a virus from an email she opened marked "URGENT". She allegedly opened said email and the phone completely died. Now, she's not too tech savvy, so I can't say how accurate this is, but it's what she claimed happened. She says there was no physical damage to the phone.

I think the clue to this is the lsusb. Once we figure out what "Qualcomm, Inc." by itself means, we might solve the mystery.

P.S. My favorite typo was "perifferils", haha.
[One (M7) Q&A, Help & Troubleshooting] SaHiLzZ:
Output:

find / -name \*.mbn
/vendor/firmware/sbl2.mbn
/vendor/firmware/sbl1_96.mbn
/vendor/firmware/sbl1_92.mbn
/vendor/firmware/sbl1_82.mbn
/vendor/firmware/sbl1.mbn
/vendor/firmware/rpm.mbn
/vendor/firmware/htcssmem.mbn
/vendor/firmware/htcsmem.mbn
/vendor/firmware/htcrfnv.mbn
/vendor/firmware/htcrcust.mbn
/vendor/firmware/htcnvbak.mbn
/vendor/firmware/htccdma.mbn
/vendor/firmware/htc65.mbn
/vendor/firmware/htc64.mbn
/vendor/firmware/htc63.mbn
/vendor/firmware/htc62.mbn
/vendor/firmware/htc61.mbn
/vendor/firmware/efs3.mbn
/vendor/firmware/efs2.mbn
/vendor/firmware/efs1.mbn
/vendor/firmware/dsp3.mbn
/vendor/firmware/dsp2.mbn
/vendor/firmware/dsp1.mbn
/vendor/firmware/apps.mbn
/vendor/firmware/acdb.mbn
/firmware/mdm/image/sbl1.mbn
/firmware/mdm/image/sbl1_92.mbn
/firmware/mdm/image/sbl1_96.mbn
/firmware/mdm/image/sbl1_82.mbn
/firmware/mdm/image/sbl2.mbn
/firmware/mdm/image/dsp1.mbn
/firmware/mdm/image/dsp2.mbn
/firmware/mdm/image/efs1.mbn
/firmware/mdm/image/efs2.mbn
/firmware/mdm/image/efs3.mbn
/firmware/mdm/image/htcnvbak.mbn
/firmware/mdm/image/htcrcust.mbn
/firmware/mdm/image/htcsmem.mbn
/firmware/mdm/image/htcssmem.mbn
/firmware/mdm/image/htcrfnv.mbn
/firmware/mdm/image/htccdma.mbn
/firmware/mdm/image/dsp3.mbn
/firmware/mdm/image/rpm.mbn
/firmware/mdm/image/apps.mbn
/firmware/mdm/image/htc61.mbn
/firmware/mdm/image/htc62.mbn
/firmware/mdm/image/htc63.mbn
/firmware/mdm/image/htc64.mbn
/firmware/mdm/image/htc65.mbn
/firmware/mdm/image/acdb.mbn
find: /proc/263/task/430/fdinfo/35: No such file or directory
find: /proc/263/task/430/fdinfo/116: No such file or directory
find: /proc/263/task/771/fd/107: No such file or directory
find: /data/DxDrm/fuse: Permission denied
[One (M7) Q&A, Help & Troubleshooting] G0DKING:
Thanks. You have the same results and files that Danny had. I'm guessing that VBlack mistakenly thought the other files would show as well (as they probably had for his Motorola Droid); the same goes for the file path.
[One (M7) Q&A, Help & Troubleshooting] Danny201281:
Ok Small update on this, While modding some firmware zips for my device I noticed something see attached screen shot. The files you were looking for appear to be contained within the firmware.zip although they are .img files rather than .mbn files.
[One (M7) Q&A, Help & Troubleshooting] shawnsingh:
Convert them then.
[One (M7) Q&A, Help & Troubleshooting] Danny201281:
I have no need to convert them my device works just fine. I was just pointing out that [MENTION=6265847]G0DKING[/MENTION] or anyone else who needs them could collect the correct firmware zips for their device and extract the files from there ;) :good:
[One (M7) Q&A, Help & Troubleshooting] G0DKING:
Awesome, can you upload them for me (in case I disassemble my phone and try using a pin to force it into Gobi Wireless Modem QDL mode) and anyone else that's already in Gobi Wireless Modem mode; don't worry about converting them, I'll handle that.
[One (M7) Q&A, Help & Troubleshooting] Danny201281:
Well all my stock firmwares are available here https://www.androidfilehost.com/?w=files&flid=23551. These are H3G UK firmware though so don't know if it would be better to use files firmware for your version main but feel free to help your self.

The open zip in the screen shot is the 2.24.771.3 firmware so you may want to grab them all to make sure you get the latest files. I did notice also that not all the firmwares contain all the files :good: