So i tried to update my software as i saw it was available through the phone.I downloaded it and then i got stuck in the custom recovery, i couldn't exit it.Then i managed to flash the stock one and i rebooted the recovery and everything was going fine with the update until it gave me an error and then rebooted.When it opened it said that the software update can't be done on rooted phones, any idea how unroot it?By unroot i mean also when i go into Download Mode to show "Unrooted" instead of "Rooted" as it is now. Thanks in advance!
http://forum.xda-developers.com/showthread.php?p=54601303
Sent from my D620R [Stock 4.4.2]
Then make a file named rct_security at /sdcard/ containing this: forel.lee
Click to expand...
Click to collapse
By this you mean to make a file rct_security and use a notepad to add forel.lee, or you mean to make a folder called rct_security and add inside it a file called forel.lee ?
Update : I've tried both methods none of them worked it still shows ROOTED in Download Mode.
Rephosix said:
By this you mean to make a file rct_security and use a notepad to add forel.lee, or you mean to make a folder called rct_security and add inside it a file called forel.lee ?
Update : I've tried both methods none of them worked it still shows ROOTED in Download Mode.
Click to expand...
Click to collapse
Unroot with SuperSU' s "Full Unroot" option. Then make a file named rct_security at /sdcard/ and in it type forel.lee
ota update
Rephosix said:
So i tried to update my software as i saw it was available through the phone.
Click to expand...
Click to collapse
could you give more information about the update? I'm just curious.
I tried the "Full Unroot" + forel.lee method (Busybox uninstalled), got the RCT check pass, but the update didn't installed. After restart I got a message about installation problem, and to try again.
rpul said:
I tried the "Full Unroot" + forel.lee method (Busybox uninstalled), got the RCT check pass, but the update didn't installed. After restart I got a message about installation problem, and to try again.
Click to expand...
Click to collapse
I can only think of 2 possibilities:
1. You have a custom recovery installed which doesn't install the update automatically
2. Stock recovery detects changes to your system and cancels the installation of the update
Sent from my D620R [Stock 4.4.2]
I have towelrot root, no custom recovery, no unlocked bootloader.
At the beginning, I tried with just RCT_security file (I didn't understand the process entirely) and stock recovery showed Err: 1117008 or Err: 1118007, I can't recall for sure. After restart I got the message about no software updates for rooted phones. After that I did go for "Full unroot" in SuperSU, put the RCT_security again (it was deleted), edited rct.cfg (it seems this was unnecessary, as this seems to be just a log file), deleted busybox and su files manually, and after that I tried the software update again. Stock recovery showed the same error, but after restart I didn't got the message about no updates for rooted phone. Instead I got a message about unsuccessful installation, and to try to again the update. I tried a couple of times, but the result was the same.
rpul said:
I have towelrot root, no custom recovery, no unlocked bootloader.
At the beginning, I tried with just RCT_security file (I didn't understand the process entirely) and stock recovery showed Err: 1117008 or Err: 1118007, I can't recall for sure. After restart I got the message about no software updates for rooted phones. After that I did go for "Full unroot" in SuperSU, put the RCT_security again (it was deleted), edited rct.cfg (it seems this was unnecessary, as this seems to be just a log file), deleted busybox and su files manually, and after that I tried the software update again. Stock recovery showed the same error, but after restart I didn't got the message about no updates for rooted phone. Instead I got a message about unsuccessful installation, and to try to again the update. I tried a couple of times, but the result was the same.
Click to expand...
Click to collapse
Well you can either use KDZ to wipe all the evidence in RCT and then update the software or use the LG program to update.Just open B2CAppSetup, wait for it to install, then plug your phone into the PC, select Software Mode, the program should recognize your phone, install your driver from the program then the program should say something like "A newer software version is available", then just wait and your phone should get into download mode and then reboot and open up but don't unplug it yet because as you can in see program is not done yet, just wait until the program get to 100%.
Updated by using LG program, but lost root. I did root it again after update. I still have a couple of problems after update, as some of the apps didn't work. I got most of them working except of one navigation app.
EDIT:
Got all the apps working again. I needed to apply SDFix again (KitKat problems with sdcard access related).
rpul said:
Updated by using LG program, but lost root. I did root it again after update. I still have a couple of problems after update, as some of the apps didn't work. I got most of them working except of one navigation app.
EDIT:
Got all the apps working again. I needed to apply SDFix again (KitKat problems with sdcard access related).
Click to expand...
Click to collapse
It is easier to root your phone via Towelroot.
Link: https://towelroot.com/
Related
Hi,
After changing my phone's date into the future, my G2 Touch told me there was an update available, so I told it to go ahead and apply it. When the phone rebooted it came up with this message:
E:No signature (218 files)
E:Verification failed
Installation aborted
I have nandroid installed on the phone. At least I think that's what's installed - I haven't played with any ROM stuff since November I think, when I changed the bootloader (I think - if that's what's giving me the option to do a nandroid backup now) and installed the newest T-Mobile G2 ROM.
Should the phone be able to install the OTA update, or will I have to replace the bootloader in order to get the OTA update on there? If I do have to replace the bootloader, will that require a full wipe?
James
Completely the same problem with HTC Hero after European OTA update. It has been rooted while ago (by following instructions from this forum) and now after setting up date in the future and confirming update, phone reboot and I get "Android System recovery" screen with menu and this message bellow it:
Build: CyaanogenMod v1.4 + JF
Finding update package ...
Opening update package ...
Veryfing update package ...
E: No signature (218 files)
E: Verification failed
Installation aborted.
Click to expand...
Click to collapse
I have the same problem (I did not write down the message, so I'm not sure which "Build:" was listed) .
The update fails, the phone reboots and then works under the old build. Under "settings/about phone" there is also no info about the update. Can one force the phone to download the update a second time? Would this help?
Bye
Nick
P.S. I'm running the phone in Germany over e-plus as network provider. The updates was done over a WiFi connection. The phone is not branded - was from the free market and not from a provider.
Hey,
got the same problem. At least I could extract the official OTA-update-zip to publish it here (see attachment)
There also is a "recovery.img" in the update zip, so I guess usually the OTA update will kill custom recovery bootloaders. We could replace the "recovery.img" in the zip with a hacked one before applying the update.
However first we should fix the verification error...
P.S.: Also Germany, not branded, Vodafone Network
Does anyone know if I will lose all my data if I reflash the original recovery.img onto my phone?
As I used flashrec to flash ra-recovery.img I keept all my data. So I don't belive you will lost any of your data except of your actual recovery image.
At last, we can try to flash origianl RUU, but with this we lost all our personal data.
----
I tried it. I installed flasrec.apk using ASTRO and used this app to flash the recovery.img from here mentioned/linked OTA update zip. Afterwards I changed date again and was able to install OTA Update without errors and loosing personal data. Now I'm without nandroid because of changing recovery image. Keep cool at this procedure installing these flashes takes long time in boot process - I was really near an hard reset ...
Flashing the original recovery.img should not be a problem.
However, I don't want to lose root access, and thus I will wait for the official HTC 2.1-update (hoping someone publishes it online) and then flash it by myself..
I don't mind losing root access at this moment (the reason I rooted my phone was to get wifi tethering but never got it working with a mac).
Since I am total noob with android stuff, I would highly appreciate some step by step instructions or link where I can find what to do. Thanks guys.
Hi, I've been trying to install the recovery.img from the update but I get this message with flashrec 1.1.3:
Code:
"Flash FAILED: Could not run command."
I'm using WWE 405.66 flashed with ra-recovery img 1.6.2... and the rom is rooted.
What am I doing wrong?
I can't even install ra-recovery with flashrec now and I have installed ra-recovery 1.6.2 this morning (I was using 1.5)
And yes, I know I'm going to lose ra-recovery.
rseffner said:
As I used flashrec to flash ra-recovery.img I keept all my data. So I don't belive you will lost any of your data except of your actual recovery image.
At last, we can try to flash origianl RUU, but with this we lost all our personal data.
----
I tried it. I installed flasrec.apk using ASTRO and used this app to flash the recovery.img from here mentioned/linked OTA update zip. Afterwards I changed date again and was able to install OTA Update without errors and loosing personal data. Now I'm without nandroid because of changing recovery image. Keep cool at this procedure installing these flashes takes long time in boot process - I was really near an hard reset ...
Click to expand...
Click to collapse
What was the rom you were using when you flashed the official recovery?
alvaritolalala said:
Hi, I've been trying to install the recovery.img from the update but I get this message with flashrec 1.1.3:
Code:
"Flash FAILED: Could not run command."
I'm using WWE 405.66 flashed with ra-recovery img 1.6.2... and the rom is rooted.
What am I doing wrong?
I can't even install ra-recovery with flashrec now and I have installed ra-recovery 1.6.2 this morning (I was using 1.5)
And yes, I know I'm going to lose ra-recovery.
Click to expand...
Click to collapse
Try the following:
- Copy the recovery.img to your SD card
- Turn off the phone, turn it on with Buttons "HOME"+"ONOFF" pressed such that the ra-recovery which you already have starts
- connect to your phone by cable using "adb shell"
- Then with root access you can flash the image by typing "flash_image recovery /sdcard/recovery.img"
This should do it
jamesots said:
Hi,
After changing my phone's date into the future, my G2 Touch told me there was an update available, so I told it to go ahead and apply it. When the phone rebooted it came up with this message:
E:No signature (218 files)
E:Verification failed
Installation aborted
I have nandroid installed on the phone. At least I think that's what's installed - I haven't played with any ROM stuff since November I think, when I changed the bootloader (I think - if that's what's giving me the option to do a nandroid backup now) and installed the newest T-Mobile G2 ROM.
Should the phone be able to install the OTA update, or will I have to replace the bootloader in order to get the OTA update on there? If I do have to replace the bootloader, will that require a full wipe?
James
Click to expand...
Click to collapse
hey,
I had same problem
go to All programs--> Recovery Flasher--> Restore backup
then restart and update OTA
Greetings from Zagreb, Croatia
Hey guys.
So, for those of you, who do NOT care about root for now, here's what worked for me:
1.: Download the zip-file with the OTA Update, mentioned on the first page and extract it.
2.: Connect your Hero to your PC and copy the recovery.img from the OTA onto your sdcard. Disconnect from computer.
3.: Boot your phone into the bootloader (Home + PWR).
EDIT: Now connect the phone to the pc again!
4.: open the command prompt of your pc, navigate to your Android SDK folder. (If it is not installed, download it and make sure you've got the needed drivers. Otherwise: Download them, using the Setup.exe from Android SDK)
5.: Here are the needed commands:
Code:
adb shell
$su
mount -a
flash_image recovery /sdcard/recovery.img
6.: reboot your phone after exitting the command prompt.
7.: Factory reset, reboot again
8.: And well, wait for the update-window again and be happy, now it should work
EDIT 2:
Any questions? Just leave a reply
@Revoluzifer
OK I did exactly as you explained, but having problem with su command:
Code:
C:\sdk\tools>adb shell
adb server is out of date. killing...
* daemon started successfully *
/ # su
su
/sbin/sh: su: not found
I know I know, you're going to say my phone is not rooted at all But believe me it was and some apps that require root access are there (screenshot, wifi tether etc.).
I even tried to find su cmd with find:
Code:
C:\sdk\tools>adb shell
adb server is out of date. killing...
* daemon started successfully *
/ # su
su
/sbin/sh: su: not found
But got nothing as you can see.
Ideas?
@dinke:
Which bootloader / recovery console is installed?
Means, what do you see, after booting with Home + PWR?
Also try to input $su instead of just su.
But first tell me your "hack" if any
@Revoluzifer
Thanks for quick reply
I see Android system recovery screen, not sure if this is nandroid or what but have this text on the screen with following options:
Android system recovery <2>
Use trackball to highlight;
click to select.
[Home+Back] reboot system now
[Alt+S] apply sdcard:update.zip
[Alt+W] wipe data/factory reset
[Alt+B] nandroid v2.2 backup
[Alt+R] restore latest backup
[Alt+F] repair ext filesystems
-------------------------------
Click to expand...
Click to collapse
And bellow menu there is build ID:
Build: CyanogenMod v1.4 + JF
I don't remember exact procedure that I applied for rooting hero, but I followed instructions from this forum (I can try by searching for exact thread if that may help you).
Edit: I applied root procedure by following instructions on these two links:
http://forum.xda-developers.com/showpost.php?p=4257045
http://forum.xda-developers.com/showthread.php?t=559613
That sounds just perfect
CyanogenMod 1.4 is exactly the same recovery console i have had before.
(Btw, Hero is not officially supported by CM anymore, had a nice discussion yesterday in cyanogen IRC )
So, try to use $su instead of su, that's what I typed and it all worked just great.
But you definitely first booted into bootload and then connected the phone to your pc again?
Tell me if this worked for you, please...
Greetz,
Sven
dinke said:
Code:
C:\sdk\tools>adb shell
adb server is out of date. killing...
* daemon started successfully *
/ # su
su
/sbin/sh: su: not found
Click to expand...
Click to collapse
Forget about the "su". You are already root.
(You can see this, as there's a '#' in front)
Just do the mounting and flashing
Oh... You're right, nerdture... didn't see the #
I *think* I've tried mount no matter of missing 'su' cmd and it didn't work either but will try again as soon as I manage to find some cable to connect hero with macbook (no longer nearby windows machine but have sdk installed on mac so should be working as well)
Revoluzifer said:
But you definitely first booted into bootload and then connected the phone to your pc again?
Click to expand...
Click to collapse
Yes
I have a quite strange problem on my HTC Hero (GSM).
Quite a while ago I flashed a backup of my stock 2.1 onto the phone because I forgot to titan-backup some apps, but in the process I seemingly somehow broke my recovery mode. Also since that point in time my superuser was ranting I should install an update of the su binary.
Now lately I tried some way to flash to cyanogenmod because of all the bloatware in stock HTC Éclaire. In this process I tried installing clockwork rom manager and titan. clockwork didn't have the rights to install recovery, regardless of the generally working root (universal androot states the device as rooted and at that point superuser worked as it should e.g. for ghost file manager and quikboot). So I googled and found that there was an alternative to superuser called supersu. I installed that after uninstalling superuser and that only gave me errors. Now I seem to have no working su bin, supersu only tells me anything I do fails and superuser gives me the following when trying to update the su bin (translated from German):
Downloading manifest... okay
Analyzing manifest... okay
Latest version = 3.1.1
Checking installed Version = legacy
Repairing database... okay
Unzipping sutools... okay
Checking current install path... /system/xbin/su
Downloading new binary... okay
Aquiring root access...
Remounting /system as rw... legacy
Copying su to /system... okay
Button saying "that was cool, do it again"
Click to expand...
Click to collapse
After that seemed not to work I tried flashing the recovery from fastboot, but that "remote operation" is "not permitted". Same goes for system remount via adb.
This means also, that in the current state I cannot flash a new su via update.zip as I don't have a recovery mode anymore.
Someone on the net suggested to install an OTA-update to fix most system files and reset root. Sadly the following update for my hero is buggy. It's a patch for the peep twitter client that broke my boot partition a couple of times before and every time I had to reset to Android 1.5 again via recovery - so I won't try it as I know I don't have recovery (only the red triangle of death)
Does anyone have any trick up their sleeves that could help restoring either the su bin or the recovery mode?
[edit]
just noticed I wrote a question about the semi-brick from the mentioned peep-update some time ago - including a solution. I will try that later on, but if someone figures something else so I can still backup my data before wiping everything I'd still be thankful for a hint.
[edit2]
I did reset the handset with a 2.1-RUU via hboot, but seemingly the recovery partition is still broken and I could not find a Clockworkmod Rom Manager-version that is a) running on 2.1 and b) actually working on my device to flash recovery and thus achieve anything... But at least I seem to have SU again, even though it is noted as outdated and I am unable to patch it.
I have the LG Power (aka LG Leon) from Tracfone, which has a protected bootloader. KingRoot roots it, but its su binary is not fully compatible with all root apps. Fooling around with KingRoot, I found a way to ultimately root the phone with SuperSU, using KingRoot as a "mule" app to do it.
Warning: As always, you can make your device unusable by attempting to root it. You follow these instructions at your own risk.
Download KingRoot from kingroot.net, install it, and let it do its thing. You may have to try a couple or three times before it gains root.
Install SuperSU from Google Play. Open it and "Cancel" the prompt to update the su binary (it won't work, yet). Configure SuperSU to your preferences, and grant it root permission when KingUser asks.
Install a root browser such as ES File Explorer from Google Play, open it, and enable root access. KingUser should prompt to allow it root.
You will need a copy of the SuperSU su binary. It is not yet in the /system/xbin folder, as KingRoot has control over that. You can get it through ChainFire's site, or from the "root.zip" file attached to this thread: http://forum.xda-developers.com/fir...ne-supersu-t3105546/post60669196#post60669196
Load the mule with the payload. Browse to /data/data/com.kingroot.kinguser using the root browser and REPLACE all instances of "su" with the SuperSU version of the su binary. You will find at least two deeply embedded in the directory tree.
Now wait, possibly for several minutes. KingRoot will eventually check its integrity and find that the installed su binary is different than the one it its data directory. It will reinstall automatically and test its access. If successful, you will see a SuperSU prompt to grant KingRoot superuser access! :victory: Deny it.
Now open SuperSU again and allow it to upgrade the su binary through the "Normal" method. It should succeed.
Restart the device.
Open SuperSU again to test root access. Open a few root apps such as the root explorer. SuperSU should prompt to grant root access.
You can uninstall KingRoot (and Purify, if you want).
Some issues that I ran into that may or may not be of concern to you:
After rooting, my device became unstable and would freeze a few minutes after restarting. I had to take out the battery to restart it. I was messing around a lot with it, so most likely it's something else I did. However, if this happens to you, go into "Safe Mode" by powering it on, waiting for the LG Logo to appear, then holding the "volume down" button until you see the default launcher screen with "Safe Mode" in the lower left corner. Give it many minutes to settle in, then restart normally. This restores a few things to default (such as your widgets, which you will have to re-configure).
SuperSU asked me a second time to update the su binary. I allowed it, and it never asked me again.
If all else fails and you can't get a stable root, install KingRoot again and have it re-root the phone.
FlashFire works on this phone after rooting as above. I was able to successfully flash Xposed to the device.
Don't try to flash TWRP, however. The bootloader is locked and you will lose recovery if you do this. (Yes, I did it.)
this not work on H340n with android 6.0
gsearle5 said:
FlashFire works on this phone after rooting as above. I was able to successfully flash Xposed to the device.
Don't try to flash TWRP, however. The bootloader is locked and you will lose recovery if you do this. (Yes, I did it.)
Click to expand...
Click to collapse
Hey, quick question because I'm still not getting the framework to successfully flash. Which version of the framework did you use specifically?
Corbow6 said:
Hey, quick question because I'm still not getting the framework to successfully flash. Which version of the framework did you use specifically?
Click to expand...
Click to collapse
I flashed version 81. It's working great, so I haven't attempted to upgrade yet.
gsearle5 said:
FlashFire works on this phone after rooting as above. I was able to successfully flash Xposed to the device.
Don't try to flash TWRP, however. The bootloader is locked and you will lose recovery if you do this. (Yes, I did it.)
Click to expand...
Click to collapse
I had the same issue... So after lots of searching I found a stock 5.0.1 recovery for a LG G3 that works. The zip file is NOT flashable but just unzip the recovery.img and flash that with FlashFire. You can then turn off the phone, press & hold vol- & power till the phone vibrates the continue to hold vol- and release then press and hold power again to enter stock recovery.
voluptuary said:
I had the same issue... So after lots of searching I found a stock 5.0.1 recovery for a LG G3 that works. The zip file is NOT flashable but just unzip the recovery.img and flash that with FlashFire. You can then turn off the phone, press & hold vol- & power till the phone vibrates the continue to hold vol- and release then press and hold power again to enter stock recovery.
Click to expand...
Click to collapse
Thank you! I'll try it out. What do I have to lose, recovery?
gsearle5 said:
I flashed version 81. It's working great, so I haven't attempted to upgrade yet.
Click to expand...
Click to collapse
I just updated to version 86 without a hitch.
Looks like I celebrated too soon, while you can enter recovery with the IMG I posted above it won't actually do anything... except make you have to pull the battery out. Least you don't get an error in the top left corner anymore so there's that.
Just installed the new Xposed Framework self-installer for Lollipop on this device (LG Power). It worked flawlessly.
http://forum.xda-developers.com/showthread.php?t=3034811
Hello
If you have already downloaded the updates packages, you don't need to redownload them via "System update"
Just copy them to Internal storage and follow the video
(In my case I need "update.zip" and "update_data_full_public.zip" and "update_full_VIE-L29_hw_meafnaf.zip")
https://www.youtube.com/watch?v=z4nOXgsic1o
I have all the three files, but in my case the "System Update" option on the settings just not appear. How should I procceed?
Kempf said:
I have all the three files, but in my case the "System Update" option on the settings just not appear. How should I procceed?
Click to expand...
Click to collapse
same question
what is your model VIE-???C???B???
xzanium said:
what is your model vie-???c???b???
Click to expand...
Click to collapse
vie-l29c636b370
The same as mine, lol. VIE-L29C636 running B370.
I've tried most of Firmware Finder's compatible versions B382, B384, but none of them work (through deload folder and 'forced' update).
The only one which works is the 81131 (VIE-L29C636B370).
have you tried to search in setting
also check in Setting -> Apps if they are the "System update" apps
I got b384 on system update ota
I search in setting "system update" appear but its not work, in setting->apps not appear
I'm not sure, but I think that when you have update to B370, the additional pack have not been installed.
try to download this pack update_full_hw_spcseas.zip and flash it with twrp
xzanium said:
I'm not sure, but I think that when you have update to B370, the additional pack have not been installed.
try to download this pack update_full_hw_spcseas.zip and flash it with twrp
Click to expand...
Click to collapse
i flash this in TWRP and now i cant boot to device, please help me
I downloaded rom b384 to copy to internal storage and install by twrp but not, is there any way to install rom from twrp
@vurobben, as long as I know and read about, there's no way to install it unless trough the System Update.
If your mobile is not booting, you've to download the version that allow you to update trough dload folder (in my case, the only one which do this is the 81131 - VIE-L29C636B370). Then, you've to install via TWRP the files that @xzanium said.
In my case, I'll try to do it at night. I've tried to locate the Update on the settings, and also in the apps.
And now my phone no os, i just boot in twrp recovery. Can you make a backup file in twrp and up to google drive?
sorry, my phone is VIE-L29C185
to fix your problem you must download the rollback package(C900B300) and firmware package (C636B190) from this page : http://consumer.huawei.com/kh/support/downloads/index.htm
(search for Keyword "P9 plus")
then install rollback package via 3 buttons methode (vol+ , vol- , power)
then the B190 package
I'll try to updload the files tonight.
I'm trying to do this rollback. Acually I did not know how to do it. I'll try the way @xzanium mentioned.
just extract teh zip file, then copy the dload folder to sd card
shutdown the phone
press all 3 buttons
It kind of did the trick. Now the Build Number is VIE-L19C900B300, but the EMUI is still 5.0 and Android 7.0 (Nougat). I think it'll solve @vurobben boot looping problem.
But.. the System Update option still not appear, and the clock does not work also
I'll keep trying.
Now I'm going to update for 370 (dload), then install TWRP and flash these ZIP files: 1)update_data_full_hw_spcseas, 2) update_data_full_public and 3) update_full_hw_spcseas.
[edit]
Mine is not woking anymore..
I've tried to flash the 'update_data_full_hw_spcseas', but it's in a bootloopping also. Tried to roolback again, but didn't work this time.
Now it enters in Huawei eRecovery, try to get the recovery from the server but fails..
[edit2]
I've installed the Rollback (dload), then I've downloaded the "HUAWEI P9 Plus Firmware (VIE-L29, Android6.0, EMUI4.1.1, C636B190, Thailand, Cambodia, Nonspecific)" on the same site that @xzanium mentioned and installed just after the rollback. Everithing is working now.
I've just checked and I'm on EMUI 4.1.1, Androind 6 (M) and Build VIE-L29C636B190. The goodnews is that the "System Update" is workind now. Tomorrow I'll try to update to Androin N and get everithing fine there also.
Thanks for the help.
Kempf said:
It kind of did the trick. Now the Build Number is VIE-L19C900B300, but the EMUI is still 5.0 and Android 7.0 (Nougat). I think it'll solve @vurobben boot looping problem.
But.. the System Update option still not appear, and the clock does not work also
I'll keep trying.
Now I'm going to update for 370 (dload), then install TWRP and flash these ZIP files: 1)update_data_full_hw_spcseas, 2) update_data_full_public and 3) update_full_hw_spcseas.
[edit]
Mine is not woking anymore..
I've tried to flash the 'update_data_full_hw_spcseas', but it's in a bootloopping also. Tried to roolback again, but didn't work this time.
Now it enters in Huawei eRecovery, try to get the recovery from the server but fails..
[edit2]
I've installed the Rollback (dload), then I've downloaded the "HUAWEI P9 Plus Firmware (VIE-L29, Android6.0, EMUI4.1.1, C636B190, Thailand, Cambodia, Nonspecific)" on the same site that @xzanium mentioned and installed just after the rollback. Everithing is working now.
I've just checked and I'm on EMUI 4.1.1, Androind 6 (M) and Build VIE-L29C636B190. The goodnews is that the "System Update" is workind now. Tomorrow I'll try to update to Androin N and get everithing fine there also.
Thanks for the help.
Click to expand...
Click to collapse
when rollback bootloader unlock or relock?
I could not verify yet, but I thing it does lock the bootloader again, because the bootloader option is enable under the developer settings again.
I never post for help, but I am at my wits end.
I have a Vodafone tablet that's running 6.0 marshmallow that refuses to root. I did find a TWRP recovery compiled for the device, which I installed using SP Flash Tool.
TWRP seems to work as expected. I can make and restore backups, format partitions, mount system, delete files with the file manager and so on.
TWRP is also kept on every reboot. It never replaced by the stock recovery.
However, when I try and install the SuperSU zip 2.82 to root the device, it seems to be successful. However, when I boot into Android and open the SuperSU app, it says,"SU binary occupied" and closes.
That error is displayed when installing 2.82. When installing versions like 2.79, it shows the option to install the SU binary, again like normal, but it always fails to install the binary.
Using a root checker app from FDroid tells me the same thing, that root isn't avaliable. TWRP flashing should be working though, since I can flash busybox and it is detected correctly by the same root checker app.
Other root apps refuse to work.
Whilst in TWRP, I am able to browse the file system and the su file is located in system/xbin, again like it should be. Numerous other files from busybox are also located there, further signalling a successful flash. I can chmod 755 the su file without issue, but it doesn't fix anything.
The bootloader of the tablet is unknown to me. I can't boot into fastboot or bootloader mode. Trying to do so just reboots the tablet. Nothing is shown on the screen either, and it boots to Android again. I did enable ,"OEM Unlocking" in developer options.
Any ideas what I can do? I really want to give this device a thorough chance, since it is a surprisingly enjoyable device to use, and for the price I paid it's almost a total no-brainer.
I just want root so it can become a total no-brainer to own.
Thank you for your time.
I figured it out.
I tried installing Magisk by patching the boot.img within the app and flashing it via SP Flash Tool, and it worked perfectly.
I never thought of using that, but I am glad that I did.
So, yeah. Use Magisk.