Related
****ORIGINAL POST****(REWARD CLAIMED ALREADY)
So here's the deal. I was running cm10 a few days ago and was having a lot of issues with 3g/4g not working and things just being buggy in general. So i decided i wanted to go back to stock since the new jb update was released. I was s-on so i knew it would be a little tricky. So here's what i did. I installed the stock rooted version of the rom, flashed boot.img and all that got the latest stock rom working fine. However, I was still getting really weird issues with 3g/4g dropping and not connecting (even when areas with good signal) so i looked at my radios (which i can't recall ever updating) and decided they would require an update. Since i was s-on this can only be done through the ruu which essentially takes you back to stock but i was ok with this.
So here's what i did today:
relocked my bootloader following this video exactly: http://youtu.be/5yS7yy4XVA4
after i did this the phone may or may not have been stuck in bootloader loop i'm not sure since then i decided to apply the ruu right after.
following this video: http://www.youtube.com/watch?v=NChdbyaHy3k
now the phone only boots into the bootloader heres all this info:
****Tampered****
****Relocked****
***Security Warning***
Jewel Pvt ship s-on rl
hboot-2.09.0000
radio-1.05.11.0606
opendsp-v25.1.0.32.0405
eMMC-boot
Oct 18 2012, 15:4620
FASTBOOT
So i'm offering $15 via paypal to anyone who can help me out step by step to get my phone working again. I just want it to be completely stock running the latest. I tried running, and re running the ruu and everything goes through says its complete but i'm still stuck in the boot loop PAY
****UPDATES****BEWARE OF RUUUUUUUUUUUU
So it seems a lot of people have been having issues with this RUU and have been running into similar problems. Basically the ruu is updating everyones hboot to 2.09 and skipping over the radios. So its come to the conclusion that you should avoid applying the ruu or use it only as a last resort(brick). If you want stock jb then simply install the stock rooted rom. For now it seems the only thing we can do is wait for a method that will give us s-off for 2.09 and allow us to update the radios, or a newer ota/radio update from htc.
for more info/updates on the ruu situation see here http://forum.xda-developers.com/showthread.php?t=2089509
Try running the ruu again while in fastboot.
Sent from my EVO using xda premium
Which hboot were you on previously? I it looks like the ruu updated your hboot, but it didn't update your radios or anything else. Since it appears you can get into fastboot mode, I would plug your phone into a usb port and try to flash the ruu using fastboot. Look for a post by bigdaddy in the Android development stickies. It may help you. One of your problems will be you have some of the current firmware bits installed but not all of them. Which means you risk a hard brick if you to to revert to an older version. There was a post a while back where someone had a hboot flashable pj75img.zip that HTC sent him. That way you could put it on your sdcard and run it from hboot. If I pop can find it I will post a link.
Sent from my A500 using Tapatalk
---------- Post added at 10:20 PM ---------- Previous post was at 10:05 PM ----------
Here is the post with a link to the pj75img.zip. Download it, put it on the root of your sdcard, boot your phone into the bootloader, let it find the file and select yes to install it.
https://www.dropbox.com/s/k8llst3qjb0pn73/PJ75IMG.zip
Sent from my A500 using Tapatalk
Was it really necessary to offer money??
Send a message to captain throwback, he'll help you if you can be helped. And there are others too who would do it for free...
Good luck to you
Yep happens to me every time I relock my bootloader. Either (1) run ruu and let it finish. Or (2) use the htcdev sife to unlock your bootloader.
Sent from my EVO using xda app-developers app
alright brahs so a quick update
i got some help from a nice guy in the irc chat (so the paypal reward is gone) however i still have a few questions.
as soon as i unlocked via htc dev unlock the phone sprang back to life. twrp was back in recovery the stock rooted rom was still there (super su still intact). However my hboot has been updated so the ruu did do something. However my radios are still not updated so how do i go about doing so?
rollerpig said:
alright brahs so a quick update
i got some help from a nice guy in the irc chat (so the paypal reward is gone) however i still have a few questions.
as soon as i unlocked via htc dev unlock the phone sprang back to life. twrp was back in recovery the stock rooted rom was still there (super su still intact). However my hboot has been updated so the ruu did do something. However my radios are still not updated so how do i go about doing so?
Click to expand...
Click to collapse
Relock bootloader. Run the Jelly RUU 3.15. Unlock boot loadr (htc) load TRWP and make a backup..H boot will be downgraded in time. It will take some time just not now there is nothing
Sigh...
I am in the EXACT same boat.
Unfortunately the radios go completely biserko running anything jelly bean.
Fortunately I am able to unlock at will and run whatever ROM I want though... just not run it well at all.
Current status in my bootloader for the lurkers:
*** TAMPERED ***
*** RELOCKED ***
*** Security Warning ****
JEWEL OVT SHIP S-ON RL
HBOOT-2.09.0000
RADIO-1.05.11.0606
OpenDSP-v25.1.0.32.0405
eMMC-boot
Oct 18 2012,15:46:20
The 3.15 RUU completes supposedly "successfully" when ran with the phone in fastboot, however it completes in record time. What takes 10 minutes in the videos takes but maybe 3 minutes on my phone. Sigh.
Gonna flash ICS and continue to lurk. If anyone finds a fix for this please update this thread as I'm subscribed.
As clarification to lurkers...
UB2NOZ said:
Relock bootloader. Run the Jelly RUU 3.15. Unlock boot loadr (htc) load TRWP and make a backup..H boot will be downgraded in time. It will take some time just not now there is nothing
Click to expand...
Click to collapse
Relocked bootloader.
Ran Jelly RUU 3.15
Unlocked bootloader
Made my backup in TWRP
Not sure what the point of that backup is though, the ROM doesn't get updated by the RUU. As soon as I re-unlock I am able to boot right into my previous rom.
I've tried a complete wipe then ran the RUU, same result, except obviously I just had to reload a ROM afterwards.
Flashed an ICS ROM then ran my RUU thinking maybe it was verifying the current ROM version, still no joy.
The RUU goes through it's process, all be it faster than what one would think it should, and finishes saying it successfully completed. But it never actually updates the ROM.
I'm adding tags so others can find the thread as it took awhile to sort through and find this particular issue.
TAGS:
Bootloader HBOOT 2.09 Boot Loader Loop Security Warning Radio-1.05.11.0606 Firmware 3.15
I think what's happening is, when running the ruu, part of the process is it checks your current hboot and firmware to verify it isn't installing an older software. Since some how you partially upgraded with that first ruu attempt. Any future ruu attempts reads your hboot and decides you've already upgraded firmware and skips or stops the rest of the installation. You may be out of luck until HTC comes out with a new ota that upgrades hboot or someone comes up with a method to flash radios in recovery with s-on. You may want to just brick your phone and take it to sprint and see if they will exchange it. A tech looking at should be able to see that the upgrade failed and you only have a partial upgrade.
Sent from my A500 using Tapatalk
Brick the phone as a solution.... Sigh...
cruise350 said:
I think what's happening is, when running the ruu, part of the process is it checks your current hboot and firmware to verify it isn't installing an older software. Since some how you partially upgraded with that first ruu attempt. Any future ruu attempts reads your hboot and decides you've already upgraded firmware and skips or stops the rest of the installation. You may be out of luck until HTC comes out with a new ota that upgrades hboot or someone comes up with a method to flash radios in recovery with s-on. You may want to just brick your phone and take it to sprint and see if they will exchange it. A tech looking at should be able to see that the upgrade failed and you only have a partial upgrade.
Sent from my A500 using Tapatalk
Click to expand...
Click to collapse
Yeah, I don't see Sprint exchanging with a Tampered and Unlocked mark on the phone; may just wait until an s-off method for hboot 2.09 is found, but attempting an exchange may be worth a look.
It's really frustrating how HTC is so hell bent on locking the radios down the way they do. Oh well, that's the mistake I made for not going with a Nexus or something more developer friendly. I knew going in HTC was a proprietary jail of sorts, if you dance in the fire you gotta expect that at some point it's going to burn. Real pisser.
Thanks for the help everyone. If a solution is discovered please PM me or update the thread.
tankerkevo said:
Yeah, I don't see Sprint exchanging with a Tampered and Unlocked mark on the phone; may just wait until an s-off method for hboot 2.09 is found, but attempting an exchange may be worth a look.
It's really frustrating how HTC is so hell bent on locking the radios down the way they do. Oh well, that's the mistake I made for not going with a Nexus or something more developer friendly. I knew going in HTC was a proprietary jail of sorts, if you dance in the fire you gotta expect that at some point it's going to burn. Real pisser.
Thanks for the help everyone. If a solution is discovered please PM me or update the thread.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2081631 this sign good things coming to 2.09 hboot
Sent from my EVO using xda premium
just a few updates. the phone is working but just ****ed up in general. Randomly reboots everyone once in a while. sometimes text messages take forever to send. won't connect to 4g and google music is unable to stream/function properly. So i hoping all this is related to the radios and once i can achieve s-off (shouldn't be long now) i'll be able to update radios and things should work better. until then is there anything i can do to improve the performance? i'm guessing not.
rollerpig said:
just a few updates. the phone is working but just ****ed up in general. Randomly reboots everyone once in a while. sometimes text messages take forever to send. won't connect to 4g and google music is unable to stream/function properly. So i hoping all this is related to the radios and once i can achieve s-off (shouldn't be long now) i'll be able to update radios and things should work better. until then is there anything i can do to improve the performance? i'm guessing not.
Click to expand...
Click to collapse
I hate to be a debbie downer, but...
I wouldn't put too much stock in the latest dirtyracun s-off technique.
The first step in Dirty Racun requires you to stock the phone with the official RUU. In our case the 3.15 RUU.
Well, for the folks in our position the official HTC 3.15 RUU doesn't actually do a damn thing.
Per their instructions:
Download the RUU for your current HBOOT and put it in your DirtyRacun folder:
This step is REQUIRED even if you are on Stock RUU already!
RUU 1.22.651.3 - HBOOT 1.15
MD5 0fde3633b4fe22123d49ea66615b57ff
RUU 2.13.651.1 - HBOOT 1.19
MD5 3c6dbe048b7cfa09fd8f31a1d65ddb51
RUU your device (with your phone in fastboot):*
fastboot erase cache
fastboot oem rebootRUU
fastboot flash zip RUU.zip
Now unless they are using a modified RUU, I don't see this technique working in our case. That said, as soon as I get home I'm going to grab the ROM out of the EXE temp folder and try flashing it this way as I haven't done it yet:
fastboot erase cache
fastboot oem rebootRUU
fastboot flash zip ROM.zip
Every time I've tried flashing I've used the Windows EXE which hasn't had any problems discovering the device while it's in fastboot usb, but trying this way may fix it, I'll let the thread know in a few hours.
Fail blog time
So I ran the flash through a terminal, at least I got a more verbose error:
***NOTE The RUU.zip used here is the PJ75IMG.zip from this thread, just renamed:
http://forum.xda-developers.com/showthread.php?t=2067921
[email protected]:/home/user/Downloads# fastboot oem lock
...
(bootloader) Lock successfully...
(bootloader) TZ_HTC_SVC_DISABLE ret = 534642032 (0x1FDDFD70)
FAILED (status read failed (No such device))
finished. total time: 5.944s
[email protected]:/home/user/Downloads# fastboot erase cache
erasing 'cache'...
OKAY [ 0.115s]
finished. total time: 0.115s
[email protected]:/home/user/Downloads# fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
OKAY [ 0.068s]
finished. total time: 0.068s
[email protected]:/home/user/Downloads# fastboot flash zip RUU.zip
sending 'zip' (659905 KB)...
OKAY [ 25.722s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) rom parsing start ...
(bootloader) rom parsing finish ...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 22 loading zip info fail)
finished. total time: 85.132s
For good measure I ran the flash a second time with the same "remote: 22 loading zip info fail" result:
[email protected]:/home/user/Downloads# fastboot flash zip RUU.zip
sending 'zip' (659905 KB)...
OKAY [ 25.271s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) rom parsing start ...
(bootloader) rom parsing finish ...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 22 loading zip info fail)
finished. total time: 83.659s
So far the bottom line is, if you ran the latest RUU, have s-on, your hboot is at 2.09 and radio at 1.05, welcome to the SOL club.
I've received several PMs from peeps who are suffering the same deal, and everytime I check the forum there's another member joining our not so elite club.
:crying:
Bummers.
I'll donate another $20 to rollerpigs fund if we can get this fixed before the next OTA... :silly: Just kidding, but seriously...
As always any help from the cloud will get stacks of kudos.
---------- Post added at 07:52 AM ---------- Previous post was at 07:19 AM ----------
To verify the image from the other thread, I just ran the same thing on my Windows partition using the rom_01.zip from the RUU EXE, and as anticipated got the same result.
Just got a new Evo LTE yesterday. Unlocked, but can't get S-off following the infamous YouTube video. Relocked then tried RUU. I have the same problem. RUU runs faster then it should. Was 2.13 and when I ran 2.13, it would say I had 2.13 installed. Doesnt work. Tried 3.15. Checks RUU image and says 3.15 is installed on my phone. Huh??? Reboot phone and still running ICS. Can't flash it back to stock. Going to try PJ75IMG. Maybe I will be lucky enough for it to brick and I can take it back to Sprint.
Maybe when Dirty Racun is for hboot 2.09 is released to the public soon, the ruu they provide to flash before you run their process may fix you guys up. Don't know. I think for the mean time people should stop running the ruu to try to upgrade and take the ota instead. The OP should try to change the title of this thread to something more informative like: "help, I ran the 3.15 RUU to upgrade my phone and it screwed up my phone, DO NOT RUN THE RUU BEFORE READING THIS"
Unbelievable how HTC has taken such a nasty stance on enabling people to tweak these phones. I have been using Sense since windows mobile, but all these hoops are not worth the hassle.
PS I am in the same boat. The 3.15RUU file updated the bootloader but NOT the Rom. On reboot the stock sprint Rom was still there along with all settings email etc. P.S. Also followed qbking77 youtube videos except went with the latest RUU instead of the one I had installed.
Op should change thread title to warn others. Problem with these forums is that there is SO much information its impossible to know what is important without spending hours reading.
Thoughts :
What if we were to unlock the bootloader again (I used RegawMOD and install TWRP, then run the older RUU with the earlier HBOOT version wouldn't that work? Does TWRP recovery overwrite the stock HBOOT? I was under the impression that it did, but now I am not too sure.
PS check this out folks:
http://www.pocketables.com/2013/01/...&utm_campaign=Feed:+GoodAndEvo+(Good+and+EVO)
Pretty much summing it all up.
http://www.pocketables.com/2012/12/...es-for-rooted-s-on-htc-evo-4g-lte-owners.html
No
I believe the current HBOOT 2.09 is what is validating the RUU being flashed. So if you try to flash an earlier RUU the current HBPOOT 2.09 halts you in your tracks.
As far as MeanBean, yeah it looks to be shaping up to be a great ROM. Unfortunately any JB ROM installed on antiquated and unflashable radio firmware isn't likely to function well. I've flashed an old stock ICS ROM and it seems to be faring well as far as radios and battery life. The only radio I've noticed dropping is WIFI but it recovers rather quickly. To be honest, I remember stock having that issue previously, so my phone is basically in the status it was in October.
I'm kicking myself, I never should have ran HTCs RUU. Hopefully this was an unintentional move by HTC and they provide updated version signatures in a soon to be released RUU to fix the issue they have caused. If not, I see them going the way of Nokia, superior quality but the geeks advise others away from it. The only non technical people I know that have an HTC cell are either the people I recommended to buy one or people who were referred by other geeks.
When it comes to Android you don't want to piss off the geeks... When you ask a non-geek why they bought a specific Android phone 90% of the time they say "because my geek friend recommended it" and that's a true reality.
The problem is, people are using the ruu improperly. A ruu is not meant to update the phone to the next version of software. It is for returning a phone back to factory condition. The ruu you flash is supposed to correspond to your current hboot and firmware. That is why you are supposed to take the ota to upgrade not run a ruu. I believe if you would have started with a pj75img.zip, which is an update file you would have been alright. Now that the hboot has upgraded all future attempts at running the ruu are failing. I am afraid you maybe out of luck on fixing this until the next ota that updates hboot and radio comes out.
Sent from my A500 using Tapatalk
First, off, awesome NOOB video, and after watching it I can safely say I've done my due diligence. I have scoured our internet and several parallel earth internets with no luck in finding a solution. If any of you can give me a hand, I'd really appreciate it.
Phone Specs:
HTC Rezound
VIGOR PVT SHIP S-ON RL
HBOOT-2.28.0000
RADIO-2.23.10.0123r/2.23.10.0124r
OpenDSP-V14.6.0.7708.00.0507
eMCC-BOOT
Sep 20 2012,17:40:22
SDK tools: "Pulled from the SDK of February 13, 2013"
PROBLEM: Cannot revert to stock rom by
1) using an RUU exe to revert, but it crashes on both my home and office PCs (Win7). The file is the only one I've been able to find: RUU_VIGOR_ICS_35_S_VERIZON_WWE_3.14.605.12_Radio_RS_1.22.10.0424r_3622A_MR3_9K_release_270509_signed
2) or flashing from Amon Ra or TWRP (can't mount eMCC/data)
3) or uploading PH98IMG.zip to SD card and letting Hboot handle the heavy lifting (sticks at HTC boot up screen on reboot)
4) or using "fastboot oem rebootRUU" followed by "fastboot flash zip PH98IMG.zip" gets
sending 'zip' (624366 KB)...
OKAY [ 55.743s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 142.046s
BACKGROUND: I'm obviously a noob, but the only way to learn is by digging in. Here's the progression that's led me to this point:
1) Learned to unlock bootloader
2) Installed cm-10.1-20130629-NIGHTLY-vigor (officially unsupported by available for Rezound from CyanogenMOD's website)
3) Noticed instability so I wiped everything (x3) and tried to revert to stock. Couldn't make any progress, especially since the RUU exe crashes on both Win7 systems I have.
4) To get functionality for work, switched to cm-10.1.0.1-vigor.
5) Still have stability issues, so I'm trying yet again to revert. Current results of attempts are listed above under "PROBLEMS"
Note1: Per Scott's suggestion over either at Phandroid or ScottsRoms (can't remember I've been so many different places), I've modified the android-info.txt in PH98IMG.zip as follows, making sure the version number is higher than the current from CID Getter:
"modelid: PH9810000
cidnum: VZW__001
mainver: 4.09.605.2
hbootpreupdate:12
DelCache:1
DelFat:1
"
Note 2: MD5s check out.
Note 3: Before my first installation of CyanogenMOD's latest nightly, adb worked fine and would list my phone. After CyanogenMOD's latest nightly, adb does succeed in starting daemon and lists what it think is my phone, but instead of listing a phone it lists a blank space and returns to the command prompt. if I try adb reboot, it returns error: device not found. BUT fastboot still works fine.
Appendix 1: fastboot getvar all returns:
C:\Users\Josh\Desktop\Root Project\sdk-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.28.0000
(bootloader) version-baseband: 2.23.10.0123r/2.23.10.0124r
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: (seem odd to anyone else that there's no number there?)
(bootloader) serialno: ******
(bootloader) imei:
(bootloader) product: vigor
(bootloader) platform: HBOOT-8260
(bootloader) modelid: PH9810000
(bootloader) cidnum: VZW__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3776mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: cecc19f7
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.499s
Appendix 2: The sequence I've been following trying to get the thing to accept the stock rom is below...and I've tried small variations variations when what's below fails miserably.
1. Load TWRP or Amon Ra recovery
2. Wipe, wipe, wipe!
3. Reboot bootloader
4. fastboot flash recovery recovery_signed.img (have treated as interchangeable in sequence with step 5)
5. fastboot flash boot boot_signed.img (have treated as interchangeable in sequence with step 4)
6. (used this, also from Scott, before I started manually editing the android-info.txt in the image zip) fastboot flash zip SetMainVersionLOW.zip (to make sure the main version is lower than the stock ROM version--otherwise it'll think you're upgrading to a lower version and won't run)
7. fastboot oem lock
8. This step varies. I've tried
a. fastboot oem rebootRUU then fastboot flash zip PH98IMG.zip
b. fastboot boot TWRP or Amon Ra recovery, then flashing PH98IMG.zip from there
c. dropping PH98IMG.zip on the SD card and letting Hboot handle the heavy lifting
I take it you didn't take a back up of your previous rom before installing CM10.1?
mjones73 said:
I take it you didn't take a back up of your previous rom before installing CM10.1?
Click to expand...
Click to collapse
That's correct. And I deserve what I'm going through for that alone if nothing else.
One additional note I'm about to edit into the post above. I've also tried using an RUU exe to revert, but it crashes on both my home and office PCs (Win7). The file is the only one I've been able to find: RUU_VIGOR_ICS_35_S_VERIZON_WWE_3.14.605.12_Radio_RS_1.22.10.0424r_3622A_MR3_9K_release_270509_signed
JoshManning said:
That's correct. And I deserve what I'm going through for that alone if nothing else.
One additional note I'm about to edit into the post above. I've also tried using an RUU exe to revert, but it crashes on both my home and office PCs (Win7). The file is the only one I've been able to find: RUU_VIGOR_ICS_35_S_VERIZON_WWE_3.14.605.12_Radio_RS_1.22.10.0424r_3622A_MR3_9K_release_270509_signed
Click to expand...
Click to collapse
I believe won't be able to use the RUU anyway because your hboot version is too high, you can't back down if you're s-on (and I could be wrong but I haven't seen a RUU with the latest OTA included). I'd suggest just installing a stock rooted rom - http://forum.xda-developers.com/showthread.php?t=2260154
mjones73 said:
I believe won't be able to use the RUU anyway because your hboot version is too high, you can't back down if you're s-on (and I could be wrong but I haven't seen a RUU with the latest OTA included). I'd suggest just installing a stock rooted rom - http://forum.xda-developers.com/showthread.php?t=2260154
Click to expand...
Click to collapse
Thank you! The opening post notes that the ROM comes without the radio or firmware. Will I be ok? I build my own PCs and know that must be an idiot question, but I just don't yet understand enough about the way the phones work. Thank you very much for your help.
JoshManning said:
Thank you! The opening post notes that the ROM comes without the radio or firmware. Will I be ok? I build my own PCs and know that must be an idiot question, but I just don't yet understand enough about the way the phones work. Thank you very much for your help.
Click to expand...
Click to collapse
You already have the latest firmware on your phone, that doesn't get touched when you do a rom install.
Thank you, Matt! I'm downloading the ROM right now. Will post results once it's down.
SOLVED
JoshManning said:
Thank you! The opening post notes that the ROM comes without the radio or firmware. Will I be ok? I build my own PCs and know that must be an idiot question, but I just don't yet understand enough about the way the phones work. Thank you very much for your help.
Click to expand...
Click to collapse
Oh my gosh! I can't believe that did the trick. Matt, you rock! May I send you a Starbucks card or something?
Couple of clarifications if you have time:
1) TWRP wouldn't install the ROM, but Amon Ra would. Any idea why?
2) What in my original post led you to this solution? Just trying to learn. =)
Thank you again!
JoshManning said:
Oh my gosh! I can't believe that did the trick. Matt, you rock! May I send you a Starbucks card or something?
Couple of clarifications if you have time:
1) TWRP wouldn't install the ROM, but Amon Ra would. Any idea why?
2) What in my original post led you to this solution? Just trying to learn. =)
Thank you again!
Click to expand...
Click to collapse
The update-binary and the updater-script in the META-INF are not updated to work properly with TWRP in the rom you installed.
I learned that the hard way when I built my OTA Blue rom.
good to see you got it working
kc6wke said:
The update-binary and the updater-script in the META-INF are not updated to work properly with TWRP in the rom you installed.
I learned that the hard way when I built my OTA Blue rom.
good to see you got it working
Click to expand...
Click to collapse
Makes perfect sense. Rocking along now nicely thanks to you. Seriously, can I send you an Amazon card or something?
JoshManning said:
Oh my gosh! I can't believe that did the trick. Matt, you rock! May I send you a Starbucks card or something?
Couple of clarifications if you have time:
1) TWRP wouldn't install the ROM, but Amon Ra would. Any idea why?
2) What in my original post led you to this solution? Just trying to learn. =)
Thank you again!
Click to expand...
Click to collapse
You're welcome, kc6wke covered question 1, for number 2, I knew you couldn't RUU cause you are on the latest firmware and s-on, it's not possible to downgrade firmware unless you're s-off. Your only option really was to install a different rom so I gave you a stock rooted one.
Matt, I've got an additional question if you have time. Any idea why my attempts to root the new ROM aren't taking hold? The phone is running just fine off the ROM you directed me to. After installation, I booted into Amon RA 3.16, installed superuser and su, and rebooted. Nothing. SUChecker returns "su declined / not found"
Actually nevermind. SUChecker is returning a false negative. Apologies, and thanks again!
The one I gave you was already rooted, no need to do that.
mjones73 said:
The one I gave you was already rooted, no need to do that.
Click to expand...
Click to collapse
I now remember your saying that. Thank you so much for your help. I really appreciate it.
Josh,
I may be wrong but I think that the iemi is sensitive info so you might want to delete that from your original post. Maybe delete your serial number as well just in case.
btw... my phone doesn't show a mainver either, never got an answer as to why not, but it works fine.
Thanks! Done and done.
well he was a noob, but then he just became just like the rest of them
how did he uploaded the rom in Amon Ra.
band001 said:
how did he uploaded the rom in Amon Ra.
Click to expand...
Click to collapse
Depends, are you s-on or s-off?
mjones73 said:
Depends, are you s-on or s-off?
Click to expand...
Click to collapse
s-off
---------- Post added at 06:46 PM ---------- Previous post was at 06:31 PM ----------
band001 said:
s-off
Click to expand...
Click to collapse
Sorry but i am s-on not s-off yet. trying to get info on how to also if this does not work.
So I've been struggling for the last 4 days now with the following situation:
A part of my touchscreen (a horizontal line in the middle of my screen), stopped working and I want to make use of the warranty.
Since I've unlocked and flashed my phone I'll need to return it to stock first.
I've tried a lot of RUU's all saying "ROM Image Error". (Of course relocked my phone everytime before running a RUU).
The things I already tried hoping the RUU would work:
- flashing different roms
- flashing different kernels
- flashing different recovery's
- restoring someone else's backup using TWRP
At the moment I'm close to giving up, leaving me with this actual state:
***UNLOCKED***
ENRC2B_U PVT SHIP S-ON RL
HBOOT 1.72.0000
CPLD-NONE
MICROP-NONE
RADIO 3.1204.171.33
eMMC-bootmode: Disabled
CPU-bootmode: Disabled
HW Secure boot: Enabled
MODEM PATH: OFF
TWRP 2.3.2.3
CyanogenMod 10.2.1-enrc2b
Android 4.3.1
Kernel version 3.1.10-g0324fc1
(also tried it on Windows 7 instead of a Windows 8.1)
I can't imagine there isn't a solution to get a RUU working.
jimscheltus said:
So I've been struggling for the last 4 days now with the following situation:
A part of my touchscreen (a horizontal line in the middle of my screen), stopped working and I want to make use of the warranty.
Since I've unlocked and flashed my phone I'll need to return it to stock first.
I've tried a lot of RUU's all saying "ROM Image Error". (Of course relocked my phone everytime before running a RUU).
The things I already tried hoping the RUU would work:
- flashing different roms
- flashing different kernels
- flashing different recovery's
- restoring someone else's backup using TWRP
At the moment I'm close to giving up, leaving me with this actual state:
***UNLOCKED***
ENRC2B_U PVT SHIP S-ON RL
HBOOT 1.72.0000
CPLD-NONE
MICROP-NONE
RADIO 3.1204.171.33
eMMC-bootmode: Disabled
CPU-bootmode: Disabled
HW Secure boot: Enabled
MODEM PATH: OFF
TWRP 2.3.2.3
CyanogenMod 10.2.1-enrc2b
Android 4.3.1
Kernel version 3.1.10-g0324fc1
(also tried it on Windows 7 instead of a Windows 8.1)
I can't imagine there isn't a solution to get a RUU working.
Click to expand...
Click to collapse
Your right, you can't restore using an RUU past hboot version 0.4. However here is the latest stock backup. If you restore in TWRP and then flash the firmware.zip you end up with at least a look alike stock. I think you can also modify the "relocked" message in the bootloader to "locked" once more. This should fool the shop/retailer easily!
file are here: http://forum.xda-developers.com/showthread.php?t=2414238
I had an issue with the file service though. If that happens then just download the megadownloader program to download it properly
Hope this helps.
Dr.ripsaw said:
Your right, you can't restore using an RUU past hboot version 0.4. However here is the latest stock backup. If you restore in TWRP and then flash the firmware.zip you end up with at least a look alike stock. I think you can also modify the "relocked" message in the bootloader to "locked" once more. This should fool the shop/retailer easily!
file are here: http://forum.xda-developers.com/showthread.php?t=2414238
I had an issue with the file service though. If that happens then just download the megadownloader program to download it properly
Hope this helps.
Click to expand...
Click to collapse
Alright, It's worth the try. Also, will this change my Hboot version?
I also found out it's impossible to get the 'LOCKED' message back. Relocked is as close we can get :')
But that doesn't automatically mean that the warranty won't pay the repair. When they find a custom rom on your phone it's a different story though. This because a custom rom could mean I overclocked my CPU for example.
jimscheltus said:
Alright, It's worth the try. Also, will this change my Hboot version?
I also found out it's impossible to get the 'LOCKED' message back. Relocked is as close we can get :')
But that doesn't automatically mean that the warranty won't pay the repair. When they find a custom rom on your phone it's a different story though. This because a custom rom could mean I overclocked my CPU for example.
Click to expand...
Click to collapse
Well When I got my phone I allowed it to update to the latest version of android and so it upgraded my Hboot version. To get the latest version you need to flash the latest firmware. I think restoring a backup that is the newest version of stock will automatically update your Hboot. Don't take my word for it as I've said my Hboot was fully updated before I started Modding.
So I'm trying to flash the 1.58.502.1 RUU but I am s-on with an unlocked bootloader. And from the sound of things the only way to relock the bootloader is by going s-off which I don't want to pay $25 to do.
My current software is 1.12.502.8 but the current baseband matches up with the baseband from 1.58.502.1 (1.16.21331931. LA11G_20.31A.4145.02L). Are there any work arounds that you guys can think of, can I just flash the RUU since the basebands match up?
From what I've read it seems you do in fact need to S-OFF to relock the bootlooader.
Here's the thing,if you S-OFF than you won't need to relock the bootlooader to achieve what your looking to do .S-OFF enables you to flash all sorts of variations assuming they are for your specific device.
I will tell you that the $25 spent to have a safe hassle free S-OFF exploit is worth every cent.
You do not need to s-off to relock the bootloader.
"fastboot oem lock" from adb command prompt connection, while in fastboot mode is all you need to do.
Put your recovery back to stock first for safety but RUU should do that for you, better safe than sorry though...
- Sent from a payphone ...
Iconic24 said:
So I'm trying to flash the 1.58.502.1 RUU but I am s-on with an unlocked bootloader. And from the sound of things the only way to relock the bootloader is by going s-off
Click to expand...
Click to collapse
I don't know where you guys are getting this from. S-off is in no way required to relock the bootloader.
Further, s-off is not required to run an RUU (another common misconception, that I don't know where people get); unless you are trying to "break the rules" and either run an older RUU ("downgrade") or run another carrier's RUU.
Iconic24 said:
My current software is 1.12.502.8 but the current baseband matches up with the baseband from 1.58.502.1 (1.16.21331931. LA11G_20.31A.4145.02L). Are there any work arounds that you guys can think of, can I just flash the RUU since the basebands match up?
Click to expand...
Click to collapse
As long as you are using an AT&T RUU, you can run an RUU for any version number that is equal to or greater than the main version on the phone. The only thing you can't do is run an older RUU ("downgrade") with s-on.
But since you are on the oldest AT&T version (1.12) and there is no 1.12 RUU anyway; you can therefore run any AT&T RUU. This includes 1.58, 2.23, and any new RUUs that come in the future.
ruu
Oh my, I know this is necro thread but it is the closest to what I am trying to achieve and google search led me to it. So if I am on SkyDragon GPE 4.4.4 flashed on top of Stock Sense 4.4.2, hboot 3.16, tampered, unlocked, rooted, s-on there is no problem for me to go RUU and update to 5.x.x? However, shall I use RUU for 4.4.4 or 4.4..2? Thanks if anyone replies
?
i am thinking of just using a toolkit to root and unlock the bootloader but before i do that i gotta ask is it worth it ?
xCellHD said:
i am thinking of just using a toolkit to root and unlock the bootloader but before i do that i gotta ask is it worth it ?
Click to expand...
Click to collapse
Is it worth it to unlock the bootloader? That question is impossible to answer without knowing your individual desires, preferences and what you want from the device.
I gave an answer to a similar question a few days ago: http://forum.xda-developers.com/htc-one-m8/help/to-root-to-root-t3102598
If you are asking "is using a toolkit worthwhile"; I would say NO. The toolkits are not up to date, and therefore install obsolete versions of TWRP (which causes issues) and I personally recommend to do the steps "manually" as its not very hard, ande also a good learning experience that will yield better results.
My personal opinion, ditch the toolkits.
---------- Post added at 10:28 AM ---------- Previous post was at 10:22 AM ----------
innocencex said:
Oh my, I know this is necro thread but it is the closest to what I am trying to achieve and google search led me to it. So if I am on SkyDragon GPE 4.4.4 flashed on top of Stock Sense 4.4.2, hboot 3.16, tampered, unlocked, rooted, s-on there is no problem for me to go RUU and update to 5.x.x?
Click to expand...
Click to collapse
It sounds like you just flashed the GPE ROM, and did not "fully convert" to GPE with the RUU. You can confirm this by booting into hboot, if the hboot screen is white, its still the Sense hboot. GPE hboot is black.
Assuming you just flashed a GPE ROM, you can just RUU to current Sense RUU (5.0). You will need to relock the bootloader to RUU, since you are s-on.
innocencex said:
shall I use RUU for 4.4.4 or 4.4..2?
Click to expand...
Click to collapse
Just run the 5.0 RUU. No need to run intermediate RUUs or run them sequentially. OTAs need to be installed in sequence. RUUs do not.
redpoint73 said:
Is it worth it to unlock the bootloader? That question is impossible to answer without knowing your individual desires, preferences and what you want from the device.
I gave an answer to a similar question a few days ago: http://forum.xda-developers.com/htc-one-m8/help/to-root-to-root-t3102598
If you are asking "is using a toolkit worthwhile"; I would say NO. The toolkits are not up to date, and therefore install obsolete versions of TWRP (which causes issues) and I personally recommend to do the steps "manually" as its not very hard, ande also a good learning experience that will yield better results.
My personal opinion, ditch the toolkits.
---------- Post added at 10:28 AM ---------- Previous post was at 10:22 AM ----------
It sounds like you just flashed the GPE ROM, and did not "fully convert" to GPE with the RUU. You can confirm this by booting into hboot, if the hboot screen is white, its still the Sense hboot. GPE hboot is black.
Assuming you just flashed a GPE ROM, you can just RUU to current Sense RUU (5.0). You will need to relock the bootloader to RUU, since you are s-on.
Just run the 5.0 RUU. No need to run intermediate RUUs or run them sequentially. OTAs need to be installed in sequence. RUUs do not.
Click to expand...
Click to collapse
Sir I'm using GPe ROM to my HTC m8..it's S-ON "Unlocked" I can't unlock my bootloader.
Prvrt said:
Sir I'm using GPe ROM to my HTC m8..it's S-ON "Unlocked" I can't unlock my bootloader.
Click to expand...
Click to collapse
If it says UNLOCKED in bootloader, that means the bootloader is already unlocked.
Or are you trying to relock your bootloader?
It's not clear exactly what you are trying to do, or what steps you've already taken. I know you're new to the forum, so please try to provide as much detail as possible when asking for help. If youknow how, do fastboot getvar all, and post the result (delete IMEI and serial number before posting).
redpoint73 said:
If it says UNLOCKED in bootloader, that means the bootloader is already unlocked.
Or are you trying to relock your bootloader?
It's not clear exactly what you are trying to do, or what steps you've already taken. I know you're new to the forum, so please try to provide as much detail as possible when asking for help. If youknow how, do fastboot getvar all, and post the result (delete IMEI and serial number before posting).
Click to expand...
Click to collapse
Im trying to root my phone again and unlock the bootloader..but i cant access when my phone is in Hboot my phone cant read on my laptop..and after i open it connect but my USB debugging is in "charging only" and i put it back again in MTP and after i put it in Hboot it disconnect again.. idont know if my laptop or my debugging mode
Prvrt said:
Im trying to root my phone again and unlock the bootloader..but i cant access when my phone is in Hboot my phone cant read on my laptop..and after i open it connect but my USB debugging is in "charging only" and i put it back again in MTP and after i put it in Hboot it disconnect again.. idont know if my laptop or my debugging mode
Click to expand...
Click to collapse
You do not need to unlock the bootloader if it says "UNLOCKED" near the top of the screen in bootloader. This specifically means the bootloader is already unlocked.
However, you will (somewhat obviously) need fastboot working if you want to flash TWRP via fastboot. There other means to install TWRP, since you also have working OS (TWRP app for instance). However, working fastboot is really valuable (possibly even critical in some situations) when modding the phone, so my recommendation would be to troubleshoot the problem, and have fastboot working (even despite the existence of "workaround" methods to install TWRP).
You actually do not need debugging enabled to use fastboot (only for adb, which is related to fastboot by there are distinct differences - so try to keep that in mind). Although having debugging enabled would not hurt anything (and obviously you will need it, if you want to use adb).
Another thing to note, the MTP connection mode selected in OS (charge only, file transfer, etc.) has not bearing once you are no longer in OS (when in bootloader) and fastboot will work regardless of whether there is even a working OS.
Fastboot connectivity issues are most usually on the PC side. Try a different USB port, different cable, re-install HTC Sync and HTC drivers. You can also try going into Windows Device Manager, finding the phone, then pick the option to manually select drivers, and select the "generic" Android MTP drivers. I often have to do this to make my PC "see" the M8 on fastboot/adb.
redpoint73 said:
You do not need to unlock the bootloader if it says "UNLOCKED" near the top of the screen in bootloader. This specifically means the bootloader is already unlocked.
However, you will (somewhat obviously) need fastboot working if you want to flash TWRP via fastboot. There other means to install TWRP, since you also have working OS (TWRP app for instance). However, working fastboot is really valuable (possibly even critical in some situations) when modding the phone, so my recommendation would be to troubleshoot the problem, and have fastboot working (even despite the existence of "workaround" methods to install TWRP).
You actually do not need debugging enabled to use fastboot (only for adb, which is related to fastboot by there are distinct differences - so try to keep that in mind). Although having debugging enabled would not hurt anything (and obviously you will need it, if you want to use adb).
Another thing to note, the MTP connection mode selected in OS (charge only, file transfer, etc.) has not bearing once you are no longer in OS (when in bootloader) and fastboot will work regardless of whether there is even a working OS.
Fastboot connectivity issues are most usually on the PC side. Try a different USB port, different cable, re-install HTC Sync and HTC drivers. You can also try going into Windows Device Manager, finding the phone, then pick the option to manually select drivers, and select the "generic" Android MTP drivers. I often have to do this to make my PC "see" the M8 on fastboot/adb.
Click to expand...
Click to collapse
I try on cmd my phone response. I type unlocktoken it works and after I type unlock code bin it success too but my phone didn't show the logo of unlock code and didn't reboot. But in my cmd it says successfully
Prvrt said:
I try on cmd my phone response. I type unlocktoken it works and after I type unlock code bin it success too but my phone didn't show the logo of unlock code and didn't reboot. But in my cmd it says successfully
Click to expand...
Click to collapse
You previously indicated UNLOCKED. Does it say UNLOCKED near the top of the bootloader screen?
Also, please refrain from quoting my whole entire post; as it clutters up the thread. I know it's the default when responding. But just leave in what is directly relevant to your response, and delete the rest.
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: [email protected]
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.20.502.5
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT45SWM06618
(bootloader) imei: XXXXXXXXXXXXXXX ( Deleted)
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul_ca
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B12000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 205bdca3
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.125s
Bootloader - Unlocked
Recovery - TWRP
Rooted - Yes
Custom ROM - Resurrection Remis 5.8.5 Final
if want to go back to stock what is procedure
i have below RUU
RUU_M8_UL_M60_SENSE70_ATT_MR_Cingular_US_6.20.502. 5_combined.exe
can i run this exe after relock the bootloader?
hotspot problem
i'm using htc one m9 at&t in india. i'm unable to turn on hotspot or bluetooth tethering. i heard a solution that i need to unlock bootloader and install cutome rom or edit some line in sql editor. so my question which is the safest method? could anyone please tell me the answer:crying:
Ashok_gajjala said:
i'm using htc one m9 at&t in india. i'm unable to turn on hotspot or bluetooth tethering. i heard a solution that i need to unlock bootloader and install cutome rom or edit some line in sql editor. so my question which is the safest method? could anyone please tell me the answer:crying:
Click to expand...
Click to collapse
This forum section is for the M8, not the M9. Anything we say here about the M8, may or may not be correct for the M9.
have a simple question I'm on firmware 3.16.617.2 there is update 3.16.617.3 if I am s-on unlocked Bootloader and attempt to flash RUU advance to 3.16.617.3 from earlier .2 will this relock my Bootloader ? as I don't want to relock it again my goal is to stall unlocked S-on .
Hello!
So I recently replaced my stolen AT&T HTC M8 with an a refurbished one and decided to root it for my first time. Unfortunately, I fell into the common mistake of using the outdated Hasoon2000 All-in-one toolkit. I'm not well-knowledged in phones, but I definitely want to learn (which is why I am here). I know I should've been more cautious and prepared prior, but all I can do is learn and move forward now. I've spent a few hours researching and trying to understand the process, but there is a lot of technical aspects that I haven't grasped yet. Well, here is my situation:
My phone is currently soft bricked and I am unable to access my phone's UI when I boot it. After the HTC One logo, the phone will be black and consistently bring up, "unfortunately AT&T ready2go has stopped". It will also say that the UI has stopped and I have no choice but to turn off my phone. Prior to this, I had an issue with Superuser where there was no binary so I tried to re-install it thinking that would do something; I then performed a factory reset (thinking it would somehow fix it). I realized after this that TWRP and SU were both out of date and now I'm here not sure what to do. I would like to be able to flash the RUU to revert back to stock and go through the rooting process manually but I haven't had much luck with the .exe file so far; do I need to have S-OFF and/or relock my bootloader? If so, how do I do that? I'm still learning, and it's a lot to pick up, so bear with me please as I try to piece together everything. I've been searching through the forums, but it hasn't really helped me too much.
Here is what my Hboot says:
*** Software Status: Modified ***
M8_UL_CA PVT SSHIP S-ON
HBOOT-3.19.0.0000
[email protected]
OpenDSP-v47.2.2-00564-M8974_F0.1024
OS-
eMMC-boot 2048MB
AUG 4 2015, 23:21:05.0
Getvar All (not exactly sure what this is, but I saw other help posts listing it and figured it's useful)
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: [email protected]
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: xxxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxxx
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul_ca
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B12000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 7f8e91a3
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
If anyone could give me some guidance/clarity then I would truly appreciate it! Thank you!
mtruong15 said:
Unfortunately, I fell into the common mistake of using the outdated Hasoon2000 All-in-one toolkit. I'm not well-knowledged in phones, but I definitely want to learn (which is why I am here). I know I should've been more cautious and prepared prior, but all I can do is learn and move forward now.
Click to expand...
Click to collapse
Were you on stock Lollipop or Marshmallow before you started modding the phone? From the radio number, I think its LP, but I'm not that familiar with the weird AT&T radio numbers (and how they correspond to LP, MM, etc.). It would be easy to see your main version, if you had not used an obsolete TWRP (from the toolkit) that deletes that info.
One piece of advice moving forward, and this goes for modding any Android device, is to always research the current methods based on your current Android version, firmware, etc.; and confirm the methods work for your setup, before you begin.
At least you've realized your mistake (outdated toolkit, outdated TWRP, outdated SuperSU), and also properly posted your getvar data. So you're not doing a bad job in that respect.
Also, did you make a TWRP backup before trying to root? If not, this is a basic step that is too frequently skipped by newer users. Having a backup of your stock (pre-root attempt) ROM would have given you an easy way to revert to a working OS.
---------- Post added at 09:44 AM ---------- Previous post was at 09:36 AM ----------
mtruong15 said:
I would like to be able to flash the RUU to revert back to stock and go through the rooting process manually but I haven't had much luck with the .exe file so far; do I need to have S-OFF and/or relock my bootloader? If so, how do I do that?
Click to expand...
Click to collapse
Do not need to s-off to run RUU.
But you do need to relock the bootloader, with fastboot command: fastboot oem lock
The RUU version will depend somewhat on your main version (Android version) which I asked above. I can give info, once you've answered that question.
After RUU back to stock, you'll need to unlock the bootloader again (try the same unlock bin code, or get another from HTCDev.com) in order to install TWRP, root, etc.
redpoint73 said:
Were you on stock Lollipop or Marshmallow before you started modding the phone?
Click to expand...
Click to collapse
I was on stock Lollipop when I received my phone.
redpoint73 said:
Also, did you make a TWRP backup before trying to root? If not, this is a basic step that is too frequently skipped by newer users. Having a backup of your stock (pre-root attempt) ROM would have given you an easy way to revert to a working OS.
Click to expand...
Click to collapse
I unfortunately did not, but will do this from now on. I've definitely learned a lot about the process, after the fact, and feel much more prepared to work on this phone. In the case that I need to do this on another phone I will do my research and take the appropriate steps as well.
redpoint said:
The RUU version will depend somewhat on your main version (Android version) which I asked above. I can give info, once you've answered that question.
Click to expand...
Click to collapse
From my understanding, the RUU version needs to be the same or above the previous. This is the only part that confuses me because I felt that I had everything right to run the RUU. What do you think is a potential reason for this specific case?
Update: I have already relocked bootloader
mtruong15 said:
From my understanding, the RUU version needs to be the same or above the previous. This is the only part that confuses me because I felt that I had everything right to run the RUU.
Click to expand...
Click to collapse
Its correct, with s-on, you need to run RUU that is equal or greater version number than the firmware on the phone (in addition to the RUU for your CID,MID so the RUU meant for AT&T M8). Meaning you can't "downgrade" or run the KitKat RUUs (only way to bypass with is with s-off, which is $25 by sunshine). Since you are on LP firmware, you can run the LP RUU.
There is another complication, in that you cannot run the Marshmallow AT&T RUU, unless you flash the MM firmware.zip separately first. Otherwise, the MM will fail with Error 155 if you try to flash from LP or KK. This is a new requirement with MM RUUs.
Link to details on how to flash the firmware.zip (if you want to RUU to MM) is in my Index thread, as well as all the AT&T RUUs (in the RUUs section): http://forum.xda-developers.com/showthread.php?t=2751432
redpoint73 said:
There is another complication, in that you cannot run the Marshmallow AT&T RUU, unless you flash the MM firmware.zip separately first. Otherwise, the MM will fail with Error 155 if you try to flash from LP or KK. This is a new requirement with MM RUUs.
Click to expand...
Click to collapse
I was able to successfully flash the MM firmware as referred to in the post and now it shows the OS number in my Hboot. However, when I used the MM .exe file (RUU_M8_UL_M60_SENSE70_ATT_MR_Cingular_US_6.20.502.5_combined), I am still running into the same issue. I see the first Install Wizard pop-up and then it disappears before I even get to the Terms and Conditions page. I feel that I have all the necessary steps now, but I can't seem to figure it out. I also haven't been able to find a .zip file of the update to manually run the RUU. Any ideas on what my options are?
mtruong15 said:
I was able to successfully flash the MM firmware as referred to in the post and now it shows the OS number in my Hboot. However, when I used the MM .exe file (RUU_M8_UL_M60_SENSE70_ATT_MR_Cingular_US_6.20.502.5_combined), I am still running into the same issue. I see the first Install Wizard pop-up and then it disappears before I even get to the Terms and Conditions page. I feel that I have all the necessary steps now, but I can't seem to figure it out. I also haven't been able to find a .zip file of the update to manually run the RUU. Any ideas on what my options are?
Click to expand...
Click to collapse
Just let it sit there after the first pop up, it does some background process and then the wizard starts , some times it takes more then 5 minutes, depends on your computer.
Sent from my HTC One_M8 using Tapatalk
grigoriisi said:
Just let it sit there after the first pop up, it does some background process and then the wizard starts , some times it takes more then 5 minutes, depends on your computer.
Click to expand...
Click to collapse
I waited for about 30 minutes and kept an eye on the process on task manager. The set-up application exited about a minute after the first loading screen passed and nothing happened afterward. I had tested out a Lollipop RUU from HTC and was able to immediately get to the Terms and Agreements page after the loading screen; however, after accepting it, the install wizard also shut down and did not give me any further screens/pop-ups. My computers is running on Windows 10 right now; would that possibly be a reason why I can't proceed further?
mtruong15 said:
I waited for about 30 minutes and kept an eye on the process on task manager. The set-up application exited about a minute after the first loading screen passed and nothing happened afterward. I had tested out a Lollipop RUU from HTC and was able to immediately get to the Terms and Agreements page after the loading screen; however, after accepting it, the install wizard also shut down and did not give me any further screens/pop-ups. My computers is running on Windows 10 right now; would that possibly be a reason why I can't proceed further?
Click to expand...
Click to collapse
Right click on the ruu exe and choose compatibility mode windows 7. It works like that for me on Windows 10.
Sent from my HTC One_M8 using Tapatalk
mtruong15 said:
However, when I used the MM .exe file (RUU_M8_UL_M60_SENSE70_ATT_MR_Cingular_US_6.20.502.5_combined), I am still running into the same issue. I see the first Install Wizard pop-up and then it disappears before I even get to the Terms and Conditions page.
Click to expand...
Click to collapse
You didn't properly describe that issue before (all you said was "haven't had much luck" with the RUU, which didn't really tell us anything), otherwise I could have given some insight earlier. Always be specific as possible when describing errors, failures, issues.
RUU can be very finicky with PC configuration. Win7 and USB2.0 have the best luck with compatibility. You can try compatibility mode, as the previous response indicated. Also try a different USB port. Also check if your PC has C++ 2008 Package installed, and if not, install it: https://www.microsoft.com/en-us/download/details.aspx?id=29
But if these still don't help, you may need to try a different PC, if possible.
redpoint73 said:
RUU can be very finicky with PC configuration. Win7 and USB2.0 have the best luck with compatibility. You can try compatibility mode, as the previous response indicated. Also try a different USB port. Also check if your PC has C++ 2008 Package installed, and if not, install it: https://www.microsoft.com/en-us/download/details.aspx?id=29
But if these still don't help, you may need to try a different PC, if possible.
Click to expand...
Click to collapse
I tried compatibility mode for Win7 and Win8, and attempted through various USB ports, but still couldn't get it to budge. I double checked the C++ Packages and already had the 2008 package and the others listed in another XDA post I found. I ended up trying on a friend's computer who was running Win8.1 and surprisingly got it to work in one go without any errors at all. Figures the problem was my computer that didn't allow me to run the .exe.
Thanks for your patience and guidance; I really do appreciate you helping me out. I was ready to throw in the towel a few days ago, but was able to get everything to work with your help.
mtruong15 said:
Thanks for your patience and guidance; I really do appreciate you helping me out. I was ready to throw in the towel a few days ago, but was able to get everything to work with your help.
Click to expand...
Click to collapse
You are very welcome, and glad to see you go the RUU to work.
If you still want to root, it looks like you've learned from your mistakes; but to summarize the proper root method:
1) Unlock bootloader again via HTCDev.com. If you still have the bin code from last time, you might be able to reuse it, with the proper fastboot command, to unlock the bootloader. Otherwise, just go through the HTCDev.com process again, and get a new code.
2) Install current TWRP 3.0. TWRP files, and instructions to install by fastboot method are here: https://twrp.me/devices/htconem8gsm.html
3) Download and flash SuperSU in TWRP. Recommend latest stable version SupersSU 2.76: https://download.chainfire.eu/969/SuperSU/UPDATE-SuperSU-v2.76-20160630161323.zip