Related
The attached utility will allow to extract .NB0 OS image from ASUS P525 "galaxy.cap" complete rom update packages, and also to update CRC on modified NB0 ROM image, to pass the flasher validity check and flash the modified ROM. Also it will allow to unpack compressed kernel partition.
The application dynamically linked to Visual C runtime libraries. They used by myriads of applications, and most likely you already have them on your system installed. If you are not (on a clean PC for example) and P525ROMTool complains about lack of needed libraries,- download and install this - http://www.microsoft.com/downloads/details.aspx?familyid=32BC1BEE-A3F9-4C13-9C99-220B62A191EE
For you technical people, the utility source is included too. You can see the basic layout, and that ASUS used Adler32 algorithm to calculate the checksum on ROMs (with slight modification that base sum was initialized to zero instead of one).
The basic procedure for cooking your own custom P525 rom is:
1) P525ROMTool -d galaxy.cap
This will extract the ROMGalaxy.NB0 OS-only image. For custom ROMs I recommend working with NB0 OS images only - no danger of corrupting bootloader & IPL this way.
2) prepare_imgfs ROMGalaxy.NB0 -nosplit
3) DelFile / AddFile
Iam not sure if you can truly fully rebuild the ROM and not to break anything (ROM tools were made for HTC platform, not for ASUS). So I recommend using DelFile/AddFile method at least for the start.
There are a lot of different ROM editing tools around, but I can not give you exact directions what is better and in which conditions - ASUS ROM cooking is less charted area then for HTCs.
I assume you know what you actually need to change on file basis for your ROM customization. If you dont know what I am talking about, this is not for you (read disclaimer at the end of the post, and think over it).
4) make_imgfs ROMGalaxy.NB0 -nosplit
5) P525ROMTool -s ROMGalaxy.NB0
it will ask about changed checksum. Enter "y" to update it. You can run P525"ROMTool -s ROMGalaxy.NB0" again to be sure that checksum was updated properly - it should'nt ask to change it second time.
6) Flash ROMGalaxy.NB0 via bootloader (copy it to SD card root, press "camera" fully, press reset).
Techincally, you can make the .cap file to flash via "autorun" loader, hovewer, I must warn you that .cap file will flash not only OS image, but also the IPL+bootloader. If something goes wrong, bootloader can be corrupted and device will be bricked.
If you flash ROMGalaxy.NB0, it will not flash over bootloader+IPL, so its a lot safer - if something goes wrong, you still must be able to flash emergency rom via bootloader.
Take note that any activity that involves the ROM updating is dangerous. Even if you understand everything, there is some risk. If you have only basic understanding of ROM mechanics, risk increases tenfold - you better consider before screwing up perfectly working and expensive device.
You have been warned.
Ingvarr, thanks a million time. I love yr WM5 Storage and I think I will love this tool also. I will start building my rom based on Sorg's build 6 since it does provide some very useful tools for us.
Ingvarr thank you for your cool tools.
But when I DIY my ROM, I can't make make_imgfs.exe work correctly. It returns some symbols I can't understand.
Even I run make_imgfs.exe just after finish running prepare_imgfs.exe, it returns the err.
Could you help me with this?
make_imgfs ROMGalaxy.NB0 -nosplit
NOT "nk.nba"
It writes the modified filesystem back in the original image, so it should remain the same. You dont want to mix the ASUS and HTC ROMs and then flash it to your device, trust me
I recommend you to read HTC ROM Tools instructions and forum threads and be sure you've got right how it works, before you screw something up
sir,
Bad news，it can't work with CHS ROM （ROMgalaxy.nb0） checksum error！～～～
Does it correctly verify the checksum on original ROM?
I will try to look over it, maybe I've missed something.
Btw, if you can, write down what does writes on screen _exactly_, down to the point of failure (including error message).
Ingvarr said:
Does it correctly verify the checksum on original ROM?
I will try to look over it, maybe I've missed something.
Btw, if you can, write down what does writes on screen _exactly_, down to the point of failure (including error message).
Click to expand...
Click to collapse
i have tried it too.
i updated the checksum in sorgs rom, and then i found, that the checksum from ur SW is diffrent with the original Checksum in sorgs ROM
harlemyin said:
i have tried it too.
i updated the checksum in sorgs rom, and then i found, that the checksum from ur SW is diffrent with the original Checksum in sorgs ROM
Click to expand...
Click to collapse
You mean, it claims that checksum is wrong even when you have not modified NB0 yet?
I may look over this NB0, can you host it somewhere? But better not at rapidshare, Iam already topped my limit
Ingvarr said:
You mean, it claims that checksum is wrong even when you have not modified NB0 yet?
I may look over this NB0, can you host it somewhere? But better not at rapidshare, Iam already topped my limit
Click to expand...
Click to collapse
yes
and it happens by official P525_V3320_WWE2nd too
checksum in official P525_V3320_WWE2nd is 79AB7436
ur SW changed it to EF722461----not modified NB0
u can download official P525_V3320_WWE2nd with www.asus.com or
ftp://dlsvr02.asus.com/pub/ASUS/IA/P525/P525_V3320_WWE2nd.zip
Thats odd, because I've just checked it with WWE 3.32 and at least checksum calculation defenitely works ok...
This roms are in .CAP package. Have you actually extracted .NB0 from .CAP?
I have uploaded version 1.01 - it has additional sanity checks to make sure that you try to run it on NB0 with structure it expects.
Try it on WWE 3.32 and write what the original checksum and calculated checksums will be.
sorry
our mistake
i tested ur SW with a *.nb0, which extracted with xda3nbftool.exe------*.nb0 with ipl and bootloader.
and now i find, that *.nb0 should be and must be extracted with ur P525ROMTool -d galaxy.cap,------that means *.nb0 without ipl and bootloader
everything is fine, when *.nb0 is extracted with ur P525ROMTool
i think creazy2000 just made the same mistake like me.
o
thanks a lot.
Thanks. The tool works perfectly on my P525.
Ingvarr said:
Thats odd, because I've just checked it with WWE 3.32 and at least checksum calculation defenitely works ok...
This roms are in .CAP package. Have you actually extracted .NB0 from .CAP?
I have uploaded version 1.01 - it has additional sanity checks to make sure that you try to run it on NB0 with structure it expects.
Try it on WWE 3.32 and write what the original checksum and calculated checksums will be.
Click to expand...
Click to collapse
I make a mistake, thanks!
harlemyin said:
sorry
our mistake
i tested ur SW with a *.nb0, which extracted with xda3nbftool.exe------*.nb0 with ipl and bootloader.
and now i find, that *.nb0 should be and must be extracted with ur P525ROMTool -d galaxy.cap,------that means *.nb0 without ipl and bootloader
everything is fine, when *.nb0 is extracted with ur P525ROMTool
i think creazy2000 just made the same mistake like me.
Click to expand...
Click to collapse
Oh, I know !
I make a mistake !
thanks
Is it a seperate tools that the imgfs? Need I find this tool to finish the whole things? Where can I find this tool?
P525_V3320_WWE2
I have P525_V3.29.0 WWE3
Can someone tell the difference between them it looks that the first one is newer but I am confused by the WWE which is newer
Thanks all
Night Runner said:
Is it a seperate tools that the imgfs? Need I find this tool to finish the whole things? Where can I find this tool?
Click to expand...
Click to collapse
Everything about complete process is in the first post. What is you dont understand from here?
jmfa59 said:
P525_V3320_WWE2
I have P525_V3.29.0 WWE3
Can someone tell the difference between them it looks that the first one is newer but I am confused by the WWE which is newer
Thanks all
Click to expand...
Click to collapse
WWE means "world wide english".
First is 3.32, therefore, its newer.
Ingvarr
Thanks Buddy,
can you explain WW2 and WWE3 it seems that the latter is newer but the version V3.29 is older or is ment for different country
guys help please.... i want to upgrade from wm5 to wm6... i dunno where to post thats why i made it here... thanks
you dont mention what device you have
if you have an htc device and got the rigth rom for it
and get that error when you run the flash tool then
maybe it's because your rom as in the nbf file is not in the
same dir as the flash tool
Hi ppl,
I just bricked my Asus A639 while trying to upgrade
to WM6. Probably my own fault, the SD was FAT32
rather then FAT16 and I noticed too late.
Also, I was stupid enough not to create a backup
of the WM5 first so I'm really stuck here.
I have been reading the forums on this but many topics
are mixed up ; they discuss migrating to another language
mixed up with rescueing the device.
I am not interested in switching language. I have read
that it is possible to force a WM5 image onto the device
but there are two issues ;
1. I don't fully understand how to do it
2. I don't have a WM5 image
So I guess I have two questions ...
1. Can anyone provide me a Dutch Asus A639 WM5 backup
2. Can anyone tell me how to get it onto the device.
Tnx,
c0r3
Got it fixed. Many tnx goes to cmonex !
There was a post some time ago which described how to recover from
a crashed upgrade ....
http://forum.xda-developers.com/showthread.php?t=308611&highlight=asus+wm6+update&page=19
I started of by downloading the official WM6 update from the Asus
site. I renamed the Update.img to A639_K733.DIO and tried to get it
onto the device. Although it did load, the PDA still wouldn't get past
the Asus welcome screen.
It appears the .img file from the update package contains too much
for this to work.
cmonex said:
find MSFLSH50 signature (search for string in a proper hexeditor!!) in the file, then go back 512 bytes and cut everything until then.
so the remaining file will have the MSFLSH signature at offset 0x200 (i.e. 512).
Click to expand...
Click to collapse
So I tried but could not find the "MSFLSH50" string in the .img file. Tried
several different hex editors, no luck.
cmonex said:
ok, it is possible it is a XOR'd file, some ASUS updates are like that.
Click to expand...
Click to collapse
Once I got the correct file from cmonex ;
1. Formatted SD FAT16
2. Rename cmonex's file to A639_K733.DIO
3. Copied file onto the SD
4. Inserted SD into PDA
5. On PDA : press+hold power+enter+reset
6. PDA enters bootloader mode and copies the file into the ROM
7. Press reset on PDA and all boots just fine although it takes a while before
it passes the Asus welcome screen. This is only the first time after the
download however. Reboots after then go as they should normally go.
The hard part in this sequence seems to be to find a decent ROM file.
Once you have a file that contains the MSFLSH50 signature it pretty
straight forward.
as someone sent this link to this thread to me in PM just now I thought I'd clarify some details..
a sample english .DIO is available from my server, but link is not public - you can PM me
otherwise, to obtain a .DIO, just make a backup of your ROM with pdocread while PDA is still working. if help is needed with that, please post the output of the command "pdocread -l"
cmonex said:
as someone sent this link to this thread to me in PM just now I thought I'd clarify some details..
a sample english .DIO is available from my server, but link is not public - you can PM me
otherwise, to obtain a .DIO, just make a backup of your ROM with pdocread while PDA is still working. if help is needed with that, please post the output of the command "pdocread -l"
Click to expand...
Click to collapse
can somebody give my a link to .DIO file
Same problem: need Dutch .DIO
Hello there,
I have exactly the same problem as described here. I also tried a rename of the
Update.img to A639_K733.DIO which did load and was written in the ROM but the device still "hangs" at the blue "welcome" screen.
Would it be possible to obtain the "correct" .DIO from one of you guys? That would help me a lot! Thanks already in advance!
My system is originally Dutch and I would like to stick with it, so I would need a Dutch .DIO, but since I have a backup of my old system made with SpriteBackup, I guess (or better hope), also an English .DIO will do.
Again, thanks in Advance,
Andreas
I uploaded the DIO to rapidshare: http://rapidshare.com/files/182003093/A639_V10733.rar
now people can stop PM'ing me, this link should work fine
Many thanks to Cmonex,
With your help and this magic DIO file, my A639 is not dead and running again !
Hi there,
I have reflashed my A639 with cmonex file posted abowe it boot now ok but is stuck on the align screen and it not detect when i press on the cross. I think it is not defective because when the screen enter in save power mode if i touch the screen it become active. What can i do ? Thank you very much for any sugestion !
cmonex said:
I uploaded the DIO to rapidshare: http://rapidshare.com/files/182003093/A639_V10733.rar
now people can stop PM'ing me, this link should work fine
Click to expand...
Click to collapse
You are the man. Thank you for the share of the ROM. Saved me huge headache.
ASUS A639 fix
Israeli users (hebrew support): this image is not the israeli original ROM image supplied by Ronlight! it does not contain Eyron Hebrew support!
Unless you already had a WM6 w/hebrew support img on your A639 flash memory, after flashing this rom img you will need to install a new third party hebrew support software!
==flashing this img can void your warranty==
If anyone still need some help fixing a bricked Asus, just PM me.
Cheers,
cmonex said:
as someone sent this link to this thread to me in PM just now I thought I'd clarify some details..
a sample english .DIO is available from my server, but link is not public - you can PM me
otherwise, to obtain a .DIO, just make a backup of your ROM with pdocread while PDA is still working. if help is needed with that, please post the output of the command "pdocread -l"
Click to expand...
Click to collapse
Hello cmonex,
can detail(retail) you how to make a protection(saving) of the rom of the PDA with " pdocread " and tranformer files got back there .nbo
Hello cmonex,
can detail(retail) you how to make a protection(saving) of the rom of the PDA with " pdocread " and tranformer files got back there .nbo
I know it's an old post, but I got a bricked a639 that I only can get the bootloader to run. USB doesn't work, only updating with a A639_Kxxx.DIO works.
cmonex mentions in the post that "I uploaded the DIO to rapidshare: http://rapidshare.com/files/182003093/A639_V10733.rar". The A639_V10733.rar file on rapidshare however contains a file called A639_V10733.NB0 and not a *.DIO...
Since I can only update using a A639_Kxxx.DIO on my sd card, does anyone have a *.DIO available? I've been searching the internet for quite a while now, but can't find a DIO for download anywhere...
Greetings Ladies and Gents,
I believe I'm having a problem here of the same sort with an Asus A639. In a few words, I wanted to upgrade WM6 to a newer version (got it from Asus support site) and the installation crashed (the message said "could not read SD card"). After reset my PDA got stuck to the Asus welcome, blue screen
Now, I followed the lead, from previous posts but got real fast, completely lost.
I also tried several files provided but did not work. The last shown on display line reads "Waiting for download !".
I am using the english version for WM6.
Can someone help me out with a complete description for what I need to do?
Thank you
Regards
Forja
cmonex said:
I uploaded the DIO to rapidshare: http://rapidshare.com/files/182003093/A639_V10733.rar
now people can stop PM'ing me, this link should work fine
Click to expand...
Click to collapse
Hi cmonex.
One question about your uploaded file: Am I going to unrar the file then rename A639_V10733.NB0 into A639_V10733.DIO ?
Thanks!
ondeugd said:
I know it's an old post, but I got a bricked a639 that I only can get the bootloader to run. USB doesn't work, only updating with a A639_Kxxx.DIO works.
cmonex mentions in the post that "I uploaded the DIO to rapidshare: http://rapidshare.com/files/182003093/A639_V10733.rar". The A639_V10733.rar file on rapidshare however contains a file called A639_V10733.NB0 and not a *.DIO...
Since I can only update using a A639_Kxxx.DIO on my sd card, does anyone have a *.DIO available? I've been searching the internet for quite a while now, but can't find a DIO for download anywhere...
Click to expand...
Click to collapse
Hi, how did you do it?
wont work
nervoptik said:
Hi cmonex.
One question about your uploaded file: Am I going to unrar the file then rename A639_V10733.NB0 into A639_V10733.DIO ?
Thanks!
Click to expand...
Click to collapse
I've tried this, and wont work
I've changed the extension from NB0 to DIO.
After holding power + reset + enter, a gray screen appears for 2 seconds and it's written "FAT 16" ... and that's it!
nervoptik said:
I've tried this, and wont work
I've changed the extension from NB0 to DIO.
After holding power + reset + enter, a gray screen appears for 2 seconds and it's written "FAT 16" ... and that's it!
Click to expand...
Click to collapse
Hi @ all!
I have the same problem (downloaded file from rapidshare, renamed to DIO and after holding power+enter+reset for 2 seconds fat 16 and then freezed asus blue welcome screen), can anybody please help us ? (my device language rom was italian)
Bye
Asus A639 upgrade problem...
Join me in the remarks, I have the same problem: "after holding power+enter+reset for 2 seconds fat 16 and then freezed asus blue welcome screen"
What's this exactly? I did something wrong, or the PDA does'nt work properly?
I downloaded the file that Cmonex published on Rapid, but are'nt working.
I tried to upgrade, because it does not load the operating system ... only the blue screen appears at startup.
Any idea what might be the problem?
nyestegabesz said:
Join me in the remarks, I have the same problem: "after holding power+enter+reset for 2 seconds fat 16 and then freezed asus blue welcome screen"
What's this exactly? I did something wrong, or the PDA does'nt work properly?
I downloaded the file that Cmonex published on Rapid, but are'nt working.
I tried to upgrade, because it does not load the operating system ... only the blue screen appears at startup.
Any idea what might be the problem?
Click to expand...
Click to collapse
I think I had the same problem ,
try renaming the file on the SD card to exactly A639_K733.DIO
I was wondering, since it looks like HTCdev has stopped working, would it be possible to alter the Unlock_code.bin file that comes from HTCdev that works for my device to work with another device? I just opened the bin file with notepad to verify that we could edit the file. If we could figure out what makes the Unlock_code.bin file work with my device, maybe we could create a new Unlock_code.bin file to work with a different device, or at least that was what I was thinking.
I'm not smart enough to know that answer, but I'd be willing to throw mine in as well.
I know that unlock code is probably the key, but I haven't seen what's inside that file yet. I can't imagine you could just change that code for your device (since you can still get that code) - that would be too easy.
Sent from my HTC6500LVW using Tapatalk 4
I need about 4 of them so I can see whats the same vs whats different.
This is a piece of what you find in the Unlock File - 潻刈ഌ垀皅꜂Ẩ筣 - it is in the ball park of 120 characters long, that is just a guesstimate.
Yeah its a bunch of gibberish like it's encrypted or encoded or something. Will send mine over in a few if you think it's worth looking at.
Sent from my HTC6500LVW using Tapatalk 4
*Removed due to incorrect information*
This is the font I used to help display the characters better - http://www.prokerala.com/downloads/fonts/AnjaliOldLipi.ttf - to install in Win 7 download the file, double click to open, select install on the top left of the window. After that you will be able to select the font in the font list in notepad or whatever text editor you choose.
- Edit - I was incorrect in stating that it was in Malayalam, that appears to only be for ഌ , the part about the font helping better display the characters is true.
Guys, it's not gonna be in a human readable language because that would be dumb of HTC since anyone would be able to replicate the unlock then. Best bet is that comparing several using a hex editor will help.
Isnt the file signed? Thats the whole point of the token really? If you edit it you would lose the signature?
Notepad++ is a good translator And thats how it looks like when you go from ASCII to HEX the Bold is what I coun't convert.
Code:
894009A6BCAB49F9AFB7D42D5F8A6F49
7465B991F0D7F613FA9DD0DAF2D23C27
BD6D3951EFBF892065
97832A471A4B663C84412681030E1925
96563BFCBD7EA8C12406A99131757C42
9AAB1412B82271777FD78ED08D732B31
828DEE3C78C6F6B973A76FCF800C4A0B
410B
D717C8ED04EEFCE23604A5
C7E445D763BEAA86DCFE1145626F[B][U]‹ÿ[/U][/B]73D99D3739E772C6136F"51DC3797
450166F8004461596BA4
85ECF55695D17B7967240B27F94CC481
C320CD7E2B86620BEEA0F0E5C8C7A216
565BF3A6762C3FC662EA0F7B40C5FDA0
7962739CBB1286A32F5BB9B3A6597374
B8E346CC17178ADA1FC66BA18BA905F7
5F4D59C87E97E69CD186353B
I went ahead and did a conversion as well. I know 123421342 said that these were signed files but is there a way to copy the signature that is associated with the Unlock_Code.bin file? I do not really understand how signed files work, but HTCdev gives a different file per user, are the signatures the same on all of the Unlock_Code.bin files or is it a unique signature for each bin file that only works with your device?
Also, I do not know what I did differently when translating my bin file to Hex but it appeared that all of it was translated.
Code:
E6BDBBE58888E0B48CE59E80E79A85EA
9C82E1BAA8E7ADA3E88D91EF86B8ECA6
BFE7A4B8E79383E0ACA0EFA885E5A19C
E4809EEFA398E3A398E48FA1EBBFAFEC
A584E8BD8CE790AEE598B0E9B8B4ECA1
ADE8AC93E9B786E2AAACF394B386EEA1
A2E79289EB8FBFEEACA8EE8EADE59698
EAB898E1AFA6E2939FEBAA81E0B0B1E9
87B1EF94BDE0B4A2E79FA3EA968EEC81
A0ED83B2E6A88EE8A89BE5A788E4B1BC
E18EAAED8395E7B59FE2A4AFE29BB5EE
99BEE6A0B9EBB3ACEB9A82EE9C90EFB9
8BEE9888E698A4EE8DA1EC82A6E28EB3
F3A4B198E49689E281B3EB9F98E99ABF
E69A8BE786B6F1B1A396EC9AB3EF89B4
E38F92EEA48BE2BE8AEF90AFEAB19CE7
A796E1B2A7DE93E8AAB6E3BC8CE1938A
EFAD81EC8F89EC8B87E5B292EE85B6EA
BC86E7A9B0ECB8A1E4AF82E2A29BE281
9ADD99EE9FB3C394E4ADBEE2AF80EE9E
83E1A3BEEC81A5EE9295E3AA9AE58090
E598B3ECA696E6B3BAE0A497E884ABEA
B89AE6B1BCE29A99ECB0AFE2BF88E585
AFEE82BEEBBF84
Wozzie said:
I went ahead and did a conversion as well. I know 123421342 said that these were signed files but is there a way to copy the signature that is associated with the Unlock_Code.bin file? I do not really understand how signed files work, but HTCdev gives a different file per user, are the signatures the same on all of the Unlock_Code.bin files or is it a unique signature for each bin file that only works with your device?
Also, I do not know what I did differently when translating my bin file to Hex but it appeared that all of it was translated.
Code:
E6BDBBE58888E0B48CE59E80E79A85EA
9C82E1BAA8E7ADA3E88D91EF86B8ECA6
BFE7A4B8E79383E0ACA0EFA885E5A19C
E4809EEFA398E3A398E48FA1EBBFAFEC
A584E8BD8CE790AEE598B0E9B8B4ECA1
ADE8AC93E9B786E2AAACF394B386EEA1
A2E79289EB8FBFEEACA8EE8EADE59698
EAB898E1AFA6E2939FEBAA81E0B0B1E9
87B1EF94BDE0B4A2E79FA3EA968EEC81
A0ED83B2E6A88EE8A89BE5A788E4B1BC
E18EAAED8395E7B59FE2A4AFE29BB5EE
99BEE6A0B9EBB3ACEB9A82EE9C90EFB9
8BEE9888E698A4EE8DA1EC82A6E28EB3
F3A4B198E49689E281B3EB9F98E99ABF
E69A8BE786B6F1B1A396EC9AB3EF89B4
E38F92EEA48BE2BE8AEF90AFEAB19CE7
A796E1B2A7DE93E8AAB6E3BC8CE1938A
EFAD81EC8F89EC8B87E5B292EE85B6EA
BC86E7A9B0ECB8A1E4AF82E2A29BE281
9ADD99EE9FB3C394E4ADBEE2AF80EE9E
83E1A3BEEC81A5EE9295E3AA9AE58090
E598B3ECA696E6B3BAE0A497E884ABEA
B89AE6B1BCE29A99ECB0AFE2BF88E585
AFEE82BEEBBF84
Click to expand...
Click to collapse
It's like making an md5 hash. If you change a single bit the hash is changed. If you change the contents htc would have to sign it again so it has the private key signature
Sent from my HTC6435LVW using xda app-developers app
Please excuse my ignorance, I really do not have much knowledge of file signatures.
If HTC can resign the bin file, what is stopping us from doing something similar? Isnt it possible to view and make a copy of the file signature before it is altered? I realize these sort of things are in place to not be circumvented but the same could be said about all the work that has been developed here on XDA to unlock bootloaders along with other things.
Wozzie said:
Please excuse my ignorance, I really do not have much knowledge of file signatures.
If HTC can resign the bin file, what is stopping us from doing something similar? Isnt it possible to view and make a copy of the file signature before it is altered? I realize these sort of things are in place to not be circumvented but the same could be said about all the work that has been developed here on XDA to unlock bootloaders along with other things.
Click to expand...
Click to collapse
It's like a checksum, I presume. If the data changes, the signature changes as well to match the checksum. Unless you have inside knowledge of this, it will be extremely difficult to hack the tokens.
Meaning, if you change the data inside the file, you can't reuse the signature.
karn101 said:
It's like a checksum, I presume. If the data changes, the signature changes as well to match the checksum. Unless you have inside knowledge of this, it will be extremely difficult to hack the tokens.
Meaning, if you change the data inside the file, you can't reuse the signature.
Click to expand...
Click to collapse
Would it be possible to extract the signature of a file that has not been altered and then add that signature to an altered file?
I know it seems like a lot of work but if we could figure out how to create our own Unlock_Code.bin files, not only this phone but possibly other HTC phones might be able to use this method.
Wozzie said:
Would it be possible to extract the signature of a file that has not been altered and then add that signature to an altered file?
I know it seems like a lot of work but if we could figure out how to create our own Unlock_Code.bin files, not only this phone but possibly other HTC phones might be able to use this method.
Click to expand...
Click to collapse
No files are signed with a private key unless we have the key by stealing it or leaking it we can't sign things with their signature
Sent from my HTC6435LVW using xda app-developers app
Wozzie said:
Would it be possible to extract the signature of a file that has not been altered and then add that signature to an altered file?
I know it seems like a lot of work but if we could figure out how to create our own Unlock_Code.bin files, not only this phone but possibly other HTC phones might be able to use this method.
Click to expand...
Click to collapse
The signature changes with the file. The unaltered file's signature would not match the alerted file.
Sent from my HTC6500LVW using Tapatalk 4
anyone attempted to super CID it? make the phone similar to the sprint or other cdma with the same bootloader to get the code to unlock on htcdev?
just throwing that out there. i wont be on the ONE till late this year so i wont be able to work on it. :/
synisterwolf said:
anyone attempted to super CID it? make the phone similar to the sprint or other cdma with the same bootloader to get the code to unlock on htcdev?
just throwing that out there. i wont be on the ONE till late this year so i wont be able to work on it. :/
Click to expand...
Click to collapse
That would be an interesting approach. Or at least try to change the CID to T-Mobile or something. I honestly don't think it would work though.
synisterwolf said:
anyone attempted to super CID it? make the phone similar to the sprint or other cdma with the same bootloader to get the code to unlock on htcdev?
just throwing that out there. i wont be on the ONE till late this year so i wont be able to work on it. :/
Click to expand...
Click to collapse
Have to be s-off don't ya?
Code:
(bootloader) [SD_ERR] The project does not support SD card
(bootloader) E0902910 E0902E20
FAILED (status read failed (Too many links))
finished. total time: 0.003s
Flyhalf205 said:
Have to be s-off don't ya?
Click to expand...
Click to collapse
thought you already had s-off? this wont work for ya? idk what bootload you guys are on. :/
http://forum.xda-developers.com/showthread.php?t=2314582
For those who are still waiting for a fix for the update error and don't want to undergo the recovery process, I found a different solution, which doesn't need a recovery operation on the phone.
I tested it with success on my 1020 and another 925 which were stuck in the CU build .297.
Keep in mind that the parameters that I will use are specific to these phone models, so if you have a different one you need to find the parameters specific to your phone model.
This is an heuristic procedure, tested on a limited number of phones, so use it at your risk, keeping in mind that you could have problems or need to recover your phone loosing all your data, so do a proper backup before.
Let's start.
The problem appears because, during update phase, the oeminput.xml file becomes corrupted: as far as I know it happens only on some x20 models, and not for all the users.
Now we're going to rebuild it...
Go to the following link
https://msdn.microsoft.com/en-us/library/windows/hardware/dn756630(v=vs.85).aspx
Copy the content of example file oeminput.xml: i.e. copy the content of the framed zone after the phrase "The following example shows the contents of a sample ProductionOEMInput.xml file"
Paste in a .txt file which you'll rename and change extension so that it becomes oeminput.xml. Save it with notepad.
Now modify the file
at the node <SOC>{PROCESSOR_NAME}</SOC> modify {PROCESSOR_NAME} fake parameter in order to have the processor name of your phone: for the 920/925/1020 use QC8960
at the node <Resolution>480x800</Resolution> instead of 480x800 use the resolution of your phone: for the 920/925/1020 use 768x1280
in all the nodes related to language <Language>en-US</Language> use the language of your phone: I used for example it-IT because I have the phone in Italian language.
Save the file.
Now if you still don't have interop tools installed (but I think you should have if you arrived to CU with an x20 phone model) install it.
Launch interop tools and then click this device and enable full file system access. Reboot your phone, connect it to a pc with cable: you'll see more directories than usual, because you also unlocked system dirs: be careful not to delete or modify any dir apart from what you find in this guide or you'll risk to damage your phone. If you want to find your usual dirs (docs photos...etc), go to phone\Data\Users\Public. I advise you that after the procedure I couldn't deactivate full file system access, because it continues re-activating in interop tools, maybe there is a way: but you can live with this, because you can find the usual dirs in the path that I specified...
Now go to phone\windows\imageupdate, make a backup on pc of the current oeminput.xml and overwrite it with the new one.
At this point in the phone go to settings, update and then search for updates: you should find Fall Creators Update...
Good Luck!
p.s. I didn't extensively search on the forum if a similar guide has been already posted, in the case sorry for the duplication.
Thanks to Antonio who has actively participated in the realization of this guide
sigfrid696 said:
https://msdn.microsoft.com/en-us/lib...(v=vs.85).aspx
Click to expand...
Click to collapse
The link is wrong
Thank you!
I modified it, now it should be ok!
friend can you share the oeminput.xml file that you used?
NeoTriXz said:
friend can you share the oeminput.xml file that you used?
Click to expand...
Click to collapse
Done! Let me know if it works...change only language to match your phone language and do a proper backup of your original file...
sigfrid696 said:
Done! Let me know if it works...change only language to match your phone language and do a proper backup of your original file...
Click to expand...
Click to collapse
no friend did not work, I keep throwing the same error, some idea that can be or another solution?
NeoTriXz said:
no friend did not work, I keep throwing the same error, some idea that can be or another solution?
Click to expand...
Click to collapse
At this point I think it's not a problem of corrupted oeminput file.
I googled around...not so many people having the problem...I found this link...
https://answers.microsoft.com/de-de...nd-eimem/0a6e1776-9005-40e8-a18e-9eaf0f35b648
It's in german language, but from what I understood the problem has been solved with Recovery Tool via pc: I know that's not the best solution, but maybe better than remaining without updates. Another significative information is that an hard reset alone doesn't solve the issue!
I hope that can be of any help...
sigfrid696 said:
At this point I think it's not a problem of corrupted oeminput file.
I googled around...not so many people having the problem...I found this link...
https://answers.microsoft.com/de-de...nd-eimem/0a6e1776-9005-40e8-a18e-9eaf0f35b648
It's in german language, but from what I understood the problem has been solved with Recovery Tool via pc: I know that's not the best solution, but maybe better than remaining without updates. Another significative information is that an hard reset alone doesn't solve the issue!
I hope that can be of any help...
Click to expand...
Click to collapse
thank you friend, for your time, but I already solved it, well I had to perform a hard reset,
does this works for lumia 520
and what parameter should i used for my lumia 520 Rm 914
i'm stuck on 15063.251
and my lumia finds fall cu update
but shows Error 0x80070273
does this really resolve this error
i could not able to copy paste it it shows you don't have permission
how i get permission
---------- Post added at 06:42 AM ---------- Previous post was at 06:22 AM ----------
it gives me this error
Yash Agarwal windows said:
does this works for lumia 520
and what parameter should i used for my lumia 520 Rm 914
i'm stuck on 15063.251
and my lumia finds fall cu update
but shows Error 0x80070273
does this really resolve this error
Click to expand...
Click to collapse
I think you should use for 520
<SOC>QC8227</SOC>
<Resolution>480x800</Resolution>
If you receive an error when you try to overwrite oeminput.xml, it means that your phone has not been unlocked for full filesystem access. Please refer to the guide in order to enable full filesystem access
thanks
it worked for me
Getting this error code - 0x8018830f while updating to 14393.1884 (Lumia 730)
Can I try the fix from this post for this error?
Donz7733 said:
Getting this error code - 0x8018830f while updating to 14393.1884 (Lumia 730)
Can I try the fix from this post for this error?
Click to expand...
Click to collapse
this error is get due to incorrect processor no or incorrect screen resolution
Donz7733 said:
Getting this error code - 0x8018830f while updating to 14393.1884 (Lumia 730)
Can I try the fix from this post for this error?
Click to expand...
Click to collapse
You can examine your oeminput.xml file and check if it is somehow not well-formed.
If that is the case you can use
<SOC>QC8926</SOC>
<Resolution>720x1280</Resolution>
Thanks for the reply guys.
I couldn't wait longer, so went with an reset. It updated fine after that.
Later came to know it was some server issue
how do you replace the xml file? it says copying but refuses to actually replace the file.
rancorx2 said:
how do you replace the xml file? it says copying but refuses to actually replace the file.
Click to expand...
Click to collapse
you should need completely interop unlock your device using interop tools
then restart your phone
then after it copies without error
Yash Agarwal windows said:
you should need completely interop unlock your device using interop tools
then restart your phone
then after it copies without error
Click to expand...
Click to collapse
how is complete unlock ??????????
I use interop tools
bloody_earth said:
how is complete unlock ??????????
I use interop tools
Click to expand...
Click to collapse
The error overwriting oeminput.xml happens when you haven't obtained full filesystem access.
In order to obtain full filesystem access:
Open Interop Tools, then this device, then Interop Unlock.
Check Full Filesysytem Access and restart your device.
Refer to this thread to download correct version of Interop Tools
https://forum.xda-developers.com/windows-10-mobile/tutorial-restore-glance-windows-10-t3540571
Let me know if you can solve the problem this way.