Database Develop

[RECOVERY] Boot Menu Manager[APP]

ALL OF THIS WORK IS DONE BY whirleyes! PLEASE CREDIT HIM AND NOT I. LINK OF HIS THREAD IS BELOW!
http://forum.xda-developers.com/showthread.php?t=2005187
Same exact thing , compatible with the Droid 4 and tested out on my Droid 4 and works fine. All I did was uninstall safestrap and simply install this app from playstore
Playstore link: https://play.google.com/store/apps/details?id=com.projectlense.bootmenu.manager&hl=en
As usual I'm not responsible nor the developer of the app is responsible for any damaged to your device.
What is Boot Menu Manager?
Well boot menu manager is practically a custom recovery (not going over the system recovery) that launches a screen at each boot asking for rom you want to boot. There are 6 slots and you can edit the system slot, although please remember when entering the recovery, do switch to rom slot 1 if you don't want to mess with system, if you don't you'll edit your stock system.
As this recovery is discontinued, it does support 4.3 and other Roms. I haven't go to mess around with all the apps but it works just fine. Sometimes by entering the recovery there is a slight delay. The Recovery seems to optimize kexec better and handle Roms a bit better, but that's just in my experience.
ALL OF THIS WORK IS DONE BY whirleyes! PLEASE CREDIT HIM AND NOT I. LINK OF HIS THREAD IS AT TOP OF THREAD!

Sorry to dig up old threads, but Safestrap will not work for me. My phone gets stuck at a certain point in the install (60/100) and then just hangs.
I was told that this might be an alternative method to get a Custom ROM on my Droid 4.
Is there a version out there of BMM that I can use?

@joefuf Yep, but
Do you have root?
Fervi

ferviverus said:
@joefuf Yep, but
Do you have root?
Fervi
Click to expand...
Click to collapse
Yeah, I do. I found BMM 0.3.4 and installed that. I managed to get a good updater-script to allow my ROM to be flashed onto my Motorola Droid 4 in System 1.
Is there another version I should be using? It was tough to find v0.3.4.
Unfortunately, I am still experiencing a lot of lagging and slow response from my ROM. Is this common with BMM? Is there anything I can do to optimize the ROM? Should I install my ROM somewhere other than System 1?

@joefuf
Eee, System 1 is on top-right?
If it is top-left, you probably delete stock rom (if u install CM or other ROM)
Fervi

ferviverus said:
Eee, System 1 is on top-right?
If it is top-left, you probably delete stock rom (if u install CM or other ROM)
Fervi
Click to expand...
Click to collapse
System 1 is top-left. I know that I deleted the Stock ROM. It's running fine and reboots into System 1 fine. The ROM just runs very slow. Do you know how to fix it?
Is there a better version of BMM than 0.3.4?

@joefuf
Well, BMM is unsupported (dead)
Technically special version of safestrap or BMM is to install system on "hidden Droid partitions", and u have 2 systems
Probably it's bugged rom, because CM works really fast
Fervi

[Q] eclipse 2.1 rom?? question

hello, i have locked moto and wonder do i need 4.2.2 root to install this rom or 4.4 cause i get bootloop after installing the rom.

Are you currently running jellybean? Sounds like you are not running the KitKat kernel.
Sent from my XT1060 using Tapatalk

Same Bootloop
Hey Nitro,
Moto X VZW Dev.Ed.
Unlocked BL
TWRP 2.6.3.1
Stock rom 4.4.2
SuperSU
Rom Toolbox Pro for my needs
Had Eclipse installed and was running great. Screen started to flash between operations and loading apps. Thought it was just a misbehaving app, deleted everything I installed and it kept happening. Reinstalled the Eclipse ROM, no-joy. So I brought the phone back to complete stock. I was running on stock for about a week, the OTA came for 4.4.2 and I took it.
Flashed TWRP and installed SU again. When I go to install Eclipse 3.3.2 it shows that everything is loading correctly (love the "mounting your system like a horse"). When it restarts itself it gets stuck in a bootloop with just the Eclipse image. I've left the phone alone for a half hour at a time and it never completes (at 45 minutes on the latest install attempt). Downloaded from the primary and mirror and tried those, same issue, tried it dirty at first, then wiped the dalvik/cache. I've read the main ROM thread - nothing that I could find where someone got stuck in a bootloop like this. Just wanted to pick your brain and see what you thought.
^^^It's long, my bad. I just wanted to make sure you had every detail possible.
Really appreciate it, it's a great ROM when I don't jack things up.

