Related
I have been checking the massive froyo thread since it was on page 7 (now its > 120 pages) but still no love for AT&T/Rogers Nexus one.
My phone is unrooted and running stock rom with Firmware on 2.1-update1 and build EPE54B. Can people who have froyo on their at&t nexus one please post a step by step guide?
Should be the same method and file as that used for the T-mobile compatible phones.
id really like this answered too..i dont want to take a risk and brick my N1.. so far all the guides are ERE27..
The update zip as it stands is only for ERE27-FroYo... sorry.
unleashed12 said:
id really like this answered too..i dont want to take a risk and brick my N1.. so far all the guides are ERE27..
Click to expand...
Click to collapse
pjcforpres said:
The update zip as it stands is only for ERE27-FroYo... sorry.
Click to expand...
Click to collapse
That makes no sense.
The guides are ERE27 only because that's the latest Eclair update. You need 2.1 update 1 to be able to jump to Froyo. You guys have the AT&T/Rogers version, which has a newer radio than those of us with the T-mobile compatible versions. If you're on the AT&T version, you already have the most recent update and can simply flash the file everyone's talking about. If it weren't compatible for some reason, the file would not flash and simply give you an error message. So there's no risk here.
I saw many at&t owners have froyo successfully flashed. They flashed to ERE27 first. Does that need rooting?
Thank you for this information.
uansari1 said:
That makes no sense.
The guides are ERE27 only because that's the latest Eclair update. You need 2.1 update 1 to be able to jump to Froyo. You guys have the AT&T/Rogers version, which has a newer radio than those of us with the T-mobile compatible versions. If you're on the AT&T version, you already have the most recent update and can simply flash the file everyone's talking about. If it weren't compatible for some reason, the file would not flash and simply give you an error message. So there's no risk here.
Click to expand...
Click to collapse
Anyone tried this?
uansari1 said:
That makes no sense.
The guides are ERE27 only because that's the latest Eclair update. You need 2.1 update 1 to be able to jump to Froyo. You guys have the AT&T/Rogers version, which has a newer radio than those of us with the T-mobile compatible versions. If you're on the AT&T version, you already have the most recent update and can simply flash the file everyone's talking about. If it weren't compatible for some reason, the file would not flash and simply give you an error message. So there's no risk here.
Click to expand...
Click to collapse
the update file is labeled signed-passion-FRF50-from-ERE27.1e519a24.zip
ATT/Rogers version is running build EPE54B. The update is from ERE27 to FRF50
uansari1 said:
That makes no sense.
The guides are ERE27 only because that's the latest Eclair update. You need 2.1 update 1 to be able to jump to Froyo. You guys have the AT&T/Rogers version, which has a newer radio than those of us with the T-mobile compatible versions. If you're on the AT&T version, you already have the most recent update and can simply flash the file everyone's talking about. If it weren't compatible for some reason, the file would not flash and simply give you an error message. So there's no risk here.
Click to expand...
Click to collapse
I guess the 20 pages of 100% stock AT&T guys not being able to flash this are just morons then.
The update zip only lets you go from ERE27 to FroYo. Those with an "AT&T version" and FroYo had to flash ERE27 first... that also means unlocking the boot loader.
Yup, AT&T/Rogers folks are going to have to wait unless they want to unlock their bootloader, flash to the 27 build and then update to FroYo.
At this point there's no point to unlock the bootloader if you've waited this long already. Keep your warranty and wait a little longer, I'm sure an update for the Rogers build will surface soon.
pjcforpres said:
I guess the 20 pages of 100% stock AT&T guys not being able to flash this are just morons then.
The update zip only lets you go from ERE27 to FroYo. Those with an "AT&T version" and FroYo had to flash ERE27 first... that also means unlocking the boot loader.
Click to expand...
Click to collapse
jasrups said:
Yup, AT&T/Rogers folks are going to have to wait unless they want to unlock their bootloader, flash to the 27 build and then update to FroYo.
At this point there's no point to unlock the bootloader if you've waited this long already. Keep your warranty and wait a little longer, I'm sure an update for the Rogers build will surface soon.
Click to expand...
Click to collapse
That sucks.
Same problem with the european stock shipping ROM (EPF21B).
Can't wait to be able to get Froyo without unlocking.
my bootloader is unlocked..going to go ahead and try to flash pauls rooted version.
jasrups said:
Yup, AT&T/Rogers folks are going to have to wait unless they want to unlock their bootloader, flash to the 27 build and then update to FroYo.
At this point there's no point to unlock the bootloader if you've waited this long already. Keep your warranty and wait a little longer, I'm sure an update for the Rogers build will surface soon.
Click to expand...
Click to collapse
What a bummer! Yeah I have waited this long to preserve my phone's virgini.. I mean warranty so I guess I'll wait longer.
At least its good to know that the build for at&t and rogers is the same!
I have the AT&T N1, and earlier today I flashed and formatted my phone back to new. I now have Froyo and it's working fine.
Kpow said:
I have the AT&T N1, and earlier today I flashed and formatted my phone back to new. I now have Froyo and it's working fine.
Click to expand...
Click to collapse
is your N1 rooted or stock?
MEGABYTEPR said:
is your N1 rooted or stock?
Click to expand...
Click to collapse
Clearly rooted and unlocked bootloader, otherwise he wouldn't have been flashing anything.
thread title misled me.
eric b
I have successfully flashed Froyo on my (AT&T) N1 with this:
http://android.modaco.com/content/g...com/309286/frf50-froyo-pre-rooted-update-zip/
I previously was on CM 5.0.6 with Amon RA Recovery v1.7.0.
I wiped and installed the update, it did flash a new radio. Rebooted and Froyo was waiting for me!
Hope this helps anyone that is not sure.
Hi there,
I'm trying to update my s-off, rooted IS to 2.3. There's an OTA update available which I understand won't work (and doesn't).
Is the best option to flash the stock ROM (hopefully my terminology is accurate) and then run the OTA update? Where can I get the stock files from?
Finally, is there a way to backup/restore my SMS history, contacts, etc. once I update?
I have clockworkmod installed.
Thanks to everyone in advance for helping someone without a clue!
greatbigbrain said:
Hi there,
I'm trying to update my s-off, rooted IS to 2.3. There's an OTA update available which I understand won't work (and doesn't).
Is the best option to flash the stock ROM (hopefully my terminology is accurate) and then run the OTA update? Where can I get the stock files from?
Finally, is there a way to backup/restore my SMS history, contacts, etc. once I update?
I have clockworkmod installed.
Thanks to everyone in advance for helping someone without a clue!
Click to expand...
Click to collapse
If you are S-OFF and rooted, then just install a rooted GB ROM. Why take a chance and mess with a carrier OTA?
http://forum.xda-developers.com/showthread.php?t=1168796
This is a rooted version of the latest WWE GB ROM for the IncS. It is an unbranded ROM and doesn't have any carrier bloatware, just the standard HTC apps.
tpbklake said:
If you are S-OFF and rooted, then just install a rooted GB ROM. Why take a chance and mess with a carrier OTA?
http://forum.xda-developers.com/showthread.php?t=1168796
This is a rooted version of the latest WWE GB ROM for the IncS. It is an unbranded ROM and doesn't have any carrier bloatware, just the standard HTC apps.
Click to expand...
Click to collapse
Thanks! Can I just go ahead and install, or do I need to wipe stuff first?
Will I then need to flash a new radio - and if so... how?
Thanks again.
If you already have gingerbread 2.3 than why on earth would you want to go back and download 2.3 again? Not understanding. And no I dont think you will need to flash a new radio going on the basis that you already have a gingerbread radio right now!!??!!
greatbigbrain said:
Thanks! Can I just go ahead and install, or do I need to wipe stuff first?
Will I then need to flash a new radio - and if so... how?
Thanks again.
Click to expand...
Click to collapse
I just flashed this over my Froyo 2.2 install and it kept all of my apps and settings in tact. Yes you will also need to upgrade your radio and flash a GB radio, too. There is a thread in the Developers section about upgrading your radio.
IncredibleSlover said:
If you already have gingerbread 2.3 than why on earth would you want to go back and download 2.3 again? Not understanding. And no I dont think you will need to flash a new radio going on the basis that you already have a gingerbread radio right now!!??!!
Click to expand...
Click to collapse
You misunderstood the OP. He has a S-OFF and rooted IncS and wants to upgrade to 2.3. No where did he say he already had 2.3.
tpbklake said:
You misunderstood the OP. He has a S-OFF and rooted IncS and wants to upgrade to 2.3. No where did he say he already had 2.3.
Click to expand...
Click to collapse
Yeah lol...I guess I read it wrong
tpbklake said:
If you are S-OFF and rooted, then just install a rooted GB ROM. Why take a chance and mess with a carrier OTA?
http://forum.xda-developers.com/showthread.php?t=1168796
This is a rooted version of the latest WWE GB ROM for the IncS. It is an unbranded ROM and doesn't have any carrier bloatware, just the standard HTC apps.
Click to expand...
Click to collapse
Final question (hopefully) - what radio should I use with this ROM?
greatbigbrain said:
Final question (hopefully) - what radio should I use with this ROM?
Click to expand...
Click to collapse
Either one of these will be fine.
From the 2.21.1400.8 RUU:
20.2808.30.085AU_3805.06.03.03
md5: f727a2dae56fd64eeef525ebf64858f7
From the 2.30.405.1 RUU:
has the same radio as the 2.21.1400.8 RUU
From the 2.32.1010.1 RUU:
20.2810.30.085AU_3805.06.03.16
md5: c8c0be410c97e9bf82cdad54d4da0ef4
Taken from this thread:
http://forum.xda-developers.com/showthread.php?t=1129014
So this morning there was a thread on androidcentral that the official ICS upgrade for the vivid was being pushed out. I got the OTA update, 3.26.502.56, and copied it to my sdcard......but I have no idea what to do with it. If this is not different from the leak floating around feel free to delete this thread
Where did it save it to cause I got it and want to save it before I upgrade.
Sent from my HTC PH39100 using XDA
jsramirez27 said:
So this morning there was a thread on androidcentral that the official ICS upgrade for the vivid was being pushed out. I got the OTA update and copied it to my sdcard......but I have no idea what to do with it.
Click to expand...
Click to collapse
Yeah, maybe try reading or searching. This topic belongs in General, blah blah blah.
Anyway, there's a thread with instructions, but since I'm operating under the presumption that you're not going to follow it, download this RUU, run it, and follow the directions it gives you.
Link.
I doubt you've unlocked your bootloader either, by the sound of it, so I'm not going to tell you to "fastboot oem lock".
I am rooted and unlocked. I know how to perform the update but I copied it to my sdcard so that it could be used for dev purposes. FYI i tried to perform the update and it gave me an error, probly because I am rooted and unlocked
tbone22 said:
Where did it save it to cause I got it and want to save it before I upgrade.
Sent from my HTC PH39100 using XDA
Click to expand...
Click to collapse
In downloads, I just copied and pasted using a file manager
jsramirez27 said:
I am rooted and unlocked. I know how to perform the update but I copied it to my sdcard so that it could be used for dev purposes. FYI i tried to perform the update and it gave me an error, probly because I am rooted and unlocked
Click to expand...
Click to collapse
I have absolutely no idea what you're on about.
So you downloaded VIVID_ICS_OTA_ROOT.zip or whatever and you tried to CWM it?
The instructions from where you downloaded it from should have either given you a PH39100.zip to update your HBOOT before you reflash recovery and then the ICS zip. You MUST lock your bootloader before you use the PH39100 update zip.
If you have only a PH39100.zip image, you MUST LOCK YOUR BOOTLOADER, otherwise it will not work. Again, it should have been very clear from wherever you got the zip from.
What sort of crap site didn't tell you these things?
EDIT: Did you get this from ATT Software Update? That's probably the worst way to get this update. I'm also pretty sure you need to relock for that too.
Aus_Azn said:
I have absolutely no idea what you're on about.
So you downloaded VIVID_ICS_OTA_ROOT.zip or whatever and you tried to CWM it?
The instructions from where you downloaded it from should have either given you a PH39100.zip to update your HBOOT before you reflash recovery and then the ICS zip. You MUST lock your bootloader before you use the PH39100 update zip.
If you have only a PH39100.zip image, you MUST LOCK YOUR BOOTLOADER, otherwise it will not work. Again, it should have been very clear from wherever you got the zip from.
What sort of crap site didn't tell you these things?
EDIT: Did you get this from ATT Software Update? That's probably the worst way to get this update. I'm also pretty sure you need to relock for that too.
Click to expand...
Click to collapse
I dont think ure understanding what I am saying, I am not referring to the leak, this is the official OTA ICS update from AT&T. I know that I need to relock to install, I dont want to do that because I dont want to lose root. I'm posting so that devs can root and do whatever else with this.
Aus_Azn said:
I have absolutely no idea what you're on about.
So you downloaded VIVID_ICS_OTA_ROOT.zip or whatever and you tried to CWM it?
The instructions from where you downloaded it from should have either given you a PH39100.zip to update your HBOOT before you reflash recovery and then the ICS zip. You MUST lock your bootloader before you use the PH39100 update zip.
If you have only a PH39100.zip image, you MUST LOCK YOUR BOOTLOADER, otherwise it will not work. Again, it should have been very clear from wherever you got the zip from.
What sort of crap site didn't tell you these things?
EDIT: Did you get this from ATT Software Update? That's probably the worst way to get this update. I'm also pretty sure you need to relock for that too.
Click to expand...
Click to collapse
No, he was just wondering if it is the same one that is one here. because the ones we have been using are leaks. There have been rumors that some are sense 4.0 instead of 3.6
jsramirez27 said:
I dont think ure understanding what I am saying, I am not referring to the leak, this is the official OTA ICS update from AT&T.
Click to expand...
Click to collapse
There was no leak... The RUU is the official HTC RUU for the ICS update.
The "leak" you speak of was made from an OTA update pushed to one of the first recipients of the Vivid's ICS. Versions .52, .54 and .56 are all essentially identical.
Aus_Azn said:
There was no leak... The RUU is the official HTC RUU for the ICS update.
The "leak" you speak of was made from an OTA update pushed to one of the first recipients of the Vivid's ICS. Versions .52, .54 and .56 are all essentially identical.
Click to expand...
Click to collapse
This is what I was trying to find out. So this OTA is nothing new.
jsramirez27 said:
This is what I was trying to find out. So this OTA is nothing new.
Click to expand...
Click to collapse
That's what I am wondering too. Why we have 3 versions of a 2 week old update?
Well, I've been trying to use some custom roms and after all I restored the backup I made before, everything fine.
Today I wanted to try to use a custom rom again but it wouldn't work so I decided to wait for the official ICS release for the IncS. And here we get to my problem: When I restore the backup, and manually flash the boot.img (have to do this manually, got S-ON) and I boot my phone it gets to the HTC bootscreen, reboots and automatically gets to the CWM recovery.
Can anyone provide me an original boot.img (I haven't found it yet) or the whole standard android rom? If you have another solution, I would like to hear it!
Vaxx93 said:
Well, I've been trying to use some custom roms and after all I restored the backup I made before, everything fine.
Today I wanted to try to use a custom rom again but it wouldn't work so I decided to wait for the official ICS release for the IncS. And here we get to my problem: When I restore the backup, and manually flash the boot.img (have to do this manually, got S-ON) and I boot my phone it gets to the HTC bootscreen, reboots and automatically gets to the CWM recovery.
Can anyone provide me an original boot.img (I haven't found it yet) or the whole standard android rom? If you have another solution, I would like to hear it!
Click to expand...
Click to collapse
You can find the latest OTA in the Android Dev section. If you would use the search function ( yeah we really have a "search" function.. ) you would easily find it. If you want your boot.img we do need what for a Rom from which carrier you got.
Silversniper said:
You can find the latest OTA in the Android Dev section. If you would use the search function ( yeah we really have a "search" function.. ) you would easily find it. If you want your boot.img we do need what for a Rom from which carrier you got.
Click to expand...
Click to collapse
Actually I DID use the search, but I haven't found any stock roms for the IncS.. I would like a boot.img for T-Mobile carrier (that's what a 'carrier' is right?).
Vaxx93 said:
Actually I DID use the search, but I haven't found any stock roms for the IncS.. I would like a boot.img for T-Mobile carrier (that's what a 'carrier' is right?).
Click to expand...
Click to collapse
Here is the sticky thread in the Development section that contains official HTC Shipped RUU/ROMs for the IncS.
http://forum.xda-developers.com/showthread.php?t=1033922
tpbklake said:
Here is the sticky thread in the Development section that contains official HTC Shipped RUU/ROMs for the IncS.
http://forum.xda-developers.com/showthread.php?t=1033922
Click to expand...
Click to collapse
Thàt is helpfull! Thanks! Now my, probably last, question: how do I know which version I need? I know I have a WWE version, but which one?
Vaxx93 said:
Thàt is helpfull! Thanks! Now my, probably last, question: how do I know which version I need? I know I have a WWE version, but which one?
Click to expand...
Click to collapse
I have just been reviewing your posts and you posted that you applied the OTA and received HBOOT 2.01.0001, correct?
Then the RUU/ROM you need is the 3.11.405.2 version.
You also stated that you were able to unlock HBOOT 2.01.0001 using the HTCDEV.com site, correct? Which custom recovery did you install after that?
tpbklake said:
I have just been reviewing your posts and you posted that you applied the OTA and received HBOOT 2.01.0001, correct?
Then the RUU/ROM you need is the 3.11.405.2 version.
You also stated that you were able to unlock HBOOT 2.01.0001 using the HTCDEV.com site, correct? Which custom recovery did you install after that?
Click to expand...
Click to collapse
That's all correct, I installed the CWM recovery after that, not sure which version, the most recent one if I'm sure. I notice that the RUU/ROMS are .exe, do I flash these the same way as a .zip rom?
Vaxx93 said:
That's all correct, I installed the CWM recovery after that, not sure which version, the most recent one if I'm sure. I notice that the RUU/ROMS are .exe, do I flash these the same way as a .zip rom?
Click to expand...
Click to collapse
No, you run the exe on a PC and follow the directions on the screens. The program will tell you when to connect your phone to the PC using the USB cable.
This will completely wipe your phone and reload the ROM. Your HBOOT screen will probably show RELOCKED and you will need to unlock it again. Please confirm.
tpbklake said:
No, you run the exe on a PC and follow the directions on the screens. The program will tell you when to connect your phone to the PC using the USB cable.
This will completely wipe your phone and reload the ROM. Your HBOOT screen will probably show RELOCKED and you will need to unlock it again. Please confirm.
Click to expand...
Click to collapse
If that's true, I LOVE YOU, that's what I've been looking for. Is there a way to save my data like contacts, whatsapp messages and settings and stuff or do I have to live with the fact that I get a completely "new" phone?
Vaxx93 said:
If that's true, I LOVE YOU, that's what I've been looking for. Is there a way to save my data like contacts, whatsapp messages and settings and stuff or do I have to live with the fact that I get a completely "new" phone?
Click to expand...
Click to collapse
You can sync your contacts to your Google/Gmail account or save them to your SD cards. You can use Titanium Backup to backup apps and some settings.
Well this sucks: The ROM Updatestff can't update the Android hpone. Get the right ROM Update program and try again.
Were you sure that this is the right one? ;p
Vaxx93 said:
Well this sucks: The ROM Updatestff can't update the Android hpone. Get the right ROM Update program and try again.
Were you sure that this is the right one? ;p
Click to expand...
Click to collapse
This is the only one that has HBOOT 2.01.0001. You will also need to relock your HBOOT before you run the RUU using the command:
fastboot oem lock
tpbklake said:
This is the only one that has HBOOT 2.01.0001. You will also need to relock your HBOOT before you run the RUU using the command:
fastboot oem lock
Click to expand...
Click to collapse
Okay I did that now, it said that it was succeeded and a line under that one it said that it failed. Trying to update now, curious what happens.
It seems that he's updating now!
He updated it to the original Android, dude, you're amazing! Thanks mennnn! Just forbid myself to ever try a custom rom again and just stick to waiting for official releases
Vaxx93 said:
He updated it to the original Android, dude, you're amazing! Thanks mennnn! Just forbid myself to ever try a custom rom again and just stick to waiting for official releases
Click to expand...
Click to collapse
Glad to help! Next time just use the "Thanks" button....
Ah ofcourse, I'm pretty new to the forum and didn't notice the thanksbutton before. Used it to thank you right away!
Hi everyone!
This is my first post, since I never had any trouble toying around with my device. I have a rooted Incredible S, that ran MIUI perfectly. I want to return back to stock (this is imperative) and use the official ICS by HTC. I tried putting back my nandroid backup, which didn't work (perhaps an incompatible radio? I have no idea...). That's when I downloaded a stock, cracked ROM from a thread I found here. This is a Gingerbread ROM with Sence 3.0 I think. Obviously, I can't get the OTA to work. I think the issue here is that my recovery is still CWM, and that OTA only works with the stock recovery (this is what I concluded from research).
This is where I'm having trouble. A RUU doesn't seem to recognise my device, so that's not an option right now. Windows recognises my SD card when I hook up my phone through USB, so I can install ROMs just fine. Is there any way to get the stock recovery and the stock ROM without using a RUU, while keeping my device rooted? I really want all of this to be stock, so no mods, hacks or tweaks. I want my phone to be in the same state as when I bought it and rooted it, before installing custom ROMS. Is this possible?
Many, many thanks in advance!
gladii said:
Hi everyone!
This is my first post, since I never had any trouble toying around with my device. I have a rooted Incredible S, that ran MIUI perfectly. I want to return back to stock (this is imperative) and use the official ICS by HTC. I tried putting back my nandroid backup, which didn't work (perhaps an incompatible radio? I have no idea...). That's when I downloaded a stock, cracked ROM from a thread I found here. This is a Gingerbread ROM with Sence 3.0 I think. Obviously, I can't get the OTA to work. I think the issue here is that my recovery is still CWM, and that OTA only works with the stock recovery (this is what I concluded from research).
This is where I'm having trouble. A RUU doesn't seem to recognise my device, so that's not an option right now. Windows recognises my SD card when I hook up my phone through USB, so I can install ROMs just fine. Is there any way to get the stock recovery and the stock ROM without using a RUU, while keeping my device rooted? I really want all of this to be stock, so no mods, hacks or tweaks. I want my phone to be in the same state as when I bought it and rooted it, before installing custom ROMS. Is this possible?
Many, many thanks in advance!
Click to expand...
Click to collapse
Hey mate, official welcome from me Second welcome from me today lol
I would advise against going s-on and fully stock.
You cannot run a ruu or ota with a custom recovery/root.
So the easiest way to get the stock experience you want is by flashing one of tpbklake's rooted stock roms. They are basically stock roms with root and can run on a custom recovery. No tweaks or anything
http://forum.xda-developers.com/showthread.php?t=1773520
http://forum.xda-developers.com/showthread.php?t=1756500
The link above (top one) is based off a newer ruu from asia, although there is not much difference
I would also suggest to try ARHD 3.0.x for the stock optimised rom
Also which bootloader version do you have?
gladii said:
Hi everyone!
This is my first post, since I never had any trouble toying around with my device. I have a rooted Incredible S, that ran MIUI perfectly. I want to return back to stock (this is imperative) and use the official ICS by HTC. I tried putting back my nandroid backup, which didn't work (perhaps an incompatible radio? I have no idea...). That's when I downloaded a stock, cracked ROM from a thread I found here. This is a Gingerbread ROM with Sence 3.0 I think. Obviously, I can't get the OTA to work. I think the issue here is that my recovery is still CWM, and that OTA only works with the stock recovery (this is what I concluded from research).
This is where I'm having trouble. A RUU doesn't seem to recognise my device, so that's not an option right now. Windows recognises my SD card when I hook up my phone through USB, so I can install ROMs just fine. Is there any way to get the stock recovery and the stock ROM without using a RUU, while keeping my device rooted? I really want all of this to be stock, so no mods, hacks or tweaks. I want my phone to be in the same state as when I bought it and rooted it, before installing custom ROMS. Is this possible?
Many, many thanks in advance!
Click to expand...
Click to collapse
Yes there a some ROMs in the Development section that are completely stock that you can flash through recovery.
The original GB 2.3.3/Sense 2.1, the GB 2.3.5/Sense 3.0 and the latest ICS 4.0.4/Sense 3.6
markj338 said:
Hey mate, official welcome from me Second welcome from me today lol
I would advise against going s-on and fully stock.
You cannot run a ruu or ota with a custom recovery/root.
So the easiest way to get the stock experience you want is by flashing one of tpbklake's rooted stock roms. They are basically stock roms with root and can run on a custom recovery. No tweaks or anything
http://forum.xda-developers.com/showthread.php?t=1773520
http://forum.xda-developers.com/showthread.php?t=1756500
The link above (top one) is based off a newer ruu from asia, although there is not much difference
I would also suggest to try ARHD 3.0.x for the stock optimised rom
Also which bootloader version do you have?
Click to expand...
Click to collapse
I'm going to sell my device so I need it back the way it was. I want to keep it rooted though, so that the next owner can decide for himself what he wants to do with it. If he he's no techie, he can enjoy the device in stock (including OTAs, or can this be done like you mentioned?). If whe wants to toy with it, he can do that too. If it's easier to just go back to stock entirely, that's fine too.
It seems that I can no longer get into hboot now? After installing that hacked gingerbread, my device just boots into Android when pressing volume down and power??
tpbklake, I'll try to flash one of those when I can get back into recovery
Weird.. Taking out the battery fixed my recovery issue. I'll flash that ROM
Btw I seem to have hboot 6.13.1002 and radio 3805.06.03.03_M. Is this the info you need?
gladii said:
Weird.. Taking out the battery fixed my recovery issue. I'll flash that ROM
Btw I seem to have hboot 6.13.1002 and radio 3805.06.03.03_M. Is this the info you need?
Click to expand...
Click to collapse
Yes
But since you want stock it won't matter
You CANNOT have both root and ota updates
Either one or the other unfortunately
You have to make a choice a rooted stock ROM will be identical to the official ota from htc but you will be able to keep root, but can't get ota updates
but unfortunately I think sense 3.6 4.0.4 is the last update
But, I have been proven wrong before
Sent from my Nexus 7
K then in my case a full stock device would be best. How do I get started with this? First install a stock ROM, then the stock recovery and then put It back in S-OFF? Which ROM should I install (would prefer the stock 2.3.3)? And where can I find the recovery? Sorry for the basic questions but those lists of ROMs can get a bit complicated..
Still getting nowhere If I flash a stock ROM in CWM, my recovery won't go back to stock, will it? Shouldn't I try to get the stock recovery first and then use a RUU? Problem is that I can't seem to find a stock recovery anywhere. And when I extract the ROM from a RUU, it's only about 180 MB, so that can't be right, can it?
gladii said:
Still getting nowhere If I flash a stock ROM in CWM, my recovery won't go back to stock, will it? Shouldn't I try to get the stock recovery first and then use a RUU? Problem is that I can't seem to find a stock recovery anywhere. And when I extract the ROM from a RUU, it's only about 180 MB, so that can't be right, can it?
Click to expand...
Click to collapse
Which ruu? Here's a good guide http://forum.xda-developers.com/showthread.php?t=1359555 but I find it faster to flash the alparev then run the ruu, 2 steps and done.
Nonverbose said:
Which ruu? Here's a good guide http://forum.xda-developers.com/showthread.php?t=1359555 but I find it faster to flash the alparev then run the ruu, 2 steps and done.
Click to expand...
Click to collapse
Sorry for the late reply. I've been busy with exams. I've tried the RUU RUU_IncredibleC_Verizon_WWE_1.22.605.0_Radio_1.00.03.04.06_release_161493_NoDriver (but I don't actually have a Verizon, could that be the problem?).
I really have no idea what all the info in the filename means, so it's difficult to find one that fits my needs. I'll take a look at your link right now and report back!
gladii said:
Sorry for the late reply. I've been busy with exams. I've tried the RUU RUU_IncredibleC_Verizon_WWE_1.22.605.0_Radio_1.00.03.04.06_release_161493_NoDriver (but I don't actually have a Verizon, could that be the problem?).
I really have no idea what all the info in the filename means, so it's difficult to find one that fits my needs. I'll take a look at your link right now and report back!
Click to expand...
Click to collapse
DO NOT attemtp to flash that one!!!! The Verizon DINC2 is a CDMA device and the radio is not compatible.
Please read the post that nonverbose referenced for you. That tells you all you need to do.
tpbklake said:
DO NOT attemtp to flash that one!!!! The Verizon DINC2 is a CDMA device and the radio is not compatible.
Click to expand...
Click to collapse
Wow, good thing it didn't succeed! How about this one:
RUU_Vivo_Gingerbread_S_HTC_ARA_2.30.415.1_Radio_20.2808.30.085AU_3805.06.03.03_M_release_199399_signed.exe
(download link: http://www.filefactory.com/file/c0af340/n/RUU_Vivo_Gingerbread_S_HTC_ARA_2.30.415.1_Radio_20.2808.30.085AU_3805.06.03.03_M_release_199399_signed.exe)
gladii said:
Wow, good thing it didn't succeed! How about this one:
RUU_Vivo_Gingerbread_S_HTC_ARA_2.30.415.1_Radio_20.2808.30.085AU_3805.06.03.03_M_release_199399_signed.exe
(download link: http://www.filefactory.com/file/c0a...5AU_3805.06.03.03_M_release_199399_signed.exe)
Click to expand...
Click to collapse
What region of the world are you in? I would recommend the HTC WWE 2.30.405.1.
tpbklake said:
What region of the world are you in? I would recommend the HTC WWE 2.30.405.1.
Click to expand...
Click to collapse
Belgium (Brussels), western Europe. I bought the device here so it should be pretty local... I'll try that one. What does the WWE mean? (Just for the info)
gladii said:
Belgium (Brussels), western Europe. I bought the device here so it should be pretty local... I'll try that one. What does the WWE mean? (Just for the info)
Click to expand...
Click to collapse
World Wide English with support for most European languages
gladii said:
Belgium (Brussels), western Europe. I bought the device here so it should be pretty local... I'll try that one. What does the WWE mean? (Just for the info)
Click to expand...
Click to collapse
Ah, perfect! Canceled my download, but there's a 20 minute interval before starting a new one, so it'll take me at least an hour to download it.
I've encountered this issue before, but randomness seemed to solve it back then: a fastboot command just displays "<waiting for device>" and then keeps hanging there. "fastboot devices" returns an empty line, so that's consistent. Phone is in fastboot USB mode, so I'm not sure what could be the issue?
And then I have a question. In that guide, it says that I should extract HBOOT.img from the rom I installed. In my case, my rom only contains a file named "hboot_1.13.0000_CRC_8a731c6e_0401.img" (along with others of course, but I assume they are redundant in this step); will that one do?
gladii said:
I've encountered this issue before, but randomness seemed to solve it back then: a fastboot command just displays "<waiting for device>" and then keeps hanging there. "fastboot devices" returns an empty line, so that's consistent. Phone is in fastboot USB mode, so I'm not sure what could be the issue?
And then I have a question. In that guide, it says that I should extract HBOOT.img from the rom I installed. In my case, my rom only contains a file named "hboot_1.13.0000_CRC_8a731c6e_0401.img" (along with others of course, but I assume they are redundant in this step); will that one do?
Click to expand...
Click to collapse
Sounds like it may be a port issue, cable issue or driver issue on the PC.
Have you tried different ports or a different cable? Do you have HTC Sync running in the System Tray on the PC?
As for the hboot file, yes that is the one.
gladii said:
And then I have a question. In that guide, it says that I should extract HBOOT.img from the rom I installed. In my case, my rom only contains a file named "hboot_1.13.0000_CRC_8a731c6e_0401.img" (along with others of course, but I assume they are redundant in this step); will that one do?
Click to expand...
Click to collapse
I thought you wanted to go to stock ICS? Hboot 1.13 it a gingerbread hboot. If you just flash the vivo_downgrade.img then run the ruu, there will be no need to extract and flash the hboot from the ruu.
Nonverbose said:
I thought you wanted to go to stock ICS? Hboot 1.13 it a gingerbread hboot. If you just flash the vivo_downgrade.img then run the ruu, there will be no need to extract and flash the hboot from the ruu.
Click to expand...
Click to collapse
No I wanted it back the way I wanted it. Rom, recovery,... all stock. But surely I'll give ICS a testdrive via OTA