P20 pro flashing error - Huawei P20 Pro ROMs, Kernels, Recoveries, & Other

Well i was tired and did the mistake to flash boot via twrp app. Now phone cant boot system of curse.
looking for advice for faster repair as im traveling and internet is not that good. I tried to access Twrp but i cant even after reflashing the image. My bootloader in unlocked and im in emui 9.1. i had saved boot.img and recovery.img but there are in the phone.
any help or advice please ?

Rovyo said:
Well i was tired and did the mistake to flash boot via twrp app. Now phone cant boot system of curse.
looking for advice for faster repair as im traveling and internet is not that good. I tried to access Twrp but i cant even after reflashing the image. My bootloader in unlocked and im in emui 9.1. i had saved boot.img and recovery.img but there are in the phone.
any help or advice please ?
Click to expand...
Click to collapse
Hello!
If still problem, please write me...
1. TWRP recovery installed this phone, and running?
2. Boot partition available this phone?
3. Available any backup this earlier system?
Please test the HISUITE software! If not recognise, need TWRP full backup.
I have only CLT-L09 8.1 TWRP clean backup. (After 8.1 not rootable.) The filesytem formatted another "unsecured" type and installed another patch to TWRP R/W full control:
nocheck.img (bootloader)
Disable_Dm-Verity_ForceEncrypt_v1.4.zip (disable encrypting)
The TWRP restore only one fast method. (~5-10 min)
Other:
Pay more USD to minimal 3 day licence DC-Unlocker / DC-Phoenix. Need unassembly the back cover and more cover to start TEST MODE (need to DC-Unlocker softwares). This softwares upload any firmware completly in test mode.
Test mode: upload patched bootloader and reboot this bootloader to flash firmware.
10-20$ + 20-30min + more to install TWRP and disable security.
Another free softwares freezing or not comaptibiles the standard FW files.

Hello!
My phone running correctly more time...
Now slow down, Lucky Patcer patcing apk-s and not patched --> uninstalled from system in patchning.
Manually shutdown this phone... (Shutdown - yes) wait, and not power on, not charging.
Plugged to PC, PC say: USB-COM mode.
Used IDT 2.0.0.9 to reflash.
After writing NVME, failed writing.
Cleared NVME line in XML file and flashed again. Flashing ended correctly.
Phone not start.
Replug and not available USB-COM mode, windows not recognize the phone (testpoint starting: same). (With/without battery: same.)
Now fully bricked the phone. Tested 2 PC, plugged USB (with/without testpoint start) no device.
Available all partition IMG file (backup, 1 year old) and TWRP WIM files (1 day old). Restore easy, only need running TWRP.
How to unbrick? DC-Phoenix/IDT work only USB-COM mode... now not recognise any (ADB/COM) mode.
Thanks!

Related

Bricked mate s

