I bought a HTC One M8 AT&T phone from eBay that was rooted. I'm not a fan of being rooted, and I've rooted and unrooted in the past, so I THOUGHT i was familiar with the process. I am just about ready to pull my hair out. I've spend a good 5-6 hours trying all sorts of methods. Maybe someone can help me. Here's the scoop:
I have S-on. I have TWRP recovery. I have HTC sync drivers installed on my computer. I have NO OS installed (I didn't back anything up not realizing I deleted the back up). I have tried flashing a boot img from CMD of my computer directly onto the phone but NOTHING i attempt to flash will work. I have zip files from a 1.158.502.1, I have been attempting to flash from the "install" folder on TWRP with NO avail. The CMD prompt: Fastboot Devices DOES recognize my device in my PC. Please help me.
Did you put the .zip on your SD card, internal? Where is the .zip located? Really, make sure CID matches ATT, relock bootloader, and run from here: http://www.htc.com/us/support/htc-one-m8-att/news/
You can't screw this phone up, you just can't.
"Did you put the .zip on your SD card, internal? Where is the .zip located? Really, make sure CID matches ATT, relock bootloader, and run from here: URL
You can't screw this phone up, you just can't."
The .zip is on my sd card. THe CID matches ATT. I do not know how to relock the bootloader. That's something I haven't tried. I'm trying NOT to screw the phone up, I don't think I am, it's just that nothing is working.
1st off, don't panic! You didn't screw up your phone.
I'm not sure what you're trying to say the problem is, but:
If your zip file is a twrp backup, then you need to put it in the corresponding twrp backups folder (sd_ext/twrp/backups/serialnumber/backupfoldername/). Otherwise, if your zip file is an RUU then you'll need to place it at the root of your sd and rename it to 0P6BIMG.zip then flash it from bootloader.
You need to flash an OS before you flash the corresponding firmware and boot image.
Anyhow, do provide more details!
cami0488 said:
I bought a HTC One M8 AT&T phone from eBay that was rooted. I'm not a fan of being rooted, and I've rooted and unrooted in the past, so I THOUGHT i was familiar with the process. I am just about ready to pull my hair out. I've spend a good 5-6 hours trying all sorts of methods.
Click to expand...
Click to collapse
Every Android phone is different, and has its own learning curve. You should also not apply methods meant for other phones, only for the M8.
cami0488 said:
I have S-on. I have TWRP recovery. I have HTC sync drivers installed on my computer. I have NO OS installed (I didn't back anything up not realizing I deleted the back up).
Click to expand...
Click to collapse
Did you delete all the partitions in the TWRP "Advanced wipe" option?
cami0488 said:
I have tried flashing a boot img from CMD of my computer directly onto the phone but NOTHING i attempt to flash will work. I have zip files from a 1.158.502.1, I have been attempting to flash from the "install" folder on TWRP with NO avail.
Click to expand...
Click to collapse
What do you mean it "nothing I attempt will work"? If you aren't specific about what you attempted, this doesn't tell us anything!!!
What was your command syntax? Where did you get the file? What is the outcome (error message, or just no boot into OS)?
Also, this is never going to get your phone running in itself, anyway. You realize boot.img is just a kernel (and a few other small things) and not the whole ROM? If you deleted the system partition, you need to restore an entire ROM (over 1GB for a Sense ROM) not just boot.img, which is about 13 MB?
---------- Post added at 09:54 AM ---------- Previous post was at 09:51 AM ----------
shirreer said:
Anyhow, do provide more details!
Click to expand...
Click to collapse
Agreed, the OP hasn't provided nearly enough info.
Its not remotely clear what the OP has even tried flashing.
Saying he "tried a bunch of stuff" is not helpful. OP needs to describe every step, what files used, and the outcomes with error messages or other results.
Need to do fastboot getvar all, and post the output (be sure to delete IMEI and serial numbers before posting the output, as these are personal data).
---------- Post added at 09:56 AM ---------- Previous post was at 09:54 AM ----------
hack14u said:
Really, make sure CID matches ATT, relock bootloader, and run from here: http://www.htc.com/us/support/htc-one-m8-att/news/
Click to expand...
Click to collapse
Agree that the OP probably just need to relock the bootloader and run the Lollipop RUU.
Not only will this get the phone up and running again in (nearly) stock condition, but will also update it to the most current Android LP version.
redpoint73 said:
Every Android phone is different, and has its own learning curve. You should also not apply methods meant for other phones, only for the M8.
Click to expand...
Click to collapse
Yeah, I certainly learned that the hard way.
Did you delete all the partitions in the TWRP "Advanced wipe" option?
Click to expand...
Click to collapse
Yes unfortunately I did. No TWRP back ups exsist.
What do you mean it "nothing I attempt will work"? If you aren't specific about what you attempted, this doesn't tell us anything!!!
Click to expand...
Click to collapse
I attemped to flash the rom 155.502.18 via a zip file to the phone. Nothing. I attempted loading up a boot.img from some YouTube view I watched that I can't link because I don't have 10 posts on here yet.
What was your command syntax? Where did you get the file? What is the outcome (error message, or just no boot into OS)?
Click to expand...
Click to collapse
I'm sorry, I don't know what a command syntax is. I got the file right off here in XDA Forums in the ROM's folder for AT&T stock rom. The error just says "failed" and will not write. It seems to keep missing an "MD5" file. The error in CMD prompt is that it just doesn't go anywhere after I type in >Flashboot Flash Boot boot.img
Also, this is never going to get your phone running in itself, anyway. You realize boot.img is just a kernel (and a few other small things) and not the whole ROM? If you deleted the system partition, you need to restore an entire ROM (over 1GB for a Sense ROM) not just boot.img, which is about 13 MB?
Click to expand...
Click to collapse
I did not know that. I was just trying to figure out how to get this to work again. Yes, I did delete the system partition, so I guess I will have to restore an entire ROM (1gb of space for a Sense ROM). The problem is, I don't know which files from these .zip files on XDA are the correct files, and I can't seem to find any videos on YouTube that show the problems I'm having.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Agreed, the OP hasn't provided nearly enough info.
Its not remotely clear what the OP has even tried flashing.
Saying he "tried a bunch of stuff" is not helpful. OP needs to describe every step, what files used, and the outcomes with error messages or other results.
Need to do fastboot getvar all, and post the output (be sure to delete IMEI and serial numbers before posting the output, as these are personal data).
Click to expand...
Click to collapse
I apologize for the lack of information. I have some screenshots of the errors and what the TWRP recovery bootloader looks like, but I can't attach my image files to this post because It says I need 10 more posts. Otherwise I would have tried to post more information. "he said". I am a woman*. I did try a fastboot getvar all before, so I'm aware what that is, but I'll have to post short messages around here to reach my 10 post mark so i can start including some screenshot images.
Agree that the OP probably just need to relock the bootloader and run the Lollipop RUU.
Click to expand...
Click to collapse
Relative question. What is the difference between manually flashing a ROM through the CMD prompt on my comptuper vs "RUU". I don't have any current operating system on the phone so I can no longer go into the settings and turn off USB debugging and whatever else I've seen instructions on using RUUs. Which all seem to indicate I need an OS before even doing that option.
Not only will this get the phone up and running again in (nearly) stock condition, but will also update it to the most current Android LP version.
Click to expand...
Click to collapse
THAT IS THE GOAL! I would be SOoooooooooooooooooooooooo happy if and when that can finally happen. Annnnnd I"ll never be buying anymore phones that are rooted again, because I don't want to go through this annoying process of unrooting. Now I know why the seller didn't unroot!, lolAnd THANK YOU to all for your replies. I shall post more information
shirreer said:
1st off, don't panic! You didn't screw up your phone.
I'm not sure what you're trying to say the problem is, but:
If your zip file is a twrp backup, then you need to put it in the corresponding twrp backups folder (sd_ext/twrp/backups/serialnumber/backupfoldername/). Otherwise, if your zip file is an RUU then you'll need to place it at the root of your sd and rename it to 0P6BIMG.zip then flash it from bootloader.
You need to flash an OS before you flash the corresponding firmware and boot image.
Anyhow, do provide more details!
Click to expand...
Click to collapse
I got this .zip file from the XDA ROMs folder off here. I'm not sure if it's an RUU file. However it is not a backup, or so it wasn't labled that way. It was labled as the "stock ROM"
Try what I said. Before, run the command fastboot OEM lock. That will relock the bootloader so you don't throw an error when you run the RUU. The RUU will wipe everything and bring it back to ATT stock. From there you can learn more commands, and how to "fix" things. An RUU is the stock files packaged as a .exe file, you actually run it from your PC like you were installing a piece of software, but it goes to your phone. Don't worry about not having this, or that, it will fix it for you, unless something else is not set right. Give it a shot, you have nothing to lose, literally. Oh, and I always run RUU's from fastboot USB so it detects it pretty quick.
hack14u said:
Try what I said. Before, run the command fastboot OEM lock. That will relock the bootloader so you don't throw an error when you run the RUU. The RUU will wipe everything and bring it back to ATT stock. From there you can learn more commands, and how to "fix" things. An RUU is the stock files packaged as a .exe file, you actually run it from your PC like you were installing a piece of software, but it goes to your phone. Don't worry about not having this, or that, it will fix it for you, unless something else is not set right. Give it a shot, you have nothing to lose, literally. Oh, and I always run RUU's from fastboot USB so it detects it pretty quick.
Click to expand...
Click to collapse
See, I read about using RUU, but I also read that if you have "S-on" you can't flash anything on the device unless you do it through the cmd prompt. That's what caused my problems to begin with, I didn't know where to start after having accidentally wiped my OS, backups, and damn near everything. So it can still work via the RUU method with my S-On? I shall try it tomorrow after work.
From CMD, type:
fastboot getvar all
Take a picture and post it, so we can find you a rom that's suitable for your CID! From then on its really simple.
cami0488 said:
Yes unfortunately I did. No TWRP back ups exsist.
Click to expand...
Click to collapse
Forgive me while I rant, but I see this all too often (wiping partitions when you don't know what they are). Quite frankly, if you don't know what you are wiping, or what the result will be, then don't wipe it. It doesn't take much research to find out what each wipe option (partition) is. There are far too many post on here to the effect "I wiped system and now I have no OS". Well, seeing as system and OS are the same thing, that is an obvious outcome. Plus, these options are called "Advanced" for a reason. If you don't have advanced knowledge (or at least research what the options mean), don't mess with them.
Further, wiping everything in TWRP Advanced Wipe options means you wiped your internal storage and removable SD (if you have one), both of which are the possible locations for TWRP backups (internal storage is the default backup location). So again, since you wiped everything, of course you wiped your TWRP backups.
cami0488 said:
I attemped to flash the rom 155.502.18 via a zip file to the phone. Nothing. I attempted loading up a boot.img from some YouTube view I watched that I can't link because I don't have 10 posts on here yet.
Click to expand...
Click to collapse
First of all, that is not a valid OS number for the M8, and the likely reason is that you typed it incorrectly. You really need to post specifically and correctly, otherwise we can't know what you are doing. It might seem unimportant or nitpicky to you, but tiny differences in these numbers can have big implications, so you really need to try harder to get it right.
Your description is still far to vague to mean anything. "a boot.img from some YouTube" Do you seriously think that is going to help us help you at all? There are thousands (if not millions) of videos on YouTube. We can't have any idea what that means. You really do need to give the exact steps you've tried and the exact files, if you want proper help.
While you can't use the link function to post links, if needed you can post the text. If the forum still won't allow it, just obfuscate the URL with "dotcom" at the end or something similar.
cami0488 said:
I'm sorry, I don't know what a command syntax is. I got the file right off here in XDA Forums in the ROM's folder for AT&T stock rom. The error just says "failed" and will not write. It seems to keep missing an "MD5" file. The error in CMD prompt is that it just doesn't go anywhere after I type in >Flashboot Flash Boot boot.img
Click to expand...
Click to collapse
Syntax is just the exact command as you typed it (order of the typed words, spelling, etc.). This is extremely important, as a single typo such as a wrong character, improper order, etc. will cause the command to fail.
For instance (and I'm not sure if what you posted above is the exact syntax you actually used or not) for the above command, there is no such thing as "Flashboot", it should be fastboot. And fastboot/adb commands typically don't have the command words capitalized like you have it. Exception is if a directory or filename has caps, in which case it needs to match exactly.
cami0488 said:
"he said". I am a woman*.
Click to expand...
Click to collapse
My apologies there. Pesky pronouns! Of course, on the internet, unless we know beforehand, we can only guess at the proper pronoun; as it often gets impractical to type "he/she" or non-gender specific "they". I'll try to get it right in this thread, moving forward.
cami0488 said:
I did try a fastboot getvar all before, so I'm aware what that is, but I'll have to post short messages around here to reach my 10 post mark so i can start including some screenshot images.
Click to expand...
Click to collapse
Just cut and paste the getvar data. In Windows command prompt, you can right mouse click, select "mark" to highlight the desired getvar text; then Ctrl-C to copy (then just right click Paste or Ctrl-V to paste into an XDA forum message).
---------- Post added at 10:22 AM ---------- Previous post was at 10:15 AM ----------
cami0488 said:
Relative question. What is the difference between manually flashing a ROM through the CMD prompt on my comptuper vs "RUU". I don't have any current operating system on the phone so I can no longer go into the settings and turn off USB debugging and whatever else I've seen instructions on using RUUs. Which all seem to indicate I need an OS before even doing that option.
Click to expand...
Click to collapse
USB debugging only affects adb use while the phone is running. It doesn't affect fastboot, and fastboot will work even when no OS. Further, RUU only requires fastboot, and even then only to reboot into RUU mode.
---------- Post added at 10:24 AM ---------- Previous post was at 10:22 AM ----------
cami0488 said:
I got this .zip file from the XDA ROMs folder off here. I'm not sure if it's an RUU file. However it is not a backup, or so it wasn't labled that way. It was labled as the "stock ROM"
Click to expand...
Click to collapse
If you don't understand what it is, you shouldn't be flashing it. You haven't sufficiently described what it is (or linked the location) so we can't possibly know what it is, or properly help with it, either.
Honestly, no offense intended, it seems like your understanding and knowledge of what you are doing is pretty shaky. I'd suggest reading up for an hour or so of the basic tutorials, guides, Index threads, etc. before doing anything more with the phone (aside from RUU, which is what I am about to recommend for you).
---------- Post added at 10:32 AM ---------- Previous post was at 10:24 AM ----------
cami0488 said:
See, I read about using RUU, but I also read that if you have "S-on" you can't flash anything on the device unless you do it through the cmd prompt.
Click to expand...
Click to collapse
This is completely false.
You only need s-off to flash hboot, radio, change CID/MID, and a few other things. You can flash M8 ROMs, kernels, and a good number of other things from TWRP with s-on. Just find the proper desire ROM, and put it on removable SD or adb push to internal storage; then boot into TWRP and flash the ROM to get OS back.
But RUU is the best option for you.
cami0488 said:
So it can still work via the RUU method with my S-On?
Click to expand...
Click to collapse
Absolutely.
You will need to relock the bootloader with the command: fastboot oem lock
After that, verify in bootloader that it says RELOCKED near the top of the screen.
Then just run the following RUU to get the phone running, and also updated to AT&T Lollipop: http://dl3.htc.com/application/RUU_M8[email protected]50319A_40.45.C33065.00_F_release_426617_signed_2.exe
Rant away, I thought I was pretty clear on the first page Just don't confuse anyone with M_7 in the link, lol...
hack14u said:
Just don't confuse anyone with M_7 in the link, lol...
Click to expand...
Click to collapse
Yeah, the "M" and the "7" has nothing to do with the M7. Its just truncated from: RUU_M8[email protected]50319A_40.45.C33065.00_F_release_426617_signed_2
redpoint73 said:
The above message and rant
Click to expand...
Click to collapse
Thank you for your response. It is much appreciated. However there is no need for the reprimand. What has happen has happen, and I have already decided that I will never again buy a rooted phone with the intention of unrooting it myself. What worked for me on my Xperia Z2, Galaxy Note 2, Galaxy S2, and HTC Evo is obviously nothing similar to what is going on here with the HTC M8. Therefore I will avoid a situation like this entirely by never attempting to unroot phones again. (I'm not personally a fan of flashing ROMs anyways)
Anyways, I'm going to try locking the bootloader as you instructed now, and then downloading the RUU file from HTC. Thanks again. I'll keep this updated.
shirreer said:
From CMD, type:
fastboot getvar all
Take a picture and post it, so we can find you a rom that's suitable for your CID! From then on its really simple.
Click to expand...
Click to collapse
Thank you sir -
hack14u said:
Try what I said. Before, run the command fastboot OEM lock. That will relock the bootloader so you don't throw an error when you run the RUU. The RUU will wipe everything and bring it back to ATT stock. From there you can learn more commands, and how to "fix" things. An RUU is the stock files packaged as a .exe file, you actually run it from your PC like you were installing a piece of software, but it goes to your phone. Don't worry about not having this, or that, it will fix it for you, unless something else is not set right. Give it a shot, you have nothing to lose, literally. Oh, and I always run RUU's from fastboot USB so it detects it pretty quick.
Click to expand...
Click to collapse
Just relocked the bootloader as you instructed
Downloading the RUU that RedPoint73 provided in his last post. Once that is downloaded, All I have to do is run the .exe program like normal and it should prompt me to a location where I can flash the information to the phone?
While i'm sitting here waiting for the RUU to download. I had yet another question. The rooted ROM that the phone was originally flashed with was Android High Definition Mike1986. For whatever reason, it would not ever let us connect to Google Play. Anytime we reboot, hard reset, factory data reset, or format the whole thing back to default settings we would always get the same message "google play services are not available". Now that was a problem of the ROM I stated, but is that related to the ROM that is flashed, or the phone itself?
Ugh oh. So I decided to run the RUU. The phone looked like what seemed to be installing. But the installation estimates it take 10 mins. I's been 20 minutes and is still 0/6 completed. I think something is wrong.
cami0488 said:
While i'm sitting here waiting for the RUU to download. I had yet another question. The rooted ROM that the phone was originally flashed with was Android High Definition Mike1986. For whatever reason, it would not ever let us connect to Google Play. Anytime we reboot, hard reset, factory data reset, or format the whole thing back to default settings we would always get the same message "google play services are not available". Now that was a problem of the ROM I stated, but is that related to the ROM that is flashed, or the phone itself?
Click to expand...
Click to collapse
It probably didn't have any gapps package installed.
---------- Post added at 07:01 PM ---------- Previous post was at 07:00 PM ----------
cami0488 said:
Ugh oh. So I decided to run the RUU. The phone looked like what seemed to be installing. But the installation estimates it take 10 mins. I's been 20 minutes and is still 0/6 completed. I think something is wrong.
Click to expand...
Click to collapse
It looks like it connected, let us know if it worked, like I said before, if it doesn't, there is something else wrong.
---------- Post added at 07:04 PM ---------- Previous post was at 07:01 PM ----------
I don't think I have ever seen any of that after fastboot oem lock. Has anyone else seen anything like that? Something looks very strange, like all of it.
---------- Post added at 07:10 PM ---------- Previous post was at 07:04 PM ----------
Oh ya, ARHD is the ROM you are referring to, some of the best folks out there, great work.
hack14u said:
It probably didn't have any gapps package installed.
Click to expand...
Click to collapse
I found this site - http://www.droidviews.com/restore-att-htc-one-m8-stock-firmware/ that seems to also to have directions to do the exact thing i"m doing now. But the very first part of the instruction yet again says "S-OFF is REQUIRED. It connected, and found the phone, but it stays stuck on that screen right there. I have tried retrying this 3 times. Waiting 20 mins a piece with no progress.
Related
I am trying to run the OTA.
I'm rooted, s-off, etc. so, in order to do this, I had to flash stock recovery and also enable all the apps that I had disabled.
When I try to run the OTA, it fails. The log says "unexpected content in system/build.prop".
I then realized that some "root" apps modify the build.prop, so I uninstalled all of them and rebooted the phone. However that didn't work —OTA still fails for the same reason.
Could someone could tell me what RUU (or stock nandroid or other file) I should download which would allow me to extract a default build.prop??
Thanks!
syntropic said:
I am trying to run the OTA.
I'm rooted, s-off, etc. so, in order to do this, I had to flash stock recovery and also enable all the apps that I had disabled.
When I try to run the OTA, it fails. The log says "unexpected content in system/build.prop".
I then realized that some "root" apps modify the build.prop, so I uninstalled all of them and rebooted the phone. However that didn't work —OTA still fails for the same reason.
Could someone could tell me what RUU (or stock nandroid or other file) I should download which would allow me to extract a default build.prop??
Thanks!
Click to expand...
Click to collapse
Are you SuperCID? If so, there is no need to return to stock.
If not, here are the instructions:
S-OFF ONLY! How to get supercid
1. Have adb and fastboot set up. There are guides all over xda and google
2. Connect phone to PC and open terminal
3. Type "adb devices" to make sure phone is connected to PC
4. Type "adb reboot bootloader"
5. Once in fastboot type "fastboot devices" to make sure fastboot sees your device
6. Type "fastboot oem rebootRUU"
7. Once in black screen that says HTC you are in ruu mode
8. Type "fastboot oem writecid 11111111"
9. After a successful cid overwrite type "fastboot reboot-bootloader"
10. Profit! You are now supercid!!
(via @skulldreamz from this thread)
Once you do that, you will never need to get an OTA. You will always have the latest and greatest before your carrier does.
---------- Post added at 07:42 PM ---------- Previous post was at 07:37 PM ----------
But yes, your problem probably lies with your /system partition being modified.
If you have Xposed installed, that would also lead to these problems, since it modifies /system
xunholyx said:
Are you SuperCID? If so, there is no need to return to stock.
If not, here are the instructions:
{...}
[/COLOR]But yes, your problem probably lies with your /system partition being modified.
If you have Xposed installed, that would also lead to these problems, since it modifies /system
Click to expand...
Click to collapse
Ok.. then it's xposed. Thanks!
If I do superCID (something I never thought was necessary since I am probably going to stay with t-mobile), then how do I install the OTA? I have a copy of the OTA which already automatically downloaded (saved a copy on Google Drive). How does having superCID bypass the updater-script which does all those pre-update checks?
syntropic said:
Ok.. then it's xposed. Thanks!
If I do superCID (something I never thought was necessary since I am probably going to stay with t-mobile), then how do I install the OTA? I have a copy of the OTA which already automatically downloaded (saved a copy on Google Drive). How does having superCID bypass the updater-script which does all those pre-update checks?
Click to expand...
Click to collapse
If you are SuperCID, you won't need OTAs. As soon as the newest version comes out, you'll be able to install it way before your carrier updates (unless your carrier gets the first HTC update, good luck with that).
As soon as the new stuff comes out, being SuperCID means you can use firmware from any carrier (gsm or cdma dependant) and update to the newest version.
5.0 is coming soon ~ might be up to a three month wait if not SuperCID. Just sayin.............
Even if I am using the stock? What you are describing sounds like AOSP or genuine nexus-type android updates. I wouldn't even know how to install them. I have never actually dealt with "updates" before. In the past on other phones on which I ran custom ROMs, "updates" typically came when whoever was creating the Rom, generated a new Rom which included the android update.
syntropic said:
Even if I am using the stock? What you are describing sounds like AOSP or genuine nexus-type android updates. I wouldn't even know how to install them. I have never actually dealt with "updates" before. In the past on other phones on which I ran custom ROMs, "updates" typically came when whoever was creating the Rom, generated a new Rom which included the android update.
Click to expand...
Click to collapse
Of course not stock. Updates from the ROM developer.
If you wanted to stay "stock", there are custom ROMs that are like that. The devs make it into a zip that is available and flashable for the rooted user.
EDIT: If you want help you can PM me.
That's not an invitation to others.
xunholyx said:
Of course not stock. Updates from the ROM developer.
If you wanted to stay "stock", there are custom ROMs that are like that. The devs make it into a zip that is available and flashable for the rooted user.
EDIT: If you want help you can PM me.
That's not an invitation to others.
Click to expand...
Click to collapse
I will pm you to ask some more questions, however I am leaving tomorrow for work for 3 days, and I wanted to run this update (and then flash TWRP) before I left.
So, right now, can you tell me what 2.22 stock file (nandroid or a .img or a .zip) that could be downloaded, and then from which I could unzip/unpack to get a default build.prop?
I don't want to reset everything or do a factory reset... just hoping I can use the default build.prop and run this OTA.
Or, if anyone is reading who has successfully ran the OTA--can you just copy the build.prop file for me (you can just paste the contents if that's easier)?
I am very interested in going through it line by line to figure out what the "unexpected contents" actually are.
Hello, I am completely new so I apologize if this is the wrong place.
I wanted to be able to lock my bootloader but still use cyanogenmod, specifically, only allow roms that I have compiled myself and signed with my cert to work on my phone. I unpacked the stock recovery.img, and made the necessary changes to the ramdisk to replace the stock OnePlus key with my own. I then was then able to confirm that only my signed zips could be sideloaded, both official CM and OxygenOS zips failed - just as I wanted.
The issue is then that this only worked with an unlocked bootloader. When I locked it, the OP3 entered a boot cycle, with a strange graphical glitch appearing then the screen going black, again and again. I could then no longer boot to either recovery or cyanogenmod, nor could I unlock fastboot. This amazing guide got my phone working again.
I now have three questions. What prevented my phone booting after I locked it, how does the unbrick tool work, and is there anything I can alter, like certifications or hashes, lower down in the boot sequence to allow only my signed images to work (using the previous tool. I am unsure what QLoader is, some form of serial interface to the 820 to write to the storage chip?).
Thanks for any advice you can offer!
Update: I have unpacked boot.img provided in the unbrick tool. I cannot find any keys to modify in /res but I have found a file called "verify_keys". Does anyone know what I need to change in boot.img to allow my self-signed recovery and os to boot? Thanks
UPDATE 2:
From reading some Android notes it appears that instead of replacing the OEM key, you can also just use fastboot to flash keystores for self-signed recovery and roms. This still allows OEM signed images to run, but is certainly a step in the right direction. I have run into an issue with building a correct keystore. I can use keytool and import my previous certs, but "fastboot flash keystore examplename.keystore" fails. I saw "fastboot flash ssd keystore.dat" used, and it works with my current dot keystore file, but then after locking it fails to boot. I'm going to see how I can convert my .keystore to a .dat.
I've been meaning to ask this same question for a while now also, so I'm eager to see the response. I suspect the official OnePlus forums might be a good place to ask as well, since they are visited by engineers from OnePlus. For anyone else who's curious as to what's being discussed and better the understand the risks of an unlocked bootloader (and how to mitigate them), there's a brief article here as well as a paper.
It is always suggested that never re-lock the bootloader until there is valid reason to do it
JumboMan said:
It is always suggested that never re-lock the bootloader until there is valid reason to do it
Click to expand...
Click to collapse
Have you read any of the attached links in my last post? There are valid reasons for doing so.
Just to pose an oversimplified hypothetical, imagine going through immigration/customs in Saudi Arabia (or maybe even the U.S.) with a Android device that has an unlocked bootloader. The officer examines your possesions, then takes your laptop and phone into a back room. Your phone is powered down and encrypted so it's not like they can do anything, right? Wrong. They plug it into a forensics device and flash a surreptitious malware app onto /system before returning it back to you. Then, the next time you turn on your phone your encryption keys and all your data, all your communications are secretly transmitted. You never have a clue... With a locked bootloader and appropriate precautions, that would never be possible.
Update 3:
I am now following the official Android guide for creating a keystore. They show how to create a "keystore.img" not .dat, bu the error I got when trying "fastboot flash keystore ..." said something along the lines of the keystore not being a valid image. Hopefully this will work. After I get this working, I will move on to removing or damaging the OEM key, hence not even allowing OnePlus images to be sideloaded.
JumboMan said:
It is always suggested that never re-lock the bootloader until there is valid reason to do it
Click to expand...
Click to collapse
I do have a valid reason - security. An unlocked bootloader means any code can be flashed to my device. Even with encryption it is vulnerable to cold boot attacks, it makes it easier to bruteforce, and pulling encryption keys from memory.
chocol4te said:
I do have a valid reason - security. An unlocked bootloader means any code can be flashed to my device. Even with encryption it is vulnerable to cold boot attacks, it makes it easier to bruteforce, and pulling encryption keys from memory.
Click to expand...
Click to collapse
sir prefer not rooting and staying on stock ROM with locked bootloader.
emptyragnarok said:
sir prefer not rooting and staying on stock ROM with locked bootloader.
Click to expand...
Click to collapse
Look, I'm sorry, I don't need any more useless comments saying the solution to my problem is to not do anything like on every other forum I've tried. I am perfectly aware of how to lock the bootloader with a stock rom, but I don't want to use the stock rom. I want to use custom roms. From what I have done so far it appears to be possible, so don't tell me it's not, at least without a good reason.
In addition, the stock method isn't even the most secure the phone can be. OnePlus can still sign any code and run it on my device and hence requires my trust in a third party that I am unwilling to give. I only want my own code to run.
Update 4:
Using the unbrick utility, I have updated the MD5 partition with the checksums of my modified boot and recovery partitions. Unfortunately, I am now getting a checksum failed error, with both the MD5 and recovery partitions highlighted in red. So I was wrong about the checksum being compared with hashes in the MD5 partition. Does anyone know where the lowest level checksums are stored? Hopefully if I can change that, then locking the bootloader will be no issue.
chocol4te said:
Update 4:
Using the unbrick utility, I have updated the MD5 partition with the checksums of my modified boot and recovery partitions. Unfortunately, I am now getting a checksum failed error, with both the MD5 and recovery partitions highlighted in red. So I was wrong about the checksum being compared with hashes in the MD5 partition. Does anyone know where the lowest level checksums are stored? Hopefully if I can change that, then locking the bootloader will be no issue.
Click to expand...
Click to collapse
Bro I am not a prolike you but I understand your vision now,... and I am with you in that.... Open Source stuff and ANdroid as an Open source impify that only... We should have our custom code for locking and unlocking our bootloader so we can have the full control over our device.... If not and the guy that said that you can lock the bootloader with the stock rom didn't get that .. even with stock rom and recovery anyone can have the access of the phone by just unlocking the boot loader and that is simple. SO I GOT YOUR VISION AND I AM WITH YOU I WILL TRY TO UNDERSTAND THE LOCKING SYSTEM OF THE BOOT-LOADER AND I WILL TRY TO FIND THE LOCATION OF LOWER LEVEL CHECKSLUMS... WE will try and try untill we succeed.... I AM WITH YOU BRO!!!!!
indroider said:
Bro I am not a prolike you but I understand your vision now,... and I am with you in that.... Open Source stuff and ANdroid as an Open source impify that only... We should have our custom code for locking and unlocking our bootloader so we can have the full control over our device.... If not and the guy that said that you can lock the bootloader with the stock rom didn't get that .. even with stock rom and recovery anyone can have the access of the phone by just unlocking the boot loader and that is simple. SO I GOT YOUR VISION AND I AM WITH YOU I WILL TRY TO UNDERSTAND THE LOCKING SYSTEM OF THE BOOT-LOADER AND I WILL TRY TO FIND THE LOCATION OF LOWER LEVEL CHECKSLUMS... WE will try and try untill we succeed.... I AM WITH YOU BRO!!!!!
Click to expand...
Click to collapse
Thanks! I'm glad to hear it!
chocol4te said:
Thanks! I'm glad to hear it!
Click to expand...
Click to collapse
You're most welcome bro.
Did I just witness a major bro-down?
Awsome thread, I'd also like to put my OP3 in a state where only ROMs I signed my self will run...
Any further development??
Sent from my Pixel XL using XDA-Developers mobile app
---------- Post added at 05:42 PM ---------- Previous post was at 05:41 PM ----------
indieross said:
Did I just witness a major bro-down?
Click to expand...
Click to collapse
Whats a bro down?
Sent from my Pixel XL using XDA-Developers mobile app
indroider said:
Any further development??
Sent from my Pixel XL using XDA-Developers mobile app
---------- Post added at 05:42 PM ---------- Previous post was at 05:41 PM ----------
Whats a bro down?
Sent from my Pixel XL using XDA-Developers mobile app
Click to expand...
Click to collapse
Sorry, other stuff came up. I am still very interested in getting this to work, but I am really stuck if I can't understand why the MD5 verification error occurs when I use Loader to flash the modified images. I looked at CopperheadOS, and in their documentation they show how to re-lock the bootloader with a custom ROM. Here is the shell script they use to upload the OS.
Code:
fastboot flash bootloader bootloader-bullhead-bhz11f.img
fastboot reboot-bootloader
sleep 5
fastboot flash radio radio-bullhead-m8994f-2.6.33.2.14.img
fastboot reboot-bootloader
sleep 5
fastboot -w update image-bullhead-nbd90z.zip
As you can see they flash two images, boot loader and radio, then update the main ROM. Then apparently it boots fine and the bootloader is OEM locked inside the OS. This was for the Nexus 5X, but I want to find out if a similar process is possible on the OP3.
I may also begin work on porting CopperheadOS to the OnePlus 3. I know it sounds unrealistic, but since OnePlus released the binaries and kernels it should make it slightly easier.
chocol4te said:
Sorry, other stuff came up. I am still very interested in getting this to work, but I am really stuck if I can't understand why the MD5 verification error occurs when I use Loader to flash the modified images. I looked at CopperheadOS, and in their documentation they show how to re-lock the bootloader with a custom ROM. Here is the shell script they use to upload the OS.
As you can see they flash two images, boot loader and radio, then update the main ROM. Then apparently it boots fine and the bootloader is OEM locked inside the OS. This was for the Nexus 5X, but I want to find out if a similar process is possible on the OP3.
I may also begin work on porting CopperheadOS to the OnePlus 3. I know it sounds unrealistic, but since OnePlus released the binaries and kernels it should make it slightly easier.
Click to expand...
Click to collapse
Ok.. Great to hear... Let me if you need any help.. I m here
chocol4te said:
Sorry, other stuff came up. I am still very interested in getting this to work ... ...
I may also begin work on porting CopperheadOS to the OnePlus 3. I know it sounds unrealistic, but since OnePlus released the binaries and kernels it should make it slightly easier.
Click to expand...
Click to collapse
This sounds exactly like what I was looking for. Have you been able to progress? Do you think that the bootloader and the radio are somehow linked in the boot verification sequence?
---------- Post added at 05:51 AM ---------- Previous post was at 05:43 AM ----------
chocol4te said:
UPDATE 2:
From reading some Android notes it appears that instead of replacing the OEM key, you can also just use fastboot to flash keystores for self-signed recovery and roms. This still allows OEM signed images to run, but is certainly a step in the right direction. I have run into an issue with building a correct keystore. I can use keytool and import my previous certs, but "fastboot flash keystore examplename.keystore" fails. I saw "fastboot flash ssd keystore.dat" used, and it works with my current dot keystore file, but then after locking it fails to boot. I'm going to see how I can convert my .keystore to a .dat.
Click to expand...
Click to collapse
Have you read this: https://mjg59.dreamwidth.org/31765.html
Morning all,
Im not S-off and I'm using a pretty dated firmware..
I was told that there is a way to obtain and flash a firmware WITHOUT wiping anything and without too much fuss.
My questions:
What is the COMMAND in CMD?
Where do you find the signed firmware?
How do you identify which one to use?
What does it actually change? As the phone does work on dated firmware, more optimised?
I highly doubt I'm the only one who would benefit from this, once I know the answers I'll leave them here and I'll write a guide on how to install them step by step I'll also link the firmwares do others can help themselves.
Thanks
Currently running: Viper 3.5.0
Firmware: 1.80.401.1
S-ON
Unecrypted.
Check out Krassermensch's Firmware Update Tool in the guide part of the forum.
Lindsten said:
Check out Krassermensch's Firmware Update Tool in the guide part of the forum.
Click to expand...
Click to collapse
Have come mate, but I've asked some other things plus there is apparently a way to do it without the use of a tool.
This is the specific thread for firmware update.
I think you can only flash the full stock zip since you are s-on. Do take note that flashing the stock firmware.zip will wipe your internal storage.
The firmware to flash should have matching CID and MID of your device.
To check your mid and cid type this command in cmd while the device is in download mode.
fastboot getvar all
side_flip15 said:
This is the specific thread for firmware update.
I think you can only flash the full stock zip since you are s-on. Do take note that flashing the stock firmware.zip will wipe your internal storage.
The firmware to flash should have matching CID and MID of your device.
To check your mid and cid type this command in cmd while the device is in download mode.
fastboot getvar all
Click to expand...
Click to collapse
Incorrect. All of @Sneakyghost's firmware.zips are for S-Off users only. It's stated in the OP of the thread right in the first sentence.
xunholyx said:
Incorrect. All of @Sneakyghost's firmware.zips are for S-Off users only. It's stated in the OP of the thread right in the first sentence.
Click to expand...
Click to collapse
Cheers,
Does anyone know the answers to any of the questions I've written?
sorry
side_flip15 said:
sorry
Click to expand...
Click to collapse
No reason to be sorry. You were trying to help, and I was just letting you know that it won't work for him.
---------- Post added at 06:16 PM ---------- Previous post was at 06:03 PM ----------
dladz said:
Does anyone know the answers to any of the questions I've written?
Click to expand...
Click to collapse
First make a backup. This will wipe your phone.
Then relock your bootloader. In fastboot fastboot oem lock
Download this RUU.zip
Rename the .zip to 2PS6IMG and place it onto your extSD
Boot to download mode and follow the prompts (vol up to flash ~ power button to reboot)
That's it. Super easy.
Delete the renamed .zip from your extSD or else every time you boot to download mode it'll try to update again.
Now unlock your bootloader again with the same bin code that HTC gave you when you first did it, or request a new one. Flash TWRP back onto your phone, then flash SuperSU or a custom ROM to regain root.
This is why I paid $25 for Sunshine.
For S-Off users, you just flash a small firmware package, and that's it. No data loss. No relocking the bootloader. No reflashing recovery. No re-rooting.
It really is worth the price in the amount of time and hassle saved through the lifetime of the phone.
xunholyx said:
No reason to be sorry. You were trying to help, and I was just letting you know that it won't work for him.
---------- Post added at 06:16 PM ---------- Previous post was at 06:03 PM ----------
First make a backup. This will wipe your phone.
Then relock your bootloader. In fastboot fastboot oem lock
Download this RUU.zip
Rename the .zip to 2PS6IMG and place it onto your extSD
Boot to download mode and follow the prompts (vol up to flash ~ power button to reboot)
That's it. Super easy.
Delete the renamed .zip from your extSD or else every time you boot to download mode it'll try to update again.
Now unlock your bootloader again with the same bin code that HTC gave you when you first did it, or request a new one. Flash TWRP back onto your phone, then flash SuperSU or a custom ROM to regain root.
This is why I paid $25 for Sunshine.
For S-Off users, you just flash a small firmware package, and that's it. No data loss. No relocking the bootloader. No reflashing recovery. No re-rooting.
It really is worth the price in the amount of time and hassle saved through the lifetime of the phone.
Click to expand...
Click to collapse
OK so this is where I've heard different.. There apparently isn't any need to return to stock so think you may need to read the originating post yourself mate
Otherwise how would the tool mentioned in the second post work? Appreciate you saying all that but it doesn't help my query.
As for sunshine I completely disagree, I've had every single htc bar two since the G1 and I've had S-off on all of them where available so I know the S-off method well, and have made a lot of donations to developers over the years, I also buy all my apps and support Devs when they deserve it for apps.
In regards to sunshine, I paid for this app for my m9 less than a year ago, I get one license, I can't use this for my 10 and I'll have another phone soon so see little point, they should offer more than one unlock for £25 and the only reason why they've got away with this daylight robbery is because they've monopolised the market, I'm sure I'm not the the only person who's noticed this.
Anyway, I'll wait to hear from someone who knows about the signed firmwares and how to install them. The tool can do it, so there must be a manual way, Id prefer to do that as I've had problems with tools in the past and with firmware you really want to get it right.
dladz said:
OK so this is where I've heard different.. There apparently isn't any need to return to stock so think you may need to read the originating post yourself mate
Otherwise how would the tool mentioned in the second post work? Appreciate you saying all that but it doesn't help my query.
As for sunshine I completely disagree, I've had every single htc bar two since the G1 and I've had S-off on all of them where available so I know the S-off method well, and have made a lot of donations to developers over the years, I also buy all my apps and support Devs when they deserve it for apps.
In regards to sunshine, I paid for this app for my m9 less than a year ago, I get one license, I can't use this for my 10 and I'll have another phone soon so see little point, they should offer more than one unlock for £25 and the only reason why they've got away with this daylight robbery is because they've monopolised the market, I'm sure I'm not the the only person who's noticed this.
Anyway, I'll wait to hear from someone who knows about the signed firmwares and how to install them. The tool can do it, so there must be a manual way, Id prefer to do that as I've had problems with tools in the past and with firmware you really want to get it right.
Click to expand...
Click to collapse
I think you misunderstood me. I'm sure there is a thread somewhere here with signed firmware (there is for M8), but I don't know of it. If I did, I would have linked you there.
But you asked if anyone could give you help, so I offered you a way to do it.
Even if you find a signed firmware.zip, you'll still need to re-lock your bootloader since you are S-On.
You might as well save some time searching and just run the RUU
xunholyx said:
I think you misunderstood me. I'm sure there is a thread somewhere here with signed firmware (there is for M8), but I don't know of it. If I did, I would have linked you there.
But you asked if anyone could give you help, so I offered you a way to do it.
Even if you find a signed firmware.zip, you'll still need to re-lock your bootloader since you are S-On.
You might as well save some time searching and just run the RUU
Click to expand...
Click to collapse
I'll check around, was speaking with @LeeDroid a while ago, can't remember him saying relock the bootloader, I'll ask him.
I'm pretty sure there is a way. Can't see that tool in the second post relocking your bootloader.
dladz said:
I'll check around, was speaking with @LeeDroid a while ago, can't remember him saying relock the bootloader, I'll ask him.
I'm pretty sure there is a way. Can't see that tool in the second post relocating your bootloader.
Click to expand...
Click to collapse
Actually, I have been following the method of @krassermensch's since before he started a thread about it. He posted to a different firmware thread about the method, and I've been curious about it since. In his OP he states that you need an unlocked bootloader, so his method is probably your best solution. I haven't tried it myself as I have always been S-Off on my HTC phones.
dladz said:
Have come mate, but I've asked some other things plus there is apparently a way to do it without the use of a tool.
Click to expand...
Click to collapse
My tool is on GitHub, read the content of the batch files and you know how to do it
https://github.com/nico151999/Firmware-Update-Tool-HTC10
krassermensch said:
My tool is on GitHub, read the content of the batch files and you know how to do it
https://github.com/nico151999/Firmware-Update-Tool-HTC10
Click to expand...
Click to collapse
Thanks :good:
xunholyx said:
Actually, I have been following the method of @krassermensch's since before he started a thread about it. He posted to a different firmware thread about the method, and I've been curious about it since. In his OP he states that you need an unlocked bootloader, so his method is probably your best solution. I haven't tried it myself as I have always been S-Off on my HTC phones.
Click to expand...
Click to collapse
yea same here man, looking at the tools code it seems that it asks you to back up first.
I'll check it out in the morning.
Thanks chaps
dladz said:
yea same here man, looking at the tools code it seems that it asks you to back up first.
I'll check it out in the morning.
Thanks chaps
Click to expand...
Click to collapse
The backup is necessary as the firmware update files overwrite the recovery and the boot partitions...
Please don't ask why (the answer will be: "because I'm stupid"), but I relocked my bootloader and now my Swift 2 Plus won't boot anymore. When turning it on, it vibrates and the Wileyfox logo flashes for less than a second. After that the screen stays black and nothing happens. Same thing when I try to boot into recovery. I can only boot into the bootloader but I can't flash any images or unlock it again ("FAILED (remote: oem unlock is not allowed)").
Is there any way I can revive my phone or is it lost?
I think your only way is to flash twrp again with fastboot install method :
//twrp.me/devices/wileyfoxswift2.html
And then flash the stock rom :
//cyngn.com/support
hope it will helps you!
---------- Post added at 02:07 PM ---------- Previous post was at 02:05 PM ----------
Sorry, I'm a new user so I can't post link, you've just have to ad "https" at the beginning of the line.
Thanks for answering, but I can't do that, because the bootloader is locked and protected from unlocking. I guess the only thing I can do is ask the support if they can provide the mbn and xml files that are needed for unbricking with QFIL (I can boot into edl mode as I recently found out). They probably won't but it's worth a shot.
If you use the signed zip ( not the fastboot image) the default recovery should be able to install it.
It doesn't boot to recovery. Only fastboot and edl mode work.
You could try flashing fastboot image from http://cyngn.com/support
Sent from my Swift 2 using XDA-Developers mobile app
Thanks, but that doesn't work with a locked bootloader (already tried).
It seems like the only way to revive it is with QFIL, but for doing that it needs the matching mbn and xml files that aren't included in the factory images. Wileyfox support wasn't helpful, either.
xrmnx said:
Thanks, but that doesn't work with a locked bootloader (already tried).
Click to expand...
Click to collapse
Can't we put the dirty cow bug to a use now? It should work on the phone unless it has the latest security patches, right? And with root privileges you should be able to flash a new recovery or reset the phone.:fingers-crossed:
I'm actually not sure, if I still have root privileges. It could be that I turned it off inside the SuperSU app.
I tried to flash the stock rom and that didn't work, though. Do I have to do something different than usually to flash with root privileges?
boa05 said:
Can't we put the dirty cow bug to a use now? It should work on the phone unless it has the latest security patches, right? And with root privileges you should be able to flash a new recovery or reset the phone.:fingers-crossed:
Click to expand...
Click to collapse
I read a little about dirty cow, now (didn't know much about it before), but if I understand it right, I need adb to upload files onto the phone, right? Sadly, adb doesn't work. Only fastboot :/
Hmmm, there is a similar thread for the Nexus 5X. You might want to check it out if you haven't already ( http://forum.xda-developers.com/nexus-5x/help/nexus-5x-permanently-bricked-locked-t3232105/page2 ).
A few of the suggestions were to try with:
Code:
fastboot flashing unlock
or
Code:
fastboot format userdata
fastboot format cache
I don't know if it will be of any help but it is worth a shot.
You could try to flash individual portions of the stock image like the recovery or the userdata but I doubt that it will be successful.
PS: From the thread above, for some reason removing the SIM card allowed them to enter recovery.
Thanks, but none of these solutions works. Already tried all of them a couple of times....
Hmmm, how about you try to trick it then?
Grab the official signed firmware, place it on SD Card and try with:
Code:
fastboot update <path/to/zip>
or this one to try to wipe the device? (dunno if the command is still in use, though)
Code:
fastboot -w
If this doesn't work as well, I guess it will be a waiting game for QFIL files.
Pak0St said:
Hmmm, how about you try to trick it then?
Grab the official signed firmware, place it on SD Card and try with:
or this one to try to wipe the device? (dunno if the command is still in use, though)
If this doesn't work as well, I guess it will be a waiting game for QFIL files.
Click to expand...
Click to collapse
I tried to flash/update every official rom (with and without -w) there is, but I never put it on an SD-card. Does that make a difference? If so, this might be one ofhe stupidest mistakes I ever made :/
I'll try in a few days. Not much time, at the moment...
Yes... Waiting for QFIL files is what I'm prepared for...
The idea with the SDCard is just a random thought. There is a slight chance to trigger the allowed update policies.
Usually you place the update.zip through adb (not possible in this situation) but placing it on the sdcard is possible.
Still, QFIL is the safest bet once someone uploads the files.
Pak0St said:
Still, QFIL is the safest bet once someone uploads the files.
Click to expand...
Click to collapse
That's what I thought. Since I couldn't find any (yet), is there a way to extract the QFIL files from a working phone (I bought another one since I needed a phone)? I don't think so, but I hope I'm wrong...
xrmnx said:
That's what I thought. Since I couldn't find any (yet), is there a way to extract the QFIL files from a working phone (I bought another one since I needed a phone)? I don't think so, but I hope I'm wrong...
Click to expand...
Click to collapse
I'm in the same boat here, same phone and same issue. Did you find a way to fix it? already searched all internet for a fix. Thanks a lot
Sorry, but for some reason I never saw your answer... I never found a solution either, though
how to unlock bootloader
Use fast boot to unlock the bootloader again.
connect your Swift 2 to your PC and in a command prompt type the following "fastboot oem unlock"
When you press enter, check the phone and using the volume keys you need to select yes and then press power to execute.
Your bootloader should then be unlocked again. Good Luck.
Hi all,
My phone keeps crashing and rebooting. Every time it comes back, it needs to resign on to wifi (retype in WPA), downloads a file calle "how-to" (which I can't find), and have to resign into Google. By the time it accomplishes all this, it crashes and restarts the whole shabang again. Tried recovery mode and clearing, no difference.
It might be worth mentioning it boots into extreme power saving mode too.
Is the phone modified (unlocked bootloader, root, custom ROM, etc.) or is it stock?
On the bootloader screen, what is the OS number?
redpoint73 said:
Is the phone modified (unlocked bootloader, root, custom ROM, etc.) or is it stock?
On the bootloader screen, what is the OS number?
Click to expand...
Click to collapse
It is stock. Tried to root it but it didn't take. Don't know which version as it is stuck in a loop currently. It seems to me this is a hardware problem though.
carljames0603 said:
It is stock. Tried to root it but it didn't take.
Click to expand...
Click to collapse
Need more details on that. How did you try to root, what exact steps did you perform, where did you get stuck and why, etc.
Always provide as many details as possible when asking for help and answering our questions.
carljames0603 said:
Don't know which version as it is stuck in a loop currently.
Click to expand...
Click to collapse
If its stuck in a loop (rebooting) then simply hold volume down, and don't let go. The next time it reboots, it will go to bootloader (then you can let go of vol down).
From there, tell us what OS number it says on the bootloader screen, near the top.
carljames0603 said:
It seems to me this is a hardware problem though.
Click to expand...
Click to collapse
What makes you think that? You haven't provided any details or evidence that would support the statement.
Its possible its a hardware issue. But based on what little you've said, its perfectly possible its a software issue. So be optimistic, unless you have specific evidence to think otherwise.
When it gets stuck in a loop, holding down VOL DOWN does nothing. The only way to get to the boot loader is to go to SETTINGS>POWER OPTIONS and disable fast boot. Then hopefully it shuts down fully and doesn't crash and reboot in the process. Pain in the ass.
The OS is 3.28.605.4
carljames0603 said:
When it gets stuck in a loop, holding down VOL DOWN does nothing. The only way to get to the boot loader is to go to SETTINGS>POWER OPTIONS and disable fast boot. Then hopefully it shuts down fully and doesn't crash and reboot in the process.
Click to expand...
Click to collapse
This is false. That setting only applies when the phone is powered off; since in that condition the phone was not truly powered off (just a deep sleep mode). A reboot is always a reboot.
I know this for fact, because back when I was on KitKat (and on past devices - the "fast boot" power setting was removed after KitKat) I never ever bothered to turn off the "fast boot" feature. I was able to get to bootloader whenever I wanted by rebooting (not power off) and then holding vol down. Worked every time.
Hold down the vol down button during the next reboot cycle, and it will go to bootloader. It may be that some set of conditions is just making you think what you posted is true. But try not to get the "timing" right. Just hold the vol down, and don't let go. It will go to bootloader, if its actually bootlooping.
---------- Post added at 01:58 PM ---------- Previous post was at 01:56 PM ----------
Also, you never answered my previous question, how far you got with the rooting, and what steps you performed exactly. Is the bootloader LOCKED, UNLOCKED, or RELOCKED?
When you do go to bootloader, it stays there (doesn't reboot)?
redpoint73 said:
This is false. That setting only applies when the phone is powered off; since in that condition the phone was not truly powered off (just a deep sleep mode). A reboot is always a reboot.
I know this for fact, because back when I was on KitKat (and on past devices - the "fast boot" power setting was removed after KitKat) I never ever bothered to turn off the "fast boot" feature. I was able to get to bootloader whenever I wanted by rebooting (not power off) and then holding vol down. Worked every time.
Hold down the vol down button during the next reboot cycle, and it will go to bootloader. It may be that some set of conditions is just making you think what you posted is true. But try not to get the "timing" right. Just hold the vol down, and don't let go. It will go to bootloader, if its actually bootlooping.
---------- Post added at 01:58 PM ---------- Previous post was at 01:56 PM ----------
Also, you never answered my previous question, how far you got with the rooting, and what steps you performed exactly. Is the bootloader LOCKED, UNLOCKED, or RELOCKED?
When you do go to bootloader, it stays there (doesn't reboot)?
Click to expand...
Click to collapse
It's not false, because that's what is happening. I hold down the button the whole time and it will go through the whole process and never go to the bootloader.
Either way, sorry I missed the question. Not very far, it crashes before to long. I tried downloading the SU app as prescribed in the site, but can't get it on the device itself.
The bootloader is locked, and it stays there until I push it to reboot.
carljames0603 said:
Either way, sorry I missed the question. Not very far, it crashes before to long. I tried downloading the SU app as prescribed in the site, but can't get it on the device itself.
The bootloader is locked.
Click to expand...
Click to collapse
Nowhere will you find a guide for this device, that tells you to use an SU app. That isn't the proper way to root this phone. You need to flash SU/SuperSU, and you need custom recovery to do that. And for that, you need an unlocked bootloader, which for your device (Verizon version M8) requires s-off.
Or there is the kingroot method, which has some mixed results.
In any case, locked bootloader is good. Since my recommendation would be to RUU to full stock image, and see if that fixes your reboot problem. If not, then you are probably correct that its a hardware issue.
You can get the RUUs from here: https://forum.xda-developers.com/verizon-htc-one-m8/general/official-ruu1-55-605-2-t2883845
Not only will this get you on a full stock image (which if its a software problem, will fix it) but you can get to a more updated version (yours is really outdated).
You may need to find and flash the Marshmallow 6.21.605.3 firmware (not sure where to find that, offhand), before you can falsh the Marshmallow RUU. But otherwise, you can certainly flash the Lollipop RUU.
---------- Post added at 02:26 PM ---------- Previous post was at 02:22 PM ----------
carljames0603 said:
It's not false, because that's what is happening. I hold down the button the whole time and it will go through the whole process and never go to the bootloader.
Click to expand...
Click to collapse
Maybe its not actually rebooting, then; but doing something like just rebooting the Android shell? But that would be interesting, and not something I've seen before.
redpoint73 said:
Nowhere will you find a guide for this device, that tells you to use an SU app. That isn't the proper way to root this phone. You need to flash SU/SuperSU, and you need custom recovery to do that. And for that, you need an unlocked bootloader, which for your device (Verizon version M8) requires s-off.
Or there is the kingroot method, which has some mixed results.
In any case, locked bootloader is good. Since my recommendation would be to RUU to full stock image, and see if that fixes your reboot problem. If not, then you are probably correct that its a hardware issue.
You can get the RUUs from here: https://forum.xda-developers.com/verizon-htc-one-m8/general/official-ruu1-55-605-2-t2883845
Not only will this get you on a full stock image (which if its a software problem, will fix it) but you can get to a more updated version (yours is really outdated).
You may need to find and flash the Marshmallow 6.21.605.3 firmware (not sure where to find that, offhand), before you can falsh the Marshmallow RUU. But otherwise, you can certainly flash the Lollipop RUU.
---------- Post added at 02:26 PM ---------- Previous post was at 02:22 PM ----------
Maybe its not actually rebooting, then; but doing something like just rebooting the Android shell? But that would be interesting, and not something I've seen before.
Click to expand...
Click to collapse
Sorry, app as the wrong word. I tried several different methods but none was an actual app. I did try using something that came from the HTC website (RUU_M8_UL_M60_SENSE70_MR_BrightstarUS_WWE_6.12.1540.4), but the phone would crash every time. It said to use the program while it was on bootloader, but I don't think I did it write because it still couldn't find the phone via USB.
carljames0603 said:
Sorry, app as the wrong word. I tried several different methods but none was an actual app. I did try using something that came from the HTC website (RUU_M8_UL_M60_SENSE70_MR_BrightstarUS_WWE_6.12.1540.4), but the phone would crash every time. It said to use the program while it was on bootloader, but I don't think I did it write because it still couldn't find the phone via USB.
Click to expand...
Click to collapse
did you read the post you quoted ?
redpoint73 said clearly what you need and where to find
you used a different RUU and it will not accepted by your device ( in red above )
carljames0603 said:
Sorry, app as the wrong word. I tried several different methods but none was an actual app.
Click to expand...
Click to collapse
Complete lack of correct terminology or any meaningful details, means you haven't provided any actual information on what "methods" you tried to root. You say you tried several different methods, but don't provide any information on what those were. You say an SU app, when you don't mean an SU app (SU zip? SuperSU zip? - which is not the same).
Further, you posted that you "downloading the SU app as prescribed in the site". What website? How are we supposed to have any idea what you are talking about? Please understand, that your posts are vague to the point, that they don't actually provide any real information.
If you want proper help on this website, in general, you need to be specific, provide proper details, and user the right terminology.
carljames0603 said:
(RUU_M8_UL_M60_SENSE70_MR_BrightstarUS_WWE_6.12.1540.4), but the phone would crash every time. It said to use the program while it was on bootloader, but I don't think I did it write because it still couldn't find the phone via USB.
Click to expand...
Click to collapse
As the previous response indicated, this isn't the right RUU for your device. Why would you try to use this? Especially since the proper RUU for your Verizon version M8 was already provided in one of my previous responses? It seems you are just guessing around for solutions (which is a recipe for disaster). You have no reason to think the RUU you listed would work on your device. The version number is all wrong, and it says Brightstar US (which is the US Developer's Edition of the M8). It isn't intended for your device, won't work, and if you flashed it successfully, it would cause your phone's SIM to stop working (radio brick - possibly permanent).
redpoint73 said:
Complete lack of correct terminology or any meaningful details, means you haven't provided any actual information on what "methods" you tried to root. You say you tried several different methods, but don't provide any information on what those were. You say an SU app, when you don't mean an SU app (SU zip? SuperSU zip? - which is not the same).
Further, you posted that you "downloading the SU app as prescribed in the site". What website? How are we supposed to have any idea what you are talking about? Please understand, that your posts are vague to the point, that they don't actually provide any real information.
If you want proper help on this website, in general, you need to be specific, provide proper details, and user the right terminology.
As the previous response indicated, this isn't the right RUU for your device. Why would you try to use this? Especially since the proper RUU for your Verizon version M8 was already provided in one of my previous responses? It seems you are just guessing around for solutions (which is a recipe for disaster). You have no reason to think the RUU you listed would work on your device. The version number is all wrong, and it says Brightstar US (which is the US Developer's Edition of the M8). It isn't intended for your device, won't work, and if you flashed it successfully, it would cause your phone's SIM to stop working (radio brick - possibly permanent).
Click to expand...
Click to collapse
Alright, clearly I'm not knowledgeable in this type of repair. I apologize for using the wrong terminology, I'm scatter brained and names often elude me. Yes, I apparently used the wrong program to flash my ROM, either way it didn't work. In the end it doesn't matter, I'm throwing in the towel and getting a new phone. Go ahead and delete this thread as I won't be using this forum anymore. You're a ****.
carljames0603 said:
Alright, clearly I'm not knowledgeable in this type of repair. I apologize for using the wrong terminology, I'm scatter brained and names often elude me. Yes, I apparently used the wrong program to flash my ROM, either way it didn't work. In the end it doesn't matter, I'm throwing in the towel and getting a new phone. Go ahead and delete this thread as I won't be using this forum anymore. You're a ****.
Click to expand...
Click to collapse
That's unfortunate, as your issue is probably completely fixable. All you need to do is follow the instructions already provided. Myself and others have taken our time, at no benefit to ourselves, in order to try to help you and others.
Any critique given by me was not mean to insult or attack, and if you read my post there is nothing in there that constitutes a personal attack or flaming (I even said "please") - while you on the other hand can't claim such a statement to be true. A constructive criticism of your posts is not the same as attacking a person (which you did). The intent was for us to obtain the proper information so that we can better understand what you did, in order to help; and hopefully to improve the quality of your subsequent posts (but that didn't happen).
You can try to learn from your mistakes and expand your knowledge; or you can complain and continue to be ignorant. Your choice.