Please delete, obsolete
its aliveee... alive i tell u!! amaze is alive
Sent from my Sensation using xda premium
If I'm tmo then no s-off required?
Sent from my HTC Amaze 4G using Xparent Green Tapatalk 2
eggydrums said:
If I'm tmo then no s-off required?
Sent from my HTC Amaze 4G using Xparent Green Tapatalk 2
Click to expand...
Click to collapse
The OP said S-OFF required in big bold and red letters.
---------- Post added at 08:58 AM ---------- Previous post was at 08:52 AM ----------
Snargaflab said:
You need S-OFF to flash this. This zip is flashed through HBOOT. Do not flash it in recovery. I assume no responsibility for any damage done by using this file.
It will work for any HTC Amaze on any carrier as long as you have S-OFF and SuperCID (check the stickies for instructions on how to get these things). I have removed the HBOOT and Recovery from the leaked ICS Rom football posted. That is the only modification to this rom, otherwise it is completely stock and contains all other parts of the update. I think it is a better alternative for anyone with S-OFF because they don't have to reflash recovery and HBOOT after flashing.
http://www.4shared.com/zip/CP5FKMHu/PH85IMG_RUBY_ICS_TMOUS_2145311.html
You have to register for this but it's super quick and easy. It's the best site I know of. If you know of a better place to upload I'll upload it there, I can upload this file in about 3 minutes on my connection. I will not use Filefactory or Dropbox.
Click to expand...
Click to collapse
What about http://goo.im/?
Yeah I know but since this is for tmo why do I need.s-off I'm tmo
Sent from my HTC Amaze 4G using Xparent Green Tapatalk 2
eggydrums said:
Yeah I know but since this is for tmo why do I need.s-off I'm tmo
Sent from my HTC Amaze 4G using Xparent Green Tapatalk 2
Click to expand...
Click to collapse
Ok I see what you're saying.
I THINK you do need S-OFF since HBOOT & Recovery have been removed, but I may be wrong about that....
S-OFF is fairly painless, it's all about timing.
I'm installing this one and got an error when it try to install the nfc it said fail "ERROR: NFC FW file! =106", did anyone else get this?
fullmetal2k said:
I'm installing this one and got an error when it try to install the nfc it said fail "ERROR: NFC FW file! =106", did anyone else get this?
Click to expand...
Click to collapse
are you SuperCID?
is a tmobile stock with s-off locked so didn't think I needed it
but I already install the other one anyways thanks for the help
S-OFF/SuperCID/ENGHBOOT on a Wind Amaze here, get a Fail-PU (106) on the NFC file mentioned also, just FYI
*See Below*
Forgot to mention that the new HBOOT is necessary to flash the nfc update, as far as I can tell the juopunutbear HBOOT and the ENG HBOOT do not understand it, which is why it reboots after installing the new bootloader and before flashing nfc. nfc seems to work fine without it. Will add to original post. Also gonna repost with it ripped out as well so it doesn't throw an error, even though it doesn't matter.
Snargaflab said:
Forgot to mention that the new HBOOT is necessary to flash the nfc update, as far as I can tell the juopunutbear HBOOT and the ENG HBOOT do not understand it, which is why it reboots after installing the new bootloader and before flashing nfc. nfc seems to work fine without it. Will add to original post.
Click to expand...
Click to collapse
Champion mate, thankyou
Can't confirm NFC as yet, but even with a 'partition error' after flashing on the ENG HBOOT, the ROM functions perfectly. You can root just by flashing the usual SU.zip.
Thanks for the good work!
Isnt SuperSID just for if you are on another carrier? IE: If I have a T-Mobile Amaze all I need is S-Off?
Since this is basically a stock ROM, I assume that everything works fine with it?
EDIT: I always get confused too; hboot is the same thing as the stock bootloader right? Hold power + volume down?
porkchopexpress said:
Isnt SuperSID just for if you are on another carrier? IE: If I have a T-Mobile Amaze all I need is S-Off?
Since this is basically a stock ROM, I assume that everything works fine with it?
EDIT: I always get confused too; hboot is the same thing as the stock bootloader right? Hold power + volume down?
Click to expand...
Click to collapse
You shouldn't need SuperCID on the T-Mobile one really, but if you run into issues it doesn't hurt to have it on there. Plus if Wind get 4.0.4 with Sense 4.0, you won't have to be jelly
HBOOT is the white screen, so yeah the stock bootloader. An ENG (Engineering) one unlocks more and allows you to send a wider variety of commands
juzz86 said:
You shouldn't need SuperCID on the T-Mobile one really, but if you run into issues it doesn't hurt to have it on there. Plus if Wind get 4.0.4 with Sense 4.0, you won't have to be jelly
HBOOT is the white screen, so yeah the stock bootloader. An ENG (Engineering) one unlocks more and allows you to send a wider variety of commands
Click to expand...
Click to collapse
Even though its not needed to do this, just to satisfy my own personal sense of curiosity, how do you get to an ENG boot screen?
Edit: I assume we are still renaming this ph85img.zip as you would with the first ROM that leaked?
You don't need SuperCID if your on T-Mobile
You don't need S-OFF to flash this
You could flash this on S-ON.
Thanks worked for me, Still have the old HBOOT and CW Recovery and ICS!
Adjust said:
You don't need SuperCID if your on T-Mobile
You don't need S-OFF to flash this
You could flash this on S-ON.
Click to expand...
Click to collapse
I'm not 100% but since I have modified the file (presumably breaking it's signature) I do not believe it will flash with S-ON. None of the files inside are modified, some are just removed, but the file itself is modified by those removals. As far as I know if even one byte of this file is changed it will not flash with S-ON. If someone would be willing to test with S-ON then I will update my post if necessary, I have no way to test personally. I do not expect it to work but it is definitely a possibility. If it does work, it will only work a T-Mobile Amaze. If it will not work, it will not damage your phone. It will fail a signature check before it installs anything. If it does not fail that signature check then the entire thing will flash as it is verified in it's entirety at the beginning of the process.
juzz86 said:
Champion mate, thankyou
Can't confirm NFC as yet, but even with a 'partition error' after flashing on the ENG HBOOT, the ROM functions perfectly. You can root just by flashing the usual SU.zip.
Thanks for the good work!
Click to expand...
Click to collapse
The reason that it says partition error is because nfc flashes to a partition and it fails. This is why it still works fine even with such a seemingly menacing error. I have ripped it out until I can figure out what I talk about in my first post. No one should receive any error now.
All right guys, I have s-on with unlocked bootloader, on tmobile, would like to test but I don't wanna risk my phone
Sent from my HTC Amaze 4G using Xparent Green Tapatalk 2
Related
Future of this rom and me - https://plus.google.com/u/0/100983447046094793882/posts/7YtTFWWgT1C
Hope this helps people others comming sooon i have slow internet
Let's hope that nobody will be needing these with the exception of obtaining S-OFF and ROM production.
I added some tags for you too.
All ruus released enjoy
md5's for the ruu's added so enjoy but remeber you need to htc relock your boot loader before you can restore
Have you are anyone tested the relock? Frrom what I remember on previous ones I thought you could not relock like the nexus one.
But basically relock then flash these thru bootloader and you are back to the way has came out the box?
M9x3mos said:
Have you are anyone tested the relock? Frrom what I remember on previous ones I thought you could not relock like the nexus one.
But basically relock then flash these thru bootloader and you are back to the way has came out the box?
Click to expand...
Click to collapse
yep you got it and me and binary both tested the relock scripts they are good to go
xboarder56 said:
yep you got it and me and binary both tested the relock scripts they are good to go
Click to expand...
Click to collapse
I tested that script on an unbiased Windows 7 machine.
Unbiased means that it had nothing but the drivers installed. No adb or fastboot files.
I wanted to clean it up and make it look better but x was in a hurry to release it for whatever reason.
Well clean up and I will reupdate it
Sent from my HTC Amaze 4G using xda premium
xboarder56 said:
Well clean up and I will reupdate it
Sent from my HTC Amaze 4G using xda premium
Click to expand...
Click to collapse
Nah. It's it's not broke, don't fix it.
Lol ok
Sent from my HTC Amaze 4G using xda premium
more various roms/ruus coming wendsday
more ruu's released
Sorry for sounding like a n00b and redundancy but just wanted to make sure I understand this right before I make any changes on device.
The relocker posted by xboarder and binary, does that completely reverse the HTC bootloader unlock done the HTC dev site?
Assuming it does, that does mean we can get the regular updates to device again?
Sorry again if is redundant but just want to make sure there is a 100% way of returning to stock software very much like my vibrant / g2 / hd2
TheArtiszan said:
Sorry for sounding like a n00b and redundancy but just wanted to make sure I understand this right before I make any changes on device.
The relocker posted by xboarder and binary, does that completely reverse the HTC bootloader unlock done the HTC dev site?
Assuming it does, that does mean we can get the regular updates to device again?
Sorry again if is redundant but just want to make sure there is a 100% way of returning to stock software very much like my vibrant / g2 / hd2
Click to expand...
Click to collapse
yes it will let you do updates again if you follow the guide
I've tried installing this via hboot both unlocked and relocked and it doesn't actually do anything. it checks the image then just goes back to hboot. Any Idea what I'm doing wrong?
I am trying to get my Telus Amaze back to stock. I have re locked the phone it says so in the hboot menu. I have downloaded the RRU for Telus and it is on the root of my SD card. When I boot into hboot I see the progress bar in blue on the right hand side, then it goes into yellow verifiying, then it just stops no option to install the update.... It just isn't working.. any thoughts?
gmarcoux said:
I've tried installing this via hboot both unlocked and relocked and it doesn't actually do anything. it checks the image then just goes back to hboot. Any Idea what I'm doing wrong?
Click to expand...
Click to collapse
I am in the same boat. Let me if you figure it out.
hello to every one, can anyone help me with installing the stock rom?
the problem is that after i relock my phone & put the RUU file in the root folder ( with root explorer), i turn of, got in to the bootloder and nothing happened.
what do i need to do from here?
Sent from my HTC_Amaze_4G using XDA App
So, if I were to flash the 1.26 or 1.35, I wonder if I'd get working WiFi calling? Anyone that is still on 1.36.531.4, does your WiFi calling still work?
ok, so i went through the s-off process and completed it successfully. It asked me if I wanted to flash the jb-hboot.zip which I said yes. Now, when I boot into hboot it has this ugly pink bar accross the top that says "juno..." (the name of the team). I am currently on the new firmware running BAMF Evita sense 4. Is there a stock ics hboot or something i can put back in its place that will leave s-off, be compatible with new firmware and not give custom labels accross the top?
Please help....
jbeitel said:
ok, so i went through the s-off process and completed it successfully. It asked me if I wanted to flash the jb-hboot.zip which I said yes. Now, when I boot into hboot it has this ugly pink bar accross the top that says "juno..." (the name of the team). I am currently on the new firmware running BAMF Evita sense 4. Is there a stock ics hboot or something i can put back in its place that will leave s-off, be compatible with new firmware and not give custom labels accross the top?
Please help....
Click to expand...
Click to collapse
Technically, you could just reflash the leaked RUU then and you will still have S-off. Changing Hboots , won't affect S-off, Numerous threads have popped up with just radio's and Hboots to flash. Just be careful and don't mix and match Radios and Hboots to avoid trouble.
mjh68 said:
Technically, you could just reflash the leaked RUU then and you will still have S-off. Changing Hboots , won't affect S-off, Numerous threads have popped up with just radio's and Hboots to flash. Just be careful and don't mix and match Radios and Hboots to avoid trouble.
Click to expand...
Click to collapse
do I have to relock anything like when I upgraded to the new ics firmware? I was hoping for a straight forware ph98img.zip flash. i know, thats lazy but easy.
IMO, leave it. Put up with eye sore. If the flash to the stock one goes belly up, you will brick the phone. Leave it til you need to go back to an S-On device.
Snuzzo said:
IMO, leave it. Put up with eye sore. If the flash to the stock one goes belly up, you will brick the phone. Leave it til you need to go back to an S-On device.
Click to expand...
Click to collapse
Technically true, but really as long as he doesn't pull the plug while its loading the Hboot its not a great danger.
---------- Post added at 12:03 PM ---------- Previous post was at 12:00 PM ----------
jbeitel said:
do I have to relock anything like when I upgraded to the new ics firmware? I was hoping for a straight forware ph98img.zip flash. i know, thats lazy but easy.
Click to expand...
Click to collapse
I am pretty sure , their hboot is already relocked . So shouldn't have to relock , I went all the way back to GB and used the full exe RUU and relocked since I didn't know that it was locked initially and it ran just fine.
I would try without relocking , it will either run or fail before it starts doing anything.
Thank you mjh. Yes it is relocked & again leave it as is. Trust me you will thank me later. No need for unlock codes anymore and just waiting for roms to be rebased and official OTA(not for the actual OTA but for kernel source if released).
you guys know how to frustrate a guy, geez. What a great world that everyone can have their own opinion. Now, who's do I want to have?
I know exactly how you feel. Cant make up my mind what I want to do either. Currently on ICS S-OFF displaying Tampered/Locked
Do I RUU back to GB and flash the ENG Hboot?
Do I go ahead and flash jb_hboot? And which one is it actually. There have been way to many threads and posts on S-OFF and a bunch of different answers.
Do I leave it alone and wait to see what happens with the next release?
In some ways it would be nice to be back on Hboot 2.11 and have ENG S-off but is it worth it? Wont really know until the next official release comes out.
jbeitel said:
you guys know how to frustrate a guy, geez. What a great world that everyone can have their own opinion. Now, who's do I want to have?
Click to expand...
Click to collapse
I am not telling not to flash, just telling you after S-off and using their Hboot it is already locked, but you can still flash the stock RUU. I did and haven't had any issues , but I didn't realize it was already locked so relocked and unlocked by HTC dev without knowing it . I am still tempted to flash the eng hboot , but not sure if I really have a need to.
mjh68 said:
I am not telling not to flash, just telling you after S-off and using their Hboot it is already locked, but you can still flash the stock RUU. I did and haven't had any issues , but I didn't realize it was already locked so relocked and unlocked by HTC dev without knowing it . I am still tempted to flash the eng hboot , but not sure if I really have a need to.
Click to expand...
Click to collapse
whats the big deal with the engineering hboot? is it different or is that the standard one in the ruu?
Snuzzo said:
No need for unlock codes anymore
Click to expand...
Click to collapse
There is more difference than this(allows more commands to be ran in prompts) but with an ENG hboot, you can keep it locked and s-off, along with still being able to flash anything your heart desires. ALTHOUGH if you wish to go back to s-on, flash an RUU of your choice first. As when you do write secureflag and a few reboots on an ENG hboot, you could brick.
Leave the hboot they give you. The tag might be annoying but it is better than having to re-unlock to use fastboot commands.
Why is un- re locking not ideal? It takes 2 minutes.
Sent from my v6 supercharged Rezound.
AJMetal87 said:
Why is un- re locking not ideal? It takes 2 minutes.
Sent from my v6 supercharged Rezound.
Click to expand...
Click to collapse
Scotty posted earlier if your S-OFF then unlock and relock again it will alway show relocked again unless you RUU then S-ON and then S-OFF again. If you S-OFF and don't unlock it and RUU it will say locked but its best to use the patched hboots supplied to be able to use certain fastboot commands that way you don't have to unlock and not have a problem with it saying relocked.
Sent from my ICS Rezound
LakerStar25 said:
Scotty posted earlier if your S-OFF then unlock and relock again it will alway show relocked again unless you RUU then S-ON and then S-OFF again. If you S-OFF and don't unlock it and RUU it will say locked but its best to use the patched hboots supplied to be able to use certain fastboot commands that way you don't have to unlock and not have a problem with it saying relocked.
Sent from my ICS Rezound
Click to expand...
Click to collapse
Aside of the text difference on the bootloader and potential warranty comprimising, is there any other downfall?
No downfall. But again, nor needed to unlock if s-off.
Sent from my ADR6425LVW using XDA
I'm not trolling or trying to start a argument, but if that's a big deal to you to have the pink junabear banner across your hboot screen then you should have never s-off. I mean really. Who sits there and stares at the hboot screen and decides that it doesn't look good. Lmao.
Sent from my ADR6425LVW using XDA
Especially when the stock hboot uses the same color banner but says locked instead?
Via Rezound using XDA Premium
GB
Anyone who was on Gingerbread when the did S-Off does *NOT* have the Juououuoouououpnutbear logo; just standard Eng HBoot.
This would be me.
Bump. I need the stock Hboot to send back to Verizon. The GB hboot if anyone has it please.
Hey All,
I am trying to install the OTA for ICS that was released by Rogers today for my EVO 3D.
I am rooted and unlocked but with the stock Rogers ROM and I also have S-OFF.
The problem I am running into is that I am able to download the upgrade but when I go into HBoot and try to apply it I get a signature verification failed.
Originally I thought it might have been a bad download so I downloaded it a 2nd time, same result.
So I thought, what the hell, I will turn off the signature check and try it again. This time I get an error that the 'assert failed: check_cid(getprop("ro.cid").' and the installation aborted.
Does anyone have any insight into why this would fail? I am hoping to apply this but not sure why its a no go.
Thanks for the help in advance.
Cheers, Crash
Have you ever changed your cid? run "fastboot getvar cid" and post what it says. If your cid is original for rogers, the ota may not be working because you are s-off.
Hey @patrick92260
I have not checked my CID, not really sure how actually.
In order for me to run that command I would have to be hooked up to ADB I assume? If so thats going to need to wait until I get home tonight to try that and give you the results, unless there is another way I can run that command?
Thx for the reply
Yeah it's done through ADB. If you don't really know what the cid is, you probably haven't changed it. If you have the stock recovery, then the reason the ota isn't working has to be because you are s-off. you will probably have to wait for an RUU to upgrade to ICS.
Makes sense then. Would setting S-ON make it so I can apply it? Or would that not be worth the effort?
Honestly I can wait a bit longer, we have been waiting this long for it
Thx for the help.
But you should be able to get back to S-ON by flashing Gingerbread RUU, no?
If you originally used revolutionary to get s-off, then you have radio s-off which is the highest level of s-off you can have and i would not recommend trying to set it back to s-on. i also have a rogers evo 3d and i am using the asian RUU ICS and it works fine while letting me keep s-off after flashing it so i would recommend using that RUU if you want ICS.
---------- Post added at 01:10 PM ---------- Previous post was at 01:07 PM ----------
SaHiLzZ said:
But you should be able to get back to S-ON by flashing Gingerbread RUU, no?
Click to expand...
Click to collapse
If he has radio s-off you can flash any RUU you want and it will not turn it back to s-on. Radio s-off is basically permanent since it removes the data in the S58 section of the phone. The fake s-off is the one you need to be careful with which is usually done by using a hacked hboot.
patrick92260 said:
If your cid is original for rogers, the ota may not be working because you are s-off.
Click to expand...
Click to collapse
Bull**** Bull**** Bull****.
For getting OTA you need NOT rooted and NOT deodexed Stock-rom+stock recovery.
Don't try to make S-ON, it is great chance to brick the phone.
And your CID you can get with cid getter from the market.
Patrik, stop it plz.
Is there any risk or advantage to used to Asia one? Not sure I want to have that one my phone over the NA ones.
Would there not be a RUU or this Rogers release? Maybe I should just say the hell with it and just ROM it?
Kemanorell said:
Bull**** Bull**** Bull****.
For getting OTA you need NOT rooted and NOT deodexed Stock-rom+stock recovery.
Don't try to make S-ON, it is great chance to brick the phone.
And your CID you can get with cid getter from the market.
Patrik, stop it plz.
Click to expand...
Click to collapse
lol good one, so why would my evo 3d not flash the ota with a completely stock rom and recovery then with no root? only thing it had was s-off.
---------- Post added at 01:28 PM ---------- Previous post was at 01:24 PM ----------
Crash1912 said:
Is there any risk or advantage to used to Asia one? Not sure I want to have that one my phone over the NA ones.
Would there not be a RUU or this Rogers release? Maybe I should just say the hell with it and just ROM it?
Click to expand...
Click to collapse
It's a toss up if the RUU for rogers or the europe ICS ever shows up here. I am using the asian one and don't really notice any difference over the rogers or europe update. If you have radio s-off you can always downgrade by flashing a gingerbread RUU if you don't like the asian ICS RUU.
I had to run the Rogers gb ruu 1.20.631.2. It then update to 631.3 when I checked for updates. I then booted checked for updates again and it updated to ics. Now I'm running official Rogers ics but as I said I had to roll all the way back 1.20.631.2 and update all the way up from there.
And it does update the hboot but you can downgrade it with ruu previously mentioned.
Sent from my HTC EVO 3D X515a using Tapatalk 2
healer82 said:
I had to run the Rogers gb ruu 1.20.631.2. It then update to 631.3 when I checked for updates. I then booted checked for updates again and it updated to ics. Now I'm running official Rogers ics but as I said I had to roll all the way back 1.20.631.2 and update all the way up from there.
And it does update the hboot but you can downgrade it with ruu previously mentioned.
Sent from my HTC EVO 3D X515a using Tapatalk 2
Click to expand...
Click to collapse
Please link how this is done. I quickly scammed google, and couldnt find how to roll back to this. Looking to do ICS update today sometime.
js593 said:
Please link how this is done. I quickly scammed google, and couldnt find how to roll back to this. Looking to do ICS update today sometime.
Click to expand...
Click to collapse
Somewhere in the development thread there is a thread with shipped ruus already covered to pg86img.zip. Just find the Rogers one and put it on the root of your sd card and boot into bootloader. It will detect it and install 1.20.631.2 then just manually check for updates under about phone. The first update should be 1.20.631.3 which is 9.35mb then xcheck again and it's the ics update around 306 mb. Sorry I can't link to it you'll have to search the development forum. I've had it since it was posted way back when on my phone.
Make sure it's renamed PG86IMG.zip
http://forum.xda-developers.com/showthread.php?p=16450859
Sent from my HTC EVO 3D X515a using Tapatalk 2
healer82 said:
Somewhere in the development thread there is a thread with shipped ruus already covered to pg86img.zip. Just find the Rogers one and put it on the root of your sd card and boot into bootloader. It will detect it and install 1.20.631.2 then just manually check for updates under about phone. The first update should be 1.20.631.3 which is 9.35mb then xcheck again and it's the ics update around 306 mb. Sorry I can't link to it you'll have to search the development forum. I've had it since it was posted way back when on my phone.
Make sure it's renamed PG86IMG.zip
http://forum.xda-developers.com/showthread.php?p=16450859
Sent from my HTC EVO 3D X515a using Tapatalk 2
Click to expand...
Click to collapse
Would this be it?
http://forum.xda-developers.com/showthread.php?p=22501510&highlight=rogers#post22501510
js593 said:
Would this be it?
http://forum.xda-developers.com/showthread.php?p=22501510&highlight=rogers#post22501510
Click to expand...
Click to collapse
That seems to be the one yes.
Sent from my HTC EVO 3D X515a using Tapatalk 2
Ive tried to do this, after downloading it and putting it in the root directory of my phone. Hboot sees the image, stalls there for a few seconds then continues. nothing has happened. Ive tried installing it from CWM, no difference. I think i may need a bit more help then this. After it was detected, i did go and see if it was downgraded in the ABOUT, but it sits at .3 still.
Any ideas?
Okay, so for those people out there that are looking to do this, here's the functional way it worked for me (no errors, nothing happened during the update)
Download the .exe file,
EXECUTE the exe file from windows while the phone is plugges in. This will revert back to .2
Put phone into a wireless network once back up and running.
Update the phone as neccessary.
After the update, i noticed my Hboot when to 1.53.007. Now we just need to wait for a root.
Also, when i went into Recovery from Hboot, i noticed that it didnt do anything, sat there with a pic of my 3D and it had a red exclamation point. should that happen?
no luck
hi i have tried every method here with no go. i have s-on and phone is rooted. can some one post a working rom or something for the love of android!
looks like it was the bootloader it needs to be relocked using rootevo3dnew.zip. which will allow you to downgrade using the ruu file in windows. followed by the 2 updates in about phone and i got the ICS yay! if you have trouble search youtube for the video on "relocking evo 3d bootloader" it was easy, good luck ppl.
For those looking to return their phones to stock or borked their phones trying to update firmware only without the appropriate ROM.
http://dl3.htc.com/application/RUU_...10.38m.1157.04_release_336982_signed_2(2).exe
Enjoy.
Sent from my HTC One using Tapatalk 2
Htein said:
For those looking to return their phones to stock or borked their phones trying to update firmware only without the appropriate ROM.
Sent from my HTC One using Tapatalk 2
Click to expand...
Click to collapse
Hmmm.. I can't help but assume this is mentioning me specifically! Lol..
Thanks for finding and posting this, I'm super excited to finally go to stock 4.3!
I've got to have that Wi-Fi calling.
Sent from my HTC One.
Htein said:
For those looking to return their phones to stock or borked their phones trying to update firmware only without the appropriate ROM.
http://dl3.htc.com/application/RUU_...10.38m.1157.04_release_336982_signed_2(2).exe
Enjoy.
Sent from my HTC One using Tapatalk 2
Click to expand...
Click to collapse
thanks for this...
now we need someone to decrypt this and give us the rom.zip file.. :silly: PLEASE..
bootloader needs to be re-locked to use this right? S-on or S-off doesn't matter does it?
gwingzero said:
bootloader needs to be re-locked to use this right? S-on or S-off doesn't matter does it?
Click to expand...
Click to collapse
Dont forget stock recovery as well
Sent from my HTC One using SinLess Rom
yea forgot to mention that looking for it now.
so, to recap, re-lock bootloader, flash stock recovery then run this file and that should put me back to 100% bone stock on T-mo 4.3, sound about right?
---------- Post added at 09:04 AM ---------- Previous post was at 09:04 AM ----------
yea forgot to mention that looking for it now.
so, to recap, re-lock bootloader, flash stock recovery then run this file and that should put me back to 100% bone stock on T-mo 4.3, sound about right?
jay661972 said:
Dont forget stock recovery as well
Click to expand...
Click to collapse
You do NOT need stock recovery to flash an RUU s-off.
With S-OFF you don't need to do anything. Plug your phone in and run the RUU. I just did this yesterday. All I had to do is flash TWRP and I'm right back to rooted.
Behold_this said:
You do NOT need stock recovery to flash an RUU s-off.
Click to expand...
Click to collapse
did not know that, thanks for that info. i always do stock recovery and lock bl, now i can skip step. thanks mate
can this be flashed on a AT&T HTC One, just left them and love the phone. BL is unlocked, have flashed the T-Mobile radio, but my phone continuously drops to EDGE, then back to LTE and 4G, I thought the baseband puts the frequencies needed for optimal T-Mobile network compatibility, namely the WCDMA 1700....im in NYC and i know they updated the towers here so 4G works on GSM1900, but having that WCDMA 1700 would be best. I guess there are other things T-mobile does to tweak the network i guess on the build.prop or whatever? not sure? any ways, any inout would be greatl appreciated,
just so anyone is confused. this was super easy to do to completely restore to a factory phone.
I was on TWRP w/ ARHD 22 ROM, unlocked bootloaded thru htcdev, S-On. here is all i had to do to flash this (super simple)
fire up fastboot on phone
verify fastboot via cmd (fastboot devices)
enter fastboot oem lock
phone reboots and i now have **Tampered** **Relocked** on bootloader
leave phone in fastboot and run the RUU file and 10 min later
factory phone
thanks all for posting this, I'll be re-rooting and flashing custom recovery soon but so nice to have wifi calling back.
I keep getting an Error 155. I've googled around and I can't seem to find anything that works. At my wits end here. Anyone?
I used this today and having trouble unlocking the boot loader. Do I need to get a new code?
kevace1 said:
can this be flashed on a AT&T HTC One, just left them and love the phone. BL is unlocked, have flashed the T-Mobile radio, but my phone continuously drops to EDGE, then back to LTE and 4G, I thought the baseband puts the frequencies needed for optimal T-Mobile network compatibility, namely the WCDMA 1700....im in NYC and i know they updated the towers here so 4G works on GSM1900, but having that WCDMA 1700 would be best. I guess there are other things T-mobile does to tweak the network i guess on the build.prop or whatever? not sure? any ways, any inout would be greatl appreciated,
Click to expand...
Click to collapse
Yes but you need s-off and change your cid and mid to match a tmo phone
Sent from my HTC One using Tapatalk 2
Thanks for this. Just used it to upgrade my son's tmo one.
Sent from my HTCONE using XDA Premium 4 mobile app
So how can I do both, kinda found the CID type thread but don't see anything about MID, can you point me to the right direction? I'm assuming S-off would be necessary?
Sent from my HTC One using xda app-developers app
So I've got a newbie q: I'm currently on 1.27.531.11, can I just flash this version just like I would an OTA update and keep my contacts, messages, settings, etc. intact? Or is this a complete wipe?
Janhaus said:
So I've got a newbie q: I'm currently on 1.27.531.11, can I just flash this version just like I would an OTA update and keep my contacts, messages, settings, etc. intact? Or is this a complete wipe?
Click to expand...
Click to collapse
RUU is complete wipe .. if you want to keep your setting you have to take the /OTA
Hi, I converted my phone to GPE. I tried to run this RUU with no luck I always get error 155. It is unlocked and S-OFF. I tried the tmobile cid, super cid, t mobile stock recovery, relock the bootloader. What should I do can some one explain step by step?
I got a question about the ruu. I have a Att phone I'm selling to a T-Mobile guy could I make the phone officially a T-Mobile device by using this ruu??
Sent from Flo Jo 7-13 using Tapatalk 4
I have an HTC rezound that was unlocked and rooted by HTC dev method. It has the 2.28.0000 hboot and every ruu I find and try to use tells me hboot failed because mine is to new. I have searched for 2 days on this subject and the reason I am returning to stock is because I can't get into diag mode to flash to cricket. When I enter ##diag it says no network. ##program does nothing either. If anyone could point me in the right direction it would be appreciated.
Sent from my Galaxy Nexus using xda app-developers app
jhr5474 said:
I have an HTC rezound that was unlocked and rooted by HTC dev method. It has the 2.28.0000 hboot and every ruu I find and try to use tells me hboot failed because mine is to new. I have searched for 2 days on this subject and the reason I am returning to stock is because I can't get into diag mode to flash to cricket. When I enter ##diag it says no network. ##program does nothing either. If anyone could point me in the right direction it would be appreciated.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
All ruu's posted here dont work....pm me...i have all the needed files...and i'll guide you through this....your big error that your doing is your going to need to relock the bootloader before doing anything...leaving it unlocked will cause a soft brick
I already relocked the bootloader and it still failed. I am not a total noob flashed lots of radios, hboots, built sense ROMs. This one has me stumped though.
Sent from my Galaxy Nexus using xda app-developers app
jhr5474 said:
I already relocked the bootloader and it still failed. I am not a total noob flashed lots of radios, hboots, built sense ROMs. This one has me stumped though.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
ok an ruu is an exe file not a zip....again i have the files if needed and can show you how...also what you may not be doing whille running the ruu is placing the phone in bootloader then press the fastboot tab...once it says fastboot usb then run the ruu.exe
He is S-ON guys.
jhr5474 said:
I already relocked the bootloader and it still failed. I am not a total noob flashed lots of radios, hboots, built sense ROMs. This one has me stumped though.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
and yes you must be s-off to do this thanks @Flyhalf205
REV3NT3CH said:
and yes you must be s-off to do this thanks @Flyhalf205
Click to expand...
Click to collapse
So, the OP cannot do the full RUU thing.
Can't he just do a factory reset and then boot to one of the custom recoveries and re-flash the latest OTA?
cheers,
john
No op's links have broken software...I have the needed files on my dropbox and media fire account...and no all factory reset does is wipe all data and setting for ROM...and may cause custom ROMs to not boot...ota is only achievable if on stock ROM and there is an update...however I have all those proper files too
Sent from my R3D D347H 4.3 using xda app-developers app
Got it.
One last question, though, since I'm not that savvy...
REV3NT3CH said:
ota is only achievable if on stock ROM and there is an update...
Click to expand...
Click to collapse
...I didn't upgrade to the latest OTA from a previous OTA---I was on the Global Leak---and I installed the ROM found here with absolutely no problems after manually upgrading the firmware to the latest, which is what the OP is on. Fwiw, that ROM still appears to be available via the link in Post 1 of that thread.
cheers,
john
jrredho said:
Got it.
One last question, though, since I'm not that savvy...
...I didn't upgrade to the latest OTA from a previous OTA---I was on the Global Leak---and I installed the ROM found here with absolutely no problems after manually upgrading the firmware to the latest, which is what the OP is on. Fwiw, that ROM still appears to be available via the link in Post 1 of that thread.
cheers,
john
Click to expand...
Click to collapse
that isnt a pure stock ota bud...thats a rom made with includes from it and rooted
This might sound stupid, but your objective here really is to get stockish, correct? With your HBoot you could use this ROM:
http://forum.xda-developers.com/showthread.php?t=2260154
Just make sure to flash boot.img afterwards via fastboot. This is as close to pure stock (only root added) as you can get without S-Off or other trickery. It should suffice for the requirements of the OP.
Sent from my Nexus 4 using XDA Premium 4 mobile app
I've been trying to deal with this problem over in the liquidsmooth thread, but it's clear now that my problems are not related specifically to the rom and that thread isn't really the place for it.
I've lost all cell connectivity. Calls, texts, data, everything. The liquid rom had been working for me for over a week. I've reverted to previous roms both with new flashes and using restore files. I've tried a different recovery. Every time, it acts like I don't have a sim card.
I was suspecting that my sim might be bad, but back on the liquidsmooth thread, it was suggested that I need to RUU back to stock and start over. I'd be willing to do that except the only way suggested was really complicated. I'm S-on and it included ubuntu and the wire trick to get s-off, which I'm hesitant to do. I searched and found another thread with instructions to run an RUU while still s-on, and it seems like it would have worked except that my hboot is newer than the RUU used, and I've been unable to find a newer one.
I tried flashing the stock rom above and flashing the stock recovery that I had from when I first rooted several months ago. It still thinks I don't have a sim card, but otherwise it booted fine until I re-locked to bootloader. Then it wouldn't boot anymore. I guess it still knows that those versions of hboot, the recovery, and the rom don't quite go together.
Is there an RUU that will work with hboot 2.28 to "un-root" my phone without downloading a second operating system and performing surgery on my phone? Are the correct stock rom and recovery out there that I can flash and re-lock? Is there a way to know if that is actually the problem if if it is just my sim card? Are there any other ideas to get my phone functioning again?
Please help!
vigor pvt ship s-on rl
hboot-2.28.0000
radio-2.23.10.0123r/2.23.1.124r
OpenDsp-v1.4.6.0.7708.00.0507
eMMC-boot
Sep 20 2012,17:40:22
There is no RUU for your hboot, need to s-off...
If your SIM is bad, get a new one from Verizon.
Also, is the battery cover on?
Sent from my ADR6425LVW using Tapatalk
mjones73 said:
There is no RUU for your hboot, need to s-off...
If your SIM is bad, get a new one from Verizon.
Also, is the battery cover on?
Sent from my ADR6425LVW using Tapatalk
Click to expand...
Click to collapse
On that note... Are using a stock battery cover? Some aftermarket ones are questionable at best. Also, try another SIM, Verizon will replace it free.
Sent from my Nexus 4 using XDA Premium 4 mobile app
acejavelin said:
On that note... Are using a stock battery cover? Some aftermarket ones are questionable at best. Also, try another SIM, Verizon will replace it free.
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I tried using a friend's good sim card and it didn't work. Yes, I'm using the stock battery cover. I guess I'll have to do s-off so I can RUU back to stock.
Ugh . . . This has become so much more than I ever intended to get myself into
amschmid said:
I tried using a friend's good sim card and it didn't work. Yes, I'm using the stock battery cover. I guess I'll have to do s-off so I can RUU back to stock.
Ugh . . . This has become so much more than I ever intended to get myself into
Click to expand...
Click to collapse
You didn't answer my question, is it on the phone while you're testing your connection. Dumb question I know, antenna's are in it though and I've caught people leaving it off and not getting a signal then wondering why...
mjones73 said:
You didn't answer my question, is it on the phone while you're testing your connection. Dumb question I know, antenna's are in it though and I've caught people leaving it off and not getting a signal then wondering why...
Click to expand...
Click to collapse
Sorry, I missed that part of the question. We did it pretty quick, but I think I did put the battery cover. Also, it's not just getting no signal, there is an icon in the notification bar and a big message on the lock screen says I have no sim card at all. That has never happened before, even with the battery cover off. As I look back I realize I failed to mention that important detail. I guess it still couldn't hurt to try a brand new sim card before taking the plunge into s-off. Even if that isn't the problem, at least I'll know for sure, and as you pointed out, its easy and free.