PLEASE help : My phone stopped working after trying to change it to a L09 and now is dependent on the company's logo and does not accept any Software
You need to read about flashing from the bootloader using fastboot. You will be able to get it back working but you will need to get an extracted rom to flash the right parts.
Now I have a bit of time, I will tell you how I solved my issues. My phone was stuck with only the bootloader screen available or the eRecovery screen which would not find any suitable download. It said that the bootloader was unlocked yet I could not flash anything that I have extracted using the ROM extractor.
After much frustration I opened and ADB session and used Fastboot commands and re-entered the number in the Fastboot OEM Unlock command and it then confirmed that it was actually unlocked. It seems that although it said it was, it really wasn't.
Now that I knew it was unlocked, I could now start to flash parts of the extracted ROM.
I used the Huawei Rom Extractor tool to extract the Boot, Cache, Cust, Recovery, System and the Userdata image files of the ROM I needed and in this case it was the CRR-UL00470B110. I renamed the extracted files and removed the prefix numbers and put them in the ADB folder for ease of flashing.
I then used the Fastboot command to flash each part in the normal Fastboot format i.e. - Fastboot flash system system.img , and so on for each part. A reboot after brings it up in a nice new live usable phone. Well that is what I thought until I started to load the apps back on. I then noticed that I only had about 3gb left of my 64gb of memory! This took me a while to resolve and after more reading, more flashing of different ROMs I found the answer.
I had to flash the TWRP recovery using Fastboot, then format the data partition from TWRP. This restored the full size of the partition. Another flash of the correct recovery using Fastboot left me with a fully working unbricked Mate S.
I know that some of you may know all about this but I could not find any information and had to work through it myself and from various websites. I hope that this will help you to unbrick your phone.
I still think there may be something missing like the oeminfo file etc. but at least it works, you may just have to update it in future using adb and Fastboot if no OTA is available or works. Not too much of a worry now you know how to do it.
I should also add that if you ever get an 'Invalid Argument' when flashing in fastboot mode and some oparts flash while others dont, it will be your cable. Trust me, one cable workws well another gives you this Invalid Argument error! Strange but true and may catch you out.
Thank you(Sathelp) to help me to solve the problem of mate s mobile, but I found only three orders adb work when used fastboot screen, there are boot, recovery and cust but the system and other order give fault result in adb. Therefore the phone remain broken. ..sorry for language
Is it possible to provide me a complete backup copy of the phone to be downloaded to my phone via the twrp recovery , perhaps back to life again, I would be grateful to you
my p[hone is a U00 not a L09, so my back up will not work. Have you changed your cable, I had simular problem, changed cable and other ROM parts worked OK. If not, then you will need to ask for a L09 TWRP back up from here. May be someopne will make one for you.
Finally, the problem has been resolved and the phone returned to work and all this is due to the help of (Sathelp), which benefited greatly from his observations in this matter ,the issue has been resolved by updating the ADB and the execution of an order (FASTBOOT FLASH SYSTEM.IMG) , which i could not be implemented except adb updated, but the phone remained unresponsive for OTA updates and remained on the android 5. Thank to xda forums.
Glad it is now working
Huawei Mate S CRR-L09 bricked
Hi
I have a Huawei Mate S (CRR-L09) does not work and remains stuck on the android logo. Mention that is installed TWRP and I tried to "wipe data factory reset". I accidentally erased everything on it, including Systema. I did not back up your data and restore the system. I downloaded firmware B145 stock on which I copied to root your phone but, but can not flash TWRP. I entered the menu Update (Vol + Vol- and Power) but does not see that folder "dload". Can someone help me with a backup or a tutorial on how to flash TWRP firmware.
Thank you

Need Help. ADB, Recovery and Fastboot/Download Mode don't work

Hey xda community,
last night i run into a tricky situation.
First, I explain what I did
I bought me the P9 EVA-L09 via Telekom Germany.
cause i don't want the Telekom **** on my device i decide to TWRP, Root, and flash P9 stock Rom on it.
Unlocking and install TWRP with the SRK Tool works fine. Install the Root was a bit more tricky, because windows lost the correct ADB connection when i go into TWRP Sideload Mode. Because that does not work, i decide to flash the P9 Stock ROM without Root to come forward.
While flashing, (i don''t now anymore which method i choose to flash) an error appers, and the flash process canceled.
The Device don't boot anymore. After a loot of googeling and testing, i've found out that the problem was the encryption of the /Data Partition.
TWRP was unable to mount it, same for the /cust and one more.
After reading about other Methods to get the Phone work again i try this Method i've found on xda.
http://forum.xda-developers.com/p9/development/stock-rom-dload-file-p9-eva-l09-b136-t3382818
Unfortunately the "press all buttons on the phone" Method don't work.
I also tried out the Huawei Update Extractor to flash single image files to the partitons of the phone. I used the dload file form the previous Method
http://forum.xda-developers.com/showthread.php?t=2433454
http://www.modaco.com/forums/topic/372688-re-partition-stock-partition-tool/ (using the answer on the bottom)
Download from xda huawei update extractor and extract img files from the update.
Turn off the phone, then press vol- and power key, you are in fastboot mode.
Then, flash img files from extracted rom with:
Fastboot flash system SYSTEM.IMG
fastboot flash boot BOOT.IMG
And do the same with the others...
When you finish, fastboot reboot
Click to expand...
Click to collapse
But that don't work. fastboot already replies with "Remote Command not allowed"
i changed the Method a bit. I've put the BOOT.IMG and RECOVERY.IMG an an SD card and flash it via the Install IMG Funktion of TWRP.
That workes very well and expect the /data partition every partition was mountable again.
Then i used the "Fastboot flash system SYSTEM.IMG" again, and tada it works without errors.
The device is booting again to Android, but it reports that the /Data Partition Decryption failed and i have to enter the Recovery Mode and do a factory reset to unlock the partition. If i reboot for get rid of this error the phone does not boot into the Recovery, it boot to the eRecovery which is useless for that because it only provide the eRecovery function instead of also a normal factory reset (how dump is this )
Now the state is, phone boots normal, reports the /Data is not decryptable, reboot to eRecovery, shutdown or reboot. It does really nothing else.
I can't get into the Fastboot/Download Mode, it ignores the Key Combination Volume down + Power. If i press this it starts normal.
I also can't get into the recovery / TWRP Mode, it ignores the Key Combination Volume Up + Power. If i press this is starts normal.
I've also noticed that the Phone is not conecting to the ADB on my computer, only the virtual CDROM from wich the HiSuite is installable connects.
I've also noticed that the eRecovery is not able to starts WIFI on the phone. It errors with "Starting WIFI failed!"
I also tryed out another time the dload function. This changed nothing. Phone boots still normal and run into the Decryption problem.
And i tried out to boot into fastboot or recovery after a cold reset, battery empty
Now it's on you. Has anybody an idea how i can solve one of the above problems. I think when one is solved the others will disappear via flashing new TWRP or so
Try connecting your phone to usb and then holding power+volume down until it boots to fastboot mode.
Huawei phone won't boot into recovery if system and twrp don't match but it should boot to fastboot allways.
What is the last rom you had on your phone while it was working?
Ogameplayer said:
Hey xda community,
last night i run into a tricky situation.
First, I explain what I did
I bought me the P9 EVA-L09 via Telekom Germany.
cause i don't want the Telekom **** on my device i decide to TWRP, Root, and flash P9 stock Rom on it.
Unlocking and install TWRP with the SRK Tool works fine. Install the Root was a bit more tricky, because windows lost the correct ADB connection when i go into TWRP Sideload Mode. Because that does not work, i decide to flash the P9 Stock ROM without Root to come forward.
While flashing, (i don''t now anymore which method i choose to flash) an error appers, and the flash process canceled.
The Device don't boot anymore. After a loot of googeling and testing, i've found out that the problem was the encryption of the /Data Partition.
TWRP was unable to mount it, same for the /cust and one more.
After reading about other Methods to get the Phone work again i try this Method i've found on xda.
http://forum.xda-developers.com/p9/development/stock-rom-dload-file-p9-eva-l09-b136-t3382818
Unfortunately the "press all buttons on the phone" Method don't work.
I also tried out the Huawei Update Extractor to flash single image files to the partitons of the phone. I used the dload file form the previous Method
http://forum.xda-developers.com/showthread.php?t=2433454
http://www.modaco.com/forums/topic/372688-re-partition-stock-partition-tool/ (using the answer on the bottom)
Download from xda huawei update extractor and extract img files from the update.
Turn off the phone, then press vol- and power key, you are in fastboot mode.
Then, flash img files from extracted rom with:
Fastboot flash system SYSTEM.IMG
fastboot flash boot BOOT.IMG
And do the same with the others...
When you finish, fastboot reboot
But that don't work. fastboot already replies with "Remote Command not allowed"
i changed the Method a bit. I've put the BOOT.IMG and RECOVERY.IMG an an SD card and flash it via the Install IMG Funktion of TWRP.
That workes very well and expect the /data partition every partition was mountable again.
Then i used the "Fastboot flash system SYSTEM.IMG" again, and tada it works without errors.
The device is booting again to Android, but it reports that the /Data Partition Decryption failed and i have to enter the Recovery Mode and do a factory reset to unlock the partition. If i reboot for get rid of this error the phone does not boot into the Recovery, it boot to the eRecovery which is useless for that because it only provide the eRecovery function instead of also a normal factory reset (how dump is this )
Now the state is, phone boots normal, reports the /Data is not decryptable, reboot to eRecovery, shutdown or reboot. It does really nothing else.
I can't get into the Fastboot/Download Mode, it ignores the Key Combination Volume down + Power. If i press this it starts normal.
I also can't get into the recovery / TWRP Mode, it ignores the Key Combination Volume Up + Power. If i press this is starts normal.
I've also noticed that the Phone is not conecting to the ADB on my computer, only the virtual CDROM from wich the HiSuite is installable connects.
I've also noticed that the eRecovery is not able to starts WIFI on the phone. It errors with "Starting WIFI failed!"
I also tryed out another time the dload function. This changed nothing. Phone boots still normal and run into the Decryption problem.
And i tried out to boot into fastboot or recovery after a cold reset, battery empty
Now it's on you. Has anybody an idea how i can solve one of the above problems. I think when one is solved the others will disappear via flashing new TWRP or so
Click to expand...
Click to collapse
Try this.
http://forum.xda-developers.com/p9/how-to/tools-huawei-p9-firmware-updater-t3432457/page1
Sent from my HUAWEI VIE-L29 using XDA Labs
I see two possibilites for this behavior:
1) The phone only pretents to reboot but makes a kind of warm start (never running the code to branch to recovery/boot) -> if the phone seems powered off and you attach usb cable, do you see standard battery laoding animation (that's what it should be) or black screen / boot logo?
2) You flashed a wrong boot.img and/or recovery.img or flashing got screwed up
If you have wrong images, fastboot should still work as edint3000 said.
For the unlikely case (1) with non removable battery you have to wait until battery is drained before you can boot into fastboot after connecting USB cable. Edit: oops just saw you did that.
I had another phone that at some point decided to go only in fastboot with volume down and no power button, when powered up with USB power. But I had never such an issue with a Huawei phone. However, playing around a bit costs nothing (but time).
I see no reason why fast boot should not work. How did you find out, that everything is fine after flahing with TWRP and before flashing system with fastboot?
Did you do anything else than flashing the system.img with fastboot?
Chilli
Same problem here...Phone not boot/not enter fastboot mode/not enter recovery mode...just stuck "your device booting now" screen...any solution?
Hello Mossyhand
you should search for the recovery Method with an "dload" ROM. This are kind of special Roms wich are able to "selfflash" onto the phone.
You have to put the right file onto your SD Card and then you have to press some keys when i remember right.
Sadly i've forgot, when i solved my problem, to reply how i did that exactly ._.
But if you do search in the dload method you will figure a way out i guess
If you don't find an right file, i can upload you my file, i have it still on my computer
had the same problem
go into the erecovery, it will tell you the data partition has been damaged. u can wipe it from there. go into trwp again, install rom and stuff. voila, works
cheers

