Database Info

Bootloop when starting android or RCK

I tried to flash a custom rom (KatKiss), and it seems that I did something wrong along the way because the tablet is stuck in a bootloop.
So I rebooted my tablet and access the bootloader ("fastboot devices" recognize my device) and try to go to the recovery (with the TWRP splash screen, "adb devices" recognize my device). Unfortunately after 20 seconds on the splash screen, the tablet reboots (tries to load my katkiss android but bootloop everytime).
Bootloader : 10.6.1.14.10
TWRP : 3.1.1.0
Since the fastboot recognize my device while in bootloader, I think that I should try to flash twrp since it seems to be corrupted somehow.
Every time I flashed a rom nothing went wrong but now that I have a problem I don't want to worsen it and would like some help on the issue.

Did you flash the rom in your current TWRP?
Something is off... Did you possibly flash the TF201 rom version??
Whatever you do - do not use Wipe Data from the bootloader!!
Reflash TWRP, format data, then reflash the rom
And report in more detail what you did
Sent from my Nexus 5X using Tapatalk

Thank you for the fast reply!
I did flash the rom with my current TWRP and only downloaded the rom version for the TF700. Below is what I tried from your suggestion:
I check that my device is recognized:
fastboot device
So I tried flashing TWRP:
fastboot flash recovery twrp-3.1.1-0-tf700t
After it succeeded, I reboot the tablet:
fastboot reboot
And as a result... nothing changes, I don't know if I should try with older version of TWRP. Seems like I only have access to the tablet with the fastboot.

That is very strange indeed. Yes, try a 3.0.2 version of TWRP and see if that works.
If not, I would flash the Asus stock blob in fastboot and start from scratch....
Sent from my TF700T using Tapatalk

Kromlech said:
And as a result... nothing changes, I don't know if I should try with older version of TWRP. Seems like I only have access to the tablet with the fastboot.
Click to expand...
Click to collapse
Not sure if this will help but I had a reboot problem with trying to load into TWRP. I posted my solution into a different thread but will toss it out here..
I just had this problem with a Transformer 201Prime. The cycle went something like this..
Power on.... get ASUS logo in middle, Tegra3 logo on lower right, and bootloader unlocked in upper left....
then a buzz... then reboot.....
So I would try the power button and hold the volume down... that got me into the bootloader but when I hit the volume up button it would give me the TWRP logo... then buzz and reboot...
After much monkeying around... I realized I would have to re install everything. Fortunately I had the original NVFLASH bloob files backed up so I was able to get into the NVFLASH commands.
Here is a great tutorial, it is for the 201 so be sure to download the correct files but the steps are basically the same.
https://forum.xda-developers.com/tra...prime-t3486237
The other problems is I had to download a bloob tool to 'unpack' the necessary .bin and .ebt files that are mentioned in the commands... I used the following link to download the tool.
https://github.com/AndroidRoot/BlobTools
I hope this helps shake loose a few answers.
Once I was able to get a working recovery I could flash an updated ROM. (KatKiss is my current favorite)

I tried to flash version 3.0.2 of TWRP and the problem is still the same.
@Unidave199 the link you put in your post points to a post that doesn't seems to exist anymore, has it been moved?
@berndblb how do I do for flashing a rom with the fastboot? any stock rom to recommend?

double post

Kromlech said:
I tried to flash version 3.0.2 of TWRP and the problem is still the same.
@Unidave199 the link you put in your post points to a post that doesn't seems to exist anymore, has it been moved?
@berndblb how do I do for flashing a rom with the fastboot? any stock rom to recommend?
Click to expand...
Click to collapse
Unidave's link would only help you if you generated your device specific nvflash blobs when the tablet was still functioning. Did you:
flash a specifically modded recovery - flash the moddded bootloader, use wheelie to generate and save your blobs, return everything to factory specs?
I highly doubt it since you would have mentioned...
To flash the stock blob in fastboot you download the Asus firmware from here: https://www.asus.com/my/support/Download/28/1/0/11/29/8/
Extract the zip twice until you see a blob and a meta-inf file.
Move the blob into your fastboot folder, discard the rest of the file
Issue these commands one by one, letting each one finish before starting the next. Some will finish quick, others may take up to 3 minutes:
Code:
fastboot erase system
fastboot erase boot
fastboot erase recovery
fastboot erase misc
fastboot erase cache
fastboot erase userdata
fastboot flash system blob
fastboot reboot
The first boot will take a while, but that should put you back on a stock JB 4.2 system.
Trash all the files you used in your last attempt and redownload the rom, gapps and supersu
Fastboot flash TWRP
Reboot
Format /data in TWRP (this will take up to 1 hour - let it finish!!), then convert /data to f2fs
Flash the rom, gapps, supersu
If you flash Nougatella remember that you have to turn on wifi right after the language selection during setup or Google framework will crash.

Spend the end of the day doing it, but it worked flawlessly! Thanks a lot @berndblb, now I can use my tablet again!

Kromlech said:
I tried to flash version 3.0.2 of TWRP and the problem is still the same.
@Unidave199 the link you put in your post points to a post that doesn't seems to exist anymore, has it been moved?
@berndblb how do I do for flashing a rom with the fastboot? any stock rom to recommend?
Click to expand...
Click to collapse
My apologies for the problem with my link, looks like you resolved it, but wanted to post a correct working link to take someone else into the full conversation and context...
https://forum.xda-developers.com/showpost.php?p=71150385

berndblb said:
To flash the stock blob in fastboot you download the Asus firmware from here: https://www.asus.com/support/Download/28/1/0/11/fq2B3oq64av1O95/8/
Click to expand...
Click to collapse
Broken link ? that post isn't very old, either. ??

