Develop Bugs

[RELEASE] Bandroidx's Bravo Bootstrap Custom Recovery

Ok all, waiting is finally over. Thanks for being so patient! I got the donate version up on the market, if you dont have the market in your country or can't make the purchase I will have a free version out (w/ banner ads) in a couple of days once I finish testing that version.
https://market.android.com/details?id=com.bandroidx.motobravo.bootstrap
Couple of notes:
1) When you hit the bootstrap button the first time, it could take a few seconds, wait until you get a success message before touching the screen again. if you get a force close message, please select wait. Usually it takes just 3-5 seconds. It can take longer though especially if you have just rooted, i recommend rebooting after rooting always.
2) After you bootstrap recovery you do not need to bootstrap again until you update to a new version of my app, after upgrading you should bootstrap once. After that you just load the app and hit reboot recovery.
3) If you are not familiar with the bootstrap process (like on the dx/d2) please be aware this does not replace your stock recovery like regular CWM. The Custom recovery can only be started by loading the app and clicking bootstrap recovery.
4) Tested more on 2.2 but 2.1 should also be fine if you havent upgraded yet (why?)
Heydabop is working on his CWM flashable boot animation and I am going to start looking into doing a bravo ROM. Thanks for all heydabop's awesome graphics!
Enjoy!

bandroidx said:
Ok all, waiting is finally over. Thanks for being so patient! I got the donate version up on the market, if you dont have the market in your country or can't make the purchase I will have a free version out (w/ banner ads) in a couple of days once I finish testing that version.
https://market.android.com/details?id=com.bandroidx.motobravo.bootstrap
Couple of notes:
1) When you hit the bootstrap button the first time, it could take a few seconds, wait until you get a success message before touching the screen again. if you get a force close message, please select wait. Usually it takes just 3-5 seconds. It can take longer though especially if you have just rooted, i recommend rebooting after rooting always.
2) After you bootstrap recovery you do not need to bootstrap again until you update to a new version of my app, after upgrading you should bootstrap once. After that you just load the app and hit reboot recovery.
3) If you are not familiar with the bootstrap process (like on the dx/d2) please be aware this does not replace your stock recovery like regular CWM. The Custom recovery can only be started by loading the app and clicking bootstrap recovery.
4) Tested more on 2.2 but 2.1 should also be fine if you havent upgraded yet (why?)
Heydabop is working on his CWM flashable boot animation and I am going to start looking into doing a bravo ROM. Thanks for all heydabop's awesome graphics!
Enjoy!
Click to expand...
Click to collapse
Wow, this will change everything for sure! Great job

Any screenshots. I am getting some info together from the x10 guys. When I get all my stuff together I will probably need your assistance band.
Sent from my SEX10 using XDA Premium App

zax10 said:
Any screenshots. I am getting some info together from the x10 guys. When I get all my stuff together I will probably need your assistance band.
Sent from my SEX10 using XDA Premium App
Click to expand...
Click to collapse
just search the market for bravo recovery, it has 2 screen shots.
as for the X10, no problem let me know.

Works fine! Great app! Feels good to be able to nandroid

Thanks!
PS everyone, http://forum.xda-developers.com/showthread.php?p=13183184
that thread is my development thread, will have my rom development, etc. This will just be a release thread (for those who look in this sub forum for this, it makes sense)
but to keep the development comments together, we will post mostly over in that thread not this one.
feel free to post specifics related to this app here if you want, i monitor both threads.

bandroidx said:
Thanks!
PS everyone, http://forum.xda-developers.com/showthread.php?p=13183184
that thread is my development thread, will have my rom development, etc. This will just be a release thread (for those who look in this sub forum for this, it makes sense)
but to keep the development comments together, we will post mostly over in that thread not this one.
feel free to post specifics related to this app here if you want, i monitor both threads.
Click to expand...
Click to collapse
Once again I feel cheep. Is there any other way to get this app? I'm 16. I've got no credit card yet...I should mail you $20 for all the work you've been doing...give me an address and I'd do it. If I had a credit card I'd be giving a lot of money to you and a ton of other devs.

bandroidx said:
I will have a free version out (w/ banner ads) in a couple of days once I finish testing that version.
Click to expand...
Click to collapse
This is something new…

Hope it goes up soon. I'm 16 and I've got no credit card. I'm dieing to test some things.

I bought it, but I don't know how to access CWM :/
I'm lame.

hippyman said:
I bought it, but I don't know how to access CWM :/
I'm lame.
Click to expand...
Click to collapse
download the rom to the sd card.
open my bravo recovery app
click "bootstrap recovery" and wait until it says success.
then click reboot recovery.
then it will reboot into cwm. then choose to install a zip from the sdcard using vol up and down to move up and down, and use the menu button on the front to select the option you want and use back to go back.

I clicked on backup and restore, was that the right thing to do to do a nandroid backup?
It's frozen on a black screen. :/

I hit home button, which led to random screen. Sorry. I'm new to using roms, if you havent noticed..

hippyman said:
I hit home button, which led to random screen. Sorry. I'm new to using roms, if you havent noticed..
Click to expand...
Click to collapse
actually that brings up a good point, the home button toggles the screen on and off. this is useful for rare cases where the recovery starts with the screen off, etc. its also good if you are going to be working in adb in recovery for a while because it will drain battery fast, turning off the display may help a little.

bandroidx said:
I will have a free version out (w/ banner ads) in a couple of days once I finish testing that version.
Click to expand...
Click to collapse
Look's like free version is very unstable for now

Cka3 said:
Look's like free version is very unstable for now
Click to expand...
Click to collapse
I think he got caught up in ROM dev and such, but IIRC, he was close to finally having a market version.

I wonder when the add version will be out. I don't have a card lol.

bandroidx said:
in a couple of days once I finish testing that version.
Click to expand...
Click to collapse
Testing...1...2..3

BravoMotorola said:
I wonder when the add version will be out. I don't have a card lol.
Click to expand...
Click to collapse
cka3 said:
Originally Posted by bandroidx
in a couple of days once I finish testing that version.
Testing...1...2..3
Click to expand...
Click to collapse
check your pm's.

When i pull the battery and then put it back in to boot up, shouldn't the recovery boot first? The droid x recovery bootstrap does that. It would be a good feature to have because if i brick my phone and can't boot into recovery, i can't restore a backup.
Tell me if I'm doing something wrong, thanks

Unlocked Bootloader Message

Is there a way to avoid the message you get when you reboot after unlocking the Bootloader? The black screen where you can wait 5 seconds or tap the power to go on...
I understand that is correct to show it...but it's boring and I'm already aware of it.

http://forum.xda-developers.com/nextbit-robin/general/guide-install-twrp-root-robin-t3334171/page7
maybe try and follow the instruction on post number 69

Thanks for the reply but that's for Moto X. Actually before Robin I was using a Moto X and I know that procedure, point is that on Moto X was just a screenshot before booting and nothing else, here looks a bit different and you can also skip it pressing the power button. Plus I would avoid to flash/use the logo.bin of Moto X...
Can anyone of Nextbit team provide any info? Thanks !

I also don´t like the screen... the opportunity to hide would be great.

here's the same, maybe someone can make a xposed module?

kcl0801 said:
here's the same, maybe someone can make a xposed module?
Click to expand...
Click to collapse
Hi, firmware/bootloader guy here - work for a Android vendor so I decided to have a quick look at the bootloader for you guys..
It's stored in the bootloader (aboot) if you are interested so you can't make a xposed module, it runs before Android (before init or zygote) does (or the Linux kernel). I haven't checked if Secure boot is on (if not, I suppose I could build a replacement aboot and just patched out the logic for that screen ) but I hope it's on for security reasons.

uberlaggydarwin said:
Hi, firmware/bootloader guy here - work for a Android vendor so I decided to have a quick look at the bootloader for you guys..
It's stored in the bootloader (aboot) if you are interested so you can't make a xposed module, it runs before Android (before init or zygote) does (or the Linux kernel). I haven't checked if Secure boot is on (if not, I suppose I could build a replacement aboot and just patched out the logic for that screen ) but I hope it's on for security reasons.
Click to expand...
Click to collapse
got it, in that case i will keep this message, but just hope it can pass faster, it says 5 secs but i feel it's about 30s to skip it...

kcl0801 said:
got it, in that case i will keep this message, but just hope it can pass faster, it says 5 secs but i feel it's about 30s to skip it...
Click to expand...
Click to collapse
Hey everyone, our team is looking into that nag screen. One of our devs pointed it out, so we're trying to see what we can do. :good:

