Related
Hello, and welcome to a short and sweet guide on the way I have found to successfully root our device, the blu studio energy 2!
DISCLAIMER - I am not a developer, and any knowledge I have has come from reading forums and tinkering with android devices I have owned. If you are reading this, you should know that I do not guarantee these steps will work for you, and will not be responsible for any damage this causes your device.
THINGS YOU WILL NEED
1. MTK VCOM Drivers Installed (Guide on XDA)
2. SP Flash Tool
3. Scatter file (modified from Gionee M4 version to match our partition table, attached)
4. TWRP Recovery ported to M4 by Hanuma50
5. SuperSU Flashable ZIP
PROCEDURE
1. Open SPFT, and load the modified scatter file
2. Click the Download Tab, and edit the settings as follows:
A. Make sure 'Download Only' is selected
B. Only Recovery Partition box is checked
C. Make sure correct scatter is loaded3. Double click in 'Location' field next to recovery partition(screenshot highlighted in blue), and select Gionee M4 TWRP recovery.img
4. Click "Download" Button
5. Download/Copy SuperSU zip to phone
6. Power off phone
7. With "Download" button clicked in SPFT, connect phone to USB without powering on (VCOM DRIVERS MUST BE INSTALLED FOR THIS TO WORK)
8. Wait for SPFT to flash, popup with green check-mark will display when complete
9. Disconnect phone from USB, hold power + volume-up keys until boot into TWRP Recovery
10. Install SuperSU zip from TWRP
11. Reboot into system, you are now successfully rooted and with custom recovery!
From this point on, you can install any app needing root, and also perform full nandroid backups using TWRP on Blu Studio Energy 2.
TECHNICAL INFO
For anyone interested in what I have done, it is all very simple, and any credit should go to Hanuma50 at Needrom for porting TWRP to Gionee M4!
The reason we can use Gionee roms/recoveries on our device is because Blu devices are just rebranded (usually Gionee) phones sold in the US. So, all that I have done is use SP Flash tools to load an M4 recovery on our device!
The only real change needed was to change the scatter file, because apparently Gionee uses some different partition sizes than Blu does. Don't worry though, the recovery partitions are exactly the same, and the scatter changes are only to avoid errors that show up without them.
I changed the scatter to reflect the partition sizes/locations found in /proc/partinfo on our Blu phones. This is very easy and if someone is getting 'PMT changed' error in SPFT trying to do this on another MT6735 device, try changing the scatter hex values to match your partinfo file :fingers-crossed:
Just followed your instructions and seems to be working flawlessly!
I didn't have to first flash the drivers because I had already done that previously. When you connect the blu studio energy 2 to your computer via usb, it popus up with a cd of the drivers which you can install.
Thank you! This will make this phone so much better. Also, I must have been using an old version of twrp, because this version has a beautiful UI!
Any suggestions for programs to free or remove, now that we have root access? I am looking forward to messing with this phone now.
I tried installing xposed but was unsuccessful. Have you tried this? Thanks again.
Glad it worked out!
Have just been starting to mess with I thyself to be honest, I actually have gotten xposed to install, haven't gotten gravity box working yet. I installed xposed arm-64 sdk 21.
On a friend's phone I have flashed gionee m4 stock rom, which works really well and seems nicer in some respects to the Blu stock, but I am hesitant to flash it since I haven't found a foolproof way to backup the stock before flashing.
EDIT - I actually got gravity box working, using sdk21 arm64 xposed installer. Everything works really well surprisingly I've had more luck than on my old nexus 4 running stock 5.1. Everything works fine for me, except for power menu, and i think that's just about it for everything else I've tried. QS remapping and navigation button remappiny works great, hope it works for you too!
Outer then that, I have installed adaway and some other apps needing root and they work well. Hopefully we can start getting some nice development for this phone or the m4 in the near future!
danageis said:
Glad it worked out!
Have just been starting to mess with I thyself to be honest, I actually have gotten xposed to install, haven't gotten gravity box working yet. I installed xposed arm-64 sdk 21.
On a friend's phone I have flashed gionee m4 stock rom, which works really well and seems nicer in some respects to the Blu stock, but I am hesitant to flash it since I haven't found a foolproof way to backup the stock before flashing.
EDIT - I actually got gravity box working, using sdk21 arm64 xposed installer. Everything works really well surprisingly I've had more luck than on my old nexus 4 running stock 5.1. Everything works fine for me, except for power menu, and i think that's just about it for everything else I've tried. QS remapping and navigation button remappiny works great, hope it works for you too!
Outer then that, I have installed adaway and some other apps needing root and they work well. Hopefully we can start getting some nice development for this phone or the m4 in the near future!
Click to expand...
Click to collapse
Thanks, I thought I tried that version of the installer but I guess not. I'll give it another shot. Can't wait to see what kind of further dev work we get!
I flashed the 78 sdk21 64 zip for xposed but when I reboot it says optimizing apps and then reboots.
Any idea what I might be doing wrong?
portezbie said:
I flashed the 78 sdk21 64 zip for xposed but when I reboot it says optimizing apps and then reboots.
Any idea what I might be doing wrong?
Click to expand...
Click to collapse
Mine did that too, you have to let it do it's thing. It will say optimizing, and keep rebooting, but after every reboot it SHOULD have 1 or 2 fewer apps listed that it says its optimizing. Pretty weird, but afterward it does seem to have installed correctly. It took my phone about 25 minutes of the rebooting, but afterwards I haven't noticed any issues with xposed/gravity box LP.
danageis said:
Mine did that too, you have to let it do it's thing. It will say optimizing, and keep rebooting, but after every reboot it SHOULD have 1 or 2 fewer apps listed that it says its optimizing. Pretty weird, but afterward it does seem to have installed correctly. It took my phone about 25 minutes of the rebooting, but afterwards I haven't noticed any issues with xposed/gravity box LP.
Click to expand...
Click to collapse
Oh weird. Thanks for the explanation!
Just curious, have you had any trouble playing music on your phone? I have problems playing through aux and Bluetooth.
danageis said:
Just curious, have you had any trouble playing music on your phone? I have problems playing through aux and Bluetooth.
Click to expand...
Click to collapse
What kind of problems are you having? I've only used my energy 2 with headphones and once briefly with a bluetooth speaker just to test it. I've had no trouble with headphones and my brief test with bluetooth audio seemed fine.
If you tell me what problems you're having I can try and test it.
portezbie said:
What kind of problems are you having? I've only used my energy 2 with headphones and once briefly with a bluetooth speaker just to test it. I've had no trouble with headphones and my brief test with bluetooth audio seemed fine.
If you tell me what problems you're having I can try and test it.
Click to expand...
Click to collapse
Ok thanks!
The problem I'm having with aux connection is that the phone thinks the connection is lost/reconnected every few seconds. So after a while, the music will either keep pausing itself, or cut out every few seconds. I have only had this problem with aux cables into stereos, but I have tried multiple cables with the results.
With Bluetooth, there are stutters in the audio.
I have actually returned the first phone I got to amazon because of this problem, and the second one did the same thing, but maybe I really did just get two duds in a row?
Thanks for your help!
danageis said:
Ok thanks!
The problem I'm having with aux connection is that the phone thinks the connection is lost/reconnected every few seconds. So after a while, the music will either keep pausing itself, or cut out every few seconds. I have only had this problem with aux cables into stereos, but I have tried multiple cables with the results.
With Bluetooth, there are stutters in the audio.
I have actually returned the first phone I got to amazon because of this problem, and the second one did the same thing, but maybe I really did just get two duds in a row?
Thanks for your help!
Click to expand...
Click to collapse
So I just used the bluetooth speaker in my shower for 20 minutes to listen to pandora. I did not notice any stuttering. I will try hooking up the phone to my stereo tomorrow and seeing what happens.
portezbie said:
So I just used the bluetooth speaker in my shower for 20 minutes to listen to pandora. I did not notice any stuttering. I will try hooking up the phone to my stereo tomorrow and seeing what happens.
Click to expand...
Click to collapse
Hmmm, weird... well thanks for your help!
danageis said:
Hmmm, weird... well thanks for your help!
Click to expand...
Click to collapse
Connected it to my stereo with a standard 3.5mm cable and listened to a podcast with pocketcast. Didn't experience any problems.
portezbie said:
Connected it to my stereo with a standard 3.5mm cable and listened to a podcast with pocketcast. Didn't experience any problems.
Click to expand...
Click to collapse
Hmm... Well, thanks for checking. I'm not sure why I'm having so many problems...
danageis said:
Hmm... Well, thanks for checking. I'm not sure why I'm having so many problems...
Click to expand...
Click to collapse
I'm trying to think what could be different. I haven't installed xposed on my phone, maybe it is something related to that, or some other change that you have made and I haven't?
portezbie said:
I'm trying to think what could be different. I haven't installed xposed on my phone, maybe it is something related to that, or some other change that you have made and I haven't?
Click to expand...
Click to collapse
I'm not sure, I have tried it out with the same problems on both phones, right after I got them from Amazon, before I made any changes
danageis said:
I'm not sure, I have tried it out with the same problems on both phones, right after I got them from Amazon, before I made any changes
Click to expand...
Click to collapse
Crazy. I have no idea then.
I received this phone yesterday and have been playing around with it. My previous phone was a Samsung Blaze 4G (yes, really old but still chugging along) that was rooted and running Cyanogenmod 10. I am planning on rooting this phone, but was curious if anyone had tried using Kingoroot to do so?
Apologies if this doesn't belong in this thread, I was just curious about the various methods of rooting that might be available.
Cheers!
Update: Kangoroot does not currently root the Blu Studio Energy 2 phone (sorry, I was impatient). I will have a crack at it using your method listed by the OP.
Vinotas said:
Update: Kangoroot does not currently root the Blu Studio Energy 2 phone (sorry, I was impatient). I will have a crack at it using your method listed by the OP.
Click to expand...
Click to collapse
I have tried all the one click root methods I could find and none of them worked. Just use the ops method, it is quite easy and works like a charm.
On an unrelated subject, I tried installing xposed and after reading ops description it worked fine for me. Have had no issues since installing xposed although gravitybox didn't seem to work properly, but I think that is due to the phone's rom. Amplify works great and so does greenify. I am currently testing out powernap, and it seems to work so far.
When Android 7.0 ( Nougat ) is finally released for Motorola X Pure (2015) XT1575 ( Hopefully by the end of the year ), will SystemLess Root still work as is it does now for 6.0 or should we wait for someone to run it in a sandbox? Should we wait for the First Quarter of 2017 before we get anxious and upgrade to the newest Android, to give all of the developer time to perfect they're processes.
We all know now that it will be released as a STOCK image, but I have a lot of Root Apps (i.e. Titainium, Backup, Root Explorer, Xposed, Gravity Box for MM, etc) which I would still like to use. From what I can see of 7.0 it's not much different than 6.0 except for split screen and some other features that I'm sure we.re not aware of yet..
All I can say it It doesn't work on the G4... yet. I maintain a root thread on the G4, haven't found a viable way to root it on Nougat, all methods mess up data and a bunch of framework stuff (like settings menu). I assume the Nougat on this will be roughly the same. Don't worry, it will come though.
And Xposed isn't available for Nougat, it isn't known yet if it will be. Remember when Marshmallow came out they almost dropped Xposed completely, they were so close they had actually said they shutting down development of Xposed then had a unexpected breakthrough. The developers of Xposed have said that it will die in the hear future due to changes in Android.
Yeah, xPosed isn't something I would rely on moving forward. Right now AICP & CM are making great strides with N 7.1 and including Root so you can go that route and get the Root you desire. I'm on TurboROM which is still an MM base and will move to AICP N 7.1 once things settle in some more, but as of right now AICP is pretty darn nice as is. I've tested it every few days to see the progress, but for daily, revert to my most current backup of Turbo for now. AICP usually includes a LARGE amount of customizations. I go that route normally and remove all the AOSP stuff I can replace with Google APPs directly and use Moto Camera instead as well giving me a really clean and functional bug-free experience. GravityBox becomes mostly unnecessary with AICP or CM. Boy I'm rambling worse than normal today...
Back on track... Try out AICP with N 7.1 or wait for a Stock Rooted
Thank you for the reply, I wasn't sure if I should upgrade or not.
My pure has been running pretty good since I got it back in May of this year thru SWAPPA, and I have the latest security mod for May 1 (Build MPHS24.49-18-4), I wasn't sure if Lenovo would push another Security update for 6.0 (MM) or push 7.0 for the next update, and I didn't want to mess anything up..
I love this phone, and I'm not sure if and when I will upgrade, but I know it won't be MOTO/LENOVO anymore, unless they can unlock the bootloader for Pixel and gain root, I may lean that way...
NEVER, NEVER, Never will I go the way of the Apple, anything that comes from that place sucks, it's too restrictive..
DROID Forever !!!!!
CLETjB said:
Thank you for the reply, I wasn't sure if I should upgrade or not.
My pure has been running pretty good since I got it back in May of this year thru SWAPPA, and I have the latest security mod for May 1 (Build MPHS24.49-18-4), I wasn't sure if Lenovo would push another Security update for 6.0 (MM) or push 7.0 for the next update, and I didn't want to mess anything up..
I love this phone, and I'm not sure if and when I will upgrade, but I know it won't be MOTO/LENOVO anymore, unless they can unlock the bootloader for Pixel and gain root, I may lean that way...
NEVER, NEVER, Never will I go the way of the Apple, anything that comes from that place sucks, it's too restrictive..
DROID Forever !!!!!
Click to expand...
Click to collapse
Pixel bootloader is unlockable. Verizon Pixel has bootloader unlock tool from the Sunshine team free of charge. Also It is rootable via newest SuperSU beta I believe.
I have been unsuccessful at rooting stock nougat, it just gets stuck on the boot animation forever and the battery heats up.
So, has anyone rooted it on nougat 7.0 and how?
Every time I try it just gets stuck loading and since I can't logcat to it I have no idea where its failing, but fastboot flashing the system image and the boot image fixes it, but then I am stuck back at non-root.
I know there has to be a way as many others say they are rooted just fine so I must be missing something.
I have several apps that use root and do system tweaks that would be helpful, mostly battery saving, option enabling, etc... But I can't use any of them for now. I especially wanted to use the undervolt and system governers min max settings.
roadrun777 said:
I have been unsuccessful at rooting stock nougat, it just gets stuck on the boot animation forever and the battery heats up.
So, has anyone rooted it on nougat 7.0 and how?
Every time I try it just gets stuck loading and since I can't logcat to it I have no idea where its failing, but fastboot flashing the system image and the boot image fixes it, but then I am stuck back at non-root.
I know there has to be a way as many others say they are rooted just fine so I must be missing something.
I have several apps that use root and do system tweaks that would be helpful, mostly battery saving, option enabling, etc... But I can't use any of them for now. I especially wanted to use the undervolt and system governers min max settings.
Click to expand...
Click to collapse
Yes, lots of people have rooted it... latest TWRP and Magisk, nothing special to do at all... Flash or boot TWRP and flash Magisk zip file, reboot and go.
Unlocked bootloader must have.
1st method:
Boot twrp - fastboot boot twrp3x.img
Do full backup,
Restore boot only,
In twrp install magisk14.zip, optionally wipe cache+dalvik, reboot.
2nd method
...the same steps,
Twrp terminal - type + ok:
echo SYSTEMLESS=true>>/data/.supersu
Install SuperSu2.82.zip, opt.wipe..., reboot.
Both method works.
I finally find magisk and it worked first time for me.
I tried SuperSU about 10 times in a row, systemless false, systemless true, etc, without it, and it always ended the same way boot loops.
So I am not sure that SuperSu2.82.zip is currently compatible with nougat, or at least with nougat + xt1565 hardware.
roadrun777 said:
...
So I am not sure that SuperSu2.82.zip is currently compatible with nougat, or at least with nougat + xt1565 hardware.
Click to expand...
Click to collapse
I wrote here(#8):
1st December 2017, 02:11 PM,
Here:
https://forum.xda-developers.com/moto-x-style/general/stock-xt-1572-reteu-7-0-ddumped-files-t3712521
30. November, 2017...rooted 29.
SuSu 2.82 is compatible.
Magisk Framework comes with SuperUser built in.. so when you flash another superuser, you mixing Binaries and it doesn't know which one to use.
EDIT & TL;DR:
(i) Some people on this thread say they have "no problems with the upgrade", but many, many people do. To me that confirms the advice of this post: don't gamble, it's not worth it.
(ii) Also note that some people say that their battery life improved with Android 10… but then it turned out that on Pie, for some reason, they had a battery life of three hours, instead of the awesome times that the rest of us are getting. In short: if someone says that Android 10 is awesome, try to read between the lines.
Original Post:
Long story short.
Upgraded to Android 10.
"Search" stopped working within Settings
Battery life went from Awesome to Awful, Awful, Awful (known issue)
Fought the battery issue for two days (requested help with BBS dump)
Downgraded to Pie using TWRP backup (mistake)
This bricked the phone
Spent a whole day unbricking
Have my phone back but lost local files (photos, documents)
Android Pie ain't broke… Don't be like me, there's nothing to fix, the OP7 on latest Pie is awesome, it's all downhill from there.
Im on android 10 OOS10.0.1, rooted, magisked, viper installed, blu_spark-r57 installed. everything is perfect. search is also working.
but i fully clean flashed the entire android 10 firmware. maybe try that? i backed my stuff up on my PC prior to this.
who ah way said:
Long story short.
Upgraded to Android 10.
"Search" stopped working within Settings
Battery life went from Awesome to Awful, Awful, Awful (known issue)
Fought the battery issue for two days (requested help with BBS dump)
Downgraded to Pie using TWRP backup (mistake)
This bricked the phone
Spent a whole day unbricking
Have my phone back but lost local files (photos, documents)
Android Pie ain't broke… Don't be like me, there's nothing to fix, the OP7 on latest Pie is awesome, it's all downhill from there.
Click to expand...
Click to collapse
But that's not a general recommendation to not update to Android 10
strongst said:
But that's not a general recommendation to not update to Android 10
Click to expand...
Click to collapse
Sure, it's just one person's experience. It caused me a lot of grief, and I don't see the point of taking the risk. For the few days I was on 10 I didn't see any benefits, only drawbacks.
Pie to stable 10 then beta 4, is just keeps getting awesome. But hey maybe its just me. Factory reset and no apps restore
Didit_Anshari said:
just keeps getting awesome
Click to expand...
Click to collapse
What would be one or two specific improvements you've found from Pie to Q?
who ah way said:
What would be one or two specific improvements you've found from Pie to Q?
Click to expand...
Click to collapse
battery life, and animation
I can confirm. Even on a clean install battery backup is significantly less on Android 10. Last Pie update gave me like 10+ hours of SOT.
Saadkhalid786 said:
Im on android 10 OOS10.0.1, rooted, magisked, viper installed, blu_spark-r57 installed. everything is perfect. search is also working.
but i fully clean flashed the entire android 10 firmware. maybe try that? i backed my stuff up on my PC prior to this.
Click to expand...
Click to collapse
Apps to display in full screen not working in 10
Don't know what's the problem with the battery this screenshots from OpenBeta 4 and now i'm on OpenBeta 5 will see how's the battery there :good: for me on every OpenBeta no problem with the battery life :good:
Maybe the reason is that I always to a fresh start from the scratch with every OpenBeta :good:
Sent from my OnePlus7 using XDA Labs
In android 10, Having auto brightness issue getting too low in medium litt conditions...
SherryWadhwa said:
In android 10, Having auto brightness issue getting too low in medium litt conditions...
Click to expand...
Click to collapse
Is not a issues, it's settings to aggressive. For resetting the auto brightness go in settings and tap on the in the screenshots marked points.
That resets the auto brightness and takes some days to learn it new :good:
Sent from my OnePlus7 using XDA Labs
Thanks mate! Tried it but still having a little issue at some point.
anyone can use sip calls with the default phone app and loudspeaker?
GraveDigger176 said:
Don't know what's the problem (...)
Maybe the reason is that I always to a fresh start from the scratch with every OpenBeta :good:
Click to expand...
Click to collapse
That's right, if you're installing from scratch, that doesn't count as an upgrade… And this thread is about warning people about upgrading to Android 10.
Let's cut through the noise for a moment.
Is there ANYONE on this thread who has actually done an UPGRADE as suggested on the guide below, and who is NOT experiencing pain with Android 10?
The Guide (see the section called 2. UPDATE):
https://forum.xda-developers.com/oneplus-7/how-to/guide-unlock-bootloader-flash-twrp-root-t3954559
1. [OPTIONAL, but highly recommended]Backup everything in case of issues!
2. Download the full rom zip file and place it into the root folder of your storage(/storage/emulated/0)
3. Go to Magisk Manager App and uninstall all modules
4. Go to Android settings -> system -> system update and hit gear icon top right -> local upgrade, don't reboot yet!
5. Flash "TWRP ZIP" within Magisk Manager App like a Module: Magisk Manager App -> Menu -> Modules "+". This installs TWRP to both a/b partitions.
6. Install Magisk via Magisk Manager App again: Magisk Manager App -> hit install after your Magisk version -> hit again install -> hit "install to inactive slot"
7. Reboot your device
8. Reinstall your Magisk Modules
Your device is now updated via local upgrade and you keep TWRP and Root
Click to expand...
Click to collapse
who ah way said:
That's right, if you're installing from scratch, that doesn't count as an upgrade… And this thread is about warning people about upgrading to Android 10.
I did also the upgrade from P to Q as I was on stable OOS, but right after upgrade and boot I booted in the stock recovery and do factory reset and the wipe everything wipe and start from the scratch and I never had any mentioned issues. But anyway now i'm on Beta path :good:
Sent from my OnePlus7 using XDA Labs
Click to expand...
Click to collapse
who ah way said:
That's right, if you're installing from scratch, that doesn't count as an upgrade… And this thread is about warning people about upgrading to Android 10.
Let's cut through the noise for a moment.
Is there ANYONE on this thread who has actually done an UPGRADE as suggested on the guide below, and who is NOT experiencing pain with Android 10?
The Guide (see the section called 2. UPDATE):
https://forum.xda-developers.com/oneplus-7/how-to/guide-unlock-bootloader-flash-twrp-root-t3954559
Click to expand...
Click to collapse
Yes, me. I did not face any issues.
I did an upgrade from pie to Q with the same instruction.
3 issues I have.
Autobrightness
Wifi is sometimes disconnecting for a sec and connecting again
Gap below the keyboard
Personally don't have any issues whatsoever with Android 10 - Magisk, kernel, and all. Though its true that if you're on pie there's no point in upgrading. Only added feature that you might enjoy is ever so slightly more customization and android 10 navigation gestures, that's it.
I upgraded to A10 and latest Oxygen and everything is working fine for a month and more, haven't experienced any issues listed above.
I have a question. I want to root my phone (upgraded from oreo to pie, stock), but i'm not sure what should i do. Should i use oreo rooting instructions? I can't find any tutorial for rooting on pie. I don't want to change my rom, i just want to have a root and be able do use the magick and modules that's all. It would be nice to have step by step instruction.
I know i have to unlock my bootloader first at htcdev, then install twrp (not sure which twrp and if the installation is same as on oreo?)
In the past i rooted one phone but it was completely different and i almost bricked my device, because some idiot posted wrong link on the forum... There is so many versions of everything and i'm feeling lost in it.
I hope this helps, but Pie is still very new for the HTC U11. Some even are saying that clean flashes of the Pie RUU have flash, camera, and wifi issues. I am currently running the amazing RR-P rom (which is based on pie), but it runs on the latest Oreo RUU. I have no issues with the ROM and I get insane SoT even without battery savings. I am excited for the future of this phone, since I love the hardware navbar (never liked the on-screen one / though my HTC m8 is still a boss, and even the forums there have a very solid Lineage 17.0 (android 10) working on it).
https://dl.twrp.me/ocn/
Above is the official link to the US HTC u11 TWRP recoveries. I don't think (to be safer than sorry) these are 100% compatible over the PIE firmware though.
I checked HTCdev, and it doesn't seem to have any difference in the instructions in unlocking the bootloader. No mention of Nougat or Oreo, so I would assume there's no difference in doing the same with Pie.
I flashed my U11 after Pie update, working fine, no problems with flash, wifi or anything else (CID: HTC__034)
1. Unlock bootloader via htcdev
2. Flash latest TWRP from the official site. Instructions here for example: https://www.xda-developers.com/how-to-install-twrp/
3. Flash Magisk (also from official Magisk site)… that was a little trickier, since TWRP can't mount the encrypted partitions. The workaround is to copy the Magisk ZIP onto an SD Card and flash it from there while in TWRP.
4. Enjoy.
I decided to root this U11 for the first time, since I don't expect any futur software updates coming form HTC.
Thank you for all your help, i'll try this out today. :good:
So i did everything and it's working but i have one problem. After installing magisk i tried to install some modules, and one of them caused bootloop and i was unable to delete it, and also i was unable to install module uninstaller (fail). So i had to do factory reset - any solution to avoid this kind of problems in future?
Also i installed xposed successfully, but none of modules was working..
Togzyk said:
So i did everything and it's working but i have one problem. After installing magisk i tried to install some modules, and one of them caused bootloop and i was unable to delete it, and also i was unable to install module uninstaller (fail). So i had to do factory reset - any solution to avoid this kind of problems in future?
Also i installed xposed successfully, but none of modules was working..
Click to expand...
Click to collapse
I have no answers, but as u can see a rooted pie is problematic, hence the many people reverting back to oreo and or nougat, but some people somehow make it work. Not me I could not downgrade quick enough after rooting, unrooted pie worked great, but my many 'need for root apps' did not , so back to oreo for me . Just my 2 cents!! Good luck.
hammered58 said:
I have no answers, but as u can see a rooted pie is problematic, hence the many people reverting back to oreo and or nougat, but some people somehow make it work. Not me I could not downgrade quick enough after rooting, unrooted pie worked great, but my many 'need for root apps' did not , so back to oreo for me . Just my 2 cents!! Good luck.
Click to expand...
Click to collapse
I found many working apps. The biggest problem is "substratum", especially when it comes to changing navbar buttons. But gravitybox is working, and I'm happy with it. Thanks for your help
My rooted Pie works fine, but I didn't install Substratum or Xposed.
I downloaded it. Went to local upgrade, installed it.
Went to Magisk and did install to inactive slot like normal. And it reboots. Then a small bootloop for a second. Then goes straight back to normal. Like I never installed anything.
Any thoughts?
I tried to root by patching new boot.img but get bootloop which not fixed except after msmdownload tool
All data wiped
Root OnePlus 9, 9 Pro, 9R Android 12 ColorOS 12 via Magisk
Thi guide will show you how to root the OnePlus 9, OnePlus 9 Pro, and OnePlus 9R running ColorOS 12 Android 12 via Magisk Patched Boot.img
www.droidwin.com
The temporary root method at the end of this page worked for me on A12 stable
illusiveairforce said:
I downloaded it. Went to local upgrade, installed it.
Went to Magisk and did install to inactive slot like normal. And it reboots. Then a small bootloop for a second. Then goes straight back to normal. Like I never installed anything.
Any thoughts?
Click to expand...
Click to collapse
Same here. If you dont install magisk to the inactive slot it will go through and you will be in oos12. Problem with mine, it wont read my flaking sim card. Tried it 5x all same problem. Also, every reboot, your dpi goes back to 360 lmao.
I patched boot.img by canary magisk and it is working good, but no option for safetynet passing
sbute said:
Root OnePlus 9, 9 Pro, 9R Android 12 ColorOS 12 via Magisk
Thi guide will show you how to root the OnePlus 9, OnePlus 9 Pro, and OnePlus 9R running ColorOS 12 Android 12 via Magisk Patched Boot.img
www.droidwin.com
The temporary root method at the end of this page worked for me on A12 stable
Click to expand...
Click to collapse
I used this guide but patched with magisk 23.0. still have all my modules and passing safety net. Using latest stable magisk 23.0 righteous. Thank you for this. I tried for 3 days killing my device flashing boot img. At least I know my downloaded msm tool works. On latest A12 build out for the global op9
I wouldnt recommend it tbh if its your only phone. Its buggy AH.
mattie_49 said:
I used this guide but patched with magisk 23.0. still have all my modules and passing safety net. Using latest stable magisk 23.0 righteous. Thank you for this. I tried for 3 days killing my device flashing boot img. At least I know my downloaded msm tool works. On latest A12 build out for the global op9
Click to expand...
Click to collapse
Would you or anyone else mind sharing the boot img for the OnePlus 9: OOS/Android 12 ?
I have the Global / NA version.
It would be greatly appreciated!
Zethiel said:
Would you or anyone else mind sharing the boot img for the OnePlus 9: OOS/Android 12 ?
I have the Global / NA version.
It would be greatly appreciated!
Click to expand...
Click to collapse
I have on my PC I will upload soon. Away from it currently. You really need 3 partitions to make work. Boot,vendor_boot,vbmeta
Geesh the battery is so much better on A12 after debloating how I see fit. Passing safety net, all banking apps working and still using old modules !! Score
mattie_49 said:
I have on my PC I will upload soon. Away from it currently. You really need 3 partitions to make work. Boot,vendor_boot,vbmeta
Click to expand...
Click to collapse
That would be greatly appreciated Sir!
0p9 partitions..A 12 - Google Drive
drive.google.com
All three are in here. Make sure to use magisk 23.0 to patch boot and vendor boot so you don't loose modules and magisk hide. Then you disable verity before boot with vb_meta img. You have to do from sdk platform tools folder though. Will not work just putting in a folder on desktop and pulling cmd window from there. Enjoy , follow the above guide to a T
Zethiel said:
That would be greatly appreciated Sir
Click to expand...
Click to collapse
infamousvincci said:
I wouldnt recommend it tbh if its your only phone. Its buggy AH.
Click to expand...
Click to collapse
Only issue I have is no advanced reboot menu what-so-ever. Battery is much better,stable af,modem is better as well. I would recommend .
File above edited. Correct images
mattie_49 said:
File above edited. Correct images
Click to expand...
Click to collapse
Thanks a lot for the files Mattie.
My experience with OOS 12 so far has been a nightmare, and I'm not even rooted.
For the record:
I was coming from OOS 11 not the latest version previous to OOS 12, rooted, pretty much stable but I felt the phone pretty slow in comparison to other (Long story short, I got a brand new OnePlus 8 I bought almost a year ago but couldn't get my hands on it, so after getting tired of waiting for it, bought the OP9).
My OP8 is not rooted, doesn't have the bootloader unlocked, and it's miles faster than my OP9 with about the same apps installed with the exception of the apps that require root.
So, since my OP9 was feeling slow in comparison, I decided to go at OOS 12 to see how it went. First experience was bad, the phone kept hanging, didn't read the SIM correctly at first, so I read someone that was suggesting to do a factory reset to fix some issues.
I did a factory reset, deleted everything on the phone to start OOS 12 from zero, and the phone keeps hanging, specially when I get phone calls via Whatsapp or other apps, and less but still some problems with "answering incoming phone calls".
At this point I rather try to downgrade to OOS 11 and sit this one out for a long while.
I thought about rooting OOS 12, but being honest, having root is not going to make the phone more stable or anything. I guess I'll do give it a try at OOS 12 in 3-6months after a couple of updates, maybe other versions are better.
Zethiel said:
Thanks a lot for the files Mattie.
My experience with OOS 12 so far has been a nightmare, and I'm not even rooted.
For the record:
I was coming from OOS 11 not the latest version previous to OOS 12, rooted, pretty much stable but I felt the phone pretty slow in comparison to other (Long story short, I got a brand new OnePlus 8 I bought almost a year ago but couldn't get my hands on it, so after getting tired of waiting for it, bought the OP9).
My OP8 is not rooted, doesn't have the bootloader unlocked, and it's miles faster than my OP9 with about the same apps installed with the exception of the apps that require root.
So, since my OP9 was feeling slow in comparison, I decided to go at OOS 12 to see how it went. First experience was bad, the phone kept hanging, didn't read the SIM correctly at first, so I read someone that was suggesting to do a factory reset to fix some issues.
I did a factory reset, deleted everything on the phone to start OOS 12 from zero, and the phone keeps hanging, specially when I get phone calls via Whatsapp or other apps, and less but still some problems with "answering incoming phone calls".
At this point I rather try to downgrade to OOS 11 and sit this one out for a long while.
I thought about rooting OOS 12, but being honest, having root is not going to make the phone more stable or anything. I guess I'll do give it a try at OOS 12 in 3-6months after a couple of updates, maybe other versions are better.
Click to expand...
Click to collapse
I have the correct msm tool for device. This is the forward route for you. Takes you to 11.4. Stock A11
Does anyone else have the issue of their touchscreen not functioning when they install the A12 update? Ive tried installing twice and both times my screen would not register any touches only the volume and power buttons functioned?
EDIT: NVM I MSM'd back to stock and upgraded to OOS 12 before unlocking the bootloader.
Zethiel said:
Thanks a lot for the files Mattie.
My experience with OOS 12 so far has been a nightmare, and I'm not even rooted.
For the record:
I was coming from OOS 11 not the latest version previous to OOS 12, rooted, pretty much stable but I felt the phone pretty slow in comparison to other (Long story short, I got a brand new OnePlus 8 I bought almost a year ago but couldn't get my hands on it, so after getting tired of waiting for it, bought the OP9).
My OP8 is not rooted, doesn't have the bootloader unlocked, and it's miles faster than my OP9 with about the same apps installed with the exception of the apps that require root.
So, since my OP9 was feeling slow in comparison, I decided to go at OOS 12 to see how it went. First experience was bad, the phone kept hanging, didn't read the SIM correctly at first, so I read someone that was suggesting to do a factory reset to fix some issues.
I did a factory reset, deleted everything on the phone to start OOS 12 from zero, and the phone keeps hanging, specially when I get phone calls via Whatsapp or other apps, and less but still some problems with "answering incoming phone calls".
At this point I rather try to downgrade to OOS 11 and sit this one out for a long while.
I thought about rooting OOS 12, but being honest, having root is not going to make the phone more stable or anything. I guess I'll do give it a try at OOS 12 in 3-6months after a couple of updates, maybe other versions are better.
Click to expand...
Click to collapse
if you are looking for performance, look into kernels and/or just use a kernel manager.
out of all the Roms I've tried (all but the latest havok release) crDroid is the best performance option I get from a ROM on O09. that piared with optional GApps and frequent OTA updates, its the best thing out so far. the OTA even works perfectly at retaining root without any user input. (but do a backup before reboot, its still technically a dirty flash so play safe)
sbute said:
Root OnePlus 9, 9 Pro, 9R Android 12 ColorOS 12 via Magisk
Thi guide will show you how to root the OnePlus 9, OnePlus 9 Pro, and OnePlus 9R running ColorOS 12 Android 12 via Magisk Patched Boot.img
www.droidwin.com
The temporary root method at the end of this page worked for me on A12 stable
Click to expand...
Click to collapse
I don't want to get too off-topic, but figured I'd save a MSM wipe to some people, I can confirm this works, but only using the latest version of Magisk (v24), temporary boot will not work with v23 (the last one with MagiskHide), it caused Qualcomm crashdump and no recovery or fastbootd.
If anyone looks into other root spoofing solutions with the newer version v24, from Magisk settings use Zygisk, select apps using Enforced Denylist, and Universal SafetyNet Fix, there is also Shamiko, which I haven't tested personally.
From my own experience, DenyList+Universal SafetyNet fix+Selinux Switch if you need to switch between permissive and enforced Selinux are enough. Apps won't get to know there is root, safetynet is passed, and selinux checks are passed (that one took me a long while to figure out)