yashsingh1/xdaforums huggingface dataset:
[General Topics] lietsen:
Maybe you should try Mount2SD. IMHO, I think there is possibilities install apps to ext sdcard with this app as long as your phone rooted. Try with this instruction originally from Mount2SD.

*Sorry, I'm just noob. And sorry for my bad english*
[General Topics] stricker49:
if your phone is rooted use luckypatcher
[XDA Assist] charliew410:
I can't find anywhere that anyone has successfully rooted a Verizon LG Lucid 3 VS876. If there is anyone that knows please help me to find it.

I am a newby that is in need of help.
[XDA Assist] Darth:
Hi,

I certainly can't find anything about rooting that device on XDA, so asking here is your best bet...

>Android Development and Hacking >Android Q&A, Help & Troubleshooting

Good luck!
[Xperia Z3 Compact Q&A, Help & Troubleshooting] dzeek:
Does anyone know if there is currently a firmware version available that supports VoLTE and where to get it?

Thank you
[Xperia Z3 Compact Q&A, Help & Troubleshooting] km8j:
Bump.... Would love to know this for tmous. Maybe when the z3 comes out for T-Mobile, a generous Dev will extract that firmware and port it?
[Xperia Z3 Compact Q&A, Help & Troubleshooting] dzeek:
Bump..I'm interested in it for Verizon. Would love to use this phone on their network.
[Xperia Z3 Compact Q&A, Help & Troubleshooting] JayP72:
Volte Z3 Compact T-Mobile

Hello,

Has anyone found a way to port the VOLTE firware from Z3 to Z3 compact?

also wifi calling?
[Xperia Z3 Compact Q&A, Help & Troubleshooting] jflaco40:
Unlikely... highly

Verizon couldn't even get the z3 out, much less the z3 compact they put out a z2 n a half and called it Z3V... Compact very unlikely on VZW

---------- Post added at 06:56 AM ---------- Previous post was at 06:44 AM ----------

No...volte software gets put in the phone by the carrier, not the manufacturer.

currently at least.

None of the unlocked Xperia devices support Volte, only the Tmobile Z3 has volte software so you have to be on tmobile and that's it. No verizon or att... The Z3 and Z3 Tmobile are different models by the way, and that model is the only model branded in the US, only thing is to ask someone to port that Tmobile rom, so we can flash it on our devices and have volte for tmobile. Hope someone does.

---------- Post added at 07:01 AM ---------- Previous post was at 06:56 AM ----------

The Z3 does not have volte, the Z3 Tmobile does, they are 2 separate models, most people know or own the Z3 so..no you have to be specific and ask for the tmobile, which no one has ported yet. I'll be happy when and if they do.
[8525, TyTN, MDA Vario II, JasJam Software Upgradin] pof:
A new bootloader version for HTC Hermes devices is available on XDA-Developers (thanks 300logic!). This is a very special bootloader version 1.01 MFG which allows to flash unsigned code, meaning that

ROM cooking should now be possible

on the Hermes :eek:

Warning to those who don't know what you're doing. Don't to be tempted to attempt this for now.​

To flash BootLoader 1.01 MFG your DEVICE MUST BE SuperCID first: If you don't have a SuperCID device, this is not useful to you.

* It makes possible flashing custom splash screens

* It makes possible flashing separate ROM parts (only OS, only ExtROM, etc...)

* It makes possible radio upgrade only

* It makes possible flashing roms in NBF format (not tested yet.. research needed)

* It makes possible flashing cooked OS.nb: RESEARCH TO BE DONE IN THIS, AND FULL CAUTION ADVISED

Instructions on how to use this bootloader version have been posted in the wiki:

ROM cooking and Bootloader 1.01 MFG​

Please read everything before asking questions!

Noob FAQs:

Q: Will this VOID my warranty or brick my device?

A: YES if you don't know what you are doing.

--

Q: How to downgrade to bootloader 1.04?

A: Reading this.

--

Q: How to make a device superCID?

A: Reading: this.

--

Q: How to check my bootloader version?

A: Put your device in bootloade mode, when you are on the tri-color screen check the number after SPL-X.XX. This is your bootloader version.

--

Q: Will this help softbank X01HT with 1.14 radio users in any way?

