Q&A for Boot/Recovery repack utils for WINDOWS
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for Boot/Recovery repack utils for WINDOWS. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Recovery Unpack issue
@michfood , i've tried with all versions of your tool the first an v2 version give a sintaxys error, the v3 give "done" but al of my folders are empty, i need to edit the build.prop because my recovery is upside down ( it works but i dislike the upside down issue)
thanks in advance
PD.: i use a W7 utimate pc for unpack, ive tried from the desktop, cmd in administrator mode, from the C:/ directory but my folders are only empty after unpack, another files like rmdisk.tar and other is present but nothing in the rmdisk internal folders
all fine, but it's not unpack & pack my MTK system.img file :/
Hi @michfood,
I did unpack boot.img successfully but for editing ramdisk, but in the extracted folder there is an empty ramdisk zip and a ramdisk file...so how do i do the ramdisk editing??
custom Recovery for Tab 4
ok so I have been doing some lots of research of late into rom building, recoveries etc . I noticed there is only a TWRP recovery for Galaxy Tab 4. I want to know is the any of the guides on porting recoveries may help me build a CWM recovery for galaxy tab 4 coz most of them look like limited to MTK devices. If its possible kindly suggest a perfect start.
No problem with the OS to use am ok with any ie. Windows or linux or cygwin.
thanks
Related
I have been trying to unpack the atrix system.img file from the stock gingerbread 4.5.91 build, but I can't seem to get it to work. I keep getting an error about a segmentation fault. I have tried it on linux (ubuntu), OSX and windows. Linux and OSX give me a segmentation fault using unyaffs. Windows just gives me a stack file. If anyone knows how to unpack and repack the atrix .img files in either three of the operating systems I would appreciate the help.
Read the forum rules, questions do not belong in this section of the forum - thats what the Q&A section is for. Mr. Clown, please move or delete this thread..
I have been attempting to apply a work around from tjayz thread for restoring recovery. In the CWD folder we are supposed to search for 5) Navigate to clockworkmod/download/download.clockworkmod.com/recoveries/
There you will see some two files - recovery-clockwork-4.0.0.4-p7100.img and recovery-clockwork-4.0.0.3-p7100.img
I only see files with names like -2110140792 and -21108160.
Does anyone know if you can rename these files as described in his post?
Thanks
Please use the Q&A Forum for questions Thanks
Moving to Q&A
Q&A for [GUIDE][MTK][EASY]Fix invalid IMEI
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [GUIDE][MTK][EASY]Fix invalid IMEI. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
umangleekha said:
Many of you might be getting INVALID IMEI after flashing any custom rom or full dump with sp, this guide will make a flashable zip of your imei which you can flash on any ROM after you see INVALID IMEI, make sure that you flash the zip after completing your 1st boot and not directly after rom, there are other reliable methods of restoring imei but this one is a very easy and quick method, keep the zip on your sdcard and flash whenever you get invalid imei
Instructions-
1.Be patient and it will fix your imei, read all steps till #14
2.Download the IMEI_WINDOWS.zip from below
3.Extract the contents to an easy location on PC (prefer C drive)
4.Open command promp and cd to the IMEI_WINDOWS folder
5.Now type "imei.exe 123456789111111 123456789111111" without quotes
6.Just replace both the 15 digit numbers with your IMEI 1 and IMEI 2 respectively
7.Now a file named "MP0B_001_NEW" will be generated in your IMEI_WINDOWS folder
8.Just rename it to "MP0B_001"
9.Now download the IMEI_FLASHABE.zip from below
10.Extract this zip and go to "/data/nvram/md/NVRAM/NVD_IMEI/"
11.Delete the placehere file and paste your "MP0B_001" file here
12.Now zip the META-INF and data folder and flash it with recovery :good:
13.You have to flash this after you see imei error on your 1st boot
14.Don't flash directly after the ROM, just do your first boot then flash it :fingers-crossed:
Click to expand...
Click to collapse
Can you please tell me how to flash as mentioned in Step 12 ? If you can add a screenshot of that it will be good.
I'm having Xolo Q3000 and i had used the stock ROM "Xolo Q3000 KK S007 27-05-2014"
Both my IMEI is missing and i cant use the phone now
Please help.
Thank you in advance
thanks (Y)
worked for me. thanks umangleekha for this
Dear Admins,
Could we get a forum setup for the Cube U27GT WiFi version? I dug around on the site a bit beforehand but didn't see one, I apologize if I missed it and please direct me there if I did.
I have this tablet and I am doing some initial basic firmware development for it and want a proper place to start putting threads.
Dear Dev Community,
I can't root this bloody thing... At least, not the rom itself. Let me explain...
I can flash the stock rom from Cube and that can be rooted using Kango Root. --Fine...
However, I can't figure out how to replicate this when I make my own rom.
Thus far, here is what I have attempted...
1. Setup dsixda's excellent kitchen on my Ubuntu workstation.
2. Unpack the rom, clean things up, manually put the boot image into the dsixda unpacked working rom folder, run dsixda's root functionality (which add SU binary to xbin and SuperSu apk file to app folder as well as do some things with the boot image file).
3. Rather than using repack with Dsixda (which makes an update.zip image which I can't use because the stock recovery environment on this device can't flash zip update files and I can't for the life of me figure out how to get and or make a working CWM or TWRP recovery image for this unit)...
4. What I do is I run commands in linux to unpack the stock rom to another directory and mount that directory, then clear out a bunch of folders and then manually copy in my files from dsixda's working folder, then repackage up my unpacked stock rom into a new system.img file.
5. Then copy my now modified boot image, system image, and also userdata image (I modify that as well as that is where most all of the chinese bloatware is loaded from) to my SP_Flash_Tool, generate new checksum.ini file and flash normally...
What I get as a result...
1. As long as I am really careful with how I copy files into my new image, the new system flashes okay (if I am not careful, after flash USB storage for some reason has a format error and the system will boot but can't mount USB storage and other odd issues ensue as a result).
2. Assuming everything flashes okay, and no issue with USB storage partition, I have SuperSU installed and when I go to use an app (ES File Explorer or Root Checker) that require's root, I do get the prompt. However none of the root functions actually work and Root Checker tells me I am not rooted.
That is as far as I have got. So as a result, I have a really nice, westernized, cleaned up rom but with no root.
Anyone have any ideas?
This is my first adventure into mod'ing MTK roms so I am sure I am doing all kinds of things wrong . I had a good bit of experience on Rockchip SoC's before this though.
Kind regards and thanks in advance!
Roman
Figured it out!
So I finally did the following rather hackish work-around...
1. Flash stock firmware...
2. Root with Kingo Root
3. Enabled ADB
4. Attach to PC and fire up MTK Droid Tools
5. Take a full backup
6. Modify the system image from the backup and make changes
7. Put that in new firmware flash package
8. Flash new firmware
YAY - Cleaned up rom, modified, with root!
Once I get it all packaged up and uploaded to mtkfirmware.com I will post a link for anyone that wants a cleaned up rom with root!
The only downfall of the above method is that it absolutely requires that the developer have a device on hand because you can't just root the stock image file (at least, I couldn't figure out how... - bleh...
Kind Regards,
Roman
Dear roman,
Thanks for your hard work.
I have a simple question (I think) and if you have the time to reply or -any other android guru- I would be thankful.
My later issue was with a U27GT cube tablet, but I have others, one for each kid, and this is more of general question.
I am reading this and other forums about how to flash tablets from PC. My question is:
Can the flashing process be done from a SD card?
Thanks a lot and regards,
Fernando
SKorea
Hi everyone, I hope you're doing great
So, I'm currently trying to debloat some XOS ROMs which is Infinix's official firmware.
I have a problem repacking product.img since it doesn't have file_contexts which is required by the tools that repack .img files
IJoseph23 said:
Hi everyone, I hope you're doing great
So, I'm currently trying to debloat some XOS ROMs which is Infinix's official firmware.
I have a problem repacking product.img since it doesn't have file_contexts which is required by the tools that repack .img files
Click to expand...
Click to collapse
Hello and good afternoon, @IJoseph23
Welcome to XDA! I hope you'll always get the support you require.
However, prior to your next posting please read the guidances that are stuck on top of every forum like
Note: Questions go in Q&A Forum
If you are posting a Question Thread post it in the Q&A forum. Technical discussion of Android development and hacking. No noobs, please. Device-specific releases should go under the appropriate device forum...
forum.xda-developers.com
and the others. I've moved your thread to Android Q&A.
Thanks for your cooperation!
Regards
Oswald Boelcke
Senior Moderator
these kind of img files are partition images of linux file systems, sometimes sparsed with simg2img to reduce file size.
usually, partition images can mounted in linux only, same as partitions. windows is not capable of mounting linux file systems natively.
"extracting" linux images on windows is just some nasty hack and not intended for "repacking", because windows file system (NTFS) cannot handle linux file names and its metadata (like permissions, uid/gid, secontext)
the proper way is to mount (EXT4) partition image on linux, delete files, and unmount it.
additionally it might need img2simg/simg2img (not for dynamic partitions on super partition)