Develop Bugs

How to get boot manager working??

Hi, I'm going mad because I can't get boot manager to work with the roms I want! I want to run virtuous quattro ics beta as my phone rom and smartdroid 3.1 T in slot 1. I've done everything but everytime I install smartdroid to slot 1 it hangs on the HTC white splash screen. I installed blackice and it worked just fine. I have forced large .imgs but it wont work. I think it may work through restoring nandroid but I don't get how I would do that?? Any help would be nice, spent the last 2 days trying to work it
Sent from my Desire HD trying to get boot manager to work -_____- using XDA App

Some ROMs have things in the updater-script that won't work correctly when flashing them to a Boot Manager slot.
What I do is this:
1) Make a nandroid backup of my main ROM.
2) Fully wipe the phone and install the new ROM.
3) Make a nandroid backup of the new ROM.
4) Restore the first backup of my main ROM.
5) Go into Boot Manager and install using the nandroid of the new ROM to one of the slots.
There are also some pre-made nandroid backups in this great thread by SmokeyMcBong. In the last few pages there are also some good tips on how to get around various problems:
http://forum.xda-developers.com/showthread.php?t=1257450
Hope that helps!

So basically I'm on rcmix 4.0 right now and have a nandroid backup already
I should wipe and flash smartdroid
Make a nandroid backup of it through recovery
Restore my backup of rcmix
Go into boot manager and restore nandroid of smatrdroid to one if the slots??
Sent from my Desire HD using XDA Premium App

Yep, that's how I've done it in the past - use the Install Zip option then Restore Nandroid. There's also some stuff in the thread about problems when using wifi and things working better using mobile data.

when u say use the install zip option and restore nandroid....isn't there a seperate option which is restore nandroid?? Shouldn't i do that instead....screenshot attached of what i mean
{
"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"
}
And i read about data but I'm on pay as you go and not with any contracts so i can't use that much data at once otherwise i will run out of credit
Sent from my Desire HD using XDA Premium App

Yep, the screenshot shows the option I mean - it's the restore nandroid option on the install zip menu.

Phone won't boot

I turned off my phone (vzw galaxy nexus) today to replace the battery and it wouldn't boot back up. It was stuck on the Google screen. I've tried almost everything i could think of. I was running AOKP jb build 4 at the time with imo's lean kernel. I've tried doing restores and installing fresh aokp b4 and ics milestone 6 ROMs. The ics rom/restore goes into boot loop and any jb rom/restore gets stuck at Google.
A few odd things i did notice was that the first time i tried to wipe dalvik cache, cwm recovery was frozen for a few minutes and i had to battery pull but after that it was able to wipe it quickly. Another thing is when i restore my backups, there is a error in restoring /data.
{
"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"
}
Anyone know any fixes? I haven't tried installing a stock image yet since I'm not home but the situation doesn't look good.
Sent from my SCH-I535 using Tapatalk 2

How long did you let it sit at the Google screen? If an 'improper shutdown' is detected (no idea what constitutes improper), the JB boot loader does a full scan of the file structure to make sure everything is intact. I've had it take several minutes now and then, and others have reported longer before the Nexus animation begins.
Sent from my Galaxy Nexus using xda premium

I let it sit for a couple of minutes, but oh well i fixed it by flashing a stock Google image. Thanks for the suggestion though.
Sent from my SCH-I535 using Tapatalk 2

Impossible to brick Nexus,always there is a way to revive your phone .

youll have to flash factory image via fastboot to get it to work again
you can pull your sdcard data in recovery to your pc because after flashing via fastboot youll lose all your data even the sdcard data

Cleaning up Custom Kernel flashes

Okay lets say im on stock everythings 100% stock and i want to flash a custom recovery kernel that has init.d support, custom boot ani support, and add blocking ect..... ok so i flash it lets say........then i lets say i revert back to my stock recovery and kernel......okay now here is the question.......is there anyway i can clean up what the custom kernel installs? Is there a need to clean up? I want to add my own tweaks so i dont want anything bumping code or have multiple code in my phone i want it nice and clean.
Thank you

Your question is confusing but bottom line if you want to start fresh do a clean installation.
Why anybody here would want a stock setup is beyond my comprehension.

Exactly my point i want it fresh and ill do my own thing but i need these custom recovery kernels to gain root or when i need to flash a zip in cwm so after im done kernel riding somebody else is work please take all the belonings with you brought with you when i flash you out. Its in view of my comprehension that these builds dont have a fresh way to gain root access for example like using one click root or an apk to root. they made them in the past before for us sgs2 users.
Sent from my SPH-D710 using Tapatalk

