Related
I tried searching for a how-to on this but apparently I'm searching inclined.
From what I can gather is it as simple as just dumping the zip onto the root of your SD card and doing:
3. Make sure phone is off then hold Power button and Call Button.
4. The menu opens quickly press the power key over the hboot option.
5. Follow onscreen instructions to install the update. the phone will reboot a few times.
you dont even need to search. go to the development section and then look at the top few, it will have very detailed instructions.
I guess I should have elaborated more and said I don't have my phone rooted and really don't want to go that route. I was just getting confused because everything i was finding on here was people running root but I came across a few things where people said the 2.1OTA Leak was just a straight upgrade, so that is my confusion.
Are you asking how to install the 2.1ota leak? Just flash it onto your phone?
Curious, why do you not want to root your phone?
Root is much more flexible, and there are roms that are based off that leak. If you're worried about your warranty, it's going to void it either way, lol.
Good luck !
rheally said:
Are you asking how to install the 2.1ota leak? Just flash it onto your phone?
Curious, why do you not want to root your phone?
Root is much more flexible, and there are roms that are based off that leak. If you're worried about your warranty, it's going to void it either way, lol.
Good luck !
Click to expand...
Click to collapse
but if you have root you can do the downgrade back to 1.5
Android22 said:
but if you have root you can do the downgrade back to 1.5
Click to expand...
Click to collapse
Oh right, I forgot about that, duh It just seems like root would be a better choice.
But to each his own.
rheally said:
Are you asking how to install the 2.1ota leak? Just flash it onto your phone?
Curious, why do you not want to root your phone?
Root is much more flexible, and there are roms that are based off that leak. If you're worried about your warranty, it's going to void it either way, lol.
Good luck !
Click to expand...
Click to collapse
yeah that is my question, can 2.1OTA just be flashed or does your phone need to be rooted?
I just feel like with root I'll be more likely to kill the phone but I'm going to check into it more again.
If you flash the 2.1 OTA leak onto your phone you CANNOT root your phone. It hasn't been figured out yet.
Root really isn't that hard to do. There are several threads over in the development forum.
rheally said:
If you flash the 2.1 OTA leak onto your phone you CANNOT root your phone. It hasn't been figured out yet.
Root really isn't that hard to do. There are several threads over in the development forum.
Click to expand...
Click to collapse
yeah I was just reading the thread on going from stock 1.5 to rooted 2.1. Can you give me some of the major benefits of rooting? I'm trying to find really practical stuff, not just the "Well it's cool cause it's like being root in Linux".
And just to clarify you can just flash to 2.1OTA? I'm skeptical of doing that now because I was reading some people think 2.1OTA has a time sensitive date on it.
Future developments will likely be easier to impliment if you root. The ability to run different (and potentially more stable) ROMs. Support for future software not designed for the Eris. Post rooting you can also make Nandroid backups and as long as you don't somehow screw your bootloader you can actually fix your phone.
Also, and this is pure speculation, should Verison decide to discontinue support for the Eris entirely, non-rooters may have issue getting new Android versions since they're limited to signed code.
EDIT: there is also little reason NOT to root. It does everything that you can do unrooted and more. All this plus the fact that you may never be able to root again but could always unroot at your leisure.
Marisa said:
Future developments will likely be easier to impliment if you root. The ability to run different (and potentially more stable) ROMs. Support for future software not designed for the Eris. Post rooting you can also make Nandroid backups and as long as you don't somehow screw your bootloader you can actually fix your phone.
Also, and this is pure speculation, should Verison decide to discontinue support for the Eris entirely, non-rooters may have issue getting new Android versions since they're limited to signed code.
EDIT: there is also little reason NOT to root. It does everything that you can do unrooted and more. All this plus the fact that you may never be able to root again but could always unroot at your leisure.
Click to expand...
Click to collapse
Can you point me to a good nandroid tutorial? tried searching for one but if you know of a good one I'd appreciate it.
I was trying to find a nandroid guide when I did it the first time, but once I discovered that Amon_RA's recovery has it built-in, I decided to wing it and see what happened. It was a lot easier than I expected to be honest.
Reboot your phone into recovery (VOL UP + Power), you should have a short list of options, one of which should be Backup/Restore. Trackball into it and select to make a backup. Let it do it's thing, should take a few minutes. Congratulations, you've made a backup of your phone. You can make as many as you like, they're given names based on the date and time they're created, but you can rename without harm (barring a few characters keep it A-Z a-z 0-9 and you should be good)
Restoring to that backup is as easy as entering the same menu but picking restore instead. You need to have made a backup first in order to restore something.
NOTE: I've written all this by memory, and while it should be fairly accurate, I can't turn my phone off currently to double check that the wording is all correct.
I'm a bit confused on the Amon thing. I found the the link here http://forum.xda-developers.com/showthread.php?t=648025
Do I just dump that IMG file onto the root of my SD card and that's it? Will it know to always use his recovery or do I need to do more?
I have an application that I write to make going from 1.5 to root a lot easier with a gui application. It will be released very soon for everyone to use. Take a look at my thread for more info. Link is at the top of my signature.
Sent from my Eris using the XDA mobile application powered by Tapatalk
frankspin said:
I'm a bit confused on the Amon thing. I found the the link here http://forum.xda-developers.com/showthread.php?t=648025
Do I just dump that IMG file onto the root of my SD card and that's it? Will it know to always use his recovery or do I need to do more?
Click to expand...
Click to collapse
If you followed Ivan's guide to the very end, you already flashed Amon_RA's recovery to your phone. To enter it, shutdown your phone and then hold volume up and the call end button (power), you should boot into the recovery.
Marisa said:
If you followed Ivan's guide to the very end, you already flashed Amon_RA's recovery to your phone. To enter it, shutdown your phone and then hold volume up and the call end button (power), you should boot into the recovery.
Click to expand...
Click to collapse
AWESOME! Thank you I am doing it right now.
NM: got it
Well I got 2.1 on but I did something wrong and can't load rooted 2.1. I get "signature verification failed" message when I load the zip file.
I've poked around the forum looking for solutions but found no situation the same as mine. I'm beginning to prepare to flash a new ROM onto my Eris, so I was doing to do a nandroid backup. I have a rooted 2.1 (non-OTA, it was one of the update versions people posted online before 2.1 officially came out)
So I boot up holding down Power and Volume Down. So far, so good. I get to the screen that has some phone info and then HBOOT, <SEND> FastBoot Mode, <VOL UP> Recovery
I hit Volume up, and phone vibrates, goes to the Androids on skateboards, and then to a picture of the phone with a red triangle and exclamation point inside it. It just stays like that until I pull my battery. Then I can turn it back on to regular mode without any problems. However, I'm not sure what's going on.. and this would be a problem if I wanted to change ROMs.
Any help would be appreciated. Thanks
raconteur001 said:
I've poked around the forum looking for solutions but found no situation the same as mine. I'm beginning to prepare to flash a new ROM onto my Eris, so I was doing to do a nandroid backup. I have a rooted 2.1 (non-OTA, it was one of the update versions people posted online before 2.1 officially came out)
So I boot up holding down Power and Volume Down. So far, so good. I get to the screen that has some phone info and then HBOOT, <SEND> FastBoot Mode, <VOL UP> Recovery
I hit Volume up, and phone vibrates, goes to the Androids on skateboards, and then to a picture of the phone with a red triangle and exclamation point inside it. It just stays like that until I pull my battery. Then I can turn it back on to regular mode without any problems. However, I'm not sure what's going on.. and this would be a problem if I wanted to change ROMs.
Any help would be appreciated. Thanks
Click to expand...
Click to collapse
It sounds like you installed the leaked 2.1 root ROM (very early, buggy version of 2.1) and never installed a custom recovery (your information above indicates that you currently have a stock recovery).
You could verify that this is the case by checking your phone's information against this thread: http://androidforums.com/eris-all-things-root/87118-reference-what-htc-rom-do-i-have.html (it is a little crazy / scary that someone has used the 2.1 base root ROM all of this time given all of the bugs that it had ).
I *think* that you could use jcase's 1-click app (see http://forum.xda-developers.com/showthread.php?t=742228) to push Amon_RA's custom recovery onto your phone.
There's other methods too, but you might want to explore the simplest first.
Amon_RA's recovery works. thanks
scary alien said:
I *think* that you could use jcase's 1-click app (see http://forum.xda-developers.com/showthread.php?t=742228) to push Amon_RA's custom recovery onto your phone.
Click to expand...
Click to collapse
FWIW, that is correct. Even though the "Leak Root" HTC ROM is already rooted, it contains the same chmod 777 symlink business in its' boot scripts, so the jcase OneClick or the Dummies method can be used to install a custom recovery to the "Leak Root" HTC ROM. (Even though it is already a "rooted" ROM in a sense). The recovery could also just be flashed directly using fastboot, as the Leak Root ROM installs the 1.49.2000 S-OFF bootloader.
Sounds like the OP fixed his problem - somehow.
bftb0
bftb0 said:
FWIW, that is correct. Even though the "Leak Root" HTC ROM is already rooted, it contains the same chmod 777 symlink business in its' boot scripts, so the jcase OneClick or the Dummies method can be used to install a custom recovery to the "Leak Root" HTC ROM. (Even though it is already a "rooted" ROM in a sense). The recovery could also just be flashed directly using fastboot, as the Leak Root ROM installs the 1.49.2000 S-OFF bootloader.
Sounds like the OP fixed his problem - somehow.
bftb0
Click to expand...
Click to collapse
Thank you for the confirmation, bftb0 as always...
Yes, it would be nice for the OP to disclose the resolution information for the sake of helping others.
Cheers and Happy New Year's Eve Eve!
I'm not sure what information you're asking for but..
HBOOT-1.49.0000 (PB0010000)
not only did Amon RA recovery work, regular recovery works now as well (unless that's amon RA recovery also, but it looks different). Thanks for your help
in recovery it says
Build: RA-eris-v1.6.2
raconteur001 said:
I'm not sure what information you're asking for but..
HBOOT-1.49.0000 (PB0010000)
not only did Amon RA recovery work, regular recovery works now as well (unless that's amon RA recovery also, but it looks different). Thanks for your help
in recovery it says
Build: RA-eris-v1.6.2
Click to expand...
Click to collapse
I think we were looking for confirmation that you really did have the base leaked 2.1 root ROM--but it looks like, based on the HBOOT version (1.49.0000) that you actually had an un-rooted 2.1 leaked ROM.
Also, you must have run the 1-click app to gain Amon_RA's custom recovery, correct?
If you would have cross-checked the original ROM's Settings -> About Phone -> Software information's "Software version" and "Kernel version" against the information in http://androidforums.com/eris-all-things-root/87118-reference-what-htc-rom-do-i-have.html it would have made diagnosing what was going on a little easier.
Thanks for responding!
Ah. I used z4root some time ago. So i'm definitely rooted because Superuser and Wireless Tether are on my phone. I have the v2 leak: 2.26.605.4
raconteur001 said:
Ah. I used z4root some time ago. So i'm definitely rooted because Superuser and Wireless Tether are on my phone. I have the v2 leak: 2.26.605.4
Click to expand...
Click to collapse
Thanks, the v2 leak info does help .
I'm only familiar with Z4 root w/regard to how it rooted my Droid X...did it (Z4) install Amon_RA's custom recovery or did you get it by another means? (I ask this because your initial post indicated you had trouble booting into recovery and it appeared from what you described to be the stock recovery).
scary alien said:
Thanks, the v2 leak info does help .
I'm only familiar with Z4 root w/regard to how it rooted my Droid X...did it (Z4) install Amon_RA's custom recovery or did you get it by another means? (I ask this because your initial post indicated you had trouble booting into recovery and it appeared from what you described to be the stock recovery).
Click to expand...
Click to collapse
I had to flash RA recovery using the ROM Manager app
raconteur001 said:
I had to flash RA recovery using the ROM Manager app
Click to expand...
Click to collapse
Aha! Thank you very much! That's actually two very useful pieces of information (to me at least ):
1) Z4 can root an Eris without installing a custom recovery (this is the first confirmation I've heard of this)
2) ROM Manager is a good vehicle for flashing / installing a custom recovery (I don't have any direct experience with ROM Manager, so this is good to know).
Thank you again for sharing with all of us!
Cheers and have a safe and Happy New Year!
I have an unrooted HTC Aria (AT&T) that i upgraded to Froyo a couple of weeks ago. I have been using it for a while and i don't like the performance with the new upgrade, it used to be a LOT snappier before.
I would like to know if its possible to revert the phone to Factory Defaults (Eclair 2.1) and where i can get the ROM since HTC is no longer providing it in its website.
I'm not interested in rooting my phone nor custom roms i just want it the way it was at the moment I took it off the box and turned it on for the first time.
If the downgrade is possible I would really appreciate if someone could provide a list of steps to follow to make it happen.
Thanks in advance.
Check out this thread: http://forum.xda-developers.com/showthread.php?t=971119. You can but you will still have the updated HBOOT (Bootloader). You will have to use the ROM linked in post 3 (Original 2.1 Rom)
P.S - Search before starting new threads on the same topic.
http://www.mediafire.com/?cj56c2gfk86k8oe
This is the original ship ROM. I downloaded this back when I first got my phone (first day the Aria was released) and have kept it for future use. This was even before they added the ability to receive OTA updates, so you won't even have to worry about being notified about the 2.2.2 OTA update.
Now, you should be able to just run this and have it downgrade everything (except HBOOT, but that isn't a problem unless you want to root). I haven't actually done it before but it should work.
If it doesn't work, there is another way that will definitely work, but I'll explain that if the need arises. Let me know if you run into any problems.
Theonew said:
Nope. Not possible since you don't want to root your device.
Click to expand...
Click to collapse
It is possible. You can downgrade everything except the HBOOT. (Meaning, he will have the original ROM like he wants but be unable to use Unrevoked, which he doesn't care about.)
drumist said:
It is possible. You can downgrade everything except the HBOOT. (Meaning, he will have the original ROM like he wants but be unable to use Unrevoked, which he doesn't care about.)
Click to expand...
Click to collapse
That post I made was a mistake. That's why I edited it. Sorry I didn't get to change it in time.
Theonew said:
Check out this thread: http://forum.xda-developers.com/showthread.php?t=971119. You can but you will still have the updated HBOOT (Bootloader). You will have to use the ROM linked in post 3 (Original 2.1 Rom)
P.S - Search before starting new threads on the same topic.
Click to expand...
Click to collapse
To be honest the advice from those threads is not really very good anyway. You don't need temp root on your device. There are easier methods that ought to work fine. Namely, just putting the 2.1 RUU zip as LIBEIMG.zip on your SD card. But from what I've read, even just running the RUU should be enough.
(Nevermind, this doesn't work.)
Thanks for you advice, in fact did some research before creating the thread, but all the threads i found were about people who wanted to downgrade to get the root back, so they were either redirected to other threads or were given a lot information not relevant to what i really need.
drumist said:
This is the original ship ROM. I downloaded this back when I first got my phone (first day the Aria was released) and have kept it for future use. This was even before they added the ability to receive OTA updates, so you won't even have to worry about being notified about the 2.2.2 OTA update.
Now, you should be able to just run this and have it downgrade everything (except HBOOT, but that isn't a problem unless you want to root). I haven't actually done it before but it should work.
If it doesn't work, there is another way that will definitely work, but I'll explain that if the need arises. Let me know if you run into any problems.
Click to expand...
Click to collapse
I tried this but for some reason i got a BOOTLOADER VERSION ERROR [140] message. Thanks for your help anyway.
eljuanpelos said:
I tried this but for some reason i got a BOOTLOADER VERSION ERROR [140] message. Thanks for your help anyway.
Click to expand...
Click to collapse
Don't give up yet. This next method should work if that one didn't.
Download this file: http://www.mediafire.com/?ct1ay7t93d8g742
Rename the zip file as LIBEIMG.zip (don't extract it) then place it on your SD card (not in a subfolder).
Then turn the phone completely off, and press VOL DOWN + power to turn the phone back on. It should detect the file after a couple seconds and start flashing it automatically. At this point just be patient for a minute or two, then press VOL UP key to start the update process when it asks you to. After that, be patient while it does everything. It takes about 5 minutes to finish installing everything and will reboot once during the process. After it's done (it will tell you when it's done), the phone will reboot and there will be a scary looking screen but JUST WAIT about 10 seconds and it will boot normally. Then you're good to go.
After you're done with this, make sure to DELETE the LIBEIMG.zip file from your SD card. Otherwise it will ask you every time you go into HBOOT if you want to apply the update.
Good luck.
drumist said:
Don't give up yet. This next method should work if that one didn't.
Download this file:
Rename the zip file as LIBEIMG.zip (don't extract it) then place it on your SD card (not in a subfolder).
Then turn the phone completely off, and press VOL DOWN + power to turn the phone back on. It should detect the file after a couple seconds and start flashing it automatically. At this point just be patient for a minute or two, then press VOL UP key to start the update process when it asks you to. After that, be patient while it does everything. It takes about 5 minutes to finish installing everything and will reboot once during the process. After it's done (it will tell you when it's done), the phone will reboot and there will be a scary looking screen but JUST WAIT about 10 seconds and it will boot normally. Then you're good to go.
After you're done with this, make sure to DELETE the LIBEIMG.zip file from your SD card. Otherwise it will ask you every time you go into HBOOT if you want to apply the update.
Good luck.
Click to expand...
Click to collapse
Unfortunately this method doesn't work either, it throws an error that says "Main Version is older, Update Fail!"
I could have sworn I've read about this working before. I would have tested it first myself but I don't have a phone that isn't S-OFF. Sorry for making you jump through hoops.
You could try the methods in the other threads linked above. I guess you do need temp root to do a downgrade.
Alternatively, you could use AlphaRevX to S-OFF, install Clockwork, and install the factory original, unrooted ROM. The downside of this is that it requires voiding your warranty if you have one.
Easiest way would be to run the official 2.2 RUU update from HTC. 100% stock.
Sent from my Liberty
Optic2 said:
Easiest way would be to run the official 2.2 RUU update from HTC. 100% stock.
Sent from my Liberty
Click to expand...
Click to collapse
He wants to return to android 2.1 so that wouldn't help whatsoever. Plus he already did that which is why he wants to downgrade.
Oh my bad, I didn't read the whole thread. Hmm why do you want to downgrade to 2.1?
Sent from my Liberty
Optic2 said:
Hmm why do you want to downgrade to 2.1?
Sent from my Liberty
Click to expand...
Click to collapse
This is the reason which he said in his post:"I don't like the performance with the new upgrade, it used to be a LOT snappier before."
drumist said:
This is the original ship ROM. I downloaded this back when I first got my phone (first day the Aria was released) and have kept it for future use. This was even before they added the ability to receive OTA updates, so you won't even have to worry about being notified about the 2.2.2 OTA update.
Now, you should be able to just run this and have it downgrade everything (except HBOOT, but that isn't a problem unless you want to root). I haven't actually done it before but it should work.
If it doesn't work, there is another way that will definitely work, but I'll explain that if the need arises. Let me know if you run into any problems.
Click to expand...
Click to collapse
One question... I have HTC Gratia, which is operator free, so can I restore your original (backuped) ROM on my phone and update it, so I can use it just like original one?
UPDATE: The latest update still is safe. I just installed it and I am still s-off.
UPDATE: The update to Jellybean does not write the secure flag and this method is safe to apply the OTA update with this method and still maintain root access afterwards.
First and foremost, a couple disclaimers.
FIRST, YOU MUST BE S-OFF FOR THIS TO WORK. PLEASE DO NOT TRY THIS IF YOU ARE NOT ALREADY S-OFF.
SECOND, FOR THE OTA UPDATE 1.22.651.3 YOU WILL FOR SURE RETAIN S-OFF. ALTHOUGH HIGHLY UNLIKELY, HTC COULD POTENTIALLY MAKE YOU S-ON IN FUTURE OTA UPDATES. SEE HERE FOR MORE INFORMATION.
To obtain s-off please see this thread: http://unlimited.io/jewel.htm
Once you are s-off you can install the OTA update no problem and still retain root. I understand that there are rooted ROMs that come out within a day or whatever, I find this method just easier and less annoying that waiting for a rooted stock ROM to come out. I don't really theme, mod, or do crazy things with my phone but still want root access. So, I decided since I was s-off, I would give this method a whirl. I am happy to report that I am s-off, with TWRP, fully rooted, and with installing the OTA update. I had a little hiccup but was able to solve that.
So, here is the process. This is kind of a hodge podge of different threads, ideas, devices, and versions of android so if I didn't give you credit, please let me know and I will put you in this thread.
Process for installing a stock recovery. I have already created some stock recovery files so see at the bottom of this post for the zip file that includes the stock recovery. If you wish to use these files, just start with step #10.
IF YOU CHOOSE TO JUST DOWNLOAD THE STOCK RECOVERY AT THE BOTTOM OF THIS POST, SKIP TO STEP #10.
Creating Stock Recovery File Manually
1. Install a stock recovery if you don't already have one.
2. To do so, get the RUU for the version you are running.
3. Run the RUU (don't connect to your phone at all)
4. Navigate to your temp directory on your computer (on windows 7 it is C:\Users\your_user_name\AppData\Local\Temp)
5. Find a folder that looks like it is in the following format "{XXXXXX-XXXX-XXXX-XXXX-XXXXXXXX}" It might help to sort by date modified. The folder should have the current date
6. Inside the folder might be a couple other folders. Navigate through the folder to find a zip that says "firmware" or "rom" (mine said rom)
7. Extract the content to a folder in the same directory called rom
8. Navigate into the rom folder and find two files android-info.txt and recovery_signed.img. Copy those to a directory of your choice.
9. Send those files to a zip folder and name the file "PJ75IMG.zip" without the quotes. Make sure zip is only listed once. If you have file extensions hidden in windows yours will only say "PJ75IMG".
Installing the stock recovery, OTA, and regaining root
10. Place the stock recovery file on the root of your sd card
11. On your phone, head into settings and power and make sure the fastboot option is unchecked
12. Power down phone
13. Once phone is completely shut down, hold the volume down button and press the power on button while keeping the volume down button pressed.
14. It will boot into your hboot (verify it says s-off at the top or don't proceed) and find the file you placed on your sd card and ask you if you want to update. click volume up for yes. Reboot once finished. After your phone boots up, navigate to the root of your sdcard and delete PJ75IMG.zip
15. Go to settings>check for updates and check to see if there is an update. Download the update. Once it verifies, click install now. It should install just fine.
16. Once you are up and running, download one of the dirty racun hboots. I used hboot 2.09 img found here. Follow the instructions on the unlimited.io website how to flash the hboot by using fastboot (flashing the zip doesn't seem to be working.
update. click volume up for yes. Reboot once finished. After your phone boots up, navigate to the root of your sdcard and delete PJ75IMG.zip
17. Make sure usb debugging is checked under settings>developer options
18. Go download a su zip file. I used this one here and place it on the root of your sd card.
19. Go grab a custom recovery flashable zip (could not find the latest twrp zip) or img (I used TWRP found here. Take the image and place it in your platform tools folder for ADB.
20. Plug in phone while powered on and type in adb devices to make sure you are connected.
21. If you see a device type in
Code:
adb reboot bootloader
22. Your device will boot into your bootloader and you will see fastboot usb (make sure usb debugging was checked if you don't see that).
23. Then type fastboot flash recovery [filename] of the recovery img you downloaded. Once flashed, toggle with the volume up buttons to bootloader and then select recovery. This should boot you into TWRP
24. Once in recovery, install the su zip you downloaded in step 18.
25. Reboot and Enjoy!!!!
You are now rooted with the most current OTA update and all the goodies (radios, PRI, etc.)
This process should hopefully hold true for any future OTA updates if you are S-OFF. The only thing you will have to find is the current RUU to create the stock recovery. If this helped, feel free to thank! Go XDA!
There already are rooted stock roms out.
Why even risk it? It takes less than a day
Sent from my EVO using Tapatalk 2
Rxpert said:
There already are rooted stock roms out.
Why even risk it? It takes less than a day
Sent from my EVO using Tapatalk 2
Click to expand...
Click to collapse
I don't know. So you don't have to wait at all? Or for the people that aren't accustomed to flashing ROMs or don't care to. I prefer this method for whatever reason and it seems just easier. Personal preference though. The beauty of android and their strong developer network is that it gives the users choices. I can take the OTA update as soon as it comes out and don't have to worry about waiting for anything. Just another method I guess.
TLR there are already rooted stock roms in one of the dev forums. Flash it and flash the update firmware via bootloader and you're done.
Sent from my htc_jewel using Tapatalk
msimindlessmsi2 said:
TLR there are already rooted stock roms in one of the dev forums. Flash it and flash the update firmware via bootloader and you're done.
Sent from my htc_jewel using Tapatalk
Click to expand...
Click to collapse
The update firmware is the part that hangs me up. I believe when it was back in the original EVO days that some people were having problems updating their PRI version and it screwed up some things with wimax. That is when I decided I would just accept the OTA to get everything they included in the update and then gain root access through this method.
Again, to each their own. Please try not to clutter up the thread with off topic items. Thanks.
Because all of the ROM flash threads state you have to do a factory reset. Even with Titanium, I don't have the time to reset everything back up the way I want it... including all the folders I've created, etc. If you could flash a ROM and maintain all your data intact, I might consider it. Perhaps there's something I'm unaware of.
Rxpert said:
There already are rooted stock roms out.
Why even risk it? It takes less than a day
Sent from my EVO using Tapatalk 2
Click to expand...
Click to collapse
im coming from the rezound, i just want the updated firmware! on my rez being s-off i could run ANY firmware ICS, or GB and then go back to whatever rom i was running. im wondering if im s-off, i should b able to do the same thing right.
greyopaque said:
Because all of the ROM flash threads state you have to do a factory reset. Even with Titanium, I don't have the time to reset everything back up the way I want it... including all the folders I've created, etc. If you could flash a ROM and maintain all your data intact, I might consider it. Perhaps there's something I'm unaware of.
Click to expand...
Click to collapse
The devs state that so that they don't have to spend their valuable time troubleshooting because you didn't flash right. Its always best to do a full wipe, but not always required when flashing an updated version of the same ROM.
1) Nandroid.
2)Wipe Dalvik cache & cache
3) Flash
You retain all data.
If you have issues, then you nand restore and do a full wipe before bugging the devs
bpdamas said:
Once you are s-off you can install the OTA update no problem and still retain root. I understand that there are rooted ROMs that come out within a day or whatever, I find this method just easier and less annoying that waiting for a rooted stock ROM to come out.
Click to expand...
Click to collapse
Lmao! You find that whole process "easier" than waiting for a day? I think it might take the better part of a day to do all that.
Sent from my EVO using xda premium
Thanks for taking the time to do a write-up OP!
Good tutorial. I actually waited but this definitely a decent tutorial. Don't listen to anyone saying that it is dumb not to wait. Why do they care what you do with your device?
Sent from my EVO using Tapatalk 2
Actually, TWRP has a PJ75IMG.zip on their site that can be flashed the same way as the HBOOT. And then, you can flash Superuser from TWRP.
I did everything from my SD card. And, in response to the person saying it would take the better part of the day... the whole thing took me barely 10 minutes, and I have a completely updated phone, all the firmware, radios, etc. And all my data and settings are intact. I think that for someone like me that likes everything stock, but rooted (for WiFi Tether and Adblock), this is the best way to go.
greyopaque said:
Because all of the ROM flash threads state you have to do a factory reset. Even with Titanium, I don't have the time to reset everything back up the way I want it... including all the folders I've created, etc. If you could flash a ROM and maintain all your data intact, I might consider it. Perhaps there's something I'm unaware of.
Click to expand...
Click to collapse
Agreed.
EPayne123 said:
Good tutorial. I actually waited but this definitely a decent tutorial. Don't listen to anyone saying that it is dumb not to wait. Why do they care what you do with your device?
Sent from my EVO using Tapatalk 2
Click to expand...
Click to collapse
Definitely agreed.
greyopaque said:
Actually, TWRP has a PJ75IMG.zip on their site that can be flashed the same way as the HBOOT. And then, you can flash Superuser from TWRP.
I did everything from my SD card. And, in response to the person saying it would take the better part of the day... the whole thing took me barely 10 minutes, and I have a completely updated phone, all the firmware, radios, etc. And all my data and settings are intact. I think that for someone like me that likes everything stock, but rooted (for WiFi Tether and Adblock), this is the best way to go.
Click to expand...
Click to collapse
I know. This is exactly why I root and I can't believe there are so many people against this method. It seems very simple to me and I can have a stock recovery waiting to flash as soon as an OTA update comes out. Oh well.
Thanks for this info. I think I'm like you and not only like the stock experience and its benefits but also prefer diy when possible.
Of course I never seem to stay stock like you but I like doing the steps my self. To each their own is the beauty of android.
Go android!
Sent from my EVO
i just noticed my internal was wiped for some odd reason? im attempting to run the previous ruu, to get my notification sounds and everything back.
Rxpert said:
There already are rooted stock roms out.
Why even risk it? It takes less than a day
Sent from my EVO using Tapatalk 2
Click to expand...
Click to collapse
One advantage to me would be you're getting the official ROM/update, and you don't have to worry about a malicious dev slipping in some malware.
zounduser said:
i just noticed my internal was wiped for some odd reason? im attempting to run the previous ruu, to get my notification sounds and everything back.
Click to expand...
Click to collapse
Very curious on this. Nothing in this method should affect this.
Robbie_G said:
One advantage to me would be you're getting the official ROM/update, and you don't have to worry about a malicious dev slipping in some malware.
Click to expand...
Click to collapse
..... I'm blown away by this.
Really?
Why do you even have S-off then? That required you down download specific drivers, and run a program as an administrator on your computer. If you're concerned about a rogue dev they would've royally screwed you there.
/Tin Hat
Rxpert said:
..... I'm blown away by this.
Really?
Why do you even have S-off then? That required you down download specific drivers, and run a program as an administrator on your computer. If you're concerned about a rogue dev they would've royally screwed you there.
/Tin Hat
Click to expand...
Click to collapse
That's fair, rooting and s-off could also inject malicious code. But so can ROM makers.
I think there's a difference between trying to be safe and being paranoid. If there is a way for someone to make money off of you/steal your identity, eventually they will try. I'm not suspicious of any of the current devs, but it's something we should maybe be more aware of. Look at all the warez Windows out there with malware built in to steal your information.
EPayne123 said:
Good tutorial. I actually waited but this definitely a decent tutorial. Don't listen to anyone saying that it is dumb not to wait. Why do they care what you do with your device?
Sent from my EVO using Tapatalk 2
Click to expand...
Click to collapse
Totally agree. Its a good thing to learn in my opinion. I broke my Evo 4G, fixed it then rerooted it. Now on the 4G LTE got it rooted with custom rom. Love learning new things plus some of the good things that come with rooting and custom roms are worth it for me.
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?