First of all, I'd like to say that I performed Anansky's BigStorage upgrade without a hitch on my 850MHz JAM running on Cingular's network. The only concern was that the device was reporting itself as a PM10A instead of a PM10C.
Precautions:
1. Use the write-protect feature on your SD card in the unlikely event that Windows or your PocketPC wishes to write or format it.
2. Use a smaller SD card, as the steps will create a ROM file as big as your card, and it'll take a while to load the file to make changes, update the SD card, etc.
3. Burn a copy of your downloaded ROM file to a CD for safety purposes.
4. Always keep your PocketPC charged either through your PC's USB port, or through a USB-to-AC adapter.
For those who want a quick rundown on how I did it:
1. From the FTP, download NTRW.EXE (version 2.0), ROMUPDATE.EXE, and MAGICIAN_OS1.11WWE_BIGSTORAGE_6.ZIP.
2. With your JAM connected via USB to your PC, disable ActiveSync's connections.
3. Enter the Bootloader and backup your entire ROM to your SD card using ROMUPDATE.EXE.
4. Read the contents of your SD card into a ROM file using NTRW.EXE. (Note that Administrator priviliges are required on your Windows account in order to read/write to the card)
5. Modify the first 416 decimal bytes of the OS1.11WWE_BIGSTORAGE.NB1 (extracted from the ZIP file) by using the first 416 decimal bytes from your ROM file.
6. Write the newly modified ROM file onto your SD card using NTRW.EXE.
7. Enter the Bootloader with the SD card inserted and flash the newly modified ROM to your device.
Notes:
1. I was able to reflash the official i-mate CE ROM (1.11) and Radio, thinking I'd force 850MHz support back into the device in the uncertain event it lost it during Anansky's upgrade. However:[list:44fd36694d]1. The Radio can't be flashed without the CE ROM being flashed alone first.
2. Any reflashing of the Radio or the CE ROM will lose your newly acquired 27MB Storage area. The Device Information applet will report a crazy value for the Storage area when in fact it's totally gone. The only way to restore it is to put your backed up old ROM image onto the SD card and perform the flash from the card.
2. The only way to find out how the hack was done is to look at the different versions of the hack and compare them byte-by-byte to the official updaters.
3. Perhaps one can perform another full SD-to-ROM backup with Anansky's upgrade and compare the files as well, then inject the compatible ROM portions and leave his hack in place.
4. Reflashing any of the ROM portions did NOT restore my model back to PM10C, which leads me to believe that it's outside that region untouched by the official flash utility.
5. I was only able to reflash with the official ROM updaters AND the hacked MaUpgradeUt_noID.exe from the FTP, and while it was in Bootloader mode only.
[/list:u:44fd36694d]
Lastly, I restored my original ROM image in its entirety and will try again sometime in the future to see if I can incorporate the 850MHz ROM into Anansky's hack. It was nice having the extra 27MB free for a short while, but until he comes back or someone else figures it all out, it'll be a risky endeavour in the event of another official ROM upgrade.
ADVANCED USERS ONLY. I take no responsibility for the information I provide below.
I dissected Anansky's ROM to find different sections which I could possibly compare. This is by no means accurate, but I have found certain locations to be of value.
Using the Magician ROM layout on http://wiki.xda-developers.com/index.php?pagename=MagicianRomLayout, I was able to build upon that template. Note that the values start with 80000000, but subtract that value and you get the starting points below.
00A6019C-00AC82D6 = UNKNOWN
00AE019C-00B3319A = UNKNOWN (REFERENCES TO RINGTONES)
00B6019C-00C3F3D5 = UNKNOWN (REFERENCES TO GPRS?)
00CB019C-00F88BF6 = UNKNOWN
00FB019C-014101CF = UNKNOWN
0143019C-0185B015 = UNKNOWN (APPROXIMATELY 4MB... RADIO ROM?)
0187019C-01995D38 = UNKNOWN (REFERENCES TO T9 DICTIONARY)
019E01AC-01CDDE58 = UNKNOWN (REFERENCES TO LDAP, DRM)
01DB019C-01E21343 = UNKNOWN (WINDOWS MEDIA PLAYER COMPONENTS?)
01E4019C-01EF8943 = UNKNOWN (SOLITAIRE / JAWBREAKER)
01F1019C-01F9B0CE = UNKNOWN (REFERENCES TO VPN)
01FC019C-0236A72B = UNKNOWN (APPROXIMATELY 3.8MB, REFERENCES TO NETWORK ADAPTERS, MODEM)
03F80140 = ANANSKY'S ROM CREDITS
03FB819C = MODEL (PM10A)
03F4015C = DATA STRING (UNKNOWN)
03F4019C = SPLASH SCREEN ("HTC MAGICIAN" VOLCANO)
For instance, if you wish to change the splash screen, you could replace the 153,600 decimal bytes starting at 03F4019C hexidecimal with your Splash2.NB file.
I have compared the 4MB block (0143019C-0185B015 hexidecimal) between my 1.11 NA ROM dump and Anansky's and found NO DIFFERENCE. It is possible that this section is the Radio ROM area, due to the size. I have to have the radio.nbk file decrypted in order to confirm.
If there are minute differences, I'll be sure to catch them now. Stay tuned.
I did something similar to find out, what he did. I first flashed Qtek's 1.11, then backed it up on SD card and wrote it to a file. Then I flashed Ananskys ROM and was now able to compare.
Unfortunately we know to few about the internals of the ROM (at least considering what's in the wiki).
BeyoneTheTech,
A question completly unrelated to the big storage ROM. How is it that your JAM has a 850Mhz Processor?
It's 850MHz radio band, unfortunately not CPU speed! I live in North America where the 900MHz is not utilized due to many pre-cellular products hogging up the 900MHz frequency.
As for everyone else, I used a program called WinHex to byte-compare the minimal differences between Anansky's BigStorage ROM file and my own ROM dump file. Bear in mind it's almost in the morning now and I crazily did this at work, so the details will be minimal:
I noticed two byte differences - B8 01 (1B8 hex=440 dec) vs 80 00 (80 hex=120 dec). I did NOT change those because I found it once in the bootloader, so I assumed it might be related to the way it handles the Storage area/Extended ROM.
The second set of differences were where the string "PM10A" was found in Anansky's ROM. Mind you, "PM10A" was also found in my ROM file (in the CE ROM portion), so I took my bytes around the "PM10C" section near the end and transposed it into Anansky's ROM file.
Of course, there was a major differrence in the middle of the two ROM files: the Extended ROM data. I left that the way it was in Anansky's ROM, mostly zeros and some "header"-looking information.
Bottom line is I have what appears to be a fully-functioning ROM file that I flashed successfully onto my 850MHz-band i-mate JAM (running on Cingular's network in the Northeast Americas.) I have little doubt it's not utilizing the 850MHz band, since the byte changes were so minimal between Anansky's WWE ROM and my official NA (850MHz) WWE ROM. My Device Information applet reports "PM10C," of course because I hardcoded it into the ROM, but I also mapped the bytes around it from my original "850MHz" ROM. Oh, and I've got my 27MB back! :wink:
I don't particularly see a problem with having your PM10C device updated with Anansky's ROM. Although the machine will now identify itself as PM10A, people have reported still being on 850MHz cells... so there shouldn't really be a problem there.
The only issue is that now when i-Mate releases upgrades, I'm only able to flash the European and not the North American mods.
What exactly is the method to force a North American ROM upgrade onto a supposedly European JAM? I didn't save the backup which was on the SD card.
As I stated last night and bleary-eyed, there was very little difference between the North American (850MHz) and the WWE (900MHz) versions of the ROM dumps. I believe most, if not all of the differences resided in the Extended ROM. Just the changes noted below worked on my 850MHz JAM.
Using the os1.11wwe_bigstorage.nb1 file...
1. Write FF's into offset 0000028Ch to 00000293h, erasing the T-MOB101 designation.
2. Change the letter A (41h) to C (43h) at offset 03FB81A4h, so it should read "P M 1 0 C."
3. Change bytes 09 2D 4D 27 C7 to 09 2D 4C D1 8E at offset 03FB81DDh to 03FB81E1h. Again, this was near the PM10C designation, and it's unlikely that this code is my IMEI number, so I'm trying to retain as much of my original ROM as possible.
4. Change the splash screen if you wish (see previous post).
Perform a full backup with Sprite Backup or similar program.
SD-Flash the new file onto your JAM and you should be good to go.
Perform a full restore with Sprite Backup, ignoring any ROM upgrade warnings.
If you feel comfortable with hex editing, use WinHex with the ROM files. It opens files fast and can copy and "write" (not paste) the splash screen in one shot.
I am hoping that if someone can easily decrypt the new CE and Radio ROM images, they can be injected into Anansky's ROM dump, while someone who still has their Extended ROM area will be able to extract any new changes or updates in the CAB files.
Shawn_230 said:
What exactly is the method to force a North American ROM upgrade onto a supposedly European JAM? I didn't save the backup which was on the SD card.
Click to expand...
Click to collapse
Just use the "NoID" version of the MaUpgrade EXE found on the FTP, but remember: Any flashing after Anansky's hack will make your Extended ROM/Storage area disappear! Like I stated in my previous post, let's hope someone can create a new xda3nbftool to decrypt the new ROMs and we might be able to either "inject" it into Anansky's ROM dump file, or we can change the necessary bytes, reencrypt, then upgrade only that portion of the ROM to your Magician/JAM device.
BeyondtheTech said:
Just use the "NoID" version of the MaUpgrade EXE found on the FTP, but remember: Any flashing after Anansky's hack will make your Extended ROM/Storage area disappear!
Click to expand...
Click to collapse
BeyondtheTech, I had an 900mzh version but I am living in US too. Actually, there is a very simple solution w/o going thru the hacking of the rom (But it's good someone can experiment how Anansky's did it so that we could do it for the future rom update).
1. Grab the latest USA rom from imate.
2. extract it w/ Winrar and U will get 3 nbf files.
3. Keep the radio_.nbf and remove the other 2
4. Use the no id version of MaUpgrade and it will only update the radio
5. U radio is 850mzh version and U still have the big storage
FYI, I don't know if you actually tested your sets, because I did flash just the alleged "USA" radio portion on my 850MHz JAM and I did lose the BigStorage area entirely, which is why I said that any subsequent flashing will do just that.
BeyondtheTech said:
FYI, I don't know if you actually tested your sets, because I did flash just the alleged "USA" radio portion on my 850MHz JAM and I did lose the BigStorage area entirely, which is why I said that any subsequent flashing will do just that.
Click to expand...
Click to collapse
Of course, I did.
BeyondtheTech said:
ADVANCED USERS ONLY.
00A6019C-00AC82D6 = UNKNOWN
.../...
03F80140 = ANANSKY'S ROM CREDITS
03FB819C = MODEL (PM10A)
03F4015C = DATA STRING (UNKNOWN)
03F4019C = SPLASH SCREEN ("HTC MAGICIAN" VOLCANO)
I have compared the 4MB block (0143019C-0185B015 hexidecimal) between my 1.11 NA ROM dump and Anansky's and found NO DIFFERENCE. It is possible that this section is the Radio ROM area, due to the size. I have to have the radio.nbk file decrypted in order to confirm.
If there are minute differences, I'll be sure to catch them now. Stay tuned.
Click to expand...
Click to collapse
Following to BeyondtheTech post, I'm now shure that the so called 'big storage' is located between address:
023c0190 : 03f40190 (about 27 MB)
I've also determined that every 256 kB (+40000h), this 'virtual disk' include something similar to a 'sector header' conform to:
f0 f0 f0 f0 00 00 00 00 96 f2 e7 10 db d3 00 fc
Click to expand...
Click to collapse
this string is present at address:
02400140h, 02440140h, 02480140h, 02480140h .../...
03f00140h, 03f40140h
For checking the validity of my theory, I've copied about 15 MB of different files, before making a backup of my Qtek S100. It's confirm that the data are occupying this space.
Because, I'm normaly working on a french OS version, I need all accentuated; and diacritic characters to answer my mail. So my purpose is now to 'reverse engeneer' the Anansky method to include this very usefull 'big storage' on a french based OS.
So, I've merged all content of my original v1.11 French OS UpGrade from address 00000000h to 023c0100h... This personaly cooked OS is working, and all is in french... but 'no-big-storage' available unfortunately.
So, in the next step, I've tried to undestand, how 'virtual storage' is working under Qtek S100. Back to my original OS, with small 7 MB storage. On the hexadecimal point of view, nothing more than, with the Anansky backup version, except that the virtual disk is smaller... Everything is in order, according to my theory...
But because the 'big storage' is not even visible, my conculsion is simple: "the solution is in the 'registry', but I've not yet been able to go through the mystery:
HKEY_LOCAL_MACHINE\System\StorageManager\Profiles\VDisk
"Name"="Extended_ROM"
"Folder"="Extended_ROM"
.../...
[HKEY_LOCAL_MACHINE\Drivers\Active\43]
"Hnd"=dword:0068e3f0
"Name"="DSK8:"
"Key"="Drivers\\VDisk"
"ClientInfo"=dword:00000000
.../...
[HKEY_LOCAL_MACHINE\Drivers\VDisk]
"Key"="Drivers\\VDisk"
"WindowBase"=dword:a2c00000
"Size"=dword:01300000
"Folder"="Extended_ROM"
"DisableInt"=dword:00000000
"OnBoard"=dword:00000001
"Dll"="VDISK.DLL"
"Index"=dword:00000008
"Prefix"="DSK"
"Profile"="VDisk"
.../...
[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\FlshDrv]
"FolderName"="Storage"
Click to expand...
Click to collapse
Close to all references in the registry seem to be dedicated to the Extended_ROM (about 19 MB) that can become visible, but not writable... until yet.
I've found only one reference to the 'Storage' folder (about 7 MB on my QTek), but I don't understand how the OS know it's type, size, location, etc. Another thing is shure: the registry is not directely visible in the backup. I suppose that this file is compressed in ROM, and decompress to Ram for working (all modification disapear in case of har reset).
Lost of questions... :?:
Regards,
Thierry
To easy patch any ROM... folow this link ;-)
http://forum.xda-developers.com/viewtopic.php?t=22582
I am not sure it's in the registry as I did a byte compare of my backed up ROM (which was the 1.11 NA 850MHz from i-mate) to Anansky's (1.11 WWE) and found that the there were two sets of bytes that were different (changed?) in the bootloader area as well as the CE ROM, and of course, the 27MB chunk of data for the Extended ROM.
I think the bootloader may have something to do with the way the memory is set up.
The bytes that were different were in both places were B8 01 vs 80 00. 1B8h=440 and 80h=128, if that means anything. There were no other changes in the Radio or CE ROM areas, which leads me to believe that the 27MB area is just formatted differently (perhaps the start of the 7MB area was pulled back to the beginning of the Extended ROM area).
The only remaining change was near the end where it has the "PM10x" designation," but I doubt that has anything to do with the BigStorage area since I used his bytes and tried my bytes with no difference.
If you feel bold enough, you can mess with these two bytes (try a value in between) to see if it enlarges the 7MB storage space, corrupts it, makes it writable, etc.
pigot,
If you're willing to try this...
After you've injected your French ROM into the NB1 file, use a hex editor and change the following bytes:
On or around 00007E32h, change B8 01 to 80 00.
Do the same at 0211E32Eh, change B8 01 to 80 00.
Leave Anansky's changes in the Extended ROM and Storage area as well as the end of the file unless you want to call your device a PM10x.
SD-Flash it and tell me if you have the 27MB of Storage free with your French OS.
You are in the good way :lol: ... Those bytes (hB8 + h01 to h80 + h00) are the key. But not always they are in the same site in all the ROM's.
Bye. 8)
Seems to work great for me over the last couple of minutes at least! Upgraded a 3 day old UK o2 qtek s100.
Thanks a million.
BTW - what software is stored in the extended rom that we lose?
Vijay
MKS said:
You are in the good way :lol: ... Those bytes (hB8 + h01 to h80 + h00) are the key. But not always they are in the same site in all the ROM's.
Bye. 8)
Click to expand...
Click to collapse
Well, the application developped by MKS is a great job. It works perfectly for me on a v1.11 Fr... The process is very simple, and really accessible to even 'medium range' users. Sounds pretty good, isn't it?
Omho, the 'anansky trial' is over, and the big winner is MKS.
Thanks alot,
Thierry
So i was looking around and came across a Chinese site that compared a few different ROMS for the G tablet/Zpad.
But unfortunately I cannot post the links yet, because of antispamming rules and the number of posts that I have put up.
I am going to post a few times here and then post the links as there is one ROM that may prove to be very beneficial to people who are more inclined in cooking roms than I am.
If you do a Google search for "malata zpad firmware"
One of the results will look like:
Malata Zpad ( updated Dec. 3,2010)(頁 1) - 平板電腦 - 電腦領域 ...
Malata Zpad ( updated Dec. 3,2010). [i=s] 本帖最後由 pcmtse 於 2010-12-3 18:25 ..... 1, 2010 firmware. This UI really not showing what the hardware can do.
This site when translated provides soem very interesting information, including a ROM called Big_Ideas
I placed the URL for that site into translate google com and chose Chinese to English. And it has a nice review of of a few different ROMs for this device, including Vegan ROM.
What Caught my Eye was one I had never heard of called Big_Ideas:
"Big_Ideas' s ROM first released on Dec, 14, and updated again o Dec. 22. It's done by Xiao1u in the QQ group from China.
This is currently the fastest ROM on the Tegra 250 platform. The score on Neocore and Gl benchmark said it all. If you look at the benchmark result on GLbenckmark webpage, all the top rating machine run this ROM, in fact they are from the same QQ group. This is a pure Android 2.2 ROM without any additive, give you the best compatibility and speed combination.
A new kernel just released that support CIFS, so that you can mapped a network drive and let media files play over the network. NTFS read support also added to this kernel. This is the first kernel, for the Tegra platform, which can do this."
When you go to the site which has a link to download the Big_Ideas ROM (81MB by the way)
they list out a bunch of stuff that is pretty much meaningless to me but my be helpful to others here, so I am going to post it.
GLBenchmark Pro 2.0 Result Details
GLBenchmark 2.0 Egypt: 2338 Frames (20.7 Fps)
GLBenchmark 2.0 PRO: 2220 Frames (44.4 Fps)
OpenGL ES Environment Variables
GL_VENDOR
NVIDIA Corporation
GL_VERSION
OpenGL ES 2.0
GL_RENDERER
NVIDIA Tegra
GL_EXTENSIONS
GL_NV_platform_binary GL_OES_rgb8_rgba8 GL_OES_fbo_render_mipmap GL_NV_depth_nonlinear GL_NV_draw_path GL_OES_EGL_image GL_OES_vertex_half_float GL_NV_framebuffer_vertex_attrib_array GL_NV_coverage_sample GL_OES_mapbuffer GL_ARB_draw_buffers GL_EXT_Cg_shader GL_EXT_packed_float GL_OES_texture_half_float GL_OES_texture_float GL_EXT_texture_array GL_OES_compressed_ETC1_RGB8_texture GL_EXT_texture_compression_latc GL_EXT_texture_compression_dxt1 GL_EXT_texture_compression_s3tc GL_EXT_texture_filter_anisotropic GL_NV_get_tex_image GL_NV_read_buffer GL_NV_shader_framebuffer_fetch GL_NV_fbo_color_attachments GL_EXT_bgra GL_EXT_texture_format_BGRA8888 GL_EXT_unpack_subimage
GL_RED_BITS
5
GL_GREEN_BITS
6
GL_BLUE_BITS
5
GL_ALPHA_BITS
0
GL_DEPTH_BITS
16
GL_STENCIL_BITS
0
GL_MAX_LIGHTS
0
GL_IMPLEMENTATION_COLOR_READ_FORMAT_OES
2048
GL_IMPLEMENTATION_COLOR_READ_TYPE_OES
9
GL_MAX_CLIP_PLANES
5
GL_MAX_TEXTURE_SIZE
2048
GL_MAX_VIEWPORT_WIDTH
3839
GL_MAX_VIEWPORT_HEIGHT
3839
GL_NUM_COMPRESSED_TEXTURE_FORMATS
9
GL_ALIASED_LINE_WIDTH_MIN
1
GL_ALIASED_LINE_WIDTH_MAX
256
GL_ALIASED_POINT_SIZE_MIN
1
GL_ALIASED_POINT_SIZE_MAX
256
GL_SMOOTH_LINE_WIDTH_MIN
3839
GL_SMOOTH_LINE_WIDTH_MAX
3839
EGL Native Platform Graphics Interface
EGL Vendor
Android
EGL Version
1.4 Android META-EGL
EGL Extensions
EGL_KHR_image EGL_KHR_image_base EGL_KHR_image_pixmap EGL_KHR_gl_texture_2D_image EGL_KHR_gl_texture_cubemap_image EGL_KHR_gl_renderbuffer_image EGL_ANDROID_image_native_buffer EGL_ANDROID_swap_rectangle EGL_ANDROID_get_render_buffer
EGL Selected Configuration
EGL_CONFIG_ID: 25
EGL_BUFFER_SIZE: 16
EGL_ALPHA_SIZE: 0
EGL_BLUE_SIZE: 5
EGL_GREEN_SIZE: 6
EGL_RED_SIZE: 5
EGL_DEPTH_SIZE: 16
EGL_STENCIL_SIZE: 0
EGL_CONFIG_CAVEAT: 12344
EGL_LEVEL: 0
EGL_MAX_PBUFFER_HEIGHT: 2048
EGL_MAX_PBUFFER_PIXELS: 4194304
EGL_MAX_PBUFFER_WIDTH: 2048
EGL_NATIVE_RENDERABLE: 0
EGL_NATIVE_VISUAL_ID: 0
EGL_NATIVE_VISUAL_TYPE: 0
EGL_SAMPLES: 0
EGL_SAMPLE_BUFFERS: 0
EGL_SURFACE_TYPE: 1127
EGL_TRANSPARENT_TYPE: 12344
EGL_TRANSPARENT_BLUE_VALUE: 0
EGL_TRANSPARENT_GREEN_VALUE: 0
EGL_TRANSPARENT_RED_VALUE: 0
Device Information
android.os.Build.BOARD
harmony
android.os.Build.BRAND
nvidia
android.os.Build.DEVICE
harmony
android.os.Build.FINGERPRINT
google / passion / pasion / mahimahi: 2.2/FRF91/43546: user / release-keys
android.os.Build.HOST
tablet-server
android.os.Build.MODEL
harmony
android.os.Build.PRODUCT
harmony
android.os.Build.TAGS
test-keys
android.os.Build.TIME
1292987773000
android.os.Build.TYPE
eng
android.os.Build.USER
navy
android.os.Build.VERSION.INCREMENTAL
20101222.111543
android.os.Build.VERSION.RELEASE
2.2
android.os.Build.VERSION.SDK
8
android.os.Build.DISPLAY
harmony-eng 2.2 FRF91 20101222.111543 test-keys
OS
Android
Screen size
1024 x 600
The page that lists all the above also states the following:
Wire brush package, integrated CM Recovery 2.5.1.3
u 115 com/file/f11c0c1570 <-- Link to page to download files just add the . in between the u & 115 & com
Firmware in the absence of a library libHWColorPen.so, handwriting input method does not result in handwriting.
Download this file with root explorer copy to / system / lib / can be.
If you click the link on that page it takes you to a page titled:
Big_ideas1222 (original pure version). Rar
near the bottom there are 3 links
they are easy to miss, the first link is "Unicom 1 download"
the second is "1 download telecom"
the third is "backup download"
Clicking any of those will get you an 80 meg rar file which contains img files and other various bits.
No very usefule to me as I have no idea what to do with them to make them usable but someone else will be able to i'm sure.
I have tried all three and the "1 download telecom" link is the fastest but none of them are blazing fast. I am going to put the file up on megaupload if anyone is interested.
I figured the more options that we have or different sources for ideas and files the better everything will be in the long run
There is a link to the original Zpad firmwares as well, but the CIFS and NTFS read functions of the Big_Ideas ROM caught my eye.
It appears that they have higher builds of the zpad firmware (1125) than i have seen so that may be helpfuill as well
I have had this rom and am working on a zpad clean version of it.
I have been following this work and have been releasing english friendly versions as zpad clean releases. Currently there are mounting problems when using a gtab compatible boot.img.
If you apply bigideas as a nvflash, it will change your partition layout.
Also I have a kernel I compiled with cifs support available in this forum that works for tnt or vegan.
http://forum.xda-developers.com/showthread.php?t=889088
Ahh ok.
I hadn't seen anything else about it so I figured I would try to be helpful.
Since You already know about it, I'll drop it. Thanks~
Is the zpad Clean 2.x based off of this ?
robrowald said:
Ahh ok.
I hadn't seen anything else about it so I figured I would try to be helpful.
Since You already know about it, I'll drop it. Thanks~
Is the zpad Clean 2.x based off of this ?
Click to expand...
Click to collapse
2.x is off of 1125, which was the old partition layout, identical to ours.
Big Ideas is a ROM that i think is based off of 1202 or something but has a lot of the stock nvidia image layered on. However since 1125, TnT and Zpad have moved in separate directions, which makes it harder to convert it over.
TnT boot.img + big ideas system.img will result in BT, Wifi, mounting not working.
Currently I have wifi and BT not working, but am working on the sdcard mounting. When I get it working I'll set it up with all the gingerbread visual stuff and post a link to it. Hopefully I can get something working sometime tonight or tomorrow.
rothnic said:
I have had this rom and am working on a zpad clean version of it.
I have been following this work and have been releasing english friendly versions as zpad clean releases. Currently there are mounting problems when using a gtab compatible boot.img.
If you apply bigideas as a nvflash, it will change your partition layout.
Also I have a kernel I compiled with cifs support available in this forum that works for tnt or vegan.
http://forum.xda-developers.com/showthread.php?t=889088
Click to expand...
Click to collapse
My Malata Zpad is on it's way. Which Kernel and Roms should I use? The ones you made or the Big_ideas1222 ones? Would the chinese ones work better with the 1GB ram version of the Zpad? Is there a lot of chinese in there?
I've read through your Zpad thread, really cool stuff you're doing
Hello, i has been reading the thread trying to find how to flash the big_ideas ROM but i doesnt see where is it, would please someone let me know how can i flash my Zpad Malata T2 please? ^^ i just recived today but its really bad the KErnel ive got :O thanks in advance!
zerranoss said:
Hello, i has been reading the thread trying to find how to flash the big_ideas ROM but i doesnt see where is it, would please someone let me know how can i flash my Zpad Malata T2 please? ^^ i just recived today but its really bad the KErnel ive got :O thanks in advance!
Click to expand...
Click to collapse
I would imagine that it would be the same/similar procedure as flashing the G-Tablet.
Install ClockworkMod -> backup -> install a ROM -> Flash Player -> and the Market Fix
but instead use the big_deas rom.
I'm a noob, so this will have to be confirmed before you try it.
Oh. BTW, that guide in the link is not mine, just in case I gave the wrong idea.
Also here is another Zpad specific thread that might help by 2manytoys.
Ive installed tnt_lite_v2_2 without problem, but im trying to install Big_Ideas and its impossible, i dunno how to do it, the internal structure of compressed archive is very different of tnt_lite_v2_2.zip and its another point because the big_ideas its.rar...
Im short in ideas and im trying to get how to do it on threads but i cant find it T_T
zerranoss said:
big_ideas its.rar...
Click to expand...
Click to collapse
What's inside the .rar?
Is there not a .zip inside?
Hi, in this page:
http://sbf.droid-developers.org/phone.php?device=14
I've seen new firmware files being uploaded. For example, the US retail version, but the only difference in the information is "svc" in the file name:
US_retail_XT1032_KXB20.9-1.8-1.4_CFC.xml.zip
vs.
US_retail_XT1032_KXB20.9-1.8-1.4_CFC_svc.xml.zip
What does SVC mean? What is the difference between those two firmware?
Thank you!
tiazek said:
Hi, in this page:
http://sbf.droid-developers.org/phone.php?device=14
I've seen new firmware files being uploaded. For example, the US retail version, but the only difference in the information is "svc" in the file name:
US_retail_XT1032_KXB20.9-1.8-1.4_CFC.xml.zip
vs.
US_retail_XT1032_KXB20.9-1.8-1.4_CFC_svc.xml.zip
What does SVC mean? What is the difference between those two firmware?
Thank you!
Click to expand...
Click to collapse
I'd like to know as well.
When I searched for it, Google points me right back to this thread.
It's sorta of typical of what I've seen with other threads and other devices. A bunch of files are listed, with NO information on what it is, what it does, what the various versions are, etc.
One is "Android 4.4.2, Blur_Version.172.44.4.falcon_umts.Retail.en.US"
One is "Android 4.4.2, Blur_Version.172.44.4.falcon_umts.Retail.en.US" ~SVC~ version!
It looks like the MD5 hashes of the files inside the ZIP files are identical, yet the size of the ZIP files are different. The non-SVC version is buried an additional folder deeper than the SVC version.
BitingChaos said:
I'd like to know as well.
When I searched for it, Google points me right back to this thread.
It's sorta of typical of what I've seen with other threads and other devices. A bunch of files are listed, with NO information on what it is, what it does, what the various versions are, etc.
One is "Android 4.4.2, Blur_Version.172.44.4.falcon_umts.Retail.en.US"
One is "Android 4.4.2, Blur_Version.172.44.4.falcon_umts.Retail.en.US" ~SVC~ version!
It looks like the MD5 hashes of the files inside the ZIP files are identical, yet the size of the ZIP files are different. The non-SVC version is buried an additional folder deeper than the SVC version.
Click to expand...
Click to collapse
Did you guys find out what the SVC means?
To be fair, these files are not intended for End Users; that's why there is no documentation. Mainly it would be 'Carrier' Engineers who access them. At a guess, SVC relates to data storage and distribution - the way these files are stored and served to external entities by Motorola. The difference in file-size is probably down to compression method.
http://www-03.ibm.com/systems/storage/software/virtualization/svc/
Hi!
Did anyone figured it out?
Hello every 1.
I need information any kind now.
I'm stuck and walking in circles.
My device isn't best wit support but it's the 1st one I'm trying to repair and spend too much time to leave it unfinished
My device: Huawei G740-L00 (not youmo)
My problem:
I'w updated from B176(NEEU) to B178(WEU)
I remember I used force upgrade, didn't know about regions
(because few months ago I had no idea what is ROM, nor recovery, ??bootloader?wtf is boot?? ) -total-noob-
Result:
Sure-->GSM, LTE, WCDMA - LOST. Wi-fi & gps - OK.
Standard upgrades dload/update.app - fails
B178 (NEEU) version doesn't exist
Impossible downgrade, stock device
I can only upgrade the same update.app B178(WEU) & ofc it doesn't change anything.
extra: (still not sure what to do with this info)
-DCunlocker: shows version B165. maybe it was my stock ROM and I did upgrades B165>B1xx>B178, else B165>B178
& my original S/N
-Phone shows B178 & wrong S/N
So that is done:
-Rooted
-Unlocked Bootloader(DC-unlocker was best solution after all huawey supports)
-Flashed CWM recovery
Solutions in progress:
1. Easiest would be to get update.zip with original firmware. Install via cwm and then upgrade via sdcard to version for my region(NEEU).
///Didn't find any, so skipped after few days.
2.Extract firmware region. I need: update.app-->Use something like: split_uppdata(or HuaweiUpdateExtractor-if it's not for MTK?? My device Qualcom based )to get .iso files and try luck to flash with ADB etc. (if possible)
/somehow it doesn't look like good idea, I think there r many missing files after extracting and i have no idea what exactly I need. So:
2.1.Use Ext4imgUnpacker on .iso files extracted-> to validate ?somehow? what files r missing in boot,system,cust,recovery etc...
--------Here I stopped----------
///It seemed something wrong at all, even if I can check what files r missing and if I really need it, I can't repack (?solutions?)
3.Flash something like radio.iso(modem) from original firmware I need. Does it have to do something with RIL files?
I was digging deeper & deeper & surfing all the web about anything what can help me & I found samsung guide how to create .iso using odin
http://forum.xda-developers.com/showthread.php?t=1777579
then searching something like that on my device I found shortcuts:
---->/dev/block/platform/msm_sdcc.1/by-name
modem (?maybe CDMA MODEM)
/dev/block/mmcblk0p13
modemst1 (?maybe LTE_MODEM)
/dev/block/mmcblk0p10
modemst2 (?maybe LTE_MODEM2)
/dev/block/mmcblk0p11
Maybe it would be enough 4 me?
BUT I have:
+Terminal
+Cygwin
-Huawei doesn't have Odin.
-------Here I stopped again-------
I really need to find people with my device. But I think any advanced android user can help me. Most of old users of G740 doesn't seem like to use it anymore. 4 me it's my 1st android repair. I must repair it, because like I said 2 months ago I didn't know what is ROM, and spent too much time researching this all.
Any info might help:good: