Hello guys,
I have a problem with my OnePlus X, and it would be lovely if I could get some help or advice from you guys.
> To provide some slight background, I purchased this off of eBay to complete my OnePlus collection. Most listings were above what OnePlus originally sold the phone for, but I found one for $125 in good condition by a seller with a good rating. It was advertised as soft-bricked, with Fastboot in working order. I thought "no problem, I'll just reflash it and be on my merry way."
Now onto the issue. I received it, charged it up, and attempted flashing the official recovery provided by OnePlus, but something is not working. I've been tinkering with Android for a number of years now, so I troubleshooted as much as I could, but to no avail.
1. Starting with device unplugged and powered off, boot into fastboot
2. Plugged into the computer, and ran `fastboot devices` to ensure it's recognized. After that, I flashed the recovery.img that was on my desktop with `fastboot flash recovery recovery.img` (yes I was in the correct directory). It looked successful. Picture of cmd response text at the following imgur album: /a/25DEQ (sorry I cannot post full links yet, had to create a new xda profile, forgot my old one :/
3. Unplugged the phone, powered off, Volume Down + Power to attempt boot into recovery. Failure. It just turns on with the 1+ logo, and quickly flashes the 'android' logo at the bottom. It stays like this until I manually power off.
I'm a bit stumped I have to admit. I would greatly appreciate any input you folks have. Thank you.
AndriyEtch said:
Hello guys,
I have a problem with my OnePlus X, and it would be lovely if I could get some help or advice from you guys.
> To provide some slight background, I purchased this off of eBay to complete my OnePlus collection. Most listings were above what OnePlus originally sold the phone for, but I found one for $125 in good condition by a seller with a good rating. It was advertised as soft-bricked, with Fastboot in working order. I thought "no problem, I'll just reflash it and be on my merry way."
Now onto the issue. I received it, charged it up, and attempted flashing the official recovery provided by OnePlus, but something is not working. I've been tinkering with Android for a number of years now, so I troubleshooted as much as I could, but to no avail.
1. Starting with device unplugged and powered off, boot into fastboot
2. Plugged into the computer, and ran `fastboot devices` to ensure it's recognized. After that, I flashed the recovery.img that was on my desktop with `fastboot flash recovery recovery.img` (yes I was in the correct directory). It looked successful. Picture of cmd response text at the following imgur album: /a/25DEQ (sorry I cannot post full links yet, had to create a new xda profile, forgot my old one :/
3. Unplugged the phone, powered off, Volume Down + Power to attempt boot into recovery. Failure. It just turns on with the 1+ logo, and quickly flashes the 'android' logo at the bottom. It stays like this until I manually power off.
I'm a bit stumped I have to admit. I would greatly appreciate any input you folks have. Thank you.
Click to expand...
Click to collapse
Which recovery u tried? Did u knOw the previous os version details?
And try this after flashing recovery in fastboot, boot into it directly by giving a cmd "fastboot boot recovery.img"
cva_kabil said:
Which recovery u tried? Did u knOw the previous os version details?
And try this after flashing recovery in fastboot, boot into it directly by giving a cmd "fastboot boot recovery.img"
Click to expand...
Click to collapse
Hi! Thank you for your reply
I posted this same question on the /r/oneplus subreddit, and received a quick and helpful walkthrough. Turns out part of the problem was that the micro-usb port on the phone itself is a bit unreliable. I haven't investigated too deeply, but it took a while to find a position for the wire to maintain a stable connection. I suspect this may be why the device was bricked in the first place (disconnect when flashing rom/kernel/etc.)
Anyways, for some reason flashing the stock recovery to the phone was just not working. The guy on reddit recommended trying TWRP, and that worked immediately. However, at that point, I had no idea what the history of the phone was or what OS was on it before, what firmware it had. I tried installing the official CM13 and then Sultan's CM13 with no luck. What *did* work was Oxygen OS 2.2.6.
At this point I'm stuck yet again though... The Marshmallow OTA (3.1.3) in the OS shows as available for download, but when I try to install the download only gets to 22% and then stops. Flashing the 3.1.3 OTA.zip available on OnePlus' support site doesn't work in TWRP, and when I try to flash stock recovery, it doesn't work.. don't know what else to try.
AndriyEtch said:
Hi! Thank you for your reply
I posted this same question on the /r/oneplus subreddit, and received a quick and helpful walkthrough. Turns out part of the problem was that the micro-usb port on the phone itself is a bit unreliable. I haven't investigated too deeply, but it took a while to find a position for the wire to maintain a stable connection. I suspect this may be why the device was bricked in the first place (disconnect when flashing rom/kernel/etc.)
Anyways, for some reason flashing the stock recovery to the phone was just not working. The guy on reddit recommended trying TWRP, and that worked immediately. However, at that point, I had no idea what the history of the phone was or what OS was on it before, what firmware it had. I tried installing the official CM13 and then Sultan's CM13 with no luck. What *did* work was Oxygen OS 2.2.6.
At this point I'm stuck yet again though... The Marshmallow OTA (3.1.3) in the OS shows as available for download, but when I try to install the download only gets to 22% and then stops. Flashing the 3.1.3 OTA.zip available on OnePlus' support site doesn't work in TWRP, and when I try to flash stock recovery, it doesn't work.. don't know what else to try.
Click to expand...
Click to collapse
Root your device using twrp or kingoroot method then install flashify and try to flash stock recovery using flashify. .. Tht may work.
Flashing 3.1.3 via official twrp ll not work... Cos ur bootloader version, U can do it only with stock recovery or u need to edit meta data file. Or u can flash stock recovery img file by twrp
cva_kabil said:
Root your device using twrp or kingoroot method then install flashify and try to flash stock recovery using flashify. .. Tht may work.
Flashing 3.1.3 via official twrp ll not work... Cos ur bootloader version, U can do it only with stock recovery or u need to edit meta data file. Or u can flash stock recovery img file by twrp
Click to expand...
Click to collapse
Thanks I'll give those a shot once I'm home from work! Quick question about editing the META INF. I've heard that doing so risks hard-bricking the device. Is that true?
AndriyEtch said:
Thanks I'll give those a shot once I'm home from work! Quick question about editing the META INF. I've heard that doing so risks hard-bricking the device. Is that true?
Click to expand...
Click to collapse
I dont think so... I hv not tried... But as of i know if u edit it wrongly, u will not be able to flash that file. . Try others methods first... Hope it works
AndriyEtch said:
Thanks I'll give those a shot once I'm home from work! Quick question about editing the META INF. I've heard that doing so risks hard-bricking the device. Is that true?
Click to expand...
Click to collapse
Hi OP, sorry for joining late to the party
So the thing is the OnePlus X is at opposites now since the official MM release on 29th September. The thing is if you are running the old bootloader (OxygenOS 2.x.x) or any ROM based on it, then the New TWRP will not boot, neither will the Stock Recovery that is hosted on the OnePlus download section for the X, which is where i assume you download the stock recovery from, right ? Also note that the official recovery hosted on the TWRP website is also yet to be updated, we're working on that.
So you are on the old Bootloader. Simple stuff. I have posted my guide a lot of time around the forums, its gained a lot of merit. You could follow it for your update process. I'll leave a link below. In case you wanna verify that the old bootloader is causing the issue my Index Thread pinned in the general section has a link for the Stock recovery for Old bootloader, try flashing that via fastboot, if it successfully boots then you're set.
Comprehensive guide to Update to Marshmallow Bootloader
The above guide is centered to the thread i have posted it on but the process is 99% the same. In the end, you could just stay with Oxygen OS 3.1.3, or flash any custom ROM based on the new Bootloader.
Now regarding your query about editing the META of the ROM, well Yes to an extent it IS risky if you ain't careful because my guide guides you to delete the one single line that removes the device check, so as long as you use the modified zip on OnePlus X only, there will be no issues.
Let me know for any further clarifications, also you're welcome to join our support group on Telegram, all of our developers are active there. Ping me (@ mellogang_unite) for an invite
Related
Chapter 1: The Foolishness of the User
Hi, I have the korean version of the optimus one(KU3700). It was on gingerbread(2.3.4) stock. I was trying to root it by downgrading it. I entered "adb reboot recovery" and I'm stuck. I tried to reflash it by going to emergency mode with the button combinations using the KDZ updater with this
"csmg. lgmobile. com:9002/swdata/WEBSW/LGKU3700/AKTFBK/KU370040_00/KU370040_00.kdz"
and it worked without any errors but when it when it came up it was still on recovery mode. Is there any way I can change the phone mode to the regular mode
Chapter 2: Journey to Salvation
For anyone who has this korean optimus one, after days of searching, I've found a web site that gave me hints to solve the problem. I just needed a different kdz file and I got it here:
h t t p://sirospace.tistory.com/category/Android%E2%97%86
popped it in google translate because I'm Filipino and can't read korean.
Downloaded the froyo kdz and flashed. I hope this can help other people stupid enough to play with their phones by typing random commands without knowing what it does, like me, LOL...so happy, now it's time to root
Chapter 3: False Hope
OK so I have successfully unbricked and rooted my KU3700, now The problem I have is installing a custom recovery on this phone, none of the images I try work.
Recovery images I have tried are as follows:
recovery-RA-GNM-thunderg-1.1.0.img
recovery-RA-GNM-thunderg-2.2.1.img
recovery-RA-GNM-thunderg-3.0.6.img
Every time it finishes and reboots, it gets stuck at the LG logo.
Chapter 4: Wisdom Within
Found the problem. The images above are for the P500.Even if the KU3700 hardware is similar to the P500, flashing firmwares made for the other model will result in errors. The same holds true for custom recoveries.
Chapter 5: The Plea to the Gods
I've contacted drellisdee and submitted the files needed for custom recovery creation for the KU3700.
Just waiting for the flash image now. Thank you everyone
Chapter 6: The Forgotten
It seems drellisdee is busy right now. I'm a windows user and knows nothing about programing. So if anybody can help I'm sure the KU3700 community would be greatful. I've attached the files I think are needed to make a custom recovery.
Chapter 7: Quest for the Custom Recovery
I got tired of waiting. So as a windows user with no experience in programming, I did a lot of copying and pasting, I managed to port clockwork mod using virtualbox following this website:
h t t p://www.koushikdutta.com/2010/10/porting-clockwork-recovery-to-new.html
So I have got a bootable and flashable custom recovery but nothing works yet. I still need to configure it according to the device.
I have uploaded the image and the build files. Please help me configure it and tell me what's wrong. I really don't know that I'm doing
PS: you can try flashing the custom recovery by doing "fastboot flash recovery /Path to/recovery.img and you can go to recovery by using android terminal and type "boot recovery". It will boot, but that's that LOL. Take out the battery to boot to normal mode.
Chapter 8: The Holy Grail
LOL, I found the answer again. I was so frustrated that I kept squishing the phone in recovery and found out that it was just a button configuration problem. A bit of research and I found out that I can toggle it by pressing volume up and volume down at the same time. WOOHOO!!! Custom Recovery at last
Chapter 9: Invasion of the ROMS
And here at last, the user is retired. But the adventure is far from over. It is foretold that the creation of the Custom Recovery will begin a new era. The key to open the gate has been found. So our hero will await the invasion of the ROMS<background music...> END
you can see at
tinhte.vn/threads/908874
Thank you for the reply but as I said, I can flash fine without errors it's getting back to regular mode I have a problem with. Rebooting and reflashing does not take me out of the recovery screen(it's just a opened box with an orange arrow and the android logo).
vidgen13 said:
Thank you for the reply but as I said, I can flash fine without errors it's getting back to regular mode I have a problem with. Rebooting and reflashing does not take me out of the recovery screen(it's just a opened box with an orange arrow and the android logo).
Click to expand...
Click to collapse
yes i see.but i'm newer android.i only send you link to fix
i hope have a pro android to fix your brick
This is just a shot in the dark because i didn't understand what you did entirely : have you used the combination to actually recover the stock rom after you flashed with KDZ ? (Home+VolDown+Power)
Yes already did. The computer can see the phone whenever I connect it except that I can't access adb. I may have to take this back to the store
vidgen13 said:
Yes already did. The computer can see the phone whenever I connect it except that I can't access adb. I may have to take this back to the store
Click to expand...
Click to collapse
Are you sure you flashed the right rom for your phone? There's an application that downloads the required rom for your phone according to your IMEI/SN, but i don't know if it works with the korean version.
Yes it's the KDZ file, unfortunately it's the only KDZ file out there for ku3700. Shouldn't have settled for this korean version
why you wanna downgrade the latest version?
Dude I have the same Korean edition as you.
Actually why you wanna downgrade the latest version.?
My phone had 2.2.2 and I did upgrade it into 2.3.4 I did it officially and I can tell you How to re-install 2.3.4 if you want.
asmOne said:
Dude I have the same Korean edition as you.
Actually why you wanna downgrade the latest version.?
My phone had 2.2.2 and I did upgrade it into 2.3.4 I did it officially and I can tell you How to re-install 2.3.4 if you want.
Click to expand...
Click to collapse
Thanks for the reply. I wanted to downgrade it to root it. And now I'm rooted. My only problem now is installing a custom recovery. I've already tried several custom recoveries:
recovery-RA-GNM-thunderg-1.1.0.img
recovery-RA-GNM-thunderg-2.2.1.img
recovery-RA-GNM-thunderg-3.0.6.img
but I get stuck at the LG logo when it reboots. I think it's because it's for the p500. So if you have a custom recovery for the ku3700 please help
I dont get it ,p504,p505,p506 are versions of p500??? And why some of our roms work on those phones?? So by logic this stock work on p500???
Sent from my LG-P500 using XDA Premium App
vidgen13 said:
Thanks for the reply. I wanted to downgrade it to root it. And now I'm rooted. My only problem now is installing a custom recovery. I've already tried several custom recoveries:
recovery-RA-GNM-thunderg-1.1.0.img
recovery-RA-GNM-thunderg-2.2.1.img
recovery-RA-GNM-thunderg-3.0.6.img
but I get stuck at the LG logo when it reboots. I think it's because it's for the p500. So if you have a custom recovery for the ku3700 please help
Click to expand...
Click to collapse
this method worked for my working KU3700 when I'm using my 1st KU3700 I also was struck as you and finely I realized there are No custom roms for Optimus one Korean edition (KU3700/SU370) and I had to connect my phone to an Octopus box (lg softwere box) via software box installed the official firmware. if this method not working you have to connect to a software box.
connect to the internet your PC and 1st install Driver and 2nd install the LG update tool. after installation connect your phone to computer and wait a five seconds for comport installation. after install your phone Run LG Update application.
it is connect to the server automatically indicating red line and after search for latest firmware.
if you can Update your phone it is shows Update butten.
Driver
http://www.4shared.com/file/C3BSNx9P/lgunitedmobiledriver_s4981man3.html
LG Update Tool
http://www.softpedia.com/get/Mobile-Phone-Tools/Others/LGMobile-Support-Tool.shtml
Thank you all for the quick answers, but I already have a rooted ku3700. All I need now is a working custom recovery. If someone has the same phone, please tell me which image is compatible
you can appear the emergency mood with android logo.
it means you have an Empty phone. your Os was been erased. You have to connect your phone to Octopus software box and box server has you original Os for your IMEI. this is the only solution. if you will able to solve this problem without a Software box please inform me. we can open a New Thread for Korean edition.
(ku3700/su370)
I already got out of the emergency mode without an octobus box. It's really simple, you just need to use a different kdz file. The hard part was looking for the kdz file. I have 3 kdz files. KU370017(froyo), KU370033(gingerbread-rootable), KU370040(latest one from LG, gingerbread-unable to root). Just flash with the KDZ updater. I'm on the second firmware because I can't root the latest firmware. To root it, I used super one click(latest version, use zerg rush option). Now I'm just waiting for a custom recovery from drellisdee so I can use custom roms. When I get it, I'll ask him if I can post it so we all can have uber phones LOL
Updated the thread. Can somebody help?
vidgen13 said:
Updated the thread. Can somebody help?
Click to expand...
Click to collapse
If you have flashed a working clockworkmod you can enter into clockworkmod via ROMManager (search in google play aka market). In ROMManager you have "reboot to recovery" option in case you want to go to recovery to flash something. Also you can try to flash from ROMManager a custom recovery (5.0.2.0 for oldBB or 5.0.2.7 for newBB), try to choose to phone model LGP500 oldBB, try and test if it's working. Wish you luck.
Thanks but I already have a working recovery. I just need some ROM makers now
vidgen13 said:
Thanks but I already have a working recovery. I just need some ROM makers now
Click to expand...
Click to collapse
Have you tried CM7.2? if your phone is very similar with Optimus One i doubt it isn't compatible with your phone.
If your phone use 2.6.35.10 or 2.6.35.14 kernel you can give a shot to try CM7.2 on your phone, but before try this make a backup first.
Check this thread Post Your CyanogenMod 7.2.0-RC1 Nightly Questions HERE!! for CM7 custom rom.
yep, it doesn't work. Is there a tutorial for building cyanogen for unsupported devices? All I can find are tutorials for supported devices. I've already got the source code from LG. The problem is just incorporating it in the cyanogen mod. I wish this phone had more users LOL
Had the phone for 2 weeks. without being rooted it is so boring! Please any devs come up with a custom recovery soon
htcmusic said:
Had the phone for 2 weeks. without being rooted it is so boring! Please any devs come up with a custom recovery soon
Click to expand...
Click to collapse
that's why i gave mine to my wife, she doesn't like root. not positive this device will really get alot of development.
fix-this! said:
that's why i gave mine to my wife, she doesn't like root. not positive this device will really get alot of development.
Click to expand...
Click to collapse
Guys the device was just launched. Right now I'm working on teaming up with Brinly Taylor so we can develop for this.
Moto e 3g Variant boot.img and recovery.img
give me the following and i will try to compile a custom recovery
- boot.img(from 3g variant)
-recovery.img(from 3g variant)
Saumitra Yadav said:
give me the following and i will try to compile a custom recovery
- boot.img(from 3g variant)
-recovery.img(from 3g variant)
Click to expand...
Click to collapse
I have this model. But when i try to extract boot.img from adb shell. it says access denied, and when i type su the it says not found . any idea how this can be resolved.
We seem to have a chicken and egg problem here. We need a custom recovery to get root, but we need root to get the bits to make a custom recovery. I'll try to make something when I have time, but I don't have a device to test with, so I'll need the community's help to test.
squid2 said:
We seem to have a chicken and egg problem here. We need a custom recovery to get root, but we need root to get the bits to make a custom recovery. I'll try to make something when I have time, but I don't have a device to test with, so I'll need the community's help to test.
Click to expand...
Click to collapse
Well i have this 3g variant of moto e 2015. I am ready to help but i am new to all this stuff. Yesterday i pulled system.img but can't pull boot image.
Ravx said:
Well i have this 3g variant of moto e 2015. I am ready to help but i am new to all this stuff. Yesterday i pulled system.img but can't pull boot image.
Click to expand...
Click to collapse
I made something. I have no clue if it will work. Things usually don't work on the first try, but we have to start somewhere. Try this at your own risk. I'm not responsible for bricking your phone. I don't have a Moto E 3G to test with.
As a good first test with this recovery, try flashing SuperSU: http://download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip?retrieve_file=1
TWRP for 3G Model only! Flash at your own risk! Completely untested first attempt!
Download link for my test recovery: http://www.mediafire.com/download/uple1nxzzpg1cb5/otus_twrp-2.8.6-untested.img
To install:
Code:
fastboot flash recovery otus_twrp-2.8.6-untested.img
EDIT: Don't use this image, it's too big and I've identified other issues.
Ravx said:
I have this model. But when i try to extract boot.img from adb shell. it says access denied, and when i type su the it says not found . any idea how this can be resolved.
Click to expand...
Click to collapse
This will be possible only when moto release sources,
squid2 said:
I made something. I have no clue if it will work. Things usually don't work on the first try, but we have to start somewhere. Try this at your own risk. I'm not responsible for bricking your phone. I don't have a Moto E 3G to test with.
As a good first test with this recovery, try flashing SuperSU: http://download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip?retrieve_file=1
TWRP for 3G Model only! Flash at your own risk! Completely untested first attempt!
Download link for my test recovery: http://www.mediafire.com/download/uple1nxzzpg1cb5/otus_twrp-2.8.6-untested.img
To install:
Code:
fastboot flash recovery otus_twrp-2.8.6-untested.img
Click to expand...
Click to collapse
I had someone try it and found out that the image is too big. I will post a smaller one that should fit when I find time. I'll need to create a stripped down kernel and device tree for otus. To do that, I'd probably need my own device to test on. The 3G model is unavailable in Canada, but for the sake of the community, I've ordered a 3G model from abroad, at a cost much greater than what it is worth, so that I have a unit to test on. My test unit won't arrive for another week I'd expect.
squid2 said:
I had someone try it and found out that the image is too big. I will post a smaller one that should fit when I find time. I'll need to create a stripped down kernel and device tree for otus. To do that, I'd probably need my own device to test on. The 3G model is unavailable in Canada, but for the sake of the community, I've ordered a 3G model from abroad, at a cost much greater than what it is worth, so that I have a unit to test on. My test unit won't arrive for another week I'd expect.
Click to expand...
Click to collapse
Thankyou so much squid bro, you are great . Please make a new thread for moto e 3g 2015 version in which all the development and testing work will be carried out. I thought that i have made wrong descision by buying Moto E 3g version because of no dev support. You are a life saver bro.....
As far as testing goes , I am in.....:good:
Ravx said:
Thankyou so much squid bro, you are great . Please make a new thread for moto e 3g 2015 version in which all the development and testing work will be carried out. I thought that i have made wrong descision by buying Moto E 3g version because of no dev support. You are a life saver bro.....
As far as testing goes , I am in.....:good:
Click to expand...
Click to collapse
Here goes my second attempt. I've tried to backport my Linux 3.10.74 based "Squid Kernel" to the 3G Moto E. This is a rather crazy idea, and I don't think anyone has ever done this for the MSM8x10 family. I've managed to create a kernel binary that is half the size of the stock kernel. I don't expect this recovery to boot at all. If it does boot, I would be quite pleased.
Download link for the adventurous: https://www.mediafire.com/?j5wgj035ml7nng9
I'd suggest first trying fastboot boot twrp-otus-2.8.6-test2.img before you flash it, since it is experimental and probably won't work. If it does boot, check the file manager to see if it is able to view all your data. If it boots and is able to see your data, then we have a miracle, so go ahead and flash it if you'd like.
If this recovery doesn't boot, don't worry, I will make a recovery that works, just be patient. I'm waiting for my test unit to arrive. It's been crawling along through the USPS. Hopefully, I'll have it by this time next week.
REMINDER: This is totally untested, and probably won't work. Try at your own risk. Make sure to try booting it with "fastboot boot" before flashing it. This might brick your device. Be careful. Even if it appears to work, I don't recommend flashing anything with this recovery until I receive my test device and properly verify it.
P.S. I'll make a new thread once I have something that works.
squid2 said:
Here goes my second attempt. I've tried to backport my Linux 3.10.74 based "Squid Kernel" to the 3G Moto E. This is a rather crazy idea, and I don't think anyone has ever done this for the MSM8x10 family. I've managed to create a kernel binary that is half the size of the stock kernel. I don't expect this recovery to boot at all. If it does boot, I would be quite pleased.
Download link for the adventurous: https://www.mediafire.com/?j5wgj035ml7nng9
I'd suggest first trying fastboot boot twrp-otus-2.8.6-test2.img before you flash it, since it is experimental and probably won't work. If it does boot, check the file manager to see if it is able to view all your data. If it boots and is able to see your data, then we have a miracle, so go ahead and flash it if you'd like.
If this recovery doesn't boot, don't worry, I will make a recovery that works, just be patient. I'm waiting for my test unit to arrive. It's been crawling along through the USPS. Hopefully, I'll have it by this time next week.
REMINDER: This is totally untested, and probably won't work. Try at your own risk. Make sure to try booting it with "fastboot boot" before flashing it. This might brick your device. Be careful. Even if it appears to work, I don't recommend flashing anything with this recovery until I receive my test device and properly verify it.
P.S. I'll make a new thread once I have something that works.
Click to expand...
Click to collapse
Ok probably a noob qiestion. But does booting recovery from adb makes any changes to my device. Is there a probabilty of soft bricking the device by this method.
And should the boot loader be unlocked before trying this.
Ravx said:
Ok probably a noob qiestion. But does booting recovery from adb makes any changes to my device. Is there a probabilty of soft bricking the device by this method.
And should the boot loader be unlocked before trying this.
Click to expand...
Click to collapse
You need an unlocked bootloader. First boot your device into bootloader mode (turn phone off, press and hold PWR and VOL- together for 3 seconds, then let go). You will see a bootloader menu. Then use fastboot on your computer to boot the recovery.
Running "fastboot boot xyz.img" will not make any changes to your device. As long as you don't flash anything with the recovery, it's fairly safe to try. Booting it up and browsing with the file manager shouldn't hurt anything. Note that when you try to leave recovery, TWRP will ask you if you want to root your device with SuperSU. If you want to be safe, read the screen carefully and make sure you say no for now.
The risky operation would be to flash the recovery (fastboot flash xyz.img) and then use the recovery to flash other ROMs or customizations. I would not recommend doing this if you don't have enough experience or are worried about messing up your phone.
squid2 said:
You need an unlocked bootloader. First boot your device into bootloader mode (turn phone off, press and hold PWR and VOL- together for 3 seconds, then let go). You will see a bootloader menu. Then use fastboot on your computer to boot the recovery.
Running "fastboot boot xyz.img" will not make any changes to your device. As long as you don't flash anything with the recovery, it's fairly safe to try. Booting it up and browsing with the file manager shouldn't hurt anything. Note that when you try to leave recovery, TWRP will ask you if you want to root your device with SuperSU. If you want to be safe, read the screen carefully and make sure you say no for now.
The risky operation would be to flash the recovery (fastboot flash xyz.img) and then use the recovery to flash other ROMs or customizations. I would not recommend doing this if you don't have enough experience or are worried about messing up your phone.
Click to expand...
Click to collapse
Sorry bro but it is not booting. The steps i followed
1.) unlocked bootloader ( Success ...getting unlock msg when booting
2.) got to bootloader.
3.)booted the recovery ( i changed the name of recovery to "recovery" for convinience)
4.) cmd showed msg booting but the phone shows android logo and does not act from there.
5. I had to reboot the phone by pressing power button for 10 secs.
Have i done anything wrong????
Ravx said:
Sorry bro but it is not booting. The steps i followed
1.) unlocked bootloader ( Success ...getting unlock msg when booting
2.) got to bootloader.
3.)booted the recovery ( i changed the name of recovery to "recovery" for convinience)
4.) cmd showed msg booting but the phone shows android logo and does not act from there.
5. I had to reboot the phone by pressing power button for 10 secs.
Have i done anything wrong????
Click to expand...
Click to collapse
It might just be that it doesn't work, but your comment about it showing the Android logo doesn't sound right. Does it show a "dead" android logo laying on its back with a door open on its body? If you see that, you booted up the stock recovery. The stock recovery will show that logo forever until you use a certain button combo to bring up a menu.
How did you boot the recovery? I assume you downloaded my file, renamed it to "recovery.img", and then ran this command from the folder that contains my recovery image:
Code:
fastboot boot recovery.img
squid2 said:
It might just be that it doesn't work, but your comment about it showing the Android logo doesn't sound right. Does it show a "dead" android logo laying on its back with a door open on its body? If you see that, you booted up the stock recovery. The stock recovery will show that logo forever until you use a certain button combo to bring up a menu.
How did you boot the recovery? I assume you downloaded my file, renamed it to "recovery.img", and then ran this command from the folder that contains my recovery image:
Code:
fastboot boot recovery.img
Click to expand...
Click to collapse
No it showed the logo of moto powered by android and yes i renamed the file and entered the same command you typed.
As soon as i typed it. It showed that logo and got hanged. And then i rebooted. And it booted normally.
Ravx said:
No it showed the logo of moto powered by android and yes i renamed the file and entered the same command you typed.
As soon as i typed it. It showed that logo and got hanged. And then i rebooted. And it booted normally.
Click to expand...
Click to collapse
I had someone else try it too, with the same result as you. No big surprise to me, didn't expect it to work. I'll make one with a more conventional 3.4.x kernel when I get time.
Otus TWRP Attempt 3
@Ravx
Alright everyone, I've made a third attempt at creating a recovery for the Moto E 3G. I still don't have the device, so you have to test yourself. I made this one with a more conventional 3.4.x kernel. I would guess that this recovery is more likely to work than the the previous one. As before, try fastboot boot xyz.img before flashing. I suspect that this recovery might boot sometimes and fail other times. If it fails to be boot the first time, try a couple more times before giving up.
Download Link: http://www.mediafire.com/download/1he2ys1832441s7/twrp-otus-2.8.6-test3.img
If it boots, try using the file manager. Check that it is able to see all your files. I don't recommended using this recovery to flash things until I'm able to verify it myself.
Try at your own risk. I'm not responsible for messing up your device. This recovery has not been tested.
squid2 said:
@Ravx
Alright everyone, I've made a third attempt at creating a recovery for the Moto E 3G. I still don't have the device, so you have to test yourself. I made this one with a more conventional 3.4.x kernel. I would guess that this recovery is more likely to work than the the previous one. As before, try fastboot boot xyz.img before flashing. I suspect that this recovery might boot sometimes and fail other times. If it fails to be boot the first time, try a couple more times before giving up.
Download Link: http://www.mediafire.com/download/1he2ys1832441s7/twrp-otus-2.8.6-test3.img
If it boots, try using the file manager. Check that it is able to see all your files. I don't recommended using this recovery to flash things until I'm able to verify it myself.
Try at your own risk. I'm not responsible for messing up your device. This recovery has not been tested.
Click to expand...
Click to collapse
Bro you have done it. the recovery booted and i moved a file from one folder to another by using file manager. :good::good::laugh:
EDIT: For now i the recovery's file manager isnt showing "build.prop" and other folders in /system
only the "bin" folder is visible. Is it ok beacaause we havent flashed the recovery or its the other way around.
Hello everyone this is my fist guide so be kind with the formatting, i will get better as I post more. I am writing this guide, because like you, the reader, I had installed lineageOS 14.1 and set up the phone and realized there was encryption on it, and with that tried to wipe it in twrp just to find out that it only wiped the encryption key, but not the encryption itself. Don't panic, it isn't all your fault, XD. Stay calm, the last thing you need is to be freaking out, flashing random zips in hopes of fixing it. I will give credit to all of the developers whose tools i am linking at the bottom.
Now that the introductions are out of the way, time for the complimentary dose of warning.
WARNING: Doing this won't guarantee that this will fix it, as every situation can vary. I am not responsible for any bricked devices, thermal reactors coming from your phone after this, or modding before it was cool.
Assuming you can still get into fastboot first you need to gather these files if you don't have them yet.
- Minimal adb and fastboot on windows after installing just drag to desktop to add files to it
- Qualcomm fastboot drivers for axon7tool.exe and for fastboot and adb
- TWRP 3.0.4-1 official for Axon 7
- B29 rollback modded zip on the second tab
- Nougat modem and bootstack
- Tenfar's axon7root.exe (just in case you can't use fastboot. that's what i used because i don't know how to use axon7tool.exe)
- Fastboot image to get fastboot working again flash it in twrp after getting twrp installed again through axon7root.exe
- Some time because this will likely take an hour of your time, assuming you have the drivers and files already downloaded, longer if not and slow internet.
- LineageOS 14.1
- GAPPS 7.1.1 ARM 64
- almost forgot, you also need a microsd card to store the files because we will be wiping your entire internal with this, so back up your lovely dank memes or forever hold the loss.
Step 0.5. if you don't have fastboot working flash the bootloader unlock file by drakenfx to get it working again. if you don't have twrp for whatever reason go to the guide for axon7root.exe linked above and reboot to edl mode by holding all buttons down and have your phone connected to computer to know you are there. there won't be a vibration to let you know, just your computer telling you it has a connected device. now flash twrp, by first renaming the recovery to recovery.img and putting it in the adb folder along with the the root exe and do 'axon7root.exe -p (insert your com number listed in device manager) -r' (without the ' obviously) and it should send the recovery. if it doesn't see your device. make sure you have the drivers installed and make sure you have put down your com number where i left the () at
Step 1. assuming your device boots to this beautiful screen. you need to go back to twrp and drag the B29 zip from your computer to your external sd card from mtp and go to mount and mount system read-only this is very important.
Step 2. flash the B29 modded and let it go through. this will take a few minutes. if the progress bar automatically jumps to the end, you didn't go read only.
Step 3. after it finishes reboot into system and let it set up your system, you can skip through because we will be resetting again anyhow.
Step 4. reboot back to recovery. you can do this by using that pesky bl unlocked message by pressing up on volume as soon as it shows and selecting recovery. there you can see you have stock recovery, don't panic this is what we need. select wipe data factory reset and let it do it
Step 5. go back and skip set up again and reboot to bootloader where you can now 'fastboot flash recovery recovery.img' to get back twrp.
Step 6. flash the nougat bootstack and modem i had you download. after flashing that, go to wipe: Advanced wipe. Select Dalvik, system, data, cache and swipe to wipe. this will format it as ext4 which is what is required to get to lineageOS
Step 7. flash lineageos 14.1 and your gapps category and wait to let it finish. Note, you don't have to flash the modem more than once after flashing lineageos, even for updating. just after leaving B29
Step 8. reboot to make sure your encryption problem is not there
Step 9. set up phone and profit.
If you have done everything right, you shouldn't have bricked and should be back to lineageos 14.1 with no further problems. If you skipped around and got yourself bricked, congratulations because i am not the best at fixing problems, and i can try to help, but you will be at the mercy of the Best devs this community has to offer.
Now to the part where I thank all the Devs who, without their tireless time and effort, would not have made this guide possible and development into this phone in the first place. @Unjustified Dev for the lineageOS build i use as my daily driver for now; you rock dude. ^^
@DrakenFX oh god where do i begin. for the bl unlock zip, B29 modded ota, inspiration to the rest of the community, etc.
@tenfar for the axon7root.exe tool used
@sixohtew for his constant help and advice with not only this guide, but with teaching me to build android. if you are interest in learning how to compile android for any device, he can probably help. he has a very fair deal and is amazing at what he does.
Thank you all for your copious hours of time spent in the building of each great tool and to the community as a whole. Everyone, these guys are amazing, even if i have only talked to one of them. Be sure to stop by and donate.
If i have left anyone's name out, please hit me up and i will add you to the credits, and to that i apologize.
Happy flashing!
I read through your guide several times. I'm missing the point here. At which step does the decryption get removed?
gpz1100 said:
I read through your guide several times. I'm missing the point here. At which step does the decryption get removed?
Click to expand...
Click to collapse
Sorry for delayed response, it gets removed when you do the factory reset in stock recovery. For some reason TWRP can't remove it from /data in nougat but stock recovery can in B29.
Wipe->Format Data in TWRP removes all encryption from /data and /sdcard. Did you try that before reinstalling the stock recovery? I've had weird experiences in the past with stuck encryption.
QuantumFluxx said:
Wipe->Format Data in TWRP removes all encryption from /data and /sdcard. Did you try that before reinstalling the stock recovery? I've had weird experiences in the past with stuck encryption.
Click to expand...
Click to collapse
I did try it. It doesn't wipe it because there is a bug with TWRP for our phone. I would wipe and even format data and it wouldn't work. If you go to the official TWRP thread it even warns you that if you have encryption to not wipe. We had a dev who wiped and it got rid of the encryption key and not the encryption, like what happened to me. I tried to wipe so many times and had to revert. Long process but I got my phone to work again
Rip me
So I was bricked to the point where I was able to access TWRP and if I flashed any ROM, even after formatting data, I would reach a Decryption unsuccessful screen on my A2017U. I followed the guide from step 0.5, since fastboot was not working. After flashing the bootloader unlock file via TWRP, I was not able to access anything, further bricking the device. It boots within a second to a black screen, and reboots to it if I hold the power button or any combination for recovery.etc. I can not go to EDL mode; Axon7tool detects it though when it is in this state, and is able to send files successfully. However, it still stays in this black screen. Is there any way to get back to a functioning phone at this point?
Edit: It is apparently always in EDL? It shows up and is identified by my PC as QUSB_BULK...
navsterama said:
So I was bricked to the point where I was able to access TWRP and if I flashed any ROM, even after formatting data, I would reach a Decryption unsuccessful screen on my A2017U. I followed the guide from step 0.5, since fastboot was not working. After flashing the bootloader unlock file via TWRP, I was not able to access anything, further bricking the device. It boots within a second to a black screen, and reboots to it if I hold the power button or any combination for recovery.etc. I can not go to EDL mode; Axon7tool detects it though when it is in this state, and is able to send files successfully. However, it still stays in this black screen. Is there any way to get back to a functioning phone at this point?
Edit: It is apparently always in EDL? It shows up and is identified by my PC as QUSB_BULK...
Click to expand...
Click to collapse
Can you still get into recovery with power & vol+? and what happened as soon as you flashed the zip?
twilighttony said:
Can you still get into recovery with power & vol+? and what happened as soon as you flashed the zip?
Click to expand...
Click to collapse
Nope :crying:. The EDL combo and the recovery combo result in the same screen and duration of boot. After flashing the bootloader unlock file, I remember reading the script to see that it was successful and yielded a result of 1 before resulting in this screen.
navsterama said:
Nope :crying:. The EDL combo and the recovery combo result in the same screen and duration of boot. After flashing the bootloader unlock file, I remember reading the script to see that it was successful and yielded a result of 1 before resulting in this screen.
Click to expand...
Click to collapse
I am not sure what happened to that, were you originally on B15? i was simply on the modem/bootstack which allowed me to succeed in flashing that file. that could be a variable. i will be sure to look into a tool ive heard of called miflash which works through edl mode to unbrick.
navsterama said:
Nope :crying:. The EDL combo and the recovery combo result in the same screen and duration of boot. After flashing the bootloader unlock file, I remember reading the script to see that it was successful and yielded a result of 1 before resulting in this screen.
Click to expand...
Click to collapse
try this.
twilighttony said:
I am not sure what happened to that, were you originally on B15? i was simply on the modem/bootstack which allowed me to succeed in flashing that file. that could be a variable. i will be sure to look into a tool ive heard of called miflash which works through edl mode to unbrick.
Click to expand...
Click to collapse
Yea, I was on B15. Trying miFlash right now though. I'll update you when its done...:good:
navsterama said:
Yea, I was on B15. Trying miFlash right now though. I'll update you when its done...:good:
Click to expand...
Click to collapse
ok that does make sense as to why it failed. i was on the modded modem file that allowed me to install los
twilighttony said:
ok that does make sense as to why it failed. i was on the modded modem file that allowed me to install los
Click to expand...
Click to collapse
Wait...in terms of the bootstack I was also on the modded one for LOS 14.1. However, it was when the last unofficial build came out (Feb 3rd???). I tried to clean flash LOS Weekly today and thats when I ran into the dilemma of the decryption. Idk why I said yes for being on B15, for some reason that translated to generally Nougat bootstack in my head. My bad, OP.
---------- Post added at 10:47 PM ---------- Previous post was at 10:30 PM ----------
navsterama said:
Yea, I was on B15. Trying miFlash right now though. I'll update you when its done...:good:
Click to expand...
Click to collapse
Unbricked, booted up, now its on the "beautiful" screen. Thanks!
twilighttony said:
try this.
Click to expand...
Click to collapse
This is posted in the dev section. No need for external linkage.
navsterama said:
Wait...in terms of the bootstack I was also on the modded one for LOS 14.1. However, it was when the last unofficial build came out (Feb 3rd???). I tried to clean flash LOS Weekly today and thats when I ran into the dilemma of the decryption. Idk why I said yes for being on B15, for some reason that translated to generally Nougat bootstack in my head. My bad, OP.
---------- Post added at 10:47 PM ---------- Previous post was at 10:30 PM ----------
Unbricked, booted up, now its on the "beautiful" screen. Thanks!
Click to expand...
Click to collapse
glad that worked. perhaps i will edit the guide to where fastboot is added at the end as an extra. seems that if we at least have twrp we can go from there. do you still have an unlocked bl?
lafester said:
This is posted in the dev section. No need for external linkage.
Click to expand...
Click to collapse
will remember for future reference. thanks
lafester said:
This is posted in the dev section. No need for external linkage.
Click to expand...
Click to collapse
At least the poster of the blog gives credit to the original author and thread.
The method referenced at the blog is confusing though. If one is in a bricked state (edl only), they can't access developer options or even boot into android.
gpz1100 said:
At least the poster of the blog gives credit to the original author and thread.
The method referenced at the blog is confusing though. If one is in a bricked state (edl only), they can't access developer options or even boot into android.
Click to expand...
Click to collapse
If you are in edl only with an unlocked bootloader than the part of enabling bl unlock won't apply.
twilighttony said:
If you are in edl only with an unlocked bootloader than the part of enabling bl unlock won't apply.
Click to expand...
Click to collapse
Right, I understand that, but the person reading your blog won't, and thus the confusion.
This guide really needs to be stickied or higher up. Restarted my phone yesterday and it randomly got encrypted upon booting. Was locked out of everything and no keyboard was popping up to be able to put in a PIN or Password. This guide saved me. Thank you.
Hi all,
tl;dr: Tried to hard unbrick my Oneplus X, which was partly succesful (no OS is installed in the process, while there should be). I am now stuck with no OS and only the Oneplus recovery. I want to install an OS, but it says my bootloader is locked. To unlock it, I need an OS ==> vicious circle.
Full story below:
Recently I've decided to reinstall LineageOS on my Oneplus X because I had quite some problems with it (battery drain, apps crashing, wifi slow to connect, ...). I've done it like 5 times before on this device for various reasons, so I didn't expect any problems. I had LineageOS 14.1 and TWRP 3.0.3 installed. When I wiped everything, I wanted to flash the ROM I had ready using TWRP. However, gave an error number 7, saying that the ROM is not compatible for the device, which I am sure was. Remembering I had a similar issue a while back, I installed flashed an updated version of TWRP (3.2.2) using TWRP itself. That was successfull, but here's where the trouble began.
I noticed that TWRP didn't recognise any storage (Internal storage, SD card and USB-OTG all showed up as 0 MB) any longer. Neither could I mount any of the storages. I've tried a lot of things to solve this. After a while, I decided that the only hope left was the 'mega unbrick guide' (https://forums.oneplus.com/threads/guide-mega-unbrick-guide-for-a-hard-bricked-oneplus-x.417648/) which claims to be able to recover any device, unless it has a hardware problem. I got good hope as I got near the end of the guide. The last step says 'Disconnect phone from PC and boot into system', but here I got stuck on the Oneplus boot logo, making me think that there is no OS installed on the device.
I can still access the recovery using power button and volume down, but the recovery that the mega unbrick guide installs, is the limited Oneplus recovery. It allows to install a ROM from the local storage, or from USB using adb sideload. When I try option 1, nothing happens, no new screen opens or anything. When I try option 2, I enter the adb sideload mode which would normally allow me to sideload a ROM using my pc. My pc confirms I'm in adb sideload mode, and I try to sideload a ROM. It starts fine, but after a few seconds, it says 'Installation failed'. I've tried stock OOS, latest OOS as well as LineageOS 14.1 that was installed before.
Another thing that I can do in the Oneplus recovery is rebooting into fastboot mode, where I should be able to flash the recovery of my choice. Again, my phone confirms I'm in fastboot mode and I try to flash or boot TWRP recovery, but I get the message: 'FAILED (remote: Device not unlocked cannot flash or erase)'. Okay, seems like the bootloader is still locked, so I should just go and unlock it using 'fastboot oem unlock'. This gives the message: 'FAILED (remote: oem unlock is disabled)'. I've been searching around a lot on the internet, and it seems like the only way to enable oem unlock, is in the OS itself in the developer settings. But the problem is, I have no OS and cannot install one because the bootloader is not unlocked... So I'm stuck in this vicious circle.
I've been searching on the internet for hours and starting to lose hope. At this point, I would be happy if I can just have any OS (OxygenOS or LineageOS or something else) running. If I have that, I should be able to take it from there.
Any help is much appreciated. Thank you very much.
Kind regards,
Jeroen
Bump
Update:
Oneplus support could solve the problem for me! Or at least, partly. It appears that Oneplus has an updated version of the tool used in the mega unbrick guide: MSMDownloadTool V2.1 instead of V2.0. This tool did it's job perfectly, OOS was also installed, in contrast to V2.0 of the tool. I ****ed it up again after that (oops), but found the tool V2.1 online here (https://github.com/finlayacourt/Oneplus-X-Recovery). Some files are missing here like the system.img, but I just copied them from the folder of tool V2.0 found in the mega unbrick guide. It didn't work as perfectly as Oneplus's tool, but at least I was able to install OOS from the Oneplus bootloader, which I wasn't able to before. So knowing that, in the end, the result is the same as for their tool. A working OS again, perfect! So now I can unlock the bootloader again and continue the adventure.
Now, what I've found is that the mainboard I have on my OPX is a newer version (if you search on Google for 'oneplus E1003_15', you'll find some things about it, not much though). I'm 99% positive that this caused all the problems I've encountered. It is why TWRP couldn't see any storage, why the stock Oneplus recovery couldn't see any storage, why the tool V2.0 didn't work and why V2.1 did work. If I wanted a working TWRP, I had to install a modified version of TWRP which is compatible with the newer version, from here: https://www.android-hilfe.de/forum/...-1-oreo-rom-unofficial-onyx-8-1-x.867374.html (yes, once you're relying on German sites, you know you went very deep). After that, I could install LineageOS 14.1 again. I was unable to install the unofficial LineageOS 15.1 however, but knowing where I came from, what I've gone through and how much time I've lost on all of this, I think I'll just stick with LineageOS 14.1 until this baby can retire...
Got to say I only have very positive experiences with Oneplus and it's customer support, and this only adds to it!
I hope I can also help other people with the same problem.
Japeroen said:
Update:
Oneplus support could solve the problem for me! Or at least, partly. It appears that Oneplus has an updated version of the tool used in the mega unbrick guide: MSMDownloadTool V2.1 instead of V2.0. This tool did it's job perfectly, OOS was also installed, in contrast to V2.0 of the tool. I ****ed it up again after that (oops), but found the tool V2.1 online here (https://github.com/finlayacourt/Oneplus-X-Recovery). Some files are missing here like the system.img, but I just copied them from the folder of tool V2.0 found in the mega unbrick guide. It didn't work as perfectly as Oneplus's tool, but at least I was able to install OOS from the Oneplus bootloader, which I wasn't able to before. So knowing that, in the end, the result is the same as for their tool. A working OS again, perfect! So now I can unlock the bootloader again and continue the adventure.
Now, what I've found is that the mainboard I have on my OPX is a newer version (if you search on Google for 'oneplus E1003_15', you'll find some things about it, not much though). I'm 99% positive that this caused all the problems I've encountered. It is why TWRP couldn't see any storage, why the stock Oneplus recovery couldn't see any storage, why the tool V2.0 didn't work and why V2.1 did work. If I wanted a working TWRP, I had to install a modified version of TWRP which is compatible with the newer version, from here: https://www.android-hilfe.de/forum/...-1-oreo-rom-unofficial-onyx-8-1-x.867374.html (yes, once you're relying on German sites, you know you went very deep). After that, I could install LineageOS 14.1 again. I was unable to install the unofficial LineageOS 15.1 however, but knowing where I came from, what I've gone through and how much time I've lost on all of this, I think I'll just stick with LineageOS 14.1 until this baby can retire...
Got to say I only have very positive experiences with Oneplus and it's customer support, and this only adds to it!
I hope I can also help other people with the same problem.
Click to expand...
Click to collapse
Greatly appreciate your feedback here. I think that I am in the same situation you were. Used what you suggested - using MSM v2.1 that you provided with the system.img, non-hlos and userdata.img from MSM v2.0. The process ends with "Download Complete" written in green but when I check "Verify" it fails exactly @system.img, userdata and non-hlos. I can't boot recovery either after these.
Do you have any clue as to why it is so?
gabytzu338 said:
Greatly appreciate your feedback here. I think that I am in the same situation you were. Used what you suggested - using MSM v2.1 that you provided with the system.img, non-hlos and userdata.img from MSM v2.0. The process ends with "Download Complete" written in green but when I check "Verify" it fails exactly @system.img, userdata and non-hlos. I can't boot recovery either after these.
Do you have any clue as to why it is so?
Click to expand...
Click to collapse
As far as I know, I haven't used the "Verify" button. Right after the green "Download Complete" line, I booted into the OOS stock recovery by pressing volume down and power button (I think? Not sure anymore, I always forget it). From there, I could install OOS with a official ROM image.
Are you sure you moved the correct files from V2.0 to V2.1? The way I knew which files to move, is by first starting the V2.1-program without any added files. Then it told me 'system.img missing' (or something like that), so I knew I had to add that. After adding that, I ran the program again and added the next file it said it was missing etc etc.
Sucks to hear your recovery process doesn't go as "smooth" (it's all relative of course) as mine.
Japeroen said:
As far as I know, I haven't used the "Verify" button. Right after the green "Download Complete" line, I booted into the OOS stock recovery by pressing volume down and power button (I think? Not sure anymore, I always forget it). From there, I could install OOS with a official ROM image.
Are you sure you moved the correct files from V2.0 to V2.1? The way I knew which files to move, is by first starting the V2.1-program without any added files. Then it told me 'system.img missing' (or something like that), so I knew I had to add that. After adding that, I ran the program again and added the next file it said it was missing etc etc.
Sucks to hear your recovery process doesn't go as "smooth" (it's all relative of course) as mine.
Click to expand...
Click to collapse
Hah, did not expect an answer, I've seen your thread on oneplus forums as well, glad you were so quick to answer here. I've found the MSM2.1 uploaded in a google drive with all the files afterwards, after some long hours of searching too. Anyway, I still can't adb sideload anything, the storage seems 'corrupted' to say the least, but there are imporvements from MSM v2.0 and v3.0 flahses. The recovery menu works flawlessly now, no artifacts or freezes, also the phone 'almost' booted. It went to the "Updating android apps" thing.
I don't really know what to do next. Recovery does not help me at all. I can't sideload anything, it renders a "protocol fault" error. Internal storage has 2 empty folders within and that's about it. Also the bootloader is locked now and I can't make any use of fastboot mode.
gabytzu338 said:
Hah, did not expect an answer, I've seen your thread on oneplus forums as well, glad you were so quick to answer here. I've found the MSM2.1 uploaded in a google drive with all the files afterwards, after some long hours of searching too. Anyway, I still can't adb sideload anything, the storage seems 'corrupted' to say the least, but there are imporvements from 2.0 and 3.1 flahses. The recovery menu works flawlessly now, no artifacts or freezes, also the phone 'almost' booted. It went to the "Updating android apps" thing.
I don't really know what to do next. Recovery does not help me at all. I can't sideload anything, it renders a "protocol fault" error. Internal storage has 2 empty folders within and that's about it. Also the bootloader is locked now and I can't make any use of fastboot mode.
Click to expand...
Click to collapse
Haha I know the feeling! But thanks to e-mail notifications.
I also thought that my storage was corrupted at first, given the symptoms I described in my first post, so I didn't expect my OPX to be revived, but hey it's still alive now.
I also had the locked bootloader-thing. The way I could unlock it, is by first installing OOS using the stock recovery (which was installed using the tool), then unlocking it in OOS, so I could install another recovery and eventually another OS.
I'm afraid I already explained the problems I encountered and the procedure I followed pretty detailed. If you have anything that deviates from this, I'm sorry to say that I can't really help you with that, even if I wanted to. Did you perform the exact steps I mentioned (including the V2.1-tool that I linked to)? What exactly do you mean with the "3.1 flash"?
It's also already 2 months ago, so I don't even know exactly what I've done apart from what I've described...
Japeroen said:
Haha I know the feeling! But thanks to e-mail notifications.
I also thought that my storage was corrupted at first, given the symptoms I described in my first post, so I didn't expect my OPX to be revived, but hey it's still alive now.
I also had the locked bootloader-thing. The way I could unlock it, is by first installing OOS using the stock recovery (which was installed using the tool), then unlocking it in OOS, so I could install another recovery and eventually another OS.
I'm afraid I already explained the problems I encountered and the procedure I followed pretty detailed. If you have anything that deviates from this, I'm sorry to say that I can't really help you with that, even if I wanted to. Did you perform the exact steps I mentioned (including the V2.1-tool that I linked to)? What exactly do you mean with the "3.1 flash"?
It's also already 2 months ago, so I don't even know exactly what I've done apart from what I've described...
Click to expand...
Click to collapse
It was a typo, I meant v2.0 and v3.0(for oneplus 3). The op3 unbrick guide suggested that the v3.0 might work for oneplus x as well, so I tried that out too.
Anyway, I've done the process a couple more times and the phone booted untill you set the device up, when you are finished it just reboots. I can see the lock screen, I can't bring down the upper bar or enter the settings, if unlocked it prompts me to the first time set up and upon it's completion the phone reboots. I wiped cache,data did a factory reset. Now it's back with the recovery menu artifacts and not booting anymore either. I will use that tool a couple more times then I am done until further suggestions from this forum. After all, my life does not depends on reviving it, I was gonna give it to my brother, who shattered his phones' touchscreen, until he repairs his. Thank you again for replying, no need to reply to this, unless it can help my case.
Something really weird happened while I was installing roms. Someone how my OEM got locked and I flashed and voila stuck on the oneplus logo. I have my fastboot working properly also got twrp installed. The thing is that my bootloader is locked so i cant flash and I cant unlock bootloader because I cant flash and set oem unlock. I know this is ****ed up and also my volume up key is not working so we have to work without that. . Whenevr i turn on the device the powered by android quickly disappears and i am in the fastboot. If I do oem unlock it sends me to the recovery. I am not sure why i can't OEM unlock in fastboot. I don't care about data and stuff. Just want the phone working. The unbrick guide wants me to press the volume up key to get to the qualcomm flashing. Unfortunately i can't do that. Need of dire help please ;_;
I kind of have the same problem as of 2 days (see https://forum.xda-developers.com/android/help/bricked-oneplus-x-unlock-bootloader-t3816387), which is kind of strange, as I haven't read anywhere else about it on the internet.
I'll be following this topic.
Japeroen said:
I kind of have the same problem as of 2 days (see https://forum.xda-developers.com/android/help/bricked-oneplus-x-unlock-bootloader-t3816387), which is kind of strange, as I haven't read anywhere else about it on the internet.
I'll be following this topic.
Click to expand...
Click to collapse
I've solved it bud. IF you have a working recovery and bootloader. Flash the stock OS. It'll flash even though the bootloader is locked and then your can oem unlock and do whatever.
KenSha105 said:
I've solved it bud. IF you have a working recovery and bootloader. Flash the stock OS. It'll flash even though the bootloader is locked and then your can oem unlock and do whatever.
Click to expand...
Click to collapse
That's good news! But I think I've tried that, but had no succes. Can you link me the ROM you've flashed?
Japeroen said:
That's good news! But I think I've tried that, but had no succes. Can you link me the ROM you've flashed?
Click to expand...
Click to collapse
https://downloads.oneplus.com/oneplus-x/oneplus_x_oxygenos_3.1.4/
There.
KenSha105 said:
https://downloads.oneplus.com/oneplus-x/oneplus_x_oxygenos_3.1.4/
There.
Click to expand...
Click to collapse
Thank you. I've tried it, but the problem is that I'm stuck with the Oneplus recovery, as I've mentioned in my post. From there, I have 2 options to flash:
1) from internal memory. When I click this, nothing happens (no new screen or anything, nothing)
2) from USB (adb sideload). When I try to sideload the ROM using this option, it starts promising, but after a few seconds, it just says 'Installation failed' without any reason why. Just like for all other ROMS.
So... No progress here. I've also tried to flash the stock recovery (even though it should be on my phone already, maybe another version) using fastboot, but my OPX won't take it because the bootloader is still locked.
Last resort: I'll try the Oneplus live chat tomorrow, but I do not expect any useful information from that...
Japeroen said:
Thank you. I've tried it, but the problem is that I'm stuck with the Oneplus recovery, as I've mentioned in my post. From there, I have 2 options to flash:
1) from internal memory. When I click this, nothing happens (no new screen or anything, nothing)
2) from USB (adb sideload). When I try to sideload the ROM using this option, it starts promising, but after a few seconds, it just says 'Installation failed' without any reason why. Just like for all other ROMS.
So... No progress here. I've also tried to flash the stock recovery (even though it should be on my phone already, maybe another version) using fastboot, but my OPX won't take it because the bootloader is still locked.
Last resort: I'll try the Oneplus live chat tomorrow, but I do not expect any useful information from that...
Click to expand...
Click to collapse
Well guess what, they could solve it.
Or at least partly. It appears that Oneplus has an updated version of the tool used in the mega unbrick guide: MSMDownloadTool V2.1 instead of V2.0. This tool did it's job perfectly, OOS was also installed, in contrast to V2.0 of the tool. I ****ed it up again after that (oops), but found the tool V2.1 online here (https://github.com/finlayacourt/Oneplus-X-Recovery). Some files are missing here like the system.img, but I just copied them from the folder of tool V2.0 found in the mega unbrick guide. It didn't work as perfectly as Oneplus's tool, but at least I was able to install OOS from the Oneplus bootloader, which I wasn't able to before. So knowing that, in the end, the result is the same as for their tool. A working OS again, perfect! So now I can unlock the bootloader again and continue the adventure.
Now, what I've found is that the mainboard I have on my OPX is a newer version (if you search on Google for 'oneplus E1003_15', you'll find some things about it, not much though). I'm 99% positive that this caused all the problems I've encountered. It is why TWRP couldn't see any storage, why the stock Oneplus recovery couldn't see any storage, why the tool V2.0 didn't work and why V2.1 did work. If I wanted a working TWRP, I had to install a modified version of TWRP which is compatible with the newer version, from here: https://www.android-hilfe.de/forum/...-1-oreo-rom-unofficial-onyx-8-1-x.867374.html (yes, once you're relying on German sites, you know you went very deep). After that, I could install LineageOS 14.1 again. I was unable to install the unofficial LineageOS 15.1 however, but knowing where I came from, what I've gone through and how much time I've lost on all of this, I think I'll just stick with LineageOS 14.1 until this baby can retire...
Got to say I only have very positive experiences with Oneplus and it's customer support, and this only adds to it!