No4g4Me said:
Exactly my point i want it fresh and ill do my own thing but i need these custom recovery kernels to gain root or when i need to flash a zip in cwm so after im done kernel riding somebody else is work please take all the belonings with you brought with you when i flash you out. Its in view of my comprehension that these builds dont have a fresh way to gain root access for example like using one click root or an apk to root. they made them in the past before for us sgs2 users.
Sent from my SPH-D710 using Tapatalk
Click to expand...
Click to collapse
Use a pre-rooted Odin one click and you get root w/o recovery. There are rooted 1clicks all the way thru fi27. If u use a no-data version all your apps and settings will remain after flash.
{
"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"
}

Ok now I understand a little more what you want. I think you should spend more time reading and browsing the development sections for more info. I think Agat63 has been packaging stock kernels lately for those who prefer this.

lol yea.. theres plenty of ways. ifor one use mobile odin whenever i need to fllash a kernel.. you can switch between all the kernels you want and maintain root
Sent from my SPH-D710 using XDA

[Q] Weird graphical glitch.. [ROM][March10][Kitkat] Beanstalk | Release 3.5 | bravo

Every time i go to install [ROM][March10][Kitkat] Beanstalk | Release 3.5 | bravo the install in recovery "succeeds".
When I reboot from recovery, I see the screen for a split second, then a few lines of horizontal color and then it goes black. I can see that it is backlit because of the slight glow. I have no control and end up pulling the battery and restoring from a backup.
Recovery: TWRP Version 2.6.3.0
I had this problem with Release 2 but kept trying and it finally took. Doesn't seem to want to go this time..

Try updating to my newer twrp build.
Sent from my HTC Desire using xda app-developers app

Will do. I'll let you know.

I don't know man. Never had this problem before.
{
"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"
}

oneBuilder said:
I don't know man. Never had this problem before.
View attachment 2625452
Click to expand...
Click to collapse
Others are having this issue as well. I think my recovery is too close to the max size allowed on the recovery partition.
Im going to try to trim it down and rebuild in a few minutes.
In the meantime you could try using 4ext recovery. Its always very reliable for me.

Thanks. I'll give it a try when I get some time.

oneBuilder said:
Thanks. I'll give it a try when I get some time.
Click to expand...
Click to collapse
I uploaded the smaller version which should work.
Sent from my HTC Desire using xda app-developers app

This is very strange indeed.
I never was able to get either Beanstalk 3.5 or TWRP 2.7 to load up. I follow your build threads and saw that you released Beanstalk 4.
I decided to try and flash it, using TWRP v 2.6.3.0 and surprisingly it worked without a hitch.
Dirty flashed to 4.5 and it's running awesome now.
I've flashed quiet a few ROM's and I've never experienced this kind of thing before. I tried to install 3.5 at least.....5 times without success.
I'm just happy it worked with this version. Excellent ROM!
Just figured I'd post this for some info and closure on this thread.
Thanks for your help. Keep up the fantastic work.

[Q] Can you turn off the boot sound?

Anyone know if it's possible to get rid of the T-Mobile sound on boot? I'm rooted with a custom recovery but unable to get s-off if that helps anything.
Sent from my HTC One_M8 using XDA Free mobile app

{
"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"
}
Just name both files .bak at the end or just delete the 2 all together with your favorite root explorer.
Sent from my HTC One_M8 using Tapatalk

Should we delete the whole animation, or just the two jingle files at the top of the list?

GinoAMelone said:
Should we delete the whole animation, or just the two jingle files at the top of the list?
Click to expand...
Click to collapse
I'm thinking Just the jingle files. Deleting the whole animation would probably leave you with the classic, metallic "android" boot animation, as the T-Mobile part was probably just packed in to the original animation...
For safety reasons, I would do the "bak" thing, that way you still have easy access to those files if something goes wrong.
Sent from my HTC One_M8 using Tapatalk

Thanks for this. For some reason when I tried renaming the files with root explorer it looked like it worked but after reopening the app the files had reverted back to their original filenames. No idea what's going on with that. I ended up going into TWRP and renaming there which worked.
Sent from my HTC One_M8 using XDA Free mobile app

ag3mo said:
Thanks for this. For some reason when I tried renaming the files with root explorer it looked like it worked but after reopening the app the files had reverted back to their original filenames. No idea what's going on with that. I ended up going into TWRP and renaming there which worked.
Click to expand...
Click to collapse
Since you are s-on, you can't make directly make system changes while booted to OS. All changes will be reverted because you actually are not writing to system, it only appears that way. HTCs kernel provides system rw protection which prevents modification to system partition. You have three options, flash a custom kernel, use flar2s system rw mod, or reboot to twrp recovery and make changes using its built in file manager (changes made while in recovery will stick).