berndblb said:
Did you flash the rom in your current TWRP?
Something is off... Did you possibly flash the TF201 rom version??
Whatever you do - do not use Wipe Data from the bootloader!!
Reflash TWRP, format data, then reflash the rom
And report in more detail what you did
Click to expand...
Click to collapse
I did wipe data from bootloader, now I can't go to bootloader. How to revive my tf700t?
Please help
Thanks

ketulharini said:
I did wipe data from bootloader, now I can't go to bootloader. How to revive my tf700t?
Please help
Thanks
Click to expand...
Click to collapse
You'll need to refer to post #8. However, the link to the tf700 stock blob is broken. You'll have to search Google for one. They're out there, but it does require digging .Make sure the one you get is for the proper SKU of your tablet (US, Worldwide, JP, etc.). I completed the process myself maybe a month ago. Good luck!

monogwai said:
You'll need to refer to post #8. However, the link to the tf700 stock blob is broken. You'll have to search Google for one. They're out there, but it does require digging .Make sure the one you get is for the proper SKU of your tablet (US, Worldwide, JP, etc.). I completed the process myself maybe a month ago. Good luck!
Click to expand...
Click to collapse
I got the stock blob ww version.
Just tab doesn't stay on fastboot mode keeps rebooting.
Don't know how to do it.
Is it possible to get stable fastboot screen some how? Or just flash the bootloader to get fastboot working.
May be this noob question but I don't know how to do.
Thanks

ketulharini said:
I got the stock blob ww version.
Just tab doesn't stay on fastboot mode keeps rebooting.
Don't know how to do it.
Is it possible to get stable fastboot screen some how? Or just flash the bootloader to get fastboot working.
May be this noob question but I don't know how to do.
Thanks
Click to expand...
Click to collapse
There is one more piece to the puzzle- hold short while I dig it up.
Here it is: http://www.transformerforums.com/forum/transformer-pad-infinity-tf700-tegra-3-development/46302-guide-help-my-transformer-tf700-boots-only-recovery.html
Do be *very* careful. Read thrice, do it once. Especially if you're feeling noob-y.

monogwai said:
There is one more piece to the puzzle- hold short while I dig it up.
Here it is: http://www.transformerforums.com/fo...my-transformer-tf700-boots-only-recovery.html
Do be *very* careful. Read thrice, do it once. Especially if you're feeling noob-y.
Click to expand...
Click to collapse
Thanks for this information.
One more question,
My tab is keep bootlooping neither it stays on twrp nor bootloader.
It has blue screen of recovery that is twrp after 5 to 10 seconds it boots again.
Is this enough time to execute the commands while it is on blue screen?
Thanks

ketulharini said:
Thanks for this information.
One more question,
My tab is keep bootlooping neither it stays on twrp nor bootloader.
It has blue screen of recovery that is twrp after 5 to 10 seconds it boots again.
Is this enough time to execute the commands while it is on blue screen?
Thanks
Click to expand...
Click to collapse
Well, that depends on several things. What I did was write a short little DOS batch file to process all the fastboot commands. So, with your batch file ready, open your command prompt (change directory to your adb/fastboot directory if it's not set in system's 'path=' environment variable) and have the batch command typed in, ready to hit enter. Tether to pc via USB, proceed to boot to adb. The second you hear windows make the USB notification sound, slap that enter key. It should just process and reset the tab and get you out of TWRP bootloop. Which is just step one.
If you aren't familiar with writing bat files for DOS, let me know.

