YOU ARE ACCEPTING RISK FOR YOUR DEVICE. THE ONLY ONE LIABLE AND RESPONSIBLE FOR YOUR DEVICE IS YOU.
Pre-Req:
(manual method) root with write-protection off
or
(flash method) unlocked bootloader with TWRP recovery installed
Flash Method:
1) Download "wirelesscharge_nosound_install.zip" and place on sdcard
2) Reboot Into TWRP recovery and flash zip. Reboot to system
3) Verify no sound when placed on wireless charger
Manual Method:
1) Download "wirelesscharge_nosound_install.zip"
2) find system\media\audio\ui folder and rename "WirelessChargingStarted.ogg" to "WirelessChargingStarted.ogg.org"
3) Extract the WirelessChargingStarted.ogg file from zip and put in system\media\audio\ui folder
4) Set permissions for the file to rw-r--r-- (644)
Owner: Read/Write
Group: Read
World: Read
8) Reboot. Verify no sound when wireless charging starts up
Back-To-Stock:
Flash method: Follow flash method procedure (above) with "wirelesscharge_nosound_revert.zip"
Manual method: delete WirelessChargingStarted.ogg and remove '.org' from original that was saved earlier. Check permissions (644) and reboot.
bbb
chewing my cud
If you have Xposed.. you may use "No Wireless Charging Sound" module to mute the noise.
BBB
Burning Paper
thanks but is there a way to turn off the wireless charging screen?
Related
This is a short guide on how to fix a boot loop or other Fc errors using safe strap (no relfash/no odin)
Always and I say always add.bak to any file you intend to replace with another
This wil let you use safestrap to fix a bootloop or other FC issues from a file you replaced using a root explorer program
Okay so you started modding a files lest say systemui.apk and you went into root explorer renamed the origna lwith a .bak extension and droped your new one in there well all seems well you reboot like normal but lo and behold after a while of waiting you realize you are caught in a boot loop or when it does load you get a continues Fc ever cuple seconds making the phone virtually unusable
Well Your in luck reboot your phone and go into SafeStrap
Step 1. Tap Mount
Step 2. Check System
Step 3. Go back and tap Advanced
Step 4. Tap File Manager
Step 5. Scroll Down to system(or wherever you may have placed your file) and tap it
Step 6. Tap App
Step 7. Fint the file you replace and clike it and delete it
Step 8. Tap the original and rename it to what ever the fiel is in this case systemui.apk.bak to its original without the .bak extension
Step 9. Reboot System
Step 10. Enjoy
If you need any help Post int the comment im here to help
If i helped you leave thanks
YOU HOLD MYSELF AND XDA FREE FROM ANY LIABILITY. WE ARE NOT RESPONSIBLE FOR YOUR DEVICE. FLASH AT YOUR OWN RISK.
I just modified the files from the previous mod of Topsnakes and uploaded them here. All credit should go to Topsnake. I even copied the instructions.
I messaged Topsnake prior to posting. He no longer has this phone and was O.K. with me posting.
This will enable Native Tether for Build 24.3.7.
Prerequisites:
Droid Maxx/Ultra Rooted w/WP off
or
Bootloader Unlocked
METHOD 1: TWRP INSTALL
1) Download the package below labeled "24.3.7-tether_twrpinstall".
2) Reboot Into TWRP recovery and navigate to the file for flashing.
3) Reboot
4) Verify tether works
5) Profit.
METHOD 2: MANUAL INSTALL
1) Download the package below labeled "24.3.7-tether".
2) Download root browser by Jrummy from the play store
3) Navigate to System/Priv-App and rename VZWEntitlementservice.apk to VzwEntitlementservice.apk.bak.
4) Navigate to System and rename the build.prop to build.prop.bak
5) Place the package on the root of your sd card and extract the build.prop file within the folder.
6) Navigate to system and Copy and paste the new file.
7) Set permissions for the file to
Owner: Read/Write
Group: Read
Others: Read
This should show (rw-r--r--)
8) Reboot. Verify tether works
9) Profit.
REVERTING
METHOD 1:
If installed in twrp, download the package below labeled 24.3.7-tether_revert. Flash in Twrp, reboot, verify subscription check re-enabled.
METHOD 2:
If manually installed, simply delete the build.prop you installed, remove the .bak extension from the original build.prop, verify permissions, reboot.
Files
Files
Nice, would you happen to have the modem too?
Will this work on the Droid Mini?
[FONT="]4 - Way Reboot Menu for Nabi2 KK 4.4 ( De-Odexed )[/FONT][FONT="]Well it's that time again after getting a needed update for our tablets. This is the extended Reboot Menu only and not a "Power Menu". I do not recommend flashing to Custom Roms as the ROMs may contain special permissions/policies ( if added ) that the Rom Developer may have implemented or even may be require so the Custom Rom may run or function properly. None are known [/FONT][FONT="]for the Nabi2 ATM so I guess we are safe LOL. [/FONT] Unlike the previous version that went through the Power Button menu, this one has a dedicated Reboot Button eliminating the extra
"Power Off "at the bottom of the Reboot Menu going through the Power Button menu.
[FONT="]The Extended Reboot Menu Includes:[/FONT]
[FONT="]REBOOT[/FONT]
[FONT="]( Normal Complete Reboot after Shutdown )[/FONT]
[FONT="][FONT="]SOFT RE[/FONT]BOOT[/FONT]
[FONT="]( Quick Reboot for restarting the Android Shell only, No Shutdown )[/FONT]
[FONT="]BOOTLOADER[/FONT]
[FONT="]([FONT="] Bootloader [/FONT]Mode / Fastboot Mo[FONT="]de [/FONT])[/FONT]
Working after it's plugged in to Computer via USB Cord ( see post#2 for Youtube link )
[FONT="]RECOVERY[/FONT]
[FONT="]( Restarts[FONT="] t[/FONT]ablet [FONT="]strai[FONT="]gh[FONT="]t to[/FONT][/FONT][/FONT] Recove[FONT="]r[/FONT]y after Shutdown )[/FONT]
=========================================================================================================
=========================================
=========================================================
[FONT="]===================================================================[/FONT]
[FONT="]DISCLAIMER:[/FONT]
===================================================================
===============================================
=========================================
[FONT="]By YOU, the USER, flashing this file or manually pasting to modify your Android System, YOU understand and know what YOU are [/FONT]
[FONT="]doing. I nor [/FONT][FONT="]anyone will be held liable nor responsible for YOUR doing if your phone bricks. As always, as is suggested by many and [/FONT]
[FONT="]myself, please make [/FONT][FONT="]sure you perform a complete[/FONT]
[FONT="]NANDROID BACKUP[/FONT]
[FONT="]before flashing and/or modifying your OS or the mentioned stock .jar file. I also suggest YOU keep a separate copy of the stock .jar file [/FONT]
[FONT="]handy, [/FONT][FONT="]like in your External SDcard, if the phone decides not to boot up. Knowing this, YOU assume all responsibility for what happens [/FONT]
[FONT="]as YOU, the USER, know and comprehend what YOU are doing and understand the consequences or severity of damages that can be [/FONT]
[FONT="]brought to your [/FONT][FONT="]device by flashing or modifying your OS incorrectly. [/FONT]
[FONT="]YOU[/FONT][FONT="] Have Been Warned !![/FONT]
=========================================================================================================
[FONT="]What's Needed / Recommended:[/FONT]
[FONT="]Rooted Device [/FONT][FONT="]( to extract the needed files Manually for backup )[/FONT]
[FONT="]Custom Recovery ( TWRP for Flashing the ZIP and/or using the File Manager or a Custom Aroma File Manager)[/FONT]
[FONT="]If you can do it via ADB Commands then all power to you.....[/FONT]
[FONT="]I provided [/FONT][FONT="]BOTH[/FONT][FONT="] , the stock NABI2 [/FONT][FONT="]( Stock NABI2 KK jar )[/FONT][FONT="] and modded NABI2 .jar [/FONT][FONT="]( android.policy.jar )[/FONT][FONT="] files and [/FONT]
[FONT="]will make a flashable zip [/FONT][FONT="]( coming soon )[/FONT][FONT="] below[/FONT]
[FONT="]What To Do:[/FONT]
[FONT="]You have two choices on installing the .jar file. You can either Flash the ZIP in TWRP ( which at the moment is not available ) or manually copy & paste or push the .jar file to system/framework/. If you decide to do this manually, you will then need to set the file permissions to the modified android.policy.jar file to 0644. Before manually pasting the file in the framework folder, you can rename the stock android.policy.jar file with " .bak " ( ex. android.policy.jar.bak ) at the end so you don't have to delete it from the framework folder if you so choose. Now using TWRP you can either use the built in File Manager and set permissions via the terminal with chmod commands or Install/Flash the Aroma File Manager in recovery to use like a simple File manager where you can hold down on the file to get a popup window to copy/paste or set permissions manually.[/FONT]
======================================================================================
[FONT="]Words of caution.....[/FONT]
[FONT="]if you attempt to do this manually and are still actively booted in your Android OS while modifying or deleting the .jar file, there is the highest probability that your tablet will immediately reboot and you will not be able to boot up the OS again and remain stuck on the Nabi boot screen as the android.policy.jar is no longer visible to your OS. This is why you need to do this before booting up like in recovery.[/FONT]
======================================================================================
[FONT="]Thanks and credits go out to :[/FONT][FONT="]@[/FONT]tdunham
[FONT="]@[/FONT]CNexus
[FONT="]@kahvitahra[/FONT]
[FONT="]for the knowledge gained over the years and information gathered on the How-Too's and the files needed for this MOD. If I missed someone please PM me or let me know.....[/FONT]
[FONT="]Enjoy! [/FONT]
Change Log
Android Policy v1:1. Unlike last from JB, this KK Reboot Menu has it's own button instead of going through the Power Button.
2. Problem with Bootloader Button not working, not going into Bootloader.Android Policy v2 ( 02/28/15 ): 1. Reboot Menu has it's own button instead of going through the Power Button as before.
2. Soft Reboot ( Quick Reboot ) using smali command of "setprop stl.restart zygote" instead of "pkill -term -f system_server" for those
that do not want to or honestly need to install BusyBox to simlink pkill if not already done so. Change will not affect anything.
3. Some more smali edits to try and get Bootloader button working. Forum member n3wt discovered when attempting to go into Bootloader mode,
after reboot and staying stuck at the nabi boot logo screen, plugging in the USB cord while USB connected to computer would then switch the
Nabi to Fastboot Mode. --- link to youtube video bellow.
http://youtu.be/Qo9ShihfCqY
Any problems ...... let me know.
.
Thanks. I get error flashing zip from TWRP. I copied the jar to /system/framework and set perms to 644 but I don't see the new options even after reboot. Also the attachment says v1. Where is v2?
If you are saying its not available from the power button how do you get to the menu?
lev777 said:
Thanks. I get error flashing zip from TWRP. I copied the jar to /system/framework and set perms to 644 but I don't see the new options even after reboot. Also the attachment says v1. Where is v2?
If you are saying its not available from the power button how do you get to the menu?
Click to expand...
Click to collapse
Sorry for not responding right away, notification was not set. The zip is not a flashable. I never got around to making one. Better one knows where it's going and one backs up their original before attempting.
You get the reboot option when pressing on "Reboot". Normally, the Nabi2 stock jar does not come with a reboot option which is what I added.
YOU ARE ACCEPTING RISK FOR YOUR DEVICE. THE ONLY ONE LIABLE AND RESPONSIBLE FOR YOUR DEVICE IS YOU.
Pre-Req:
(manual method) Build 24.13.2 root with write-protection off
or
(flash method) unlocked bootloader with TWRP recovery installed
Flash Method:
1) Download "24.13.2-tether_install.zip" and place on sdcard
2) Reboot Into TWRP recovery and flash zip. Reboot to system
3) Verify tether works
Manual Method:
1) Download "24.13.2-tether.zip"
2) find system folder and rename the build.prop to build.prop.org
3) Extract the build.prop file from zip and put in system
4) Set permissions for the file to rw-r--r-- (644)
Owner: Read/Write
Group: Read
World: Read
8) Reboot. Verify tether works
Back-To-Stock:
Flash method: Follow flash method procedure (above) with "24.13.2-tether_revert.zip"
Manual method: delete build.prop and remove '.org' from original that was saved earlier. Check permissions (644) and reboot.
bbb
eat more chlorophyll
If you have Xposed.. you may use "x Tether" module instead to enable mobile hotspot. If not I hope you find the above information useful.
bbb
Sinking Stick
realbbb said:
If you have Xposed.. you may use "x Tether" module instead to enable mobile hotspot. If not I hope you find the above information useful.
bbb
Sinking Stick
Click to expand...
Click to collapse
Does manual method work without rooting device? The root method for Droid Ultra is a long around 2 hr method. Trying to avoid rooting until a new method is available.
JDunc said:
Does manual method work without rooting device? The root method for Droid Ultra is a long around 2 hr method. Trying to avoid rooting until a new method is available.
Click to expand...
Click to collapse
No.
bbb
Bursting Bubblers
realbbb said:
YOU ARE ACCEPTING RISK FOR YOUR DEVICE. THE ONLY ONE LIABLE AND RESPONSIBLE FOR YOUR DEVICE IS YOU.
Pre-Req:
(manual method) Build 24.13.2 root with write-protection off
or
(flash method) unlocked bootloader with TWRP recovery installed
Flash Method:
1) Download "24.13.2-tether_install.zip" and place on sdcard
2) Reboot Into TWRP recovery and flash zip. Reboot to system
3) Verify tether works
Manual Method:
1) Download "24.13.2-tether.zip"
2) find system folder and rename the build.prop to build.prop.org
3) Extract the build.prop file from zip and put in system
4) Set permissions for the file to rw-r--r-- (644)
Owner: Read/Write
Group: Read
World: Read
8) Reboot. Verify tether works
Back-To-Stock:
Flash method: Follow flash method procedure (above) with "24.13.2-tether_revert.zip"
Manual method: delete build.prop and remove '.org' from original that was saved earlier. Check permissions (644) and reboot.
bbb
eat more chlorophyll
Click to expand...
Click to collapse
Does this work for Maxx as well?
JarMagic said:
Does this work for Maxx as well?
Click to expand...
Click to collapse
Yes, XT1080
Realbbb
Zebra Red
Sent from my XT1254 using Tapatalk
Warning!!! I’m not responsible for anything (death, destruction, or nuclear war) which happens to you & your stuffs after following this guide.
Downloads :-
RR-Magisk-Root-vivo-Y51L.zip
TipsyOS Prerooted ROM
How to Install ?
1. Make sure you have RR rom installed(Get it Here) before flashing RR-Magisk-17.2-vivo-Y51L.zip
2. Reboot to TWRP recovery
3. Install RR-Magisk-17.2-vivo-Y51L.zip or TipsyOs-prerooted.zip, whatever your choice is.
4. Reboot to System.
5. If root worked, Come back and the hit the thanks button below!
:Video Tutorial on the same:
https://www.youtube.com/watch?v=omUggCUJGGk
-:NOTES FOR VIVO Y51L DEVS:-1. Played with Magisk once for around 3 hours
2. You wanna know ? Seriously ? Okay
3. Disable Selinux which isn't needed by root ! (Just for fun)
4. Downlad Magisk-latest.zip
5. Extract magiskinit from arm folder
6. Push magiskinit to /data/local/tmp
7. Run :
adb shell
cd data/local/tmp
chmod 755 magiskinit
./magiskinit -x magisk magisk
exit
adb pull /data/local/magiskinit8. Now you will get an file with name magisk in the current dir
9. Place it in the /system/xbin/ folder of your rom
10. Place Magisk Manager apk in /sytem/app/Magisk
11. Now, boot.img part :
Following things to be done in boot.img :
Created /sbin/permissive.sh
Patched default.prop, fstab.qcom, init.environ.rc, init.rc, init.recovery.service.rc, init.root.rc, init.superuser.rc (create one if..), sepolicy, service_contexts
If you wanna know the stuff i added in these files, just search 'Naveen' in all those files (Yeah, i reckon that, i'm Superlazy to find & write those here even though i can write 55wpm)12. What about how to patch sepolicy ? Uh, I used supolicy by @Chainfire (Thanks man....)
13. How to find selinux denies ? Install audit2allow in your linux system & :
adb shell dmesg | audit2allow -p (your sepolicy here, use 'adb pull /sys/fs/selinux/policy') > selinux.error
Now push supolicy to phone (Download SuperSU.zip)
adb push ./ /data/local/tmp/tony/
adb shell
cd /data/local/tmp/tony/
chmod 755 *
./supolicy --live "error here"
./supolicy --save /data/local/tmp/tony/new_sepolicy
exit
adb pull /data/local/tmp/tony/new_sepolicy
Rename new_sepolicy to sepolicy & replace your original one in boot.img
Repack your boot.img13. This won't work with stock rom since we get operation not permitted errors while trying to exec su, i think it's Linux Capabilities (Read more about that here : http://man7.org/linux/man-pages/man7/capabilities.7.html) Don't ask me why it works in cm roms if kernel is the problem
14. Whatever you wanna ask me, reply here please (I'm don't check private messages anymore)
Official Telegram Group for Vivo Y51L/Y21L : https://t.me/vivodevelopment
Fix for bugs
Please fix the bugs asap....i am facing audio and video playback problems
#ask
are you facing mic and call problem?
use y51l kernal
bro.
can you use y51l kernal to patch file?
so that y51l may get rooted with no bugs
Bugs are there
*Front camera not working
*Flash light not working
*Magisk not installing
y51 kernal source restore
can you make tutorial to restore y51 kernal source .also there a wifi bug wont turn on
device stuck at app starting up....pls hlp
installed the miui root boot.img and twrp.img but after rebooting the device was stuck
Can't root
How to download
Magisk cannot run in third-party ROM
It's a pity that my favorite ROM cannot be ROOT. It's not that the installation fails, but it always stops working.
I have a more useful method for rooting vivo y51L
Requirements:-
OTG
Data cable
A second phone
Bootloader unlock
Bugjaeger application
Root checker application
Your custom ROM or stock ROM zip file
Firstly we have to unzip our stock or custom ROM zip file, after unzipping file we have to move out boot.img file and save it in our internal storage . After that we have to flash the boot.img file in magisk and after flashing we will get a magisk patch in our download folder . We have to send that patch to our second phone and save it in it's internal storage .after that we have to boot our phone in fastboot mode and for that we have to power off our device and press volume down and power button .After booting the device in fastboot mode you have to connect otg in your second device and data cable in fastboot device . After that connect data cable and otg , after connecting the Bugjaeger application will open automatically . after that find an icon which looks like lightning in app and click that , after that you will find a blue dot at the bottom of the screen . Click that button and you will get inside command section after that type the first command :- Fastboot devices and click the play button at the right side. After that you will see a serial number which means you are connected. After that write the second command :- Fastboot flash boot , after writing it we will find a paper clip type button at the top right corner , just click that and attach the magisk patch which we sent to our second device and tap the play button at the right side . After the command has succeeded we have have to reboot our fastboot phone after removing data cable and otg . After rebooting just open root checker application and keep internet on , Click on verify root. Your phone is rooted now.
Now do whatever you want to do
Fun fact :- this method works on every phone
Those who want to say me thanks for this method please reply me