Hi
Emui 9.1.0.257
I have TWRP 3.4.0-1 installed i trying format data waiting over 10min
Any ideas.
Hello again - I had the same issue and after restarting without any success notice in TWRP, I was left with an not booting system.
I could fix it by flashing all the different needed *img files via fastboot. This was needed as my rescue tasks may made it even worse.
Do you have any idea why this happend? The used TWRP was TWRP-3.4.0.0-emui9_eR.img
horqai said:
Hello again - I had the same issue and after restarting without any success notice in TWRP, I was left with an not booting system.
I could fix it by flashing all the different needed *img files via fastboot. This was needed as my rescue tasks may made it even worse.
Do you have any idea why this happend? The used TWRP was TWRP-3.4.0.0-emui9_eR.img
Click to expand...
Click to collapse
Hi!
I have the same problem and tried to fix it via flashing *img files, but I don't know which. I downloaded an update.zip and extracted some *img files from the UPDATE.APP. I read somewhere that I need to flash kernel, system, ramdisk and recovery_ramdisk to get back to the stock rom. But I didn't find a ramdisk.img file to flash. So which is necessary to restore at least erecovery to get back stock rom and where to get the right files?
lenzelot said:
But I didn't find a ramdisk.img file to flash.
Click to expand...
Click to collapse
On EMUI 9.1 ramdisk is included in the recovery_ramdisk.
Try this way out...
- Make sure to have the stock recovery flash
- Download correct Service ROM for your region and EMUI version ( Settings > About phone > build number.
The bracketed (Cxxx) is your device’s regional variant. This number is very important in determining the correct firmware to download!)
- download Service ROM here: Androidhost.ru website, (type Ane- or Anne-).
- Unpack .zip archive , find dload file in "Software" folder, and simply transfer it to the SD card, without unpacking it!
- Turn off your phone and flash FW using three button combo. The process will erase all your data! (and lock again the bootloader! ).
Edit: you can also try following:
- Install TWRP (on Pie)
- In TWRP flash eRecovery_ramdisk (use button Install image ). Then reboot into eRecovery and download latest versiom via WiFi.
-Alf- said:
On EMUI 9.1 ramdisk is included in the recovery_ramdisk.
Try this way out...
- Make sure to have the stock recovery flash
- Download correct Service ROM for your region and EMUI version ( Settings > About phone > build number.
The bracketed (Cxxx) is your device’s regional variant. This number is very important in determining the correct firmware to download!)
- download Service ROM here: Androidhost.ru website, (type Ane- or Anne-).
- Unpack .zip archive , find dload file in "Software" folder, and simply transfer it to the SD card, without unpacking it!
- Turn off your phone and flash FW using three button combo. The process will erase all your data! (and lock again the bootloader! ).
Click to expand...
Click to collapse
Thanks for the quick response. I think I tried something like that but unfortunately the transfer to the phone stopped due to storage shortage. Is there any partition I could format using fastboot or adb if this is possible? So far I can only access the bootloader and the start screen of twrp (without really booting it). In the latter state it is possible to run adb commands.
Just read the edit. Will try so.
lenzelot said:
Is there any partition I could format using fastboot
Click to expand...
Click to collapse
Try fastboot command
fastboot erase userdata
and restart.
lenzelot said:
the transfer to the phone stopped due to storage shortage
Click to expand...
Click to collapse
You can use also OTG.
Sorry for the late response and thanks for your great help!! erasing the userdate was the key
Related
I just make my mobile unlock(KIW-TL00C01), I have tried
1. extract the image of UPDATE.app from B228 and fastboot flash (failure)
https://forum.xda-developers.com/honor-7/general/guide-beginners-how-to-root-update-fix-t3255452
2. using e-recovery(internal recovery), put firmware zip file(B228) in dload directory in SDcard, inform failed at 5%,
if you put that file in root directory of SDcard, it would stop at 5%.
3. install the 3rd part firmware from TWRP recovery(installed, but reboot would make the touch screen support in all the place, and boot loops)
I have tried install a different firmware through the adb when the touch screen is broken.
I use the following command, I didn't find a one could work.
Code:
recovery --update_package=/external_sd/firmware.zip
The one thing I could do to is put the UPDATE.app of B430 into dload, and retry the method 2 or my mobile is complete brick.
I wonder does the Huawei update the signature or firmware of TrustZone?
I don't know anything I could do to make it work.
if you want to downgrade, you first have to dload the rollback package, then the actual firmware
the rollback package
Click to expand...
Click to collapse
Oh I don't know that before, but where could I get that?
hizukiayaka said:
I just make my mobile unlock, I have tried
1. extract the image of UPDATE.app from B228 and fastboot flash (failure)
https://forum.xda-developers.com/honor-7/general/guide-beginners-how-to-root-update-fix-t3255452
2. using e-recovery(internal recovery), put firmware zip file(B228) in dload directory in SDcard, inform failed at 5%,
if you put that file in root directory of SDcard, it would stop at 5%.
3. install the 3rd part firmware from TWRP recovery(installed, but reboot would make the touch screen support in all the place, and boot loops)
I have tried install a different firmware through the adb when the touch screen is broken.
I use the following command, I didn't find a one could work.
Code:
recovery --update_package=/external_sd/firmware.zip
The one thing I could do to is put the UPDATE.app of B430 into dload, and retry the method 2 or my mobile is complete brick.
I wonder does the Huawei update the signature or firmware of TrustZone?
I don't know anything I could do to make it work.
Click to expand...
Click to collapse
where are you getting your files ? what is the Full version of your phone KIW-TL00C00 or KIW-TL00C01 or KIW-TL00HC00 ?
you must use the exact version for your phone.
the only useful info on the Honor 7 link you posted is how to flash from dload
nowhere did you say you put update.app in dload folder on ext_sdcard and flash with power + volume up and volume down
First determine the correct file for your phone and then flash it correctly
clsA said:
where are you getting your files ? what is the Full version of your phone KIW-TL00C00 or KIW-TL00C01 or KIW-TL00HC00 ?
you must use the exact version for your phone.
the only useful info on the Honor 7 link you posted is how to flash from dload
nowhere did you say you put update.app in dload folder on ext_sdcard and flash with power + volume up and volume down
First determine the correct file for your phone and then flash it correctly
Click to expand...
Click to collapse
I tried to use the match file, but failed in rollback, it would always inform me that system update failed.
hizukiayaka said:
I tried to use the match file, but failed in rollback, it would always inform me that system update failed.
Click to expand...
Click to collapse
Follow this : https://forum.xda-developers.com/honor-5x/how-to/guide-entering-fastboot-using-key-t3400869
After you entered fastboot, flash twrp, then restart to recovery and copy stock firmware to sdcard.
Even if it fails, you can hold VOL+ button during startup to enter eRecovery, where you can revert to stock using nothing but wireless LAN
P/S : I'm also stuck at bootloops trying to install lineage and mokee, please post a guide if you have done it successfully
This is for real, folks. The first working custom recovery for Asus ZenPad 8.0 Z380M and a method to flash it under a locked bootloader. This took quite a bit of work to make, partly due to having to find a way to bypass the locked bootloader. And because of a kernel configuration issue that limited the size of the initial ramdisk, which took some serious effort to weed out. @lss1977 helped to port it to this device. And of course, credits to TeamWin for TWRP.
In addition to this thread, the current Z300M/Z301M TWRP thread and the the old Z300M recovery/rooting thread may be helpful. These models share the same hardware and software base, so most things that apply to one tablet also apply to the other.
DISCLAIMER
As usual, you do anything described in this post at your own risk. No one but you is responsible for any data loss, bricking or damage of your device.
REQUIREMENTS
Windows PC
SP Flash Tool version 5.1532 (only this version will bypass security checks)*
MediaTek VCOM drivers (available through Windows Update)
Z380M scatter file, attached
Recovery image, attached
Z380M preloader file (optional), available inside the stock firmware download
ZenPad Z380M tablet upgraded to Android N
* If you prefer to use a more recent SP Flash Tool, check out the special image file below.
This won't be a guide on how to use SP Flash Tool. There are plenty of good guides out there like this one on how to set up drivers, load scatter files, flash and make backups with SP Flash Tool. If you're not familiar with this software or how to flash MediaTek devices in general, please do your research before attempting this. I will just get straight to the specifics about the ZenPad 8.
FIRST TIME INSTALLATION
For a locked bootloader:
At this point you should have your tablet powered off, the drivers installed, all of your data backed up, and SP Flash Tool v5.1532's Download tab open and loaded with the tablet's scatter file. Open the download agent file DA_PL.bin, replacing the default MTK_AllInOne_DA.bin. (You can use the AllInOne DA if you want, but the procedure involves extra steps as described below.) Load the extracted TWRP recovery image (twrp-3.2.1-0-z380m.img) under the recovery partition line in the partition table. Click the Download button inside SPFT. Now just connect the USB cable to your tablet and your computer's USB port. It should start the download process automatically and disconnect when finished.
Alternative Method:
If you're using MTK_AllInOne_DA.bin, you have to hold the Volume Up key as you insert the cable, which puts the device into an emergency download mode. In addition, you will need to have the stock preloader*.bin file loaded inside SPFT for it to be able to communicate with your tablet. The preloader is available inside the official zip file download. Do not flash the preloader (untick the box) or any partitions other than recovery. You just need to have a valid bin file selected under the Preloader line.
For an unlocked bootloader:
If you have used the Asus unlock tool to unlock your device, you will still not be able to use fastboot flash to install a custom recovery. However, you can do a "hot boot" or a tethered boot of TWRP. This method doesn't require SP Flash Tool. Download the TWRP image, put your tablet in fastboot mode and connect to PC. Then run this command to boot TWRP dynamically:
fastboot boot twrp-3.2.1-0-z380m.img
Once inside TWRP, flash twrp-3.2.1-0-z380m.img to Recovery using Install -> Install Image. Then reboot to recovery. You may be able to use TWRP in the tethered boot mode, but that could result in glitches due to different parameters passed by the bootloader to the kernel. That's why flashing is recommended.
To update from your installed TWRP version to a new one, just transfer the image to your tablet, then boot to TWRP and install it by going to Install -> Install Image and flashing to Recovery.
START RECOVERY
With the tablet powered off, hold the Volume Up and Power keys together until you get to a menu where you can select "recovery". Use Vol. Up to scroll and Vol. Dn to select. If you have a locked bootloader, it will show a Yellow State message because the recovery is not signed by the OEM. Just press volume up to boot it. On the welcome screen of TWRP it will ask you about modifying the system partition, I suggest you go with Keep System Read-only. Doing otherwise will complicate your OTA updates.
WARNING: Never start the stock recovery from the bootloader menu on this device. It is programmed by the bootloader to instantly wipe your data without any warning. Also, be aware that Android installs the stock recovery at every normal boot cycle. So you either have to flash the TWRP every time you want to run it, or disable the automatic recovery installation in the stock firmware. Any kind of mod to the boot image will prevent the automatic recovery installation. If you're not sure which recovery you have installed, you can always do a 'adb reboot recovery' from Android without risk of data loss.
What works: Basically everything... access to major partitions, decrypted userdata partition, decrypted adoptable storage, external SD card, ADB, USB-OTG, touch interface, splash screen, installing stock Asus OTA/web FW updates
What doesn't work: (no known problems yet, but please report any)
Not guaranteed to work: factory reset
DOWNLOAD
(Updated February 3, 2018: updated kernel to firmware 5.3.18; up-to-date TWRP 3.2.1 sources)
SP Flash Tool v5.1532
Z380M Scatter file for all storage sizes (right click, Save link as...)
Recovery image
Signed image for Flash Tool only -- may be flashed with recent SP Flash Tool versions -- DO NOT INSTALL USING ANY OTHER METHOD -- tested with SPFT 5.1736.
Development and experimental files
Source code
P.S. The thanks button doesn't bite.
Nice one now lets get some custom roms done.
Has anyone installed this yet? I see the file has been downloaded a few times. Any feedback is welcome.
If you want the recovery to stick after reboot either rename or remove system/bin/install_recovery.sh.
lss1977 said:
If you want the recovery to stick after reboot either rename or remove system/bin/install_recovery.sh.
Click to expand...
Click to collapse
The way I did it was to edit the init.rc file inside the boot ramdisk and comment out the service block that calls install_recovery.sh. I used the MTK boot image unpack/repack tools. I don't know, it seems like changing anything on the system partition will break OTA updates because of dm-verity. Because that depends on verifying each block of the file system. I have never even mounted the system as R/W in recovery.
how to create scater file from text posted? I copied all text to MT8163_Android_scatter.txt file but when open with splash tools give error "scatter file is invalid"
please atach your working scatter file to other atachments
PxYra said:
how to create scater file from text posted? I copied all text to MT8163_Android_scatter.txt file but when open with splash tools give error "scatter file is invalid"
please atach your working scatter file to other atachments
Click to expand...
Click to collapse
OK, I added the scatter file as a download. It was a pain in the ass to copy & paste. (But it did work.)
Problem fixed downloaded new version of flashtool 5.16 and scatter working
Ok I installed TWRP on Z380M P00A, and wanna say to other
1. Use VCOM drivers only from splash tool official site
2. To install VCOM drivers first need enter chinese recovery tablet, then in windows device manager you see USB device, install manualy drivers (don forget in windows disable driver signature)
3. Use only SP-Flash-Tool-v5.1532.00, newer or older version not properly working with this phone
Ok, thanks for the update, PxYra. Just to let you know, there are signed versions of VCOM drivers floating around so you don't need to mess with signature enforcement. Here's one: https://www.androidfilehost.com/?fid=24591000424943663. They are also updated by Windows so you can just let Windows Update install them.
Thanks for your work.
Flashing procedure works only with "MTK_AllInOne_DA.bin" method for me. But this is OK!
(Updated May 6, 2017: added kernel from firmware 5.3.7, source code cleanup)
Click to expand...
Click to collapse
is it possible to get the older versions? I need Android 6.x, because of xposed-Framework for my Zenpad 8.0 Z380M.
Greets Freisei
Hey freisei...
I never posted a version for Android 6. There was just one based on the 5.3.6 kernel, practically the same as the current one. That's why I didn't keep it. I could try to build one for you if you want, but I can't test it of course. Does this recovery not boot at all on the old firmware?
It's strange that the DA_PL.bin method didn't work for you. What happened when you tried it? I suppose the old preloader doesn't allow it(?).
hello guys, you think lineage os official version for asus z380kl (p024) will work on our z380m ?
---------- Post added at 08:19 PM ---------- Previous post was at 08:05 PM ----------
Can anyone help me? after selecting recovery img, pressing download and inserting usb cable, nothing happens. Thanks in advance
lss1977 said:
If you want the recovery to stick after reboot either rename or remove system/bin/install_recovery.sh.
Click to expand...
Click to collapse
hello friend, can you please upload that file? I deleted it, but now I need it to revert to official recovery, as my zenpad is bricked! It would be of great help! thanks!
Pires_7 said:
hello friend, can you please upload that file? I deleted it, but now I need it to revert to official recovery, as my zenpad is bricked! It would be of great help! thanks!
Click to expand...
Click to collapse
Your ZenPad didn't brick because you deleted install_recovery.sh. It's because you modified the system partition. Making any mods to system is bad advice unless you know exactly what you're doing. Even mounting it in r/w mode can break it. That's because dm-verity has tripped and is blocking access to changed blocks of the file system. So you have 3 options: mod your boot image fstab file to disable dm-verity, restore the original system image block-for-block (either from backup or official firmware converted to an img file), or wipe userdata (lss reported that to work).
Pires_7 said:
hello guys, you think lineage os official version for asus z380kl (p024) will work on our z380m ?
Click to expand...
Click to collapse
Nope, no chance.
diplomatic said:
Your ZenPad didn't brick because you deleted install_recovery.sh. It's because you modified the system partition. Making any mods to system is bad advice unless you know exactly what you're doing. Even mounting it in r/w mode can break it. That's because dm-verity has tripped and is blocking access to changed blocks of the file system. So you have 3 options: mod your boot image fstab file to disable dm-verity, restore the original system image block-for-block (either from backup or official firmware converted to an img file), or wipe userdata (lss reported that to work).
Nope, no chance.
Click to expand...
Click to collapse
Ok. I made some real s*it, I think I deleted every partition except recovery. Can you provide me a twrp backup or some way around my problem?
What do you mean you deleted every partition except recovery? There's like 28 partitions. You would have to work hard to accomplish that.
My first suggestion is to extract a system.img from the Asus stock firmware zip using this. Then flash it with SP Flash Tool. You might also try to install a full firmware zip from TWRP. Although I have no idea if that will work or if it's even safe to try.
diplomatic said:
What do you mean you deleted every partition except recovery? There's like 28 partitions. You would have to work hard to accomplish that.
My first suggestion is to extract a system.img from the Asus stock firmware zip using this. Then flash it with SP Flash Tool. You might also try to install a full firmware zip from TWRP. Although I have no idea if that will work or if it's even safe to try.
Click to expand...
Click to collapse
i was able to extract system.new.dat from stock firmware zip, but it extracts to a system folder. How do I flash this through sp flash tool?
OK, the system folder you don't need. It should have produced a system.img file also. That's the file you need to flash. Just select it for the system partition row in the partition list and then Download. Hopefully that will be enough.
EDIT: I just looked at the script, and realized the system.img.img file gets deleted in the process. So what you need to do is start the extraction, then after it makes system.img.img, when it starts extracting individual files, hit Ctrl+C. Then you'll end up with the img file.
Thank you very much! it works! YOU are the BEST!
please tell me, in your scatter file, address partition_name: frp (0x80a5000) is correct? if i format this partition (frp), google account remove?
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.
I've bricked my phone and am in need of help!
What I've done:
Unlocked bootloader with a code from DC-Unlocker then using minimal ADB and Fastboot to unlock
Flashed TWRP 3.1.1
Installed Magisk
Took TWRP backup - but I was unable to backup Data (I believe this was due to encryption - recovery.log shwed errors initially on Bluedorid files)
Wiped data with TWPR to try and do a factory reset
This is where my problems started and now I cant restore boot with TWPR the error is "No such file or directory"
I can ADB pull my recovery.log which says
Read info file, restore size is 12444160
Restoring 6 partitions...
Total restore size is 4512MB
I:Restore filename is: /external_sd/TWRP/BACKUPS/L5NDU17B18000539/Stock V7 2018-06-23--16-58-45/boot.emmc.win
I:Restore file system is: 'emmc'.
I:Restore file system is: 'emmc'.
Restoring Boot...
Error opening: '' (No such file or directory)
I can restore OEM recovery and do a factory reset but it hangs at 99%
power down then it goes back to factory reset and goes to 100% - message "Reset Successful!"
but... then it gets stuck in a boot loop
I've tried downloading other stock ROMS and extracting and flashing images via fastboot (Boot, cust, product, recovery, system, vendor, version)
I've tried Huawei Multi-tool but I lack the Userdata.img disk image
I've tried flashing Resurrection Remix N v5.8.5 For Honor 9 (STF) but without success, although the TWRP install says it is successful and the vendor.img flashes fine.
I've tried extracting UPDATE.app files and putting them in sd_card/dload and then 3 button resetting
I've tried the above in external_sd/dload (not sure why - desperation)
I've tried looking on as many threads as I can find on XDA but with no luck
I can always get to fastboot, flash TWRP or OEM recovery, I can also run ADB commands via Putty (in command line they display strangely)
Any suggestions would be greatly appreciated! I am at a loss an quite frustrated, and have been working on this for maybe 15 hours now.:crying:
LOL, Stop your mumbo-jumbos.
I guess you'r still with nougat partitioning because you're using a pretty much outdated twrp.
So just dload flash a nougat 'service repair firmware' from the same region you're firmware is actually, and not any random update.app you 'made' yourself.
For this you'll need a micro-sdcard (or usb-otg) exfat formated :
https://forum.xda-developers.com/honor-9/development/firmware-huawei-honor-9-stf-l09-stock-t3696892
Fixed!
Thank you, I think I even saw this thread but for some reason did not download the file, also the exfat formatting tip was excellent. I owe you a beer!
Can I always use this method to go back if I totally destroy things again even If I update to Oreo?
oslo83 said:
LOL, Stop your mumbo-jumbos.
I guess you'r still with nougat partitioning because you're using a pretty much outdated twrp.
So just dload flash a nougat 'service repair firmware' from the same region you're firmware is actually, and not any random update.app you 'made' yourself.
For this you'll need a micro-sdcard (or usb-otg) exfat formated :
https://forum.xda-developers.com/honor-9/development/firmware-huawei-honor-9-stf-l09-stock-t3696892
Click to expand...
Click to collapse
Unfortunatly, there only nougat 'service repair firmware' available publicly as far I know.
So, for now, you can only use this when on nougat.
When on oreo, you should use HuRUpdater with oreo's Twrp.
Or if you're oreo device is really messed badly, a paying app called DC-Phoenix then HuRUpdater.
Hello,
i was on EMUI 9 with my BKL-L09 and decided to give the custom roms a new try.
So i backed up my recovery_ramdisk (it was rooted with magisk before) and then flashed twrp (version 3.2.3-3).
Now i went for Wipe>format data and gave it a try. Result: it was hanging after makefs->(..) done. So i done the whole procedure again but it was still hanging.
Now i can't get back into twrp, because only the twrp bootscreen is showing up. Even after restoring my recovery_ramdisk backup with fastboot i can't get back into erecovery Is there anything i can do?
Thanks.
Ok, i solved this by myself through downloading the full ota update, extracting everything and flashing new kernel, system and recovery from ota update contents.
Can you put the CMD lines to do it?
Thank you anyway. I think i have the same problem.
jesusdoar said:
Can you put the CMD lines to do it?
Thank you anyway. I think i have the same problem.
Click to expand...
Click to collapse
I don't have this smartphone anymore but i remember the following:
1. Download the Full OTA Zip (e.g. here: https://www.getdroidtips.com/huawei...-update-for-honor-view-10-download-available/
2. Use the Huawei Update Extractor to extract the partitions from the content in the zip file. (https://forum.xda-developers.com/showthread.php?t=2433454)
3. Flash the partitions over the existing ones on your V10 using fastboot "fastboot flash recovery_ramdisk recovery_ramdisk.img , ...) - these contents are inside the full ota package
Greetings
Did it work out for you?
You can also try to flash the original erecovery using fastboot und use the download option inside the Recovery App. This will reset all partitions back to default. But also all data is lost.
Brodelpiet said:
Did it work out for you?
You can also try to flash the original erecovery using fastboot und use the download option inside the Recovery App. This will reset all partitions back to default. But also all data is lost.
Click to expand...
Click to collapse
it works thank you, now the problem is that the erecovery doesn´t download the package to flash.
jesusdoar said:
it works thank you, now the problem is that the erecovery doesn´t download the package to flash.
Click to expand...
Click to collapse
Did you just flash the erecovery or also the normal recovery partition und Kernel from the zip? What kind of error do you get?
Brodelpiet said:
Did you just flash the erecovery or also the normal recovery partition und Kernel from the zip? What kind of error do you get?
Click to expand...
Click to collapse
Yeah i flashed the kernel and the recovery ramdisk. And now it boots into erecovery, but inside the erecovery, the option to download and install the last version of emui doesn´t work, it just shows an error that it can´t get the package info.
thanks for your attention.
greets