monogwai said:
Well, that depends on several things. What I did was write a short little DOS batch file to process all the fastboot commands. So, with your batch file ready, open your command prompt (change directory to your adb/fastboot directory if it's not set in system's 'path=' environment variable) and have the batch command typed in, ready to hit enter. Tether to pc via USB, proceed to boot to adb. The second you hear windows make the USB notification sound, slap that enter key. It should just process and reset the tab and get you out of TWRP bootloop. Which is just step one.
If you aren't familiar with writing bat files for DOS, let me know.
Click to expand...
Click to collapse
You mean a batch file with the adb commands right? Once he can boot into fastboot he has all the time in the world to run the commands for the buster99 (description in post #8). Depending on what situation he came from before, it might be a good idea to start all fresh...
The tricky thing are the adb push bootit.ko and the insmod command. Those have to be timed just right to get executed, so a batch file might come in handy. Both commands only take a second or two to execute, so your window of 5 seconds could work. Maybe not in the same session, but they should work.
If the insmod command does not kick the tablet into the bootloader, there are 2 possible reasoons:
adb push bootit.ko did not work
the insmod command did not work
To find out if the file push worked you could add a simple list command for the contents of /sdcard/. Again - tricky, I know since you still are working with the 5 sec window, but that's what you got to work with...
That would look something like in the attached picture. So after pushing bootit.ko you issue:
Code:
adb shell ls /sdcard/
Try it with the batch file, try it with single commands... Don't give up. As long as you have any kind of adb access you should be able to solve it.
Good luck!

berndblb said:
You mean a batch file with the adb commands right?
Click to expand...
Click to collapse
Yeah.
berndblb said:
Once he can boot into fastboot he has all the time in the world to run the commands for the buster99 (description in post #8).
Click to expand...
Click to collapse
Again, mistake in my terminology. What I meant to say is, batch commands for the process involving the Bootit.ko- the adb portion.
Thanks for clearing that up.
@ketulharini
Anyhow, I was unable to get the process to take without having automated *every last step* of the process. Literally open the cmd window, have the command for your batch file typed in ready to go, and plug in. Hear the noise from windows and slap enter asap. That's the only way I could get it in time, and I'm a ridiculously fast typist.

monogwai said:
Yeah.
Again, mistake in my terminology. What I meant to say is, batch commands for the process involving the Bootit.ko- the adb portion.
Thanks for clearing that up.
@ketulharini
Anyhow, I was unable to get the process to take without having automated *every last step* of the process. Literally open the cmd window, have the command for your batch file typed in ready to go, and plug in. Hear the noise from windows and slap enter asap. That's the only way I could get it in time, and I'm a ridiculously fast typist.
Click to expand...
Click to collapse
Care to share the batch file?

Unable to access bootloader after rebranding attempt (AL00 (B225) -> L29 (C636))

I was running the Ephemeral Mate 9 B225 ROM on AL00. It worked well but I wasn't satisfied with the custom ROM.
So I decided to rebrand to MHA-L29 and run a stock rom.
I started converting my MHA-AL00 (B225) to MHA-L29 using this guide: Link
I've override the L29C636 OEMinfo while keeping the other 5 existing files of the original OEMinfo intact. (See attachment for original OEMinfo files)
I got stuck after restoring the new OEMinfo through TWRP recovery as stated in the guide.
The phone booted up and started the installation of the new firmware. When completed it did a reboot but it never started up again.
Now my phones doesn't respond to input from physical buttons although my PC does recognise a decive as "HI3650". In device manager it also shows up as "Android Bootloader Interface".
Summary of process followed:
1. Bootloader unlocked
2. Instaled TWRP
3. Flashed Ephemeral Mate 9
4. Did a OEMinfo back-up
5. Changed AL00B225 OEMinfo to L29C636 oeminfo
6. TWRP back-up recovery
Next step should be to unlock the bootloader and instal TWRP again but I can't get to interact with the phone at this stage.
Can anyone point to what I did wrong and/or advice me on the next steps I could take?

Use this link mate, always succeed for me, dont need to do anything, just download 3 big files, copy to sdcard and run the bat file.
https://forum.xda-developers.com/mate-9/how-to/guide-mate-9-flash-update-package-t3593108

lemonade747 said:
Use this link mate, always succeed for me, dont need to do anything, just download 3 big files, copy to sdcard and run the bat file.
https://forum.xda-developers.com/mate-9/how-to/guide-mate-9-flash-update-package-t3593108
Click to expand...
Click to collapse
I can copy those files to the SD-card though a different source.
How can I run the update bat file from the SD when its inserted in my phone?
The phone doesn't respons to ADB and I can't get it to boot in bootloader or recovery. It even doesn't show up as a storage device at my PC (both internal and SD storage).

30-08-2017 14:50 UPDATE: It seems fastboot does recognise the device but adb doesn't. It there a way to use fastboot command to run the bat file or restore the OEMfile back-up. Both are present on the SD-card.
Questions @lemonade747: Does the phone need be be bootloader unlocked and TWRP instaled? I have a slight suspicion that that it both the bootloader got locked and TWRP uninstaled afther the TWRP recovery back-up to L29C636.

Bulrock said:
30-08-2017 14:50 UPDATE: It seems fastboot does recognise the device but adb doesn't. It there a way to use fastboot command to run the bat file or restore the OEMfile back-up. Both are present on the SD-card.
Questions @lemonade747: Does the phone need be be bootloader unlocked and TWRP instaled? I have a slight suspicion that that it both the bootloader got locked and TWRP uninstaled afther the TWRP recovery back-up to L29C636.
Click to expand...
Click to collapse
Go to download mode (power + volume down), plug the cable and run the bat file from the link I give (remember to download all small link and extract to the same folder), follow its instruction (in the cmd window) to complete the installation. Sorry I cant give your more clearly step. Regarding your question, if your phone has already unlocked BL, it will move to the next step (install the recovery), if not it will ask you put in your passcode to unlock BL then the next step will happen. All thing I said here is in that bat file, very detail.

lemonade747 said:
Go to download mode (power + volume down), plug the cable and run the bat file from the link I give (remember to download all small link and extract to the same folder), follow its instruction (in the cmd window) to complete the installation. Sorry I cant give your more clearly step. Regarding your question, if your phone has already unlocked BL, it will move to the next step (install the recovery), if not it will ask you put in your passcode to unlock BL then the next step will happen. All thing I said here is in that bat file, very detail.
Click to expand...
Click to collapse
Thanks for your detailed explanation, but it didn't solve the problem.
The phone is not responsive to go to bootloader mode (power + volume down) and the screen stays black. Fastboot command also dont seem to get it in bootloader mode. I keep getting the error message: (remote: Command not allowed).
The phone won't start up and is not responsive to any input and therefore unable to check status of USB-debugging. (unknown if it is enabled or disabled at this stage).
This stage happend, as explained in the first post, through TWRP back-up recovery with L29C636 OEMinfo files.

Bulrock said:
Thanks for your detailed explanation, but it didn't solve the problem.
The phone is not responsive to go to bootloader mode (power + volume down) and the screen stays black. Fastboot command also dont seem to get it in bootloader mode. I keep getting the error message: (remote: Command not allowed).
The phone won't start up and is not responsive to any input and therefore unable to check status of USB-debugging. (unknown if it is enabled or disabled at this stage).
This stage happend, as explained in the first post, through TWRP back-up recovery with L29C636 OEMinfo files.
Click to expand...
Click to collapse
There are two method to go to the download mode:
1. Make sure the phone DOES NOT connect to any charger (via cable). Press volume down + Power button and wait at least 10 seconds. If the phone are connecting to charger or laptop, it wont work.
2. Press and hold the volume down button then plug the cable to your laptop (or charger but I prefer laptop cuz we can move to the next step without disruption), it will enter the download mode automatically.
If after trying two method above and still dont work for you, you may need to flash stock rom (including stock firmware) by using E-recovery method.

5-9-2017 UPDATE: I've been unable to solve this issue by myself. The phone is sent for repairs, fingers crossed they will accept it....

Request for a Guide

I'm not so happy with EMUI 8/Oreo on my Mate 9. Several widgets don't update, requiring me to change the screen resolution during the day (weird temporary fix). I'd rather run Nova but EMUI pushes against that. I have a pretty good backup phone (ZTE Axon 7) so I thought I would give a generic system image a try. The last time I rooted and installed an alternative ROM was 2014, so I'm rusty. I successfully put minimal fastboot on a PC, unlocked the bootloader and installed TWRP 3.2.1-0 (something may have gone wrong already at this point since I accessed it by vol up + power, rather than vol up + vol down + power). Then I installed the generic system image. It booted, but gave error messages at boot. Perhaps all I needed to do was install it a second time, but instead I tried installing a different image, achieved bootloop, made matters worse, and was rescued by the amazing and wonderful FunkyHuawei.
I am thinking about trying again, but I wondered if an expert would write a more patient guide that provides the exact steps to flashing a generic system image. By the exact steps, I mean with links to files and what you type in minimal fastboot (if indeed that is the right program), or when it is best to install from an SD card. I'm sure such a guide would get more people to try other ROMs besides the generic ROM.

prestonmcafee said:
I'm not so happy with EMUI 8/Oreo on my Mate 9. Several widgets don't update, requiring me to change the screen resolution during the day (weird temporary fix). I'd rather run Nova but EMUI pushes against that. I have a pretty good backup phone (ZTE Axon 7) so I thought I would give a generic system image a try. The last time I rooted and installed an alternative ROM was 2014, so I'm rusty. I successfully put minimal fastboot on a PC, unlocked the bootloader and installed TWRP 3.2.1-0 (something may have gone wrong already at this point since I accessed it by vol up + power, rather than vol up + vol down + power). Then I installed the generic system image. It booted, but gave error messages at boot. Perhaps all I needed to do was install it a second time, but instead I tried installing a different image, achieved bootloop, made matters worse, and was rescued by the amazing and wonderful FunkyHuawei.
I am thinking about trying again, but I wondered if an expert would write a more patient guide that provides the exact steps to flashing a generic system image. By the exact steps, I mean with links to files and what you type in minimal fastboot (if indeed that is the right program), or when it is best to install from an SD card. I'm sure such a guide would get more people to try other ROMs besides the generic ROM.
Click to expand...
Click to collapse
By a generic system image, you are referring to wanting to install an aosp image (treble ROM), correct?

Yes.

prestonmcafee said:
Yes.
Click to expand...
Click to collapse
And obviously you still have your bootloader unlock code?
Also what Mate 9 version do you have and what exact firmware is it running?
I can help ya out no problem. Just obviously want to make sure you avoid going through that again

Thanks, Wirmpolter! I have the unlock code, but it shows as unlocked, at least I get the dire warning about the device being unsafe on boot. I have the US model, build number MHA-L29 9.0.0.360 (C567), with both Android and EMUI versions listed as 8.0.0.

Sorry, MHA-L29 8.0.0.360 (C567)

prestonmcafee said:
Thanks, Wirmpolter! I have the unlock code, but it shows as unlocked, at least I get the dire warning about the device being unsafe on boot. I have the US model, build number MHA-L29 9.0.0.360 (C567), with both Android and EMUI versions listed as 8.0.0.
Click to expand...
Click to collapse
Oh...You're already bootloader unlocked that makes it even easier.
I'm using the system.IMG form the thread below this paragraph. Tried a few different aosp ROMs and it seems to be the best so far. Aside from a couple things of course. And the honor 8 Pro is the same CPU, GPU found in the mate 9.
https://forum.xda-developers.com/honor-8-pro/development/rom-t3758564.
In the main post of that thread, just follow step 2 and 3 and you'll be good to go for having an aosp ROM.
As for magisk/root... You can follow my guide below that I posted the other day. Just let the aosp ROM boot up once first. Also I can extract the ramdisk.IMG you'll need if you can't once you check it over.
https://forum.xda-developers.com/mate-9/how-to/guide-install-magisk-mate-9-running-t3773878
Basically in a nutshell to get setup on an aosp ROM is as follows
1 Download the ROM from the first thread i posted
2 Extract the system.img to where your adb folder is
3 Run command prompt from there
4 With your phone powered off. Hold the volume up button and connect it to your computer (fastboot screen)
5 Run command fastboot flash system system.img
6 Then type fastboot reboot but when you goto run this command get ready to hold the volume up button when the screen goes off so you can get the phone into stock recovery
7 Once in the recovery, perform a factory reset
8 Reboot the phone and should be good to go
Need to do first boot on its own before rooting

Thanks!!!
It will be about a week before I can try again but I'm looking forward to it. Are you pretty happy with it?

prestonmcafee said:
Thanks!!!
It will be about a week before I can try again but I'm looking forward to it. Are you pretty happy with it?
Click to expand...
Click to collapse
Yeah, fairly happy about it. A few bugs though but nothing major. Get better standby drain and about the same SOT time as EMUI. The only thing that is lacking is the camera in aosp doesn't use both cameras.
There is the stock camera port (works with magisk) but it's lacking a few things like video recording doesn't work... And umm not sure what else.

I needed to install an update, enable developer options and enable OEM unlocking (which was greyed out) before it would install. Here is my earlier post:
Dang, didn't work. Here is what I did.
-reset phone, but did not enable developer options.
-extracted and placed system.img in the minimal fastboot and adb folder. Ran a command prompt with administrative rights (win 10)
-shut off and connected Huawei mate 9 by USB, holding vol up
-vol up brought the EMUI restore screen. Shut off and tried again, same outcome. So shut off and tried vol down, and that brought up the fastboot screen. It reported phone unlocked but FRP locked.
-ran command "fastboot flash system system.img" and get:
target reported max download size of 471859200 bytes
sending sparse 'system' 1/4 (460796 KB)...
OKAY [ 11.167s]
writing 'system' 1/4...
FAILED (remote: Command not allowed)
finished. total time: 11.183s
I suspect this is due to the FRP locked condition.

Now I've run into a different problem: the EMUI screen gives me the options of
Download latest version and recovery
Reboot
Shutdown
It does not give me the option of a factory reset. What seemed to work was holding volume down through a couple of boots, when EMUI gave me the option of a factory reset. This gave me what appears to be a fully functioning system!

prestonmcafee said:
Now I've run into a different problem: the EMUI screen gives me the options of
Download latest version and recovery
Reboot
Shutdown
It does not give me the option of a factory reset. What seemed to work was holding volume down through a couple of boots, when EMUI gave me the option of a factory reset. This gave me what appears to be a fully functioning system!
Click to expand...
Click to collapse
Yeah, the FRP lock would prevent fastboot commands from working.
So, your system is back up and running?

OK, now that I have it up and running, here is the procedure I used, fixing what are either typos or variations because my system was slightly different. I unlocked the bootloader using instructions from:
http://www.teamandroid.com/2017/04/08/huawei-mate-9-unlock-bootloader/
I used Minimal ADB and Fastboot from
https://forum.xda-developers.com/showthread.php?t=2317790
I downloaded and extracted the system image from the link Wirmpolter provided:
https://forum.xda-developers.com/honor-8-pro/development/rom-t3758564
Here is a slightly edited set of instructions that worked for me:
a. unlock bootloader
b. reset phone
c. enable developer mode (settings/system/about phone tap on build number until developer mode is enabled), enable OEM unlock and USB debugging
d. check that FRP unlock and bootloader unlock worked by booting into fastboot screen (for me, hold VOL DOWN while booting)
1 Download the ROM from the thread above
2 Extract the system.img to where your adb folder is
3 Run command prompt from there (or use MA&F's desktop icon, which does the same thing)
4 With your phone powered off. Hold the volume DOWN button and connect it to your computer (fastboot screen)
5 Run command: fastboot flash system system.img
6 Then type fastboot reboot but when you goto run this command get ready to hold the volume up button when the screen goes off so you can get the phone into stock recovery
7 Once in the recovery, perform a factory reset [eRecovery didn't have this option, so I rebooted a couple of times while holding vol up and it eventually gave me the option to factory reset]
8 Reboot the phone and should be good to go

Up and Running!
Wirmpolter said:
Yeah, the FRP lock would prevent fastboot commands from working.
So, your system is back up and running?
Click to expand...
Click to collapse
I'm up and running. Thanks! So far, the only glitches are:
While Android can see and format the SD card (a Samsung 64GB), the SD card is invisible over a USB connection and Google Maps and my music player can't see it. File explorer and copy files to the SD card, so the SD card works.
The camera is terrible, but you have a fix for that.

I'm quite lost about how to install Magisk and a camera module
At the risk of asking too much, I have another request. I'm looking at how to install the stock camera on my Mate 9 with the AOSP, and here is my pathetic understanding of the steps.
First, I looked at your (Wirmpolter) instructions:
1. Install latest Magisk Manager from the Official Thread: https://forum.xda-developers.com/app...mless-t3473445
Follow the instructions of "Install Via Magisk Manager" in the main thread, but instead of providing the boot image (which these devices do NOT have), provide the stock ramdisk.img extracted from your Update.app using Huawei Update Extractor.
2. If you are using Mate 9 with model MHA-L29636 running on firmware ending in B362, you can download the stock ramdisk.img I extracted from official OTAs in the attachments
If you have stock ramdisk images for other devices, please share them and I'll add them to the OP.
3. Pull the patched image with adb pull /sdcard/MagiskManager/patched_boot.img, and flash the patched ramdisk via fastboot:
fastboot flash ramdisk patched_boot.img
Reboot and you shall have a properly rooted device passing SafetyNet, start playing with some Magisk modules!
Here are some questions:
1. Huawei update extractor
https://forum.xda-developers.com/showthread.php?t=2433454
I probably need help using this. The item I need extracted is the update.app, but where do I get the update.app that I extract from? And I'm extracting ramdisk.img?
2. download file for my phone that will be the source of the update.app in #1 (MHA-L29 8.0.0.366(C567)) from FunkyHuawei? Firmware finder? or from the phone itself? (see, I'm pretty lost)
3. install magisk manager (from https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445):
This method does not need root, and also does not require a custom recovery.
However, you MUST have a stock boot image dump beforehand, and you also have to be able to flash the patched boot image, either through fastboot/download mode or ODIN
Install the latest Magisk Manager -- this is an android app? Do I sideload it?
If you're planning to flash the patched boot image through ODIN, go to Settings > Update Settings > Patched Boot Output Format, and select .img.tar. For normal users leave it as the default .img
Press Install > Install > Patch Boot Image File, and select your stock boot image file
Magisk Manager will now patch your boot image, and store it in [Internal Storage]/MagiskManager/patched_boot.img[.tar]
Copy the patched boot image to your PC. If you can't find it via MTP, you can pull the file with ADB:
adb pull /sdcard/MagiskManager/patched_boot.img[.tar]
Flash the patched boot image to your device and reboot. Here is the command if using fastboot:
fastboot flash boot /path/to/patched_boot.img
Magiskmanager is an android app. How do I install on my phone? I was expecting this to be a windows app that would install magisk on my phone, so was thrown when it was an .apk.
Finally, the camera image is here:
https://forum.xda-developers.com/showpost.php?p=75848917&postcount=2
It isn't clear to me how to flash using Magisk, but perhaps that will be obvious once I have magisk operating.

prestonmcafee said:
1. Huawei update extractor
https://forum.xda-developers.com/showthread.php?t=2433454
I probably need help using this. The item I need extracted is the update.app, but where do I get the update.app that I extract from? And I'm extracting ramdisk.img?
2. download file for my phone that will be the source of the update.app in #1 (MHA-L29 8.0.0.366(C567)) from FunkyHuawei? Firmware finder? or from the phone itself? (see, I'm pretty lost)
Click to expand...
Click to collapse
Firmware Finder (they have Windows desktop and Android apps for it, and there's also http://pro-teammt.ru/firmware-database/ which does the job just as well, though it's all in Russian.)
Find the FullOTA-MF firmware that corresponds to your model, download the 'update.zip' that goes with it - on the website, it's under the link 'update' in the same row. If you do it on your phone in the Firmware Finder app, hit "Download" on the relevant detail screen and it'll prompt you for which files you want.
Once you've got the update.zip, extract it, you'll find a file UPDATE.APP, which is what the extractor wants. If it throws up an error, disable CRC checking of the extracted content. (I don't recall what the label for it is and I don't have it installed on the machine in front of me...); and yes, you'll want RAMDISK.img from it.
prestonmcafee said:
3. install magisk manager (from https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445):
Magiskmanager is an android app. How do I install on my phone? I was expecting this to be a windows app that would install magisk on my phone, so was thrown when it was an .apk.
Click to expand...
Click to collapse
Magisk Manager wants to create a patched ramdisk image. When it updates, it'll want to update the ramdisk image on your device (which it'll be able to do since it's running with root privileges itself anyway), but for the first pass, it needs that image provided and for you to manually flash it.

Thanks!
That is perfect. I downloaded the correct file from FF and I will try installing Magisk tomorrow or Sunday.

prestonmcafee said:
That is perfect. I downloaded the correct file from FF and I will try installing Magisk tomorrow or Sunday.
Click to expand...
Click to collapse
The magisk manager app apk you just run on your phone to install it, no side loading required.

Thanks! Magisk installed! To flash the camera app, I first extract and flash kernel.img from update.app with fastboot, put the camera zip (extract first?) in the magisk folder on the phone to install it with magisk?

That worked
prestonmcafee said:
Thanks! Magisk installed! To flash the camera app, I first extract and flash kernel.img from update.app with fastboot, put the camera zip (extract first?) in the magisk folder on the phone to install it with magisk?
Click to expand...
Click to collapse
That seems to have worked.

softbricked pixel

Hello everybody, hope u doing fine.
i was looking to root my pixel, so i installed kingroot and it rooted it just fine, then i wanted a root manager so i went to play store installed supersu (i guess that was the cause, i shouldn't have done that),then i opened it, it asked to download binaries(or install i'm not quite sure...), anyway this went fine too, then it sayed, everything gone right, restart your device, i clicked in reboot, it restarts with google logo and animations, but it bassicaly wont boot it is just stuck at the dots animation.
the problem is that i left oem bootloader locked, so now i can't do anything via fastboot adb... when i do: fastboot oem unlock , it says: failed (remote: oem unlock is not allowed)
i searched a bit more and found that we can unbrick qualcomm powered devices with qfil flashing tool, but requires a firmware wich is in .mbn format, wich i don't find on the internet (at least for the pixel), maybe there's a custom rom in mbn format...
i'm on android 7.1.2, stock rom, unlocked version.
please tell me if there's a way to fix that,
thank you in advance ? !

luigigigi said:
Hello everybody, hope u doing fine.
i was looking to root my pixel, so i installed kingroot and it rooted it just fine, then i wanted a root manager so i went to play store installed supersu (i guess that was the cause, i shouldn't have done that),then i opened it, it asked to download binaries(or install i'm not quite sure...), anyway this went fine too, then it sayed, everything gone right, restart your device, i clicked in reboot, it restarts with google logo and animations, but it bassicaly wont boot it is just stuck at the dots animation.
the problem is that i left oem bootloader locked, so now i can't do anything via fastboot adb... when i do: fastboot oem unlock , it says: failed (remote: oem unlock is not allowed)
i searched a bit more and found that we can unbrick qualcomm powered devices with qfil flashing tool, but requires a firmware wich is in .mbn format, wich i don't find on the internet (at least for the pixel), maybe there's a custom rom in mbn format...
i'm on android 7.1.2, stock rom, unlocked version.
please tell me if there's a way to fix that,
thank you in advance ? !
Click to expand...
Click to collapse
Did you try turning the phone off and then using the power-on + volume down key to get to the bootloader menu? from there press the volume up key until you get to recovery and the press the power button. In recovery do a factory reset. That should take care of stuff. In future, don't use kingroot as it's a malware ridden app (that is if you care about your personal data). If you need root then use Magisk instead. Gives you root and also a root manager. If you are planning to tamper with root then make sure to have your bootloader unlocked. Let me know if factory reset worked.

yes i tried to factory reset it from recovery mode ( i did that twice ) and that didn't help.

luigigigi said:
yes i tried to factory reset it from recovery mode ( i did that twice ) and that didn't help.
Click to expand...
Click to collapse
I have one more idea you could try. Download latest OTA update from here: https://developers.google.com/android/ota
go into recovery and follow the instructions given on the link I just gave you and apply the update using adb sideload in recovery. (You have to manually get into recovery as you did before but follow the instructions from the point where you're inside the recovery.) This should work. Seems that kingroot/supersu corrupted your system somehow. Let me know if it worked.

i already came across that site because i was on android p, i didn't like it so i went back to nougat...anyway to say that i have the nougat image .zip , so do i have to download the latest firmware ?

ok ok, that's not the same...SORRY ?? !!

luigigigi said:
ok ok, that's not the same...SORRY ?? !!
Click to expand...
Click to collapse
yeah, it's not the same and you'll find the 8.1.0 update there and the updates from the past. Give it a go and tell me the results when you're done

i tried that, everything went as intended, when i power it up there's animations of 8.1 but still wont boot.
i tried to wipe data and boot again, nothing.
is there a way to flash stock rom with adb (just like we did with that update) ?

now, the phone just booted up and i'm on the set up screen, BUT it showed me a pixel 2 , and theres a lock at the top left corner and it asked for a pattern (cause i did a wipe)... it's like another phone stuck in mine ?!

---------- Post added at 04:28 PM ---------- Previous post was at 04:26 PM ----------
[/COLOR]
luigigigi said:
now, the phone just booted up and i'm on the set up screen, BUT it showed me a pixel 2 , and theres a lock at the top left corner and it asked for a pattern (cause i did a wipe)... it's like another phone stuck in mine ?!
Click to expand...
Click to collapse
It's the newer setup screen. Have you managed to boot into system. Is everything working?

Arju said:
---------- Post added at 04:28 PM ---------- Previous post was at 04:26 PM ----------
[/COLOR]
It's the newer setup screen. Have you managed to boot into system. Is everything working?
Click to expand...
Click to collapse
no since i did a wipe ( i guess i shouldn't have done that) , now when it boots it is locked, it is asking for a pattern, wjch i don't know because i didn't set a pettern previously.
i guess i'm stuck here for ever ? ??

is there a way to flash the stock firmware via stock recovery or external flashing tools on pc, if yes please explain how !

((((Update))))
I didn't notice that there was a connect to Google option, so I finally set up the phone with my Google account and I'm back in.
I'm very thankful to you man you saved my phone, thank you a lot.
(Are you from India ? ? I love a lot India it's a beautiful place to visit and I really hope I could travel there once in my life, greatings from Algeria ?? )

luigigigi said:
(Are you from India ? ? I love a lot India it's a beautiful place to visit and I really hope I could travel there once in my life, greatings from Algeria ?? )
Click to expand...
Click to collapse
I'm glad it worked itself out.
I'm from Norway. Married a swede so living in Sweden now. My parents are from Sri Lanka (the island below India) but moved to Norway before I was born. I've been to Sri Lanka once. Would like to travel to India sometime too :silly:
Algeria seems nice. Must be hot there. I've never been to Africa. Would like to travel there too some day

Yes totally, Algeria is really safe and people here won't bother you (like if you're wondering how u would be seen or received as a foreigner) there's foreigner all year round but especially in summer time, just have something planned in advance because it's Algeria not USA or another well developed country ? but still there's a lot to see here, definitely worth the visit.
When it comes to whether, well it's a Mediterranean weather so expect nice warm days, that being said, there's some time when it goes rainy with thunders and cold, for example now it is very pleasant outside, but yesterday the weather gone crazy... I guess that's because of the global warming.

luigigigi said:
is there a way to flash the stock firmware via stock recovery or external flashing tools on pc, if yes please explain how !
Click to expand...
Click to collapse
1) Install the Google Android driver if your Pixel isn't already recognized by your computer when booted to fastboot mode.
https://developer.android.com/studio....html#download
2) Download the factory system image for Pixel to C:/Google
https://developers.google.com/android/images
3) Unzip the system image folder into same folder, same with adb/fastboot tools in C:/Google
4) Run these commands in cmd prompt as administrator while Pixel is in bootloader mode
adb reboot-bootloader
fastboot flash bootloader bootloader-sailfish-*.img
fastboot reboot-bootloader
fastboot flash radio radio-sailfish-*.img
fastboot reboot-bootloader
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
fastboot flash system system.img
fastboot flash system_b system_other.img
fastboot flash vendor vendor.img
fastboot flash modem modem.img
fastboot reboot
hope this helps

MpandAUS said:
1) Install the Google Android driver if your Pixel isn't already recognized by your computer when booted to fastboot mode.
https://developer.android.com/studio....html#download
2) Download the factory system image for Pixel to C:/Google
https://developers.google.com/android/images
3) Unzip the system image folder into same folder, same with adb/fastboot tools in C:/Google
4) Run these commands in cmd prompt as administrator while Pixel is in bootloader mode
adb reboot-bootloader
fastboot flash bootloader bootloader-sailfish-*.img
fastboot reboot-bootloader
fastboot flash radio radio-sailfish-*.img
fastboot reboot-bootloader
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
fastboot flash system system.img
fastboot flash system_b system_other.img
fastboot flash vendor vendor.img
fastboot flash modem modem.img
fastboot reboot
hope this helps
Click to expand...
Click to collapse
I'm sure this gonna help me in the future, as i'm planing to try some custom Rom's and i'm probably gonna brick it again so ? ... Thanks you ? !

