Hi folks, i am struggling with this issue the last 2 days,
first i kinda bricked my X, i followed this guide to bring it back on
http://forum.xda-developers.com/oneplus-x/general/guide-mega-unbrick-guide-hard-bricked-t3272108
i made all updates available to 3.1.4... i unlocked boot loader, flashed TWRP blu_sp★rk r175 and afterwards tryed to flash latest CM13 nightly
but with no luck, i am always receiving Error 7.. does anyone has a solution to this?
thanks in advance!
Tommyr84 said:
Hi folks, i am struggling with this issue the last 2 days,
first i kinda bricked my X, i followed this guide to bring it back on
http://forum.xda-developers.com/oneplus-x/general/guide-mega-unbrick-guide-hard-bricked-t3272108
i made all updates available to 3.1.4... i unlocked boot loader, flashed TWRP blu_sp★rk r175 and afterwards tryed to flash latest CM13 nightly
but with no luck, i am always receiving Error 7.. does anyone has a solution to this?
thanks in advance!
Click to expand...
Click to collapse
There's no blu spark kernel for ROMs/OOS with updated bootloader . Not sure if that's what causing the error 7 but its a start. Try using. Sultans uodated twrp I don't have any issues with it.
Exodusche said:
There's no blu spark kernel for ROMs/OOS with updated bootloader . Not sure if that's what causing the error 7 but its a start. Try using. Sultans uodated twrp I don't have any issues with it.
Click to expand...
Click to collapse
hmmm.. ok, i will give it a try! Thanks, i will tell if this works out
Tommyr84 said:
hmmm.. ok, i will give it a try! Thanks, i will tell if this works out
Click to expand...
Click to collapse
V175 is a kernel
You certainly flashed BS TWRP V41.
Kéno40 said:
V175 is a kernel
You certainly flashed BS TWRP V41.
Click to expand...
Click to collapse
so i tried sultans TWRP (Sultan-TWRP-onyx-3.0.2-3_2016-10-23)... also flashed SuperSU.. worked like a charm!
But when i am trying to flash CM13 (cm-13.0-20161122-NIGHTLY-onyx) i still get Error 7 ...
You tried to flash TWRP for CM13 sultan rom ?
Tommyr84 said:
so i tried sultans TWRP (Sultan-TWRP-onyx-3.0.2-3_2016-10-23)... also flashed SuperSU.. worked like a charm!
But when i am trying to flash CM13 (cm-13.0-20161122-NIGHTLY-onyx) i still get Error 7 ...
Click to expand...
Click to collapse
Flash twrp from here
http://forum.xda-developers.com/one...al-twrp-3-0-2-0-recovery-onyx-t3471584/page10
Fap4k said:
Flash twrp from here
http://forum.xda-developers.com/one...al-twrp-3-0-2-0-recovery-onyx-t3471584/page10
Click to expand...
Click to collapse
ok, i flashed this Twrp version, same error ! Error : 7 Error installing zip file
i realy don't know which point i am missing, i downloaded the CM13 nightly fresh from the official side...
i can't be the only one who is facing this error
Update the Boot-loader first, you can follow a post found in home page of opx, u still have to use another TWRP recovery (not official) after updating bootloader. U vil get all info in the thread.
raj.ify said:
Update the Boot-loader first, you can follow a post found in home page of opx, u still have to use another TWRP recovery (not official) after updating bootloader. U vil get all info in the thread.
Click to expand...
Click to collapse
Hi, according to your post, i followed this description http://forum.xda-developers.com/oneplus-x/general/guide-update-bootloader-firmware-to-t3478917
flashed "OPXBLUpdateOOS3.1" and new TWPR afterwards "twrp-3.0.2-2_blu_spark.v41-onyx_by-engstk.img" with no error!
rebooted into recovery, tried to install "cm-13.0-20161204-NIGHTLY-onyx" ... and guess what?! ERROR 7 again!
so i am defenetly on new bootloader, i tried all 3 options from the threat above (flashed via ADB and via SD card) no problem! also got bootloader unlocked info form ADB.
everything works, till i try to flash a CM image... then i receive ERROR 7 ;(
Hey There,
I`m stuck with the same Error.
The only Recovery i can boot ist the normal TWRP Recovery.
The blu Spark TWRP Recovery, the Stock Recovery and the CM13 Nighty Onyx Recovery wont work. I get the fastboot DTB not found Error.
And I cant install any custom ROM. I Always get the Error 7, ZIP could not be installed from Z://
If i erase the Assets it boots directly in to Bootloader (without saying Fastboot Mode on the screen, but with the OnePlus Logo).
If I flash one of the CM14 versions it gives no error 7 but boots into the Bootloader as well.
I have no custom kernel installed.
My plan was to flash the CM13 Nighty Onyx Recovery but I cant get around the DTB error,
Thanks for Help.
Greetings Clon
EDIT:
I tied the BL Update from the mentioned thread above.
aaaaand: Error 7
Here is my complete error:
Code:
Can't install this package on top of incompatible data. Please try another package or run a factory reset.
[COLOR="Red"]Updater ended with ERROR: 7
Error installing zip file '/sdcard/ROMs/cm-13.0-20161122-NIGHTLY-onyx.zip'[/COLOR]
---------- Post added at 05:33 PM ---------- Previous post was at 04:56 PM ----------
Okay I have a Solution, but I dont know how I did it.
This is what I made.
1. I did a factory reset.
2. I did a factory reset. (Why not tho)
3. I restarted the recovery.
4. I did a factory reset.
5. I changed the filesystem for data partition. (It was on ext4, but I changed it to ext4 although to get Errors out or something like that.
6. I rebooted into Bootloader.
7. I flashed and booted this recovery: http://forum.xda-developers.com/devdb/project/dl/?id=20236&task=get (and got no dtb error. yay!)
8. I installed the nightly CM, and the latest gapps (and i got no error 7. yay!)
I know its a bit random but i think the error has to do something with the data partition and the filesystem....
Void your warranty!
Related
I accidentally flashed TWRP to the boot instead of recovery. Whenever I turn on the phone it goes straight to TWRP. As it stands the phone is unsuable! AS far I understand it the way to fix this is to flash the phone's original boot.img to the boot. Is this correct? If so my phone is MT2L03 with the 5.1 update. Does anynone know of any link or could anyone PLEASE share their stock boot.img with me. I really need help!
Thank You.
Boot image is part of OS. If you want to install CM12, while you are in twrp, just transfer the cm12 rom and gapp from pc to your sdcard, then flash both. You get complete cm12 with its boot image.
But if you want stock boot image back, you can just flash the stock firmware using the 3 button boot. It is available in the "official stock firmware" section in the INDEX page: http://forum.xda-developers.com/showthread.php?t=3149530
If you have difficulties doing that, let us know. I maybe can find it somewhere, but to be honest, I don't use stock anymore once CM is out.
Thanks. CM12 flash problem
I was able to find a b321 boot.img online so problem solved. The cm 12 flash is not working for me I keep getting an error while flashing TWRP keeps telling me that the cm 12.1mt2 file is specifically for the b322 bootloader but that my bootloader is "unknown" so its unable to flash.
Still haven't figured out what the problem is. I tried to install the specific 2.8.7.0 TWRP for the mt2l03 via the app but it gives me an error. When I try to flash it in recovery it still has no effect on the cm install. Maybe someone would be kind enough to guide me.
fcbfan2k said:
I was able to find a b321 boot.img online so problem solved. The cm 12 flash is not working for me I keep getting an error while flashing TWRP keeps telling me that the cm 12.1mt2 file is specifically for the b322 bootloader but that my bootloader is "unknown" so its unable to flash.
Still haven't figured out what the problem is. I tried to install the specific 2.8.7.0 TWRP for the mt2l03 via the app but it gives me an error. When I try to flash it in recovery it still has no effect on the cm install. Maybe someone would be kind enough to guide me.
Click to expand...
Click to collapse
Try reading the OP for that ROM. It clearly states you have to be in b322.... Reading is key.
Moody66 said:
Try reading the OP for that ROM. It clearly states you have to be in b322.... Reading is key.
Click to expand...
Click to collapse
i do have b322. So the problem is not that. the problem was already there even before i booted with the b321.img. In any case the img is for boot only. It is not the build.
Also twrp, have you install the twrp listed in that same page? other twrp version doesn't work.
Edit, saw you mentioned already that install twrp error using app. So try install the correct twrp in bootloader.
fcbfan2k said:
i do have b322. So the problem is not that. the problem was already there even before i booted with the b321.img. In any case the img is for boot only. It is not the build.
Click to expand...
Click to collapse
If you flashed b321 boot image you are not on b322 boot... And the correct twrp is found in the same OP....
Ok guys, im at the end and need your help. I searched for this Problem since yesterday but couldnt find what describes my problems.
I think i did mistake after mistake, and yes im a noob, so feel free to dump on me what you got
Yesterday i wanted to update Sultan's CM ROM on my OPX, so i downloaded it and tried to install it over TWRP what gives me error messages. I made a factory wipe and installed OxygenOS 2.2.3 and then updated my TWRP to Sultan's new one (Version 3.0.2.3). After i flashed the .img, TWRP wasnt booting anymore, it was stuck on the 1+ Screen, but i was able to get to the System. So i get Root access over the SuperSU App and then flashed the TWRP zip over the Rashir App and TWRP worked again, then i flashed the new OxygenOS (3.1.3) what was successful. But now, TWRP wont work again. When i try to boot into recovery, it just show the 1+ Screen and Vibrates for maybe 1 second, but than it skips and boot automatically into System. The SuperSU App says its no SU File installed and can't be installed. Fastboot didnt't work either. When i connect it and type in ADB devices it shows me the ID. But with Fastboot devices nothing happens and im unable to do anything over it. (Drivers are correctly installed, without Signature check by windows etc.)
I know, i probably made some huge mistakes with all that. Do you guys have any solutions to get the Bootloader working again?
Thanks for any helps!
best regards
That recovery was for new BL and you flashed it over Old one.
Follow this guide http://forum.xda-developers.com/oneplus-x/general/guide-mega-unbrick-guide-hard-bricked-t3272108
Adesh15 said:
That recovery was for new BL and you flashed it over Old one.
Follow this guide http://forum.xda-developers.com/oneplus-x/general/guide-mega-unbrick-guide-hard-bricked-t3272108
Click to expand...
Click to collapse
Ok i will do that.
But just to be sure. After ive done this, im updating Oxygen to the newest Version and then install Sultan's newest TWRP and CM ROM?
Like i said, im not a Pro with it and i just dont want to fu** it up again.
Thank you.
Ulman2033 said:
Ok i will do that.
But just to be sure. After ive done this, im updating Oxygen to the newest Version and then install Sultan's newest TWRP and CM ROM?
Like i said, im not a Pro with it and i just dont want to fu** it up again.
Thank you.
Click to expand...
Click to collapse
Yup.
Will work fine.
I was flashing paranoid android 6.0.2 for my device. I downloaded the zip(from the official paranoid android website) and checked the md5 checksum, which did not match. However, like a total idiot, I flashed it nonetheless. On booting, the phone gets stuck on the boot logo. I tried booting into recovery(TWRP) and performing a factory reset to no avail. I redownloaded the flashable zip for Paranoid, successfully verified the md5 checksum and flashed it again, no avail. Restore a full backup from within TWRP, no avail. My phone still gets stuck on the bootlogo. I have looked all over every forum without any results. Please help me out? I would like to get it back to functional state and flash the rom again. As mentioned, I have access to my custom recovery and can connect to my device via fastboot. I am willing to give any other information you may need.
Thanks!
Shreyas
shreyasminocha said:
I was flashing paranoid android 6.0.2 for my device. I downloaded the zip(from the official paranoid android website) and checked the md5 checksum, which did not match. However, like a total idiot, I flashed it nonetheless. On booting, the phone gets stuck on the boot logo. I tried booting into recovery(TWRP) and performing a factory reset to no avail. I redownloaded the flashable zip for Paranoid, successfully verified the md5 checksum and flashed it again, no avail. Restore a full backup from within TWRP, no avail. My phone still gets stuck on the bootlogo. I have looked all over every forum without any results. Please help me out? I would like to get it back to functional state and flash the rom again. As mentioned, I have access to my custom recovery and can connect to my device via fastboot. I am willing to give any other information you may need.
Thanks!
Shreyas
Click to expand...
Click to collapse
What was your last rom? Did u upgrade ur bootloader?
You probably looking at mega unbrick guide
cva_kabil said:
What was your last rom? Did u upgrade ur bootloader?
Click to expand...
Click to collapse
I was running stock OxygenOS(>3.0.0) ROM.
shreyasminocha said:
I was running stock OxygenOS(>3.0.0) ROM.
Click to expand...
Click to collapse
Yeah thats d problem, PA roms are only compatible with old lollipop bootloader, u said u were in oos3 which means u hv updated to ur bootloader to marshmallow. Try clean flashing new bootloader supported roms. Before downloading check for its compatibility, all nougat roms r compatible.. U can try if u wish ))
cva_kabil said:
Yeah thats d problem, PA roms are only compatible with old lollipop bootloader, u said u were in oos3 which means u hv updated to ur bootloader to marshmallow. Try clean flashing new bootloader supported roms. Before downloading check for its compatibility, all nougat roms r compatible.. U can try if u wish ))
Click to expand...
Click to collapse
That said, should I follow a bricked guide before doing the above?
cva_kabil said:
Yeah thats d problem, PA roms are only compatible with old lollipop bootloader, u said u were in oos3 which means u hv updated to ur bootloader to marshmallow. Try clean flashing new bootloader supported roms. Before downloading check for its compatibility, all nougat roms r compatible.. U can try if u wish ))
Click to expand...
Click to collapse
Also, is there any way I can downgrade my bootloader?
shreyasminocha said:
Also, is there any way I can downgrade my bootloader?
Click to expand...
Click to collapse
Flash any 2.X.X ROM. One way is to fastboot flash old stock recovery and flash safest way I think. The other is to flash with twrp make sure after flashing the ROM to flash old twrp IMG after. Make sure you boot right back into twrp.
shreyasminocha said:
Also, is there any way I can downgrade my bootloader?
Click to expand...
Click to collapse
Assuming you're on OOS3 with TWRP for new bootloader,
- Boot into recovery
- Wipe everything except SD Card
- Flash OOS2 zip
- Boot into it
- Goto settings, unlock dev options, enable advanced reboot
- Then reboot to bootloader
- Flash twrp for old bootloader via fastboot, use this one https://dl.twrp.me/onyx/twrp-3.0.2-0-onyx.img
Done
-Now u hv sucessfully downgraded ur bootloader,flash PA or any supported roms
Used mega unbrick tool because I was unable to unlock bootloader and now I'm stuck at 1+ logo (powered by android disappears quickly), did you solve it?
edit: nevermind, adb sideload with stock OOS fixed it.
TravaPL said:
Used mega unbrick tool because I was unable to unlock bootloader and now I'm stuck at 1+ logo (powered by android disappears quickly), did you solve it?
edit: nevermind, adb sideload with stock OOS fixed it.
Click to expand...
Click to collapse
Tried mega unbrick. (bootloop)
Tried OOS3.1.4.zip via stock recovery and success message apears after installation but still bootloop (previusly it was on CM13)
Tried ADB sideload (but not booting)
i have access to ADB and Fastboot.
please help :crying:
iamsandiprathva said:
Tried mega unbrick. (bootloop)
Tried OOS3.1.4.zip via stock recovery and success message apears after installation but still bootloop (previusly it was on CM13)
Tried ADB sideload (but not booting)
i have access to ADB and Fastboot.
please help :crying:
Click to expand...
Click to collapse
Did you managed to sort it out? How?
Mega unbricked guide?
Hi guys
Can't install any OS (tried via ADB commands and flashing custom roms via TWRP).
Whatever I try, it just boots to TWRP.
ADB commands do work because I managed to install TWRP 3.0 and 3.1 for the Moto Z Griffin
Bootloader is unlocked
This device was working fine on Stock Noughat (installed via ADB) and AOKP (installed via TWRP).
Problems began when the camera "failed to start" and in my frustration, I wiped everything via TWRP including system, so now I have no OS.
Not sure why I can't get anything to install.
Follow this guide: https://forum.xda-developers.com/showthread.php?t=3506342
Sent from my XT1650 using XDA-Developers Legacy app
grneyez said:
Follow this guide: https://forum.xda-developers.com/showthread.php?t=3506342
Sent from my XT1650 using XDA-Developers Legacy app
Click to expand...
Click to collapse
followed that guide
Had this working for months and needed to wipe so I did a factory reset and all my phone does is boot to twrp
I tried this process again and all goes good or so it seems but just boots to twrp
I tried a restore from my backup from twrp and get all the way done and it fails on "unable to wipe Fsg."
Above there is a bunch of red failed:
Could not mount /data and unable to find crypto foooter
Failed to mount '/data' (Invalid argument)
Unable to recreate /data/media folder
Failed to mount'/cache' (invalid argument)
failed to mount'/system'(invalid argument)
Failed to mount storage
failed to mount'/data'(invalid argument)
failed to mount'/cache'(invalid argument)
failed to mount'/data/media/twrp'(invalid argument)
unable to wipe fsg.
any ideas? right now just a brick here. i have tried flashing roms from twrp and still just boot to twrp
I'm assuming you tried to flash the stock ROM via fastboot?
If so, I'm a little at a loss here. Although since you have TWRP, try flashing the stock ROM along with its recovery following the guide linked below;
https://forum.xda-developers.com/moto-z/development/android-nougat-moto-z-versions-t3506342
And grab the firmware for your device here;
https://firmware.center/firmware/Motorola/Moto Z/Stock/XT1650-03/
Make sure it's the correct firmware for your device. If you updated to Nougat via an OTA, you have to flash a Nougat ROM. You may also use the one linked in the XDA article, although I can't guarantee its stability.
D13H4RD2L1V3 said:
I'm assuming you tried to flash the stock ROM via fastboot?
If so, I'm a little at a loss here. Although since you have TWRP, try flashing the stock ROM along with its recovery following the guide linked below;
https://forum.xda-developers.com/moto-z/development/android-nougat-moto-z-versions-t3506342
And grab the firmware for your device here;
https://firmware.center/firmware/Motorola/Moto Z/Stock/XT1650-03/
Make sure it's the correct firmware for your device. If you updated to Nougat via an OTA, you have to flash a Nougat ROM. You may also use the one linked in the XDA article, although I can't guarantee its stability.
Click to expand...
Click to collapse
Maybe it's because I haven't had my coffee yet, but is there a US 7.0 file on that site? I can only find the 6.0 version. I'm on Rodgers nougat rom I flashed a couple weeks ago and I'd like to get on the US version since I've been having apn issues
royalflush5 said:
Maybe it's because I haven't had my coffee yet, but is there a US 7.0 file on that site? I can only find the 6.0 version. I'm on Rodgers nougat rom I flashed a couple weeks ago and I'd like to get on the US version since I've been having apn issues
Click to expand...
Click to collapse
Sadly, no.
As of right now, there's only a Marshmallow-based RETUS firmware. It'll take a while for someone to post firmware that's Nougat-based for RETUS.
D13H4RD2L1V3 said:
Sadly, no.
As of right now, there's only a Marshmallow-based RETUS firmware. It'll take a while for someone to post firmware that's Nougat-based for RETUS.
Click to expand...
Click to collapse
Ah, thanks for confirming. Do you happen to know of a twrp flashable zip for retus 7.0 then?
royalflush5 said:
Ah, thanks for confirming. Do you happen to know of a twrp flashable zip for retus 7.0 then?
Click to expand...
Click to collapse
Again, there's sadly no TWRP-flashable firmware for 7.0 RETUS.
There's only one for TELUS. While it works on other XT1650-03s with unlocked BLs, can't guarantee that it's all stable.
https://forum.xda-developers.com/moto-z/development/android-nougat-moto-z-unlocked-versions-t3552210
I know this thread is old but maybe this will help someone out. I had the exact same problem after a Factory Reset my phone went on a TWRP bootloop. To resolve it, just reboot into Bootloader and then select Factory Mode. My phone just started as new.
lovetatfitties said:
I know this thread is old but maybe this will help someone out. I had the exact same problem after a Factory Reset my phone went on a TWRP bootloop. To resolve it, just reboot into Bootloader and then select Factory Mode. My phone just started as new.
Click to expand...
Click to collapse
Thank you for this!!!!!!! It solved my boot loop problem too after installing stock via fastboot. Only thing that worked.
raymccoy said:
Thank you for this!!!!!!! It solved my boot loop problem too after installing stock via fastboot. Only thing that worked.
Click to expand...
Click to collapse
thanks for the Rescue same trick work for me though as i was been stuck on TWRP after flashing stock firmware via fastboot , so i manage to flash irfan v4 stock rom and booted to factory image to get it resolved , But now i want to move to complete stock without twrp as i think Oreo update is near by but i get the same issue again, Just wanna ask can u help me out with the process to go back to stock Rom
lovetatfitties said:
I know this thread is old but maybe this will help someone out. I had the exact same problem after a Factory Reset my phone went on a TWRP bootloop. To resolve it, just reboot into Bootloader and then select Factory Mode. My phone just started as new.
Click to expand...
Click to collapse
that worked for me also, but it's not a fix, its a workaround. is there an actual fix for this? I've tried the Verity_FE_patcher but that didn't work also.
hey all!
So this is a first for me... I've been rooting and playing with android for a very long time (going back to the g1 days) and this is the first time I've ever seen this.
So I was on an old version of CM and decided it was time to update finally. I had unrooted a long time ago, but was still running cm perfectly fine. I went to install a new version of recovery (so I could update) and now when I try to boot into recovery I just get the oneplus logo. Here's the strange part, the phone isn't soft bricked... I can still boot into android no problem.
Anyone else every seen this problem? Do I need to start over (unlock bootloader, root, recovery, rom)?
Anyone else ever seen this happen on Oneplus One or any other phone for that matter?
Thanks in advance!
Same Problem Here
I am having the same exact issue with my OPX: I wanted to update my old CyanogenMod and for that I needed to update my TWRP. After I flashed it successfully when trying to boot into Recovery it stucks on the 1+ Logo forever.
If I boot into OS it works (the same old CM since I haven't been able to upgrade), Fastboot as well, it's Recovery that doesn't work.
I found some post for the OP3 that state:
WHY AM I STUCK ON THE TWRP SPLASH SCREEN FOR 8 HOURS?
Be patient, wait another 8 hours.
Just kidding, try this while stuck on the loading screen:
adb shell wipe_misc; adb shell reboot recovery
Some devices might somehow get a flag set in misc that tells the bootloader to ignore the android boot image command line.
This results in the kernel not receiving the hardware name (qcom), which then confuses recovery and causes it to wait forever. FOREVER.
Click to expand...
Click to collapse
I tried it and I got the following error:
/system/bin/sh: wipe_misc: not found
Click to expand...
Click to collapse
I don't know what else to do now. Please help.
janc_z said:
I am having the same exact issue with my OPX: I wanted to update my old CyanogenMod and for that I needed to update my TWRP. After I flashed it successfully when trying to boot into Recovery it stucks on the 1+ Logo forever.
If I boot into OS it works (the same old CM since I haven't been able to upgrade), Fastboot as well, it's Recovery that doesn't work.
I found some post for the OP3 that state:
I tried it and I got the following error:
I don't know what else to do now. Please help.
Click to expand...
Click to collapse
I'm guessing we need to do a full wipe, and go back to the begining (root, reflash reocvery, reflash rom), but hoping not...
zbt1985 said:
I'm guessing we need to do a full wipe, and go back to the begining (root, reflash reocvery, reflash rom), but hoping not...
Click to expand...
Click to collapse
I guess you were right! Here's what I did:
- Tried to reflash TWRP using adb. It did flashed it but couldn't boot it and throws error "dtb not found".
- I found this post that first suggested to use the Blue Spark version of the TWRP. I tried adb-ing it and got the same error.
- In a later comment the following video was suggested: https://www.youtube.com/watch?v=kTdKmceC5xU.
- I the downloaded the stock recovery and the stock ROM from this page: https://devs-lab.com/download-oneplus-official-stock-rom.html. Be sure to find the OnePlus X section.
- Using adb I flashed the stock recovery, did a full wipe, rebooted and copied the stock ROM to my SD card.
- Reboot to Recovery, flash from local, selected the Stock ROM zip and let it do its thing.
- Again, from Fastboot I flashed the latest TWRP. I didn't get any errors now!
- Downloaded the Tesla ROM and flashed it using TWRP.
Everything is working fine now!
janc_z said:
I guess you were right! Here's what I did:
- Tried to reflash TWRP using adb. It did flashed it but couldn't boot it and throws error "dtb not found".
- I found this post that first suggested to use the Blue Spark version of the TWRP. I tried adb-ing it and got the same error.
- In a later comment the following video was suggested: https://www.youtube.com/watch?v=kTdKmceC5xU.
- I the downloaded the stock recovery and the stock ROM from this page: https://devs-lab.com/download-oneplus-official-stock-rom.html. Be sure to find the OnePlus X section.
- Using adb I flashed the stock recovery, did a full wipe, rebooted and copied the stock ROM to my SD card.
- Reboot to Recovery, flash from local, selected the Stock ROM zip and let it do its thing.
- Again, from Fastboot I flashed the latest TWRP. I didn't get any errors now!
- Downloaded the Tesla ROM and flashed it using TWRP.
Everything is working fine now!
Click to expand...
Click to collapse
Lucky you!
I on the other hand can't connect via adb, only fastboot...