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
Related
Hi all,
I have a small problem, my phone does not boot and hanging on Logo. Now i can boot to fastboot menu, but i cannot really use it since i have FRP lock . Is there any chance to baypass it to make possible to flash recovery boot.img ?
When i try any command getting this error :
Code:
target reported max download size of 266338304 bytes
sending 'revocery' (4096 KB)...
OKAY [ 0.142s]
writing 'revocery'...
FAILED (remote: Necessary to unlock FRP! Navigate to Settings > Develope
finished. total time: 0.154s
Since my phone not booting i cannot use this option Please help
Hi, back again
As i can see, try not to mess with the names :revocery...
When you want to flash the boot.img don't change that name.
Just flash it like : fastboot flash boot boot.img
Use my last boot.img which i sent you. That's a good one out of my backup.
For the FRP (perhaps edit your thread tiltle ) i have no answer in a minute. Did the "fastboot oem unlock" gave anything better ?
raystef66 said:
Hi, back again
As i can see, try not to mess with the names :revocery...
When you want to flash the boot.img don't change that name.
Just flash it like : fastboot flash boot boot.img
Use my last boot.img which i sent you. That's a good one out of my backup.
For the FRP (perhaps edit your thread tiltle ) i have no answer in a minute. Did the "fastboot oem unlock" gave anything better ?
Click to expand...
Click to collapse
I have try also boot , try everything, not matter if youhave FRP lock fastboot oem unlock is only to unlock bootloader, which i have, that is not a problem.
See if this method works for you
http://forum.xda-developers.com/showthread.php?t=3261846
Sent from my Nexus 6 using Tapatalk
joyrida12 said:
See if this method works for you
http://forum.xda-developers.com/showthread.php?t=3261846
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
You cannot use this method since i have only FastBoot feature, adb is not possible to use, since phone never boot. This method can be used only for phones what can boot correctly, so unfortunately useless for me. but thx for link
michalss said:
You cannot use this method since i have only FastBoot feature, adb is not possible to use, since phone never boot. This method can be used only for phones what can boot correctly, so unfortunately useless for me. but thx for link
Click to expand...
Click to collapse
i have exactly the same problem. FRP is locked but my phone doenst boot. so how can i unlock the frp with the fastboot mode?
stiggu said:
i have exactly the same problem. FRP is locked but my phone doenst boot. so how can i unlock the frp with the fastboot mode?
Click to expand...
Click to collapse
same problem on my mate s
good to know that adb is not working for others
i thaught it was just me
I've the same problem , any idea ??
michalss said:
Hi all,
I have a small problem, my phone does not boot and hanging on Logo. Now i can boot to fastboot menu, but i cannot really use it since i have FRP lock . Is there any chance to baypass it to make possible to flash recovery boot.img ?
When i try any command getting this error :
Code:
target reported max download size of 266338304 bytes
sending 'revocery' (4096 KB)...
OKAY [ 0.142s]
writing 'revocery'...
FAILED (remote: Necessary to unlock FRP! Navigate to Settings > Develope
finished. total time: 0.154s
Since my phone not booting i cannot use this option Please help
Click to expand...
Click to collapse
activate "Developer options"
playing several times "compilation"
go to options and enable developer
"Enable OEM unlock"
Hey , the problem is the device won't boot , so how can we enable developer option?!!!!
Sent from my iPhone using Tapatalk
There was a time when xda where the place to get the right answer and quick!
nowadays most topics are full of people with same problem and no dev to come to help, pity.
on topic: I have the same problem, ( mine is a Y6 pro) and before bricking it I had debugging and oem unlock enabled but now can't flash boot etc using fastboot ( error , denied ..) and can't use spflashtools either : preloader vcom appears for 1 second and then disappears and phone turns on.
tried many drivers, 3 Os'es (7, 8.1 ,10) still no luck.
porcha18 said:
activate "Developer options"
playing several times "compilation"
go to options and enable developer
"Enable OEM unlock"
Click to expand...
Click to collapse
Danke!!!!!!!!!!!!! Nach ewigem Suchen diese einfache Lösung. Vielen Dank!! Tag gerettet
the same issue
Good day, i have the same issue on my p9 EVA-L19.
FRP lock. And i can't do anything...
My warranty says that they cannot recover data from the phone, but the information is very important. I need to unlock FRP and somehow boot into TWRP or something to recover my data.
Please help someone if you had a same issue and results.
For the Huawei Y6 you can return to Stock.
Try to fastboot boot recovery-twrp.img and put your stock firmware (dload) folder to the rootdir at your sdcard.
Reboot your device to bootloader and hold down vol+ + vol- and use the command: fastboot boot stockrecovery.img (keep the keys pressed until the stock recovery comes up and starts installing your stock rom.
You will see an emui logo and the recovery will install the complete stock rom if you did everything right.
Retry to boot the stock recovery with this way if it is not working at the first try.
EDIT: after i wiped /system and and all the other stuff i was able to flash stock recovery via fastboot.
Runner85sx said:
For the Huawei Y6 you can return to Stock.
Try to fastboot boot recovery-twrp.img and put your stock firmware (dload) folder to the rootdir at your sdcard.
Reboot your device to bootloader and hold down vol+ + vol- and use the command: fastboot boot stockrecovery.img (keep the keys pressed until the stock recovery comes up and starts installing your stock rom.
You will see an emui logo and the recovery will install the complete stock rom if you did everything right.
Retry to boot the stock recovery with this way if it is not working at the first try.
EDIT: after i wiped /system and and all the other stuff i was able to flash stock recovery via fastboot.
Click to expand...
Click to collapse
Is there a way to do this on a mac?
Ive got adb enabled on terminal and I have a recovery.img file in my downloads though Im not sure if its the right one.
I typed in fastboot devices and then fastboot flash recovery recovery.img but it said cannot load recovery.img
anditan said:
Is there a way to do this on a mac?
Ive got adb enabled on terminal and I have a recovery.img file in my downloads though Im not sure if its the right one.
I typed in fastboot devices and then fastboot flash recovery recovery.img but it said cannot load recovery.img
Click to expand...
Click to collapse
your recovery location in adb is wrong probably. try changing it to the correct path. atleast thats what worked for me
man u can'T do anything because FRP is ACTIVATED !!!
No solution till now
Use the Huawei Swype bypass Method
michalss said:
Hi all,
I have a small problem, my phone does not boot and hanging on Logo. Now i can boot to fastboot menu, but i cannot really use it since i have FRP lock . Is there any chance to baypass it to make possible to flash recovery boot.img ?
When i try any command getting this error :
Code:
target reported max download size of 266338304 bytes
sending 'revocery' (4096 KB)...
OKAY [ 0.142s]
writing 'revocery'...
FAILED (remote: Necessary to unlock FRP! Navigate to Settings > Develope
finished. total time: 0.154s
Since my phone not booting i cannot use this option Please help
Click to expand...
Click to collapse
Try to do:
fastboot boot recovery.img
This will boot up the device with the given image. With that you can put a custom rom to your sd-card and flash it.
I will upload a Nandroid (stock system, recovery, boot) from my Y6 SCL-L01 soon.
With that you can restore boot and recovery with twrp. For this way you don't need to have a frp unlock.
Procedure:
fastboot boot recovery-twrp.img
Put your stock firmware (dload folder) to the sdcard.
Put my Nandroid to your sdcard.
Restore my Nandroid, reboot your device with Vol+ and Vol- pressed.
This way only works for SCL-L01 up to SCL-L04.
I need to create an extra recovery.img that includes a dt image that fits for all SCL variants.
Work in progress...
I have just removed frp today, but its not free method, unfortunately
EDIT: ALSO, use usb 2.0 ports to flash stuff, usb 3.0 is not working 100 percent yet.
EDIT, 14 Mar 2016: Kingroot got me to root and now I have twrp installed, http://www.kingroot.net/ .
I have a Sprint prepaid Moto E 2015 LTE, XT1526. I did the motorola bootloader unlock, that went fine.
The phone works and is activated on RingPlus, when it boots, I get the Red Warning, Bootloader unlocked, when normally booting.
When I try to flash a recovery to the phone (all that I could find here on XDA), I get this response:
S:\Phones\Moto_E-2015-2ndGen-XT1526\adb-and-fastboot>fastboot devices
TA0XXXXXXX fastboot (edited to take out SN)
S:\Phones\Moto_E-2015-2ndGen-XT1526\adb-and-fastboot>fastboot flash recovery recovery.img
target reported max download size of 268435456 bytes
sending 'recovery' (12916 KB)...
FAILED (data transfer failure (Unknown error))
finished. total time: 0.015s
S:\Phones\Moto_E-2015-2ndGen-XT1526\adb-and-fastboot>adb kill-server
I've tried everything, and am providing as much info as I can, in case anyone seeing something that is 'new' or 'different' about my phone.
Double check and be sure you're attempting to flash the TWRP for the Moto E 2015 LTE "Surnia", not "Otus" (which is the Moto E 2015 3G). iirc, I used Squid's TWRP from here: http://forum.xda-developers.com/moto-e-2015/development/twrp-squid-twrp-recovery-moto-e-lte-t3137649 . If 3.0.0 doesn't work, try 2.8.7.
You should also try changing USB ports. I ran into a similar issue where I wasn't able to flash things when I plug into my most often used USB port. I suspect that the contacts got worn from how often I used it, so I tried another USB port and it worked fine.
I have done same procedure as yours and meet same problem yesterday.
I flashed twrp recovery with following command,
fastboot boot recovery.img
instead of
fastboot flash recovery recovery.img
here are the post which I followed.
http://www.xda-developers.com/how-to-root-the-moto-e-2015-and-unlock-the-bootloader-xda-tv/
http://forum.xda-developers.com/moto-e-2015/orig-development/twrp-moto-e-2015-recovery-t3049726
faheyd said:
When I try to flash a recovery to the phone (all that I could find here on XDA), I get this response:
S:\Phones\Moto_E-2015-2ndGen-XT1526\adb-and-fastboot>fastboot devices
TA0XXXXXXX fastboot (edited to take out SN)
S:\Phones\Moto_E-2015-2ndGen-XT1526\adb-and-fastboot>fastboot flash recovery recovery.img
target reported max download size of 268435456 bytes
sending 'recovery' (12916 KB)...
FAILED (data transfer failure (Unknown error))
finished. total time: 0.015s
Click to expand...
Click to collapse
Thanks, but not working:
S:\Phones\Moto_E-2015-2ndGen-XT1526\adb-and-fastboot>fastboot boot recovery.img
downloading 'boot.img'...
FAILED (data transfer failure (Unknown error))
finished. total time: 0.009s
S:\Phones\Moto_E-2015-2ndGen-XT1526\adb-and-fastboot>
You can get rid of the warning by method in post 2 of this link
http://forum.xda-developers.com/moto-e-2015/general/guide-unlock-bootloader-moto-e-2015-t3045748
Q1:How to remove the unlocked bootloader message?
Then, flash the twrp recovery again. Make sure you have right recovery.img. here is the one I used.
http://forum.xda-developers.com/devdb/project/?id=8591#downloads
llaalways said:
You can get rid of the warning by method in post 2 of this link
http://forum.xda-developers.com/moto-e-2015/general/guide-unlock-bootloader-moto-e-2015-t3045748
Q1:How to remove the unlocked bootloader message?
Then, flash the twrp recovery again. Make sure you have right recovery.img. here is the one I used.
http://forum.xda-developers.com/devdb/project/?id=8591#downloads
Click to expand...
Click to collapse
I know that, does not help. I've tried that recovery, one from cyanogenmod also, the recovery img is not the problem. Thanks anyway.
go to phone options and turn on USB debugging and when you go to flash it..
- turn off phone.
- hold volume down and power to get to boot loader screen..
Leave it there and connect to PC.
It should be showing you the bootloader screen.. you know what that is right ?
Then open "Minimal ADB and Fastboot" install folder..
Right click empty folder space while holding shift key down..
Select open cmd window here..
type in either,
fastboot devices
or
mfastboot devices
and make sure it says your device is listed
then paste into cmd window..
mfastboot flash recovery recovery.img
make sure your new recovery file has that name and is copied to that fastboot folder.
that should be it..
xpmule said:
go to phone options and turn on USB debugging and when you go to flash it..
- turn off phone.
- hold volume down and power to get to boot loader screen..
Leave it there and connect to PC.
It should be showing you the bootloader screen.. you know what that is right ?
Then open "Minimal ADB and Fastboot" install folder..
Right click empty folder space while holding shift key down..
Select open cmd window here..
type in either,
fastboot devices
or
mfastboot devices
and make sure it says your device is listed
then paste into cmd window..
mfastboot flash recovery recovery.img
make sure your new recovery file has that name and is copied to that fastboot folder.
that should be it..
Click to expand...
Click to collapse
As stated in my OP, I've done all that, but I'll do it again, please look at my pics and post, you'll see I've done all that already:
S:\Phones\Moto_E-2015-2ndGen-XT1526\mfastboot-v2>mfastboot devices
TA00000000 fastboot (edited to change serial number)
S:\Phones\Moto_E-2015-2ndGen-XT1526\mfastboot-v2>mfastboot flash recovery recovery.img
target max-sparse-size: 256MB
sending 'recovery' (12916 KB)...
FAILED (data transfer failure (Unknown error))
finished. total time: 0.007s
S:\Phones\Moto_E-2015-2ndGen-XT1526\mfastboot-v2>
Can a DEV please help ? If I need to go back to stock I'll be glad to do it and then unlock the bootloader again, however, I've posted in two diff forums trying to get someone to tell me the correct SPRINT img to bring back to stock, no answers.
XT1526_SURNIA_USC_5.0.2_LXI22.50-29.1_cid9_subsidy-DEFAULT_CFC.xml
XT1526_SURNIA_REPW_5.0.2_LXI22.50-56-1.1_cid6_subsidy-REPUB_CFC.xml
XT1526_SURNIA_BOOST_5.0.2_LXI22.50-14.8_cid9_subsidy-DEFAULT_CFC.xml
I think it's the boost, but it doesn't have the SPRINT label on it, like my phone.
You just said,
"Can a DEV please help ? If I need to go back to stock I'll be glad to do it and then unlock the bootloader again"
So why would you say that ?
Did you relock your bootloader ?
Maybe that is why you are having a problem ?
I never have relocked mine eh..
And i have had no problem flashing TWRP from Squid.. all his various updates overwriting the old one.
I have flashed a bunch of stock retail recoveries too and all of those worked fine too.
I am curious did you try and load recovery after to see if it actually changed or not ?
EDIT:
Can i ask you exactly what Custom Recovery you are trying to install ?
And did you verify the MD5 hash ?
I always do *if it's available..
xpmule said:
You just said,
"Can a DEV please help ? If I need to go back to stock I'll be glad to do it and then unlock the bootloader again"
So why would you say that ? On other models of phones it has solved a problem of this nature.
Did you relock your bootloader ? Of course not, if you had read the post, you would see that.
Maybe that is why you are having a problem ? No
I never have relocked mine eh.. Good for you, that doesn't help me.
And i have had no problem flashing TWRP from Squid.. all his various updates overwriting the old one.
I have flashed a bunch of stock retail recoveries too and all of those worked fine too. Good for you, that doesn't help me.
I am curious did you try and load recovery after to see if it actually changed or not ? I did, I get an icon with something that says no cmd,
EDIT:
Can i ask you exactly what Custom Recovery you are trying to install ? Surnia and CM's recovery, no difference.
And did you verify the MD5 hash ? Yes.
I always do *if it's available..
Click to expand...
Click to collapse
I've done all those things and tried to post as much info in my OP. Is there a Dev that can help me?
I've now tried to go back to stock in an effort to unlock this biatch using XT1526_SURNIA_BOOST_5.0.2_LXI22.50-14.8_cid9_subsidy-DEFAULT_CFC.xml, and it wont let me do that either. It's not letting me write to the GPT partition. This leads me to believe my phone is NOT unlocked, even though the bootloader shows UNLOCKED BOOTLOADER. Anyone know an answer?
I noticed something a while back when I attempted to flash recovery on a different phone (nexus 6) but failed. I tried a bunch of stuff to no avail. The solution was to simply get a new set of platform tools because mine was too old. Doesn't hurt to try.
Snorbro said:
I noticed something a while back when I attempted to flash recovery on a different phone (nexus 6) but failed. I tried a bunch of stuff to no avail. The solution was to simply get a new set of platform tools because mine was too old. Doesn't hurt to try.
Click to expand...
Click to collapse
Thank you for trying. I just found a post, (and now I can't find it), but the guy went through what I did, and then he used KingRoot, http://www.kingroot.net/ , and it worked.
So, I tried it too, and magic, it worked. I now have root and TWRP installed.
I could have sworn I tried KingRoot, but it must have been on another phone I had.
Are you sure your recovery file is called recovery.img and not twrp.xxx.img? If not you need to rename it
Another problem I had, I was using a USB 3.0 port on my computer. This is a not the way. Using a USB 2.0 port works on flashing stuff.
Hi faheyd, I also have XT1526 on android 5.0.2, but kingroot fails. I was told not to update OS to keep it working in India.
Doess ur phone run on 5.1?
Does USB debugging needs to be activated?
drshreenivaas said:
Hi faheyd, I also have XT1526 on android 5.0.2, but kingroot fails. I was told not to update OS to keep it working in India.
Doess ur phone run on 5.1?
Does USB debugging needs to be activated?
Click to expand...
Click to collapse
I have no idea, hopefully someone that knows will step in and help.
I am trying to flash twrp or any custom recovery image so that I could root my LGv10, I am running Android 6.0.
When I boot my phone into fastboot mode I dont get the fastboot options just the options to exit or restart. However I still can run commands through adb, I try running the command to flash the custom image and I keep getting this.
Code:
C:\adb>fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (5158 KB)...
OKAY [ 0.160s]
writing 'recovery'...
FAILED (remote: unknown command)
finished. total time: 0.185s
If I try to start up in recovery mode I get an android with a red error triangle, preventing me from rooting. Is there anyway I can fix this? any help will be appreciated as I've looked already and cannot seem to find a fix to this problem.
Hi, which model of the V10 do you own?
Please note that bootloader unlock and installation of a custom recovery is only officially supported on the T-Mobile Version of the V10 and the European V10 with the model number H960A. On the H960A you need to unlock your bootloader first. Otherwise flasing recovery fails.
cyvr1 said:
Hi, which model of the V10 do you own?
Please note that bootloader unlock and installation of a custom recovery is only officially supported on the T-Mobile Version of the V10 and the European V10 with the model number H960A. On the H960A you need to unlock your bootloader first. Otherwise flasing recovery fails.
Click to expand...
Click to collapse
Thanks for the reply!
My LGv10 is the T-Mobile version, model number LG-H901. I'm running Marshmallow 6.0, My bootloader is unlocked I'm still getting the same problem.
Not sure what to try anymore
Same exact issue I have. Don't know what else to do.
I was getting that yesterday, though I found another method that seems to have worked, only issue with that one is that whenever I try I flash a ROM, it fails with error 7.
https://dottech.org/198032/how-to-root-lg-v10-t-mobile-h901-on-android-6-0-marshmallow/
This was the method I used, though I didn't do it properly since I couldn't figure out what to do with the kdz file. But I do have TWRP recovery installed to my phone now.
Hi all,
Today I tried to root my LG G5 H830 but with an older method for Marshmallow(in the video i was watching the version wasn't even specified so I was unaware and I believed that the version of the phone did not really matter). I proceeded to follow this man's instructions @: "How to Root T-Mobile LG G5!" by "Max Lee" on Youtube(as a new user i cannot post links ) I unlocked my bootloader, got drivers and followed his instructions up onto an error on LGUP. Basically the error's purpose was to tell me that Nougat is not supported. So I had no choice but to reboot my phone and go through the android initializing setup.
After realizing the error of my ways I then found this post here via Google Search: "Install TWRP Recovery and Root LG G5 on Android Nougat | DroidViews" to install TWRP. Now my bootloader is unlocked and I have no root. The only problem here is that whenever I go into developer options and try to toggle 'OEM unlock' on it won't let me. The OEM unlock setting is grey-ed out and I am unable to toggle it!! This is what I need help with! Although my bootloader is very much infact unlocked I think some error occurred to where now I cant toggle my OEM unlock thus I am unable to flash a TWRP recovery via fastboot!
If I reboot into my bootloader and run the command "fastboot flash recovery recovery.img" i get this:
Code:
target reported max download size of 536870912 bytes
sending 'recovery' (18668 KB)...
OKAY [ 0.419s]
writing 'recovery'...
FAILED (remote: unknown command)
finished. total time: 0.435s
I even ignored the error and tried to boot into recovery manually and i just get the stock recovery.
Please help me guys
What about locking the bootloader again and unlocking it after that with the newer video you used?
MAGNVM said:
Hi all,
Today I tried to root my LG G5 H830 but with an older method for Marshmallow(in the video i was watching the version wasn't even specified so I was unaware and I believed that the version of the phone did not really matter). I proceeded to follow this man's instructions @: "How to Root T-Mobile LG G5!" by "Max Lee" on Youtube(as a new user i cannot post links ) I unlocked my bootloader, got drivers and followed his instructions up onto an error on LGUP. Basically the error's purpose was to tell me that Nougat is not supported. So I had no choice but to reboot my phone and go through the android initializing setup.
After realizing the error of my ways I then found this post here via Google Search: "Install TWRP Recovery and Root LG G5 on Android Nougat | DroidViews" to install TWRP. Now my bootloader is unlocked and I have no root. The only problem here is that whenever I go into developer options and try to toggle 'OEM unlock' on it won't let me. The OEM unlock setting is grey-ed out and I am unable to toggle it!! This is what I need help with! Although my bootloader is very much infact unlocked I think some error occurred to where now I cant toggle my OEM unlock thus I am unable to flash a TWRP recovery via fastboot!
If I reboot into my bootloader and run the command "fastboot flash recovery recovery.img" i get this:
Code:
target reported max download size of 536870912 bytes
sending 'recovery' (18668 KB)...
OKAY [ 0.419s]
writing 'recovery'...
FAILED (remote: unknown command)
finished. total time: 0.435s
I even ignored the error and tried to boot into recovery manually and i just get the stock recovery.
Please help me guys
Click to expand...
Click to collapse
Did you try to run the terminal/cmd as an administrator/root?
Sent from my LG-H840 using Tapatalk
Hello Everyone!
I unlocked and installed TWRP on my P20 lite, but now I want to be able to install the updates of Huawei again (especially when Android P is about to release).
So how do I uninstall TWRP and if it's possbile lock my phone again?
(am not that amazing with Smartphone software, so just saying...)
Greets Louis
LouisJ444 said:
Hello Everyone!
I unlocked and installed TWRP on my P20 lite, but now I want to be able to install the updates of Huawei again (especially when Android P is about to release).
So how do I uninstall TWRP and if it's possbile lock my phone again?
(am not that amazing with Smartphone software, so just saying...)
Greets Louis
Click to expand...
Click to collapse
Maybe this thread somehow can helps you:
https://forum.xda-developers.com/huawei-p20-lite/help/req-stock-recovery-p20-lite-t3803027
Don't need lock bootloader to install or receive via OTA official updates.
Lock the bootloader is not possible (maybe it is, but is a pay service).
You can relock instead of lock, but don't do it if your device is not completely stock.
Within the little experience that I have with this team I have investigated the following, when flasheas the official roms by twrp the boatloader is blocked again and the twrp is erased
kilroystyx said:
Maybe this thread somehow can helps you:
https://forum.xda-developers.com/huawei-p20-lite/help/req-stock-recovery-p20-lite-t3803027
Don't need lock bootloader to install or receive via OTA official updates.
Lock the bootloader is not possible (maybe it is, but is a pay service).
You can relock instead of lock, but don't do it if your device is not completely stock.
Click to expand...
Click to collapse
I still don't really understand how it works:
I downloaded the huawei extractor and extracted the files in a folder on my computer.
I got a update.zip file from my phone and extracted it on my computer.
But when I try to open the update.app file I get an error message saying:
https://i.gyazo.com/abce07c696fb31f15b95c832e3baa899.png
(if it doesn't work: ERECOVERY_VBMET.img: Invalid header crc - Expected: 42613 Got 18415)
LouisJ444 said:
I still don't really understand how it works:
I downloaded the huawei extractor and extracted the files in a folder on my computer.
I got a update.zip file from my phone and extracted it on my computer.
But when I try to open the update.app file I get an error message saying:
https://i.gyazo.com/abce07c696fb31f15b95c832e3baa899.png
(if it doesn't work: ERECOVERY_VBMET.img: Invalid header crc - Expected: 42613 Got 18415)
Click to expand...
Click to collapse
Remove the verification on the settings, check pic enclosed.
Mannuok said:
Within the little experience that I have with this team I have investigated the following, when flasheas the official roms by twrp the boatloader is blocked again and the twrp is erased
Click to expand...
Click to collapse
Your are partially correct.
Flashing official firmware with TWRP, have to be done with HuRUpdater, during installation the TWRP is replaced by stock recovery, then is your decision keep it or not.
About lock bootloader, mine is unlocked since day one and every time that I install new firmware it keep it unlocked. My experience so far is installing ANE-LX1 firmware in my ANE-LX1 device, probably with other firmware like ANE-AL00 or ANE-TL00 it can be different.
kilroystyx said:
Remove the verification on the settings, check pic enclosed.
Click to expand...
Click to collapse
So I can't seem to do "adb reboot bootloader" It will just go to the system.
And when I manually go into the bootloader and try to flash it, I get this error
Before this I tried to flash an other recovery on it which I found on a guide, but after I did that TWRP did get removed but I can't get on the recovery anymore and updating doesn't work either.
LouisJ444 said:
So I can't seem to do "adb reboot bootloader" It will just go to the system.
And when I manually go into the bootloader and try to flash it, I get this error
Before this I tried to flash an other recovery on it which I found on a guide, but after I did that TWRP did get removed but I can't get on the recovery anymore and updating doesn't work either.
Click to expand...
Click to collapse
In the Fastboot&Rescue Mode screen did you see phone unlocked and FRP unlock ?
Can you share all commands that you are using, can be text like you see bellow:
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery_ramdisk TWRP_3.2.1-0_ANE-LX1_Full_01.img
target reported max download size of 471859200 bytes
sending 'recovery_ramdisk' (24962 KB)...
OKAY [ 0.861s]
writing 'recovery_ramdisk'...
OKAY [ 0.109s]
finished. total time: 0.970s
Are you trying to use command recovery instead of recovery_ramdisk?
kilroystyx said:
In the Fastboot&Rescue Mode screen did you see phone unlocked and FRP unlock ?
Can you share all commands that you are using, can be text like you see bellow:
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery_ramdisk TWRP_3.2.1-0_ANE-LX1_Full_01.img
target reported max download size of 471859200 bytes
sending 'recovery_ramdisk' (24962 KB)...
OKAY [ 0.861s]
writing 'recovery_ramdisk'...
OKAY [ 0.109s]
finished. total time: 0.970s
Are you trying to use command recovery instead of recovery_ramdisk?
Click to expand...
Click to collapse
1. It says: Phone Unlocked
FRP Unlock
2. When I was in this screen I do:
- cd C:\Users\Louis\Desktop\platform-tools
- fastboot flash recovery RECOVERY_RAMDIS.img
then it gives the error
3. When I try to do it normally, I do:
- cd C:\Users\Louis\Desktop\platform-tools
- adb reboot bootloader
LouisJ444 said:
1. It says: Phone Unlocked
FRP Unlock
2. When I was in this screen I do:
- cd C:\Users\Louis\Desktop\platform-tools
- fastboot flash recovery RECOVERY_RAMDIS.img
then it gives the error
3. When I try to do it normally, I do:
- cd C:\Users\Louis\Desktop\platform-tools
- adb reboot bootloader
Click to expand...
Click to collapse
You have to use recovery_ramdisk because this is the name of the partition in this Android version.
I assume that you didn't change the name of the stock recovery extracted, for your case the right command is:
Code:
fastboot flash recovery_ramdisk RECOVERY_RAMDIS.img
kilroystyx said:
You have to use recovery_ramdisk because this is the name of the partition in this Android version.
I assume that you didn't change the name of the stock recovery extracted, for your case the right command is:
Code:
fastboot flash recovery_ramdisk RECOVERY_RAMDIS.img
Click to expand...
Click to collapse
Thanks, that seemed to work!
kilroystyx said:
Your are partially correct.
Flashing official firmware with TWRP, have to be done with HuRUpdater, during installation the TWRP is replaced by stock recovery, then is your decision keep it or not.
About lock bootloader, mine is unlocked since day one and every time that I install new firmware it keep it unlocked. My experience so far is installing ANE-LX1 firmware in my ANE-LX1 device, probably with other firmware like ANE-AL00 or ANE-TL00 it can be different.
Click to expand...
Click to collapse
Where I get the original romes of Huawei???
Mannuok said:
Where I get the original romes of Huawei???
Click to expand...
Click to collapse
web version:
http://pro-teammt.ru/firmware-database/?firmware_model=&firmware_page=0
android version:
https://play.google.com/store/apps/details?id=com.teammt.gmanrainy.huaweifirmwarefinder
some tips:
https://forum.xda-developers.com/hu...om-official-emui-8-0-huawei-p20-lite-t3773999
kilroystyx said:
Your are partially correct.
Flashing official firmware with TWRP, have to be done with HuRUpdater, during installation the TWRP is replaced by stock recovery, then is your decision keep it or not.
About lock bootloader, mine is unlocked since day one and every time that I install new firmware it keep it unlocked. My experience so far is installing ANE-LX1 firmware in my ANE-LX1 device, probably with other firmware like ANE-AL00 or ANE-TL00 it can be different.
Click to expand...
Click to collapse
ANE LX3 no funciona asi,
Mannuok said:
ANE LX3 no funciona asi,
Click to expand...
Click to collapse
what do you mean by that?
kilroystyx said:
Maybe this thread somehow can helps you:
https://forum.xda-developers.com/huawei-p20-lite/help/req-stock-recovery-p20-lite-t3803027
Don't need lock bootloader to install or receive via OTA official updates.
Lock the bootloader is not possible (maybe it is, but is a pay service).
You can relock instead of lock, but don't do it if your device is not completely stock.
Click to expand...
Click to collapse
Hi all,
Getting a "lock" state is possible indeed. I believe you @kilroystyx had seen it as well on @Merlin_99 's thread:
https://forum.xda-developers.com/huawei-p20-lite/how-to/root-how-to-install-update-t3841557
This will erase all data, except from sdcards of course
Cheers,
AS
Mannuok said:
ANE LX3 no funciona asi,
Click to expand...
Click to collapse
ars_chelsea said:
Hi all,
Getting a "lock" state is possible indeed. I believe you @kilroystyx had seen it as well on @Merlin_99 's thread:
https://forum.xda-developers.com/huawei-p20-lite/how-to/root-how-to-install-update-t3841557
This will erase all data, except from sdcards of course
Cheers,
AS
Click to expand...
Click to collapse
You are right, first post was on the August 20th, at that time I didn't knew that was possible lock bootloader, only after Merlin_99 create that thread on September 12th.