Database Info

Custom initial boot splash screens in full 480x640 - 2nd Round Posted

Using the tools and info from pfcsabre and the below link I created some initial splash screen .nbh files. This replaces the very first picture you see when you turn on your phone and displays your radio version and such. If you want to make your own use this link. http://forum.xda-developers.com/showthread.php?t=436105
Since I spent a little bit of time making these files and other files I haven't uploaded yet, I figured I would share them. I will probably upload more later.
Instructions: - Make sure your phone is Hard-SPL
1. Download the RaphaelCustomRUU.zip and unzip it to the RaphaelCustomRUU.exe file.
2. Download one of the Splash.zip files and unzip it to the same folder as the RaphaelCustomRUU.exe file (Make sure there is only 1 .nbh file in the same folder as the .exe,,, if you download multiple splashes put them in a subfolder)
3. Connect your phone to your PC and Run the RaphaelCustomRUU.exe file and follow the prompts. Its the exact same method as burning a ROM, but these files only replace the Splash screen and nothing else.
4. It will take about 20-30 seconds to burn and your phone will reboot displaying the pics in full 480*640 resolution.
5. These look incredible when you first boot up your phone.
Splashes:
{
"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"
}
Downloads:
RaphaelCustomRUU.zip
Gears of War.zip
Matrix Trinity.zip
Lich King.zip
Kelly Brook.zip
Warnings:
I take no responsibility for any problems you have.
Make sure your phone is Hard-SPL and follow the instructions.
These are only for the Raphael, do not use on the Diamond.
I have tested all of these files and confirmed they all worked.

Splashes V2:
Downloads:
RaphaelCustomRUU.zip
Decepticons.zip
Metroid.zip
Slayer.zip
Jennifer Lopez.zip

4 more boot splash screens are done. I will upload them tomorrow. My new favorite is a sweet looking Transformers Decepticons Logo.

Can you make these please?

heres a couple id like to have done if at all possible.
thanks in advance,
Jstar

I just overwrite the image to what the default boot screen was. (You can find out what the original filename was somewhere in Advanced Config)

Maveaxe said:
Can you make these please?
Click to expand...
Click to collapse
JstarLuvsTina said:
heres a couple id like to have done if at all possible.
thanks in advance,
Jstar
Click to expand...
Click to collapse
If both of you look here, I think you will both be pleasantly surprised.
http://forum.xda-developers.com/showthread.php?t=462668

CarlCastro said:
I just overwrite the image to what the default boot screen was. (You can find out what the original filename was somewhere in Advanced Config)
Click to expand...
Click to collapse
This process changes the 1st boot screen, the one with the red letters in the lower right corner. It cannot be done within Windows by overwriting a file, it must be burnt in. When turning on your phone you can have up to 4 pictures, This boot screen process, follow by up to 2 splash screens (usually windows & operator splashes), then your wallpaper.

Tried many "fixes" and still in boot loop.

I've been stuck in a boot loop on one of my G-Tabs for about 4 days now. Been trying every fix I can find to no avail so far. I have the Viewsonic to G-Tablet boot loop. I keep noticing people reffering to using NVFlash with the Img9 fix to add in ClockWord mod. Many said to do that flash then to wipe the data, which is where the problem lies. I get this error everytime I try:
{
"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"
}
Any ideas?

Repartition 2048 and 0.

Hello KJ and thanks for replying, I have seen you offer help to alot of people so thanks for dropping by here too.
I have tried that as well and it hasn't done anything. I don't know if it is the order in which I am doing things or what on this tab. My other one works like a dream but it was done before the 4539 (I think that's right) update came out.
I have done the NV Flash and added CWM via Ext SD and then partitioned and that was a no go. I also tried doing Roebeet's example of doing NVFlash and changing te Img9 file as well with a repart and that didn't work either.
I also tried this "fix" and even it didn't work.
http://forum.xda-developers.com/showthread.php?t=974422
I'm not giving up because from all I am reading, these things seem immpossible to fully brick. I also feel pretty safe to say that it is my fault and that maybe I don't have the correct order for doing the entire process but I have tried until I turned blue in the face before giving up and going to bed.

Well... what your tablet is having trouble mounting is the partitions that you should be creating with the repartitioning. /dev/blk/mmcblk3 is the internal memory. Are you familiar with ADB?

No not at all. I googled during this and saw Android Debug Manager. Something with that I should try? I definitely don't claim to be the smartest guy on the block but at the same time I pick up this stuff well and am not really scared to try something if you have an idea.

Congrats, man. I think you're the first to truly brick his gtab.

tunez23 said:
No not at all. I googled during this and saw Android Debug Manager. Something with that I should try? I definitely don't claim to be the smartest guy on the block but at the same time I pick up this stuff well and am not really scared to try something if you have an idea.
Click to expand...
Click to collapse
Unfortunately, I'm not a good enough teacher (I lack the proper patience) to get someone going with ADB from scratch. Especially since my development environment is somewhat unusual so I often have no frame of reference to assist in setting up the tools. So, if you're up to it, you need to do one of two things. Either get ADB installed and running on your computer or get a rooted ROM and a terminal emulator on the device that we need to work on.
Your situation is somewhat different from the others in that you can actually get CWM installed and get into recovery. I still think that perhaps some combination of partitioning, data wipe and fix permissions should be working for you. What I would do in your case is:
1) Data wipe one more time (perhaps use: http://forum.xda-developers.com/showthread.php?t=1030915)
2) Reboot into CWM recovery and repartition
3) nvflash the stock ROM again (without CWM)
4) Factory reset from the ROM settings
If that fails then research setting up ADB for your computer and we'll discuss some diagnostics you can run from that.

