Related
Got the phone today. I noticed one thing that the capture during video functionality wasn't working at all.
I have a Redmi 1S as well. When i compared, the capture button during the video doesn't show up at all. Both for the rear and front cameras.
I am recording the videos at 1080p for both the cameras. Tried 720p as well. The issue persists. Please help.
Use OTA update to solve many issues on Indian Redmi Note 3G
Sheila-aliehS said:
hi there.
try to download a app photographie,if it still not working, and then, root it or setting Restore Factory. the problem will be solved.
fr.xiaomidevice.com
Click to expand...
Click to collapse
There's a Update to that version already available on official site, as well on the OTA.
go to settings and about, then run system update when on WI-FI, and it would give you a update named
"miui_H3WGlobal_JHDMIBH38.0_59e44d8bab_4.2" of 555MB to download.
The file would be downloaded to phone memory under folder "downloaded_rom" and make sure you copy this ZIP file to PC
as after installation this file will get self destructed, so if you have a friend whom you wish to share this update you must copy it to PC.
or if you mess with something later, this ROM update would let you restore your phone.
You can install it from system update by touching the option button and chose "select update package" browse for this downloaded file and phone would reboot to complete the update.
Once done, you would certainly see improvement in phone working and more RAM would be available for apps etc.
However real fun of using this would start when this phone gets updated to any of the kitkat/CM12/Lollipop versions.
Managed to soft brick my Note 4. Set my dpi to 200, and my resolution to 720p. Apparently, it's just too low. Worked great when I set the values, but restarting the phone caused the brick. (It boots, but can't access anything. Unfortunately, I don't have my PC allowed as ADB, so I can't even connect from that state to ADB.)
So.
My idea to prevent full wipe, is to use ADB sideload OR ORS.
- Sideload. Make a "payload" that will replace the build.prop with the stock one.
- ORS. http://wiki.rootzwiki.com/OpenRecoveryScript
How do I actually do this?
Like the RecoveryScript seems to be a great idea, but from TWRP, I could not find a single build.prop file at all. There is a default prop, but it contains no resolution, dpi or whatever.
So I spent another few hours on this. I hate myself. And I hate the app's developer for being so careless.
- Flashed latest Samsung firmware hoping it will kill the software. Nope. It did not.
- Flashed the .zip for build.prop. NO effect.
The system has the correct DPI value so it must not be the issue.
- I think the app auto runs, and sets resolution. So I tried grep, but it cannot find the "1280" string anywher,e and I also removed the app from /data/app and /data/data.
- I cannot get MTP or ADB working in TWRP whatsoever. Huge letdown, but there is just no support. And without seeing what happens on the screen (it must be just my lockscreen there), I can't accept ADB connections either.
Well, so I went YOLO and cleared data. And... behold, NOTHING.
Did this retarded stupid program killed my phone? Holy hell.
Okay, so full entire wipe + reflash + full wipe, and now it works.
This app? Never again. The others are good on the market, so go for it.
App in question: https://play.google.com/store/apps/details?id=com.chornerman.easydpichanger
[ DO NOT USE !!! ]
Instead of wipes at Restore DPI: You can remove only of "com.android.providers.settings" at "/data".
Sorry but I have to resurrect this. I've played with dpi settings and now after reboot I cannot press enter when I type in my password as keyboard is partly off screen. TWRP is not working as it does not support Android 12. Any chance to resolve this beside flash?
Update: Connected keyboard via OTG cable and managed to unlock
Resurrecting this to offer another solution that doesn't involve any wiping/flashing/restoring-to-stock or messing with build.props
I used the same app as OP and feared the worst when I got stuck on recovery after changing DPI
This method allowed me to restore my xiaomi Redmi 9 with android 10
-You need to have a custom recovery installed
-"shell wm" commands don't work in recovery
You need to edit settings_global.xml & settings_secure.xml found in /data/system/users/0
You can do this by pulling&pushing the files to a PC using adb or editing in recovery using nano editor or something similiar.
Search for:
"display_size_forced" in settings_global.xml
"display_density_forced" in settings_secure.xml
Edit those with something close to your default values, then reboot and that's it!
Now that you're no longer stuck in boot you can reset resolution and density with the usual methods like adb or a better app
I hope this helps anyone else stuck in the same problem I was
mrmrva said:
...TWRP is not working as it does not support Android 12. ......
Click to expand...
Click to collapse
Where did you get a A12 version for which Note4?
Owning a N910F=trlte I don't find any higher than A11.
Don't have Samsung but Poco f2 pro and was looking for solution everywhere so posted here.
Moto G3 2015 Osprey XT1541 1GB Ram.32bit(ARM)
AFAIK these roms cover other Moto G3 versions but investigate more for yourself.
Always keep Nandroid backups using TWRP of your running Rom. I keep copies of my latest Android 10 Chli360/Lineage running Roms on my Phone's portable SD card in the phone and also on my Laptop.
https://twrp.me
Warning!
I've never bothered with any Android 8 Oreo roms on my G3 2015 Osprey. I went straight to Android 9(PIE).
https://chil360.github.io
I've tried most and now I'm only interested in the Lineage versions and the Havoc versions of Android 10 as these keep the Hardware FM radio that I like to use.
Havoc version,
Havoc-OS-v3.3-20200306-osprey-Unofficial.zip
Working fine and
Lineage,
ineage-17.1-20200308-UNOFFICIAL-osprey.zip
Working fine.
Note: If I recall correctly Chil360 Havoc Android 10 Rom does not need Gapps installing. If Lineage does I use Arm_10_Pico,
Note:
When setting up the phone I never let the phone install backups automatically I have my apps backed up on my SD card and re-install them from there. Google photos will not not clone-Install and a few others so I just re-download those.
Contacts:
Although Google backs up contacts lists to be safe I keep an,"Old School" backup using the Contact's apps Import/Export option and save them to a .vcf file. This will look like contacts.vcf or 000001.vcf on the phone wherever you have chosen to save it. This can be imported into any contacts app,Even on APPLE phones!
I send a copy of this .vcf file to myself attached to an Email. This means I can download my contacts to any phone anywhere in the World if I ever need to.
Note:
I never encrypt my phones so cannot answer any questions on this subject.
If you want to,"Root" the phone then install the .zip version of Magisk from your phone's Internal Memory and keep it on your phone's Internal memory. You install the .zip using TWRP's install option and always take it's advice on clearing Dalvik Cache and Cache.
Then once the phone is booted update both it and it's manager via an Internet connection.
Note: Some,"Pay/Money" apps will detect that you are running a non-stock rom. You can hide these apps using,"Magisk Hide" and in some cases you need to Hide the app AND then use Magisk option to rename itself. You can call it anything you like but keep it simple like Osprey.
HTH
Moto G3 2015 Osprey XT1541 1GB Ram.32bit(ARM)
Chil360 has updated the April 2020 Havoc 3.4 and it now installs on the Above phone. I am testing it as I post.
Havoc-OS-v3.4-20200417-osprey-Unofficial.zip. Does not require Gapps installing.
BTW I do like the AOSP_Pizza Android 9 rom for Chil360 as well(Still has FM RAdio).
https://www.androidfilehost.com/?fid=4349826312261742008
I go back to it sometimes as it has some features others don't have like showing local temp on the Lockscreen and also allows me to install a Custom boot animation logo. I like the old,"Stitch" Moto Logo
The Android 10 roms won't let me change the animated loading logos(They will let me change the static boot logo) or I need to find versions that will work with Android 10
Moto G3 2015 Osprey XT1541 1GB Ram.32bit(ARM)
Just thought I'd update.
Started to install Chil's latest Paranoid Android and it installed fine but stopped as I realized it doesn't have as many tweaks as Havoc 3.4.
Things I like about Havoc 3 series.
I can have,
Date and time in the notification bar.
Battery percentage next to Battery icon and time left when Notification bar is swiped down.
Easy to swap software buttons(I'm right handed so like my Back button on the right).
It still lets me use my old version of Holo Launcher.
You can assign functions to the Software buttons like Long press to Lockscreen. Can't seem to get Long press to enable the Flashlight tho
Advanced Restart on Power button.
Loads more tweaks to explore.
One thing I would like but I'm not sure if the Motos are capable but I have a cheap China phone that lets me double tap the screen to wake it up and I don't mean just at the Top of the phone I mean anywhere on the screen.
I can't see myself using any other version except as stated AOSP Pizza for a bit of a change now and then
PS
Continued thanks to CHIL his work is much appreciated keeping these Classic little phones going
Latest Chil360 roms are out. I'm running Havoc(May Security updated) but FM radio not working
Has anybody else had issues with the FM radio not working after upgrading to v3.5-20200508 version of Havoc Android 10 for Moto G3 2015? I found after upgrading to this version, the FM radio would no longer work, it would just freeze. Downgrading to v3.4-20200417, it would work perfectly again. Upgrading again to v3.5-20200508, it no longer would work. Has anything been changed that would cause this? Other than this issue, I believe that the ROM is excellent.
Gord
Glad you found this. Checking the FM radio is usually one of the first things I do but didn't this time
Yes you are right it's not working for me as well in Havoc 3.5.
Gone back to 3.4 with no problems :good:
Gordster
Thank you for responding to my reply and addressing the FM radio issue. I have found one other ongoing problem with the camera app. This has been occurring with all custom roms that I have tried whether Android 9 or 10. When photos or videos are saved to the internal phone, they go to the "main storage\DCIM\Camera" directory. I however like to save my photos and videos directly to the SD card.
With Android 6 they could be directed to "sdcard\DCIM\Camera" directory but with all custom roms I've tried when directed to the SD card, they wind up in "sdcard\Android\data\org.lineageos.snap\files" directory. Can this be changed so they go directly to the default location "sdcard\DCIM\Camera" directory?
Thanks
Gord
Gordster said:
Thank you for responding to my reply and addressing the FM radio issue. I have found one other ongoing problem with the camera app. This has been occurring with all custom roms that I have tried whether Android 9 or 10. When photos or videos are saved to the internal phone, they go to the "main storage\DCIM\Camera" directory. I however like to save my photos and videos directly to the SD card.
With Android 6 they could be directed to "sdcard\DCIM\Camera" directory but with all custom roms I've tried when directed to the SD card, they wind up in "sdcard\Android\data\org.lineageos.snap\files" directory. Can this be changed so they go directly to the default location "sdcard\DCIM\Camera" directory?
Thanks
Gord
Click to expand...
Click to collapse
I haven't used a Stock android Camera for years. I use the way better,"Open Camera" .You can set it to save to the SD card by enabling it's framework option and then pointing it to the SD card. It now says it contains ads but It used to be ad-free but I haven't seen any ads even in the latest version.
https://play.google.com/store/apps/details?id=net.sourceforge.opencamera&hl=en_GB
Open Camera > Gear icon(settings) More Camera controls and Use Storage Access Framework and then Save location and say yes to permissions asked
R1ffR4ff said:
I haven't used a Stock android Camera for years. I use the way better,"Open Camera" .You can set it to save to the SD card by enabling it's framework option and then pointing it to the SD card. It now says it contains ads but It used to be ad-free but I haven't seen any ads even in the latest version.
https://play.google.com/store/apps/details?id=net.sourceforge.opencamera&hl=en_GB
Open Camera > Gear icon(settings) More Camera controls and Use Storage Access Framework and then Save location and say yes to permissions asked
Click to expand...
Click to collapse
How can you use the OpenCamera? I try that but the photo with flash are blur, only Moto Camera can do photo with flash without the blur effect.
stukdev said:
How can you use the OpenCamera? I try that but the photo with flash are blur, only Moto Camera can do photo with flash without the blur effect.
Click to expand...
Click to collapse
Open camera has worked on all the roms I've tested.
Try another Camera app and if it does it with that you may have a hardware fault
Make a Nandroid backup and then do a Factory reset from Recovery mode but when setting up the phone don't let Google auto install any apps and just get to the Stock camera as soon as you can and see if it works. There may be an app you install that is causing the problem.
BTW.
Check back through this thread on how I install custom roms. I do it clean and add my apps back after I've got into the phone from .apk backups.
R1ffR4ff said:
Open camera has worked on all the roms I've tested.
Try another Camera app and if it does it with that you may have a hardware fault
Make a Nandroid backup and then do a Factory reset from Recovery mode but when setting up the phone don't let Google auto install any apps and just get to the Stock camera as soon as you can and see if it works. There may be an app you install that is causing the problem.
BTW.
Check back through this thread on how I install custom roms. I do it clean and add my apps back after I've got into the phone from .apk backups.
Click to expand...
Click to collapse
Maybe its an hardware fault, but with the Moto App i haven't any problem
stukdev said:
Maybe its an hardware fault, but with the Moto App i haven't any problem
Click to expand...
Click to collapse
See previous reply and also I don't know if you know the,"Soft Reset" trick on Moto phones that can clear some problems.
Press and hold the Power button in for around 10/15 seconds until the phone restarts. This emulates taking the Battery out and can clear clogged RAM of old data that can prevent correct operation
I've been running the latest May AOSP PIZZA
AOSiP-9.0-Pizza-osprey-20200517.zip
Since yesterday and all seems fine so far. Only thing missing is the local Temp on the lock screen unless I'm missing a setting. This was the same with the last version
Not a deal breaker
Installed Chil360's latest AOSP_QUICHE Android 10 June updates(Clean install).
AOSiP-10-Quiche-osprey-20200605.zip
All working well including FM Radio. Updated TWRP using the APP to 3.3.1 as the TWRP clock and date went funky but may not be related.
Phone is still rooted with Magisk and Root removed before installing clean and then re-rooted and Magisk updated.
Nice editing option to move Software buttons around in the AOSP roms. When texting I have a habit of hitting the Home button making my SMS app disappear. I've moved my Home button a little off-centre more to the right(I'm right handed) and this has cured that
Update. The Rom is working well but it's doesn't feel as slick as the AOSP_PIZZA version(May version) so I've gone back to that for now just out of personal preference.
So presently my faves are Havoc 3.4 and Havoc 3.6(Android 10) 2020 and AOSP_PIZZA Android 9 May 2020 version(Moto Stitch Boot animation).
Again my ongoing thanks for CHIL360's work in keeping these great little phones updated
Latest Android 10 Havoc 3.6 released by Chil360 with June 2020 updates,
https://chil360.github.io/ten.html
Gapps included.
Installed and all working e.g Text/Calls/GPS/FM Radio/ WiFi/WiFi Hotspot/Camera/Bluetooth etc.
Very fast booting and really slick
One possible glitch is the Stock Camera has the option to Save to SD but it doesn't seem to work. As I rarely use the Stock Camera preferring the much better,"Open Camera" from the Playstore this is not an issue for me
PS
Because of the dedication of the Android Developers on here we have an old 2015 Phone/s with more up-to-date software than many brand new phones
Chil360 has released a first and new Rom to his collection. Android 10 PixelExperience Plus 10.0,
https://chil360.github.io
If you like Google I think you will like this
I wonder if he might be looking to work on the new Android 11 if it can be used on the Moto G3
Then install Gapps if required.
Then do another Factory reset for good measure.
If ever there's a problem when first setting up after the first boot-up has loaded just press and hold the Power Button in for around 10/15 seconds and the phone will reboot(Soft Reset) which emulates taking the Battery out. [/B]
Chil360 has released a new Rom,
potato_osprey-10-20200619-croquette.v3.2.0+15.Community.zip
Unfortunately I cannot test it as it boot-loops.
Tried all my tricks but no good
Gone back to Havoc 3.6
Latest POSP Croquette v3.2.0-hotfix+16 loads but no FM radio so no good to me
Back to Havoc 3.6(Android 10)/ AOSP_PIZZA Android 9 May version
July 2020 Havoc 3.7 released by Chil360.
Installed clean and running well
The Havoc 3.7 July 2020 release by Chil360 IMO is the best and most stable custom rom I've tested for Moto g3 2015 (osprey) and is highly customizable. I especially like the "smart battery charger" feature which allows the charger to be set at a maximum percentage in my case 92%. I have not found any other custom rom with this feature. This will help prolong the battery life by not charging it to 100% every time. The July 2020 release installed fine and is running with no apparent problems. I tried the latest "official" lineageos version July 3 2020 but had problems with random spontaneous reboots.
Hey guys,
since I dont get neither Netflix nor Disney+ to work on my TB-X704F after having flashed LOS 16, I want to go back to stock rom. I've already tried to use Lenovo Smart Assistant but the flashing procedure always fails. I also tried QComLoader but also fails at 5%.
Is there a working way on going back to stock rom having TRWP ans LOS 16 installed???
Due to the fact that Netflix and Disney+ arent working (already tried Magisk module to change the tablets' fingerprint), I need to go back to stock rom.
Thanks in advance!!!!
Please use this tool to flash the stock rom: https://qfiltool.com/qfil-tool-v2-0-2-3
need help here. I'm flashed LineageOS previously. Can't install NetFlix hence i want to switch back to stock. I've installed the drivers and QFIL software. however when the device is off, i hold the volume up button then plug in the usb, but the QFIL software still show port not available. I entered the TWRP screen asking me to whether i can choose Boot to FFBM. Restart Bootloader.. etc. what should i choose?
I assume by "magisk module", you mean the termux props method? That's worked for me on several devices.
Also I really don't know how I can help you past that, most stock firmwares aren't designed to be flashed on modified devices. Very few manufacturers even support that (Samsung, LG and OnePlus are falriy major exceptions)
Edit: just realised the age of the thread, apologies.
rhchia said:
need help here. I'm flashed LineageOS previously. Can't install NetFlix hence i want to switch back to stock. I've installed the drivers and QFIL software. however when the device is off, i hold the volume up button then plug in the usb, but the QFIL software still show port not available. I entered the TWRP screen asking me to whether i can choose Boot to FFBM. Restart Bootloader.. etc. what should i choose?
Click to expand...
Click to collapse
I've got the same problem. What did you do in the end?
K14_Deploy said:
I assume by "magisk module", you mean the termux props method? That's worked for me on several devices.
Also I really don't know how I can help you past that, most stock firmwares aren't designed to be flashed on modified devices. Very few manufacturers even support that (Samsung, LG and OnePlus are falriy major exceptions)
Edit: just realised the age of the thread, apologies.
Click to expand...
Click to collapse
What exactly is the termux props method?
Is that to fix Magisk not authenticating? Or to allow the tool QFIL to restore stock?
boomhaueruk said:
What exactly is the termux props method?
Is that to fix Magisk not authenticating? Or to allow the tool QFIL to restore stock?
Click to expand...
Click to collapse
I mean the MagiskHide Props Config, which requires Termux. Basically you install the module, give Termux root and configure props with it. Then you use MagiskHide to hide magisk from them.
On the topic of reverting to stock, it's not possible. Custom firmware is almost always a one way process, and you understand if you do it things like the OP has described can and will happen. People who want things to "just work" use stock firmware, or an Apple device, it was never designed to not need tinkering.
K14_Deploy said:
I mean the MagiskHide Props Config, which requires Termux. Basically you install the module, give Termux root and configure props with it. Then you use MagiskHide to hide magisk from them.
On the topic of reverting to stock, it's not possible. Custom firmware is almost always a one way process, and you understand if you do it things like the OP has described can and will happen. People who want things to "just work" use stock firmware, or an Apple device, it was never designed to not need tinkering.
Click to expand...
Click to collapse
Goodness, I'm not a person who needs a 'just work' situation. It took weeks to get this onto stock and I've spent a long time reading up trying to fix Magisk. Surely there has to be a point when you're actually using the device and not just fixing it!
Basic things like being able to download and use apps...that seems like a reasonable request.
I think there's 'tinkering' and 'it doesn't work!'
Also, I've rolled back to stock roms before on various phones, recovery and so on - not with this tablet admittedly. Surprised it seems such a difficult or - as you say - impossible process. But hey.
That said, I appreciate the help! I really do.
So; I need to find 'Termux'. https://termux.com/
This says I get it from 'F Droid'. But I then found a link on their webpage to this;
https://f-droid.org/repo/com.termux_117.apk
I'm assuming that's the right one.
It looks like a terminal?
Googling for Termux Magiskhide props config got me to this youtube video;
It's in Indonesian, but shows you some steps. Would that be the best place to find instructions?
boomhaueruk said:
Goodness, I'm not a person who needs a 'just work' situation. It took weeks to get this onto stock and I've spent a long time reading up trying to fix Magisk. Surely there has to be a point when you're actually using the device and not just fixing it!
Basic things like being able to download and use apps...that seems like a reasonable request.
I think there's 'tinkering' and 'it doesn't work!'
Also, I've rolled back to stock roms before on various phones, recovery and so on - not with this tablet admittedly. Surprised it seems such a difficult or - as you say - impossible process. But hey.
That said, I appreciate the help! I really do.
So; I need to find 'Termux'. https://termux.com/
This says I get it from 'F Droid'. But I then found a link on their webpage to this;
https://f-droid.org/repo/com.termux_117.apk
I'm assuming that's the right one.
It looks like a terminal?
Googling for Termux Magiskhide props config got me to this youtube video;
It's in Indonesian, but shows you some steps. Would that be the best place to find instructions?
Click to expand...
Click to collapse
Is this going to be a problem?
Magisk is dropping support for hiding root access from apps
Magisk, the popular Android rooting tool, will continue to be developed by topjohnwu, but without its root hiding feature called MagiskHide.
www.xda-developers.com
boomhaueruk said:
Goodness, I'm not a person who needs a 'just work' situation. It took weeks to get this onto stock and I've spent a long time reading up trying to fix Magisk. Surely there has to be a point when you're actually using the device and not just fixing it!
Basic things like being able to download and use apps...that seems like a reasonable request.
I think there's 'tinkering' and 'it doesn't work!'
Also, I've rolled back to stock roms before on various phones, recovery and so on - not with this tablet admittedly. Surprised it seems such a difficult or - as you say - impossible process. But hey.
That said, I appreciate the help! I really do.
So; I need to find 'Termux'. https://termux.com/
This says I get it from 'F Droid'. But I then found a link on their webpage to this;
https://f-droid.org/repo/com.termux_117.apk
I'm assuming that's the right one.
It looks like a terminal?
Googling for Termux Magiskhide props config got me to this youtube video;
It's in Indonesian, but shows you some steps. Would that be the best place to find instructions?
Click to expand...
Click to collapse
You can install Termux from the Play Store if you have GApps. I did and it worked. And yes, it is a terminal. I've just upgraded to 17.1 on this device so I'm going to be doing it again sooner rather than later anyway.
K14_Deploy said:
You can install Termux from the Play Store if you have GApps. I did and it worked. And yes, it is a terminal. I've just upgraded to 17.1 on this device so I'm going to be doing it again sooner rather than later anyway.
Click to expand...
Click to collapse
Thanks.
I guess my other issue is I'm not actually sure what steps I'm supposed to do next.
That youtube video looks really dodgy!
It's nice to find someone else on this device. Mine has sat unused for months, I've decided to finally either get it to work properly or bin it. Todays the day.
boomhaueruk said:
Thanks.
I guess my other issue is I'm not actually sure what steps I'm supposed to do next.
That youtube video looks really dodgy!
Click to expand...
Click to collapse
Ok, so...
Make sure Magisk has "MagiskHide Props Config" and "Busybox For Android NDK" and root fully enabled. Hide must be disabled. If this isn't the case, do so and then reboot.
Open Termux. Type 'su' to give root access. Then type 'props' and follow the menu for your device. Type '1' for 'Edit device fingerprint'. Type 'f' for 'Pick a certified fingerprint'. Type '13' for 'Lenovo'. Type '2' for 'Lenovo Tab 4 8 Plus TB-8704F (8.1.0)'. If you have another device you might be out of luck. Type 'y' for 'yes'. Wait. Type 'y' again to reboot.
Configure MagiskHide to hide these parts of GPS + any other root sensitive apps. The screenshot I have was taken from a OnePlus but it shows the GPS that needs to be hidden. The less you can get away with hiding the better for performance reasons. Also make sure to repackage Magisk as 'Settings' and change the name of the 'TWRP' folder using a root file explorer (for some reason I don't have one) to... I'm partial to 'f**kyougoogle' personally, but anything will do. Reboot again and Disney+ should work just fine. If it doesn't, I can't help you.
I'd recommend moving to 18.1 before doing this, you'll have to start from square 1 but it means you're more up to date and won't have to do it again until someone builds 19.1 for this device. Can confirm, that build works.
This isn't without risk. Some apps specifically wanting android 11 might not work right. But it SHOULD fix root sensitive apps that use Safetynet. I also can't say anything about Widevine compatibility as I don't have Disney+ on this device.
boomhaueruk said:
Thanks.
I guess my other issue is I'm not actually sure what steps I'm supposed to do next.
That youtube video looks really dodgy!
It's nice to find someone else on this device. Mine has sat unused for months, I've decided to finally either get it to work properly or bin it. Todays the day.
Click to expand...
Click to collapse
K14_Deploy said:
Ok, so...
Make sure Magisk has "MagiskHide Props Config" and "Busybox For Android NDK" and root fully enabled. Hide must be disabled. If this isn't the case, do so and then reboot.
Open Termux. Type 'su' to give root access. Then type 'props' and follow the menu for your device. Type '1' for 'Edit device fingerprint'. Type 'f' for 'Pick a certified fingerprint'. Type '13' for 'Lenovo'. Type '2' for 'Lenovo Tab 4 8 Plus TB-8704F (8.1.0)'. If you have another device you might be out of luck. Type 'y' for 'yes'. Wait. Type 'y' again to reboot.
Configure MagiskHide to hide these parts of GPS + any other root sensitive apps. The screenshot I have was taken from a OnePlus but it shows the GPS that needs to be hidden. The less you can get away with hiding the better for performance reasons. Also make sure to repackage Magisk as 'Settings' and change the name of the 'TWRP' folder using a root file explorer (for some reason I don't have one) to... I'm partial to 'f**kyougoogle' personally, but anything will do. Reboot again and Disney+ should work just fine. If it doesn't, I can't help you.
I'd recommend moving to 18.1 before doing this, you'll have to start from square 1 but it means you're more up to date and won't have to do it again until someone builds 19.1 for this device. Can confirm, that build works.
This isn't without risk. Some apps specifically wanting android 11 might not work right. But it SHOULD fix root sensitive apps that use Safetynet. I also can't say anything about Widevine compatibility as I don't have Disney+ on this device.
Click to expand...
Click to collapse
Thanks.
OK. So, I've attached a few pics to show you where I am.
Booted, checked into Magisk for those settings. I can see 'Magiskhide', so I can untick that, but how do I ensure "Magisk has "MagiskHide Props Config" and "Busybox For Android NDK" and root fully enabled"
Root wise, I'm pretty sure it is, but yes, not sure how I double check!
boomhaueruk said:
Thanks.
OK. So, I've attached a few pics to show you where I am.
Booted, checked into Magisk for those settings. I can see 'Magiskhide', so I can untick that, but how do I ensure "Magisk has "MagiskHide Props Config" and "Busybox For Android NDK" and root fully enabled"
Root wise, I'm pretty sure it is, but yes, not sure how I double check!
Click to expand...
Click to collapse
They are Magisk modules, you go to there the puzzle piece is and search for them.
boomhaueruk said:
Thanks.
OK. So, I've attached a few pics to show you where I am.
Booted, checked into Magisk for those settings. I can see 'Magiskhide', so I can untick that, but how do I ensure "Magisk has "MagiskHide Props Config" and "Busybox For Android NDK" and root fully enabled"
Root wise, I'm pretty sure it is, but yes, not sure how I double check!
Click to expand...
Click to collapse
OK, found 'root checker' on the play store. And Termux.
so I have root.
K14_Deploy said:
They are Magisk modules, you go to there the puzzle piece is and search for them.
Click to expand...
Click to collapse
Ah! Got it. Ok, went into Magisk, went to the puzzle piece, found them both and...
Ah, I've just seen you've said "I'd recommend moving to 18.1 before doing this, you'll have to start from square 1 but it means you're more up to date and won't have to do it again until someone builds 19.1 for this device. Can confirm, that build works."
Right. I'd better go and find all the instructions for that. I've forgotten how I got this thing onto custom firmware, but I've got recovery installed.
boomhaueruk said:
Ah! Got it. Ok, went into Magisk, went to the puzzle piece, found them both and...
Ah, I've just seen you've said "I'd recommend moving to 18.1 before doing this, you'll have to start from square 1 but it means you're more up to date and won't have to do it again until someone builds 19.1 for this device. Can confirm, that build works."
Right. I'd better go and find all the instructions for that. I've forgotten how I got this thing onto custom firmware, but I've got recovery installed.
Click to expand...
Click to collapse
Go to the 18.1 thread on this forum and look for the instructions for flashing without being on stock. Also use TWRP 3.4.0.0. You will need a computer, as you have to wipe internal storage and use ADB.
K14_Deploy said:
Go to the 18.1 thread on this forum and look for the instructions for flashing without being on stock. Also use TWRP 3.4.0.0. You will need a computer.
Click to expand...
Click to collapse
I may stay where I am on Android 9. I've just seen it doesn't support sim and I sort of need that.
I can always come back and do that later, right?
I'm a bit worried about bricking it too. I might just get myself onto Android 9 working with the fix for now. It took me so long to get it onto custom rom the first time.
boomhaueruk said:
I may stay where I am on Android 9. I've just seen it doesn't support sim and I sort of need that.
I can always come back and do that later, right?
I'm a bit worried about bricking it too. I might just get myself onto Android 9 working with the fix for now. It took me so long to get it onto custom rom the first time.
Click to expand...
Click to collapse
Yeah of course, but you will have to start over if / when you upgrade
Ah. Hit a snag.
You said "Type '2' for 'Lenovo Tab 4 8 Plus TB-8704F (8.1.0)"
I've got the TB-8704L, the 10 inch.
Let me see if anythings listed.
DON'T DO THIS ON A RAZER PHONE 1 OR IT WILL BE OMEGA BRICKED! ONLY DO THIS ON A RAZER PHONE 2!
This was just an experiment to see if i could cobble together some GSI install guides (that on their own are kinda confusing) to make something moderately more cohesive and understandable. Here's my moderately usable guide!
-----------------------------------------------------------------
VIDEO!
-----------------------------------------------------------------
-----------------------------------------------------------------
Things that work and don't work:
-----------------------------------------------------------------
This section will update periodically as issues arise or fixes arise for said issues.
Note: Things that work: Bluetooth*, all sensors, audio, LTE/SIM/phone stuff, 120hz (you need to go into the settings > Phh treble settings > Misc features > Force FPS > [email protected])
Things that probably work: N/A
Things that don't work for some reason: SafteyNet with Magisk. All modules that I've used work tho...??! Verizon.
Remember, you can always flash back to stock if something doesn't work properly.
-----------------------------------------------------------------
FIXES!!!
-----------------------------------------------------------------
AUDIO FIX!!! GO TO Phh Treble Settings > Qualcomm features > Use alternate audio policy.
Bluetooth audio stops working with this enabled. Disable it for Bluetooth audio. The audio fix doesn't apply to Bluetooth audio ether way.
BLUETOOTH FIX!!! Download a root file browser from the google play store and allow it to have root access. Delete BluetoothCommonRes.apk which is found in the overlay folder which is found in the vendor folder. After you delete BluetoothCommonRes.apk, rename the RazerAuraBluetoothRes.apk to BluetoothCommonRes.apk.
-----------------------------------------------------------------
Important notes
-----------------------------------------------------------------
THIS IS ASSUMING YOU HAVE ALREADY UNLOCKED THE BOOTLOADER OF YOUR DEVICE AND HAVE GOTTEN A SERIAL NUMBER OUTPUT FROM CMD AFTER TYPING IN "fastboot devices" AND MAKE SURE YOU HAVE TYPED IN "fastboot flashing unlock" AND "fastboot flashing unlock-critical".
***NOTE: I AM NOT RESPONSIBLE FOR ANY HARD BRICKED DEVICES OR ANGRY PARENTS. PLEASE DO NOT COME BACK AT ME SAYING I AM STUPID AND BRICKED YOUR PHONE. YOU DECIDED TO DO THIS. PLEASE PROCEED WITH CAUTION AND DON'T SKIM***
ANOTHER IMPORTANT NOTE: The stock firmware is actually really good for unbricking devices. Razer made it easy to fix your bricked device. So basically, if you can get in to fastboot mode, (which you basically always can do) you can unbrick your device super easily.
AGAIN JUST PLEASE, MAKE SURE TO FOLLOW ALL THESE INSTRUCTIONS CAREFULLY AND DONT SKIM OR ELSE YOU MIGHT BREAK SOMETHING!!!
-----------------------------------------------------------------
Introduction
-----------------------------------------------------------------
This is a quick and easy guide for how to install Android 11 on the Razer Phone 2. I'm kind of a noob here myself but I did this and it worked flawlessly. (also if you do run into any issues PLEASE don't count on me for troubleshooting tips (I'm not that great at that))
-----------------------------------------------------------------
Pre-requisites/Downloads
-----------------------------------------------------------------
Get the factory firmware for your phone. It's a good failsafe in case of a bootloop or a bad case of the phone not booting up. Download it here: P-SMR6-RC001-RZR-201022 (latest build at the time of writing)
Extract this with 7zip or WinRar (or windows. You will need 7zip or WinRar for the rest of this)
First you need the actual GSI. Get the latest version. (Make sure its not a pre-release). system-roar-arm64-ab-vndklite-gapps.img.xz is the version that you should get. The vndklite release will allow you to modify the system partition making it possible to get magisk. Note: If you want magisk, MAKE SURE TO COMPLETELY follow the magisk section of this guide aswell or else magisk will NOT install correctly and will NOT work.
This version also has GApps. It will give you Gmail, the google play store, google play services, etc.
Use 7zip or WinRar to extract this.
Your also gonna need the Trinity Kernel (v2). This gives you TWRP and I'm pretty sure you also need this to have the ability to boot up the phone (I may be wrong but it's required.)
use 7zip or WinRar to extract this.
You will also need this zip file made by arter97 I don't really know what it does but you need it. here is the download: Download.
Don't extract this.
Put all these in a known folder that you can access later.
Alright. Now that we're done with the downloads, time to test to make sure your ready to put this on your phone.
-----------------------------------------------------------------
Making sure your computer is ready
-----------------------------------------------------------------
First things first. Go open your platform tools folder, shift-right click and open a PowerShell, or command prompt window there. Shut down your Razer phone 2 and turn it back on with the power and volume down buttons.
Plug it into your PC and type in
Code:
fastboot devices
you should end up with the serial number of the device. if you don't, follow Razer's instructions on how to install USB drivers and then come back here. Link to PDF.
If you get a serial number, close that and flash stock firmware by going into the aura-p-release-etc. folder, then opening flash_all.bat.
When it finishes and the screen goes black, hold the power and volume down buttons again to get back in to fastboot mode.
open back up the CMD/PowerShell platform tools window thing again.
-----------------------------------------------------------------
Installing/Flashing
-----------------------------------------------------------------
In your CMD or PowerShell window, (while in fastboot mode on the phone) type
Code:
fastboot flash system <file name>
in the <file name> area, just drag and drop the system-roar-arm64-etc.img file into your command line. your command will look a little something like this:
Code:
fastboot flash system C:\Users\user\Desktop\system-roar-arm64-ab-gapps.img
Wait until it says complete or something similar like done or something and has no errors.
Then, time to flash the kernel. it should just be called boot.img.
We will be typing in:
Code:
fastboot flash boot <file name>
Do the same thing that you did for the last command which is drag and drop the boot.img file for the file name.
Again, wait until it says done or complete and has no errors.
After that is done, use the volume buttons to select reboot bootloader with your power button on your phone.
Go to recovery mode and swipe where it says to swipe.
Go to the wipe menu and then tap on format data. Type yes and then press enter/ok.
Go back to your computer and open file explorer.
Put the last zip file that I was talking about earlier (the f2fs thing) on the razer phone 2's internal storage. Head back to your phone, and press install.
Scroll down until you find the zip file and press it and install it. (ignore the errors that may or may not be there) After that, go back to the TWRP home screen (with the 8 options)
Go to the reboot menu, then reboot into recovery
Tap on format data and type in "yes" and tap ok. click on "don't install" because you don't need the TWRP app on your phone.
The phone will shut down. Turn it on normally and everything will work!
----------------------------------------------------------------------------------------------------------------------------------
GET THESE THINGS IF YOU WANT 120Hz, GCam, and a SNAZZY RAZER LOGO.
----------------------------------------------------------------------------------------------------------------------------------
To get 120Hz, you need to go into the settings > Phh treble settings > Misc features > Force FPS > [email protected].
If you want your Razer logo to light up again, use Logo+. here is a download: Logo+ APK
The default camera app sucks. Make sure to get GCam 7.4 from Cyanogen Mods (v8.0 is broken). you can get it here.
Download a root file browser from the google play store and allow it to have root access. Delete BluetoothCommonRes.apk which is found in the overlay folder which is found in the vendor folder. After you delete BluetoothCommonRes.apk, rename the RazerAuraBluetoothRes.apk to BluetoothCommonRes.apk.
-----------------------------------------------------------------
Magisk
-----------------------------------------------------------------
So this part was pretty long-awaited. It half-passes SafteyNet and modules work! (at least all the modules that I've used.)
Make sure you have the vndklite variant. That is the only way that this will work.
1. Open up an adb/fastboot powershell/cmd/windows terminal window.
2. Type adb root and hit enter.
3. Type adb shell and hit enter.
4. Type mount -o remount,rw / and hit enter.
5. Type mv /bin/resetprop_phh /bin/phh-resetprop and hit enter.
6. Type phh-securize.sh and hit enter.
The phone should reboot after you approve the request (if there is one) and you are now able to install magisk!
MAKE SURE THAT THE SUPERUSER APP IS NOT THERE AFTER RUNNING phh-securize.sh.
Get specifically this version of Magisk. Download the zip file.
Boot into TWRP and tap on mount, and select everything (usb storage doesn't matter in this case. it never mounts either way.)
Transfer over your zip file via file explorer, and go back to your phone.
Tap install, then scroll down until you find the zip file and tap it. Swipe to flash and wait. After it is done, you can reboot!
You should see Magisk manager in your app drawer. Open that. It might ask you to install it, if so, install it. Allow apps from this source then install. Open it up. You should see that Magisk is installed. Update it and turn on Magisk hide.
If it passes SafteyNet, it's a miracle.
-----------------------------------------------------------------
In case of failure
-----------------------------------------------------------------
If it starts bootlooping or is perpetually stuck at the razer logo, powered by android screen, go back into fastboot mode and run the flash_all.bat stock firmware thing. it will unbrick your phone automatically. Really make sure you don't skim if you try it again. If it did work (which it probably did), then have a good time with android 11!
There is one bug that has stopped me from going GSI. On every one I've tried, there is a game music bug that is common in many of the games I own. If the volume is set to below 50%, the music will cut in and out constantly. It resolves itself if you keep media volume above 50%. It may not be a deal breaker for everyone, but it was for me, as I use my RP2 heavily for games. Other than that, GSIs work beautifully. Thanks for the comprehensive guide!
Reznor7 said:
There is one bug that has stopped me from going GSI. On every one I've tried, there is a game music bug that is common in many of the games I own. If the volume is set to below 50%, the music will cut in and out constantly. It resolves itself if you keep media volume above 50%. It may not be a deal breaker for everyone, but it was for me, as I use my RP2 heavily for games. Other than that, GSIs work beautifully. Thanks for the comprehensive guide!
Click to expand...
Click to collapse
Just curious, what games have that issue?
Marcos8760 said:
Just curious, what games have that issue?
Click to expand...
Click to collapse
All of The Room games, Battle Chasers: Night War, and most premium games that I've bought. For some reason, Monster Hunter Stories doesn't. It seems like mostly games that have more complex audio/music.
Reznor7 said:
All of The Room games, Battle Chasers: Night War, and most premium games that I've bought. For some reason, Monster Hunter Stories doesn't. It seems like mostly games that have more complex audio/music.
Click to expand...
Click to collapse
Thanks for the info. I added that to the top of the thread.
EDIT: Fix at the top of the thread
Ultimately at the end of the day I could not get Dolby Atmos and the RGB lighting on the back of the phone to work on GSI 10. Hopefully someone will come up with a work around for those 2 items in GSI 11.
RJR
rrusek said:
Ultimately at the end of the day I could not get Dolby Atmos and the RGB lighting on the back of the phone to work on GSI 10. Hopefully someone will come up with a work around for those 2 items in GSI 11.
RJR
Click to expand...
Click to collapse
I got the Razer logo working flawlessly with logo+. I didn't really see the appeal for Dolby Atmos as all it did was made it louder and made the audio clip more.
I did have success getting Atmos to work with this module: https://github.com/reiryuki/Dolby-Atmos-Razer-Phone-2-Magisk-Module
Reznor7 said:
I did have success getting Atmos to work with this module: https://github.com/reiryuki/Dolby-Atmos-Razer-Phone-2-Magisk-Module
Click to expand...
Click to collapse
How can I get magisk on the phone though? it has Superuser pre-installed but it doesn't have support for modules and stuff (as far as I can tell). I really would like some info on how to install magisk if possible.
Marcos8760 said:
How can I get magisk on the phone though? it has Superuser pre-installed but it doesn't have support for modules and stuff (as far as I can tell). I really would like some info on how to install magisk if possible.
Click to expand...
Click to collapse
Actually, I may be misremembering. That may have been on a 10 GSI. I don't think I ever did get Magisk to work on an 11.
Reznor7 said:
Actually, I may be misremembering. That may have been on a 10 GSI. I don't think I ever did get Magisk to work on an 11.
Click to expand...
Click to collapse
Alright good to know. like the other info I've gathered, ill put that at the top of the thread until further notice.
The unofficial LOS GSI just got updated with supposed Magisk support. I'm going to give it a try in a few.
Reznor7 said:
The unofficial LOS GSI just got updated with supposed Magisk support. I'm going to give it a try in a few.
Click to expand...
Click to collapse
Nope, Magisk doesn't work.
Thank you. I got it all set up and mostly working well. I was wondering if you could try Minecraft and let me know if it will let you get to the actual login screen.
I cannot get flashing the Android 11 GSI to work.
I downloaded the latest factory image (MR6) and proceeded to install it. To do that, I had to copy the "fastboot.exe" from the SDK platform tools download to the "aura-p-release..." folder with the factory image.
I open a CMD line and type in "fastboot devices" which get me a string of numbers. Then I type in "fastboot flash system system-roar-arm64-ab-gapps.img.xz" which tries to install it but concludes with an error message, being 'Error: Last flash failed : Bad Buffer Size'.
I tried using different computers and cables, but I end up with the same thing. I'm able to flash the factory image just fine, but can't flash Android 11.
AgentXGhost said:
I cannot get flashing the Android 11 GSI to work.
I downloaded the latest factory image (MR6) and proceeded to install it. To do that, I had to copy the "fastboot.exe" from the SDK platform tools download to the "aura-p-release..." folder with the factory image.
I open a CMD line and type in "fastboot devices" which get me a string of numbers. Then I type in "fastboot flash system system-roar-arm64-ab-gapps.img.xz" which tries to install it but concludes with an error message, being 'Error: Last flash failed : Bad Buffer Size'.
I tried using different computers and cables, but I end up with the same thing. I'm able to flash the factory image just fine, but can't flash Android 11.
Click to expand...
Click to collapse
You forgot to extract it with winrar or 7zip. make sure it is a .img file and not a .xz file.
Wow. I spent close to 7 hours trying and trying again. But that's what I get when I don't read all the instructions. -____-
Thanks very much. It works perfectly.
AgentXGhost said:
Wow. I spent close to 7 hours trying and trying again. But that's what I get when I don't read all the instructions. -____-
Click to expand...
Click to collapse
oh noes!
When in TWRP, the system is not mounted, and I cannot see it on my PC nor in TWRP itself. Any ideas what I did wrong?
Gurcharan5 said:
When in TWRP, the system is not mounted, and I cannot see it on my PC nor in TWRP itself. Any ideas what I did wrong?
Click to expand...
Click to collapse
Try going to wipe, then format data. That might fix the problem. If not, try everything again.