Related
Ok so that this is up front so that everyone understands.. I do not care about root and have no plans to root this phone for a while. (This is my primary phone and I need it working and not bricked)< I have personal reasons for not wanting root at this time so please don't ask.
Now my question is the following:
If I extract the rom.zip file from RUU that was leaked yesterday will I be able to just rename the file to PB31IMG.zip and place it in the root of my SD card. Then boot into hboot and apply the update?
From the threads I have found so far on how to do this state that the phone will do a quick reboot while applying this update. This is caused by the updating of hboot from what I have see. Then I'm suppose to just tell it again to apply the update. < Is Applying the update the second time safe?
Will this work to flash my phone to the new version of the android, hboot, radio and so forth? I just want to apply the update instead of waiting days or weeks for verizon to finally push it to my phone via OTA.
I'm currently with the following settings.
S-On
Hboot .77
Stock Android 2.1 update-1(not rooted)
radio 100
Additional Information.
I've tried just using the RUU but due to driver conflicts it keeps giving me the USB error. The most I've ever gotten was the phone into the bootloader then the RUU loses connection. Tried this on 3 machines now and it still fails. And yes I've installed HTC Sync only on 2 of those 3 machines and it still fails..
To be honest, I would say just wait for the OTA, Verizon themselves have confirmed it has been/will be released today 8/27. Then there will be no worrying, since you don't want root this would be the best way.
boomertwo said:
Ok so that this is up front so that everyone understands.. I do not care about root and have no plans to root this phone for a while. (This is my primary phone and I need it working and not bricked)< I have personal reasons for not wanting root at this time so please don't ask.
Now my question is the following:
If I extract the rom.zip file from RUU that was leaked yesterday will I be able to just rename the file to PB31IMG.zip and place it in the root of my SD card. Then boot into hboot and apply the update?
From the threads I have found so far on how to do this state that the phone will do a quick reboot while applying this update. This is caused by the updating of hboot from what I have see. Then I'm suppose to just tell it again to apply the update. < Is Applying the update the second time safe?
Will this work to flash my phone to the new version of the android, hboot, radio and so forth? I just want to apply the update instead of waiting days or weeks for verizon to finally push it to my phone via OTA.
I'm currently with the following settings.
S-On
Hboot .77
Stock Android 2.1 update-1(not rooted)
radio 100
Additional Information.
I've tried just using the RUU but due to driver conflicts it keeps giving me the USB error. The most I've ever gotten was the phone into the bootloader then the RUU loses connection. Tried this on 3 machines now and it still fails. And yes I've installed HTC Sync only on 2 of those 3 machines and it still fails..
Click to expand...
Click to collapse
I'm sorry this has nothing to do with what you're asking, I've read, and don't know sorry man, but I do have a quick question for you. I see you have never rooted, or maybe or have, I thought maybe you hadn't for some reason, but anyway, I see you HBOOT it .77, how long have you had your phone since?
Yes I had rooted the phone recently for about 2 weeks then it got messed up but thanks to an unrevoked member I was able to recover the phone. It wasn't bricked or anything but some how the NAM was messed up which prevented me from using *228 to update roaming or my ability to activate the phone after a factory reset. I do remember it having hboot .79 before rooting though.
Update: I verified that the hboot in the stock restore img file I used had only hboot 77 in it and not 79. This means I downgraded to 77 without knowing it at first. (From the threads I have read it is stated that .77 and .79 are interchangeable so I don't think I need to worry about it when the ota comes I hope..)
I've had it for about 3 months now so I'm out of the return policy and I do like the phone and have no intention of returning it.
After trying root out for those 2 weeks I found that for me I didn't really gain anything that seemed worth it for my personal needs.
Also I like to tinker with stuff but since I'm in a 2 year contract I rather not take the risk of bricking it and having to pay for the next 2 years for service I can't even use due to my own fault of breaking the device.
Right now I'm just wondering if it is safe to apply the file that can be found in the ruu without root and without breaking the device since it has the same build number and radio number as the update that verizon has stated on the update page.
.77
I am on my third incredible, and all 3 shipped to me with v.77. Last one shipped was 8/9 (wow, maybe this one is a keeper).
jdmba said:
I am on my third incredible, and all 3 shipped to me with v.77. Last one shipped was 8/9 (wow, maybe this one is a keeper).
Click to expand...
Click to collapse
were these all brand new phones, refurbs..?
To my understanding of this whole .77, .79 HBOOT is that these two are interchangeable and doesn't matter which one you have. I was just curious because at first I used the RUU that gave me software 1.22.605.0 and the latest is 1.22.605.2 and I never got an OTA update for the latest 2.1. but I think this is normal since the servers are doing the new thing.
and from what I think, if you had .77, and got the OTA for the latest 2.1 that came out a while ago, it kept the .77, but if you did the latest 2.1 through the RUU on ur computer instead of OTA it updated the HBOOT to .79 as well.
This is how it was with the Droid Eris with the leaks and stuff which blocked you out of root.
...
BlazeD OnE said:
were these all brand new phones, refurbs..?
Click to expand...
Click to collapse
Phone # 1 - New ... would get hotter and hotter (even when not in use) until it would enter a reboot cycle. It would also reboot randomly during the day.
Phone # 2 - Refurb ... got it with a bad speaker, but otherwise it worked perfectly.
Phone # 3 - Refurb ... still going.
boomertwo said:
Ok so that this is up front so that everyone understands.. I do not care about root and have no plans to root this phone for a while. (This is my primary phone and I need it working and not bricked)< I have personal reasons for not wanting root at this time so please don't ask.
Now my question is the following:
If I extract the rom.zip file from RUU that was leaked yesterday will I be able to just rename the file to PB31IMG.zip and place it in the root of my SD card. Then boot into hboot and apply the update?
From the threads I have found so far on how to do this state that the phone will do a quick reboot while applying this update. This is caused by the updating of hboot from what I have see. Then I'm suppose to just tell it again to apply the update. < Is Applying the update the second time safe?
Will this work to flash my phone to the new version of the android, hboot, radio and so forth? I just want to apply the update instead of waiting days or weeks for verizon to finally push it to my phone via OTA.
I'm currently with the following settings.
S-On
Hboot .77
Stock Android 2.1 update-1(not rooted)
radio 100
Additional Information.
I've tried just using the RUU but due to driver conflicts it keeps giving me the USB error. The most I've ever gotten was the phone into the bootloader then the RUU loses connection. Tried this on 3 machines now and it still fails. And yes I've installed HTC Sync only on 2 of those 3 machines and it still fails..
Click to expand...
Click to collapse
in theory that should work.
k.electron said:
in theory that should work.
Click to expand...
Click to collapse
Well I took the plunge and can confirm that the method in my original post does work and without a hitch(For me at least.)I did this after reading another question thread that had a guy basically asking the same thing and was recommended just to follow to step 6. I cannot link to anything yet so I will just give you the thread title that is located in the Q&A section of this forum for the droid incredible.
Thread Title: "[Q] Applying RUU update to stock phone"
The phone did however reboot the bootloader and put me into fastboot. I did not pull the battery but instead selected bootloader again and it continued the update on its own.
I'm successfully not root and s-on with android 2.2(HTC stock)
Hboot .92
Stock Recovery.
*Before you say it.. I know I'm now not able to get root till unrevoked or another dev team releases new tools for this version. I did this by choice*
*I in no way will recommend anyone to do this and will not take responsibility for your phone being turned into a paper weight* < You have been warned..
Sooooo.. anyone want to clarify how to extract rom.zip from the RUU please?
Just download the extracted ROM. It's on page 6 or 7 in the RUU thread.
NinjaRicky said:
Sooooo.. anyone want to clarify how to extract rom.zip from the RUU please?
Click to expand...
Click to collapse
did you get it?
So I've been at this one for a while, using information from various threads, getting things wrong, getting things right... now I'm at a loss!
Background
My Desire went faulty. I sent back to HTC. They sent me a new phone. It was locked. They sent me an unlock code. It was then unlocked. It was branded to T-Mobile. I didn't want that. So...
From what I can remember...
First, I flashed (I think that's the correct term) an unbranded version:-
RUU_Bravo_Froyo_HTC_WWE_2.09.405.8_Radio_32.43.00.32U_5.09.00.20_release_140022_signed.exe
I then accepted the OTA update from HTC so that I was on Android Froyo 2.2.
All was well.
I then got anther OTA notification about a week later (2.2.1?).
Downloaded and tried to install, but got the Red Triangle with Exclamation Mark icon.
I read somewhere that I need to Root the phone.
So I did the downgrade from 2.2 to 2.1, changing the HBOOT from something like 0.9x to 0.83.
Used Unrevoked to Root the phone.
Now I get an OTA notification to say that 2.2 is available.
But when I download and try to install, the phone reboots into Clockwork Recovery mode.
What I want
It's simple. I dont want the phone rooted. I want to leave the phone unbranded. I want to be able to accept OTA updates.
...All this was to simply try and debrand the phone, but wasn't expecting such a tough task.
Someone please help!
HTC don't brand their phones, only specific phone operators. If you didn't have any operator logos then you already had an unbranded handset. Having said that, you can't apply an OTA update to a rooted phone as it screws things up
What you need to do is download the 2.29.405.5 RUU and just flash that and you'll be fully up-to-date
Thanks for the info.
I am downloading the 2.29.405.5 RUU as I type.
Will this enable OTA updates in future or will I always have to manually update using this method?
If the RUU installs WITHOUT the use of a gold card then OTA will always work, if you need to use a gold card to flash that RUU then, at present, you'll need to do it this way each time
Okay, so I tried to run the update without a gold card, but got error 131. I presume this indicates that I need a gold card.
I have a gold card, but is there any way to ensure that the future OTA updates can be installed without having to use a gold card?
What else did the error code say? Pretty sure code 140 is wrong CID (need a gold card)
Basically, each phone has a vendor ID. This limits the phone to only install ROMs released for it. The gold card, when in use, masks this code to allow any ROM of any build to be installed. The gold card would then need to be used for all future updates as otherwise they fail
Something happened with the last unbranded OTA update - 2.29.405.5. Even using an gold card the update would fail. Seems Google have changed something to stop people flashing it who aren't truely unbranded
So, to answer your question - If you use a gold card to flash that RUU you MIGHT need to use an RUU each time in future as the OTAs may still fail. We won't know until the next one is released
The error code 131 is Customer ID error. So probably same as 140-CID, therefore I assume I need to use my Gold Card.
I will try using the Gold Card now whilst updating to see if this works ok.
It is disappointing... I wasn't aware that debranding your phone would cause all of these problems. The process was easy and the instructions didn't mention this as a potential downfall. I have my fingers crossed that the next OTA wont fail!
It's only the last OTA that failed, previous ones worked fine so long as the gold card was in use (the gold card can be used as a normal day to day card btw)
Thanks Eddy, you've been a massive help. Was tired of scratching my head for answers... I've been using my gold card as normal anyway so was aware it wasn't much of an impact to update manually... just a bit of a pain of OTAs don't work in future.
How do you know so much? Are you a developer?
I've had my Desire since the phone was released in March/April last year so have a lot of experience. I'm not a developer but I read a lot of threads and this was one that came up a lot when the 2.29.405.5 OTA came out. I do make my own ROMs but they're for my own use (I wouldn't wanna have it take up all my time changing for others!!)
Hopefully it won't be an issue in future OTAs but until one is released we'll never know
On a slightly separate note, can you recommend the best way to Root the Desire... is it using Unrevoked3? Or is this pretty much the only way? Cheers
These days unrEVOked is the only way
I just got this phone 3 days ago and love but im seeing alot of things floating around saying this thing is locked down. I hope this is not true because i love rooting my phones and installing custom roms and kernels. Can anyone confirm or deny this?
aczm1988 said:
I just got this phone 3 days ago and love but im seeing alot of things floating around saying this thing is locked down. I hope this is not true because i love rooting my phones and installing custom roms and kernels. Can anyone confirm or deny this?
Click to expand...
Click to collapse
You may want to read the Incredible S forum as well as just generally look around here.
Moved as not rom development.
Htc devices use nand/emmc write protection, preventing write access to much of the phone's internal memboery
On top of that the latest HTC phones (thunderbolt, inc2, inc3, desire s) released check for a signature on the recovery and kernel images, and throw the device into a "security warning" mode if the signatures are wrong or absent. If it is the recovery that is missing the signature, the phone will still boot but deny access to recovery. If it is the kernel, then the device won't boot.
Older HTC radios had a vulnerability that is exploitable (via scotty2's wpthis), to remove the write protection. Seems to be radios dating before January ~7th.
If such firmware exists and can be found, you guys can go the same route we did with the Thunderbolt, and replace the hboot with an ENG hboot, bypassing the signature checks.
Well this stinks taking mine back tomorrow....
jcase said:
Htc devices use nand/emmc write protection, preventing write access to much of the phone's internal memboery
On top of that the latest HTC phones (thunderbolt, inc2, inc3, desire s) released check for a signature on the recovery and kernel images, and throw the device into a "security warning" mode if the signatures are wrong or absent. If it is the recovery that is missing the signature, the phone will still boot but deny access to recovery. If it is the kernel, then the device won't boot.
Older HTC radios had a vulnerability that is exploitable (via scotty2's wpthis), to remove the write protection. Seems to be radios dating before January ~7th.
If such firmware exists and can be found, you guys can go the same route we did with the Thunderbolt, and replace the hboot with an ENG hboot, bypassing the signature checks.
Click to expand...
Click to collapse
inc3????
?????
Perhaps go for the Samsung Droid Charge which doesn't have these problems. I think that Motorola is opening up their system. Sadly enough HTC used to the best for development.
Hi all,
I love this forum as it's got so much useful info so have just joined as I'm a little unsure of a few things and would really appreciate any help/advice.
Firstly, the big question, can I downgrade from 2.2 to 2.1 on a T-Mobile UK branded device without risking losing the warranty (only got the phone in March - just in case any hardware defects as I had the camera break a month after I got the phone!). I have read numerous guides and they seem to be associated with rooting and what confuses me is the stock roms I'm finding are for 1.14 not 2.1?
The reason is because (there may be an answer to this somewhere but have searched loads and can't find it) the Webkit browser on 2.2 seems to constantly crash. I didn't have the issue on 2.1 and have had the phone repaired twice, the issue occurs straight after a factory reset and is definitely an issue with 2.2 on T-Mobile UK branded firmware at least. T-Mobile UK assured me it was fixed but it certainly isn't as it crashed twice (just disappeared) within 5 minutes of browsing and later in the evening came up with the 'force close' error when browsing.
I loved using the stock provided browser over Opera/Skyfire etc and it was fine on 2.1...
So I am wondering whether T-Mobile UK have just bodged the firmware and whether rooting/debranding would give me a very stable version of webkit?
I had this with my first Wildfire after upgrading in December 2010, after two repairs they couldn't fix it so swapped for a new phone in March. The new phone was fine on 2.1 and this issue occurred again straight after the OTA update of 2.2 last night.
I'm really hoping someone can help with the above?
Many thanks in advance
1.14 is the ROM version number, and, is actually Android 2.1. But, you will not be able to downgrade without root. (Atleast easily).
If you wish to take the complex way out to downgrading to 2.1 without rooting and stuff, you can refer this guide here:
http://forum.xda-developers.com/showthread.php?t=921752
Excellent, many thanks 3xeno. I'll have a go at that. I am tempted to try unbranded 2.2 firmware as by the sounds of it the browser crashing issue might be specific to T-Mobile UK. I can't find other people reporting this issue anywhere and its happened to me with two phones, after 2 repairs with ota updates twice and after multiple factory resets.
Do you use webkit and get any crashes at all? I've tried other browsers but prefer the webkit one when it works, would be great if it played flash content like YouTube etc but I'll do some more research on that...
try dolphin browser HD(has many add-on's) or opera Mobile ,these are the best in the line & opera min for more data saving efficiency
Thanks all, I am having a lot of trouble with the SuperOneClick part though.
I have S-ON on boot and the boot loader that ends in 001 does that affect the ability of SuperOneClick to do Temp Root?
All I get is:
Killing ADB Server...
* server not running *
OK
Starting ADB Server...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
OK
Waiting for device...
OK
Pushing rageagainstthecage...
cannot stat 'C:\Documents and Settings\Marty\Desktop\HTC Downgrade\SuperOneClickv1.5.5\rageagainstthecage': No such file or directory
OK
chmod rageagainstthecage...
Unable to chmod /data/local/tmp/rageagainstthecage: No such file or directory
OK
Running rageagainstthecage...
It just says the last part for ages and never seems to go any further...
Do I need to do S-OFF using Unrevoke or similar?
It shouldn't, since the procedure was performed on an official Froyo release on HBoot 1.01.0001. BTW, You have to press 'Shell Root', not 'Temp Root'. Further make sure USB Debugging and all is on, as the author states.
Hi 3xeno,
I can confirm debugging is on and it is Shell Root I am trying but it just seems to stick on that last stage for ages.
I have the goldcard in, does that matter?
I have also tried unmounting the SD Card as mentioned on another thread?
It shouldn't matter. But, I think this should help you out:
http://forum.xda-developers.com/showpost.php?p=16634853&postcount=139
If you check the 2 posts above it, the user was experiencing similar problems as yours. So, I believe that solution should help.
(That guide is to downgrade to a WWE (Non Branded ROM) with HBoot 1.01.0001, and the 1st step is essentially the same as what you are attempting to do - Downgrade Misc Partition and flash an 'older' ROM)
Good Luck
Thanks 3xeno, I ended up doing the revolutionary thing in those steps and it says S-OFF now with Revolutionary at the top.
I was then able to use a stock RUU and install 2.1 on the phone but it looks different in that the clock widget and icons on the main screen weren't there? It's supposed to be the T-Mobile UK v2.1 firmware I thought?
I thought I might as well use unrEVOKed to root it anyway but I wondered if it was possible to revert it back to the way it was using the factory RUU if I needed any warranty repairs? Would reverting back then change the bootloader screen or is that permanently changed by Revolutionary?
martyp78 said:
Thanks 3xeno, I ended up doing the revolutionary thing in those steps and it says S-OFF now with Revolutionary at the top.
I was then able to use a stock RUU and install 2.1 on the phone but it looks different in that the clock widget and icons on the main screen weren't there? It's supposed to be the T-Mobile UK v2.1 firmware I thought?
I thought I might as well use unrEVOKed to root it anyway but I wondered if it was possible to revert it back to the way it was using the factory RUU if I needed any warranty repairs? Would reverting back then change the bootloader screen or is that permanently changed by Revolutionary?
Click to expand...
Click to collapse
Revolutionary introduces a new userspace issue. It can be fixed by flashing this (Needs Clockworkmod, I hope you had selected Yes to installing Clockworkmod to Revolutionary) -
http://forum.xda-developers.com/showthread.php?t=1156713
To change your bootloader from the Revolutionary one, you will need the HBoot.nb0 file from your TMobile Eclair RUU. Once you obtain that, you will need to follow this guide:
http://forum.xda-developers.com/showthread.php?t=1160251
So, essentially, once you perform this, you are back to factory stock, on a T-Mobile 2.1 ROM. (Essentially summing up my first post, its far easier to root and downgrade. )
Oh, and dont touch Unrevoked. Its not needed at all.
Many thanks 3xeno, really appreciate your help and such quick responses
I actually ended up with root (I think) as the super user icon is in there and I was able to do a nandroid backup on bootup.
Nice to be back to 2.1 though, I might leave it how it is at the moment and keep this info in mind to revert if needed for a warranty claim (fingers crossed it won't be a screen fault!).
One thing I'm really pleased about so far is that it doesn't seem to sync up immediately with my google account and fill my people list with a load of random e-mail addresses which is something I didn't like before.
So far so good, I'll have some fun playing with root now...
Thanks again
Cheers mate.
BTW, You can go to People > Menu Key > View > Check 'Only show Contacts with Phone Numbers'. It may not have synced immediately, but, it will, sooner or later.
EDIT: Did you flash the Sense Fix? If not, then, HTC Setup Wizard (The startup guide which greets you first thing when you boot up after a factory reset) will not work, implying that your Google Account is not setup on the phone. (Or, you'll have to do it manually.) Probably, that's why, its not syncing.
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