Thanks KJ, I will try those when I get home this evening.

[Q] Bricked SGS4G

Hi, i got this Samsung G S 4g. I was supposed to fix the rom (somewhat unstable thing). I will try to write all the things i have done until now. I got the "phone to pc" icon. I cannot boot or use download mode (the triangule thing)
General Info
Device is rooted. T-mobile branded, carrier-locked.
Froyo rom. (i think is stock but rooted).
Somewhat old device.
Had stock recovery (Android recovery e3 o something like that)
SGH-T959V (KB5)
Things i did
1. Pull some files from device, to sim-unlock. (using ADB) DID not modify anything else
2. SIM-Unlock using code (worked)
Then, device worked ok some weeks... then stopped working, contacts and phone apps crashed suddenly, everytime i open them
4. Use lastest Heimdall and this guide to get CWM on the phone. The idea was to flash the kernel. did not work. Check the part called "How To Flash a Kernel with Heimdall".
I did that. NOTE: used this kernel insted of the "old" one that the guide says.
Then it output this error: "libusb error: -12". So Heimdall didn't detect the device so i used zadig.exe after reinstalling the samsung drivers to avoid this issue. Then, it started working, and output something like this: "failed sending file part packet heimdall"
And now i have this:
{
"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"
}

What you have is an alternate form of DL mode that occurs after a failed flash. Read this to get back up and running.
Lumins Guide

Or just reboot the phone, it should go to a disturbing looking tiny-phone mode. Then just resend your heimdall command and it should happily work.

Major kudos to diego930 for such a nicely detailed description of his problem!

Yes... my computer didn't feel like showing the tiny disturbing phone this morning, else I could have skipped the suggestion to reboot.
That just means that the safeties are off and your phone is ready and waiting to get flashed. You're close... and probably got fixed, based on the thanks provided.

Theraze said:
Or just reboot the phone, it should go to a disturbing looking tiny-phone mode. Then just resend your heimdall command and it should happily work.
Click to expand...
Click to collapse
How i do reboot ? I just get the phone to pc icon everytime lol
jeffsf said:
Major kudos to diego930 for such a nicely detailed description of his problem!
Click to expand...
Click to collapse
Thanks I like making myself very clear (and i know how annoying is the lack of info)
I haven't touch the device since i broke it so i'm going to try that guide and post any news. Thanks all!

When you get that phone to pc icon, just use Heimdall to flash again.
The reboot-step is from official-download mode where it has the big yellow caution taking you to panic-download mode where it has the tiny phone you posted in #1. Once you have panic-download mode, your phone is ready to accept anything. Even whatever failed before.
Summary: Repeat OP Step 4.

ok, done. Fix using heimdall 1 click! I just reflash GB with kernels and bootloaders, now it works flawless.
Thanks Theraze.

RedWolf Recovery for Orbic Wonder

{
"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"
}
For a little while there I had an Orbic of my own, but that caused mass-hysteria on Verizon's part because you aren't supposed to try and put a post paid SIM in a pre paid phone or it won't work. However it doesn't just "not work", it totally messes up your account big time to the point where no one knows how to fix it. It turns your postpaid SIM into a prepaid one and locks you out, among some other things too that generally turn your smile into a frown. Long story short I was without service for 5 days straight and ended up having to return my Orbic and get an X4 from Best Buy (so I guess there's a happy ending to it). Lesson learned, won't be trying that again. Hopefully this message can prevent someone else from making the same mistake as well
Anyway, during that very short time I had the Orbic I managed to make a dirty port of something called RedWolf Recovery. I had this sitting around on my computer and almost forgot about it entirely. Think TWRP but it has different branding and much more features, like more partitions it can back up and a theme engine that's supposedly much better and more flexible than TWRP's
WHAT WORKS:
Everything except what's listed below
WHAT DOESN'T WORK:
Basically the same stuff as my dirty port of normal TWRP, the vendor partition won't mount and data won't mount until you flash the disable-encryption zip and factory reset
If you find anything else let us know. I might not be able to fix it entirely since I don't have proper source code to work from (all these images are pre-compiled dirty ports) but at least everyone else can be aware to stay away from certain things if they break something
DOWNLOAD:
LINK TO THE IMAGE ITSELF
To install it just flash it in fastboot like you would the normal TWRP image
I can't exactly provide any "source code" either since all of my stuff are dirty ports so far. However all of the images I use I will link to right here so you can still have access to everything I did to work with in your own endeavors
THANKS TO:
Team RedWolf for that bangin' recovery I could pull from
XDA user @Devil7DK for making the Redmi 3S port of RedWolf, that has the same chipset as the Orbic so that's what I used to dirty port. Check out his original thread HERE
Team Orbic for the usual help they provide
Carliv Image Kitchen for letting me do all those dirty ports and mods of images that I did

how do i flash the dm verity? I can't seem to save it on the phone on a partition thats mounted, and thus can find it in twrp.
Can i flash it with adb/fastboot?

bubbyj said:
how do i flash the dm verity? I can't seem to save it on the phone on a partition thats mounted, and thus can find it in twrp.
Can i flash it with adb/fastboot?
Click to expand...
Click to collapse
You can't flash "dm verity"

Stone Age. :)

