Database Info

[Q] Flash A Custom ROM : P3100 : Specific Issue - Fastboot Not Supported

I have made a custom ROM, with additional API's and patches using stock ICS source - Downloaded from source.android.com.
After modifying, patching etc, I built the ROM using 'make' on my Ubuntu machine.
I followed the steps here to build the ROM: http://source.android.com/source/building.html
The output of this procedure is attached as a screenshot
(I copied the folder to windows hence the screenshot shows a windows OS)
Now I have a ROM I am asked to flash it using'fastboot flashall' per the instruction here:
http://source.android.com/source/building-devices.html
My device doesn't seem to support a Fastboot mode.
The output folder of the ROM is attached as a screenshot.
A> When I try to use CWM, it fails to flash - MD5 Mismatch:
Also I am unsure how CWM flashes and which of the folders are to be included. A CWM recovery generates:
1. boot.img
2. recovery.img
3. system.ext4.tar
4. data.ext4.tar
5. cache.ext4.tar
6. nandroid.md5
Clearly my output folder is not aligned to this format. So I'm a bit lost here.
B> Odin takes on tar file. I am not sure if simply making the folder a tar will work.
C> Heimdall doesnt support this tab I guess...
Any ideas on a solution would be appreciated.
Thanks & Regards
Indrajit

Downloaded & Installed a custom ROM zip, it worked. How can I make mine into a zip?
Most of the custom ROMs have a boot.img, system folder, data folder and meta-inf.
What is Meta-Inf?
Also If I zip my ROM (created as mentioned above) and try installing it doesnt since I dont have a Meta-Inf & I cant use the other meta-inf.
This is the ROM I installed: Worked fine except USB-PC connection didnt:
http://forum.xda-developers.com/showthread.php?t=1643736
Any ideas / suggestions would be highly useful & appreciated.
Thanks in advance.

[FIX]Repair White Screen, Bootloop, Soft Brick etc. the quick & dirty way

