Database Develop

Nexus One Splashscreen Scaled for G1/Magic

BIG LOGO
{
"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"
}
DOWNLOAD: http://www.megaupload.com/?d=7RXNL18L
DOWNLOAD: http://www.mediafire.com/?3nymonjmmuj
LITTLE LOGO
DOWNLOAD: http://www.megaupload.com/?d=GHAP5YFE
DOWNLOAD: http://www.mediafire.com/?1an13t2yqta
How to flash:
fastboot flash splash1 <filename>
fastboot reboot

Nice.
Thanks !!

rgb556?
hey maxisma, whats the file type opened with ?

I was hoping that someone would make this, thanks!

Yeah, I also just get a .txt file downloaded. Should it be renamed to .zip and flashed from recovery?...or ...?

bert269 said:
Yeah, I also just get a .txt file downloaded. Should it be renamed to .zip and flashed from recovery?...or ...?
Click to expand...
Click to collapse
don't change the filename. he has instructions at the bottom of the post. boot into fastboot and type in the commands. everything is how it should be. rgb565 is the correct file type.

Is this animated or not?

idbl_fanatic said:
Is this animated or not?
Click to expand...
Click to collapse
it's a splash screen. it replaces the tmobile g1 screen when you first boot up your device.

grandomegabosses said:
it's a splash screen. it replaces the tmobile g1 screen when you first boot up your device.
Click to expand...
Click to collapse
Oh ok, so it's not the 2nd screen that comes up, darn it! Oh well.

is it possible to use console or terminal?

s0mep00p said:
is it possible to use console or terminal?
Click to expand...
Click to collapse
not from anything i've read. fastboot is your friend.

why the hell is it keep on saying cannot find <file name> when i try to do fastboot for splash screens!!! i made a folder on the desktop with the name "fastboot" and even made a folder with the same name on the root of the sd card. fastboot works and it recognizes my device. if you can help send me a email at [email protected]

Thankyou so much Maxis!

Thanks for the image

AndroidNoobie said:
why the hell is it keep on saying cannot find <file name> when i try to do fastboot for splash screens!!! i made a folder on the desktop with the name "fastboot" and even made a folder with the same name on the root of the sd card. fastboot works and it recognizes my device. if you can help send me a email at [email protected]
Click to expand...
Click to collapse
you need to be operating out a folder that has fastboot.exe in it. like the tools folder of the sdk.

david1171 said:
you need to be operating out a folder that has fastboot.exe in it. like the tools folder of the sdk.
Click to expand...
Click to collapse
And fastboot has to be in the same folder as the .rgb565 file

david1171 said:
you need to be operating out a folder that has fastboot.exe in it. like the tools folder of the sdk.
Click to expand...
Click to collapse
thanks man. I love you (no homo)

Somebody backed this up perhaps? Download links aren't working..

Bad SBF

Hi guys!Sorry for my post but i don't know where to post.So,let's start.
First i install a sbf file from sbf room's.The process was a success.When i start the phone to look i saw i don't have the Play Store and File Manager to install a new ROM.
When i try to install the ROM i have an error:
E:Can't open /cache/recovery/command
--Install from sdcard...
Finding update package...
Opening update package...
E:failed to open /sdcard/update.zip(No such file or directory)
E:signature verification failed
Installation aborted.
I have a Motorola Milestone A853.It is rooted.
I need help because i don't want to go in service because i know we can fix this problem.This SBF is bat because the battery is go to 0% in just few hours.Sorry for my bother but i need much help.Thanks you!

You have to flash vulnerable recovery again.

Eiertschik said:
You have to flash vulnerable recovery again.
Click to expand...
Click to collapse
ok i will try

dragosneagu95 said:
ok i will try
Click to expand...
Click to collapse
I had made the root.Everything goes ok.My phone was rooted again.But the error with sd card persist.:crying:
I don't know what can I do....

Are you sure the update.zip file and "OpenRecovery" folder are on your SD card?

Eiertschik said:
Are you sure the update.zip file and "OpenRecovery" folder are on your SD card?
Click to expand...
Click to collapse
First,beause of this SBF i don't have on my phone the File Manager and Play Store.I don't see the files.Just see the memory in settings.
Second, the update.zip goes successfully. Appeared a message that my phone was successfully rooted.
I will come with somes images...mybe you will now.

dragosneagu95 said:
First,beause of this SBF i don't have on my phone the File Manager and Play Store.I don't see the files.Just see the memory in settings.
Second, the update.zip goes successfully. Appeared a message that my phone was successfully rooted.
I will come with somes images...mybe you will now.
Click to expand...
Click to collapse
{
"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"
}
Take a look and reply please.

Guys do you know some answers or can i go to service?

Did the apps HSTcmd, My Sign, Superuser Whitelist already come within the sbf?
If yes then you did NOT get an original sbf.

