Related
Long story short, bootloader is stuck. -- Phone is stuck in a boot-loop of sorts ... it keeps showing the very first screen that shows the Galaxy name and some other info and then flashes that screen over and over again. It is not a boot-loop that loads the OS and keeps loading that continuously. From what I know about phones/programming, which is limited, the bootloader either doesn't exist anymore or the code is not executing properly.
I know there are guides that are similar to my issue, but none of them seem to answer my questions specifically. And when I have attempted some other fixes, nothing happens. I am hoping for a direct answer if anyone has one.
Here's what led to this:
1. I wanted to install the new Android Revolution rom which suggested I have the MJ5 bootloader. I have not attempted to install this rom yet, my issue occurred when I tried to flash the new bootloader.
2. Followed a thread that explained bootloaders and how to install mj5 on note 2 via Odin. --> then got this boot-loop. MD5 and all that jazz was fine. Downloaded from reputable source too.
3. I was/am running a custom rom (JellyBeans build 26 I think) with TWRP recovery. I was previously running CWM recovery, but switched to TWRP because the guide suggested TWRP or Philz recovery for MJ5. Switch between recoveries went just fine. Also, I don't remember what bootloader was installed before I broke it.
I am not a developer (obviously), but I am fairly computer savvy. I can do most things if explained properly. Although I am prone to being an idiot so if someone is feeling a little helpful a step-by-step guide may be best.
I am hoping that someone could (1) provide me with a how-to fix this issue, (2) provide me with a link to the right bootloader that I need to flash in ODIN in order to fix this issue.
PLEASE HELP! I am waiting for some job interview calls this upcoming week and I will be F***ed without my phone. I know it's my fault that the phone is stuck, but I know one of you geniuses here will be able to provide me with some information.
In Summary:
Bootloader is stuck
Phone can get into Download mode, but that's it.
Odin will connect and phone shows up on COM port.
I am an idiot.
I am fine going back to stock recovery/build if necessary to fix this issue.
Thank you all in advance.
P.S. Soul is available upon resolution of the issue; shipping and handling extra ; ) If you don't want my soul I will send you a holiday card with my dogs on it.
You flashed a bootloader for a different phone. Mj5 is for the n7100. The Verizon Note 2 is i605. You have 2 options to get your phone back to 100%. Either use kobols unbrick method found in the general section or send it off to mobiletechvideos and pay them to get it working.
Here is a link to kobol's method: http://forum.xda-developers.com/showthread.php?t=2615587
BluGuy said:
You flashed a bootloader for a different phone. Mj5 is for the n7100. The Verizon Note 2 is i605. You have 2 options to get your phone back to 100%. Either use kobols unbrick method found in the general section or send it off to mobiletechvideos and pay them to get it working.
Here is a link to kobol's method: http://forum.xda-developers.com/showthread.php?t=2615587
Click to expand...
Click to collapse
Thank you for the reply, I will try this now. I saw this thread but was hoping I wouldn't have to do this because of its requirements (screwing with the hardware and such).
Like I said, I'm an idiot.
Thank you for the tip though, it is much appreciated.
axpaxp said:
Thank you for the reply, I will try this now. I saw this thread but was hoping I wouldn't have to do this because of its requirements (screwing with the hardware and such).
Like I said, I'm an idiot.
Thank you for the tip though, it is much appreciated.
Click to expand...
Click to collapse
axpaxp,
You may try the method in this thread: How To: Unbrick A Hard Bricked i605 [n7100 Bootloader Flash] NO Resistor , as an alternative to Kobol's method.
THIS IS A CLOSED CASE, GO HOME. The answer is Hairybean found in step 2 of here [ROM] [TF201] KatKiss 5.1.1 - v30 [MultiWindow] [Stable] [RRO] Read the rest of this post if you're a sadist or want to know of people in the same pain boat as you.
Part 1: My life's story. Skip to Update if you just want to hear of my current problem.
So approximately 12 hours ago, I decided, "Hey, I want to upgrade my tablet so I can download the newest and coolest apps. Since I need to upgrade to a newer OS (ICS>KK ?) I may as well go through the extra hurdle and download a nice, fast custom ROM because the stock feels like crap for the lightweight that is the TF201."
Now me, not having ever touched an android in my life before this tablet, knew this was going to be a challenge. After doing plenty of research into unlocking, flashing a custom recovery, general custom ROM flashing etiquette, and following this guide ([ROM] [MM 6.0.1] KatshMallow v29 [TF201]), I encountered my first of many hurdles. This being: I was able to boot just fine, but the Wifi was in a perpetual state of "Wifi turning on..." I put a total of a couple or so hours into researching this and easily found others having the same issue, albeit not specifically to the exact ROM and device in question. I also tinkered a bit in these hours, reflashing and rebooting and all that jazz. I eventually settled upon one of three conclusions:
The "/persist" folder had gotten deleted which contains vital wifi/network configuration data
wlan0 was borked on a hardware level and I managed to completely kill an hope of wifi on my device
There was a MAC address somewhere that I needed to manually edit (that WASN'T in the persist file)
Considering the fact that I could not see nor change directory via adb terminal (yes, with su) into a "/persist" folder, and that the hardware-broken devices other users had were most if not all cellphones, I pushed on ahead assuming #1 to be my problem. ("See" includes dropping and installing a file explorer onto the tablet as well.)
With this is mind, the next course of action was to somehow get this "/persist" folder back. It seemed like the best way to do this would be to flash a stock ROM (link in Part 2) or ask the community to give me files without even trying to solve things on my own. So in the spirit of remaining a lurker I chose the former. Flashed fine, booted fine, ran.... okay-ish (the status bar "System UI" would crash every 10 seconds, ROM was a means to an end so I didn't care), but the Wifi WORKED! However, I still didn't find a /persist folder and the tablet didn't show up in windows... "Weird but okay, whatever let's do this." Load up recovery again, wipe everything, see if I can get Katshmallow to load again...
Part 1.5: And here we are. tl;dr I'm a scrub at anything android and after 12+ hours of tom****ery, I'm in a bootloop using Katshmallow v29 (v27 made no difference). The "bootloop" is in the form of the ASUS logo appearing with the usual "UnLocked" message in the top for a minute or two, then a reset, rinse, repeat. I am able to boot into recovery and mess around in TWRP just fine, so my ignorance hasn't completely wrecked me... yet.
The information that I believe is most pertinent to my current issue is:
I unlocked using ASUS' utility for the TF700. It worked no problem and with how compatible things seem to be between the two, I don't think this is an issue (especially considering I've flashed and booted system more-or-less just fine).
The most recent ROM I flashed was this [ROM] TF201 JB JRO03C 10.4.2.15 (US) Stock Deodexed + Mods [Unlocked BL]. I figure that this did something (maybe changed the bootloader?) that Katshmallow does not agree with. If I hadn't already spent the better half of a day working on trying to get things working, maybe I would do more research and figure out the inner workings on my own, but I'm done bashing my head against a brick wall that's only pushing me further back.
I am currently running KANG TWRP 2.8.7.2 for the TF201T (yes, the device I'm specifically running). The problem existed with some TWRP 2.8.x for the TF300 as well.
The bootloader message is "Android card-hu-user bootloader <1.00e> released by "US_epad-10.4.2.15-20120917" A03 ... Oh son of a-
Part 2: So I'm a dumb*** who can't read. Okay, I need to know how to get from my current bootloader (10.4.2.15) to the one Katshmallow requires (10.6.1.27.1). In typing this, I realized that the stock ROM I used to test stuff is why I've been screwed for the past 5 hours (coupled with my ignorance of course). In my quick 2 minutes of research I found this: [GUIDE][13/11]Update/Recovery/Root/Downgrade Android 4.2.1 on Unlocked/Locked Devices. I fancy methods 2 and 3, I can do those, but that doesn't change the fact that I know NOTHING about the bootloader and what I need to update it (but apparently I know how to give myself a headache by downgrading it).
Any help will be greatly appreciated. Oh, and if you know of how to solve the Wifi issue or the likely related /persist folder issue in the wall of text above, please I beseech you to tell me.
Disclaimer: My "research" is not at all limited to the links in the post. I've spent 90% (or more) of what's now probably 13-14 hours working on getting this piece of- getting things to just go right. So... tired...
Update: The problem has changed to my second post that I will be pasting here to save people the trouble:
So the problem as it stands now. I'm cannot seem to flash a different custom recovery and whenever I try to flash a ROM I get "E:Error executing updater binary in zip" The line above it, "symlink: some symlinks failed". I give up for now... Maybe I'll try again tonight. I'm running bootloader 10.4.2.15 and TWRP KANG 2.8.7.2 (which seems to require a 14.10 bootloader). In this mess, I don't know what to fix nor how to fix it. The angles I see are fix the custom recovery or fix the error/symlink problem since the bootloader version seems to be dependent on successfully flashing ROMs.
Update2: So I managed to upgrade the bootloader by somewhat forcefully flashing Hairybean. While Katshmallow said "JB 4.2.1 BOOTLOADER VERSION 10.6.1.27.1," I glazed over this because I didn't know the importance of the bootloader and there was no other mention of the bootloader in the post (no mention of Hairybean or a download link or a "More information" link). I still have no one but myself to blame, just bitter that I have to blame myself in the first place.
For the time being, I'm following the somewhat better instruction on found in this thread([ROM] [TF201] KatKiss 5.1.1 - v30 [MultiWindow] [Stable] [RRO]) and will be picking up Katshmallow at the "wipe" step (currently waiting on the /data format). I downloaded the newest version of TWRP for TF201T and it's working just fine (note how that thread also doesn't mention anything aside from "MUST BE ON THE HAIRYBEAN BOOTLOADER ENDING IN 27.1" While that's such an obvious and blatant statement that should have inspired some research, my ignorance blinded me).
Now that I know for a fact that I am running the right TWRP and the right bootloader, I am going to pray that I can at VERY LEAST flash and boot into Katshmallow. Whether or not the Wifi problem persists will be for another thread.
IT BOOTS! YAAASSS. How do I close this embrassment of a thead?
Sorry I can't be of more help but what I CAN say is:
- read instructions thoroughly with any release. Sometimes a modified TWRP or other file is posted that you must use even if you have a newer version. You might also have to bounce around to other posts along the way to install/update all of the necessary files.
- keep a written log of changes you've made with notes on reversing them. Changing the bootloader means you can't go back unless you revert it back first. I can back track everything I've done based on my own notes, much easier to understand than someone else's notes or directions.
Good luck and be patient. Don't make more than one change at a time and get it working or revert back before trying something totally different.
Sent from my LG-H811 using Tapatalk
HorthLithperer said:
Sorry I can't be of more help but what I CAN say is:
- read instructions thoroughly with any release. Sometimes a modified TWRP or other file is posted that you must use even if you have a newer version. You might also have to bounce around to other posts along the way to install/update all of the necessary files.
- keep a written log of changes you've made with notes on reversing them. Changing the bootloader means you can't go back unless you revert it back first. I can back track everything I've done based on my own notes, much easier to understand than someone else's notes or directions.
Good luck and be patient. Don't make more than one change at a time and get it working or revert back before trying something totally different.
Sent from my LG-H811 using Tapatalk
Click to expand...
Click to collapse
Thank you for replying nonetheless. I'll keep the note thing in mind. Regarding the bouncing around to get the files necessary, I've done plenty of that. When installing a new ROM, I made sure to follow the links as they were given and did further research where things weren't clear. My current problem stems from that fact that, 1: I have no point in which to restore back to due to my aforementioned ignorance and oversight of basic Android terminology; and 2: The next step is to revert the bootloader, that of which I have no clue how to do or where to start since my preliminary google search. Even if I had been taking notes, no one mentions how to do this without a backup. And so I'm on a hunt to find this information and for posterity, I'll post my quest here:
Google search: "tf201 bootloader version"
Upgrading from ICS Bootloader > [ROM] [TF201] [JB Bootloader] CyanogenMod 10 Unofficial - JZO54K - Oct 30 2012 - I learned that apparently certain ROMs can overwrite the bootloader, extrapolated from:
4) Needs the new Jelly Bean 10.4.2.15 bootloader [IMPORTANT: Flashing over an incorrect bootloader can permanently brick you device. The Oct 13 2012 build includes the bootloader upgrade and can be flashed over any ROM/bootloader]
Google search: " update tf201 bootloader"
[GUIDE] How to manually update/restore firmware (TF101, TF201, TF300, TF700, TF701) - Post #2 sent me to ASUS official support wherein I downloaded "V10.4.2.18." This is a test in hopes that I can get a ROM running and see if the bootloader changes. I'm not able to use the methods in that thread as I do not have a system nor a microSD, as such I'll flash it the way I have been. Same custom recovery as before. Run the usual wipe (Dalvik, System, Cache, Data, Internal). Drop ASUS ROM onto pad's internal. Attempt flash... Error: "E:Error executing updater binary in zip"
More research, now trying to find out what this error is. Tried this and read a couple pages from here. Settled on reflashing TWRP. While looking up the command again, I came upon here, then went to the first post of that thread here, then from the TWRP link in that post to here (yes, I see the big TF700T at the top, I also see the big MUST BE ON A BOOTLOADER ENDING IN 14.10).
Okay so, I have 10.4.2.15 and am going to have to jump through several hoops to get to the mysterious 10.6.1.27.1. Annnnd It seems as though I have a custom flash that doesn't support my bootloader (which I feel should've been an issue up until now?) I just want to boot into A ROM, so either I find a ROM that supports the bootloader and probably flash a recovery that does as well...
Googled: "10.4.2.15 tf201" Came upon this, tried to flash twrp2.3.1.0 for the tf201 (downloaded straight from their website)... Still in 2.8.7.2 ... Okay, what? FINE! Screw it, redownload the stock ROM that got me into this mess (here) and see if I can even flash that. Wipe all the usual but internal storage because I'm lazy and afaik it doesn't need to be wiped anyway. Error: "E:Error executing updater binary in zip" The line above it, "symlink: some symlinks failed". Popped into here, unmounted the things, reformatted /data to f2fs (this may just be a Marshmallow thing though... it was ext_4 before I reformatted) Same error... Kill me.
So the problem as it stands now. I'm cannot seem to flash a different custom recovery and whenever I try to flash a ROM I get "E:Error executing updater binary in zip" The line above it, "symlink: some symlinks failed". I give up for now... Maybe I'll try again tonight. I'm running bootloader 10.4.2.15 and TWRP KANG 2.8.7.2 (which seems to require a 14.10 bootloader). In this mess, I don't know what to fix nor how to fix it. The angles I see are fix the custom recovery or fix the error/symlink problem since the bootloader version seems to be dependent on successfully flashing ROMs.
I'm sure there's someone out that that can point to me the correct tree in this forest using their superior knowledge of the subject. Having grown up with computers, even a new error message is something to work with. But when you can't even get results (success nor detailed failure), then it becomes downright no fun.
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
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.
This is weird and boggles my mind. I updated to the latest update for my pixel 6, Everything went fine.
When I try to flash the patched boot.img the phone just bootloops and I have to reflash the stock boot.img. I feel like I've tried everything flashed the patch img to both slots tried reinstalling the update, tried flashing stock boot to both slots and retrying the process again.
Everything is normal i.e. bootloader unlocked, that Verity thing dealt with. I just can't get my head around it. I tried following that post with the guide but still the same result.
Any help would be great, it's not about achieving root anymore tbh, I just want to beat it as I've been at it for hours and it's annoyed me now haha.
Thanks in advanced
This has to be a joke, right?
Okay, I give up.
What's the punch line?
I wish it was mate maybe I've been trying for ages now that the obvious is escaping me. Scared to know the answer now haha.
@Newrooter22 Ask in the guide you looked at. They know all. Yep, it's under "guides".
will you try following through adb ?
- boot to bootloader
- from fastboot try to boot with the patched img yuo made with command : fastboot boot patched -image-you-made.img
- see if your phone boot.
- if not, get a copy of patched boot img with your img version on this forum.
i used to have same issue, turned out patched img wasn't good.
hope will help.
Thanks everyone for the replies, I've posted the situation under the "guides" as I'm starting to think it's something wrong with the patched boot.img that I'm getting from Magisk.
@mailistman I thought that could've worked as well hopefully just booting the patched img but never worked so hopefully if someone on the other thread has a copy, the second thing you mentioned might work.
Thanks again