any luck on the nag screen yet? maybe gone in the july update? =D lol

I get this message Everytime, any ideas? Help would be great

Akoolive said:
I get this message Everytime, any ideas? Help would be great
Click to expand...
Click to collapse
Make sure that the recovery.img is in the same folder as your adb/fastboot files. Let me know if that works!

makbomb said:
Make sure that the recovery.img is in the same folder as your adb/fastboot files. Let me know if that works!
Click to expand...
Click to collapse
Thanks that worked

Akoolive said:
I get this message Everytime, any ideas? Help would be great
Click to expand...
Click to collapse
Replace "recovery.img" at the end with the actual twrp filename and it should work.

I'd love to get rid of that error message on my new Robin, but I'm confused about whether or not the previous two posts were a solution to the problem. I had flashed TWRP after unlocking the bootloader, and the recovery was in the same folder as the ADB and Fastboot files, but I'm not sure what that has to do with removing the error message.
Thanks in advance!

Saaber said:
I'd love to get rid of that error message on my new Robin, but I'm confused about whether or not the previous two posts were a solution to the problem. I had flashed TWRP after unlocking the bootloader, and the recovery was in the same folder as the ADB and Fastboot files, but I'm not sure what that has to do with removing the error message.
Thanks in advance!
Click to expand...
Click to collapse
The last several message in this thread regarding 'recovery.img' was for someone trying to flash TWRP in fastboot, it has nothing to do with the 5-second nag screen.
Since khang never responded, I'm assuming this won't change and the nag screen will remain. I'm so used to keeping my finger on the power button when i reboot that it's almost habit now, so really doesn't bother me too much.

How can a device that is marketed for its unlockable bootloader and warranty coverage have an jnlockable bootloader experience that is worse than basically all devices. You don't see unlocked Sony or LG phones having boot screens that require user input. The only device I know of that is worse is the Pixel c, which has a 30 second "integrity check" if the bootloader is unlocked.

Nextbit_Khang said:
Hey everyone, our team is looking into that nag screen. One of our devs pointed it out, so we're trying to see what we can do. :good:
Click to expand...
Click to collapse
IS this going to change? really annoyed by it

..It's only 5 seconds, the only reason it seems longer is the fact that the message merges in with the boot logo

Nextbit_Khang said:
Hey everyone, our team is looking into that nag screen. One of our devs pointed it out, so we're trying to see what we can do. :good:
Click to expand...
Click to collapse
Very old thread here, but could you guys maybe release an optional "developer/enthusiast" bootloader update that gets rid of that nag screen? Or at least give the option to confirm the warning in future updates, like "I have read and understood this warning. Don't show again."

I am posting hoping some progress may or may not have been made on this. Its atrocious.

rebooting issue never pass boot animation

i have asus zenfone 2 laser (snap dragon 615) i downloaded the correct rom
lineage-14.1-20180318-nightly-Z00L-signed Installed successfully no errors but the phone keep rebooting never passed boot animations
everything wiped before installing and i am using twrp-3.2.1-0-Z00L any idea wat should i do ?

Where there's a will theres a way
Factory reset. That happen to me on my Note 8 a while back and factory reset using hard keys was not working. Every one including sprint was telling me the keys where, Power button, bixby, and valume up at the same time. Well come to find out after refusing to believe that my new Android device could not be rest, I figured it out. Just saying.. Whith Android there is always a way.

JJsmizzle2002 said:
Factory reset. That happen to me on my Note 8 a while back and factory reset using hard keys was not working. Every one including sprint was telling me the keys where, Power button, bixby, and valume up at the same time. Well come to find out after refusing to believe that my new Android device could not be rest, I figured it out. Just saying.. Whith Android there is always a way.
Click to expand...
Click to collapse
I am sorry but I don't understand u, my phone is working perfectly with the stock rom now but when i tried to install lineage os, I followed the steps but it never pass the boot animation that's what I was trying to say

patrapatra said:
I am sorry but I don't understand u, my phone is working perfectly with the stock rom now but when i tried to install lineage os, I followed the steps but it never pass the boot animation that's what I was trying to say
Click to expand...
Click to collapse
I don't have any specific re your device, but I have a Galaxy Tab E that did the same thing. Why yours is doing that may be the same reason the Tab E is. At about 11/21/17 the builds for the E quit booting, stuck at animation. You * might * try an older build, if that works, I'd say it's the same problem.
good luck.

