Yesterday, I tried rooting my HTC One M8. Everything worked except the supersu told me it could not get the binaries so i thought maybe wiping the whole phone would clear the supersu off. Sorry i'm new at this stuff. So getting back what i did was i cleared the whole OS of the HTC One M8. Now i can just into recovery mode. When i try to turn the phone on it gets stuck on the white boot screen.
I have downloaded a stock m8 sytemdump rom.
I also have a SD card.
Can someone just walk me through what needs to be done in order to load that ROM onto my phone so my HTC is usable again.
theeUsaid said:
Yesterday, I tried rooting my HTC One M8. Everything worked except the supersu told me it could not get the binaries so i thought maybe wiping the whole phone would clear the supersu off. Sorry i'm new at this stuff. So getting back what i did was i cleared the whole OS of the HTC One M8. Now i can just into recovery mode. When i try to turn the phone on it gets stuck on the white boot screen.
I have downloaded a stock m8 sytemdump rom.
I also have a SD card.
Can someone just walk me through what needs to be done in order to load that ROM onto my phone so my HTC is usable again.
Click to expand...
Click to collapse
A couple of questions to find out where you're at: Are you on stock recovery or custom? Do you know how to use adb/fastboot terminal commands at all? You are not in trouble here first off, if you can get into recovery, you'll be fine, you just need a new rom. By any chance did you do a nandroid backup?
If you're rolling your eyes at all these questions and you're on a custom recovery; simply download a custom rom (for your carrier) to your PC, put it on your SD card, find a copy of the SuperSU ZIP FILE, Flash the rom, boot it up, then reboot recovery and flash the SU zip. After that go to the play store and get the SU apk and install.
From your post I'm assuming that you under the impression that installing the SU app would do the trick for you, but you need to flash the binaries through recovery first, then the apk will do it's job.
By the way, there is an entire forum dedicated to the HTC One M8, you probably would've got the help you needed sooner if you had posted over there, as this is the Chef Central forum, which is for learning how to develop for Android. PM me if you have further questions, I'll be happy to help if you get stuck.
Protocol 9 said:
A couple of questions to find out where you're at: Are you on stock recovery or custom? Do you know how to use adb/fastboot terminal commands at all? You are not in trouble here first off, if you can get into recovery, you'll be fine, you just need a new rom. By any chance did you do a nandroid backup?
If you're rolling your eyes at all these questions and you're on a custom recovery; simply download a custom rom (for your carrier) to your PC, put it on your SD card, find a copy of the SuperSU ZIP FILE, Flash the rom, boot it up, then reboot recovery and flash the SU zip. After that go to the play store and get the SU apk and install.
From your post I'm assuming that you under the impression that installing the SU app would do the trick for you, but you need to flash the binaries through recovery first, then the apk will do it's job.
By the way, there is an entire forum dedicated to the HTC One M8, you probably would've got the help you needed sooner if you had posted over there, as this is the Chef Central forum, which is for learning how to develop for Android. PM me if you have further questions, I'll be happy to help if you get stuck.
Click to expand...
Click to collapse
Yes. That worked brilliantly. Thank You Very much.
Related
SO here is the deal... I am a complete an total rooting noob but i need some help. After unlocking the bootloader with the help of Hansoons2000 tool and then flashing the phone and then pushing SuperSu to the phone i installed super su and that is where my issues began. After installing SUperSu i got stuck on the Quietly Brilliant screen on my first boot i heard this could take a while so i waited about an hour. Thats when i realized I had a problem. Heres a list of all the steps i attempted so far but to no avail..
I went into recovery and did a factory reset and cleared the cache.. Didnt work
I also relocked the phone and unlocked assuming it would wipe it that did not work.
ANy help to save my phone would be greatly appreciated. I am a first time rooter and have been stressing about my phone all day thinking i threw 700 dollars down the Drain. Any help would be greatly appreciated. And i may ask some stuid question because i am a noob. Thanks in Advance!
By the way it is an Att One X+ that i got about 3 weeks ago if that helps
which recovery you have?
you need a custom recovery for rooting
Install the TWRP Recovery if you haven't already. Do it through terminal. Then, go install a custom Rom (I suggest Viper XL+). Make sure you wipe everything your supposed to. You can do this with the installation of. Venom, it is the AROMA Installer. Flash the boot.img through terminal to. Everything should be fine and it will be rooted.
»»»Correct me if I'm wrong.
Sent from my HTC One X+
This might mean that you would need to reinstall a new rom. Now what you can do to avoid the whole fast boot terminal stuff you can try locking the bootloader and running the ruu for the at&t hox+. What that does is it wipes everything and brings the phone back to stock (stock rom, stock recovery)
After the install goes through you can re unlock the bootloader and install a custom recovery (I have an at&t hox+ and use CWM) and flash a new rom (I use desensed stock look Elegancia ROM)
I like doing the ruu method because I like having a clean slate if something went wrong.
Sent from my HTC One X+ using xda premium
Thanks
I got my phone working again and all set up using th ATT ruu so now i wondering how to make a good backup for my phone and go at rooting it again! thanks
albert1854 said:
I got my phone working again and all set up using th ATT ruu so now i wondering how to make a good backup for my phone and go at rooting it again! thanks
Click to expand...
Click to collapse
Gald you got it working again! I had to find out myself how to fix my phone when similar stuff happened to me too, now I am able to flash my phone properly with different roms. It's almost like an addiction .
now on topic, the one method i do use for backup is I use the CWM backup method, because it says your apps and your systems settings etc all in one folder and when you finish installing your new rom you can use the CWM recovery to restore the backup of your phone. CWM will restore your information and apps as well as the screens and where the icons were at in the home screens. Pretty cool I'd have to say
Now as a backup to the backup I keep my text messages call logs MMS alarms near and dear to me so I use My Backup Pro, keeps a backup online on their servers and can restore them without a prob (although I do find it annoying when it saves information when you sync facebook to the contacts. i have about 200 contacts on my phone and somehow it backs up 700 contact information?)
The tool I used to unlock my bootloader, root my phone, and install CWM (Clockworkmod Recovery) is here
pretty self explanatory and easy and has not failed me
Any questions feel free to ask
same
That the same program unused the first time that bricked my phone after installing super su so do I need to install supersu or are there any alternatives? Thanks for all your help.
So, I have never rooted or flashed a device before and I kinda dove into rooting mine and hoped to learn along the way.
I rooted my Verizon Galaxy S4 version i545VRUEMK2, I used this method from a guy on YouTube named Andre Hebra, it's his only video so if you want to see what it was you can find it (sorry couldn't post a link, I'm a forum newb) now I'm rooted but half of the superuser app is in Chinese or Japanese and its kind of annoying but I can figure out what is happening.
Now here is where I started having some trouble, I decided to try and flash a ROM to my device. I was trying to flash CyanogenMod 11 (12/26/13) Nightly (have no idea what nightly means) and I ran into a few problems that I hope some of you guys can help me with. I downloaded Clockwork ROM Manager and Installed a Recovery. I moved the .zip file from the Cyanogen website to the SD card in my phone. And also moved phone's files into a folder on my computer as a backup. I put my phone into recovery mode through the CWM app and cleared the cache and wiped the data. Now, I can't manually enter recovery boot by holding the volume up, power and home buttons, the phone boots up, the Recovery Boot message appears for a split second and then the phone turns off and boots up again into Android. I'm also struggling to figure out how to flash the ROM, shouldn't I be able to use this Clockwork app to install it from my SD card? But when I try and do that the .zip file doesn't show up in the directory. Did I do something wrong? A quick run through and tutorial would be helpful.
Device Info:
Model number: SCH-i545
Android Version: 4.3
Baseband Versions: i545VRUEMK2
I'm also having trouble navigating to the guides on this site for rooting and flashing my particular device. So i apologize if there is a guide for all of this somewhere but I couldn't find it.
What ROM
Shagen34 said:
So, I have never rooted or flashed a device before and I kinda dove into rooting mine and hoped to learn along the way.
I rooted my Verizon Galaxy S4 version i545VRUEMK2, I used this method from a guy on YouTube named Andre Hebra, it's his only video so if you want to see what it was you can find it (sorry couldn't post a link, I'm a forum newb) now I'm rooted but half of the superuser app is in Chinese or Japanese and its kind of annoying but I can figure out what is happening.
Now here is where I started having some trouble, I decided to try and flash a ROM to my device. I was trying to flash CyanogenMod 11 (12/26/13) Nightly (have no idea what nightly means) and I ran into a few problems that I hope some of you guys can help me with. I downloaded Clockwork ROM Manager and Installed a Recovery. I moved the .zip file from the Cyanogen website to the SD card in my phone. And also moved phone's files into a folder on my computer as a backup. I put my phone into recovery mode through the CWM app and cleared the cache and wiped the data. Now, I can't manually enter recovery boot by holding the volume up, power and home buttons, the phone boots up, the Recovery Boot message appears for a split second and then the phone turns off and boots up again into Android. I'm also struggling to figure out how to flash the ROM, shouldn't I be able to use this Clockwork app to install it from my SD card? But when I try and do that the .zip file doesn't show up in the directory. Did I do something wrong? A quick run through and tutorial would be helpful.
I'm also having trouble navigating to the guides on this site for rooting and flashing my particular device. So i apologize if there is a guide for all of this somewhere but I couldn't find it.
Click to expand...
Click to collapse
You have to make sure that you get the correct ROM for the device you have as they are many. Always if a new to rooting, write down all information from Setting>about. This is where all the most important information is. This way folks on here can help you out a lot better. It seems that you are stuck in a "Boot loop" it's not a big deal. There are a bunch of Youtube videos about boot loop check it out. I'm not that familiar with the ROM you have. Good Luck!
Shagen34 said:
So, I have never rooted or flashed a device before and I kinda dove into rooting mine and hoped to learn along the way.
I rooted my Verizon Galaxy S4 version i545VRUEMK2, I used this method from a guy on YouTube named Andre Hebra, it's his only video so if you want to see what it was you can find it (sorry couldn't post a link, I'm a forum newb) now I'm rooted but half of the superuser app is in Chinese or Japanese and its kind of annoying but I can figure out what is happening.
Now here is where I started having some trouble, I decided to try and flash a ROM to my device. I was trying to flash CyanogenMod 11 (12/26/13) Nightly (have no idea what nightly means) and I ran into a few problems that I hope some of you guys can help me with. I downloaded Clockwork ROM Manager and Installed a Recovery. I moved the .zip file from the Cyanogen website to the SD card in my phone. And also moved phone's files into a folder on my computer as a backup. I put my phone into recovery mode through the CWM app and cleared the cache and wiped the data. Now, I can't manually enter recovery boot by holding the volume up, power and home buttons, the phone boots up, the Recovery Boot message appears for a split second and then the phone turns off and boots up again into Android. I'm also struggling to figure out how to flash the ROM, shouldn't I be able to use this Clockwork app to install it from my SD card? But when I try and do that the .zip file doesn't show up in the directory. Did I do something wrong? A quick run through and tutorial would be helpful.
Device Info:
Model number: SCH-i545
Android Version: 4.3
Baseband Versions: i545VRUEMK2
I'm also having trouble navigating to the guides on this site for rooting and flashing my particular device. So i apologize if there is a guide for all of this somewhere but I couldn't find it.
Click to expand...
Click to collapse
If you are new to all this, then you need to do alot more reading first of all if you are on MK2 base, you can not load any custom recovery except for safestrap. And with safestrap you CANNOT load any CM or ASOP based ROMS. This situation has been discuss a couple hundred times thru out this forum. You will get to learn about ODin process now as that is your only recourse.
many youtube videos on odin and search function works in XDA
A few weird things are happening on my phone and I'm quite concerned (even though it's actually working perfectly fine, which is the weirdest part of all!)
A little background: I recently wiped my phone and flashed the Sense 5 Android 4.3, stock rom. Now I'm trying to flash Viper 4.0.
First of all, as the title suggests, whenever I put a zip file on my phone it doesn't show in the TWRP recovery. I downloaded the correct one on the site (the newest one for the HTC EVO 4G LTE) so I don't think that's the problem. Also, I tried to push the file Viper zip onto my phone using this program called WinDroid Toolkit, and it claims it did but when I go into TWRP I cannot see the zip file at all, and if I try to use other folder names (such as the 'boot' folder I saw when I was in TWRP recovery) it says those folders don't exist!
Second of all, TWRP claims there is no OS installed on my phone but when I reboot my phone, it's fine! It just goes to the home screen as usual and it works perfectly fine... so I don't understand this warning but I couldn't shake the feeling that this was relevant to my issue.
I've been combing the forums looking for this type of problem, and I've tried multiple things but to no avail. I've read snippets about partition problems after formatting some phones but I'm not sure because there doesn't seem to be much information about it (at least from what I could find).
Altom85 said:
A few weird things are happening on my phone and I'm quite concerned (even though it's actually working perfectly fine, which is the weirdest part of all!)
A little background: I recently wiped my phone and flashed the Sense 5 Android 4.3, stock rom. Now I'm trying to flash Viper 4.0.
First of all, as the title suggests, whenever I put a zip file on my phone it doesn't show in the TWRP recovery. I downloaded the correct one on the site (the newest one for the HTC EVO 4G LTE) so I don't think that's the problem. Also, I tried to push the file Viper zip onto my phone using this program called WinDroid Toolkit, and it claims it did but when I go into TWRP I cannot see the zip file at all, and if I try to use other folder names (such as the 'boot' folder I saw when I was in TWRP recovery) it says those folders don't exist!
Second of all, TWRP claims there is no OS installed on my phone but when I reboot my phone, it's fine! It just goes to the home screen as usual and it works perfectly fine... so I don't understand this warning but I couldn't shake the feeling that this was relevant to my issue.
I've been combing the forums looking for this type of problem, and I've tried multiple things but to no avail. I've read snippets about partition problems after formatting some phones but I'm not sure because there doesn't seem to be much information about it (at least from what I could find).
Click to expand...
Click to collapse
Try using the TWRP found here:
http://forum.xda-developers.com/showthread.php?t=2639180
Sent from my Nexus 5 using XDA Premium 4 mobile app
download this twrp http://d-h.st/7Cr
name it properly and fastboot flash it. after that mount your device to you pc and transfer a rom zip to storage.
Okay, well I flashed that TWRP and now I'm stuck at the white HTC screen. I can't even get into the bootloader, it just continually boots to the white HTC screen. Thoughts?
Altom85 said:
Okay, well I flashed that TWRP and now I'm stuck at the white HTC screen. I can't even get into the bootloader, it just continually boots to the white HTC screen. Thoughts?
Click to expand...
Click to collapse
RUU or ViperRUU. TBH it sounds like the behavior of a dirty flash. ViperRUU is especially helpful in these situations.
Once done, use the TWRP recommended by Evolution_Freak. There were some major changes to the partitioning in the last few releases, make sure your recovery is appropriate for your ROM.
FesterCluck said:
RUU or ViperRUU. TBH it sounds like the behavior of a dirty flash. ViperRUU is especially helpful in these situations.
Once done, use the TWRP recommended by Evolution_Freak. There were some major changes to the partitioning in the last few releases, make sure your recovery is appropriate for your ROM.
Click to expand...
Click to collapse
Ok it's not stuck anymore, I can get into recovery and bootloader, so I'm not in a panic anymore at least However, my computer is not detecting my phone, nor is VipeRUU. If I try to mount to the computer via TWRP, nothing comes up. BTW my recovery is 2.7.8.0b now. Still no OS, still gets stuck on the HTC screen until I boot to recovery or bootloader
Edit: Now the computer tries to install drivers for my phone whenever I plug it in. It pops up as HTC MTP Device, always fails to install, then has a warning in the device manager. So I uninstalled the drivers, uninstalled HTC Sync, reinstalled HTC Sync. Didn't help. This is beyond frustrating...
Edit 2: After scouring the internet someone said to lock the bootloader and that'll allow my PC to see my phone. Well, now i have a RELOCKED (that's what it says on top) bootloader and I'm no closer to the solution methinks. I'm ready to just throw this phone out the window.
Edit 3: I actually discovered ViperRUU has a way to bypass the initial screen so I can use it in bootloader. Great, except now it's stuck on "Flashing..." and has been for half an hour. I really might throw this phone out the window.
5th and final edit: VipeRUU just would not work at all, so I had to go back to an older stock RUU, which sucks but at least my phone is working now Thanks for your help guys!
So im fairly new to unlocking, flashing, etc. I have a HTC One M8 for AT&T that im trying to unlock to use with different carriers. After reading a bit I realized that I had to unlock my bootloader, root, install s-off before I could achieve my goal. I used htc-one.wonderhowto. com/how-to/unlock-bootloader-root-your-htc-one-m8-0154444 to root and unlock my bootloader. Followed the guide to a T and all was fine. Then I was going for S-Off and here's where I encounters my problems. I used htc-one.wonderhowto. com/how-to/get-s-off-your-htc-one-m8-install-custom-firmware-mods-0154461 guide and this is where I believe I fudged up bad. Step one says to download InsertCoin from insertcoin-roms. org/category/devices/onem8 this link. I downloaded the OTA 4.0.6 to 4.0.7 and saved it onto my phone I think maybe I should of downloaded the link for the full ROM and that's why im having this problem but im not sure. I followed each step with the exception to Step 3 which is also where I fudged up. I didnt back up because I didnt think it was needed since the phone was just wiped clean of everything. At step 5 my life changed forever..lol.. but when I flashed it , it said failure. I tried to follow the steps again but it kept failing to flash. So I went back and tried to re-flash SuperSU which was successful but when I go to reboot it from TWRP it says I have no OS installed and it gets stuck on the HTC boot screen unless I put my phone into fastboot mode. Which says ***unnlocked*** and ***tampered*** at the top and im stuck. Please someone help me and tell me what to do.
I recently deleted my OS by my stupidity. I fixed the issue by side loading a stock Rom via adb/twrp sideload. Saved me. There are tutorials on how to do this. Just Google search. You could also put a stock Rom on an external sd and flash that way. Don't have a link to the stock Rom I used, but it's in the resources thread in general section. Hope this works for ya
Sent from my HTC One_M8 using XDA Free mobile app
vansslamcityjam said:
I downloaded the OTA 4.0.6 to 4.0.7 and saved it onto my phone I think maybe I should of downloaded the link for the full ROM
Click to expand...
Click to collapse
The file you downloaded is if you were already on InsertCoin 4.0.6, and updating to version 4.0.7, which was not the case for you. You should have downloaded the full ROM, and that is likely why the flash failed.
If you ever have any doubt about what you are flashing, this should be a red flag to STOP and either read and research some more, or come on here and ask.
vansslamcityjam said:
I didnt back up because I didnt think it was needed since the phone was just wiped clean of everything.
Click to expand...
Click to collapse
That is why you make a TWRP backup before wiping anything.
vansslamcityjam said:
So I went back and tried to re-flash SuperSU which was successful but when I go to reboot it from TWRP it says I have no OS installed and it gets stuck on the HTC boot screen unless I put my phone into fastboot mode. .
Click to expand...
Click to collapse
Did you specifically wipe system in TWRP? If so, that is where the OS is stored, so of course wiping it means you have no OS.
I do not advocate wiping system when flashing ROM, especially if you are new to this. Reason being, it already gets wiped when you flash a ROM anyway (so its redundant). Also, if the ROM fails to flash, you will still have a working OS if you did not wipe system manually. As stated on the wipe screen in TWRP, the default wipe (data, cache, and Dalvik) is all that is usually needed. It says this for good reason.
All you need to do is download a ROM to your computer, and either adb push to the phone, sideload flash, or copy it to a removeable MicroSD card using a USB card reader. Then flash in TWRP.
tl;dr - Can't seem to find my way out of a software brick. Have sideloaded the stock OS from 1+ but still forever getting the spinning dots or fastboot screen, depending on which mode i boot into.
Hi all. Signed up to make this thread, but i've been lurking for years.
I have a OnePlus X that is about the least modded smartphone i've ever owned. I've never been pleased enough with a retail product that i didn't feel compelled to strip out the bloat and start over, until this phone. Other than stock, i've just got a gallery app, some apps for manipulating text files or compiling code, couple games, and social media apps.
Anyway, a few days ago i got a notification about a software update. Downloaded. Installed. Updated. No problem.
Maybe yesterday or the day before, it showed up again. This morning i downloaded, installed, and suddenly i have apps closing. It's been over 12 hours so i'm hazy on how it all started, but i was getting something like "package installer" errors when attempting to open some apps. Same deal when i went to adjust permissions of those affected apps. Every time i unfocused a box that had pulled up swype, i would get an error message saying swype crashed or closed or something.
So i started uninstalling third party apps (i don't keep many, and most i've had for years so i think they're probably trustworthy). Same deal. Started uninstalling updates to google apps. Same deal. Went to uninstall and reinstall some non stock apps that i'd kept previously. Nothing.
I went to cook breakfast while an app was reinstalling, and i came back to a red dot on my screen with two white dots chasing each other around it. From what i'm reading that's a sign of a bootloop or software brick. I've taken all steps i could find, including wiping cache and sideloading a fresh stock OS, but to no avail.
Is it that i've ruined my google apps somehow and need to restore them? How would i even go about figuring out what the problem is? Any advice or guidance is appreciated
Hi,
As your device is in bootloop state, try flashing the stock rom. Make sure you wipe data and cache. As far as after update problems, i faced it few times. After updating many app crashed and phone hangs. So i prefer clean flash over dirty flashing, to make sure everything is hazel free. For the time being i upgraded from 3.1.2 to 3.1.3 without wiping data or cache and facing no problem( of course since it was an OTA). But sometimes situation comes when after update phone act weird, so tbe option which i prefer then is clean flashing the stock rom. Hope this helps.
"A09" said:
Hi,
As your device is in bootloop state, try flashing the stock rom. Make sure you wipe data and cache. As far as after update problems, i faced it few times. After updating many app crashed and phone hangs. So i prefer clean flash over dirty flashing, to make sure everything is hazel free. For the time being i upgraded from 3.1.2 to 3.1.3 without wiping data or cache and facing no problem( of course since it was an OTA). But sometimes situation comes when after update phone act weird, so tbe option which i prefer then is clean flashing the stock rom. Hope this helps.
Click to expand...
Click to collapse
I have wiped cache, deleted data, tried a factory reset in the stock bootloader, and i have used ADB to sideload a full stock rom (not upgrade package) that i downloaded from OnePlus.
Flash old stock recovery then 2.2.3. From there you can flash any MM stock firmware.
Exodusche said:
Flash old stock recovery then 2.2.3. From there you can flash any MM stock firmware.
Click to expand...
Click to collapse
Pardon me for being nooby, but how do i do this? Do i just sideload in ADB like i did the ROM? Most instructions i'm finding assume access to the OS either normally or through fastboot. I'm just stuck in the default recovery.
Thanks for the tip, though. Looking for a copy of the old stock recovery now. Did OnePlus alter their stock recovery recently? In some threads i've seen people say that a recent update made them unable to load a non-stock ROM. Is that the new recovery blocking access to non-1+ operating systems?
jtg1984 said:
Pardon me for being nooby, but how do i do this? Do i just sideload in ADB like i did the ROM? Most instructions i'm finding assume access to the OS either normally or through fastboot. I'm just stuck in the default recovery.
Thanks for the tip, though. Looking for a copy of the old stock recovery now. Did OnePlus alter their stock recovery recently? In some threads i've seen people say that a recent update made them unable to load a non-stock ROM. Is that the new recovery blocking access to non-1+ operating systems?
Click to expand...
Click to collapse
Fastboot flash easiest way. Make sure it's the old recovery from 2.2.2. Not the new mm stock recovery.
Yes, but how do i install the old stock recovery? I dug around on the forums and found the file, but the phone rejects it when sideloading and doesn't show the .img in the filesystem when inserted on a SD card.
Have to send it off to 1+ maybe? Literally all i can access right now is the (new) stock recovery. I never modded, rooted, etc before the software update sent me into the chasing dots
jtg1984 said:
Yes, but how do i install the old stock recovery? I dug around on the forums and found the file, but the phone rejects it when sideloading and doesn't show the .img in the filesystem when inserted on a SD card.
Have to send it off to 1+ maybe? Literally all i can access right now is the (new) stock recovery. I never modded, rooted, etc before the software update sent me into the chasing dots
Click to expand...
Click to collapse
I m not a dev, i m a newbie like you. i hv done a lot of experiments with my oneplus-x, as for u the first update u got few days back should be oos 3.1.2 and the one u got 2 days before should be 3.1.3. When u upgrade from lollipop to marshmellow, even your stock recovery got upgraded to latest version, which is something different from old lollipop recovery.
You said you have access to recovery mode. thts pretty much gud, what u can do is that wipe data and cache through stock recovery and do a clean install of oos 3.1.3. I ll be providing all the necessary links down below. If you need assistance with fastboot cmds and anything feel free to ask.
Thanks to original link provider @Sachin7843
Useful Links: -
1. Stock Lollipop Recovery - https://s3.amazonaws.com/oxygenos.oneplus.net/OPX_recovery.img
2. Official TWRP Recovery - https://dl.twrp.me/onyx/
3. Blu Spark Recovery - http://forum.xda-developers.com/devdb/project/dl/?id=20236
4. SuperSU for OOS 3.x.x - https://drive.google.com/file/d/0B4K5cvm1zdldcmZpc3RuVnRjUUE/view
5. Unbrick Guide - http://forum.xda-developers.com/oneplus-x/general/guide-mega-unbrick-guide-hard-bricked-t3272108
6. Official Oxygen OS 3.1.3 link - https://s3.amazonaws.com/oxygenos.o...OTA_018_all_201609291837_741146bcf28e4587.zip
7. SD Card Writable fix in MM - http://forum.xda-developers.com/android/software/fix-extsd-fix-v1-0b-2016-01-18-t3296266
8. For Stock MM Recovery - http://forum.xda-developers.com/oneplus-x/general/oxygenos-3-1-0-marshmallow-community-t3445043
Sorry for my bad english
jtg1984 said:
Yes, but how do i install the old stock recovery? I dug around on the forums and found the file, but the phone rejects it when sideloading and doesn't show the .img in the filesystem when inserted on a SD card.
Have to send it off to 1+ maybe? Literally all i can access right now is the (new) stock recovery. I never modded, rooted, etc before the software update sent me into the chasing dots
Click to expand...
Click to collapse
Don't sideload it, use fastboot to flash it. "Fastboot flash recovery name.img" - without he quotes and the image name.
Sorry for vanishing. Had a busy week.
Not sure what happened the first time i tried to put the 2.2.3 image on the SD card, because the file didn't show up in my recovery, but i tried again later (after giving up on flashing the old recovery, since i couldn't figure out how to do that in recovery) and managed to do a clean install of the older OOS version.
That did the trick, and after booting up, my phone proceeded to update again - this time without any crashes or errors with my apps afterward. The phone still does the red dot with the white dots chasing around it when it boots up, which must be the new boot screen. It also seems to stay on that screen for much longer than it stayed on the old morphing shape boot screen, but it still boots up reliably now after 30-60 seconds rather than freezing in boot forever.
I've since enabled dev mode on my phone. Is that going to be enough to enable ADB commands from recovery? I kind of like that i've kept my phone stock, so i'll leave it that way if i can, but it would have been much easier to fix this problem if i'd had access to most of my debug commands. As it was, without dev mode and in the standard recovery, it seemed that sideload was the only command i was able to use, and only when the phone was requesting a sideload over usb