Help I have a htc vivid it was 4.0 I did root and change the rom to 4.1.2
I did not know why but I put the PH39IMG and returned to be 2.3.4
4.0 and wanted to put it down on the page ruu htc
but every time I try to install it says error 155 something like that you can not upgrade the rom image
I gave up searching google and decides to do a root and no root reading for this version of android
Anyone know how I can do to make it 4.0 or a root to that version 2.3.4
thanks
The Smartphone is out of USA and here I am in Panama there is no coverage for updating ATT
The best thing to do would be to determine if your device is locked or unlocked, if you are unlocked you should lock the device and download the RUU for ICS, since the phone came from the US look for the ATT or Cingular ICS RUU. If you are locked just download that RUU and run the RUU from your computer. This will install ICS. This will also ensure you have the correct HBoot for running any newer android (4.0 or 4.1).
I think 1.85.0025 is the ICS hboot
Sent from my Vivid 4G using Tapatalk 2
Related
I've recently gotten a Unlocked Bell (but Unrooted!) IS with Froyo on it.
I check the system software update and the gingerbread update is available for download and whatnot.
I download it and click to install but it stops after a restart on the bootloader screen where I see the install package cannot open. (You know the screen with the blue android and exclamation mark)
Is it REQUIRED that I need to root the IS to update the phone to 2.3?
I'm under Telus btw.
-Canada-
Thanks
sdkim89 said:
I've recently gotten a Unlocked Bell (but Unrooted!) IS with Froyo on it.
I check the system software update and the gingerbread update is available for download and whatnot.
I download it and click to install but it stops after a restart on the bootloader screen where I see the install package cannot open. (You know the screen with the blue android and exclamation mark)
Is it REQUIRED that I need to root the IS to update the phone to 2.3?
I'm under Telus btw.
-Canada-
Thanks
Click to expand...
Click to collapse
Since your IncS is carrier unlocked, you are trying to load a Bell GB update on the phone and I bet it is checking to see if the phone has a Bell CID (which it doesn't since you have unlocked it).
You would be better off running AlphaRevX Revolutionary to S-OFF and install ClockworkMod recovery. After that process you would then be able to install a rooted version of the IncS WWE Gingerbread ROM and lose all of the Bell bloatware.
I'm just very unsure about rooting IS 'cause it says its still in the beta stages so, I'm trying to optimize my phone as much as it's able before considering rooting (which I'm sure everyone is trying to).
Also not sure if anything will go wrong and such 'cause it's in beta
Had the Desire before and everything was sure 100% hence.
HI, quick noob question,
I have a rooted, stock rom, bell htc raider with CWM 5.5.0.4 recovery.
What steps should I take to prepare for the upcomming OTA update to ICS.
I read that the safest way to do this is to get it as close to stock as possible, how do I do that?
I found a method for the AT&T phones but obviously since bell hasn't released the update yet I wont find one for mine.
thanks for any help you can give me.
PatG20
*edit, I used the same method as the At&t phones, found an original RUU for Bell, relocked the bootloader and ran the RUU. back to bone stock.
AT&T RUU
Run the ICS AT&T RUU and use a Custom ROM like Dark Raider until we get the official update from BELL or ROGERS.
Hi,
A few months ago i installed the leaked 4.2.2 rom version that was provide on xda
http://forum.xda-developers.com/showthread.php?t=2224752 odexed
Now the OTA has arrived for the HTC One, i would like to head back to the clean stock htc rom sow i will be able to receive normal ota's provided by HTC.
I try to do this by installing an older RUU but get stuck at an error due to the bootloader version.
Can somebody tell me how i can downgrade to the stock rom?
Thx!
Without s-off you can't. But if you are s-off flash the 1.44 hboot in sneakyghosts. Thread about getting rid of red txt on boot screen
H
lukzke said:
Hi,
A few months ago i installed the leaked 4.2.2 rom version that was provide on xda
http://forum.xda-developers.com/showthread.php?t=2224752 odexed
Now the OTA has arrived for the HTC One, i would like to head back to the clean stock htc rom sow i will be able to receive normal ota's provided by HTC.
I try to do this by installing an older RUU but get stuck at an error due to the bootloader version.
Can somebody tell me how i can downgrade to the stock rom?
Thx!
Click to expand...
Click to collapse
If you have not used the firmware.zip you should just need to install an older wwe stock , lock and, login and let the phone upgrade .
Skickat från min HTC One via Tapatalk 2
Ok, I've already got around to resetting my CID to the stock CID number (VODAP102)
I'm using this site for all the downloads http://www.htc1guru.com/downloads/ - sadly since Vodafone doesn't seem that popular there isn't any RUUs for it, there are however a Nandroid backup, OTA update and Guru-reset.
My phone is currently S-OFF and rooted and has all the lastest firmware e.t.c, and since I can't find a guide on how to go to stock without a RUU I thought I better ask first!
Also side note, when changing firmware using the command with cmd to check the version number is fine, but when the phone is booted and I got to about>software infomation, it still shows the old software number, is that normal?
I got an unlocked HTC One that was originally on AT&T's network, but now I use it on T-Mobile. The OTA updates won't work since I'm not on AT&T's network and the RUU file has not been released yet. I'm debating whether I should root the device, wait for the RUU file, or bug a friend to use their AT&T sim card to get the update. I'm currently running android 4.1.2 and sense 5 (software number 1.26.502.10). Also if the RUU file does come out can I use it from 4.1 to get to 4.4 or will there be issues?
Thanks
wbrianw said:
I got an unlocked HTC One that was originally on AT&T's network, but now I use it on T-Mobile. The OTA updates won't work since I'm not on AT&T's network and the RUU file has not been released yet. I'm debating whether I should root the device, wait for the RUU file, or bug a friend to use their AT&T sim card to get the update. I'm currently running android 4.1.2 and sense 5 (software number 1.26.502.10). Also if the RUU file does come out can I use it from 4.1 to get to 4.4 or will there be issues?
Thanks
Click to expand...
Click to collapse
The easiest way is to borrow your friend's sim card but that just keeps you locked into AT&T's network. Since, you are running on T-Mobile it may be better to change your phone to look like T-Mobile so you can get all of the benefits of T-Mobile including their OTA updates. You can use this guide Complete Flashing Guide | Rooting to Unlock your bootloader, install custom recovery and root. Then I would use this guide get S-OFF. Once you are S-OFF, then change your MID using this tool MID change without ENG HBOOT then change the CID. You can use this guide nkk71's SuperGUIDE to returning 100% back to stock to show the steps to install the latest T-Mobile RUU. Once the RUU is installed you are set with a stock T-Mobile rom, recovery and S-OFF. Keep S-OFF as long as you can, don't return to S-ON!
majmoz said:
The easiest way is to borrow your friend's sim card but that just keeps you locked into AT&T's network. Since, you are running on T-Mobile it may be better to change your phone to look like T-Mobile so you can get all of the benefits of T-Mobile including their OTA updates. You can use this guide Complete Flashing Guide | Rooting to Unlock your bootloader, install custom recovery and root. Then I would use this guide get S-OFF. Once you are S-OFF, then change your MID using this tool MID change without ENG HBOOT then change the CID. You can use this guide nkk71's SuperGUIDE to returning 100% back to stock to show the steps to install the latest T-Mobile RUU. Once the RUU is installed you are set with a stock T-Mobile rom, recovery and S-OFF. Keep S-OFF as long as you can, don't return to S-ON!
Click to expand...
Click to collapse
Thanks so much for the help, I'll try that when I get the chance.