Bootloop to recovery [solved]

Hello everyone, I have the problem, that my 3T boots to recovery every time I boot. The system is no more booting. What I did was, "updating" in the CM about/update menu (from unofficial cm14.1 13.12. to 14.12. ).
So maybe an open recovery script was created and booted to bootloader. Update failed but I did it manually.
From now on the phone does just only boot twrp recovery (or is it a boot loop ?). I tried to restore a backup and install the oxygen os via zip and wiped all partitions (except internal storage) but nothing helps. Does anyone know this and can give me advice ? Thank a lot in advance.
Edit:
For the OnePlus One if found an error report which look a little bit my error:
The problem is suspected to stem from the "persist" partition getting corrupted during the reboot, even though CyanogenMod doesn't use this particular location. The damaged area doesn't get fixed like other partitions because a filesystem integrity check isn't ran. It's left corrupted, and even though the area isn't needed for the OS to run, the OnePlus One boot loops anyway.
Click to expand...
Click to collapse
But the partition layout on the 3T seems to be different, I can see only partitions like sda etc ...
same here
Called the 1+ support and they sent me the same file like in this post http://forum.xda-developers.com/oneplus-3t/help/unbrick-unbrick-tutorial-oneplus-3t-t3515306 They offered me a telephone support slot in 2 days, but I tried myself, now the default system is booting again. If you need assistance write I can guide you as best as i can.
Good luck to you.
sniperle said:
Called the 1+ support and they sent me the same file like in this post http://forum.xda-developers.com/oneplus-3t/help/unbrick-unbrick-tutorial-oneplus-3t-t3515306 They offered me a telephone support slot in 2 days, but I tried myself, now the default system is booting again. If you need assistance write I can guide you as best as i can.
Good luck to you.
Click to expand...
Click to collapse
Thank you!
Enviado do meu ONEPLUS A3003 através de Tapatalk
Thnaks so much
sniperle said:
Called the 1+ support and they sent me the same file like in this post http://forum.xda-developers.com/oneplus-3t/help/unbrick-unbrick-tutorial-oneplus-3t-t3515306 They offered me a telephone support slot in 2 days, but I tried myself, now the default system is booting again. If you need assistance write I can guide you as best as i can.
Good luck to you.
Click to expand...
Click to collapse
:good:
I follow your recommendation thanks for your assistance I fixed my OP3T,
What a mess ... after all this I wanted to install my CM backups again, but TWRP refused to boot. I had only a black screen with a white LED when going to recovery. But now after some hours I have a solution to this. You need to update Oxygen OS before going on !!
Make a full system update or flash this update via TWRP: http://downloads.oneplus.net/oneplus-3t/oneplus_3t_oxygenos_3.5.3/
After this TWRP is booting as expected.
Now I'll enjoy a beer or two or ....
Good luck to all others. If anybody needs assistance ... contact me.
never had a issue
Please help!!!! I tried flashing the update for the latest OTA, I had the full zip. I have unlocked bootloader, twrp, phh supersu, magisk and xposed. I did a nandroid backup and then clicked Wipe- Dalvik and Cache. I then flashed the zip. For 20 mins the boot logo was spinning around, so I rebooted into twrp to see what was going on. Now I can't reboot and it shows no data, it says my device is encrypted and I can't see any files. What can I do??
Was your internal storage encrypted before ?
TWRP doesn't show your internal storage and didn't ask for a password ?
fix bootloop
Boot into your recovery [Vol+ and Power]
Connect your phone to your PC
Execute the following fastboot command on your PC (More informations on fastboot)
Code:
fastboot continue
Your phone will start right away. :good:
I solved the problem
OK what i did was when the phone was starting and vibrating I push the power bottom and volume down bottom at the same time ,then i connected the phone to the PC,from the panel in the phone there are 3 categories to erase everything on the phone I did it all(1,2,3) and then I put the phone in ADB mode from the control panel in the phone,After that I flash via fastboot the original .zip from one plus for the version 4.0.3 (1.4 GB) ,when it finished I restarted and the phone started normal again,I hope this help someone alse,I was so desesperated:silly:.
RE
TOMASITO95 said:
OK what i did was when the phone was starting and vibrating I push the power bottom and volume down bottom at the same time ,then i connected the phone to the PC,from the panel in the phone there are 3 categories to erase everything on the phone I did it all(1,2,3) and then I put the phone in ADB mode from the control panel in the phone,After that I flash via fastboot the original .zip from one plus for the version 4.0.3 (1.4 GB) ,when it finished I restarted and the phone started normal again,I hope this help someone alse,I was so desesperated:silly:.
Click to expand...
Click to collapse
how ? can you please teach me ( my op3t didn`t go to system is says " md5 checksum failed , recovery failed , boot failed , system failed , boot_aging failed , dsp failed , modem failed please help me (
Change USB port
Try a different USB port. I flashed it through a 2.0 USB port instead of the 3.0 and no checksum error!

BOOT problem

99% SOLVED
Hello all.
EDIT 070117 Partially SOLVED - after 0% battery is possible enter to FastBoot, but problem with TWRP or Unbrick stay...
EDIT 2 only Revolution recovery is going, but no efect... still trying install OS
I tried install Revolution ROM on my Huawei P9 lite (1 SIM card model for Europe - LN21), I unlocked BOOTloader, flash recoveries and ROMs, but after last install phone reboot ONLY in "wait for boot" mode... No acces to recoveries and FASTBOOT mode.....
Any ideas?
Thanks..
EDIT 10 01 2017
After about 100 reflashing everything inside OS works only 1 solution (99%) - i was on broke Nougat, nothing work correctly....
go to fastboot (turn off, hold down volume and plug USB - PC)
1. flash twrp beta 9 from BadWolf
2. Flash this zip http://forum.xda-developers.com/atta...1&d=1481994704
IN CASE OF UNABLE MOUNT ANY PARTITION - USE product v_3 (twrp restore by Badwolf)....
3. Put the MM UPDATE.APP in the DLOAD folder on EXTERNAL SDCARD (it is possible use internal storage, i used VNS-L21XXXXX120)
4. Install it using the 3 button method (dload method) but sometimes work only + volume and power on
5. Factory reset
In case - decryption code need, only write anything and ask on revert data by eRecovery....
Now everything works correctly , ONLY FASTBOOT DONT WORK yet....
PS SORRY for terrible english!
6. DONE!!
mrmajco said:
Hello all.
I tried install Revolution ROM on my Huawei P9 lite (1 SIM card model for Europe - LN21), I unlocked BOOTloader, flash recoveries and ROMs, but after last install phone reboot ONLY in "wait for boot" mode... No acces to recoveries and FASTBOOT mode.....
Any ideas?
Thanks..
Click to expand...
Click to collapse
Nobody know?

NEM-L21: Stucked with wrong version of boot.img, no more possibility of flashing

Hello everyone, it's my first time writing here, but I’ve tried everything, searched everywhere, and am desperate for help.
I screwed up big time while trying to flash a custom rom on my nem-l21, as I successfully did before with my xiaomi... So what I did:
I managed to unlock bootloader with dc unlocker. Then I got stucked flashing twrp with adb tools. Everything was looking to be fine, no error messages, “flashing successful”… But, I was never able to boot into flashed twrp. Always got stuck on “your phone has been unlocked blah blah. Your device is booting.” It never booted, not in twrp, nor in stock recovery. I tried different versions of twrp from different sources, always same result (flashing successful, booting into recovery not). Booting into the system was fine. And then I made that horrible mistake. Oh, how I wish I didn’t!!
I read on some website, that you are supposed to flash the twrp as boot.img, not as recovery.img. Seemed illogical and stupid to me, but in the end I tried it. Of course, this just bricked my phone, with no possibility to boot. After hours of googling, installing, trying and crying, I managed in the end to flash back stock boot.img. But at that time, I didn’t know my build number (b359), and I flashed boot.img b351. So now I have a phone which boots into the system b359 with boot.img b351, but with lot of errors.
- developer options, security options, display and factory reset option doesn’t work and just crashes. Therefore I am not able to flash the correct boot.img b359 or anything else at all from pc, no way to enable usb debugging and oem unlocking. Adb devices → nothing. I am able to use fastboot (fastboot devices sees the phone), but when try to flash something, I get error “command not allowed”. Also I can’t enable unknown sources installation, which bothers me a lot. And I can’t make factory reset to restore the crashing settings. Also I can’t change display timeout, and original 30 secs is super annoying.
- I am not able to uninstall even apps installed by me, always just restarts system UI and app stays.
What I tried so far:
- flashing correct boot.img from pc, not working because of dev options crashing
- go into recovery, but stock one is overwritten with unfunctioning twrp, always just get stuck on “your phone was unlocked blah blah… your device is booting now”, but it never does, have to hard reboot
- go into huawei erecovery, which is working, but when I try to resolve problem from there, always ends up with errors and crashes
- connect to pc and use HiSuite, system recovery tool here always says “no problem detected”
- updating to b361 through system update settings, always crashes on 5% and sends phone into “your phone was unlocked blah blah… your device is booting now” error
- downloading the proper b359 as and update.app file, put it in dload internal storage → same error during update, put it in dload sdcard → same error, no matter which way I use to start the update
- boot into twrp or stock recovery.img through fastboot without actually flashing it, anyway error “command not allowed”
- do factory reset or update through dial codes (i.e. *#*#123456#*#* …), nothing worked
My pc is windows 10, all drivers up to date. Using powershell as an admin. Am an idiot for not making backup of the phone before I started...
So, now I have more or less functioning phone, but I can’t uninstall any apps at all, can’t install from unknown sources, can’t do nothing from pc, can’t make any update, and lot of important settings keep crashing.
I can use the phone like this, but if somebody could think about some solution for this ****ed up situation I got myself into, I would be grateful to him/her for the rest of my life.
Sorry for a long post.
Thank you in advance and have a nice day
I think using Hisuit will help. Enter Fastboot and connect ur phone to ur computer and use system recovery toll

Categories

Resources