Eiertschik said:
Did the apps HSTcmd, My Sign, Superuser Whitelist already come within the sbf?
If yes then you did NOT get an original sbf.
Click to expand...
Click to collapse
no,they didn't come
but if i install a SBF over SBF i brick my phone?I tried this solution on a Defy and i bricked.Tell me please.

You can get the stock SBFs from HERE.

Erovia said:
You can get the stock SBFs from HERE.
Click to expand...
Click to collapse
Ok but who is the original SBF?
And if I install a SBF over SBF I brick my phone?

These are all original ones. You should choose the one which is closest to your mobile carrier.
I can't say for sure, but I don't see how it could brick your phone. Writing the same data over and over into the memory of your phone doesn't make any difference.

Erovia said:
These are all original ones. You should choose the one which is closest to your mobile carrier.
I can't say for sure, but I don't see how it could brick your phone. Writing the same data over and over into the memory of your phone doesn't make any difference.
Click to expand...
Click to collapse
I will try and I'll come with news

GOD Bless You!I fix the problem with yours answers,special Erovia(your guidance was great),but all members.Sorry for my raunchy style to write but I was sad.Thanks you again!:fingers-crossed:

[GUIDE] How to get back the stock kernel of Nexus 5 (LMY47I)

Hi everybody,
This is my second post at XDA and as an answer to my first post (List of Lollipop 5.1 custom kernels for the Nexus 5) This post guides you how get back the stock kernel (LMY47I).
Always remember: You flash at your own risk! This post is only for the Lollipop build LMY47I!
There are two ways to get the stock kernel back, the first with a custom recovery like TWRP or CWM and the second with FASTBOOT (UNLOCKED BOOTLOADER is imortant)
1. Download the STOCK-KERNEL.ZIP in the attachments and extract it (for example with WINRAR or 7-ZIP). Then you have two files. The only one you need is the Kernel.zip file! Copy it to your phone, then switch to the custom recovery navigate to the Kernel.zip file and flash it. Now reboot the phone. The stock kernel was succesfully flashed.
2. Download the STOCK-KERNEL.ZIP in the attachments and extract it (for example with WINRAR or 7-ZIP). Then you have two files. The only one you need is the boot.img! If you haven't downloaded the Android SDK yet download it now! Switch to folder where you installed the SDK and navigate to "platform-tools". Copy the boot.img file into it. Now reboot your phone into FASTBOOT (Bootloader) with POWER Button + VOLUME DOWN and connect your phone to your PC wait until the drivers are installed if you get an error install the latest Google drivers. Open CMD navigate to "platform-tools" and type: "fastboot flash boot boot.img". Reboot your Phone and disconnect the USB-Cable. The stock kernel was succesfully flashed.

Error
Can't flash the zip, says "Unable to execute"

falcon.prj said:
Can't flash the zip, says "Unable to execute"
Click to expand...
Click to collapse
What is the name of the .zip that you tried to flash?

some custom kernels also modify/replace other files in the system partition, so is flashing just boot.img enough to return to stock kernel then?

Wakamatsu said:
What is the name of the .zip that you tried to flash?
Click to expand...
Click to collapse
Kernel.zip
And the problem was with TWRP, sorry
and thanks!

iamelton said:
some custom kernels also modify/replace other files in the system partition, so is flashing just boot.img enough to return to stock kernel then?
Click to expand...
Click to collapse
Nope. So this thread is kinda pointless. You need to reflash your rom after hellscore, code blue, elementalx and probably franco (not used franco since kitkat)
From hells thread -
{
"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"
}
Sent via tapatalk from my cataclysm'd Lollipooop Nexus 5

Marshmallow "Couldn't capture screenshot."