Was Bricked - CLT-L04 with EMUI 8.1 - the fixed ended up giving me EMUI 9 CLT-L04

Bricked my phone by doing the following:
Honor View 10 ROMs are compatible with P20 Pro, I installed and used them all. Then the other day they made a mod that force the EMUI 9 update so I ran it. The mod ended rebranding my entire phone to Honor View 10 followed by boot loops like crazy. So then I went into twrp and tried to format thinking it would help. It ended up deleting everything including eRecovery. The only this I had access to was fastboot. Yes I brought this on my self lol. I paid a lot for Funky Huawei but nothing worked. I tried every tool they had.
Fix: (Turns out my phone's structure is now EMUI 9\Android 9)
1- Downloaded my phone image (CLT-L04 - EMUI 9 version), extracted the update.app file from it.
2- Used EMUI extractor app to extracted everything from the update.app file (Lots of image files)
3- Noticed userdata.img wasn't in the extracted files so I downloaded multiple images that are similar models to my phone until I found it.
4- Used fastboot command to flash the userdata.img, followed by eRecovery.img, followed by the rest I pulled from that update.app file.
after about three reboots I was back into my phone except I now have EMUI 9.

My case is similar. I downgraded from B195 to rollback B161. Now I am literally doomed. No erecovery, no huawei logo, just plain black fastboot screen. My bootlodaer is unlocked and I'm unable to relock it. Huawei is denying service, is there any way to revive my black dead phone???
twrp.img gets flashed succesfully but doesnt boot into it.

QuazIqbal said:
My case is similar. I downgraded from B195 to rollback B161. Now I am literally doomed. No erecovery, no huawei logo, just plain black fastboot screen. My bootlodaer is unlocked and I'm unable to relock it. Huawei is denying service, is there any way to revive my black dead phone???
twrp.img gets flashed succesfully but doesnt boot into it.
Click to expand...
Click to collapse
Can you try this.
Files that you will be downloading are,
update.zip
update_full_CLT-L29_hw_eu.zip (Or whatever model of phone you have)
Get them here by searching for your model and click filelist
Prep:
a. Rename update_full_CLT-L29_hw_eu.zip to update_all_hw.zip
b. Download this Flash tool and extract in to a folder in your PC
c. Copy update.zip and update_all_hw.zip to ZIPS-HERE folder (you can find this folder where you have extracted Flash tool
How to flash Firmware
1. Double click to run the file cmd-here.exe. It opens command prompt in the same folder where you are.
2. Once command prompt opens, type FLASH.bat and follow steps carefully. Once flashing is complete, it will boot normally.
- if it fails to detect the files try removing the .zip from the names of the files in the ZIPS-HERE folder
This should bring back eRecovery, recovery, system, whatever. Even at the end if it fails the structure should be rebuilt enough for you to recover via HiSuite application. This worked for me.

Vedrick said:
2. Once command prompt opens, type FLASH.bat and follow steps carefully. Once flashing is complete, it will boot normally.
- if it fails to detect the files try removing the .zip from the names of the files in the ZIPS-HERE folder
This should bring back eRecovery, recovery, system, whatever. Even at the end if it fails the structure should be rebuilt enough for you to recover via HiSuite application. This worked for me.
Click to expand...
Click to collapse
Thanks for offering your help. Mine case looks different....
I have tried this, after flashing twrp in the fastboot the device fails to boot into twrp recovery, it's all black, only fastboot is accessible in the black screen.

I experienced the same problem. Bricked my P20 Pro and can only access fastboot (no access to erecovery). Could you tell me which image that you used to flash userdata.img and erecovery.img? I tried several images but none of them contains userdata.img and erecovery.img.
Thanks.
Edit:
Also, aside from userdata.img and erecovery.img, what files did you flash to the phone?

przival said:
I experienced the same problem. Bricked my P20 Pro and can only access fastboot (no access to erecovery). Could you tell me which image that you used to flash userdata.img and erecovery.img? I tried several images but none of them contains userdata.img and erecovery.img.
Thanks.
Edit:
Also, aside from userdata.img and erecovery.img, what files did you flash to the phone?
Click to expand...
Click to collapse
Update : Good news finally. My device is now unbricked by flashing downloaded OTA from Firmware Finder (Oreo B161 simple non-rollback version) using DC phoenix via testpoint mode. P.S. Flashing B195 pie didn't worked earlier.

QuazIqbal said:
Update : Good news finally. My device is now unbricked by flashing downloaded OTA from Firmware Finder (Oreo B161 simple non-rollback version) using DC phoenix via testpoint mode. P.S. Flashing B195 pie didn't worked earlier.
Click to expand...
Click to collapse
Nice one!!
Can I ask that you help me out as I'm in the same situation? I'm scared about removing back cover and loading credit to CD and still not being able to fix it. A step-by-step idiots guide would be greatly appreciated.
How was it removing the back?
Did you need to buy a new back glass case?
Were are the test points and how do you trigger them?
What FW did you use exactly?
Sorry for the questions but I've yet to find anyone who's provided help to sort it.

QuazIqbal said:
Update : Good news finally. My device is now unbricked by flashing downloaded OTA from Firmware Finder (Oreo B161 simple non-rollback version) using DC phoenix via testpoint mode. P.S. Flashing B195 pie didn't worked earlier.
Click to expand...
Click to collapse
can i ask you are your phone relock after update or not ??if yes are you unlock your phone again with same number and in the end can you give us full guide what you done to unbrick your phone

Deano1889 said:
Nice one!!
Can I ask that you help me out as I'm in the same situation? I'm scared about removing back cover and loading credit to CD and still not being able to fix it. A step-by-step idiots guide would be greatly appreciated.
How was it removing the back?
Did you need to buy a new back glass case?
Were are the test points and how do you trigger them?
What FW did you use exactly?
Sorry for the questions but I've yet to find anyone who's provided help to sort it.
Click to expand...
Click to collapse
I will do my best to answer tomorrow, God willing. Please wait
---------- Post added at 09:04 PM ---------- Previous post was at 08:55 PM ----------
black_1986 said:
can i ask you are your phone relock after update or not ??if yes are you unlock your phone again with same number and in the end can you give us full guide what you done to unbrick your phone
Click to expand...
Click to collapse
After this process your bl will be in 'locked' state. If you had my kind of downgrade brick the imeis and serial will number will not be disturbed. You may simply use your old bl code to unlock. However I messed up my oeminfo but due to my own stupidity, I'm looking to restore my imei and will try to unlock again.

If possible, could you share the files you use?