I want to do a custom boot animation using Rom Toolbox. I was told befor I pick a boot animation I need to hit the menu button and then do a back up. When I try and do the back up I get this. (See picture) I dont wanna pick a boot animation until I know 100% how I can go back to the stock boot.
Thanks for the help!
Sent from my SGH-T999 using xda premium
What kernel are you on? If your kernel does not support etc/init.d (ie stock) then you will not be able to put a custom bootanimation in there. That is probably why the toolbox is not seeing your BA to back up.
There is another way (maybe). You can always download a custom BA and drop it in /data/local, set permissions and reboot. It should run that one over the stock BA. It may not though, as I have never tried this one a stock kernel. Make a full nandroid before trying this just in case it doesn't work.
Sometimes I use this method to mess with my wife's phone and drop a new BA in her /data/local and then when she reboots the next time she's like WTF. She is pretty saavy, so it only takes her a minute or so to figure it out and shoot me a text.
Related
Thanks for taking your time and helping me, I saw you guys(and girls) have done some pretty amazing things here at XDA. I just need some help with getting this Gingerbread ROM to work.
I'm using Supersonic 2.2.1 first off, and using the alter. recovery rom from Rom Manager.
Ok, so I rooted my phone using rEVOked and chose a ROM called Bc-Gingerbread-beta4. I'm not sure of the eact title used, but if anyones faimilar with Gingerbread ROMS, they should know what that is... It was on the EVO ROM page.
So at first, I was using ClockWorkMod Recovery (2.6.*) to try and install the ROM. I eneded up with status 7 ever time, so I tried to upgrade to 3.0.* (newest one) and recieved a error about not being able to flash. No details were given.
I tried flashing to the alternate recovery, and it worked. From their, i (un?)successfully installed the ROM according to the recovery application.
The status bar didn't move past the halfway mark, but i figured it was just how it worked..
Then, I tried to boot into the new ROM. I was on the HTC screen for about 3~5 minutes, then it showed me the android load screen instead of the usual Sprint/4G screen. From their, it was in a constant loop because every 3 to 4 seconds, it would take off the android logo, then place it back. I waited approx. 10 minutes... Nothing. Unfortunetly, the alternate screen doesn't have the option to browse for your nandroid back ups (mine aren't in /android) So i'm left with a relativly bricked phone until I can find a working ROM.
I have a microsd card reader.. so I'm not too terribly screwed, I just need help on what I did wrong, how can I fix it (if im able to), and what Gingerbread ROM I should use. It needs to be relativly stable. I don't care about 4G support, even though its almost everywhere in Atlanta. I'd like to have video rec. if possible. and 8MP support.
If it fits those standards, please, I'd like to hear what the community thinks is a great Ginger ROM.
Also, I'm using Windows. I have the adb shell installed, and im familair with basic-medium level terminal commands.
Edit: I'm going to flash again, using cm_supersonic_18.zip. It says installing update, but it says flash zip from sdcard in the main menu...
Edit #2: apparently it's a Cyanogen mod (#7)
Just keeps looping the android on the skateboard screen... I'm going to figure out how to get back to the clockwork recovery console and -hopefully- get this thing working.
So... I seen baconbits shortly after rooting and flashing, I installed baconbits, phone booted, than right from start up I get forceclose on every app and process... than I tried to do a backup, I got an error on cwm so than I wiped data and tried to reflash fresh and start over, that would not work. So I recovered the stock froyo and fixed cwm than I flashed fire and ice cm7 rom.. everything has been fine since I fixed it.. it was still frustrating tho..
But when ever I go to my boot loader before recovery, I get this green font that says blah blah blah not found (its trying to locate files to install that stock froyo, but after it doesn't locate the file I'm free to access recovery or do whatever.. is there a way to delete that "cannot find" ****, it takes about 20 seconds from holding power and volume down to give me control.. that's why I want it gone its annoying.. even if I can't fix it, I guess its not a major setback..
melodicjunkie said:
So... I seen baconbits shortly after rooting and flashing, I installed baconbits, phone booted, than right from start up I get forceclose on every app and process... than I tried to do a backup, I got an error on cwm so than I wiped data and tried to reflash fresh and start over, that would not work. So I recovered the stock froyo and fixed cwm than I flashed fire and ice cm7 rom.. everything has been fine since I fixed it.. it was still frustrating tho..
But when ever I go to my boot loader before recovery, I get this green font that says blah blah blah not found (its trying to locate files to install that stock froyo, but after it doesn't locate the file I'm free to access recovery or do whatever.. is there a way to delete that "cannot find" ****, it takes about 20 seconds from holding power and volume down to give me control.. that's why I want it gone its annoying.. even if I can't fix it, I guess its not a major setback..
Click to expand...
Click to collapse
thats internal feature of Hboot... it looks for pc10img.zip on sd card.... not at all an error....
and it can be useful in a situation where you mess up your recovery and rom ... you would be able to save your phone via that ....
also its used to go back to stock rom and unroot when needed
+1 for hispeedword. Best possible answer right there - that's exactly what's going on. Use ROM Manager to reboot straight to recovery from now on and it will skip HBOOT so you don't have to wait through all of that. CM and most other roms also allow that option when you hold down the power button.
Now, you said "shortly after rooting and flashing" - what exactly did you flash? You do know baconbits is ONLY meant to be used with the stock rom right? The exact one that you rooted and that came on your phone. If you flash ANY other rom - even a 'stock rooted rom' then you run into tons of errors when flashing baconbits.
Dont flash baconbits, its not needed
Sent from my HTC Vision using XDA App
TheMod'sPolice said:
Dont flash baconbits, its not needed
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
Yeah I was being stupid, I didn't even know at the time when my phone messed up that it was from me flashing baconbits...until I did a back up, than flashed a different rom and reflashed baconbits, lmao..
so your saying to use baconbits if you rooted but didn't flash custom roms, than it works fine?
I'm thinking of switching to a sense rom, I don't even know why.. what are the pros/cons of sense? Thanks.
Assuming you've already answered your question up there, sense roms usually consume more battery life because of the plethora of constantly active widgets. However, if you're VERY social or buisiness, Id recommend it. The battery drain only cuts down on a few hours, depending on your usage, cpu governers and radio, and for that, you get a lot of functionality from the rom. Plus the new elegant blues ported theme for sense roms is just gorgeous. I also like the whole manual link to facebook in the contacts. Still hoping for a port for that xP try it out.
Sent from my HTC Vision using XDA Premium App
On both Blazer (w/ rogue and Lost Kernel) and Calks 2.0 (only tried rogue) whenever I reboot my phone nine times out of ten, it hangs on the lockscreen with a random date and random time flashing back and forth between no signal and the regular status bar symbols. It is unresponsive to touch and repeats the process of the keys lighting up, screen comes on for about 4 seconds, keys turn off, screen turns off. Repeat... If I hit the power button, the pop up shows up but I can't touch anything so I end up having to do a battery pull and reflash the rom. I've re-downloaded both roms to rule out a bad copy. I over-wipe every time I flash a new rom formatting system, wiping data, cache, and dalvik, and then flashing Calk's format all.
I messed with it last night and it seems pretty random but more often than not, it happens. If I try to restore a nandroid I had made recently, it does the same thing. In other words, there were multiple instances where I flashed the rom, got it set up, booted to recovery to make a back up, and then it wouldn't boot back up NOR could I get my back up to boot up.
What in the hell could be causing this??? Please and 1000 thank you's!!!!
First of all, sorry to tell you I don't have the answer.
I have this exact same issue and have tried almost everything you have tried, (I didnt have a back up since I just got this phone not too long ago).
My issue started at work when my battery died really fast in the middle of the day after being fully charged. The phone got hot and I just pulled the battery to stop it. Then I came home and am having this exact same issues.
I've spent the last few hours working on resolving this without success. Hopefully someone out there knows how to resolve this issue.
Edit: I am on Rogue recovery 1.10 (cmw v 5.6.2.7) and on Blazer ROM [11/26/11] [v1.2]
Might be the rom since we are both on Blazer...Im gonna try another. Hmm we are on the same recovery too!
Thanks!
Why not flash back to stock and start over?
Sent from the future.
FIXED!!
I've got it working finally. For me, I just had to check Go Launcher as my default launcher. Now when I reboot, it loads up just fine. I guess it was hanging when it tried to open up the pop-up where you select your launcher if you have more than one and don't have one set as default. So, to the few people affected by this, set your favorite launcher as default and give it a try. Thank you to everyone for all of the suggestions.
VegasEvo4G said:
I've got it working finally. For me, I just had to check Go Launcher as my default launcher. Now when I reboot, it loads up just fine. I guess it was hanging when it tried to open up the pop-up where you select your launcher if you have more than one and don't have one set as default. So, to the few people affected by this, set your favorite launcher as default and give it a try. Thank you to everyone for all of the suggestions.
Click to expand...
Click to collapse
Yes this has been an ongoing issue and posted in a few places. Also remember that when Go Launcher updates this may happen to you again. You can always use adb and push a launcher over to your phone incase you find yourself stuck like this again. Or delete launchers so there is only 1 choice
I finally got rid of this loop. I was able to flash a rom via the recovery menu in clockworkmod, since for some strange reason it won't recognize my sd card now.
Playya, so if I wanted to push a recovery on my phone (I have clockworkmod v. 4.015 installed but it won't recognize the sd card no matter what I do to it), can I do this from Root Explorer? ADB? What commands would I use? I am on Linux and am looking for a guide. Thanks.
In the past couple of weeks I had jedi 3.x rom installed on my i317 from att, with asylumcore kernel at 1.92ghz overclock and no fsync(). Had it fully themed from various theme mods around the forum and everything was running great till i found a AOSP lockscreen mod that i decided i really wanted to put on here. I flashed the mod and my phone would load up show the TW lockscreen for 1 second then reboot again over and over. I was stupid and did not make a backup before flashing the lockscreen. could not get phone to stop resetting w/o pulling battery. after flashing the new jedi rom and kernel my phone still continued to bootloop, but without ever getting to the bootanimation. I had a cm rom on the sd card that i kept to try on a "rainy day". after flashing that the phone was able to fully boot and was working but this rom is very buggy for me. i realized that i had forgot to format /data before or after flashing and thought this could be the issue. went into recovery and now every time i try to format it the recovery reboots. tried flashing teamwinrecovery and it only loads the splash image then a blank screen. So i went back into cm and used the app Rom Toolbox Pro to see if it could clear out all of /data, and mentioned that my version of cwm had to be done with rom manager but with the option to try anyway? i answered yes. phone booted into recovery and now automatically tries to clear /data but keeps rebooting and repeating the process. Now i can't flash anything becuase rom toolbox is automating the whole thing.
So I ask, does anyone please know of anyways that i can mount my phone to my computer for editing without being booted up into the rom or recovery? or is there a way to use Odin to somehow clear all the partitions so that i can start new?
Sorry for long post but right now my phone is a $650 brick.
U just answered ur own question.......odin bacjk to complete stock
Sent from my SAMSUNG-SGH-I317 using xda premium
I live outside of any major city and the only real internet i could get was through my phone via tethering. so i was on dialup to even write the previous post. But I went into town and borrowed the local restaurant's cable internet and downloaded the stock firmware and I believe everything is in working order
Hello, im new to android and im inexpert, tryed to change the default boring boot animation, using an app called something like "Bootanim mod" downloaded from blackmart.I Applied a cool animation, the phone restarted, and now shows the logo, the boot music, the animation i put (with very bad resolution) and nothing more. Black screen. Please help me i have very important things inside the phone i dont want to lose.
The phone is rooted, could i backup the entire content in some way?
You were suppose to backup your content BEFORE you made such change. Idk if it'll work but are you running custom rom? Maybe dirty flash over it. Wait for some more insight. Maybe someone can chime in with better knowledge.
Sent from my SGH-T999 using xda app-developers app
Do you have custom Recovery ? If yes then you could copy original Boot animation back and then Set permission correctly. The app may haver missed setting permissions correctly or may be the boot animation be coded incorrectly.
Please reflash existing Rom.