Hello,
I followed the guide on AndroidRoot.Mobi.
I didn't find any information, if the received files are correct.
So I tried the guide twice to be sure that there was no error during file copy.
Sadly the factory-config.img has two different md5 checksums. :crying:
The other files (blob.bin, bricksafe.img & unlock-token.img) have the same checksum during both runs.
So is this possible?
Is there any script to check the generated files?
thanks
_beast_ said:
Sadly the factory-config.img has two different md5 checksums. :crying:
So is this possible?
Click to expand...
Click to collapse
Maybe the last mount timestamp in the filesystem was updated between your 2 runs. Check the real binary differences, they should be only few bytes.
_that said:
Maybe the last mount timestamp in the filesystem was updated between your 2 runs. Check the real binary differences, they should be only few bytes.
Click to expand...
Click to collapse
There are two times one byte chenged.
So this is cased by using the tablet between the 2 runs?
If this is really a time stamp it is very surprising that only 1 byte is changed.
_beast_ said:
There are two times one byte chenged.
So this is cased by using the tablet between the 2 runs?
If this is really a time stamp it is very surprising that only 1 byte is changed.
Click to expand...
Click to collapse
Maybe it's also something else, but if there is only one byte difference between your images, then you can be 99% sure that they are fine.
_that said:
Maybe it's also something else, but if there is only one byte difference between your images, then you can be 99% sure that they are fine.
Click to expand...
Click to collapse
Hopefully I will never need them.
Testing of files isn't possible I guess.
Related
Can Someone Please explain MD5 ... The uses and how to compare and check?
Many thanks in advance
What it does, how it works:
en.wikipedia.org/wiki/Md5
Program to calculate checksums (for example):
en.wikipedia.org/wiki/Md5sum
http://implbits.com/Products/HashTab.aspx this puts a tab on your (right click -> properties) and you can compare it there. makes MD5 easy.
its a way of error-detecting to see if it verifies 100% without any errors. this is critical when updating radios and things. if you have a bad copy of it then you may brick your phone or cause damage because you received a corrupted version
zephiK said:
http://implbits.com/Products/HashTab.aspx this puts a tab on your (right click -> properties) and you can compare it there. makes MD5 easy.
its a way of error-detecting to see if it verifies 100% without any errors. this is critical when updating radios and things. if you have a bad copy of it then you may brick your phone or cause damage because you received a corrupted version
Click to expand...
Click to collapse
I sort of get it....just ....what are you checking it with....so say i download a radio.img , then i check its md5 against what ? how would i know that whatever md 5 it had generated is the right one.....sorry for the questions
menov321 said:
I sort of get it....just ....what are you checking it with....so say i download a radio.img , then i check its md5 against what ? how would i know that whatever md 5 it had generated is the right one.....sorry for the questions
Click to expand...
Click to collapse
the OP would include a MD5. once you download it, right click the file you downloaded and go to the hash tab and copy paste the one the OP pasted.. copy paste it into the box and if it matches a check will appear meaning its 100% identical
if OP doesn't include one then you cant check
zephiK said:
the OP would include a MD5. once you download it, right click the file you downloaded and go to the hash tab and copy paste the one the OP pasted.. copy paste it into the box and if it matches a check will appear meaning its 100% identical
if OP doesn't include one then you cant check
Click to expand...
Click to collapse
OP????
what happens though if it isnt identical......
When it isn't identical, then the file got corrupted.
This can happen in a variety of ways, including:
- There was an error during download
- There was an error during the original upload
- The file got corrupted during storage on the server
- The file got corrupted because of an write/read error on your hard disk
- Someone purposefully manipulated the file, for example including a virus or even changed the file so that it would brick your device if you install it.
In any case: If the md5 doesn't match, then installing it is a big NO NO.
Effects can range from no problems over occasional errors and crashes to a completely bricked device (especially, if the error happens to be in the bootloader).
Or if someone manipulated the file willingly, he could be spying on you or causing you costs by making your phone send messages or doing calls to special expensive numbers. Or he could use your phone as a proxy for various illegal things.
PS: OP = orginal poster = the person who posted the file on the first place
Thank-you very much I understand now ....nice comprehensive answer....thanks though to all who posted
Sent from my Nexus S using XDA Premium App
Im trying to unpack system.IMG from the ruu and running into.issues.
Unyaffs.exe gives an error. And every other unpack tool I can think of fails.
Any ideas? Has anyone unpacked this yet?
Sent from my ADR6425LVW using XDA App
It doesn't use the yaffs filesystem. you need to unpack with explore2fs.exe on windows or in linux since it is ext4
Serinety said:
Im trying to unpack system.IMG from the ruu and running into.issues.
Unyaffs.exe gives an error. And every other unpack tool I can think of fails.
Any ideas? Has anyone unpacked this yet?
Sent from my ADR6425LVW using XDA App
Click to expand...
Click to collapse
Its EXT4.
The attached tool "should" do it for you. Its what I used...
I cannot however attrribute credit to the tool because I honestly do not know where it came from but its freeware GNU 3. The license is in the Help -> About.
Enjoy!
con247 said:
It doesn't use the yaffs filesystem. you need to unpack with explore2fs.exe on windows or in linux since it is ext4
Click to expand...
Click to collapse
I dont beleive explore2fs will read ext4. You need to use the one I posted above. Could be wrong as I am at work right now
scrosler said:
I dont beleive explore2fs will read ext4. You need to use the one I posted above. Could be wrong as I am at work right now
Click to expand...
Click to collapse
your the man, that worked I thought it was yaffs and nothing I did worked, it was driving me crazy lol.
2nd thing tho. the img file is 1.2gb, but after i extract it its about 697mb.. are there some hidden files that are not being extracted?
scrosler said:
I dont beleive explore2fs will read ext4. You need to use the one I posted above. Could be wrong as I am at work right now
Click to expand...
Click to collapse
It does I used it to extract the system image a couple weeks ago.
Serinety said:
your the man, that worked I thought it was yaffs and nothing I did worked, it was driving me crazy lol.
2nd thing tho. the img file is 1.2gb, but after i extract it its about 697mb.. are there some hidden files that are not being extracted?
Click to expand...
Click to collapse
Your saying JUST system.img is 1.2GB but extracts to /system/ as 697MB?
Thats some serisous backwards compression
700 Megs sounds about right for /systesm/ image. I can look when I get home. Maybe Con has it close by?
con247 said:
It does I used it to extract the system image a couple weeks ago.
Click to expand...
Click to collapse
What version do you have? I tried with the (what I thought was) latest and it wouldnt read it. I then tried with the other and it was fine. Can you post the version you have that read it?
scrosler said:
Your saying JUST system.img is 1.2GB but extracts to /system/ as 697MB?
Thats some serisous backwards compression
700 Megs sounds about right for /systesm/ image. I can look when I get home. Maybe Con has it close by?
Click to expand...
Click to collapse
File Name: system.img
Type: Disc Image File (.img)
Size on Disk: 1.21 GB (1,308,618,752 bytes)
Folder name: systemimg_upack
Type: Folder
Size on Disk: 697 MB (731,574,272 bytes)
Contains: 1,370 Files, 58 Folders
Serinety said:
File Name: system.img
Type: Disc Image File (.img)
Size on Disk: 1.21 GB (1,308,618,752 bytes)
Folder name: systemimg_upack
Type: Folder
Size on Disk: 697 MB (731,574,272 bytes)
Contains: 1,370 Files, 58 Folders
Click to expand...
Click to collapse
Wow, 500 Megs in slack? Now thats efficency!
But 700 megs sounds right to me for a sys img. I will in a few hours, at work now... Maybe can remopte desktop in... LMS...
Ok, RDP and 4G is AWESOME!
I can confirm what you are seeing is 100% correct.
I never noticed that before....
I also compared this with an Evo 3D ROM and it matches up proportionately....
scrosler said:
Ok, RDP and 4G is AWESOME!
I can confirm what you are seeing is 100% correct.
I never noticed that before....
I also compared this with an Evo 3D ROM and it matches up proportionately....
Click to expand...
Click to collapse
Wonder if its because Windows sees ext4 in a different way.. and mis represents its actual size
Sent from my ADR6425LVW using XDA App
Serinety said:
Wonder if its because Windows sees ext4 in a different way.. and mis represents its actual size
Sent from my ADR6425LVW using XDA App
Click to expand...
Click to collapse
Windows is not looking at it as a ext4 file system. Its looking at it as a single IMG file that is 1.x GB's big.
If you ever came across one of these QSB files from Lenovo and wondered how you could make use of it, this is what you are looking for. It is mostly wild guessing but this script have been tested successfully on 3 different QSB for the Vibe Z (K910).
You need Perl and its XML Simple extension in order to run the script.
Every feedback will be greatly appreciated.
csu333 said:
If you ever came across one of these QSB files from Lenovo and wondered how you could make use of it, this is what you are looking for. It is mostly wild guessing but this script have been tested successfully on 3 different QSB for the Vibe Z (K910).
You need Perl and its XML Simple extension in order to run the script.
Every feedback will be greatly appreciated.
Click to expand...
Click to collapse
Noob questions, I know:
How can I use this instead on running on linux? Can you build a win version? If I begin to work in a virtualbox machine, which are the steps?
katalinscrob said:
Noob questions, I know:
How can I use this instead on running on linux? Can you build a win version? If I begin to work in a virtualbox machine, which are the steps?
Click to expand...
Click to collapse
Good news is that since Perl is scripting, it should work pretty easily under Windows. If it is installed on your machine, just
Code:
perl split_qsb.pl
should be enough.
As for the extension needed (XML Simple), if I remember correctly, Perl is shipped with a configurator allowing to download such addon pretty easily.
I get this:
Code:
Data starts at offset 0
End of index detected
-1 entries and 0 bytes extracted
Rebuild the splitted files...
File does not exist: rawprogram0.xml at split_qsb.pl line 185
I think that it cannot split the qsb file, it's a lenovo firmware update, you now why this happen?
Thanks!
csu333 said:
Good news is that since Perl is scripting, it should work pretty easily under Windows. If it is installed on your machine, just
Code:
perl split_qsb.pl
should be enough.
As for the extension needed (XML Simple), if I remember correctly, Perl is shipped with a configurator allowing to download such addon pretty easily.
Click to expand...
Click to collapse
jarayama said:
I get this:
Code:
Data starts at offset 0
End of index detected
-1 entries and 0 bytes extracted
Rebuild the splitted files...
File does not exist: rawprogram0.xml at split_qsb.pl line 185
I think that it cannot split the qsb file, it's a lenovo firmware update, you now why this happen?
Thanks!
Click to expand...
Click to collapse
This means the QSB file you got differs from the one I've got. Are you able to make an extract of the first few kb so I can have a look?
Sent from my K910 with Tapatalk
csu333 said:
This means the QSB file you got differs from the one I've got. Are you able to make an extract of the first few kb so I can have a look?
Sent from my K910 with Tapatalk
Click to expand...
Click to collapse
I have similar issue for "B8080_S003191_140515_ROW_3GData_SD_Update.qsb"
Attached is the first 500 bytes of the qsb. Thank you
Resolved it finally just to the datastart to 0
seek(INF, 0, 0) or die "Could not seek in $IMAGE_FN: $!\n";
Thanks for the hint.
Little of topic, but what is a QSB file? Im trying to flash a Lenovo K920 and the instructions says (translated from Russians) un-zip to a QSB file... a normal un-zip does not reveal any QSB files. It is just a bin folder containing a lot of other file other than QSB-files...
Any advice?
csu333 said:
If you ever came across one of these QSB files from Lenovo and wondered how you could make use of it, this is what you are looking for. It is mostly wild guessing but this script have been tested successfully on 3 different QSB for the Vibe Z (K910).
You need Perl and its XML Simple extension in order to run the script.
Every feedback will be greatly appreciated.
Click to expand...
Click to collapse
----------------------------------------------------------------------------
It works, you did a great job.
but how coud we put these files back to QSB file after some modification?
Jacky_AndroidFanse said:
----------------------------------------------------------------------------
It works, you did a great job.
but how coud we put these files back to QSB file after some modification?
Click to expand...
Click to collapse
I know I am not adding much, but please how can we rebuild a QSB file from img bin files etc?
csu333 said:
If you ever came across one of these QSB files from Lenovo and wondered how you could make use of it, this is what you are looking for. It is mostly wild guessing but this script have been tested successfully on 3 different QSB for the Vibe Z (K910).
You need Perl and its XML Simple extension in order to run the script.
Every feedback will be greatly appreciated.
Click to expand...
Click to collapse
It's a handy tool, but how do we rebuild the qsb file?
Hi. Can You Mention The Procedure Completely. I Can't Understand The Flow.
hi there
Code:
PS C:\Users\blabl\Downloads\split_qsb.pl> perl .\split_qsb.pl
Usage: .\split_qsb.pl file.qsb
PS C:\Users\blabl\Downloads\split_qsb.pl>
i am using windows 10 x86 and have installed Strawberry perl
Hello.
I'm trying to customize the Boeffla Kernel (I9305 port) with a custom splash screen.
I've worked out that I need to use a initlogo.rle file at the root of the ramdisk, however I can't get the image to display properly.
I've atached two images, the first image is what the splash screen is supposed to look like, the second image is a photo of my phone showing how the image turns out.
Any assistance would be greatly appreciated
That typically happens when you're using the wrong size to convert the image. Make sure you're using 720x1280 and not any other resolution
CNexus said:
That typically happens when you're using the wrong size to convert the image. Make sure you're using 720x1280 and not any other resolution
Click to expand...
Click to collapse
I did use 720x1280, so it is the correct size (the image have been been reszied for the forum)
Is there a certain way the mage should be saved (Index, RGB etc?)
djb77 said:
I did use 720x1280, so it is the correct size (the image have been been reszied for the forum)
Is there a certain way the mage should be saved (Index, RGB etc?)
Click to expand...
Click to collapse
What are you using to convert the image to an RLE file?
I'm using the app from this thread here
The only thing I can guess is maybe this app might not be the right one
Still having trouble with it.
I don't want to give up on this, even if it takes me a while. I'm sure it can't be that complicated
BUMP
Any help at all? I'm still stuck with the same issues
Questions:
Is there a initlogo.rle there that you're trying to replace ?
If yes, can you provide both rle files?
There is no file I'm replacing just inserting it. The res is 720 x 1280
Sent from my GT-I9305 using XDA Premium HD app
Can you attach the initlogo.rle that you created?
You can use the same image in the OP
Sent from my GT-I9305 using XDA Premium HD app
That's a PNG, i need the RLE you used to create that double image error.
daedric said:
That's a PNG, i need the RLE you used to create that double image error.
Click to expand...
Click to collapse
Here you go...I had to zip it because the forums don't like RLE images
I'll need to check it at home... but i suspect the rle might be badly encoded.
How did you make it by the way?
daedric said:
I'll need to check it at home... but i suspect the rle might be badly encoded.
How did you make it by the way?
Click to expand...
Click to collapse
Using a PNG to RLE converter that I found on XDA. I dare say that somehting was encoded bad for this to happen.
If I knew exactly how it was to be encoded (or had the right encoder) I would be right hopefully.
It's just that I would probably want to create more splashes in the future, and even though I'd be grateful if this file was fixed, I'd also like to know how to make them properly in future
Here lies the catch: RLE is a means of encoding anything.
IF my memory doesn't fail me, you need a RAW file encoded in RLE. Now, you might need a RGB565 RAW file...
Take a look: http://forum.xda-developers.com/showthread.php?t=1516711
daedric said:
Here lies the catch: RLE is a means of encoding anything.
IF my memory doesn't fail me, you need a RAW file encoded in RLE. Now, you might need a RGB565 RAW file...
Take a look: http://forum.xda-developers.com/showthread.php?t=1516711
Click to expand...
Click to collapse
Still seem to be having the same issues.
Is it possible since there was no initlogo.rle there that it isn't properly supported by the kernel?
I know that it does show something when I put one there, but maybe there's something that needs adding to show it properly.
I've been digging the source code looking for logo loading code... and i suspect we MIGHT be missing something, i'm failing to find this instruction: load_565rle_image
daedric said:
I've been digging the source code looking for logo loading code... and i suspect we MIGHT be missing something, i'm failing to find this instruction: load_565rle_image
Click to expand...
Click to collapse
So it might not support that format at all by stock. It's weird how it does read that file though.
djb77 said:
So it might not support that format at all by stock. It's weird how it does read that file though.
Click to expand...
Click to collapse
You should pm DerTeufel1980. He's managed to accomplish adding a splash screen to his kernel for the Note II.
Has anyone come across a method to change the file naming convention on the HTC One M8? I want to have the date and time stamp included in the file name like other Android devices utilize. This not only helps easily identify the images without checking image meta data, but eliminates duplicate file names after flashing new roms.
Thanks for any help!
lagvoid said:
Has anyone come across a method to change the file naming convention on the HTC One M8? I want to have the date and time stamp included in the file name like other Android devices utilize. This not only helps easily identify the images without checking image meta data, but eliminates duplicate file names after flashing new roms.
Click to expand...
Click to collapse
Yes, please! I just got a replacement and all photo file names are duplicating. I can't find anywhere how to change the naming convention.
Shinteetah said:
Yes, please! I just got a replacement and all photo file names are duplicating. I can't find anywhere how to change the naming convention.
Click to expand...
Click to collapse
Huge fail on HTC's part with this one. Here's an alternative to help sort through your issue.
NameExif
http://www.digicamsoft.com/softnamexif.html
run the free program on your old files and it'll rename them according to the exif date data.
lagvoid said:
Huge fail on HTC's part with this one. Here's an alternative to help sort through your issue.
Click to expand...
Click to collapse
Thanks for the tip!
I found the ability to prepend a timestamp to camera files in the HTC one tweaker xposed module
Have you tried Dropbox?
lagvoid said:
Has anyone come across a method to change the file naming convention on the HTC One M8? I want to have the date and time stamp included in the file name like other Android devices utilize. This not only helps easily identify the images without checking image meta data, but eliminates duplicate file names after flashing new roms.
Thanks for any help!
Click to expand...
Click to collapse
I noticed that when I installed Dropbox, it automatically saved all my pictures and videos on my computer with the format you're requesting. This still doesn't solve the issue where it's fixed on my phone, but it wouldn't be too hard to just copy and paste them back after they're all uploaded to Dropbox. Good luck!
lagvoid said:
Huge fail on HTC's part with this one. Here's an alternative to help sort through your issue.
NameExif
http://www.digicamsoft.com/softnamexif.html
run the free program on your old files and it'll rename them according to the exif date data.
Click to expand...
Click to collapse
Shinteetah said:
Thanks for the tip!
Click to expand...
Click to collapse
morgej said:
I found the ability to prepend a timestamp to camera files in the HTC one tweaker xposed module
Click to expand...
Click to collapse
sigmacts said:
I noticed that when I installed Dropbox, it automatically saved all my pictures and videos on my computer with the format you're requesting. This still doesn't solve the issue where it's fixed on my phone, but it wouldn't be too hard to just copy and paste them back after they're all uploaded to Dropbox. Good luck!
Click to expand...
Click to collapse
Hi guys,
I know this thread is like ages old, but does anybody of you know a tool that's doing the exact opposite?
I have so many screenshots with the date + hour in the filename, but the exif data is lost .. Now I can't sort them by date anymore. Thanks so sooo much!!!