Related
I'm just wondering, I purchased a phone on ebay (not knowing it was flashed/rooted). The boot animation says "clean rom" so after researching this site and the forums for this device, I see that it's probably a rom you guys are familiar with and it seems to be ICS based (from what I can see). With that being said, does this mean when they actually RELEASE the stock ICS that I probably won't get the update to my phone? Because I really would like to see what their stock version will be like. Can anyone answer that question or has it even been asked before?
you can't take the OTA rooted or while unlocked but you can flash the RUU once it gets posted after relocking your phone. hopefully by then we will have s-off.
mighty_markus12 said:
you can't take the OTA rooted or while unlocked but you can flash the RUU once it gets posted after relocking your phone. hopefully by then we will have s-off.
Click to expand...
Click to collapse
So does this mean I will no longer be able to receive updates to my phone with this "s-off" or what ever? That sucks, and I can't seem to follow the steps that have been given to get it back to a stock rom or "ruu" what ever THAT means. lol ****that moment when you realize you might look dumb or "newbish" for posting what you just posted****
Your phone has been hacked a little bit, and it's always going to have tell-tale signs.
The worst case scenario is that you have to manually install the next official update and manually relock the phone, which will always say "Relocked" in the boot menu. But if you do everything by the book you should be able to get it back to stock in every other way, including taking subsequent updates over the air normally.
If they get s-off working and you're willing to experiment, it may be possible to completely revert the phone to stock. But that's quite a bit more hackage in order to get your phone "unhacked."
cpurick said:
Your phone has been hacked a little bit, and it's always going to have tell-tale signs.
The worst case scenario is that you have to manually install the next official update and manually relock the phone, which will always say "Relocked" in the boot menu. But if you do everything by the book you should be able to get it back to stock in every other way, including taking subsequent updates over the air normally.
If they get s-off working and you're willing to experiment, it may be possible to completely revert the phone to stock. But that's quite a bit more hackage in order to get your phone "unhacked."
Click to expand...
Click to collapse
To be honest, the only thing I really want is to be able to get it stock on the basis of the apps, getting system updates etc. I'm not concerned with it having evidence of being "tampered with" "hacked" or "rooted". lol It already says "re-locked" The problem is the instructions I've gotten on here seem to go over my head. I might have to be walked through it like a little 3 or 4 year old being taught to sound out little words for the first time. lol Hey, I'm just saying..... No seriously though, I have a MAC and all of the instructions here seem to be based on having a PC
This can be done. But you're going to need to have somebody who knows what they're doing relock and reset your phone from the official ICS RUU after it's released, probably from a PC. There's nothing can be done before then.
cpurick said:
This can be done. But you're going to need to have somebody who knows what they're doing relock and reset your phone from the official ICS RUU after it's released, probably from a PC. There's nothing can be done before then.
Click to expand...
Click to collapse
So this means I'll need to basically need to take or send it to someone to get this done? I don't know why all of these instructions seem like their in spanish to me now, about 3 years ago I used to flash and unlock WM devices almost every other day. I guess I should've never stopped, but once the g1 came out and switched to android devices I stopped flashing and now I'm lost because I need to "tamper with" my phone again, but can't seem to get going at all. I mean SERIOUSLY, I used to flash WM devices so often that if a certain period of time went by without me finding a rom worth "flashing" I'd start having withdrawals. Now i'm feeling like an absolute IDIOT when it comes to getting into these android devices. I think part of that has to do with the fact that I only had PC's and now not only am I trying to tamper with android for my first time, but I only have mac computers as well.
Go to settings, about phone, software information, more, and write what your baseband version is.
http://forum.xda-developers.com/showthread.php?t=1417839
This thread may help you getting osx and fastboot going so you can relock and run an ruu. As was stated above, what is your baseband? If the previous owner flashed the leaked ics you will not be able to go all the way back to stock until either an official ics is released or the s-off tool is released. Good luck!
Sent from my ADR6425LVW using XDA
Unless you have issues, I would leave it as is for the time being. Take time to learn how to do all the stuff you need to do.
The custom ROMs really do make the phone better, you may find you want to keep it in the end. Battery life is much better on a good ROM.
When the official update comes out, we will have a new ROM based on the update within a day or two at most of the release anyway.
The baseband (the radio firmware) is also important. And unfortunately we can not downgrade to older basebands due to not having S=off. So if you are on the newest leaked version then you can run the old stock software.
BTW S=off (or S=on) is a security flag located in the firmware. S=on limits what parts of the phone you can flash and change. S=off gives you full access, it will allow you to downgrade as well. S=off also makes it easier to brick your phone because it does let you change software that is bootstrap essential, the baseband and hboot (sort of like BIOS) for example.
I separate the idea of bootstrap from boot. Most people associate booting with the OS, but bricking effects the firmware initializing the hardware that allows the OS to load and boot. So you get to see the old school term used.
Kennnny1 said:
http://forum.xda-developers.com/showthread.php?t=1417839
This thread may help you getting osx and fastboot going so you can relock and run an ruu. As was stated above, what is your baseband? If the previous owner flashed the leaked ics you will not be able to go all the way back to stock until either an official ics is released or the s-off tool is released. Good luck!
Sent from my ADR6425LVW using XDA
Click to expand...
Click to collapse
The baseband is 1.22.10.0310r, 1.22.10.0308r It also says clean rom 4.1. I don't mind waiting until an offcial ics is released, but I will I be able to receive THAT instead having to have a "dev equivalent" version is what I'm wondering....
It's like I said. Those radios are new, and part of a firmware upgrade that can't be completely backed out. Your simplest bet is to wait for the official ICS release, and then you (or someone more technical) can apply it manually. After doing that and relocking your phone, it should start to take updates automatically again. You'll also have the full factory-installed "bloatware" suite of software.
It's possible to downgrade all the other parts of your software manually back to the latest stock release, but it's expected that your current upgraded firmware version will continue to prevent you from taking OTA releases. It would be good training, actually, though you'll get better results and more support from a PC than on a Mac. If you figured out how to do all this, then you could get your phone back on the HTC software track yourself.
Depending on your flexibility, maybe you can find someone here you could send your phone to who can put it back on the official release track. But even they won't be able to put a permanent fix on it until the official ICS release comes out and somebody uploads it as a manually-installable package.
---------- Post added at 10:08 AM ---------- Previous post was at 09:29 AM ----------
EDIT:
So did the seller not mention on eBay that the phone had been customized?
Some of the responses lean toward telling you how to flash your phone for yourself. Is that something you'd have any interest in? Do you really want to go back to stock, or do you just want to see the difference?
Are you having any problems with the phone?
The custom ROMs are better, overall, but they usually have one or two bugs that you have to learn to live with. (Which is not to say that stock ROMS are bug-free, though the final versions of stock ROMs tend to be very, very stable.) But if you are on custom ROMs, then you're completely off the automatic update path, and everything will have to be done manually.
So unless you want to learn how to flash your own phone, the only way to get updates is to set it back to stock so HTC and Verizon can handle the updates for you. And therein lies the dilemma, because that in itself is something which must be flashed manually from where you're currently at.
(Oh, and you're probably going to end up losing any of your own customizations in the process, though the data on your SD card should be safe.)
cpurick said:
It's like I said. Those radios are new, and part of a firmware upgrade that can't be completely backed out. Your simplest bet is to wait for the official ICS release, and then you (or someone more technical) can apply it manually. After doing that and relocking your phone, it should start to take updates automatically again. You'll also have the full factory-installed "bloatware" suite of software.
It's possible to downgrade all the other parts of your software manually back to the latest stock release, but it's expected that your current upgraded firmware version will continue to prevent you from taking OTA releases. It would be good training, actually, though you'll get better results and more support from a PC than on a Mac. If you figured out how to do all this, then you could get your phone back on the HTC software track yourself.
Depending on your flexibility, maybe you can find someone here you could send your phone to who can put it back on the official release track. But even they won't be able to put a permanent fix on it until the official ICS release comes out and somebody uploads it as a manually-installable package.
---------- Post added at 10:08 AM ---------- Previous post was at 09:29 AM ----------
EDIT:
So did the seller not mention on eBay that the phone had been customized?
Some of the responses lean toward telling you how to flash your phone for yourself. Is that something you'd have any interest in? Do you really want to go back to stock, or do you just want to see the difference?
Are you having any problems with the phone?
The custom ROMs are better, overall, but they usually have one or two bugs that you have to learn to live with. (Which is not to say that stock ROMS are bug-free, though the final versions of stock ROMs tend to be very, very stable.) But if you are on custom ROMs, then you're completely off the automatic update path, and everything will have to be done manually.
So unless you want to learn how to flash your own phone, the only way to get updates is to set it back to stock so HTC and Verizon can handle the updates for you. And therein lies the dilemma, because that in itself is something which must be flashed manually from where you're currently at.
(Oh, and you're probably going to end up losing any of your own customizations in the process, though the data on your SD card should be safe.)
Click to expand...
Click to collapse
Well, I've kind of decided to just keep what I have. I don't have any issues other and it seems to run smoothly. What I REALLY want to see is what the official update will be like as being "stock released" when it comes out and was concerned that I might not be able to get the update because of the "clean rom" I have now being ICS based (as far as I can see). Other than that, I'm fine until then.
You really should consider leaving negative feedback if they ebay seller did not state in the auction that the phone was rooted and running a custom rom. If I sell a phone and im too lazy to revert it to stock ill ALWAYS state its rooted and what its running in the auction etc
mdunn1066 said:
You really should consider leaving negative feedback if they ebay seller did not state in the auction that the phone was rooted and running a custom rom. If I sell a phone and im too lazy to revert it to stock ill ALWAYS state its rooted and what its running in the auction etc
Click to expand...
Click to collapse
Good point, I mentioned it in the feeback portion and rated him low on the "item described accurately" portion
I would just wait til offiical ics is released. I am sure there will be instructions here on xda on how to relock and flash the new official ics ruu. It will involve downloading some files and entering items into command prompt from PC.
sent from my Rezound
stelv said:
I would just wait til offiical ics is released. I am sure there will be instructions here on xda on how to relock and flash the new official ics ruu. It will involve downloading some files and entering items into command prompt from PC.
sent from my Rezound
Click to expand...
Click to collapse
The problem is I don't HAVE a PC. It's already "re-locked" though. I just want to be able to receive the update without having to deal with any other flashing etc. But from what I was told, I should be able to since the current flashed rom is nearly stock (clean rom) and I'm already re-locked. But I guess we'll just see....
refuse2bstopped said:
The problem is I don't HAVE a PC. It's already "re-locked" though. I just want to be able to receive the update without having to deal with any other flashing etc. But from what I was told, I should be able to since the current flashed rom is nearly stock (clean rom) and I'm already re-locked. But I guess we'll just see....
Click to expand...
Click to collapse
seems like people are giving you information that is kinda all over the place.
Lemme try and help clear this up, since you are in a odd scenario.
You are running cleanrom 4.1 on a re-locked phone. For starters, cleanrom 4.1 is based off the current ics LEAK and is not an official OTA update. Chances are high you won't be able to get the OTA if the rom is not a stock rom, and also because chances are you don't have a stock recovery even though it is relocked. Since you are currently on the latest leaked firmware, not an official firmware, you can run the RUU for the phone and go back to stock. In your case, your kinda lucky with this, as you don't technically need a computer to run it. You would need someone to extract the PH98IMG.zip file from the RUU.EXE file for you to run when the OTA comes out through Hboot.
Be for warned, doing it like this, will wipe all data.
I would say you should run the leaked RUU on the phone, as since it is a beta testing Leak, you should still get the OTA, and that way the phone will think it is completely stock and get the latest update.
If you wanna do this, ask and we can help you.
nosympathy said:
seems like people are giving you information that is kinda all over the place.
Lemme try and help clear this up, since you are in a odd scenario.
You are running cleanrom 4.1 on a re-locked phone. For starters, cleanrom 4.1 is based off the current ics LEAK and is not an official OTA update. Chances are high you won't be able to get the OTA if the rom is not a stock rom, and also because chances are you don't have a stock recovery even though it is relocked. Since you are currently on the latest leaked firmware, not an official firmware, you can run the RUU for the phone and go back to stock. In your case, your kinda lucky with this, as you don't technically need a computer to run it. You would need someone to extract the PH98IMG.zip file from the RUU.EXE file for you to run when the OTA comes out through Hboot.
Be for warned, doing it like this, will wipe all data.
I would say you should run the leaked RUU on the phone, as since it is a beta testing Leak, you should still get the OTA, and that way the phone will think it is completely stock and get the latest update.
If you wanna do this, ask and we can help you.
Click to expand...
Click to collapse
Yes, I'm VERY interested, I'm not worried much about the data wipe, between what's backed up to my google account and my SD card, I'll be fine with a data wipe. My battery life is also HORRIBLE for some reason with this rom, but since I've not had it stock yet, I guess I can't REALLY say it's good or bad. But my Droid Bionic's battery life was at least twice as good as this phone's seem to be and I don't use it any more than I did the Bionic.
I will tell you right now the battery life will most likely get worse if you go to stock.
Now if the person who sold it installed a custom kernel rather than the one Scott includes in his ROM (scott makes clean ROM) then battery life could be worse than it should be.
Second, this is a 4.3 inch HD screen... it eats battery like a starving animal.
Third, try cleanROM developers edition (a very striped out cleaned up stock based ROM) or cleanROM senseless. I am running cleanROM developers edition and I get double to triple the battery life over stock.
Unless I actually use the phone... When I use it a lot, I do not get that big of a jump. When using the phone the battery life will be similar due to the screen and CPU use remains similar to what stock would be. (which you would expect, the screen will always use the same power, same for CPU) Its when the phone is in standby mode that you see the real gains. Because all the extra junk that is in the stock software is pulled out and isn't constantly running in the background, waking the phone, starting the cell radio to phone home, etc.
Senseless and the Developers edition have their quirks caused by removing so much of the stock sense based apps and functions and replacing with AOSP versions. Thinks like the caller ID not showing up on the screen until you unlock the phone because the sense phone/dialer can not talk to the AOSP lockscreen. Nothing major just different.
I have a stock rom evo 4g LTE, rooted, with Android 4.0.3 on it.
I forget the root app I used, some one click thingy, I guess my bootloader is unlocked
because I get a boot menu every time I reboot, on that screen that says **TAMPERED**.
Anyway, I ignored the notification icon in my taskbar for OTA updates, for a very long time.
Since the day I bought it over a year ago.
Finally I decided "eh, screw it, why not." ...I'm sure I'll regret that.
I told it to do the OTA update, and it downloaded (I think??) and rebooted.
The icon went away. Seemed to be a done deal.
But once per day since then, my phone rings, and I see a prompt saying
there's an OTA update, and would I like to install it now?
I think it's the same OTA update being prompted repeatdly,
because the filesize is always the same (~42 megs).
What should I do? I can choose install, reboot, and be fine for the rest of the day,
or choose cancel, reboot, and be fine for the rest of the day.
Doesn't seem to matter. But would be nice to fix it for good.
Well, considering that you are about 4-5 OTAs behind the rest of the community, I would say that the notification is probably correct. HOWEVER, of you are not using the stock recovery, then the OTA did not flash. Yes, the phone rebooted, but that's because it is installed entirely through recovery, and the phone has to reboot to get into recovery mode in the first place.
Now, for the more important question at hand....why exactly are you still using ICS? Furthermore, if you are still using ICS, then why are you rooted? As far as I'm concerned, the OTAs are actually necessary updates for the phone. I'm sure that you will love Jelly Bean if you have never used it before.
And please, for the sake of us all who are cringing at the sight of the first sentence....PLEASE UPDATE your phone! If you have a good reason not to, please share.
Hi, thanks for the reply... Maybe they were all different updates after all.
I haven't been prompted to update again since my post.
Maybe I grabbed the 3 or 4 OTA updates that I needed to catch up on.
I do think I'd like Jelly Bean too, seeing some of the features is what prompted me to finally catch up.
Can you explain this part to me? I'm not familiar with this stuff.
HOWEVER, of you are not using the stock recovery, then the OTA did not flash.
Yes, the phone rebooted, but that's because it is installed entirely through recovery,
and the phone has to reboot to get into recovery mode in the first place.
Click to expand...
Click to collapse
So, there's more than one recovery mode, the stock one, and ...whatever else you can install?
When I see the white screen that says **TAMPERED** (looks basically like this screen)...
should I have chosen Recovery instead of the usual reboot option?
If I no longer see the notification, does that mean the updates worked? My Android version still shows 4.0.3.
why exactly are you still using ICS? Furthermore, if you are still using ICS, then why are you rooted?
Click to expand...
Click to collapse
Well, I had no compelling reason to upgrade. I still don't really, the phone does what I want,
I just saw some of the features in the next version and thought "huh, that sounds pretty cool".
I'm rooted for all the usual reasons... I want to be able to browse, copy, move, rename files (including system files)
without incident... use nandroid for backups... wifi tether (still can't get that to work actually)... install unapproved apps...
tweak the OS, and so on.
Ok, my friend...let me educate you. Instead of giving you the simplest, fastest solution, I will actually try to answer all of your questions, since you did ask.
I do think I'd like Jelly Bean too, seeing some of the features is what prompted me to finally catch up.
Can you explain this part to me? I'm not familiar with this stuff.
Click to expand...
Click to collapse
To give a very superficial explanation of Jelly Bean, it is everything that ICS does, and more. It just does it smoother. It also brings Google Now, which was – and still is – the selling point of Jelly Bean. The Sense launcher got a few changes, too, but you will have to explore those changes on your own (mainly because I don’t remember them off hand, and this post is beginning to become lengthy).
Maybe I grabbed the 3 or 4 OTA updates that I needed to catch up on.
If I no longer see the notification, does that mean the updates worked? My Android version still shows 4.0.3.
Click to expand...
Click to collapse
If the first update didn’t update properly, then the phone is simply downloading and trying to install the same update over and over. When you boot back into Android after a successful update, you will be greeted by a welcome message congratulating you for installing the new version.
If you are rooted, odds are, you are using a custom recovery, such as TWRP or CWM. OTAs are only installed through the stock recovery & a locked bootloader. The stock recovery doesn’t make nandroids, or do anything of the sort. To install the stock recovery, go here:
http://downloadandroidrom.com/file/HTCEvo4GLTE/rooting/Evo4GLTERoot2.zip
Click to expand...
Click to collapse
The stock recovery is located somewhere within the zip file.
So, there's more than one recovery mode, the stock one, and ...whatever else you can install?
When I see the white screen that says **TAMPERED** (looks basically like this screen)...
should I have chosen Recovery instead of the usual reboot option?
Click to expand...
Click to collapse
You can flash install the stock recovery by using fastboot commands from the bootloader (which is the screen that shows the TAMPERED status on the top), or you can use Flash Image GUI. It is a paid app on the Play Store, or you can get it from XDA (the dev let XDA users download it for free…Google it).
Lastly, there are a few things that I suggest that you do. First, obtain S-Off (Google, Google, Google...very simple), so you can install the new firmwares directly, instead of using OTAs. Otherwise, if you accept the OTA, you will lose root, and you will have to root your phone again and again. Installing the firmware, then the new rom is the same as accepting the OTA, then rooting.
Another alternative is to get S-Off, then accept the OTA (after installing the stock recovery). Your bootloader does not need to be locked, and there are recovery zips floating around here that can be installed through the bootloader (therefore, you will not be stuck rooting the phone the hard way, just boot into recovery and flash SuperSU). I highly suggest achieving S-Off.
If you want to jump straight to the latest version (Android 4.3, Sense 5.0) by installing the RUU located somewhere in this forum. I actually suggest that you try Sense 4 with Jelly Bean first, but that is completely up to you. Keep in mind that using the RUU will wipe your internal memory, so back up what needs to be backed up. This doesn’t require you to be rooted, and the state of the bootloader does not matter. It will lock the bootloader, load the stock recovery, and you will lose root. You won’t be able to downgrade without S-Off.
Other Notes:
When using the 4.3 RUU, make sure that Android USB Debugging is enabled.
Bookmarking for later but I wanted to say thanks for the thorough reply!
I can confirm the update never worked, because I never got the confirmation message
and I got prompted again a few hours after I posted.
Are you willing to answer just a few more things?
Based on what I've read, it sounds like this is what I ought to do:
- Back up anything I need to. Just to confirm, updating firmware and flashing a new rom wipes out everything in the phone's internal memory, but not external SDcard? Or both?
Are apps considered "on the cloud" and I can reinstall by just redownloading, without paying again?
Except sideloaded apps? Or will I need to find all those APK files and save them somewhere else?
Is it safe to say they're all in \data\app and \system\app? Or would system\app be unwanted since it's what came with the old phone OS?
- Get my phone into S-OFF status.
- Update firmware (this is a separate process from updating the rom? Where do I get this firmware? Google google google?)
- Install a new ROM (stock or otherwise) which will have these updates built in, so I won't need to regain root.
- Not sure what my bootloader is, maybe TWRP, does it matter? Do the above steps affect it? Should I change it to stock anyway?
- You suggested trying Sense 4 rather than Sense 5 first... any special reason?
Are you willing to answer just a few more things?
Click to expand...
Click to collapse
As always, I'm open for questions. Not to sound egotistic, but I enjoy sharing my opinion.
Based on what I've read, it sounds like this is what I ought to do:
- Back up anything I need to. Just to confirm, updating firmware and flashing a new rom wipes out everything in the phone's internal memory, but not external SDcard? Or both?
Updating to the 4.3 firmware wipes your internal memory, not your sd card (although, that may be a very unfortunate circumstance, so it should be backed up as well). The other firmware updates do not affect your memory.
Are apps considered "on the cloud" and I can reinstall by just redownloading, without paying again?
Technically, yes they are "on the cloud." The fact that you paid is saved somewhere within your main Google account that you downloaded the app with. It is possible to pay for apps with your secondary gmail account, which can be switched within the Play Store app.
Except sideloaded apps? Or will I need to find all those APK files and save them somewhere else?
Use Titanium Backup if you can't find the apks. I do save my apks that I download, and I also upload them to Google Drive, since I have multiple Android devices, and I also have a faulty micro sd card that I am yet to replace. I can lose my data at any given moment, but everything is backed up, so I'm not worried.
Is it safe to say they're all in \data\app and \system\app? Or would system\app be unwanted since it's what came with the old phone OS?
Everything within the /system folder is wiped when you flash new roms. That data is NOT backed up while flashing between roms. Also, since it is from an older Android version, it's best to leave them alone. You may back up the data if you like, but I would refrain from restoring the apks along with the data.
The /data directory may be wiped, depending on the dev who built the rom zip. If they added the superwipe script, then /data will be wiped as well. Most devs do not include this, since many people "dirty flash," which is flashing new roms or updates of the current rom without wiping /data first.
- Get my phone into S-OFF status.
You will save yourself a LOT of headaches in the future. It was my S-Off status that allowed me to reflash my firmware when I lost the function of my data/voice antennas while carelessly flashing a port of a phone on a different carrier. Also, if you feel curious to try AOSP roms, then you do not need to do any extra steps to flash them.
- Update firmware (this is a separate process from updating the rom? Where do I get this firmware? Google google google?)
Yes, the firmware handles manages how the hardware of the phone operates. Updating the rom changes how the software looks and behaves. The kernel is sort of a bridge between the firmware and the software, since it manages the firmware (like battery life, processor speed, antennas, etc.), but the kernel is dependent on the software version. The firmware is not dependent on the software version, just as the software version is not dependent on the firmware version.
The only exception of the firmware/software independence is the 4.3 update, which requires a complete update of the firmware, and the older software cannot run on the new firmware without being modded by a dev.
- Install a new ROM (stock or otherwise) which will have these updates built in, so I won't need to regain root.
- Not sure what my bootloader is, maybe TWRP, does it matter? Do the above steps affect it? Should I change it to stock anyway?
Your bootloader is the white screen that shows the TAMPERED status on the top, and little Androids on skateboards on the bottom. With the exception of the firmware information in the top left corner, this screen does not change...ever.
TWRP is your recovery image, which is accessible through the RECOVERY option in your bootloader, or you can boot directly into it through different apps in Android - Titanium Backup is one of them (yes, that's one of the options, even for the free version).
The only reason to return your recovery to stock is to accept OTAs, and also to bring your phone back to the complete factory settings, just as the day when it was first purchased (for the sake of selling the phone, or returning back to Sprint for service}. Otherwise, don't bother with it. You may want to update your version of TWRP, though. If you update to 4.3, you will have to update it. I'm not going to take the time to get into that right now. I've given you enough homework.
- You suggested trying Sense 4 rather than Sense 5 first... any special reason?
I am a very patient person. To me, exploring Android takes time. I enjoy reading before I test, and testing before I settle (which I'm yet to "settle"). All of that being said, I suggested Sense 4 before Sense 5 because I wanted you to experience the both of them. They are truly two different versions of Sense, which one might not realize, as their version numbers are differentiated by one integer (in other words, 4 to 5). Sense 3 was a small step above Sense 2, and Sense 4 was a bigger step from Sense 3. Sense 5 is a complete overhaul of the Sense UI, save the flip clock.
I just feel that skipping from 4.0 to 4.3 is missing out on a great experience, but that is mainly if you actually want to try out different roms. Until the Sense 5 RUU, I still visiting ICS on occassion, but I usually didn't last more than 3 hours before I jumped back to JB.
Click to expand...
Click to collapse
Whew...you're making me work. But I like it. Anymore questions? Feel free to ask.
OK I've been working on this all afternoon and I'm at an impasse.
You've been a huge help so far and I hope you can guide me through this part.
I want to S-OFF and am following a tutorial: http://www.thefortressofnerditude.com/s-off-your-sprint-htc-evo-4g-lte/
Step 3 says root and install recovery. So I decide I need TWRP.
Already have nandroid and titanium backups both completed.
And I copied the whole SDcard to my computer after.
Annoyingly, TWRP's install page suggests that I need to be in S-OFF.
TWRP says I need S-OFF. S-OFF guide seems to suggest I need TWRP working.
I installed "TWRP Manager". Realize that might not be the same thing as TWRP.
Googled and found it on the TeamWin page.
The page asks first to input my device. I choose Evo 4G LTE (Jewel).
That brings me to this page: http://teamw.in/project/twrp2/98
They suggest I do the android app install method. I follow the first link (Market Link)
and install GooManager, and follow their steps.
Install the app and open it. Tap menu then hit Install OpenRecoveryScript. Tap Yes. Verify that the filename displays your device's code name and hit Yes. The file will download and your device will reboot and install the recovery automatically.
This all goes smoothly, but here's my issue.
It doesn't reboot automatically, or install anything automatically.
I see in the comments a recommendation to reboot into recovery mode.
I choose that in GooManager's menu, and after rebooting I get my bootloader screen with 4 menu options:
Bootloader
Reboot
Reboot Bootloader
Power Down
The only one that sounds sensible to me is bootloader so I pick that.
Now I get some new options:
Fastboot
Recovery
Factory Reset
Clear Storage
Simlock
Image CRC
Show Barcode
So, the only one that makes sense is Recovery. I choose it. The phone reboots.
Now I'm back at the first menu. So I'm in a loop.
Nothing I do in this loop seems to install anything.
So I just rebooted the phone normally and I'm back to my OS.
Where to go from here?
CreeDo said:
OK I've been working on this all afternoon and I'm at an impasse.
You've been a huge help so far and I hope you can guide me through this part.
I want to S-OFF and am following a tutorial: http://www.thefortressofnerditude.com/s-off-your-sprint-htc-evo-4g-lte/
Step 3 says root and install recovery. So I decide I need TWRP.
Already have nandroid and titanium backups both completed.
And I copied the whole SDcard to my computer after.
Annoyingly, TWRP's install page suggests that I need to be in S-OFF.
TWRP says I need S-OFF. S-OFF guide seems to suggest I need TWRP working.
I installed "TWRP Manager". Realize that might not be the same thing as TWRP.
Googled and found it on the TeamWin page.
The page asks first to input my device. I choose Evo 4G LTE (Jewel).
That brings me to this page: http://teamw.in/project/twrp2/98
They suggest I do the android app install method. I follow the first link (Market Link)
and install GooManager, and follow their steps.
Install the app and open it. Tap menu then hit Install OpenRecoveryScript. Tap Yes. Verify that the filename displays your device's code name and hit Yes. The file will download and your device will reboot and install the recovery automatically.
This all goes smoothly, but here's my issue.
It doesn't reboot automatically, or install anything automatically.
I see in the comments a recommendation to reboot into recovery mode.
I choose that in GooManager's menu, and after rebooting I get my bootloader screen with 4 menu options:
Bootloader
Reboot
Reboot Bootloader
Power Down
The only one that sounds sensible to me is bootloader so I pick that.
Now I get some new options:
Fastboot
Recovery
Factory Reset
Clear Storage
Simlock
Image CRC
Show Barcode
So, the only one that makes sense is Recovery. I choose it. The phone reboots.
Now I'm back at the first menu. So I'm in a loop.
Nothing I do in this loop seems to install anything.
So I just rebooted the phone normally and I'm back to my OS.
Where to go from here?
Click to expand...
Click to collapse
Did you unlock your boot loader first? You don't need to be S-off to install a custom recovery. Unlock your bootloader at htcdev.com then install twrp.
Read here for more info:
http://forum.xda-developers.com/showthread.php?t=2420916
Also, I suggest learning how to use fastboot commands. Install twrp using fastboot.
Sent from my EVO using XDA Premium 4 mobile app
OK, so I'm semi-bricked but not panicking yet.
Here's where I'm at.
• Unlocked boot loader successfully
• Installed TWRP using fastboot.
• Followed instructions as closely as I could on moonshine.io to get S-OFF working.
Several times during the process I got "installing device driver software" in my win7 system tray.
Not sure if that's normal. But the drivers seemed to install fine. At first.
But then, during this part of the process:
Moonshining .................(1)
Windows prompted me that it was installing some drivers again, But it failed to install the MTP driver.
After ten tries with the "Moonshining" step, I got "ERROR: don't drink and moonshine!" or something like that.
So, it seems like I need to get this MTP driver going. First I tried solutions on the computer:
• Uninstalled all HTC software, unplugged phone, rebooted,
installed HTC Sync Manager (setup name setup_3.0.52.0_htc.exe), then uninstalled it...
because a tutorial said this would keep the drivers but remove the software. Still no luck on the MTP driver though.
• Found "Mass Storage Device" (my phone) under device manager, removed it, unplugged, rebooted, replugged.
• Plugged cord into back of PC, so I'm using USB 2.0 rather than USB 3.0.
• One suggestion said a certain registry section might have an upperfilter key that shouldn't be there.
But I don't have that upperfilter key so that's not the issue.
Some fixes require getting into my phone (one guy suggests turning off USB debugging)...
but I no longer have a working OS. I can get into my bootloader, I tried Factory Reset.
But after choosing this I go into TWRP and I have no TWRP backups that I can restore.
So my next guess is, I need to get a recovery ZIP (is that basically a ROM?) that TWRP can install.
If that's correct, what ZIP should I get? I was on Android 4.0.3 Sense 4.0, can I download jellybean with Sense 5.0,
and install it via TWRP?
That was my goal all along, but I'm determined to get S-OFF working, so if doing that means my phone gets wiped again,
I guess I just want whatever ROM/recovery/whatever that allows me to change this USB debugging setting,
and try other phone-related fixes to the MTP driver issue.
First of all, flash an ICS rom. I'm assuming that you are still using the same ICS firmware, and you will want to have your phone operational (to enable USB debugging). The link for MeanRom ICS still works. http://old.androidfilehost.com/main/EVO_3D_Developers/mikeyxda/LTEvo/MeanROM-ICS-v65-jewel-ltevo.zip
Ok....since you are on the old HBoot, I think that you need to use the older S-Off methods (LazyPanda or DirtyRacun), if I'm not mistaken. You can not download and flash Sense 5.0 through TWRP as of yet, because you need to be using the new firmware to do so. You may want to pay http://unlimited.io/jewel.htm a visit. Also, to use LazyPanda or DirtyRacun, you need to be using Ubuntu. Another option that you have is to use the regular RUU and update directly to Sense 5.0. You will be stock, unrooted, but you can easily use the latest S-Off method.
Lastly, for your rooting/S-Off needs, you can also use a handy-dandy toolkit from @WindyCityRockr that can handle everything that you need to do. I usually encourage manual labor, but there are some exceptions. http://forum.xda-developers.com/showthread.php?t=2436217
Thanks again for jumping in.
I'm getting somewhere, but still so many difficulties.
Fix one thing, break two more.
I finally have a new working rom, but almost against my will it ended up
being CyanogenMod.
The short version:
- unlocked bootloader, got TWRP going, finally got ADB working (don't think it's the right driver,
but whatever, ADB commands work fine), wiped everything... factory reset, Dalvik, external storage.
- Didn't wipe Internal storage, I wiped only /data/ per some post's recommendation.
- I used ADB PUSH to get a few possible roms onto /sdcard/
PJ75IMG_1.13.651.1.zip (failed with "unable to open zip")
(ROM)_Stock_Rooted_OTA_(3.16.651.3)V2.zip (failed with "unable to execute updater binary in zip")
cm-10.2.0-jewel.zip (cyanogenmod) - success!
So, the phone works. It appears to be at least based on android 4.3... and I'm guessing CM, which updates
frequently, has all those OTA updates bundled into it. Any downsides to CyanogenMod?
I could just proceed from here to reinstall my old apps etc.
I'm still not "S-OFF" which annoys me, but I read a post suggesting it's not really that necessary.
The way they put it is, s-off allows you to access partitions so they can be modded,
but nobody is developing anything interesting for those partitions. Like nobody's doing custom radios and such.
Should I still pursue S-OFF anyway?
If so, is there a way to do it with CyanogenMod?
That awesome app (Windroid Universal Toolkit) doesn't recognize the phone.
Last question, how should I go about restoring everything?
I had titanium and nandroid backups copied to my computer.
Can it restore to such a wildly different version of the OS?
Can I get back not just apps, but stuff like my keyboard preferences, texting history, etc.?
Should I still pursue S-OFF anyway?
Click to expand...
Click to collapse
Yes! Being S-On is a complete pain in the BUTT when switching AOSP roms. Have you tried to flash the rom that I posted, MeanRom ICS? I'm really trying to get you to stay on Sense, because S-Off and other different tools work so much better while using Sense. AOSP is better after S-Off. But that's up to you.
If so, is there a way to do it with CyanogenMod?
Click to expand...
Click to collapse
I am not sure. You can try if you have the time. I suggest making a nandroid of your CM rom, and try to flash a Sense ICS rom, not JB...yet.
That awesome app (Windroid Universal Toolkit) doesn't recognize the phone.
Click to expand...
Click to collapse
CM might be the issue here, as well as it might not.
Last question, how should I go about restoring everything?
I had titanium and nandroid backups copied to my computer.
Can it restore to such a wildly different version of the OS?
Click to expand...
Click to collapse
Yes, TB will still work. There are some apps that might cause the restoration process to freeze, so I suggest killing TB and skipping over the app that froze the process when you return.
Can I get back not just apps, but stuff like my keyboard preferences, texting history, etc.?
Click to expand...
Click to collapse
If your keyboard preferences was not backed up, then no. If you were using the stock Sense keyboard, then that is a no as well. As long as your texting history was backed up, it can be restored. Texts are not like apps...their data is typically stored in XML files which are readable through any version of Android (2.3+).
I'm still soliciting my help if you need it.
I'm for sure going to need it, so thanks very much for the ongoing support!
I got discouraged after all the failures but I'll download Meanrom now.
The thing is... now that Cyanogen mod works, I hesitate to wipe it and try a new one.
Especially since several other roms I tried mysteriously failed to install.
I like that it's jellybean and don't wanna move backwards to ICS.
And I like their goal of cutting out the fluff.
I still want S-OFF, will I end up having to wipe everything again to get it?
Also, I really don't feel confident I have the right drivers for my windows machine.
I can transfer files in USB mode, go into USB debugging, and do the usual ADB commands.
But the phone shows up as a nexus in device manager, but it's definitely evo 4G lte.
I tried installing an executable RUU and it failed after a bit saying it can't detect the device.
And there's that issue where Windroid doesn't detect it.
So I have the feeling that without the right USB drivers, tools like Moonshine will still fail.
I specifically got errors every time when anything tried to install MTP usb drivers. Do I really need them?
You think LazyPanda or DirtyRacun's tools will work even if I never get the MTP thing installed?
CreeDo said:
I'm for sure going to need it, so thanks very much for the ongoing support!
I got discouraged after all the failures but I'll download Meanrom now.
The thing is... now that Cyanogen mod works, I hesitate to wipe it and try a new one.
Especially since several other roms I tried mysteriously failed to install.
I like that it's jellybean and don't wanna move backwards to ICS.
And I like their goal of cutting out the fluff.
I still want S-OFF, will I end up having to wipe everything again to get it?
Also, I really don't feel confident I have the right drivers for my windows machine.
I can transfer files in USB mode, go into USB debugging, and do the usual ADB commands.
But the phone shows up as a nexus in device manager, but it's definitely evo 4G lte.
I tried installing an executable RUU and it failed after a bit saying it can't detect the device.
And there's that issue where Windroid doesn't detect it.
So I have the feeling that without the right USB drivers, tools like Moonshine will still fail.
I specifically got errors every time when anything tried to install MTP usb drivers. Do I really need them?
You think LazyPanda or DirtyRacun's tools will work even if I never get the MTP thing installed?
Click to expand...
Click to collapse
Feel free to try the facepalm S-off method as well. Works on devices with older software and is super easy. Look here:
http://forum.xda-developers.com/showthread.php?t=2163013
Sent from my Nexus 5 using XDA Premium 4 mobile app
Evolution_Freak said:
Feel free to try the facepalm S-off method as well. Works on devices with older software and is super easy. Look here:
http://forum.xda-developers.com/showthread.php?t=2163013
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Cheers, it does look pretty straightforward.
Of course that's what I thought hours ago when I tried moonshine haha.
I'll give it a go.
To be clear, does this method wipe anything?
They don't actually say.
CreeDo said:
Cheers, it does look pretty straightforward.
Of course that's what I thought hours ago when I tried moonshine haha.
I'll give it a go.
To be clear, does this method wipe anything?
They don't actually say.
Click to expand...
Click to collapse
Can't remember if it wipes or not. Best thing to do is make a backup with TWRP and keep the backup on your external SD card. If it wipes you can always restore your backup.
Sent from my HTC device
Thanks for the help so far guys. I am currently really enjoying Cyanogenmod. I suspect it's eating battery more,
but then against I am on the phone for hours redoing everything that got changed/removed.
Does anyone know if there's a simple way (or even a difficult way) to restore my texts?
Because the app is totally different, and the old text app was the one that came
with the stock rom, I cannot restore it in titanium. But if I could extract even the raw text that'd be helpful.
Get back to Sense, or get someone with Sense to restore it for you, and save it using a different app. Or maybe try using SMS Backup & Restore from the Play Store. I'm not sure if it can read the backups saved through Sense, but it's worth a try. You just have to navigate to the location of the old backup.
It looks like I can import an XML in this messaging app so maybe if sense offers an export to XML option, I'll be set.
Sense is sort of an OS on top of the OS, right?
Can sense be loaded without flashing a new rom? or is it too integrated with the OS?
I successfully rooted my phone and installed android revolution hd, which i ditched due to slow startup speed. I don't want to mess with s off and all that. So, after I installed the stock rom from his website, i was surprised to see that I still have an over 2 minute boot time. How can I fix this easily? I'd rather not have to redownload everything for the 4th time today...
My device is S on, unlocked bootloader. I restored the default recovery. Honestly, I'd like to just go back to stock without losing everything. Root would be nice but if it's difficult I'd rather not.
What hboot and what radio baseband? What carrier/region version of the M8?
You can return to stock to accept the OTA, to avoid having to S-off just to update the firmware.
redpoint73 said:
What hboot and what radio baseband? What carrier/region version of the M8?
You can return to stock to accept the OTA, to avoid having to S-off just to update the firmware.
Click to expand...
Click to collapse
I honestly don't know anything except ATT US. I think I may have accidentally restored with the international firmware.
What do you mean accept the OTA? What does that even mean? sorry, I'm really green at this stuff.
siren_shadows said:
I honestly don't know anything except ATT US. I think I may have accidentally restored with the international firmware.
What do you mean accept the OTA? What does that even mean? sorry, I'm really green at this stuff.
Click to expand...
Click to collapse
You're S-on, so if all you did is flash a international ROM or restored a international stock nandroid, its not a big deal. That doesn't touch any of the important stuff like radio baseband (s-off is required to do that) and is easily reversible. But try to keep careful track of any mods you do to the phone moving forward. Its hard to help you, if you don't even remember what you did to the phone.
OTA = official "over the air" updates. OS software updates that come from HTC or your carrier direct to the phone automatically.
Forgot that you posted in the AT&T section (I spend time in both this and the "international" or generic M8 forums, so I just lost track of which one you posted in). Being the AT&T version, returning to stock is very easy. Just relock the bootloader, connect the phone to a PC, and run the RUU executable:
http://forum.xda-developers.com/att-htc-one-m8/general/htc-one-m8-ruu-m8ul-4-4-3-t2860423
This will get you on the latest firmware, and the latest stock ROM, recovery, radio, etc. From there, you can either just leave it be, or unlock the bootloader, install custom recovery and root, if you want to.
redpoint73 said:
You're S-on, so if all you did is flash a international ROM or restored a international stock nandroid, its not a big deal. That doesn't touch any of the important stuff like radio baseband (s-off is required to do that) and is easily reversible. But try to keep careful track of any mods you do to the phone moving forward. Its hard to help you, if you don't even remember what you did to the phone.
OTA = official "over the air" updates. OS software updates that come from HTC or your carrier direct to the phone automatically.
Forgot that you posted in the AT&T section (I spend time in both this and the "international" or generic M8 forums, so I just lost track of which one you posted in). Being the AT&T version, returning to stock is very easy. Just relock the bootloader, connect the phone to a PC, and run the RUU executable:
http://forum.xda-developers.com/att-htc-one-m8/general/htc-one-m8-ruu-m8ul-4-4-3-t2860423
This will get you on the latest firmware, and the latest stock ROM, recovery, radio, etc. From there, you can either just leave it be, or unlock the bootloader, install custom recovery and root, if you want to.
Click to expand...
Click to collapse
Wow! Thanks so much! Do I need to backup everything first? Also, what method of backing up would you suggest?
siren_shadows said:
Do I need to backup everything first? Also, what method of backing up would you suggest?
Click to expand...
Click to collapse
Yes, backup all user data. RUU will wipe the phone.
I usually just copy and paste things like photos to my PC, or you can backup to the cloud by Picasa, Dropbox, or other means. Contacts are backed up to GMail by default (unless you changed it).
If you want to backup other things (like app data, SMS) you can checkout Helium. I haven't personally used it, but I've seen it recommended by others. There are other backup options that require root, but it sounds like you are on the fence about root.
https://play.google.com/store/apps/details?id=com.koushikdutta.backup
siren_shadows said:
Wow! Thanks so much!
Click to expand...
Click to collapse
There's a button for that.
redpoint73 said:
Yes, backup all user data. RUU will wipe the phone.
I usually just copy and paste things like photos to my PC, or you can backup to the cloud by Picasa, Dropbox, or other means. Contacts are backed up to GMail by default (unless you changed it).
If you want to backup other things (like app data, SMS) you can checkout Helium. I haven't personally used it, but I've seen it recommended by others. There are other backup options that require root, but it sounds like you are on the fence about root.
Click to expand...
Click to collapse
awesome. I really appreciate it. Is there a reason the custom roms take so long to boot up? Was I doing something wrong?
siren_shadows said:
awesome. I really appreciate it. Is there a reason the custom roms take so long to boot up? Was I doing something wrong?
Click to expand...
Click to collapse
Any Sense 2.x based ROM combined with outdated 1.x firmware (hboot, radio, etc.) on the phone will result in known issues like long boot times, broken WiFi, Bluetooth, etc.
Updating with the 2.23 RUU, or alternately updating by OTA (more complicated) will update the firmware and resolve this issue.
Followed instructions to the T I'm pretty sure, and since then all incoming calls go straight to voicemail.. Now I want to revert back to stock, do the sunshine s off and then try revolution hd again to see if the problem goes away.
homthtrnut said:
Followed instructions to the T I'm pretty sure, and since then all incoming calls go straight to voicemail.. Now I want to revert back to stock, do the sunshine s off and then try revolution hd again to see if the problem goes away.
Click to expand...
Click to collapse
This issue has been reported by a couple folks now (also on Euro based LP ROMs); although I don't think the exact cause and fix has been determined definitely yet. http://forum.xda-developers.com/att-htc-one-m8/help/m8-skydragon-incoming-calls-t3042091
First off, if you have the AT&T version of the M8 and are s-on, you aren't on the right firmware (hboot, radio, and several other critical modules that don't flash with the ROM) for the an recent (Lollipop) version of ARHD. For now, s-off is needed to update to LP firmware; until AT&T releases LP officially by OTA, RUU.
Although I'm not sure its just a firmware issue (so that may or may not fix the issue). "International" ROMs often don't play well with AT&T's network; since the devs (often Euro) don't understand the nuances of AT&T's network. Not to knock those fine devs, but they can't know what they don't know (or can't test, since they aren't on that particular network). Plus, AT&T is probably mostly to blame, as they seem to do some things differently from just about every other carrier in the world.
The quick fix would be return to a stock AT&T ROM, as you have already figured out. You don't need s-off to do that. Restore your nandroid (that you should always make before messing with flashing new ROMs). Or find a stock AT&T ROM corresponding to your firmware, and flash in recovery. Another option is to relock the bootloader and RUU to stock.
Just need to dig in and get it done!
redpoint73 said:
This issue has been reported by a couple folks now (also on Euro based LP ROMs); although I don't think the exact cause and fix has been determined definitely yet. http://forum.xda-developers.com/att-htc-one-m8/help/m8-skydragon-incoming-calls-t3042091
First off, if you have the AT&T version of the M8 and are s-on, you aren't on the right firmware (hboot, radio, and several other critical modules that don't flash with the ROM) for the an recent (Lollipop) version of ARHD. For now, s-off is needed to update to LP firmware; until AT&T releases LP officially by OTA, RUU.
Although I'm not sure its just a firmware issue (so that may or may not fix the issue). "International" ROMs often don't play well with AT&T's network; since the devs (often Euro) don't understand the nuances of AT&T's network. Not to knock those fine devs, but they can't know what they don't know (or can't test, since they aren't on that particular network). Plus, AT&T is probably mostly to blame, as they seem to do some things differently from just about every other carrier in the world.
The quick fix would be return to a stock AT&T ROM, as you have already figured out. You don't need s-off to do that. Restore your nandroid (that you should always make before messing with flashing new ROMs). Or find a stock AT&T ROM corresponding to your firmware, and flash in recovery. Another option is to relock the bootloader and RUU to stock.
Click to expand...
Click to collapse
I can do anything that is new to me with good instructions. I WAS able to unlock, root, and flash a ROM with good success following the steps. What I would like to do now is put it back the way it was, then s off using sunshine, and then go ahead and flash the Revo HD ROM again and whatever else I need to do, maybe the firmware too idk. Before I started anything , I backed it up using HTC SYNC on my laptop. Is that useful in returning it to stock? Or is that just for media and texts and such? Maybe what I should do is check the forum where the Revo users are and see what they say. Sorry if it sounds like Im thinking out loud but Im a noob at forums and flashing. And Im getting burnt out on having a phone that doesnt receive calls properly. Not to mention burnt out from working all day and coming home to try and solve this mystery. OK I wont mention it. Thanks to those who have attempted to give me input here to try to figure this thing out.
Just a lil something to think about...,youll not have dialer, vvm messages,contacts integrated,signal will probably be not as good,and no VoLTE when using euro ROM's. Stand alone vvm app may or may not install from playstore if you use it. My suggestion,flash back to stock,wait alil while and get an official Lollipop release from ATT.
Flash a twrp backup of latest 4.4.4
Flash stock recovery from latest 4.4.4
Steps above will put you back to as close to stock as possible,without relocking bootloader and reflashing the exe ruu file.
homthtrnut said:
What I would like to do now is put it back the way it was, then s off using sunshine, and then go ahead and flash the Revo HD ROM again and whatever else I need to do, maybe the firmware too idk.
Click to expand...
Click to collapse
If you don't flash the firmware, I don't think the above will help you in any way. You'll just be back to where you are now, just with s-off. Which is just a permission/security change; and won't change the functionality of the phone or address the issue with calls.
Either you need to change firmware, or ROM, or both, in order to fix the problem.
Flashed firmware successfully.........darn .zip.zip tricksters!!!! Anyway!
redpoint73 said:
If you don't flash the firmware, I don't think the above will help you in any way. You'll just be back to where you are now, just with s-off. Which is just a permission/security change; and won't change the functionality of the phone or address the issue with calls.
Either you need to change firmware, or ROM, or both, in order to fix the problem.
Click to expand...
Click to collapse
After several attempts getting cannot load error I figured out I needed to back off the .zip from the renamed folder (its already a damn .zip)! duh....so finally got that done. Wondering what to do about relock now. Guess I will have to google it like everything else. Usually throws me right back in here when I do. I found a guy with the exact same problem I was having and it was just cuz he renamed it firmware.zip. Even the dude on youtube tells you to do it! Us noobs are this close to pulling our eyes out from that one!!!! But after trying this and trying that we finally flashted our firmwares on our little precious. Now to see if I can receive calls again. Whats the procedure for unlocking a relocked phone now? Can it now be done by a cmd prompt? Thanks people!
homthtrnut said:
After several attempts getting cannot load error I figured out I needed to back off the .zip from the renamed folder (its already a damn .zip)! duh....so finally got that done.
I found a guy with the exact same problem I was having and it was just cuz he renamed it firmware.zip. Even the dude on youtube tells you to do it! Us noobs are this close to pulling our eyes out from that one!!!! But after trying this and trying that we finally flashted our firmwares on our little precious.
Click to expand...
Click to collapse
Do yourself a huge favor, and turn off the Windows option (if you haven't already) to hide known file extensions. The option is usually enabled by default. I suspect its mainly meant to prevent non-tech savvy PC users from deleting or modifying file extensions and rendering files unusable (or at least not associated with a program to open it).
For most folks who are going to be messing with things like modding phones, and even halfway familiar with the file extensions, the option to hide them is counter-productive and confusing.
The recommendation to rename the file to firmware.zip is valid. This is done since the files are often named things like 4.16.401 to differentiate the firmwares from each other (such as in firmware collections). Technically, you didn't rename the file to firmware.zip (although Windows make it look like you did), you actually named it firmware.zip.zip, even though Windows didn't display it that way.
homthtrnut said:
Wondering what to do about relock now. Guess I will have to google it like everything else. Usually throws me right back in here when I do.
Whats the procedure for unlocking a relocked phone now? Can it now be done by a cmd prompt? Thanks people!
Click to expand...
Click to collapse
To unlock the bootloader again, simply go through the HTCDev.com process to get another unlock bin token, then run the fastboot command with that token again (like you did the first time).
On past devices, it was sometimes possible to reuse the original token (run the fastboot command with it). But an XDA user commented that doesn't work on this device (and that you need to get a new token). But you can always try it, if you want.
Flashed firmware and now stuck in HBOOT! I REALLY NEED HELP NOW
redpoint73 said:
This issue has been reported by a couple folks now (also on Euro based LP ROMs); although I don't think the exact cause and fix has been determined definitely yet. http://forum.xda-developers.com/att-htc-one-m8/help/m8-skydragon-incoming-calls-t3042091
First off, if you have the AT&T version of the M8 and are s-on, you aren't on the right firmware (hboot, radio, and several other critical modules that don't flash with the ROM) for the an recent (Lollipop) version of ARHD. For now, s-off is needed to update to LP firmware; until AT&T releases LP officially by OTA, RUU.
Although I'm not sure its just a firmware issue (so that may or may not fix the issue). "International" ROMs often don't play well with AT&T's network; since the devs (often Euro) don't understand the nuances of AT&T's network. Not to knock those fine devs, but they can't know what they don't know (or can't test, since they aren't on that particular network). Plus, AT&T is probably mostly to blame, as they seem to do some things differently from just about every other carrier in the world.
The quick fix would be return to a stock AT&T ROM, as you have already figured out. You don't need s-off to do that. Restore your nandroid (that you should always make before messing with flashing new ROMs). Or find a stock AT&T ROM corresponding to your firmware, and flash in recovery. Another option is to relock the bootloader and RUU to stock.
Click to expand...
Click to collapse
I picked a version that was made for the cid 001 according to android file host https://www.androidfilehost.com/?w=files&flid=24258 and after numerous attempts to flash I finally got it to go by getting rid of the renamed .zip at the end. ( It was already a zip file) I think a lot of people have had that problem. Anyway I have now a sort of bricked phone that wont leave HBOOT. My son bought an M8 that should be getting here in a day or so and I was wondering if I made a nandroid of that one, maybe it could pull me out of the hole. I still have fastbboot usb so maybe theres a procedure that will get me going again. Can anyone point me? I'll buy you a beer! or 12
homthtrnut said:
I picked a version that was made for the cid 001 according to android file host https://www.androidfilehost.com/?w=files&flid=24258
Click to expand...
Click to collapse
401 firmware is Euro based firmware. AT&T is 501.
homthtrnut said:
Anyway I have now a sort of bricked phone that wont leave HBOOT. My son bought an M8 that should be getting here in a day or so and I was wondering if I made a nandroid of that one, maybe it could pull me out of the hole. I still have fastbboot usb so maybe theres a procedure that will get me going again.
Click to expand...
Click to collapse
Probably making it more complicated than need be. Also, depending on what firmware you now have on the phone, and whether it corresponds to the "new" nandroid, you might not be in any better place than you are now.
I can think of at least 2 (rather simple) ways to get the phone up and running:
1) Flash a stock or custom ROM that corresponds to your firmware. You can adb push the ROM to your phone; or alternately move it to a removable SD using a card reader connected to your computer.
What hboot and radio numbers are currently on the device?
2) Relock the bootloader and RUU back to stock.
hboot and radio numbers currently on m8
redpoint73 said:
401 firmware is Euro based firmware. AT&T is 501.
Probably making it more complicated than need be. Also, depending on what firmware you now have on the phone, and whether it corresponds to the "new" nandroid, you might not be in any better place than you are now.
I can think of at least 2 (rather simple) ways to get the phone up and running:
1) Flash a stock or custom ROM that corresponds to your firmware. You can adb push the ROM to your phone; or alternately move it to a removable SD using a card reader connected to your computer.
What hboot and radio numbers are currently on the device?
2) Relock the bootloader and RUU back to stock.
Click to expand...
Click to collapse
HBOOT-3.19.0.0000 [email protected] OS-3.42.502.1 eMMC-boot 2048MB
homthtrnut said:
HBOOT-3.19.0.0000 [email protected] OS-3.42.502.1 eMMC-boot 2048MB
Click to expand...
Click to collapse
Dude, all you have to do is relock the bootloader using the fastboot command "fastboot oem lock" and download the HTC One M8 file from here http://www.htc.com/us/support/rom-downloads.html . With the phone plugged in to the computer, run the RUU file. It will bring the phone back to the most recent 4.4.4 OTA. Takes ten minutes. You're making this wayyyyyyy harder on yourself than it should be.
homthtrnut said:
HBOOT-3.19.0.0000 [email protected] OS-3.42.502.1 eMMC-boot 2048MB
Click to expand...
Click to collapse
That is the Android 4.4.4 radio. Meaning the 401 firmware you linked and tried to flash didn't take. And it won't with s-on, unless its signed and hacked to accept AT&T's CID (which I don't think there is any 401 firmware that meets those requirements).
Agree with the above response, in that the easiest way to get the phone up and running again is relock the bootloader and RUU to stock.
Since your device is hboot 3.19, you are stuck with s-on and that means you are stuck on KitKat firmware until AT&T releases Lollipop officially.
That also means you can only run ROMs that support 4.4.4 firmware (no LP based Sense ROMs), otherwise you will run into various serious bugs like the call issue on ARHD (or broken WiFi). There are some LP GPE and AOSP ROMs that support the 4.4.4 firmware, if you want to go that route.
Was just starting out, not enough experience.
bford152 said:
Dude, all you have to do is relock the bootloader using the fastboot command "fastboot oem lock" and download the HTC One M8 file from here http://www.htc.com/us/support/rom-downloads.html . With the phone plugged in to the computer, run the RUU file. It will bring the phone back to the most recent 4.4.4 OTA. Takes ten minutes. You're making this wayyyyyyy harder on yourself than it should be.
Click to expand...
Click to collapse
The above phone was eventually returned. Now I have an unlocked, s off M8. With help from PearlyMon I was able to do it all about a month ago. Now I'm just waiting to work up the nerve to flash a customer Rom and also add in the H/K sound feature. Really liked the HD Revolution Rom, I just didn't have the wherewithall to find and install the proper firmware. This time around will be better. On third M8 now. First one, brand new slipped out of workshirt pocket and faceplanted on a tile floor. First damn day! Didn't have the otter box defender case like I should've. 2nd and 3rd ones have been refurbs. So who knows how much use the battery saw before? So I'd like a nice Rom that has built in low battery drain. Every day it seems to drain off a little sooner. Went to black background today to help it out a little. Anyway, haven't been on this forum much since the above problem and thought I'd touch base with you and say thanks. Have a nice one.
I have the same problem as the OP with ATT using any custom ROM since i got the OTA lollipop update in early April. Firmware is 4.28.xx and it appears that no one has been able to work around it without flashing back to 4.16.xx
Anyone come across a ROM that will receive calls on ATT with s-on and 4.28?
jon145 said:
I have the same problem as the OP with ATT using any custom ROM since i got the OTA lollipop update in early April. Firmware is 4.28.xx and it appears that no one has been able to work around it without flashing back to 4.16.xx
Anyone come across a ROM that will receive calls on ATT with s-on and 4.28?
Click to expand...
Click to collapse
Some folks have been having issues with "international" based custom ROMs on AT&T's LTE network. It seems that AT&T has been making some changes to LTE, possibly in preparation for Voice over LTE (VoLTE, which AT&T calls "HD Voice"), that are messing up voice calls on "international" ROMs.
Some folks have this trouble, while others don't. I can only assume its location dependent; and the mentioned "changes" have only been implemented in some areas. I've been running SkyDragon Sense 7 fine on AT&T in my home area of Massachusetts, as well as travelling to a couple other areas (Chicago and Green Bay) with none of the LTE issues.
You might try WNC's ROM here: http://forum.xda-developers.com/att-htc-one-m8/development/att-4-4-3-2-22-1540-3-debloated-sense-6-t2837365
Its based on the Lollipop Developer's Edition ROM, which is intended for use on AT&T's network. He's working on a version based on the AT&T 4.28 update, but its still in testing and not posted yet.
Yeah I've been running the SD 9.0 for several days and no love here in Dallas ... I could speculate for days since D is AT&T's home city.
Thanks for the info, I will definitely keep an eye out for WNC's next release. Does he usually do beta releases?
jon145 said:
Thanks for the info, I will definitely keep an eye out for WNC's next release. Does he usually do beta releases?
Click to expand...
Click to collapse
He has a beta in testing right now. Just ping him, and he will probably send you a link to the test build. Probably the only reason he would say "no" is if he is going to release soon anyway.
redpoint73 said:
Some folks have this trouble, while others don't. I can only assume its location dependent; and the mentioned "changes" have only been implemented in some areas. I've been running SkyDragon Sense 7 fine on AT&T in my home area of Massachusetts, as well as travelling to a couple other areas (Chicago and Green Bay) with none of the LTE issues.
Click to expand...
Click to collapse
Interestingly, I'm in Chicago and did have that problem with SkyDragon. Having reverted back to the stock ROM, everything works again. In my thread, I think you mentioned that you are using the "other GSM" option, rather than the AT&T specific option in AROMA. I wonder if it could be some of these AT&T specific "optimizations" or whatever that could be part of the problem.
rhughes93 said:
Interestingly, I'm in Chicago and did have that problem with SkyDragon. Having reverted back to the stock ROM, everything works again. In my thread, I think you mentioned that you are using the "other GSM" option, rather than the AT&T specific option in AROMA. I wonder if it could be some of these AT&T specific "optimizations" or whatever that could be part of the problem.
Click to expand...
Click to collapse
Interesting, indeed. Did you pick AT&T from the AROMA options? If not, try the "other GSM" option (or whatever its called).
I was just in the Chicago area a few weeks ago to visit family. Not the city proper, but the suburbs of Arlington Heights and Batavia. I was on SD 7.0 at the time (there was no AT&T option for that version, so I had picked the "other GSM"). Everything seemed to be working fine.
redpoint73 said:
Interesting, indeed. Did you pick AT&T from the AROMA options? If not, try the "other GSM" option (or whatever its called).
I was just in the Chicago area a few weeks ago to visit family. Not the city proper, but the suburbs of Arlington Heights and Batavia. I was on SD 7.0 at the time (there was no AT&T option for that version, so I had picked the "other GSM"). Everything seemed to be working fine.
Click to expand...
Click to collapse
So I re-flashed SkyDragon, and I think I was not understanding the difference between AROMA installer and the software itself. When I did it the first time, I think I did select T-mobile with wifi calling in AROMA, but AT&T within the software SIM setup. It did not work. Now after getting the stock ROM working, I re-flashed, chose the Other GSM/WWE/whatever option within AROMA, AT&T within the software, and all is right in the world. I may also try the same with Venom this weekend now that I have good restore options, though I don't recall if it had similar options in AROMA or not.
Hello everyone!
I've been very happy with my rooted M9 for the last few months but now a system update message on my screen and I'm trying to figure out what to do about. I seem to recall when I rooted my phone that there could be complications if I install a system update on a rooted phone (like making a Nandroid Backup) but I'm finding scarce information on the topic. Does anyone here have some advice about this?
Rom...
http://forum.xda-developers.com/showthread.php?t=3083799
Firmware...
http://forum.xda-developers.com/showthread.php?t=3073355
Follow the second link above.
You will need to restore the factory system.img using TWRP (exFAT or NTFS for external USB as file is > 4GB).
This puts the modified system (root) back to stock so the update will run successfully.
Flash the original recovery for you system version too.
Then you can accept the OTA and then root the phone again.
Thanks for the responses! I'm still uncertain about a few things so tell me if I have this right.
First I need to restore the factory image. Is that a guy named OJM is talking about on this thread? (http://forum.xda-developers.com/sprint-one-m9/general/rooting-guide-t3073004)
To restore your clean system backup to accept OTAs, you must use fastboot. If you are S-ON, you must be in download mode.
-copy your clean system.emmc.win to your adb/fastboot folder on your pc
-boot into download mode
-use cmd fastboot flash system system.emmc.win
Click to expand...
Click to collapse
In that case, what is a system.emmc.win?
Then I flash the original recovery...what are you refering to when you say "original recovery"?
After that my phone should be locked again and I can go to that second link, download the latest firmware and flash it. And then I can unlock and root my phone again.
Edit: So it looks like someone has made a guide on how to get the OTA updates (if you use the right words in your search). It looks no one done anything with it since May so maybe it still works? http://forum.xda-developers.com/one-m9/general/best-unlocking-bootloader-rooting-guide-t3087354
I would just run the official RUU, it's a one shot process will take care of everything including the radios. Much easier than messing around, just make sure you are S-OFF before you do it. When it's done just flash the latest TWRP and install your rom you will be done.
Sim-X said:
I would just run the official RUU, it's a one shot process will take care of everything including the radios. Much easier than messing around, just make sure you are S-OFF before you do it. When it's done just flash the latest TWRP and install your rom you will be done.
Click to expand...
Click to collapse
That was what I ended up doing. Had few bumps on the way but I managed to get everything working. Thanks for the help everyone!
RUU
Sim-X said:
I would just run the official RUU, it's a one shot process will take care of everything including the radios. Much easier than messing around, just make sure you are S-OFF before you do it. When it's done just flash the latest TWRP and install your rom you will be done.
Click to expand...
Click to collapse
hi sim I have a question the only thing I got to make sure is that the phone is S-OFF and nothing will happen because I read that also the bootlooder had to be lock again so I'm not sure