Related
I'd like to flash my Vivid with the new Rum Float ROM and from what I gather; now that a RUU is available it should be fairly easy. I.bought the phone last Thursday and haven't had a chance to grab a SD card. I just want to make sure that I fully understand the process involved. I've read a number of posts here at XDA and elsewhere but I still have a few questions to make sure my knowledge is solid and I don't end up with an HTC paperweight! A) Will the Android market will have a record of what I have already dl'd so I can dl it again? B) Is using the RUU executable fairly simple? Should I do the BL UL before I restore?(I would like root, so I'm assuming that this is one of the first steps!) C) Is it a simple follow the instructions sort of thing with the RUU? D) Will "frigid's" "supertool" method to get root work in this instance or do I need to use CWM? E) I'm using an AT&T Vivid could somebody give me a simple step by step(not in detail, but if you could that would be great!) Such as "1- Do BL UL, 2- Run supertool for root, 3 - Run RUU, etc, etc, etc
Also there appears to be a sense and a NONSense version of the ROM, are they both included in the RUU exe file? And for the NONSense version will there be any difference in stability, performance, you acceleration, etc?
Thanks for any info in advanced!
-MeeGz-
MeeGz said:
I'd like to flash my Vivid with the new Rum Float ROM and from what I gather; now that a RUU is available it should be fairly easy. I.bought the phone last Thursday and haven't had a chance to grab a SD card. I just want to make sure that I fully understand the process involved. I've read a number of posts here at XDA and elsewhere but I still have a few questions to make sure my knowledge is solid and I don't end up with an HTC paperweight! A) Will the Android market will have a record of what I have already dl'd so I can dl it again? B) Is using the RUU executable fairly simple? Should I do the BL UL before I restore?(I would like root, so I'm assuming that this is one of the first steps!) C) Is it a simple follow the instructions sort of thing with the RUU? D) Will "frigid's" "supertool" method to get root work in this instance or do I need to use CWM? E) I'm using an AT&T Vivid could somebody give me a simple step by step(not in detail, but if you could that would be great!) Such as "1- Do BL UL, 2- Run supertool for root, 3 - Run RUU, etc, etc, etc
Also there appears to be a sense and a NONSense version of the ROM, are they both included in the RUU exe file? And for the NONSense version will there be any difference in stability, performance, you acceleration, etc?
Thanks for any info in advanced!
-MeeGz-
Click to expand...
Click to collapse
The RUU DOES NOT CONTAIN MY ROM. It is an official tool used by HTC for upgrading and returning to stock.
Android market will keep tabs on purchased apps. It will not keep track of free apps.
You need an sdcard to keep safe.
The RUU is easy to run. Its just an exe. Follow the on-screen prompts.
I don't know what you are trying to restore but it would appear you have your terminology and methods all mixed up.
RUU will get you a stock ics. And it will wipe your apps and settings. It will act like a phone you just pulled out of the box with ics.
In order to run rum float (or any aftermarket rom) you need to unlock your bootloader. Rooting has nothing to do with it. Unlock bl then flash recovery on then flash rom and kernel.
Your steps as you perceive them are slightly off. I don't recommend you do anything to your phone right now.
After you complete the RUU you'd have to go to htc.dev and unlock your bootloader. After you can fastboot flash a recovery and CWM with root. After that's complete you can flash a rom of your choice. I'd get familiar with using fastboot commands in ADB (command prompt). I guess you can use the supertool to root but it isn't necessary really a matter of preference. Check out the superguide. Maybe PG or someone can update it with specific steps if you are using the RUU but the process is the same. It starts with the unlocking the bootloader. Definitely pick up an SD card!
Thanks for the quick replies and the clarification. I think I get it now, I would do the following to get to a rooted custom ICS Rom: Unlock the boot loader, root and run titanium backup to save my apps(using an ad card), run the RUU and get to stock HTC ics, copy ROM to sd card, re-root, download and run CWM, root again and restore apps with titanium backup, enjoy!
The only things that may be a bit off in that process is running the RUU as I don't need that to just flash a custom ROM, assuming said ROM includes the ICS kernel. If did have to use the RUU would I have to re-root to run cwm? Also the actual ROM itself is installed from HBoot, correct?
Sorry if these sound like dumb questions, I'm just new at this. I really appreciate the replies. I'm sure I will pick this up fairly quickly as I have years of linux & OS X command line experience and am well versed with c. It's just kind of information overload on this board as there is such a wealth and variety of info here!
Thanks again,
-MeeGz-
So you can run the ruu.exe even if you are rooted, unlocked bootloader, on att stock? Or do you have have to relock bootloader to proceed with the ruu?
Sent from my HTC PH39100 using XDA
RUU is for stock roms IIRC. If you are rooted and already unlocked I'd use the original method PG and Thecubed created.
back on my computer for a little better explanation.
the RUU or the methods that thecubed and i have laid out will get you the necessary HBOOT/RADIO/etc that you will need to flash a custom ICS rom
either method will get you the same thing....an updated HBOOT and ICS
if you run the bootloader unlock tool from htcdev, YOU WILL LOSE ALL YOUR SETTINGS! it will wipe the device like its brand new......do NOT include this in your dreams of getting backups prior to flashing a custom rom....
please just read through the posts and understand what is going on.
in order for ICS to happen on your vivid you need the new HBOOT, Radio, and various other components that the RUU/PH39IMG contain
there are 3 different roads you can follow to get there, the EASIEST being just run the RUU (WHICH WILL ALSO WIPE SETTINGS!), afterwards, reboot to bootloader, unlock bootloader, reboot to fastboot, fastboot flash the boot.img and the recovery.img of your choice on (limited on boot.img's at the moment, better use the one from the rom), reboot to recovery and flash the rom
the other methods imply you understand somewhat how the process works.
relock bootloader (if unlocked), run PH39IMG install, unlock bootloader, fastboot flash recovery and boot.img, reboot to recovery and flash rom.....
if you wrap your head around HOW it works, its all really simple....so the first step is understanding HOW it works, not blindly following some tutorial or walkthrough.
please try to LEARN and UNDERSTAND what it is you are doing....
PS. you have involved ROOTING too many times in your post...... the rom is already ROOTED, you dont have to ROOT to unlock, flash rom or anything....ROOTING is only applicable INSIDE the booted OPERATING SYSTEM, and has nothing to do with recovery/bootloader
i feel i need to apologize to the board here.
frustrations were not directed at the OP of this thread, just in general....
i have been inundated with PM's and seeing the same barrage of questions for the last few days on the forum....
i can understand everyone's excitement...hell i was excited to get this too.
but you all need to read, and try to take it all in before attempting anything. sometimes those of us that understand whats going on, dont explain in a whole lot of detail, because we take the knowledge for granted, and assume if you are on this site, you are here to learn. it is frustrating to see the same questions pop up on nearly an hourly basis...
all i ask is that you take forth the effort to learn how these tools of ours work and understand that a lot of us working on things like this rely on you guys to assist each other in the process. that leaves us more time to deal with what we need to deal with and try and fix and squash bugs/processes/etc.
in return i apologize if i seem on edge the last couple of days...its because i am. if you can imagine one question multiplied by a hundred.....and having people freaking out about them 'bricking'.....after being warned its possible, but unlikely. i think most of these 'bricks' are salvageable and just require someone that understands how they work.
sorry to seem like an ass, but mainly its because i am an ass, and i have a hard time being nice most of the time.
Thanks pirateghost. I understand how to do the other methods but wanted to use something less complicated with less risk for user error. I read and read everything that is posted on the forums. I try not to ask a question unless I am not understanding what has been posted. Thanks for your patience and understanding.
Sent from my HTC PH39100 using XDA
PG, so im pretty sure i "bricked" it lol. im not upset as it was entirely my fault, just wondering if there is any way to get this mother to turn on? i know that when i plug it into the computer it recognizes it but not as anything i have seen lol..if i can find the correct drivers can this be reversed?
Thanks
Thanks to PG for everything and the instructions. I thought I had bricked my phone, but theCube was able to help me on IRC, which is where I suggest anybody go for real-time assistance.
This could off all been avoided with step by step Detail instruction. Why? Well example , I don't follow this forum at all never had an HTC phone but my wife's phone the vivid. All my phone has been Nexus and the galaxy line from Samsung, things over there are a bit different. All I did was flash the ph.img and then after not seen the device reboot I wipe/factory reset and all when to hell from there. Couldn't unlock the bootloader or reboot the phone. How could this happen? Assuming that people should know the basic is wrong. I'm not in any way blaming anyone I did this own my on risk but at the same time I'm super mad had to buy a new phone. As developer you should eliminate all threats and post a details instructions step by step with do's and don't before posting firmwares.
Sent from my Galaxy Nexus using xda premium
Dxtra said:
As developer you should eliminate all threats and post a details instructions step by step with do's and don't before posting firmwares
Click to expand...
Click to collapse
As a user, you should understand the risks/benefits of the things you download. The devs are under no obligation to keep you from bricking your phone, and to be fair, most everything is covered in the Superguide and the various ROM threads. Even if someone were to post a file called NOT_A_VIRUS.EXE and you downloaded it and it wiped your computer when you ran it, the responsibility is squarely on your shoulders.
As far as I remember, there is no dev/user contract and they're not getting paid for any of this.
Dxtra said:
As developer you should eliminate all threats and post a details instructions step by step with do's and don't before posting firmwares.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
oh?
am i being paid to do a job here?
i gave instructions based on how *I* got it to work and duplicated the procedure several times. so its MY responsibility to try and find a way to brick my phone for you?
an RUU cant brick your phone.....however, being a retard can.
this is the type of attitude i would expect my boss to have, if i screwed up a project....but alas, i am here out of my own free will.....
if this is how you feel, then you should get the F off this site.
formicae said:
As a user, you should understand the risks/benefits of the things you download. The devs are under no obligation to keep you from bricking your phone, and to be fair, most everything is covered in the Superguide and the various ROM threads. Even if someone were to post a file called NOT_A_VIRUS.EXE and you downloaded it and it wiped your computer when you ran it, the responsibility is squarely on your shoulders.
As far as I remember, there is no dev/user contract and they're not getting paid for any of this.
Click to expand...
Click to collapse
I totally 100% agree with you. If you HAVE taken the time to read and are still a bit confused, ask! For me I'm not even a week into this platform and I WILL NOT do anything that I don't entirely understand. The problem with android, if you could even call it a problem, is that there is such a huge variety of handsets and a big variety methods for doing this, that, and the other thing. It basically results in a non-linear process to get from point A to point B. It's imperative to understand the basic proceedures. If you were here since the G1, great, you've been able to.follow things from the start. I've used iOS for years, and I still love it btw.(only jailbroken of course!) I'll probably buy an iPad 3! The software is integrated with the hardware amazingly well, battery life is phenomenal, and ONCE JAILBROKEN, iOS is an excellent platform. Sure the "spec numbers" may not be as high but it boils down to.performance. That has always been great for me, obviously battery life is exceptional on apple devices as well. I'm hoping with a rooted ICS Rom there won't be cpu-time hogging processes and ill be able to adjust other things accordingly to get somewhat better battery life. I really wish each OEM would take the time to optimize the SW that they're using to the HW that they're selling. B/C from what I've seen the "Nexus" devices generally perform extremely well, even.against higher spec'd devices. So far I'm loving Android and my Vivid. I love the freedom that I get even on a non-rooted device! It's an excellent platform. Flexible, dynamic, and personal. Customization is there from the get-go. There are a million different things that one could do, even while staying un-rooted. The only reason that I've waited so long to get on board with android is ibwas waiting for it to grow and mature, if I could have a device that tri-booted Android, iOS, and WebOS I'd be a very happy person. I love using multiple platforms.
PG - I'm sorry if I bothered you, thanks for the great info though!
I think knowledge-wise I'm at a point where I'm not going to brick my phone. Wish me luck!
Pirateghost said:
oh?
am i being paid to do a job here?
i gave instructions based on how *I* got it to work and duplicated the procedure several times. so its MY responsibility to try and find a way to brick my phone for you?
an RUU cant brick your phone.....however, being a retard can.
this is the type of attitude i would expect my boss to have, if i screwed up a project....but alas, i am here out of my own free will.....
if this is how you feel, then you should get the F off this site.
Click to expand...
Click to collapse
Seriously if that is how you feel do get the f*ck off this site please. The devs in all mobile hacking communities are unpaid and do it for fun. You sir are a prime example of WHY THEY LEAVE!!! IF YOU DON'T KNOW AND HAVE READ, ASK, DON'T BE A ****!!!
Dxtra said:
This could off all been avoided with step by step Detail instruction. Why? Well example , I don't follow this forum at all never had an HTC phone but my wife's phone the vivid. All my phone has been Nexus and the galaxy line from Samsung, things over there are a bit different. All I did was flash the ph.img and then after not seen the device reboot I wipe/factory reset and all when to hell from there. Couldn't unlock the bootloader or reboot the phone. How could this happen? Assuming that people should know the basic is wrong. I'm not in any way blaming anyone I did this own my on risk but at the same time I'm super mad had to buy a new phone. As developer you should eliminate all threats and post a details instructions step by step with do's and don't before posting firmwares.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
REALLY? You want the UNNPAID DEV'S TO REMOVE ALL THREATS?!?!?! FROM WHAT IS BASICALLY OSS AND A FIRMWARE THAT SOMEBODY DL'D? REALLY? These guys take a FW and cook it into a ROM for FREE and just b/c you didn't take the time to understand it you're gonna put it on them? WTF?!?!?!?
i'll make him a deal. next time we get a hold of something like this, i will let him figure out how to get it on his phone....i don't have to share how...
Dxtra said:
This could off all been avoided with step by step Detail instruction. Why? Well example , I don't follow this forum at all never had an HTC phone but my wife's phone the vivid. All my phone has been Nexus and the galaxy line from Samsung, things over there are a bit different. All I did was flash the ph.img and then after not seen the device reboot I wipe/factory reset and all when to hell from there. Couldn't unlock the bootloader or reboot the phone. How could this happen? Assuming that people should know the basic is wrong. I'm not in any way blaming anyone I did this own my on risk but at the same time I'm super mad had to buy a new phone. As developer you should eliminate all threats and post a details instructions step by step with do's and don't before posting firmwares.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
You know, its users like you that get Devs frustrated and not want to share the work that they have accomplished. XDA is a site for Devs, its not a WalMart that people can stop by and expect to be spoonfed and be on their merry way. Pirateghost is a very talented Dev who wanted to share something with this community, and instead of saying "thank you" you decide to look a the glass as half empty instead of half full and EXPECT MORE from him?
Reading your post, it tells me that you dont frequent the HTC forums at all, and instead of reading up, you just decided to flash. Just because it didnt go as smoothly as you thought it would is NO REASON to tell a Dev that they needed to do more. That part lays on you.
Next time you decide to tell a Dev that "they need to do more" I think you need to do more reading so it prevents you from having to buy a new phone. If it dosent make sense to you or you dont think theres enough documentation/step-by-step instructions YOU HAVE THE POWER TO SAY NO AND NOT FLASH IT.
Uh, there's a reason every single solitary dev puts a disclaimer on their ROM threads. Their work, if directions are not followed to the letter can turn your device into a +/- 200$ paperweight. I've been lurking around these forums for a hot minute, rarely post ( not an ounce of dev skill being the main reason), and really, when's the last time a dev didn't post at least semi detailed instructions to go along with his/her OP.
@pirateghost- bought a vivid literally 12 hours ago, got home, saw your thread, FOLLOWED THE DIRECTIONS CAREFULLY, and now have ICS on my device. Just wanted to say thanks.
And now for the most epic noob question of all time. Wth is RUU? I'm very familiar with flashing roms, cam, tibu, etc from my days on the sgsII SR forums. So most if not all HTC terminology is new to me.
Sent from my HTC PH39100 using xda premium
Hi fellas having troubles here, trying to get an OTA update (I only want it because it fixes the annoying "sprint connections optimizer" popup), I flashed stock recovery, I'm rooted ofc, s-off, on stock rom and when I rooted my phone I also flashed h/k zip. But the difference with my case is that I don't even get to OTA update screen, no exclamation marks whatsoever, I press "install update now" while in Android OS, the phone turns off and boots in the bootloader menu. I restart the phone and of course nothing updated. I assume I'm doing something wrong, so maybe someone can help?
The H/K zip is most likely what's giving you problems.
Is there a way to uninstall it?
Flash the non H/K firmware...just be careful I know of at least 1 person that bricked going between the 2
I'm sorry to bother you again, that's probably stupid and against the rules, but I searched Sprint HTC One (M8) Forums here over and over for stock firmware and it did not end up well. Found this, but it seems like I shouldn't try it, judging by the first line, last messages and that its a closed thread. Also found that one, but it doesn't seem that it is stock, it says there are some tweaks and modifications made. I would go and google the stock firmware, but I don't know any other forums or websites I can trust, so could you please provide me a link with a stock firmware? I'm sorry again, but I really can't find it anywhere on these forums.
theleadwind said:
I'm sorry to bother you again, that's probably stupid and against the rules, but I searched Sprint HTC One (M8) Forums here over and over for stock firmware and it did not end up well. Found this, but it seems like I shouldn't try it, judging by the first line, last messages and that its a closed thread. Also found that one, but it doesn't seem that it is stock, it says there are some tweaks and modifications made. I would go and google the stock firmware, but I don't know any other forums or websites I can trust, so could you please provide me a link with a stock firmware? I'm sorry again, but I really can't find it anywhere on these forums.
Click to expand...
Click to collapse
Bottom of post 1
1.54.651.10
http://forum.xda-developers.com/showthread.php?t=2729173
This is just me reporting
I tried flashing 1.54.651.10 and it didn't really change anything, so I decided to flash it through the ARUwizard thought I was doing everything right and actually ended up with h/k firmware! Not bricked or anything, downloaded my OTA, just finished unlocking and rooting it now.
Anyway thanks so much, I "owe you a beer" for guiding me through :laugh:
sent you a little donation
Hi folks. So I haven't been on this site in a good while, but I've come across an issue that requires the help of someone with wisdom about the issue at hand. Up front, you should know that I'm not familiar with the whole rooting thing and even the technical terminology of most of it.
A little back story...I've recently purchased a Sprint HTC One M8 from someone. Everything works fine with the phone, there's nothing wrong with it at all. It's rooted and has s-off. I bought it that way. I asked the seller if he could unroot and take the phone back to full stock before the deal, but turns out he had someone else root and soff for him so he wasn't able to take it back to full stock. But he put the stock ROM back on it for me, though it's still rooted and has s off. I've provided pictures for those who are in the know to see for yourself, because I don't know what any of that software info means on those screens.
Here are my questions, and I'll put them in numerical format so there won't be any confusion in replying back:
1. From what you see in the pictures provided, are you able to to tell if it is in fact on the stock ROM or not?
2. I am receiving notifications that an official OTA update is available from Sprint/HTC:
A. What are the consequences of downloading and installing the OTA update(s)?
B. Will s-off be effected?
C. Will the root block the update from happening, or will it work fine since it's on stock ROM and has s-off?
D. Will it brick my phone if I update, or is there a chance at all that my phone will get bricked or stuck?
3. If I want to revert my Sprint M8 back to full stock (unroot and s-on), or maybe even put on a different ROM, how can I go about doing it?
4. What benefits do I have in keeping my phone in the state that it is currently in, that is, having rooted and s-off? And how can I take advantage of those benefits?
5. If I want to flash a different ROM or revert back to full stock (unroot and s-on), will it delete everything off my phone, including specifically my synced Gmail accounts?
6. As you can see in the picture with the 3 Android figures, at the top it says "tampered" and "unlocked." Does the "unlocked" mean that the phone is fully unlocked and can be used on any other service provider network, domestically and internationally?
Sorry about the length of this message, but I know there are some knowledgeable people on here who have wisdom and experience on the issue, so I would greatly appreciate any productive and helpful replies to my questions. If you have any questions for clarification please feel free to ask. Thanks!
If you choose recovery from the menu option in your first screenshot, what happens?
Captain_Throwback said:
If you choose recovery from the menu option in your first screenshot, what happens?
Click to expand...
Click to collapse
Hi Captain. I haven't tried anything because I wanted to seek help first and get answers to my questions before doing anything. That would be much appreciated. I also didn't want to risk bricking since I don't know anything about this stuff. What is recovery, what is it supposed to do?
1. Yes, it appears to be a stock rooted ROM. Appears to be the first update. There have been two since, including the most recent one from this past week.
2.Your software & firmware version will be updated. S-off won't be affected. You simply have to have the stock recovery installed to take the OTA. Taking the OTA won't brick your phone.
3. You can revert to S-on but I'm not even sure why you'd want to. If you want to unroot simply take the OTA after installing the stock recovery.
4. Hit the second link in my sig for more info.
5. If you flash a different ROM yes, your phone will get wiped and you'll need to set up your accounts again. If you take a OTA update your data won't be affected.
6. "Unlocked" means your bootloader is unlocked, plain and simple. See my answer to question #4 for more info.
As far as what recovery is, think of it as a very small and separate OS from the Android OS. It allows for the flashing of .zip files (ROM's, kernels, mods, etc.). It also allows you to back up your entire phone to either the internal storage or micro-SD card, among other things.
Take a look at this thread if you haven't already.
Magnum_Enforcer said:
1. Yes, it appears to be a stock rooted ROM. Appears to be the first update. There have been two since, including the most recent one from this past week.
2.Your software & firmware version will be updated. S-off won't be affected. You simply have to have the stock recovery installed to take the OTA. Taking the OTA won't brick your phone.
3. You can revert to S-on but I'm not even sure why you'd want to. If you want to unroot simply take the OTA after installing the stock recovery.
4. Hit the second link in my sig for more info.
5. If you flash a different ROM yes, your phone will get wiped and you'll need to set up your accounts again. If you take a OTA update your data won't be affected.
6. "Unlocked" means your bootloader is unlocked, plain and simple. See my answer to question #4 for more info.
As far as what recovery is, think of it as a very small and separate OS from the Android OS. It allows for the flashing of .zip files (ROM's, kernels, mods, etc.). It also allows you to back up your entire phone to either the internal storage or micro-SD card, among other things.
Take a look at this thread if you haven't already.
Click to expand...
Click to collapse
Thank you very much Magnum_Enforcer for the detailed and organized response. I will definitely be looking into the links you've mentioned/provided. Ideally, it would be great if I can somehow keep it rooted and have s-off while being able to take OTA updates. From that point I clean learn about and use the benefits from it being rooted with s-off, although I need to keep my Google accounts synced, so no flashing of ROMs for me.
So after reading your reply, I went ahead and tried taking the OTA, and after it turned off, it loaded up in the screen in the pic I've attached to this message. I'm assuming it doesn't seem I have the stock recovery as you said is required to take the OTA. How do I get the stock recovery on my phone in place of this "Team Win Recovery Project" recovery so that I can be able to take the OTA update properly? And will removing the current recovery and putting on the stock recovery effect s-off, root, or my synced accounts in any way?
P.S. I see you're in Birmingham. I actually grew up all over B'ham. Which part of town are you from?
L A Z I Z A said:
Thank you very much Magnum_Enforcer for the detailed and organized response. I will definitely be looking into the links you've mentioned/provided. Ideally, it would be great if I can somehow keep it rooted and have s-off while being able to take OTA updates. From that point I clean learn about and use the benefits from it being rooted with s-off, although I need to keep my Google accounts synced, so no flashing of ROMs for me.
So after reading your reply, I went ahead and tried taking the OTA, and after it turned off, it loaded up in the screen in the pic I've attached to this message. I'm assuming it doesn't seem I have the stock recovery as you said is required to take the OTA. How do I get the stock recovery on my phone in place of this "Team Win Recovery Project" recovery so that I can be able to take the OTA update properly? And will removing the current recovery and putting on the stock recovery effect s-off, root, or my synced accounts in any way?
P.S. I see you're in Birmingham. I actually grew up all over B'ham. Which part of town are you from?
Click to expand...
Click to collapse
That's why I asked you to select recovery in the first place. I could've told you whether it would've worked based on that.
I recognize you wanted answers to your questions, but in order to give you the most complete and accurate answer, all I asked was for you to check your recovery.
Captain_Throwback said:
That's why I asked you to select recovery in the first place. I could've told you whether it would've worked based on that.
I recognize you wanted answers to your questions, but in order to give you the most complete and accurate answer, all I asked was for you to check your recovery.
Click to expand...
Click to collapse
There's no need for quarrel or to take anything personal. It's not as if I ignored you, I replied back to you. I'm here to seek answers and help, I've no interest in disagreements. Sorry if you feel that way. I'm sure you're quite knowledgeable and experienced enough to have been able to tell me the same, if not more. The response I received from Magnum just happened to be complete and informative enough to me to let me know it was ok to try it out. I like to know at least a little about what I'm doing before jumping into something. That's just the way I am, people are different.
I sought help again in my last response though, and if you're still interested in helping, it would be appreciated. If not, I would understand, no worries or hard feelings.
You won't be able to take the OTA with TWRP installed. You can find the stock recovery in the first post of the link below. There are also instructions on how to install it. Once installed you can boot back to the OS and take the OTA.
Stock Backups + OTA's
To answer your other question, I've lived in several different places all over the state over the years but now live in the northern part of Jefferson county, outside of the city of Birmingham (you couldn't pay me to live in the city limits of B'ham).
Sent from my HTC M8
I'm not sure if I'm posting this in the right thread or not, and I do hope that I'm not wasting anyone's time. However, I have searched and searched and have gone through an insane amount of trial and error to no avail. I have just recently purchased an HTC One M8 for Sprint and the lcd underneath the glass got cracked when it fell and so, I assumed that I'd take advantage of the Advantage program, and all seemed well, except I had previously unlocked the bootloader using htcdev and have been running stock rooted with TWRP recovery. I've tried so many methods of getting back to stock, at least enough to argue with HTC into fixing my screen, since it has no bearing on hardware. I'm now s-off with a relocked bootloader and root, and I'm lost. I've trying to use RUU files to recover my device, but everytime, I get a bad zip file. And when I tried flashing the firmware anyways using adb it looked exactly the same, in fact the only thing different is that TWRP was gone and booting into recovery simply got me a picture of a phone with an exclamation point in a red triangle. I don't know if they're corrupted or if I'm just dumb. I apologize for any inconvenience. Please help, I've just spent 650 dollars on this phone and I'm out of money. Thank you for your time and any suggestions you may give, I sincerely appreciate it.
MrCeroSombra said:
I'm not sure if I'm posting this in the right thread or not, and I do hope that I'm not wasting anyone's time. However, I have searched and searched and have gone through an insane amount of trial and error to no avail. I have just recently purchased an HTC One M8 for Sprint and the lcd underneath the glass got cracked when it fell and so, I assumed that I'd take advantage of the Advantage program, and all seemed well, except I had previously unlocked the bootloader using htcdev and have been running stock rooted with TWRP recovery. I've tried so many methods of getting back to stock, at least enough to argue with HTC into fixing my screen, since it has no bearing on hardware. I'm now s-off with a relocked bootloader and root, and I'm lost. I've trying to use RUU files to recover my device, but everytime, I get a bad zip file. And when I tried flashing the firmware anyways using adb it looked exactly the same, in fact the only thing different is that TWRP was gone and booting into recovery simply got me a picture of a phone with an exclamation point in a red triangle. I don't know if they're corrupted or if I'm just dumb. I apologize for any inconvenience. Please help, I've just spent 650 dollars on this phone and I'm out of money. Thank you for your time and any suggestions you may give, I sincerely appreciate it.
Click to expand...
Click to collapse
did u do a backup prior to rooting? if yes, restore backup & flash the stock recovery
if no, RUU is your best bet. make sure you're extracting the 0P6BIMG.zip from Sprint_HTC_One_M8_1.54.651.10_RUU.zip using 7zip, to your ext sd card, then boot into bootloader
u can also use the older Sprint_HTC_One_M8_1.54.651.8_RUU.zip which has a exe to flash from pc
Thank you. When I attempted flashing the stock recovery, I'd gotten the red exclcmation screen. And when I try using 7 zip on the actual 0P6BIMG.zip it says zip is invalid, is this just normal?
MrCeroSombra said:
Thank you. When I attempted flashing the stock recovery, I'd gotten the red exclcmation screen. And when I try using 7 zip on the actual 0P6BIMG.zip it says zip is invalid, is this just normal?
Click to expand...
Click to collapse
red exclamation screen is stock recovery....no, you can't open 0P6BIMG.zip, it's encrypted...just copy to ext sd
Wait. So flashing stock recovery did work then? I feel, really foolish if thats the case. I was only wondering about it because I did not see any text up top. But, thank you so much! If that's it then I'm done. Now to send it off and convince htc to fix it. Thank you
MrCeroSombra said:
Wait. So flashing stock recovery did work then? I feel, really foolish if thats the case. I was only wondering about it because I did not see any text up top. But, thank you so much! If that's it then I'm done. Now to send it off and convince htc to fix it. Thank you
Click to expand...
Click to collapse
yeah, your only indication of stock recovery is the red exclamation
MrCeroSombra said:
I'm not sure if I'm posting this in the right thread or not, and I do hope that I'm not wasting anyone's time. However, I have searched and searched and have gone through an insane amount of trial and error to no avail. I have just recently purchased an HTC One M8 for Sprint and the lcd underneath the glass got cracked when it fell and so, I assumed that I'd take advantage of the Advantage program, and all seemed well, except I had previously unlocked the bootloader using htcdev and have been running stock rooted with TWRP recovery. I've tried so many methods of getting back to stock, at least enough to argue with HTC into fixing my screen, since it has no bearing on hardware. I'm now s-off with a relocked bootloader and root, and I'm lost. I've trying to use RUU files to recover my device, but everytime, I get a bad zip file. And when I tried flashing the firmware anyways using adb it looked exactly the same, in fact the only thing different is that TWRP was gone and booting into recovery simply got me a picture of a phone with an exclamation point in a red triangle. I don't know if they're corrupted or if I'm just dumb. I apologize for any inconvenience. Please help, I've just spent 650 dollars on this phone and I'm out of money. Thank you for your time and any suggestions you may give, I sincerely appreciate it.
Click to expand...
Click to collapse
When you use HTCDEV you void the warranty and they'll most likely charge you to fix it since you literally gave them the info about your phone to unlock the bootloader. Had a previous experience like this.
Using this guy's guide for the Nexus 5 I had no issues, bought a N6 today and was giddy to flash on Cataclysm for N6 and figured might as well use same person's guide for next phone up.
http://www.androidrootz.com/2014/12/how-to-root-nexus-6-windowsmaclinuxubun.html
Was able to unlock bootloader, then installed TWRP but now am getting the 'corrupt phone' message, however unlike others like I have read on XDA, am unable to boot up by just letting it sit. Screen turns off and that's that. Before beginning entire process I enabled "enable/allow oem unlocking". I'm assuming that when the phone factory resets after the bootloader unlock I need to go back in and recheck 'allow oem unlock' in dev options, but I didn't as I assume/ed that it wasn't necessary and the guide doesn't tell you to.
Tried relocking the bootloader to maybe get phone to open up, but terminal tells me that I need to have 'allow oem unlock' checked. Nice Catch-22 http://puu.sh/moOUf/d0f8fa9050.png
Tried formatting data from within TWRP and factory resetting/wiping everything but it tells me that it is unable to mount '/data'
Have since tried WugsToolkit and flashing to stock with 'softbricked' option enabled the shamu-mmb29k-fact....tgz image that I downloaded and imported myself into Wugs (was taking 10 minutes to dl 1%). That seemed to work and told me it was a success, however when I then went back to re-enable the bootloader via wugs it fails and reboots with the lock sign still open and boots again onto 'corruption' screen that then flashes off and turns phone off, left it for 30 minutes at one point and didn't boot so don't think I'm lucky enough to be able to sit if through like others who had that issue
Where to go from here? Really hoping I didn't brick this phone less that 3 hours after getting it. I can still boot and see the Google screen and can get onto the bootloader and used to be able to get into recovery (since wugs have been getting the android with red triangle)
Been rooting/rom'ing since day one that I've had androids. Had a Samsung Apollo with CM on it, same for the Nexus S, then the Galaxy Nexus, then the N5 and looks like my chain of no issues ended tonight
Anything you can do for guys would be greatly appreciated. No clue where to go from here....
So from what I gathered, I think you are in luck. It sounds like your bootloader is unlocked. This is a very good thing. Under no circumstances do you want to try to re lock it right now or do you ever when stuck not being able to boot or any issues like that. If you lock it while stuck, thats when you are soft bricked. If I remember correctly, I got myself in the same situation , although maybe with out a custom recovery installed. None of that matters though. The way to fix this is to reflash the the factory image. Here are the guides for that.
https://www.youtube.com/watch?v=K_m6bYNKrXQ
This is the video I used the first time. A bit rough but, It did the job.
https://www.youtube.com/watch?v=2hao_Yf-gaw
Here is a bit of a nicer one. I used it the second time around.
and lastly here is an xda post http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008
I would recommend reading and watching all of these and maybe doing more research so you really knows whats going on. The flash-all script is not going to work from what I've read and I've always done it manual so go with that. It may also be a good idea to keep the custom recovery, so look into to keeping that. Maybe it is as simple as not erasing the recovery partition and not flashing the recovery image. This is what should save your nexus.
Now, I am fairly new to the Rooting and ROMming, really only started 2 months ago, so I would really appreciate if any of the more experienced guys on XDA can confirm what I said. Please don't try any of this without confirmation from another member here, I do not want to be responsible for sending your device past the point of no return. I recently had to order a new Nexus 6 as the screen is dead, so I know it's frustrating to have that loss. In your case, as long as that boot loader is unlocked, you should be safe. Best of luck to you.
DO NOT RELOCK THE BOOTLOADER!!!!! I cannot emphasize how critical it is that you do not relock the bootloader, given the position you are in. If you somehow manage to relock the bootloader and "enable OEM unlock" is toggled off and Android will not boot (even after attempting a factory reset), then you are 100% bricked with no way to fix your phone. Personally, I leave my bootloader unlocked 100% of the time so that I can fix anything that may go wrong with my phone. Additionally, I (as well as many other users on here) will always advise against using Wug's or any other toolkit in order to do stuff to your phone. While they do provide a nice GUI as well as an easy way to install the necessary drivers, using the regular platform-tools command line method isn't all that hard to figure out, and it allows you to know exactly what you have done to your phone. With Wug's and the like, you never really know what commands that they are running and exactly at what point in the process a flash may fail. Right now, I would advise you to read up on using the platform-tools method to flash stock images. After you have all of the necessary drivers, platform-tools, etc. working properly on your computer, I would strongly advise that you download MMB29S (the latest official update) from the Google Developer page and flash it using the platform-tools method, NOT with Wug's. And whatever you do, I repeat, DO NOT LOCK YOUR BOOTLOADER!
---------- Post added at 07:03 AM ---------- Previous post was at 06:51 AM ----------
triguyrn said:
So from what I gathered, I think you are in luck. It sounds like your bootloader is unlocked. This is a very good thing. Under no circumstances do you want to try to re lock it right now or do you ever when stuck not being able to boot or any issues like that. If you lock it while stuck, thats when you are soft bricked. If I remember correctly, I got myself in the same situation , although maybe with out a custom recovery installed. None of that matters though. The way to fix this is to reflash the the factory image. Here are the guides for that.
https://www.youtube.com/watch?v=K_m6bYNKrXQ
This is the video I used the first time. A bit rough but, It did the job.
https://www.youtube.com/watch?v=2hao_Yf-gaw
Here is a bit of a nicer one. I used it the second time around.
and lastly here is an xda post http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008
I would recommend reading and watching all of these and maybe doing more research so you really knows whats going on. The flash-all script is not going to work from what I've read and I've always done it manual so go with that. It may also be a good idea to keep the custom recovery, so look into to keeping that. Maybe it is as simple as not erasing the recovery partition and not flashing the recovery image. This is what should save your nexus.
Now, I am fairly new to the Rooting and ROMming, really only started 2 months ago, so I would really appreciate if any of the more experienced guys on XDA can confirm what I said. Please don't try any of this without confirmation from another member here, I do not want to be responsible for sending your device past the point of no return. I recently had to order a new Nexus 6 as the screen is dead, so I know it's frustrating to have that loss. In your case, as long as that boot loader is unlocked, you should be safe. Best of luck to you.
Click to expand...
Click to collapse
Regarding the flash-all script, my friend and I just used the script included with MMB29S and it worked fine. In addition, I was able to use the one with MMB29K, MRA58K and MRA58R, all of which worked fine. I'm not sure if these scripts always work for some users and never work for others, but I always recommend that people who are new to flashing simply try them, as they are quite convenient when they work. In addition, I have only been in the rooting and ROMing scene for about a month or two as well, but I would consider myself pretty seasoned by now considering all the different ROMs, rooting methods, etc. that I have tried. All the advice that you gave to the OP is excellent and I agree with it all.
matthew2926 said:
Regarding the flash-all script, my friend and I just used the script included with MMB29S and it worked fine. In addition, I was able to use the one with MMB29K, MRA58K and MRA58R, all of which worked fine. I'm not sure if these scripts always work for some users and never work for others, but I always recommend that people who are new to flashing simply try them, as they are quite convenient when they work. In addition, I have only been in the rooting and ROMing scene for about a month or two as well, but I would consider myself pretty seasoned by now considering all the different ROMs, rooting methods, etc. that I have tried. All the advice that you gave to the OP is excellent and I agree with it all.
Click to expand...
Click to collapse
Thank you. I always wanted to try the flash-all script but, I ahve read a few places it wouldn't work and haven't had the chance to give it a try lately. When my new device arrives in a day or two, I'll give it a shot. Thanks for the confirmation, makes me feel good knowing I'm starting to get the hang of this stuff
triguyrn said:
Thank you. I always wanted to try the flash-all script but, I ahve read a few places it wouldn't work and haven't had the chance to give it a try lately. When my new device arrives in a day or two, I'll give it a shot. Thanks for the confirmation, makes me feel good knowing I'm starting to get the hang of this stuff
Click to expand...
Click to collapse
No problem! It's too bad to hear about your device but at least you got a new one on the way. There is really no harm to at least trying the flash-all script. It will either work and save you time or fail halfway through and force you to flash everything manually.
triguyrn said:
Thank you. I always wanted to try the flash-all script but, I ahve read a few places it wouldn't work and haven't had the chance to give it a try lately. When my new device arrives in a day or two, I'll give it a shot. Thanks for the confirmation, makes me feel good knowing I'm starting to get the hang of this stuff
Click to expand...
Click to collapse
Flash-all script is still broken, flash the img files individualy in fastboot.
gee2012 said:
Flash-all script is still broken, flash the img files individualy in fastboot.
Click to expand...
Click to collapse
You guys are life savers, thank you so much
Got it to work after I was getting ready to phone it in and bring it to a repair shop and eat whatever the charge might've been