Related
Hi.
This is my first post, I hope i'm in the correct forum.
I have a friend whom I requested to Root, Flash TWRP and Install LineagOS and GAAP on my OnePlus One phone.
He successfully flashed TWRP and installed LineagOS & GAAP but could not root my OnePlus One using SuperSu. He mentioned permission issue trying to root.
He went back to his country, so I am stuck trying to root my phone.
I would like to root my LineagOS (formally OnePlus One) using SuperSU.
I have downloaded/copied the latest SuperSu zip file into the Phone Sd/Download folder.
I went into custom recovery (TWRP).
Click on the Install button and verified I can see my SuperSu zip file.
Since this is my first time performing a phone root, I did not click SuperSu zip to install, until some experts can assist. me.
Just a few (Q's).
Questions:
a) Should I run any preliminary steps prior to clicking install SuperSu.zip?
b) Since I have LineagOS, GAAP apps already installed, will they be wiped after rooting SuperSu. If (Yes), any software available to backup/restore LineagOS & GAAP prior to the root process?
c) My friend mention “Permission problems with OPO”. Are there some options to open OPO and allow rooting SuperSu?
BTW: I do have the adb & fastboot installed if I need to enter some commands to get this done.
Thanks.
Tom.
a) No.
Download flashable supersu zip and flash it from here and flash it via TWRP https://forum.xda-developers.com/apps/supersu/stable-2016-09-01supersu-v2-78-release-t3452703
b) No.
But you can take nandroid backup through twrp in case something goes wrong.
c) As far as I know there is no problem with "permission" for rooting.
Happy flashing
Hi psxda97.
I did your requested instructions, but still not Rooted.
Here are the steps I did:
1) Downloaded the latest SuperSu zip from XDA and copied to Sd/Download folder on my phone.
2) Went into Custom Recovery TWRP) on my phone.
3) Click Install, selected SuperSu.zip Swipe bar to continue.
Completed 181 seconds did not see errors.
4) Wiped Dalvic & Cache. Reboot the Phone.
When phone restarted I went into Titanium backup apps to test if Root was successful. Received error msg from Titanium "Could not acquire root privileges. This app will not work Verify your Rom is rooted and try again"
Not sure if this makes a difference: in Developers Option I had root access ADP Only enabled & allow Unknown Sources set off.
Since this is the second time running SuperSu should I needed to wipe any files before rooting?
I'll await you reply.
Thanks.
Tom.
tomx2x said:
Hi psxda97.
I did your requested instructions, but still not Rooted.
Here are the steps I did:
1) Downloaded the latest SuperSu zip from XDA and copied to Sd/Download folder on my phone.
2) Went into Custom Recovery TWRP) on my phone.
3) Click Install, selected SuperSu.zip Swipe bar to continue.
Completed 181 seconds did not see errors.
4) Wiped Dalvic & Cache. Reboot the Phone.
When phone restarted I went into Titanium backup apps to test if Root was successful. Received error msg from Titanium "Could not acquire root privileges. This app will not work Verify your Rom is rooted and try again"
Not sure if this makes a difference: in Developers Option I had root access ADP Only enabled & allow Unknown Sources set off.
Since this is the second time running SuperSu should I needed to wipe any files before rooting?
I'll await you reply.
Thanks.
Tom.
Click to expand...
Click to collapse
I think I'm missing something. Did you tried any other method to root? I recommend a clean flash.
1. Download Sultanxda's unofficial lineageOS from here
2. Download Gapps from here. ( ARM-7.1-nano)
3.Download SuperSU from here
4. [Optional] take back up of your apps (No need to back up medias like photo,video,etc)
5.Got Recovery>wipe>advanced wipe
select system,data,cache and dalvik cache (DO NOT SELECT INTERNAL)
6.flash the zips you already downloaded in this order - ROM- Gapps - SuperSU
do not wipe anything after this step
7.Reboot
1st reboot will take some time (10-20 min ). Do not interrupt this process.
PS: I totally recommend Sultan's LineageOS over official LOS. You can actually feel the difference in smoothness and performance. Especially the Camera.
Feel free to check device specific forum for OnePlus One
Happy flashing!
@psxda97.
Thanks for the quick reply.
OK, I'm going to start from scratch as you requested.
When I try to download SuperSu (from your link above) located in Google Play, I get “supersu already installed for your device”.
Did not find SuperSu in Phone Apps settings.
Went into TWRP File Manager \ supersu folder. Deleted all (4) entries.
Rebooted.
Went back into TWRP. The 4 entries reappear.
Google Play continues to gray out my device name. SuperSu is already installed.
I do have a SuperSu zip file on my PC. I installed this on my last attempt. It appears to be the same as Google Play.
Here is the name:
“C:\Users\Tomx\Downloads\SR1-SuperSU-v2.82-SR1-20170608224931.zip\”
Should I go with this?
Tom.
tomx2x said:
@psxda97.
Thanks for the quick reply.
OK, I'm going to start from scratch as you requested.
When I try to download SuperSu (from your link above) located in Google Play, I get “supersu already installed for your device”.
Did not find SuperSu in Phone Apps settings.
Went into TWRP File Manager \ supersu folder. Deleted all (4) entries.
Rebooted.
Went back into TWRP. The 4 entries reappear.
Google Play continues to gray out my device name. SuperSu is already installed.
I do have a SuperSu zip file on my PC. I installed this on my last attempt. It appears to be the same as Google Play.
Here is the name:
“C:\Users\Tomx\Downloads\SR1-SuperSU-v2.82-SR1-20170608224931.zip\”
Should I go with this?
Tom.
Click to expand...
Click to collapse
Yes. Copy all 3 zip (rom,gapps,supersu) to you phone.
Let me know how it goes..
@psxda97
Ok, I followed your steps 1-7.
Instructions completed successfully.
After setting up LineageOS and my Google acct I downloaded Titanium Backup.
Clicked on the app and received same error message stated in my previous post.
Is there another option/app to check if my phone is rooted?
I notice when I logoff from TWRP, I get this message displayed “Your device does not appear to be rooted Install SuperSU now This will root your device?“ There is a button to Install.
XDA put out a notice this is a bogus message and do not install.
“Sometimes, TWRP can’t detect that you already have SuperSU, so it’ll ask to flash its built-in version. But it’s almost always best to flash the latest version of SuperSU yourself “
In TWRP file manager\supersu folder contains 4 files.
99SuperSuDaemon, install-recovery.sh, su, Superuser.apk.
Are these the Built in version of supersu?
If you have other suggestions, let me know – Thanks for your help.
Tom.
tomx2x said:
@psxda97
Ok, I followed your steps 1-7.
Instructions completed successfully.
After setting up LineageOS and my Google acct I downloaded Titanium Backup.
Clicked on the app and received same error message stated in my previous post.
Is there another option/app to check if my phone is rooted?
I notice when I logoff from TWRP, I get this message displayed “Your device does not appear to be rooted Install SuperSU now This will root your device?“ There is a button to Install.
XDA put out a notice this is a bogus message and do not install.
“Sometimes, TWRP can’t detect that you already have SuperSU, so it’ll ask to flash its built-in version. But it’s almost always best to flash the latest version of SuperSU yourself “
In TWRP file manager\supersu folder contains 4 files.
99SuperSuDaemon, install-recovery.sh, su, Superuser.apk.
Are these the Built in version of supersu?
If you have other suggestions, let me know – Thanks for your help.
Tom.
Click to expand...
Click to collapse
Can you send me a screenshot of supersu app?
I'm using the exact settings and I don't have any problem at all.
Do not let TWRP install supersu.
@psxda97
As you know the Supersu is a zip file. When I open/ then extract, the display will show folders & their contents.
I have attached all the folders & contents from supersu extract for your review.
To get a screenshot maybe you can walk me through this step.
The only way I can think of is to find & download the SuperSu apk file (for this version) onto my phone and open it to get a visual screenshot of the app.
Here is the website link where I downloaded SuperSu 2 days ago.
" https://download.chainfire.eu/1114/...r&utm_medium=referral&utm_source=DonanimHaber “
tomx2x said:
To get a screenshot maybe you can walk me through this step.
The only way I can think of is to find & download the SuperSu apk file (for this version) onto my phone and open it to get a visual screenshot of the app.
Click to expand...
Click to collapse
I meant this
Edit : So you've no supersu app on you phone?
@psxda97
Maybe that's my problem. I do not have supersu on my phone application. (see my attached).
Here' what I do.
1. Download supersu zip file from website to my PC.
2. Connect PC to phone.
3. I do not extract the supersu.zip on my PC, I just manually copy the supersu.zip (as is) to Download folder (A0001) of my Phone.
4. Logoff off phone.
5. Get into TWRP. Click Install. Click supersu zip.
6. Reboot, when finish, run Titanium Backup on phone to check for root.
Should supersu app be on my phone after installation/rebooting?
Somehow it's not doing the root, even though it completes successfully in TWRP. Strange.
Tom.
tomx2x said:
[MENTION=7046372]
Should supersu app be on my phone after installation/rebooting?
Tom.
Click to expand...
Click to collapse
Yes.
Go to recover and flash it one more time
Then go to Advanced on twrp and select copy log (without kernel log).
Log will be on root folder of internal. attach the log in your next post
Also send me the screenshot of your about phone settings.
You're still missing something.
tomx2x said:
@psxda97
Maybe that's my problem. I do not have supersu on my phone application. (see my attached).
Here' what I do.
1. Download supersu zip file from website to my PC.
2. Connect PC to phone.
3. I do not extract the supersu.zip on my PC, I just manually copy the supersu.zip (as is) to Download folder (A0001) of my Phone.
4. Logoff off phone.
5. Get into TWRP. Click Install. Click supersu zip.
6. Reboot, when finish, run Titanium Backup on phone to check for root.
Should supersu app be on my phone after installation/rebooting?
Somehow it's not doing the root, even though it completes successfully in TWRP. Strange.
Tom.
Click to expand...
Click to collapse
Go to system settings>developer options>root access and set it to "apps and adb"
If you flash the SuperSU.zip in TWRP on your device then you should have root.
I think you misunderstood from the beginning, did you download the SuperSU.zip and then extract it on PC and then try to install it? If so, that was completely the wrong thing to do. You might have to remove what you've done so far and then try again from a clean start, you might gave to flash your stock firmware to get a clean start.
Have you looked into whether you need normal SuperSU or whether you need systemless SuperSU?
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Additional info provided - Anyone with advice.
@psxda97 - No problem about your availability time will put my post in advance reply for others to share their advice. I'm currently in Thailand for awhile, so your PM time is my AM.
@Droidriven.
No I never did an extract of the Supersu zip file. I just raised that as a "Should I".
I have attached screenshots of my About Phone & Developer Options for review.
I found only 1 Recovery log file at the Root. This has been attached.
Normal Supersu or Seamless. Not an expert on this, but the article (see below), implies if you flash supersu it will decide what method to use. I'd prefer seamless if this help. "https://www.howtogeek.com/249162/what-is-systemless-root-on-android-and-why-is-it-better/"
Just curious. What if I ran in this order Supersu, ROM, GAAP.
Would that make any difference?
Tom.
tomx2x said:
@psxda97 - No problem about your availability time will put my post in advance reply for others to share their advice. I'm currently in Thailand for awhile, so your PM time is my AM.
@Droidriven.
No I never did an extract of the Supersu zip file. I just raised that as a "Should I".
I have attached screenshots of my About Phone & Developer Options for review.
I found only 1 Recovery log file at the Root. This has been attached.
Normal Supersu or Seamless. Not an expert on this, but the article (see below), implies if you flash supersu it will decide what method to use. I'd prefer seamless if this help. "https://www.howtogeek.com/249162/what-is-systemless-root-on-android-and-why-is-it-better/"
Just curious. What if I ran in this order Supersu, ROM, GAAP.
Would that make any difference?
Tom.
Click to expand...
Click to collapse
The problem might be in the LineageOS ROM that you're using, I've seen others have this issue on other devices using LineageOS.
I don't recall what some of the solutions were.
@Sam Nakamura is pretty knowledgeable about the OnePlus devices, maybe he has some useful input.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
tomx2x said:
@psxda97 - No problem about your availability time will put my post in advance reply for others to share their advice. I'm currently in Thailand for awhile, so your PM time is my AM.
@Droidriven.
No I never did an extract of the Supersu zip file. I just raised that as a "Should I".
I have attached screenshots of my About Phone & Developer Options for review.
I found only 1 Recovery log file at the Root. This has been attached.
Normal Supersu or Seamless. Not an expert on this, but the article (see below), implies if you flash supersu it will decide what method to use. I'd prefer seamless if this help. "https://www.howtogeek.com/249162/what-is-systemless-root-on-android-and-why-is-it-better/"
Just curious. What if I ran in this order Supersu, ROM, GAAP.
Would that make any difference?
Tom.
Click to expand...
Click to collapse
Sorry, it's early in the morning here and I think I haven't been able to get the question yet...
First of all, lineageOS provides a own method of root, found here:
https://download.lineageos.org/extras
If you instead choose to use supersu the order must be -> rom, (custom kernel), supersu, (or rom, custom kernel, gapps, supersu but for gapps it doesn't matter when to flash them as long as it is in the same session and after the rom, supersu intendes to either patch the kernel (hence systemless) or to write in system (partition of the rom), that's why rom and custom kernel (if you choose to use a custom kernel) needs to be flashed before supersu...
The supersu systemless / system detection does not always work properly, in that case you can force supersu systemlessly by going to the terminal option in twrp before flashing supersu and type this:
"echo SYSTEMLESS=true>>/data/.supersu" no quotes, type "false" instead of "true" in this line to force system mode...
If that doesn't solve your problems please elaborate on this again..
Sent from my OnePlus 2 using XDA Labs
Sam Nakamura said:
Sorry, it's early in the morning here and I think I haven't been able to get the question yet...
First of all, lineageOS provides a own method of root, found here:
https://download.lineageos.org/extras
If you instead choose to use supersu the order must be -> rom, (custom kernel), supersu, (or rom, custom kernel, gapps, supersu but for gapps it doesn't matter when to flash them as long as it is in the same session and after the rom, supersu intendes to either patch the kernel (hence systemless) or to write in system (partition of the rom), that's why rom and custom kernel (if you choose to use a custom kernel) needs to be flashed before supersu...
The supersu systemless / system detection does not always work properly, in that case you can force supersu systemlessly by going to the terminal option in twrp before flashing supersu and type this:
"echo SYSTEMLESS=true>>/data/.supersu" no quotes, type "false" instead of "true" in this line to force system mode...
If that doesn't solve your problems please elaborate on this again..
Sent from my OnePlus 2 using XDA Labs
Click to expand...
Click to collapse
I haven't used LineageOS yet so I'm not familiar with its details, I was pretty sure you'd know though. [emoji106]
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
@Sam Nakamura.
Thanks for the info.
I have previously executed the steps in the order you posted. I was just asking if other sequences to flash these apps were plausible.
With the help of member psxda97, he documented similar steps 1-7 for me. (Please read Post #4 on this thread and my results in Post #7). It's basically a snapshot of what you posted regarding the order seq.
Unfortunately, my phone still did not root after applying the ROM, GAAP & Supersu in this order. I'm not sure why the root is declared successful in TWRP, and the phone remain un-rooted.
Do you suggest I rerun steps1-7 from Post#4 and include your echo statement before installing supersu?
The LineageOS extras, (you mentioned) has a built-in root.
I now have LineagOS from Sultanxda's installed on my phone. It is highly recommended by XDA members over the official LOS, for it's smoothness and camera enhancements. Sultanxda' release is 06/25/2017.
LOS extras has a release date of 06/21/2017. My only issues, whether to choose LOS extras. I will subsequently get the next “Official” LOS release for 6/25 and loose LOS Sultanxda installation.
Tom.
Tried Installing LOS extras 14.1
@Sam Nakamura
I downloaded LOS extras from the link you provided.
Went into TWRP
Did the Install
Then rebooted.
Went back to phone\Developers Option
Root Access is still grayed out.
See screenshot attached.
Any suggestions?
Should I just do a TWRP factory reset and start over?
Tom.
tomx2x said:
@Sam Nakamura
I downloaded LOS extras from the link you provided.
Went into TWRP
Did the Install
Then rebooted.
Went back to phone\Developers Option
Root Access is still grayed out.
See screenshot attached.
Any suggestions?
Should I just do a TWRP factory reset and start over?
Tom.
Click to expand...
Click to collapse
Did you choose the correct arm(32) version of lineageOS su? I'd try the following:
Backup all partitions with twrp so you can return to your set-up later on..
Wipe everything except internal storage
Flash rom, (custom kernel), gapps and su
Boot up and check if it's working now
If not restore your backup and check next point
Alternatively:
Have you tried superSU with forced systemless via twrp terminal (by the way, if done correctly there shouldn't fallow a output with this command line..)
Flash supersu from here:
https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
I never had issues with the beta but you can also use the stable version, downloads on post 1
Using Magisk as root and root management tool
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Flashable zip via twrp, if successful go to magisk settings, and check superuser and read the rest of Magisk's potential on the linked thread, my preferred method as it allows you to hide root from certain apps which deny service to rooted devices..
Important, it's not a good idea to flash lineageOS su, then supersu, then magisk after each fails, at least restore your clean boot partition from twrp or flash the boot.img from within your rom zip... Best would be clean of course - but as you have a backup of your previous system you can play around and make errors...
Sent from my OnePlus 2 using XDA Labs
Hello guys, I seriously need help please.
I decrypted my data. Everything is working perfectly with the exception of the Huawei camera.
1.The icon has change to android green icon
2.It flashes when u open
3 . 3rd party camera app like camera 360 which I just Install from playstore also not working, only showing me black screen.
Will be glad if someone can restore my camera back:crying:.
Am on firmware L29C185B181 please.
golastic said:
Hello guys, I seriously need help please.
I decrypted my data. Everything is working perfectly with the exception of the Huawei camera.
1.The icon has change to android green icon
2.It flashes when u open
3 . 3rd party camera app like camera 360 which I just Install from playstore also not working, only showing me black screen.
Will be glad if someone can restore my camera back:crying:.
Am on firmware L29C185B181 please.
Click to expand...
Click to collapse
Did you flash some other models boot image?
ante0 said:
Did you flash some other models boot image?
Click to expand...
Click to collapse
Everything I flashed was extracted from my firmware version... update_data_full_public.zip and update_full_hw_meafnaf.zip.
golastic said:
Everything I flashed was extracted from my firmware version... update_data_full_public.zip and update_full_hw_meafnaf.zip.
Click to expand...
Click to collapse
Camera is not part of those zips so that can't be it. Could you backup your current boot image in twrp and send to me?
Maybe Flash public and hw in twrp to fix the camera?
ante0 said:
Camera is not part of those zips so that can't be it. Could you backup your current boot image in twrp and send to me?
Click to expand...
Click to collapse
Sure Sir.....
https://mega.nz/#!8JNX3CwZ!PjSDO9c4mNWh5_ddKANmLNqLPRo7hyk_of5lAZThPUU (from partitions backup apk)
https://mega.nz/#F!BZ0XRb6Z!Y8QkOaw6K8dtuzuysgImNA (from twrp)
You can revert to stock anytime using this tool https://forum.xda-developers.com/mate-9/how-to/guide-mate-9-flash-update-package-t3593108/page74
golastic said:
Sure Sir.....
https://mega.nz/#!8JNX3CwZ!PjSDO9c4mNWh5_ddKANmLNqLPRo7hyk_of5lAZThPUU
Click to expand...
Click to collapse
Something is up with your boot images, none can be unpacked.
Try flashing https://mega.nz/#!lhVTmbqQ!gIf4Tu4JC3pdzz-T7OAxi4wr3PQySkqdTgclkOkEU2E
Then re-root without rebooting.
Which root are you using by the way?
ante0 said:
Something is up with your boot images, none can be unpacked.
Try flashing https://mega.nz/#!lhVTmbqQ!gIf4Tu4JC3pdzz-T7OAxi4wr3PQySkqdTgclkOkEU2E
Then re-root without rebooting.
Which root are you using by the way?
Click to expand...
Click to collapse
Magisk 13.3 alongside superuser-r310-beta.zip
golastic said:
Magisk 13.3 alongside superuser-r310-beta.zip
Click to expand...
Click to collapse
Ah. Phh is probably why it won't unpack then.
I'm not sure then. If re-flashing B181 hw and public doesn't fix it, it's probably the boot image (seeing as regular camera apps don't work either something is up with the drivers).
I'd try with SuperSU/phh too or update to b182+ if possible and flash regular magisk 13.3, without phh.
ante0 said:
Ah. Phh is probably why it won't unpack then.
I'm not sure then. If re-flashing B181 hw and public doesn't fix it, it's probably the boot image (seeing as regular camera apps don't work either something is up with the drivers).
I'd try with SuperSU/phh too or update to b182+ if possible and flash regular magisk 13.3, without phh.
Click to expand...
Click to collapse
Thx sir but huawei firmware finder is only tell me current firmware to be C185B181.
Will be glad to link me to me 182 .
Thx
golastic said:
Thx sir but huawei firmware finder is only tell me current firmware to be C185B181.
Will be glad to link me to me 182 .
Thx
Click to expand...
Click to collapse
Correct. Latest is 181. I guess you could try installing Magisk, it will reboot instantly in twrp if it can't mount image as loop. 182+ is only because most firmware got loop support in 182. (First) B182 for C432 was released 12th of April and yours was released 24th of April, so it might work.
Or rebrand to C636.
golastic said:
Thx sir but huawei firmware finder is only tell me current firmware to be C185B181.
Will be glad to link me to me 182 .
Thx
Click to expand...
Click to collapse
New build for C185: B184.
It says BC185, but checking VERSION.mbn in update.zip confirms it's for C185:
MHA-L29C185B184
There was actually a B182 too for C185, released as BC185 too.
http://hwmt.ru/hwmtsite/firmware-database/?firmware_model=MHA-L29BC185&firmware_page=0
ante0 said:
New build for C185: B184.
It says BC185, but checking VERSION.mbn in update.zip confirms it's for C185:
MHA-L29C185B184
There was actually a B182 too for C185, released as BC185 too.
http://hwmt.ru/hwmtsite/firmware-database/?firmware_model=MHA-L29BC185&firmware_page=0
Click to expand...
Click to collapse
Can Install the firmware through Huawei finder apk and will it restore my camera please. I love my phone but without the camera working is makes my headache.
Have tried all u ask me by restoring stock boot loader and flashing superSu but the camera is still not working. It flashing :crying::crying::crying::crying:
golastic said:
Can Install the firmware through Huawei finder apk and will it restore my camera please. I love my phone but without the camera working is makes my headache.
Have tried all u ask me by restoring stock boot loader and flashing superSu but the camera is still not working. It flashing :crying::crying::crying::crying:
Click to expand...
Click to collapse
Before updating, have you tried restoring boot without rooting and see if that fixes camera?
Try this one, I removed verity and replaced fileencryption with encryptable so it doesn't encrypt your /data again.
https://mega.nz/#!lhE2zLSR!ngNY3bXKMS_eKizjmfnKHbFgVSVnp94dgCXnxuL_G_0
If it doesn't do anything, continue below.
Currently, https://forum.xda-developers.com/mate-9/how-to/guide-mate-9-flash-update-package-t3593108
Other ways are Firmware Finder or OTA, but both those require your IMEI to be approved for the update.
And Funky Huawei, which you need to pay for.
It will wipe /data when/if you decrypt again so make sure to make a backup of /data first, or backup apps with Titanium Backup or which backup app you use.
Basically download the Base zip, MHA zip and Windows or linux zip from https://forum.xda-developers.com/mate-9/how-to/guide-mate-9-flash-update-package-t3593108
Extract all to the same folder (hwota) and merge if it asks.
Then download:
http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1366/g104/v91627/f1/full/update.zip
http://update.hicloud.com:8180/TDS/...hw_meafnaf/update_full_MHA-L29_hw_meafnaf.zip
http://update.hicloud.com:8180/TDS/...27/f1/full/public/update_data_full_public.zip
Put all in the "update" folder in the hwota folder you extracted before.
Rename update_full_MHA-L29_hw_meafnaf.zip to update_all_hw.zip
Rename update_data_full_public.zip to update_data_public.zip
Put phone in fastboot mode (download mode) and run update.bat (windows) or update.sh (linux)
Pick "Same brand update" when it asks, and "Script update directory".
When it's done your bootloader will be locked again so you need to unlock it if you want to root again.
You will be able to install regular Magisk 13.3 now without superuser (phh)
ante0 said:
Before updating, have you tried restoring boot without rooting and see if that fixes camera?
Try this one, I removed verity and replaced fileencryption with encryptable so it doesn't encrypt your /data again.
https://mega.nz/#!lhE2zLSR!ngNY3bXKMS_eKizjmfnKHbFgVSVnp94dgCXnxuL_G_0
If it doesn't do anything, continue below.
Currently, https://forum.xda-developers.com/mate-9/how-to/guide-mate-9-flash-update-package-t3593108
Other ways are Firmware Finder or OTA, but both those require your IMEI to be approved for the update.
And Funky Huawei, which you need to pay for.
It will wipe /data when/if you decrypt again so make sure to make a backup of /data first, or backup apps with Titanium Backup or which backup app you use.
Basically download the Base zip, MHA zip and Windows or linux zip from https://forum.xda-developers.com/mate-9/how-to/guide-mate-9-flash-update-package-t3593108
Extract all to the same folder (hwota) and merge if it asks.
Then download:
http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1366/g104/v91627/f1/full/update.zip
http://update.hicloud.com:8180/TDS/...hw_meafnaf/update_full_MHA-L29_hw_meafnaf.zip
http://update.hicloud.com:8180/TDS/...27/f1/full/public/update_data_full_public.zip
Put all in the "update" folder in the hwota folder you extracted before.
Rename update_full_MHA-L29_hw_meafnaf.zip to update_all_hw.zip
Rename update_data_full_public.zip to update_data_public.zip
Put phone in fastboot mode (download mode) and run update.bat (windows) or update.sh (linux)
Pick "Same brand update" when it asks, and "Script update directory".
When it's done your bootloader will be locked again so you need to unlock it if you want to root again.
You will be able to install regular Magisk 13.3 now without superuser (phh)
Click to expand...
Click to collapse
Resolved the camera issue by following the last steps by flashing the 3 zip files......have unlocked bootloader and installed twrp 3.1.0.1 and trying to install magisk 13.3 but it always stuck at huawei logo.
Have also tried rooting but it seems only SuperSU2.82EMUI5noverityEnforcing works and do i need to follow the steps of formatting data to get it decyrpted?
Currently on MHA-L29C185B182 at the moment.
Thx @ante0 for your kind gesture.Appreciated
golastic said:
Resolved the camera issue by following the last steps by flashing the 3 zip files......have unlocked bootloader and installed twrp 3.1.0.1 and trying to install magisk 13.3 but it always stuck at huawei logo.
Have also tried rooting but it seems only SuperSU2.82EMUI5noverityEnforcing works and do i need to follow the steps of formatting data to get it decyrpted?
Currently on MHA-L29C185B182 at the moment.
Thx @ante0 for your kind gesture.Appreciated
Click to expand...
Click to collapse
My bad.
If you're using official Magisk 13.3, that's why it's not booting. Since your data partition is encrypted, and Magisk removes the encryption flag, it tries to boot without decrypting. So it ends in a boot loop.
Use this: https://mega.nz/#!I4FQzbyA!gBZelHmD3lGGwzGISUXkf7GQTUAq5i785d_qPHQOaVE (this one just doesn't force remove encryption)
Or decrypt first, then flash HW and Public and official Magisk 13.3.
But yes, to decrypt you need to format data.
ante0 said:
My bad.
If you're using official Magisk 13.3, that's why it's not booting. Since your data partition is encrypted, and Magisk removes the encryption flag, it tries to boot without decrypting. So it ends in a boot loop.
Use this: https://mega.nz/#!I4FQzbyA!gBZelHmD3lGGwzGISUXkf7GQTUAq5i785d_qPHQOaVE (this one just doesn't force remove encryption)
Or decrypt first, then flash HW and Public and official Magisk 13.3.
But yes, to decrypt you need to format data.
Click to expand...
Click to collapse
Is there another way of flashing the 3 zip files without running through pc cuz i dont know whats happening. Am done with with everything working with Magisk and data encrypted but what i have realised this around is my development option is not working along with debugging mode. Also am not able to install apk aside from playstore....Due to that adb in command prompt is not working cuz debugging mode is disables.
In fastboot mode am only able to check device status and reboot device.Id you send a commnd to flash an image it response failed....
golastic said:
Is there another way of flashing the 3 zip files without running through pc cuz i dont know whats happening. Am done with with everything working with Magisk and data encrypted but what i have realised this around is my development option is not working along with debugging mode. Also am not able to install apk aside from playstore....Due to that adb in command prompt is not working cuz debugging mode is disables.
In fastboot mode am only able to check device status and reboot device.Id you send a commnd to flash an image it response failed....
Click to expand...
Click to collapse
If you can't get in to dev options, wipe dalvik/art & cache in twrp, it could fix playstore as well.
If you can't enable adb, try enable disable a few times and remove USB cable between. I always have to do that the first time.
You can actually do everything from twrp to install firmware. But you'd have to check the hwota.sh file for commands... There are a few you must execute.
And is camera working now again?
ante0 said:
Before updating, have you tried restoring boot without rooting and see if that fixes camera?
Try this one, I removed verity and replaced fileencryption with encryptable so it doesn't encrypt your /data again.
https://mega.nz/#!lhE2zLSR!ngNY3bXKMS_eKizjmfnKHbFgVSVnp94dgCXnxuL_G_0
If it doesn't do anything, continue below.
Currently, https://forum.xda-developers.com/mate-9/how-to/guide-mate-9-flash-update-package-t3593108
Other ways are Firmware Finder or OTA, but both those require your IMEI to be approved for the update.
And Funky Huawei, which you need to pay for.
It will wipe /data when/if you decrypt again so make sure to make a backup of /data first, or backup apps with Titanium Backup or which backup app you use.
Basically download the Base zip, MHA zip and Windows or linux zip from https://forum.xda-developers.com/mate-9/how-to/guide-mate-9-flash-update-package-t3593108
Extract all to the same folder (hwota) and merge if it asks.
Then download:
http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1366/g104/v91627/f1/full/update.zip
http://update.hicloud.com:8180/TDS/...hw_meafnaf/update_full_MHA-L29_hw_meafnaf.zip
http://update.hicloud.com:8180/TDS/...27/f1/full/public/update_data_full_public.zip
Put all in the "update" folder in the hwota folder you extracted before.
Rename update_full_MHA-L29_hw_meafnaf.zip to update_all_hw.zip
Rename update_data_full_public.zip to update_data_public.zip
Put phone in fastboot mode (download mode) and run update.bat (windows) or update.sh (linux)
Pick "Same brand update" when it asks, and "Script update directory".
When it's done your bootloader will be locked again so you need to unlock it if you want to root again.
You will be able to install regular Magisk 13.3 now without superuser (phh)
Click to expand...
Click to collapse
ante0 said:
If you can't get in to dev options, wipe dalvik/art & cache in twrp, it could fix playstore as well.
If you can't enable adb, try enable disable a few times and remove USB cable between. I always have to do that the first time.
You can actually do everything from twrp to install firmware. But you'd have to check the hwota.sh file for commands... There are a few you must execute.
And is camera working now again?
Click to expand...
Click to collapse
Yes Camera is working good and it looks like they have added a new feature in the camera app for b182 called MOVING PICTURE which add sound whiles you capture.I use to love that when i was using S5.
Now after careful observation about the instruction u gave me,am able to install B182 ,have decyrpted data ,have magisk 13.3 running without any issue.
I jux wanna say thanks so much for your patience with me...Much appreciated:good::good::good::good::good:
BTW which of the models will u recommend if want to rebrand?:
Hello all, long time member but never really had a reason to post.
I just received my oneplus6, I wanted IOS style emojis (ridiculous I know... lol) So I unlocked bootloader, flashed the temporary TWRP release and flashed MAGISK.
When I booted my phone the error "There's an internal problem with your device contact your device manufacturer" comes up. Unfortunately I took my nandroid backup AFTER installing MAGISK.
I have no wifi at all, I can't use wifi hotspot either, but cellular works. I wanted to flash back to stock recovery but it seems oneplus hasn't released it. I have tried removing magisk and rebooting (via the magisk app) but then the device wont boot.
I canno't flash a stock copy of OxygenOS as it seems it can only be flashed with stock oxygen oneplus6 recovery (which I cannot get access to.) TWRP simply fails to flash it.
Recently in an attempt to solve my issue I formatted the memory, magisk has gone from my app drawer, but the effects it had are still there (I still have IOS emojis) Now apps wont login (snapchat for example says there is a temporary error) Facebook managed to login after a few reboots, I cannot stream video at all. And as I have formatted memory the original nandroid backup (after magisk flash where apps would login but still gives the internal error message and no wifi) is gone.
I really just want to get the device back to a stable operation, if anyone knows what I should do next or somehow has access to stock oneplus6 recovery, please let me know! Thankyou in advance for all help.
Find post with stock fastboot ROMs, download it and extract, then run flash-all.bat while phone is in fastboot
But data will be gone
DalekExt said:
Find post with stock fastboot ROMs, download it and extract, then run flash-all.bat while phone is in fastboot
But data will be gone
Click to expand...
Click to collapse
you mean this?: https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665
I just did this and it has bricked the phone lol, it fails when I try to complete it
Bricked
19kylegreer96 said:
you mean this?: https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665
I just did this and it has bricked the phone lol, it fails when I try to complete it
Click to expand...
Click to collapse
Hi,there is un-brick tool available
I would just like to guide anyone who might be having the same issue as me, to this post:
https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665
And take note of what I said here about Large address aware ( to make this fix work on 64bit PC):
https://forum.xda-developers.com/showpost.php?p=76658555&postcount=34
Using the BAT file in that post that I have linked and the large address aware fix, my problem is fixed and I have now booted the phone and have working wifi!
If you run into that issue next time, just remember to install the provided boot image within TWRP, along with the other zip files to get TWRP to not lag. I had the exact same issues as you and I realized I missed the step of flashing the boot.img within TWRP.
Once I did that, I had working TWRP and WiFi!
I received the same message after rooting. However, everything is working well (wifi, 4G/LTE/camera, etc) except this message [There's an internal problem with your device. Please contact your adminstrator] during start-up.
Whenever I have seen this I just flash the same version of the original rom over my install and it fixes it.
I also notice that for me, Magisk 6.6 causes this, whereas 6.4 does not.
Was an issue if you use Magisk and stock kernel. Use any other kernel around: They fixed it. @Sultanxda pointed the issue at his GitHub site and kernel devs have included it. Thanks @Sultanxda for this .
MickyFoley said:
Was an issue if you use Magisk and stock kernel. Use any other kernel around: They fixed it. @Sultanxda pointed the issue at his GitHub site and kernel devs have included it. Thanks @Sultanxda for this .
Click to expand...
Click to collapse
Going from memory so I might not have it straight but I want to say this was from installing either twrp on just 1 partition or Magisk on the inactive partition. Making 16.4 and 16.6 works perfectly with stock kernel since already 5.1.6 for me as I've had this phone since launch.
It was all working without a problem - just the message popped up. Altering something in the kernel triggered this to happen. @eng.stk got this issue explained by another user, pointing to the Git from sultanxda. Since then, it was solved. Dunno. Had this in the very beginnings and since then never again. Well... Yeah
Thanks
MickyFoley said:
Was an issue if you use Magisk and stock kernel. Use any other kernel around: They fixed it. @Sultanxda pointed the issue at his GitHub site and kernel devs have included it. Thanks @Sultanxda for this .
Click to expand...
Click to collapse
Thank you. That worked fine. I flashed [KERNEL] [blu_spark r31 OP6] [OOS 5.1.*] and the Error-Message is gone.
Installing a custom kernel fixed the issue for me as well.
Magisk fully working now as well as safetynet.
Might want to to edit the title to *fixed* so people know you resolves your issue.
Q: After flashing Magisk, my device will show a scary popup saying "There's an internal problem with your device. Contact your manufacturer for details"
A: This is caused by dtbo image patched to remove AVB 2.0 of the vendor partition. This is required for allowing you to mount vendor to rw and make modifications
If you never plan to modify the vendor partition, in Magisk Manager, "Uninstall > Restore Images" to restore the images, check "Preserve AVB 2.0/dm-verity" box in Advanced Settings, then reinstall Magisk via the app.
JerryGoyal said:
Q: After flashing Magisk, my device will show a scary popup saying "There's an internal problem with your device. Contact your manufacturer for details"
A: This is caused by dtbo image patched to remove AVB 2.0 of the vendor partition. This is required for allowing you to mount vendor to rw and make modifications
If you never plan to modify the vendor partition, in Magisk Manager, "Uninstall > Restore Images" to restore the images, check "Preserve AVB 2.0/dm-verity" box in Advanced Settings, then reinstall Magisk via the app.
Click to expand...
Click to collapse
Great, it worked!!!! It solved the scary message pop-up and kept the root. Thanks!!!
Hi, i have a oneplus 6 rooted with magisk running twrp recovery and last night i was messing around with a mock location spoofer and everything was going okay but after a reboot my phone started only going into safe mode and i couldnt access anything basically my phone screen would flash on then off then on and off again constantly.
i Followed this tutorial https://www.reddit.com/r/PokemonGoSpoofing/comments/8ytjz5/expert_mode_for_fake_gps_and_routes/
then after that i had trouble using systemizer to make the app a system app so i used lucky patcher instead.
after all this my phone was working fine
the final thing i done what wasnt on the tutorial was used a package manager app to disable all location services from a very low software level. after that the safe mode thing started happening.
what i have tried so far -
i have tried going into the root and deleteing the app folder for the APK MANAGER app hoping that this would remove any changes it caused.
i have also tried using the magisk uninstaller to try and remove root.
now my phone wont even boot. i get a screen on start up saying my phone is corrupt and it just loops on this screen.
Before i do a full reflash and loose everything i thought id put my last hope on here and see if anyone can help me resolve this without a reflash.
Thanks for any help i'm stupid and didn't back up before hand
https://forum.xda-developers.com/oneplus-6t/how-to/guide-how-to-fix-red-boot-screen-device-t3891479
mauronofrio said:
https://forum.xda-developers.com/oneplus-6t/how-to/guide-how-to-fix-red-boot-screen-device-t3891479
Click to expand...
Click to collapse
thanks when i follow instructions it says too many symbolic links. can you help?
Shaun98 said:
thanks when i follow instructions it says too many symbolic links. can you help?
Click to expand...
Click to collapse
If you are root, install terminal app from playstore
open terminal, type : su, hit enter > grant root permission
then type : reboot "dm-verity enforcing", hit enter
I've got my shiny new Pixel 4 XL up and running on the stock ROM after coming from a worn out Note 8. Everything is better except the new version of GMaps. I was using 9.47.x and this new 10.x.x is just awful. I want to completely delete the stub from the system so I can install the older version. I've tried several root uninstallers, even using the adb shell command. It always "uninstalls" but the stub is still there. Therefore the older APK refuses to install. I've even gone into the root/product/app/maps folder to try manually. It doesn't work, nor does changing any permissions. I have a feeling someone is going to tell me that this can't be done without installing a custom rom.
I'm guessing the culprit is not being able to remount the system with read/write permissions on newer versions of android. Unless there's something I'm missing.
iBreakStuff said:
I've got my shiny new Pixel 4 XL up and running on the stock ROM after coming from a worn out Note 8. Everything is better except the new version of GMaps. I was using 9.47.x and this new 10.x.x is just awful. I want to completely delete the stub from the system so I can install the older version. I've tried several root uninstallers, even using the adb shell command. It always "uninstalls" but the stub is still there. Therefore the older APK refuses to install. I've even gone into the root/product/app/maps folder to try manually. It doesn't work, nor does changing any permissions. I have a feeling someone is going to tell me that this can't be done without installing a custom rom.
I'm guessing the culprit is not being able to remount the system with read/write permissions on newer versions of android. Unless there's something I'm missing.
Click to expand...
Click to collapse
It may be having a conflict with cached data from the version that you installed, removing the cached data might allow you to install the version you want.
Uninstall the app from system partition, then, power the device off, then, boot into recovery and wipe the cache partition, then reboot into system and try installing the older version.
Sent from my SM-S767VL using Tapatalk
Droidriven said:
Uninstall the app from system partition, then, power the device off, then, boot into recovery and wipe the cache partition, then reboot into system and try installing the older version.
Click to expand...
Click to collapse
That is right where the issue is. I can get it to the point from being a 66mb APK down to 200k where the system; or play store, even recognizes it's installed. I need to get write access to the system partition to get rid of the "Maps" folder persistently living in the root apps folder. If that can be done on 10 in stock recovery then I've never done that. Mind you I'm rooted on Magisk with the flashed boot image, no TWRP yet.
iBreakStuff said:
That is right where the issue is. I can get it to the point from being a 66mb APK down to 200k where the system; or play store, even recognizes it's installed. I need to get write access to the system partition to get rid of the "Maps" folder persistently living in the root apps folder. If that can be done on 10 in stock recovery then I've never done that. Mind you I'm rooted on Magisk with the flashed boot image, no TWRP yet.
Click to expand...
Click to collapse
After flashing the Magisk patched boot.img, did you install the Magisk Manager app? Magisk Manager is what is used to grant root permissions to your other apps. There is more to it than just flashing the boot.img.
You can also use adb shell to remove the app as demonstrated in the second method described in the link below.
https://www.maketecheasier.com/uninstall-system-apps-without-root-android/
Sent from my SM-S767VL using Tapatalk
Droidriven said:
After flashing the Magisk patched boot.img, did you install the Magisk Manager app? Magisk Manager is what is used to grant root permissions to your other apps. There is more to it than just flashing the boot.img.
You can also use adb shell to remove the app as demonstrated in the second method described in the link below.
https://www.maketecheasier.com/uninstall-system-apps-without-root-android/
Sent from my SM-S767VL using Tapatalk
Click to expand...
Click to collapse
So I tried what you suggested, I got the same result. Maps uninstalls but still lives in the root directory. Not being an ADB expert I went into adb shell super user mode and tried the the rm command to delete the folder, also the remount system command. Neither of those worked. Trying to install the older APK results in "App not installed"
And yes I have Magisk manager. It installed the latest version automatically. I use RootExplorer and it has superuser permissions.
Would something like this work? I'm not completely clear on how this works.
https://www.isrgrajan.com/how-to-copy-and-delete-files-in-android-using-recovery-mode.html