Since i flash twrp and install magisk i dont have sound on my mi a3. Mic not working, audio not working,music is not playing. When i try to open a video it gives an error " Something went wrong". I tried erase boot flash twrp again, factory reset my mi a3 etc. still problem exist. I downloaded 10.3.8 stock boot.img and flashed system give error in red characters and telling me Factory reset my phone. I live in mountain as a soldier now. This is the only phone that i have in this mountain. Please help
As the first attempt for a fix I'd try switching active slots. If that won't help, you'll probably need to download whole stock ROM and reflash it (for this you must change active slot to A). You can try keeping data (flash all except storage.bat), if it won't work then you'll need to reflash again with data wipe (flash all.bat).
Switching slot doesnt help. i downloaded 10.3.4 rom which has .tgz extension. miFlashtool doesnt recognize my phone and gives error about installing drivers. How to flash new rom? Can you help me little :/
sasukeob said:
Switching slot doesnt help. i downloaded 10.3.4 rom which has .tgz extension. miFlashtool doesnt recognize my phone and gives error about installing drivers. How to flash new rom? Can you help me little :/
Click to expand...
Click to collapse
Unpack the tgz file (inside is another zip if I remember correctly - unzip it as well). Then locate file "flash_all_except_storage.bat" and run it with phone connected in fastboot mode. It should start flashing all images. Do not forget to set slot A as active before booting up the phone.
_mysiak_ said:
Unpack the tgz file (inside is another zip if I remember correctly - unzip it as well). Then locate file "flash_all_except_storage.bat" and run it with phone connected in fastboot mode. It should start flashing all images. Do not forget to set slot A as active before booting up the phone.
Click to expand...
Click to collapse
when i click flash all except storage in fastboot mode. it will do everything i should do right?
sasukeob said:
when i click flash all except storage in fastboot mode. it will do everything i should do right?
Click to expand...
Click to collapse
Yes, it will reflash all partitions with correct stock images.
Guys any other solitions to tell? i cant understand how a phone doesnt play sound even i factory reset it? my hardware is working problem is software but i dont know which part of software...
You might have incorrect combination of kernel and vendor/system/dsp/.. partitions. If one of them is from different version, phone might not boot at all, or cause wifi/sound/.. issues. Have you gone through full rom flashing successfully?
i will do that but first let me find drivers for miflashtool
Generic Google ADB/fastboot drivers will work fine.
_mysiak_ said:
Generic Google ADB/fastboot drivers will work fine.
Click to expand...
Click to collapse
it didnt but i will find qualcomm drivers and install
Qualcom drivers are for EDL mode as far as I know.
i flashed stock rom and my problem solved admins can close this thread. @_mysiak_ thank you for all your help bro
Mine also same, wifi not working, mic not working, no call outgoing/receiving, no media playing, mp3 file is not supported by any player how you fixed?
sasukeob said:
Since i flash twrp and install magisk i dont have sound on my mi a3. Mic not working, audio not working,music is not playing. When i try to open a video it gives an error " Something went wrong". I tried erase boot flash twrp again, factory reset my mi a3 etc. still problem exist. I downloaded 10.3.8 stock boot.img and flashed system give error in red characters and telling me Factory reset my phone. I live in mountain as a soldier now. This is the only phone that i have in this mountain. Please help
Click to expand...
Click to collapse
Mine also have same problem after flashing twrp.
But you can solve it by flashing stock rom in fastboot mode.(Using .bat files included in tgz package after extracting)
But while flashing, If you face any error like remote failed crc error.
Just press the power key of device till it reboots again, and process continues in cmd. Wait for it. Enjoy
Related
hi guys!
Anyone knows how to install twrp in the latest stock rom?
I tried in windows 10 using flash tools and a preloader error apperas.
In windows XP i could install twrp but it did not load when trying to access it.
Thanks!
Fran Montero said:
hi guys!
Anyone knows how to install twrp in the latest stock rom?
I tried in windows 10 using flash tools and a preloader error apperas.
In windows XP i could install twrp but it did not load when trying to access it.
Thanks!
Click to expand...
Click to collapse
it might not have loaded because it was maybe an updated twrp eith an old preloader, try flashing an older twrp or update preloader
Ruben Craveiro said:
it might not have loaded because it was maybe an updated twrp eith an old preloader, try flashing an older twrp or update preloader
Click to expand...
Click to collapse
Have you installed it already?
Many thanks!
Fran Montero said:
Have you installed it already?
Many thanks!
Click to expand...
Click to collapse
Im using latest twrp with updated preloader and LOS13
Hi,
I'm unsure if this method will work for you, but I also had "preloader Error message" in FlashTools trying to flash TWRP in Stock Rom 2016810 while trying to flash the Eragon ROM.
As the Stock ROM you are using (20171201) is kinda newer than stock 2016810 Im kinda assuming it should work the same.
In order for it to flash without errors, I did the following and worked fine :
Use FlashTools ver v5.1612 - https://www.androidfilehost.com/?fid=24591000424940027
Download your stock rom 20171201
https://mega.nz/#!atZAyKxb!i6jpNQNR_VZZ3nS79LhL2xi78WHx7XI4gKFllc8 RJKw
Then download TWRP_3.0.2.8.zip here: https://www.androidfilehost.com/?fid=24727369092696060
Unzip all and and copy the "MT6755_Android_scatter" & "recovery.img" from TWRP_3.0.2.8 folder into the Elephone_P9000_20170112 Rom folder.
Then open Flash Tools - add the scatter file from the Elephone_P9000_20170112 Rom folder
Untick everything in flashtools except the recovery and then try to flash, hopefully it will work for you too. without errors '
jotei66 said:
Hi,
I'm unsure if this method will work for you, but I also had "preloader Error message" in FlashTools trying to flash TWRP in Stock Rom 2016810 while trying to flash the Eragon ROM.
As the Stock ROM you are using (20171201) is kinda newer than stock 2016810 Im kinda assuming it should work the same.
In order for it to flash without errors, I did the following and worked fine :
Use FlashTools ver v5.1612 - https://www.androidfilehost.com/?fid=24591000424940027
Download your stock rom 20171201
https://mega.nz/#!atZAyKxb!i6jpNQNR_VZZ3nS79LhL2xi78WHx7XI4gKFllc8 RJKw
Then download TWRP_3.0.2.8.zip here: https://www.androidfilehost.com/?fid=24727369092696060
Unzip all and and copy the "MT6755_Android_scatter" & "recovery.img" from TWRP_3.0.2.8 folder into the Elephone_P9000_20170112 Rom folder.
Then open Flash Tools - add the scatter file from the Elephone_P9000_20170112 Rom folder
Untick everything in flashtools except the recovery and then try to flash, hopefully it will work for you too. without errors '
Click to expand...
Click to collapse
Thanks for the answer.
I tried and TWRP is flashed succesfully and i can even load it, but when rebooting system it is not loading, it remains on the withe elephone logo
Fran Montero said:
Thanks for the answer.
I tried and TWRP is flashed succesfully and i can even load it, but when rebooting system it is not loading, it remains on the withe elephone logo
Click to expand...
Click to collapse
Maybe you have a sd card formatted as internal storage?
Fran Montero said:
Thanks for the answer.
I tried and TWRP is flashed succesfully and i can even load it, but when rebooting system it is not loading, it remains on the withe elephone logo
Click to expand...
Click to collapse
Hi, I think this maybe to do with the new preloader etc..
I read this in the thread for TWRP for Elephone P9000 3.0.2-8:
1. load scatter.txt in earlier post.
2. select preloader, lk and boot imgs, location of these from the stock 20160810 ROM.
3. select recovery, location of TWRP img.
4. unselect everything else.
Click to expand...
Click to collapse
Here: https://forum.xda-developers.com/el...hone-p9000-t3426678/post70713618#post70713618
So maybe Unzip the 20171201 Rom, copy TWRP scatter & recovery.img to this folder, open flash tools and select recovery and point to recovery.img
But also select preloader, lk and boot img (double check they are pointing to corresponding files from the 20171201 ROM
Again, I am unsure if that will work but as I noticed the above post in the TWRP thread, thought it maybe relevant to your issue
PS: Windows 10 can be awkward with splash tools at times, I have windows 10 but in order for it to work - I have to press the Download in SplashTools, kinda count to 5, then hold vol + and then attach USB to my phone and it works fine
If your device already rooted, you can also install flashyfi and flash the .img file.
jotei66 said:
Hi,
I'm unsure if this method will work for you, but I also had "preloader Error message" in FlashTools trying to flash TWRP in Stock Rom 2016810 while trying to flash the Eragon ROM.
As the Stock ROM you are using (20171201) is kinda newer than stock 2016810 Im kinda assuming it should work the same.
In order for it to flash without errors, I did the following and worked fine :
Use FlashTools ver v5.1612 - https://www.androidfilehost.com/?fid=24591000424940027
Download your stock rom 20171201
https://mega.nz/#!atZAyKxb!i6jpNQNR_VZZ3nS79LhL2xi78WHx7XI4gKFllc8 RJKw
Then download TWRP_3.0.2.8.zip here: https://www.androidfilehost.com/?fid=24727369092696060
Unzip all and and copy the "MT6755_Android_scatter" & "recovery.img" from TWRP_3.0.2.8 folder into the Elephone_P9000_20170112 Rom folder.
Then open Flash Tools - add the scatter file from the Elephone_P9000_20170112 Rom folder
Untick everything in flashtools except the recovery and then try to flash, hopefully it will work for you too. without errors '
Click to expand...
Click to collapse
a bit late (did came to it to test your solution earlier) but it worked indeed. perfect, very much appreciated.
Can u upload 20171201 again?! Link is not working... Thx
opss said:
Can u upload 20171201 again?! Link is not working... Thx
Click to expand...
Click to collapse
You'll find a link here: https://forum.xda-developers.com/el...t/rom-stock-rom-android-6-0-12-01-17-t3542463
Thx dude
jotei66 said:
Hi, I think this maybe to do with the new preloader etc..
I read this in the thread for TWRP for Elephone P9000 3.0.2-8:
Here: https://forum.xda-developers.com/el...hone-p9000-t3426678/post70713618#post70713618
So maybe Unzip the 20171201 Rom, copy TWRP scatter & recovery.img to this folder, open flash tools and select recovery and point to recovery.img
But also select preloader, lk and boot img (double check they are pointing to corresponding files from the 20171201 ROM
Again, I am unsure if that will work but as I noticed the above post in the TWRP thread, thought it maybe relevant to your issue
PS: Windows 10 can be awkward with splash tools at times, I have windows 10 but in order for it to work - I have to press the Download in SplashTools, kinda count to 5, then hold vol + and then attach USB to my phone and it works fine
Click to expand...
Click to collapse
I've wasted countless hours trying to get spf to work with my windows 10 machine. Your solution worked like a charm, the flashing was successful (managed to get the process to work when before I was getting only preloader errors), however I still don't have twrp but the standard android recovery. Have you got any other solution that I should try? Cheers.
---------- Post added 9th May 2017 at 12:18 AM ---------- Previous post was 8th May 2017 at 11:43 PM ----------
thecrazyfarang said:
I've wasted countless hours trying to get spf to work with my windows 10 machine. Your solution worked like a charm, the flashing was successful (managed to get the process to work when before I was getting only preloader errors), however I still don't have twrp but the standard android recovery. Have you got any other solution that I should try? Cheers.
Click to expand...
Click to collapse
I reflashed and managed to get twrp but now the phone won't boot, it is stuck in the Elephone logo
thecrazyfarang said:
I've wasted countless hours trying to get spf to work with my windows 10 machine. Your solution worked like a charm, the flashing was successful (managed to get the process to work when before I was getting only preloader errors), however I still don't have twrp but the standard android recovery. Have you got any other solution that I should try? Cheers.
---------- Post added 9th May 2017 at 12:18 AM ---------- Previous post was 8th May 2017 at 11:43 PM ----------
I reflashed and managed to get twrp but now the phone won't boot, it is stuck in the Elephone logo
Click to expand...
Click to collapse
Have you tried pressing power and then keep finger pressed on vol up to go straight to TWRP recovery and then flashing a new ROM in TWRP ?
I didn't do that as I didn't have another rom saved in my phone. What I eventually managed to do was flash the official nougat via spf tool. I'm saying eventually because this piece of crap windows 10 didn't want to make the connection even with the volume up button. When I was going to give up and order a new phone, it connected and now I am happy even though I don't have twrp nor root, but not going to risk it again. Thanks again for your help though, greatly appreciated.
thecrazyfarang said:
I didn't do that as I didn't have another rom saved in my phone. What I eventually managed to do was flash the official nougat via spf tool. I'm saying eventually because this piece of crap windows 10 didn't want to make the connection even with the volume up button. When I was going to give up and order a new phone, it connected and now I am happy even though I don't have twrp nor root, but not going to risk it again. Thanks again for your help though, greatly appreciated.
Click to expand...
Click to collapse
No worries, just glad you got it sorted out.
Btw (although I know you dont really wanna risk trying it) my son uses my P9000 and has TWRP installed with no issues at all and root with Magisk.
But great yous sorted out
Root twrp Step by step for newbeee-
Ok,so I've installed TWRP 3.0.2-8 and when I start the phone it goes into the recovery... what to do next? Can I find a tutorial somewhere how to do this? And wich image can I use or is the best for the moment?
thx for helping...
Managed to download and flash the B130 update on my stf-L09C432. After a factory reset and a couple of reboots it seemed to work fine. It goes through the configuration as supposed all the way to completing configuration. Then it stays there for a minute and then the configuration guide restart. Tried rebooting and wipeing, but it won't go any further.
The settings are saved though and everything is pre-set when I go through the configuration again.
Can it be some kind of permission problem?
Can I bypass the configuration?
I guess there's a flag somewhere for configuration_done = true or something.
Any ideas?
Still doesn't work. Have tried to download several times. Have tried both dload (fails) and flashing with fastboot.
Flashing boot, recovery and system works fine. But it won't permit flashing the vendor partition.
"Command: Not allowed" even if I tried several downloads.
Maybe if someone have a working twrp backup to share with me. Either B130 or B120.?
That might open up so I can flash everything new
Have you tried manually reinstalling the OS back onto your device?
iceepyon said:
Have you tried manually reinstalling the OS back onto your device?
Click to expand...
Click to collapse
Manually like flashing each image separately or is there any other way?
zybitx said:
Manually like flashing each image separately or is there any other way?
Click to expand...
Click to collapse
Oh. Of course by pushing with adb ?
zybitx said:
Manually like flashing each image separately or is there any other way?
Click to expand...
Click to collapse
Just reinstall the stock OS back onto your device and see if that helps.
zybitx said:
Manually like flashing each image separately or is there any other way?
Click to expand...
Click to collapse
iceepyon said:
Just reinstall the stock OS back onto your device and see if that helps.
Click to expand...
Click to collapse
Since I was stupid enough not to make a backup I downloaded the latest stock update.zip and extracted the images from there.
I manage to flash system and boot but not the vendor image. Get "command not allowed".
The partition seem to be ok though, since I can push files to it and according to the simg tools there is nothing wrong with the image.
Is there like a full ROM that I can just install with twrp? I couldn't find any.
Rommco05 said:
Try flash custom.img, I think is in small region zip
Click to expand...
Click to collapse
Ok. Tried a bunch of solutions:
- Install stock full update.zip
with twrp - gives updater error: 9with fastboot - can flash system, boot, recovery but not vendor image.dload folder - stops with failureby unpacking images and using adb puschNone of these works fully and there is always some error, hanging loading screen or boot loop or as from the beginning setup wizzard won't complete.
Question: Which images from the update.zip are actually required on a wiped system? Should I get all of the on to the phone?
Would a fully working twrp backup from a kind soul be a safer way to go?
Also tried the custom ROMs but was unable to flash their vendor.zip files because of wrong header format
and simg2img was unable to read them.
Tried the ROMs with stock vendor.zip but got some java error in main (used logcat)
Been working on this for a week now. at one part I feel like throwing my new phone in the wall, but at another part I kind of enjoy this mess and of course I learn a lot in the process
Where should I go from this?
I would like to get the stock firmware working first so I can take a backup.
zybitx said:
Ok. Tried a bunch of solutions:
- Install stock full update.zip
with twrp - gives updater error: 9with fastboot - can flash system, boot, recovery but not vendor image.dload folder - stops with failureby unpacking images and using adb puschNone of these works fully and there is always some error, hanging loading screen or boot loop or as from the beginning setup wizzard won't complete.
Question: Which images from the update.zip are actually required on a wiped system? Should I get all of the on to the phone?
Would a fully working twrp backup from a kind soul be a safer way to go?
Also tried the custom ROMs but was unable to flash their vendor.zip files because of wrong header format
and simg2img was unable to read them.
Tried the ROMs with stock vendor.zip but got some java error in main (used logcat)
Been working on this for a week now. at one part I feel like throwing my new phone in the wall, but at another part I kind of enjoy this mess and of course I learn a lot in the process
Where should I go from this?
I would like to get the stock firmware working first so I can take a backup.
Click to expand...
Click to collapse
the same problem, i hope we could solve it soon.
My attempt to root my H930 went very wrong... So I started by unlocking the bootloader and flashing TWRP. After that I didn't manage to get in to TWRP. Instead it started to boot, but froze eventually. Now I can't get it to boot (It gets stuck on initial LG V30 screen), and I can't power it off. I can get into stock recovery (apparently it got far enough to replace TWRP) and download mode with hardware button combinations. But the download mode seems to be different from fastboot mode (looks different on phone, and fastboot can't find it) so I can't try to flash TWRP again. I also managed to get it into a check IMEI + S/N mode by holding all buttons at once...
I've tried flashing H93010f_00_OPEN_EU_OP_0925.kdz with LG UP/Uppercut (since I can get to download mode). It went fine but the situation is the same - no boot, no way to power off.
A factory reset from stock recovery doesn't help either.
Please advice..
Alright, I acually got in to fastboot mode even though I'm not quite sure how.. I basically first went in to download mode, and then pressed vol down + power to reboot, and ended up in fastboot mode. From there I flashed twrp again. And this time I managed to get in to TWRP. Since I didn't have a working ROM I went ahead and wiped all but external sdcard and tried flashing Boombox. It resulted in an "Error: 1"..
So I tried flashing H93010f_00_OPEN_EU_OP_0925.kdz from LGUP again, and now I'm back to a device that doesn't boot again.
Which root are you trying to flash? TWRP also is in alpha at the very best at this point. Can you extract the KDZ and use fastboot to flash the .img files inside, assuming they have .img files inside of the KDZ?
jcsww said:
Which root are you trying to flash? TWRP also is in alpha at the very best at this point. Can you extract the KDZ and use fastboot to flash the .img files inside, assuming they have .img files inside of the KDZ?
Click to expand...
Click to collapse
I'm not trying to flash any root. I was planning on flashing Magisk but never got that far. At this point I'm just trying to get a working phone. I read about extracing img files from kdz but the tool didn't work in my virtual WinXP machine so I'm trying to fire up a Win10 machine now (I'm on mac).
Meanwhile I tried flashing boot and system from "LGH930GAT-00-V10c-222-01-OCT-12-2017+0.zip" but that resulted in the phone automatically booting into TWRP... That can't be good.
egendomligt said:
I'm not trying to flash any root. I was planning on flashing Magisk but never got that far. At this point I'm just trying to get a working phone. I read about extracing img files from kdz but the tool didn't work in my virtual WinXP machine so I'm trying to fire up a Win10 machine now (I'm on mac).
Meanwhile I tried flashing boot and system from "LGH930GAT-00-V10c-222-01-OCT-12-2017+0.zip" but that resulted in the phone automatically booting into TWRP... That can't be good.
Click to expand...
Click to collapse
With some other phones, like Nexus devices. Flashing older boot images can cause bootloops. I don't know if this is the case with your device but it might be something to consider. Have you tried flashing the complete latest factory image to see if that solves the bootloop?
jcsww said:
With some other phones, like Nexus devices. Flashing older boot images can cause bootloops. I don't know if this is the case with your device but it might be something to consider. Have you tried flashing the complete latest factory image to see if that solves the bootloop?
Click to expand...
Click to collapse
Unfortunately I haven't been able to get able to get a hold of a KDZ other than for 10f. I'd like to try 10v.
I got the extraction tool working in a Win10 box now, and I'm trying to extract boot and system images from the 10f KDZ...
egendomligt said:
Unfortunately I haven't been able to get able to get a hold of a KDZ other than for 10f. I'd like to try 10v.
I got the extraction tool working in a Win10 box now, and I'm trying to extract boot and system images from the 10f KDZ...
Click to expand...
Click to collapse
Best of luck!
Nope, that didn't work either. fastboot threw an error telling me the system image was too big for the partition.. At least the system image from the 10c dump fit properly..
So I guess my best bets right now are to either get a hold of a 10v KDZ, or wait for something flashable through TWRP.. :/
Is there like a lastlog for system boot that would be reachable from TWRP/adb..? It would sure be nice to see whats going wrong...
egendomligt said:
Nope, that didn't work either. fastboot threw an error telling me the system image was too big for the partition.. At least the system image from the 10c dump fit properly..
So I guess my best bets right now are to either get a hold of a 10v KDZ, or wait for something flashable through TWRP.. :/
Is there like a lastlog for system boot that would be reachable from TWRP/adb..? It would sure be nice to see whats going wrong...
Click to expand...
Click to collapse
No clue!
Ok, I got it to boot again!
* I formatted data (not wiped) inTWRP - Not sure if this step was relevant
* Flashed stock recovery/boot/system from a KDZ dump called "LGH930GAT-00-V10c-222-01-OCT-12-2017+0" - found the link in some other thread here
* Rebooted and watched it boot - went in to "Android is upgrading..."-screen - rebooted - then booted normally.
Thanks for the help and a special thanks to @Perkash who helped me out through PM.
Hi all,
I went ahead and rooted my Mate 10 Pro today - I unlocked my bootloader, installed TWRP and got it running pretty sweet. Then, like a tool - tried installing xposed framework and got myself into a boot loop.
I can get to fastboot, I can get into twrp - but for the life of me don't know how to get a system wipe and fresh format! I've tried flashing LineageOS - but that's stuck on a loading screen and then boot loops after about 10minutes.
What happens is I turn my phone on - see the bootloader message - if I do nothing there's a 50/50 changes Huawei's eRecovery window opens (where if i connect it to the wifi, it fails and gives me the option of reboot or shutdown) or LineageOS boot animation loops for about 10minutes before shutting down.
At this stage, I don't mind what rom i get working - i just want something working and I'm really regretting xposed (I should of googled!).
I really don't want to pay $40 usd - and am happy tinkering around, but would appreciate some solid advice on how I can use TWRP to wipe everything and start again!
I'm also a little confused as to why eRecovery is coming up at all - and why it can't download anything!!!!!
Can someone help me get a phone back?
Thanks!
Yeah, I bootlooped going with xposed too, but I have the Mate 10 (regular) and no TWRP. Can you get to TWRP and simply flash a clean ROM? If not, which I presume is the case, can you get to Fastboot? To try, when you get to the eRecovery window, use the option to shut down your phone. Then press the power button and, while holding it, plus in your USB cable (the other end which should already be attached to your computer). Then go to Mankindtw's thread for flashing ROMs (Mate 10 Flash Oreo one). Basically, you download three zip files from a russian language page with all the latest Huawei ROMs, repackage them within his utility, and then flash them from within his utility. Worked for me.
download update.zip (for your firmware) from http://pro-teammt.ru/firmware-database
Extract update.app from update.zip
Download Huawei Update Extractor (open it and go to settings and disable header check)
Open update.app in Huawei Update Extractor
Extract SYSTEM from update.app using Huawei Update Extractor.
(Not sure if Xposed modifies vendor too, so you might have to extract that as well)
Fastboot flash system system.img
See if it boots now. If not you could try extracting recovery_ramdisk and flash recovery_ramdisk.img to the recovery_ramdisk partition then factory reset from stock recovery.
If it does modify vendor you'd have to flash vendor as well.
Or you could try flashing lineage os system, flash recovery_ramdisk and factory reset from stock recovery (factory reset is needed to get aosp roms running)
If it still fails, use mankindtws HWOTA as described by rogerinnyc above. (link: https://forum.xda-developers.com/mate-10/how-to/guide-mate-10-flash-oreo-update-package-t3716814)
Stock rom seems to be installing. TY for your help
Toldorn said:
The problem I'm having now is, on my win7 and win10 pc's - when I enter fastboot, neither PC will accept drivers for it and therefore, I can't fastboot flash anything.
I just get '<waiting for device>' even when plugged in (and windows 'driver no successful' message)
Is there a way to transfer the files via twrp adb sideload?
Click to expand...
Click to collapse
Sadly no, this corresponds to reflashing the whole phone, block by block.
have you tried to find matching drivers ? (it should be pretty easy on windows 10 normally...)
Toldorn said:
The problem I'm having now is, on my win7 and win10 pc's - when I enter fastboot, neither PC will accept drivers for it and therefore, I can't fastboot flash anything.
I just get '<waiting for device>' even when plugged in (and windows 'driver no successful' message)
Is there a way to transfer the files via twrp adb sideload?
Click to expand...
Click to collapse
ChriKn said:
Sadly no, this corresponds to reflashing the whole phone, block by block.
have you tried to find matching drivers ? (it should be pretty easy on windows 10 normally...)
Click to expand...
Click to collapse
Install this regfix https://www.dc-unlocker.com/huawei-mate-10-fastboot-usb-device-not-recognised-fix
However, you would probably have had problems before too when flashing twrp.
But worth a shot I guess.
Didn't see it said you tried on win 7 too.
And if it worked before on Win 10 it should work without it.
I guess you could push system.img to /data/system.img then tap Install and selectInternal storage, tap on (go up one level) in browser, now you'll be at /. Tap on /data and then on system.img. Flash to 'System Image'.
Edit: I've tested with recovery and that flashes fine from /data/.
please see below;
Hi all. My SDCARD was encrypted in TWRP, so I googled and saw I should run this command;
recovery --wipe_data --set_filesystem_encryption=off
Which I did on TWRP terminal - and now im boot looping again. I tried fastboot system.img and it's still bootloading. I see there's supposed to be a 'boot.img' in my update.app, but there isn't.
Any ideas?
Toldorn said:
Hi all. My SDCARD was encrypted in TWRP, so I googled and saw I should run this command;
recovery --wipe_data --set_filesystem_encryption=off
Which I did on TWRP terminal - and now im boot looping again. I tried fastboot system.img and it's still bootloading. I see there's supposed to be a 'boot.img' in my update.app, but there isn't.
Any ideas?
Click to expand...
Click to collapse
Boot.img is for Nougat. Oreo uses ramdisk.
Try wiping data in TWRP (Wipe - Format Data).
You can't turn off encryption in TWRP. It's controlled by /vendor/etc/*.fstab (* = kirin970 in this case). (You can temporarily turn off encryption but it re-encrypts after booting if fstab is untouched)
But removing encryption won't fix you bootlooping, and that command you used is for Full disk encryption, we use file based encryption.
You could also try flashing back stock recovery and do factory reset from there.
Edit: Oh, you're the guy who PM'd me
I've reflashed my 'system.img' as before - but im having trouble getting into factory reset menu.
all it ever does is go into e'Recovery instead, which is useless.
Also, my booting image is still a green page of pixels - rather than a huawei logo.
Hi. I have a bla-a09 and need help. can boot into twrp but will not boot.
After unlocking, I installed EU rom via adb, the installed unofficial TWRP 3.4.1b -0506 and rooted.
I used the phone without any probems for some days .
I then decided to get rid of MI software. After uninstalling a lot of software using App Uninstaller by Jumobile.
Also after that the phone worked well for an hour or two, but after a reboot the phone always goes into Fastboot.
I still can go into TWRP. When I try to install Curtana Global from external SD card, TWRP returns "Install zip Successful" but with an error message
"Failed to mount "/vendor" (Read-only file system)
I am very grateful for any help to unbrick my phone
Bruno
brufi said:
After unlocking, I installed EU rom via adb, the installed unofficial TWRP 3.4.1b -0506 and rooted.
I used the phone without any probems for some days .
I then decided to get rid of MI software. After uninstalling a lot of software using App Uninstaller by Jumobile.
Also after that the phone worked well for an hour or two, but after a reboot the phone always goes into Fastboot.
I still can go into TWRP. When I try to install Curtana Global from external SD card, TWRP returns "Install zip Successful" but with an error message
"Failed to mount "/vendor" (Read-only file system)
I am very grateful for any help to unbrick my phone
Bruno
Click to expand...
Click to collapse
Hello
Why not to flash a fastboot rom via Miflash? Phone will be from clean basis.
Test the new Miflashpro if you have time.
Good luck.
Note 9S not yet listed in Miflashpro; fastboot rom not found
thanks Lolo93939 for the input.
I found miflashpro under a com domain with the same name and installed the most recent version 4.3.1220.29. Selection of device does not include Redmi Not 9 S or Pro, accordingly moflashpro can not be used as of today for note 9S.
I then downloaded XIAOMIFlashTool from the com domain of the same name: miflash20191206.zip and installed
Downloaded latest fastboot rom from mifirm net / model / curtana.ttt which is V11.0.7.0.QJWMIXM.
unziped the rom 2 times until I had a folder with subfolder "Images" and shortened the folder name to V11.0.7.0.QJWMIXM and copied it under new folder c:XIAOMI
Executed XiaoMIFlash.exe, selected V11.0.7.0.QJWMIXM folder, selected "clean all" at bottom (to make sure the device is not locked again), then connected phone in Fastboot screen, refreshed in XiaoMiFlash and flashed.
Flash ended with error but phone seems to be up and running again.
brufi said:
Lolo93939, i would love too. I have searched for 3 hours now and did not find a functioning Miflash. I tried the 2 latest versions from xiaomiflash com but both give out an error "could not find flash script."
I find Stable roms for curtana but all links to fastboot roms end in 404 pages.
Could you point me to source of Miflash and a fastboot rom?
Thanks a lot!
Click to expand...
Click to collapse
It doesn't find your computer path for stating flashing.
Did you unzip the tgz and the tar file?
Place the unzipped result close to your computer C: directory and clean as much as possible the name.
That MUST work...
https://mirom.ezbox.idv.tw/en/phone/curtana/
Thank you! I did as suggested.
all worked well, but got
error: not catch checkpoint (\$fastoot -s . *lock).flash is not done
still the phone is up and running again, so things seem to be good.
:good:
brufi said:
Thank you! I did as suggested.
all worked well, but got
error: not catch checkpoint (\$fastoot -s . *lock).flash is not done
still the phone is up and running again, so things seem to be good.
:good:
Click to expand...
Click to collapse
Yeah, had the "catch checkpoint" error, too.
Don't mind, phone is running without problems after that, also when you got this error.
Biggest difference I've noticed is that I had to restart the device manually after flashing (normally without this error, it would reboot automatically) ?
By the way, have you edited your posts a few times?
That makes it hard for other users to understand the whole problem and on that way maybe your posts can't help other users with same problem, so please don't edit/change whole postings ?