patrapatra said:
i have asus zenfone 2 laser (snap dragon 615) i downloaded the correct rom
lineage-14.1-20180318-nightly-Z00L-signed Installed successfully no errors but the phone keep rebooting never passed boot animations
everything wiped before installing and i am using twrp-3.2.1-0-Z00L any idea wat should i do ?
Click to expand...
Click to collapse
I don't have this device but, your best bet is to post this question within the following Official LineageOS thread for your device. Even though it states "Discontinued" on the title, you should be able to obtain some member guidance within it.
https://forum.xda-developers.com/showthread.php?t=3545692
If all else fails, and you don't receive any responses from the above thread, you can always try to obtain some member guidance within the following Q&A thread that's specific to your device.
https://forum.xda-developers.com/showthread.php?t=2997779
Good Luck!
~~~~~~~~~~~~~~~
I DO NOT provide support via PM unless asked/requested by myself. PLEASE keep it in the threads where everyone can share.

has anyone tested this?

What are your thoughts? does it boot for you too? I work on a lot of stuff for various devices in the background and behind the scenes..
Just curious if other people are having success with some of my projects as well.
Unofficial pie RR
Edit: link removed

AnierinB said:
What are your thoughts? does it boot for you too? I work on a lot of stuff for various devices in the background and behind the scenes..
Just curious if other people are having success with some of my projects as well.
Unofficial pie RR
https://androidfilehost.com/?fid=11410963190603910079
No gapps included
Click to expand...
Click to collapse
Hey brother,
just seen your RR-Rom on AFH and found this thread. I will try in a bit to see if it is booting. Thanks for for this...
EDIT: forgot to ask, i assume this is built on faygi's LoS build? I am downloading now to test. RR is my favorite and glad to see this...

_Sherrif said:
Hey brother,
just seen your RR-Rom on AFH and found this thread. I will try in a bit to see if it is booting. Thanks for for this...
EDIT: forgot to ask, i assume this is built on faygi's LoS build? I am downloading now to test. RR is my favorite and glad to see this...
Click to expand...
Click to collapse
Yes, it's built with the same trees and dependencies so expect the same device side bugs.
I also built XenonHD pie but I accidentally set it to only include common.mk which resulted in missing latinIME (aosp keyboard).
I totally spaced out and forgot that common_full_phone.mk inherits common_full and common_full.mk inherits common.mk ?
I'll recompile XenonHD tonight with the fix tonight and make a thread for it on this forum as long as someone else doesn't already have plans to maintain it.

@AnierinB,
OK, i just installed the ROM and it would not boot. I wipe and factory reset, not boot. Then i wiped, factory reset and FORMATED data, still no boot. I only tried to install and boot without any gapps, ROM only. Not sure. I get to the RR logo and it tries to boot for about 2-3 minutes then re-boots back to TWRP.
Also, i found your HAVOC-OS build, i think it was yours anyway, if i remember correctly. I tried as above with HAVOC-OS and had the same result. The only thing i have not tried is to RUU back to the latest OREO build, then install the ROM(S). If there is anything i can do to assist in trouble shooting let me know, and i can re-install later today and get the log, or whatever is needed for ya! I use my phone for work so i can't go long during the day with service.

_Sherrif said:
@AnierinB,
OK, i just installed the ROM and it would not boot. I wipe and factory reset, not boot. Then i wiped, factory reset and FORMATED data, still no boot. I only tried to install and boot without any gapps, ROM only. Not sure. I get to the RR logo and it tries to boot for about 2-3 minutes then re-boots back to TWRP.
Also, i found your HAVOC-OS build, i think it was yours anyway, if i remember correctly. I tried as above with HAVOC-OS and had the same result. The only thing i have not tried is to RUU back to the latest OREO build, then install the ROM(S). If there is anything i can do to assist in trouble shooting let me know, and i can re-install later today and get the log, or whatever is needed for ya! I use my phone for work so i can't go long during the day with service.
Click to expand...
Click to collapse
Interesting, I'll have to take a look when I get off work tonight. I apologise for that. XenonHD is still planned as it works flawlessly with no boot issues