Hello All,
I have a Nexus 6 (Hence the reason I'm posting in this thread) and I am not able to take screenshots after upgrading to Marshmallow 6.0. I would think to post in the thread of the current rom I'm running but I also full wiped and tried a different rom with the same result.
Every time I try and take a screen shot it says "Couldn't capture screenshot. - Can't take screenshot due to limited storage space, or it isn't allowed by the app or your organization." I would post a screenshot of what it's doing but... well... I think you get the point. I have plenty of storage space and I have dived into the various permissions settings on 6.0 but have yet to find out how to fix it.
Has anyone else had this problem across multiple roms and no luck with screenshots?
Currently running:
Chroma Oct-10-2015
Kernel:
3.10.40-Chroma-v1.01

Go to the screenshot directory and try to manually create any file there using your usual file manager/explorer.. If that fails,.it may be that the permissions are screwed which sometimes happens when you copy sdcard data back whilst in recovery.
If that sounds like your problem, there is a zip you can flash. Do NOT use "fix permissions" in recovery.
Flash this*zip*via recovery...
http://forum.xda-developers.com/attachment.php?attachmentid=2849968&d=1405300107
Located from thread: http://forum.xda-developers.com/showthread.php?t=2239421 by @osm0sis

danarama said:
Go to the screenshot directory and try to manually create any file there using your usual file manager/explorer.. If that fails,.it may be that the permissions are screwed which sometimes happens when you copy sdcard data back whilst in recovery.
If that sounds like your problem, there is a zip you can flash. Do NOT use "fix permissions" in recovery.
Flash this*zip*via recovery...
http://forum.xda-developers.com/attachment.php?attachmentid=2849968&d=1405300107
Located from thread: http://forum.xda-developers.com/showthread.php?t=2239421 by @osm0sis
Click to expand...
Click to collapse
There was a miscellaneous file on the /sdcard/pictures folder called screenshots. I couldn't access it and I couldn't create a new folder called screenshots
Es says operations failed
Sent from my Nexus 6 using Tapatalk

mkgarrod said:
There was a miscellaneous file on the /sdcard/pictures folder called screenshots. I couldn't access it and I couldn't create a new folder called screenshots
Es says operations failed
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Try this. Boot into TWRP select Advanced, File Manager go to /sdcard/pictures hit Select, chmod 755, confirm, reboot.
{
"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"
}

mkgarrod said:
There was a miscellaneous file on the /sdcard/pictures folder called screenshots. I couldn't access it and I couldn't create a new folder called screenshots
Es says operations failed
Click to expand...
Click to collapse
Witek_M said:
Try this. Boot into TWRP select Advanced, File Manager go to /sdcard/pictures hit Select, chmod 755, confirm, reboot.
Click to expand...
Click to collapse
Why are you still in ES? The problem isn't permissions, it's ownership. Use my zip as was suggested by @danarama.

The permissions zip worked,
As to why I was "still in ES?" I like to have an understanding of how everything works. May not be the quickest way to fix a problem, but it allows process of elimination on my side to see what specifically the issue is.
I appreciate the .zip and suggestions everyone! Thanks!

osm0sis said:
The problem isn't permissions, it's ownership. Use my zip as was suggested by @danarama.
Click to expand...
Click to collapse
@osm0sis, You are amazeballs!! Ran into this same inconvenience the last couple of days. Swyped a quick search, quite effortlessly arrrived here, where I can thank you for the fruits of your labour. And I do mean ALL of your work across XDA. I appreciate you much! ?

Take screenshot on your PC
Well, I think maybe you can try taking the screenshot of your Nexus 6 on computer. Just don't do it on the phone if it keeps failing. Android Manager can do this and save the picture on your PC.

is it working now?

You can try to rename pictures to pictures2 and reboot your phone, this was a quick solution on the oneplus one, if it works, but it's a dirty solution.

Error when flashing factory images to RP2

I'm attempting to flash the Global Pie Image (P-MR1-RC003-RZR-190305.3110) to my ATT variant as I saw other members saying they did this and it worked without any problems. I managed to unlock the bootloader and whatnot but when I run flash_all I get the error "fastboot: error: cannot load 'gpt_both0.bin' : No such file or directory" and so on for the rest of the files. Any ideas as to what I could have done wrong?

Bot_None said:
I'm attempting to flash the Global Pie Image (P-MR1-RC003-RZR-190305.3110) to my ATT variant as I saw other members saying they did this and it worked without any problems. I managed to unlock the bootloader and whatnot but when I run flash_all I get the error "fastboot: error: cannot load 'gpt_both0.bin' : No such file or directory" and so on for the rest of the files. Any ideas as to what I could have done wrong?
Click to expand...
Click to collapse
Windows or Linux? Which flash_all are you using? seems like the files are not there maybe inside a folder?

Warrior1988 said:
Windows or Linux? Which flash_all are you using? seems like the files are not there maybe inside a folder?
Click to expand...
Click to collapse
I'm using Windows 10 and as far as I can tell everything seems to be in the same directory.
{
"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"
}

Bot_None said:
I'm using Windows 10 and as far as I can tell everything seems to be in the same directory.
Click to expand...
Click to collapse
I don't see the fastboot.exe
This might help.
Go here https://forum.xda-developers.com/showthread.php?t=2588979

Warrior1988 said:
I don't see the fastboot.exe
This might help.
Go here https://forum.xda-developers.com/showthread.php?t=2588979
Click to expand...
Click to collapse
I just added the folder with ADB and fastboot to the path variable. Is it necessary to have them in that directory if I have it added as a path variable?

Bot_None said:
I'm using Windows 10 and as far as I can tell everything seems to be in the same directory.
Click to expand...
Click to collapse
Bot_None said:
I just added the folder with ADB and fastboot to the path variable. Is it necessary to have them in that directory if I have it added as a path variable?
Click to expand...
Click to collapse
Not if you set the path environment up right. To be on safe side copy fastboot.exe inside the folder with all the .img

Warrior1988 said:
Not if you set the path environment up right. To be on safe side copy fastboot.exe inside the folder with all the .img
Click to expand...
Click to collapse
Tried that and it still gives the same error

Bot_None said:
Tried that and it still gives the same error
Click to expand...
Click to collapse
Other things to try different usb c or port.

Warrior1988 said:
Other things to try different usb c or port.
Click to expand...
Click to collapse
I set up a Windows 10 VM and now this happens so that's progress ig