hi im newbie here this section about this tablet
yesterday i upgrade the tablet to version 4.0.x
My question is , how root it ?
Best Regwards
Nuno Rodrigues
Lisbon
Portugal
No root for ICS (OTA), yet...
ok ....
i will wait for that
thanks
See here: http://forum.xda-developers.com/showthread.php?t=1712150
It's an attempt on ICS root, and he needs testers. Since you have ICS, maybe you can give it a try. It's supposed to be harmless (please read that thread carefully), but I don't have ICS, so I can't really say...
Hi what is the zip i will install ???
Attached Files
File Type: zip 01 S update.zip - [Click for QR Code] (1.51 MB, 46 views)
File Type: zip 02 U update.zip - [Click for QR Code] (1.51 MB, 31 views)
File Type: zip 03 BB-SU.zip - [Click for QR Code] (1.14 MB, 39 views)
File Type: zip 04 Unroot.zip - [Click for QR Code] (241.4 KB, 28 views)
Click to expand...
Click to collapse
for root i think
No luck with the proposed files
I just tried to apply both updates (01 and 02) and both failed with "signature verification failed", tried to reply on the thread in development but I dont have enough points to do that.
Someone suggested to offer money to the developers to root the device, there is any place where I can send that money?
Thanks
I just tried to apply both updates (01 and 02) and both failed with "signature verification failed", tried to reply on the thread
Click to expand...
Click to collapse
I will wait for root
Thanks for all
Well, maybe next time it will work. What matters is that there's someone who's trying to root ICS. Let's hope success comes soon...
Related
Hi 2 All!
Please, can you help me in solving with the following problem.
I have download file bootloader.exe to my hp ipaq 1930 and I run it.
Now I see hp logo on white font and some numbers (bootloader version?) 1.07 and under it 1.07
Certainly, hard reset and removing the battery for 2-3 days didn't help. As I was said I need only to run update from big pc. I have another 1930, alive. I made rom-image to sd card using mtyy
Flashing with the card with rom-image didn't help to my injuried 1930
I contacted hp and they said to me that
the rom version for hp1940 1.00.03 is compatible. Then I ran the update, before that changing in the *.nbf file 1940 to 1930 and started flashing. It went to 75% and stoped saying Update error.
Then I was said to fullfill sd card with one symbol (Z). Then I made again a rom-image and I copied all hex values above code Z into a new file. I founf 2 entering starting from FE 03 00 EA and deleted the values above. Then I copied from 1940 nbf the following information^
Offset 0 1 2 3 4 5 6 7 8 9 A B C D E F
00000000 68 70 20 69 50 41 51 20 68 31 39 34 30 00 00 31 hp iPAQ h1940..1
00000010 2E 31 30 2E 32 30 20 45 4E 47 00 00 00 00 0F F6 .10.20 ENG.....?
00000020 71 77 00 00 0C 01
and in the dress from E1-21 wrote checksum value in 32 bit and length of the file in the addresses from 22-25. Then I copied the file into the folder from 1940 with the name=the name of the *.nbf file in the folder. I started update. It began and stoped on 50% saying "Update eroor"
Are there any ideas? Thanks a lot.
Or perhaps somebody has firmware for 1930/35? Thanks a lot
Maybe these people could help you, they must have the image if they are offering the service.
http://www.ipaqrepair.co.uk/ipaqpart447.html
Thanks. Here is the *.nbf file for 1930. http://www.megaupload.com/?d=HROH0ZOO It must have the same nema, as it is in the folder, where 1940 utiilty unpack it's files.
Copy it where the 1940 romupdateutility unpacked it's files. Then run again the utility
Alva said:
Thanks. Here is the *.nbf file for 1930. http://www.megaupload.com/?d=HROH0ZOO It must have the same nema, as it is in the folder, where 1940 utiilty unpack it's files.
Copy it where the 1940 romupdateutility unpacked it's files. Then run again the utility
Click to expand...
Click to collapse
hello could you please re-upload file?
Rom? where is the rom for 1930? please help me
Hey all,
I've been looking into how QDLTool works a bit and figured out how to swap the images that it flashes. Please note that QDLTool verifies image hashes for a good reason. You should understand the risks before attempting to meddle with QDLTool for any reason. Anything you do is at your own risk.
I would *strongly* recommend not flashing anything but amss, system, recovery and boot from any custom builds. Any time you flash a partition image, dbl, fsbl or osbl, you run the risk of bricking your device beyond recovery.
Important note: The information below is based entirely on analysis of QDLTool. I haven't used this to flash an image yet. If you plan on using this for development, you'll have to take that step.
Let's get to the details:
QDLTool automatically determines what to flash from the images/ directory. It stores a hash internally for each of the files that it will flash. This hash is basically just a 32-bit XOR of the bytes in the file:
Code:
#!/usr/bin/python
import sys
x = open(sys.argv[1], "rb").read()
print "%02x%02x%02x%02x" % (reduce(lambda x,y: x^ord(y), x[3::4], 0), reduce(lambda x,y: x^ord(y), x[2::4], 0), reduce(lambda x,y: x^ord(y), x[1::4], 0), reduce(lambda x,y: x^ord(y), x[0::4], 0))
To swap out an image, you need to patch the old hash of a file that was previously flashed with the new hash of the file that you'd like to flash.
For this post, I'll assume you're looking at QDLTool from streakflash.zip with MD5 = 63b64ba6a9d1ee770998d2a0e4a19df1.
In this file, the hashes start at offset 0x5fa90. There are 14 of them:
Code:
0005fa90 0b b0 a7 5c 3e e9 bb 29 17 4e 8d ac a0 dc 43 62
0005faa0 2c 3f 4e f1 fb 6b fc 80 11 9d 22 07 66 70 22 4a
0005fab0 bc 38 64 95 d2 c6 72 29 6d f8 99 e2 cc 74 14 49
0005fac0 1b ad 7a 9c 77 fb ee cc
As 32-bit words, they are:
5CA7B00B
29BBE93E
... etc ...
9C7AAD1B
CCEEFB77
In order, they are:
00. Partition (hash = 5CA7B00B)
04. Dbl (hash = 29BBE93E)
08. Fsbl
0c. Osbl
10. Amss
14. Dsp1
18. DT
1c. Appsbl
20. Boot
24. System
28. Userdata
2c. Recovery
30. Logfilter
34. RCFile
So, if I wanted to flash a new recovery, I'd take the hash of my recovery file via the Python script above, then replace the bytes at 0x5fa90 + 2c = 0x5fabc with my hash (stored in little-endian, of course).
It's a bit of manual work at this point, but I think a lot of this could be automated. You'd probably be better off and safer using batch files and fastboot though.
we discovered batch files to flash the images is a bad idea as some images cant be flashed using the normal fastboot mode
Thanks,
i'am looking some infomation about QDLTool also.
but i've no idea what hash was
i'll probatly wait for some "automated" way
QDLTools has so much potention. Somebody that knows coding should make it a automated system for us the little people...
Sent from my Dell Streak using XDA App
Yes, it would be nice if someone could figure out a way to insert new "roms" into the QDL tool, so when new updates are release, it would be a no brainer to do the updates without having to go through a bunch of command lines, or hocus-pokus to get an updated rom (minus the bloated carrier rom) onto the device.
Years ago, I played around with Linux, and found the same issue. A lot of command line knowledge is required. My command line stopped at dos 6.x, going all the way back to dos 2.x
Windows spoiled everyone
Just got my new sgs2 from germany
Already got the cm tough case, its good but hard to remove when needed.
As a n00b with the I9100, few things:
1. From my older I897 I know COG roms, is it the better option here too?
2. What way should I root my device? I know there is normal root and cf root
For unlocking I know there is chainfires app
Anything else I need to know?
Sent from my SGH-I897 using XDA App
Be useful to know about the rootin too please
easiest way
iakovl said:
Just got my new sgs2 from germany
Already got the cm tough case, its good but hard to remove when needed.
As a n00b with the I9100, few things:
1. From my older I897 I know COG roms, is it the better option here too?
2. What way should I root my device? I know there is normal root and cf root
For unlocking I know there is chainfires app
Anything else I need to know?
Sent from my SGH-I897 using XDA App
Click to expand...
Click to collapse
Well for me, I looked at the available ROMs and evaluated how troublesome each was flashing. And started from the easiest one to flash. I have not tried any other.
I read about 2 weeks in diffrent android forums before I flashed new ROM. It isn`t very dificult but at the moment there is simply no need to flash a custom ROM. There are very slight performance increases. But this will be different in 1 month I guess.
The ROM Guys here are very motivated! They ll do great work
To root, I flashed CF-Root kernel from this post:
http://forum.xda-developers.com/showthread.php?t=1103399
Very easy to do. Many thanks to Chainfire.
allanon+ said:
To root, I flashed CF-Root kernel from this post:
http://forum.xda-developers.com/showthread.php?t=1103399
Very easy to do. Many thanks to Chainfire.
Click to expand...
Click to collapse
I get root and a custom ROM in the same amout of process
Could anyone tell me which Kernel to put on?
I presume its 4.1 as thats the latest?
CF-Root-SGS2_XW_XEU_KE2-v4.0-CWM4.zip - [Click for QR Code] (7.01 MB, 11836 views)
CF-Root-SGS2_XW_XEU_KE7-v4.0-CWM4.zip - [Click for QR Code] (5.96 MB, 14348 views)
CF-Root-SGS2_XW_ODD_KE8-v4.0-CWM4.zip - [Click for QR Code] (7.01 MB, 4533 views)
CF-Root-SGS2_XW_OJV_KF1-v4.0-CWM4.zip - [Click for QR Code] (5.97 MB, 41211 views)
CF-Root-SGS2_XX_OXA_KF2-v4.0-CWM4.zip - [Click for QR Code] (5.97 MB, 18589 views)
CF-Root-SGS2_ZS_OZS_KF4-v4.0-CWM4.zip - [Click for QR Code] (5.96 MB, 6970 views)
CF-Root-SGS2_XW_CLK_KF3-v4.0-CWM4.zip - [Click for QR Code] (5.98 MB, 4642 views)
CF-Root-SGS2_XX_OXA_KG1-v4.1-CWM4.zip - [Click for QR Code] (6.08 MB, 9980 views)
I have an orange branded S2S with BVKE2 firmware on now?
Any help appreciated before I install it!
Funkyfin2000 said:
Could anyone tell me which Kernel to put on?
I presume its 4.1 as thats the latest?
CF-Root-SGS2_XW_XEU_KE2-v4.0-CWM4.zip - [Click for QR Code] (7.01 MB, 11836 views)
CF-Root-SGS2_XW_XEU_KE7-v4.0-CWM4.zip - [Click for QR Code] (5.96 MB, 14348 views)
CF-Root-SGS2_XW_ODD_KE8-v4.0-CWM4.zip - [Click for QR Code] (7.01 MB, 4533 views)
CF-Root-SGS2_XW_OJV_KF1-v4.0-CWM4.zip - [Click for QR Code] (5.97 MB, 41211 views)
CF-Root-SGS2_XX_OXA_KF2-v4.0-CWM4.zip - [Click for QR Code] (5.97 MB, 18589 views)
CF-Root-SGS2_ZS_OZS_KF4-v4.0-CWM4.zip - [Click for QR Code] (5.96 MB, 6970 views)
CF-Root-SGS2_XW_CLK_KF3-v4.0-CWM4.zip - [Click for QR Code] (5.98 MB, 4642 views)
CF-Root-SGS2_XX_OXA_KG1-v4.1-CWM4.zip - [Click for QR Code] (6.08 MB, 9980 views)
I have an orange branded S2S with BVKE2 firmware on now?
Any help appreciated before I install it!
Click to expand...
Click to collapse
I believe that the KG1 is the kernel being used in 2.3.4 roms. And the KF2 has newer modems than KF3 (old modem). And I'm unsure of KF4.
So do i need to upgrade to 2.3.4 first?
Orange has no update avaialble for 2.3.4 so guess I need to put that ROM on from somewhere? But I thought i couldn't do that before I rooted?
Ive come from a hero you see, things are a bit different! @
Funkyfin2000 said:
So do i need to upgrade to 2.3.4 first?
Orange has no update avaialble for 2.3.4 so guess I need to put that ROM on from somewhere? But I thought i couldn't do that before I rooted?
Ive come from a hero you see, things are a bit different! @
Click to expand...
Click to collapse
Well, in my case I just flashed Lite'ning rom which comes with root. So you only need 1 file to flash. This was when it was version 1.5. Now you have to flash 2.0 via odin and then flash the 2.1 update via CWM as I recall. I am not really sure about other processes since I have not tried others. Anyway, I hope this helps you somewhat.
You should always flash stock aim version (2.3.4) if the version is different (2.3.3. -> 2.3.4) to prevent any issues with the new rom. The new version is a 3file packet an data will be wiped.
You would need root first if you need to backup eg with titanium.
I can't seem to get the boot.img file to unpack, regardless of what tool I use or what os. I typically get the results below. the long term goal is to edit the boot.img to allow the next7p to use ext3 /system as opposed to cramfs, and give full read/write. It has been done by Wendal Chen on a different but similar tablet. (Both are rk29xx tablets.)
Any help would be appreciated.
I have been able to create a "custom" rom, which has root and SU, but you cannot write to the /system.
the boot.img from my custom rom is 598k The boot.img pulled from the tablet
is 4096K i get the same issues from both.
Code:
Welcome to the ZTE Racer kitchen by TigTex!
If you aren't using Windows XP, you might need to run this as admin
Make sure you have boot.img on the same folder as this file
Press 1 to decompress the ramdisk and kernel from boot.img
Press 2 to build the boot.img from the ramdisk folder and boot.img-kerne
Press q to exit
Type 1,2 or q and press ENTER: 1
Android Magic not found in boot.img. Giving up.
******kernel and ramdisk extracted!******
* Kernel is the "boot.img-kernel" file *
* Ramdisk is on gzip + cpio *
* YOU CAN ONLY EDIT RAMDISK ON LINUX *
* original img backed up as oldboot.img *
*****************************************
Press 1 to decompress the ramdisk and kernel from boot.img
Press 2 to build the boot.img from the ramdisk folder and boot.img-kerne
Press q to exit
Type 1,2 or q and press ENTER:
Ok so let's try the android kitchen
Here is the show boot.img information
Code:
Working folder's boot.img information
-------------------------------------
Kernel Size : 559903 bytes
Kernel Base Address : 0x00000000
Ramdisk Size : 2090599168 bytes
Ramdisk Load Address : 0x65545c0b
Second Stage Size : 779876570 bytes
Second Stage Load Address : 0xe1906573
Page Size : 84348953 bytes
ASCIIZ Product Name : (None)
Command Line: (None)
Press Enter to continue
And now the attempt to extract first using w option...
Code:
Working folder found
Android header not found at start of boot.img
Warning: Android header not located anywhere in boot.img
Kernel found at offset 84348953 in boot.img
Making folder BOOT-EXTRACTED ...
Extracting kernel ...
Extracting ramdisk ...
Error: No ramdisk folder found!
Press Enter to continue
Ok so lets try the other option in the menu.
Code:
Press Enter to continue
Android header not found at start of boot.img
Warning: Android header not located anywhere in boot.img
Kernel found at offset 84348953 in boot.img
Extracting kernel ...
Extracting ramdisk ...
Error: No ramdisk folder found!
Contents of bootimg_010612_234100:
total 0
-rw-r--r-- 1 0 2012-01-06 23:41 zImage
Press Enter to continue
The zImage file it writes is 0k in size.
Here is the first line from the boot.img looking at it in the hexeditor.
Code:
00000000 4b 52 4e 4c 3a 93 08 00 1f 8b 08 00 00 00 00 00 KRNL:"...<......
From what I have read the kernel is supposedly starting at 1f 8b.....
getting the error that the Ramdisk is not there, it is almost like it is not a complete boot.img file. More so if I look at boot.img in a hexeditor and lookup that address. (Sigh) I keep plugging away.
any help is appreciated.
Dochoppy said:
I can't seem to get the boot.img file to unpack, regardless of what tool I use or what os. I typically get the results below. the long term goal is to edit the boot.img to allow the next7p to use ext3 /system as opposed to cramfs, and give full read/write. It has been done by Wendal Chen on a different but similar tablet. (Both are rk29xx tablets.)
Any help would be appreciated.
I have been able to create a "custom" rom, which has root and SU, but you cannot write to the /system.
the boot.img from my custom rom is 598k The boot.img pulled from the tablet
is 4096K i get the same issues from both.
Code:
Welcome to the ZTE Racer kitchen by TigTex!
If you aren't using Windows XP, you might need to run this as admin
Make sure you have boot.img on the same folder as this file
Press 1 to decompress the ramdisk and kernel from boot.img
Press 2 to build the boot.img from the ramdisk folder and boot.img-kerne
Press q to exit
Type 1,2 or q and press ENTER: 1
Android Magic not found in boot.img. Giving up.
******kernel and ramdisk extracted!******
* Kernel is the "boot.img-kernel" file *
* Ramdisk is on gzip + cpio *
* YOU CAN ONLY EDIT RAMDISK ON LINUX *
* original img backed up as oldboot.img *
*****************************************
Press 1 to decompress the ramdisk and kernel from boot.img
Press 2 to build the boot.img from the ramdisk folder and boot.img-kerne
Press q to exit
Type 1,2 or q and press ENTER:
Ok so let's try the android kitchen
Here is the show boot.img information
Code:
Working folder's boot.img information
-------------------------------------
Kernel Size : 559903 bytes
Kernel Base Address : 0x00000000
Ramdisk Size : 2090599168 bytes
Ramdisk Load Address : 0x65545c0b
Second Stage Size : 779876570 bytes
Second Stage Load Address : 0xe1906573
Page Size : 84348953 bytes
ASCIIZ Product Name : (None)
Command Line: (None)
Press Enter to continue
And now the attempt to extract first using w option...
Code:
Working folder found
Android header not found at start of boot.img
Warning: Android header not located anywhere in boot.img
Kernel found at offset 84348953 in boot.img
Making folder BOOT-EXTRACTED ...
Extracting kernel ...
Extracting ramdisk ...
Error: No ramdisk folder found!
Press Enter to continue
Ok so lets try the other option in the menu.
Code:
Press Enter to continue
Android header not found at start of boot.img
Warning: Android header not located anywhere in boot.img
Kernel found at offset 84348953 in boot.img
Extracting kernel ...
Extracting ramdisk ...
Error: No ramdisk folder found!
Contents of bootimg_010612_234100:
total 0
-rw-r--r-- 1 0 2012-01-06 23:41 zImage
Press Enter to continue
The zImage file it writes is 0k in size.
Here is the first line from the boot.img looking at it in the hexeditor.
Code:
00000000 4b 52 4e 4c 3a 93 08 00 1f 8b 08 00 00 00 00 00 KRNL:"...<......
From what I have read the kernel is supposedly starting at 1f 8b.....
getting the error that the Ramdisk is not there, it is almost like it is not a complete boot.img file. More so if I look at boot.img in a hexeditor and lookup that address. (Sigh) I keep plugging away.
any help is appreciated.
Click to expand...
Click to collapse
Dsixda's kitchen has this feature, (un/re-pack) boot.img built in. Makes for very easy editing. Also helps for making your ROM.
Sent from my PC36100 using xda premium
jamieg71 said:
Dsixda's kitchen has this feature, (un/re-pack) boot.img built in. Makes for very easy editing. Also helps for making your ROM.
Sent from my PC36100 using xda premium
Click to expand...
Click to collapse
That's what he said he used, but the kitchen does not support boot.img of his device's format. A lot of the cheaper tablets use a special format but I have seen Wiki guides on how they are built and extracted.
Any chance you know a link to one of the guides? I will also start searching on like tablets.
Dochoppy said:
Any chance you know a link to one of the guides? I will also start searching on like tablets.
Click to expand...
Click to collapse
Google for the "cmp738a" by Craig. It's a really ****ty tablet that I owned for one day. It uses cramfs like yours, and there are some links on how to unpack and create a ROM. Use terms like "cmp738a unpack ROM"
Dsixda: First thanks for your kitchen tool really it is a great piece of work, I am sure you are under appreciated for it.
After you told me to do some searches I did, then I looked back over everything I had been reading.
I can say I feel like an idiot. I was letting the big picture blot out the details so to speak.
Almost literally all I had to do was remove 3-4 bytes from the header, and ungzip the file...cpio etc etc.
I was stuck in the train of thought that I had to "unpack the boot.img" file first, then ungzip it...
Dochoppy said:
Dsixda: First thanks for your kitchen tool really it is a great piece of work, I am sure you are under appreciated for it.
After you told me to do some searches I did, then I looked back over everything I had been reading.
I can say I feel like an idiot. I was letting the big picture blot out the details so to speak.
Almost literally all I had to do was remove 3-4 bytes from the header, and ungzip the file...cpio etc etc.
I was stuck in the train of thought that I had to "unpack the boot.img" file first, then ungzip it...
Click to expand...
Click to collapse
You mean it's like any other boot.img except for the extra bytes at the beginning and a different header (instead of "ANDROID!" - the actual header the kitchen looks for)?
Well yes and no. The kitchen still does not extract the boot.img correctly, zImage is created as a 0k file, and the ramdisk is still not extracted.
Ok I am still missing something here.
Ok I am still missing something here.
dsixda-
Could you take a look at the boot.img file and tell me what I may be missing?
http://www.mediafire.com/?n9an9o5vmjida1c
I would appreciate it very much.
Dochoppy said:
Ok I am still missing something here.
dsixda-
Could you take a look at the boot.img file and tell me what I may be missing?
http://www.mediafire.com/?n9an9o5vmjida1c
I would appreciate it very much.
Click to expand...
Click to collapse
It's not going to work in the kitchen, what are you trying to do? It is missing the "ANDROID!" magic header and the rest of the file is in a garbled format. You'll need to Google for the solution for your device. I can't offer much help, sorry.
I understand that much. When you do a file boot.img command in linux it just comes back as DATA.
I'm not so much concerned with being able to use the kitchen on it as just being able to unpack and pack the file correctly, and completely.
Thanks for taking a peak at it.
Can you upload to dropbox and let me know. I was working on an experimental tool to do this, so an unknown device would be good to check.. I might be some time in getting back to you though
Sent from my HTC Desire using Tapatalk
Droidzone-
Drop box link
http://dl.dropbox.com/u/56600275/boot.img
Media fire link if that doesn't work.
http://www.mediafire.com/?n9an9o5vmjida1c
Thanks for taking a peak.
Could you also provide the full name of the tablet, manufacturer, and possibly a link to the device?
The tablet in question is the nextbook 7 premium
marketed in the US by E-fun. Website is www.nextbookusa.com
on the front of the page there is a link to the latest firmware which the current version of DocHoppy Rom is based on.
Thanks again for taking a peak at it.
I know this much, the boot.img file it's self once unpacked from the update.img file
is a gziped cpio file, with odd header and footer bits. I have been able to unpack the file (removing header info to make it gzip recognizable), and then using 7zip of all things to unpack the cpio portion. That is where I get hung up at. I need to unpack it correctly so it can be rebuilt correctly. By doing it the way I have, you can't rebuild the file properly.
Update:
After alot of research, and trial and error, I was able to correctly unpack and repack the boot.img. I flashed the repack to my tablet, and successfully booted.
Next step is to modify init.rc and convert /system to ext3.
I will keep you posted.
Do document what you did so that it helps someone else later
Sent from my HTC Desire using Tapatalk
I'm having a similar problem, posted about here. I don't understand why the Android magic number isn't making it into my kernel. I thought the kernel compile would be straightforward, but sheesh...
Dochoppy said:
Update:
After alot of research, and trial and error, I was able to correctly unpack and repack the boot.img. I flashed the repack to my tablet, and successfully booted.
Next step is to modify init.rc and convert /system to ext3.
I will keep you posted.
Click to expand...
Click to collapse
Hi, i am trying to extract a boot.img without the Android header too. What have you done to extract it?
Regards.
I have problem when i try to unpack boot.img from CM10.1.3 Stable version for I9100G.
I tried many time but It say can't find kernel or ramdisk.
Any body help me please?
Anybody help me please???????????????????????
Very few people post here these days, not even the mods seem to be around. If you want help with this, you're either going to have to be really patient (understatement, don't be surprised if you still don't have an answer in a week), or go ask in the CM discussion thread. Your question isn't exactly a 'Hlap mai fone borked ! Odin don't werk !' type query. There aren't many people who post to S2 forums anymore who can answer this type of question.
So you can either sit in this thread & not get the answers you're looking for, or you can be proactive & seek them out.
I tried to worked out with few boot images before. I dont know what is yours
can you upload it please.
If you have windows it will be easy for you to explore that image in hex editor
That what i know so far is. Open your image in hex editor and look for "error" phrase
and you will find several of that 'error' kernel error header error compression error
im my case it is last one before compressed file. You need to recognize magic of
compressed file it is just after 'error'
Ex.
for gzip is: 1F 8B 0B
for LZMA is: 5D 00 00 00 04 FF FF
you can look for that instead 'error' And then you need to cut of everything before
magic number. Make your file start of that magic number. If you do that you will be able to
decompress it. gunzip file.gz or unlzma file.lzma
or you can use your android to find archive in your boot.img
hexdump -C boot.img | grep '1f 0b 08'
and result is
000046b0 72 6f 72 00 1f 8b 08 00 00 00 00 00 02 03 ac bd |ror.............|
ant then you have hex address 46b0 witch is pointing on first byte of that line. Its 72
hex is not easy to count in your memory so we need to convert it to dec value
echo $((16#46b0))
result is
18096 but remember this addres is pointing on 72. We need address of next 4 byte 1f
so we need to count in a memory then. Addres of 1f is 18100
Its easy now. We need to extract archive from boot.img
dd if=boot.img of=archive.gz bs=18100 skip=1
And then decompress it. Thats not all it is just a clue i hope it will work out for you