Is it possible? With my old phone you could (droid bionic) is it possible on the glorious N⁴?
Sent from my Nexus 4
Boot logo or animations? If can rom toolbox.
Sent from my Nexus 4 using Tapatalk 4
boot logo changing isnt possible on the n4, unless you want a bricked device.
max1001 said:
Boot logo or animations? If can rom toolbox.
Sent from my Nexus 4 using Tapatalk 4
Click to expand...
Click to collapse
Another vote for Rom Toolbox Pro, changed my boot animation without any hicup! I'm using "Mbrokeh" listed under tablet animations!
realmeister said:
Another vote for Rom Toolbox Pro, changed my boot animation without any hicup! I'm using "Mbrokeh" listed under tablet animations!
Click to expand...
Click to collapse
boot animation and boot logo are two completely different things. and you dont need an app to change boot animations. just put whatever bootanimation.zip into /system/media/ or /data/local/ and reboot for it to take affect. but again, boot logo and boot animation are two different unrelated things.
Oops, thanks for correcting me. Only goes to show I need to read more carefully next time before responding!
Well that sucks. And odd that you can't. I think you can on the gnex. I flashed a kernal on it and it had the kernal branded under Google. Odd.
Sent from my Nexus 4
zakkyzombie said:
Well that sucks. And odd that you can't. I think you can on the gnex. I flashed a kernal on it and it had the kernal branded under Google. Odd.
Sent from my Nexus 4
Click to expand...
Click to collapse
on the gnex we can, thanks to ezekeel. he tried to enable it on the n4 as well, but he said the chances of bricking is way to high. that boot img is located in the bootloaders partition. i did the testing for him on the gnex, and was very happy when he finally got it
simms22 said:
on the gnex we can, thanks to ezekeel. he tried to enable it on the n4 as well, but he said the chances of bricking is way to high. that boot img is located in the bootloaders partition. i did the testing for him on the gnex, and was very happy when he finally got it
Click to expand...
Click to collapse
Damnit Google! Lol. I'd love to have my own image there. Thanks for your help Simms.
On a unrelated topic; are you handy with apkmultitool? And super awesome at decompiling/compiling?
Sent from my Nexus 4
I want to change the logo on my Honda accord to a Ferrari F1 logo.
See the logic here? lol
Sent from my shiny new(bought last Nov), scratch less Nexus 4!
Again used to be able to do this on the nexus one also.
The correct name is the splash (the first thing you see when powering on. The x and Google before the animation)
It used to be a separate partition on older phones (splash1)
But now it is part of the bootloader which means modifying it is risky
Sent from my Nexus 4 using xda app-developers app
Related
Hello everybody.
A few days back I managed to brick my Nexus 4 after using it for 1 day!!!! I realize that this all is a very moronic situation and there isn't a fix for my brick because a used a *Toolkit*. Well, I'm already receiving my replacement and it will be here in an hour.
I know how everyone here feels about Google paying for our mistakes but I'm so lucky they're so kind. The advice that I need is on how to NEVER be in this same position. If I were to have set up fastboot instead of a toolkit would all of this have been avoidable? Btw, CM 10.1 is how I bricked my phone....I never have had any luck with that rom.
Thanks everyone for your advice.
Almost all errors are caused by, you guessed it, users. I am skeptical when people claim the toolkit bricked their phone. Also, if cm 10.1 has been troublesome for you, why keep using it? Its the very definition of insanity: keep doing the same thing over and over and expecting different result.
Sent from my Nexus 4 using xda premium
Sooooo, in your professional opinion....would my brick have been less severe if I used fastboot?
Maybe you flashed the wrong cm 10.1 ROM. Perhaps, from another device?
Sent from my Nexus 4
blitzzz3434 said:
Maybe you flashed the wrong cm 10.1 ROM. Perhaps, from another device?
Sent from my Nexus 4
Click to expand...
Click to collapse
Well what happened was when I tried to flash it the first time I got a boot loop. So I restored from a backup. Then I redownloaded and when I was in my custom recovery I did a factory reset, a cache wipe and a factory wipe. Then I installed CM.
No after like 3 minutes of booting, I got to my homescreen. I think what happened was I wanted to get off CM because it wasn't working right so I tried to boot into recovery so I held down power and volume keys. I got a yellow light then a red light and now bootloader. After deliberation I figured that when I reset factory settings I got rid of the bootloader some how so I googled it. I found smirkit and tried to install a bootloader. After I did that from my phone I powered down my phone and tried to get to the bootloader but I found that I was bricked.
My excuse for all of this stupidity is that it was 6am and I hadn't slept yet. Nothing good happens for me without sleep lol. btw, thats as accurate as I remember.
Alpha-Wat3rloo said:
After deliberation I figured that when I reset factory settings I got rid of the bootloader some how so I googled it. I found smirkit and tried to install a bootloader. After I did that from my phone I powered down my phone and tried to get to the bootloader but I found that I was bricked.
Click to expand...
Click to collapse
What is smirkit? The only hits I could find on it were for the Kindle Fire. It sounds to me like you flashed a bootloader for another device, that would certainly give you a hard brick.
Sent from my Nexus 4
As I suspected, user error.
Sent from my Nexus 4 using xda premium
I don't think you needed to suspect anything. I am admitting that I bricked it and it wasn't a toolkit.... What I needed you to tell me is would it have been recoverable if I used fastboot and not a toolkit. I would appreciate it if you would answer that question instead of needlessly placing blame.
Sent from my Nexus 4 using xda app-developers app
Thank you you've actually helped Mr to figure out why it happened. It was super late/early. Serves me right flashing anything without proper rest.
Sent from my Nexus 4 using xda app-developers app
If you had flashed the wrong bootloader or kernel (one meant for a different device) via fastboot then you would still have a hard brick.
Using fastboot instead of a toolkit does mean you have more control over what your are doing, but you still need to make sure you are still flashing the right things.
Sent from my Nexus 4
Alpha-Wat3rloo said:
I don't think you needed to suspect anything. I am admitting that I bricked it and it wasn't a toolkit.... What I needed you to tell me is would it have been recoverable if I used fastboot and not a toolkit. I would appreciate it if you would answer that question instead of needlessly placing blame.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Your original post made it sound like you used one of the toolkits made specifically for the Nexus 4 and that is what had bricked your phone. It wasn't till half way down the thread you mention you used a tookit for another device. Toolkits are not free from user error even when you use the correct one as you still have to download the correct files and place them in the correct folders. There have been a lot of newbies bricking phones because they have downloaded the incorrect files and then blame it on the developers and or phone for being defective. So this is why people are skeptical when they read these threads.
Alpha-Wat3rloo said:
I don't think you needed to suspect anything. I am admitting that I bricked it and it wasn't a toolkit.... What I needed you to tell me is would it have been recoverable if I used fastboot and not a toolkit. I would appreciate it if you would answer that question instead of needlessly placing blame.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
And that`s what happens when your SMARTphone is Smarter than you.....
How active is the development for this device? is it dying, or is it alive?
I am asking because I might get a Nexus 4. Any advice for a first rom, or rooting procedures?
Man I just switched from a note 2 to a nexus 4 and couldn't be happier besides the battery life. Rom development is amazing and everything is up to date with no wait . nexus is a different breed all together . you won't regret it
Sent from my Nexus 4 using xda app-developers app
juggamonkey said:
Man I just switched from a note 2 to a nexus 4 and couldn't be happier besides the battery life. Rom development is amazing and everything is up to date with no wait . nexus is a different breed all together . you won't regret it
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
I just flashed Faux123 from Franco.kernel I heard both have really nice battery life over stock kernel or even CM's kernel I used to have bad battery until I flashed a custom kernel
Nexus 4 CyanogenMod 10.1.0
And how do I S-off the device? is it easyier, or harder than HTC devices?
Mihir1997 said:
And how do I S-off the device? is it easyier, or harder than HTC devices?
Click to expand...
Click to collapse
LMAO!!
You don't S-OFF a Nexus device, you just unlock the bootloader with fastboot oem unlock and away you go!
Mihir1997 said:
How active is the development for this device? is it dying, or is it alive?
I am asking because I might get a Nexus 4. Any advice for a first rom, or rooting procedures?
Click to expand...
Click to collapse
The development for the Nexus 4 is highly active. It's been alive ever since the Nexus 4 came out. I don't think it'll die anytime soon. The Galaxy Nexus forum is still alive and let's not forget about the HTC Nexus One forum. LOL.
EddyOS said:
LMAO!!
You don't S-OFF a Nexus device, you just unlock the bootloader with fastboot oem unlock and away you go!
Click to expand...
Click to collapse
Seriously? and that means I can just flash a rom without having to fastboot flash boot images ? so basically, after root, I don't need my comp for flashing roms at all?
Mihir1997 said:
Seriously? and that means I can just flash a rom without having to fastboot flash boot images ? so basically, after root, I don't need my comp for flashing roms at all?
Click to expand...
Click to collapse
Unlock the bootloader, flash a custom recovery and from there you don't need your PC at all. Nexus devices are a lot easier than any other type of phone to flash and development will be active for the next few years at the least since it's a Nexus. The biggest disadvantages of this phone (if you care about them) are the lack of removable battery, low storage, poor camera and the glass back. Other than that this phone is one of the fastest available and you won't be disappointed if those things don't matter to you.
Hey guys not affiliated in anyway but jcase in the development thread got root working for att and Verizon through a simple apk on the phone.. Tested and working great hit up his thread more info
Sent from my XT1058 using Tapatalk 4
So does root stick around after a reboot? The moto root app showed I wasn't rooted after a reboot. Just came back from iOS so I'm a little rusty
Let me double check.. Havent rebooted since the app rebooted the phone
Sent from my XT1058 using Tapatalk 4
OK just rebooted and root stuck just fine
Sent from my XT1058 using Tapatalk 4
Its not there immediately takes 5 or so seconds after boot to work.. Jcase is aware of the issue though and working on it..
The only downside with that is something like setcpu not being able to set on boot
Sent from my XT1058 using Tapatalk 4
rcklss1 said:
Its not there immediately takes 5 or so seconds after boot to work.. Jcase is aware of the issue though and working on it..
The only downside with that is something like setcpu not being able to set on boot
Sent from my XT1058 using Tapatalk 4
Click to expand...
Click to collapse
Also effecting the exposed software since if you do a reboot instead of a soft reboot it kills part of the process
With this root method can you use the exposed mods to remove the ATT icon from top left of status bar? Or does that require a flashable zip?
Sent from my Nexus 7
phositadc said:
With this root method can you use the exposed mods to remove the ATT icon from top left of status bar? Or does that require a flashable zip?
Sent from my Nexus 7
Click to expand...
Click to collapse
Check out the motoexposed thread in the android dev section :good:
just being back from IOS, i may hold out on pursuing this till things get ironed out. I installed 1.1 and installed the chainfire su and rebooted to find the andriod on his back with a red exclamation point. Not sure what this meant but rebooted and all is fine so I've restored to factory till future times of solid dev. I donated to jcase so i'll be back once i'm versed in android again.
What in particular was the android pic i saw referencing?
Thanks guys! Good to be back! still getting used to things as you can see
mj0528 said:
just being back from IOS, i may hold out on pursuing this till things get ironed out. I installed 1.1 and installed the chainfire su and rebooted to find the andriod on his back with a red exclamation point. Not sure what this meant but rebooted and all is fine so I've restored to factory till future times of solid dev. I donated to jcase so i'll be back once i'm versed in android again.
What in particular was the android pic i saw referencing?
Thanks guys! Good to be back! still getting used to things as you can see
Click to expand...
Click to collapse
Sounds you like you tried rebooting to CMW or TW recovery. I clicked it to see what would happen and that's what I got. Rebooted normally after that and no issues.
rmead01 said:
Sounds you like you tried rebooting to CMW or TW recovery. I clicked it to see what would happen and that's what I got. Rebooted normally after that and no issues.
Click to expand...
Click to collapse
Good to know I wasn't on the verge of breaking my new moto
Thanks!
How do you go about changing the splash screen on the S4? I came from an HTC One which achieved it through fastboot but to my understanding AT&T's S4 doesn't have fastboot.
P.S I'm not talking about boot animations since a lot of people get them confused lol.
Deleted
Sent from my Nexus 5 using XDA Free mobile app
Kendosis said:
How do you go about changing the splash screen on the S4? I came from an HTC One which achieved it through fastboot but to my understanding AT&T's S4 doesn't have fastboot.
P.S I'm not talking about boot animations since a lot of people get them confused lol.
Click to expand...
Click to collapse
I don't believe you can. I had an HTC before this and a custom splash, but the splash on this one is probably integrated into the bootloader (so it changes with the custom flag).
Sent from my SGH-I337 running BlackBox 3.0
DeadlySin9 said:
I don't believe you can. I had an HTC before this and a custom splash, but the splash on this one is probably integrated into the bootloader (so it changes with the custom flag).
Sent from my SGH-I337 running BlackBox 3.0
Click to expand...
Click to collapse
Aww that sucks at&t really has this device on lock, thanks though probably gonna end up sending back the S4 and try something else.
Well another rom to the collection, so that means finally we have the main roms available so development is on its peak now
Cheers ?
https://plus.google.com/104399241323212354617/posts/goaNRkN4ERm
Prattham said:
Well another rom to the collection, so that means finally we have the main roms available so development is on its peak now
Cheers
https://plus.google.com/104399241323212354617/posts/goaNRkN4ERm
Click to expand...
Click to collapse
AICP isn't available for Taimen just yet.
Prattham said:
Well another rom to the collection, so that means finally we have the main roms available so development is on its peak now
Cheers
https://plus.google.com/104399241323212354617/posts/goaNRkN4ERm
Click to expand...
Click to collapse
Thanks for the info, can't wait.........:good:
ROM is up guys!
Great to see here! Kudos
Anybody been able to get past the boot logo? I've tried 4 times. Always hangs on the boot logo indefinitely. Not frozen, the boot animation is cycling, it just never fully boots.
Namolas said:
Anybody been able to get past the boot logo? I've tried 4 times. Always hangs on the boot logo indefinitely. Not frozen, the boot animation is cycling, it just never fully boots.
Click to expand...
Click to collapse
Nope , same here! Can't get it to boot past boot animation and I started with a clean factory image. Dang
tmoore3496 said:
Nope , same here! Can't get it to boot past boot animation and I started with a clean factory image. Dang
Click to expand...
Click to collapse
Same, I started from a flash-all factory image in both slots. Most interesting part ( to me ) is after the 4th try I flashed only the AICP zip, and not TWRP zip this time. Still wouldn't boot and when I booted back to recovery, expecting the stock recovery, but instead now I have Lineage recovery...
Seems I still have a thing or 2 to learn about this device.
Prattham said:
Well another rom to the collection, so that means finally we have the main roms available so development is on its peak now
Cheers ?
https://plus.google.com/104399241323212354617/posts/goaNRkN4ERm
Click to expand...
Click to collapse
id say its at its peak when we also have pixie dust or w.e and pure nexus roms
Anyone installed this one?....any exclusive features?
amandeepparmar said:
Anyone installed this one?....any exclusive features?
Click to expand...
Click to collapse
To my knowledge nobody has successfully booted it. Won't boot past the boot animation, been trying all night. We are waiting for further instruction from the maintainer.
elliwigy said:
id say its at its peak when we also have pixie dust or w.e and pure nexus roms
Click to expand...
Click to collapse
+1 for Pure Nexus
I got it to boot. I tried mostly what you guys tried. What I did to get it to boot was dirty flash over my previous rom. I had rr before. Make sure you do a backup. I also took off finger prints out any security locks. Also remove any substratum themes otherwise system ui will crash. If you try it, at your own risk.
I forgot to add. I switched slots before flashing.
Sent from my Pixel 2 XL using Tapatalk
Namolas said:
To my knowledge nobody has successfully booted it. Won't boot past the boot animation, been trying all night. We are waiting for further instruction from the maintainer.
Click to expand...
Click to collapse
*fart*
Nochis said:
I got it to boot. I tried mostly what you guys tried. What I did to get it to boot was dirty flash over my previous rom. I had rr before. Make sure you do a backup. I also took off finger prints out any security locks. Also remove any substratum themes otherwise system ui will crash. If you try it, at your own risk.
I forgot to add. I switched slots before flashing.
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
So what do you think? You stick with it? Worth trying?
Namolas said:
So what do you think? You stick with it? Worth trying?
Click to expand...
Click to collapse
Don't know yet if I stay on it. I don't know if worth a try. Most roms have same stuff. I normally try for battery life and volte and wifi calling.
Sent from my Pixel 2 XL using Tapatalk
Can confirm that dirty flash over RR ROM does indeed allow it to boot!
Dirty flash worked like a charm..
Do you need to delete data to dirty boot? Were you still rooted with magisk installed? Thinking by about trying to over stock but wanna be prepared for the worst so have some fresh backing be up to do first. Lol
I dirty flashed, without wiping data on previous rom. I was going to try on stock but didn't want to turn on computer.
Sent from my Pixel 2 XL using Tapatalk