A: No, you can't SuperCID your devices because it is not known how to replace the radio on your device.

--

Q: Will this fix my bricked device?

A: No, unless it is SuperCID after bricking.

--

Q: What is the CID? How do I check my CID? blah, blah...

A: READ THE WIKI before asking questions please!

Please don't ask questions on this post if you don't have a SuperCID device yet, your question will probably be answered in any other post, and this is not the place to ask it.

Real FAQs:

Q: What is a NBH file?

A: Read here.

--

Q: How can I extract the ROM parts from a NBH file?

A: Read here.

--

Q: What is the difference between 'lnb' and 'lnbs' bootloader commands?

A: lnbs is to flash signed code and is available in all bootloader versions, lnb is to flash unsigned code and is only available in 1.01MFG

--

Q: What is the diference between 'wdata' and 'wdatah' bootloader commands?

A: wdatah is to flash signed NBH files and is available in all bootloader versions, wdata is to flash NBF files and is only available in 1.01MFG

--

Q: Why can't I use 'lnbs' in bootloader >= 1.04?

A: You need to issue 'task 32' first to check your SecLevel, it must be Level=0

--

Q: What are the addresses for each ROM part?

A: See NAND Flash distribution here.

--

Q: Has someone successfully cooked OS.nb?

A: Not yet, the format seems to be different from previous NK.NBA, but we're working on it and you are welcome to join us for development/research purposes in this thread.

Do I miss anything? :)

Enjoy! ;)
[8525, TyTN, MDA Vario II, JasJam Software Upgradin] shogunmark:
I think that covers it!
[8525, TyTN, MDA Vario II, JasJam Software Upgradin] Zgembo:
Could we 'upgrade' this preproduction bootloader to version 1.10 for example?!?
[8525, TyTN, MDA Vario II, JasJam Software Upgradin] VivaErBetis:
Thanks Pof for the Wiki and thanks 300logic for provide the bootloader:)

Please, I some questions;

- is now possible to flash a dumped ROM? If yes, How?

- Is possible to get a backup copy of the actual splash screens before changing it?

Thank you.
[8525, TyTN, MDA Vario II, JasJam Software Upgradin] Deleted member 384713:
Can I really downgrade from BL 1.09 to 1.04 with the Bootloader 1.01 MFG-Tool!:)
[8525, TyTN, MDA Vario II, JasJam Software Upgradin] hellejoep:
POF answers this one later.....
[8525, TyTN, MDA Vario II, JasJam Software Upgradin] hellejoep:
Great news!!!!

Excellent POF and all of the others; let the cooking begin!
[8525, TyTN, MDA Vario II, JasJam Software Upgradin] pof:
You can go from 1.01MFG to 1.09 with 'lnb', and you would to any version too...

First you have to convert the dumped ROM to OS.nb format of the Hermes... something which will require quite some time until someone can figure out. See here if you are interested.

Take a shipped ROM from your vendor, and extract the splash screen with NBHextract.

Yes if your device is SuperCID (Security Level=0).
[8525, TyTN, MDA Vario II, JasJam Software Upgradin] canope:
Hi :)

I'm interrested on informations about rom cooking form hermes trinity :)

Can you tell me if it's possible, with the current imgfs tools , to extract valid dll files and to use this files on other devices...

I currently have problems for loading a dll driver and i'm looking for help for analyzing why...

Anybody know how to use kitl.... ?

Thanx
[8525, TyTN, MDA Vario II, JasJam Software Upgradin] Lurker0:
So... is it possible now to flash a dumped ROM somehow?
[8525, TyTN, MDA Vario II, JasJam Software Upgradin] vador:
Great news.

This mean in future cooked wm6 roms :D :D
[8525, TyTN, MDA Vario II, JasJam Software Upgradin] qooqoo:
bravo, i'am waiting for this days for a long time.
[8525, TyTN, MDA Vario II, JasJam Software Upgradin] diseage:
mtty has been sitting at

USB>task 32

Level = 0

USB>lnbs SPL-1.01.nbs 50020000

:F=SPL-1.01.nbs

:A=50020000

:O=00000000

:L=FFFFFFFF

start NB image download

