Hi, probably going to sound like a N00b question but I haven't yet found answer that fits.
If I have a HOX that is running v1.26 and I root and ROM to something using v1.29 or anything higher than 1.26 can I use the RUU for 1.26 that fits my CID to revert to stock?
Only reason I ask is that I have already had one HOX that I managed to well and truly kill that my provider has fortunately replaced for me (although they don't yet know it's been unlocked!).
The Mic died after a few days from root and ROM onto RD MIUI, but as I had performed a full wipe I had no stock backup to revert to when I then wanted to get it replaced, and so ended up trying all I could to find the RUU for v1.29 but there was only v1.26 available. So I've had to send back my faulty handset with a different ROM on it.
Just looking to avoid a repeat in the future.
Thanks
(Please try to keep your comments helpful rather than mocking)
It is the hboot you can't downgrade. As far as I can tell, it has been updated with every release of the OTA.
If you root and install a ROM with a newer base, the hboot won't be updated (unless it's a newer stock ROM updated by RUU or OTA) you can still go back to an RUU with the same or newer version you have now.
Related
I've used the search but frankly, the vBulletin search still sucks after all these years.
I rooted the phone following this guide. Now my phone says a system update is available.
Since I would like to install it (my phone is still 1.34, I think. The latest version should be 1.72, right?) and installing a stock update onto a S-OFF phone is highly inadvisable (I've read), how do I go about this?
I have Visionary installed but it says the phone does not appear rooted, even though it is (just checked).
I'm sure there have been others with similar questions and I just couldn't find the right thread. If so, please point me in the right direction.
Regards and thank you,
Kokuyo said:
I've used the search but frankly, the vBulletin search still sucks after all these years.
I rooted the phone following this guide. Now my phone says a system update is available.
Since I would like to install it (my phone is still 1.34, I think. The latest version should be 1.72, right?) and installing a stock update onto a S-OFF phone is highly inadvisable (I've read), how do I go about this?
I have Visionary installed but it says the phone does not appear rooted, even though it is (just checked).
I'm sure there have been others with similar questions and I just couldn't find the right thread. If so, please point me in the right direction.
Regards and thank you,
Click to expand...
Click to collapse
Why did you root your phone? There is no need to update your phone to the latest OTA update if you are wanting to install custom ROMs.
Because I was testing custom mods and wanted to go back to stock?
Kokuyo said:
Because I was testing custom mods and wanted to go back to stock?
Click to expand...
Click to collapse
ahhh, I thought you had just rooted it. I updated the day after I received my new phone. I had problems with bluetooth (music wouldn't resume after ending phone calls) and wound up here on the XDA forums looking for answers. I ended up rooting my phone, installing CM6 and now CM7 and never looked back. There is no bluetooth switching problems using CM builds so I'm happy.
Found this:
http://www.thinkthinkdo.com/trac/project1/wiki/back_to_stock
Thanks, that looks interesting. Now the only question: Do I need my original CID? And if so, how do I find it now that the CID has been changed by gfree?
That link is about a procedure to restore the stock G2 ROM. Since you seem to have a DZ ROM, I'm not sure if you want to flash a G2 ROM (though the other bits might be useful).
The 1.72 OTA update has been rootable for some time now, so you can safely accept the update if you want. But it might be easier just to flash the 1.72 ROM in its entireity (you can get it from the dev forum).
With SuperCID and S-OFF you should have no problems flashing 1.72.
steviewevie said:
With SuperCID and S-OFF you should have no problems flashing 1.72.
Click to expand...
Click to collapse
Really? Then I don't quite understand the stickied warning thread that says to never, ever attempt that.
Anyhow, I gave the Virtuous mod another go. Since it has sense and 1.72 I'm thinking of testing this one out a bit more, before I go flashing stock.
Thanks for the replies, though.
Hi guys, I've been searching the forum for a while but I still can't find a solution/reason for what it's happening to my DZ, which I bought from England and vodafone branded.
Soon after the first configuration I upgraded to 1.72 as suggested, but I couldn't know that rooting was then no more possible. I didn't want to be stuck on a vodafone branded and only-english rom, so I debranded succesfully my DZ by downgrading to a stock htc 1.34 rom (RUU_Vision_HTC_WWE_1.34.405.5_Radio_12.28b.60.140e_26.03.02.26_M_release_155556_signed), obtaining then permroot + superCID.
Now my rom speaks italian (as I wanted) and is rooted, but if I check manually for updates, I get only a message telling me that the phone is updated and there are no new upgrades available.
I tried to:
- look for updates before rooting and with s-on (CID vodap_001), waiting even for 1 week
- put back the gold card I used to downgrade and then checking for OTA
- check for updates with root, superCID and s-off
Is there any reason for that?
How can I update again to 2.2.1 (1.72 & 1.83)?
ps: I prefer a stock rom for the moment instead of a custom rom
Any help/opinion is appreciated!
There won't be any OTA updates once you've rooted and de-branded. And if there are, do not accept them, as they will either fail or possibly unroot/brick your phone.
Your option will to be to find a rooted, stock ROM that comes with the latest OTA software package already installed. Check the dev section, they have a list of ROMs. You may not be able to find the exact specific ROM you've currently got, but there are many choices that can come close.
First of all, thanks for prompt answering martonikaj.
I thought I could receive and install ota updates since there was a stock rom with superCID in my devide.. which is different from having a custom rom like Virtuos.
What about users telling they had downgraded-debranded-rooted their DZ and can receive and install successfully OTA updates??
Flashing a rooted stock rom implies wiping everything.. and I prefer to avoid that.
There's a rooted 1.82 stock ROM at : http://forum.xda-developers.com/showthread.php?t=960149 . Really if you're going to make that huge version jump you should do a wipe. Back up your stuff with Titanium backup first
Rixan said:
First of all, thanks for prompt answering martonikaj.
I thought I could receive and install ota updates since there was a stock rom with superCID in my devide.. which is different from having a custom rom like Virtuos.
What about users telling they had downgraded-debranded-rooted their DZ and can receive and install successfully OTA updates??
Flashing a rooted stock rom implies wiping everything.. and I prefer to avoid that.
Click to expand...
Click to collapse
Sorry but in all my times rooting and modding devices, applying OTA updates has never been something that works with rooted devices.
Unfortunately, yes, if you want to upgrade to the rooted version of the latest OTA ROM, you're gonna have to wipe everything and start from fresh with the new ROM.
Same here
Hi,
The same thing is exactly happening to me. My phone keeps telling me that there is not update but the software number is 1.34, which from what I've read is an older firmware. Shouldn't my phone be able to detect the update?
The question isnt whether rooted is better, but why our phones are not receiving any ota. Granting that stock rom is not better, the problem is there is no notification at all that there is an update.
FYI, I have flashed an official rue version but still has s-off. :-D I don't know if having s-off would prevent the phone from finding an update.
Think about it this way people: when you mod your phone by rooting, it's like cutting the imbillical cord with your carrier/manufacturer's update servers. Don't worry about why, just have that mentality as it will make all your lives easier. If you rooted, why would you want a stock rom that limits you?
If you want stock with sense, go for GingerSense, Vitruous, etc..
If you want stock w/o sense, go for any of the other pre-rooted G2 roms.
I really don't understand why people would complain about OTA updates when you can backup and update to a rom of your choice whenever you want. Plus, if you don't like it, you can revert! Something you cannot do with a stock OTA update.
/rant
Sent from my Virtuous Desire Z 1.0.2 using XDA App
Hi I would like to know if there would be a problem if I flash the official rue of an Asian desire z with a european version or vice versa?
I bought my phone second hand and I decided to flash the 1.34.707.1 version into my originally 1.72 desire z. Now my phone cannot find updates. It keeps telling me that there is no update even if check manually.
I know that I can flash a higher version by downloading a higher rue version but what I wanted to find out if I can no longer receive ota updates because of what I did.
Since when I was in 1.72 my phone did not notify me of the 1.82 update too...
I don't know what's wrong.. Please help. Thank you.
I think if you are SuperCID and S-Off, it would work. Otherwise, it won't let you flash the ROM from another region.
Also, if you flash an official ROM, you will lose root, and you can't get it back on any ROM version higher than 1.34. For this reason, if you downgraded to 1.34 for purposes of rooting, you don't want the OTA updates, anyway.
If you're rooted and S-Off, and you want a more updated ROM version, just flash the Virtuous custom ROM. Its mostly stock 1.85, but rooted, and with a few cool added features and some optimizations.
Hi, the thing is I'm not very knowledgeable when it comes to rooting. I read the posts here specifically in the wii section and I don't think I have the skills to pull it off and risk bricking my phone.
I think my phone is not rooted or it was before but not anymore, since as mentioned I flashed an official ruu.
So basically, I should still be able to receive OTA's from HTC right? I was wondering why my phone keeps telling me there's no update when the software number is 1.34 stock and not rooted. Shouldn't it notify me that there's an update at least regardless of whether I want to or not?
If you are not rooted, why did you downgrade to 1.34?
I also don't understand why you want to flash the RUU from a different region. If you aren't SuperCID and S-Off it won't work. Why not just flash the latest official RUU for your phone versions/region if you want to be updated and don't care about root?
I'm not sure why your OTA's don't work. I'm still on 1.34 (well, back to it), and I still get notifications to update.
redpoint73 said:
If you are not rooted, why did you downgrade to 1.34?
I also don't understand why you want to flash the RUU from a different region. If you aren't SuperCID and S-Off it won't work. Why not just flash the latest official RUU for your phone versions/region if you want to be updated and don't care about root?
I'm not sure why your OTA's don't work. I'm still on 1.34 (well, back to it), and I still get notifications to update.
Click to expand...
Click to collapse
@redpoint73
I bought the phone from a friend of mine. I noticed that it had eng hboot and had s-off.
I have zero knowledge about rooting. When the gingerbread test rom for the desire z came out, I flashed the pc10img.zip via the bootloader, however since it was very buggy and laggy, I decided to flash stock desire z rom.
Having no knowledge about rooting I read some of the threads in this forum and learned that flashing an official rom i.e. the RUU would be the easiest way to return back to stock.
It worked, I am using stock rom. I experimented and found out that I can flash any of the RUU, so I chose any of the WWE release. I decided to flash an older firmware version specifically, the 1.34.707.1.
Now the problem is my phone doesn't prompt me with an update, even after checking in about phone > check for update.
I still have s-off but eng hboot is gone. To clarify I was not the one who rooted the phone, so I have no idea what to do.
Is it possible that the previous owner tweaked something in the phone that would absolutely prevent it from receiving OTA?
I am just worried since I have a feeling that the gingerbread OTA will be released in a few weeks since the update for the Desire HD is already out.
Please help and thank you again. I extremely as a NOOB!
qtlestat said:
I am just worried since I have a feeling that the gingerbread OTA will be released in a few weeks since the update for the Desire HD is already out.
Click to expand...
Click to collapse
I wouldn't worry about getting the official Gingerbread ROM OTA. It will probably be posted here or at shipped-roms.com long before you would get it OTA.
Hi Guys,
I know that there are already tons of topics about this question and I read al lot of them but none of them gave me a answer that satisfied me.
I'm running on my HOX this ruu: RUU_ENDEAVOR_U_ICS_40_S_HTC_Europe_2.17.401.2
with CID ID HTC__E11 (Lucky me).
As far as I believe I can update to JB according to this topic: http://forum.xda-developers.com/showthread.php?t=1957376
the only problem is that since I ****ed up my HOX once while getting back to stock for the ota update (I was on EternityProject) it cost me 4 hours and way to high blood pressure to fix it. So as you can imagine I'm a bit scared to do it.
The other question is where in the hell does the S stand for in my ruu? It was late when I downloaded the ruu (and flashed it) and since I thought the higher the better and the 401 was the same I went for it.
My HOX is preforming fine now but on tweakers (a Dutch tech site) a person with the same cid did get the update 3-4 days ago and I'm still waiting.
I hope that one of you can help me.
Greetz,
I'mpossible
Yeah, you can update your hboot to 1.31.
From there, you can install Sense based JB ROMs such as ARHD 13.
You might struggle to have AOSP ROMs work correctly after that, though.
To install the official OTA, you just (wait, and then) flash back your 2.17 backup (ROM, boot.img and stock recovery) I'm led to beleive that works.
Oh, if somebody has the 401 JB update, it's because they are on elevate (closed beta test).
I don't know what the 'S' is.
I did a little too much screwing around with my One V earlier today, and I'm honestly afraid that I've hard-bricked it at this point. I have middling experience when it comes to RUU installs and flashing/experimenting with new ROMs and kernels - but my last root/ROM flash attempt didn't go as planned. I'd installed the stock RUU earlier in the day in order to get the radio update (which, as I now realize, was more or less pointless as the new radio sounds like it's a pain to deal with), and had just finished unlocking and rooting the phone. I booted into TWRP to flash my favorite ROM, and I'm pretty sure this is where I messed up: rather than just wiping System, Cache, Dalvik, and Factory Resetting, I opted to wipe everything I could select in that menu. Please don't ask why (I was tired and out of it, and had planned on re-formatting my SD card at some point - it made sense at the time...) - I now realize how stupid this was, and I'm going out of my mind trying to fix it.
I thought it would be a simple matter of flashing the RUU file I currently have, but alas, I now have hboot 1.57 and the newest radio version - so I get an "hboot is older!" error when I attempt to install this older RUU. I can't locate an RUU based on hboot 1.57, and I'm not sure whether I'm just looking in the wrong places or interpreting RUU filenames incorrectly (perhaps certain RUUs would prove compatible despite incorporating a slightly downgraded hboot...?).
Any help you can offer would be greatly appreciated - if you need any more information from me in order to provide a solution, please let me know and I'll respond as quickly as I can.
EDIT: I have a CDMA One V.
don't boots said:
I did a little too much screwing around with my One V earlier today, and I'm honestly afraid that I've hard-bricked it at this point. I have middling experience when it comes to RUU installs and flashing/experimenting with new ROMs and kernels - but my last root/ROM flash attempt didn't go as planned. I'd installed the stock RUU earlier in the day in order to get the radio update (which, as I now realize, was more or less pointless as the new radio sounds like it's a pain to deal with), and had just finished unlocking and rooting the phone. I booted into TWRP to flash my favorite ROM, and I'm pretty sure this is where I messed up: rather than just wiping System, Cache, Dalvik, and Factory Resetting, I opted to wipe everything I could select in that menu. Please don't ask why (I was tired and out of it, and had planned on re-formatting my SD card at some point - it made sense at the time...) - I now realize how stupid this was, and I'm going out of my mind trying to fix it.
I thought it would be a simple matter of flashing the RUU file I currently have, but alas, I now have hboot 1.57 and the newest radio version - so I get an "hboot is older!" error when I attempt to install this older RUU. I can't locate an RUU based on hboot 1.57, and I'm not sure whether I'm just looking in the wrong places or interpreting RUU filenames incorrectly (perhaps certain RUUs would prove compatible despite incorporating a slightly downgraded hboot...?).
Any help you can offer would be greatly appreciated - if you need any more information from me in order to provide a solution, please let me know and I'll respond as quickly as I can.
EDIT: I have a CDMA One V.
Click to expand...
Click to collapse
Well i dont have a CDMA one v but i know that the RUU for hboot greater than v1.17 had not been released.. So the best method to recover stock ROM is using a stock ROM backup with the same hboot and radio version , if anyone bought a one v recently he should be on the latest hboot and radio version , you can get a stock backup from such a person or search on xda for such a backup..
There isn't a RUU for the Hboot 1.57 and the newest radio. Sorry to give the bad news. You will either have to use a nandroid backup or install one of the custom roms such as RhythmicRom, e3remeSense or myOneV. Good luck on your rooting journey!
Thanks. I ended up successfully installing Rhythmic, but I can't get x3reme Sense (my preferred ROM) to work, for some reason (which is sort of ironic - I know Rhythmic incorporates a fix to allow for compatibility, but I thought one of the OTA updates was supposed to prevent installing anything not based on Sense). Oh, well.
If you'll use this kernel, then x3reme Sense will boot. I tried it for a while, but for a sense based rom I prefer myOne. If you want to try it, Cyanprimo will boot and run fine with the RhythmicRom v1.2 kernel. That is my daily driver(at least for now).
http://forum.xda-developers.com/showthread.php?t=2261819