Related
Been lurking for sometime learning things here and there, but now I've got an issue of my own I been pulling hair out over for the last 6 hrs.
I Upgraded to 2.11.605.9 Verizon OTA release today... attempted to use the revolutionary tool to re-root after the upgrade. Well that didn't work. I just get the message "Zerging Root... this might take a minute or so.. Failed to get Root! "
I have tried http://forum.xda-developers.com/showthread.php?t=1009423 the non root users section. With no luck.
Pretty new at this stuff, so if someone can let me if its possible to get s-off, i'd just like to downgrade to an earlier pg05img and NOT get the latest update So i can use revolutionary root.
Thanks in advance.
Nick
Try this..
This thread sounds like the same problem as what you are having. Read what the last two commenters did to correct the problem they are having.
http://forum.xda-developers.com/showthread.php?t=1308324
Also, the thread you originally posted is for returning back to stock, which is not the case. You want to refer to this thread at Thunderbolt Forums in order to acquire root...
http://www.thunderboltforums.com/fo...ry-5-minutes-less-root-without-data-loss.html
Confirm that you are following each and every step. In addition, make sure you are using the USB ports on the back of your PC opposed to the ones in the front. Good luck!
CaptainStrange said:
This thread sounds like the same problem as what you are having. Read what the last two commenters did to correct the problem they are having.
http://forum.xda-developers.com/showthread.php?t=1308324
Also, the thread you originally posted is for returning back to stock, which is not the case. You want to refer to this thread at Thunderbolt Forums in order to acquire root...
http://www.thunderboltforums.com/fo...ry-5-minutes-less-root-without-data-loss.html
Confirm that you are following each and every step. In addition, make sure you are using the USB ports on the back of your PC opposed to the ones in the front. Good luck!
Click to expand...
Click to collapse
I've rooted multiple times using the method above, but since the update, I can't get past the Zerging Root step, even following the posts from the first link you sent
Flashed the Pg image using .androidpolice.com/2011/10/24/exclusive-gingerbread-build-2-11-605-5-for-the-htc-thunderbolt-fixes-several-issues-from-the-previous-leak/[/url] and it works, I was able to re-root using the rev.
Capt....
I am having the same problem as him. After I got this warranty replacement yesterday, no matter what I tried, I can't get past "zerging root". Cannot gain root access. I see you said to flash that image, but how do you do that if you cannot get s-off. I have also rooted thunderbolt several times using the "one click method" (which is also not working for this new 2.11. 605.9 build) and revolutionary. Any suggestions or instructions?
You dont need S-off to load that image... Simply download the file and rename it pg05img.zip and put it on the root of your SD card. Reboot the phone and hold down the vol down + power button to access the bootloader, push the volume button and it will search the sd card for the pg05img.zip file and load it. Just keep in mind it will reload it to factory settings, so back anything up that you have. It takes about 15 mins, but it does work. Once you have that image loaded from the link above you can use the revolutionary root. Let me know if you need help.
Rooting after 2.11.605.9 on TB solution
For those of you that have endured the frustration of updating to the latest software version (2.11.605.9) There is hope! Apparently with this software version, the bootloader is locked. And for some reason this version would not allow the "Revolutionary" rooting method to work. (I would imagine everyone with this problem had issues with not being able to get past Zerg Root. At least that was the problem I had)
Anyways, I got my phone rooted....heres how.
Per the instructions for using Revolutionary, install the driver as stated on their website. (Make sure HTC Sync is not installed on your computer)
Download Mecha_2.11.605.3.zip (I'm a newbie here so I cant post links, but I found it through Android Police but if u google it its easy to find, its hosted on multi upload) rename the zip file as PG05IMG and put on the root of your SD card (as you would in other rooting methods) and run the bootloader.
Once its booted and all that fun waiting is over and your TB powers back up, make sure to turn off all wireless connections to make sure OTA doesnt try to upgrade you. (I turned on airplane mode as soon as I could)
From there run Revolutionary as instructed from their website. Worked like a charm for me, and hope it does for all of you with this same problem.
I TAKE ABSOLUTELY NO CREDIT FOR THIS SOLUTION. Thank you for all you developers out there that make our phones able to be so much cooler and more enjoyable. I'm just glad I could help in this marginal way, and hope that someone will find it usefull. SPREAD THE WORD IF YOU KNOW OF ANYONE HAVING
So if I unroot and my phone takes the latest 2.11.605..9 update, all I have to do is flash the 2.11.605.5 RUU, put phone into airplane mode as soon as it boots, then I can root again?
I am not sure if I missed something but I followed those steps. When I went into boot, it said my version is "older- failed" and won't revert to the .5
I am miserable here with stock. I want to be rooted again.
Any thing else I can do?
Not sure why it wouldn't let you revert to an earlier RUU. Have you tried other earlier versions other than .5? The RUU I used was 2.11.605.3. Try that one. What version bootloader do you have? Also is there Pink letter at the top that says LOCKED?
I have not tried an earlier version... Yet. Will try and will update you. But the bootloader says "***locked***" s-on on the main screen. So I am not sure any older one will work. I read other people were able to accept a downgrade so I am hopeful.
Bootloader 1.5 and yes... It is ***locked*** sigh...
Try loading the 2.11.605.3 If it works just make sure you disable wireless connections when it boots, so OTA doesn't push the upgrade
Even if the OTA comes up before you disable any wireless connection it will download the OTA but then ask if you want to accept or defer. Just hit defer and proceed with the Revolutionary method to root and gain s-off.
*Note: when you hit defer on the OTA, it asks you for a date to remind you, I just set the date to 12/29/2099. If anyone is still using this phone on that date, please tell them not to accept the OTA
Ok guys hold on now, this is kind of misleaing... so did the OP have s-off for the downgrade ? Revolutionary has a password protected HBOOT that was designed to maintain s-off during an OTA or upgrade RUU, hence the reason a downgrade would be possible... Is the OP able to confirm they had S-OFF during the upgrade or S-ON. If i upgrade to 2.11.605.9 on a stock phone S-ON, am i going to be able to downgrade with ease ? I would say no.. not without tricking the bootloader into thinking its an older version which is what the commands are for:
adb push misc.img /data/local/
adb shell dd if=/data/local/misc.img of=/dev/block/mmcblk0p17
However you can't do this without a temporary root shell.
on build 2.11.605.9 there is no exploit for temporary root shell currently..
Please clarify.. ?
rberry88 said:
*Note: when you hit defer on the OTA, it asks you for a date to remind you, I just set the date to 12/29/2099. If anyone is still using this phone on that date, please tell them not to accept the OTA
Click to expand...
Click to collapse
No matter how far out you pick, the limit is 5 days. Picking anything longer, the phone will tell you that.
Like I was saying before the OTA came out, this OTA patches zergRush.
Bootloader has always been locked, this is not new.
I have a few vulns found, and erishasnobattery and I have a couple working exploits done.
However I am on vacation and wont be home until late tonight, once I am we will get something packaged and released for root.
Until then (this isn't the one we are going to release)
Awesome, i just bought my wife a t-bolt Friday and it did an OTA (that i just assumed was the same old gingerbread update that my buddy got but apparently it wasn't because i could not root. Thanks jcase for working on this for us.
I was able to get root with 2.11.605.9
I was already on 2.11.605.5 with root and S-OFF (revolutionary). Perhaps you can try one of the earlier releases such as MR2? This is what you do to get root with 2.11.605.9 if you can get your phone back to 2.11.605.5 or older:
1. Reinstall 2.11.605.5 stock (no root). I got the file from Android Police. I had to rename the file as PG05IMG.zip and run it from the bootloader.
2. Obtain S-OFF with Revolutionary after 2.11.605.5 has installed. Do not install clockworkmod or super user yet.
3. Allow the 2.11.605.9 OTA to be installed. Let the phone do it's thing, the update took my phone awhile.
4. Install Clockwork Recovery (again rename it as PG05IMG.zip and run it from the bootloader)
5. Boot into bootloader again and select Recovery. Install superuser.
6. Reboot and enjoy.
PS. I stumbled upon this on another thread here.
So I'm on a new phone that just did the .9 update about 10 minutes ago and then I find this thread after failing to root. So I'm s on stock everything. I can't revert can I? I'm screwed. I hate stock phones. Adds everywhere. No tether boring no options. I want my skyraider back.
I have the white htc evo lte. I used the ota update before i decided to root my phone. now that there is a regawmod root update for OTA. but im still having problems. i have to manually put the phone in boot mode in order to start the process... also when it starts the automated process. the program get stuck on rebooting.... right after it flashes the recovery my now says unlock with tAMPERED right above it. thats as far as i get. is there something im doin wrong ive followed the directions to the T. please hellpp
Does it say failed or anything? How do u know it didn't work? Heard some people say that they had to press power to reset since the script woildnt do it and it still worked fine in the end.
That's what it is suppose to say, you've unlocked the bootloader and you've tampered with the software. If TWRP didn't automatically install then you need to install it, look for their post in the development section. Check in you app drawer and see if you have superuser app or super su. Install an app that requires root and see if it runs.
Thanks guys for your advice. Shortly after I posted this I just kept repeating the root process and it eventually went thru so far so good in my book. Thanks again guys
Sent from my EVO using xda app-developers app
Ok so I have a question how do I backup my phone before I use htc devunlock or regawmod ... Every thing I see nandroid, titanium, all requires root. How do i root with out unlocking (wiping phone) bootloader? Is there a step I pause at during the process and then do the backup before continuing? Thanks.. Its my first time be gentle!
There's a thread here with a program that can do that.
oc_dub said:
I have the white htc evo lte. I used the ota update before i decided to root my phone. now that there is a regawmod root update for OTA. but im still having problems. i have to manually put the phone in boot mode in order to start the process... also when it starts the automated process. the program get stuck on rebooting.... right after it flashes the recovery my now says unlock with tAMPERED right above it. thats as far as i get. is there something im doin wrong ive followed the directions to the T. please hellpp
Click to expand...
Click to collapse
I had this same problem, what finally worked for me was when I restarted to fastboot, don't actually select anything (I had been selecting fastboot -> reboot). Once I let my phone sit there for a few seconds it connected and was able to flash recovery and reboot on it's own. Then I made it to restart into recovery and voila, Root.
I tried a while ago to unlock my bootloader using HTCDev when it first came out, would get to the part where the confirmation screen should pop up on your phone screen to unlock the bootloader but the screen never showed after multiple attempts, so frustrated, I gave up and told my self I'd come back later. Well later came around a few days ago and I attempted to unlock the bootloader again with the same results as the first time, get to the point where I'm supposed to confirm on my phone screen but it never shows. Did some research to find out the OTA version of the update to ICS could have possibly been the problem, but before I went any further I did a full backup of my phone using Carbon, then did a factory reset from the fastboot menu. Now the problem is, after I did the factory reset my computer no longer recognizes my phone when I plug it in. It can't find HTC sync on my computer even though it is, adb devices shows nothing, same with fastboot devices in fastboot mode. My computer recognized the phone just fine up until the factory reset. So I guess my question is, what caused this to happen and how can I fix it? Also, maybe some help unlocking my bootloader? I think I have to flash the RUU but my phone is 2.95.651 and I don't think it lets you go backwards unless you are S-OFF?
Edit: I guess I should mention that I've tried uninstalling and reinstalling the HTC drivers, usb debugging is enabled and Fast Boot in the power options is disabled, I'm also using the USB cord supplied with my phone, tried different USB ports, performed a second factory reset, made sure all my SDK stuff was up to date, and scoured these forums for 2 days now trying to figure it out (apologies if I missed the one thread with all the answers I need, I did try though). Additionally, in fastboot when I plug in my USB cord it switches to fastboot usb, but nothing shows up on devices, which I find really odd.
Anybody have any ideas/solutions for this?
Yep,
http://androidforums.com/showthread.php?p=5810229
I used srs root to gain a root shell followed scotty85's instructions to set mainver low via adb shell then used the brick downgrade hboot method and followed it up with 1.13 ruu and finished with revolutionary
Post #50 is my instructions and scotty85 are a few posts back
Ok, so I got it... kind of. What I did was try the above method with no luck but I ended up using wraith's temproot and scotty's mainver workaround from above then while it was still in it's temproot state I was able to flash a 2.89 RUU, and after that I was unable to unlock the bootloader through HTCdev. Now on to actually root/s-offing it ^ ^
embersanenders said:
Ok, so I got it... kind of. What I did was try the above method with no luck but I ended up using wraith's temproot and scotty's mainver workaround from above then while it was still in it's temproot state I was able to flash a 2.89 RUU, and after that I was unable to unlock the bootloader through HTCdev. Now on to actually root/s-offing it ^ ^
Click to expand...
Click to collapse
Do 2.89 and 2.95 both use the same hboot?
Sent from my Evo V 4G using Tapatalk 2
thewraith420 said:
Do 2.89 and 2.95 both use the same hboot?
Sent from my Evo V 4G using Tapatalk 2
Click to expand...
Click to collapse
I'm not sure if they use the same hboot or not. I was able to flash 2.89 RUU in the temproot state on hboot 1.58.0000. After the flash I retried unlocking the bootloader through HTCdev and it worked flawlessly. Then I was able to root it and juopnutbear s-off, which applied juopnutbear hboot 1.58.5858. It seems like temprooting the phone using your method and flashing a 2.89 RUU might be the workaround for people who have trouble using HTCdev due to the OTA update.
I should also mention someone suggested this method on phandroid forums (scott actually, I believe) on a different thread and so I tried it. I was going to link his post here but I haven't met the link post requirement yet. So as a disclaimer, this isn't my idea, it just worked so I posted here.
Now that I'm home from work I figured I could give a more detailed list of what I did to root my Evo 3D, I feel the information above gets a little confusing with so many different places to go. As previously stated I had trouble unlocking my bootloader using HTCdev, it would get to the step where you confirm on your phone the unlock but never show up, I found this was usually caused by updating your phone to ICS using the OTA as compared to an RUU. Somehow something gets messed up and your phone never wants to confirm, hopefully this will help people who don't want to brick/downgrade hboot in order to be able to root their phones but can't unlock from HTCdev do to this error. Anyway, on to it.
1. Download SRSRoot
A 2.89 RUU
The files from [Guide] Quick And Dirty Evo 3D/V Root & S-OFF (Sprint and Virgin Mobile Only)
2. Run SRSRoot
3. SmartRoot
4. Follow the steps until your phone restarts and you just have a status bar at the top (this is your 'temproot')
5. Close SRSRoot (you may have to kill in the task manager, or at least I did to get it to completely quit mid-steps)
6. Navigate to the folder where the files from the 'QnD' guide and open the cmd link in the Root folder.
7. Type, or copy & paste the following in order (not the stuff in brackets like this, these are notes);
adb devices (should return your phones serial number, indicating drivers are working, and you're connected)
adb push misc_version /data/local/tmp/misc_version
adb shell (should change your prompt to a #, if not, have your phone awake and watch the screen to grant superuser permissions when you enter su (not likely applicable here))
chmod 777 /data/local/tmp/misc_version (have your phone awake and be watching it, in case superuser needs you to grant permission (again, not likely applicable))
/data/local/tmp/misc_version -s 1.00.000.0
exit (exit again if your prompt changes to a $)
8. Run your 2.89 RUU exe (it should run and reinstall 2.89 to stock, you may lose information, unsure about that though, so back ups are always recommended)
9. Restart your phone after the install if it doesn't happen automatically
10. Retry unlocking using HTCdev method
Hopefully at this point the bootloader actually unlocks for you and you can start at Step 2 of the 'QnD' guide to get root access and S-Off.
Big thanks to thewraith420 for the temproot method and scotty85 over at phandroid for the mainver change directions.
The reason I asked if 2.89 used the 1.58 hboot is just to further understand why it worked I think that setting the mainver is what let you run the ruu. And it didn't complain about the hboot because they use the same one. Nicely done getting the info together.
Sent from my PG86100 using Tapatalk 2
misc_version location
embersanenders said:
adb push misc_version /data/local/tmp/misc_version
Click to expand...
Click to collapse
I was encountering the same issue as you for the HTC bootloader unlock, so thanks so much for this info, it worked like a charm. It might be helpful for others to know that you can find the misc_version referenced by downloading the file scotty85 mentions in his post on guide-how-manually-downgrade-firmware-build-6-01-605-05 (Sorry, I'm unable to post the link)
I have the verizon htc droid 4g lte and I am running viper 2.2 with the twap recovery, but my phone can no no longer be seen
with the unblocking tool that I use to get the bootloader unlocked with the first time. when I hook it up to my computer, I can
see both my internal and external card, and I can even read and write to them, but when it comes to the programs recognizing
my phone like they did before, they want. They will no longer recognize my phone. I can flash a few roms,but nothing that requries me to be s-off.
I tried 10.1, but the phone gets stuck when installing the appz part of the rom. So, I am guessing, it must be because I am not s-off. I want to get to s-off now,but I can't.
Any advice would be great. thanks.
MR_PERFECT said:
I have the verizon htc droid 4g lte and I am running viper 2.2 with the twap recovery, but my phone can no no longer be seen
with the unblocking tool that I use to get the bootloader unlocked with the first time. when I hook it up to my computer, I can
see both my internal and external card, and I can even read and write to them, but when it comes to the programs recognizing
my phone like they did before, they want. They will no longer recognize my phone. I can flash a few roms,but nothing that requries me to be s-off.
I tried 10.1, but the phone gets stuck when installing the appz part of the rom. So, I am guessing, it must be because I am not s-off. I want to get to s-off now,but I can't.
Any advice would be great. thanks.
Click to expand...
Click to collapse
Presumably, your bootloader is still unlocked? Rather than using a script or automated tool, follow the manual procedure in this thread for Part 2: Apply SuperCID. After this, reboot your phone to the bootloader and verify SuperCID with fastboot getvar cid, it should return 11111111. Once this is verified, you can follow the instructions for Facepalm S-OFF. Finally, after achieving S-OFF, revert your CID to normal again using the manual instructions for Part 6: Revert your CID to stock.
BTW, use a more meaningful title next time and this post belongs in the q&a/troubleshooting section, not general.
I converted my AT&T HTC One to an HTC Developer Edition for the following reason which were important for me:
1. wanted 4.4.0 with sense 5.5
2. wanted to be able to put custom RSS feeds into blinkfeed
3. wanted to be able to change quick settings items
4. accuweather allows non standard locations
5. remove att bloat ware (traded with HTC bloatware, but that is much lighter IMHO)
6. unlocked now from at&t
7. quicker updates from HTC
8. ability to select network mode i.e. disable LTE to prevent switching to and from in fringe areas
9. Hotspot without a plan
10. Device doesn't show TAMPERED.
11. Not interested in GPE or custom ROM for now
This is my first android phone, though I have always had rooted android tablets, I've been more in the iphone JB community. I thought I would post my steps here so someone wanting the same can do the steps. Gathered various tidbits from other posts and forums and somehow managed to make it work without bricking. Setps are as follows.
SETUP WINDOWS PC --> UNLOCK BOOT LOADER --> ROOT & INSTALL SU --> ENABLE DEBUGGING/SUPERSU --> S-OFF with RUMRUNNER --> CHANGE CID/MID --> FLASH DEVELOPER EDITION ANDROID --> UPDATE --> ENJOY
1. Use a Windows 7 or Windows 8.0 PC over a USB 2.0 Port. DO NOT use a Windows 8.1 PC over USB 3.0. If you must use a Windows 8.1 PC and a USB 3.0, first install the Intel USB 3.0 drivers instead of the Microsoft USB 3.0 drivers. Plently of posts online to do this. Disable the Windows Firewall during this procedure.
2. Download and Install HTC Sync Manager. Uninstall Sync Manager. This leaves the HTC One drivers only.
3. Downloaded and Install "minimal_adb_fastboot_v1.1.3_setup" (Search for that file on google) to extract to a folder such as C:\AndroidRoot
4. Test communication to the phone by first opening a command prompt window using "run as administrator" and issuing "adb reboot bootloader". If the command cannot reboot the phone. Enable developer options by Settings --> About --> Software Information --> More --> Click "Build Number" 7 times --> select OK. Go to Settings --> Developer Options --> USB Debugging should be CHECKED ON.
Once the phone reboots into boot loader issue command "fastboot getvar cid" and "fastboot getvar mid". If everything is setup correctly then the commands should work and the phone will return return its CID and MID information. Copy that down for future STOCK conversion if needed.
5. I started with an STOCK ATT HTC One, S-ON, LOCKED, HBoot 1.55 running Stock ATT Version of Android 4.3. Fully Charged. Backed up all data via a file copy to the PC.
6. Created an account on htcdev.com. Followed the instructions on the htcdev site to unlock the bootloader by using "Other Supported Devices" in the drop down list. It involved rebooting phone to bootloader menu, running the command "fastboot oem get_identifier_token" to obtain the phone's hash code. Then Copy and Paste it exactly onto htcdev.com site. After a few minutes you will get an email with a file called "Unlock_code.bin" from HTC. Download that file to "C:\AndroidRoot, where adb is located. Then issued the command "fastboot flash unlocktoken Unlock_code.bin". Use the volume keys to select "YES". Click Power button to select Ok and the phone reboots and Everything is Wiped Clean, All user data is deleted. At this point the Phone will be S-ON but UNLOCKED.
7. Now to root and install SuperSU. Download "openrecovery-twrp-2.6.3.3-m7.img" from goo.im. Put it into the C:\AndroidRoot folder. Issue the command "adb reboot bootloader". Once the phone has booted into the bootloader issue the command "fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img". After it is flashed, on your phone, go back to the bootloader menu by pressing Power (Bootloader should be selected). Then highlight Recovery and press Power again. In TWRP menu, tap Reboot, and then System. It'll ask you if you want to install root, so Swipe to install. The phone will reboot and be ROOTED. It will now show **TAMPERED**, but S-ON.
8. Install SuperSu. At this point you can download and install SuperSu, but since PlayStore is not setup you can either do that or reboot back into TWRP recovery. Another way to do this is to hold the "power and volume down" buttons until the phone reboots. When the screen turns blank, let go of power button and keep holding "volume down". From Bootloader menu go into Recovery Menu which will now load TWRP. Use TWRP to install SuperSu and reboot the phone.
9. Once the phone is booted. Enable Developer Options screen. Settings --> About --> Software Information --> More --> Click "Build Number" 7 times --> select OK.
Go to Settings --> Developer Options --> USB Debugging should be CHECKED ON.
Go to Setting --> Personalize --> Select No Lock Screen
Go to Setting --> Power --> Fast boot (UNCHECKED)
Go to Settings --> Display --> Screen Timeout --> Maximum Value of 10 min
10. Run rumrunner to get S-OFF. Yes Rumrunner works with HBoot 1.55 just fine. The reasons it failed for me initially were: Did not have Root, did not have SuperSu installed and permission granted, firewalls, didn't allow debugging permissions. Download software from http://rumrunner.us and extract it into your C:\AndroidRoot folder and follow the rumrunner instructions exactly! Right click sojo.exe and "Run as administrator"
While it does state not to touch the phone, 3 things must be done on the phone screen: When the phone asks to grant USB debugging permissions to rumrunner, say YES and select Always. When SuperSu asks to grant permission to ADB Root, say Yes and Always. If you do not grant these permission in enough time, then rumrunner will timeout. 3rd time was the charm for me as I was on my game by then. My log from 3rd attempt:
Please wait....
..........
Checking for updates......
Test 1: Rebooting into bootloader
Waiting for fastboot (7/120)
Waiting
Test 2: Booting device
Waiting for ADB (27/120)
must ferment longer...
must sanitize, skunky rum is nasty
hold please..............................................
[------------------------------------------------------------]
Rebooting into bootloader (again)
Waiting for fastboot (7/120)
Waiting for ADB (26/120)
must ferment longer...
chilling..................
it's a little stinky here, hmm....
bottles are packed, here we go, shhhhhh....
hmm, cap is on tighter than I expected........
hell, that damn cap is on REALLY tight.......
pouring (1)............................
pouring (2)...........................
pouring (3)........
Waiting for ADB (26/120)
must ferment longer...
what's that in the bottle still? rum foul, sloppy, real sloppy...
wait for it.........
yep, done. Hope you enjoyed the rum!
Don't forget to send us all your money - [email protected]
Press ENTER to exit
At this point the phone should be S-OFF, UNLOCKED, TAMPERED.
11. Change CID and MID. Boot into bootloader either by Power button + volume down or "abd reboot bootloader"
Issue the command "fastboot oem writecid BS_US001" this changes the CID to BrightStar US which is the HTC Developer ROM I wanted. You can go to super CID of 11111111, but I did not care as I can change it anytime with S-OFF.
The MID should be PN0712000, which can be seen in step 4, if not then issue "fastboot oem writemid PN0712000"
Reboot the phone.
12. From htcdev.com download the BrightStar US firmware. "RUU_M7_UL_JB43_SENSE50_MR_BrightstarUS_WWE_3.22.1540.1.exe". It is 1.1GB. Run the executable with the phone connected. It will flash the proper recovery and OS. It will take a good 20 minutes or so. Once the phone is rebooted it will NOT have the *TAMPERED* anymore, as it will not be rooted but it will be S-OFF and UNLOCKED.
13. Now do or skip whatever setup is needed e.g. setup a wifi connection, select your carrier, etc. and go to Settings --> About --> Software Updates. This will cause an update top 4.4.0 with Sense 5.5, HBOOT 1.56.
14. Restore your files and application and enjoy.
I have not noticed any battery drain due to google now and the only bug I have found is that the bluetooth volume with some devices like bluetooth headphone + Pandora jumps around sometimes. I found App Ops the best app so far and thus I am not anxious to get to 4.4.2 anytime soon. Now Changed CID back to CWS__001 to fix the 1 bar issue.
Is this method for all HTC ONE? Or only for AT & T? Is everything working? Or a problem? I normally go LTE in Europe? I have HTC One (m7ul, cid htc_032).
wrong thread.
Sorry you must put that here >>> http://forum.xda-developers.com/htc-one-att
Nice job buddy
Sent from my HTC One using XDA Premium 4 mobile app
5. I started with an STOCK ATT HTC One, S-ON, LOCKED, HBoot 1.55 running Stock ATT Version of Android 4.3. Fully Charged. Backed up all data via a file copy to the PC.
Click to expand...
Click to collapse
Silly question but by LOCKED you mean locked bootloader or carrier locked, I am using an unlocked AT&T version in India. Any chance the device gets locked if i do this ?
This is my first HTC device after a long line of samsungz and nexusz...
A couple things maybe you know about. I have a T-mobile phone that I am using on AT&T. It is S-off.
First thing. The signal is weaker than my other ATT phones. Will changing to the AT&T CID help with signal strength?
Second thing. S-off was done with revone on old firmware. With your steps above if the phone is already S-off and unlocked do you need the htcdev unlock to be done?
Third thing. Can you go straight from 4.1.2 to 4.4.0 or are other updates needed first?
Thanks.
Very well written guide, thanks for the post!
I had just purchased a SIM unlocked at&t 64gb version so this happened to be perfect
I'm not sure if I've looked thoroughly enough, I did search through this other thread regarding the dev edition, but I was wondering if using the Dev firmware permanently reduces signal? This is my first ROM flash and it went off without an issue (thanks for the amazing write-up!) but I am seeing that I no longer get 4G LTE coverage; does this firmware cause that and/or is there any way to improve the radio so that it does receive 4G LTE coverage? Thanks in advance.
**EDIT** I went derp for a moment. I checked about --> network and saw that I am on my LTE network, it just doesn't show that in the status bar.
light_pollution said:
I'm not sure if I've looked thoroughly enough, I did search through this other thread regarding the dev edition, but I was wondering if using the Dev firmware permanently reduces signal? This is my first ROM flash and it went off without an issue (thanks for the amazing write-up!) but I am seeing that I no longer get 4G LTE coverage; does this firmware cause that and/or is there any way to improve the radio so that it does receive 4G LTE coverage? Thanks in advance.
**EDIT** I went derp for a moment. I checked about --> network and saw that I am on my LTE network, it just doesn't show that in the status bar.
Click to expand...
Click to collapse
I also noticed that after I converted my AT&T HTC One to the Dev Edition, it appears my LTE signal dropped to just 1 bar, where I used to get at least 3. Would changing the radio help this?
You can't go by bars. It had been report many times that at&t uses a different method for calculating bars then the rest if the world. The best way to compare is by signal strength. Go to settings -about-network and look at the signal strength db. The lower the -db the better the signal. If you flash back to old setup and compare you will know if this is real or perceived.
When the international roms first got ported to at&t this was a big topic and what I stated above came out of this.
Sent from my HTC One using XDA Premium 4 mobile app
I thought Hboot 1.44 was needed to run RUU's
Only because I had a problem with Hboot 1.54 so I downgraded and then the RUU worked according to what I read online.
Ok, I followed the instruction and it worked for me. But I now want to got back tot stock AT&T 4.3 ROM. When I attempt to RUU back to 4.3 i get an error. Is it becausde of the hboot being a higher number? I still have it unlocked and s-off. Any help would be appreciated. Thanks in advance.
Thank you!
d-pak said:
I converted my AT&T HTC One to an HTC Developer Edition for the following reason which were important for me:
...
Click to expand...
Click to collapse
worked like a charm. even got the latest 4.4.2 update today.
Only question, I left the CID as BS_US001. If i change my CID back to CWS__001 will i be able to get future developer edition update automatically or i have to change the CID back to BS_US001. I wan to switch to CWS_001 cause of the signal bar issue.
sevusal said:
worked like a charm. even got the latest 4.4.2 update today.
Only question, I left the CID as BS_US001. If i change my CID back to CWS__001 will i be able to get future developer edition update automatically or i have to change the CID back to BS_US001. I wan to switch to CWS_001 cause of the signal bar issue.
Click to expand...
Click to collapse
You don't get ota changing cid. That's how it determines what phone you have.
4.4.2 dev edition Gave me terrible battery life/drain even after RUU full rest. Switched to stock at&t thru RUU and battery life is good again. I'll just wait for at&t 4.4.2, nothing really different anyway
Sent from my HTC One using xda app-developers app
pewpewbangbang said:
You don't get ota changing cid. That's how it determines what phone you have.
4.4.2 dev edition Gave me terrible battery life/drain even after RUU full rest. Switched to stock at&t thru RUU and battery life is good again. I'll just wait for at&t 4.4.2, nothing really different anyway
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Thanks. Will keep an eye on battery. So far very happy with Dev edition. Hate all the att bloat. Also they are taking ages to push the new update out.
Sent from my HTC One using Tapatalk
m7u ?
d-pak said:
I converted my AT&T HTC One to an HTC Developer Edition for the following reason which were important for me:
Click to expand...
Click to collapse
i have HTC One 801e CID 038 m7u not ul LTE version can i change to devloper edition ?
main concern fast updates and battery bug present in stock indian 4.4 rom which gives poor battery life
pewpewbangbang said:
You don't get ota changing cid. That's how it determines what phone you have.
4.4.2 dev edition Gave me terrible battery life/drain even after RUU full rest. Switched to stock at&t thru RUU and battery life is good again. I'll just wait for at&t 4.4.2, nothing really different anyway
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
I do was having horrible battery life on the Developer Edition RUU, so I converted mine to a Google Edition. Battery life is excellent and it is running smooth.
great instructions. worked like a charm. I was using a nexus 5 but I missed the boomsound speakers. I'm on the dev edition ruu with 4.4.2 and it's working fine for me. glad to be rid of ATT bloat.
Has anyone tried returning to locked/S-ON after doing this? Does it still work?
Sent from my Galaxy Note 3 using Tapatalk
getting this-
unfortunately this isn't going to work out with your configuration. you have 2
options:
1.) flash an unsecure kernel that's compatible with your ROM and retry rumrunner
(preferred and most reliable method).
2.) flash a different rom.
NOTE: No amount of messing around with su binaries and apk's is going to fix thi
s issue for you!!!.
Better luck next time!!!!bye
starting from the at&t ota update to 4.4.2 with sense 5.5. is this the issue? what changes do i need to make to the instructions?
or is it the new inability to disable lock screen...?
thanks in advance for any help.