for about 10 minutes now. anything wrong?

[edit] never mind, I was using the wrong mtty. when I used the one included, it worked great. thanks![/edit]
[8525, TyTN, MDA Vario II, JasJam Software Upgradin] liva:
+1 thks for all
[8525, TyTN, MDA Vario II, JasJam Software Upgradin] pof:
Yes, it should be possible... see this thread for info on how to split the file to extract correct imgfs_raw_data.bin.

Put hermes in KITL mode (comm manager + power + softreset) and connect to it with Platform Builder. I can't help you more, because I don't have PB.
[8525, TyTN, MDA Vario II, JasJam Software Upgradin] blcc:
Thank you very much, bootloader downgrade from 1.09 to 1.01 MFG now.
[8525, TyTN, MDA Vario II, JasJam Software Upgradin] kanakira:
cool

you are very cool
[8525, TyTN, MDA Vario II, JasJam Software Upgradin] monx®:
pof (maybe we should call u prof.)

as u have mentioned, after flash to bootloader 1.01 can revert to SPL 1.04.

is it possible to re-flash SPL 1.06 which i've extracted from Dopod newer ROM?

[just need advise from an expert before my hermes die :) ]
[8525, TyTN, MDA Vario II, JasJam Software Upgradin] ionide:
Why would you want 1.06 over 1.04?
[8525, TyTN, MDA Vario II, JasJam Software Upgradin] pof:
@hang.tuah: yes, it is possible... but I have the same question as ionide... why 1.06?? it does not offer any good over 1.04, just has downsides and annoyances :P
[8525, TyTN, MDA Vario II, JasJam Software Upgradin] monx®:
thanx pof. just curious. thought just can revert to SPL 1.04 as provided only.

:)
[8525, TyTN, MDA Vario II, JasJam Software Upgradin] mxlaser:
So, any updates on the ROM cooking front? and success had? or failures?
[8525, TyTN, MDA Vario II, JasJam Software Upgradin] pof:
@mxlaser: one success, several failures :P See the thread on rom cooking.
[8525, TyTN, MDA Vario II, JasJam Software Upgradin] lvsw:
DelFile - OK!

