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
Related
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 trying my damnedest for the past week to un-root my HTC One, but I can't seem to make any progress. Unfortunately, I believe I may have flashed the wrong ROM at one point, making my situation much worse. I think the kernel is totally wrong, the CID, and god only knows what else. I never S-OFFed, so I can't imagine i screwed things up too bad, but nevertheless, I have had no luck running a valid RUU in Windows nor gotten fastboot to successfully flash the stock rom zip. I have an AT&T HTC One M7, currently showing the following info:
INFOversion: 0.5
INFOversion-bootloader: 1.54.0000
INFOversion-baseband: 4A.18.3263.15
INFOversion-cpld: None
INFOversion-microp: None
INFOversion-main: 3.06.1700.10
INFOversion-misc: PVT SHIP S-ON
INFOmeid: 00000000000000
INFOproduct: m7_ul
INFOplatform: HBOOT-8064
INFOmodelid: PN0712000
INFOcidnum: CWS__001
INFObattery-status: good
INFObattery-voltage: 4184mV
INFOpartition-layout: Generic
INFOsecurity: on
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: dirty-94cf81a8fd
INFOhbootpreupdate: 11
INFOgencheckpt: 0
all: Done!
All I want to do is un-root and restore the device entirely back to stock and somehow I've really messed my phone up. Total noob here, appreciating any direction and advice to get my phone back to it's original state. Can anyone help? Thanks in advance!
Move Thread
Would anyone know how I could move this thread to the more general HTC One board (http://forum.xda-developers.com/forumdisplay.php?f=2117)? Since this is not a carrier specific problem and nobody in the AT&T forum seem to know what to do either, it would make sense for more HTC One users to see this as they may have more advice. thanks
When you tried to Flash the stock RUU did you make sure to relock the bootloader first?
RespectTheTech said:
When you tried to Flash the stock RUU did you make sure to relock the bootloader first?
Click to expand...
Click to collapse
yep and I got Error 155 every time, after more than a handful of attempts. I tried troubleshooting the error by reading more than a dozen threads here on xda, but still could not get anything to work.
jinkus said:
yep and I got Error 155 every time, after more than a handful of attempts. I tried troubleshooting the error by reading more than a dozen threads here on xda, but still could not get anything to work.
Click to expand...
Click to collapse
Earlier today I had completely bricked my phone and inadvertently deleted the entire OS so that it wouldn't boot any further than the HTC Logo.
The Forum won't let me post links yet because my lack of posts so I will PM you the links I used to get back to stock.
RespectTheTech said:
Earlier today I had completely bricked my phone and inadvertently deleted the entire OS so that it wouldn't boot any further than the HTC Logo.
The Forum won't let me post links yet because my lack of posts so I will PM you the links I used to get back to stock.
Click to expand...
Click to collapse
That RUU file by DesignGears is one of the few RUU's I've attempted to use, and have gotten Error 155 with. In the video, the guy mentions that while running the RUU, the Image Version for both From and TO should be the same. Mine are not. The From version is 3.06.1700.10 and the To version is 1.26.502.12. So the ROM/kernel on my phone is for the Google Play Edition, yet I do not have a Google Play Edition phone.
If I try using fastboot to flash a 1.26.502.12 AT&T rom.zip file I downloaded, I get this error: usb_write failed with status e00002be
jinkus said:
That RUU file by DesignGears is one of the few RUU's I've attempted to use, and have gotten Error 155 with. In the video, the guy mentions that while running the RUU, the Image Version for both From and TO should be the same. Mine are not. The From version is 3.06.1700.10 and the To version is 1.26.502.12. So the ROM/kernel on my phone is for the Google Play Edition, yet I do not have a Google Play Edition phone.
If I try using fastboot to flash a 1.26.502.12 AT&T rom.zip file I downloaded, I get this error: usb_write failed with status e00002be
Click to expand...
Click to collapse
The Image versions I had didn't match either, but weren't off as far as yours. Mine was From 1.26.502.15 and To 1.26.502.12. So even though he says they have to match, They don't. Wondering if they problem lies with the Goog Edition ROM. Have you tried to clean install any of the AT&T ROM's? Curious if you are able to do that then it should let you Relock the bootloader and then Install the RUU. Hypothetically anyways.
I was running LiquidSmooth after obtaining S-OFF using Revolutionary on my Thunderbolt I had bought online. After a few days the charging port would no longer charge the phone. The device is under warranty so I readied a return and ordered an external battery charger to get the Thunderbolt back to stock.
My external charger showed up in the mail and I fully charged the battery while getting the files required to follow this guide to returned to a relocked bootloader, S-ON, and the "stock" Android. I was able to unroot the phone but after flashing the PG05IMG_no_hboot_2.11.605.19.zip, it returned "Failed-UZ" (or something along those lines, I know it failed to unzip though). After 3-4 retries, it returned the same error.
I decided to use a RUU executable from Shipped-Roms (stupid of me, I was S-OFF) and it failed with "wrong bootloader version". Now I believe I've dug a hole here.
Rather than digging a bit more and "throwing" the phone into it, I figured I'd ask for a bit of help.
--
My goal is to return it to the most stock it could be. Just so I don't get hit the replacement fee. This charging port is a bit finicky but it does work. It just takes a few plugs/unplugs to get it into FASTBOOT USB and recognized by the PC. I've tried using a couple methods to return to some sort of working order and it runs through and gives "Checking . . PG05IMG.zip..." then it just goes right back to HBOOT.
I'm unable to get into the phone and it doesn't help that the phone is old so 9/10 links are dead or lead to useless advertisements. Excuse my frustration as I understand some of what I'm doing. I'm just getting increasingly aggravated at the idea of paying for an out-of-date phone when it's under the seller's warranty.
Code:
*** UNLOCKED ***
MECHA XD SHIP S-ON
HBOOT-1.05.0000
MICROP-/
RADIO-1.48.00.0930w_3
eMMC-boot
Jul 19 2011,14:51:08
Many thanks ahead of time!
- H00k3d0nCr0n1cz / Zero
Can you give me the results of fastboot getvar all
Also you'll need to relock the boot loader in order to run an ruu(.zip or .exe)
Sent from my HTC One using Tapatalk
Thanks for the reply! I appreciate it. I can't seem to find much out between the missing downloads and my experience with this phone!
Let me get this half-working port to connect and I'll post the output ASAP (prolly 10 or so mins tops, it connects when it feels like it).
EDIT, EDIT:
It's all about using an OEM cable . It didn't like my Moto or Sammy cable at all. Here's the output:
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.05.0000
(bootloader) version-baseband: 1.48.00.0930w_3
(bootloader) version-cpld: None
(bootloader) version-microp: /
(bootloader) version-main: 7.02.605.10
(bootloader) serialno: HT16TS018000
(bootloader) product: mecha
(bootloader) platform: HBOOT-7630
(bootloader) modelid: PG0510000
(bootloader) cidnum: VZW__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3678mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-47e85ff5
(bootloader) hbootpreupdate: 12
(bootloader) gencheckpt: 0
(bootloader) region-id: not support
all: Done!
finished. total time: 0.042s
version-main: 7.02.605.10 < Wouldn't that be ICS? So I'm stuck where the phone is expecting ICS or higher? It'd be unfortunate if I'm bricked due to not having a newer update.
Also, bootloader is relocked.
Anyone?
iamz3r0 said:
Anyone?
Click to expand...
Click to collapse
sorry,apparently i missed a notification of your other response
anyway,yes that is the ICS main version. you will need to install a recovery,then flash the "main version low" zip in recovery. you can then run the GB ruu.
basically you can follow this guide: http://androidforums.com/thunderbolt-all-things-root/689221-how-downgrade-root-ics.html
just skip the part about runing revolutionary im pretty sure the downgrade ruu is a release keys version,meaning you can let the phone OTA to current afterward if you want to.
holler in that thread if you have questions and youll prolly get faster responses from me
scotty1223 said:
sorry,apparently i missed a notification of your other response
anyway,yes that is the ICS main version. you will need to install a recovery,then flash the "main version low" zip in recovery. you can then run the GB ruu.
basically you can follow this guide: http://androidforums.com/thunderbolt-all-things-root/689221-how-downgrade-root-ics.html
just skip the part about runing revolutionary im pretty sure the downgrade ruu is a release keys version,meaning you can let the phone OTA to current afterward if you want to.
holler in that thread if you have questions and youll prolly get faster responses from me
Click to expand...
Click to collapse
Thanks! If you didn't point that out to me I would've spent forever looking around.
I unlocked the bootloader and flashed the recovery .img inside of PG05IMGrecovery-ra-mecha-3.06-gnm.zip with fastboot. Then I booted into recovery and flashed the "main version low" zip from here. After that I was able to relock the bootloader and RUU back to normal.
While everything started up, the phone still doesn't charge.
I'm assuming there isn't a way to get rid of the "relocked" message? I'm not quite sure it matters though. The phone is running software from the manufacturer and the charging port still doesn't work correctly. I'm not quite sure unlocking the bootloader would cause that. :laugh:
iamz3r0 said:
Thanks! If you didn't point that out to me I would've spent forever looking around.
I unlocked the bootloader and flashed the recovery .img inside of PG05IMGrecovery-ra-mecha-3.06-gnm.zip with fastboot. Then I booted into recovery and flashed the "main version low" zip from here. After that I was able to relock the bootloader and RUU back to normal.
While everything started up, the phone still doesn't charge.
I'm assuming there isn't a way to get rid of the "relocked" message? I'm not quite sure it matters though. The phone is running software from the manufacturer and the charging port still doesn't work correctly. I'm not quite sure unlocking the bootloader would cause that. :laugh:
Click to expand...
Click to collapse
Correct,unlocking the bootloader definately cannot cause hardware malfunctions
Unfortunately,with the thunderbolt,relocked is the best you can do. Revolutionary installs a patched hboot,wich gives most of the benefits of a true,radio s off,but does not allow you to write to write-protected partitions. As such,the flag that signals hboot as to wether it is locked,relocked,or unlocked cannot be modified.
I'd say you should fine with warrantying your device with a.malfunctioning charge port.
Sent from my HTC PG09410 using Tapatalk 2
scotty1223 said:
Correct,unlocking the bootloader definately cannot cause hardware malfunctions
Unfortunately,with the thunderbolt,relocked is the best you can do. Revolutionary installs a patched hboot,wich gives most of the benefits of a true,radio s off,but does not allow you to write to write-protected partitions. As such,the flag that signals hboot as to wether it is locked,relocked,or unlocked cannot be modified.
I'd say you should fine with warrantying your device with a.malfunctioning charge port.
Sent from my HTC PG09410 using Tapatalk 2
Click to expand...
Click to collapse
Alright! Time to OTA to ICS and use this half-working TBolt til the replacement arrives.
I still don't miss my DROID3 but I need a newer phone
Thanks again for all your help!
--
EDIT: They accepted the phone with the bootloader relocked. Funny thing was, they were out of Thunderbolts! Instead they're sending me a Galaxy Nexus instead. Gonna go check out that KitKat.
iamz3r0 said:
Alright! Time to OTA to ICS and use this half-working TBolt til the replacement arrives.
I still don't miss my DROID3 but I need a newer phone
Thanks again for all your help!
--
EDIT: They accepted the phone with the bootloader relocked. Funny thing was, they were out of Thunderbolts! Instead they're sending me a Galaxy Nexus instead. Gonna go check out that KitKat.
Click to expand...
Click to collapse
GNex.... isn't that kind of outdated these days?
Couldn't you get something a bit newer, maybe a One X (4G) or a Nexus 4....
At least its not as bad as an iPhone 4S.
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 friends, recently got an M8 Att, its already S-Off, BL Unlocked, Tried CIDs BS_US001, BS_US002 and Super CID 11111111 tried to install UL/DEV Ruu from HTC dev site but alwasys got error 155.
Any suggestion or what am i doing wrong? Thanks in advance.
My getvar:
(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: 4.28.502.2
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HT4xxxxxxxxxxx
(bootloader) imei: 35xxxxxxxxxxxxxx
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul_ca
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B12000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 7f8e91a3
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.047s
Which RUU are you trying to flash? If it's the Sense 7/ Marshmallow RUU then you need to first flash 6.x firmware. I found the same exact version as in the name of the RUU and flashed that first then the RUU flashed without a problem.
Sent from my Nexus 5 using Tapatalk
Hey thanks for your reply, yep I'm trying to flash marshmallow ruu because is the only one I found, where can I found such 6.X firmware? Or how can get it?
firultd said:
Hey thanks for your reply, yep I'm trying to flash marshmallow ruu because is the only one I found, where can I found such 6.X firmware? Or how can get it?
Click to expand...
Click to collapse
Search Google for 6.12.1540.4 firmware. I used the one in the first result uploaded by Einwod.
Flash that via fastboot oem rebootRUU.
Twice. It will fail the first time, wait about a minute for the bootloader to reload and flash it again. Don't unplug your phone at all. Once you successfully flash the firmware, do fastboot reboot-bootloader to get back into fastboot, then you should be able to flash the RUU
Sent from my Nexus 5 using Tapatalk
What happens in case of any ruu installation error? phone won't boot right? Can flash att stock run to recover device? Don't wanna end with a brick
Which error? Are you familiar with fastboot at all? And HTC oem commands? I take no responsibility for your flashing but what I posted worked fine for me.
Sent from my Nexus 5 using Tapatalk
firultd said:
What happens in case of any ruu installation error? phone won't boot right? Can flash att stock run to recover device? Don't wanna end with a brick
Click to expand...
Click to collapse
Depends on the error. If the RUU errors out before it actually installs anything, your phone will probably boot normally. But if it partially installs, then an error, it may be a no-boot situation.
Yes, in most cases if your phone won't boot after an RUU error, going back to the AT&T RUU should get your phone working again. But if you actually were successful in updating (even partially) to MM firmware, you may need to flash LP firmware before the LP RUU will work.
Not sure why, but it seems to be a glitch with the MM RUU. To go from LP>MM you need to flash the MM firmware, then RUU. And MM>LP the vice versa is also true, you may need to flash LP firmware in order for the LP RUU to work properly.
Yes i personally do boot loader unlock s -off and all that stuff. Don't worry I know that all responsibility is mine. I mean if after flashing firmware ruu still give an error obviously device will not but isn't it? In that case I still can flash att 5.0 stock ruu?
redpoint73 said:
Depends on the error. If the RUU errors out before it actually installs anything, your phone will probably boot normally. But if it partially installs, then an error, it may be a no-boot situation.
Yes, in most cases if your phone won't boot after an RUU error, going back to the AT&T RUU should get your phone working again. But if you actually were successful in updating (even partially) to MM firmware, you may need to flash LP firmware before the LP RUU will work.
Not sure why, but it seems to be a glitch with the MM RUU. To go from LP>MM you need to flash the MM firmware, then RUU. And MM>LP the vice versa is also true, you may need to flash LP firmware in order for the LP RUU to work properly.
Click to expand...
Click to collapse
OK. Very clear explanation that's give me a better look of the situation. Will keep in mind and try. Thank s a lot.
So now that i have a real keyboard in front of me....
I had very similar issue as you just two days ago where I have an AT&T Branded M8 that is S-Off and had an unlocked bootloader and superCID and I was not able to flash any RUU besides the AT&T one. Although I didn't investigate a lot into why the other Dev RUUs (earlier versions) didn't flash, I was beating my head against the wall trying to get the newest Marshmallow Dev RUU to flash.
Since you are trying to flash an HTC rom, which is signed by HTC the zip in the RUU has to be decrypted with the correct key from HTC. I believe (I'm not an expert on this) the key is embedded into HBOOT. HTC changed the encryption key sometime ago so when you use a firmware that preceeds the key change, the HBOOT will not be able to decrypt the rom.zip file and it fails.
By flashing the firmware I mentioned earlier, it has the correct key to decrypt the zip in the RUU and flash it.
The steps that I followed to get my phone converted are below. The only assumption I am making is that you are able to get into fastboot mode and you have a working knowledge of fastboot commands on a Windows PC.
1. Boot phone into fastboot mode
2. PC command: fastboot oem rebootRUU (Puts the phone into HTC RUU mode)
3. PC command: fastboot flash zip firmware-6.12.1540.4.zip (Flashes the firmware onto the phone)
4. The above command will fail with: FAILED (remote: 90 hboot pre-update! please flush image again immediately)
Wait about a minute then...
5. PC command: fastboot flash zip firmware-6.12.1540.4.zip (Flashes the firmware onto the phone again)
6. PC command: fastboot reboot-bootloader (Restarts the bootloader)
7. At this point your phone should be ready to accept the Dev RUU RUU_M8_UL_M60_SENSE70_MR_BrightstarUS_WWE_6.12.1540.4.exe
8. Launch the RUU on the PC and follow the steps in the RUU Instructions to flash the phone.
9. After it successfully flashes the RUU it will reboot the phone and start optimizing the apps...and then it should drop you into the Welcome screen.
Now, the bricking your phone bit....You can read this thread about the errors you can get and how dangerous they are.
psychephylax said:
So now that i have a real keyboard in front of me....
I had very similar issue as you just two days ago where I have an AT&T Branded M8 that is S-Off and had an unlocked bootloader and superCID and I was not able to flash any RUU besides the AT&T one. Although I didn't investigate a lot into why the other Dev RUUs (earlier versions) didn't flash, I was beating my head against the wall trying to get the newest Marshmallow Dev RUU to flash.
Since you are trying to flash an HTC rom, which is signed by HTC the zip in the RUU has to be decrypted with the correct key from HTC. I believe (I'm not an expert on this) the key is embedded into HBOOT. HTC changed the encryption key sometime ago so when you use a firmware that preceeds the key change, the HBOOT will not be able to decrypt the rom.zip file and it fails.
By flashing the firmware I mentioned earlier, it has the correct key to decrypt the zip in the RUU and flash it.
The steps that I followed to get my phone converted are below. The only assumption I am making is that you are able to get into fastboot mode and you have a working knowledge of fastboot commands on a Windows PC.
1. Boot phone into fastboot mode
2. PC command: fastboot oem rebootRUU (Puts the phone into HTC RUU mode)
3. PC command: fastboot flash zip firmware-6.12.1540.4.zip (Flashes the firmware onto the phone)
4. The above command will fail with: FAILED (remote: 90 hboot pre-update! please flush image again immediately)
Wait about a minute then...
5. PC command: fastboot flash zip firmware-6.12.1540.4.zip (Flashes the firmware onto the phone again)
6. PC command: fastboot reboot-bootloader (Restarts the bootloader)
7. At this point your phone should be ready to accept the Dev RUU RUU_M8_UL_M60_SENSE70_MR_BrightstarUS_WWE_6.12.1540.4.exe
8. Launch the RUU on the PC and follow the steps in the RUU Instructions to flash the phone.
9. After it successfully flashes the RUU it will reboot the phone and start optimizing the apps...and then it should drop you into the Welcome screen.
Now, the bricking your phone bit....You can read this thread about the errors you can get and how dangerous they are.
Click to expand...
Click to collapse
Well, lets do it, just give me some hours to backup and will try and post results, again thanks for your time.
A tiny question before proceed, firmware zip file is 30.88 MB size? Its the right one? feel like its too small
firultd said:
A tiny question before proceed, firmware zip file is 30.88 MB size? Its the right one? feel like its too small
Click to expand...
Click to collapse
Yeah, it's about 30mb (31626 KB)
Here's the md5 sum from my file: b5add816536334711fb2baa6e8a4d134
HAve no words to describe the happines to see my phone just like a real dev edition, many thanks to all of you for your time. Whole process was right and phone is working awesome.
Glad you got it working.
Sent from my Redmi Note 2 using Tapatalk
firultd said:
A tiny question before proceed, firmware zip file is 30.88 MB size? Its the right one? feel like its too small
Click to expand...
Click to collapse
Note that firmware.zip only contains a subset of partitions including hboot, radio, kernel, recovery, WiFi, Bluetooth, Audio and a few others. It doesn't contain the ROM, which is a much larger file (1.5 GB or so); nor is it a full RUU or ROM.zip, etc.
Firmware is important, but not a large file.
Any harm in flashing the 6.12.1540.4 but staying on Lollipop?
I don't know, but why would you want to stay on lollipop?
Sent from my Redmi Note 2 using Tapatalk