Database Users

Anyone Willing to Help? Stock To FroYo

I guess I missed this over the weekend and I am looking for the original install that I dont need to have root for. I have been reading over the threads here and in the Dev forum and I am not seeing any links to the download for Non-Root users.
I am to much of a ***** to root my phone. i spent way to much cash on it and i am too worried something will go wrong.
So here is want I am asing for
A. The original non root install with instructions on how to do it
or
B. Someone to help walk me through the process of rooting and getting FroYo 2.2 set up on my phone.
Please shoot me a PM if your willing to help out. I am just way to worried if I do this without someone who knows what they are doing I am going to screw up my phone, and my wife would never let me buy another one ...lol
Can somsone help out a fellow Dev, thanks

Sorry I can't post links but here you go
androidandme.com/2010/05/news/how-to-manually-install-android-2-2-on-your-nexus-one/

Ya just found it buried in a thread
Thanks
See if I would have spent another 10 minutes searching I would have found it without having to ask ...lol
Got to remember to scan threads for 30 minutes not 20 before asking ...lol

Or use this: http://forum.xda-developers.com/showthread.php?p=6043779#post6043779
(Or the Root/2.2 links in my sig.)

Okay, I'll give you the general idea, as I understand it:
The FRF50 ROM that was leaked from Google is exclusively for ERE27 Builds only. Unless that is the native build on your phone, you will not be able to apply that as is.
Paul O'Brien, over at Modaco, repacked it so that it can be flashed with any current ROMs. Though he's said that there are no conditions, there in fact are a few stipulations to be aware of.
-If you have never unlocked your bootloader, you won't be able to flash anything at all. Something to think about. There's a few threads here dedicated to this topic alone. It voids your warranty so that is why some people are holding off and waiting for the official OTA update to be released.
-Though it's true that you don't have to be rooted to flash Paul's repack, unless you have ERE27 stock, you need to flash using one of the custom recovery images. And in order to flash your recovery.img, you need to be rooted. So you need to have had rooted before.
So the steps, from stock, would be:
(1) Unlock your bootloader, via flashboot.
(2) Flash superuser to your boot.img (aka rooting)
(3) Flash a custom recovery to recovery.img (I use RA)
(4) Flash Paul's FRF50 repack using said recovery image.
I'm sorry I can't post the links to the relavant posts, but my status as a member doesn't allow me to. Hope this helped clear some things up for you.

Paul22000 said:
Or use this: http://forum.xda-developers.com/showthread.php?p=6043779#post6043779
(Or the Root/2.2 links in my sig.)
Click to expand...
Click to collapse
Paul, is that Avatar a picture of YOU?

OMG theres a search feature!!!
Really OMG I didnt know this!
I guess me saying I searched threads and the site for 20 minutes was something you missed.
But thanks to all who actually decided to help and not be another one of these "USE SEARCH" people.
I respect the work you do for us here Paul, but come on man. Read before making a post like that ....lol

attn1 said:
Paul, is that Avatar a picture of YOU?
Click to expand...
Click to collapse
All I wil say is:
λ

LOL ...........

you don't need to root to install froyo and you don't need to hook up your nexus to a pc. my method is pretty simple and it works.
edit: I shouldn't say it's my method. Its actully a backdoor to installing froyo.

theletterj said:
Okay, I'll give you the general idea, as I understand it:
The FRF50 ROM that was leaked from Google is exclusively for ERE27 Builds only. Unless that is the native build on your phone, you will not be able to apply that as is.
Paul O'Brien, over at Modaco, repacked it so that it can be flashed with any current ROMs. Though he's said that there are no conditions, there in fact are a few stipulations to be aware of.
-If you have never unlocked your bootloader, you won't be able to flash anything at all. Something to think about. There's a few threads here dedicated to this topic alone. It voids your warranty so that is why some people are holding off and waiting for the official OTA update to be released.
-Though it's true that you don't have to be rooted to flash Paul's repack, unless you have ERE27 stock, you need to flash using one of the custom recovery images. And in order to flash your recovery.img, you need to be rooted. So you need to have had rooted before.
So the steps, from stock, would be:
(1) Unlock your bootloader, via flashboot.
(2) Flash superuser to your boot.img (aka rooting)
(3) Flash a custom recovery to recovery.img (I use RA)
(4) Flash Paul's FRF50 repack using said recovery image.
I'm sorry I can't post the links to the relavant posts, but my status as a member doesn't allow me to. Hope this helped clear some things up for you.
Click to expand...
Click to collapse
Okay, there's a lot of good info out there mixed in with a lot of mis-information.
Your steps will work BUT:
I prefer to do it this way:
Unlock the boot loader via fastboot
Flash Amon_RA 170 recovery for Nexus One
Do a nandroid Backup
Flash your ROM of choice (Modaco's FROYO in this case)
If you are running stock recovery, you CAN flash, but only Google's updates. If you have a T-mobile N1 this may work for you without unlocking the bootloader by flashing the Google Froyo Release with the stock recovery:
Google Froyo Release
You must be on release ERE27 for this to work.
Here's a link to some instructions on how to use the stock recovery program:
jp_macaroni's thread
I suspect that since most people have already rooted or cannot get to ERE27, Paul's guide is the best way to go for them.
If you are running a custom recovery, you can flash custom updates, but NOT Google's updates intended for any stock phone/firmware level.
You don't need to root (root access) to the current ROM before flashing a custom ROM. You only need to unlock the bootloader and install a custom recovery image.

jcohenlv said:
OMG theres a search feature!!!
Really OMG I didnt know this!
I guess me saying I searched threads and the site for 20 minutes was something you missed.
But thanks to all who actually decided to help and not be another one of these "USE SEARCH" people.
I respect the work you do for us here Paul, but come on man. Read before making a post like that ....lol
Click to expand...
Click to collapse
Yeah you know, everyone is new once. It's easy to sort out the tripe from the real deal when you've been around the block once or twice. Paul is doing his best to be helpful and not cause more confusion.
The problem isn't that people can't search so much as it is that searches yield too much conflicting information, so lets not jump down people's throats when they ask for a point of clarification. Instead, lets start asking moderators to sticky good info and pulling redundant/bad info so that searches are more meaningful. The number of new threads in here because of the Froyo release is mind numbingly high. Let's all try to exercise some patience.

attn1 said:
Okay, there's a lot of good info out there mixed in with a lot of mis-information.
Your steps will work BUT:
I prefer to do it this way:
Unlock the boot loader via fastboot
Flash Amon_RA 170 recovery for Nexus One
Do a Nadroid Backup
Flash your ROM of choice (Modaco's FROYO in this case)
If you are running stock recovery, you CAN flash, but only Google's updates. If you have a T-mobile N1 this may work for you without unlocking the bootloader:
If you are running a custom recovery, you can flash custom updates, but NOT Google's updates intended for any stock phone/firmware level.
You don't need to root (root access) to the current ROM before flashing a custom ROM. You only need to unlock the bootloader and install a custom recovery image.
Click to expand...
Click to collapse
I'm not disagreeing with you, but as far as I know, yes, you do have to root in order to flash Amon_RA Recovery to your phone. If that's not correct, I apologize for spreading misinformation.

theletterj said:
I'm not disagreeing with you, but as far as I know, yes, you do have to root in order to flash Amon_RA Recovery to your phone. If that's not correct, I apologize for spreading misinformation.
Click to expand...
Click to collapse
You only need to unlock the bootloader. You do not need root.
Unlocking the boot loader allows installation of an alternate recovery, which allows you to install custom software to the existing ROM or to install a custom ROM. It's updating the ROM that allows you to gain root access, not unlocking the boot loader. It goes in this order:
> Unlock boot loader (void warranty - still not rooted)
> Install custom recovery
> nandroid backup (recommended/optional)
> Update ROM (for root access - or not)

The original instructions worked perfect
All that was needed was to change the name to update.zip load it on the root of the SD card then but the phone in bootloader and load recovery from SD.
Took about 5 minutes.
Once the phone came up it did a few things and took about another 5 minutes to chill on the processes then I was able to use the phone without any problems.
So for those interested here are the exact steps:
This is for NON Rooted T-Mobile Version!!!!
To manually install Android 2.2 on the Nexus One, perform the following steps:
1. Download the official Android 2.2 firmware for the Nexus One.
2. Copy the file to your microSD card and name it update.zip (newb warning: not update.zip.zip)
3. Power off your phone.
4. Hold down the VOLUME DOWN button and power it back on.
5. The phone will now search for files like PB00IMG.zip, etc. This is normal. Scroll down to recovery (using Volume Down Key) and press the POWER button.
6. When you see the “/!\” symbol, press the POWER button and the Volume Up button at the same time. You should be presented with a menu and one of the options should be “Apply sdcard:update.zip”.
7. Use the trackball to navigate to “apply sdcard:update.zip” and select it.
8. When you see “Install from sdcard complete”, select “reboot system now”.
Wait 5 minutes, phone will reboot once rebooted let the phone sit for about 5 minutes then you are good to go. It couldn't be any easier

Have to admit I need some help with rooting

Ok so this is whats been happening. I have an eris im trying to load a custom rom on after I did the 2.1OTA
When I came out to XDA to use the root I was at first confused since it was all going from 1.5 to 2.1. After reading further I read reports that 2.1OTA is rootable just like 1.5 as long as I follow the proper steps.
I: Gaining root
An unlocked hboot will allows us to flash in a modified IMG ROM signed with test keys as supposed to requiring an official ROM from HTC. This will open us to be able to flash a modified recovery.
1. Download this file: PB00IMG.zip (md5: 63eacc5ede3b179f95dc22d8ef585f94)
2. Place PB00IMG.zip onto the root directory of your sdcard.
3. Power down your phone.
4. Hold Volume Down while you Power On. This should bring you to a screen saying "HBOOT" and some other stuff. Wait for it to load the image, and it will say Push Activate. Push the trackball button to continue. The process will take around 5-10 minutes. The first time your phone boots up it will take a lot longer than normal.
Click to expand...
Click to collapse
I think this is where things go wrong. When this was attempted it I saw that my bootloader was now reading 1.49 (phone never been rooted before) instead of the one people report you need to root which is 1.47
It loaded up under 2.1 still and I believe its still the 2.1OTA so I head on to next step for recovery img. something seems to have gone wrong with it too (possibly me messing up the sdk) as now when I try to load any recovery images via fastboot "FAILED <remote: not allow>
Now the more trouble part is now that its ready I follow the instructions on how to actually load the rom through the recovery and SD card method. I believe my recovery is not what its supposed to be either as when it loads I see an android next to a caution symbol with a yellow ! and when the recovery screen is brought up I only have 4 options. Ill type abit what I see
"
Android system recovery <2e>
Use volume key to highlight:
click power key to select.
Reboot system now
Apply sdcard:update.zip
Wipe data/factory reset
Wipe cache partition
E:Can't open /cache/recovery/command"
Now I have tried the instruction of wiping first with a data and cache wipe but it does not give me any options after that on to flash from sdcard
IV: Flashing a custom ROM
1. Download the Rooted 2.1 v0.8T2 zip file.
2. Copy the WHOLE zip file to the root directory of your SD card. (You can enable USB-MS enable from your shiny new recovery to mount your phone as a USB Mass Storage device.)
3. Choose Wipe. Choose data/factory Reset (In the stock ROM, the dalvik is stored in the data and you don't have an EXT partition... yet.)
4. Choose Flash zip from sdcard. Find the eris_0_3.zip file.
5. Wait until it shows as complete and choose reboot system now.
Click to expand...
Click to collapse
I have tried putting different ROM's on my sdcard. I attempted to downgrade using the tutorial provided and using the official RUU from PCD's website. (which both didnt work as downgrade would stop at recovery or RUU states wrong bootloader version towards the middle of the load) and I tried even renaming the ROM's to update.zip the message I get everytime is the same with 2 results one for the rom without the update.zip and one with it.
(with update.zip)
-- Install from sdcard...
Finding update package...
Opening update package...
Verifying update package...
E:signature verification failed
Installation aborted
(without update.zip)
Finding update package...
Opening update package...
Verifying update package...
E:signature verification failed
Installation aborted
Also for those wondering I followed the method of installing drivers and using debugging mode ....all drivers seem to be working fine.
Also just for further info when I run the RUU to try and downgrade my bootloader goes back to showing 1.47 but the radio is still 2.40 if this gives and help
If some could first tell me where I went wrong and then where to go from here I will be most appreciative and im even willing on putting out a reward if someone can do this for me quickly (I am poor some it wont be a big reward but it will be something)
Thanks for any help.

This means you are on the leaked version now and there is nothing that can be done as of right now.

K well thanks for the short and sweet answer. Can anyone tell me how I went from stock 2.1OTA to getting the leaked verision? was it step number one that did it? something didnt load correctly after that?

ca2l3vin said:
K well thanks for the short and sweet answer. Can anyone tell me how I went from stock 2.1OTA to getting the leaked verision? was it step number one that did it? something didnt load correctly after that?
Click to expand...
Click to collapse
So you saying you had 1.5, then got the OTA update from Verizon?
If that is true, are you sure you downloaded the correct root image? Cuz if I remember correctly, the non root one is named the samething. But I could be wrong as I never tried leak.

sounds like you got a bad pb001.img file.

ca2l3vin, it sounds like you may have downloaded and flashed the wrong PB00IMG.zip file. Where did you get it from?

nevermind addressed my issue

As far as I understood I got it from the tutorial was the first place I got it. After I started to have issues I downloaded it from another site thinking I could just update with correct one. Same name same file size and unfortunately same results.
also I did forget to put in my build number like the above post so ill drop that in now.
Firmware Version
2.1
Baseband Version
2.40.00.01.22
Kernel Version
2.6.29-5898f66b
[email protected] #1
Build Number
2.19.605.1 CL123435 test-keys
Software Number
2.19.605.1
Browser version
webKit 3.1
PRI Version
2.11_002
PRL Version
51866 (I know this is just area based)
ERI Version
5

ca2l3vin said:
As far as I understood I got it from the tutorial was the first place I got it. After I started to have issues I downloaded it from another site thinking I could just update with correct one. Same name same file size and unfortunately same results.
also I did forget to put in my build number like the above post so ill drop that in now.
Firmware Version
2.1
Baseband Version
2.40.00.01.22
Kernel Version
2.6.29-5898f66b
[email protected] #1
Build Number
2.19.605.1 CL123435 test-keys
Software Number
2.19.605.1
Browser version
webKit 3.1
PRI Version
2.11_002
PRL Version
51866 (I know this is just area based)
ERI Version
5
Click to expand...
Click to collapse
I hate linking back to another forum, but I used this guide and it worked flawlessly for me.
http://androidforums.com/all-things-root-eris/53963-guide-stock-1-5-latest-root-2-1-a.html
Did not check your link to see if its teh same but I can vouch that this one is 100% working.

af man...seriously!

out of curiously i reboot my phone via power + volume up and saw my hboot version 1.49.... it's werid because I had my phone rooted long ago when I was running on 1.50. Anyway, I'm still able to boot into Amon_RA's recovery and using Tainted Vanilla ROM as of now. I'm thinking it might be because of *228 actually reprogrammed SPL somehow, because i saw glimpse of message during programming phase, it said "SPL unlocked" and "OTA update completed"

HAAZAAAA!!!! Thanks to droidkevlar
So what happened was the wording on the original tutorial confused me quite abit. basically on the recovery step I skipped over it completely due to the fact that it was worded as an optional step for just creating your own recovery point. Once I read the guide linked by droidkevlar I see that THAT is the actually Amon's Recovery image needed to load the custom ROMS in the first place.
ITS A NEEDED STEP not really an optional one (unless your a dev I guess)
I just did my first flash to the EvilEris Rom and now will be trying others out.
I think the tut should be possibly re-worded as I have seen others that seem to be in the same boat I was in. or atleast put in that all steps are needed.
Anyways all the steps and files are the same on both so just follow them both out all the way and it works with 2.1OTA

ca2l3vin said:
HAAZAAAA!!!! Thanks to droidkevlar
So what happened was the wording on the original tutorial confused me quite abit. basically on the recovery step I skipped over it completely due to the fact that it was worded as an optional step for just creating your own recovery point. Once I read the guide linked by droidkevlar I see that THAT is the actually Amon's Recovery image needed to load the custom ROMS in the first place.
ITS A NEEDED STEP not really an optional one (unless your a dev I guess)
I just did my first flash to the EvilEris Rom and now will be trying others out.
I think the tut should be possibly re-worded as I have seen others that seem to be in the same boat I was in. or atleast put in that all steps are needed.
Anyways all the steps and files are the same on both so just follow them both out all the way and it works with 2.1OTA
Click to expand...
Click to collapse
Glad I could help. Aloysius is also a very good one to check out. Heard there are issues with v12 but v11 maps is solid!

[Q] All I want is Frodo 2.2 + root...but how???

All I want to do is upgrade to Froyo 2.2 and retain root so that I can use Wireless Tether. I've been reading several different EVO/Android forums but it seems like the more I read, the more confusing it gets. I'm still a noob, but here are my questions so I hope someone can lay it all out in the open for me.
Currently, my EVO has Unrevoked3 applied so I'm running on the "updated" 2.1, and I have root access and wireless tether is working as of now. Phone specs are:
Firmware version: 2.1-update1
Baseband version: 2.05.00.06.10
Build/Software number: 1.47.651.1
PRI version: 1.40_003
PRL version: 60665
1) What is the best/most reliable way for me to update to 2.2? Can I use Unrevoked Forever to do so? Or do I have to use some manual method? Toast's method? ROM Manager?
2) I read the steps for installing on the Unrevoked site, but I don't understand the terms it uses. It says to "flash from custom recovery". First of all, how do I access this custom recovery tool or whatever? Second, some ppl said they use a ROM Manager. Other sites say to "boot into recovery". Still, some instructions say boot into Clockwork....How do these method differ? Or are they the same? Which do I use???
3) One post says "After you unrevoke4, you can use your custom recovery image to flash a rooted 2.2 stock rom". I dont understand. A ROM is an image...so how can I use an image to flash another image?? makes no sense =\
4) Is "recovery" an app/tool that is already on the phone (or needs to be downloaded), and if so how do I access it? Or is it a ROM image?
5) After unrevoked is done, do I accept the OTA firmware update (i think it's the ugrade to Froyo update that keeps popping up)?
6) Which ROM needs to be installed? The zip that Unrevoked is going to install, or HTC Stock Froyo 3.26.651.6 [Rooted][Deodex'd], or both?
7) What is PRI and PRL and why are ppl so concerned about getting those updated? Will they get updated automatically once Frodo is installed?
8) Same deal with the Wimax and Radio updates. What do they do? Why do ppl want to retain them so badly, and if they are so important, why don't the updated ROMs or OTAs have them included?
9) What's the difference b/t a Nandroid backup and a Titanium backup? And which one should I do?
Please help! Thanks!

one does not simply walk into Mordor.

So I can identify with the OP. I don't know many of those same things, but I am slowly learning through reading these forums.........
However........that comment was quite amusing, also very accurate......... Ya that made my night
Sent from my PC36100 using XDA App

1) What is the best/most reliable way for me to update to 2.2? Can I use Unrevoked Forever to do so? Or do I have to use some manual method? Toast's method? ROM Manager?
Use Simpleroot to fully root. Then flash SteelH's 2.2 Stock Rooted ROM/
2) I read the steps for installing on the Unrevoked site, but I don't understand the terms it uses. It says to "flash from custom recovery". First of all, how do I access this custom recovery tool or whatever? Second, some ppl said they use a ROM Manager. Other sites say to "boot into recovery". Still, some instructions say boot into Clockwork....How do these method differ? Or are they the same? Which do I use???
Power + Volume Down while the phone is off boots your into the bootloader. You can then enter your custom recovery from there. Or you can use Rom Manager/Spare Parts to boot into recovery directly within your phone. Clockwork is a custom recovery; AmonRa is the other custom recovery. Use either one.
3) One post says "After you unrevoke4, you can use your custom recovery image to flash a rooted 2.2 stock rom". I dont understand. A ROM is an image...so how can I use an image to flash another image?? makes no sense =\
You need to install a custom recovery, ie AmonRa or Clockwork (an image) so you can flash a ROM (another image)
4) Is "recovery" an app/tool that is already on the phone (or needs to be downloaded), and if so how do I access it? Or is it a ROM image?
Recovery is already in your phone, but you need to flash a custom recovery after you root. Simpleroot will allow you to flash a custom recovery on the last step.
5) After unrevoked is done, do I accept the OTA firmware update (i think it's the ugrade to Froyo update that keeps popping up)?
Not relevant, when you are on 2.2, you won't be notified of OTA updates. After you root, NEVER accept any OTA. Wait for the updated rooted roms.
6) Which ROM needs to be installed? The zip that Unrevoked is going to install, or HTC Stock Froyo 3.26.651.6 [Rooted][Deodex'd], or both?
Don't use Unrevoked. Root using Simpleroot and flash your downloaded ROM afterwords.
7) What is PRI and PRL and why are ppl so concerned about getting those updated? Will they get updated automatically once Frodo is installed?
No one can really prove that an updated RPI/RPL affects your phone in positive ways. Your RPL will be updated. RPI will be 1.34 after Simpleroot, this forum just figured out how to get 1.40 RPI today (go read the dev forum)
8) Same deal with the Wimax and Radio updates. What do they do? Why do ppl want to retain them so badly, and if they are so important, why don't the updated ROMs or OTAs have them included?
Wimax and Radio updates improves your 4G/Radio/Data performance. They should be flashed after you flash your rom.
9) What's the difference b/t a Nandroid backup and a Titanium backup? And which one should I do?
Nandroid backup creates a complete image of your phone. Titanium backup only backs up your apps.

Speak friend and enter...
Speak friend and enter!
OK then, all the LOTR references aside, I was in your shoes not to long ago. You could have done a little more reading or googling (something like "how to root EVO"), as these forums usually contain a number of threads with titles something like "Moron-proof guide to....."
Anyway. Unrevoked seems to be considered a somewhat incomplete root according to most ROM threads (I don't know the details to speak intelligently on
the matter).
Here is what I did, and it worked well.
1) Get SimpleRoot. This will let you root your phone for real.
NOTE: I don't know if you need to get rid of unrevoked before this; maybe someone more knowledgeable can chime in on this one.
2) Step 2 of SimpleRoot is to flash recovery. There are two options; I chose RA. There are a few threads that talk about pros/cons of each.
For simplicity sake, I think of "recovery" as a program that lets you do lower lever system stuff, like flash files, do backups, etc. The general way to reach it is to hold VolDown while powering up you phone, then selecting "recovery".
Anyways, after you've flashed recovery, you'll be able to flash whatever ROM you want.
3)If you want stock 2.2 get THIS. Get the radios as well. Generally there are instructions with the ROMS, READ THEM.
You should have three zips. Put them on your sdcard. Then in recovery select flash from zip file (or something like that). Do that for all three with reboots in between.
You should now have the latest stock ROM and radios.
There are a ton of other ROMs out there. NO one will be able to tell you which one is the best, so don't ask.
Wireless Tether - the newest version is floating around here somewhere (pre7). It works well with the rooted stock 2.2
The PRL/PRI debate is still going on. You can read the million threads and see if you want to worry about it. I don't.
As far as backup goes, the more knowledgeable folks can speak to the details. A simple way of describing it is nand backup (from recovery) is like a ghost of your system, where as Titanium is more of an apps/settings kinda thing.
I strongly suggest reading the guide threads to gain more insight.
And, of course, I didn't come up with any of this stuff. If you find anyone's work helpful, then you should thank/donate to them.
EDIT: Hehe, looks like I was second in the helpful line.

That pretty much answers it all.
I can address #7.
Once Frodo is installed into mount doom he must cast the ring into the fiya.
Quickly though. For the creature gollum lays await in the shadows of every crevice left behind.
You must upgrade your puke ridden leggings and ingest some pain reducing ibuprofen for maximum connectivity with the force.
There I go switching epics again..

PLEEEASE STICKY!!!!!!!!
Then I could always find this thread in a hurry when I'm in a bad mood and need a pick me up.
This thread has brought great joy to my life. Expect me to bump it about once a week.
It's funny that I have no clue how to do this, because I full-rooted my EVO with the first firmware and never looked back. I've just been running custom recovery and custom roms ever since. I need to root a friends phone soon, so I guess I'll have to learn.

After much lurking and wiki reading I would like this stickied as well.

To get Frodo 2.2, you would have to write a novel, placing him in a setting similar to The Terminator. From there, create a back story on how his first version was inferior and lacking superior abilities, dubbing the need for a new version. After that have a fight scene of him going against his creator, thus needing to make him version 2.2. The non violent version. From there he would have the dramatic speech in a weird code of language.
Simple root, click click, RA, click. Power button volume down. Wipe, wipe. wipe. rooted rom zip, radio zip, reboot, power button volume down wimax zip, reboot.
After that Frodo will walk away into the sunset, in search of the future version of him, Frodo 3.0 - Fighting in the conquest of his arch nemesis, Apple Conner.

Quiksmage said:
one does not simply walk into Mordor.
Click to expand...
Click to collapse
Dammit Bilbo, you beat me to punch

Can I get frodo as well?will this give me wifis?
Sent from my HTC Evo using Tapatalk.

Update to HTC EVO 4G failed

All,
I got a notification of update this morning (June 29, 2011) on my HTC EVO 4G (rooted/with netarchy toast mod) but when I tried to apply the update I get:
assert failed: apply_patch_check ("/system/lib/modules/bcm4329.ko". "78fE:unknown command [c535f323ef3a5c8304b32f514c23ea458132b".]
E:unknown command [9"0]
E: Error in /cache/OTA-Supersonic_4.24.651.1-3.70.651.1_release404yzkft23eop520.zip (Status 7)
Installation aborted.
Android system recover is open and the prompts are:
- Reboot system now
- USB-MS toggle
- Backup/Restore
- Flash zip from sdcard
- Wipe
- Partition sdcard
- Mounts
- Other
- Power off
What do I do next? How do I get this update? Thanks!

guidecca said:
All,
I got a notification of update this morning (June 29, 2011) on my HTC EVO 4G (rooted/with netarchy toast mod) but when I tried to apply the update I get:
assert failed: apply_patch_check ("/system/lib/modules/bcm4329.ko". "78fE:unknown command [c535f323ef3a5c8304b32f514c23ea458132b".]
E:unknown command [9"0]
E: Error in /cache/OTA-Supersonic_4.24.651.1-3.70.651.1_release404yzkft23eop520.zip (Status 7)
Installation aborted.
Android system recover is open and the prompts are:
- Reboot system now
- USB-MS toggle
- Backup/Restore
- Flash zip from sdcard
- Wipe
- Partition sdcard
- Mounts
- Other
- Power off
What do I do next? How do I get this update? Thanks!
Click to expand...
Click to collapse
Anyone, anyone? Don't everyone rush down. There's room for everyone.

Is your recovery old (ie not Clockworkmod 3)
Have you tried to backup your apps with titanium and just starting all over with a new updated full rom?
Have you edited the filesystem to cause the update to say this? If you edit any of the filesystem, the update fails.
You need to download a new rom and just start all over it seems.
How are we to figure things out if you dont give any background?

Try unrooting and put a stock rom and then do an update. Hope that helps
Sent from my HTC EVO phone, shouldn't we all have one?

If you want to keep root, then you never take the update. Otherwise you will most likely lose root, and will have to wait until a Dev finds an exploit to reroot. If you want to just update the radio(s) then there are flashable updates in the Dev section that you can flash.

I Think I Did/Didn't
mattrb said:
Is your recovery old (ie not Clockworkmod 3)
Have you tried to backup your apps with titanium and just starting all over with a new updated full rom?
Have you edited the filesystem to cause the update to say this? If you edit any of the filesystem, the update fails.
You need to download a new rom and just start all over it seems.
How are we to figure things out if you dont give any background?
Click to expand...
Click to collapse
Not sure what clockworkmod I have. I could backup app with titanium and which "full rom" would you recommend? I have netarchy-toastmod-4.3.4-cfs-havs-less-nosbc-uni installed and in zip format. I rooted the phone and applied the toastmod so I modified the stock HTC EVO 4G file system. The next comment suggests unrooting the phone and starting over. Why so much work for a "smart" phone? Any specifics would be appreciated on how to proceed.

kf2m said:
If you want to keep root, then you never take the update. Otherwise you will most likely lose root, and will have to wait until a Dev finds an exploit to reroot. If you want to just update the radio(s) then there are flashable updates in the Dev section that you can flash.
Click to expand...
Click to collapse
Seems to be a rule never to take an update of the original after modifying any gadget. Maybe my rooted phone is better off/more advanced without the update but I haven't found anyone that has said it yet. Since the update failed I think I have root but I will check it. My wife's unrooted phone took the update easily.

guidecca said:
Seems to be a rule never to take an update of the original after modifying any gadget. Maybe my rooted phone is better off/more advanced without the update but I haven't found anyone that has said it yet. Since the update failed I think I have root but I will check it.
Click to expand...
Click to collapse
That is why you should read, read, read a little more and when you feel comfortable with doing something to your phone, stop and keep reading. This is posted over and over and over again in this forum. Never, ever take the OTA update. As soon as the update was available, Haux had the rooted version ready to be flashed within hours.

If you would like to keep the stock rom but update to the newest release you can download Rom Manager from the market and flash the newest stock rom. Quite easy and only takes a few clicks. Next time you see an update from sprint, just wait until Rom Manager gets a rooted rom of that release and go nuts. If you don't feel like dealing with Rom Manager you can manually flash the roms you find in this forum. Hope this helps.

This has worked rather well for me for the past few updates, including the most recent one:
forum.androidcentral.com/htc-evo-4g-rooting-roms-hacks/90582-guide-updating-rooted-gingerbread-without-flashing-new-rom-wiping-your-phone.html
Also, the error you see is likely due to you changing the Broadcom file in that location to enable Wifi-N speeds on your EVO. Is that something you remember doing? When installing updates, it needs the original unchanged version of "\system" files to be there to verify against, including this one.
I just went through the process, and got the same error before I remembered to change bcm4329.ko back to the original. Also, don't forget to unfreeze any bloatware if it is frozen, or it won't proceed past the verification process (as it changes "\system" files. Additionally, clearing the Davlik cache is always a good idea when updating.

I forgot to mention- If I remember correctly, the instructions are elaborated on in post #44 of that page.

tgruendler said:
That is why you should read, read, read a little more and when you feel comfortable with doing something to your phone, stop and keep reading. This is posted over and over and over again in this forum. Never, ever take the OTA update. As soon as the update was available, Haux had the rooted version ready to be flashed within hours.
Click to expand...
Click to collapse
You say a rooted version was ready to be flashed within hours.
This is what I read on Android Forums:
There is no exploit yet to allow unrevoked to root the new hboot(2.16). They will find it but how long is unknown.
You can apply the update by flashing the rooted rom and the updated radios found here: [ROM][STOCK] 4.24.651.1 - Odexed & De-Odexed - xda-developers and here: [ Radios ][ 6-3 ] All EVO Radio, WiMAX, PRI, NV & HBoot versions - xda-developers
The only thing that would not happen by flashing those it that your hboot would not be upgraded which you don't want anyway so that you can retain root.
If Haux has an exploit would it work on netachy toastmod rooted EVO 4G?

guidecca said:
You say a rooted version was ready to be flashed within hours.
This is what I read on Android Forums:
There is no exploit yet to allow unrevoked to root the new hboot(2.16). They will find it but how long is unknown.
You can apply the update by flashing the rooted rom and the updated radios found here: [ROM][STOCK] 4.24.651.1 - Odexed & De-Odexed - xda-developers and here: [ Radios ][ 6-3 ] All EVO Radio, WiMAX, PRI, NV & HBoot versions - xda-developers
The only thing that would not happen by flashing those it that your hboot would not be upgraded which you don't want anyway so that you can retain root.
If Haux has an exploit would it work on netachy toastmod rooted EVO 4G?
Click to expand...
Click to collapse
To be technical because I am a jerk, Hehe, you don't root the hboot. You unlock it via making it s off. You root the Rom by applying super user privileges from within. Hboot s off means you can easily flash different recovety images, radios, and any ruu considering you have supported radios. Tomatoes tomahtoes.
Sent from my PC36100 using XDA Premium App

Thanks
That is why you should read, read, read a little more and when you feel comfortable with doing something to your phone, stop and keep reading. This is posted over and over and over again in this forum. Never, ever take the OTA update. As soon as the update was available, Haux had the rooted version ready to be flashed within hours.
I just thought that maybe there was an exploit for gingerbread 2.3 (OTA) that someone had found within hours of Google's release. I wanted to definitely make sure there was or wasn't a way to update my phone. Thanks for your clarification on hboot, etc. Mattlock over on Android Forums has a good guide for rooting and he is good at step-by-step 'how to do it' and some explanation why for us newbies. My rooted phone works fine but my wife's stock phone with the update seems to get a lot of network failures. She has a lot apps and a stock SD card - she refuses to let me root her phone - superstitious kind.

[GUIDE] Everything Explained.

Before you go ahead and start unlocking, flashing and rooting, there are things you should know. This thread is a general guide that will serve to explain most of those things.​
.oOo.oOo.oOo.oOo.oOo.oOo.oOo.oOo.oOo.oOo.oOo.oOo.oOo.oOo.oOo.​
Table of Contents
A. The layers (Hardware, Firmware, Software)
B. Definitions
C. Troubleshooting Common Issues
.oOo.oOo.oOo.oOo.oOo.oOo.oOo.oOo.oOo.oOo.oOo.oOo.oOo.oOo.oOo.​
The Layers. How does everything come together?
Just like any other computing device there are 3 Layers to your phone. It helps to realize this prior to modifying your phone, so you are able to troubleshoot issues more effectively.
Layer 1 Hardware: The hardware layer is the physical components of your phone. That which you can touch, hold and see. This layer is the least likely to be modified unless you are a crazy super master level modder. Very few bother to mess with this layer so this layer tends to be the most stable with very little issues arising. The best way to make sure a problem is not related to the hardware layer, that is to say, a physical hardware problem where a physical component needs replacing, is to return all software and firmware to stock. This is typically done by running an RUU or manually reflashing stock firmware and software. There are instances where software or firmware modifications can affect the hardware. For example, if you overclock your CPU, the added heat could permanently damage the CPU and even other hardware components so be sure to take that into consideration.
Layer 2 Firmware: This layer is what allows the software to control the hardware in your phone, like a bridge between the two. There is firmware for just about every component of your phone, the camera, screen, radio, processor etc etc. This is the second least likely layer to be modified. S-Off is required to modify most, but not all, firmware files and rightfully so. Modifying firmware components can easily damage your phone if you do not understand what you're doing. In some cases a JTAGG repair can fix your phone from firmware modification damage, other times, only replacing physical components can repair the damage done. (Recovery and the kernel are technically part of the firmware layer but do not require S-Off to flash)
Layer 3 Software: The software layer consists of the "ROM" and applications on your phone. This is where most of the modification takes place and while modifying the software layer is the least likely to cause serious issues, it can still be dangerous. Flashing a ROM not intended for your device could easily put your phone into a bricked state. With SuperUser or Root access, software is capable of modifying the firmware layer of your device. It is up to you to decide what is safe and what's not safe. This is why rooting is not for everyone. How can you properly decide what is safe for your device without the proper knowledge?
Definitions
What is root?
Root, super user or su for short is a level of access giving you permission to read or write to folders, or partitions you could not have access to as a regular user. Think administrative access.
Consider a folder path “/sdcard/downloads/” If we break it down, “downloads” is a folder in “sdcard” and “sdcard” is one of the folders in “/” which is the “root” of the folder structure. As a regular user, one might not consider that folders other than sdcard exist in “/” as they are kind of hidden from us but rest assure they are there and this is typically where the android OS and firmware files are kept. Modifying these files can be extremely dangerous for your phone if you do not understand the modifications to the file you're making, and what steps you can take to recover from any issues you encounter.
What is an RUU?
RUU stands for ROM Update Utility. An RUU is used to reflash an existing firmware/software set or updated firmware/software set. An RUU will wipe everything and basically get your phone back to stock. Unless your phone is S-Off, you cannot run an RUU with an older firmware or software than those currently on your device. You can only run an RUU that matches your MID/CID unless you are S-Off and have SuperCID or have changed the MID/CID to match the carrier you are flashing. There may be differences in hardware/firmware between MIDs and CIDs so be mindful as this can lead to a brick. To properly run an RUU with S-On, you must also have stock recovery installed, the bootloader must be locked/relocked. BE VERY CAREFUL DOING THIS. It is not recommended to RUU or OTA after unlocking your bootloader unless you have to. If you are S-OFF you can RUU whether the bootloader is locked or not and if you are superCID, CID checks will be ignored so be sure to be mindful of the RUU you are running and that it will play nice with your phone.
What is an OTA?
OTA stands for Over The Air and implies an Over the air update distributed by your phone manufacturer, carrier or ROM developer. Unlike an RUU, an OTA will not typically wipe/factory reset your phone but can update your firmware and/or software set. To a apply a manufacturer/carrier released OTA you will need stock recovery and stock system apps installed. Your CID/MID must match that of the carrier/manufacturer your phone came from.
What is a ROM?
When the term ROM was first introduced it stood for Read Only Memory, however, most memory that claims to be Read Only nowadays is not like it was back then. Now a days it is not as complicated to write ROM as only permissions are in your way as opposed to the days when you were required to modify the hardware layer in some way to update the ROM chip. In this particular case, we are referring to the android software on your phone. Stock ROM would imply the manufacturer released ROM that came on your device when you purchased it. Custom ROMs are ROMs the are modified stock ROMs or ROMs built from android source code to. I think you get the idea. It's the device software or Operating System if you will. You should never flash a ROM that is not intended for the device you are flashing it to, this is very dangerous. Like, brick dangerous.
What is a nandroid backup?
A nandroid backup is a backup of your phone's current state. Like a snapshot or image of your phone's software. It includes the ROM currently flashed to your phone, the kernel, apps and settings. It does not include any firmware files other than the kernel and possibly the recovery. A nandroid is done with custom recovery and cannot be done with stock recovery. Taking a nandroid before you start messing with your phone is good practice. In fact, It's good practice to make nandroids before flashing a new ROM, or making any changes that may impact stability. This will ensure you always have a quick way to get back to having a usable phone. Obviously, a nandroid will not help in cases where you mess up firmware files like the radio firmware or hboot.
What is a kernel?
The kernel is the central point of an operating system. It contains the modules and settings necessary for the ROM or OS to work properly. Every Operating System has a kernel, including android. Just like ROMs there are custom kernels, with tweaks and the like that may improve or decrease performance/stability. Also, like ROMs, you should never flash a kernel not intended for your device. Very Dangerous!
What is a bootloader?
The bootloader is as the name implies, a device software/interface for handling boot operations it is contained within the hboot file. The bootloader screen has a few nifty features:
Gives you device information such as:
The bootloader state (locked, relocked or unlocked)
The Secureflag state (S-On or S-Off)
Your hboot and radio versions
Your Cid (only if you changed it)
Allows you to power down, reboot or boot your phone to android.
Allows you to factory reset your phone (Though should never really be used unless you are completely stock as you can properly factory reset in custom recovery)
Allows you access to the recovery
It gives you access to fastboot command operations you can send from your PC to your phone.
To boot to bootloader: Press and hold Power and volume up until the phone shuts off, then let go of power and volume up. Press and hold Volume down until your screen comes up in bootloader mode.
What is recovery?
Recovery is a software/User Interface that allows you to handle and make changes to your device, without having to boot the android OS. The stock M8 comes with a recovery that is quite limited but allows you to factory reset your phone and flash OTA updates which really is more than enough for the average user.
Those of us who want more from our phones, and modify them tend to flash custom recoveries with many extra features. I won't go into all the features they provide as the devs have websites, and you can visit them for more information. The two custom recoveries for the m8 include TWRP and Philz Touch. Both are very functional and choosing one is a matter of preference over anything else.
To flash a recovery image. Put the recovery image in your fastboot/adb folder and in the command prompt:
Code:
fastboot flash recovery recoveryfilename.img
You can find The latest:
TWRP for the M8 HERE
Philz Touch for the M8 HERE
To manually boot to recovery, boot to bootloader (Press and hold Power and volume up until the phone shuts off, then let go of power and volume up. Press and hold Volume down until your screen comes up in bootloader mode). Then select recovery in the bootloader menu.
What is S-Off/S-On?
This stands for Securewrite-on or Securewrite-Off. The name kind of gives some hints as to what it means. Having your bootloader unlocked, affords you the ability to to flash a custom recovery and custom roms as well as a custom kernel however, some people may need more. They may want to alter other system partitions. That is where S-Off comes in. It gives you full write access to all system partitons. It also forces a bypass for all security checks, such as those made by OTAs and RUUs, for CID and MID. S-Off is persistent. No matter if you RUU, OTA, Flash a ROM, Firmware, Factory Reset, S-Off will remain so until you use fastboot to reset the flag. I should say, if you don't know what you're doing, that is to say, if you are the type to follow instructions blindly on a thread, without much idea what is ACTUALLY Happening, what files you're modifying, you should not have S-Off. It should not concern you and that is that. S-Off can be dangerous. You have been warned.
What does a Factory Reset do?
A Factory Reset Clears the Cache, Dalvik Cache and Data Partitions. All settings will reset to default. User Apps (Apps you installed that did not com preinstalled with the ROM) will be removed. This will not restore your phone to when you purchased it. This will not relock your bootloader, Reset the S-Off flag, remove root, or downgrade your hboot. It merely affects the system and user settings and user apps.
What is fastboot?
Fastboot is a command line tool that allows you to manipulate certain parts of your phone from the bootloader. Your phone must be in fastboot mode and you must have the fastboot application and HTC drivers installed if you are on Windows. If you are on linux, the HTC driver is preinstalled.
Popular fastboot commands include:
Fatsboot devices (Lists devices connected for use with fastboot)
Fastboot flash recovery recovery.img (Flashes a recovery image)
Fastboot flash boot boot.img (Flashes a boot image)
Fastboot oem readcid (Shows the CID of the phone installed)
Fastboot oem writecid (Writes a new CID to your phone. Must be 8 Characters. Requires S-Off)
Fastboot oem rebootRUU (Puts the phone in RUU mode which is used for flashing firmwares and/or entire RUUs)
Fastboot reboot (Reboots your phone)
Fastboot reboot-bootloader (Reboots to bootloader)
Fastboot erase cache (Wipes the cache partition using fastboot. Good idea after flashing things via fastboot)
Fastboot help (Will list fastboot commands)
Fastboot boot imagefilename.img (Allows you to boot a recovery image or kernel image without actually flashing to your phone
allowing you one time access to the features without the headache of reflashing stock afterwards) Thanks to @garyd9 for suggesting I include this. Very convenient command.
What is ADB?
ADB is another command line tool used to manipulate your phone. The commands for ADB are way more extensive. ADB can only communicate with your phone while in a custom recovery or while the ROM is booted up with USB debugging turned on. The reason ADB is so much more extensive is because it allows you to remotely access your phone's terminal just like a linux terminal. You can use ADB to push or pull files to and from any partition (Some partitions will require S-Off), list devices, get a logcat, troubleshoot issues etc etc. For an extensive list of commands and how to use ADB I strongly suggest visiting http://developer.android.com/tools/help/adb.html
What is the CID?
CID stands for carrier ID. It's a string of letters and numbers, eight characters long that identify what carrier your phone is from. When you flash an OTA or RUU, The OTA or RUU checks for a few things, one of those things is the CID, to ensure you are flashing software intended for your device. Realistically, There's no hardware difference between the M8s (with the exception of CDMA vs GSM) so all firmwares/softwares should be compatible. With regards to radio firmware, your radio may function better with one firmware over another. There have been occasions with HTC where flashing an RUU or OTA with the wrong CID or SuperCID, while S-On would brick your phone. So try to be mindful of this and be careful.
Thanks to @garyd9 for suggesting I include this in my guide!
Some common CIDs include but are not limited to:
SuperCID: 11111111
HTC International: HTC__001
AT&T: CWS__001
ROGERS: ROGER001
VODAPHONE: VODAP001
T MOBILE: T-MOB010
TELESTRA: TELST001
Bell Canada: BM___001
What is a brick?
The term brick is sometimes thrown around a bit too casually. A brick is when your phone is no longer operable. It does not boot, there is no way to save it without resorting to Jtagg or replacing the nand chip or motherboard. If your phone powers on and something appears on your screen, your phone can almost always be saved. Be sure you know how to save your device before messing with your device.
Troubleshooting Common Issues
I flashed a ROM or Kernel and it's not booting! WHAT DO I DO!?
When this happens. There are actually a number of things to consider but first off, Hopefully you made a nandroid to restore from just in case the reason it doesn't boot is something not quickly or easily fixed.
1. Is the ROM you're flashing indeed intended for your device? ROMs you're flashing should be for the HTC One m8 International. You should not be flashing ROMs designed for the m8 Sprint or Verizon and should not be flashing ROMs designed for other models of phone. If the ROM you flashed is not for your device, best case scenario, it's not flashing properly. Worst case scenario, you have a brick. You will need to factory reset and wipe system then either flash a new ROM or restore a nandroid to get your phone up and running again.
2. Did you wipe Cache, Dalvik Cache, Data and System? (Don't wipe System for Kernel Install)
A factory reset will wipe all but system. You should wipe System manually in case the script for the ROM install does not do it or does it improperly. A factory reset is enough for a Kernel install. If you wiped system and just flashed a kernel, it's no doubt your phone is not booting.
* If you did not factory reset and wipe system, do so and then reflash your rom. It should then boot.
* If you wiped system to flash a kernel, you will need to reflash the rom, and then reflash your kernel again if you are flashing a custom kernel. (Note a GPE Kernel will not work on Sense and a Sense kernel will not work on GPE.
3. Did you matchup the Checksum? MD5 or SHA1 are usually posted on the ROM Download site/post. This allows you to check and make sure the integrity of the file you downloaded has been maintained. If The SHA1 or MD5 of the file you downloaded does not match what is posted, you have a corrupted file and should redownload. If you don't have a MD5 or SHA1 Checker, I suggest downloading one. Google MD5 or SHA1 Checker and you should find one. MD5 is most commonly used but it's up to the Dev as to which they post. Sometimes both. You only need to match one. (Linux comes with utilities for checking MD5/SHA1 called md5sum and/or sha1sum)
4. If you tried all these steps and it's still not booting, try another ROM. If no ROMs appear to be booting, you may be having an issue with your custom recovery. Redownload your recovery (Make sure it's the right one for your phone and check the checksum) Then reflash recovery, then use fastboot erase cache, boot to recovery and try flashing again.
5. If you tried all these and you're having issues, ask in the M8 Q&A!
I wiped everything and I don't have a ROM on my phone to flash! What do I do?
This is quite simple really.
Boot to recovery
Connect your phone to your PC
Make sure your ROM is on your PC and in your adb folder
Then use:
Code:
adb push romfilename.zip /sdcard/
Be patient, this could take a while, when it finishes you will get a confirmation with bytes in/bytes out.
Then flash.
Where can I go to find links to do all this cool stuff I want to do to my Phone!?!?!?!?
HERE!
Thank Yous!
Thanks to @garyd9
Thanks to @keithross39
This is a work in progress. I will be updating this as often as I can, trying to explain as much as I can for newer M8 owners who are not used to HTC or Android devices. If you have any suggestions for what I can put here, post here and let me know! Also, I'm not perfect, I make mistakes if I have/do make any, do not be shy! Let me know.
[08/18/2014] Partially updated and fixed spelling mistakes. More coming soon!

Hey fella, this is a good idea.
Thanks for taking the time to do this.
I am going to be getting the M8 in the near future, so reading up about the HTC specific stuff is really useful for me as I'm currently familiar with Samsung procedures and not a lot else. Most folks reading this should be familiar with the 'cross platform basics', so what you've covered so far should be enough........
But.....
Those (like me) who are getting an HTC device for the first time would probably benefit from more of a detailed description of the HTC side of things......maybe you could concentrate on expanding that information.......
Maybe you could include links to threads for s-off, rooting and/or anything else relevant?
Just my 2 cents worth....for what it's worth.....
Sent from my rooted debloated thingy

keithross39 said:
Hey fella, this is a good idea.
Thanks for taking the time to do this.
I am going to be getting the M8 in the near future, so reading up about the HTC specific stuff is really useful for me as I'm currently familiar with Samsung procedures and not a lot else. Most folks reading this should be familiar with the 'cross platform basics', so what you've covered so far should be enough........
But.....
Those (like me) who are getting an HTC device for the first time would probably benefit from more of a detailed description of the HTC side of things......maybe you could concentrate on expanding that information.......
Maybe you could include links to threads for s-off, rooting and/or anything else relevant?
Just my 2 cents worth....for what it's worth.....
Sent from my rooted debloated thingy
Click to expand...
Click to collapse
Thanks man! I welcome all suggestions! I will do my best to incorporate your suggestions
Sent from my HTC One_M8 using XDA Free mobile app

Great idea, thanks. I've been wondering what S-Off is for weeks but didn't want the flaming for asking a noob question!
Sent from my HTC One_M8 using XDA Premium 4 mobile app

Some possible additions:
What is "RUU"?
What is MID (model ID) along with a list of some common MID's
What is CID (carrier ID?) along with a list of some common CID's
How do the MID and CID relate to each other and how does the combination relate and/or interact with RUU. Related, of course, is the third part of the version number.

I was thinking of writing a guide myself, because I was so confused myself after coming from samsung, really nice.

Shebee said:
I was thinking of writing a guide myself, because I was so confused myself after coming from samsung, really nice.
Click to expand...
Click to collapse
Lol...ain't that the truth....
Sent from my rooted debloated thingy

Nice one

Very well done!
Sent from my HTC One_M8 using Tapatalk

I'm one of those who also came from Samsung (S4).
This is really great and easy to understand. This should be sticky :victory:

While I think the OP uses the term "ROM" incorrectly (Read Only Memory), I'll admit that's just me being picky. Otherwise, a very useful post... I've requested it be made sticky.
Take care
Gary

garyd9 said:
While I think the OP uses the term "ROM" incorrectly (Read Only Memory), I'll admit that's just me being picky. Otherwise, a very useful post... I've requested it be made sticky.
Take care
Gary
Click to expand...
Click to collapse
That's not being picky at all! Feel free to suggest any corrections. I welcome criticism and corrections.
Thanks for the recommendation!
Sent from my HTC One_M8 using XDA Free mobile app

exad said:
That's not being picky at all! Feel free to suggest any corrections. I welcome criticism and corrections.
Click to expand...
Click to collapse
LOL. I'm one of those people who goes nuts when people want to install "ROM's" on their phone. I keep reminding them that if it was really "Read Only Memory", that they wouldn't be able to overwrite it. Ever.
I do understand, however, that it's one of the misused terms these days. I guess it's kind of like saying you are "dialing a phone number." (There aren't any dials on our phones anymore. I haven't even seen a working rotary dial phone in years...)
Anyway - I'll stop with my OT bantering. Once I get more familiar with HTC devices I'll probably have some good suggestions for your posts.
Take care
Gary

garyd9 said:
LOL. I'm one of those people who goes nuts when people want to install "ROM's" on their phone. I keep reminding them that if it was really "Read Only Memory", that they wouldn't be able to overwrite it. Ever.
I do understand, however, that it's one of the misused terms these days. I guess it's kind of like saying you are "dialing a phone number." (There aren't any dials on our phones anymore. I haven't even seen a working rotary dial phone in years...)
Anyway - I'll stop with my OT bantering. Once I get more familiar with HTC devices I'll probably have some good suggestions for your posts.
Take care
Gary
Click to expand...
Click to collapse
Read only memory isn't a great name for it. If you've ever updated the bios on a pc, flashed a firmware update to a router, etc... you've written to read only memory. There are types that are truly read only but I can't think of a single practical example. And welcome to htc phones!
Sent from my HTC One_M8 using Tapatalk

lampel said:
Read only memory isn't a great name for it. If you've ever updated the bios on a pc, flashed a firmware update to a router, etc... you've written to read only memory. There are types that are truly read only but I can't think of a single practical example. And welcome to htc phones!
Click to expand...
Click to collapse
I'm old enough to remember (clearly) when you couldn't update the BIOS on a PC - you had to physically replace the BIOS chip. (Usually, they were socketed to make replacement a bit easier.) That was ROM. Also, early game consoles used true ROM in cartridges.
As for current practical example: a simple CDROM (not CD/RW) is, of course, read only.

I agree that it's not the best name lol but that is what it stands for....
Sent from my HTC One_M8 using XDA Free mobile app

Added this to my index thread

Hi guys! I am planning to buy an htc one m8 but can someone please tell me the different models out there? I don't want to end up buying the wrong one. Also is the dev one worth spending the extra money over the international? And is it the same model as the international one? Thanks in advance. I didn't know where else to post this. I didn't wanted to start a new thread.

Karan and all other users, please post questions in Q&A. Only things that should be posted here are suggested additions to this thread.
Also thread has been updated and more to come!

Part on RUUs is wrong...
An RUU can be run at any point and in any state (so long as you can get to the bootloader) as it completely replaces the entire system so doesn't matter if you don't have the stock recovery as it replaces it during the update process. Also, if you're S-OFF it means you can flash any RUU for any phone, handy to go between branded and unbranded software. OK, there's a risk of trying to flash an RUU from another device but if you do that you're a bit dumb!!