Related
Hi Guys,
Long-time listener, first-time caller..
I have a feeling I’ve broken my HTC One X+ [enrc2b] (UK Vodafone running CM10.2) due to a bad upgrade.
I had Cyanogen 10.2 installed and have been happily using and updating it via the built in CM update tool.
I went from stable to nightly a couple months ago and have never found any major issues so continued to use nightlies.
On Sunday (12th Jan) a new CM update was made available and I went through the usual process without really looking closely at the update. The update was for CM11. (Shouldn't matter? I've flashed new boot.img's before when required).
The update downloaded so the phone rebooted and went to flash, but failed halfway through due to a corrupt download.
I’m not sure if it was the file on the CM servers or if the download simply corrupted but I’ve never seen a similar issue and didn’t interrupt the update so I’m guessing it was a bad file uploaded for the update.
This is where it gets messy.
I had removed the previous update files so there are none available in the /cmupdate/ folder other than the CM11 version. If I had kept just one I wouldn't be in this situation (lesson learnt!).
My phone DOES NOT have USB debugging turned on, therefore I am not able to use ADB to push files to the device. Is there anyway to send files to the phone without using ADB. I'm pretty familiar with fastboot but can only flash recovery/boot using fastboot (?).
I’ve tried flashing the stock recovery so I can use the RUU for Vodafone UK but the RUU flsah fails. I’ve re-locked the bootloader and have the stock recovery but I get an error when using the RUU.
The RUU is v1.14 and my phone has v1.17 (from CM) so I suspect this is the problem as the version needs to be greater than the current?
The error from the RUU is related to the bootloader (error 140). I’ve tried a couple different versions of RUU such as a Europe one with v1.17 but it throws the wrong region code error when trying to flash.
I don’t have a nandriod back up. I thought I had done when I originally unlocked and rooted the phone. Turns out that it didn’t work.
I have downloaded a couple nandriods that I think would work but because I don’t have ADB working I can’t push the files to the device anyway.
I have CWM recovery installed again now, after the failed RUU update, and a version of hboot (that’ll check when I get home). I think it’s 1.400?
So, is my phone save-able, or is it now a paperweight. Any and all help appreciated.
A lot of the posts relating to fixing similar issues assume you have ADB/USB debug available, and I don’t! I have done a lot of reading over the past couple of days but am no closer to resolving this.
In case it helps, I can grab the zips from the RUU temp folder but wouldn't know how to flash them (does it need ADB?).
Can anyone help?
max3o6 said:
Hi Guys,
Long-time listener, first-time caller..
I have a feeling I’ve broken my HTC One X+ [enrc2b] (UK Vodafone running CM10.2) due to a bad upgrade.
I had Cyanogen 10.2 installed and have been happily using and updating it via the built in CM update tool.
I went from stable to nightly a couple months ago and have never found any major issues so continued to use nightlies.
On Sunday (12th Jan) a new CM update was made available and I went through the usual process without really looking closely at the update. The update was for CM11. (Shouldn't matter? I've flashed new boot.img's before when required).
The update downloaded so the phone rebooted and went to flash, but failed halfway through due to a corrupt download.
I’m not sure if it was the file on the CM servers or if the download simply corrupted but I’ve never seen a similar issue and didn’t interrupt the update so I’m guessing it was a bad file uploaded for the update.
This is where it gets messy.
I had removed the previous update files so there are none available in the /cmupdate/ folder other than the CM11 version. If I had kept just one I wouldn't be in this situation (lesson learnt!).
My phone DOES NOT have USB debugging turned on, therefore I am not able to use ADB to push files to the device. Is there anyway to send files to the phone without using ADB. I'm pretty familiar with fastboot but can only flash recovery/boot using fastboot (?).
I’ve tried flashing the stock recovery so I can use the RUU for Vodafone UK but the RUU flsah fails. I’ve re-locked the bootloader and have the stock recovery but I get an error when using the RUU.
The RUU is v1.14 and my phone has v1.17 (from CM) so I suspect this is the problem as the version needs to be greater than the current?
The error from the RUU is related to the bootloader (error 140). I’ve tried a couple different versions of RUU such as a Europe one with v1.17 but it throws the wrong region code error when trying to flash.
I don’t have a nandriod back up. I thought I had done when I originally unlocked and rooted the phone. Turns out that it didn’t work.
I have downloaded a couple nandriods that I think would work but because I don’t have ADB working I can’t push the files to the device anyway.
I have CWM recovery installed again now, after the failed RUU update, and a version of hboot (that’ll check when I get home). I think it’s 1.400?
So, is my phone save-able, or is it now a paperweight. Any and all help appreciated.
A lot of the posts relating to fixing similar issues assume you have ADB/USB debug available, and I don’t! I have done a lot of reading over the past couple of days but am no closer to resolving this.
In case it helps, I can grab the zips from the RUU temp folder but wouldn't know how to flash them (does it need ADB?).
Can anyone help?
Click to expand...
Click to collapse
the phone when on recovery doesn't need the USB debugging to be turned on....
if u had installed the proper drivers u will be able to see ur phone as on recovery.....
[email protected] said:
the phone when on recovery doesn't need the USB debugging to be turned on....
if u had installed the proper drivers u will be able to see ur phone as on recovery.....
Click to expand...
Click to collapse
Hmm, ok thanks. Maybe I need to reinstall ADB drivers. The HTC USB drivers work ok (fastboot usb is fine) and I do have ADB installed but having meddled with it (reinstalled ADB) I should try pushing again I guess.
Thanks, will try when when home! :good:
ADB without USB debugging turn on
Now sorted!
ADB works when the phone is in recovery, not in hboot. Dur.
Thanks!
I haven't used my Nexus in about a month and the last time I used it, I had flashed a new rom with the wrong gapps. It was a fresh factory reset and whenever it booted up, I would get error messages and I wouldn't be able to do the initial set up. At the time, this was nothing I couldn't fix, but I had to put it aside because I was busy.
Fast forward to present day, I completely forgot about it. I locked the device, flashed stock recovery and did another factory reset. Now whenever I try to turn it on I get stuck at a black screen with error messages (I can't do initial setup). I can't install a new rom because the device is locked and I can't unlock it because it's OEM locked and I can't get into the OS.
Am I screwed or can I still pull off a miracle?
Wug's Nexus Root Toolkit! There are tons of video tutorials on YouTube that should help.
Sent from my Nexus 6 using Tapatalk
Go_Radio said:
I haven't used my Nexus in about a month and the last time I used it, I had flashed a new rom with the wrong gapps. It was a fresh factory reset and whenever it booted up, I would get error messages and I wouldn't be able to do the initial set up. At the time, this was nothing I couldn't fix, but I had to put it aside because I was busy.
Fast forward to present day, I completely forgot about it. I locked the device, flashed stock recovery and did another factory reset. Now whenever I try to turn it on I get stuck at a black screen with error messages (I can't do initial setup). I can't install a new rom because the device is locked and I can't unlock it because it's OEM locked and I can't get into the OS.
Am I screwed or can I still pull off a miracle?
Click to expand...
Click to collapse
Hi, Go_Radio...
Probably screwed ... sorry, I don't mean to be glib or flippant. I've experienced something similar myself, late last year, and I had to return my Nexus 9 for a replacement, so I know what a pain in the backside this problem is.
-----
But to be clear, if I read and understand your post correctly, you're looking to run fastboot flash commands (either directly yourself, or allow a toolkit to run them for you) in order to either...
----
a) Fastboot Flash back to Google Factory Stock.
~ or ~
b) Fastboot Flash TWRP, and via TWRP, flash some Custom ROM.
----
...but cannot do either...
...because the bootloader is locked, and attempts unlock it with fastboot oem unlock fail.
And it fails because the option in SETTINGS>>DEVELOPER OPTIONS>>OEM unlocking (allow the bootloader to be unlocked) has not be enabled, or has been disabled.
This damnable nuisance problem, at the moment, can only be resolved in one of two ways... Either by returning your device for repair or replacement...
Or by the method described here...
[INFO] Nexus 6 / Nexus 9 Enable OEM Unlock [GUIDE] Unlock via TWRP/CWM
http://forum.xda-developers.com/nexus-6/help/info-nexus-6-nexus-9-enable-oem-unlock-t3113539
...unfortunately for this to work, you do need TWRP installed, in order for the necessary files to be copied over to your Nexus 9, as the stock recovery doesn't allow for ADB connections (I know, I've tried )
And since Android won't boot, for whatever reason, you're locked out, and you can't enable the 'Allow OEM unlocking' setting in Developer Options in order to allow the bootloader to be unlocked, in order to fastboot flash TWRP. You're caught in a Catch 22 situation .
I wish I had some better options for you... .
Rgrds,
Ged.
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.
So,
This may seem mundane to some of you, and I apologize. But I'm hitting a wall with this Pixel. I cannot use Fastboot normally because I can't get access to any of the internal partitions. I have a list of them that I looked up, but fastboot will not allow me to use any fastboot flash or flashing commands that I need to flash a new ROM.
I've unlocked bootloader - Duh - (been doing this a little while)
Rebooted
Reenabled ADB - #adb reboot bootloader (works fine)
Sending files --> ADB and fastboot both will serve the image or file to the phone, but the phone fails on "partition does not exist" on every time.
I have tried re-flashing this device with the android flashing tool through Google (works fine and I'm currently running the 13 Beta T3B3). Would straight flashing from a zip file help?
I want to be running LoS but I cannot get even the vendor_boot or boot image to flash. Everything seems to be software/firmware locked and I've tried the fastboot commands to unlock certain partitions and things like that from what I can tell in the changes to fastboot. So my question is:
What am I missing? I have even got it to boot into LoS and things worked, but you could tell something was very wrong with the flash and major app/gapp issues. This was accomplished with the flash tool flashing the partitions "boot" and "vendor_boot" and "dtbo" for me to get me into the LoS recovery. From there I reset and installed via sideload like normal, flashed the rest of the partitions listed with LoS and I cannot get a working build without major app issues and major stability issues. CLI will also not give me any info on why these can't be flashed, of course, but that's not how this should work. I know it should be more stable than it is just because it's a Pixel (one would think - has been in the past) It's a Global model GB7N6 and I don't understand what the hold up is.
Any help or suggestions would be greatly appreciated! Thanks!
You need to flash the regular factory image first, not the beta!!
Factory Images for Nexus and Pixel Devices | Google Play services | Google for Developers
developers.google.com
See instructions
To be fair, I just flashed the beta as a last ditch. Every try I've done was with production software.
I will absolutely try this though. Anything to straighten this mess out.
XGX5309 said:
To be fair, I just flashed the beta as a last ditch. Every try I've done was with production software.
I will absolutely try this though. Anything to straighten this mess out.
Click to expand...
Click to collapse
Hi friend
If prior attempts to fix the problem in GetSimple CMS failed, it could be worthwhile to try the beta version as a last resort. A alternative strategy can occasionally assist in solving the issue Free Fire