Dear all ,
I hope your expert team will give me an idea with my old Samsung GT-P5110 (wifi). I had good times with that tablet , but seems like , even if the technology go fast, everybody tell me to throw it away. I am still believe that old devices they do their own job. At least one ( other than clock ).
I stack for days now to find away what I can do to upgrade this as with the 4.0.4 you can do practically a big NOTHING. Neither online update. ( No support from Samsung but when I bought it they loved my money) Sorry but I am not agree with their policies . In now days I would like to use this table just to show me the status of my solar panels, even without android based os ( Linux for tablet was also a good idea ) but nothing to escape from 4.0.4
The problem is that the USB/ samsung port is destroyed, and the only way to update it is via SD card. But I am lost. Everything I try with official firmwares just not make any change. If I am correct after so much reading -Probably I need a file just for update only ex Filename: GT-P5113_P5113XARCLH-OTA-P5113UEBLH3_XAR_280235988.zip | Size: 267 MB but nowhere availabe.
You have any ideas to save my beloved table and to convert it on something more useful than that where the "brick" is same as now for me
Altough I am an old guy - old board, that I was starting at my 5 ys to play with old radio tubes and fixing radios... just for the history.. )
Thank you in advance for your replies and knowledge - much appreciate it.
Pic with About page included.
{
"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"
}

First things first One should not expect to get any further official updates from you manufacturer. You may get a newer Android version by flashing a custom rom. This could be done without a working usb port but if at some point you cannot boot into recovery nor system for some reason, you get a shiny paperweight (usually one would fix that using usb download mode).
Android 4.0.4 is really not new, but the usability greatly depends on what you want to do with it. How would you get the status of your solar panels? You should have a working browser on your tablet, so showing a website with your solar panel statistics should not be a problem.
If you still want to go through the process of installing a custom rom, this is what you could do:
Get root access by using some Root Apps, for example KingoRoot. You will find guides on XDA
Install flashFire and use it to flash a custom recovery
boot into the custom recovery and install the custom rom from SD card.
reboot into your new rom

olympicwave said:
GT-P5113_P5113XARCLH-OTA-P5113UEBLH3_XAR_280235988.zip | Size: 267 MB
Click to expand...
Click to collapse
where have you found this filename?
You may look here for Roms for your device

PauSteu said:
First things first One should not expect to get any further official updates from you manufacturer. You may get a newer Android version by flashing a custom rom. This could be done without a working usb port but if at some point you cannot boot into recovery nor system for some reason, you get a shiny paperweight (usually one would fix that using usb download mode).
Android 4.0.4 is really not new, but the usability greatly depends on what you want to do with it. How would you get the status of your solar panels? You should have a working browser on your tablet, so showing a website with your solar panel statistics should not be a problem.
If you still want to go through the process of installing a custom rom, this is what you could do:
Get root access by using some Root Apps, for example KingoRoot. You will find guides on XDA
Install flashFire and use it to flash a custom recovery
boot into the custom recovery and install the custom rom from SD card.
reboot into your new rom
Click to expand...
Click to collapse
PauSteu, Thank you very much for your reply and guidance.
Yes, I tried old versions of Kingoroot but nothing work. The newer versions reply parse error before even installing. Its quite old the 4.0.4 ( after factory reset ). Thats why I thought that if I will able to upgrade at least to Jelly 4.2 to start doing something. Becuase now even the browser are not compatible with most of web pages, including the solal panels one.
Althout I will continiue try to take the challenge and searching more. Thank you for your time spending for me.

PauSteu said:
where have you found this filename?
You may look here for Roms for your device
Click to expand...
Click to collapse
I founded in some old forums back to 2013 as an update only file that you can feed from SD card and upgrade the tablet from 4.0.4 to 4.2. But not available anymore in any hosting. ( thanks for the link)