AnierinB said:
Interesting, I'll have to take a look when I get off work tonight. XenonHD is still planned as it works flawlessly with no boot issues
Click to expand...
Click to collapse
Noted and Tahanks.
Also, I would like to give XENON-HD a try but i do not see it on AFH any longer. I saw it the other day when i seen the HAVOC upload, but was uncertain as to what android flavor it was and could not find any posts anywhere about it so i passed on it. If you could provide a link to XENON-HD i would be happy to give it a test run.

_Sherrif said:
Noted and Tahanks.
Also, I would like to give XENON-HD a try but i do not see it on AFH any longer. I saw it the other day when i seen the HAVOC upload, but was uncertain as to what android flavor it was and could not find any posts anywhere about it so i passed on it. If you could provide a link to XENON-HD i would be happy to give it a test run.
Click to expand...
Click to collapse
I have to recompile it tonight with the keyboard fix. I already have all the source on @holofractals server so when I get off work I'll get right on that. The previous build was deleted from Android file host because of the missing aosp keyboard.

i cant get xenon to boot. tried pico gapps from today and pervous days what gapps you recommend?

voodooline said:
i cant get xenon to boot. tried pico gapps from today and pervous days what gapps you recommend?
Click to expand...
Click to collapse
Mind the gapps

AnierinB said:
Mind the gapps
Click to expand...
Click to collapse
I tried without gapps and couldnt get it to boot not sure whats up

voodooline said:
I tried without gapps and couldnt get it to boot not sure whats up
Click to expand...
Click to collapse
Try the latest build. I compiled two last night and they retained the same package name since the date was the same. I deleted the previous one in favor of the new one so download everything from the links in xenonhd thread (mindthegapps, and ROM). advance wipe everything in TWRP before flashing so make a backup prior and store it on sdcard or PC

TWRP (Ianmacd) Images, New Space.

This is NOT my work (Ianmacd) and guide is written by Mr Pickles all credits to him for his install method.
Also this is just a copy and paste but the guide is well written and TWRP should cause less issues.
I'm sure Gieti94 is just perhaps busy with other commitments, credit also to him for his fantastic efforts.
Just a new space for the currently working TWRP so all don't get in a pickle.
----------------------------
Download Maintained By Pickles (best all in one convenient place) will have everything necessary for twrp functionality. Credit to pickles.....:good:
http://bit.ly/2VlcqYd
Excellent installation Guide below
Install Guide
---------------------------
- NOT A SINGLE STEP IS UNNESSECARY
- DO THEM _ALL_ EXACTLY!
- ALL YOUR DATA WILL BE GONE - BACKUP!
---------------------------------------
DO NOT INSTALL MODPACK FROM SOLDIER - IT BREAKS TWRP!
---------------------------------------
If you have any problems - contact @PiCkLeS or on Telegram by PiCkLeS or @rp4k
---------------------------------------
All development is by @ianmacd (Ian Macdonald).
---------------------------------------
0 - No matter what you have today, no root or Magisk-only solution or TWRP with Magisk-solution, do ALL the steps..
1 - Make sure you copy the "Magisk_Manager_Ian_install.apk" file and "Multidisabler-g97x_by_Ian.zip" file to your sd-card before you start!
2 - Download latest firmware via Samfirm or Frija or in any way you can, and unpack.
3 - Boot your phone to Download mode (Power+Bixby+VolDown) and remember to have the USB connected to your computer, it won't boot to DL-mode otherwise
4 - Keep autoboot etc in Odin settings, put each file in its place (AP, BL, CSC etc) and _dont_ use HOME_CSC, use CSC-only-file.
5 - After Odin is done, your phone will reboot automatically - let it! It can feel like forever, but let it do its restarts and stuff until you are in system-setup
6 - Do the setup as per usual, CONNECT TO WIFI but you can safely just say Skip on sign in and other stuff
7 - When setup says its all finished and you get to the standard launcher - go into Settings and enable Developer settings
8 - This step IS necessary.. If you don't do this step, you might get in pre-normal rrm state and you will have wait 7 days to try again: Enter Developer settings and look for the "OEM Unlock" switch - if you are rooting for the first time, Enable it. If you already have root since before or unlocked your bootloiader before, just confirm that its Enabled and graded out.
9 - If you already have an unlocked bootloader, skip to step 12. If not, continue with step 10.
10 - IF you never have unlocked your bootloader before, Power off the phone and boot into download mode again. You will see the long press volUp option for unlock bl, do that.
11 - IF you never have unlocked OEM before, boot the phone again, do the setup without signing in etc but connect to wifi, enable dev settings, go into dev settings and check that OEM now is enabled and grayed out.
12 - Reboot the phone in recovery mode (Power+Bixby+VolUp and keep holding until you are in stock recovery. Choose and do a factory reset.
13 - Reboot to bootloader with option in Recovery.
14 - Flash the tar you got (S10x-TWRP+Magisk_fixed_by_Ian.tar I Odin in the AP-slot. DISABLE auto reboot in Odin first!
15 - When the tar has flashed - Do as instructed on the phone, hold Power+VolDown for a few seconds and AS SOON AS THE SCREEN GOES BLACK -> quickly press power+bixby+volUp for a _long_ time, and I mean it can feel as if its a full minute! After a while you will see TWRP starting with its start screen, you can now let go and enter TWRP.
16 - FORMAT data, then WIPE data AND Cache. DO NOT LET IT REBOOT
17 - Flash "Multidisabler-g97x_by_Ian.zip" from SD card
18 - Go back to start screen of TWRP, Choose Reboot, Choose Recovery - YOU MUST ALWAYS CHOOSE REBOOT TO RECOVERY and _NOT_ system!
19 - Let the phone reboot into system, it will do some reboots it self, and again it will feel like it takes FOREVER - Just let it do its thing and DO NOT PRESS ANY KEYS!
20 - When your phone is finally done booting, just do the normal setup/signing for real this time.
21 - When you are done and in system/launcher, install "Magisk_Manager_Ian_install.apk" from SD card and verify that you now have Magisk Manager installed.
22 - Start Magisk Manager and say YES to what it says, it will do some stuff and then say "Rebooting in 5 seconds" - LET IT BOOT AND DO NOT TOUCH ANY KEYS this time either..
23 - Now when booted to system, start Magisk Manager and see that you have all green and its installed.
24 - Now you have root.
** Every time you reboot manually, be prepared to hold Power+Bixby+VolUP until you see the Samsung S10x-logo, then release and let it reboot, you will have root.
** Every time you power off the phone, when you power ON again, hold Power+Bixby+VolUP until you see the Samsung S10x-logo, then release and it will boot with root.
** Every time you want to enter TWRP-recovery, do as above but KEEP HOLDING THE KEYS UNTIL TWRP-start screen shows then release. Remember to choose reboot to recovery afterwards and you will boot with root.
** IF you screw up and forget or miss the key combo, just let it boot to system, immediately when system is up - reboot again and do the key combo and all is fine again.
This is me just trying to get an emergency first aid space, nothing more, I'm NOT trying to take any credits or dismiss Gieti94.
Thanks All

Duncan1982 said:
This is NOT my work (Ianmacd) and guide is written by rp4k all credits to him for his install method.
Click to expand...
Click to collapse
This is my tutorial and not r4pk. And I'd prefer that you use the download I provide here and no where else to make sure the right files gets downloaded when updated.
http://bit.ly/2VlcqYd
/P

Yea I can keep the OP updated, this is just an emergency first aid thread, thanks to Pickles for his well written guide.
I'm really not wanting to offend anyone, just for all to make life a bit easier....

very nice to have a reliable twrp solution, pitty that we don't have too many things to flash in recovery

Please remove the alternate download link, I have updated the multidisabler zip with a important update, v1.1 and the one download link for all is just for things like that, the other download link still have the old zip.
Very important that everyone uses Ian Macdonald's new v1.1 multidisabler script.
/P

I can update the mega link with the new disabler I reposted it to mega because I can't access Google @PiCkLeS
And yes I never said I wrote the guide I just added myself for helping people

rp4k said:
I can update the mega link with the new disabler I reposted it to mega because I can't access Google @PiCkLeS
Click to expand...
Click to collapse
I understand. But that doesn't seem to be a big problem for any one else and the bigger problem is that you risk having a link that is being used by the people only see it here and don't read anywhere else, or this message, and end up with old information or even worse, outdated files.
I can help you get the files on PM but please remove these links outside of my drive, which I maintain every day and keep up to date. It's not for vanity, it's for safety.
For now please edit your text and remove the link. All must use v1.1 of the multidisabler zip by Ian.
/P

Maybe this thread was a bad idea, as stated I am around and willing to keep things up to date
I know the importance, and how things are at present.

Duncan1982 said:
Maybe this thread was a bad idea, as stated I am around and willing to keep things up to date
I know the importance, and how things are at present.
Click to expand...
Click to collapse
Listen, just to be clear. I and I dont think Ian have a problem with you having this thread.
All I am worried about is the download link. Things can and are happening fast. If there are multiple sources for downloading files in this case, and today one was updated with important improvements, and there are many places to download from people can miss that and download old files that can cause big problems.
Keep the downloading to one good source and everything will be fine. The thread in it self can do much good by showing that there is an alternative, it works and right now almost 100 people in 24 hours have used it. Fantastic!
So I dont think it was a bad idea, I just dont want PM:s from people in a week or two asking why their device suddenly lost data, only to find out that they downloaded from a source that didnt have the latest files.
Thats all.
//P

PiCkLeS said:
Listen, just to be clear. I and I dont think Ian have a problem with you having this thread.
All I am worried about is the download link. Things can and are happening fast. If there are multiple sources for downloading files in this case, and today one was updated with important improvements, and there are many places to download from people can miss that and download old files that can cause big problems.
Keep the downloading to one good source and everything will be fine. The thread in it self can do much good by showing that there is an alternative, it works and right now almost 100 people in 24 hours have used it. Fantastic!
So I dont think it was a bad idea, I just dont want PM:s from people in a week or two asking why their device suddenly lost data, only to find out that they downloaded from a source that didnt have the latest files.
Thats all.
//P
Click to expand...
Click to collapse
I fully appreciate and understand that, the reason I created as I have plenty of time to maintain, and will keep it up to date I have been around for quite some time, if you look at my posts (search) I have had almost every device you can think of, currently have the Vivo IQOO also, I have enough experience to understand the important and implications.
I don't want your PM's to be going crazy so I'll fully respect your decisions and will keep everything updated also. But it is better if everything is tody and not one thing here and there, OP has been updated with your direct link, is this cool?
Just thought by creating this thread that it might help, my sincere and good intentions are hopefully evident

PiCkLeS said:
Please remove the alternate download link, I have updated the multidisabler zip with a important update, v1.1 and the one download link for all is just for things like that, the other download link still have the old zip.
Very important that everyone uses Ian Macdonald's new v1.1 multidisabler script.
/P
Click to expand...
Click to collapse
Can I install multi Disabler 1.1 withouth lost data?

zubi182 said:
Can I install multi Disabler 1.1 withouth lost data?
Click to expand...
Click to collapse
Yes just flash it in twrp, nothing will be lost.
/P

I assume this is only for the Exynos version? Or does it work for Snapdragon as well?

mistermidas said:
I assume this is only for the Exynos version? Or does it work for Snapdragon as well?
Click to expand...
Click to collapse
You have a working snapdragon root? How did you get past step #9 of launching stock recovery after you flashed magisk

rp4k said:
You have a working snapdragon root? How did you get past step #9 of launching stock recovery after you flashed magisk
Click to expand...
Click to collapse
Man... did you even read my comment???
I was asking if this would work for Snapdragon, not saying I got it to work. It doesn't mention if it's a method for both versions in the OP or not.

mistermidas said:
Man... did you even read my comment???
I was asking if this would work for Snapdragon, not saying I got it to work. It doesn't mention if it's a method for both versions in the OP or not.
Click to expand...
Click to collapse
Sorry I responded when I was half asleep. My fault.

I will try this out and post and update, i had no luck with previous twrp, always boot loops regardless of what i do.
My bootloader is unlocked but not grayed out. Can i still do it?

mercifool said:
I will try this out and post and update, i had no luck with previous twrp, always boot loops regardless of what i do.
My bootloader is unlocked but not grayed out. Can i still do it?
Click to expand...
Click to collapse
Yes, just do exactly all the steps and use the new files in the link and you will be fine.
//P

deleted

Carotix said:
hi ,
do you have the OEM switched to on?
if not , you need it ..... if you can't get it because you are waiting the 7 days , you can make this trick
open settings and set the date 8 days before ... then reboot
so you can enable OEM in developer settings
Click to expand...
Click to collapse
Hi there, are these instructions for Exynos only or can I apply it to Snapdragon as well, please advise. Thank!