Cannot flash rom getting error updater process ended with error 7 using twrp
My device has unlocked boot loader, device is rooted and having twrp recovery
i am having latest firmware 6.0.1 oxygen os 3.0.2
tried 2 different rom but getting same error
please help
ajaychhadwa said:
Cannot flash rom getting error updater process ended with error 7 using twrp
My device has unlocked boot loader, device is rooted and having twrp recovery
i am having latest firmware 6.0.1 oxygen os 3.0.2
tried 2 different rom but getting same error
please help
Click to expand...
Click to collapse
Try flashing an older twrp first
Also did you dirty flash? Wipe first then flash
Sent from my ONE A2005 using Tapatalk
What version TWRP U used now? Try used hybrid recovery or latest TWRP.
tried not working
bennyboy2120 said:
Try flashing an older twrp first
Also did you dirty flash? Wipe first then flash
Sent from my ONE A2005 using Tapatalk
Click to expand...
Click to collapse
tried with three different recovery same problem
also tried factory reset then flash
tried not working
usernamesz said:
What version TWRP U used now? Try used hybrid recovery or latest TWRP.
Click to expand...
Click to collapse
tried with latest twrp for one plus two and also tried hybrid recovery, also tried cm13 recovery not working
ajaychhadwa said:
tried with latest twrp for one plus two and also tried hybrid recovery, also tried cm13 recovery not working
Click to expand...
Click to collapse
Try Relocking and Unlocking the bootloader again
Sent from my ONE A2005 using Tapatalk
Related
Hi I unlocked my Oneplus x bootloader using fastboot adb and flashed blu_spark, super SU. But somehow my bootloader got locked again. Now i am trying to flash Cyanogen and other roms and im getting an error. I tried unlocking again but when i type fastboot oem ulock the phone restarts and boots in to TWRP. Please someone help me to unlock the bootloader again. There's a method which i found for oneplus one called tamper bit. But i cant find anything related to oneplus x.
Thank you
Did you enable "OEM Unlocking" in Developer options?
Did you enable "OEM Unlocking" in Developer options?
Yes i did. As i mentioned earlier that i have unlocked my device to install super su and blu_spark. When a new ota arrived i tried to flash the stock rom but there was an error called E: ERROR UPDATING PARTITION BINARY. So i wiped dalvik cache, system, data. Still i got the same error when i flashed. So i restore the TWRP backup of my stock rom. I tried flashing stock recovery but the device reboots into twrp. And when i triedfastboot device-info, it says device unlocked : false. And also tried again by enabling oem unlock, but when i enter the code fastboot oem unlock, the device restarts in to Twrp without asking confirmation and its still locked.
Which recovery are you using? Get the 2.8.7.0 or 3.0.0.1. It appears like TWRP issue.
Sent from my One using Tapatalk
saurabh40629 said:
Which recovery are you using? Get the 2.8.7.0 or 3.0.0.1. It appears like TWRP issue.
Sent from my One using Tapatalk
Click to expand...
Click to collapse
Im using twrp 2.8.7.0
saurabh40629 said:
Which recovery are you using? Get the 2.8.7.0 or 3.0.0.1. It appears like TWRP issue.
Sent from my One using Tapatalk
Click to expand...
Click to collapse
I want to install cm 13 on my one x but the problem that i cant unlock the bootloader again. And i cant flash stock recovery because of the same issue. It restarts to twrp.
Do one thing. Download full 2.2.0 from oneplus website and flash via twrp. Reboot to system. It will oveeride twrp and install oos and stock recovery.
Sent from my One using Tapatalk
saurabh40629 said:
Do one thing. Download full 2.2.0 from oneplus website and flash via twrp. Reboot to system. It will oveeride twrp and install oos and stock recovery.
Sent from my One using Tapatalk
Click to expand...
Click to collapse
I downloaded it and tried to install it a month ago. But when i flash i get an error, E: error updating partition binary. I cant go forward. I tried installing stock 2.1.2 too.
Do it via twrp 3.0.0
Sent from my One using Tapatalk
saurabh40629 said:
Do it via twrp 3.0.0
Sent from my One using Tapatalk
Click to expand...
Click to collapse
Can i flash twrp 3.0 without unlocking bootloader?
xkanth said:
Can i flash twrp 3.0 without unlocking bootloader?
Click to expand...
Click to collapse
Try it via adb and fastboot.
Sent from my One using Tapatalk
saurabh40629 said:
Try it via adb and fastboot.
Sent from my One using Tapatalk
Click to expand...
Click to collapse
I will give it a try.
so i had marshmallow on my phone xt1524, i then unlocked bootloader and installed twrp, and it installed fine, and also booted. i then went into android and it worked well. i then downloaded a supersu zip. then i booted back into recovery and it was the stock recovery... so i flashed twrp again and booted into it. then i installed the supersu zip, and now i cant boot my phone. it is stuck on the "Bootloader unlocker" error message. btw i used twrp 3.0.0 from this site from the official twrp site
weird thing is my phone can boot into the bootloader and also recovery and gets recognised by the computer as well, in twrp and also while its stuck on the "bootloader unlocked" error message screen
Please help, i don't know what to do.
I managed to mfastboot all the stock files. now it boots but i would still like to root; does anyone know how i can?
chandyy said:
I managed to mfastboot all the stock files. now it boots but i would still like to root; does anyone know how i can?
Click to expand...
Click to collapse
One don't use the official twrp it's having issues. Used squid twrp and it's updated. Then proceed to root by flashing a custom ROM or just flashing superSU zip on stock rom
Sent from my XT1526 using XDA-Developers mobile app
903tex said:
One don't use the official twrp it's having issues. Used squid twrp and it's updated. Then proceed to root by flashing a custom ROM or just flashing superSU zip on stock rom
Sent from my XT1526 using XDA-Developers mobile app
Click to expand...
Click to collapse
thank you it has worked for me now
chandyy said:
thank you it has worked for me now
Click to expand...
Click to collapse
Just hit the thanks button for me lol!
Sent from my XT1526 using XDA-Developers mobile app
OK so I'm on cm13 and I initially wanted to flash cm14.1 so I flashed the updated TWRP (v3.0.2-0 bc 3.0.2-1 wouldn't boot) and I factory reset and try to flash cm14.1 but I get an error7 and I read that that might be bc I'm on the old bootloader so I try to flash OOS 3.1.4 (newest to my knowledge) but that also fails with an error7 and I tried flashing the stock recovery via fastboot but it won't boot.. any suggestions?
Sent from my Pixel XL using XDA-Developers mobile app
ArmStrongDickPunch said:
OK so I'm on cm13 and I initially wanted to flash cm14.1 so I flashed the updated TWRP (v3.0.2-0 bc 3.0.2-1 wouldn't boot) and I factory reset and try to flash cm14.1 but I get an error7 and I read that that might be bc I'm on the old bootloader so I try to flash OOS 3.1.4 (newest to my knowledge) but that also fails with an error7 and I tried flashing the stock recovery via fastboot but it won't boot.. any suggestions?
Click to expand...
Click to collapse
Look here
http://forum.xda-developers.com/oneplus-x/general/guide-update-bootloader-firmware-to-t3478917/page1
saurabh40629 said:
Look here
http://forum.xda-developers.com/oneplus-x/general/guide-update-bootloader-firmware-to-t3478917/page1
Click to expand...
Click to collapse
Thanks, I figured it out tho, I had to flash OOS v2.2.0 and it boot fine then after a little searching I found my stock recovery backup from OOS 2.2.0 and it worked, and now I'm updating it to the newest oos version by the OTA in system and after I'm done and fully updated, I'll reflash the latest TWRP and make a nadroid backup and try flashing cm14.1
Sent from my Pixel XL using XDA-Developers mobile app
ArmStrongDickPunch said:
Thanks, I figured it out tho, I had to flash OOS v2.2.0 and it boot fine then after a little searching I found my stock recovery backup from OOS 2.2.0 and it worked, and now I'm updating it to the newest oos version by the OTA in system and after I'm done and fully updated, I'll reflash the latest TWRP and make a nadroid backup and try flashing cm14.1
Click to expand...
Click to collapse
Yeah.. Little long way. But whatever fixes your problem.
saurabh40629 said:
Yeah.. Little long way. But whatever fixes your problem.
Click to expand...
Click to collapse
Hey quick question, do I need to reunlock the bootloader after the method I did? The reason I'm asking is bc when I boot into fastboot to try to reflash twrp (after flashing) I reboot to recovery and it's still the stock recovery? Any suggestions? Thanks
Sent from my Pixel XL using XDA-Developers mobile app
ArmStrongDickPunch said:
Hey quick question, do I need to reunlock the bootloader after the method I did? The reason I'm asking is bc when I boot into fastboot to try to reflash twrp (after flashing) I reboot to recovery and it's still the stock recovery? Any suggestions? Thanks
Click to expand...
Click to collapse
If it's already unlocked, you don't need to do it. Did you lock it again? If you have bootloader locked, flashing recovery will fail. Anyways unlocking will not hurt. FYI Just don't lock bootloader unless you are totally stock with stock recovery.
saurabh40629 said:
If it's already unlocked, you don't need to do it. Did you lock it again? If you have bootloader locked, flashing recovery will fail. Anyways unlocking will not hurt. FYI Just don't lock bootloader unless you are totally stock with stock recovery.
Click to expand...
Click to collapse
I didn't relock it but was curious if by reverting to stock and updating to the latest version of oos that it might be locked considering I'm on the newest bootloader now or so I think at least haha
Sent from my Pixel XL using XDA-Developers mobile app
ArmStrongDickPunch said:
I didn't relock it but was curious if by reverting to stock and updating to the latest version of oos that it might be locked considering I'm on the newest bootloader now or so I think at least haha
Click to expand...
Click to collapse
No it will not. I hope you have solved your issue by now.
My phone stucks on oneplus logo after flashing paranoid rom . I do everything like wiping dalvin cache, data , system . TWRP recovery i am using is 3.03 and currently running cm 13. Any solution?
Mandeep Singh 07 said:
My phone stucks on oneplus logo after flashing paranoid rom . I do everything like wiping dalvin cache, data , system . TWRP recovery i am using is 3.03 and currently running cm 13. Any solution?
Click to expand...
Click to collapse
Is ur bootloader updated to latest one ??
[email protected] said:
Is ur bootloader updated to latest one ??
Click to expand...
Click to collapse
yeah its latest one 3.0.3
Mandeep Singh 07 said:
yeah its latest one 3.0.3
Click to expand...
Click to collapse
PA I believe is on the old bootloader still. So you would have to downgrade your bootloader by flashing LL stock recovery and 2.x.x OOS firmware. Not worth the hassle if you ask me.
Mandeep Singh 07 said:
yeah its latest one 3.0.3
Click to expand...
Click to collapse
actually when i root the phone , then it goes into bootloop, i didn`t backup my data so i lost my all data ,
after that i install paranoid then it stucks on boot logo , i tried it several times but none happens,
then i use adb push command ino twrp recovery(3.0.2) to copy cyanogenmod after that i flash it , it fails ,
then i flash cwm recovery then flash is succeded and currently running cm 13 ,
when i installed root checker it said your phone is partially rooted, when i enable root option in developer option then it said root verified.
But when i tried to flash other roms using twrp (3.0.3, 3.0.2) it stucks on boot logo.
Please help me
Exodusche said:
PA I believe is on the old bootloader still. So you would have to downgrade your bootloader by flashing LL stock recovery and 2.x.x OOS firmware. Not worth the hassle if you ask me.
Click to expand...
Click to collapse
lower bootloader can`t flash it fails every time....
Mandeep Singh 07 said:
lower bootloader can`t flash it fails every time....
Click to expand...
Click to collapse
Did you also revert to the old TWRP version 3.0.2? Other then that I'm out of ideas.
Exodusche said:
Did you also revert to the old TWRP version 3.0.2? Other then that I'm out of ideas.
Click to expand...
Click to collapse
At that twrp blu spark 3.0.2 is available and of only that recovery is working lower recoviers cant flash and boot
Mandeep Singh 07 said:
At that twrp blu spark 3.0.2 is available and of only that recovery is working lower recoviers cant flash and boot
Click to expand...
Click to collapse
Right but if your downgrading your bootloader to flash PA you need to use old bootloader TWRP 3.0.2. So that being said easiest way is flash 2.2.3 with blusprk 3.0.2-2 TWRP then immediately after flash TWRP 3.0.2 image. Now re boot back into recovery and flash PA. I prefer flashing 2.2.3 with stock LL recovery less chance of issues. Then just fastboot flash old TWRP 3.0.2 and continue with PA.
Exodusche said:
Right but if your downgrading your bootloader to flash PA you need to use old bootloader TWRP 3.0.2. So that being said easiest way is flash 2.2.3 with blusprk 3.0.2-2 TWRP then immediately after flash TWRP 3.0.2 image. Now re boot back into recovery and flash PA. I prefer flashing 2.2.3 with stock LL recovery less chance of issues. Then just fastboot flash old TWRP 3.0.2 and continue with PA.
Click to expand...
Click to collapse
thanks bro this works fine
so i was on epic miui 7.1.20 and i was triying to flash latest epic miui 7.2.16 (( https://forum.xda-developers.com/redmi-note-3/how-to/epic-rom-miui-8-7-1-12-beta-redmi-note-t3536480 )) using jamflux twrp which is the one they use on that thread. and was getting error 7 every time i tried flashing epic rom. so i flashed AOSIP that i had on my sd card and that installed just fine and booted no problem.
i tried to flash epic rom again but using this recovery (( https://forum.xda-developers.com/redmi-note-3/development/recovery-twrp-3-0-2-0-t3446909 )) and still getting error 7. so i downloaded latest nitrogenOS and twrp says it installed succesfull but when i hit reboot system it reboots stragiht into recovery. doesnt even show the MI logo on startup. so now the phone is just sitting in recovery no matter how many times i wipe and re install roms. when i reboot into system, it wont boot, even when i select power off it goes straight to recovery.
there has to be a solution and i dont thing my phone is bricked since i can access twrp.
any help ? thanks.
Change twrp recovery and reinstall rom
Sent from my ZUK Z2131 using Tapatalk
hadiyalkishan said:
Change twrp recovery and reinstall rom
Sent from my ZUK Z2131 using Tapatalk
Click to expand...
Click to collapse
which twrp should i use? and how do i flash it? flash a new twrp img via the current twrp?
cjvzla said:
which twrp should i use? and how do i flash it? flash a new twrp img via the current twrp?
Click to expand...
Click to collapse
Try flashing zcx TWRP using fastboot
flash zxc twrp usinbg the option of flashing image files within your current twrp and
flash zxc twrp using existing twrp and reboot to new twrp and then wipe data,cacahe,system and dalvik cache and see to it that system is mounted to have effects.
flash new epic rom and should resolve your problem.
regards
Dharmesh
Zcx is best for rn3
Sent from my ZUK Z2131 using XDA-Developers Legacy app
Hello plz help me i have redmi note 3 2/16 gb i have unlocked its bootloader and currently on marshmallow version. Whenever i flash miui rom based on lolipop version it bootloop and doenst boot also tried with miflash, twrp, orange fox, redwolf but same problem. But when i flash rom based on marshmallow it boots and work fine. So what is the problem can anyone help with this.
Androiddeep said:
Hello plz help me i have redmi note 3 2/16 gb i have unlocked its bootloader and currently on marshmallow version. Whenever i flash miui rom based on lolipop version it bootloop and doenst boot also tried with miflash, twrp, orange fox, redwolf but same problem. But when i flash rom based on marshmallow it boots and work fine. So what is the problem can anyone help with this.
Click to expand...
Click to collapse
Why do you need to go back to Lollipop? Even in Oreo nowadays many banking/financial apps etc. don't work anymore.