Hello,
I have rooted my Honor7 with Kingoroot. Now I want to unroot it to do OTA Updates.
Unroot with Kingoroot is failing and the Support is not answering.
I tried with Honor Multi Tool and flashing stock recovery (.IMG) , but as soon as I want to flash Recovery this is printed out: FAILED (remote: Command not allowed)
I have already checked bootloader and there is written "Phone unlocked"
So what's the Problem?
Regards,
Christian
Qhris said:
Hello,
I have rooted my Honor7 with Kingoroot. Now I want to unroot it to do OTA Updates.
Unroot with Kingoroot is failing and the Support is not answering.
I tried with Honor Multi Tool and flashing stock recovery (.IMG) , but as soon as I want to flash Recovery this is printed out: FAILED (remote: Command not allowed)
I have already checked bootloader and there is written "Phone unlocked"
So what's the Problem?
Regards,
Christian
Click to expand...
Click to collapse
There´s an option inside Kingroot to uninstall. I can't remember the steps to get there, but you can't just uninstall the app.
The other options would be flash system.img or factory reset after backing up the relevant data with Huawei backup native app.
I was struggling a bit with Kingroot unroot too, but after I restarted Honor it just worked out. Just use option in menu of Kingroot to uninstall. First time during unroot I got error or it just froze for a moment and nothing hapenned.
And just FYI even you remove Kingroot, you have to reflash completely your FW by local update otherwise OTA won´t work because system partition was changed by Kingroot.
Go to Settings>Root Authorization Settings>Remove Root permission. Select OK for the next screens (it will take some time) and check if app was uninstalled. If not, do it.
Reboot the phone and you´re done.
Ing.King said:
I was struggling a bit with Kingroot unroot too, but after I restarted Honor it just worked out. Just use option in menu of Kingroot to uninstall. First time during unroot I got error or it just froze for a moment and nothing hapenned.
And just FYI even you remove Kingroot, you have to reflash completely your FW by local update otherwise OTA won´t work because system partition was changed by Kingroot.
Click to expand...
Click to collapse
I have restarted the device many times. Everytime the unroot with the computer software is failing...
One question regarding kingroot. I am not able to remember, that I need to unlock the bootloader over huawei. Is this possible?
zinko_pt said:
Go to Settings>Root Authorization Settings>Remove Root permission. Select OK for the next screens (it will take some time) and check if app was uninstalled. If not, do it.
Reboot the phone and you´re done.
Click to expand...
Click to collapse
What APP do you mean? There is an app named "Kingo Link", but this app does not have any Settings.
The other was SuperSU#. I have done there the unroot option and deinstalled the app, but the device is still rooted. (Checked with Root Checker Basic)
I suppose you used kingroot installed in your phone.
Ah ok. No I used the pc program (https://www.kingoapp.com/)
If you didn't modified your system other than rooting it, I suggest you to flash system.img from Stock Firmware you were using previously.
DigiGoon said:
If you didn't modified your system other than rooting it, I suggest you to flash system.img from Stock Firmware you were using previously.
Click to expand...
Click to collapse
Already tried....
"I tried with Honor Multi Tool and flashing stock recovery (.IMG) , but as soon as I want to flash Recovery this is printed out: FAILED (remote: Command not allowed)"
Is it possible to do the update without removing the root?
Qhris said:
Already tried....
"I tried with Honor Multi Tool and flashing stock recovery (.IMG) , but as soon as I want to flash Recovery this is printed out: FAILED (remote: Command not allowed)"
Is it possible to do the update without removing the root?
Click to expand...
Click to collapse
Nope, the install will fail everytime if the system is modified, but in some cases it is reported that, by doing this process multiplte times it actually passes through regardless the rooted system.
So keep trying, and that error occurs when you have a Locked Bootloader, did you checked if its not in any way relocked?
Qhris said:
Already tried....
"I tried with Honor Multi Tool and flashing stock recovery (.IMG) , but as soon as I want to flash Recovery this is printed out: FAILED (remote: Command not allowed)"
Is it possible to do the update without removing the root?
Click to expand...
Click to collapse
Modified partition, so no.
I would go with the PC app side and try a uninstall.
If it doesn't work, then a manual fastboot flash of the boot.img, recovery.img, system.img, by this order. If not with current Bxxx version, go back to B100.
As a rule of thumb I never use Kingroot as it sticks like a chewed bubble gum.
DigiGoon said:
Nope, the install will fail everytime if the system is modified, but in some cases it is reported that, by doing this process multiplte times it actually passes through regardless the rooted system.
So keep trying, and that error occurs when you have a Locked Bootloader, did you checked if its not in any way relocked?
Click to expand...
Click to collapse
How i could check, if my bootloader is relocked? The multi tool check says it's unlocked...
To boot into bootloader mode follow these steps:
Switch off your device.
Press and hold Vol DOWN button.
While pressing and holding it, connect your device to PC.
Once in bootloader mode you'll get text on the screen like:
Phone Locked - If your bootloader is locked.
Phone Unlocked - If your bootloader is unlocked.
Phone Relocked - If your bootloader is relocked after once doing an unlock.
Report back after checking.
Good News. I removed root with the king app, but flashing is not working:
C:\Users\Chris\Desktop\HONOR_MultiTool\Files>fastboot flash system SYSTEM.img
target reported max download size of 471859200 bytes
sending sparse 'system' (459682 KB)...
OKAY [ 10.279s]
writing 'system'...
FAILED (remote: Command not allowed)
finished. total time: 10.283s
C:\Users\Chris\Desktop\HONOR_MultiTool\Files>fastboot flash system SYSTEM.img
target reported max download size of 471859200 bytes
sending sparse 'system' (459682 KB)...
OKAY [ 10.244s]
writing 'system'...
FAILED (remote: Command not allowed)
finished. total time: 10.247s
I have checked bootloader like DigiGoon said and there is written "Phone Unlocked"... Wtf? ..
Qhris said:
Good News. I removed root with the king app, but flashing is not working:
C:\Users\Chris\Desktop\HONOR_MultiTool\Files>fastboot flash system SYSTEM.img
target reported max download size of 471859200 bytes
sending sparse 'system' (459682 KB)...
OKAY [ 10.279s]
writing 'system'...
FAILED (remote: Command not allowed)
finished. total time: 10.283s
C:\Users\Chris\Desktop\HONOR_MultiTool\Files>fastboot flash system SYSTEM.img
target reported max download size of 471859200 bytes
sending sparse 'system' (459682 KB)...
OKAY [ 10.244s]
writing 'system'...
FAILED (remote: Command not allowed)
finished. total time: 10.247s
I have checked bootloader like DigiGoon said and there is written "Phone Unlocked"... Wtf? ..
Click to expand...
Click to collapse
Have you tried with B100?
zinko_pt said:
Have you tried with B100?
Click to expand...
Click to collapse
Yes, this was system.img from "PLK-L01C432B100 Upgrade Software UK"
zinko_pt said:
Have you tried with B100?
Click to expand...
Click to collapse
No, flash the boot.img from current Bxxx version.
zinko_pt said:
No, flash the boot.img from current Bxxx version.
Click to expand...
Click to collapse
It must be the current boot.img? I am not able to find any for B180...
Qhris said:
It must be the current boot.img? I am not able to find any for B180...
Click to expand...
Click to collapse
Yes, use this full B180 https://www.androidfilehost.com/?w=files&flid=102830
@Qhris Try to update your ADB & Fastboot drivers, it seems like the drivers are outdated.
Use the latest SDK from Google.
Related
Hi,
I followed this article -> phandroid DOT com/2014/11/05/how-to-root-nexus-9/ (Sorry, new account, can't link) to the letter, and everything seemed to go well, until the last step where I ran "fastboot reboot" which returned "error: device not found" I thought nothing of this as there was a reboot option on the devices screen, so I rebooted, I get the google logo, followed by the four orbs, then it says "Optimising app x of 99" once this is done, its back to the orbs again and it just repeats.
I tried restoring to factory defaults from the recovery menu, that did nothing, then sometime after I noticed I actually cant turn the device off any more, if I hold the power button it turns off, but reboots instantly. I tried going through the steps again, but no luck, the only change was that I didn't have the error at the end, and the first Optimising dialogue said 104 apps, not 99, but all the rest afterwards have said 99.
I'm not sure what do do from here, any advice?
Here's my cmd output:
Code:
## First attempt ##
C:\Development\Android\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>adb
reboot bootloader
C:\Development\Android\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>fas
tboot oem unlock
...
(bootloader) ability is 1
(bootloader) RUU_frame_buffer_enable_flag=0
(bootloader) Start Verify: 0
(bootloader) [hboot query] query 24 is not implemented
(bootloader) [hboot query] query 24 is not implemented
(bootloader) Start Verify: 0
(bootloader) [hboot query] query 24 is not implemented
(bootloader) [hboot query] query 24 is not implemented
(bootloader) Unlock device successfully!
OKAY [ 23.489s]
finished. total time: 23.489s
C:\Development\Android\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>fas
tboot boot inject.img
cannot load 'inject.img': No such file or directory
C:\Development\Android\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>fas
tboot boot nexus9\inject.img
downloading 'boot.img'...
OKAY [ 0.783s]
booting...
OKAY [ 0.156s]
finished. total time: 0.939s
C:\Development\Android\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>fas
tboot flash boot nexus9\patched.img
target reported max download size of 518205818 bytes
sending 'boot' (7830 KB)...
OKAY [ 0.541s]
writing 'boot'...
(bootloader) Device State : Unlocked
OKAY [ 0.798s]
finished. total time: 1.339s
C:\Development\Android\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>adb
reboot
error: device not found
C:\Development\Android\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>adb
reboot
error: device not found
## Second attempt ##
C:\Development\Android\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>fas
tboot oem unlock
< waiting for device >
...
(bootloader) ability is 1
(bootloader) Device stete is unlock already
OKAY [ 0.141s]
finished. total time: 0.141s
C:\Development\Android\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>fas
tboot boot inject.img
cannot load 'inject.img': No such file or directory
C:\Development\Android\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>fas
tboot boot inject.img
downloading 'boot.img'...
OKAY [ 0.749s]
booting...
OKAY [ 0.158s]
finished. total time: 0.908s
C:\Development\Android\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>fas
tboot flash boot patched.img
target reported max download size of 518205818 bytes
sending 'boot' (7830 KB)...
OKAY [ 0.539s]
writing 'boot'...
(bootloader) Device State : Unlocked
OKAY [ 0.787s]
finished. total time: 1.326s
C:\Development\Android\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>fas
tboot reboot
rebooting...
finished. total time: 0.066s
C:\Development\Android\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>
Try returning to stock and trying again. See method 2 of this, http://forum.xda-developers.com/showthread.php?p=58956577
Sent from my Nexus 9 using XDA Free mobile app
That root method is for the old 5.0 Android; it doesn't work anymore with 5.1.1. Go back to stock using jd1639's link, then run Chainfire's Auto-root and you should be good to go. Link is here: https://download.chainfire.eu/595/CF-Root/CF-Auto-Root/CF-Auto-Root-flounder-volantis-nexus9.zip. There's supposedly an update coming in the next week or so to fix the stagefright vulnerability, make sure you do NOT take it in case it does weird things that could cause you to lose root.
(I know it says Volantis and not flounder but the Nexus 9 is known by both names, just to keep things confusing)
Thanks guys, root is now all working
Had a strange way of getting there though, I went back to stock, then tried the auto root as mentioned, but I had the same problem again, so I re-flashed just the boot.img file from stock, powered up, and lo and behold, root working fine
TheShryke said:
Thanks guys, root is now all working
Had a strange way of getting there though, I went back to stock, then tried the auto root as mentioned, but I had the same problem again, so I re-flashed just the boot.img file from stock, powered up, and lo and behold, root working fine
Click to expand...
Click to collapse
Your better off doing the bootloader unlock, then flashing TWRP recovery, then flashing supersu. IMO using autoroot methods make no sense. You now have no recovery and if anything goes wrong you have to flash all of the factory images again. And what if you want to use a custom rom? I would highly recommend getting TWRP at http://twrp.me and flashing it. Then you can actually make full backups in case of disaster. Good luck!
bynarie said:
Your better off doing the bootloader unlock, then flashing TWRP recovery, then flashing supersu. IMO using autoroot methods make no sense. You now have no recovery and if anything goes wrong you have to flash all of the factory images again. And what if you want to use a custom rom? I would highly recommend getting TWRP at http://twrp.me and flashing it. Then you can actually make full backups in case of disaster. Good luck!
Click to expand...
Click to collapse
i'll try your TWRP method once i get my LTE version 32gb
link to bootloader unlock method? thx
which version do i use here?
https://dl.twrp.me/flounder/
cobyman7035 said:
i'll try your TWRP method once i get my LTE version 32gb
link to bootloader unlock method? thx
which version do i use here?
https://dl.twrp.me/flounder/
Click to expand...
Click to collapse
Hey, to unlock bootloader you enable developer settings in android, check the "enable oem unlock" switch, boot the device into fastboot mode "adb reboot fastboot" and issue "fastboot oem unlock". This is assuming you have adb and fastboot in your path/working folder. Then, download the lastest twrp - flounder-2.8.7.0.img - and "fastboot flash recovery flounder-2.8.7.0.img". The flounder version of twrp works for both LTE and WIFI variants. If you need any more assistance just let me know.
cobyman7035 said:
i'll try your TWRP method once i get my LTE version 32gb
link to bootloader unlock method? thx
which version do i use here?
https://dl.twrp.me/flounder/
Click to expand...
Click to collapse
bynarie said:
Hey, to unlock bootloader you enable developer settings in android, check the "enable oem unlock" switch, boot the device into fastboot mode "adb reboot fastboot" and issue "fastboot oem unlock". This is assuming you have adb and fastboot in your path/working folder. Then, download the lastest twrp - flounder-2.8.7.0.img - and "fastboot flash recovery flounder-2.8.7.0.img". The flounder version of twrp works for both LTE and WIFI variants. If you need any more assistance just let me know.
Click to expand...
Click to collapse
Just take notice that this will wipe everything on your device, so make a backup first.
dictionary said:
Just take notice that this will wipe everything on your device, so make a backup first.
Click to expand...
Click to collapse
cobyman7035 said:
...
Click to expand...
Click to collapse
Yes, my apologies... I forgot to mention this. You will definitely want to pull any pictures or other files you might want to keep from the /sdcard partition. Or anything else because ALL DATA WILL BE WIPED.
thx. where do i dload the latest SU chainfire? after i flash twrp, then flash SU? do i need to wipe dalvik or cache?
im installing that huge android SDK studio setup into my laptop for prep
cobyman7035 said:
thx. where do i dload the latest SU chainfire? after i flash twrp, then flash SU?
Click to expand...
Click to collapse
Here > https://download.chainfire.eu/740/SuperSU/BETA-SuperSU-v2.49.zip
ok i just unlocked my bootloader....so i rebooted in android again...i have to go back and enable usb debugging and developers again?
---------- Post added at 10:16 AM ---------- Previous post was at 10:01 AM ----------
when i typ adb reboot fastboot. ...my n9 reboots into the android o.s and NOT into fastboot?
---------- Post added at 10:23 AM ---------- Previous post was at 10:16 AM ----------
nm i installed and flash twrp and SU! i didn't do a dalvik cache wipe...is that ok? booting in android o/s again to setup!
my next step is to go unencrypted... don't wanna setup too many apps cuz its just gonna be all deleted again
Hello everyone. I had TWRP installed on my Mate 2. There was some update a few months ago and now I can no longer boot into TWRP. All I get is the stock recovery. ADB install of TWRP always reports successful (OKAY [ 0.797s]). Graphical installation always fails however ("Something is wrong" error).
Has anyone been through this? Nothing I do seems to get me back to being able to use TWRM.
Ascend Mate 2 running B147 rooted and unlocked from Consumer Cellular.
Bill R said:
Hello everyone. I had TWRP installed on my Mate 2. There was some update a few months ago and now I can no longer boot into TWRP. All I get is the stock recovery. ADB install of TWRP always reports successful (OKAY [ 0.797s]). Graphical installation always fails however ("Something is wrong" error).
Has anyone been through this? Nothing I do seems to get me back to being able to use TWRM.
Ascend Mate 2 running B147 rooted and unlocked from Consumer Cellular.
Click to expand...
Click to collapse
There is numerous posts that walk you through it. General and question threads.
Moody66 said:
There is numerous posts that walk you through it. General and question threads.
Click to expand...
Click to collapse
Agreed, there are, and I have been through and tried many including:
Downloading TWRP Manager and install from there
Down;load Flashify and install fropm there
Install via ADB Fastboot
Copying image to SD card and flashing from there
Copying update to SD card and flashing from there
None has worked. I'mk thinking the one and only update I received changed the boot partition or something.
Bill R said:
Agreed, there are, and I have been through and tried many including:
Downloading TWRP Manager and install from there
Down;load Flashify and install fropm there
Install via ADB Fastboot
Copying image to SD card and flashing from there
Copying update to SD card and flashing from there
None has worked. I'mk thinking the one and only update I received changed the boot partition or something.
Click to expand...
Click to collapse
147 is what I had. http://forum.xda-developers.com/ascend-mate2/general/guide-cc-variant-to-oem-convertion-t3149767
I have tried that particular one as well. It appears to install but when I go into recovery I get the stock recovery.
C:\adb>fastboot flash recovery twrp.img
target reported max download size of 1073741824 bytes
sending 'recovery' (14382 KB)...
OKAY [ 0.469s]
writing 'recovery'...
OKAY [ 0.438s]
finished. total time: 0.922s
Bill R said:
I have tried that particular one as well. It appears to install but when I go into recovery I get the stock recovery.
C:\adb>fastboot flash recovery twrp.img
target reported max download size of 1073741824 bytes
sending 'recovery' (14382 KB)...
OKAY [ 0.469s]
writing 'recovery'...
OKAY [ 0.438s]
finished. total time: 0.922s
Click to expand...
Click to collapse
Download quick boot from play store and try rebooting into recovery.
If that doesn't work try this.
http://forum.xda-developers.com/ascend-mate2/general/root-b321-t3182399
fastboot boot TWRP.img (with your phone still connected to PC)
Sent from my MT2L03 using XDA Free mobile app
Moody66 said:
Download quick boot from play store and try rebooting into recovery.
If that doesn't work try this.
http://forum.xda-developers.com/ascend-mate2/general/root-b321-t3182399
Click to expand...
Click to collapse
You are a life saver! Your link led me to this which fixed my issue.
http://forum.xda-developers.com/showpost.php?p=62380283&postcount=754
Renamed update.app to update.appx and rebooted to recovery. Thank you again very much!
Bill R said:
You are a life saver! Your link led me to this which fixed my issue.
http://forum.xda-developers.com/showpost.php?p=62380283&postcount=754
Renamed update.app to update.appx and rebooted to recovery. Thank you again very much!
Click to expand...
Click to collapse
You are welcome. It was Xordos that figured it out.
After fumbling with install twrp in order to change over to CM13 from stock, I somehow managed to install the original recovery wrong as well as completely boning the OS. Because of this, on boot, all that shows is the honor screen continuously. Of course the obvious answer to this is to reinstall twrp and restore one of my recovery files. Unfortunately trying to flash twrp through fastboot results in an "FAILED (data transfer failure (Unknown error))". Any suggestions? I can't access the phones internal storage nor the SD card either when I plug it into my PC.
Only one solution, flash a stock firmware using a PC.
PalakMi said:
Only one solution, flash a stock firmware using a PC.
Click to expand...
Click to collapse
How would I go about doing this? I would really love to get my honor working again. Would it just be using fastboot to flash the firmware?
I'd be worried about that error you're getting. It's strange.
Have you considered trying to flash stock recovery? You can extract the recovery image file from the official website update download. Or use the repository.
Or have you tried flashing a different version of TWRP recovery? Here's the official website.
Dueter1um said:
How would I go about doing this? I would really love to get my honor working again. Would it just be using fastboot to flash the firmware?
Click to expand...
Click to collapse
I don't think only fastboot is enough, but take a look at the link provided by JT-on
JT-on said:
I'd be worried about that error you're getting. It's strange.
Have you considered trying to flash stock recovery? You can extract the recovery image file from the official website update download. Or use the repository.
Or have you tried flashing a different version of TWRP recovery? Here's the official website.
Click to expand...
Click to collapse
Luckily, after trying to reflash the twrp with a different version like you suggested, there was no error message and it was completed successfully! Currently restoring as I type this. Don't know how to upload an image so text should do
C:\Users\zakpw\Desktop\Honor 5x rooting>fastboot flash recovery twrp-3.0.2-0-kiwi.img
target reported max download size of 266338304 bytes
sending 'recovery' (45202 KB)...
OKAY [ 1.423s]
writing 'recovery'...
OKAY [ 0.694s]
finished. total time: 2.121s
Dueter1um said:
Luckily, after trying to reflash the twrp with a different version like you suggested, there was no error message and it was completed successfully! Currently restoring as I type this. Don't know how to upload an image so text should do
C:\Users\zakpw\Desktop\Honor 5x rooting>fastboot flash recovery twrp-3.0.2-0-kiwi.img
target reported max download size of 266338304 bytes
sending 'recovery' (45202 KB)...
OKAY [ 1.423s]
writing 'recovery'...
OKAY [ 0.694s]
finished. total time: 2.121s
Click to expand...
Click to collapse
Happy for you, next time be careful
I got this same error, had to use different USB cable and different USB port.
Everytime I type the command 'fastboot oem unlock', the screen says;
OKAY [ 0.002s]
finished. total time: 0.002s
but then when I want to flash a recovery it says;
target reported max download size of 1073741824 bytes
sending 'recovery' (15482 KB)...
OKAY [ 0.498s]
writing 'recovery'...
FAILED (remote: Device not unlocked cannot flash or erase)<<< Why does this happen? -_-
finished. total time: 0.501s
Anybody has a solution for this?
Have you tried just flashing stock recovery? Does it say that for everything you try and flash? A lot of people are trying these shortcuts to try and upgrade bootloader. Though most can work the safest bet is to flash original stock recovery and upgrade from there. You might be looking at going through the hard brick guide.
seems like you locked the bootloader while you are rooted...iam stack on same step too...
Exodusche said:
Have you tried just flashing stock recovery? Does it say that for everything you try and flash? A lot of people are trying these shortcuts to try and upgrade bootloader. Though most can work the safest bet is to flash original stock recovery and upgrade from there. You might be looking at going through the hard brick guide.
Click to expand...
Click to collapse
But everything else works. And yeah, I did try flashing the stock recovery too
Fastboot oem unlock>fastboot reboot>doesn't ask about wiping
I've followed every tutorial they all say that after requesting oem unlock, you can verify the unlock was successful with fastboot oem devices-info> device tampered-false, device unlock-true, then fastboot reboot> system reboot, but it does NOT ask to wipe the data. Am I missing something?
Ubuntu_noobi said:
I've followed every tutorial they all say that after requesting oem unlock, you can verify the unlock was successful with fastboot oem devices-info> device tampered-false, device unlock-true, then fastboot reboot> system reboot, but it does NOT ask to wipe the data. Am I missing something?
Click to expand...
Click to collapse
Not necessarly.
If it 's device unlock-true , you're OK. If not...
Hi~
My phone is huawei honor 7.
Fist, I'm sure I have unlocked my bootloader.
I upgrade to B388 today by fastboot flash cust.img and boot.img and system.img which extract from huawei's official update.app.
Then the phone reboot and I leaved for a while, but when I come back, I found it has replace my twrp by official recovery.
So I just reset my phone and wipe cache. When I reboot to system, I receive an OTA update, and I choose "Download latest full package" then the phone finish update by itself. So my phone now running EMUI 4.0.3 B389.
Finally, I enter fastboot model by "adb reboot bootloader" and try to flash twrp, it tell me:
Code:
PS E:\Root\platform-tools> fastboot flash recovery E:\Root\twrp.img
target reported max download size of 471859200 bytes
sending 'recovery' (25890 KB)...
OKAY [ 0.563s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.570s
I try to flash some old version system, but I got same error. But I type " fastboot oem get-bootinfo" It shows that I was unlocked.
So how can I flash twrp again and Root my phone?
--------------------------
By the way, I found I even can not relock my oem by now!
Code:
C:\Users\omicron3069>fastboot oem relock 23**********9971
...
FAILED (remote: stat not match)
finished. total time: 0.000s
C:\Users\omicron3069>fastboot reboot
rebooting...
finished. total time: 0.125s
hmmmm... solve this weird problem by turn on "unknown source " switch in security setting.
I have the same problem. After B396 update I can not load anything in bootloader mode. I also get a "Software Install Failed" error when I try to return to an older version using dload or update.zip.
Edit: My bootloader is unlocked but i can't relock or unlock it again.
How can i solve this problem? Please someone help me!
alperenadalar said:
I have the same problem. After B396 update I can not load anything in bootloader mode. I also get a "Software Install Failed" error when I try to return to an older version using dload or update.zip.
Edit: My bootloader is unlocked but i can't relock or unlock it again.
How can i solve this problem? Please someone help me!
Click to expand...
Click to collapse
1. If you want to downgrade your firmware version, you need flash a downgrade package first by use dload method. Generally, you can find this kind of package in huawei hiclub ROM thread.
This is Chinese hiclub (club.huawei.com/thread-7268260-1-2.html) that contain this kind of package.
2. I solve this problem by open that unknown source switch . If you don't know where it is, just search it in settings.
3. I know a tool named HiSuit, which may can help you to downgrade your system.
4. Also, make sure you have turn off that f**ing "Phone Finder"!! This is just a s**t made by huawei!!
Hope those can help you~
omicron3069 said:
1. If you want to downgrade your firmware version, you need flash a downgrade package first by use dload method. Generally, you can find this kind of package in huawei hiclub ROM thread.
This is Chinese hiclub (club.huawei.com/thread-7268260-1-2.html) that contain this kind of package.
2. I solve this problem by open that unknown source switch . If you don't know where it is, just search it in settings.
3. I know a tool named HiSuit, which may can help you to downgrade your system.
4. Also, make sure you have turn off that f**ing "Phone Finder"!! This is just a s**t made by huawei!!
Hope those can help you~
Click to expand...
Click to collapse
I will try downgrade package. I already turn on unknown sources and disbled phone finder but still i can't flash any firmware nor image via fastboot or recovery.
alperenadalar said:
I will try downgrade package. I already turn on unknown sources and disbled phone finder but still i can't flash any firmware nor image via fastboot or recovery.
Click to expand...
Click to collapse
Have you wiped system? That could be the error that twrp gives.
Edit: Don't forget to make a backup of system and data!
Even if the bootloader screen says that the phone is unlocked, in reality it isn't and that's why you are getting the command not allowed text. Just type fastboot oem unlock and your code to unlock it again. The same problem is present on many Huawei phones like the P8 and P9 Lite I've tested after installing an update.
if you want to emui4.0 to 3.0 it was impossible
HUAWEI big chrysanthemum and foolish engineer doesnt want you to flash emui3.0 But you can use the hisuite to demotion.I hope reply is very useful to you