Hello, i got an used oneplus x - very nice device
I can only flash older TWRP versions up to 3.0.2.0. Newer versions >3.0.2.0 don't boot. AS well i can't flash newer custom roms like RR7.02 or lineageos 17.1. The TWRP installiert script sad "the rom is for an other device" . When i patch the script to ignore the device check the system don't boot. An old RR version based in Android 6 works. All TWRP and custom rom files are for the Oneplus X (onyx).
Has anyone an idea?
Addition: Flashing the Oneplus original Rom OnePlusOxygen_14_OTA_019.....zip has the same insztallation problem. he TWRP Script report: ""This package is for "OnePlus" devices; this is a "ONE". . The RR-P-v7.02-201909... reports "E3004: This package is for device: OnePlus,ONE; this device is ." Lineage-17.1-2020...UNOFFICIAL-... the same too: "E3004: This package is for device: OnePlus,ONE; this device is ."
It seams to me, that the Oneplus X has another hardware revision(?).
The problem is solved. I install Oneplus original recovery.img over TWRP. Than i flash the latest Stock Rom. After that i could install the nevest TWRP and a new Custom Rom.
Related
Hello All,
Hope you all are doing well.
Recently I installed CM-13 on my One Plus X with TWRP but now when I try installing OxygenOS 3.1.3 via TWRP its giving an error stating zip is corrupted which is not the case but still I re-downloaded the OTA and tried again but still same error. Upon googling found that OxygenOS cannot be installed via TWRP but is that true? Some say that is is possible, please can someone guide me how to install the OxygenOS 3.1.3? Any help would be highly appreciated!
Regards,
Vineeth
If you are using official TWRP then after installing the oos 3.1.3 it should be gone.
So its better to flash oos stock recovery and just flash the oos 3.1.3. after that you can use bluspark modified TWRP recovery.
And yes you can flash oos 3.1.3 by twrp.
Which version of TWRP you are using??
when you flashing the zip, Is it show something like that "This package is for ONEPLUS BUT YOUR IS ONE"
Which version of TWRP you are using?? --> twrp-3.0.2-0
when you flashing the zip, Is it show something like that "This package is for ONEPLUS BUT YOUR IS ONE" ---> Yes, I get this message!
So its better to flash oos stock recovery and just flash the oos 3.1.3. after that you can use bluspark modified TWRP recovery.-------> Please can you provide me some link for for more help??
Which version of TWRP you are using?? --> twrp-3.0.2-0
when you flashing the zip, Is it show something like that "This package is for ONEPLUS BUT YOUR IS ONE" ---> Yes, I get this message!
So its better to flash oos stock recovery and just flash the oos 3.1.3. after that you can use bluspark modified TWRP recovery.-------> Please can you provide me some link for for more help??
See here :
http://forum.xda-developers.com/oneplus-x/help/to-stock-rom-form-cm13-t3472765
Thanks alot Kéno40, will check and try it and get back here with my observations, thnx alot for response and help!!
Here is the Solution watch this video
https://www.youtube.com/watch?v=kTdKmceC5xU
am not able to update twrp
twrp-3.1.0-0-onyx.img
twrp-3.0.3-0-onyx.img
twrp-3.0.2-1-onyx.img
when i flashed these files using twrp and rebooted my device i was stuck in one plus logo.
Even i cant flash any of above 3 twrp files using fastboot adb method i am getting an error "remote dtb not found" pls check screenshot
then i reinstalled twrp-3.0.2-0-onyx.img using adb fastboot method , but i cant not install or update version above 3.0.2.0 plz help
Hi guys if anyone facing same problem Read this
PROBLEM
1)Error Code 7 while flashing new ROM (like Nogut ROMS ).
2)Remote dtb not found while updating old twrp to new (eg. twrp 2.8 to twrp 3.1.0.0)
Cause of problem
Users who have already flashed and rooted their phone and using custom ROMs like CM12 CM 13 or any other from past year will likely to face this problem
while updating twrp recovery or while updating to new custom ROM Nogut cm14 .
Because new custom ROMs have bootloader in diffrent partition (something like this) so you wont be able to flash your phone with new ROMs i.e cm14 or nogut or you wont be able to flash new twrp recovery which is 3.1.0.0
Please keep in mind if you are using following twrp version then you should flash your phone with old twrp 2.8.7.0
twrp-3.0.2-0-onyx.img 14.4M 2016-04-04 23:04:23 EDT
twrp-3.0.1-0-onyx.img 14.5M 2016-04-01 04:24:54 EDT
twrp-3.0.0-1-onyx.img 14.5M 2016-02-15 23:17:25 EST
twrp-3.0.0-0-onyx.img 14.4M 2016-02-06 09:18:41 EST
above point is important look at the solution now
Solution
Step
1)flash your phone with old twrp version TWRP 2.8.7.0 using fastboot method(because we are going to install stock recovery in my case stock recovery of oneplus X lollipop version)
2)after installing stock recovery install 2.14 ver of stock ROM of oneplus X (for oneplus x devices) (for other brands eg samsung look for ur old stock recov and ROM)
3)install old Stock ROM in ur device
4)now again boot into stock recovery and install latest stock ROM (for oneplus X i installed latest oneplus X oxygen OS 3.1.4).
5)after doing above step you can install latest twrp-3.1.0-0-onyx.img without any "remote dte not found error" using fastboot.
6)once you flash twrp-3.1.0-0-onyx.img flash your phone with latest CM14 or any latest android N or nogut ROM without any problem
Note : For error code 7 some people suggested to edit udatescrip file which is not good solution and it is temporary and it wont work for all so do it as i suggested
Comman ERRORS :
1) if you are on twrp 3.x.x.x you will face Remote dte not found while booting your phone in stock recovery using fastboot
so first of all flash your phone with old twrp 2.8.7.0.
2)Do not wipe your internal storage in frustration it will create more problems because you wont be able to transfer files into your phone to flash it (Use OTG cable or SD card if u did it already).P.S you can do it afterwards
Do i need to install stock recovery of stock ROM ? some help would really be appreciated
i can install all twrp upto "twrp3020 " version
but if i try to flash greater version like twrp3021 or twrp3100 m getting same error
i need new twrp because i am not able to flash Android N custome roms i am getting an error code 7 when i am installing ROM
Follow the mega unbrick guide, then update your bootloader then flash latest twrp.
@Joshwin Aranha
CheckYourScreen said:
Follow the mega unbrick guide, then update your bootloader then flash latest twrp.
@Joshwin Aranha
Click to expand...
Click to collapse
thanx for replay but i found solution
Hi guys if anyone facing same problem Read this
PROBLEM
1)Error Code 7 while flashing new ROM (like Nogut ROMS ).
2)Remote dtb not found while updating old twrp to new (eg. twrp 2.8 to twrp 3.1.0.0)
Cause of problem
Users who have already flashed and rooted their phone and using custom ROMs like CM12 CM 13 or any other from past year will likely to face this problem
while updating twrp recovery or while updating to new custom ROM Nogut cm14 .
Because new custom ROMs have bootloader is diffrent partition (something like this) so you wont be able to flash your phone with new ROMs i.e cm14 or nogut or you wont be able to flash new twrp recovery which is 3.1.0.0
Please keep in mind if you are using following twrp version then you should flash your phone with old twrp 2.8.7.0
twrp-3.0.2-0-onyx.img 14.4M 2016-04-04 23:04:23 EDT
twrp-3.0.1-0-onyx.img 14.5M 2016-04-01 04:24:54 EDT
twrp-3.0.0-1-onyx.img 14.5M 2016-02-15 23:17:25 EST
twrp-3.0.0-0-onyx.img 14.4M 2016-02-06 09:18:41 EST
above point is important look at the solution now
Solution
Step
1)flash your phone with old twrp version TWRP 2.8.7.0 using fastboot method(because we aree going to install stock recovery in my case stock recovery of oneplus X lollipop version)
2)after installing stock recovery install 2.14 ver of stock ROM of oneplus X (for oneplus x devices) (for other brands eg samsung look for ur old stock recov and ROM)
3)install old Stock ROM in ur device
4)now again boot into stock recovery and install latest stock ROM (for oneplus X i installed latest oneplus X oxygen OS 3.1.4).
5)after doing above step you can install latest twrp-3.1.0-0-onyx.img without any "remote dte not found error" using fastboot.
6)once you flash twrp-3.1.0-0-onyx.img flash your phone with latest CM14 or any latest android N or nogut ROM without any problem
Note : For error code 7 some people suggested to edit udatescrip file which is not good solution and it is temporary and it wont work for all so do it as i suggested
Comman ERRORS :
1) if you are on twrp 3.x.x.x you will face Remote dte not found while booting your phone in stock recovery using flashboot
so first of all flash your phone with old twrp 2.8.7.0.
2)Do not wipe your internal storage in frustration it will create more problems because you wont be able to transfer files into your phone to flash it (Use OTG cable or SD card if u did it already).P.S you can do it afterwards
mhmm.. the unbrick guid dosnt help.. followd the guidé - now my bootloader is locked and stuck locked so no 2.8.7.0 flashing.. Ideas? i`m working now 24h this issue..
Wagner.B said:
mhmm.. the unbrick guid dosnt help.. followd the guidé - now my bootloader is locked and stuck locked so no 2.8.7.0 flashing.. Ideas? i`m working now 24h this issue..
Click to expand...
Click to collapse
are you on stock recovery right now ?
Finaly the Lv.2 support got it back working via "our" msm unbrick tool (Still got it on my drive =D)
but learned nothing - trying to get lineageOS again.
The recovery is now TWRP v3.1.0-0 for E1003_15_161107 (it works for now on a backup..)
But... i must say - I'm very worried that i cant flash lineage again..
I dont know what the trick is...
Here is the Solution watch this video
https://www.youtube.com/watch?v=kTdKmceC5xU
Yes!!
I ve been looking for a solution the past days since i got stuck in older twrp versions and could only upgrade to android 6.
Thanks man!! You rock!!
I tried to install the OOS beta 3 on a TWRP/UNLOCKED BOOTLOADER, Oneplus 5 running OOS 4.5.(Something) [The Nougat Version]. As the ROM did not flash I booted into TWRP to find that all of my files were encrypted. How do i get another rom onto the device to flash that, what rom should i flash, and how do i prevent this in the future?
**ADB sideload on TWRP also wont load
Hi i have a problem with my poco f1
Status : UBL , NO OS , Orangefox recovery
Tried : flashing many roms and changed from twrp to orangefox but the problem persists. While trying to install the roms i wiped everything before.
Problem : Whenever i try installing a custom rom i get an error 7 message that says : xiaomi.verify_vendor() failed to read current vendor UTC build date: -2
I am not able to flash any custom rom and when i try i get this error.
The problem occurred when i tried to boot on my installed rom from multirom recovery. I had backed up everything but when i restore the backup (except the multiRom recovery) the phone is stuck on the pocophone logo.
If you need any more info i can provide please ask for it.
try clean flashing global stable fastboot rom using mi flash tool then flash twrp and flash any rom you want
https://mirror.akhilnarang.me/MIUI/beryllium/
take the latest vendor image 9.3.28 (dated 29-03-2019 17:11)
flash this via twrp and then flash rom
it should work
YasuHamed said:
https://mirror.akhilnarang.me/MIUI/beryllium/
take the latest vendor image 9.3.28 (dated 29-03-2019 17:11)
flash this via twrp and then flash rom
it should work
Click to expand...
Click to collapse
I will try this method first due to the smaller download size. I hope it works so i do not have to flash the stock rom again and go though the whole process.
It worked. I am now flashing a custom rom. My question is why did this happen ?
jackaros said:
It worked. I am now flashing a custom rom. My question is why did this happen ?
Click to expand...
Click to collapse
BRO WHENEVER you are trying to flash new rom be on latest vendor , firmware and vendor can be found on leanage os xda page 1 , updated rom requires latest vendor
jackaros said:
It worked. I am now flashing a custom rom. My question is why did this happen ?
Click to expand...
Click to collapse
I think you came from MIUI10.2.x
since, miui10 on android9, Xiaomi has started using MODIFIED version of VENDOR image*
so when you flash custom rom which works on standard vendor image, it gives your either error7 or hangs on splash screen
*android has following partitions /boot /recovery /system, /data, /internalstorage /persist /OEM
oem or VENDOR partition translates android
using modified oem (vendor) image in android 9, its xiaomi's attempt for speedy android updates (CGI) (treble)
YasuHamed said:
I think you came from MIUI10.2.x
since, miui10 on android9, Xiaomi has started using MODIFIED version of VENDOR image*
so when you flash custom rom which works on standard vendor image, it gives your either error7 or hangs on splash screen
*android has following partitions /boot /recovery /system, /data, /internalstorage /persist /OEM
oem or VENDOR partition translates android
using modified oem (vendor) image in android 9, its xiaomi's attempt for speedy android updates (CGI) (treble)
Click to expand...
Click to collapse
Just a follow up question..
So what will happen to my phone.. if its on miui 10.2.3.0 then i flashed the latest vendor img?? Will it cause bootloop?? Will it have a better performance?? Will it make games much smoother???
santiagoruel13 said:
Just a follow up question..
So what will happen to my phone.. if its on miui 10.2.3.0 then i flashed the latest vendor img?? Will it cause bootloop?? Will it have a better performance?? Will it make games much smoother???
Click to expand...
Click to collapse
miui10.2.x has its own modified vendor image,
to comeback on standard image, you must flash the image (which you did)
"E1001: failed to update system image. Updater process ended with error 7" on Mido
I need your help guys.
I kept on getting this error saying "E1001: failed to update system image.
Updater process ended with error 7" everytime I flash roms on my Redmi note 4x SD variant Mido. No matter what the rom I flash and recovery I use results were all the same.
I already edited the roms that I have, I removed all the asserts scripts from the updater script but it was still the same.
I have been flashing roms before but I am not completely familiar with this error and on how to fix it.
I hope you guys can help me.
rabe0334 said:
I need your help guys.
I kept on getting this error saying "E1001: failed to update system image.
Updater process ended with error 7" everytime I flash roms on my Redmi note 4x SD variant Mido. No matter what the rom I flash and recovery I use results were all the same.
I already edited the roms that I have, I removed all the asserts scripts from the updater script but it was still the same.
I have been flashing roms before but I am not completely familiar with this error and on how to fix it.
I hope you guys can help me.
Click to expand...
Click to collapse
Which ROMs are you trying to flash?
Which TWRP (recovery) are you using?
Noter2017 said:
Which ROMs are you trying to flash?
Which TWRP (recovery) are you using?
Click to expand...
Click to collapse
Attempted to flash:
Corvus 5 Q mido
Corvus 7.5 Q mido
Corvus 8.5 Q mido
Syberia OS 3.9 Q mido
Resurrection Remix Q 8.6.2 mido
MIUI 12 Razer mido
MIUI 11 stock global recovery rom
Colt OS Q latest ver mido
AbhiXROG Edition 20.9.24
Recoveries that I've used:
TWRP 3.3.1
Orange Fox r11
Pitchblack Recovery 3.0.0 (twrp 3.4.0 based)
Firmware:
MIUI 11 Global stable
They've failed me, and my phone is dead until now.
I also tried to flash fastboot global miui rom, so what I did is I boot my phone to EDL then used miflash the latest one to flash the rom into my phone. Flash attempts were all successful, but my phone kept on being stuck on Mi Logo. I can no longer think of other options.
rabe0334 said:
Attempted to flash:
Corvus 5 Q mido
Corvus 7.5 Q mido
Corvus 8.5 Q mido
Syberia OS 3.9 Q mido
Resurrection Remix Q 8.6.2 mido
MIUI 12 Razer mido
MIUI 11 stock global recovery rom
Colt OS Q latest ver mido
AbhiXROG Edition 20.9.24
Recoveries that I've used:
TWRP 3.3.1
Orange Fox r11
Pitchblack Recovery 3.0.0 (twrp 3.4.0 based)
Firmware:
MIUI 11 Global stable
They've failed me, and my phone is dead until now.
I also tried to flash fastboot global miui rom, so what I did is I boot my phone to EDL then used miflash the latest one to flash the rom into my phone. Flash attempts were all successful, but my phone kept on being stuck on Mi Logo. I can no longer think of other options.
Click to expand...
Click to collapse
Hey, I faced the same issue today.
I'm not sure what I did wrong, but I think I wiped my data incorrectly or something.
I tried many things but it wouldn't work.
Here is how I resolved it.
1. Installed Orange Fox Recovery (Maybe not necessary, but that's what I did)
2. Format Data. (Not Wipe, Format)
3. Flashed ROM again.
Voila, it flashed.
Hope it helps.
Thanks for your response. I'll make sure to do the same procedure. I hope it can fix everything.