Hey guys,
Since yesterday I was trying to fix this issue but i could not make it.
Before bricking my P20 Pro, i have installed the Android Pie 9 "CLT-L29C432E5R1P7B108" and it was working very well.
Then i tried to install the root via Magisk and I flashed the TWRP but all failed. I was able to boot into the TWRP but later on just stopped. Now I am have screen of Error ," Attention..." similar to this
{
"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 am able only to access to the bootloader , the fastboot commands are working and I flashed many TWRP images successfully (eg. fastboot flash recovery_ramdisk twrp_clt_0.1.img) but without the ability to boot on TWRP.
Phone Unlocked
FRP Unlock
Note: erecovery is working but i am getting this error "Getting package info failed".
My Model : CLT-L29C432
Please help..
I have placed down here some more info from fastboot which may could help,,
*****************
PS C:\adb> fastboot oem get-product-model
(bootloader) CLT-L29
OKAY [ 0.004s]
Finished. Total time: 0.005s
PS C:\adb> fastboot getvar vendorcountry
vendorcountry: hw/eu
Finished. Total time: 0.004s
PS C:\adb> fastboot oem get-build-number
(bootloader) :CLT-L29 9.0.0.108(C432E5R1P7log)
OKAY [ 0.004s]
Finished. Total time: 0.004s
PS C:\adb> fastboot getvar rescue_enter_recovery
getvar:rescue_enter_recovery FAILED (remote: 'FAIL:need all image flashed!')
Finished. Total time: 0.020s
PS C:\adb> fastboot oem oeminforead-SYSTEM_VERSION
(bootloader) :CLT-L29 9.0.0.108(C432E5R1P7log)
OKAY [ 0.005s]
Finished. Total time: 0.006s
PS C:\adb>
*******************
I have the same issue! Mine gets the package, but fails after 1% when it starts the recovery process.
TWRP doesn't have MTP or ADB Sideload support. So I can't push anything to TWRP.
Funkyhuawei eRecovery doesn't work either.
At this point. I'm just waiting for a TWRP update with MTP support.
p.s I seen that the unofficial twrp version supports MTP. I can push files. But that version will NOT mount system. (So its useless)
Anutter226 said:
I have the same issue! Mine gets the package, but fails after 1% when it starts the recovery process.
TWRP doesn't have MTP or ADB Sideload support. So I can't push anything to TWRP.
Funkyhuawei eRecovery doesn't work either.
At this point. I'm just waiting for a TWRP update with MTP support.
p.s I seen that the unofficial twrp version supports MTP. I can push files. But that version will NOT mount system. (So its useless)
Click to expand...
Click to collapse
ATt least your TWRP is working, .. even it is useless.. looking forward for solution..
alfrqan said:
Hey guys,
Since yesterday I was trying to fix this issue but i could not make it.
Before bricking my P20 Pro, i have installed the Android Pie 9 "CLT-L29C432E5R1P7B108" and it was working very well.
Then i tried to install the root via Magisk and I flashed the TWRP but all failed. I was able to boot into the TWRP but later on just stopped. Now I am have screen of Error ," Attention..." similar to this .
I am able only to access to the bootloader , the fastboot commands are working and I flashed many TWRP images successfully (eg. fastboot flash recovery_ramdisk twrp_clt_0.1.img) but without the ability to boot on TWRP.
Phone Unlocked
FRP Unlock
Note: erecovery is working but i am getting this error "Getting package info failed".
Please help..
Click to expand...
Click to collapse
When you've flagged twrp have you disconnected the cable? Remove it before you try to boot to twrp.
Had the same issue myself.
Never seen that before though.
You should never tried rooting pie. It's written everywhere that emui9 is not rootable yet.
For the fix, I would try to flash stock rom via HuRu.
Wipe everything first... /system, /data, /caches
After 3 days, I finally fixed mine.
(Requires unlocked bootloader)
I downloaded the update.zip for my region/version here *MAKE SURE TO CHOSE THE CORRECT REGION*
Used the Huawei update unpack-er to unpack the UPDATE.APP (You can download that here)
Flashed as many of the .img's as possible
At the end I did fastboot erase -w
The phone fails to boot the first time, eRecovery will prompt to format data/factory reset. I did that, it auto rebooted like normal.
SUCCESS!
(A lot of the .img's will say command not allowed. Ignore it an move on flashing the rest)
I think it was because if your modded ram disk. Android pie isn't rootable on huawei phones rn
KennyDumah said:
I think it was because if your modded ram disk. Android pie isn't rootable on huawei phones rn
Click to expand...
Click to collapse
So you should just flash stock boot.img to be able to boot to os again....
Anutter226 said:
After 3 days, I finally fixed mine.
(Requires unlocked bootloader)
I downloaded the update.zip for my region/version here *MAKE SURE TO CHOSE THE CORRECT REGION*
Used the Huawei update unpack-er to unpack the UPDATE.APP (You can download that here)
Flashed as many of the .img's as possible
At the end I did fastboot erase -w
The phone fails to boot the first time, eRecovery will prompt to format data/factory reset. I did that, it auto rebooted like normal.
SUCCESS!
(A lot of the .img's will say command not allowed. Ignore it an move on flashing the rest)
Click to expand...
Click to collapse
I am going to try this. I hope it will work.
Can I know which rom that you have downloaded?
and which commands you have used to flash that .imgs.
side_flip15 said:
You should never tried rooting pie. It's written everywhere that emui9 is not rootable yet.
For the fix, I would try to flash stock rom via HuRu.
Wipe everything first... /system, /data, /caches
Click to expand...
Click to collapse
TWRP is not working and I can not push any file in SD Card. Only fastboot is working..
dladz said:
When you've flagged twrp have you disconnected the cable? Remove it before you try to boot to twrp.
Had the same issue myself.
Never seen that before though.
Click to expand...
Click to collapse
Sounds interesting. will give it a try.
side_flip15 said:
So you should just flash stock boot.img to be able to boot to os again....
Click to expand...
Click to collapse
I download several update.zips and up pack them and so far i could not find this file in :boot.img:
dladz said:
When you've flagged twrp have you disconnected the cable? Remove it before you try to boot to twrp.
Had the same issue myself.
Never seen that before though.
Click to expand...
Click to collapse
can i know which TWRP you have used here?
YellowSnowman23 said:
After 3 days, I finally fixed mine.
(Requires unlocked bootloader)
I downloaded the update.zip for my region/version here *MAKE SURE TO CHOSE THE CORRECT REGION*
Used the Huawei update unpack-er to unpack the UPDATE.APP (You can download that here)
Flashed as many of the .img's as possible
At the end I did fastboot erase -w
The phone fails to boot the first time, eRecovery will prompt to format data/factory reset. I did that, it auto rebooted like normal.
SUCCESS!
(A lot of the .img's will say command not allowed. Ignore it an move on flashing the rest)
Click to expand...
Click to collapse
I have tried this without success. I used to flash imgs by "fastboot flash system xxx.img"
alfrqan said:
TWRP is not working and I can not push any file in SD Card. Only fastboot is working..
Click to expand...
Click to collapse
Unofficial twrp should work. If you have problem with encryption you should format data in twrp.
side_flip15 said:
Unofficial twrp should work. If you have problem with encryption you should format data in twrp.
Click to expand...
Click to collapse
I tried a lot of them.. but still not able to boot into TWRP
alfrqan said:
I am going to try this. I hope it will work.
Can I know which rom that you have downloaded?
and which commands you have used to flash that .imgs.
Click to expand...
Click to collapse
As for rom. I used official Huawei firmware.
Download the correct update.zip for your device.
Unzip it
Put the UPDATE.APP in the Huawei update extractor Make sure in the extractor tool, you go to settings and UNCHECK "Verify header checksum"
Code:
(Ex. system)
fastboot flash system [I]LOCATION_OF_SYSTEM.IMG[/I]
(Ex. recovery_ramdisk)
fastboot flash recovery_ramdisk [I]LOCATION OF RECOVERY_RAMDISK.IMG[/I]
alfrqan said:
can i know which TWRP you have used here?
Click to expand...
Click to collapse
Always unofficial, it's the most functional
Update>>
I have visited Huawei service center in Madrid and they said "there is no way to repair it, you have to change the motherboard". This is ridicules and I dont believe that.
YellowSnowman23 said:
As for rom. I used official Huawei firmware.
Download the correct update.zip for your device.
Unzip it
Put the UPDATE.APP in the Huawei update extractor Make sure in the extractor tool, you go to settings and UNCHECK "Verify header checksum"
Code:
(Ex. system)
fastboot flash system [I]LOCATION_OF_SYSTEM.IMG[/I]
(Ex. recovery_ramdisk)
fastboot flash recovery_ramdisk [I]LOCATION OF RECOVERY_RAMDISK.IMG[/I]
Click to expand...
Click to collapse
hey,
I have downloaded and extracted many official and found the following files unzip file (update.zip):
for system: SYSTEM.img
command: fastboot flash system SYSTEM.img
Result: error: cannot load 'SYSTEM.img'
For RECOVERY_RAMDISK: RAMDISK.img
command:
Result:
target reported max download size of 471859200 bytes
sending 'recovery_ramdisk' (16384 KB)...
OKAY [ 0.369s]
writing 'recovery_ramdisk'...
OKAY [ 0.140s]
finished. total time: 0.509s
conc. still not booting only fastboot commands,,,,,,
Related
Hello everybody, for serveral months i saw several people asking help to back to stock ROM
here we finally have a guide that saved me and can save you!
Requirements:
Windows operative system
Multi Tool
OFFICIAL stock rom (in this guide i'll use B370 for H60-L04) Download
and the most important thing Huawei Update Extractor! Download
and let's go!
First of all open HUE (Huawei Update Extractor) and after selected UPDATE.APP file, extract system.img , boot.img , cust.img, recovery.img that we will flash on the phone, and put them in the folder where adb and fastboot are installed (in this case we use the multi tool directory).
now open cmd or command prompt and move on multi tool directory (cd C:\\Users\NAME bla bla bla\DIRECTORY TO MULTI TOOL)
now plug in your phone and enable Debug USB and type:
Code:
adb.exe devices (to control if your device is online, if not grant the permission on the phone)
adb.exe reboot bootloader
Now we flash all the files with fastboot
the order of commands doesn't matter
(MAKE SURE THAT YOU HAVE SYSTEM, BOOT, RECOVERY AND CUST .img ON THE MAIN FOLDER!)
Code:
fastboot.exe flash boot BOOT.img
fastboot.exe flash recovery RECOVERY.img
fastboot.exe flash cust CUST.img
fastboot.exe flash system SYSTEM.img
than reboot into recovery by doing
fastboot.exe reboot and holding only VOLUME UP button
than do all the wipe (cache and data) than reboot system
Easy right? :laugh:
TheTigerDeveloper said:
Hello everybody, for serveral months i saw several people asking help to back to stock ROM
here we finally have a guide that saved me and can save you!
Requirements:
Windows operative system
Multi Tool
OFFICIAL stock rom (in this guide i'll use B370 for H60-L04) Download
and the most important thing Huawei Update Extractor! Download
and let's go!
First of all open HUE (Huawei Update Extractor) and after selected UPDATE.APP file, extract system.img , boot.img , cust.img, recovery.img that we will flash on the phone, and put them in the folder where adb and fastboot are installed (in this case we use the multi tool directory).
now open cmd or command prompt and move on multi tool directory (cd C:\\Users\NAME bla bla bla\DIRECTORY TO MULTI TOOL)
now plug in your phone and enable Debug USB and type:
Code:
adb.exe devices (to control if your device is online, if not grant the permission on the phone)
adb.exe reboot bootloader
Now we flash all the files with fastboot
the order of commands doesn't matter
(MAKE SURE THAT YOU HAVE SYSTEM, BOOT, RECOVERY AND CUST .img ON THE MAIN FOLDER!)
Code:
fastboot.exe flash boot BOOT.img
fastboot.exe flash recovery RECOVERY.img
fastboot.exe flash cust CUST.img
fastboot.exe flash system SYSTEM.img
than reboot into recovery by doing
fastboot.exe reboot and holding only VOLUME UP button
than do all the wipe (cache and data) than reboot system
Easy right? :laugh:
Click to expand...
Click to collapse
Thanks for the guide! I used to follow the same procedure too but another alternative is to use multi-tool and use the unbrick option and follow the instructions. It super noob friendly:highfive:
shubham1120 said:
Thanks for the guide! I used to follow the same procedure too but another alternative is to use multi-tool and use the unbrick option and follow the instructions. It super noob friendly:highfive:
Click to expand...
Click to collapse
i know, but with this one any type of user can follow the guide (especially linux user)
my phone keep restarting, i have try this method, no works, helpppppppp
it stuck on honor logo
Hi Guys,
i got the same problem here with my H60-L12
After flashing Beta Lollipop 5.1.1 i tried to go back to 4.4.4.
Now it's stuck in bootloop and now it keeps flashing the honor logo.
Tried to unbrick it with Multi-Tool and different stock roms but i cant get into recovery or the 3 button install method, only thing working is fastboot mode.
Any suggestions?
Thank you!!
ok, now i'm desperate.
Got different Stock Roms (4.4 5.8.1;4.4 B119;4.4 B310; 4.4 B316, tried TWRP in different versions, even tried to reinstall fastboot drivers , same problem on Windows 10 and 7.
Only think working is Fastboot&Rescue Mode (White Screen, Phone UNLOCKED), but only when plugged in on PC with USB cable.
When plugged in charger, it just reboots and reboots i can't switch to Recovery or Fastboot mode and doesn't even charge the phone.
Maybe someone got any idea, did i use wrong stock roms? Do i have to use Rollback/Revert versions?
Any way to back to stock rom without unlock bootloader?
I've made a horrible mistake.
I was on 5.9.16, tried to downgrade by flashing system, recovery, cust and crc.
Unfortunately I've done it with B316, which is 4.4.4, so i got this annoying bootloop, in which i can't access recovery, bootloader or use the 3 buttons method.
It seems as if the phone tries to forcefully boot into system ignoring everything I do.
I tried draining the battery to turn it off, which worked, but when i charged it it tried to system boot as soon as there's enough battery.
Any ideas?
and where can I find update.app?
This worked for me! I switched from CM11 to the stable 5.1.1 release using your guide. Flashed B370 and then did a local update for the stable lollipop rom. Thanks a ton.
i need help
I extract listed file and open cmd.
I was able to reboot into bootloader.
I writing "fastboot.exe flash boot BOOT.img" and here is the result:
target reported max download size of 471859200 bytes
sending 'boot' (7754 KB)...
OKAY [ 0.810s]
writing 'boot'...
FAILED (remote: Command not allowed)
finished. total time: 0.820s
Whats now?
I have rooted H60-L04 with cyanogenmod 11-20150822 KitKat
Thanks
Michal
yeah, very easy guide
i did to my H60-L04 CM11
thanks for sharing
error
target reported max download size of 471859200 bytes
sending 'boot' (7754 KB)...
OKAY [ 0.810s]
writing 'boot'...
FAILED (remote: Command not allowed)
finished. total time: 0.820s
i couldnot flash stock recovery because of the fail command not alowed,
i couldnot flash stock recovery because of the fail command not alowed,
Thank you so much! Now my phone is bricked... How about not sharing ur help when u don't know what could happen?
My phone shows Rescue Mode
Attention! Please update system again!
Error!
FuncNo (FUNC_BOOT_KERNEL)
Error NO: 2
i couldnot flash stock recovery because of the fail command not alowed,
i couldnot flash stock recovery because of the fail command not alowed,
thalaraj1992 said:
i couldnot flash stock recovery because of the fail command not alowed,
Click to expand...
Click to collapse
are you on a boot loop?
make sure your device is recognized by your computer.
download universal-adb-driver for windows and install
Hello Guys,
Now it s finally here
working root for ze550kl, a very big thanks to @shakalaca,
he developed this, full credit goes to him. :fingers-crossed:
Version 1.15.40.639
original thread source
http:// www.asus.com/zentalk/tw/forum.php?mod=viewthread&tid=111151&extra=page=1
Before starting root procedure make sure that you have backup all installed apks, in order to avoid apk update after installing patched firmware, as it consume more bandwidth & time.
Steps to Root
1- Download the full version of firmware patch: new version folder 1.15.40.639.
https://mega.nz/#F!lodnzDhK!H5ChxausDTyko1qGlnF7dw!Fg9FwLoa
2- Descompress system.img.7z with 7zip program
3- Copy the boot.img / system.img / recovery.img to (adb/fastboot) folder.
4- Execute this commands in sequence:
-adb device
-adb reboot bootloader
-fastboot devices
-fastboot erase userdata
-fastboot erase cache
-fastboot flash boot boot.img
-fastboot flash recovery recovery.img
-fastboot flash system system.img
It will take some time to finish approx 10 min, let it finish
-fastboot reboot
first time, it will take more time than usual, as it will build cache, if stuck more than 15 minute, remove battery & charging (if charging) & after insert battery after 2 min, go to recovery mode, wipe factory/data, erase cache, reboot system.
It will take some time to restart be patient.
now you do not need to install any super user it s already there.
Enjoy,
@shakalaca thanks again
Tried & working well
adaway .
busy box
titanium backup
root explorer
working xposed may be find here
http://forum.xda-developers.com/zenfone-2-laser/general/wroking-xposed-ze550kl-t3247915
Hope you will enjoy.
Press thanks, if it helps you
I hope some day we will get CM or AOSP rom
codejam100 said:
I hope some day we will get CM or AOSP rom
Click to expand...
Click to collapse
yes hope so, but for that we need unlock bootloader, which is not possible till yet.
rajlko said:
Hello Guys,
Now it s finally here
working root for ze550kl, a very big thanks to @shakalaca,
he developed this, full credit goes to him. :fingers-crossed:
Version 1.15.40.639
original thread source
http:// www.asus.com/zentalk/tw/forum.php?mod=viewthread&tid=111151&extra=page=1
Before starting root procedure make sure that you have backup all installed apks, in order to avoid apk update after installing patched firmware, as it consume more bandwidth & time.
Steps to Root
1- Download the full version of firmware patch: new version folder 1.15.40.639.
https://mega.nz/#F!lodnzDhK!H5ChxausDTyko1qGlnF7dw!Fg9FwLoa
2- Descompress system.img.7z with 7zip program
3- Copy the boot.img / system.img / recovery.img to (adb/fastboot) folder.
4- Execute this commands in sequence:
-adb device
-adb reboot bootloader
-fastboot devices
-fastboot erase userdata
-fastboot erase cache
-fastboot flash boot boot.img
-fastboot flash recovery recovery.img
-fastboot flash system system.img
It will take some time to finish approx 10 min, let it finish
-fastboot reboot
first time, it will take more time than usual, as it will build cache, if stuck more than 15 minute, remove battery & charging (if charging) & after insert battery after 2 min, go to recovery mode, wipe factory/data, erase cache, reboot system.
It will take some time to restart be patient.
now you do not need to install any super user it s already there.
Enjoy,
@shakalaca thanks again
Tried & working well
adaway .
busy box
titanium backup
root explorer
working xposed may be find here
http://forum.xda-developers.com/zenfone-2-laser/general/wroking-xposed-ze550kl-t3247915
Hope you will enjoy.
Press thanks, if it helps you
Click to expand...
Click to collapse
Sir.
What new in this ? And
Can we use some of the file like system. 001 orr 002 of before zip means of build 496.,or we have to download all these again.
harshk60 said:
Sir.
What new in this ? And
Can we use some of the file like system. 001 orr 002 of before zip means of build 496.,or we have to download all these again.
Click to expand...
Click to collapse
【Version】
V1.15.40.639
【Model Name】
ZenFone 2 Laser (ZE550KL)
【Release Date】
2015/11/10
【Release Note】
1 Imrpoved phone call quality.
2 Improved photo quality in HDR mode.
3 Fine-tune camera image detail and noise improvement.
4 Updated camera shutter/focus animation and improve shooting speed.
# New Features
1 Camera shutter up to 32 seconds in Manual mode.
2 Add ZenFlash App, the first external Xenon Flashlight for mobile devices.
It can fulfill the demand of professional photographers in rendering dark detail and strengthen delicate sense.
At present we do not have dedicated developers, so we need to download all image files every times we got new working root for new update.
rajlko said:
【Version】
V1.15.40.639
【Model Name】
ZenFone 2 Laser (ZE550KL)
【Release Date】
2015/11/10
【Release Note】
1 Imrpoved phone call quality.
2 Improved photo quality in HDR mode.
3 Fine-tune camera image detail and noise improvement.
4 Updated camera shutter/focus animation and improve shooting speed.
# New Features
1 Camera shutter up to 32 seconds in Manual mode.
2 Add ZenFlash App, the first external Xenon Flashlight for mobile devices.
It can fulfill the demand of professional photographers in rendering dark detail and strengthen delicate sense.
At present we do not have dedicated developers, so we need to download all image files every times we got new working root for new update.
Click to expand...
Click to collapse
Ok thnx.
Phone protected.....??
I downloaded these files and The CACHE and USERDATA got deleted,
but when I tried to flash the boot.img and recovery.img with fastboot, in both cases got the message:
FAILED (remote: Permission denied, phone is protected).
I did not even try to flash the system.img
Then when I did a fastboot reboot, I just got the ASUS screen with a spinning wheel during boot.
IDEAS?
bert269 said:
I downloaded these files and The CACHE and USERDATA got deleted,
but when I tried to flash the boot.img and recovery.img with fastboot, in both cases got the message:
FAILED (remote: Permission denied, phone is protected).
I did not even try to flash the system.img
Then when I did a fastboot reboot, I just got the ASUS screen with a spinning wheel during boot.
IDEAS?
Click to expand...
Click to collapse
please share cmd log & build number you are using.
rajlko said:
please share cmd log & build number you are using.
Click to expand...
Click to collapse
Build 1.15.40.639
And here is the cmd log:
C:\adb>adb devices
List of devices attached
F9AZCY251451 device
C:\adb>adb reboot bootloader
C:\adb>fastboot devices
F9AZCY251451 fastboot
C:\adb>fastboot erase userdata
******** Did you mean to fastboot format this partition?
erasing 'userdata'...
OKAY [ 1.084s]
finished. total time: 1.084s
C:\adb>fastboot erase cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.011s]
finished. total time: 0.011s
C:\adb>fastboot flash boot boot.img
target reported max download size of 268435456 bytes
sending 'boot' (24545 KB)...
OKAY [ 0.772s]
writing 'boot'...
FAILED (remote: Permission denied, phone is protected)
finished. total time: 0.773s
C:\adb>fastboot flash recovery recovery.img
target reported max download size of 268435456 bytes
sending 'recovery' (26507 KB)...
OKAY [ 0.833s]
writing 'recovery'...
FAILED (remote: Permission denied, phone is protected)
finished. total time: 0.834s
C:\adb>fastboot reboot
rebooting...
finished. total time: 0.001s
C:\adb>
Thank you!
bert269 said:
Build 1.15.40.639
And here is the cmd log:
C:\adb>fastboot reboot
rebooting...
finished. total time: 0.001s
C:\adb>
Thank you!
Click to expand...
Click to collapse
Please share your exact model number & current build you have in your phone.
Setting>about device
like z00ld, 1.13.40.496 or 1.15.40.639.
rajlko said:
Please share your exact model number & current build you have in your phone.
Setting>about device
like z00ld, 1.13.40.496 or 1.15.40.639.
Click to expand...
Click to collapse
Model: Z00TD
Baseband: 202c10_10.0.0_151008
Build: LRX22G.WW_user_1.15.40.639_20151029
044030520_201505210103
001000200001
bert269 said:
Model: Z00TD
Baseband: 202c10_10.0.0_151008
Build: LRX22G.WW_user_1.15.40.639_20151029
044030520_201505210103
001000200001
Click to expand...
Click to collapse
you having issue because of different model number, this root is for z00ld.
Thanx..
Works Perfect for me..root and xpose both
rajlko said:
you having issue because of different model number, this root is for z00ld.
Click to expand...
Click to collapse
Oooooops, sorry.
Thanks!
Have a little problem there, after flashing, all was ok, but the first turning still lasts more then 20 minutes. How can i enter recovery mode?
UPD:
You can enter Recovery by pressing volume dn + power or by fastboot oem reboot-recovery
fastboot mode zenfone laser 2? how? it has no volume buttons? (zenfone 2 Qualcom Snapdragon unit here)
asukaragnaboy said:
fastboot mode zenfone laser 2? how? it has no volume buttons? (zenfone 2 Qualcom Snapdragon unit here)
Click to expand...
Click to collapse
As a first time ZenFone user, this baffled me too.
{
"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"
}
xyberz09 said:
As a first time ZenFone user, this baffled me too.
Click to expand...
Click to collapse
hahaha!! So that's what it is, i thought it's just a design or something.. Thanks man..
---------- Post added at 10:40 AM ---------- Previous post was at 10:39 AM ----------
I have another question, do I need to make the zenfone laser goto fastboot, so I could determine if it's in ADB mode? and see it if it's in my device manager lists?
asukaragnaboy said:
hahaha!! So that's what it is, i thought it's just a design or something.. Thanks man..
---------- Post added at 10:40 AM ---------- Previous post was at 10:39 AM ----------
I have another question, do I need to make the zenfone laser goto fastboot, so I could determine if it's in ADB mode? and see it if it's in my device manager lists?
Click to expand...
Click to collapse
If you only need to connect to it using ADB, you don't need to enter fastboot. Just enable USB Debugging in Developer Options and connect it to your computer using a USB cable. You must have ASUS USB drivers installed prior to doing this and just MAYBE you need to boot your Windows PC with TESTSIGNING on (I don't know if it works with it off. I always have it enabled).
Run the
Code:
adb devices
command and it should show.
Thanks for the inquiry, I'll be trying that later
I have bricked my A2 today. I first unlocked the bootloader then insatlled GCAM.
everything was fine, but i tried to install XPOSED (sdk 27) from Magisk module, then rebooted from magisk. My set is stuck at android one animation.
I downloaded official firmware of A2 and tried to flash via mi flash tool, always gets an error of "FLASH_DEVCFG_A ERROR" . Then i tried by clicking on "flash_all_except_data.bat" file, cmd just opened and closed very soon, Same thing happended with "flash_all_lock.bat" ,again cmd just opened and closed.
Still my phone is stuck at Android one animation, and i cant flash or boot my set.
EDIT :: USED. /FASTBOOT -W TO UNBRICK PHONE
Just follow this instructions on the link bellow.
https://forum.xda-developers.com/showpost.php?p=77302899&postcount=4
minnuss said:
Just follow this instructions on the link bellow.
https://forum.xda-developers.com/showpost.php?p=77302899&postcount=4
Click to expand...
Click to collapse
should i flash only those images? because i have some more image files than the llist, kindly check the screen shot
minnuss said:
Just follow this instructions on the link bellow.
https://forum.xda-developers.com/showpost.php?p=77302899&postcount=4
Click to expand...
Click to collapse
Now stuck at devcfg
PS C:\Users\KSN\Desktop\platform-tools> fastboot flash devcfg_b C:\Users\KSN\Desktop\images_V9.6.10.0.ODIMIFE_8.1\images\devcfg.img
target reported max download size of 536870912 bytes
sending 'devcfg_b' (47 KB)...
OKAY [ 0.005s]
writing 'devcfg_b'...
FAILED (remote: Flashing is not allowed for Critical Partitions
)
finished. total time: 0.007s
bluetooth_a , bluetooth_b was flashed successfully
try fastboot flashing unlock_critical
munchy_cool said:
try fastboot flashing unlock_critical
Click to expand...
Click to collapse
This appears everytime . :/
{
"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"
}
Syed Shahriar said:
This appears everytime . :/View attachment 4581400
Click to expand...
Click to collapse
xposed would have not messed with those partitions. did you flash system partition yet?
if not just flash system, vendor and boot
once you have flashed those, do fastboot -w (will loose all data).
and then reboot
fastboot reboot
munchy_cool said:
xposed would have not messed with those partitions. did you flash system partition yet?
if not just flash system, vendor and boot
once you have flashed those, do fastboot -w (will loose all data).
and then reboot
fastboot reboot
Click to expand...
Click to collapse
i just flashed bluetooth_a, bluetooth_b, and then went to devcf_a, failed , and did nothing else.
and what will be the command to flash system, vendor and boot ? kindly give me an example please
Syed Shahriar said:
i just flashed bluetooth_a, bluetooth_b, and then went to devcf_a, failed , and did nothing else.
and what will be the command to flash system, vendor and boot ? kindly give me an example please
Click to expand...
Click to collapse
GOT THESE ERROR::
PS C:\adb> fastboot flash system_a C:\adb\images\system.img
error: cannot load 'C:\adb\images\system.img'
my system iso is there in that location
but successfuly done fastboot flash vendor_b C:\adb\images\vendor.img
and fastboot flash vendor_a C:\adb\images\vendor.img
What are you even doing with all those commands
You need to download latest ADB, that is the first that you need to do, and second, copy all of the images from stock rom to your adb folder, it will be easier for commands to work.
And then start your cmd.exe with administrative privileges (right click on cmd in search bar of windows start, and "run as administrator").
Then move yourself from directory to your adb directory with commands from DOS, like "cd.." for going back from directory, and "cd nameofdir" to go into directory.
So move yourself in adb directory, then type the commands from the upper link to flash those .img one by one.
Oh yes, one other thing, you need to check if you see your mobile device in fastboot, did you install correct drivers.
When you are in adb folder, in cmd type fastboot devices, and you should see your mobile connected, if not, then you can type all you want, the phone is not recognized with pc connection.
Right, so... follow this guide to make sure you've unlocked your bootloader successfully. After you've finished, also add in the command "fastboot flashing unlock_critical". I'm not sure why it didn't work for you in the first place - but I know for a fact it works, because I did it to my own A2.
Make sure you've installed adb/drivers as attached by that link above. Why? 'Cause that's what I did, so I know it should work.
Then go here, extract the files to the same folder as platform-tools (the adb and fastboot tools folder), and run flash-all.bat.
Hey bro i do it too, tô solve, just do a fastboot unlock_critical
https://forum.xda-developers.com/mi-a2/how-to/mi-a2-toolkit-unlock-bootloader-root-t3834585
I had the same issue, no OS installed.
Adb Sideload and OTG didn't worl no matter what I tried.
I followed this thread, and it worked properly without errors, not even one.
It took me 5 minutes to recover my dead MiA2 device to a smooth original/official ROM built.
Locled OEM, rebooted the device and everything is working perfectlt.
Thank you all for the info.
Hi, I'm writing this to guide those who faced - and will face similar situation in the future - the problem of being stuck on the fastboot screen, where the recovery or booting in EDL is not available.
So, after failing to get root after upgrading to android 10 I was fiddling with TWRP to try to get it to recognize my storage so I can reflash it and flash Magisk, but I couldn't get it to mount the storage, so my stupid brain decided to go to the wipe page and wiped everything in the hope it might magically work!! well.. it didn't!! and I got stuck in the fastboot screen and I thought that I bricked my phone for good.
after hours of searching online and trying everything nothing helped... but finally I managed to fix it.
and btw when I tried to flash TWRP by (fasboot boot twrp.img) I got the following message:
"remote: Failed to load/authenticate boot image: Load Error"
So here is what I did to get my phone working again:
Download and install Tool All in One
Download Fastboot ROM for your phone from here
In the Tool All in One app click on the Flash Factory Images button.
Select the ROM and let it do its work,
hopefully this will work and your device will reboot into a fresh android.
Also it's good to know that the official TWRP of twrp.me does not support Android Q at the moment, that's why you couldn't decrypt and mount the storage. TWRP in Oneplus 7 Pro thread here on XDA does support Q, you just have to remember to boot into the inactive/upgraded slot before booting back to TWRP to flash Magisk as it only installs to the active slot and not the upgraded slot.
Skickat från min GM1913 via Tapatalk
vegatr0n said:
Hi, I'm writing this to guide those who faced - and will face similar situation in the future - the problem of being stuck on the fastboot screen, where the recovery or booting in EDL is not available.
So, after failing to get root after upgrading to android 10 I was fiddling with TWRP to try to get it to recognize my storage so I can reflash it and flash Magisk, but I couldn't get it to mount the storage, so my stupid brain decided to go to the wipe page and wiped everything in the hope it might magically work!! well.. it didn't!! and I got stuck in the fastboot screen and I thought that I bricked my phone for good.
after hours of searching online and trying everything nothing helped... but finally I managed to fix it.
and btw when I tried to flash TWRP by (fasboot boot twrp.img) I got the following message:
"remote: Failed to load/authenticate boot image: Load Error"
So here is what I did to get my phone working again:
Download and install Tool All in One
Download Fastboot ROM for your phone from here
In the Tool All in One app click on the Flash Factory Images button.
Select the ROM and let it do its work,
hopefully this will work and your device will reboot into a fresh android.
Click to expand...
Click to collapse
Or just use the MSM tool. Job done
All with varying levels of interpretation, steps, descriptions, and the solution. Not all are useful.
I had the same issue and this worked perfectly to get my device up and running again. Thanks again!!
Hi all!
Here is plan B!
First of all - BEFORE you do some upgrade - make OPSwitch backup and copy to PC !!!!!
If you stuck - it's mean that something is badly damaged and wrong. Some of the files reside in the areas where upgrade tools (including Fastboot!) can't change and repair them.
We don't have time, knowledge to sort out WHAT was damaged.
We make all straight from beginning:
1. MSM tools - make your phone like from the Factory with "clean" install (ver 9 for now)
2. "FlashAll" то ver 10E
3. If you need - install "global"
4. If you need - install TWRP and Magisk
5. Restore your backup from PC
At the end you will have "clean" phone with all programs working
EASY!!!
Same as OP, I wanted to flash twrp.img.
I had my OP7Pro stuck in 'fastboot mode', I thought. It wouldn't respond to any commands from console (device not found) and I couldn't turn it off with the power button any more.
For noobs, just like me, I learned that I just had to press the powerbutton + volume up button. My phone rebooted after this.
Now making a backup before rooting and such, phew.
vegatr0n
I was stuck in Fastboot after switching slots. Excelent stuf! 2,3 clicks , done! Thank you!
vegatr0n said:
Hi, I'm writing this to guide those who faced - and will face similar situation in the future - the problem of being stuck on the fastboot screen, where the recovery or booting in EDL is not available.
So, after failing to get root after upgrading to android 10 I was fiddling with TWRP to try to get it to recognize my storage so I can reflash it and flash Magisk, but I couldn't get it to mount the storage, so my stupid brain decided to go to the wipe page and wiped everything in the hope it might magically work!! well.. it didn't!! and I got stuck in the fastboot screen and I thought that I bricked my phone for good.
after hours of searching online and trying everything nothing helped... but finally I managed to fix it.
and btw when I tried to flash TWRP by (fasboot boot twrp.img) I got the following message:
"remote: Failed to load/authenticate boot image: Load Error"
So here is what I did to get my phone working again:
Download and install Tool All in One
Download Fastboot ROM for your phone from here
In the Tool All in One app click on the Flash Factory Images button.
Select the ROM and let it do its work,
hopefully this will work and your device will reboot into a fresh android.
Click to expand...
Click to collapse
Many people have found this problem. Thank you, I am working again.
i am not even able to flash the twrp in android 10 always getting stuck at fastbootlogo after flashing the recovery cmd
nitinvaid said:
i am not even able to flash the twrp in android 10 always getting stuck at fastbootlogo after flashing the recovery cmd
Click to expand...
Click to collapse
Then you have to use the MSM unbrick tool:
https://forum.xda-developers.com/oneplus-7-pro/how-to/op7pro-collection-unbrick-tools-t3956595/amp/
vegatr0n said:
Then you have to use the MSM unbrick tool:
https://forum.xda-developers.com/oneplus-7-pro/how-to/op7pro-collection-unbrick-tools-t3956595/amp/
Click to expand...
Click to collapse
Nope...
I was able to reboot holding both vol+ and - and power
I bricked my tmobile oneplus 7 pro and dont know which file is safe to try can anyone please point me in the right direction?
I already tried the steps using the tool and downloading the FASTBOOK os file and I get this error
"CreateProcess failed: %1 is not a valid Win32 application. (193)
fastboot: error: Cannot generate image for userdata"
Tried booting the device but boots to OOS recovery always.
---------- Post added at 11:54 PM ---------- Previous post was at 11:21 PM ----------
vegatr0n said:
Hi, I'm writing this to guide those who faced - and will face similar situation in the future - the problem of being stuck on the fastboot screen, where the recovery or booting in EDL is not available.
So, after failing to get root after upgrading to android 10 I was fiddling with TWRP to try to get it to recognize my storage so I can reflash it and flash Magisk, but I couldn't get it to mount the storage, so my stupid brain decided to go to the wipe page and wiped everything in the hope it might magically work!! well.. it didn't!! and I got stuck in the fastboot screen and I thought that I bricked my phone for good.
after hours of searching online and trying everything nothing helped... but finally I managed to fix it.
and btw when I tried to flash TWRP by (fasboot boot twrp.img) I got the following message:
"remote: Failed to load/authenticate boot image: Load Error"
So here is what I did to get my phone working again:
Download and install Tool All in One
Download Fastboot ROM for your phone from here
In the Tool All in One app click on the Flash Factory Images button.
Select the ROM and let it do its work,
hopefully this will work and your device will reboot into a fresh android.
Click to expand...
Click to collapse
I am getting the error
"Erasing 'userdata' OKAY [ 0.243s]
CreateProcess failed: %1 is not a valid Win32 application. (193)
fastboot: error: Cannot generate image for userdata"
I dont know how to proceed with this :crying:
moonbosques said:
I already tried the steps using the tool and downloading the FASTBOOK os file and I get this error
"CreateProcess failed: %1 is not a valid Win32 application. (193)
fastboot: error: Cannot generate image for userdata"
Tried booting the device but boots to OOS recovery always.
---------- Post added at 11:54 PM ---------- Previous post was at 11:21 PM ----------
I am getting the error
"Erasing 'userdata' OKAY [ 0.243s]
CreateProcess failed: %1 is not a valid Win32 application. (193)
fastboot: error: Cannot generate image for userdata"
I dont know how to proceed with this :crying:
Click to expand...
Click to collapse
Sounds like you're having problems with Windows Defender. I also got the same error messages suddenly once week ago. I did sfc /scannow and all that but all files were intact. After rebooting the PC two times the problem was gone, really strange.
Skickat från min GM1913 via Tapatalk
Anyone here know what fastboot rom i can use to fix my bricked tmobile oneplus 7 pro?
Can you explain this strange effect, please
pitrus- said:
Also it's good to know that the official TWRP of twrp.me does not support Android Q at the moment, that's why you couldn't decrypt and mount the storage. TWRP in Oneplus 7 Pro thread here on XDA does support Q, you just have to remember to boot into the inactive/upgraded slot before booting back to TWRP to flash Magisk as it only installs to the active slot and not the upgraded slot.
Skickat från min GM1913 via Tapatalk
Click to expand...
Click to collapse
After an update to Android Q twrp an root was lost.
I was going the normal way like this:
1. In fastboot boot twrp.img
2. In twrp install twrp.zip
3. Reboot to twrp
4. In twrp install magisk.zip
After this the phone stuck a while on this orange splash screen and then reboot to bootloader.
Reboot --> the same effect
Then:
1. Boot into twrp
2. install twrp.zip
3. Reboot system
Everything ok, but no root
Just one method is working for me:
1. Download the full package of OOS 10.x.x
2. Extract the boot.img
3. Patch boot.img with Magisk
4. Flash on fastboot boot magisk_patched.img
5. reboot
My phone is rooted now but without twrp.
Why can twrp an Magisk not work together?
And why I can´t find any information for this problem on the internet?
Well, since TWRP lives in the boot partition on this phone, you will have to boot TWRP using fastboot boot TWRP. Then you flash the unofficial TWRP build 74 installer zip downloaded from the link below (the one from twrp.me only works on OOS 9 and not 10). Reboot phone back into Magisk to switch slot, flash Magisk installer zip which will then install Magisk to both boot slot a and boot slot b. Reboot phone and you should have both Magisk root and working TWRP.
https://r.tapatalk.com/shareLink/to...2&share_fid=3793&share_type=t&link_source=app
Skickat från min GM1913 via Tapatalk
Fails anyway
Bricked my OnePlus and now I'm left with bootloader (no os, no twrp). Everything leads back to bootloader. Any attempts to apply fastboot boot lead to "Load Error". Now I tried with that tool and ended up with this:
Sending 'odm' (102400 KB) OKAY [ 2.576s]
Writing 'odm' FAILED (remote: '(odb_b) No such partition')
fastboot: error: Command failed
Press any key to exit...
P.S. Full log:
--------------------------------------------
Bootloader Version...:
Baseband Version.....:
Serial Number........: e434a4c8
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
android-info.txt syntax error: я╗┐require product=msmnile
Setting current slot to 'b' OKAY [ 0.002s]
extracting boot.img (96 MB) to disk... took 0.776s
archive does not contain 'boot.sig'
Sending 'boot_b' (98304 KB) OKAY [ 2.389s]
Writing 'boot_b' OKAY [ 0.406s]
extracting dtbo.img (16 MB) to disk... took 0.151s
archive does not contain 'dtbo.sig'
Sending 'dtbo' (16384 KB) OKAY [ 0.393s]
Writing 'dtbo' OKAY [ 0.047s]
archive does not contain 'dt.img'
archive does not contain 'recovery.img'
extracting vbmeta.img (0 MB) to disk... took 0.001s
archive does not contain 'vbmeta.sig'
Sending 'vbmeta' (8 KB) OKAY [ 0.008s]
Writing 'vbmeta' OKAY [ 0.002s]
archive does not contain 'vbmeta_system.img'
archive does not contain 'super_empty.img'
archive does not contain 'boot_other.img'
extracting odm.img (100 MB) to disk... took 0.395s
archive does not contain 'odm.sig'
Sending 'odm' (102400 KB) OKAY [ 2.576s]
Writing 'odm' FAILED (remote: '(odm_b) No such partition')
fastboot: error: Command failed
Press any key to exit...
I am getting this error, any ideas what is going wrong? (please see attachment)
vegatr0n said:
Hi, I'm writing this to guide those who faced - and will face similar situation in the future - the problem of being stuck on the fastboot screen, where the recovery or booting in EDL is not available.
So, after failing to get root after upgrading to android 10 I was fiddling with TWRP to try to get it to recognize my storage so I can reflash it and flash Magisk, but I couldn't get it to mount the storage, so my stupid brain decided to go to the wipe page and wiped everything in the hope it might magically work!! well.. it didn't!! and I got stuck in the fastboot screen and I thought that I bricked my phone for good.
after hours of searching online and trying everything nothing helped... but finally I managed to fix it.
and btw when I tried to flash TWRP by (fasboot boot twrp.img) I got the following message:
"remote: Failed to load/authenticate boot image: Load Error"
So here is what I did to get my phone working again:
Download and install Tool All in One
Download Fastboot ROM for your phone from here
In the Tool All in One app click on the Flash Factory Images button.
Select the ROM and let it do its work,
hopefully this will work and your device will reboot into a fresh android.
Click to expand...
Click to collapse
Spoiler: UPDATING UPGRADE METHOD
Hello to everyone!
Following this guide, you'll be able to rebrand your T5 to Chinese version (W09-C00 or AL00-C00), so you can upgrade to EMUI 9.1/HARMONY 2.0
(IF YOU HAVE THE HONOR PAD 5 AND YOU WANT TO UPDATE, TALK ME)
I have a T5, W19 / 3gb ram / 32 internal.
It worked for me, should work for you too, but I'm not responsible if something goes wrong (well...maybe a little).
PROCESS:
1- You need to UNLOCK the BOOTLOADER with POTATONV and you MUST CHECK "Disable FBLOCK" or you'll have problems flashing the IMGs.
(fastboot oem lock-state info - to check if FBLOCK is unlocked)
{
"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"
}
1.1- Check that FRP is UNLOCKED
1.2- CHECK that HISUITE is installed (for drivers) >>> CLICK HERE TO DOWNLOAD
1.3- BACKUP YOUR OEMINFO USING TWRP, IF SOMETHING GOES WRONG, YOU'LL NEED IT.
Follow this amazing guides to UNLOCK your BOOTLOADER:
SOFTWARE >>> CLICK HERE TO DOWNLOAD
UNLOCK BOOTLOADER T5 process >>> CLICK HERE FOR THE GUIDE
SAVE YOUR BOOTLOADER CODE, YOU'LL NEED IT.
2- Download fastboot and oeminfo, extract it and flash it:
FASTBOOT FILES (USE IT):
WINDOWS: CLICK HERE TO DOWNLOAD
LINUX: CLICK HERE TO DOWNLOAD
MAC: CLICK HERE TO DOWNLOAD
OEMINFO AGS2 / C00:
W09 - W19 WIFI ONLY:
fastboot flash oeminfo oeminfoW09C00.img
https://www.androidfilehost.com/?fid=14655340768118449368
L09 LTE (don't know if it will work on L03):
fastboot flash oeminfo oeminfoags2al00c00.img
https://androidfilehost.com/?fid=14655340768118450716
YOU CAN ALSO USE TWRP TO FLASH OEMINFO, IF YOU DO THAT, FLASH IT AND REBOOT INTO BOOTLOADER TO CONTINUE THE PROCESS
3- Now, download and extract the zip, flash the IMGs inside and wait for the best:
FILES FOR AGS2-W09 & W19
https://www.androidfilehost.com/?fid=14655340768118449355
FILES FOR AGS2-L09
https://www.androidfilehost.com/?fid=14655340768118459545
Flash this files in FASTBOOT
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot flash fastboot fastboot.img
fastboot flash kernel kernel.img
fastboot flash ramdisk ramdisk.img
fastboot flash recovery_ramdisk recovery_ramdisk.img
fastboot flash cust cust.img
fastboot flash version version.img
***Reboot into STOCK recovery and format data***
*If the above files doesn't work, try flashing the firmware with DLOAD method.
Download the zip and extract the DLOAD folder into the root of your SDCARD, reboot the tablet pressing VOL + and VOL - and wait...*
DOWNLOAD DLOAD W09-C00
DOWNLOAD DLOAD AL00-C00
4- Now, the phone should boot normally, rebranded and with the chinese firmware.
Now, go to settings and check for update, you'll see an update to PIE available.
You'll need to install all the PIE updates before the server sends Harmony, or... you can send the Harmony update directly with this:
https://professorjtj.github.io/ (AGS2-W09 - C00) (AGS2-AL00 - C00)
https://github.com/ProfessorJTJ/HISuite-Proxy/wiki/Complete-Guide (follow instructions, very easy to use)
Upgrading to Pie/Harmony locked my bootloader, but if you saved your code, write it again and unlock it again ^.^
Thanks to @Fosanz for its help.
Thanks to @Rockel for the detailed guide to unlock the bootloader. Go to the post
Thanks to @iceows for the script and steps to edit the oeminfo: Go to the link
Thanks to @oslo83 for helping me to fix the mess that I caused to my tablet.
IF YOU HAVE DOUBTS OR ANY PROBLEM, SEND ME A PM
TELEGRAM: sfoot13
Nc
The shadow proves the sunshine.
t.me
After the rebrand, I didn't lost Widevine L1
That's all folks!
Have a good day, cheers.
Spoiler: REBRAND TO HONOR PAD 5 TABLET AND GET A NICE NAVBAR
After upgrading to PIE/HARMONY, IF YOU WANT TO... FLASH ONLY OEMINFO!!!
W09 - W19 DOWNLOAD LINK
L09 DOWNLOAD LINK
Flash it, reboot, and done, don't do nothing else.
ROOT WITH MAGISK
Download latest magisk apk and patch your recovery ramdisk img, after that, flash with fastboot and reboot into recovery to have root working.
fastboot flash recovery_ramdisk yourimg.img
fastboot reboot-recovery (keep usb cable connected)
Here's my recovery rooted, if you want to flash it
https://www.androidfilehost.com/?fid=14655340768118462757
TWRP: System and Vendor can't be mounted, Huawei changed file system, now is EROFS, so system can't be modify.
Go to the post.
Go to data > hw_init - You'll see many folders, you can delete almost all the apps inside the folders, unless you use one of them. (you'll see the chinese apps)
Script to delete/disable some apps (if you know other apps that can be disable, tell us)
adb shell
sh deletebloatware.sh
Click here to go to the download link
PLAY STORE - MAGISK MODULE
Download the module and go to magisk and install it
Releases · nift4/microg_installer_revived
Install microG GmsCore, GsfProxy, FakeStore (or Play Store if you want so) and MapsV1 to /system/ - nift4/microg_installer_revived
github.com
Download the Playstore apk
Google Play Store 29.9.16-19 [0] [PR] 438372530 (nodpi) (Android 4.4+) APK Download by Google LLC - APKMirror
Google Play Store 29.9.16-19 [0] [PR] 438372530 (nodpi) (Android 4.4+) APK Download by Google LLC - APKMirror Free and safe Android APK downloads
www.apkmirror.com
Download latest playstore apk, use a root explorer, copy the playstore apk, go to SBIN > MAGISK > MODULES > MICROG_INSTALLER > SYSTEM > PRIV-APP > PHONESKY and delete fakestore.apk and paste the latest playstore apk and reboot.
SCREENSHOTS!!!
Hmm, tried to do this but fastboot flash oeminfo oeminfoags2al00c00.img failed. No big deal I did it through TWRP.
Next fastboot flash system system.img but also failed
Sending sparse 'system' 1/6 (412324 KB) OKAY [ 12.720s]
Writing 'system' FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
Bootloader shows PHONE Unlocked and FRP Unlocked both in red.
What am I missing?
@Sleeepy2 Hello, I'm talking with a guy that has the same problem, can't flash oeminfo and system with fastboot.
Same as your tabket, FPR and bootloader unlocked.
I was thinking that maybe in one of the latest huawei updates, they (huawei) changed something (security patches), because I never had that problems and I haven't updated to the latest security patch that huawei released...
You can try sending the firmware with EMUI Flasher https://www.androidfilehost.com/?fid=14655340768118451775
But should download the firmware from this page https://professorjtj.github.io/ look for
AGS2-AL00 - C00AGS2-AL00 8.0.0.215(C00)
@sfoot13 Can't use the EMUI flash yet, as I tried flashing system through TWRP and it failed now can't boot. lol
I've found the firmware on that page but I don't know how to down load it. Clicking the 3 dot menu opens the Downlad ROM window but it doesn't work, says to use the HISuite.Proxy. If I run that and click the link, it shows 3 zips but clicking on any of them doesn't download.
Clicking the Add Rom shows up in HISuite.Proxy but I still don't see a way to download it.
I think I figured out how I am supposed to use the ROM but it doesn't work. Run the Proxy, go to website and click add and it shows up in the proxy. Then open HiSuite connect tablet and click Update. It shows a new version is available however clicking update it instantly goes to Failed to update.
Well if I read the op closer it actually has a link explaining how to use the proxy.
I have flashed the oem file through TWRP, used the proxy to download the 8.0.0.215 rom but wile HiSuite is "installing" Proxy said it's probably not going to work. When the tablet reboots to install it says software update failed
@Sleeepy2 if you flashed the oeminfo, you can flash the system with Emui Flasher, even if you're using linage os or any gsi, because you just need to download the oreo firmware, copy it to internal memory, open emui flasher and select the firmware zip.
To download the firmware directly from the page, you need to click in the box with the three dots ... and you'll see the option to download (always with hisuite proxy open)
ugh, well I think I pooched it now.
I started over and got linage os flashed and rooted. EMUI Flasher couldn't find any files in any folder to flash.
Rebooted back into TWRP and flashed the oeminfo now it only boots into eRecovery or stock recovery, no sign of TWRP.
Booted back into fastboot to try and just flash TWRP again.
fastboot flash recovery_ramdisk TWRP_3.5.2-prague_DarkJoker360_20210508.img
Sending 'recovery_ramdisk' (14894 KB) OKAY [ 0.398s]
Writing 'recovery_ramdisk' FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
eRecovery wont download and install stock anymore. I am going to give up for today.
Ugh, well I guess my tablet is done. Fastboot wont flash recovery and eRecovery
Getting package info failed"
If any one has any suggestions, that would be great.
I just did the oem unlock again from fastboot even though it said it was unlocked. After I did that it automatically rebooted into TWRP and I was able to flash my oeminfo back and it was good to go again.
I've gone through all the the steps successfully, however when I check for updates I don't see any?
What could be wrong?
scabs said:
I've gone through all the the steps successfully, however when I check for updates I don't see any?
What could be wrong?
Click to expand...
Click to collapse
Successfully? Really? Great.
Well, if you installed oeminfo and the IMGs and you formatted data and it booted, go to settings and tell me the version it says.
Not working for me. flashing oeminfo failed using fastboot. Same problem than Sleeepy2
Any clear explanation will be appreciated. I'm not a specialist.
In fact, I'm a little bit a specialist because I've unlocked bootloader and FRP. I've also installed LineOS 18.1
@bedelaitre I'll rewrite it, maybe it will work for everyone.
One thing, you're not able to flash some imgs, because you need to unlock again your bootloader with PotatoNV and CHECK THE BOX "DISABLE FBLOCK", after that you'll be able to flash system and others img, but that means, you'll need to open again the tablet...
sfoot13 said:
Successfully? Really? Great.
Well, if you installed oeminfo and the IMGs and you formatted data and it booted, go to settings and tell me the version it says.
Click to expand...
Click to collapse
scabs said:
Click to expand...
Click to collapse
You need to format data bro.
sfoot13 said:
SCREENSHOTS!!!
Click to expand...
Click to collapse
sfoot13 said:
Hello to everyone!
Following this guide, you'll be able to rebrand your T5 to Chinese version (W09-C00 or AL00-C00), so you can upgrade to EMUI 9.1/HARMONY 2.0
(IF YOU HAVE THE HONOR PAD 5 AND YOU WANT TO UPDATE, TALK ME)
I have a T5, W19 / 3gb ram / 32 internal.
It worked for me, should work for you too, but I'm not responsible if something goes wrong (well...maybe a little).
PROCESS:
1- You need to UNLOCK the BOOTLOADER with POTATONV and you MUST CHECK "Disable FBLOCK" or you'll have problems flashing the IMGs.
(fastboot oem lock-state info - to check if FBLOCK is unlocked)
View attachment 5597429
1.1- Check that FRP is UNLOCKED
1.2- CHECK that HISUITE is installed (for drivers) >>> CLICK HERE TO DOWNLOAD
1.3- BACKUP YOUR OEMINFO USING TWRP, IF SOMETHING GOES WRONG, YOU'LL NEED IT.
Follow this amazing guides to UNLOCK your BOOTLOADER:
SOFTWARE >>> CLICK HERE TO DOWNLOAD
UNLOCK BOOTLOADER T5 process >>> CLICK HERE FOR THE GUIDE
SAVE YOUR BOOTLOADER CODE, YOU'LL NEED IT.
2- Download fastboot and oeminfo, extract it and flash it:
FASTBOOT FILES (USE IT):
WINDOWS: CLICK HERE TO DOWNLOAD
LINUX: CLICK HERE TO DOWNLOAD
MAC: CLICK HERE TO DOWNLOAD
OEMINFO AGS2 / C00:
W09 - W19 WIFI ONLY:
fastboot flash oeminfo oeminfoW09C00.img
https://www.androidfilehost.com/?fid=14655340768118449368
L09 LTE (don't know if it will work on L03):
fastboot flash oeminfo oeminfoags2al00c00.img
https://androidfilehost.com/?fid=14655340768118450716
YOU CAN ALSO USE TWRP TO FLASH OEMINFO, IF YOU DO THAT, FLASH IT AND REBOOT INTO BOOTLOADER TO CONTINUE THE PROCESS
3- Now, download and extract the zip, flash the IMGs inside and wait for the best:
FILES FOR AGS2-W09 & W19
https://www.androidfilehost.com/?fid=14655340768118449355
FILES FOR AGS2-L09
https://www.androidfilehost.com/?fid=14655340768118459545
Flash this files in FASTBOOT
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot flash fastboot fastboot.img
fastboot flash kernel kernel.img
fastboot flash ramdisk ramdisk.img
fastboot flash recovery_ramdisk recovery_ramdisk.img
fastboot flash cust cust.img
fastboot flash version version.img
***Reboot into STOCK recovery and format data***
*If the above files doesn't work, try flashing the firmware with DLOAD method.
Download the zip and extract the DLOAD folder into the root of your SDCARD, reboot the tablet pressing VOL + and VOL - and wait...*
DOWNLOAD DLOAD W09-C00
DOWNLOAD DLOAD AL00-C00
4- Now, the phone should boot normally, rebranded and with the chinese firmware.
Now, go to settings and check for update, you'll see an update to PIE available.
You'll need to install all the PIE updates before the server sends Harmony, or... you can send the Harmony update directly with this:
https://professorjtj.github.io/ (AGS2-W09 - C00) (AGS2-AL00 - C00)
https://github.com/ProfessorJTJ/HISuite-Proxy/wiki/Complete-Guide (follow instructions, very easy to use)
Upgrading to Pie/Harmony locked my bootloader, but if you saved your code, write it again and unlock it again ^.^
Thanks to @Fosanz for its help.
Thanks to @Rockel for the detailed guide to unlock the bootloader. Go to the post
Thanks to @iceows for the script and steps to edit the oeminfo: Go to the link
Thanks to @oslo83 for helping me to fix the mess that I caused to my tablet.
IF YOU HAVE DOUBTS OR ANY PROBLEM, SEND ME A PM
TELEGRAM: sfoot13
Nc
The shadow proves the sunshine.
t.me
After the rebrand, I didn't lost Widevine L1
That's all folks!
Have a good day, cheers.
Click to expand...
Click to collapse
Good morning !
Sorry for my broken english, i have a huawei mediapad t5 tablet with 3 giga ram exactly like yours.
I would like to know where did you make the contact point on the motherboard so that I can also do it on mine to unlock the bootloader.
I thank you in advance.
@TONYFR-1984
Follow this steps , there's a photo of the motherboard, the exact place that you need to touch (it is marked with a red line and circle)
Trying to unlock the bootloader with PotatoNV on Mediapad T5 not working (video explanation)
Hi there, So After seen many tutorials I wanted to proceed to unlock the bootloader of my Huawei Mediapad T5 , here are the specs ``` Model: AGS2-W09 Build No: AGS2-W09 8.0.0.360(OCEC431) CPU : Hisilicon Kirin...
forum.xda-developers.com
What would be the process of going back to LineageOS?
sfoot13 said:
@bedelaitre I'll rewrite it, maybe it will work for everyone.
One thing, you're not able to flash some imgs, because you need to unlock again your bootloader with PotatoNV and CHECK THE BOX "DISABLE FBLOCK", after that you'll be able to flash system and others img, but that means, you'll need to open again the tablet...
Click to expand...
Click to collapse
Hi, sorry for delay. I don't understand why I need to unlock the bootloader. When booting, the tablet says that the bootloader is unlocked. Are you sure I need to unlock it again ?