I have been using Asus Fonepad 8 recently.It is rooted but its bootloader were not unlocked.I have try to unlock it but it says "unknown oem command".Would you help me solve this problem.I am new to android.Thank you.
can't flash through fastboot and no OS installed to boot
lukhmanrahim said:
I have been using Asus Fonepad 8 recently.It is rooted but its bootloader were not unlocked.I have try to unlock it but it says "unknown oem command".Would you help me solve this problem.I am new to android.Thank you.
Click to expand...
Click to collapse
Same here, I ended up with the device having no OS installed and I can't flash through fastboot. When using "fastboot flash boot boot.img" I recevice following:
sending 'boot' (8741 KB)...
OKAY [ 0.607s]
writing 'boot'...
(bootloader) Please flash boot_sign.img
FAILED (remote: check_sign_key fail: no allow update kernel)
finished. total time: 0.943s
Why is this happening?
I also tried "Tethered Temporary CWM / TWRP Recovery Session" and in that menu I tried install zip file (UL-K016-WW-4.2.2.0-user) but receive following output:
Checking BOM token
BOM flashing failed
return code 0E:Error in /external_sd/MOFD_SDUPDATE.zip (=UL-K016-WW-4.2.2.0-user; just renamed it because I read that in some thread)
My device is from China and I am trying to use a WW version...
I would appreciate any help, thanks in advance!
lukhmanrahim said:
I have been using Asus Fonepad 8 recently.It is rooted but its bootloader were not unlocked.I have try to unlock it but it says "unknown oem command".Would you help me solve this problem.I am new to android.Thank you.
Click to expand...
Click to collapse
I have the asus fonepad 8 too, ans i've read that the bl isn't unblockable... I'll try other methods to unlock.
---------- Post added at 10:48 AM ---------- Previous post was at 10:47 AM ----------
canoge said:
Same here, I ended up with the device having no OS installed and I can't flash through fastboot. When using "fastboot flash boot boot.img" I recevice following:
sending 'boot' (8741 KB)...
OKAY [ 0.607s]
writing 'boot'...
(bootloader) Please flash boot_sign.img
FAILED (remote: check_sign_key fail: no allow update kernel)
finished. total time: 0.943s
Why is this happening?
I also tried "Tethered Temporary CWM / TWRP Recovery Session" and in that menu I tried install zip file (UL-K016-WW-4.2.2.0-user) but receive following output:
Checking BOM token
BOM flashing failed
return code 0E:Error in /external_sd/MOFD_SDUPDATE.zip (=UL-K016-WW-4.2.2.0-user; just renamed it because I read that in some thread)
My device is from China and I am trying to use a WW version...
I would appreciate any help, thanks in advance!
Click to expand...
Click to collapse
Check my reply. I have the solution for you (i've mentioned you)
Giovix92 said:
I have the asus fonepad 8 too, ans i've read that the bl isn't unblockable... I'll try other methods to unlock.
---------- Post added at 10:48 AM ---------- Previous post was at 10:47 AM ----------
Check my reply. I have the solution for you (i've mentioned you)
Click to expand...
Click to collapse
Hi, I'm currently downloading the needed files which are listed in the thread that you have sent me. Also I've posted a reply to that post (its #111) - do you know if the raw file for FE380CG is suitable for my device, which is FE8030CXG (as I said its from China, maybe that is important to note...) In the list of raw files that are uploaded in that thread the FE380CG is the closest to my model.
canoge said:
Hi, I'm currently downloading the needed files which are listed in the thread that you have sent me. Also I've posted a reply to that post (its #111) - do you know if the raw file for FE380CG is suitable for my device, which is FE8030CXG (as I said its from China, maybe that is important to note...) In the list of raw files that are uploaded in that thread the FE380CG is the closest to my model.
Click to expand...
Click to collapse
I don't know if it's for your model... But, I have the FE380CXG too and i have the FE380CG's firmware flashed. I
Giovix92 said:
I don't know if it's for your model... But, I have the FE380CXG too and i have the FE380CG's firmware flashed. I
Click to expand...
Click to collapse
Ok, that sounds promising :good: I'll let you know whether the method worked or not
canoge said:
Ok, that sounds promising :good: I'll let you know whether the method worked or not
Click to expand...
Click to collapse
Okay, i'll be waiting.
Guys, i've found this on an english forum:
To unlock the boot loader on your Asus Fonepad 8 Fe380cg you need to have the ADT with all the packages installed and configured. Download ADT with all the packages from this link : http://developer.android.com/sdk/index.html
Later once the configuration is done properly then you can connect your device and enable USB Debugging under the options.
1. Download Modaco Superboot file for Asus Fonepad 8 Fe380cg from this link :
http://downloadsafe.org/file/0YgX7 , and save them to your computer.
Tutorial Video : Easy Way To Download file = http://how-to-root.com/10
2. Once downloaded, extract it by right clicking and extract all.
3. On your device, click on Settings > Developer Options > Turn USB Debugging On.
4. Plug the device in to your computer via USB cable.
5. Open the superboot folder that we just extracted (until you see the folder with fastboot-windows inside it), then hold the shift key down on your computer and right click any blank area.
6. Now, select open command window here.
7. In the command prompt, type the following with hitting enter at the end of each line.
adb-windows reboot bootloader (and wait for the device to reboot) fastboot-windows oem unlock *If it gets stuck at waiting for device here, download and install PDANet on your computer, once installed, unplug then plug the device back in and see if that fixes it.
Once it runs the device should display a screen asking you if you are sure. Click yes using the volume buttons. The device will go back to the bootloader screen but say unlocked at the bottom.
Click to expand...
Click to collapse
Can anyone verify if this method will unlock the bl?
Bro plz tell me how u root asus ko16 plz
canoge said:
Same here, I ended up with the device having no OS installed and I can't flash through fastboot. When using "fastboot flash boot boot.img" I recevice following:
sending 'boot' (8741 KB)...
OKAY [ 0.607s]
writing 'boot'...
(bootloader) Please flash boot_sign.img
FAILED (remote: check_sign_key fail: no allow update kernel)
finished. total time: 0.943s
Why is this happening?
I also tried "Tethered Temporary CWM / TWRP Recovery Session" and in that menu I tried install zip file (UL-K016-WW-4.2.2.0-user) but receive following output:
Checking BOM token
BOM flashing failed
return code 0E:Error in /external_sd/MOFD_SDUPDATE.zip (=UL-K016-WW-4.2.2.0-user; just renamed it because I read that in some thread)
My device is from China and I am trying to use a WW version...
I would appreciate any help, thanks in advance!
Click to expand...
Click to collapse
very bad
HI
my asus tablet is Fonepad 8 (fe380cg).
DiroidBoot not running and stay on INTEL INSIDE logo.
i read this forum and do it
http://4pda.ru/forum/index.php?showt...ost&p=52946315
during flash by xFSTK Downloader like this Error appear
https://forum.xda-developers.com/sho...&postcount=105
i need Fonepad 8 (fe380cg) firmware .bin file ( Fw_Dnx IFWI OS_Dnx OS_Image ) for flash by xFSTK Downloader.
what is GP Flag override for my tablet?
DiroidBoot not running and stay on INTEL INSIDE logo.
Please Help Me
Thanks
lukhmanrahim said:
I have been using Asus Fonepad 8 recently.It is rooted but its bootloader were not unlocked.I have try to unlock it but it says "unknown oem command".Would you help me solve this problem.I am new to android.Thank you.
Click to expand...
Click to collapse
How Did You Root It Without Unlocking the Bootloader?
Giovix92 said:
Guys, i've found this on an english forum: Can anyone verify if this method will unlock the bl?
Click to expand...
Click to collapse
will it erase data?
Related
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.
Hi !
I desesperatly seeking a root process for the Archos Diamond 2 Plus.
I can not find it by google.
As it looks like the P9000 of Elephone, I wondered if it was possible to use its recovery.img and supersu 1 and 2.
An idea ? A link for tutorial or for the stock rom (If root process failed) ?
Please ?
ok, no response.
I have tested with unlocked bootloader procedure but :
- i type adb reboot bootloader
- fastboot oem unlock
An normaly we confirm unlock with vol+ . But with archos diamond 2 plus, wol + is not active. There is no reaction at this moment.
So, if not unlocked bootloder, no flashing..
An idea ?
fanfan7110 said:
ok, no response.
I have tested with unlocked bootloader procedure but :
- i type adb reboot bootloader
- fastboot oem unlock
An normaly we confirm unlock with vol+ . But with archos diamond 2 plus, wol + is not active. There is no reaction at this moment.
So, if not unlocked bootloder, no flashing..
An idea ?
Click to expand...
Click to collapse
What android version?
android 6.0 marshmallow
fanfan7110 said:
android 6.0 marshmallow
Click to expand...
Click to collapse
You can boot into fastboot, which is good, in fastboot, type fastboot oem startftm. It will give you an error in the command line but what this allows you to do, is push files into partitions that are mounted R/W, that is of course, if this actually works for your device since every device is different.
Report results!
So after typed fastboot oem startftm i have the message "FAILED (remote: unknown command)"
And after to trying to put img file in boot , i have this : 'FAILED (remote: download for partition 'boot' is not allowed)"
fanfan7110 said:
So after typed fastboot oem startftm i have the message "FAILED (remote: unknown command)"
And after to trying to put img file in boot , i have this : 'FAILED (remote: download for partition 'boot' is not allowed)"
Click to expand...
Click to collapse
Please please please make a whole IMG backup since what we'll do might brick your device. I can't help you till Thursday, hit me up on Thursday with a reply on this thread.
---------- Post added at 08:51 PM ---------- Previous post was at 08:50 PM ----------
fanfan7110 said:
So after typed fastboot oem startftm i have the message "FAILED (remote: unknown command)"
And after to trying to put img file in boot , i have this : 'FAILED (remote: download for partition 'boot' is not allowed)"
Click to expand...
Click to collapse
Also, it is supposed to say failed when you start it.
hummm i can't take a backup of boot.img, because SU is not installed..
fanfan7110 said:
hummm i can't take a backup of boot.img, because SU is not installed..
Click to expand...
Click to collapse
Well, since the device is running mtk, try this. Flash the superuser binary and report, also, I am NOT responsible for anything, YOU are making these changes.
ok tested, but don't work with marshmallow. MTK Droid tools is incompatible with V6
fanfan7110 said:
ok tested, but don't work with marshmallow. MTK Droid tools is incompatible with V6
Click to expand...
Click to collapse
Well, now you have a mission to somehow port a working recovery to your phone.
Hey guys, I do not think this is a re-post of the other TWRP problems on Blackview 6000s. I have tried to install TWRP on my device many times. When I reboot into the custom recovery, a android with a danger sign appears. Instead of the TWRP screen. So what is the problem? (Android Noob here, please don't throw big developer words ).
Have tried
1. Changing USB ports / Using different computers
2. Flash_tool.exe
3. Flashing though adb/fastboot (is it the same?)
4. Different versions of TWRP.
5. Enabled USB debugging, OEM unlock & Install from Unknown Sources
Error Messages:
1. Running this -> adb reboot bootloader
error :no devices/emulators found (device was detected in "fastboot devices")
2. Running this -> fastboot flash recovery recovery.img
target reported max download size of 134217728 bytes
sending 'recovery' (9318 KB)...
OKAY [ 0.892s]
writing 'recovery'...
OKAY [ 0.250s]
finished. total time: 1.142s
(However, TWRP is not installed?)
Problem is solved, if u need help pm me
Hi,
Its good phone? Worth to buy it?
off160 said:
Hi,
Its good phone? Worth to buy it?
Click to expand...
Click to collapse
Yes, it is. It is a damm good phone. Pm me for more details.
Managed to solve issue. flashed wrong TWRP file lol
ROM for the bv6000s MT6737T?
DoctStrange said:
Managed to solve issue. flashed wrong TWRP file lol
Click to expand...
Click to collapse
Hi did you manage to find a ROM for the phone?
Hello
Might I know what ROM you are using, and where you got the TWRP? I managed to flash TWRP once on the device, and then install SuperSU when it had a previous ROM.
But I flashed it with blackview's latest ROM I found on their website. Since then, when I flash TWRP, the phone won't boot anymore
I'm using TWRP3.0.0, which is the latest one I found with a scatter file.
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
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.