hi guys
we know the huawei close page for unlock bootloader, the question there are another way to unlock the bootloader or flash the root without unlock the bootloader
mr.mgmg said:
hi guys
we know the huawei close page for unlock bootloader, the question there are another way to unlock the bootloader or flash the root without unlock the bootloader
Click to expand...
Click to collapse
Depends on which firmware you're on.
If you're on May patch or earlier you can use DC-Unlocker/HCU, if you're on June or later you can't unlock bootloader.
ante0 said:
Depends on which firmware you're on.
If you're on May patch or earlier you can use DC-Unlocker/HCU, if you're on June or later you can't unlock bootloader.
Click to expand...
Click to collapse
i can downgrade to old firmware?
mr.mgmg said:
i can downgrade to old firmware?
Click to expand...
Click to collapse
What firmware are you on now?
ante0 said:
What firmware are you on now?
Click to expand...
Click to collapse
8.0.0.138
mr.mgmg said:
8.0.0.138
Click to expand...
Click to collapse
And cust? BLA-Lx9CxxxB138
ante0 said:
And cust? BLA-Lx9CxxxB138
Click to expand...
Click to collapse
BLA-L29 8.0.0.138(c185)
mr.mgmg said:
BLA-L29 8.0.0.138(c185)
Click to expand...
Click to collapse
It's possible you can use DC-Unlocker/HCU (If it hasn't been fixed...)
Most likely it has, but you can test before continuing below as you'd need DC/HCU anyway.
Since you should be on XLOADER 01 now you can downgrade to XLOADER 01.
You can downgrade to B135 (Or earlier, check http://pro-teammt.ru/firmware-database/ as C185 has weird builds, lower builds released after higher ones ) using an USB C to USB A female OTG cable and sd adapter + microsd card (8GB minimum) or a USB Stick (8GB minimum).
Download dload package from http://androidhost.ru/search.html (Search for BLA-L29C 8.0.0.135(C185) and extract downloaded zip. Place 'dload' folder on sdcard/usb stick and either reboot to DLOAD mode (Vol up + down + power + otg inserted in phone) or through ProjectMenu (*#*#2846579#*#* in dialer then tap on SD update, it will say PT Failed but this can be ignored. It worked fine for me). Verify package will take a while so just stay on that screen until it's done.
You may have to factory reset after it's done.
When you are on B135 you can use DC-unlocker/HCU to get bootloader unlock code.
ante0 said:
It's possible you can use DC-Unlocker/HCU (If it hasn't been fixed...)
Most likely it has, but you can test before continuing below as you'd need DC/HCU anyway.
Since you should be on XLOADER 01 now you can downgrade to XLOADER 01. The version on B138 is weird on teammt's website, it has both
You can however downgrade to B135 (Or earlier, check http://pro-teammt.ru/firmware-database/ as C185 has weird builds, lower builds released after higher ones ) using an USB C to USB A female OTG cable and sd adapter + microsd card (8GB minimum) or a USB Stick (8GB minimum).
Download dload package from http://androidhost.ru/search.html (Search for BLA-L29C 8.0.0.135(C185) and extract downloaded zip. Place 'dload' folder on sdcard/usb stick and either reboot to DLOAD mode (Vol up + down + power + otg inserted in phone) or through ProjectMenu (*#*#2846579#*#* in dialer then tap on SD update, it will say PT Failed but this can be ignored. It worked fine for me). Verify package will take a while so just stay on that screen until it's done.
You may have to factory reset after it's done.
When you are on B135 you can use DC-unlocker/HCU to get bootloader unlock code.
Click to expand...
Click to collapse
thanks bro i will try
I am on BLA-L29 8.0.0.145(C432). Any chance to unlock the bootloader ?
Thank's for your help.
energiez said:
I am on BLA-L29 8.0.0.145(C432). Any chance to unlock the bootloader ?
Thank's for your help.
Click to expand...
Click to collapse
Yes, but using the B142 dload pack from androidhost.ru.
Use same description as I typed above, but search for BLA-L29C 8.0.0.142(C432). This is the version I downgraded (from B148-SP1 to B142) to when testing.
ante0 said:
It's possible you can use DC-Unlocker/HCU (If it hasn't been fixed...)
Most likely it has, but you can test before continuing below as you'd need DC/HCU anyway.
Since you should be on XLOADER 01 now you can downgrade to XLOADER 01.
You can downgrade to B135 (Or earlier, check http://pro-teammt.ru/firmware-database/ as C185 has weird builds, lower builds released after higher ones ) using an USB C to USB A female OTG cable and sd adapter + microsd card (8GB minimum) or a USB Stick (8GB minimum).
Download dload package from http://androidhost.ru/search.html (Search for BLA-L29C 8.0.0.135(C185) and extract downloaded zip. Place 'dload' folder on sdcard/usb stick and either reboot to DLOAD mode (Vol up + down + power + otg inserted in phone) or through ProjectMenu (*#*#2846579#*#* in dialer then tap on SD update, it will say PT Failed but this can be ignored. It worked fine for me). Verify package will take a while so just stay on that screen until it's done.
You may have to factory reset after it's done.
When you are on B135 you can use DC-unlocker/HCU to get bootloader unlock code.
Click to expand...
Click to collapse
Hi
I can use this on my mate 10 ALP-L29 8.0.0.138(C363patch1)
hamadazh said:
Hi
I can use this on my mate 10 ALP-L29 8.0.0.138(C363patch1)
Click to expand...
Click to collapse
If you're on a 01 xloader and you download dload for C363 (I assume C636?) you can. I can't find Patch1 OTA so I don't know what it contains.
ante0 said:
If you're on a 01 xloader and you download dload for C363 (I assume C636?) you can. I can't find Patch1 OTA so I don't know what it contains.
Click to expand...
Click to collapse
I'm a new in mate 10 and how i know if I am on a 01 xloader i was on b138 then OTA update to b138 patch01
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
........ Delete
thanks bro it's work with me
hamadazh said:
I'm a new in mate 10 and how i know if I am on a 01 xloader i was on b138 then OTA update to b138 patch01
View attachment 4574655
Click to expand...
Click to collapse
It *should* work. But since there is no patch01 available for download from pro-teammt.ru I can't check xloader to make sure it's 01, so it's risky if you are on 02... It can end in a hard-brick which is unrecoverable
ante0 said:
It *should* work. But since there is no patch01 available for download from pro-teammt.ru I can't check xloader to make sure it's 01, so it's risky if you are on 02... It can end in a hard-brick which is unrecoverable
Click to expand...
Click to collapse
Patch01 it's only patch for PUBG games and size is 100mb only., and the main rom is still 8.0.0138 nothing changed, i mean I was on b8.0.0.138 then OTA update (patch01) and size for this update was 100mb only.
ante0 said:
It *should* work. But since there is no patch01 available for download from pro-teammt.ru I can't check xloader to make sure it's 01, so it's risky if you are on 02... It can end in a hard-brick which is unrecoverable
Click to expand...
Click to collapse
Question please,, can i use FF to updatd to b139 then to b141?
Thanks :good:
hamadazh said:
Question please,, can i use FF to updatd to b139 then to b141?
Thanks :good:
Click to expand...
Click to collapse
You might using: https://forum.xda-developers.com/mate-10/how-to/firmwarefinder-dns-method-updating-c432-t3830476
In June the way FF works was fixed by Huawei, so the in-app proxy itself won't work to send update to System Update.
Related
I tested on LG G2 Korea Version F320S, F320L, F320K
- Why bootloop?: Some people Update OTA after flash CWM or TWRP so it will be bootloop. Or some strange reasons
- What should we do when we can not flash Stock firmware by FlashTool.1.0.54?
Let do follow this guide:
- Download file:
Flashtool V1.5 --> http://www.fshare.vn/file/TNVQZ9N74T ( tks to GSM Hosting forum )
Crack Flashtool : http://www.fshare.vn/file/TS1SGGVYWT ( tks to GSM hosting Forum )
File .TOT firmware :
F320S ->>> http://www.fshare.vn/file/T3SZR52W6T
F320K ->>> http://www.fshare.vn/file/TZRVMVMPFT
F320L V11c -->>> http://www.fshare.vn/file/TVR9DPAC7T
.dll file F320S/L/K >----- http://www.fshare.vn/file/TKW8J7QPQT
Driver: http://tool.xcdn.gdms.lge.com/dn/downloader.dev?fileKey=UW00120120425
- Let do:
Step1: Install Flashtool V1.5. Default install folder C:\LG\LGFlashtool
Copy crack file Megalock.dll to C:\LG\LgFlashtool
Step2: Enter download mode: Turnoff, push vol+ and plug USB cable in
Open Device Manager on your computer and choose COM41 for phone connection:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Step3: Open Flashtool, choose .dll and .tot file, then fresh yellow icon like this:
Step4: When Flashtool show Realdy, push USB out for 5secs and plug in again. Flash tool will automatic run
Step5: Wait for finishing:
Read more: http://choimobile.vn/threads/huong-dan-cuu-soft-brick-lg-g2-f320s-l-k.12932/#ixzz2h8Fy9fJB
Suggest you read the rules for XDA no warez allowed, CRACKED SOFTWARE = WAREZ!
fma965 said:
Suggest you read the rules for XDA no warez allowed, CRACKED SOFTWARE = WAREZ!
Click to expand...
Click to collapse
This is extremely useful, please blackout offending list and leave the post alone.
JoeTF said:
This is extremely useful, please blackout offending list and leave the post alone.
Click to expand...
Click to collapse
As a RC i can't do that.
Even though it is cracked, we don't see it as "warez". Almost every device has it cracked, so noone would be able to use it if we wouldn't allow it.
I mean, we also "crack" the bootloader of devices, which would be considered as warez, too, in that case
Cheers
laufersteppenwolf said:
Even though it is cracked, we don't see it as "warez". Almost every device has it cracked, so noone would be able to use it if we wouldn't allow it.
I mean, we also "crack" the bootloader of devices, which would be considered as warez, too, in that case
Cheers
Click to expand...
Click to collapse
hmm i guess, the way it was worded seems like you were cracking software tbh. my bad
fma965 said:
hmm i guess, the way it was worded seems like you were cracking software tbh. my bad
Click to expand...
Click to collapse
oops, may be a bit unluckily worded... the first "we" was meant as the mod staff, and the 2nd "we" as xda in general
laufersteppenwolf said:
oops, may be a bit unluckily worded... the first "we" was meant as the mod staff, and the 2nd "we" as xda in general
Click to expand...
Click to collapse
sorry, yeah i meant the OP not your reply
fma965 said:
sorry, yeah i meant the OP not your reply
Click to expand...
Click to collapse
Good post. Please leave this post coz I am also the lucky guy can get repair my bricked G2 using this usefuly TOT recovery method.
If possible, remind to set back correct version number (F320 L / K / S) in build info. which match with your IMEI#.
dokyson said:
I tested on LG G2 Korea Version F320S, F320L, F320K
- Why bootloop?: Some people Update OTA after flash CWM or TWRP so it will be bootloop. Or some strange reasons
- What should we do when we can not flash Stock firmware by FlashTool.1.0.54?
Let do follow this guide:
- Download file:
Flashtool V1.5 --> http://www.fshare.vn/file/TNVQZ9N74T ( tks to GSM Hosting forum )
Crack Flashtool : http://www.fshare.vn/file/TS1SGGVYWT ( tks to GSM hosting Forum )
File .TOT firmware :
F320S ->>> http://www.fshare.vn/file/T3SZR52W6T
F320K ->>> http://www.fshare.vn/file/TZRVMVMPFT
F320L V11c -->>> http://www.fshare.vn/file/TVR9DPAC7T
.dll file F320S/L/K >----- http://www.fshare.vn/file/TKW8J7QPQT
Driver: http://tool.xcdn.gdms.lge.com/dn/downloader.dev?fileKey=UW00120120425
- Let do:
Step1: Install Flashtool V1.5. Default install folder C:\LG\LGFlashtool
Copy crack file Megalock.dll to C:\LG\LgFlashtool
Step2: Enter download mode: Turnoff, push vol+ and plug USB cable in
Open Device Manager on your computer and choose COM41 for phone connection:
Read more: http://choimobile.vn/threads/huong-dan-cuu-soft-brick-lg-g2-f320s-l-k.12932/#ixzz2h8Fy9fJB
Click to expand...
Click to collapse
can't eneter in download mode i am stuck!!! help!!!
can someone give me the files for my D80210a
Stuck
Every time I try to press vol.up and plug in I still load right into twrp
ocarlty said:
Every time I try to press vol.up and plug in I still load right into twrp
Click to expand...
Click to collapse
I have the same problem with the CWM.
when i press the yellow arrow it gives me this error
i press ok and it continues to the step i have to reconnect the phone.
i reconnect it and i get this
i have changed the com number
i don't know what is the problem...
taxexpert said:
I have the same problem with the CWM.
Click to expand...
Click to collapse
Me too. Ever get this figured out?
I think what this boils down to is USB debugging was disabled by the factory reset. I had reset my device to prepare to sell it. When it booted back up I got an OTA offer and, not thinking, I accepted it. However, I still had CWR and root. I think OTA'S require stock recovery to work properly. So, no USB debugging and CWR as the recovery = soft brick. And, since CWR does not have a terminal option, there's no way to enter commands. I'm thinking this is going to be a warranty claim for me.
Will it work to restore a D805?
dokyson said:
I tested on LG G2 Korea Version F320S, F320L, F320K
- Why bootloop?: Some people Update OTA after flash CWM or TWRP so it will be bootloop. Or some strange reasons
- What should we do when we can not flash Stock firmware by FlashTool.1.0.54?
...
Click to expand...
Click to collapse
Hi!
Thank you for this n.n
Will it work to restore a D805? If not, then I better be careful with OTAs, or I better don't use any recovery as I'm not going to
flash any custom ROM till the G2 is done with official updates (2015?).
Thanks again n.n
- L.
I get this problem any help would be appreciated. thanks.
Could someone give another link on file for F320S > LGF320SAT-00-V10e-SKT-KR-JUL-29-20130
Becuse I have tried to download it by link in the topic. It takes me more than 8 hour, but file was corrupted (2.3 GB not 2.5 GB).
Please - I need TOT for F320
Sorry, if I interrupt here. I'm very new to forum.
My LG G2 F320S having Boot Loop after i updated on 4th Jan 2014.
I try to get TOT file for - 320S ->>> Given location But it seems not working. (I meant not downloading. I tried several days).
If anybody having it please please share with me.
Thanks Lot.
LK
Weird issue
Hi All,
tried using flashtool but I get the error that I need to check my phone model or the DLL.
I bought this phone from the Philippines with model number LG D802. I had flashed other roms for this with D802.
But when I was trying a while ago since I got a bootloop issue, the phone's downlaod mode is in korean and says in the phone and flashtool that my phone is running F320K? but it's so weird since I had D802 before even in the IMEI sticker in the back and to think I installed rayglobe ROM, before having the boot loop.
Any help would be appreciated.
THanks!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
LG isai LGL22 is a Japanese water-resistant G2 variant which has a microSD card slot, a IR port, Osaifu-Keitai and TV.
References
au: http://www.au.kddi.com/english/mobile/product/smartphone/lgl22/
LG: http://www.lg.com/jp/mobile-phone/lg-LGL22
pdadb: http://pdadb.net/index.php?m=specs&id=4958&view=1&c=lg_ks1204_g2_au_isai_lgl22
Hidden Menu
3845#*22#
Touch Firmware Upgrade: HW Device Test > Touch Test > Touch Firmware Upgrade
Firmwares Courtesy of Fairy Tale, wan8_kln, anonymous members and QQ group 263639652.
removed
Firmware Flash Instruction
tot instruction
kdz instruction
Android 4.2.2 JellyBean Root and Recovery
G2 Support Tool
Get a cwm_v*_lgl22.img from here and put it in ...\files\recovery then run "runme.bat".
Otherwise get a lokified TWRP or PhilZ Touch Recovery from here instead of CWM.
Android 4.4.2 KitKat Root
English: http://forum.xda-developers.com/showpost.php?p=53249488&postcount=308
日本語: https://sites.google.com/site/ma34ssss/lge/tools/g2_support_tool/how-to-use-for-kk
中文: http://bbs.gfan.com/android-7483086-1-1.html
Vietnam: http://lgviet.com/forum/threads/huóng-dãn-root-isai-tren-4-4-2.21058/
Android 4.4.2 KitKat Recovery
TWRP
CyanogenMod 11
cm-11-20140721-UNOFFICIAL-lgl22.zip
Any SIM card won't be recognized
还不能识别SIM卡
SIMカード認識しないです
CyanogenMod 12
Tekcafe
Any SIM card won't be recognized
还不能识别SIM卡
SIMカード認識しないです
Other ROMs
MIUI
CloudyG3
SphinX Isai
AOJP - Any SIM card won't be recognized so far
eXT for G2 series Mobile flash tool and tweaks by ma34s
Free
Donation
When your phone has got stuck after OTA with CWM installed (CWM flashable)
Zero_Fota_fix_ota_auto_recovery.zip
4G/LTE stabilize patch for docomo/SoftBank users (CWM flashable) Only for Android 4.2.2 JellyBean. This problem has been fixed on Android 4.4.2 KitKat.
LGL22_LTE_PATCH.zip
Original post: 2ちゃんねる 【root】 au isai LGL22 【sim unlock】 vol.2 #112
CloudyG2 NFC patch
L22_NFC.zip
Original post: #612 by A Sornchai
CyanogenMod project is pending due to the SIM card problem :\
CyanogenMod 11 still working in progress
Not Avaialble
Known issues of CyanogenMod 11
Baseband [Solved by ma34S]
microSD card mount [Solved by ma34S]
Wi-Fi [Solved by ma34S]
LED flash light [Solved by ma34S]
SIM card recognition (and also phone call and mobile network)
Camera focus
GPS [Solved by ma34S]
NFC
Osaifu-Keitai
We need your pull request
LG isai LGL22 [Water-resistant and microSD slot available Japanese G2 variant]
General Q&A
Q. Is this a G2 variant though called isai?
A. Yes. Search LG OpenSource Code Distribution for "LGL22" and you can see it's classified as G2.
Q. What are the differences with original G2?
A. This device has a microSD card slot, a IR port, Osaifu-Keitai and TV. In addition, it's IPX5 / IPX7 water-resistant but water submersion can cause damage. The battery capacity is 2500mAh and it's reduced more than original G2's.
Q. Can I use this phone on GSM network?
A. Yes. A number of XDA members unlocked their phone and they are using in their countries. A unlock code for international LG G2 works on this phone.
Development Q&A
Q. Can I root by using IORoot?
A. No. IORoot exploit has been patched in all Japanese G2 variants. You need to use g2_support_tool in OP.
Q. Has Loki exploit been patched?
A. Loki is executable on JellyBean firmwares. On KitKat firmwares it has been patched, however, Bump! vulnerability hasn't been patched.
KDZ flash instruction by @hoangthuong266
KDZ flash instruction by @hoangthuong266
If you have rooted or installed a ROM or a recovery, flash 10b tot before flashing 20b kdz so as to restore the firmware to factory condition.
English
hoangthuong266 said:
Download: http://www.mediafire.com/download/oz6r6cddxc1c09n/KDZ_flash_kit.zip
First, install B2Cappsetup.exe.
Second, delete C:\ProgramData\LGMOBILEAX folder and replace by LGMOBILEAX folder.
Third, run ScriptByMe.cmd in LG_Mobile_offline_mode folder, after that we enter to show this and select each dialog as below.
Select Upgrade Start and do the same as this image below
Make LG Isai phone to Download Mode and Press OK.
Click to expand...
Click to collapse
日本語
blackzigong said:
ダウンロード: http://www.mediafire.com/download/oz6r6cddxc1c09n/KDZ_flash_kit.zip
まずB2Cappsetup.exeをインストールします。
次にC:\ProgramData\LGMOBILEAXフォルダの中身をすべて削除し、ダウンロードしたLGMOBILEAXフォルダの中身で置き換えます。
そうしたらLG_Mobile_offline_modeにあるScriptByMe.cmdを実行するとこのような画面が表示されますので、以下のように選択して進めてください。
Upgrade Startを選択して画像と同じように設定してください。
isaiをダウンロードモードにしてOKを押してください。
Click to expand...
Click to collapse
Root and CWM Utility is now available in the OP.
CyanogenMod 11 for debugging
Updated g2_cwm_install_tool in the OP.
And also released CyanogenMod 11 for debugging in the OP.
We need your feedback and pull request.
The link is temporarily disabled to fix the kernel issue.
blackzigong said:
Updated g2_cwm_install_tool in the OP.
And also released CyanogenMod 11 for debugging in the OP.
We need your feedback and pull request.
The link is temporarily disabled to fix the kernel issue.
Click to expand...
Click to collapse
HI @blackzigong
LED flash light is fixed too.(it depend on camera fix)
ma34S said:
HI @blackzigong
LED flash light is fixed too.(it depend on camera fix)
Click to expand...
Click to collapse
Thanks, updated OP.
And I'm just uploading a new CM11 for debugging which includes @ma34S' changes.
blackzigong said:
Thanks, updated OP.
And I'm just uploading a new CM11 for debugging which includes @ma34S' changes.
Click to expand...
Click to collapse
thankyou^^
after i flashed •ma34S' CM based ROM called AOJP rom
baseband & MEID comes out
but the phone say "NO SIM"
how can i make the signal comes out?
thankyou^^
and the phone always in sleep mode
that can't wake up while press the power button.
i only can reboot it.
wan8_kln said:
thankyou^^
after i flashed •ma34S' CM based ROM called AOJP rom
baseband & MEID comes out
but the phone say "NO SIM"
how can i make the signal comes out?
thankyou^^
and the phone always in sleep mode
that can't wake up while press the power button.
i only can reboot it.
Click to expand...
Click to collapse
Thank you for your feedback.
It seems that the baseband is recognized but it can't recognize a SIM card yet due to a bug.
I heard about a sleep mode issue for the first time.
Issues is added in OP.
well I got a L22 today, would u plz tell me where I can download the latesr firmware V10b?
nicemblem said:
well I got a L22 today, would u plz tell me where I can download the latesr firmware V10b?
Click to expand...
Click to collapse
I don't have that firmware image. Update via FOTA.
ma34S posted a new AOJP rom for LGL22 on his website.
We need your feedback of a sim recognition and GPS.
If it helps lastest firmware is
LGL22AT-01-V10b-440-50-FEB-18-2014+0.zip
BigBoyPL said:
If it helps lastest firmware is
LGL22AT-01-V10b-440-50-FEB-18-2014+0.zip
Click to expand...
Click to collapse
ye and did u know where we can download it？
Yes I know where but I don't have B2B account so I can't download.
I posted my cm11 build in OP.
nicemblem said:
well I got a L22 today, would u plz tell me where I can download the latesr firmware V10b?
Click to expand...
Click to collapse
i have download firmware V10b but i forgot where got it, is there any way i can send it to u?
tolves said:
i have download firmware V10b but i forgot where got it, is there any way i can send it to u?
Click to expand...
Click to collapse
Would you share it here by using Dropbox or copy.com or something else?
blackzigong said:
Would you share it here by using Dropbox or copy.com or something else?
Click to expand...
Click to collapse
i have a TEST version of this phone
KDZ : V08d_00
do u need it???
v08d's baseband(1.9.10059) is different between v10a(1.9.10061)
v08d can use ONE CLICK ROOT
v08d building up seems like D80X
=======================================================
also i have full read of V10A phone block 1-38
if anyone needs, i can share.
wan8_kln said:
i have a TEST version of this phone
KDZ : V08d_00
do u need it???
v08d's baseband(1.9.10059) is different between v10a(1.9.10061)
v08d can use ONE CLICK ROOT
v08d building up seems like D80X
=======================================================
also i have full read of V10A phone block 1-38
if anyone needs, i can share.
Click to expand...
Click to collapse
That's cool!
Would you upload v08d_00 kdz firmware here?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Notes:
These are built with kernels from the latest Beelink GT-King (Amlogic S922X w/ w400 reference board) and Beelink GT1mini (Amlogic S905X2 w/ u212 reference board) firmware, but will probably work on any device based on the same reference boards.
The signed .ZIP files are suitable for installation with stock OEM recovery, but they use platform test keys and so might not work on builds requiring release keys.
If your device uses Android Verified Boot, there are additional measures you must take to successfully boot with a custom recovery partition.
Some OEM firmware have a stock recovery auto-restoration "feature" that will immediately replace TWRP after you reboot to system. The easiest workaround is simply to reboot to recovery immediately after the flash by holding the reset button. You can also try renaming /system/recovery-from-boot.p.
This is unofficial and unsupported, so the usual caveats apply. Since we don't flash the bootloader, you should be able recover from any problems...but nothing is guaranteed.
Not working:
MTP & ADB
Downloads:
S922X (Amlogic w400 reference board):
twrp-9.0-w400-3.7.0-0.img
twrp-9.0-w400-3.7.0-0-signed.zip
S905X2 & S905X3 (Amlogic u212 reference board):
twrp-9.0-u212-3.7.0-0.img
twrp-9.0-u212-3.7.0-0-signed.zip
Change Log:
v3.7.0-0: (20221204)
Updated to TWRP 3.7.0 release built from OMNI branch.
Updated to 007P0 LPDDR4 (u212) and 921P0 (w400) kernels.
v3.3.1-0: (20191111)
Switched from KM9 to GT1mini kernel
v3.2.3-0: (20190929)
Initial release
Instructions:
From OEM update app:
Copy .ZIP file to flash drive or microSD card
Open the UPDATE app and select Local Update
Select the .ZIP file and confirm
Note: No need to wipe data or cache
From OEM stock firmware (with root):
Open terminal window (e.g. Terminal Emulator for Android by Jack Palevich)
Navigate to location of .IMG file
Type the following:
Code:
su
dd if=twrp.img of=/dev/block/recovery
reboot recovery
From existing TWRP install:
Copy .IMG file to flash drive or microSD card
Click Install->Select Storage and pick the external drive
Click Install Image and select the .IMG file
Select Recovery partition and swipe to install
Reboot to Recovery
Source:
android_device_amlogic
Donations:
Your support is always appreciated! Just click here.
Hi!
I put your recovery using the UPDATE app method and I am unable to boot to it using "adb reboot recovery". Got a black screen
knuxxx said:
I put your recovery using the UPDATE app method and I am unable to boot to it using "adb reboot recovery". Got a black screen
Click to expand...
Click to collapse
Sounds like your box is using AVB 2.0.
Can someone please assist with how to root the U211 devices? TWRP works great, SuperSu 2.82 installs successfully via TWRP but when the system boots, it's still not rooted.
Any help is greatly appreciated here
Hey I'm stuck on bootloop, any hElp please? Gtking (S922X)
Vee89 said:
Hey I'm stuck on bootloop, any hElp please? Gtking (S922X)
Click to expand...
Click to collapse
Do you perhaps have the DDR4 (S/N: B922X) version of the GT-King? This one was build for the LPDDR4 (S/N:922X) hardware revision.
Magendanz said:
Do you perhaps have the DDR4 (S/N: B922X) version of the GT-King? This one was build for the LPDDR4 (S/N:922X) hardware revision.
Click to expand...
Click to collapse
I have : S/N:922XHQHE00129
Do you know a way to boot in recovery?
Vee89 said:
I have : S/N:922XHQHE00129
Click to expand...
Click to collapse
That *should* work then.
Vee89 said:
Do you know a way to boot in recovery?
Click to expand...
Click to collapse
Just hold the reset switch in for about 20 seconds while connecting power.
Fastboot mode is more of a challenge on the GT-King, since it can't get enough power from the USB cable by itself. You've got to hold the reset switch while simultaneously connecting both power and the USB cable to the back port.
Magendanz said:
That *should* work then.
Just hold the reset switch in for about 20 seconds while connecting power.
Fastboot mode is more of a challenge on the GT-King, since it can't get enough power from the USB cable by itself. You've got to hold the reset switch while simultaneously connecting both power and the USB cable to the back port.
Click to expand...
Click to collapse
Ok thank you, I tryed recovery mode.. still stuck in bootloop, I ordered a usb cable from gearbest so I will try fastboot wen mail knocks
Thank You TWRP work well
Magisk installation
And what to do to install Magisk correctly. The root is already on the Android 9 device. Unfortunately, the Magisk installation by TWRP has failed so far. Have any ideas? (applies to device and Amlogic S905X2 HK1 Play)
Can this be used on the Ugoos AM6 pro 4 gb / 32 gb s922x?
I guess so?
Duvel999 said:
Can this be used on the Ugoos AM6 pro 4 gb / 32 gb s922x?
Click to expand...
Click to collapse
My understanding is that Ugoos doesn't use the platform keys, and so the .zip file won't work with the OEM stock recovery. You should be able to flash the .img file, though, from TWRP or dd with root. (Yes, I know that's a bit of a chicken-or-egg scenario, so you might need to use Amlogic's USB Burning Tool or update.exe.) Also, look to see if they've implemented AVB 2.0, which can also be a PITA to work around.
Hi
I've got my eyes on a Beelink GT king Pro. Does this work with a s922x-h board @Magendanz ?
MAMATDZ said:
I've got my eyes on a Beelink GT king Pro. Does this work with a s922x-h board @Magendanz ?
Click to expand...
Click to collapse
I'd be surprised if it didn't. It's based on the same reference board as the GT King.
Ok great !
Thanks for the quick answer ^^
have someone a way to put TWRP on Amlogic S905X3?
Hi.
Can this be used on the S905X3? (Wechip v9 4GB/32GB)
Hello. When I try "Apply update from EXT", I got:
Code:
Found: Amlogic/p281:8.10/OPM1.171019.011/root:userdebug/test-keys
E3003: This update package is intended only for Android Pie builds (SDK 28)
Does it mean I cannot install it in Oreo Android?
romkeris said:
Hello. When I try "Apply update from EXT", I got:
Code:
Found: Amlogic/p281:8.10/OPM1.171019.011/root:userdebug/test-keys
E3003: This update package is intended only for Android Pie builds (SDK 28)
Does it mean I cannot install it in Oreo Android?
Click to expand...
Click to collapse
Yes that is what it means, I think his REF to TWRP-9.0 pretty much explains its for android 9 aka Pie only.
But there are many other recoverys that do work for Oreo...
As you may know, at the time of writing it's not possible to unlock the bootloader of the European model. Fortunately there's a workaround. To know how it works, scroll to the end of the post.
First of all, this is only for the European RMX3301, but you can try on any other global model that doesn't allow the unlocking of the bootloader. I'm not talking about temporary errors, but of the infamous This phone model does not support deep testing error message.
Before starting I would like to thank polygraphene for their implementation of the Dirty Pipe vulnerability on Android. Without that, this would not have been possible.
Requirements:
The phone with a decent charge. Do not attempt this procedure with the phone at 10% and then cry if something goes wrong
A compatible build, read below
A Windows or Linux PC with adb and fastboot drivers installed
Check if your build is compatible:
Go to Settings -> About device -> Version and check Build number:
If your build is between RMX3301_11_A.14 and RMX3301_11_A.21, go to the procedure below
If your build is lower than RMX3301_11_A.14, or higher than RMX3301_11_A.21, install this OTA package to downgrade (or upgrade) to RMX3301_11_A.14
Procedure:
Make sure under Developer options you have OEM unlocking and USB debugging enabled
Download and extract the attached gt2pro_eu_unlock_dirtypipe_v0.2.zip file
Open a terminal in the folder of the extracted files
Connect the phone to the PC and select the File transfer option
Run the script:
On Windows, type run.bat and press enter
On Linux, type ./run.sh and press enter
Now the phone is temporarily rooted and the phone model is changed to RMX3301. Do not reboot or you will lose this status.
At this point you can follow the procedure on the official forum to unlock the bootloader of the global model. If you already have the Deeptesting app installed, clear its data to make sure it will update.
Changelog:v0.2:
Show more info about device for better debug
Show the model at the end to check if it worked
For technical people: how does it work?The script abuses a vulnerability of the Linux kernel called Dirty Pipe (or CVE-2022-0847). For further details, you can visit the official website. This allows us to gain temporary root and overwrite the ro.product.name property, the only one checked by the Deeptesting app. The vulnerability is present in Android and it has been fixed, at least for the Pixel 6, in the May 2022 security update. On the GT 2 Pro, the vulnerability has been fixed with the Android 13 update, while the latest Android 12 build (RMX3301_11_A.21) is still vulnerable. I have tested the procedure personally up to build RMX3301_11_A.16. If you're on a newer build and it doesn't work, please report it in the comments.
Will it work on device X?If the following conditions are met:
it is a Realme device;
the kernel version is 5.10.66;
there's a global model with a different ro.product.name that can be unlocked;
then you can edit the startup-root file and replace RMX3301 (near the end) with the ro.product.name of the global model and try if it works. If it doesn't, it could be for a lot of reasons. Unfortunately, I can't help you without physically having the device in hand.
If you have further questions about the procedure, please post them below.
woowww... thanks for you aport
I wonder if we can use this temporary root to do some modifications on system.
criszz said:
I wonder if we can use this temporary root to do some modifications on system.
criszz said:
I wonder if we can use this temporary root to do some modifications on system.
Click to expand...
Click to collapse
Excellent question... for example try modific the build regist
Click to expand...
Click to collapse
Rapper_skull said:
As you may know, at the time of writing it's not possible to unlock the bootloader of the European model. Fortunately there's a workaround. To know how it works, scroll to the end of the post.
First of all, this is only for the European RMX3301, but you can try on any other global model that doesn't allow the unlocking of the bootloader. I'm not talking about temporary errors, but of the infamous This phone model does not support deep testing error message.
Before starting I would like to thankpolygraphene for their implementation of the Dirty Pipe vulnerability on Android. Without that, this would not have been possible.
Requirements:
The phone with a decent charge. Do not attempt this procedure with the phone at 10% and then cry if something goes wrong
A compatible build, read below
A Windows or Linux PC with adb and fastboot drivers installed
Check if your build is compatible:
Go to Settings -> About device -> Version and check Build number:
If your build is RMX3301_11_A.14, RMX3301_11_A.15 or RMX3301_11_A.16, go to the procedure below
If your build is lower than RMX3301_11_A.14, or higher than RMX3301_11_A.16, install this OTA package to downgrade (or upgrade) to RMX3301_11_A.14
Procedure:
Make sure under Developer options you have OEM unlocking and USB debugging enabled
Download and extract the attached gt2pro_eu_unlock_dirtypipe.zip file
Open a terminal in the folder of the extracted files
Connect the phone to the PC and select the File transfer option
Run the script:
On Windows, type run.bat and press enter
On Linux, type ./run.sh and press enter
Now the phone is temporarily rooted and the phone model is changed to RMX3301. Do not reboot or you will lose this status.
At this point you can follow the procedure on the official forum to unlock the bootloader of the global model. If you already have the Deeptesting app installed, clear its data to make sure it will update.
For technical people: how does it work?
The script abuses a vulnerability of the Linux kernel called Dirty Pipe (or CVE-2022-0847). For further details, you can visit the official website. This allows us to gain temporary root and overwrite the ro.product.name property, the only one checked by the Deeptesting app. The vulnerability is present in Android and it has been fixed, at least for the Pixel 6, in the may 2022 security update. At the time of writing, the latest build for the GT2 Pro is RMX3301_11_A.16, and it's still vulnerable.
If you have further questions about the procedure, please post them below.
Click to expand...
Click to collapse
When you try the procedure... delete al date of phone? whe finish---- type run.bat and press enter ---- erase all?
criszz said:
I wonder if we can use this temporary root to do some modifications on system.
Click to expand...
Click to collapse
Theoretically you can do everything you can do on a rooted phone (Magisk, but without modules and Zygisk). In practice I never got Magisk to work properly, so I just limited myself to change the property. My goal was to unlock the bootloader, so I did it and installed Magisk.
manu81cba said:
When you try the procedure... delete al date of phone? whe finish---- type run.bat and press enter ---- erase all?
Click to expand...
Click to collapse
My procedure will not delete any data, but after that you have to follow the official procedure to unlock the bootloader, and that will factory reset your phone.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I have this error... why?
manu81cba said:
View attachment 5634133
I have this error... why?
Click to expand...
Click to collapse
Can you post the output of adb devices?
Rapper_skull said:
Can you post the output of adb devices?
Click to expand...
Click to collapse
You can explain? no understand.. what do you say?
manu81cba said:
You can explain? no understand.. what do you say?
Click to expand...
Click to collapse
In the terminal, where you are, type adb devices and press enter, then post the output.
Rapper_skull said:
In the terminal, where you are, type adb devices and press enter, then post the output.
Click to expand...
Click to collapse
manu81cba said:
View attachment 5634133
I have this error... why?
Click to expand...
Click to collapse
Yes i have same output on A.16 installed.
manu81cba said:
View attachment 5634153
Click to expand...
Click to collapse
I can see that you have two different versions of adb, one inside the platform-tools folder and one installed elsewhere. Please confirm that by running adb version inside platform-tools and then outside.
Rapper_skull said:
In the terminal, where you are, type adb devices and press enter, then post the output.
Click to expand...
Click to collapse
now put all file decripted to plataform adb... and this result... all ok?
manu81cba said:
now put all file decripted to plataform adb... and this result... all ok?
View attachment 5634159
Click to expand...
Click to collapse
Yes. To make sure, run adb getprop ro.product.name and confirm it's RMX3301.
manu81cba said:
now put all file decripted to plataform adb... and this result... all ok?
View attachment 5634159
Click to expand...
Click to collapse
Working now?
Is rooting temporary? i can modific build.pro? or this process is only for change the model propety?
manu81cba said:
Working now?
Is rooting temporary? i can modific build.pro? or this process is only for change the model propety?
Click to expand...
Click to collapse
No, you can't modify any files, since /system is read-only. Even if you manage to do it, you will brick your device since the bootloader is still locked. If you want to unlock your bootloader, follow the official guide I've linked.
Rapper_skull said:
Yes. To make sure, run adb getprop ro.product.name and confirm it's RMX3301.
Click to expand...
Click to collapse
manu81cba said:
View attachment 5634169
Click to expand...
Click to collapse
Sorry, adb shell getprop ro.product.name
Its taken me a while to figure out a way to bypass the FRP (Factory Reset Protection) Lock on my Huawei EVA-L09 and do so while not bricking my device or installing shady software/roms so if this helps I hope you leave me a like and comment how long its taken you before you found this guide.
Its completely free as I refuse to pay money which I hope you appreciate as every other guide wants you to pay to unlock a device so no matter what level of skills you are this should help you to gain access to you're Huawei EVA-L09 and other models (I've also used this method on a Huawei P Smart (FIG) but this should also work on all the devices listed in the table below)
DeviceModelBootloaderHuawei P8 Lite (2015)ALEKirin 620Huawei Y6IICAMKirin 620Honor 5C / 7 LiteNEMKirin 65x (A)Honor 7XBNDKirin 65x (A)Honor 9 LiteLLDKirin 65x (A)Huawei MediaPad T5AGS2Kirin 65x (A)Huawei Nova 2PICKirin 65x (A)Huawei P10 LiteWASKirin 65x (A)Huawei P20 Lite / Nova 3eANEKirin 65x (A)Huawei P8 Lite (2017)PRAKirin 65x (A)Huawei P9 LiteVNSKirin 65x (A)Huawei Y9 (2018)FLAKirin 65x (A)Huawei MediaPad M5 LiteBAH2Kirin 65x (B)Huawei Nova 2i / Mate 10 LiteRNEKirin 65x (B)Huawei P Smart 2018FIGKirin 65x (B)Honor 6 PlusPEKirin 925Huawei P8GRAKirin 935Honor 8 Pro / V9DUKKirin 950Honor 8FRDKirin 950Huawei P9 StandartEVAKirin 950Honor 9STFKirin 960Huawei Mate 9 ProLONKirin 960Huawei Mate 9MHAKirin 960Huawei MediaPad M5CMRKirin 960Huawei Nova 2sHWIKirin 960Huawei P10VTRKirin 960
First download and extract the Android SDK Platform-Tools package for windows from -> https://developer.android.com/studio/command-line/adb
Next download drivers from -> https://adb.clockworkmod.com/ and run .exe file
Next go to -> https://github.com/mashed-potatoes/PotatoNV and read through the entire page and follow the steps to install HiSuite, test point drivers and latest version of PotatoNV and find out where you're test point are on you're device and learn how to use the tool
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Open PotatoNV and click disable FBlock and choose you're bootloader (refer to list on GitHub Repo) in my case for the Huawei EVA-L09 it was the Kirin 950 and follow the repo instructions to ground you're test point while inserting you're USB, now the target device field should show you're device then click start! and If you've followed the steps correctly then congrats you've generated a new bootloader code and got the following display.
Click to expand...
Click to collapse
From the display write down the "New Unlock Code" + "Build number" for later
Click to expand...
Click to collapse
Now we need the firmware to flash
Go to -> http://huawei-firmware.com/phone-list/ to find you're compatible firmware
Click to expand...
Click to collapse
My build number was "EVA-L09C02B363" so on the site I searched for that build number but found nothing so I removed 1 character from the end "EVA-L09C02B36" and found 2 results for "Huawei P9 EVA-L09C02B361 Firmware"
If you cant find a result keep removing 1 character from the end of you're build number until you can find the closet build to yours and Download it
Boot phone into fastboot mode
In the Android SDK Platform-Tools package folder hold In "CTRL + Shift" and Right click in the folder and click the option "open PowerShell window here"
In PowerShell type the following command "./fastboot oem unlock YOUR_CODE_HERE"
Press the volume key to select unlock bootloader on you're phone and press the power button (Now you've unlocked you're bootloader)
Download the firmware and extract the files and move the entire Dload folder to an SDcard (rename the SDcard SDcard) and insert it into you're device
Now boot the phone with both volume buttons pressed down and power button and let it install the new firmware
Click to expand...
Click to collapse
I personally had an error at 99% of install doing it this way so I had to manually flash each partition if you have the same issue then follow the steps
Download the tool Huaweiupdateextract tool -> https://www.leakite.com/flash-huawei-ota-update-without-sdcard/
Click to expand...
Click to collapse
And click "click", now browse for the update.app file inside the Dload folder and right click on the files and click extract all and save them into the Android SDK Platform-Tools package folder you extracted earlier
Boot phone into fastboot mode
Click to expand...
Click to collapse
Now you need to manually flash every .img file you extracted to the corresponding partition, all the .img files are saved in CAPSLOCK and the corresponding partition you need to flash to is the file name in all lowercase minus the .img part so for example the file RECOVERY.img needs to be flashed to the recovery partition and USERDATA.img to userdata and so on
In the same Powershell Window from earlier type "./fastboot flash *partition" "PARTITION.img" and replace partition with every img you extracted, example for USERDATA.img: "./fastboot flash userdata USERDATA.img"
Some flash's may fail, just move on to the next
Then type "./fastboot reboot"
Click to expand...
Click to collapse
And now skip through everything and access you're phone, I then personally booted my phone into Erecovery and clicked Install firmware and recovery and signed into my wifi after downloading I opened my phone and inserted my sim card (in my case it was lyca mobile and after the phone accepts the sim you will be prompted to take the system update, I flashed build EVA-L09C02B361 to my device but now I can update to my original build number EVA-L09C02B363.
Hopefully if you followed everything correctly you've just bypassed FRP.
You're welcome as someone who dosent have a lot to spend on tech I really value this sort of information and hopefully this full guide can help even a beginner gain access to there bricked phone.
Let me know if this helps!
doesn't work on Huawei Y6II CAM-L21 ..
kalinx said:
doesn't work on Huawei Y6II CAM-L21 ..
Click to expand...
Click to collapse
Did you ground the test point while clicking start?
brokeboy said:
Did you ground the test point while clicking start?
Click to expand...
Click to collapse
yes, in many ways i try it but this doesn't work too
kalinx said:
yes, in many ways i try it but this doesn't work too
Click to expand...
Click to collapse
Can you run it without Fblock and then run again with it ticked?
Yes I was struggling with it yesterday all day, in many ways. Now I get off. I will buy Sony Xperia M4 aqua with very easy root, I get unlock code from Sony website. Damn you HUAWEI! :/
kalinx said:
Yes I was struggling with it yesterday all day, in many ways. Now I get off. I will buy Sony Xperia M4 aqua with very easy root, I get unlock code from Sony website. Damn you HUAWEI! :/
Click to expand...
Click to collapse
Can you explain every step you did before to get to that point, also what's wrong with you're device?
Can this process work on Honor 10 col l29? He has kirin 970. Thank you.
levis36 said:
Can this process work on Honor 10 col l29? He has kirin 970. Thank you.
Click to expand...
Click to collapse
If its not on the list then it isn't supported but I believe if you look through the repo maybe someone forked it or there might be an alternative... I typed in honor in the questions and found this but there could be more
I solved it by changing the motherboard. I bought a phone with a broken display, 4 €, I changed the card and it did not have a lock on the screen and I entered the settings, return to the factory settings and everything goes ok. The new motherboard has emui 10.0.0 4 / 64gb and the old one was emui 8.1 which I failed to unlock I don't know the specifications it had. I would have liked to unlock the other one can have 6 / 128g.
levis36 said:
I solved it by changing the motherboard. I bought a phone with a broken display, 4 €, I changed the card and it did not have a lock on the screen and I entered the settings, return to the factory settings and everything goes ok. The new motherboard has emui 10.0.0 4 / 64gb and the old one was emui 8.1 which I failed to unlock I don't know the specifications it had. I would have liked to unlock the other one can have 6 / 128g.
Click to expand...
Click to collapse
Well done, that's good way to get past it... What phone did you take the motherboard from? Did you not find any info on how to use the bootloader unlocker with you're Honor 10 COL-L29 (Kirin 970)?
I tried 3 methods and none of them worked, they were all restricted, I got to a point and I couldn't move on.
Hi, I have a mate 9 with FRP and Bootloader locked, and when I try to unlock bootloader via fastboot, I have a warning telling that FRP needs to be unlocked first. Do you have any suggestiong?
Well, I did it at last After I have done this here and got no FRP bypass, I continued to google because this is weird, being able to run ADB/Fastboot commands, but unable to remove damn FRP. I have found this tool and it worked:
Download Huawei FRP and ID remove Tool For PC
Download Huawei FRP and ID remove Tool For PC if you want to bypass FRP lock google account from Huawei/Honor mobile
huaweiflash.com
So I can now thank the author for this guide, although unclear in some parts, then it has led finally to success. I have spent a couple of hours yesterday trying that bypass from the device (each and every method to start Youtube/Chrome/Maps/Google vie Talkback is already blocked as of now). Then a couple of hours for this guide. I could have purchased me an open phone instead of cracking this one but I wanted to play with some Huawei without having to pay anything.
There were unclear point in the guide, I elaborate
- to start fastboot mode: keep Volume down pressed and connect USB cable.
- you don't need specifically powershell, command line works as well
- the reflash is done from 32GB FAT32 formatted card named SDCARD which contained the unpacked folder dload with firmware files (SDCARD:/dload/<files>)
---initial comment---
EVA-L09 here.
Well, the procedure as described does not remove FRP lock.
PotatoNV worked, oem unlock command went through as well, but... Fastboot screen shows "FRP Lock" in green before the "oem unlock" command run; after the command and subsequent lowlevel reset; and after reflash.
The device asks the Google account after boot the same way as before the unlock/reflash.
Maybe the cumbersome way how you reflashed the phone is instrumental to enable FRP bypass (I have found exactly the same software build and my phone updated normally to 100% from SD card).
I have a P9 EVA-L09 device that has FRP locked. i try this method without PC and its work for me