I found older threads with references to full 2.17 Firmware minus HBoot
like this http://dev-host.org/svsae25h2v0n/PG86IMG-2.17.651.5_Firmware_Only.zip
But it appears to not roll back.
My phone still says "Virgin Mobile" on lock screen.
Applying the 2.17 above seems successful but I don't think it is.
Is Freeza's patch forward only?
I also saw mixed messages of folks running with "Virgin Mobile" on their screen that said they never applied Freeza's patch.
Do all ICS Leaked ROM say Virgin Mobile or is this only in the Freeza Patch firmware.
Is there a FULL Stock ROM (minus HBOOT [I'm on 1.4 and want to stay there]) that can reset everything?
I'm confused.
mswlogo said:
I found older threads with references to full 2.17 Firmware minus HBoot
like this http://dev-host.org/svsae25h2v0n/PG86IMG-2.17.651.5_Firmware_Only.zip
But it appears to not roll back.
My phone still says "Virgin Mobile" on lock screen.
Applying the 2.17 above seems successful but I don't think it is.
Is Freeza's patch forward only?
I also saw mixed messages of folks running with "Virgin Mobile" on their screen that said they never applied Freeza's patch.
Do all ICS Leaked ROM say Virgin Mobile or is this only in the Freeza Patch firmware.
Is there a FULL Stock ROM (minus HBOOT [I'm on 1.4 and want to stay there]) that can reset everything?
I'm confused.
Click to expand...
Click to collapse
Also want to know. I have been looking for a way back. my service isn't what it used to be. i have emailed some people for help to find a solution to this problem. There are cases where i cant get phone calls or text msgs and need to reboot my phone.
if you use the qpst hack to increase your volume. while you in qpst you can change the banner. mines been xXx since the day i got it. not hard.
Would love to know a solution to this as well.
kaos420 said:
if you use the qpst hack to increase your volume. while you in qpst you can change the banner. mines been xXx since the day i got it. not hard.
Click to expand...
Click to collapse
I think it's more than just the "Banner".
It's the firmware that went along with that Banner change we want to set back.
I think it's a license key thing and the old 2.17 will not flash back or flash over the patch.
I just confirmed I've lost VPN due to applying the patch.
I restored GB ROM that had VPN working and it no longer does.
Freeza HELP !!!
I did send Freeza a PM and asked if he could reply here.
If you s-off try running an ruu. You can always flash the older hboot zip I believe.
#Root-Hack_Mod*Always\
laie1472 said:
If you s-off try running an ruu. You can always flash the older hboot zip I believe.
#Root-Hack_Mod*Always\
Click to expand...
Click to collapse
I was thinking of that. Worried I might get myself in a deeper hole
I'm 1.4 Hboot with S-OFF
What is the newest Sprint RUU that still had 1.4 Hboot?
There is 2.17, 2.08, and 1.13 RUU's
Is there such things as RUU's that are rooted?
Thanks
Ass long as your s-off ruu is the way to go.I do it all the time.
Sent from my PG86100 using XDA
As far as the latest ruu that has the 1.4 hboot I'm thinking anything under the 2.17 update. I know for a fact that 2.17 has the hboot1.5 however if you have rev-s-off you can still flash the 2.17 and flash the old h-boot.zip to get it back. Also no full factory ruu's are not rooted.
#Root-Hack_Mod*Always\
Ran 2.17 RUU
Still on F'n Virgin Mobile.
Change the banner with qpst.
#Root-Hack_Mod*Always\
laie1472 said:
Change the banner with qpst.
#Root-Hack_Mod*Always\
Click to expand...
Click to collapse
It's NOT a banner problem. I lost VPN with it.
I doubt changing the Banner will fix VPN.
Nah don't think it will either I was referring to the banner. Now do you mean when go into wireless settings the vpn settings are not there ??
#Root-Hack_Mod*Always\
laie1472 said:
Nah don't think it will either I was referring to the banner. Now do you mean when go into wireless settings the vpn settings are not there ??
#Root-Hack_Mod*Always\
Click to expand...
Click to collapse
Neither VPN from Windows 7 through WIFI tether nor Creating a VPN Connection on the Phone will work.
I completely restored a prior Ginger Bread ROM that I know worked (backup made just before I applied the patch and installed ICS ROM) and no longer will connect since I applied that stupid Patch.
The Connection just fails.
Something is very wrong with that patch. There are credentials or something that are now wrong which is why not even the RUU will flash over it.
Firmware before 2.17 used to have the same issue and 2.17 fixed it. Now with the patch it's broken and basically I'm not getting 2.17 fully back on there.
This might be hint.
I triggered a handfree activation.
Now I'm stuck on 1X.
I tried suggested fixed in Clean ROM ICS Thread for stuck on 1X and it did not work.
But VPN works.
But I think each speed 1x, 4G and 3G all connect over VPN differently.
4G used to always work but 3G failed. I think 1X might have always worked too.
But this Virgin thing is now blocking 3G.
I may have to call sprint
Yea the banner doesn't do anything. There is an app I use to check grades (blackboard) and it only works with sprint service. It won't let me use it anymore..says I'm not a sprint user
an idea: (requires you are s-off)
*********DO NOT ATTEMPT TO REFLASH HBOOT*********
step 1 - make note of EVERY firmware partition in the firmware zip you flashed
(adsp, radio, tz, etc..etc.)
step 2 - collect the files with the same name from the 2.17 RUU
if you can not find them all in the 2.17 ruu, make note of the ones you cant find in 2.17
step 3- to back ONE previous RUU and look for the files you could not find in 2.17 - repeat this until you have ALL your files...
when you are done, if freeza's zip had 8 files, you should now have 8 files
now from fastboot -
do a fastboot flash xxxxxx.img
for each and every one of the IMG files you collected from 2.17 and previous ruus
the order of this can be an issue, and you do this at your own risk.
the reason i say fastboot, is that if it fails, it "should" notify you. I do not know if you will be notified if bootloader flashes the pg86img.zip file for you when something fails, but you can try...
why older than 2.17
example: if adsp was not included in 2.17, but was in 2.08 - it was NOT updated when you went to 2.17, so its still @ 2.08... and if its on ur list, it means u updated it to the latest..
like i said 10+ times before
the ONLY firmware needed for linux 3 is adsp. BUT it is unknown if ADSP requires any of the others to be updated as well
EDIT:
on my engineering device, i did receive an OTA a few days prior to this leak
it consisted of some firmware updates
the files i received DID match the files in freeza's zip when i did a MD5 compare (except hboot, my hboot was uppdated to 1.58.0001 ENG)
but the zip from the leak DID CONTAIN ADDITIONAL files that were not pushed to my phone - its prolly one of these additional files that is causing the issue.
more info...
visual example:
in the image below is a list of files from the 1st released of firmware
so if rfg_1.img was not found in 2.17, it was not updated in 2.17, so check 2.08 - if its there, is it from there,if its not
go back 1 more version
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
mswlogo said:
This might be hint.
I triggered a handfree activation.
Now I'm stuck on 1X.
I tried suggested fixed in Clean ROM ICS Thread for stuck on 1X and it did not work.
But VPN works.
But I think each speed 1x, 4G and 3G all connect over VPN differently.
4G used to always work but 3G failed. I think 1X might have always worked too.
But this Virgin thing is now blocking 3G.
I may have to call sprint
Click to expand...
Click to collapse
I did a profile refresh in EPST and got stuck on 1x. I did it again and then it went back to normal. Just try doing it again.
chad.goodman said:
an idea:
step 1 - make note of EVERY firmware partition in the firmware zip you flashed
(adsp, radio, tz, etc..etc.)
step 2 - collect the files with the same name from the 2.17 RUU
if you can not find them all in the 2.17 ruu, make note of the ones you cant find in 2.17
step 3- to back ONE previous RUU and look for the files you could not find in 2.17 - repeat this until you have ALL your files...
when you are done, if freeza's zip had 8 files, you should now have 8 files
now from fastboot -
do a fastboot flash xxxxxx.img
for each and every one of the IMG files you collected from 2.17 and previous ruus
the order of this can be an issue, and you do this at your own risk.
why older than 2.17
example: of adsp was not included in 2.17, but was in 2.08 - it was NOT updated when you went to 2.17, so its still @ 2.08...
Click to expand...
Click to collapse
Makes sense. Freeza has been on a road trip I think, lol, he might have a fix for the Virgin Mobile stuff. It's more than banner.
Side note, volume low for anybody else? I've never had this issue.
Sent From My HTC Evo 3D, On The Now Network From Sprint!
Related
Are you hboot 2.09 and s-on?
When you open supersu does it ask to update the binary and then reboot?
Does Adfree reboot the phone when you try to update the host file? Read on my friends!
****Please read the update dated 1/1/13****
Hey folks smarter than me,
I have a question, it's not really a problem but maybe you all can help me here. I used to use an app called 3g/4g optimizer prior to updating to JB. It essentially edits the build.prop file to increase the 3g/4g speeds. Specifically these entries:
ro.ril.gprsclass=
ro.ril.hsdpa.category=
ro.ril.hsupa.category=
ro.ril.hsxpa=1
The Rom I'm using now (flex360s Stock w/ Goodies 3.25) has these settings at:
ro.ril.gprsclass=10
ro.ril.hsdpa.category=8
ro.ril.hsupa.category=6
ro.ril.hsxpa=1
Well I didn't like them (I'm all about speed. I know flex loves the battery life so I can respect the 10 setting) and I thought that since I upgraded to hboot 2.09 (yeah yeah I know...never take an OTA...but hey man I am s-on and I plan to stay that way so I wanted the latest radios and a geek's gotta do what a geek's gotta do ) that editing the build.prop file was not going to happen for me because when I do that now and reboot whatever setting is in the Stock with Goodies.zip overlays my changes. But what I did was go into his zip and change the build.prop THERE and reflashed and it worked!! my changes now stick to whatever I flashed in the ROM. Which are:
ro.ril.gprsclass=12
ro.ril.hsdpa.category=15
ro.ril.hsupa.category=7
ro.ril.hsxpa=1
So I'm asking: (yeah it's a long buildup to a question lol)
Do you think it is it some setting in the ROM preventing me from just changing my build.prop and having it stick between boots? Mind you I'm rooted and using root explorer to make these changes and my permissions are right rw-r--r-- and it used to work on ICS. Or is it the new hboot 2.09 saying "no way man you are gonna use whatever build.prop is in the rom and that's it mister!!! no changes!!!" ??? Orrrr is it JB itself saying no way????
As I said it's not a big deal. I can get around it by just reflashing my modified version of flex's rom. So I'm happy. Just curious.
In short, can anyone who has hboot 2.09 and is s-on AND IS ROOTED edit their build.prop with root explorer or es file manager AND have it stick between boots?
Oh and PS...with my settings I can pull 2327 down on 3g (see screenie below ) which is pretty good for 3g in my area. Hence my impetus for changing these settings.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
As an afterthought.I guess I could flash an ICS kernel and rom and test this myself and see if I can change it with the new hboot.
******UPDATE 1/1/13******
Happy NEW YEAR!!! and what's a great way to start off the year? A resolution to the superuser/Adfree/reboot problem! (read on)
If you're hboot 2.09 (and if you took the latest OTA you are) and s-on (if you're s-off this doesn't apply to you as you're aren't having this issue) then this thread is for you.
If you've read above and a few posts down this thread you will notice several issues with hboot 2.09
for a full description of the problem please go here and read:
http://www.pocketables.com/2012/12/...es-for-rooted-s-on-htc-evo-4g-lte-owners.html
Ok...that's the bad news. The good news? There's a fix!!!!!!!!!!!
Over in the android development section a developer by the name of flar2 has created the first over clockable kernel for the Evo 4g LTE. What he's ALSO done is create a system write module so the over clocking settings stick between boots. What this also does is allow writes to the /system partition WITHOUT REBOOTING THE PHONE. And your changes to the partitions stick!!!
The catch? When you flash a new ROM most of them install a kernel. So you will need to redo the process listed below.
Here's what we folks with hboot 2.09 with s-on need to do:
Go to flar2's kernel thread and download his zip: Go here -----> http://forum.xda-developers.com/showthread.php?t=2075542
(1) boot your phone into fastboot usb in the bootloader
(2) extract the boot.img file from the Elemental-EVO-JB-v0.7.zip (it's located in the /boot directory)
(3) place it into your adb/sdk folder (if you don't know what adb/sdk is please read step #2 in my Manual root thread here: http://forum.xda-developers.com/showthread.php?t=2038123
(4) open an adb command window
(5) issue the 'fastboot flash boot boot.img' command that will push the modified stock kernel to your boot partition
(6) boot to recovery and flash the Elemental-EVO-JB-v0.7.zip as normal selecting your AROMA installer overclocking options (if you want stock speed you can select it) Use the volume up/down keys to move around in the AROMA installer as the touch screen is rather buggy. use the power button to select an option.
(7) reboot your phone and that's it! say goodbye to /system partition reboots!
As proof this works please notice my phone now runs at 1.8Ghz and these settings stick between boots. Also I can temp unroot and I can update Adfree hostfiles with no reboots:
ATTENTION!!! None of this is my work. Please go to flar2's thread and thank him! I'm just pointing the way!!!!!
Please donate to him!!!! I did and it was the best $20 I ever spent!!!
Is there a way you can edit it manually in editprop and setting the vaules. I believe it will stick that way
Sent from my JEWEL using xda premium
Nope. It won't. Again I'm looking for someone with hboot 2.09 to test this and see if they get the same results?
Sent from my EVO using xda app-developers app
If you can do me a favor and upload the zip u r using with JUST the build.prop with your adjustments and I will flash it. I am on h-boot 2.09 w/s-off.
Ill give it a shot I have really really terrible speeds anyway so if this improves it ill ..... Well just upload the zip lol.
Edit: Nvm on uploading the flashable buil.prop. I edited the one for the meanbean v1.0 update. Flashed the new Rom with the edited build.prop. the settings stuck. Have rebooted twice. Build.prop still good to go. Ran a speedtest (mind you this is at three in the morning with no-one really using my towers:
Mind you during the day I barely IF I AM LUCKY get 80kbps. Most if the time I get 40 so if I get any consistant in the 100 kbps ill be happy. Ill update with another speedtests throughout the day if I remember.
Sent from my JEWEL using Tapatalk 2
aestivalisakito said:
If you can do me a favor and upload the zip u r using with JUST the build.prop with your adjustments and I will flash it. I am on h-boot 2.09 w/s-off.
Ill give it a shot I have really really terrible speeds anyway so if this improves it ill ..... Well just upload the zip lol.
Edit: Nvm on uploading the flashable buil.prop. I edited the one for the meanbean v1.0 update. Flashed the new Rom with the edited build.prop. the settings stuck. Have rebooted twice. Build.prop still good to go. Ran a speedtest (mind you this is at three in the morning with no-one really using my towers:
Mind you during the day I barely IF I AM LUCKY get 80kbps. Most if the time I get 40 so if I get any consistant in the 100 kbps ill be happy. Ill update with another speedtests throughout the day if I remember.
Sent from my JEWEL using Tapatalk 2
Click to expand...
Click to collapse
So it's confirmed? You too were having the issues of your changes to build.prop not sticking between boots on hboot 2.09? as I said editing the prop in the rom then flashing it seems to be a viable workaround.
Oh and lest anyone think this speed is a freak chance I took this screenshot right now as I'm waiting for my car to warm up to leave work
Sent from my EVO using xda app-developers app
I dunno if this is an hboot thing though. I remember that t-mobile had done things a couple years ago that caused something similiar. So sprint may be pulling the same thing. But yeah I was having a problem with my edits sticking after reboots. Now no problem. Btw you may want to test your speeds on your lunch break at work, because I have gotten higher speeds till about 9am or so then they drop dramatically ill keep testing too. But I just did a test at 0711 am, and hit about the same speed as earlier.
Sent from my JEWEL using Tapatalk 2
aestivalisakito said:
I dunno if this is an hboot thing though. I remember that t-mobile had done things a couple years ago that caused something similiar. So sprint may be pulling the same thing. But yeah I was having a problem with my edits sticking after reboots. Now no problem. Btw you may want to test your speeds on your lunch break at work, because I have gotten higher speeds till about 9am or so then they drop dramatically ill keep testing too. But I just did a test at 0711 am, and hit about the same speed as earlier.
Sent from my JEWEL using Tapatalk 2
Click to expand...
Click to collapse
Well the very fact that it pulls the build.prop setting from the ROM on each boot now means it's either:
The rom doing it
Hboot copying it from the rom.
Or something new in JB.
All I'm trying to prove is that someone else with hboot 2.09 has this same issue. you and I are using different roms. I'm using flex360's stock with goodies. You're using meanbean v1.0. So clearly it's not something they baked in. So it's not the rom. It's either JB now (which could easily be disproved by flashing an ICS rom and kernel and retesting) or it's hboot 2.09 saying NO edits to /system can take place. I'm betting on hboot. You stated you're also at hboot 2.09 and flex himself says he has NO issues changing his build.prop in his rom. He's on an older hboot but running 3.25 of stock with goodies. same as me. So what's different between me and flex? hboot. what's the same with you and me? hboot. Simple deductive reasoning.
so I think hboot 2.09 is the problem. Mind you I see that in meanbean v1.0, I see that mikeyxda has changed the /system partition to r/w now at boot. this may eliminate our issue. but then again if it's the hboot it's not going to. this is the purpose of my question and this thread. I'm trying to figure out just how limited our access to /system is now?
oh and during prime time I get about 2mb/s and sometimes it drops to 1.3mb/s at it's slowest. depending on where I am. at 8 pm at my home I pull about 1.6-2.1 mb/s. Not saying this tweak is a miracle cure but to quote my favorite general in the movie wargames "Hell I'd p*ss on a sparkplug if I thought it'd do any good."
rawintellect said:
Well the very fact that it pulls the build.prop setting from the ROM on each boot now means it's either:
The rom doing it
Hboot copying it from the rom.
Or something new in JB.
All I'm trying to prove is that someone else with hboot 2.09 has this same issue. you and I are using different roms. I'm using flex360's stock with goodies. You're using meanbean v1.0. So clearly it's not something they baked in. So it's not the rom. It's either JB now (which could easily be disproved by flashing an ICS rom and kernel and retesting) or it's hboot 2.09 saying NO edits to /system can take place. I'm betting on hboot. You stated you're also at hboot 2.09 and flex himself says he has NO issues changing his build.prop in his rom. He's on an older hboot but running 3.25 of stock with goodies. same as me. So what's different between me and flex? hboot. what's the same with you and me? hboot. Simple deductive reasoning.
so I think hboot 2.09 is the problem. Mind you I see that in meanbean v1.0, I see that mikeyxda has changed the /system partition to r/w now at boot. this may eliminate our issue. but then again if it's the hboot it's not going to. this is the purpose of my question and this thread. I'm trying to figure out just how limited our access to /system is now?
oh and during prime time I get about 2mb/s and sometimes it drops to 1.3mb/s at it's slowest. depending on where I am. at 8 pm at my home I pull about 1.6-2.1 mb/s. Not saying this tweak is a miracle cure but to quote my favorite general in the movie wargames "Hell I'd p*ss on a sparkplug if I thought it'd do any good."
Click to expand...
Click to collapse
I read somewhere in this forum on a post the ilduce posted that said htc did some wierd ish to the rom that constantly checks for root and messes with things.. He said he was having a hard time trying to get some issues worked out with some things in his rom...
Lol i know its not specific but i tried...
Sent from my EVO using xda premium
That's great for you unfortunately mine is not even close I am back down to the 80kbps that I was getting before it seems rediculous that that much of a variation happens in my area. Checked and my build.prop is the same.
Btw you are missing what I was saying about the carriers being the ones stopping the adjustment. You may want to read up on sum things. 1. There is more similiarities than just hboot, like our radios. Newer radios from carriers such as sprint enable them to access and push settings to your phone without having to ask your permission (read your contract). The other thing is radio's in HTC devices do Mich more than provide reception, they can be hardcoded to allow certain changes and not. I have been dealing with HTC devices since the MDA (wizard) and Olipro taght me how to dissassemble hboots, Rils, and radios. Sorry bud but believe it or not there are more hardcoded similarities than just hboots. Anyway glad your getting good data speeds, I can only hope they figure out the congestion problem in my area.
Sent from my EVO using Tapatalk 2
aestivalisakito said:
That's great for you unfortunately mine is not even close I am back down to the 80kbps that I was getting before it seems rediculous that that much of a variation happens in my area. Checked and my build.prop is the same.
Btw you are missing what I was saying about the carriers being the ones stopping the adjustment. You may want to read up on sum things. 1. There is more similiarities than just hboot, like our radios. Newer radios from carriers such as sprint enable them to access and push settings to your phone without having to ask your permission (read your contract). The other thing is radio's in HTC devices do Mich more than provide reception, they can be hardcoded to allow certain changes and not. I have been dealing with HTC devices since the MDA (wizard) and Olipro taght me how to dissassemble hboots, Rils, and radios. Sorry bud but believe it or not there are more hardcoded similarities than just hboots. Anyway glad your getting good data speeds, I can only hope they figure out the congestion problem in my area.
Sent from my EVO using Tapatalk 2
Click to expand...
Click to collapse
I didn't miss that at all. Annnnd despite my "new" status on xda I'm hardly new to HTC or tweaking/flashing/modding phones. I'm aware of changes in radios and the consequences thereof. Still my point is valid. You and I are on hboot 2.09. flex is not. you and I have the same radios because we took the OTA. We have the same issue. Flex does not have the newer radios nor does he have the new hboot. Also the very fact that now when some app tries to write to the system partition (mainly supersu...check chainfire's supersu thread for more info) the phone will now HARD REBOOT and not allow the change. This happens in more than one app. Adfree does it when you try to update the host. System tuner does it when you try and select init.d script as a boot up option.
Sir, I am not trying to say I know more than you. I am not trying to debate with you. I am merely trying to get to the bottom of the new hboot with s-on. I fully respect your knowledge in HTC phones. However I DO 100% believe the new hboot and OK the new FIRMWARE as well...is at least PARTIALLY preventing apps from writing to and saving changes (best case senerio) or REBOOTING the phone (worst case senerio) when there are changes to /system. Heck I've even had it reboot when I did an adb push of a build.prop to the /system partition. So I KNOW it's not the method of writing to the phone it's some weird permission problem/addition to hboot 2.09. I am merely seeking others who are experiencing the same issue. Which you have confirmed is happening to you as well. Mission accomplished. Good luck on your speeds my friend as I saw a noticeable improvement when I made those changes to build.prop.
After looking at my reply I realize now that probably came off as snooty and a "I know more than thou" this was not ny intent and I apologize, like yourself I was trying to present more options. Anywho on a happier note and I do have you to thank for this (btw your new? Says you have been regged since 2008) I am now getting CONSISTANT throughtout the day around 200 kbps. Which compared to my 80 kbps I normally get that's about a 1.5x increase. And considering Saturday's are normally a really fn slow data day for me I like it. Again apologies for the misrepresentation of what I was trying to say and I appreciate your work and hope I helped you in some way. I am going to pull and dissassemble 2.09 hboot and see if I can find evidence of what's going on and if HTC snuck in sum nefarious stuff
Sent from my JEWEL using Tapatalk 2
aestivalisakito said:
After looking at my reply I realize now that probably came off as snooty and a "I know more than thou" this was not ny intent and I apologize, like yourself I was trying to present more options. Anywho on a happier note and I do have you to thank for this (btw your new? Says you have been regged since 2008) I am now getting CONSISTANT throughtout the day around 200 kbps. Which compared to my 80 kbps I normally get that's about a 1.5x increase. And considering Saturday's are normally a really fn slow data day for me I like it. Again apologies for the misrepresentation of what I was trying to say and I appreciate your work and hope I helped you in some way. I am going to pull and dissassemble 2.09 hboot and see if I can find evidence of what's going on and if HTC snuck in sum nefarious stuff
Sent from my JEWEL using Tapatalk 2
Click to expand...
Click to collapse
Not a problem. I'm here to learn and help like everyone else. :cyclops:
And yes I registered a long time ago but only began to post recently. Referring to my new status as being a "low poster". Not my actual time here on xda.
I've seen this behavior reported by several people on hboot 2.09. It seems anything written to the system partition is not permanent and will be returned to original state on a reboot. No fix for this yet, but it is being worked on I think.
Sent from my icrap 2 using Tapatalk HD
cruise350 said:
I've seen this behavior reported by several people on hboot 2.09. It seems anything written to the system partition is not permanent and will be returned to original state on a reboot. No fix for this yet, but it is being worked on I think.
Sent from my icrap 2 using Tapatalk HD
Click to expand...
Click to collapse
correct. so what I did is make my changes to build.prop in the ZIP of the ROM I'm flashing. Then flash the ROM and it sticks.
rawintellect said:
correct. so what I did is make my changes to build.prop in the ZIP of the ROM I'm flashing. Then flash the ROM and it sticks.
Click to expand...
Click to collapse
for the time that looks like your best bet saw some people thinking it may have something to do with s on as well
It does have to do with s-on my wife's evo 4g lte is at 2.09 hboot is s-on and has all those symptoms I am s-off on hboot 2.09 but I don't suffer these symptoms at all. I am still going through the hboot code, its a lot of crap to go through so bear with me
Sent from my JEWEL using Tapatalk 2
Updated this thread with a solution/workaround for the hboot 2.09 s-on /system partition reboot issue! Please read post #1
rawintellect said:
Updated this thread with a solution/workaround for the hboot 2.09 s-on /system partition reboot issue! Please read post #1
Click to expand...
Click to collapse
AWESOME!! I was losing my mind... thanks for sharing!!!
AFSOC_Commando said:
AWESOME!! I was losing my mind... thanks for sharing!!!
Click to expand...
Click to collapse
You're welcome! I was losing it too! My phone is 100% back to operating as it was when I was hboot 1.15
[Stock ROM] Aroma Reset | 1.26.502.12 & 15 | ROM + Recovery + Radio | Get the 4.3 OTA
Be ready for the 4.3 OTA update that should be rolling out sometime this morning. These packages will get you back to stock all in one install including the stock recovery so you can take the OTA's right away.
XDA member migascalp gave me the idea of packaging stock ROM's with the aroma installer and include the ability to flash the stock recovery also as sort of a poor mans RUU since so many still are S-on and cannot properly run a RUU.
I have made both 1.26.502.12 and 1.26.502.15 versions as some users have already applied the first OTA update however some still haven't so either one should work, but I would choose the one that matches you current firmware.
If you install the 1.26.502.12 version then you will get the OTA that will update to 1.26.502.15 right away. The 4.3 update was not available to me on 1.26.502.15 when I finished testing at 3:30am EST
If you have a higher firmware version (if you updated manually) then the touchscreen will not work and you will have to use a mouse and OTA cable to accept the update. However I'm not sure S-on users would be able to do that, so most should be ok.
If you are S-off you should just run the RUU or RUU zip to reset back to stock.
Here is a video Demo of the install:
Here are the screen shots from the 2.24.401.1 installer as I didn't have time to take new ones.
You simply flash these in recovery like installing any other rom.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
.
As long as you chose to install the stock recovery, and didn't choose to add root, then you should be able to get the OTA update as soon as it's available. When the script exits and you see the last bits of your custom recovery it might say that you are not rooted. On TWRP make sure to hit Don't Install before rebooting.
During the testing of these packages I was able to get the OTA from 1.26.502.12 to 1.26.502.15 right away.
At time of testing the 4.3 update was still not available.
You do not need to re-lock your bootloader.
Here are the Download Links:
Guru Reset M7 1.26.502.12
md5: 30c0072fb5a02ca75a609bc57a3f34e9
Guru Reset M7 1.26.502.15
md5: 79d290ec018ea3761e8ad35f62476c5a
If these helped you out please consider a small donation or just a thanks would be great.
Enjoy! :good:
crushalot said:
Be ready for the 4.3 OTA update that should be rolling out sometime this morning. These packages will get you back to stock all in one install including the stock recovery so you can take the OTA's right away.
XDA member migascalp gave me the idea of packaging stock ROM's with the aroma installer and include the ability to flash the stock recovery also as sort of a poor mans RUU since so many still are S-on and cannot properly run a RUU.
I have made both 1.26.502.12 and 1.26.502.15 versions as some users have already applied the first OTA update however some still haven't so either one should work, but I would choose the one that matches you current firmware.
If you install the 1.26.502.12 version then you will get the OTA that will update to 1.26.502.15 right away. The 4.3 update was not available to me on 1.26.502.15 when I finished testing at 3:30am EST
If you have a higher firmware version (if you updated manually) then the touchscreen will not work and you will have to use a mouse and OTA cable to accept the update. However I'm not sure S-on users would be able to do that, so most should be ok.
If you are S-off you should just run the RUU or RUU zip to reset back to stock.
Here are the screen shots from the 2.24.401.1 installer as I didn't have time to take new ones.
You simply flash these in recovery like installing any other rom.
.
As long as you chose to install the stock recovery, and didn't choose to add root, then you should be able to get the OTA update as soon as it's available. When the script exits and you see the last bits of your custom recovery it might say that you are not rooted. On TWRP make sure to hit Don't Install before rebooting.
During the testing of these packages I was able to get the OTA from 1.26.502.12 to 1.26.502.15 right away.
At time of testing the 4.3 update was still not available.
You do not need to re-lock your bootloader.
Here are the Download Links:
Guru Reset M7 1.26.502.12
md5: 30c0072fb5a02ca75a609bc57a3f34e9
Guru Reset M7 1.26.502.15
md5: 79d290ec018ea3761e8ad35f62476c5a
If these helped you out please consider a small donation or just a thanks would be great.
Enjoy! :good:
Click to expand...
Click to collapse
Thanks Mate! While downloading, is there a particular OTA cable or program to use for the touchscreen issue? Im S-OFF and on 3.22 currently and I Havent had this phone long enough to have to deal with on screen cpu before Ive just used custom firmwares. Thanks!
Sent from my HTC One using XDA Premium 4 mobile app
the ManaWhoney said:
Thanks Mate! While downloading, is there a particular OTA cable or program to use for the touchscreen issue? Im S-OFF and on 3.22 currently and I Havent had this phone long enough to have to deal with on screen cpu before Ive just used custom firmwares. Thanks!
Sent from my HTC One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
If you are S-off then you should use a RUU to reset your firmware back down rather than these packages. However if you have a OTG cable around, that is what I used to test the updates as I am also on 3.22 firmware.
Here the ruu to use:
http://www.htc1guru.com/dld/ruu_m7_...20_10-40-1150-04_release_326691_signed_2-exe/
This is EXACTLY what I was looking for. And it is genius to have the prior version available so we can be sure OTA is working properly. Downloading now. You're my hero!
Sent from my HTC One using Tapatalk 4
Gotcha thanks. Before I do this, even though I have S-OFF will the RUU wipe my sd card? Was tryn to avoid that so I hunted for a custom firmware.zip and I was unable to find one for .12... I was however able to find one for .15 so I flashed that, wrote cid to CWS__001, and then ran my old stock nandroid with stock recovery for .12. Did a full wipe and installed tarp again and ran your aroma .15 and then reflashed .15 custom firmware.zip. from the moment I restored my nandroid back to .12 my touch screen works fine and I'm still up and running so is the original RUU.exe the only way I can get the 4.3 OTA? I'M hoping I didn't just waste a butt load of time lol. Thanks for the reply by the way
Sent from my HTC One using XDA Premium 4 mobile app
the ManaWhoney said:
Gotcha thanks. Before I do this, even though I have S-OFF will the RUU wipe my sd card? Was tryn to avoid that so I hunted for a custom firmware.zip and I was unable to find one for .12... I was however able to find one for .15 so I flashed that, wrote cid to CWS__001, and then ran my old stock nandroid with stock recovery for .12. Did a full wipe and installed tarp again and ran your aroma .15 and then reflashed .15 custom firmware.zip. from the moment I restored my nandroid back to .12 my touch screen works fine and I'm still up and running so is the original RUU.exe the only way I can get the 4.3 OTA? I'M hoping I didn't just waste a butt load of time lol. Thanks for the reply by the way
Sent from my HTC One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Here's some screenshots
Sent from my HTC One using XDA Premium 4 mobile app
Sorry both didn't post
Sent from my HTC One using XDA Premium 4 mobile app
Lol well just for giggles I went ahead and flashed TWRP and flashed your 1.26.502.12 reset and my phone says OTA available!! Sweet!
Sent from my HTC One using XDA Premium 4 mobile app
the ManaWhoney said:
Lol well just for giggles I went ahead and flashed TWRP and flashed your 1.26.502.12 reset and my phone says OTA available!! Sweet!
Sent from my HTC One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Yes, that should be the first update to go to 1.26.502.15.
If you are only at 1.26.502.15 firmware and have working touchscreen in these roms then no, you don't need to use a RUU, which would wipe all your sdcard data.
You should be all set.
Let me know if you have any other questions.
Maybe also provide download links to TWRP Recovery and flashable SuperSU so people can get back to root after the update?
i installed the stock 12 rom through aroma with no problems but my phone does not detect an update when i check, anyone have any ideas why?
I have the RUU.exe for the release!
Edit: someone already posted it.
gil516 said:
i installed the rock 12 rom through aroma with no problems but my phone does not detect an update when i check, anyone have any ideas why?
Click to expand...
Click to collapse
Did you choose to install the stock recovery?
I have tested both packages and both got the OTA updates.
You do have to check through AT&T Software Updates on the setting page, not under about Software Updates.
godfirst said:
I have the RUU.exe for the release!
Edit: someone already posted it.
Click to expand...
Click to collapse
Thanks. Downloading the ZIP and RUU now so it can be posted on my site. I will also make a Dark Bootloader firmware update for the new version.
crushalot said:
Thanks. Downloading the ZIP and RUU now so it can be posted on my site. I will also make a Dark Bootloader firmware update for the new version.
Click to expand...
Click to collapse
I have custom firmware on my thread as well. I'm doing an ota with my wife phone and att says there is a new radio, different from the one downloaded from HTC website of the RUU. If ATT servers wasn't so slow I would be able to know exactly.
godfirst said:
I have custom firmware on my thread as well. I'm doing an ota with my wife phone and att says there is a new radio, different from the one downloaded from HTC website of the RUU. If ATT servers wasn't so slow I would be able to know exactly.
Click to expand...
Click to collapse
I heard about that. I am also looking into it but my test unit is taking forever to download the OTA from ATT.
crushalot said:
I heard about that. I am also looking into it but my test unit is taking forever to download the OTA from ATT.
Click to expand...
Click to collapse
Tell me about it I'm at 6% with only 38mb downloaded.:crying:
Can confirm the new radio ATT is pushing is 4T.20.3218.13_10.12.1718.01L. I'm wondering if the firmware package from the OTA would be different then what HTC has on it's site. Something isn't right.
crushalot said:
Did you choose to install the stock recovery?
I have tested both packages and both got the OTA updates.
You do have to check through AT&T Software Updates on the setting page, not under about Software Updates.
Click to expand...
Click to collapse
yes stock recovery checked, did not install root after the aroma installer, checked through the at&t software update menu, all it does is check for updates and dissappear. thanks for your response though, as i am sure this is not rom related anymore
Demo Video Added to OP
Here is a video Demo of the install:
I'm in 4.3 with 3.22 firmware. Fully s-off. I need to send my phone in for a camera replacement to HTC. So can I run one of these or just run the ruu? And if it'd the 4.3 ruu. Any guide , I forgot how it's been a while since I did one.
Hello everyone,
I have a SIM unlocked AT&T HTC One (M7) that I am using on T-Mobile.
I am not rooted (I do not wish to be rooted at this time), and I have managed to get up to version 4.3 by use of the HTC RUU, but when I try to get to android version 4.4, the RUU shows error 155. How would I fix this?
Help Please
-TR3Y
TR3Y said:
Hello everyone,
I have an unlocked AT&T HTC One (M7) that I am using on T-Mobile.
I am not rooted (I do not wish to be rooted at this time), and I have managed to get up to version 4.3 by use of the HTC RUU, but when I try to get to android version 4.4, the RUU shows error 155. How would I fix this?
Help Please
-TR3Y
Click to expand...
Click to collapse
try this one
http://www.androidruu.com/getdownlo...09_10.26.1718.01L_release_356565_signed_2.exe
clsA said:
try this one
http://www.androidruu.com/getdownlo...09_10.26.1718.01L_release_356565_signed_2.exe
Click to expand...
Click to collapse
Thank you for replying. I have tried that one already, as well as the one from HTC1Guru. Both of them read the build number as 4.20.502.1 instead of 4.18.502.7 . I believe the error keeps happening because the build number does not match and pretty much my laptop won't allow it to upgrade as long as the build numbers don't match. I will try it again though.
Thanks,
-TR3Y
P.S. has this happened with anyone else?
Update: I have re-tried the update now. At 5% and checking header. I will give it over night to update.
clsA said:
try this one
http://www.androidruu.com/getdownlo...09_10.26.1718.01L_release_356565_signed_2.exe
Click to expand...
Click to collapse
clsA, is this an official RUU from HTC? Every time I try do it, it hangs at 5% (checking header...). I just want to make sure there is no virus/malware here. and androidruu.com is blocked at the location I am at. It says that there was malware found on AndroidRUU. Can you confirm any of this?
-Malware on AndroidRUU and
-official RUU from HTC
-TR3Y
Well I'm going to say the files work for smorgasbord and not others
Malware no I've never seen any infections RUU
Sent from my HTC One_M8 using Tapatalk
clsA said:
Well I'm going to say the files work for smorgasbord and not others
Malware no I've never seen any infections RUU
Sent from my HTC One_M8 using Tapatalk
Click to expand...
Click to collapse
So, are the RUU files are official from HTC? Also HTC1GURU was not blocked at the location I was at. I got the RUU from there. I am guessing both of the RUU files from both websites are the same?
Yeah their the same file
And no their not on the HTC site
I'm not really sure where they originated from
Sent from my HTC One_M8 using Tapatalk
clsA said:
Yeah their the same file
And no their not on the HTC site
I'm not really sure where they originated from
Sent from my HTC One_M8 using Tapatalk
Click to expand...
Click to collapse
Oh ok... Well, now I have a new error when I try from a last resort computer. When I try and run the RUU an error box comes up that says "htc_fastboot.exe has stopped" and then everything crashes. This is an error I have not had anywhere else. Any suggestions?
clsA said:
Yeah their the same file
And no their not on the HTC site
I'm not really sure where they originated from
Click to expand...
Click to collapse
I'm pretty sure the 4.18.502.7 RUU on androidRUU was leaked from some member of the HTC elevate program, that's why it changes the build version to 4.20.502.1, so that it's clear its not the GA release (and possibly to prevent downgrading once its installed.) Also, several reports of that RUU failing to install, possibly it has different signature-- I don't really know.
cschmitt said:
I'm pretty sure the 4.18.502.7 RUU on androidRUU was leaked from some member of the HTC elevate program, that's why it changes the build version to 4.20.502.1, so that it's clear it not the GA release (and possibly to prevent user's from downgrading once they've installed it.) Also, several reports of that RUU failing to install, possibly it has different signature-- I don't really know.
Click to expand...
Click to collapse
Are you recommending that people not install that RUU and just wait for HTC to release it?
TR3Y said:
Are you recommending that people not install that RUU and just wait for HTC to release it?
Click to expand...
Click to collapse
Just sharing my observations. If you're trying to stay 100% stock and are currently on 3.17.502.3 then download the 4.18.502.7 OTA and flash it in stock recovery.
@clsA posted it here.
cschmitt said:
I'm pretty sure the 4.18.502.7 RUU on androidRUU was leaked from some member of the HTC elevate program, that's why it changes the build version to 4.20.502.1, so that it's clear it not the GA release (and possibly to prevent downgrading once its installed.) Also, several reports of that RUU failing to install, possibly it has different signature-- I don't really know.
Click to expand...
Click to collapse
Thanks for the info ... I know I downloaded the RUU when it first come out and had @nkk71 decrypt the rom zip for me ... he mentioned that it had errors during the decrypting but nothing specific, just that he fixed it. Flashing the rom.zip alone fails on all attempts. I was s-off when i flashed the RUU.exe so i don't really know if it's a signature problem or not. The Decrypted version i uploaded worked fine on my 2nd One (s-off of coarse). But I have had reports of it not flashing also ...so I'm really not sure what to think.
cschmitt said:
Just sharing my observations. If you're trying to stay 100% stock and are currently on 3.17.502.3 then download the 4.18.502.7 OTA and flash it in stock recovery.
@clsA posted it here.
Click to expand...
Click to collapse
I have tried going into the current recovery already. The OTA is on the root of internal storage. I went into the recovery and went install from phone storage, and it had an error and just restarted my One. If you have a few minutes. I will do it again and say what the error was.
clsA said:
Thanks for the info ... I know I downloaded the RUU when it first come out and had @nkk71 decrypt the rom zip for me ... he mentioned that it had errors during the decrypting but nothing specific, just that he fixed it. Flashing the rom.zip alone fails on all attempts. I was s-off when i flashed the RUU.exe so i don't really know if it's a signature problem or not. The Decrypted version i uploaded worked fine on my 2nd One (s-off of coarse). But I have had reports of it not flashing also ...so I'm really not sure what to think.
Click to expand...
Click to collapse
I've decrypted the RUUs as well and the format has changed in KK RUUs (due to the size) so now the encrypted rom.zip contains 5 zip files: firmware.zip, system1.zip, system2.zip, system3.zip, and userdata.zip. That's why we see messages like "checking 1/5" when it's flashing, it's verifying each of the 5 zips.
I haven't attempted to flash that RUU (or any RUU for that matter), been on CM builds for the last year.
---------- Post added at 03:05 PM ---------- Previous post was at 03:03 PM ----------
TR3Y said:
I have tried going into the current recovery already. The OTA is on the root of internal storage. I went into the recovery and went install from phone storage, and it had an error and just restarted my One. If you have a few minutes. I will do it again and say what the error was.
Click to expand...
Click to collapse
Give it a try, let's see what happens. There's also a means to flash the OTA in TWRP that worked for at least a couple of people: here
cschmitt said:
I've decrypted the RUUs as well and the format has changed in KK RUUs (due to the size) so now the encrypted rom.zip contains 5 zip files: firmware.zip, system1.zip, system2.zip, system3.zip, and userdata.zip. That's why we see messages like "checking 1/5" when it's flashing, it's verifying each of the 5 zips.
I haven't attempted to flash that RUU (or any RUU for that matter), been on CM builds for the last year.
Click to expand...
Click to collapse
@clsA ... @cschmitt ...
can either of you tell me how to fix this error? http://ow.ly/w0iCY
TR3Y said:
@clsA ... @cschmitt ...
can either of you tell me how to fix this error? http://ow.ly/w0iCY
Click to expand...
Click to collapse
it says check cid failed .. have you changed your cid to something else ?
change it back
fastboot oem writecid CWS__001
TR3Y said:
can either of you tell me how to fix this error?
Click to expand...
Click to collapse
Other's have reported that, it's seems to be an issue with the update script checking the CID.
Does your fastboot screen show CID CWS__001 and OS 3.17.502.3 ?
clsA said:
it says check cid failed .. have you changed your cid to something else ?
change it back
fastboot oem writecid CWS__001
Click to expand...
Click to collapse
I don't remember changing the CID, unless unlocking it did that. That won't wipe my phone if I do that, right?
cschmitt said:
Other's have reported that, it's seems to be an issue with the update script checking the CID.
Does your fastboot screen show CID CWS__001 and OS 3.17.502.3 ?
Click to expand...
Click to collapse
it doesn't appear to.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
cschmitt said:
Other's have reported that, it's seems to be an issue with the update script checking the CID.
Does your fastboot screen show CID CWS__001 and OS 3.17.502.3 ?
Click to expand...
Click to collapse
TR3Y said:
I don't remember changing the CID, unless unlocking it did that. That won't wipe my phone if I do that, right?
Click to expand...
Click to collapse
sorry for the confusion, you seem to be in really good hands try the fix @cschmitt posted above
I have packaged up the last two official RUUs into exe form for use on the DNA. I have tested these on my own DNA. They will work with locked/s-on phones.
DO NOT LOCK OR S-ON for the purpose of flashing these. It's not necessary.
Below you will find both 4.09.605.1 and 4.09.605.5
Intructions:
Extract to folder. Double click ARUwizard.exe. Follow prompts. When complete phone will reboot. If attempting on a non bootable phone connect the phone in fastboot mode.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Downloads
4.09.605.1 link
- https://www.androidfilehost.com/?fid=312968873555011856
4.09.605.5 link
- https://www.androidfilehost.com/?fid=312978532265371239
Very nice work. Haven't tested, but if I ever need to this is available. Thanks
MicroMod777 said:
Very nice work. Haven't tested, but if I ever need to this is available. Thanks
Click to expand...
Click to collapse
These ones are great too because they don't phone home and they don't care what custom rom you had been on. We had a problem for a while on htc phones that didn't have external SD cards failing signature checks when flashing via fastboot.. With these that problem is no more.
I have a couple of questions.;
1) does it matter what firmware you are on to flash any of these 2 firmwares?
2) if I wanted to RUU to complete 100% stock, I can use either of these?
3) Can I flash these if I am currently using a modified hboot?
4) will my deivce stay S-OFF after flashing either of these?
50 Will my HBOOT stay Unlocked after flashing either of these?
Thanks....
ThePunisher said:
I have a couple of questions.;
1) does it matter what firmware you are on to flash any of these 2 firmwares?
2) if I wanted to RUU to complete 100% stock, I can use either of these?
3) Can I flash these if I am currently using a modified hboot?
4) will my deivce stay S-OFF after flashing either of these?
50 Will my HBOOT stay Unlocked after flashing either of these?
Thanks....
Click to expand...
Click to collapse
1)Firmware version depends. If you want the latest one and you are not current on firmware I would suggest flashing the hboot separately.
2) yes either will do. Either will also flash on a locked and s-on phone as well.
3)there's a good chance your hboot will get over-written with a stock one. Are you aware of what can happen if you ever try to s on using a modified boot?
4+5) these will not affect your unlock or s status.
there's a good chance your hboot will get over-written with a stock one. Are you aware of what can happen if you ever try to s on using a modified boot?
Click to expand...
Click to collapse
my main concern was if I could use your RUU to flash my DNA. I could care less whether it overrides my current hboot, as long as it does not during the flashing process lock and s-on my device
thanks for your reply....
This will not make a connection to my Device. However, ADB and Fastboot works, but this RUU/FUU still gives an error....
Current setup:
Unlocked
S-Off
hboot 1.57
Stock (Rooted) 4.4.2/Sense 5.5 Rom
ThePunisher said:
This will not make a connection to my Device. However, ADB and Fastboot works, but this RUU/FUU still gives an error....
Current setup:
Unlocked
S-Off
hboot 1.57
Stock (Rooted) 4.4.2/Sense 5.5 Rom
Click to expand...
Click to collapse
What mode are you starting it in ? The phone that is..
dottat said:
What mode are you starting it in ? The phone that is..
Click to expand...
Click to collapse
I have tried from the Android Homescreen, ADB, Fastboot, and from the RebootRUU downloader/installer. Neither of those work. I have also tried usb 2 and 3 ports. I have tried with and without usb debugging enabled. HTC Sync loads the the device without issues.
ThePunisher said:
I have tried from the Android Homescreen, ADB, Fastboot, and from the RebootRUU downloader/installer. Neither of those work. I have also tried usb 2 and 3 ports. I have tried with and without usb debugging enabled. HTC Sync loads the the device without issues.
Click to expand...
Click to collapse
It never even reboots the phone? What os do you have?
ThePunisher said:
my main concern was if I could use your RUU to flash my DNA. I could care less whether it overrides my current hboot, as long as it does not during the flashing process lock and s-on my device
thanks for your reply....
Click to expand...
Click to collapse
Thank you So Much to the person(s) that made this possible, I've been patiently waiting for this fix and it finally paid off - I can confirm that this 100% works - I had previously all but bricked my phone, it was Re-Locked and S-On along with Tampered - I could only get Hboot to come on and Fastboot. Now it has been completely restored to stock firmware - It still says RELOCKED when in hboot mode but I'm ok with that -
Android Version 4.4.2
HTC Sense Version 5.5
Software Number 4.09.605.1
tat2me2 said:
Thank you So Much to the person(s) that made this possible, I've been patiently waiting for this fix and it finally paid off - I can confirm that this 100% works - I had previously all but bricked my phone, it was Re-Locked and S-On along with Tampered - I could only get Hboot to come on and Fastboot. Now it has been completely restored to stock firmware - It still says RELOCKED when in hboot mode but I'm ok with that -
Android Version 4.4.2
HTC Sense Version 5.5
Software Number 4.09.605.1
Click to expand...
Click to collapse
You are welcome.....DNA crowd has not been forgotten!?
dottat said:
It never even reboots the phone? What os do you have?
Click to expand...
Click to collapse
no, it reboots everytime to the RUU Downloader/Installer on the phone but then gives that error after trying to send the first packet. It never gets past the "Updating 0 of 5" . As I posted. i am running stock rooted 4.4.2/Sense 5.5. I was just wanting to test this ruu out and give feed back.
ThePunisher said:
no, it reboots everytime to the RUU Downloader/Installer on the phone but then gives that error after trying to send the first packet. It never gets past the "Updating 0 of 5" . As I posted. i am running stock rooted 4.4.2/Sense 5.5. I was just wanting to test this ruu out and give feed back.
Click to expand...
Click to collapse
When it gets to the ruu mode it starts a 60 second time out. Quickly unplug the phone and reconnect it to another port.
dottat said:
When it gets to the ruu mode it starts a 60 second time out. Quickly unplug the phone and reconnect it to another port.
Click to expand...
Click to collapse
This is where is gets stuck before is says unable to make a connection. i also tried disabling my av and firewall with no further progress.
ThePunisher said:
This is where is gets stuck before is says unable to make a connection. i also tried disabling my av and firewall with no further progress.
Click to expand...
Click to collapse
How long did you leave it sitting? Until it timed out? Also, open task manager and tell me how much free ram you have.
dottat said:
How long did you leave it sitting? Until it timed out? Also, open task manager and tell me how much free ram you have.
Click to expand...
Click to collapse
yes, until it timed out approximately 3-5mins. i tried what you recommended but it did not work. I have a custom built win 8 x64 with 16gb of ram. trust me, im not using even a 1/3 of that, lol
ThePunisher said:
yes, until it timed out approximately 3-5mins. i tried what you recommended but it did not work. I have a custom built win 8 x64 with 16gb of ram. trust me, im not using even a 1/3 of that, lol
Click to expand...
Click to collapse
Try running the app in windows 7 compatibility mode and as admin.
You would be surprised what an x64 system can consume. To send the ruu over usb the system has to have enough free ram for the 1.x gig file to fit in the free ram.
dottat said:
Try running the app in windows 7 compatibility mode and as admin.
You would be surprised what an x64 system can consume. To send the ruu over usb the system has to have enough free ram for the 1.x gig file to fit in the free ram.
Click to expand...
Click to collapse
says im using 11% of my installed ram i tried running as an admin previously. I tried Win7 Compat mode, still no progress. I guess the RUU is not meant to work for me lol
ThePunisher said:
says im using 11% of my installed ram i tried running as an admin previously. I tried Win7 Compat mode, still no progress. I guess the RUU is not meant to work for me lol
Click to expand...
Click to collapse
Can you install team viewer and screen share with me? If that's ok pm me your login info
As many of you are aware, flashing roms to our phone comes with risk. That risk is dimished by the availability of an RUU for our phone.
I have made this available as a standalone APP (.exe) for PC use as well as a SINGLE zip file for SD card loading.
This is for s-off users only. I repeat...s-off only.
This WILL wipe your phone (internal memory). IF you are able...backup data prior to using this. This works EXACTLY like an RUU for s-off users. Two options exist for using this zip. This will land you on STOCK Lollipop 5.0.2 or Kitkat 4.4.4 pre-rooted with stock recovery.
Option 1
Download the RUU.zip for the OS you would like to land on and Rename file to 0P6BIMG.zip and Copy 0P6BIMG.zip to root of a physical SD. Not internal storage! If you have issues with it getting stuck while loaded simply flash the hboot zip below first using the above method.
Reboot phone to bootloader and follow prompts once RUU is detected by phone.
Option 2 (App/EXE)
For Lollipop, this will be a single EXE with no need to extract. The EXE will install any/all dependencies your pc needs to in order to flash. Simply download the Lollipop exe and run it!
For Kit Kat exe-
Download DOTTAT_ATTM8_4.4.4_S_off_FUU.zip from below. Extract files to folder. Double click ARUwizard.exe. Proceed with prompts until phone reboots (complete).
## expect a good 5 minute plus first boot!
### if you get a side by side application error install this and the fuu again.
- https://www.androidfilehost.com/?fid=95916177934538674
Downloads Do NOT mirror these elsewhere.
SD card method zip
Lollipop
- https://www.androidfilehost.com/?fid=95916177934552416
KitKat
- https://www.androidfilehost.com/?fid=95916177934519267
FUU/EXE method
Lollipop
- https://www.androidfilehost.com/?fid=95916177934552420
Kitkat
- https://www.androidfilehost.com/?fid=95916177934519268
4.4.4 HBOOT zip (SD card flashable)
- https://www.androidfilehost.com/?fid=95916177934519892
Links are live....mine.
Thank you for the RUU. What radio version and hboot will it update the phone to?
devbro said:
Thank you for the RUU. What radio version and hboot will it update the phone to?
Click to expand...
Click to collapse
Baseband here. I honestly forgot to check hboot but it's likely 3.19 like the other m8's.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This looks like the OTA that came down from AT&T this past week? If so it comes with a new radio that switches the AT&T APN to something called "nxtgenphone". This has been found to have issues with ROMS like CM12, in which no data signal is present and you are not able to set a new APN to resolve the issue. As far as I know it's actively being worked on by the CM team, but I haven't seen any updates in the past 24 hours or so. I do not know if this new radio has adverse affects on other ROMs.
Ajax1885 said:
This looks like the OTA that came down from AT&T this past week? If so it comes with a new radio that switches the AT&T APN to something called "nxtgenphone". This has been found to have issues with ROMS like CM12, in which no data signal is present and you are not able to set a new APN to resolve the issue. As far as I know it's actively being worked on by the CM team, but I haven't seen any updates in the past 24 hours or so. I do not know if this new radio has adverse affects on other ROMs.
Click to expand...
Click to collapse
thanks for the heads up! Sounds like the same crap we have been going through over on the VZW devices for some time. We have sim card unlocked phones from the factory but the APN selection has become a huge pain in the arse. You cannot edit them and have to use what shows up (which varies based on the sim card used and they only ALL show when a vzw sim card is inserted!)
Do we need stock recovery installed in order to run these?
DanGeorges said:
Do we need stock recovery installed in order to run these?
Click to expand...
Click to collapse
Nope!
dottat said:
Nope!
Click to expand...
Click to collapse
So is this an RUU or an FUU? The two are pretty different and I'm not sure if I should use this or not?
CavyS said:
So is this an RUU or an FUU? The two are pretty different and I'm not sure if I should use this or not?
Click to expand...
Click to collapse
Both are full RUU. One is just the zip version and one is the EXE. Both are pre-rooted.
I am currently on a stock custom rom that's on 4.4.2 with Philz recovery. Can I just run this ruu to update? I realize I may lose data but I've got that backed up.
johnnyutah22 said:
I am currently on a stock custom rom that's on 4.4.2 with Philz recovery. Can I just run this ruu to update? I realize I may lose data but I've got that backed up.
Click to expand...
Click to collapse
Yes. You may need to separately flash the hboot if you do the SD card method.
@dottat
Nice to see you over here bud.
Just an FYI for those coming from 4.4.2. I was on Skyfall's custom stock 4.4.2 with a ton of xposed mods. I followed the sd card method for install and then did a data only restore from a twrp nandroid. Everything restored fine except for my notification ringtones which I had pushed to system. You will have to reinstall the xposed framework for the modules to kick back in.
Question, does one have to be CID specific to flash this? I am currently SuperCID and don't have a computer with HTC drivers at my disposal right now.
Chargerdude70 said:
Question, does one have to be CID specific to flash this? I am currently SuperCID and don't have a computer with HTC drivers at my disposal right now.
Click to expand...
Click to collapse
Super cid should be ok as long as your mid matches.
took me two tries but the 0p6bimg.zip method worked for me to revert from GPE conversion. The first time it said it failed, booted to a red triangle screen. Manually booted back to hboot and that had reverted. let it update again and it was fine.
Thanks for this.
Straight outta York yo!
Duffman14 said:
took me two tries but the 0p6bimg.zip method worked for me to revert from GPE conversion. The first time it said it failed, booted to a red triangle screen. Manually booted back to hboot and that had reverted. let it update again and it was fine.
Thanks for this.
Straight outta York yo!
Click to expand...
Click to collapse
I can tell you why the first time failed if you want to know.
sure, I would like to. I'm sure it might be good information for others also
Duffman14 said:
sure, I would like to. I'm sure it might be good information for others also
Click to expand...
Click to collapse
Gpe uses a much smaller system partition. When converting back to sense the best method is to flash the latest sense firmware and factory reset from hboot or recovery. That format puts your system partition back to the stock size of around 2.6 gigs vs the 1.2gigs of gpe.