d33pblue said:
Hey Nitro,
Moto X VZW Dev.Ed.
Unlocked BL
TWRP 2.6.3.1
Stock rom 4.4.2
SuperSU
Rom Toolbox Pro for my needs
Had Eclipse installed and was running great. Screen started to flash between operations and loading apps. Thought it was just a misbehaving app, deleted everything I installed and it kept happening. Reinstalled the Eclipse ROM, no-joy. So I brought the phone back to complete stock. I was running on stock for about a week, the OTA came for 4.4.2 and I took it.
Flashed TWRP and installed SU again. When I go to install Eclipse 3.3.2 it shows that everything is loading correctly (love the "mounting your system like a horse"). When it restarts itself it gets stuck in a bootloop with just the Eclipse image. I've left the phone alone for a half hour at a time and it never completes (at 45 minutes on the latest install attempt). Downloaded from the primary and mirror and tried those, same issue, tried it dirty at first, then wiped the dalvik/cache. I've read the main ROM thread - nothing that I could find where someone got stuck in a bootloop like this. Just wanted to pick your brain and see what you thought.
^^^It's long, my bad. I just wanted to make sure you had every detail possible.
Really appreciate it, it's a great ROM when I don't jack things up.
Click to expand...
Click to collapse
Did you do a factory reset wipe? Also, are you running the 4.4.2 kernel?
Sent from my HTC6525LVW using Tapatalk

Info
nitroglycerine33 said:
Did you do a factory reset wipe? Also, are you running the 4.4.2 kernel?
Sent from my HTC6525LVW using Tapatalk
Click to expand...
Click to collapse
I did not do a factory reset wipe the first time. I did the second time. Same situation.
The kernel I'm using is:
3.4.42-g3385454
- Jan 23 17:09
System Version:
164.55.2.ghost_verizon.Verizon.en.US
Build #:
KXA20.16-1.25.2
I appreciate you taking the time out to look at this, thank you.

Nexus 6 boots into TWRP when trying to install system update?

I recently rooted my Nexus 6 and a few days ago I got the notification for the January security patches. When the phone downloads them and reboots, instead of showing the Android Mike update screen it boots into TWRP. I've poked around in the TWRP settings and checked the logs and I've had no luck. I did some research as well and haven't come across anyone else having this issue. This doesn't happen on my GS2 when I install a Cyanogenmod update. Why is this happening and how can I fix it? Thanks!

You cannot apply Google OTA updates with a custom recovery. Replace your recovery with the stock version and try again.

Not just custom recovery - any system change such as root will stop the OTA. Depending on how you rooted, you might be able to unoot using the built-in SuperSU function (I'm guessing Supersu?) but more likely than not it still won't work.
The simplest thing to do is forget about the OTA entirely. Download the full ROM from Google, unzip it, unzip the zip inside the zip, and there you'll find system.img, which you can flash in Fastboot, then reroot. Done.

sonic2kk said:
I recently rooted my Nexus 6 and a few days ago I got the notification for the January security patches. When the phone downloads them and reboots, instead of showing the Android Mike update screen it boots into TWRP. I've poked around in the TWRP settings and checked the logs and I've had no luck. I did some research as well and haven't come across anyone else having this issue. This doesn't happen on my GS2 when I install a Cyanogenmod update. Why is this happening and how can I fix it? Thanks!
Click to expand...
Click to collapse
How did TWRP ended on your phone in the first place?

istperson said:
How did TWRP ended on your phone in the first place?
Click to expand...
Click to collapse
I installed TWRP.
Thanks for the suggestions everyone!

sonic2kk said:
I installed TWRP.
Thanks for the suggestions everyone!
Click to expand...
Click to collapse
Oh, then as other people said, if you want OTA then totally unroot it, then reflash system of the current version, and flash stock recovery. But it's much better when a new version arrives, just download it, flash system and boot, reroot it, clear cache and dalvik. This way you'll have your updated Android days or even weeks before the OTA.

Extremely Long Boot Times In Custom Roms

Hi, I recently bought a Droid Turbo, and had the bootloader unlocked by Sunshine. The phone works wonderfully, but I'm having a few issues. Most notably, it takes ages(over 15 minutes) to boot when I'm using a custom rom. I'm specifically trying to use AOKP Android version 7.X. I've tried clearing cache, clearing ART cache, clearing modem, factory resetting, reflashing system, and nothing seems to be fixing it. At first I thought it was the ROM's fault, like maybe it was a common issue with the ROM, but I flashed Bliss to it, and had the same issue. One thing I should note is that it doesn't take very long to boot into the stock Verizon rom. Another issue I'm having is sometimes the orientation sensor doesn't work, It's not that big of a deal, but I thought it would be a good idea to include it. I remember my LG G2 having a similar issue because I had the wrong bootstack flashed, but I'm not sure if a similar context applies to the Droid Turbo.

Are you using the very latest modded TWRP from @bhb27? Not the crap from the official TWRP website, but from our official TWRP maintainer? 3.1.1_mod2 is the latest right now.
He knows what's best for our Quarks (he's a recognized XDA dev) and although he got us official status with TWRP over two years ago, for some reason they won't post TWRP with his tweaks that work best with custom ROMs. Some people using official TWRP can only boot to recovery, their phone won't even boot to their ROM directly. I helped someone with that just this week.
So, we ignore the official TWRP website and download his modded TWRP. This is the one you should be using:
twrp-3.1.1-mod_2-quark.img
https://androidfilehost.com/?w=files&flid=39562
If you are using that, then I don't know. You could also try other ROMs just to see. AOKP is in the top three, in my opinion, but wouldn't hurt to test with something else.
[ROMs][Quarks][List for Moto Maxx and Droid Turbo]

