Related
All of a sudden the superuser on my TF700 stopped working; all rooted apps are now being denied superuser status. Worse, Superuser won't reinstall, and Rootchecker.apk tells me the tablet isn't rooted anymore. Voodoo OTA rootkeeper still has the saved root files, but won't reinstall them on account of the borked superuser, I'm assuming.
I should add that NONE of the available Superuser apps will install; not the original Superuser, Koush's Superuser, or SuperSU.
So I tried the whole rooting procedure by trying to downgrade to ICS. But although the tablet sees the file it won't install it; on reboot all I get is the dead Android with a big red X. When I tried it a second time, the tablet now doesn't even acknowledge the presence of the downgrade file.
I need help here. I just rooted this tablet but never installed recovery (wasn't interested in unlocking it at the time). How do I proceed from here?
mudge
iCurmudgeon said:
All of a sudden the superuser on my TF700 stopped working; all rooted apps are now being denied superuser status. Worse, Superuser won't reinstall, and Rootchecker.apk tells me the tablet isn't rooted anymore. Voodoo OTA rootkeeper still has the saved root files, but won't reinstall them on account of the borked superuser, I'm assuming.
I should add that NONE of the available Superuser apps will install; not the original Superuser, Koush's Superuser, or SuperSU.
So I tried the whole rooting procedure by trying to downgrade to ICS. But although the tablet sees the file it won't install it; on reboot all I get is the dead Android with a big red X. When I tried it a second time, the tablet now doesn't even acknowledge the presence of the downgrade file.
I need help here. I just rooted this tablet but never installed recovery (wasn't interested in unlocking it at the time). How do I proceed from here?
mudge
Click to expand...
Click to collapse
Hard for me to understand where you're at exactly.
Did you actually boot into ICS before trying to re-root?
Sometimes when SuperSU updates you will have to go back into the application and reset permissions for all rooted applications.
If you can boot and if the previous SU is still there go into settings for the tablet and uninstall any updates for SuperSU then try to reset permissions in the app.
iCurmudgeon said:
All of a sudden the superuser on my TF700 stopped working; all rooted apps are now being denied superuser status. Worse, Superuser won't reinstall, and Rootchecker.apk tells me the tablet isn't rooted anymore. Voodoo OTA rootkeeper still has the saved root files, but won't reinstall them on account of the borked superuser, I'm assuming.
I should add that NONE of the available Superuser apps will install; not the original Superuser, Koush's Superuser, or SuperSU.
So I tried the whole rooting procedure by trying to downgrade to ICS. But although the tablet sees the file it won't install it; on reboot all I get is the dead Android with a big red X. When I tried it a second time, the tablet now doesn't even acknowledge the presence of the downgrade file.
I need help here. I just rooted this tablet but never installed recovery (wasn't interested in unlocking it at the time). How do I proceed from here?
mudge
Click to expand...
Click to collapse
Go into settings -> recovery- factory reset. Try one or both if needed:
1. Download the full Asus ICS .30 zip, verify MD5 (ensure file is not corrupted), unzip the file then copy the unzipped file called US_epad-user-9.4.5.30.zip to the root of your internal, boot into stock recovery and let it flash.
or
2. Reformat your micro sdcard.
1) Download and unzip US_epad_user_9_4_5_30_20120907_UpdateLauncher.zip and got US_epad-user-9.4.5.30.zip. Copied it to root of microsdcard, reboot your tablet and check your notification for software update.
or
3) unzip US_epad_user_9_4_5_30_20120907_UpdateLauncher.zip and got US_epad-user-9.4.5.30.zip. Rename this file to EP201_768_SDUPDATE.zip then copy this to root of microsdcard. Power off your device, boot into recovery by hold power + vol down buttons, when you see white text release both buttons, you should see 4 icons. The icon "RCK" should be highlighted by default, just wait a few seconds and it should start flashing.
then renamed US_epad-user-9.4.5.30.zip to EP201_768_SDUPDATE.zip and
Thats OK said:
Hard for me to understand where you're at exactly.
Did you actually boot into ICS before trying to re-root?
Sometimes when SuperSU updates you will have to go back into the application and reset permissions for all rooted applications.
If you can boot and if the previous SU is still there go into settings for the tablet and uninstall any updates for SuperSU then try to reset permissions in the app.
Click to expand...
Click to collapse
I finally managed to get back to ICS, then ran the rooting procedure. However, it always failed when it came to testing Superuser. Tried it four or five times. Then I tried installing the other Superuser apks. Every last one of them said the su binary needed to be updated, but every one of them failed to do so.
That's where I am right now. Unrooted ICS.
buhohitr said:
Go into settings -> recovery- factory reset. Try one or both if needed:
1. Download the full Asus ICS .30 zip, verify MD5 (ensure file is not corrupted), unzip the file then copy the unzipped file called US_epad-user-9.4.5.30.zip to the root of your internal, boot into stock recovery and let it flash.
or
2. Reformat your micro sdcard.
1) Download and unzip US_epad_user_9_4_5_30_20120907_UpdateLauncher.zip and got US_epad-user-9.4.5.30.zip. Copied it to root of microsdcard, reboot your tablet and check your notification for software update.
or
3) unzip US_epad_user_9_4_5_30_20120907_UpdateLauncher.zip and got US_epad-user-9.4.5.30.zip. Rename this file to EP201_768_SDUPDATE.zip then copy this to root of microsdcard. Power off your device, boot into recovery by hold power + vol down buttons, when you see white text release both buttons, you should see 4 icons. The icon "RCK" should be highlighted by default, just wait a few seconds and it should start flashing.
then renamed US_epad-user-9.4.5.30.zip to EP201_768_SDUPDATE.zip and
Click to expand...
Click to collapse
Thanks for the info. I managed to get back into ICS (see previous msg) using your number 1 (took three tries) but I can't complete the root procedure because for some unknown reason superuser won't install correctly.
iCurmudgeon said:
Thanks for the info. I managed to get back into ICS (see previous msg) using your number 1 (took three tries) but I can't complete the root procedure because for some unknown reason superuser won't install correctly.
Click to expand...
Click to collapse
Is there a previous version of SU installed or leftover?
See if it's still in running apps under settings.
If you're on ICS I'd try a factory reset and go from there.
iCurmudgeon said:
Thanks for the info. I managed to get back into ICS (see previous msg) using your number 1 (took three tries) but I can't complete the root procedure because for some unknown reason superuser won't install correctly.
Click to expand...
Click to collapse
After you flashed superuser, did you launch the app?? you need to launch the app and it should prompt to update, do the update. Once done now you can test for root.
buhohitr said:
After you flashed superuser, did you launch the app?? you need to launch the app and it should prompt to update, do the update. Once done now you can test for root.
Click to expand...
Click to collapse
I did launch the app and it did tell me the su binary needed to be updated. So I told it to go ahead with a normal install. Installation failed. Also tried the SU update fixer from the play store, and that failed as well.
You need to reflash your ROM... I get this often. I'm maintaining 6 devices for my family.
Lim Wee Huat said:
You need to reflash your ROM... I get this often. I'm maintaining 6 devices for my family.
Click to expand...
Click to collapse
Yes, I would agree, this is the only way left for what to do next!
buhohitr said:
Yes, I would agree, this is the only way left for what to do next!
Click to expand...
Click to collapse
Ouch. But didn't I do this when I downgraded from Jellybean back to ICS?
Can someone point me to a post how to do this?
iCurmudgeon said:
Ouch. But didn't I do this when I downgraded from Jellybean back to ICS?
Can someone point me to a post how to do this?
Click to expand...
Click to collapse
Just do a factory reset, then follow my number 3 post. Also make sure you verify MD5 on the ICS .30 rom before flashing.
buhohitr said:
Just do a factory reset, then follow my number 3 post. Also make sure you verify MD5 on the ICS .30 rom before flashing.
Click to expand...
Click to collapse
Well, I tried, but when I rebooted with the power and vol-down buttons, I only got an "Android" icon and something else to its left, no RCK at all. The pad rebooted eventually and I was stunned when Superuser started working! I immediately ran Voodoo OTA Rootkeeper, then let the tablet update to 4.1.1. I then ran SuperSU and it said the su binary needed to be updated. I told it to do a normal install. "Installation failed." Said bad words in several languages and tried again. Update of SU binary succeeded.
Restored root. Success. Now restoring last Titanium backup backup.
I'm still worried, though. The symptoms would seem to point to flaky or at least unstable flash memory. What do you think?
I gotta decide whether to get a Samsung Galaxy Note tablet (7-inch) or the updated Nexus 7 tablet when they come out. I don't trust this TF700 anymore..
mudge
I have the same problem, but didn't downgrade!
I have the same problem, except I have not tried to downgrade.
The first problem I noticed after the OTA update was that Bluetooth simply would not turn on. Going through the steps to fix this problem I noticed that OTA Rootkeeper "kept root", but any time I try to use su, it fails to work.
I managed to fix bluetooth using ADB, but I am still left with su and superuser that do not work. Is there a way to fix this from ADB by twiddling with permissions somehow?
IT Wannabe said:
I have the same problem, except I have not tried to downgrade.
The first problem I noticed after the OTA update was that Bluetooth simply would not turn on. Going through the steps to fix this problem I noticed that OTA Rootkeeper "kept root", but any time I try to use su, it fails to work.
I managed to fix bluetooth using ADB, but I am still left with su and superuser that do not work. Is there a way to fix this from ADB by twiddling with permissions somehow?
Click to expand...
Click to collapse
Seems like now there is a way to root if you already on JB, no need to downgrade to root.http://forum.xda-developers.com/showthread.php?t=2228613 .
buhohitr said:
Seems like now there is a way to root if you already on JB, no need to downgrade to root.http://forum.xda-developers.com/showthread.php?t=2228613 .
Click to expand...
Click to collapse
The su and busybox binares and SuperSU.apk get installed, but any time I try to use root permissions I get an Access/Permission Denied error. I used the root method you gave me and everything seemed to work properly... The only thing I see that may be wrong is that the su binary is owned by "root root" rather than "root shell" like everything else is. If I try to chmod it using ADB I get permission denied errors.
Now I'm just frustrated and don't know what to do. Nothing seems to work with the 4.2.1 stock ROM. I don't want to have to unlock the bootloader because I chose not to void the warranty (didn't enable nvflash) when I first got my tablet.
I think I'm just screwed at this point. Does anyone have any ideas? I did manage to get bluetooth working, but I still can't seem to get my TF700 rooted. Without root, Titanium Backup can't restore my apps...
IT Wannabe said:
The su and busybox binares and SuperSU.apk get installed, but any time I try to use root permissions I get an Access/Permission Denied error. I used the root method you gave me and everything seemed to work properly... The only thing I see that may be wrong is that the su binary is owned by "root root" rather than "root shell" like everything else is. If I try to chmod it using ADB I get permission denied errors.
Now I'm just frustrated and don't know what to do. Nothing seems to work with the 4.2.1 stock ROM. I don't want to have to unlock the bootloader because I chose not to void the warranty (didn't enable nvflash) when I first got my tablet.
I think I'm just screwed at this point. Does anyone have any ideas? I did manage to get bluetooth working, but I still can't seem to get my TF700 rooted. Without root, Titanium Backup can't restore my apps...
Click to expand...
Click to collapse
Since motochopper has the ablility to root JB, you should remove superuser root (open supersuser and select remove root then reboot), then re root using motochopper if needed.
I finally managed to fix the problem, though I did it the long way...
I downloaded the stock 9.4.5.30 US ROM zip file, extracted it, renamed the extracted zip file to EP201_768_SDUPDATE.zip, and copied it to a microSD card. I booted to recovery and installed the zip file. Once it was installed, I went to Settings --> About Tablet --> System Update --> Check Update. I had to update this way twice to get to a clean, stock JellyBean 4.2.1 (US_epad-10.6.1.14.4-20130329).
Once I was up to date, I ran the Motochopper root tool and it worked! I have no idea what it was about my tablet that prevented su from working after the update to 4.2, but thanks to everyone for your suggestions.
IT Wannabe said:
I finally managed to fix the problem, though I did it the long way...
I downloaded the stock 9.4.5.30 US ROM zip file, extracted it, renamed the extracted zip file to EP201_768_SDUPDATE.zip, and copied it to a microSD card. I booted to recovery and installed the zip file. Once it was installed, I went to Settings --> About Tablet --> System Update --> Check Update. I had to update this way twice to get to a clean, stock JellyBean 4.2.1 (US_epad-10.6.1.14.4-20130329).
Once I was up to date, I ran the Motochopper root tool and it worked! I have no idea what it was about my tablet that prevented su from working after the update to 4.2, but thanks to everyone for your suggestions.
Click to expand...
Click to collapse
Can you tell us what the owner,group and permissions of the /system/bin/su binary are now ?
sgtrwe said:
Can you tell us what the owner,group and permissions of the /system/bin/su binary are now ?
Click to expand...
Click to collapse
Oh, sure!
After a search through my PATH, I've found that 'su' no longer lives in /system/bin, but in /system/xbin, with busybox and dexdump and every POSIX command you can think of symlinked to busybox. It is owned by root:root.
I guess that's just the way the JB root method does it...
Hi guys android newbie here! My friend rooted my Nexus 5 and it was working fine for a couple of weeks. Yesterday I tried to open SuperSU and it didn't work! Other apps that required root didn't work either.
I have been looking around and it seems OTA updates may have screwed up my root. Every time I try to open SuperSU it says: "There is no SU binary installed, and SuperSU cannot install it. This is a problem!" If you just upgraded to Android 4.3 (I have 4.4), you need to manual re-root. Consult the relevant forums for your device!" I have used root checker by joeykrim and it says "Sorry! this device does not have proper root access" (to confirm my root is busted).
My question is, is there any way to fix this without re-rooting? If I have to re-root, can I just directly re-root it again using something like Wugs rootkit?
Thank you very much in advance!
Just flash the newest version of supersu and you'll be good to go..... http://download.chainfire.eu/370/SuperSU/UPDATE-SuperSU-v1.80.zip
go to the play store, find supersu, install/update it, open tbe app and update your binaries.
simms22 said:
go to the play store, find supersu, install/update it, open tbe app and update your binaries.
Click to expand...
Click to collapse
I've tried to insyall /uninstall, wiping the cache and data with no luck. Right when I open the app the supersu binary problem comes up and I can't even get into it!
seyba said:
I've tried to insyall /uninstall, wiping the cache and data with no luck. Right when I open the app the supersu binary problem comes up and I can't even get into it!
Click to expand...
Click to collapse
cant even get into it?
Yea it says there is no SU binary installed. I think I've lost root access
seyba said:
Yea it says there is no SU binary installed. I think I've lost root access
Click to expand...
Click to collapse
flash this with your custom recovery, its the latest supersu http://download.chainfire.eu/supersu
bodooo said:
Just flash the newest version of supersu and you'll be good to go.....
Click to expand...
Click to collapse
I can install/update to v1.8! I just can't open it. Gives me a "SU binary not installed" when I do!
Did you install/update from the playstore or flashed the new update?
simms22 said:
flash this with your custom recovery, its the latest supersu
Click to expand...
Click to collapse
Sorry if this is a stupid question .. but how/ do I flash this or what program do i use?
My friend helped me root it so i have no idea on how to do this @@ Very sorry.
Hmmm... from the link I posted in one of my last post, you can just use a useful app called "flashify" and flash it that way (the easiest way) but you need that file that is in the link obviously to do so haha. So afterwards when in flashify you'll get 3 simple options, boot image, recovery image, and zip file. choose zip file, go into your downloads folder from the file explorer from the app (which it should be there if you downloaded it off your phone) and let the app do the rest
bodooo said:
Hmmm... from the link I posted in one of my last post, you can just use a useful app called "flashify" and flash it that way (the easiest way) but you need that file that is in the link obviously to do so haha. So afterwards when in flashify you'll get 3 simple options, boot image, recovery image, and zip file. choose zip file, go into your downloads folder from the file explorer from the app (which it should be there if you downloaded it off your phone) and let the app do the rest
Click to expand...
Click to collapse
Ok so I can't open flashify either. It also says I have lost root access and my superuser is busted. I have attached a screenshot!
http://i42.tinypic.com/2mgw0v6.png
Of course, you don't have root access, silly me lol Well guess we'll have to do it the hard way (it's not really that complicated) ok read carefully. Power off your phone, afterward hold the power and volume down buttons which should get you into the bootloader, cycle trough the options with the volume buttons and when you see recovery mode select it with the power button, now depending on which Recovery you have you'll have to choose the option that says install or install from sd card, again, depending on which one you have this will be slightly different. After doing i believe the paths will be the same, chose 0/ then look for the download/ folder which you should have that supersu.zip file, if you're using twrp recover it should be touch screen and you simply select it and swipe to install, if you're using cwm (which i do) you'' have to scroll with the volume buttons and select the file with the power button to install. I hope I was as clear as i could be, good luck
after going into recovery mode, there is just a android robot with his chest open and an exclamation mark! can't proceed after that.
Ouhhh you don't have a recovery then, do you have adb or any kind of toolkit?
I have wugs toolkit. but every time i try to do anything at all on it. It says ADB device not found? That seems to be preventing me from doing anything as well.
Do you have the adb drivers installed or/and usb debug turned on in developer settings?
how/where do i install adb drivers? I have not done so, and i doubt my friend did it when he rooted.
I do turn on usb debugging when i tried to unroot/root on wugs toolkit
In wugs toolkit it has a walk-through on how to do so, i suggest you use the RAW drivers option
I must be blind to not have seen this before. Thank you very much for your help I'll let you know how it goes!
So I decided it's time to upgrade seeing as my phone prompted me to do so. My phone is rooted and I wanted to keep it that way. I downloaded the latest version D6603_23.5.A.0.570_R2D (Swiss edition) using experifirm and then created the ftf using flashtool. (Latest version for all apps). I then used prf creator to create a flashable zip installable file (see attached picture)
With PRF creator I added the ftf file, SuperSU-v2.65-20151226141550, Z3-lockeddualrecovery2.8.26 and also in the Extra Files section; RICDefeat.zip and byeselinux_flashable.zip
The zip file I then copied to my sd card, rebooted into recovery and installed. Once the upgrade was complete, I discovered to my horror, that root is gone.
My question is, where did I go wrong? What did I leave out etc.
Final question, how to get my phone rooted again?
As far as I understand using the superSU zip without it being modded to be a system install means it will install as systemless (tried to get around MM root verification) with Sony this actually causes a problem whereas the system root (normal SU) works just fine for us with the extras you added.
You did everything right. But superSU needs to be different and duel recovery does not work with MM.
One way is to leave the recovery part blank and just add RecRootv3 under the SU part. This will install SU as system and all the other parts like byeselinux and RICDefeat.
Also you cannot use NUT duel recovery with MM yet it does not work. RecRoot includes TWRP which you boot into by pressing volume down like duel recovery.
Hope this helps. There is not a guide that I can see so it is all a bit confusing for now so I don't blame you for using the lollipop method!
Missed the bit about rerooting! You're gonna have to do the whole downgrade to KitKat, root, update to MM procedure again (unless I missed a new way to do it)... tbh a clean install won't do any harm so back everything up and go ahead. Guides are around if you need them
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?: