hello, I have a mate 10 pro (BLA-L09), bootloader unlocked, rebranded from demo to europe, with OmniRom.
I flashed Omnirom because… is the only rom working properly on my phone.
I would like to send my phone "back to the emui" (get the quote ) but…
- I tried to flash a stock rom with hwota (2 times) and got wrong (the .bat worked fine but emui said "software install failed")
-i got my phone bricked… I tried to fix it reflashing omnirom with adb but the phone boot didn't work.
-I installed magist with hwota and my phone got fixed by itself (I don't understand why)
- I have again Omnirom.
How can I flash a stock rom without bricking it again?
thanks for any help or advice you will give me.
:highfive:
Related
Hello fellow xda members helpers and developers
I need to downgrade my Phone from Android 7 Build: C432B370 to Android 6
What do I need to make sure of in my Huawei P9 Lite Android 7 Emui 5 before following the Rollback/software upgrade procedure described in the respective Zip files.
Do I need to unroot and relock ? .. If yes which version of recovery or TWRP do I need.. if I am going to rollback.
I am a little hesitant at the moment becouse I managed to get into a bootloop yesterday by just flashing recovery_stock .
I am guessing it is becouse I unawarely flashed the wrong recovery_stock(?)
Recovery/Fastboot mode were not availiable - and then tried to flash the rollback via 3 button method.. which of course did not work.
( In case you are wondering how I managed to fix this: I let the battery drain to 0% - this broke the loop - afte the fifth try I managed to reset it with volume up + power all the way through booting)
So now I am back to square one..
Thank you
ok so I managed to fix this by myself: The problem I had was, I had a corrupted/wrong recovery on my Android 7.
So what I did was, I checked which build I excactly had .. in my case C432B370 ... downloaded the full rom. Extracted the stock recovery.img with "HuaweiUpdateExtractor" and flashed it.
Then I did the normal rollback procedure with both update.app files.
Had to unlock and root it once more... ( this time with the correct twrp) and voila it works.
So what do we learn?: dont trust simple internet guides if they not offer informations on file versions they offer ... they may not use the correct versions for your phone.
thrad can be closed or deleted
thanks for looking
I just bought a Huawei Mate SE which is a newer phone that looks like the Honor 7x. I've noticed whenever I search for Huawei Mate Se custom roms, recoveries, and even stock roms I only find Mate 9 stuff and find my self desperate with no support of root, and anything else. I found an article called "How to : Huawei Mate SE Root & TWRP Recovery" , and I successfully unlocked the bootloader, and I successfully installed twrp. The text on the bottom I didn't see which said to install the dm-verity thing. I ran into the problem where there were all these folders were displaying weird text in the main partitions, so instead of installing the version they told me, which was the no-verity-opt-encrypt-4.1.zip, I installed the latest which was the no-verity-opt-encrypt-6.0.zip version, which soft bricked. So I thought I could fix this by installing a custom ROM. But there were none, so I tried to install cm13 honor 7x rom and It didn't work. I tried installing the correct version after the rom. So even now if I tried to revert the old boot img it still wouldn't work because of the rom. However, since my bootloader is unlocked there is definitely a way I can fix all this. But the problem is their is not any Huawei Mate SE roms anywhere. I need a stock rom for my phone (possisbly a custom rom), or some fix. I can access my recovery, and the bootloader, but not anything else. My model is the BND-L34, pls help.
I did the same thing. Got it working
Put this in twrp back up folder on external SD card. Restored both files then factory reset in twrp. It worked for me every thing works. unzipped with Windows pc
Can't post links. Post [EMUI 5.1] OTA Firmwares and Unbrick Phone method. In Huawei 7x thread post#139 by AlexxC might be easter to search his posts. I have mate se in us on tmo/MetroPCS I flashed the correct 4.1 and still got soft brick. That article cost me couple hours. rooted with honor 7x method. Guess it really is the same phone with extra gig of ram. To AlexxC thanks, you the man
bradass402 said:
Put this in twrp back up folder on external SD card. Restored both files then factory reset in twrp. It worked for me every thing works. unzipped with Windows pc
Can't post links. Post [EMUI 5.1] OTA Firmwares and Unbrick Phone method. In Huawei 7x thread post#139 by AlexxC might be easter to search his posts. I have mate se in us on tmo/MetroPCS I flashed the correct 4.1 and still got soft brick. That article cost me couple hours. rooted with honor 7x method. Guess it really is the same phone with extra gig of ram. To AlexxC thanks, you the man
Click to expand...
Click to collapse
I tried the manual method of unbricking with multi touch and the phone booted, but it is a black screen, and I only see the home, back and tabs buttons. So after i figured out to use the backup that you sent me and it still wouldn't boot.
Are you getting errors in twrp restore you have to mount the partitions that your restoring boot system data etc
bradass402 said:
Are you getting errors in twrp restore you have to mount the partitions that your restoring boot system data etc
Click to expand...
Click to collapse
i did what you said in the pm, and got the cust.img flashed, but now it bootloops to the recovery
tomjfmu said:
i did what you said in the pm, and got the cust.img flashed, but now it bootloops to the recovery
Click to expand...
Click to collapse
Why dont you boot into huawei eRecovery? It downloads the firmware and recovery and recovers your phone.
Hi everybody,
I was on rooted and rebranded ALP-L29C432B148 (before rebranding it was L29C636 as far as I remember) and wanted to go back to Stock. I flashed the ALP-L09C432B149 firmwarefrom this thread
https://www.android-hilfe.de/forum/...nstall-stock-rom-mate10-mate10pro.882911.html
and then after sucessful flashing the buld-nr. showed ""System 8.0.0.046 (0FTC)". To get the correct buoild-nr and to be able to receive ota updates I wanted to rebrand again and install the ALP-L09C432B148 from this thread
https://www.android-hilfe.de/forum/...jeder-version-zum-alp-l09-l29c432.882774.html
again to use the rebrand mod again. This wasn't successful as the firmware install failed. After that I couldn't install any firmware (neither B149 nor B148). If I install twrp-alp-firedance it shows only the twrp startscreen, but I can't access twrp.
Further more I'm not able any more to push any files to the phone, it fails with "adc couldn't create file..Is a directory" Flashing files via adb works.
What can I do now to get back a working system with stock rom?
Thank you very much in advance for your help!
hello, my miA3 was in V10.3.17.0.PFQEUXM, and i had some troubles with it after trying to root with magisk because of a wrong boot.img, and i lost wifi.
since I couldn't find a V10.3.17.0.boot.img to flash and get back wifi, i try to find some escape plan and finally i succeed to install twrp and then official V11.0.8.0 , but i would like to go back to V10.3.15.0 and root it ( or 10.3.17.0 if someone have the good boot.img ), is it possible?
Just download fastboot rom and you are good to go
arjo656 said:
hello, my miA3 was in V10.3.17.0.PFQEUXM, and i had some troubles with it after trying to root with magisk because of a wrong boot.img, and i lost wifi.
since I couldn't find a V10.3.17.0.boot.img to flash and get back wifi, i try to find some escape plan and finally i succeed to install twrp and then official V11.0.8.0 , but i would like to go back to V10.3.15.0 and root it ( or 10.3.17.0 if someone have the good boot.img ), is it possible?
Click to expand...
Click to collapse
If you want to keep your sensors and DRM working, follow this guide:
https://forum.xda-developers.com/showpost.php?p=82110807&postcount=224
amnher said:
Just download fastboot rom and you are good to go
Click to expand...
Click to collapse
ok,do you have a link with DL and tuto step by step?
_mysiak_ said:
If you want to keep your sensors and DRM working, follow this guide:
https://forum.xda-developers.com/showpost.php?p=82110807&postcount=224
Click to expand...
Click to collapse
thanks (again ) mysiak, the steps are clear but there is no link for dl any of the rom he's talking
edit : i downloaded a rom 10.3.15.0 here https://forum.xda-developers.com/mi-a3/how-to/rom-xiaomi-mi-a3-laurelsprout-t3962489, but when i double click on flash_all.bat nothing happends
arjo656 said:
thanks (again ) mysiak, the steps are clear but there is no link for dl any of the rom he's talking
edit : i downloaded a rom 10.3.15.0 here https://forum.xda-developers.com/mi-a3/how-to/rom-xiaomi-mi-a3-laurelsprout-t3962489, but when i double click on flash_all.bat nothing happends
Click to expand...
Click to collapse
Run the script from terminal window, it will show you an error message why it fails.
arjo656 said:
hello, my miA3 was in V10.3.17.0.PFQEUXM, and i had some troubles with it after trying to root with magisk because of a wrong boot.img, and i lost wifi.
since I couldn't find a V10.3.17.0.boot.img to flash and get back wifi, i try to find some escape plan and finally i succeed to install twrp and then official V11.0.8.0 , but i would like to go back to V10.3.15.0 and root it ( or 10.3.17.0 if someone have the good boot.img ), is it possible?
Click to expand...
Click to collapse
Guys, I did the update for android 10 in the second wave.
after trying to return to android 9 my device got stuck resetting the "android one" home screen, as there was no solution i put the "pixel" rom for mi a3.
Today as a test again I tried to flash the rom stock 9 and everything went back to normal as it was before, with everything working.
I believe that after installing "PIXEL" something made it back to normal.
alexjmachado said:
Guys, I did the update for android 10 in the second wave.
after trying to return to android 9 my device got stuck resetting the "android one" home screen, as there was no solution i put the "pixel" rom for mi a3.
Today as a test again I tried to flash the rom stock 9 and everything went back to normal as it was before, with everything working.
I believe that after installing "PIXEL" something made it back to normal.
Click to expand...
Click to collapse
yes , that's what sapper morton explained in a other post:
" I received Android 10 as an OTA 29th February, and a couple of days later I updated to v11.0.8.0 (locked bootloader); but I didn't enjoy it overall, so I did install Magisk, after a couple of days, I downgraded to Pie (March firmware); I lost my sensors, did try a couple of things, none of them solved the issue.
I knew from the beginning I could have flashed persist.img, but then again, I would've lost my DRM Keys (Widevine), thus I updated to Android 10 Stock (recovery firmware) to regain my sensors.
After a little search I read that downgrading from a custom Android 10 ROM (PX in my case) solves the issue on Pie, I tried and the sensors started working again on Android 9 Stock, without losing Widevine L1, since persist partition was intact. "
So my steps to solve the issue was as it follows:
1• Flashed Android 10 Stock (sensors working) [Recovery]
2• Flashed Android 9 Stock (sensors not working) [Fastboot]
3• Flashed Android 10 custom (sensors working) [Recovery]
4• Flashed Android 9 (sensors working) [Fastboot]
hello all
is there any download link to "3• Flashed Android 10 custom (sensors working) [Recovery]" or do you recommend a specific custom rom ?
I want to do the downgrade right
Hi,
My favourite phone is the Xiaomi Redmi note 3 Pro SE with Lineage OS 13 (Yes marshmallow).
I got a new one that was in endless bootloop and I planned to get it working.
I don't know if the bootloader has been unlocked and how (last time I checked it was written locked), if a custom ROM as been flashed or anything that could been done on it before I get it.
After many tries I first succeed to install LineageOs 13 on it, what I remember:
I go to fastboot mode
I go to edl mode
I flashed it with an old MiFlash 2016.04.01.0 64 bit with an old official ROM : kate_global_images_6.9.29_20160805.0000.29_6.0_global_9aa2d85137 with recovery.img replaced by an old ZXC-TWRP 3.0.2-X. (This is the way to get a recovery with no need to unlock bootloader)
I started it directly to TWRP recovery mode (to be sure TWRP will stay it I guess?) changed the language and checked OTA checkbox in parameters
I started this old official ROM once (to get the full storage capacity)
I discovered it was a 16GB ROM / 2GB RAM version instead a 32GBROM / 3GB RAM I previously knowed
I restarted to TWRP recovery mode
I wiped david/cache
I flashed the last knowed LineageOS 13 for this phone: https://forum.xda-developers.com/re...ageos-13-0-t3533744/post83687823#post83687823
I wiped david/cache
I flashed the last radeon kerned on it
I wiped david/cache
I restarted it to LineageOS 13
I restarted to TWRP recovery mode, changed the language and checked OTA checkbox in parameters
I flashed magisk (sytemless)
I wiped david/cache
I restarted it to LineageOS 13
I could use it install a lot of things, was happy with it
Before succeeding I tried a lot of combinations of official ROM/TWRP/MiFlash versions and this couple was the only one working.
Other MiFlash versions don't detect the phone in edl mode
But 2 weeks later, just after installing a new app, the phone sudently reboots and I got stuck in bootloop again...
I could go to recovery one time, I selected reboot system, now I can't go to recovery anymore
I still can go to fastboot mode and edl mode, and I can flash a ROM, but whatever I flash I can't go away from bootloop.
What could the new bootloop come from?
Is my installation sequence good?
Why only this combination of official ROM/TWRP/MiFlash versions was working?
Why can't I start a ROM anymore after a new flash?
Why can't I go to the recovery anymore after a new flash?
How to check if the emmc memory is defective (I got no error while flashing)?
Thanks for reading, hope someone still cares on this old great phone
Sorry for my bad English
No clue what the problem may be. What app did you install? You could always try to go back to stock if you haven't already. Basically wipe phone completely and flash stock through mi flash.
JD. A said:
No clue what the problem may be. What app did you install? You could always try to go back to stock if you haven't already. Basically wipe phone completely and flash stock through mi flash.
Click to expand...
Click to collapse
Thanks for your answer.
The last app before bootloop was a sms/mms backup app on google store I get through Aurora.
I tried to flash the stock ROM (old one) kate_global_images_6.9.29_20160805.0000.29_6.0_glo bal_9aa2d85137 but it doesn't start, always bootloop.
I have no option to wipe on the only miflash version that detect my phone in edl : the 2016.04.01.0 64 bit version. so I choose flash all data/storage include, but still bootloop.
Why are you using such a old rom? Use latest miflash and latest global. On the bottom right of miflash you should have something like clean and lock. Just note that if you're unofficially unlocked you'll need to apply for unlock or unlock unofficially again.
JD. A said:
Why are you using such a old rom? Use latest miflash and latest global. On the bottom right of miflash you should have something like clean and lock. Just note that if you're unofficially unlocked you'll need to apply for unlock or unlock unofficially again.
Click to expand...
Click to collapse
Other Miflash version don't detect my phone when it is in edl mode
I could start other stock rom, I know tried this ones:
kate_global_images_7.6.8_20170608.0000.00_6.0_global_2040bd5a39
kate_global_images_8.12.13_20181213.0000.00_6.0_global_304fc0692b
But I couldn't flash my LineageOS 13 + recovery with those.
I tried so much combinations TWRP/Stock rom, I don't remember what I tested.
I just know the MiFlash 2016.04.01.0 64 bit with an old official ROM : kate_global_images_6.9.29_20160805.0000.29_6.0_glo bal_9aa2d85137 with recovery.img replaced by an old ZXC-TWRP 3.0.2-X. was the only one combination that worked for me for installing LineageOS 13 + recovery working
Now, every time I try to flash something (whatever it is) it goes to bootloop...
Only fastboot and edl mode are working
If you have other links / combinations I would be happy to try
ROUGE13 said:
Other Miflash version don't detect my phone when it is in edl mode
I could start other stock rom, I know tried this ones:
kate_global_images_7.6.8_20170608.0000.00_6.0_global_2040bd5a39
kate_global_images_8.12.13_20181213.0000.00_6.0_global_304fc0692b
But I couldn't flash my LineageOS 13 + recovery with those.
I tried so much combinations TWRP/Stock rom, I don't remember what I tested.
I just know the MiFlash 2016.04.01.0 64 bit with an old official ROM : kate_global_images_6.9.29_20160805.0000.29_6.0_glo bal_9aa2d85137 with recovery.img replaced by an old ZXC-TWRP 3.0.2-X. was the only one combination that worked for me for installing LineageOS 13 + recovery working
Now, every time I try to flash something (whatever it is) it goes to bootloop...
Only fastboot and edl mode are working
If you have other links / combinations I would be happy to try
Click to expand...
Click to collapse
This is a little bit to late to the party but the latest both dev rom and global works for me with the latest me miflash. No problems what so ever. Seems like you're facing a hardware issue.
JD. A said:
This is a little bit to late to the party but the latest both dev rom and global works for me with the latest me miflash. No problems what so ever. Seems like you're facing a hardware issue.
Click to expand...
Click to collapse
Hi,
No, not too late my phone is still waiting, so thanks for your answer
Could you tell me witch version of rom / tool did you use?
I will try on a other windows computer to be sure there is no conflict with old tools I installed before.
If it works I will flash CM13 (marshmallow), I thought I should not use a too recent dev/global ROM before flashing CM13, but I don't remember were I read this. Is this true?
ROUGE13 said:
Hi,
No, not too late my phone is still waiting, so thanks for your answer
Could you tell me witch version of rom / tool did you use?
I will try on a other windows computer to be sure there is no conflict with old tools I installed before.
If it works I will flash CM13 (marshmallow), I thought I should not use a too recent dev/global ROM before flashing CM13, but I don't remember were I read this. Is this true?
Click to expand...
Click to collapse
I'm not home this weekend so I can't say for sure. gismoZ recommends using the 8.0.2 firmware or something like that can't remember, but the latest works just fine on my kate. The latest miflash is from 20200314 and just get the latest global rom and try to flash it.
I tried with an other windows computer, I successfully used last MiFlash version
But now, whatever I flash, ROM version or recovery version, it stay in bootloop when I power it.
I expect the eMMC memory to be faulty but why doesn't I have any error while flashing?
How to be sure this comes from the eMMC chip?
Some people have successfully changed it on the mediatek version of the phone:
https://fr-fr.facebook.com/16816505...c-kmvtu-done/1821360108117225/?_fb_noscript=1
https://translate.google.com/transl.../03/service-hp-xiaomi-redmi-mi-note-mati.html
If I go on this solution I have some questions before:
Must the eMMC chip be programmed before soldering it?
If not, can I program it with MiFlash once soldered?
If not, have I to use some special touch/contact on the mainboard to program it?
How to be sure of the chip model to buy?
Will the chip come already balled? Or have I to ball it before soldering it on mainboard?
Could I buy a 32GB chip instead 16GB original one?
Something else to test before going on this crazy last chance solution?
I bought a EDL flash cable, but I think I don't need it on this phone, I alway success to go to EDL mode from fastboot mode with a small batch script.
Hello ,
Any chance I could get an answer anymore or is my problem too specific maybe?