Hi there,
I was on firmware V10.3.1.0.PFKEUXM running unofficial LineageOS 16.0 Now, today I flashed the firmware update V10.3.3.0.PFKEUXM in TWRP, which went through without a problem. Unfortunately the device is no longer booting up: I do see the MI and "unlocked" message for around 15 seconds, then the screen goes dark, and that's it.
By pressing volume-down + power I can get into fastboot, and I can flash TWRP for example, but I cannot get the device booted into TWRP (or into system). I am stuck here ... any help is welcome.
Kind regards, mistersixt.
PS: Flashed the new version from here: https://xiaomifirmwareupdater.com/firmware/raphael/
Did you try to flash stock global rom via mi flashtool?
(Just dont forget to unclick flash and lock)!
Mr.Vag said:
Did you try to flash stock global rom via mi flashtool?
(Just dont forget to unclick flash and lock)!
Click to expand...
Click to collapse
Do you have a download link for the EU version which can be used from the MiFlash tool? On www.miui.com I can find the indian version only ...
[edit]Just found this site https://mirom.ezbox.idv.tw/en/phone/raphael/, do I need recovery or the fastboot image?
mistersixt said:
Do you have a download link for the EU version which can be used from the MiFlash tool? On www.miui.com I can find the indian version only ...
[edit]Just found this site https://mirom.ezbox.idv.tw/en/phone/raphael/, do I need recovery or the fastboot image?
Click to expand...
Click to collapse
Yeap..tjats it.
Yes download fastboot rom unzip it on your desktop (you will have a folder) open flashtool refresh and select your ROM.. dont forget at the right om the bottom rhere is an option pre checked flash and lock.. change it to only flash (the first option) an just wait to flash..
Mr.Vag said:
Yeap..tjats it.
Yes download fastboot rom unzip it on your desktop (you will have a folder) open flashtool refresh and select your ROM.. dont forget at the right om the bottom rhere is an option pre checked flash and lock.. change it to only flash (the first option) an just wait to flash..
Click to expand...
Click to collapse
That ends with an error within the miflash tool:
Code:
...
err:sending 'sparecrclist' (0 KB)...
err:FAILED (remote: update sparse crc list failed)
err:finished. total time: 0.016s
error:"Flash sparsecrclist error"
Someone any ideas?
mistersixt said:
That ends with an error within the miflash tool:
Code:
...
err:sending 'sparecrclist' (0 KB)...
err:FAILED (remote: update sparse crc list failed)
err:finished. total time: 0.016s
error:"Flash sparsecrclist error"
Someone any ideas?
Click to expand...
Click to collapse
Maybe file is corrupted? Did you get the error on the beginning?
Try to not move your phone cable when ypu flashing also check ypur adb drivers.
mistersixt said:
That ends with an error within the miflash tool:
Code:
...
err:sending 'sparecrclist' (0 KB)...
err:FAILED (remote: update sparse crc list failed)
err:finished. total time: 0.016s
error:"Flash sparsecrclist error"
Someone any ideas?
Click to expand...
Click to collapse
Make sure you're downloading the fastboot image and not the recovery image. Fastboot images end with .tgz.
Here's the link for latest EEA 10.3.3.0
http://bigota.d.miui.com/V10.3.3.0....KEUXM_20190903.0000.00_9.0_eea_1ff82a2c11.tgz
Sent from my Redmi K20 Pro using Tapatalk
mistersixt said:
That ends with an error within the miflash tool:
Someone any ideas?
Click to expand...
Click to collapse
The Xiaomi firmware site you linked to also has all the ROMs. Go to the menu in the to left, then select MIUI, then search for K20 Pro. You'll see the most recent fastboot and recovery ROMs for each region. There's also a link to the archives where you'll find more or less all previous versions.
So... thanks for the hints, I started from scratch on a different Windows box, and I now successfully flashed the latest global EU version via the XiaomiFlash tool... the device is "up" again.
What I would like to know of course is what happened in the first place! With my Xiaomi Mi5s and Mi6 it was always safe to flash the latest firmware ZIP packages from https://xiaomifirmwareupdater.com/ ... I never had an issue. With bei Mi 9T Pro flashing the V10.3.3.0.PFKEUXM (came from V10.3.1.0.PFKEUXM) from within TWRP the device was unbootable afterwards . What would be the correct procedure in case this way isn't possible any longer?
Kind regards, mistersixt.
Hi,
I confirm the described issue. After flashing the FW package, the phone is in unusable state.
Regards,
meiser
meiser said:
Hi,
I confirm the described issue. After flashing the FW package, the phone is in unusable state.
Regards,
meiser
Click to expand...
Click to collapse
Ok, which means there might be a general issue then, I will let "yshalsager" know.
Kind regards, mistersixt.
Hi,
the same happened to me! After flashing the new firmware EEA my phone did not boot anymore. I had to restore the old firmware by flashing manually all partitions in fastboot to get it back working without data loss.
My phone boots but I cant install TWRP via fastboot on raphael_eea_global_images_V10.3.3.0.PFKEUXM EEA. Installed rom via MiFlash. Going back to 10.3.1.0.
UPDATE: flashed 10.3.1.0. and everything is ok
manul said:
Hi,
the same happened to me! After flashing the new firmware EEA my phone did not boot anymore. I had to restore the old firmware by flashing manually all partitions in fastboot to get it back working without data loss.
Click to expand...
Click to collapse
Would you mind providing the commands you have fired? What exactly did you do?
Thanks in advance,
mistersixt.
mistersixt said:
So... thanks for the hints, I started from scratch on a different Windows box, and I now successfully flashed the latest global EU version via the XiaomiFlash tool... the device is "up" again.
What I would like to know of course is what happened in the first place! With my Xiaomi Mi5s and Mi6 it was always safe to flash the latest firmware ZIP packages from https://xiaomifirmwareupdater.com/ ... I never had an issue. With bei Mi 9T Pro flashing the V10.3.3.0.PFKEUXM (came from V10.3.1.0.PFKEUXM) from within TWRP the device was unbootable afterwards . What would be the correct procedure in case this way isn't possible any longer?
Kind regards, mistersixt.
Click to expand...
Click to collapse
I guess whatever you flashed resulted in corrupted boot file and recovery as well. that's why you could not either boot or go to recovery. In case corrupted boot.img, system redirects to recovery itself. In your case since recovery is also gone, it tries to boot recovery for 15 seconds. then shuts down because it fails.
If anyone fixes this, please tell how
By the way, I used OrangeFox recovery, maybe this is the reason. Did not try TWRP.
manul said:
Hi,
the same happened to me! After flashing the new firmware EEA my phone did not boot anymore. I had to restore the old firmware by flashing manually all partitions in fastboot to get it back working without data loss.
Click to expand...
Click to collapse
How... What did you do? I have the same problem! Please help!
i have resolved it by downloading and extracting the older firmware EEA (Europe) V10.3.1.0.PFKEUXM from the site. Then in the folder firmware-update there are several partition files and you have to flash them via fastboot commands.
i.e. boot the device in fastboot mode (vol-down & pwr-btn).:
fastboot flash xbl xbl.elf
fastboot flash xbl_config xbl_config.elf
fastboot flash abl abl.elf
fastboot flash tz tz.mbn
fastboot flash hyp hyp.mbn
fastboot flash devcfg devcfg.mbn
fastboot flash storsec storsec.mbn
fastboot flash bluetooth BTFM.bin
fastboot flash cmnlib cmnlib.mbn
fastboot flash cmnlib64 cmnlib64.mbn
fastboot flash modem NON-HLOS.bin
fastboot flash dsp dspso.bin
fastboot flash keymaster km4.mbn
fastboot flash logo logo.img
fastboot flash aop aop.mbn
fastboot flash qupfw qupv3fw.elf
fastboot flash imagefv imagefv.elf
fastboot flash uefisecapp uefi_sec.mbn
hope it helped and is not too late! (prob theres a faster way to do it)
manul said:
i have resolved it by downloading and extracting the older firmware EEA (Europe) V10.3.1.0.PFKEUXM from the site. Then in the folder firmware-update there are several partition files and you have to flash them via fastboot commands.
i.e. boot the device in fastboot mode (vol-down & pwr-btn).:
fastboot flash xbl xbl.elf
fastboot flash xbl_config xbl_config.elf
fastboot flash abl abl.elf
fastboot flash tz tz.mbn
fastboot flash hyp hyp.mbn
fastboot flash devcfg devcfg.mbn
fastboot flash storsec storsec.mbn
fastboot flash bluetooth BTFM.bin
fastboot flash cmnlib cmnlib.mbn
fastboot flash cmnlib64 cmnlib64.mbn
fastboot flash modem NON-HLOS.bin
fastboot flash dsp dspso.bin
fastboot flash keymaster km4.mbn
fastboot flash logo logo.img
fastboot flash aop aop.mbn
fastboot flash qupfw qupv3fw.elf
fastboot flash imagefv imagefv.elf
fastboot flash uefisecapp uefi_sec.mbn
hope it helped and is not too late! (prob theres a faster way to do it)
Click to expand...
Click to collapse
wow thats a lot! thanks!
That problem I have from 10.3.1.0 eea, when you want flash on k20pro model, it install sucessfull via twrp but stucks on mi logo. But I find that flashing twrp again after rom can enter twrp after some sec of stuck in twrp, just lock and unlock twrp( use latest unofficial).Then just flash k20p china firm and all good. Never been able to succesfully flash EEA global roms (mi 9t pro roms) via twrp. I do not want use miflash because dont want mess with data wipe. I am decrypted. I think some procces is missing via twrp.. sucessfully is via Mi flash (friends phone flashed)
Related
Strange, maybe I am missing something but not aware of what...
I've been on Revolution OS and as being curious I gave Android Q a try....means, I flashed "Q" successfully yesterday -through Mi flashing tool- but wasn't happy at all, therefore I went back to Global Dev (again via Mi Flashing tool) to reinstall Revoultion.....Regardless of which TWRP version I' am trying to flash, even after Fastboot is indicating a successful TWRP flash I am not able to access the Recovery. Trying to use adb reboot recovery ends-up in the stock recovery....also fastboot boot recovery.img dosn't help....
even trying to flash the TWRP version I used to install Revolution recerntly does not work.
flyingjack said:
Strange, maybe I am missing something but not aware of what...
I've been on Revolution OS and as being curious I gave Android Q a try....means, I flashed "Q" successfully yesterday -through Mi flashing tool- but wasn't happy at all, therefore I went back to Global Dev (again via Mi Flashing tool) to reinstall Revoultion.....Regardless of which TWRP version I' am trying to flash, even after Fastboot is indicating a successful TWRP flash I am not able to access the Recovery. Trying to use adb reboot recovery ends-up in the stock recovery....also fastboot boot recovery.img dosn't help....
even trying to flash the TWRP version I used to install Revolution recerntly does not work.
Click to expand...
Click to collapse
What I've found is normal commands to boot into recovery do not work for this phone. Boot into fastboot, flash recovery then use volume up and power combination to boot into recovery. Hopefully that will get you back in.
flyingjack said:
Strange, maybe I am missing something but not aware of what...
I've been on Revolution OS and as being curious I gave Android Q a try....means, I flashed "Q" successfully yesterday -through Mi flashing tool- but wasn't happy at all, therefore I went back to Global Dev (again via Mi Flashing tool) to reinstall Revoultion.....Regardless of which TWRP version I' am trying to flash, even after Fastboot is indicating a successful TWRP flash I am not able to access the Recovery. Trying to use adb reboot recovery ends-up in the stock recovery....also fastboot boot recovery.img dosn't help....
even trying to flash the TWRP version I used to install Revolution recerntly does not work.
Click to expand...
Click to collapse
I escaped from the FASTBOOT loop by flashing the FASTBOOT ROM using command.
ROM I used
cepheus_global_images_V10.2.6.0.PFAMIX_20190327.0000.00_9.0_global_9cc39b4570.tgz
The command I used
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash cache cache.img
fastboot flash cust cust.img
fastboot flash dtbo dtbo.img
fastboot flash dummy dummy.img
fastboot flash logo logo.img
fastboot flash metadata metadata.img
fastboot flash misc misc.img
fastboot flash persist persist.img
fastboot flash vbmeta vbmeta.img
fastboot flash vendor vendor.img
fastboot erase userdata
fastboot flash userdata userdata.img
fastboot reboot
Finally I found a TWRP version that is working (3.3.0-0423 by wzsx150 -thx mate!) and got back to Revolution OS!!
Thx also for your support!
somebody can tell me, what i need try more
i cant update rom(cn 2.27) and cant change it. all updates stucks at 25% with failure.
i try do that (flashing cn rom 2.27 from instructions)
fastboot oem nubia_unlock NUBIA_NX629J
fastboot flash parameter parameter.img
fastboot reboot
fastboot oem nubia_unlock NUBIA_NX629J
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash splash splash.img
fastboot flash modem NON-HLOS.bin
fastboot flash system system.img
fastboot reboot
lock and unlock bootloader
flashing twrp (device dont boot into twrp!)
i tried different roms (eu 2.07, cn 2.27, cn 2.30, us 1.11) all stucks on 25%
when i try update with system.new.dat (from 1.11) in last step i see that
sending sparse 'system' 5/5 (138492 KB)...
FAILED (data write failure (Unknown error))
finished. total time: 101.151s
Click to expand...
Click to collapse
update!
all done) by flashing fastboot flash boot, recovery, modem, splash from 2.30
Here is 1.11, unfortunately I dont have the original one saved, only the one I patched. It's rooted w/ magisk patch.
https://drive.google.com/open?id=11hEZ3W2GeyM2CfBhgaRBYGiSTTVnQqOK
Secretcow said:
Here is 1.11, unfortunately I dont have the original one saved, only the one I patched. It's rooted w/ magisk patch.
https://drive.google.com/open?id=11hEZ3W2GeyM2CfBhgaRBYGiSTTVnQqOK
Click to expand...
Click to collapse
i think need not patched boot, need system part system.img( but thanks
Rauh-Welt said:
i think need not patched boot, need system part system.img( but thanks
Click to expand...
Click to collapse
Woops you're 100% right. Sorry man, I need to go to sleep.
You can find the na global rom v1.11 here: http://rom.download.nubia.com/Europe&Asia/NX629/NX629J_Z69_EN_WPJ0O_V111.zip
Should be able to unzip and flash the system img.
Could you explain to me step by step how to solve it? please
Rauh-Welt said:
somebody can tell me, what i need try more
i cant update rom(cn 2.27) and cant change it. all updates stucks at 25% with failure.
i try do that (flashing cn rom 2.27 from instructions)
fastboot oem nubia_unlock NUBIA_NX629J
fastboot flash parameter parameter.img
fastboot reboot
fastboot oem nubia_unlock NUBIA_NX629J
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash splash splash.img
fastboot flash modem NON-HLOS.bin
fastboot flash system system.img
fastboot reboot
lock and unlock bootloader
flashing twrp (device dont boot into twrp!)
i tried different roms (eu 2.07, cn 2.27, cn 2.30, us 1.11) all stucks on 25%
when i try update with system.new.dat (from 1.11) in last step i see that
update!
all done) by flashing fastboot flash boot, recovery, modem, splash from 2.30
Click to expand...
Click to collapse
Could you explain to me step by step how to solve it? please
Things are changing with the advent of project treble and seamless updates. OnePlus will no longer release ROMs flashable via recovery (either stock) because is no more needed. The updates will be done on the slot not used for example if you are using slot a the update will be installed on slot b and the slot b will be set as default. If you brick and you are in bootloop how you can restore the rom? You can't with Stock ROM you have, because the zip can be only installed via Update Engine, so what can you do? Flash a stock rom via fastboot. I have extracted all images from the stock zip and i have made a new zip with the Fastboot ROM with a flash-all.bat included. This will work only if your bootloader is unlocked. This will erase all your data and will wipe your internal storage.
HOW TO FLASH
This version is only for not branded devices
Download the zip;
Unpack the zip in a folder;
Reboot the OnePlus 7T in fastboot-bootloader mode (Power and volume + and volume-);
Connect the OnePlus 7T to PC;
Run flash-all.bat flasher you need;
Wait until the process end;
The phone will automatically reboot.
DOWNLOAD
All roms on AFH: https://www.androidfilehost.com/?w=files&flid=301115
All roms on Sourceforge: https://sourceforge.net/projects/fastbootroms/files/OnePlus 7T Pro
BRANDED PHONE
For now branded device are not supported
MANUAL FLASH: Windows - OSX - Linux
If you want to manual flash these roms these are the commands (You need the latest sdk platform tools, you can find it here
Is reccomended to format data or the rom cannot boot:
Code:
fastboot -w
Others Commands to flash a fastboot rom
Code:
fastboot flash aop aop.img
fastboot flash aop aop.img
fastboot flash bluetooth bluetooth.img
fastboot flash boot boot.img
fastboot flash dsp dsp.img
fastboot flash dtbo dtbo.img
fastboot flash LOGO LOGO.img
fastboot flash modem modem.img
fastboot flash oem_stanvbk oem_stanvbk.img
fastboot flash qupfw qupfw.img
fastboot flash storsec storsec.img
fastboot flash multiimgoem multiimgoem.img
fastboot flash uefisecapp uefisecapp.img
fastboot flash recovery recovery.img
fastboot --disable-verity flash vbmeta vbmeta.img
fastboot --disable-verity flash vbmeta_system vbmeta_system.img
fastboot flash opproduct opproduct.img
fastboot reboot fastboot
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot flash product product.img
fastboot reboot
REMEMBER
"Invalid sparce file format at header magic" is not an error, you need to wait a bit when you see that string, just wait.
If the device automatically reboot in Stock Recovery mode don't reboot it and wait the flash end.
These ROMs can't be used to update or downgrade your phone but just to restore your phone.
If the rom seems doesn't start go in recovery stock and follow this guideline: English -> Wipe data and cache -> Erase everything.
If you want to rebrand your phone from HydrogenOS to OxygenOS you can follow this guide: Rebrand Guide
If you want you can use also my tool to flash Factory Images, unlock bootloader, flash twrp or to understand if the device is recognized: https://toolaio.tk/
If you got some problems like write error or no partition, check this: https://forum.xda-developers.com/showpost.php?p=76658555&postcount=34
DONATE LINK
If you want to support this and others my projects please consider making a donation, thanks.
sorry im new to oneplus , i buy op7t pro come in 2 day , what the mean branded and non branded ?
sorry sir , not clear about Branded phones
China version have flash this rom ?
akino553 said:
sorry im new to oneplus , i buy op7t pro come in 2 day , what the mean branded and non branded ?
Click to expand...
Click to collapse
If you buy it from like Verizon or T-Mobile.
nyzoli72 said:
If you buy it from like Verizon or T-Mobile.
Click to expand...
Click to collapse
mmmm ok thank you but I bought it from China so I don't know about that
Things sure really changing with Android, everything seems more complicated last time I rooted an OnePlus phone. So I appreciate this effort by you.
Sent from my OnePlus7TPro using XDA Labs
Lossyx said:
Things sure really changing with Android, everything seems more complicated last time I rooted an OnePlus phone. So I appreciate this effort by you.
Sent from my OnePlus7TPro using XDA Labs
Click to expand...
Click to collapse
The script will ask if you want to format data or not
Is twrp available for oneplus 7t pro?
adamo86 said:
Is twrp available for oneplus 7t pro?
Click to expand...
Click to collapse
https://forum.xda-developers.com/7t-pro/development/recovery-unofficial-twrp-recovery-t3989333
mauronofrio said:
The script will ask if you want to format data or not
Click to expand...
Click to collapse
Hello! Can I flash this ROM to change from Hydrogen OS to Oxygen OS as per instruction "Rebrand guide"? Because on official website Oxygen OS ROM is not available for 7T Pro!
Can you (or anyone) post the oxygenOS build zip which I can flash via updater?
Right now I'm on hydrogen OS and want to move to OxygenOS by official means.
One+Nexus said:
Hello! Can I flash this ROM to change from Hydrogen OS to Oxygen OS as per instruction "Rebrand guide"? Because on official website Oxygen OS ROM is not available for 7T Pro!
Click to expand...
Click to collapse
You can try
mauronofrio said:
You can try
Click to expand...
Click to collapse
I don't know what to do.. already 1 week on hand with Hydrogen OS... What can I expect bad if I try?
How do you go back to stock rom if there are no stock rom available for 7t pro
One+Nexus said:
Hello! Can I flash this ROM to change from Hydrogen OS to Oxygen OS as per instruction "Rebrand guide"? Because on official website Oxygen OS ROM is not available for 7T Pro!
Click to expand...
Click to collapse
Cannot. I have tried and got fastboot bootloop.
Writing 'system' FAILED (remote: 'Partition not found')
mhammadleo said:
Writing 'system' FAILED (remote: 'Partition not found')
Click to expand...
Click to collapse
When the device reboots in recovery doesn't touch it
Silly question after returning to stock, I've tried to relock the bootloader and get a device corrupt won't boot message and the phone then turns off. How do I relock without this happening.
Wooot. Ok guys, i came from 5T and Root,TRWP and flash stock ROM was easy. Where do i have to begin, anyone can give me structured process of ROOT,TWRP?or FASTBOOT and ROM?
I had an issue earlier and begged support for the stock firmware, they sent me https://drive.google.com/open?id=171cVS9ku7rHF74Gyl1VGP3jQXAFwWDpl
The OnePlus 7 Pro is now officially EOL, which means going forward new vulnerabilities found in the firmware stay unpatched.
I present to you Android 11/12 firmware collection, to be flashed within fastbootd mode. For that you need a compatible recovery and your device needs to be unlocked.
For example the official Lineage OS recovery supports fastbootd.
Instructions using Lineage OS recovery (copied from the official Lineage OS Wiki)
1. Boot up LineageOS recovery (fastboot boot recovery.img)
2. Go to “Advanced” -> “Enter fastboot” (you will notice that the recovery switches to an orange color)
3. Connect your phone with your pc and execute the following commands:
Code:
fastboot flash --slot=all abl abl.img
fastboot flash --slot=all aop aop.img
fastboot flash --slot=all bluetooth bluetooth.img
fastboot flash --slot=all cmnlib64 cmnlib64.img
fastboot flash --slot=all cmnlib cmnlib.img
fastboot flash --slot=all devcfg devcfg.img
fastboot flash --slot=all dsp dsp.img
fastboot flash --slot=all hyp hyp.img
fastboot flash --slot=all keymaster keymaster.img
fastboot flash --slot=all LOGO LOGO.img
fastboot flash --slot=all modem modem.img
fastboot flash --slot=all oem_stanvbk oem_stanvbk.img
fastboot flash --slot=all qupfw qupfw.img
fastboot flash --slot=all storsec storsec.img
fastboot flash --slot=all tz tz.img
fastboot flash --slot=all xbl_config xbl_config.img
fastboot flash --slot=all xbl xbl.img
fastboot reboot
Downloads (Global and Europe versions):
Dropbox
Mega
Happy flashing!
11.0.1.1 global firmware added
Edit: Europe firmware now uploaded.
hi there,
hopefully u can help. i started this in windows powershell in the order where the .img files are
fastboot flash --slot=all abl abl.img
but get always error. unknow option -- slot=all
any idea what do i wrong??
thanks
Sirloc said:
hi there,
hopefully u can help. i started this in windows powershell in the order where the .img files are
fastboot flash --slot=all abl abl.img
but get always error. unknow option -- slot=all
any idea what do i wrong??
thanks
Click to expand...
Click to collapse
make sure you use the latest fastboot, which can be downloaded here: https://developer.android.com/studio/releases/platform-tools
And make sure you are in fastbootd mode.
11.0.2.1 global and europe firmware added
Using locked BL with Pixel Experience. Cannot flash from fastboot because "Download is not allowed on locked devices", but that's the way to upgrade firmware so.... Any suggestions?
Maybe a flashable zip just for flashing this from recovery?
jknvv13 said:
Using locked BL with Pixel Experience. Cannot flash from fastboot because "Download is not allowed on locked devices", but that's the way to upgrade firmware so.... Any suggestions?
Maybe a flashable zip just for flashing this from recovery?
Click to expand...
Click to collapse
sorry, you can't flash firmware from regular fastboot. you need to be in fastbootd mode. the official lineage os recovery supports it for example
hellcat50 said:
sorry, you can't flash firmware from regular fastboot. you need to be in fastbootd mode. the official lineage os recovery supports it for example
Click to expand...
Click to collapse
Actually using fastbootd with Pixel Recovery. But locked BL is the issue.
jknvv13 said:
Actually using fastbootd with Pixel Recovery. But locked BL is the issue.
Click to expand...
Click to collapse
oh sorry my bad. i'll update my thread accordingly and gl with fixing your problem
hellcat50 said:
oh sorry my bad. i'll update my thread accordingly and gl with fixing your problem
Click to expand...
Click to collapse
Correct me if I'm wrong but...
A flashable zip would work under Pixel/Lineage/Modified recovery.
Because AFAIK the problem is when you modify system files, but not the other partitions that store the fw parts.
jknvv13 said:
Correct me if I'm wrong but...
A flashable zip would work under Pixel/Lineage/Modified recovery.
Because AFAIK the problem is when you modify system files, but not the other partitions that store the fw parts.
Click to expand...
Click to collapse
i suggest you ask the rom developer on how to update the firmware with a locked bootloader
11.0.3.1 global firmware added
11.0.3.1 europe firmware added
This is the 4th option I have tried and it doesn't work. I'm on unlocked OP 7Pro; it was already on Android 11 when I got it so I can't install TWRP. I was able to root and install LOS 18.1. I haven't been able to install any other ROMs. I can't even go back to stock now.... What am I missing?
I have already installed the latest drivers, software, etc. Most guides are for Android 10 which makes this more difficult but even the more recent guides fail to do anything except cause an occasional bootloop if they even do anything at all.
MrAwesome75 said:
This is the 4th option I have tried and it doesn't work. I'm on unlocked OP 7Pro; it was already on Android 11 when I got it so I can't install TWRP. I was able to root and install LOS 18.1. I haven't been able to install any other ROMs. I can't even go back to stock now.... What am I missing?
I have already installed the latest drivers, software, etc. Most guides are for Android 10 which makes this more difficult but even the more recent guides fail to do anything except cause an occasional bootloop if they even do anything at all.
Click to expand...
Click to collapse
Hi, I have only had my op7p for a little over a week and mine was a11 but I as able to install twrp many many times , There are several good xda posts that helped me tremendously including a functional msm tool
[RECOVERY] [12] [OFFICIAL] TeamWin Recovery Project
Introduction: Team Win Recovery Project or TWRP for short, is a custom recovery built with ease of use and customization in mind. We started from the ground up by taking AOSP recovery and loading it with the standard recovery options, then added...
forum.xda-developers.com
[MSM Tool] Guac for All
To everyone who donated, I love y'all. This took a really long time to get lol but it's straight from support and I did not make any modifications to it; I hope it helps a lot of people. The revision is listed in the archive, I believe it's...
forum.xda-developers.com
Just trying to help, Sorry if you tried both of these before.
Eu estava com a OOS 11.0.3.1 no meu OP7P porém resolvi instalar a custom ROM dotos. Infelizmente não gostei muito do resultado e gostaria de voltar a stock. Já tentei esse tutorial entre outros que voltam para a oxygen 10 mas nenhum deu certo. Poderia me ajudar
11.0.4.1 europe and global firmware added
Sir Hopefull For Reply
I'm a little confuse here
- Theres no system img file in the zip file
- what if I am on custom rom and have fastbootd recovery can I direct flash 11.0.4.1 these files?
- or is it for only update
Thanks
Tnbh9 said:
Sir Hopefull For Reply
I'm a little confuse here
- Theres no system img file in the zip file
- what if I am on custom rom and have fastbootd recovery can I direct flash 11.0.4.1 these files?
- or is it for only update
Thanks
Click to expand...
Click to collapse
it's intented to be used to update your firmware while you are running custom roms like lineage os
11.0.5.1 global and europe firmware added
Hi,
First of all, I hope this is the correct place to ask for help. I didn't see a better place
I own a honor 9 lite phone. I opened bootloader using PotatoNV and testpoints. Everything worked like a charm
But yesterdayy I tried to update it to Treble and after flashing a rom, I faced this error just after restarting the phone:
ERROR MODE
Attention!
Please update system again
Error!
Func NO : 15 (bl31 image)
Func NO : 1 (security verify failed!)
And it keeps restarting all the time
I tried to flash system image from multiple roms, even stock. Also I tried to flash multiple recovery images, boot images, and so on.. but nothing seems to work
The only way I can use thee phone is via fastboot. NO TWRP and no OFFICIAL RECOVERY using Vol+ and Vol-
Please, I need you help
Thank you in advance
Regards
oloco2 said:
Hi,
First of all, I hope this is the correct place to ask for help. I didn't see a better place
I own a honor 9 lite phone. I opened bootloader using PotatoNV and testpoints. Everything worked like a charm
But yesterdayy I tried to update it to Treble and after flashing a rom, I faced this error just after restarting the phone:
ERROR MODE
Attention!
Please update system again
Error!
Func NO : 15 (bl31 image)
Func NO : 1 (security verify failed!)
And it keeps restarting all the time
I tried to flash system image from multiple roms, even stock. Also I tried to flash multiple recovery images, boot images, and so on.. but nothing seems to work
The only way I can use thee phone is via fastboot. NO TWRP and no OFFICIAL RECOVERY using Vol+ and Vol-
Please, I need you help
Thank you in advance
Regards
Click to expand...
Click to collapse
Hi,
in fastboot mode run commands :
fastboot oem get-build-number
fastboot oem get-product-model
fastboot getvar vendorcountry
fastboot oem oeminforead-CUSTOM_VERSION
fastboot oem oeminforead-SYSTEM_VERSION
and post the results.
Some might fail, so don't worry about it.
Try something from the following:
A) in fastboot mode use command
fastboot erase userdata
reboot and try to flash stock recovery_ramdisk and flash full stock FW via dload
B) try to update your phone via eRecovery - turn off, plug the cabel and press and hold Power + Vol Up. In eRecovery's menu select "Download latest etc etc."
C) fully discharge the battery and try previous methods
(in your case little chance, this method works with error 11/2, you have 15/1)
D) use testpoint method
E) paid services (dc-phoenix etc.)
Thank so much for your help -Alf-
Unfortunally I have to say that now my phone is not able to enter fastboot mode.
What I dd:
The comands you asked for:
fastboot oem get-build-number
(bootloader) :System 8.0.0.046(0JRE)
OKAY [ 0.007s]
Finished. Total time: 0.009s
fastboot oem get-product-model
(bootloader)
OKAY [ 0.006s]
Finished. Total time: 0.009s
fastboot getvar vendorcountry
vendorcountry: hw/eu
fastboot oem oeminforead-CUSTOM_VERSION
FAILED (remote: 'The reason of failed input oem_nv_item error!')
fastboot: error: Command failed
fastboot oem oeminforead-SYSTEM_VERSION
(bootloader) :STF-L09C10B100a
OKAY [ 0.008s]
Finished. Total time: 0.009s
As nothing changed, I used testpoints.
I had to enter fastboot oem unlock 5KKK7... in order to unlock bootloader again
But now.. Phone keeps rebooting with the same eror window as before, but I'm still unable to ener not fastboot mode not erecovery.
Now i really feel locked, as I think there's nothin else I can do.
I also unplugged battery multiple times in order to discharge all the circuit, but no news...
Any other idea, please?
Regards
oloco2 said:
Unfortunally I have to say that now my phone is not able to enter fastboot mode
Click to expand...
Click to collapse
oloco2 said:
The only way I can use thee phone is via fastboot.
Click to expand...
Click to collapse
?
Before using potatonv I was able to enter fastoot mode and perform some commands.
Now, after using it, the phone just keeps rebooting showing the errors, but even if I press the buttons, no fastboot/twrp mode...
oloco2 said:
Before using potatonv I was able to enter fastoot mode and perform some commands.
Now, after using it, the phone just keeps rebooting showing the errors, but even if I press the buttons, no fastboot/twrp mode...
Click to expand...
Click to collapse
Try this method - turn off, hold Volume Down and plug the cabel.
oloco2 said:
System 8.0.0.046(0JRE
Click to expand...
Click to collapse
oloco2 said:
fastboot oem get-product-model
(bootloader)
OKAY [ 0.006s]
Click to expand...
Click to collapse
oloco2 said:
failed input oem_nv_item error
Click to expand...
Click to collapse
oloco2 said:
SYSTEM_VERSION
(bootloader) :STF-L09C10B100a
Click to expand...
Click to collapse
Testpoint or dc-phoenix, bro.
-Alf- said:
Testpoint or dc-phoenix, bro.
Click to expand...
Click to collapse
I posted in the previous post that I already used testpoint using potatonv.
I only used testpoint in order to unlock bootloader, and today I used it via potatonv because you seggested it but.... is there any other use I could give to testpoint other than unlocking bootloader? Something that couldhelp in this situation?
Regards
oloco2 said:
I posted in the previous post that I already used testpoint using potatonv.
I only used testpoint in order to unlock bootloader, and today I used it via potatonv because you seggested it but.... is there any other use I could give to testpoint other than unlocking bootloader? Something that couldhelp in this situation?
Regards
Click to expand...
Click to collapse
You have to flash board software using testpoint . Google it, I have no experience with that.
Ok. Thank you -Alf-. I will have a look to google.
But in the meanwhile, if someone else coukd help me a little bit, will be more than welcome
Regards!!
Hi -Alf-
I got good news for me. I got fastboot working again. I need to use potatonv in order to get it, but anywayI think it's good news.
Please, any other idea in order to make it come back, please?
Thank you
oloco2 said:
any other idea in order to make it come back,
Click to expand...
Click to collapse
your phone has an incomplete FW (System 8.0.0.046 (0JRE)),, an unknown model and a problem with oeminfo. Do you even read what I'm writing???
https://forum.xda-developers.com/t/...-security-verify-failed.4453855/post-86982695
Yes I read.
You told me to use testpoint or DC after telling you that I was unable to enter fastmode, but now I'm able to enter again. That's why I asked you for help again, because maybe using fastboot you were able to tell me any other way to test.
Regards
oloco2 said:
Yes I read.
You told me to use testpoint or DC after telling you that I was unable to enter fastmode, but now I'm able to enter again. That's why I asked you for help again, because maybe using fastboot you were able to tell me any other way to test.
Regards
Click to expand...
Click to collapse
https://forum.xda-developers.com/t/i-bricked-my-honor-9-lite.3799176/post-76943641
Hey -Alf- !
I can ay that finally I got it working.
How I did it:
I got a full firmware for my devce and using Huawei Update extractor I extracted all the images to a folder.
Using a little script un batch I createda .txt with multiple lines:
fastboot flash cache cache.img
fastboot flash crc crc.img
fastboot flash curver curver.img
fastboot flash cust cust.img
fastboot flash dts dts.img
fastboot flash eng_system eng_system.img
fastboot flash eng_vendor eng_vendor.img
fastboot flash erecovery_kernel erecovery_kerne.img
fastboot flash erecovery_ramdis erecovery_ramdi.img
fastboot flash erecovery_vbmet erecovery_vbmet.img
fastboot flash erecovery_vendor erecovery_vendo.img
fastboot flash fastboot fastboot.img
fastboot flash fw_hifi fw_hifi.img
fastboot flash fw_lpm3 fw_lpm3.img
fastboot flash hisiufs_gpt hisiufs_gpt.img
fastboot flash boot kernel.img
fastboot flash modemnvm_update modemnvm_update.img
fastboot flash modem_fw modem_fw.img
fastboot flash odm odm.img
fastboot flash package_type.img package_type.img
fastboot flash patch patch.img
fastboot flash preas preas.img
fastboot flash preavs preavs.img
fastboot flash preload preload.img
fastboot flash product product.img
fastboot flash recovery_ramdisk recovery_ramdis.img
fastboot flash recovery_vbmeta recovery_vbmeta.img
fastboot flash recovery_vendor recovery_vendor.img
fastboot flash sensorhub sensorhub.img
fastboot flash sha256rsa sha256rsa.img
fastboot flash system system.img
fastboot flash teeos teeos.img
fastboot flash trustfirmware trustfirmware.img
fastboot flash userdata userdata.img
fastboot flash vbmeta vbmeta.img
fastboot flash vendor vendor.img
fastboot flash verlist verlist.img
fastboot flash version version.img
fastboot flash xloader xloader.img
And I run all the commands.
Some of them gave me some errors like partition lenght or something like that, but at the end, once rebooted, the error was gone.
Then, I updated all the firmware usong dload.
Now I'm facing a little error about oeminfo. I think itis due to the fact that the firmware I used was rusian, and my phone is from EU. I already created another thread in this forum.
I want to thank you for your tme and your ideas.
I hope this post can help someone over there with an error like mine.
Thank you very much for your time and help
Regards
No problem. Btw, why russian FW? I gave you a link with EU FW . Okay, your choice...
oloco2 said:
Now I'm facing a little error about oeminfo
Click to expand...
Click to collapse
Little?
Yes, The russian FW I flashed was yeterday. Now, after you replied to my post, I will try to upgrade FW to the EU version. I hope now everything works as it should
The "litle error" about oeminfo is:
"/preas/xxx" in some parts of the settings. I read somewhere it was due to oeminfo.I'm I wrong?
Thank you!!
I have already tried to fix the /preas/xxx "little error", but it didn't work
After flashing the EU version of lld-l31, I tested it and it seems to be showing the same error in "Compilation Number", in About
lso, in Model it says "unknow". I thing this is why when I tried to find a new OTA version, it didn't find anyone, even if using android 8
Any idea to fix "/preas/xxx"?
Thank you ad regards!!
All fixed!!
I found this oeminfo:
OEMinfo & Dump & CERT Honor 9 Lite (LLD-ALL)
OEMinfo & Dump & CERT Honor 9 Lite (LLD-AL00 / LLD-AL10 / LLD-AL20 / LLD-AL30 / LLD-TL00 / LLD-TL10 / LLD-L21 / LLD-L22 / LLD-L31 / LLD-L32 / LLD-L42). Share File Certificate, File Dump, OE…
azrom.net
After updating it, all info seems to be correct in about. Also, there's a new OTA for me!
What a road gave me this phone
I hope I'mnot comming back to here in a while
Thank you for all your help
Regards!!!
oloco2 said:
I have already tried to fix the /preas/xxx "little error", but it didn't work
After flashing the EU version of lld-l31, I tested it and it seems to be showing the same error in "Compilation Number", in About
lso, in Model it says "unknow". I thing this is why when I tried to find a new OTA version, it didn't find anyone, even if using android 8
Any idea to fix "/preas/xxx"?
Thank you ad regards!!
Click to expand...
Click to collapse
Kindly share your batch script, pls