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.
Related
I am a relative noob at flashing roms and rooting phones, but last night I ran into an issue. My phone was having all sorts of problems so I was going to put it back to factory, then start from scratch. I then decided to just flash a different rom. here is what happened.
I deleted SuperSU - this was done as part of the process to unroot and put back to factory, after this step I decided to flash a different rom
Put new ROM on phones internal memory as well as SD card
Wipe data
wipe cache and delvic cache
install new rom
Black screen
In an attempt to unbrick I relocked my bootloader.
Now, my phone can power on (Give white screen and HTC logo), then go black, and I can access Recovery mode. That is all.
I have plugged the phone to my computer and tried running the RUU, but the RUU will not recognize the phone.
I am not sure what to do to unbrick my phone and get it working again. Any and all help would be most appreciated!
Sorry I can't be more eloquent with my words, but I'm at work. I will be responding throughout the day, though.
thanks again so much to anyone that can help!
Try running it straight from bootloader
I loaded into Bootloader, selected Fastboot(USB), ran the .exe and it still won't recognize the phone. However, I did get recovery unlocked again. So I can get into recovery mode, flash all the ROMs I want, mount and unmount, yet still everytime I flash a new ROM it still boots to a black screen. Am I doing this right?
Try a Rom with kernel installer
Thanks! Since I am still a little new could you tell me how I would spot a ROM with kernel installer or could you point me to any one that could work? From then, it's the same process as flashing any other ROM? Do I need to do something with the kernel?
Meanbean and stock with goodies are the 2 that I'm certain of. Meanbean needs to be flashed twice the first time
Thanks so much for your help, I will post my results soon!
Failed
Here's what it says. Sorry for the blurry picture. I followed directions closely.
What version of recovery are you using? You may need to update it. Assuming you have a pc, try mounting the internal memory to pc through twrp. Windows will automatically tell you to format if its damaged
2.1 Updating now
omg it finally worked! Updated TWRP using fastboot and flashed MeanBean. Thank you so much!!!
Hi, first the details
S-Off via dirtyracun
HBoot 1.19.2222
Radio 1.12.11.1210
TWRP 2.4.4.0
Latest Viper ROM
Weird issues I have;
-Can not install any ROM other than Viper.
-Can not perform backup, it creates a backup successfully and while still in recovery you can locate the backup file, but if the card is pulled out or the phone is booted, the file disappears.
-ROM feels buggy and laggy recently (I'm pushing power right now & it takes the phone about 30 seconds to wake up) this is the most annoying issue and it's becoming consistent.
-Images taken with phone camera are all corrupt files afterwards and can not be viewed.
The phone worked PERFECT with absolutely no flaws after first installing viper when I achieved S-off & rooted the phone. These problems started when I tried to install a different ROM, after multiple failed attempts I gave up & went back to Viper. I checked everything that I know of and have no clue what to do to remedy these issues.
Now the phone works OK with Viper ROM but it's getting annoying that Viper is my only option and it's not even working as smoothly as it first did (even after wiping cache etc.)
I guess I could return the phone back to stock & start all over again but I refuse to since it took too much time unbricking & troubleshooting when I went through dirtyracun's S-Off procedure, I absolutely can not go through that ever again.
Any help would be appreciated :good:
does no one have any ideas? I tried to start over but now I have locked bootloader and the message "tampered" I'm pretty much stuck at this point and not sure what to try to get ROMs to successfully flash. Still rooted & still have Viper ROM running.
oceanisbleu said:
does no one have any ideas? I tried to start over but now I have locked bootloader and the message "tampered" I'm pretty much stuck at this point and not sure what to try to get ROMs to successfully flash. Still rooted & still have Viper ROM running.
Click to expand...
Click to collapse
Haven't been around as much as I use to so I'm behind the times a bit. If you are rooted and S-Off then bootloader should not say locked. Can you fix permissions from recovery? You have root access with SU and are htc dev unlocked? Is the rom zip or backup on sd or sd2? Can you read either when booted with a file explorer?
I went through the htc dev unlock process now bootloader says "Tampered" & "Unlocked" after that I did fix permissions in recovery and flashed sinister V10 successfully BUT I can't flash a Kernel, I tried to flash Arc-Reactor and failed.
Thanks for the help getting another ROM flashed
oceanisbleu said:
I went through the htc dev unlock process now bootloader says "Tampered" & "Unlocked" after that I did fix permissions in recovery and flashed sinister V10 successfully BUT I can't flash a Kernel, I tried to flash Arc-Reactor and failed.
Thanks for the help getting another ROM flashed
Click to expand...
Click to collapse
Have you tried flash booting the kernel boot.img prior to flashing the kernel ?
Sent from my EVO using xda premium
so I tried Bulletproof Kernel and that installed fine...
as far as flash booting the kernel boot.img no I'm not sure how to do that!
What wipe process r u using? I had issues similar to this on my og EVO and it came down to I wasn't fully wiping and getting a dirty install.
I'm having a similar problem. My phone is really, really laggy since I recently moved from MeanRom to Viper. I ran Viper previously with no issues that I can remember. In terms of my phone, I have TWRP 2.5, wiped using TWRP to clear cache, dalvik cache, and data. I didn't wipe system or internal/external sd.
SmallPsych said:
I'm having a similar problem. My phone is really, really laggy since I recently moved from MeanRom to Viper. I ran Viper previously with no issues that I can remember. In terms of my phone, I have TWRP 2.5, wiped using TWRP to clear cache, dalvik cache, and data. I didn't wipe system or internal/external sd.
Click to expand...
Click to collapse
You should always wipe Cache/dalvik cache/data/system going to a different rom so that might be why viper is laggy.
Try a new install using the wipe method above or use the superwipe zip attached below
I usually do a full wipe cache/dalvic/system etc. in TWRP before flashing, I actually managed to flash several different roms and ironically enough I ended up back on Viper, it just seems to have all the tools I like to use and work smoothly enough to keep me happy. It works as smooth as it originally did when I first installed it, I'm not sure what I did that fixed the issue
Though for some reason I still can't flash most kernels, currently I'm using whatever kernel that comes with Viper
Hello Everyone,
Ok so not sure where to start, umm yesterday i decided to root my phone i have the HTC Desire C from Cricket wireless. I was successful at unlocking my bootloader and rooting the device. Now for some reason im unable to flash a custom rom or whatever to my device, not sure if im doing something wrong, but i must have screwed something up because i cant even perform a factory reset or a hard reset to the device at all, and the google play store no longer works and the sync icon never goes away. Now when i attempt to flash the custom rom the clockwork recovery tool wont allow me to do a full wipe which i believe must be completed before you can even install the roms.
any help or suggestion would be greatly appreciated.
Thank You.
Just unlocking and rooting the device should not affect how the Play Store works at all. That seems odd. What's the error? By the Clockwork recovery tool, are you referring to the Rom Manager or the actual ClockWorkMod recovery?
es0tericcha0s said:
Just unlocking and rooting the device should not affect how the Play Store works at all. That seems odd. What's the error? By the Clockwork recovery tool, are you referring to the Rom Manager or the actual ClockWorkMod recovery?
Click to expand...
Click to collapse
Actually you know what, I think i know what happened. when i was trying to flash the rom i also flashed the gapps for jelly bean into my phone which is running ice cream sandwich currently because the rom flashing failed. So basically i think the gapps apps are conflicting with the stock apps on the phone ? It seems like all the google apps are the only ones messing up and the google account sync is messing up also the google playstore and google plus crashes a lot so its only the google apps. so what do you think and how do i restore the phone ? I didnt make a back up recovery either. If someone could also just walk me through how to flash a custom rom like CyanogenMod i believe everything will probably fix its self (hopefully). oh and as for the Clockworkmod i think its the actual clockworkmod recovery the one with a black hat, i accessed it through bootloader recovery options, anyway it doesnt allow me to flash any custom roms ive tried like 3 so far and everytime it ask me for some update file or something about a update not sure.
Yep, the other Google apps is what did it. You don't need to flash Gapps on a stock rom, only for ones like CM that don't come pre-installed. Well, first off, it's good to take note of what system version and baseband version you have, in case you need to find the files for later to reflash. As far as CM, well, you might want to check on how stable a version is for your phone. Often times less popular HTC CDMA phones don't have as good of support from CM. If you just find another stock rom and install it through CWM, you'll probably be fine. Just make sure to wipe everything suggested in the install guide for the rom you pick. Some devs and roms require a full wipe including /system and some do not. ProTip : Do a backup in CWM before ever wiping /system, even your system now which doesn't work right, because if you wipe the system and the rom you downloaded doesn't work, then you will be stuck with nothing to do and at that point would need to find the RUU from HTC to restore the phone back to stock.
FYI: If you unlocked via htcdev.com, this is not a full unlock and whenever you install a custom rom that has a different kernel than what is already on the phone, then you need to extract the boot.img from the rom.zip and install it via fastboot. You should get familiar with fastboot as it is very handy for reviving the phone in a worst case scenario.
es0tericcha0s said:
Yep, the other Google apps is what did it. You don't need to flash Gapps on a stock rom, only for ones like CM that don't come pre-installed. Well, first off, it's good to take note of what system version and baseband version you have, in case you need to find the files for later to reflash. As far as CM, well, you might want to check on how stable a version is for your phone. Often times less popular HTC CDMA phones don't have as good of support from CM. If you just find another stock rom and install it through CWM, you'll probably be fine. Just make sure to wipe everything suggested in the install guide for the rom you pick. Some devs and roms require a full wipe including /system and some do not. ProTip : Do a backup in CWM before ever wiping /system, even your system now which doesn't work right, because if you wipe the system and the rom you downloaded doesn't work, then you will be stuck with nothing to do and at that point would need to find the RUU from HTC to restore the phone back to stock.
FYI: If you unlocked via htcdev.com, this is not a full unlock and whenever you install a custom rom that has a different kernel than what is already on the phone, then you need to extract the boot.img from the rom.zip and install it via fastboot. You should get familiar with fastboot as it is very handy for reviving the phone in a worst case scenario.
Click to expand...
Click to collapse
Ok Thanks for the reply, now as for the full wipe my CWM wont allow me to do this im only allowed to do a cache wipe and I believe this is why im unable to get a Rom working on my phone and this is getting very frustrating, the CWM is the latest version and TWRT wont even flash to my phone so that one doesnt work at all if you know of any others please let me know. Yesterday morning i soft bricked my phone and none of the roms are working because i believe i must perform a full wipe which i am unable to do at this time. oh and about unlocking my bootloader via htcdev.com and it not being a full unlock, do you suggest that may have something to do with the fact roms wont work on my phone and how do you do a full unlock ? oh and i tried to restore back to stock also thats not working either, I get a status 7 error when installing the roms and sometimes a status 6.
Silver5150 said:
Ok Thanks for the reply, now as for the full wipe my CWM wont allow me to do this im only allowed to do a cache wipe and I believe this is why im unable to get a Rom working on my phone and this is getting very frustrating, the CWM is the latest version and TWRT wont even flash to my phone so that one doesnt work at all if you know of any others please let me know. Yesterday morning i soft bricked my phone and none of the roms are working because i believe i must perform a full wipe which i am unable to do at this time. oh and about unlocking my bootloader via htcdev.com and it not being a full unlock, do you suggest that may have something to do with the fact roms wont work on my phone and how do you do a full unlock ? oh and i tried to restore back to stock also thats not working either, I get a status 7 error when installing the roms and sometimes a status 6.
Click to expand...
Click to collapse
Are you sure you don't have the recovery from another version of the Desire C - GSM maybe? I still don't understand what you mean when you say you can factory reset. Why not? What is the error? And sounds like at this point you should just use the RUU to return to full stock and start over.
es0tericcha0s said:
Are you sure you don't have the recovery from another version of the Desire C - GSM maybe? I still don't understand what you mean when you say you can factory reset. Why not? What is the error? And sounds like at this point you should just use the RUU to return to full stock and start over.
Click to expand...
Click to collapse
Ok not sure what the RUU is and how im suppose to use it to return to full stock, and correct i cant perform a factory reset in bootloader period, when i select factory reset it does nothing but reboot and say HTC "this build is for development purposes only do not distribute outside of htc without written permission. Failure to comply may lead to legal action." then it stays like that and nothing else happens period, not sure what im doing wrong but no worries im going to buy a new phone tomorrow and never use custom roms again, if i want a upgrade ill just go out and buy a new phone which i should have done in the first place, only thing ill be doing is rooting my devices for now on and nothing more thank you for your help.
Well, once you have a custom recovery, you don't factory reset from the bootloader screen, but via the recovery itself. That's one of the main reasons for the recovery - better options to wipe the phone as well as backing up, restoring, and flashing the custom stuff. Not saying you shouldn't buy another phone, but no reason to give up on this one. I just think it would require a bit more reading since you don't see very familiar with what to do with CWM after you installed it. Have you even booted INTO CWM?
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
Good afternoon everyone, I got a dilemma here I can't seem to resolve or find a solution on here for. I have a new HTC One M9 (hima) and I was attempting to do a full root and install Lineage OS and Open Gapps. The phone is S-Off, but appears to have a locked bootloader still since it does not have the fastboot option on the bootloader, only boot to downloader, boot to recovery, reboot, and power down options.
When I attempted to install Lineage, I made the mistake of doing an advanced wipe, wiped the data, cache, dalvik cache, and internal storage prior to install figuring this would be like the many installs of custom ROMS I've done in the past.
Well, I cannot get any ROM to work at this point, CM 12, CM13, Bad Boyz, and Viper roms all seem to install ok but will hang on the first boot process and will not load up to the in initial first run wizard screens. I also cannot get Open Gapps to install at all, it reports errors and rejects the install. I've tried it with the verify zip box checked and unchecked, I've tried both the 7.1 ARM and 7.1 ARM64 versions, I've also used Gapps 6.0 with the CM 12 and 13.
Unfortunately I didn't realize I needed to enable OEM unlocking in developer options prior to attempting a boot loader unlock, I have no ROM installed so I cannot do this now.
So my question to everyone is, how do I get an OS installed again on this phone so I can get back to where I was prior to wiping everything so I can begin the root and bootloader unlock process again?
Thanks for your help with this everyone.
I am not a dev, so not positive this is what you will need to do. I think you need to RUU your phone. If phone is Sprint HTC M9, OMJ has a thread with the latest RUU and all the instructions. Of course this does assume you can get into download mode. I had a similar issue a while back, ended up I had to use adapter for SD card into PC to transfer the RUU. Then put SD card back into phone. Hope this gets you started.
Ok thanks, I'll try that.
fldave612 said:
Ok thanks, I'll try that.
Click to expand...
Click to collapse
You get this fixed?
Yes, I was able to get it fixed, I had to RUU it with a signed firmware from HTC directly. Thanks for the help.