Just wanted to share this method of changing your boot splash image without using hboot,rather a flashable zip.
I am not responsible for damaging your phone.
Lets begin...
What you need/should have before we start..
Using your favorite image editing program take your desired image and make it 480w x800h and save it to your desktop as splash1.bmp(24 bit color bitmap).
NBIMG.exe is used to convert your BMP image into the proper format
-Windows
-Linux
-[Refrence]
(7zip or Winzip)
This zip is required for the last steps
-splash1.zip
1.Make sure desired splash1.bmp is on desktop
2.Extract nbimg.exe to desktop
3.HOLD SHIFT, right click on desktop and open command prompt
4.Type nbimg.exe,this will give you the options
5.At the top of the command window you will see the path needed to convert
6.Simply just add splash1.bmp to that path(nbimg -F splash1.bmp)
7.Once executed you should see splash1.bmp.nb on your desktop
8.Rename file to splash1.nb0 (thats a zero)
9.Open the splash1.zip/splash.zip and replace the splash1.nb0 file with yours
10.Confirm file was replaced, sign zip if you want (Right click, Sign file)
Now that we have our zip finished,place on root of SD card
Boot into recovery and flash zip
Follow onscreen instructions
Reboot phone as directed
It will start installing,let it do its thing
Once finished you should be back in recovery
Reboot and enjoy your new splash
[*]THANKS
-Calkulin for the model zip
-Deficitism for hboot splash thread
Hello Everyone,
Thank you in advance for any help on this item.
I have an HTC Sensation phone which is already S-off and has CWM in it.
It also has "su" previleges in it and I was able to modify CID too.
The ROM inside it is stock ROM.
I have been reading and following several guides on how to modify default.prop for other devices. And from what I gather I have to do the following :
1. Unpack boot.img.
2. Modify default.prop.
3. And repack boot.img.
The problem here is that I tried all sorts of things only to end up failing in the "repacking" stage.
I want to modify default.prop to be able to set adb daemon (adbd) to have root previleges and eventually be able to "inject" into HTC sensation my own custom-made versions of framework.jar and other files.
Is modifying default.prop possible?
Is the method I am using correct?
Is it possible to have my own customized framework.jar inside the HTC Sensation?
I hope you guys can point me to some sites and links which can help me in what I intend to do.
Thank you all very much.
Use dsixda kitchen.
Hello Sebastian,
Thanks for your response.
I also tried to use the dsixda kitchen.
What I did was :
1. Downloaded a backup of my phone using ClockworkMod Recovery.
2. I took the boot.img file from the backup generated.
3. Unpacked boot.img using the kitchen.
4. And then repacked it using the kitchen again.
5. I then flashed the generated boot.img into the phone.
6. The phone went into a forever loop in the start up screen.
Did I do it right?
I am rechecking the notes on the kitchen again though. I might have missed something.
Thanks again.
Upload your boot.img, I'll check it. Do you use fastboot.exe to flash boot?
Hello Again,
Thanks once again for the support Sebastian.
"Upload your boot.img, I'll check it. Do you use fastboot.exe to flash boot?"
I use fastboot.exe first and then try to use the ClockworkMod Recovery Advanced option to update the "boot" only part.
I am attaching here my dsixda-kitchen generated boot.img.
This boot .img was generated with the following steps :
1. Unpack htc stock rom boot.img generated by CWM nandroid backup.
2. No changes were made in the ramdisk nor in the kernel part.
3. Repack the ramdisk and kernel using dsixda kitchen.
4. Used fastboot.exe to flash the boot part. "fastboot flash boot boot.img"
5. Wiped the cache partition of the phone.
6. Wiped the /data/dalvik-cache directory.
7. Restarted phone in normal mode.
8. Phone hanged up in startup image.
Many thanks again and more power.
Hi All,
Long time reader, first time poster. Long story short I picked my Gtab up after a long hiatus and wanted to load a custom boot logo to replace the g-tablet logo. Unfortunately I coudlnt find any posts for windows-only users. I found 2 sites with really helpful guides and put 2 n 2 together. I was stoked when my custom logo worked! Credit goes out to Igorv at Slatedroid and LeslieAnn from Android Central forums for their well detailed guides. Special thanks goes out to rajeevvp for compiling the cwm script.
Running Flashback ROM on BL 1.2.
Standard Disclaimer:
Use at your own risk. Im not responsible for what happens to your tablet. Nor do I know how this will affect your other apps. Its highly recommended you do a back up.
Required:
- Gtablet
- 1024x600 pixel image of choice
- Update.zip from Igorv at Slatedroid
- boot_screen_logo_creation_package.rar from LeslieAnn at Android Central
- CWM experience
- Command Prompt experience
This was created for Viewsonic G-tablet. It will replace 2nd boot logo (logo after birds).
Using Clockworkmod flash "update.zip" as you would with a ROM. It will only replace logo.
A. Download one of the Gtablet.zip file from Igorv (See Link 1 below)
B. Unpack any one of the update.zip files. You should have subfolders META-INF and tmp folders. You will replace the initlogo.rle in the tmp folder later.
C. Choose or Create any image file you want to replace the logo with. Make sure the dimensions are 1024x600 pixels
D. Create the RLE file with LeslieAnn's guide (See Link 2 below)
Install:
Extract the boot_screen_logo_creation_package.rar file someplace (see Link 3 below), I recommend something short because you will have to type the location. I use my D drive and a folder named RLE. So D:\RLE is the location I put these files.
How to create an rle file:
Step 1
Make the image you want to use. It MUST be 1024x600 pixels (for the G Tablet).
Step 2
Save the file as a PNG file to the directory you extracted the tool (in my case D:\RLE). I also save the file as a psd so I can later edit it further in a folder specifically for storing this stuff.
Step 3
Go to your start menu and find Command Prompt. This will be in (All) Programs/Accessories.
Step 4
Go to the folder you put the tool, in my case D:\RLE
Step 5
Run the tool, you need to know the name of the png file, again, in my case this is logo.png. Run the tool with the command:
convert_image_to_rle.bat logo.png
You should be left with the raw file, a png file and an rle file, all named logo.
Step 6
Rename the rle file to initlogo.rle and place the file into the update\tmp folder
E. repackage both the META-INF and tmp folder into a new update.zip file. (do not repackage the update folder. Repackage both the META-INF and tmp folders.)
F. Copy the update.zip file into your internal SD card
G. flash the update.zip file you created in CWM like you normally would for a rom
H. Reboot twice and enjoy! (mine hung after the 2nd boot logo and wouldnt get to the boot animation. a second reboot did the trick)
Thanks
Links (add www in front)
1 - Boot Logos (replace 2nd logo) Flashable with CWM
slatedroid.com/topic/20807-boot-logos-replace-2nd-logo-flashable-with-cwm/
2 - Make/extract RLE files in Windows, the easy way (now with Linux)
forums.androidcentral.com/optimus-v-rooting-roms-hacks/113550-make-extract-rle-files-windows-easy-way-now-linux.html
3 - (image file)-to-RLE converter
mediafire.com/?36b7g54t1az8p4j
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.
Hi!
I tried 4 TWRP versions that i found on youtube and this forum, but none seems to work. Each version makes my screen glitchy then restarts into bootloop.
Can someon help me with the right TWRP version for my device?
RP SWREV: B:5 K:5 S:5
Device is SM-A750FN
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
itsmirel said:
Hi!
I tried 4 TWRP versions that i found on youtube and this forum, but none seems to work. Each version makes my screen glitchy then restarts into bootloop.
Can someon help me with the right TWRP version for my device?
RP SWREV: B:5 K:5 S:5
Device is SM-A750FN
View attachment 5264873
Click to expand...
Click to collapse
Download the stock recovery and any TWRP from the internet for your device. Downlaod carliv image kitchen and extract your stock recovery. Copy recovery.img-kernel and “recovery.img-kernel_offset”to any location in your pc. Now take the TWRP for your phone that you download but it's not WORKING. Extract it in the same way using carliv image kitchen. Form this extracted TWRP of your device delete recovery.img-kernel and “recovery.img-kernel_offset” and replace it with the file you copied from your stock recovery in the first step. Then repack this image and flash it. BTW is your bootloader unlocked?
Tab E said:
Download the stock recovery and any TWRP from the internet for your device. Downlaod carliv image kitchen and extract your stock recovery. Copy recovery.img-kernel and “recovery.img-kernel_offset”to any location in your pc. Now take the TWRP for your phone that you download but it's not WORKING. Extract it in the same way using carliv image kitchen. Form this extracted TWRP of your device delete recovery.img-kernel and “recovery.img-kernel_offset” and replace it with the file you copied from your stock recovery in the first step. Then repack this image and flash it. BTW is your bootloader unlocked?
Click to expand...
Click to collapse
Yes, my bootloader is unlocked (if you mean to ask if i have checked OEM/USB debugging in developer mode), I unlocked it first time i tried to run TWRP.
By "repack this image and FLASH IT", flash it using Odin, right?
My current TWRP is unaccessible
Tab E said:
Download the stock recovery and any recovery from the internet for your device. Downlaod carliv image kitchen and extract your stock recovery. Copy recovery.img-kernel and “recovery.img-kernel_offset”to any location in your pc. Now take the TWRP for your phone that you download but it's not WORKING. Extract it in the same way using carliv image kitchen. Form this extracted TWRP of your device delete recovery.img-kernel and “recovery.img-kernel_offset” and replace it with the file you copied from your stock recovery in the first step. Then repack this image and flash it. BTW is your bootloader unlocked?
Click to expand...
Click to collapse
itsmirel said:
Yes, my bootloader is unlocked (if you mean to ask if i have checked OEM/USB debugging in developer mode), I unlocked it first time i tried to run TWRP.
By "repack this image and FLASH IT", flash it using Odin, right?
My current TWRP is unaccessible
Click to expand...
Click to collapse
Is fastboot available? If yes then use fastboot to flash. If no try odin
Tab E said:
Is fastboot available? If yes then use fastboot to flash. If no try odin
Click to expand...
Click to collapse
I guess so
Ok great. Then go ahead with fastboot
Tab E said:
Ok great. Then go ahead with fastboot
Click to expand...
Click to collapse
i will use odin, i dont know how to enter fastboot and couldnt find
Tab E said:
Download the stock recovery and any TWRP from the internet for your device. Downlaod carliv image kitchen and extract your stock recovery. Copy recovery.img-kernel and “recovery.img-kernel_offset”to any location in your pc. Now take the TWRP for your phone that you download but it's not WORKING. Extract it in the same way using carliv image kitchen. Form this extracted TWRP of your device delete recovery.img-kernel and “recovery.img-kernel_offset” and replace it with the file you copied from your stock recovery in the first step. Then repack this image and flash it. BTW is your bootloader unlocked?
Click to expand...
Click to collapse
can you be more specific please? i dont know and understand how to use carliv image kitchen
this is what i downloaded
itsmirel said:
i will use odin, i dont know how to enter fastboot and couldnt find
can you be more specific please? i dont know and understand how to use carliv image kitchen
this is what i downloaded
Click to expand...
Click to collapse
ALSO, the stock rom i downloaded has only .md5 files
itsmirel said:
i will use odin, i dont know how to enter fastboot and couldnt find
can you be more specific please? i dont know and understand how to use carliv image kitchen
this is what i downloaded
Click to expand...
Click to collapse
itsmirel said:
i will use odin, i dont know how to enter fastboot and couldnt find
can you be more specific please? i dont know and understand how to use carliv image kitchen
this is what i downloaded
Click to expand...
Click to collapse
Use md5 firmware extractor
[TUTORIAL] How To Extract Files From a TAR.MD5 Stock ROM (SPH-D710)
I've received a TON of PM's and emails asking how to do this and I've decided to do a write-up for everyone. Now to start off, this does not automatically make you a Super Duper Developer, this does not show you how to make your own TAR ROMs...
forum.xda-developers.com
Open carliv.bat batch file.
Copy your device’s stock ROM’s recovery.img and paste it in the “recovery-resources” named folder that is located inside the unzipped folder.
In the Carliv Image Kitchen window, type in R and press enter. Next, type 1 and hit enter again.
Type 1 to unpack the image file that you downloaded earlier.
If you get a message, “Your image is unpacked in recovery folder”, you have successfully unpacked the image file.
Now open the recovery folder in the Carliv unzipped folder. Look around for a folder named “ramdisk” and other files.
Create a new folder somewhere and name it “stock” (you can name it anything you want). Copy and paste all the contents from the “recovery” folder (ramdisk folder and all 10 other files).
Next, delete the recovery.img file that was left behind on the “recovery-resources” folder before.
Also, delete all the contents in “recovery” folder.
Copy and paste the custom recovery image file, the TWRP that you want to port into the “recovery-resources” folder.
You will need to repeat the same steps as before.
never delete the custom recovery image in the “recovery-resources” folder.
Copy the “recovery.img-kernel” and “recovery.img-kernel_offset” from the stock folder and paste it to the TWRP which you extracted in recovery folder in carliv image kitchen . Overwrite it to replace existing files with the same name.
In the Carliv Image Kitchen window, type 2 and hit the enter key.
A message notifying that the image file was repacked will appear. You can view it on the output folder named “output”. This is the brand new TWRP ported image file.
Copy the newly made image file from the “output” folder and paste it to a new folder. Rename it as you want with any name of your choice. Hope it helps. If you are still stuck I'll do it for you
Tab E said:
Use md5 firmware extractor
[TUTORIAL] How To Extract Files From a TAR.MD5 Stock ROM (SPH-D710)
I've received a TON of PM's and emails asking how to do this and I've decided to do a write-up for everyone. Now to start off, this does not automatically make you a Super Duper Developer, this does not show you how to make your own TAR ROMs...
forum.xda-developers.com
Open carliv.bat batch file.
Copy your device’s stock ROM’s recovery.img and paste it in the “recovery-resources” named folder that is located inside the unzipped folder.
In the Carliv Image Kitchen window, type in R and press enter. Next, type 1 and hit enter again.
Type 1 to unpack the image file that you downloaded earlier.
If you get a message, “Your image is unpacked in recovery folder”, you have successfully unpacked the image file.
Now open the recovery folder in the Carliv unzipped folder. Look around for a folder named “ramdisk” and other files.
Create a new folder somewhere and name it “stock” (you can name it anything you want). Copy and paste all the contents from the “recovery” folder (ramdisk folder and all 10 other files).
Next, delete the recovery.img file that was left behind on the “recovery-resources” folder before.
Also, delete all the contents in “recovery” folder.
Copy and paste the custom recovery image file, the TWRP that you want to port into the “recovery-resources” folder.
You will need to repeat the same steps as before.
never delete the custom recovery image in the “recovery-resources” folder.
Copy the “recovery.img-kernel” and “recovery.img-kernel_offset” from the stock folder and paste it to the TWRP which you extracted in recovery folder in carliv image kitchen . Overwrite it to replace existing files with the same name.
In the Carliv Image Kitchen window, type 2 and hit the enter key.
A message notifying that the image file was repacked will appear. You can view it on the output folder named “output”. This is the brand new TWRP ported image file.
Copy the newly made image file from the “output” folder and paste it to a new folder. Rename it as you want with any name of your choice. Hope it helps. If you are still stuck I'll do it for you
Click to expand...
Click to collapse
The stock rom i downloaded has multiple .md5 archives. And [AP_A 750...] has inside a recovery.img.lz4 file
Should i download other stock rom? Or use this as .img.lz4
itsmirel said:
The stock rom i downloaded has multiple .md5 archives. And [AP_A 750...] has inside a recovery.img.lz4 file
Should i download other stock rom? Or use this as .img.lz4
Click to expand...
Click to collapse
Btw, the tutorial "How To Extract Files From a TAR.MD5 Stock ROM" isn't working anymore. his MyBB forum doesnt work. (MyBB has experienced an internal error and cannot continue.)
Tab E said:
Use md5 firmware extractor
[TUTORIAL] How To Extract Files From a TAR.MD5 Stock ROM (SPH-D710)
I've received a TON of PM's and emails asking how to do this and I've decided to do a write-up for everyone. Now to start off, this does not automatically make you a Super Duper Developer, this does not show you how to make your own TAR ROMs...
forum.xda-developers.com
Open carliv.bat batch file.
Copy your device’s stock ROM’s recovery.img and paste it in the “recovery-resources” named folder that is located inside the unzipped folder.
In the Carliv Image Kitchen window, type in R and press enter. Next, type 1 and hit enter again.
Type 1 to unpack the image file that you downloaded earlier.
If you get a message, “Your image is unpacked in recovery folder”, you have successfully unpacked the image file.
Now open the recovery folder in the Carliv unzipped folder. Look around for a folder named “ramdisk” and other files.
Create a new folder somewhere and name it “stock” (you can name it anything you want). Copy and paste all the contents from the “recovery” folder (ramdisk folder and all 10 other files).
Next, delete the recovery.img file that was left behind on the “recovery-resources” folder before.
Also, delete all the contents in “recovery” folder.
Copy and paste the custom recovery image file, the TWRP that you want to port into the “recovery-resources” folder.
You will need to repeat the same steps as before.
never delete the custom recovery image in the “recovery-resources” folder.
Copy the “recovery.img-kernel” and “recovery.img-kernel_offset” from the stock folder and paste it to the TWRP which you extracted in recovery folder in carliv image kitchen . Overwrite it to replace existing files with the same name.
In the Carliv Image Kitchen window, type 2 and hit the enter key.
A message notifying that the image file was repacked will appear. You can view it on the output folder named “output”. This is the brand new TWRP ported image file.
Copy the newly made image file from the “output” folder and paste it to a new folder. Rename it as you want with any name of your choice. Hope it helps. If you are still stuck I'll do it for you
Click to expand...
Click to collapse
i am in the same position, have read your guide intensively but do not succeed in finding the "recovery-resources" folder, and i my version of CiC there is no R (ecovery) in the main menu. will you be so kind to make the twrp?
benniehelder said:
i am in the same position, have read your guide intensively but do not succeed in finding the "recovery-resources" folder, and i my version of CiC there is no R (ecovery) in the main menu. will you be so kind to make the twrp?
Click to expand...
Click to collapse
Following this guide has booted TWRP on some devices. Please make sure you are on android 10
Tab E said:
Following this guide has booted TWRP on some devices. Please make sure you are on android 10
Click to expand...
Click to collapse
thx,thx,thx for the support!. I have done the carliv protocol but in the end the new compiled twrp failed in Odon. Maybe the new image converting to ,tar is the culprit? after that i tried to do the method in the video but twarp was 3 seconds visible and then back in bootloop!. i shall DL the magisk 20.3 edition. maybe that makes the difference'I bought this A7 last monday after a HUawei, that has no posibilities whatsoever for twrp or root, but in this Samsung I totally surprised that it, untill now, is so umbeatable, albeit unlocked!
benniehelder said:
thx,thx,thx for the support!. I have done the carliv protocol but in the end the new compiled twrp failed in Odon. Maybe the new image converting to ,tar is the culprit? after that i tried to do the method in the video but twarp was 3 seconds visible and then back in bootloop!. i shall DL the magisk 20.3 edition. maybe that makes the difference'I bought this A7 last monday after a HUawei, that has no posibilities whatsoever for twrp or root, but in this Samsung I totally surprised that it, untill now, is so umbeatable, albeit unlocked!
Click to expand...
Click to collapse
how to make from the new homemade recovery a tar, so you can flash with odin?
benniehelder said:
how to make from the new homemade recovery a tar, so you can flash with odin?
Click to expand...
Click to collapse
Convert TWRP .img to .tar (for ODIN)[Easy]
Sometimes the latest version of TWRP is in ".img", so some people use an older version instead, which is in .tar, so they can flash it with ODIN. The thing is that the ".tar" version is just the ".img" compressed XD, so I'm going to show you how...
forum.xda-developers.com
i had done this with z7 myself already, but to no avail, but: i began, in a moment of despair, with Odon to try all the .tars i had collected sofar , to flash and when i flashed PBRP (it was not the first time) it worked!!!. after a week the gizmo do have a recovery, that is not stock! Little new prob: By rebooting system he bootloops (for a change!) in bootloader mode.