Most guides suggest reflashing stock rom for this, however that means you would have to re-root your device and also install a new recovery again. Any other data on your system will get lost as well.
I had a white screen problem with my SGA+ and according to a post about Indian and Chinese SGA+ phones, I needed to flash a European stock rom first before I was able to use certain roms (e.g. kk) at all. Because of various reasons Odin was not an option, so I had to use heimdall. With heimdall all partitions are flashed in sequence and you can choose which ones you want to flash. In other words, you can flash a partial stock without touching anything that would be flashed by your custom rom anyway.
Tested with a Chinese SGA+
This will flash all partitions that are not affected by custom roms and rooting.
Requirements:
heimdall --- (google for it. XDA's spam filter prevented me from posting the link, lol)
stock rom --- If your phone is an Indian or Chinese SGA+, choose an S7500XX rom. Mine was S7500XXNB1_S7500OXXNA1_XSK. Getting a relatively new rom is also not a bad idea.
zip, tar capable archive manager
Tutorial:
1. Unzip your stock rom.
2. Rename the xx.tar.md5 file to xx.tar.
3. Untar / extract the tar file.
4. Open a terminal and move to the extracted directory.
5. Put your SGA+ in download mode (turn your phone off and boot with Power+Volume down+Home pressed).
6. Connect your USB cable.
7. Check your partitions with heimdall (as root on Linux systems)
Code:
heimdall print-pit
This step should be optional, but it's always good to be on the safe side. Check if the partition names and image names correspond with the following table:
Code:
[B]partition[/B] [B]image[/B]
HIDDEN hidden.img.ext4
APPSBL appsbl
OEMSBL oemsbl
QCSBL qcsbl.mbn
CFG_DATA qcsblhd_cfgdata.mbn
8. Flash all five partitions with heimdall (as root on Linux systems)
Code:
heimdall flash --HIDDEN hidden.img.ext4 --APPSBL appsbl --OEMSBL oemsbl --QCSBL qcsbl.mbn --CFG_DATA qcsblhd_cfgdata.mbn
9. Re-flash your custom rom if necessary.

[GUIDE][I9500] Complete guide on installing and using 8GB/11GB PIT files

WARNING!
I'm not responsible for anything that happens to your device after using this guide
Use at your own risk!​
CREDITS to @lch920619x for the original guide, @aboodyaiman for teaching me how to convert the ROM in the first place. This small guide is simply a newer one with updated links and steps on converting ROMs to work with 11GB pit. I'll add images when I have time yay
You will need THIS PACKAGE for converting between 8GB and 11GB pits, THIS PACKAGE for converting the ROMs you want to work with 11GB pit.
If you haven't download Odin yet then here is ODIN 3.12.3 ( you will need it to convert PIT between 8GB & 11GB
Installing the PIT files
1. Download the PIT Package
2. Flash pit your desired pit (PIT)
<8GB.pit to convert to the standard 8GB data partion - RECOMMENDED>
<11GB.pit to convert to the 11GB data partition>
3. Flash CF-Auto-Root (AP)
4. Wipe Cache & Data in stock recovery.
5. Flash modem (AP)
6. Flash param.bin (CP)
7. Flash custom recovery (AP)
8. Format all partitions using TWRP
9. Optional: Update to latest TWRP if you wish
Converting ROMs to work with 11GB pit
<Haven't test on Alberto's Lineage since I don't have the device anymore, REMEMBER that Alberto said he is NOT supporting 11GB pit for now>
1. Head to Python website, download and install Python
2. Download ROM CONVERT PACKAGE and extract it anywhere
3. Extract File context, system.new.dat and system.transfer.list from the ROM zip you want to convert in to where you extract the ROM CONVERT PACKAGE
4. Execute extractor and press 1, then press Enter three times
5. It will provide system folder when it's done
6. Extract boot.img, meta folder and file context from the original ROM zip again.
7. Replace updater-script with the one in the ROM COVERT PACKAGE
8. Add all to zip archive and flash your new 11GB pit compatible ROM

sry i am a newbee for packing and unpacking rom. I want to flash ALE95 n5 7.1. but since it doesnt supports 11gb pit. i am giving a try.
1. i downloaded and install python 2.x.x
2. now i am stuck at how to extract file context, system.new.dat, system.transfer.list from ALE95.
i googled much, i downloaded filecontext tools, system.extractor.win, rom convert package all. but how to use python and extract those files and repacking i duuno. i did bit of research in google also.. but need some guidance please

can you make video review about how to convert roms from 8 gb to 11gb

Insert ROM in PDA file

I have a problem. I am new in the domain of android customization and that is why I am testing.
I have a PDA file for my old GT-S6102 Galaxy Y, which contains the following files:
boot.img
param.lfs
Sbl.bin
system.img
userdata.img
I also downloaded a custom ROM from the internet called evo_x2.1 (evo_x2.1.zip) which contains the following files:
META-INF (folder)
system (folder)
installbusybox (file)
Normaly this file is supposed to be put on /sdcard and update the system partition only from recovery mode.
But I have a question: Can I edit my PDA file mentioned above by inserting this ROM in it? (so that when I flash this firmware with odin into my phone I will no longer have to update it with this ROM separately afterwards, manually)
I tried to create a system.img which contained the files included in the ROM file and replaced the system.img in the PDA file with the system.img I just created from the ROM file.But when I try to flash the PDA with Odin, it crashes while analyzing the file.
NOTE: there is no md5 hashsum at the end of the PDA so there is no problem concerning the integrity of the file.
Thank you, and any observations are welcomed.

ReznicencuBogdan said:
I have a problem. I am new in the domain of android customization and that is why I am testing. I have a PDA file for my old GT-S6102 Galaxy Y,........
Click to expand...
Click to collapse
I don't have this device but, the following area of the forum is also specific to your device as well.
https://forum.xda-developers.com/galaxy-y
With that guidance...
Your best bet is to post this question within the following Q&A thread that's specific to your device and variants.
https://forum.xda-developers.com/showthread.php?t=2063534
Good Luck!
~~~~~~~~~~~~~~~
I DO NOT provide support via PM unless asked/requested by myself. PLEASE keep it in the threads where everyone can share.

ReznicencuBogdan said:
I have a problem. I am new in the domain of android customization and that is why I am testing.
I have a PDA file for my old GT-S6102 Galaxy Y, which contains the following files:
boot.img
param.lfs
Sbl.bin
system.img
userdata.img
I also downloaded a custom ROM from the internet called evo_x2.1 (evo_x2.1.zip) which contains the following files:
META-INF (folder)
system (folder)
installbusybox (file)
Normaly this file is supposed to be put on /sdcard and update the system partition only from recovery mode.
But I have a question: Can I edit my PDA file mentioned above by inserting this ROM in it? (so that when I flash this firmware with odin into my phone I will no longer have to update it with this ROM separately afterwards, manually)
I tried to create a system.img which contained the files included in the ROM file and replaced the system.img in the PDA file with the system.img I just created from the ROM file.But when I try to flash the PDA with Odin, it crashes while analyzing the file.
NOTE: there is no md5 hashsum at the end of the PDA so there is no problem concerning the integrity of the file.
Thank you, and any observations are welcomed.
Click to expand...
Click to collapse
It doesn't quite work like that, you can create your own Odin flashable file(.tar.md5) containing the custom ROM, but it isn't as simple as just pasting the system.img into the .tar.md5.
Here are some threads for extracting Odin files and for creating your own .tar.md5 using the custom ROM file.
This thread is for correctly extracting the existing .tar.md5:
https://www.rwilco12.com/forum/showthread.php?tid=74
This thread is for creating your own Odin flashable .tar or .tar.md5:
https://www.rwilco12.com/forum/showthread.php?tid=92
Sent from my LGL84VL using Tapatalk

(GUIDE) - How to make rooted stock firmware to update rooted device whilst keeping data

Hi All
Please see steps below to make stock rooted firmware for flashing in odin:
1 unpack stock odin firmware for your update
2 copy AP file to tablet and patch with magisk - copy the resulting "magisk_patched.tar" to your firmware folder when patching finishes
3 get your TWRP file of choice and load it onto this website https://cruelkernel.org/tools/bootimg/ - patch it to the date matching your firmware's security patch date - March 2021 in the case of CUB7 (I HAVE BEEN USING THE 3.13 TWRP BY MENTALMUSO QUITE HAPPILY SINCE SEPTEMBER LAST YEAR)
4 Open magisk_patched.tar with 7zip and delete recovery.img.lz4. You then need to rename the TWRP file you date patched "recovery.img"
5 Drop this recovery.img into the magisk_patched.tar you have opened with 7zip
6 extract the vbmeta.img in magisk_patched.tar and set this aside
7 extract the BL file to a folder, delete the vbmeta.img.lz4 which is there and replace that with the vbmeta.img from Magisk_patched.tar from step 6
8 re-zip the bl folder using 7zip.
you now have the stock rooted odin files you can flash in odin for a seamless and data safe update!
TO UPDATE DEVICE WHEN YOUR FILES ARE MADE:
1 reboot to download mode
2 load Magisk_patched.tar in AP, BL in BL, CP in CP (T865 only) and HOMECSC in CSC slot and flash these with Auto reboot off in odin
3 Press vol down and power to exit download and then press and hold vol up and power until you are in TWRP
4 Flash the Multidisabler 3.1 from @ianmacd here
5 reboot your updated device to system!!!