recovery-safestrap

This is how alot of phones with locked bootloader get custom recovery and roms
https://github.com/mohammad92/recovery-safestrap
This is safestrap 3.1.1 I think versions going up to 4, but this one listed was the last updated. We just need to get someone to build for our device.

DroidisLINUX said:
This is how alot of phones with locked bootloader get custom recovery and roms
https://github.com/mohammad92/recovery-safestrap
This is safestrap 3.1.1 I think versions going up to 4, but this one listed was the last updated. We just need to get someone to build for our device.
Click to expand...
Click to collapse
Safestrap was patched long ago. Its a waste of time.

There is newer versions of safestrap, we can write over the recovery I have done it with enyox version of twrp it doesnt boot but it flashes with flashfire,
we can also set selinux to permissive I believe this is all we need to get a safestrap to work. booting normaly might not work, might have to boot into "recovery mode"
everytime and let the safestrap boot into system for a custom recovery and roms to work, but it is a possibility.
there is also a newer similar version of recovery like safestrap called Fish I believe
someone should look into Fish and or at least compile a safestrap version before you go and say its not possible.

DroidisLINUX said:
There is newer versions of safestrap, we can write over the recovery I have done it with enyox version of twrp it doesnt boot but it flashes with flashfire,
we can also set selinux to permissive I believe this is all we need to get a safestrap to work. booting normaly might not work, might have to boot into "recovery mode"
everytime and let the safestrap boot into system for a custom recovery and roms to work, but it is a possibility.
there is also a newer similar version of recovery like safestrap called Fish I believe
someone should look into Fish and or at least compile a safestrap version before you go and say its not possible.
Click to expand...
Click to collapse
There are newer version but for old hardware. The exploit safestrap used in the first place was patched on lollipop. It won't work on versions after that. Unless it's been renamed. But safestrap is not for newer devices. It won't work.

Ive tried fish already. It kinda works. Kinda not though. Cant get it to load the new ramdisk.

If anyone was looking here is the note 8 kernel released by Samsung
http://opensource.samsung.com/reception/receptionSub.do?method=sub&sub=F&searchValue=N950
N950U is on the second page

I also noticed that if you use flashfire you can flash over the boot.img and system.img,
I know someone will say it's because I used a boot.img from an update.zip, but you need to realize that the flashfire apk doesn't check a signature so it can't tell if it was a custom boot.img or a stock boot.img
I also noticed in the root directory a default.prop file that shows oem_unlocked=1
I have the snapdragon with stock rooted firmware.

Safestrap? Wow. Talk about a flashback to the Droid Razr days.
I bet we will soon see a "Help! I Bricked my Note 8!" Thread from the OP soon. LOL

Lol nope I am not going to brick my phone
Sent from my note 8

I was waiting to get another Note 8 that I could chance bricking...but haven't jumped on it yet...I was trying some of the same and almost bricked my main device so I took a breather...it would be nice...the unlock tools also show that we have oemunlock=1...it's pretty neat but so far away...