Hi,
i tried to update to OpenKirin RR Beta 3, but flashing failed with fastboot (fastboot flash system C:\Daten\rr3.img.xz)
target reported max download size of 471859200 bytes
Invalid sparse file format at header magi
error: write_sparse_skip_chunk: don't care size 131128796 is not a multiple of the block size 4096
sending sparse 'system' 1/2 (460796 KB)...
error: write_sparse_skip_chunk: don't care size 131128796 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 131128796 is not a multiple of the block size 4096
OKAY [ 10.747s]
writing 'system' 1/2...
FAILED (remote: sparse flash write failure)
finished. total time: 14.841s
Click to expand...
Click to collapse
I had installed magisk with OpenKirin beta2 before. After failed flashing the device tries booting a few times but then it boots to eRevovery.
I tried flashing -kernel-recovery-ramdisk 368 from @JBolho Thread (https://forum.xda-developers.com/honor-9/how-to/emui8-kernel-recovery-ramdisk-stock-t3781347), because i thought something went wrong with the patched boot.img from magisk. But no success. Still bootloops and ended in eRecovery.
Can somebody help?
Thank you
P.S.: I posted this question in https://forum.xda-developers.com/honor-9/development/roms-openkirin-aosp-collection-t3828787/page3 too, but i don't know if somebody reads it there.
You tried to flash the compressed file instead of extracting the img file from it...
JBolho said:
You tried to flash the compressed file instead of extracting the img file from it...
Click to expand...
Click to collapse
Thank you. Rookie mistake. Flashing system now works, but boot ends in eRecovery too.
Saftpresse99 said:
Thank you. Rookie mistake. Flashing system now works, but boot ends in eRecovery too.
Click to expand...
Click to collapse
OpenKirin website where the rom can be downloaded has full installation instructions.
You flashed recovery, ramdisk and kernel from B368, was that the EMUI version you were before?
I would recommend flashing TWRP and re-install B368 with HuRUpdater tool, reboot to stock recovery (not eRecovery), wipe cache and do a factory reset, turn off the device and boot in fastboot mode, flash RROS and reboot again.
JBolho said:
OpenKirin website where the rom can be downloaded has full installation instructions.
You flashed recovery, ramdisk and kernel from B368, was that the EMUI version you were before?
I would recommend flashing TWRP and re-install B368 with HuRUpdater tool, reboot to stock recovery (not eRecovery), wipe cache and do a factory reset, turn off the device and boot in fastboot mode, flash RROS and reboot again.
Click to expand...
Click to collapse
I don't know my EMUI version before. Is it important?
I choose B368, because it was the last version available.
Saftpresse99 said:
I don't know my EMUI version before. Is it important?
I choose B368, because it was the last version available.
Click to expand...
Click to collapse
Of course it's important, the stock kernel, recovery and ramdisk must match the EMUI version installed or it will never boot.
JBolho said:
Of course it's important, the stock kernel, recovery and ramdisk must match the EMUI version installed or it will never boot.
Click to expand...
Click to collapse
What can i do to determine the correct version?
With B360 i can boot and the splash screen from RR3 appears. But after some time the phone restarts into eRecovery. I tried RR2 and phhusson's treble roms , which factory reset and wipe cache. Rom boots but then the device restarts into eRecovery.
Saftpresse99 said:
With B360 i can boot and the splash screen from RR3 appears. But after some time the phone restarts into eRecovery. I tried RR2 and phhusson's treble roms , which factory reset and wipe cache. Rom boots but then the device restarts into eRecovery.
Click to expand...
Click to collapse
Please do what I told you earlier, it's the best way. Flash zxz0O0's TWRP and use HuRUpdater tool to flash EMUI again, get the FullOTA from Firmware Finder of B368 or B369 at the most.
Then do a factory reset and see if it boots properly.
After that go to OpenKirin website and follow instructions carefully.
JBolho said:
Please do what I told you earlier, it's the best way. Flash zxz0O0's TWRP and use HuRUpdater tool to flash EMUI again, get the FullOTA from Firmware Finder of B368 or B369 at the most.
Then do a factory reset and see if it boots properly.
After that go to OpenKirin website and follow instructions carefully.
Click to expand...
Click to collapse
Thanks. Installed twrp, but can't get FullOTA from firware finder: http://pro-teammt.ru/projects/hwff/v2/GetLatestVersion.action Site is down. :crying:
Installing zxz0O0 works but if i try to boot into recovery it stucks on welcome screen. Nothing happens. Log attached.
I tried this twrp: https://forum.xda-developers.com/ho...p-ish-twrp-3-2-1-honor-9-running-gsi-t3818442 and this boots.
Saftpresse99 said:
Installing zxz0O0 works but if i try to boot into recovery it stucks on welcome screen. Nothing happens. Log attached.
I tried this twrp: https://forum.xda-developers.com/ho...p-ish-twrp-3-2-1-honor-9-running-gsi-t3818442 and this boots.
Click to expand...
Click to collapse
You can also flash roms with HuRUpdater using that twrp. The problem now is getting the rom, try to search on other forums as well, like 4pda and such, since FF is down...
JBolho said:
You can also flash roms with HuRUpdater using that twrp. The problem now is getting the rom, try to search on other forums as well, like 4pda and such, since FF is down...
Click to expand...
Click to collapse
Hi,
thank you very much. My device is now working again. Your instructions working very well. I flashed stf-L09c432 B360 with HuRUpdater and device boots. I donwloaded the firware from this site: http://huawei-firmware.com/phone-list/huawei-honor-9
Related
DISCLAIMER: This is NOT my work. This files I've downloaded from a different site and flashed them to my device with success. I will not take any responsibility for anything wrong happen to your device. Do it at your own risk. Also, I will not update this thread. I just want to share this information.
After searching for hours I found on a site in Taiwan the way to root the ZenFone 3 Ultra on latest update of Android 7.0 (WW_14.1010.1703.42)
Here are the steps I did:
1. Unlock Bootloader with the original program from Asus website.
2. Flash TWRP 3.1.1 recovery with fastboot.
3. Reboot in to Recovery and installed SuperSU-v2.80-201705171619.zip
4. Wipe cache and reboot.
5. Once booted DO NOT UPDATE SuperSU from Play Store, it will break the root.
Both files are in the link below.
Files:
https://drive.google.com/open?id=0B69uFcMh3Eb6QTFSYXF1TzZxX00
Thank you for your share. I am on my 2nd ZF3U and will look to keep this UNROOTED and BOOTLOADER LOCKED until a decent custom rom becomes available but looks like the developer community does not want to touch this device which is really sad as in my opinipn it is the best large screen phablet currently available,?
AWFRONT said:
Thank you for your share. I am on my 2nd ZF3U and will look to keep this UNROOTED and BOOTLOADER LOCKED until a decent custom rom becomes available but looks like the developer community does not want to touch this device which is really sad as in my opinipn it is the best large screen phablet currently available,?
Click to expand...
Click to collapse
I was going to do the same but I got tired of the ads and bloatware, so I needed root to install AdAway and Titanium Backup to clean the preinstalled programs
Any reason for the v2.80 vs the 2.79? I was rooted before with 2.79 and didn't have any issues that I saw.
doctahjeph said:
Any reason for the v2.80 vs the 2.79? I was rooted before with 2.79 and didn't have any issues that I saw.
Click to expand...
Click to collapse
That is what they recommend on the other site. I do not know why.
once you've done this, does it block OTA updates from Asus?
speculatrix said:
once you've done this, does it block OTA updates from Asus?
Click to expand...
Click to collapse
I think so.
speculatrix said:
once you've done this, does it block OTA updates from Asus?
Click to expand...
Click to collapse
Once you unlock the bootloader the OTAs are blocked, even if you aren't rooted. It is okay you can still manually install the firmware easily.
mushufasas said:
[
5. Once booted DO NOT UPDATE SuperSU from Play Store, it will break the root.
Click to expand...
Click to collapse
I updated it & still have root
I have rooted again on latest firmware and used Supersu 2.79. Works as advertised so far.
Gone Looking
mushufasas said:
DISCLAIMER: This is NOT my work. This files I've downloaded from a different site and flashed them to my device with success. I will not take any responsibility for anything wrong happen to your device. Do it at your own risk. Also, I will not update this thread. I just want to share this information.
After searching for hours I found on a site in Taiwan the way to root the ZenFone 3 Ultra on latest update of Android 7.0 (WW_14.1010.1703.42)
Here are the steps I did:
1. Unlock Bootloader with the original program from Asus website.
2. Flash TWRP 3.1.1 recovery with fastboot.
3. Reboot in to Recovery and installed SuperSU-v2.80-201705171619.zip
4. Wipe cache and reboot.
5. Once booted DO NOT UPDATE SuperSU from Play Store, it will break the root.
Both files are in the link below.
Files:
https://drive.google.com/open?id=0B69uFcMh3Eb6QTFSYXF1TzZxX00
Click to expand...
Click to collapse
Currently at WW_14.1010.1703.36 so off to find xxxxxx42.
This process will not work on my Ultra at rev 36.
cheers,
av8or091 said:
Currently at WW_14.1010.1703.36 so off to find xxxxxx42.
This process will not work on my Ultra at rev 36.
cheers,
Click to expand...
Click to collapse
Have now update to rev 46 and this process still defaults to Android recovery on my Ultra.
I have used your files included in the attached zip and it will not install TWRP.
Thoughts?
av8or091 said:
Have now update to rev 46 and this process still defaults to Android recovery on my Ultra.
I have used your files included in the attached zip and it will not install TWRP.
Thoughts?
Click to expand...
Click to collapse
I do not know why, but I had to reinstall the rom on my phone, used the same files for root and it worked with no problem.
I have updated to UL-ASUS_A001-WW-14.1010.1704.46 using the file from ASUS support page and used the same method to root, and it worked without a problem.
Suggested Edit
mushufasas said:
I have updated to UL-ASUS_A001-WW-14.1010.1704.46 using the file from ASUS support page and used the same method to root, and it worked without a problem.
Click to expand...
Click to collapse
As there can be more than one method in which to select 'Recovery Mode' your third line should read as follows;
3. Do not select Recovery Mode from Fastboot Menu, Reboot Phone then select Recovery Mode to install SuperSU-v2.80-201705171619.zip
C:\Users\xxxxxx\>adb reboot bootloader
C:\Users\xxxxxx\>fastboot flash recovery twrp3.1.1.img
target reported max download size of 536870912 bytes
sending 'recovery' (19986 KB)...
OKAY [ 0.772s]
writing 'recovery'...
OKAY [ 0.331s]
finished. total time: 1.109s
C:\Users\xxxxxx\>fastboot reboot
rebooting...
Works like a charm, thanks for the research making this available.
signature verification failed
hi i have 14.1010.1705.49-20170602 verison
twpr flash is ok but when i try to flash supersu
i get signature verification failed
any help please
TH
krcma.cz said:
hi i have 14.1010.1705.49-20170602 verison
twpr flash is ok but when i try to flash supersu
i get signature verification failed
any help please
TH
Click to expand...
Click to collapse
i flash downgrade fw WW-14.1010.1703.42
and flashing of supersu still not working
any idea ?
av8or091 said:
As there can be more than one method in which to select 'Recovery Mode' your third line should read as follows;
3. Do not select Recovery Mode from Fastboot Menu, Reboot Phone then select Recovery Mode to install SuperSU-v2.80-201705171619.zip
C:\Users\xxxxxx\>adb reboot bootloader
C:\Users\xxxxxx\>fastboot flash recovery twrp3.1.1.img
target reported max download size of 536870912 bytes
sending 'recovery' (19986 KB)...
OKAY [ 0.772s]
writing 'recovery'...
OKAY [ 0.331s]
finished. total time: 1.109s
C:\Users\xxxxxx\>fastboot reboot
rebooting...
Works like a charm, thanks for the research making this available.
Click to expand...
Click to collapse
seems like all went well for me . . . unlocked / twrp / superuser / even the upgraded kernel & software upgrade ........ but the system hangs on the start screen ... but upon restart - the zenphon still goes into bootloader & twrp if i want to.
I don't suppose anyone made a twrp backup of a fresh / no added programs? Even one w/ bloat removed?
anybody able to show a bit of love?
thx in advance
Bummer . . . . no one's made a twrp backup yet? That's one of the 1st things i do - just in case.
.
Is it possible to update to new version of SuperSU then 2.80 ?
I try to update SuperSU with TWRP to version 2.82-201705271822.zip but installation failed....
I want to rollback to B190 to B150. Tried with /dload (B150 update.app), no success. Mostly because, there is no root on B190 with Kingroot. I did not tried Magisk, yet. Have to flash TWRP with ADB. Not likely to me.
So, is there any chance for downgrade?
Phone came with B150, upgraded to B170, then B181 and to B190.
Device is SCL-L01C432.
If You need more information, please tell me.
3zero3 said:
I want to rollback to B190 to B150. Tried with /dload (B150 update.app), no success. Mostly because, there is no root on B190 with Kingroot. I did not tried Magisk, yet. Have to flash TWRP with ADB. Not likely to me.
So, is there any chance for downgrade?
Phone came with B150, upgraded to B170, then B181 and to B190.
Device is SCL-L01C432.
If You need more information, please tell me.
Click to expand...
Click to collapse
With the fastboot method if you have the bootloader unlocked, there are many tutorials on the net. But how did you rate an upgrade to the B170 ??
Androfish said:
With the fastboot method if you have the bootloader unlocked,
Click to expand...
Click to collapse
Unlock bootloader is the very first thing I did.
Androfish said:
there are many tutorials on the net.
Click to expand...
Click to collapse
But I am not really, really sure, which one will work with B190?
You mean flash custom recovery, custom ROM, then try to comeback to stock recovery and stock ROM?
Ok, looking now inside B190 update.zip and there is B190 recovery.img. (12.recovery.img in Huawei Update Extractor)
I see this with magisk:
https://forum.xda-developers.com/showpost.php?p=73838305&postcount=24
Should I try for B190?
Last version of KingRoot (5.3) is not working.
I found (on internet ) for some other Huawei phone, there is some special "middle package" (update.zip) to get the possibility for downgrade. Maybe I need that "special package"?
Androfish said:
But how did you rate an upgrade to the B170 ??
Click to expand...
Click to collapse
With Firmware Finder.
There is update (for me) numbered under #63737.
Update from:
SCL-L01C432B150CUSTC432D008
to:
SCL-L01C432B170CUSTC432D004
Put in /dload and update.
Have not used much B170, but B190 work smoothly.
You just have to download the b150 version and after extracting with Huawei extract the necessary files including the recovery stock, make the flash with fastboot:
fastboot system system.img
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash cust cust .img
quick reboot
I followed Your instruction for fastboot.
Boot, recovery, system flashed. Cust cannot be flashed. They are from B150.
Code:
target reported max download size of 266338304 bytes
sending 'cust' (194411 KB)...
OKAY [ 6.275s]
writing 'cust'...
FAILED (remote: Command not allowed)
finished. total time: 6.283s
Tried to flash whole B150 (UPDATE.APP) with:
Settings -> Updater
EMUI Updater (Volume Up + Volume Down + Power)
Project Menu -> Update (it mean *#*#2846579#*#*)
Nothing work.
Now I have "half" B190 and "half" B150 in my phone.
Is there any way to flash whole B150 (UPDATE.APP)?
Please? Anybody?
Have weird problems, like i cannot remove widgets, launcher crash sometimes, etc...
I do not know is there any downgrade package? Or something?
Maybe I need SCL-L01C432B190CUSTC432D002 firmware? If exist?
Given that I still do not understand how you have run the B190 version on this device, try to install this version always with the fastboot method: http: //huawei-firmware.com/rom/huawei-y6/scl-l01/1027
After install any other updated B150 version and it should work.
The cust.img file I do not know why but it does not work with fastboot.
---------- Post added at 09:20 AM ---------- Previous post was at 09:14 AM ----------
Androfish said:
Given that I still do not understand how you have run the B190 version on this device, try to install this version always with the fastboot method: http: //huawei-firmware.com/rom/huawei-y6/scl-l01/1027
After install any other updated B150 version and it should work.
The cust.img file I do not know why but it does not work with fastboot.
Click to expand...
Click to collapse
Rom: http://huawei-firmware.com/rom/huawei-y6/scl-l01/1027
hi there.
soooo I kinda bricked my mate 10 lite (RNE-L21C432)
bootloader is unlocked, rooted.
I tried flashing a flashable rom and got a bootloop...sooooo
I downloaded the firmware via huawei firmware finder , the oreo one.
I opened the UPDATE.APP via huawei update extractor, there are alot of files, so can you please tell me what files I need to extract and flash to unbrick my phone?
I extracted system, kernel, vendor and odm for now, system flashed fine. but I cant flash kernel it gives me the error FAILED: remote: command not allowed
can you pleaste help me?
Edit: I can flash system, I did flash kernel, I can flash recovery too, but when I try to flash anything else, it gives me that error
Edit2: can someone tell me which files do I need to extract via huawei update extractor to flash? I know that system.img is one of them
konopla4 said:
hi there.
soooo I kinda bricked my mate 10 lite (RNE-L21C432)
bootloader is unlocked, rooted.
I tried flashing a flashable rom and got a bootloop...sooooo
I downloaded the firmware via huawei firmware finder , the oreo one.
I opened the UPDATE.APP via huawei update extractor, there are alot of files, so can you please tell me what files I need to extract and flash to unbrick my phone?
I extracted system, kernel, vendor and odm for now, system flashed fine. but I cant flash kernel it gives me the error FAILED: remote: command not allowed
can you pleaste help me?
Click to expand...
Click to collapse
Check if you're still FRP unlock in Fastboot.
ante0 said:
Check if you're still FRP unlock in Fastboot.
Click to expand...
Click to collapse
Both bootloader and from are unlocked
konopla4 said:
Both bootloader and from are unlocked
Click to expand...
Click to collapse
Ah, didn't see your edit.
Fastboot is limited in flashing, you can't flash everything.
From memory I think it is:
System, vendor, recovery_ramdisk, recovery_vendor, recovery_vbmeta, ramdisk, kernel, cache, userdata
You could use HWOTA for Mate 10 Lite if you can get into stock recovery, as it will flash the full update.app rather than the limited partitions fastboot can flash.
https://forum.xda-developers.com/ma...development/hwota-huawei-mate10-lite-t3777115
ante0 said:
Ah, didn't see your edit.
Fastboot is limited in flashing, you can't flash everything.
From memory I think it is:
System, vendor, recovery_ramdisk, recovery_vendor, recovery_vbmeta, ramdisk, kernel, cache, userdata
Click to expand...
Click to collapse
So I can flash all of these without getting the error and it'll will restore my system?
I remember on p8 lite I needed to flash only system, boot, and cust. To restore the system. It was much easier.
konopla4 said:
So I can flash all of these without getting the error and it'll will restore my system?
I remember on p8 lite I needed to flash only system, boot, and cust. To restore the system. It was much easier.
Click to expand...
Click to collapse
Edited while you posted, use HWOTA if you can get into stock recovery
https://forum.xda-developers.com/ma...development/hwota-huawei-mate10-lite-t3777115
ante0 said:
Edited while you posted, use HWOTA if you can get into stock recovery
https://forum.xda-developers.com/ma...development/hwota-huawei-mate10-lite-t3777115
Click to expand...
Click to collapse
Yeah, just noticed.
So hwota. I don't have the "stock recovery" I can only flash the recovery that I extract from update.app
The one I flash is bugged for some reason, probably because it's from a slightly different system than the one I had.
konopla4 said:
Yeah, just noticed.
So hwota. I don't have the "stock recovery" I can only flash the recovery that I extract from update.app
The one I flash is bugged for some reason, probably because it's from a slightly different system than the one I had.
Click to expand...
Click to collapse
If it can be booted into it should work. HWOTA will replace it anyway with a no-check recovery. Or you could use TWRP by Caucava21 and use HuRUpdater (https://forum.xda-developers.com/honor-9/development/tool-flash-official-firmware-recovery-t3769279) to update from TWRP.
Either way will work.
ante0 said:
If it can be booted into it should work. HWOTA will replace it anyway with a no-check recovery. Or you could use TWRP by Caucava21 and use HuRUpdater (https://forum.xda-developers.com/honor-9/development/tool-flash-official-firmware-recovery-t3769279) to update from TWRP.
Either way will work.
Click to expand...
Click to collapse
Waaaait it, I can update from TWRP?
Or is it a specialized one?
konopla4 said:
Waaaait it, I can update from TWRP?
Or is it a specialized one?
Click to expand...
Click to collapse
It's a script, but it needs a TWRP that's compatible. The one by Catuva21 is (or so I've heard).
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
My Mi 8 Lite had stock, rooted (Magisk) MIUI Oreo and I dirty flashed MIUI Pie with TWRP 3.2.3. It booted up again with no problems and everything works but when I boot into recovery it now asks for a password to decrypt the data partition. Needless to say, the PIN for unlocking the screen is not accepted by TWRP. I'm hoping I won't need to wipe the data partition to fix this. Any ideas?
Thanks
<bump> anyone?
Sent from my MI 8 Lite using Tapatalk
If you are using the wzsx150 TWRP, notice that versions 1003/1203 are for Oreo only. You need to upgrade to versions 0121, 0212 or 0330 for Pie.
chan200606 said:
If you are using the wzsx150 TWRP, notice that versions 1003/1203 are for Oreo only. You need to upgrade to versions 0121, 0212 or 0330 for Pie.
Click to expand...
Click to collapse
Thanks a million, that fixed the problem. This information should be made available on the existing TWRP posts. I had a job finding the updated recoveries to download but came across a Google Drive folder that someone had posted https://drive.google.com/drive/folders/1780TJvn-ZHPBtgDdNjrN8i9YRlqPy38v - I went with the 0330 version which seems to be working fine.
dwl99 said:
Thanks a million, that fixed the problem. This information should be made available on the existing TWRP posts. I had a job finding the updated recoveries to download but came across a Google Drive folder that someone had posted https://drive.google.com/drive/folders/1780TJvn-ZHPBtgDdNjrN8i9YRlqPy38v - I went with the 0330 version which seems to be working fine.
Click to expand...
Click to collapse
I had the same problem (TWRP asking for password to decrypt data partition) and I have the 1003 version. So I am going to flash 0121, 0212 or 0330. Which do you recommend?
0330
Sent from my MI 8 Lite using Tapatalk
When I flashed 0330 the touchscreen is not working in twrp. How do I fix this?
tuytel said:
When I flashed 0330 the touchscreen is not working in twrp. How do I fix this?
Click to expand...
Click to collapse
This device has 3 different touchscreen panels (that I know of) and one of them is not fully supported. Which seems to be the one you have. To fix the problem the recovery needs some additions on source and then compiled. I suggest connecting to a pc and copying what you need off the internal storage and then use a recovery that your touchscreen works with and format the data partition using the option that asks you to type yes. This will remove encryption and allow you to access data no matter what recovery you use.
Maybe it's a stupid question bud wat is soue8and ?
tuytel said:
Maybe it's a stupid question bud wat is soue8and ?
Click to expand...
Click to collapse
My arthritis is bad today and it causes some issues with phone keyboard. It should say "source and". I went back and corrected it.
tuytel said:
When I flashed 0330 the touchscreen is not working in twrp. How do I fix this?
Click to expand...
Click to collapse
If you are not encrypted, flash OrangeFox recovery using the adb/fastboot method.
DarthJabba9 said:
If you are not encrypted, flash OrangeFox recovery using the adb/fastboot method.
Click to expand...
Click to collapse
Link to download OrangeFox?
I see: https://sourceforge.net/projects/orangefox/files/platina/OrangeFox-R9.0-2-platina.zip/download
MelvinGt5 said:
Link to download OrangeFox?
I see: https://sourceforge.net/projects/orangefox/files/platina/OrangeFox-R9.0-2-platina.zip/download
Click to expand...
Click to collapse
Yes, that is the correct download link.
I tried to flash this TWRP several times : TWRP-3.2.3-1003-XIAOMI8LITE-CN-wzsx150.img
but asks me for the password to decrypt the partition
later I read this trhead and tried to flash 0330 but now it returns the following error: Sending 'recovery' (63448 KB) FAILED (Write to device failed (Invalid argument))
What is the problem ?
Thank you
redblack68 said:
I tried to flash this TWRP several times : TWRP-3.2.3-1003-XIAOMI8LITE-CN-wzsx150.img
but asks me for the password to decrypt the partition
later I read this trhead and tried to flash 0330 but now it returns the following error: Sending 'recovery' (63448 KB) FAILED (Write to device failed (Invalid argument))
What is the problem ?
Thank you
Click to expand...
Click to collapse
Looks like you typed something wrong
cidxtc said:
Looks like you typed something wrong
Click to expand...
Click to collapse
it seems that adb / fastboot command no works
not even FASTBOOT ERASE CACHE
with FASTBOOT DEVICES the phone is seen
the phone runs normally
do I do a factory reset?
redblack68 said:
it seems that adb / fastboot command no works
not even FASTBOOT ERASE CACHE
with FASTBOOT DEVICES the phone is seen
the phone runs normally
do I do a factory reset?
Click to expand...
Click to collapse
Do you have root access in rom? If so you can flash rhe recovery image with an app called flashify. You can use the free version from playstore.
cidxtc said:
Do you have root access in rom? If so you can flash rhe recovery image with an app called flashify. You can use the free version from playstore.
Click to expand...
Click to collapse
No, no root. I would like to flash twrp to root with magisk
redblack68 said:
No, no root. I would like to flash twrp to root with magisk
Click to expand...
Click to collapse
Your bootloader was unlocked with mi unlocker?
cidxtc said:
Your bootloader was unlocked with mi unlocker?
Click to expand...
Click to collapse
Yes exactly
but now if i turn on my phone in fastboot, when i give an adb / fastboot command, the screen goes black and in the top left there is a very very small image " any key to shutdown". The same if i connect my phone in fastboot mode with mi unlocker