AddFile - not working :((((((((((((((
[8525, TyTN, MDA Vario II, JasJam Software Upgradin] jokinawa:
I love this bootloader. I was able to put the following on my X01HT.

Radio: 1.27.00.00

OS ROM: 1.33.761.4 (Softbank)

Bootdr: 1.01MFG

After that I used Asukal's English MUI's and it is running like a champ.

Thanks fellas.

I even had to fix the "stuck at bootloader" brick.
[8525, TyTN, MDA Vario II, JasJam Software Upgradin] baudy2:
Will change of Bootloader to 1.01 MFG require the cold reset (removing of all the content and installed programs) or the content of the machine will stay unchanged ?
[8525, TyTN, MDA Vario II, JasJam Software Upgradin] pof:
@baudy2: it does not require hardreset, nothing will be erased.
[8525, TyTN, MDA Vario II, JasJam Software Upgradin] lvsw:
pof, how correct add file to the ROM?

When I use addfile.exe, my ROM not loading! But when I use delfile.exe, my ROM loading OK!
[8525, TyTN, MDA Vario II, JasJam Software Upgradin] tadzio:
I had planned to look into this over the weekend, but didn't find the time. But aren't the Universal folks using AddFIle all the time? Maybe they know about some pitfalls that must be avoided which we haven't found yet?

Cheers

Daniel
[8525, TyTN, MDA Vario II, JasJam Software Upgradin] ahlok_hk:
@lvsw: did you flashed the cooked ROM after using addfile.exe? If yes, was there any bad block error that your have encountered afterward? Thanks.
[8525, TyTN, MDA Vario II, JasJam Software Upgradin] lvsw:
After using of addfile exe i have sucsessful flashed my device. while flashing there was no errors or any problems. But the device is booting until the second splash with a label TEST ONLY.

If use only delfile.exe - everything`s ok!

tadzio, In the Universal`s NAND flash and Samsung CPU?
[8525, TyTN, MDA Vario II, JasJam Software Upgradin] zohaer21:
from my days of cooking custom roms for my Universal.. i never used the add file command with maimachs tools.. rather i copied and pasted files directly to dump folder and complied a rom thereafter..

has anyone tried this approach???
[8525, TyTN, MDA Vario II, JasJam Software Upgradin] pof:
I did a quick test and wasn't able to use addfile, delfile worked fine and I haven't had time to look at it more deeply.

Second splash has nothing to do with OS.nb.

No, universal has M-Systems DOC and Intel PXA270 CPU.

Yes, and everyone who tried bricked the device. We have to go "step by step" first.

I didn't had time too :( Universal rom cooks dump the full rom and work with a rom kitchen that facilitates the rom editing work... add|del file is way too primitive for them :p but it's our starting point, as we risk the device every time we flash something modified. Universal has DOC (Disc-on-Chip) as non-volatile memory storage but Hermes has NAND flash. Most NAND flash devices contain a initial manufacturer marked bad-block table, and I think that the problem we are facing when flashing modified OS.nb is that we flash (overwrite) these factory-marked bad blocks and we loose the marking on the bad-block table inside the memory array. After using those initially marked bad blocks as if they were good, we produce other good blocks to fail.

Today I got a hermes device from a friend who flashed cooked OS.nb and it was not booting OS, it was a SuperCID device with 1.01 MFG on it. Bootloader output for "info 8" showed a lot of bad blocks on it, not enough buffer in mtty to see them all:

...
Block 0x2B7(695) is BAD block !!!
Block 0x2B8(696) is BAD block !!!
Block 0x2B9(697) is BAD block !!!
...
Block 0x3EC(1004) is BAD block !!!
Block 0x3ED(1005) is BAD block !!!
Block 0x3EE(1006) is BAD block !!!
Block 0x3FB(1019) is Reversed block

My first test has been flashing a 64Mb file filled with zeros, after that I got this message when formating NAND:

USB>task 28
Storage format start
Write Nand Success
dwBlockToWrite = 1007
Can't find OS in flash!!!
Storage format success

But the bad blocks where still there when issuing a "info 8" again, then I tried to flash a 64Mb file filled with FF's and this has been the result while flashing:

USB>lnb osFF.nb
:F=osFF.nb
:A=501A0000
:O=00000000
:L=FFFFFFFF

start NB image download
Load ADDR: 501A0000 Length: 3F000AC
*********************NANDFlashWriteBlockWithSectorInfo: dwBlockIndex=0x400
NANDFlashWriteBlockWithSectorInfo: Address Error2!!!
NANDFlashWriteBlockWithSectorInfo: dwBlockIndex=0x401
NANDFlashWriteBlockWithSectorInfo: Address Error2!!!
NANDFlashWriteBlockWithSectorInfo: dwBlockIndex=0x402
NANDFlashWriteBlockWithSectorInfo: Address Error2!!!
NANDFlashWriteBlockWithSectorInfo: dwBlockIndex=0x403
NANDFlashWriteBlockWithSectorInfo: Address Error2!!!
...
NANDFlashWriteBlockWithSectorInfo: dwBlockIndex=0x7FE
NANDFlashWriteBlockWithSectorInfo: Address Error2!!!
NANDFlashWriteBlockWithSectorInfo: dwBlockIndex=0x7FF
NANDFlashWriteBlockWithSectorInfo: Address Error2!!!

Device got stuck here... we left it for a while, but USB monitor showed there was no traffic, so we finally soft resetted it and it didn't wake up anymore not even the bootloader, so I guess NAND flash god corrupted in the IPL/SPL part.

I wished I had tried to debug it with KITL+PB to see if I coudl find any useful info there, but it was too late :(
[8525, TyTN, MDA Vario II, JasJam Software Upgradin] invictus:
auch Pof! that's ugly and sad!

maybe we sould try to trace the jtag connector on the Samsung Cpu

http://www.samsung.com/Products/Sem...or/ARM9Series/SC32442/JtagFlash_Prog_Code.zip

on this page is everything for samsung cpu jtag. you can read and write anything on 4 wires (trough a jtag interface) they supply the program and also the source code on how to write in NAND, Flash Strata, etc. Interface schematic included. In C you can see that you where right about the array of bad-blocks in NAND
[8525, TyTN, MDA Vario II, JasJam Software Upgradin] pof:
Thanks invictus, already looked at almost everything in the samsung cpu page :) however I don't think I am able to connect the jtag to hermes hardware, jtag pins are unknown and I'm not an electronics junkie :rolleyes:
[8525, TyTN, MDA Vario II, JasJam Software Upgradin] lvsw:
Info about NAND -flash!!!

http://msdn2.microsoft.com/en-us/li...mgmtwince_topic1#systemmemorymgmtwince_topic1
[8525, TyTN, MDA Vario II, JasJam Software Upgradin] Zgembo:
Hi pof, I got curious about what you tried here, the infamous bad-block issue. If I'm right, task 28 command formats flash. But what area, and how does it deal with hardware bad-blocks?!? Also I have seen other task x commands on this forum, but can't find any reference for this commands... I simply want to know what different task commands do, is there any known list or something?!?
[8525, TyTN, MDA Vario II, JasJam Software Upgradin] lvsw:
Can it has sense use old utilities with the key “- acer” (instead of the renovated version with the key “- hermes”)
[8525, TyTN, MDA Vario II, JasJam Software Upgradin] ahlok_hk:
@pof: Do u mean that even we flash the original extracted 06_OS.nb, there is still some risk of bricking the device because of the NAND flash?

I am asking because for me it doesn't make sense if flashing original .nb won't overwrite factory-marked bad blocks but flashing cooked .nb will have them overwritten. I always think that it's the format of the .nb that matters....
[8525, TyTN, MDA Vario II, JasJam Software Upgradin] jokinawa:
I flashed an original ROM extracted from the NBH without bricking it. Is it possible to extract a file from an original ROM (1) then re-inject the same file into a new ROM (2) and compare the Original to the New one? Maybe the bad blocks will be more identifiable that way.
[8525, TyTN, MDA Vario II, JasJam Software Upgradin] kyphur:
Unless I misunderstood something in this thread, I thought the problem is only when something is added to the OS image file. So If I use "DelFile" to remove operator themes, ringers and start-up files that image flashes fine, is this correct?

I don't claim to understand squat about NAND Flash Memory but all storage contains a bad-block table. The command we use should not be able to modify this info as it is managed by the bootloader read/write processes (and used exclusively by them) all we can do is send the data in. With the OS image we don't even get to tell it where to start writing.

I'm sure you guys have already looked at the possiblity that when adding a file the image becomes too large to fit so I doubt overwriting past the end of the OS Space is the issue (besides the bootloader

should

protect against that).

So now I wonder when files are added to the image are they simply appended to the end? I mean is there some kind of sync-bit or something that tell the bootloader "at this point in the image you should be at address XXXX" which would put it at the end of the OS space and now we are adding data after that so it gets written where is should not be?

I hope this isn't just so stupid that I lose credibility, please remember that I understand jack squat about NAND, just trying to think outloud here.
[8525, TyTN, MDA Vario II, JasJam Software Upgradin] Zgembo:
task 28 - format DoC !?!

Format Disk on Chip ??? This is strange, Hermes is NAND not DoC... What exactly this command 'formats'? What ROM range? I guess it does not touch bootloader, right? How does it treat bad blocks? I don't understand...
[8525, TyTN, MDA Vario II, JasJam Software Upgradin] pof:
Original extracted OS.nb does not produce bad blocks at all, but cooked/modified OS.nb does. I did several test with delfile.exe and flashed cooked image without problems, I checked before flashing that all the IMGFS_GUID occurrences where kept at the same place in the original OS.nb and my modified OS.nb, this seems to be safe. I wasn't able to use addfile.exe with my dumped imgfs_raw_data, through I haven't looked at the issue deeply.

Correct.

Please don't start throwing theories and try for yourself, don't flash, just use tadzio tools and play with several OS.nb and [add|del]file.exe and use a good hex editor to compare the results of your cooked file and the original file. Also try to play with other devices nk.nba and compare the results you get with the ones you get cooking hermes OS. Only through this path we will be able to conclude something.
[8525, TyTN, MDA Vario II, JasJam Software Upgradin] pof:
@Zgembo: On hermes it formats NAND, but the help was taken from other device bootloader which has the same command. Hermes bootloader doesn't have help. We don't know how does it treat bad blocks... so get a disassembler (I'd suggest IDA pro) and find yourself if you are curious about it, otherwise nobody will answer your questions because there is no documentation about it and nobody knows (well,.... sure HTC programmers do, but they won't come here and tell us! :P)
[8525, TyTN, MDA Vario II, JasJam Software Upgradin] Zgembo:
I was afraid you would say that! ;) Do we know, at least, what ROM range it formats? I'm bit afraid of trying to 'format' my working device.
[8525, TyTN, MDA Vario II, JasJam Software Upgradin] kyphur:
pof, I may be crazy but I ain't stupid! I paid $500 US for my 8525 and I don't plan on frying it two weeks in.

I've never editing a Rom image before so I'll probably sh#t myself the first time I get brave enough to flash one I've changed (even simple delete) because it seems with the Hermes you can fry it with just an OS Image unlike the Wizard & BlueAngel.

I think I'll probably flash back an original Shipped Cingular Rom (and wait until they release the PTT AKU 3.3 update) before taking that step because they will warranty replace my phone if the Operator Upgrade makes it toast.

In the meantime, I'm reading everything posted here and will be downloading the tools mentioned so be ready for some Newbie Rom Cooking questions from me!
[8525, TyTN, MDA Vario II, JasJam Software Upgradin] kyphur:
I have successfully used MTTY to do an OS only flash of my 8525.

Given that you format, flash the os.nb then format again my guess would be that the format command is equal to "Clear Storage" in settings or the "Hard Reset" where it simply removes personal changes to the device and resets the status to "New OS, requires configuration".
[8525, TyTN, MDA Vario II, JasJam Software Upgradin] pof:
@Zgembo: It's just like doing a hard reset. I've done that hundreds of times... it's safe.

@kyphur: I don't like to fry my hermes either, that's why I only try dangerous stuff after examining everything is under my control, but sometimes you just have to risk a device if you want to do some progress :)
[8525, TyTN, MDA Vario II, JasJam Software Upgradin] hellejoep:
I completely agree pof! Keep up the good work!
[8525, TyTN, MDA Vario II, JasJam Software Upgradin] kyphur:
Are you saying that when you used Addfile.exe you got an error or that the IMGFC_GUID occurrences were changed?
[8525, TyTN, MDA Vario II, JasJam Software Upgradin] pof:
@kyphur: I got an error, see here.

I haven't tried with other OS.nb after that... not enough time for everything, I got a new device ;)
[8525, TyTN, MDA Vario II, JasJam Software Upgradin] mun_rus:
Have a look.

Just find something, may be it could be usefull to know.

First column-original bin; 2nd-modified

I tryed to del wceload.exe then compared bin files

i saw these at header

69D580:	B8	FF
69D581:	00	FF
69D582:	B8	FF
69D583:	00	FF
....

then i made new bin file and deleted welcome.exe

1151680:	B8 FF
1151681:	00 FF
1151682:	B8 FF
1151683:	00 FF

non-module files has this on header (tried to delete camera.exe etc)

33B05A8:	FE	FF
33B05A9:	F6	FF
33B05AC:	00	FF
33B05AD:	00	FF
33B05AE:	00	FF
33B05AF:	00	FF
33B05B0:	00	FF

So, next i tryed to use addfile.exe and compared bin files.

i saw that.

1st-modified, 2nd-original.

347CE05:	D2	00
347CE06:	47	00
347CE07:	03	00
347D1C0:	2F	FF
347D1C1:	0E	FF
347D1C2:	2F	FF
347D1C3:	0E	FF
347D1C4:	00	FF
347D1C5:	D4	FF
347D1C6:	47	FF

Every time addfile writes new files to the same adress. And owerwrites zero values.

Also I compared wizard's bins before and after adding a file. So :) file was written in FF (clear) area only!

I think that we should try to write new file to rom only in FF area. Probably, when we overwrite zero values we get bad block with incorrect values. also i think that addfile get free space of rom incorrectly...and area for searching free space should be fixed

btw, old prepare imgfs with acer key give the same bin file as new prepare imgfs tool with hermes key.