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
Related
[ROM][STOCK] Deodex Bases for Rom Development
Standard Disclaimer:
I am not responsible for anything that may happen to your device.
I have created a stock deodex bases, based on the latest releases every month, to flash as a standalone rom in twrp, or use as a base for custom roms. it is COMPLETELY STOCK, NO ROOT
Prerequisites:
An Essential Phone
Working adb/fastboot binaries, and drivers.
Bootloader unlocked and critical unlocked (Just like the BTS)
Working TWRP
Installation Instructions
1. Make sure your running the correct firmware for the release PRIOR to flashing. Make sure you have touch in TWRP prior
2. Boot to TWRP.
3. Flash the zip
4. Reboot.
This is a free-for-all zip, meaning i dont care if you modify it, pass it off to other groups, help anybody else, etc. Im NOT liable for any brickery, trickery, thickery, or otherwise.
Thanks:
@SuperR. - superr kitchen @invisiblek - knowledge @Dees_Troy - Official TWRP
Links
PPR1.181005.076 AFH (Deodex November)
PPR1.181005.034 AFH (Deodex October)
My collection of BTS (Back to stock) zips. Mine wipe everything twice, and flash both slots. They include current working adb/fastboot binaries as well as a cmd prompt tool.
https://www.androidfilehost.com/?w=files&flid=228895
Enjoy
XDA:DevDB Information
Deodexed Stock System/Vendor Images, ROM for the Essential Phone
Source Code: [url]https://github.com/EssentialOpenSource[/URL]
ROM OS Version: 9.x Oreo
ROM Kernel: Linux 4.4.x
ROM Firmware Required: PPR1.180905.036 Firmware
Based On: AOSP
Version Information
Status: Stable
Created 2018-03-28
Last Updated 2018-11-06
XDA:DevDB Information
[ROM][STOCK] Deodex Bases for Rom Development, ROM for the Essential Phone
Contributors
63c
ROM OS Version: 9.x Pie
Version Information
Status: Testing
Created 2019-02-03
Last Updated 2019-02-03
mine
also mine
Nice to see excellent development going on. Thanks for bringing this to us!
Bootloader need to be unlocked? Mine bricked I can't unlock again nor booting recovery.
hussaination01 said:
Bootloader need to be unlocked? Mine bricked I can't unlock again nor booting recovery.
Click to expand...
Click to collapse
It's just like the back to stocks. Same rules apply. Did you turn off OEM unlock
aer0zer0 said:
It's just like the back to stocks. Same rules apply. Did you turn off OEM unlock
Click to expand...
Click to collapse
Yes by mistake. Now it's been 2 month not working. I can't do anything. It's just bricked.
hussaination01 said:
Yes by mistake. Now it's been 2 month not working. I can't do anything. It's just bricked.
Click to expand...
Click to collapse
oh ohhhh....... OK got ya,
No, this wont help, im not sure will ever get anything from essential at this point that will fix it. Send it in for repair.
Any advantage to flashing deodex vs keeping stock odexed ?
Sent from my PH-1 using XDA Labs
avd said:
Any advantage to flashing deodex vs keeping stock odexed ?
Click to expand...
Click to collapse
In theory, it would allow for better theming and easier ability to hardcode mods
OP updated with new deodex BTS for .141, as well as my collection of regular odexed back to stocks. Enjoy
OP updated with new deodex BTS for .166, enjoy
OP updated with new deodex BTS for .234
Enjoy
aer0zer0 said:
OP updated with new deodex BTS for .234
Enjoy
Click to expand...
Click to collapse
Thank you for your contribution. I was wondering. I run stock, rooted, elemental X .234. it themes pretty well. Will it have better theming capabilities with the deodex rom? I know it said that deodex is better for theming and customizing but theme developers do such a good job theming Google apps as it is with some limitations like battery icons and such. So I was wondering if deodex would give it the capability. Thank you again.
tomzefi said:
Thank you for your contribution. I was wondering. I run stock, rooted, elemental X .234. it themes pretty well. Will it have better theming capabilities with the deodex rom? I know it said that deodex is better for theming and customizing but theme developers do such a good job theming Google apps as it is with some limitations like battery icons and such. So I was wondering if deodex would give it the capability. Thank you again.
Click to expand...
Click to collapse
It should, I'm not much of a theme tho. You tell me
Updated for July OTA
avd said:
Any advantage to flashing deodex vs keeping stock odexed ?
Sent from my PH-1 using XDA Labs
Click to expand...
Click to collapse
aer0zer0 said:
In theory, it would allow for better theming and easier ability to hardcode mods
Click to expand...
Click to collapse
You left out the best part -- Signature Spoofing! microG!
Mine wipe everything twice, and flash both slots, yeah baby!
What are all these differences for compared to Essential's Fastboot Oreo which doesn't have these?
fastboot flash devcfg_a devcfg
fastboot flash devcfg_b devcfg
fastboot flash hyp_a hyp
fastboot flash hyp_b hyp
fastboot flash keymaster_a keymaster
fastboot flash keymaster_b keymaster
fastboot flash mdtp_a mdtp
fastboot flash mdtp_b mdtp
fastboot flash mdtpsecapp_a mdtpsecapp
fastboot flash mdtpsecapp_b mdtpsecapp
fastboot flash pmic_a pmic
fastboot flash pmic_b pmic
fastboot flash rpm_a rpm
fastboot flash rpm_b rpm
fastboot flash xbl_a xbl
fastboot flash xbl_b xbl
THANKS
DoR3M3 said:
You left out the best part -- Signature Spoofing! microG!
Mine wipe everything twice, and flash both slots, yeah baby!
What are all these differences for compared to Essential's Fastboot Oreo which doesn't have these?
fastboot flash devcfg_a devcfg
fastboot flash devcfg_b devcfg
fastboot flash hyp_a hyp
fastboot flash hyp_b hyp
fastboot flash keymaster_a keymaster
fastboot flash keymaster_b keymaster
fastboot flash mdtp_a mdtp
fastboot flash mdtp_b mdtp
fastboot flash mdtpsecapp_a mdtpsecapp
fastboot flash mdtpsecapp_b mdtpsecapp
fastboot flash pmic_a pmic
fastboot flash pmic_b pmic
fastboot flash rpm_a rpm
fastboot flash rpm_b rpm
fastboot flash xbl_a xbl
fastboot flash xbl_b xbl
THANKS
Click to expand...
Click to collapse
It's a full BTS, like the BTS thread. All you need are system, boot, vendor really.
Boot, vendor, modem, bluetooth, these are pretty self explanatory, I was hoping you could explain so the end-users besides myself understood what each of these others are?
Essential doesn't have these in their Fastboot ROM, so I was trying to understand why these are in these ROMS, and the differences?
So if you could give a break down on each, that would be great.
devcfg?
hyp?
keymaster?
mdtp?
mdtpsecapp?
pmic
rpm? - hmm rpm package management? As in rpm archives? http://rpm.org/
xbl?
Thanks
DoR3M3 said:
Boot, vendor, modem, bluetooth, these are pretty self explanatory, I was hoping you could explain so the end-users besides myself understood what each of these others are?
Essential doesn't have these in their Fastboot ROM, so I was trying to understand why these are in these ROMS, and the differences?
So if you could give a break down on each, that would be great.
devcfg?
hyp?
keymaster?
mdtp?
mdtpsecapp?
pmic
rpm? - hmm rpm package management? As in rpm archives? http://rpm.org/
xbl?
Thanks
Click to expand...
Click to collapse
Lol, Google-fu...
I had installed the latest January patch on my stock ROM Moto One Power XT1942, and after rooting and tinkering, I accidentally put my phone in a bootloop. I tried to get hold of a stock ROM image but I only found ROMs with November patch, and comments warning me to not downgrade. So what do I do? Can anyone provide me with a January updated stock ROM?
If your phone is defined in the device manager as COM port 9008, you can restore it according to this instruction.
https://forum.xda-developers.com/moto-z/how-to/guide-how-to-unbrick-moto-z-hardbricked-t3590133
The file 'blank-flash.bat' can be taken in the folder "mbm-ci", the cat will be in the unpacked firmware.
https://mirrors.lolinet.com/firmware/moto/chef/official/RETAIL/fastboot_chef_oem_user_9_PPT29.74-25_64be_release-keys-cid50_oem.tar.gz
After installing this file, the phone will be able to boot into fastboot.
After that, you can restore the phone by flashing the same downloaded firmware using the method described here.
https://web.telegram.org/#/[email protected]
[1:27:03 PM]
smyaknti.tar.gz
:
admin
Set your device in fastboot mode do the following and skip the
fastboot -w
step if you don't want to format everything :
fastboot oem fb_mode_set
fastboot -w
fastboot flash bootloader bootloader.img
fastboot flash partition gpt.bin
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash bluetooth BTFM.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
(If you have more or less sparsechunk files then continue or terminate beforehand accorfingly)
fastboot flash system_b system_other.img
fastboot flash vendor vendor.img
fastboot flash oem oem.img
fastboot oem fb_mode_clear
fastboot reboot
Just yesterday, I so restored my phone from a brick, obtained after installing an unofficial TWRP and firmware RR.
Good luck.
https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
This is the January Patch Stock ROM
NitrodiumSK said:
I had installed the latest January patch on my stock ROM Moto One Power XT1942, and after rooting and tinkering, I accidentally put my phone in a bootloop. I tried to get hold of a stock ROM image but I only found ROMs with November patch, and comments warning me to not downgrade. So what do I do? Can anyone provide me with a January updated stock ROM?
Click to expand...
Click to collapse
You did not "Brick" your device per se. Probably some improper file was flashed. If you have not wiped your phone, you can just simple try to fastboot flash the stock boot image. It may solve the issue. If not then do a clean flash to either the stock ROM or any custom ROM from this AFH link.
Note that the Custom ROMs are still in beta due to a VoLTE issue and thus are not released on XDA Dev DB yet. They are safe to flash though and are stable if you do not need VoLTE.
You can also ask for more help at the official telegram channel for the device.
smyaknti said:
You did not "Brick" your device per se. Probably some improper file was flashed. If you have not wiped your phone, you can just simple try to fastboot flash the stock boot image. It may solve the issue. If not then do a clean flash to either the stock ROM or any custom ROM from this AFH link.
Note that the Custom ROMs are still in beta due to a VoLTE issue and thus are not released on XDA Dev DB yet. They are safe to flash though and are stable if you do not need VoLTE.
You can also ask for more help at the official telegram channel for the device.
Click to expand...
Click to collapse
I thank you very much for your help. I was able to successfully flash the stock firmware from the link you provided. I only have a small question. The stock ROM zip, is it updated after every security patch OTA update?
NitrodiumSK said:
I thank you very much for your help. I was able to successfully flash the stock firmware from the link you provided. I only have a small question. The stock ROM zip, is it updated after every security patch OTA update?
Click to expand...
Click to collapse
Yes, the complete firmware file is different with every new build released. You can install OTA with the current fastboot flashed stock ROM but provided it has to be "FULLY STOCK". Else the update will fail.
smyaknti said:
Yes, the complete firmware file is different with every new build released. You can install OTA with the current fastboot flashed stock ROM but provided it has to be "FULLY STOCK". Else the update will fail.
Click to expand...
Click to collapse
Alright gotcha! Thanks a lot for your help
Hello dear Mates!
I purchased a cellphone yesterday Motorola Power One. its working fine, but I want to ask n know two things,
1. It has unlocked "bootloader" and on all restart it says to relock it to secure it. If I relock it, will still work or stop working?
2. It has Android 8.1.0 SKU XT1942-1 BUILD NUMBER OPT28.81-45 When I click update it shows Your Device is up-to-date
Android version 8.1.0
Current Version OPT28.81-45
Security Patch level September 1, 2018
But today I saw this update
XT1942-2_CHEF_RETAIL_9.0_PPTS29.74-29-2_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
I want to know can I update this version and how to?
Please help me as quickly as possible
Thanks and regards
azhar
No issue downgrade
You can downgrade one power there is no issue of you downgrade it don't worry
NitrodiumSK said:
I had installed the latest January patch on my stock ROM Moto One Power XT1942, and after rooting and tinkering, I accidentally put my phone in a bootloop. I tried to get hold of a stock ROM image but I only found ROMs with November patch, and comments warning me to not downgrade. So what do I do? Can anyone provide me with a January updated stock ROM?
Click to expand...
Click to collapse
Any how can anybody provide stock rom oem fastboot mode with March update???
azhar63 said:
Hello dear Mates!
I purchased a cellphone yesterday Motorola Power One. its working fine, but I want to ask n know two things,
1. It has unlocked "bootloader" and on all restart it says to relock it to secure it. If I relock it, will still work or stop working?
2. It has Android 8.1.0 SKU XT1942-1 BUILD NUMBER OPT28.81-45 When I click update it shows Your Device is up-to-date
Android version 8.1.0
Current Version OPT28.81-45
Security Patch level September 1, 2018
But today I saw this update
XT1942-2_CHEF_RETAIL_9.0_PPTS29.74-29-2_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
I want to know can I update this version and how to?
Please help me as quickly as possible
Thanks and regards
azhar
Click to expand...
Click to collapse
Yeah bro flash this room via fastboot commands
motorola one power
my moto one power starts freezing and when i restart its touch stop working....i flashed stock rom using twrp but still same problem and also try to flash rom using fastboot but still its system ui not responding and phone freezes and touch not working after reboot...please help please!!!:crying:
aum25 said:
Yeah bro flash this room via fastboot commands
Click to expand...
Click to collapse
Did you flash that rom in 1942- 1 ??? I have the same model num and running oreo... Want to update pie??? Were you successful in doing that ? Because that firmware file was for 1942-2 ? Plz share experience.
rudranshrajput said:
my moto one power starts freezing and when i restart its touch stop working....i flashed stock rom using twrp but still same problem and also try to flash rom using fastboot but still its system ui not responding and phone freezes and touch not working after reboot...please help please!!!:crying:
Click to expand...
Click to collapse
Did you install any third party app or it happens by itself? I had the same problem but i was messing around with the moto app launcher. Anyhow, try flashing this stock rom with latest june security patch. Don't use TWRP, it is a full rom. Use Fastboot mode. Also backup your device, if you want your files back. This will do a clean install of the rom.
Here is the link: https://drive.google.com/file/d/1lLmDvX4R4o2Jqrhp1RQflap27jxe4hXS/view
Steps:
1) Boot your device into fastboot mode
2) Open flashall.bat and wait for flashing
3) Reboot
colorist said:
If your phone is defined in the device manager as COM port 9008, you can restore it according to this instruction.
https://forum.xda-developers.com/moto-z/how-to/guide-how-to-unbrick-moto-z-hardbricked-t3590133
The file 'blank-flash.bat' can be taken in the folder "mbm-ci", the cat will be in the unpacked firmware.
https://mirrors.lolinet.com/firmware/moto/chef/official/RETAIL/fastboot_chef_oem_user_9_PPT29.74-25_64be_release-keys-cid50_oem.tar.gz
After installing this file, the phone will be able to boot into fastboot.
After that, you can restore the phone by flashing the same downloaded firmware using the method described here.
https://web.telegram.org/#/[email protected]
[1:27:03 PM]
smyaknti.tar.gz
:
admin
Set your device in fastboot mode do the following and skip the
fastboot -w
step if you don't want to format everything :
fastboot oem fb_mode_set
fastboot -w
fastboot flash bootloader bootloader.img
fastboot flash partition gpt.bin
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash bluetooth BTFM.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
(If you have more or less sparsechunk files then continue or terminate beforehand accorfingly)
fastboot flash system_b system_other.img
fastboot flash vendor vendor.img
fastboot flash oem oem.img
fastboot oem fb_mode_clear
fastboot reboot
Just yesterday, I so restored my phone from a brick, obtained after installing an unofficial TWRP and firmware RR.
Good luck.
Click to expand...
Click to collapse
thanks by you my device just boot up in fastboot mod
thank you very much
best regard
Need help with phone bricked.
I was installing the Arrows OS in Motorola one power and after rebooting, the set is in the bricked mode now it's not responding to anything. Can anyone please guide how can I fix it?
I got similar problem.when I'm flashing arrows or others custom ROMs(1custom ROM,2twrp installer)and restart my phone no restarting only bricked.help only blankflash
Phone bricked after installing arrow is on p30 note xt1942-1
I tried the blankflash method but not working, I'm getting I/O error
Any ideas?
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!
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)
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