Hi, my name is Quinn.
Cards on the table, I don't know anything about phones and very little about computers.
So I rooted my phone About two years back and my phone has been acting sluggish for a while so I decided to try putting it back in stock software and updating it to see if it would become quicker. When I tried to install the update there was a thing that said the startup wizard has stopped working so I was trying to delete it and did an advanced wipe on my phone for some reason. Now when I boot it up, it only brings me to the loading screen. The big thing for me is that the factory reset turned off usb debugging and I have no idea how to access my phone from my computer.
I can get to the recovery page, and my bootloader(I think) is unlocked.
Any help would be appreciated.
Let's walk this back for a second. If you had a car with some problems, would you just randomly open the hood, without knowing what you are doing, and start pulling stuff out, without knowing what it was, or what the effect would be? Because that is kinda what you did, by going into the TWRP "Advanced" wipe options.
What you did was not a factory reset. You probably wiped "system" which is the OS (operating system - Android), and therefore you have no OS to boot.
My constructive advise to you, in moving forward, is only do what other experienced users have directed you to do. Don't guess solutions, make things up, etc. Don't do anything unless you have a good understanding of what the result will be; or if you were instructed to do so by a knowledgeable person. Make sense?
Now let's get you back up and running. Doing so will take some steps, and take some time. You may (almost certainly) learns some things in the process.
Do you by any chance remember if you ever made a backup of the ROM using TWRP? You can check this by booting into TWRP, selecting RESTORE, and seeing if it identifies any available backups. However, if you wipe internal storage and/or the SD card; even if you had previously made a backup, it would be gone now.
On the bootloader screen (the white screen where you can select recovery) what does it say for OS number? If its blank, what does it say for hboot number and radio number?
On that same bootloader screen, it will indicate at the top whether the bootloader is UNLOCKED or RELOCKED (or LOCKED, but its probably not that one). Tell us which one.
ShaferQ said:
The big thing for me is that the factory reset turned off usb debugging and I have no idea how to access my phone from my computer.
Click to expand...
Click to collapse
This only affects adb commands. You will find fastboot commands will still work, when booted properly into bootloader-fastboot mode.
Also, if booted into TWRP, you should be able to access the phone's internal storage and SD card (if one is inserted) from your computer.
---------- Post added at 12:36 PM ---------- Previous post was at 12:33 PM ----------
ShaferQ said:
I decided to try putting it back in stock software and updating it to see if it would become quicker. When I tried to install the update there was a thing that said the startup wizard has stopped working
Click to expand...
Click to collapse
How far exactly did you get with this process (restoring stock software, and update)?
Describe step by step, what you did, and in as much detail as possible (files used - exact names, results of each step, any other observations).
Yeah, I don't know what I was thinking. Thanks for the help though.
My Bootloader is unlocked
OS is blank
HBOOT is 3.19.0.0000
RADIO is 1.09.20.0209
No backups
I didn't get far at all with installing stock. I just had the intention. I tried to use some program to install the stock firmware, but my phone couldn't connect to my computer.
ShaferQ said:
I tried to use some program to install the stock firmware, but my phone couldn't connect to my computer.
Click to expand...
Click to collapse
Then how did you get to the point where it said "Setup Wizard has stopped working"? Isn't that the error that prompted you to wipe everything in TWRP?
Also, you must realize that saying "some program" doesn't really tell us what you used? You have any idea what it was? Is it still on your computer?
Do you have any idea how to use fastboot, and issue fastboot commands?
redpoint73 said:
Then how did you get to the point where it said "Setup Wizard has stopped working"? Isn't that the error that prompted you to wipe everything in TWRP?
Also, you must realize that saying "some program" doesn't really tell us what you used? You have any idea what it was? Is it still on your computer?
Do you have any idea how to use fastboot, and issue fastboot commands?
Click to expand...
Click to collapse
No, I did the factory reset, thinking that would undo my rooting, but it didn't. At this point it was still working and I thought that it was fine, but then I couldn't take pictures or anything so I installed major update from my phone and that's when the startup wizard wouldn't work. I then did the wipe and used a program I got from htc rom downloads from their support page. I thought it was a program that installed stock roms on your phone? But it couldn't connect and did nothing to my phone.
redpoint73 said:
Do you have any idea how to use fastboot, and issue fastboot commands?
Click to expand...
Click to collapse
I know how to get there, but I don't really know anything other than that.
ShaferQ said:
so I installed major update from my phone and that's when the startup wizard wouldn't work.
Click to expand...
Click to collapse
You mean an over-the-air (OTA) official update? I'm confused how that would even install. It normally will fail if the phone is rooted, and also won't install with TWRP on the phone.
---------- Post added at 01:13 PM ---------- Previous post was at 01:06 PM ----------
ShaferQ said:
I know how to get there, but I don't really know anything other than that.
Click to expand...
Click to collapse
When you say you know how to get there, you mean only know how to boot into fastooot mode on the phone?
You'll need to also issue fastboot command from your PC's command prompt (with phone connected, and booted to fastboot mode). To do that, you'll need to find where fastboot.exe is on the PC. You might find it at (where it is on my PC): C:\Program Files (x86)\HTC\HTC Sync Manager\HTC Sync
After you find it, hovering the mouse cursor over the window (where fastboot.exe is located) do Shift + Right Mouse Click, and from the pulldown menu, select "Open command window here".
In the command window, type: fastboot getvar all
Then copy and paste the output, and post it (delete IMEI and serial number before posting). To copy in command prompt, right mouse click, select "Mark" then highlight the area you want to copy. Press Ctrl + C to copy. Then go to your forum post window, and Ctrl + V to paste. And remember again to delete IMEI and serial number before posting.
Well, I was also the one who rooted the phone, so I probably did it poorly somehow. Yeah the over the wifi one. The update failed the first time, but then I just tried again and it went though and that was the point where I got the startup wizard is not responding message that wouldn't let me pass.
Ok, give me a second to do that.
C:\Program Files (x86)\HTC\HTC Sync Manager\HTC Sync>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.09.20.0209
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 99000499185667
(bootloader) product: m8_whl
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B70000
(bootloader) cidnum: SPCS_004
(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: 631e3609
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.037s
htc_fastboot finished. total time: 0.120s
Okay, great. That confirms some things I had figured out earlier. One that this is a Sprint version, and it looks to be the Harman Kardon version. Is Sprint your current cell provider?
redpoint73 said:
Okay, great. That confirms some things I had figured out earlier. One that this is a Sprint version, and it looks to be the Harman Kardon version. Is Sprint your current cell provider?
Click to expand...
Click to collapse
Yes sir, it is.
ShaferQ said:
Yes sir, it is.
Click to expand...
Click to collapse
Ok, good. That makes the rest somewhat easier.
Another fastboot command. Enter the following:
fastboot oem lock
On the bootloader screen (after an auto reboot, I believe) you should see the bootloader say RELOCKED near the top.
Next go to the following page, and download the 4.25.654.18 RUU under where it says "Previous RUUs":https://forum.xda-developers.com/showthread.php?t=2729173
After you download the RUU, open it, and it should install the full stock factory image, Lollipop version. The phone should be running after that. And since you are connected to Sprint, you should soon get an update, which will bring you up to Marshmallow.
You can also RUU right to Marshmallow, but it takes more steps. You would have to flash MM firmware (more fastboot steps) before you can do the MM RUU. So that is why the LP RUU may be easier for your. But if you are interested in doing RUU right to MM (instead or LP RUU, then OTA update) then let me know, and I'll walk you through it.
I got it re-locked and everything, but my phone still wont connect to my computer. The Rom utility still says that it cannot connect.
View attachment 4009482
And I know that it's not just the USB because I already issued fastboot commands perfectly fine.
Does the phone still have to be in fastboot?
ShaferQ said:
Does the phone still have to be in fastboot?
Click to expand...
Click to collapse
Yes. Is that how you are trying to run the RUU? If so, try a different USB port, different cable, if possible. The RUU is much more finicky than fastboot commands.
If all fails, and you have an SD card, you can use the SD method of RUU (no PC needed): Go back to the thread, download the zip version of the RUU. Rename to 0P6BIMG.zip, put on the SD, then reboot to bootloader, it will detect the RUU and auto install it.
You are a freakin life saver, thank you so much for helping me. I really really appreciate it.
ShaferQ said:
I got it re-locked and everything, but my phone still wont connect to my computer. The Rom utility still says that it cannot connect.
And I know that it's not just the USB because I already issued fastboot commands perfectly fine.
Does the phone still have to be in fastboot?
Click to expand...
Click to collapse
As redpoint73 said
Try another USB port ( USB 2 not 3 )
Un install HTC sync manager if you installed it earlier
But the main reason i post here is to tell you to remove meid numbers from this post ( as it's personal info and not to share on public forum )
https://forum.xda-developers.com/ht...ng-screen-factory-reset-t3541234/post70630772
Sent from my HTC M8 using XDA Labs
Related
I got fed up with the problems my phone has been having since the Lollipop update and I decided to "reinstall" the whole thing. I've looked through lots of threads here and I more or less have an idea of what to do, but what troubles me is that most people point out that the phone will still not be the same as when it came from the shop.
So, could anyone please explain to me, how do I bring the phone back to its original maiden state. At this point, I don't even care if it would be Lollipop or KitKat, seeing that many people claim to have no problems with Lollipop.
It might well be that the problems I'm having are due to my meddling with the phone - i.e. disabling apps and restricting permissions. But at the same time, when I started backing up files to my PC in preparation to what I want to do with the phone, I found out that there are gigabytes of leftover data from apps that I had installed on KitKat. These apps are no longer installed on Lollipop, but their data (maps, dictionaries, etc.) are still there, despite the update and subsequent factory reset. And it certainly does not help that HTC Sync Manager erases records from my Outlook database instead of actually "syncing" the contacts with the phone.
I imagine what I need to do it to completely wipe the internal storage and flash the original HTC software there. Could anyone please confirm that this is possible and which method would be the safest?
Post the output of fastboot getvar all (minus your IMEI and serial number) first and we'll go from there
unifex_ said:
I got fed up with the problems my phone has been having since the Lollipop update and I decided to "reinstall" the whole thing. I've looked through lots of threads here and I more or less have an idea of what to do, but what troubles me is that most people point out that the phone will still not be the same as when it came from the shop.
So, could anyone please explain to me, how do I bring the phone back to its original maiden state. At this point, I don't even care if it would be Lollipop or KitKat, seeing that many people claim to have no problems with Lollipop.
It might well be that the problems I'm having are due to my meddling with the phone - i.e. disabling apps and restricting permissions. But at the same time, when I started backing up files to my PC in preparation to what I want to do with the phone, I found out that there are gigabytes of leftover data from apps that I had installed on KitKat. These apps are no longer installed on Lollipop, but their data (maps, dictionaries, etc.) are still there, despite the update and subsequent factory reset. And it certainly does not help that HTC Sync Manager erases records from my Outlook database instead of actually "syncing" the contacts with the phone.
I imagine what I need to do it to completely wipe the internal storage and flash the original HTC software there. Could anyone please confirm that this is possible and which method would be the safest?
Click to expand...
Click to collapse
Do as EddyOS says, he will guide you on the best which version to downgrade to (if your looking to do that). Honestly I didnt have any issues with Lollipop, its all good.
my suggestion of the easiest way to totally wipe up your internal memory is to unlock bootloader (if you've already unlocked it, then relock and unlock again), doing that will totally wipe your internal memory, as for ext. sd card, you can just format that.
Flashing original stock rom is done by an RUU.
EddyOS said:
Post the output of fastboot getvar all (minus your IMEI and serial number) first and we'll go from there
Click to expand...
Click to collapse
Thanks Eddy, I appreciate the help.
I attach an image of the fastboot output.
If you don't mind setting up the device from scratch, you just use the 4.19.111.2 RUU, available here:
https://drive.google.com/file/d/0B17smFr95pleNTFvYi1yNnJrcU0/view
You need a locked bootloader first, so use fastboot oem lock first otherwise it'll fail
1. Run the file as administrator
2. Connect the phone in fastboot mode to your PC
3. Follow the instructions
This will give you a 100% stock device, as if you just got it out the box
EddyOS said:
If you don't mind setting up the device from scratch, you just use the 4.19.111.2 RUU, available here:
https://drive.google.com/file/d/0B17smFr95pleNTFvYi1yNnJrcU0/view
You need a locked bootloader first, so use fastboot oem lock first otherwise it'll fail
1. Run the file as administrator
2. Connect the phone in fastboot mode to your PC
3. Follow the instructions
This will give you a 100% stock device, as if you just got it out the box
Click to expand...
Click to collapse
Great, that sounds uncomplicated enough. My bootloader is locked, as far as I know, at least I never did anything to unlock it. So I should be good to go.
One question though. At the moment, the phone is unlocked as far as SIM is concerned. I mean that although the CID is from T-Mobile Germany, I'm using O2 as the service provider. Will that RUU keep it that way, or it will make the phone locked towards T-Mobile SIM cards?
Thanks a lot.
It shouldn't put the SIM lock back on, if that's what you mean, but I can't say for certain it won't
EddyOS said:
It shouldn't put the SIM lock back on, if that's what you mean, but I can't say for certain it won't
Click to expand...
Click to collapse
In case it would, what would I have to do to unlock it? I don't have any T-Mobile SIM cards around here after all.
Buy a code, like you did last time
EddyOS said:
Buy a code, like you did last time
Click to expand...
Click to collapse
I did not buy any code, I bought a phone. That's how it came from the shop - SIM-unlocked. I had no idea it had the T-Mobile anything in it until I started looking around this forum and someone asked me about my CID.
If it was factory SIM-unlocked then it'll still be SIM-unlocked after flashing the RUU
EddyOS said:
If it was factory SIM-unlocked then it'll still be SIM-unlocked after flashing the RUU
Click to expand...
Click to collapse
Great, thanks! I'll let you know how it went.
OK, finally got the time to do it, but unfortunately, the RUU that I downloaded
EddyOS said:
If you don't mind setting up the device from scratch, you just use the 4.19.111.2 RUU, available here:
https://drive.google.com/file/d/0B17smFr95pleNTFvYi1yNnJrcU0/view
You need a locked bootloader first, so use fastboot oem lock first otherwise it'll fail
1. Run the file as administrator
2. Connect the phone in fastboot mode to your PC
3. Follow the instructions
Click to expand...
Click to collapse
did not work, I attach the screenshot with the error. Any ideas? The error was the same regardless of whether the phone was connected to the PC.
Yeah, it appears that RUU is corrupt
EddyOS said:
Yeah, it appears that RUU is corrupt
Click to expand...
Click to collapse
That's a pity. Do you know where can one find a proper RUU? I looked at the htcdev.com download section, they list the software I need, 4.19.111.2, but the download link brings me simply to the htc.de, where nothing can be downloaded, it's just their regular advertising site.
I also found a zip file with the 4.16.111.2 firmware on a German forum (basically, from a link in the xda thread with RUU and OTA collection), but to be honest, I'm not sure what to do with the bunch of img files.
The files on HTCDev are the kernel source so can't be flashed. Easiest thing to do for now is flash a ROM based on Lollipop until the proper RUU is re-posted
EddyOS said:
The files on HTCDev are the kernel source so can't be flashed. Easiest thing to do for now is flash a ROM based on Lollipop until the proper RUU is re-posted
Click to expand...
Click to collapse
How about the files from that site (German, though). I found that link on the xda thread for RUU collection.
http://www.handy-faq.de/forum/htc_o...ne_m8_firmwaresammlung_ruus_otas_backups.html
They have a list of various files, for 4.19.11.2 they have nandroid backups and signed firmware, but not a RUU.
Or could you suggest a well working ROM?
You could flash the backup, then the firmware to restore stock recovery and it should work
EddyOS said:
You could flash the backup, then the firmware to restore stock recovery and it should work
Click to expand...
Click to collapse
Could you help me with mine as well
from fastboot
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.25.21331147A1.06G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.20.631.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: SH445WM0----
(bootloader) imei: ----------------------
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B16000
(bootloader) cidnum: ROGER001
(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: dcdaa6e0
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.177s
Sorry about any terminology...
Recently my htc one m8 stopped booting. I had rooted it a long time ago and had a ROM that was working fine for a long time. No recent changes.
On normal boot it sits on the white and green text 'htc' forever.
If I boot with power+down buttons I get to a hboot screen, but choosing 'recovery' takes me to a white screen small pink 'Entering Recovery' text. Nothing happens. To even get power+down screen to be available I had to move two zip files from root of sdcard which I guess were related to the custom rom, being 0P6BIMG.zip and M8-GPE-03-16-2015.zip
I tried reinstalling twrp after downloading the latest .img file
fastboot command
c:\twrp>fastboot flash recovery twrp-3.0.2-0-m8.img
just says <waiting for device> whether on pink text screen or white 'htc'
I can see the sdcard through a pc card reader and manipulate files. Is there any way to copy files manually so it will boot?
This is on Win 10, UK unlocked version of phone.
bt999 said:
To even get power+down screen to be available I had to move two zip files from root of sdcard which I guess were related to the custom rom, being 0P6BIMG.zip and M8-GPE-03-16-2015.zip
Click to expand...
Click to collapse
When you have a file named 0P6BIMG.zip, it will automatically try to install it every time you enter bootloader. Its an update or RUU of some sort, placed there by you, but exactly what is impossible to tell.
The other file is a ROM zip for a GPE ROM, which I would guess is the custom ROM you installed. It doesn't make a difference for this file not be on the SD card or not (bootloader will not try to install it automatically, and bootloader will function normally).
bt999 said:
I tried reinstalling twrp after downloading the latest .img file
fastboot command
c:\twrp>fastboot flash recovery twrp-3.0.2-0-m8.img
just says <waiting for device> whether on pink text screen or white 'htc'
Click to expand...
Click to collapse
Are you in bootloader-fastboot mode when you run the command (which is required)? Meaning, FASTBOOT should be highlighted in red just under the green text on the bootloader screen. If not, just select using the vol buttons, and confirm using power button.
Fastboot clarification
redpoint73 said:
When you have a file named 0P6BIMG.zip, it will automatically try to install it every time you enter bootloader. Its an update or RUU of some sort, placed there by you, but exactly what is impossible to tell.
The other file is a ROM zip for a GPE ROM, which I would guess is the custom ROM you installed. It doesn't make a difference for this file not be on the SD card or not (bootloader will not try to install it automatically, and bootloader will function normally).
Are you in bootloader-fastboot mode when you run the command (which is required)? Meaning, FASTBOOT should be highlighted in red just under the green text on the bootloader screen. If not, just select using the vol buttons, and confirm using power button.
Click to expand...
Click to collapse
Thanks for your reply.
I guess the 0P6BIMG.zip file would explain why it was always slow to boot when things were working ok, if it was being reinstalled each time. I don't recall its purpose.
I wasn't in bootloader-fastboot mode when trying the fastboot command, but have tried it again.
When connected to an Ubuntu 16.04 machine the white on red text says 'fastboot usb', but ubuntu commandline fastboot flash ... gives same 'waiting for device'. When connected to Win 10 white/red text just says 'fastboot', if that is relevant. When I installed fastboot on Win 10 from instructions at http://forum.xda-developers.com/showthread.php?p=48915118#post48915118 there is a note to remove Google drivers before installing new ones - I did not do this, not sure if relevant, but new driver install gave no errors.
Is there a way to copy a new ROM image to the sdcard so that on 'normal' booting it gets detected and applied? Or to copy twrp somewhere manually?
Is there a log file that would show how far through the normal boot things get? I guess it is inaccessible until things work better.
bt999 said:
I wasn't in bootloader-fastboot mode when trying the fastboot command, but have tried it again.
When connected to an Ubuntu 16.04 machine the white on red text says 'fastboot usb', but ubuntu commandline fastboot flash ... gives same 'waiting for device'. When connected to Win 10 white/red text just says 'fastboot', if that is relevant. When I installed fastboot on Win 10 from instructions at http://forum.xda-developers.com/showthread.php?p=48915118#post48915118 there is a note to remove Google drivers before installing new ones - I did not do this, not sure if relevant, but new driver install gave no errors.
Click to expand...
Click to collapse
Try going into Windows Device Manager, finding the device, and picking the option to manually select drivers, and select the generic Android MTP drivers. See if that helps fastboot connect.
Make sure you have HTC drivers (HTC Sync) installed as well. Try to re-install HTC Sync.
bt999 said:
Is there a way to copy a new ROM image to the sdcard so that on 'normal' booting it gets detected and applied? Or to copy twrp somewhere manually?
Click to expand...
Click to collapse
You can't flash a ROM, if TWRP isn't working properly. And there isn't a way to make one automatically flash upon normal boot, that I am aware.
I've seen some folks make 0P6BIMG.zip files for TWRP, which will install automatically when you boot to bootloader. But honestly, USB fastboot connectivity is a pretty vital thing to have working, and usually just a matter of right drivers and a good cable (and being in fastboot mode is a must), so shouldn't be that hard to troubleshoot.
Old twrp
redpoint73 said:
Try going into Windows Device Manager, finding the device, and picking the option to manually select drivers, and select the generic Android MTP drivers. See if that helps fastboot connect.
Make sure you have HTC drivers (HTC Sync) installed as well. Try to re-install HTC Sync.
You can't flash a ROM, if TWRP isn't working properly. And there isn't a way to make one automatically flash upon normal boot, that I am aware.
I've seen some folks make 0P6BIMG.zip files for TWRP, which will install automatically when you boot to bootloader. But honestly, USB fastboot connectivity is a pretty vital thing to have working, and usually just a matter of right drivers and a good cable (and being in fastboot mode is a must), so shouldn't be that hard to troubleshoot.
Click to expand...
Click to collapse
I have got a twrp running, unfortunately it says it is only compatible with bootloader 3.19 and above when I try to install the rom. I have 3.16.
Do you know where I can get an old twrp?
Thanks.
bt999 said:
I have got a twrp running, unfortunately it says it is only compatible with bootloader 3.19 and above when I try to install the rom. I have 3.16.
Do you know where I can get an old twrp?
Thanks.
Click to expand...
Click to collapse
https://dl.twrp.me/m8/
twrp versions
xunholyx said:
https://dl.twrp.me/m8/
Click to expand...
Click to collapse
Thanks. I have now tried
twrp-2.7.0.1-m8.img twrp-2.7.1.0-m8.img twrp-2.8.7.0-m8.img
twrp-2.7.0.2-m8.img twrp-2.8.0.0-m8.img twrp-3.0.2-0-m8.img
The oldest ones don't run the newer ones work but I still get an error on attempting to install the custom ROM. I think I may be misinterpreting the error message. I now think it is telling me the custom ROM needs bootloader 3.19, rather than twrp not being able to run, i.e. twrp knows not to install the rom.
Message 'This package supports bootloader(s): 3.19.0.0000; this device has bootloader 3.16.0.0000'
Do you know how I can update my bootloader?
bt999 said:
Do you know how I can update my bootloader?
Click to expand...
Click to collapse
Post fastboot getvar all result without serial & imei no.
Without proper info, everyone is guessing what you actually need.
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: INVALID_VER_INFO
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: HTC__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: 098a72e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
I found this thread http://forum.xda-developers.com/showthread.php?t=2696282 and went through the process with a zip linked from there , but I guess it was old and turned out to still be 3.16
Shouldn't HTC be distributing these files? Or my carrier?
You need to relock bootloader if not yet done.
Command :
fasboot oem lock
fastboot reboot-bootloader
Then follow this : http://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
Put both files in your adb/fastboot folder.
(The guide was written for system-wide adb/fastboot)
Once completed, you can re unlock boorloader and install latest TWRP and install any ROM that you like, if you want to.
I have a working phone now, htc setup screens ended up with no google account prompts or apps, so I installed cwm nightlies and open-gapps hoping I would have full functionality, however gapps was rejected for not having enough internal storage.
I don't care whether htc or cwm but need gapps/play store. Is there anything you can suggest?
/Last reply lost..]I now have a working phone with cwm nightlies. Unfortunately open-gapps wont install saying not enough space on internal drive.
Any suggestions on how to clear space or to make HTC install Google accounts/store (it did not ask)?
I have a working phone now.
RUU didn't install google app store, so I installed cwm nightlies. I got an error that there was not enough space on internal for open-gappps.
Is there a way to free up space?
bt999 said:
I have a working phone now.
RUU didn't install google app store, so I installed cwm nightlies. I got an error that there was not enough space on internal for open-gappps.
Is there a way to free up space?
Click to expand...
Click to collapse
I have no idea what cwm nightlies is ... but if you have this kind of error not enough internal space ... you need to format data (not wipe) in TWRP.
Install latest TWRP, select wipe - format data - yes ... reboot to recovery again, now you can install ROM.
Solved
ckpv5 said:
I have no idea what cwm nightlies is ... but if you have this kind of error not enough internal space ... you need to format data (not wipe) in TWRP.
Install latest TWRP, select wipe - format data - yes ... reboot to recovery again, now you can install ROM.
Click to expand...
Click to collapse
I installed a mini gapps that had just Play Store then installed other apps manually through that.
Thank you all for your help, this is a well-informed forum.
For anyone reading one thing I learned was to run fastboot from Ubuntu/Linux with 'sudo' or else it will not connect, just says 'waiting for device'
ckpv5 said:
I have no idea what cwm nightlies is
Click to expand...
Click to collapse
He means CM, not CWM. Easy mistake to make (adding one letter) but the two are completely different things (Cyanogen Mod custom ROM versus Clockwork Mod custom recovery).
Folks
I need help to solve a problem.
I bought a HTC One M8x and decided to set up a rom custon. I study the subject before. I took the program kit available for the M8 and follow all the steps to unlock. All this function normally, however when installing the ROM custon the device just gave error. I was exploring the tool I ended up pressing and making procedures that were not listed, but apparently did not issue before starting the installation made the backup and then wipe. I started the procedure to install, entered the install section and located the ROM and sent install. After a while appeared an error saying that the installation was not possible, I managed to recover the backup, but the phone was not the same. I realized that my internal memory is no longer visible, I can not download pictures or audios in whatsapp, another thing I noticed is that the file manager also does not provide the internal memory (directories, programs, and others). When I try to synchronize your phone with your computer to the same thing, I can see the micro SD, but can not see the internal memory. I possibly when I was digging the Recovery program just blocking the internal memory and wanted to know how do to reverse. Does anyone have any ideas.
Do you have access to bootloader? if yes. You can try to restore your phone with HTC RUU
ddfilho said:
I took the program kit available for the M8 and follow all the steps to unlock. All this function normally, however when installing the ROM custon the device just gave error.
Click to expand...
Click to collapse
Using the (now outdated) toolkit was a mistake. Whenever modding these devices, you need to research the current methods applicable to the current state of the phone, not methods from 2 years ago (and all the toolkits have not been updated in that long or more).
The toolkit installs an obsolete version of TWRP, and that is probably why the ROM is failing to flash. It probably also wiped out your OS version on bootloader screen and getvar (not a major issue, but an inconvenience if you want to determine the firmware number).
You should update to more current version of TWRP. But you'll probably need to solve the issue of your internal storage first, which is apparently been corrupted. Go into TWRP, and try the option in Wipe to "Format Data" (button next to "Advanced"). This usually fixes the corrupt internal storage issue.
Also do fastboot getvar all, and post the results, so we can see more info about the phone, and more properly provide guidance. Delete IMEI and serial number before posting.
I have access to the bootloader but do not know run this action. Could you tell me where I can walkthrougt to do so.
Thank you for your help
Pardon
Now that saw the second message. I will perform this procedure now
Friend
Your solution worked perfectly.
I wanted your help to make the second action, I entered the bootloader and accessed the fastboot but did not find the getvar option. Could you tell me how to do it.
I found the TWRP 3.0.2, I believe it is the last version but need help because I believe that the update version is not simple, I installed the 2.7.0.2 version.
Thanks again
ddfilho said:
I wanted your help to make the second action, I entered the bootloader and accessed the fastboot but did not find the getvar option. Could you tell me how to do it.
Click to expand...
Click to collapse
This isn't an option on the phone, if that is what you mean. Its a fastboot command issued from your PC, and you'd know how to issue a fastboot command if you unlocked the bootloader via HTCDev.com, instead of letting the toolkit do it for you. Which is another reason I don't like the toolkits: they shortcut the learning process, and leave you without the skills to solve basic problems, which almost inevitably happen.
You're going to need to figure out where fastboot.exe was installed during the bootloader unlock process. Once you've found that, you can then:
1) Connect phone to PC, booted into bootloader-fastboot mode
2) On PC, open a window for the folder that contains fastboot.exe
3) Hover mouse cursor over the window, and Shift+Right Mouse button, then select "Open command window here" and this will open up Command Prompt to the fastboot directory
4) In Command Prompt window, type: fastboot getvar all
5) You will see output with details about the phone, to copy the desired text, right click on the command window, select Edit>Mark, then highlight the desired text (getvar output) and press Enter. Then paste the text.
6) Be sure to delete IMEI and serial number from getvar output before posting it here
ddfilho said:
I found the TWRP 3.0.2, I believe it is the last version but need help because I believe that the update version is not simple, I installed the 2.7.0.2 version.
Click to expand...
Click to collapse
Exact TWRP version depends on your current firmware, which we can determine from the getvar output above.
Once we've determined the proper TWRP version, its easily installed by putting the file in your fastboot folder, and flashing with fastboot command. Again, we see how valuable it is to know how to use fastboot. But don't try that, until we've determined the proper version from getvar output.
I managed to perform the procedure now. See the information:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.29.214500021.24_2G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B11000
(bootloader) cidnum: HTC__621
(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.017s
ddfilho said:
I managed to perform the procedure now. See the information:
(bootloader) version-baseband: 1.29.214500021.24_2G
(bootloader) version-main:
Click to expand...
Click to collapse
As I suspected, your firmware number (version-main) info was wiped out by using an obsolete version of TWRP (known bug). But luckily I know the radio number corresponds to Marshmallow firmware.
Flash TWRP 3.0.2 using the fastboot install method here. No need to install Android SDK, or drivers noted in the instructions, since you already have fastboot setup (and you're a fastboot expert now ); and not need to reboot using adb, if you do it using the button combo other otherwise.
After getting the updated TWRP version installed, you should be able to put the desired custom ROM on the phone, and flash it. If not, take note of any error messages or other behaviors, and post them here.
redpoint73 said:
As I suspected, your firmware number (version-main) info was wiped out by using an obsolete version of TWRP (known bug). But luckily I know the radio number corresponds to Marshmallow firmware.
Flash TWRP 3.0.2 using the fastboot install method here. No need to install Android SDK, or drivers noted in the instructions, since you already have fastboot setup (and you're a fastboot expert now ); and not need to reboot using adb, if you do it using the button combo other otherwise.
After getting the updated TWRP version installed, you should be able to put the desired custom ROM on the phone, and flash it. If not, take note of any error messages or other behaviors, and post them here.
Click to expand...
Click to collapse
Folks
Thank you for your help
I managed to update TWRP following the instructions, but when I tried to install the ROM did not succeed.
It gave an error as if he could not open the file or install, see the message:
Error opening: `/and-sec/uuuuuuuu.uuu'(I/O error) ===> Several lines with mensagem.
You know how I can be able to install any rom?
In TWRP go to WIPE then select Format data, type yes
Then go to REBOOT select recovery ... now try again to install ROM
Hi Guys,
I have an interesting one here, which I have been battling for a couple of days!
My nephew some time ago decided to put some custom ROM’s on his M9. Recently he had some odd happenings relating to encryption (something about asking for passwords), he tried to recover it and bricked it slightly!
Twrp 3.0.2-0 is on the device, but I cannot flash anything to the recovery, even 3.0.1-0. I cannot lock/relock the bootloader and when I try to flash the Unlock_code.bin it hands in download mode and does not give me onscreen instructions. Twrp tells me it cannot mount any partitions with a crypto footer missing message. I have tired reformatting some partitions (cache and data) as well as writing zero’s to the start of the partition and they still cannot mount with an invalid argument message. It also boots straight to the bootloader (with a flash of the HTC logo screen) and I have dd’ed the boot partition off the device and it’s all zeros (not sure if some kind of protection is stopping this).
Together with this these issues, I need to hold volume up and volume down to get to the bootloader (without it flashing the htc logo), but documentation I have read says down and power. When I hold down the volume up, it boots to a white screen with HTC logo. When I hold down the volume down it boot loops the black HTC logo.
Download mode is version 3.35.401.12 and CID HTC__001.
Any help would be appreciated,
Thanks,
FlangeMonkey said:
Hi Guys,
I have an interesting one here, which I have been battling for a couple of days!
My nephew some time ago decided to put some custom ROM’s on his M9. Recently he had some odd happenings relating to encryption (something about asking for passwords), he tried to recover it and bricked it slightly!
Twrp 3.0.2-0 is on the device, but I cannot flash anything to the recovery, even 3.0.1-0. I cannot lock/relock the bootloader and when I try to flash the Unlock_code.bin it hands in download mode and does not give me onscreen instructions. Twrp tells me it cannot mount any partitions with a crypto footer missing message. I have tired reformatting some partitions (cache and data) as well as writing zero’s to the start of the partition and they still cannot mount with an invalid argument message. It also boots straight to the bootloader (with a flash of the HTC logo screen) and I have dd’ed the boot partition off the device and it’s all zeros (not sure if some kind of protection is stopping this).
Together with this these issues, I need to hold volume up and volume down to get to the bootloader (without it flashing the htc logo), but documentation I have read says down and power. When I hold down the volume up, it boots to a white screen with HTC logo. When I hold down the volume down it boot loops the black HTC logo.
Download mode is version 3.35.401.12 and CID HTC__001.
Any help would be appreciated,
Thanks,
Click to expand...
Click to collapse
Oofta. If there ever was a candidate for restoring to stock via RUU, this would be it. From the OS version you list, your SKU is 401. Head to the readme thread and follow the instructions there.
computerslayer said:
Oofta. If there ever was a candidate for restoring to stock via RUU, this would be it. From the OS version you list, your SKU is 401. Head to the readme thread and follow the instructions there.
Click to expand...
Click to collapse
Thank you for the reply, I have an RUU zip that doesn't flag any errors via SD card (not the same story via fastboot, as I get RU security errors). However when it reboots, it goes to the bootloader and not the expected rebootRUU. If I execute 'fastboot oem rebootRUU', it goes into a bootloop. I did some checking and although I could be wrong, it appears to need the boot strap to do RUU, which could be hosed.
FlangeMonkey said:
Thank you for the reply, I have an RUU zip that doesn't flag any errors via SD card (not the same story via fastboot, as I get RU security errors). However when it reboots, it goes to the bootloader and not the expected rebootRUU. If I execute 'fastboot oem rebootRUU', it goes into a bootloop. I did some checking and although I could be wrong, it appears to need the boot strap to do RUU, which could be hosed.
Click to expand...
Click to collapse
Have you tried the backup files in flippy's thread?
Beamed in by telepathy.
shivadow said:
Have you tried the backup files in flippy's thread?
Beamed in by telepathy.
Click to expand...
Click to collapse
Can you please point me to the thread your referring to?
edit: I think I have found what your refering to, I'm just looking at this (Stock_Backup_3.35.401.12.zip), I'll check it out and see if I can do anything with it.
So I tired the flippy "TWRP Backup Section II" and after the restore and selecting boot to system, it boots to the bootloader and it appears retain the original recovery, so it isn't restoring anything by the looks of it. I've also just found out that this phone is a M9u, if that makes any difference and the RUU that doesn't flag any errors is signed_2_4.
FlangeMonkey said:
So I tired the flippy "TWRP Backup Section II" and after the restore and selecting boot to system, it boots to the bootloader and it appears retain the original recovery, so it isn't restoring anything by the looks of it. I've also just found out that this phone is a M9u, if that makes any difference and the RUU that doesn't flag any errors is signed_2_4.
Click to expand...
Click to collapse
It makes a difference all right. Let's back up a step and get all of your phone's information straight. What is it's model and OS version? You can find out by running the command "fastboot getvar all" after installing the HTC adb drivers (via HTC Sync Manager) with your phone plugged into your computer.
Under fastboot:
(bootloader) version:0.5
(bootloader) variant:MTP eMMC
(bootloader) secure:yes
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) max-download-size: 0x20000000
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache: 0x14000000
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0x5e0000000
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0x118000000
(bootloader) serialno:*redacted*
Under Download Mode:
(bootloader) kernel: lk
(bootloader) product: htc_himauhl
(bootloader) version: 1.0
(bootloader) imei: *redacted*
(bootloader) version-main: 3.35.401.12
(bootloader) boot-mode: download
(bootloader) version-baseband: 01.01_U11440792_97.00.51203G_F
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 0PJA10000
(bootloader) cid: HTC__001
On the back of the phone it reads: 0PJA100... FCC... M9u
FlangeMonkey said:
(bootloader) product: htc_himauhl
(bootloader) version-main: 3.35.401.12
(bootloader) mid: 0PJA10000
(bootloader) cid: HTC__001
Click to expand...
Click to collapse
These are the pieces that I find most helpful. From everything provided, I can't see why the M9u shouldn't be able to accept the RUU under normal circumstances.
I notice that in the instructions for the SD card method there is this note in step 6:
"Depending on your current firmware version it may reboot to Android or the Bootloader instead of rebooting to Download Mode. If this happens you just need to manually boot it to Download Mode."
Have you given that a shot? That may solve the problem.
computerslayer said:
These are the pieces that I find most helpful. From everything provided, I can't see why the M9u shouldn't be able to accept the RUU under normal circumstances.
I notice that in the instructions for the SD card method there is this note in step 6:
"Depending on your current firmware version it may reboot to Android or the Bootloader instead of rebooting to Download Mode. If this happens you just need to manually boot it to Download Mode."
Have you given that a shot? That may solve the problem.
Click to expand...
Click to collapse
Yea I did try that as well as a slew of different modes and options, which none of seem to work. I just performed it again for good messure and it bootloops on rebootRUU. I've also found an old backup from the phone itself that was performed back in October with twrp and that has no effect.
I have performed backups using TWRP after restores and examined the images but they are all zeroed! Additionally I do recall seeing write speeds in DD at the 50mb mark, which is way to fast in my opinion and using twrp restore is quick.
It’s very much like nothing is being written, but I have no idea why or if it’s possible to fix.
Could it be possible that something is physically broken, which is preventing writes?
FlangeMonkey said:
Yea I did try that as well as a slew of different modes and options, which none of seem to work. I just performed it again for good messure and it bootloops on rebootRUU. I've also found an old backup from the phone itself that was performed back in October with twrp and that has no effect.
I have performed backups using TWRP after restores and examined the images but they are all zeroed! Additionally I do recall seeing write speeds in DD at the 50mb mark, which is way to fast in my opinion and using twrp restore is quick.
It’s very much like nothing is being written, but I have no idea why or if it’s possible to fix.
Could it be possible that something is physically broken, which is preventing writes?
Click to expand...
Click to collapse
Bummer - it would have been nice if it had been a simple fix there.
It's entirely possible that something is physically broken, but that would probably involve some sort of corrupt memory chip or something. I don't know how you would confirm that though, at least without a professional tearing the phone apart.
From posts I've read elsewhere, it may be possible to flash individual partitions, but that's beyond me. Apart from exploring that option, I'm afraid I'm at a loss.
computerslayer said:
Bummer - it would have been nice if it had been a simple fix there.
It's entirely possible that something is physically broken, but that would probably involve some sort of corrupt memory chip or something. I don't know how you would confirm that though, at least without a professional tearing the phone apart.
From posts I've read elsewhere, it may be possible to flash individual partitions, but that's beyond me. Apart from exploring that option, I'm afraid I'm at a loss.
Click to expand...
Click to collapse
I appreciate your efforts. I have tried flashing partitions via DD and fastboot, but its the same result. Unless anyone can tell me another means to try?
On another note, is it possible to s-OFF in this state (paid or otherwise)?
FlangeMonkey said:
I appreciate your efforts. I have tried flashing partitions via DD and fastboot, but its the same result. Unless anyone can tell me another means to try?
On another note, is it possible to s-OFF in this state (paid or otherwise)?
Click to expand...
Click to collapse
Maybe with a Java Clip. The common method (Sunshine) requires a working ROM
I received an unlocked HTC One M8 (US, works on AT&T, not Harmon Kardon), factory reset, never been modded. Because it ran Android 6.x, I was concerned that it wasn't as secure as it could be, so I researched how to install the newest Android possible. I found many articles on these forums, guides from 2014 all the way to 2016. I didn't (and still don't) know enough to tell the difference between a good tutorial and a bad/outdated one. I saw that some tutorials were edited to reflect new mods, but now that I have read even more, I suspect that even those updated ones are now obsolete.
My problem is that I installed Resurrection Remix with v7.1.2, along with pico Open Gapps, and it won't let me install several apps like Chrome or even YouTube. I have decided that I don't want a newer ROM and I would rather just revert to stock. I have been attempting to revert to stock for the last three or four days, and I have spent many hours researching and reading (mostly this site...go figure), but so far I have not accomplished anything.
Current information about the phone: I did not make a backup (I've had little success doing this over the years on Android phones), I unlocked the bootloader with the HTC unlock code.bin file, the phone has S-ON and has not been rooted. In fact, I've tried SuperSU and Sunshine and neither worked. I have TWRP 2.7.1.0 installed. I have drivers from HTC Sync, but I also installed the Android Studio, along with some utilities that come with it. I have attempted the RUU from HTC (RUU_M8_UL_M60_SENSE70_MR_BrightstarUS_WWE_6.12.1540.4) and it always says that there was an error.
I have attempted several times to change the CID, but only because a tutorial told me to. I assume that it was changed when I installed the Remix mod. I have no idea what it should be. I have attempted to install firmware as well, both with the adb method and by copying it to the SD card and renaming it for bootloader, but both options fail. The adb method fails with...
(bootloader) zip info parsing...
FAILED (remote: 99 unknown fail)
...and the SD card method thinks for a bit, then says "press power to reboot" in the same type of text as the bootloader text.
I am only a little familiar with adb and fastboot, so please, be gentle. If you list commands, I will use them without even thinking, like how Ron Burgandy reads everything on the teleprompter.
Please help.
Here's the getvar:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: INVALID_VER_INFO
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: XXXXXXXXXXXX
(bootloader) imei: XXXXXXXXXXXXX
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul_ca
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B17000
(bootloader) cidnum: GOOGL001
(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: 11459804
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Did I post in the wrong forum? Any help would be greatly appreciated. Thanks!
speedee39 said:
Did I post in the wrong forum? Any help would be greatly appreciated. Thanks!
Click to expand...
Click to collapse
Hi,
no you did not post in the wrong forum. This section is not that active but there are still a handful of people visiting and trying to help.
You've posted plenty of info - which is good. First of all, you can't change the cid if you're s-on. You need to be s-off. Changing the cid is not really necessary unless you want to convert your carrier device into the dev edition or the Google Play edition M8. What cid were you trying? Was changing the cid successful? In that current state it shouldn't.
Speaking of the Google Play edition. You tried to revert to sense stock, according to the ruu you mentioned. The thing is your getvar result shows that your mid and cid directs towards a Google Play edition device. If you want to go on sense there are a few steps you have to do before you can (repartitioning system for example as the storage size is bigger on sense than on GPe).
Another thing is, the TWRP recovery you used is way too old for the firmware. The latest one can be found on twrp.me
Can you tell us how big your system partition is? If it's only over 1GB you certainly have a GPe device - in fact getvar says that as well.
maultasche said:
You've posted plenty of info - which is good. First of all, you can't change the cid if you're s-on. You need to be s-off. Changing the cid is not really necessary unless you want to convert your carrier device into the dev edition or the Google Play edition M8. What cid were you trying? Was changing the cid successful? In that current state it shouldn't.
Click to expand...
Click to collapse
The guide I found for reverting to stock said to change to the super CID (fastboot oem writecid 11111111). I only did that because I thought that it was the "right way" to do this. But if the CID can't be changed unless the phone is s-off, then it must still be stock, because I doubt that I've ever achieved s-off while flashing a different ROM.
maultasche said:
Speaking of the Google Play edition. You tried to revert to sense stock, according to the ruu you mentioned. The thing is your getvar result shows that your mid and cid directs towards a Google Play edition device. If you want to go on sense there are a few steps you have to do before you can (repartitioning system for example as the storage size is bigger on sense than on GPe).
Click to expand...
Click to collapse
Yes, I attempted the Sense stock because the tutorial told me to and also because that's what is listed on HTC's website. I don't want to go to Sense, just thought that I was supposed to. So you're saying that the phone is a Google Play Edition? I'll need to look that up.
maultasche said:
Another thing is, the TWRP recovery you used is way too old for the firmware. The latest one can be found on twrp.me
Click to expand...
Click to collapse
Thank you for that, I didn't know. I'll get it. One question that I've never found the answer to is, if I installed TWRP to change the ROM, what is the stock recovery image? Or, is it bad to simply leave TWRP installed? I have no plans to sell the phone.
maultasche said:
Can you tell us how big your system partition is? If it's only over 1GB you certainly have a GPe device - in fact getvar says that as well.
Click to expand...
Click to collapse
I think I did this correctly. Here's what I found through the shell:
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/block/mmcblk0p45 1032088 853196 178892 83% /system
Once I started looking this up, I found a post on XDA about GPe and different partition sizes. I'll check for GPe ROMs now. Do I need any other files besides that and the updated TWRP? Is the order to install a newer TWRP, then flash the GPe ROM, and then relock the bootloader?
I noticed that the bootloader has a persistent message about it being relocked and **WARNING**. Is there a way to clear the warning flag? One of the tutorials that I was following listed several shell commands to do this. I'm going to list them, so let me know if that is the way to clear the flag.
adb shell
su
echo -ne '\x00\x00\x00\x00' | dd of=/dev/block/mmcblk0p2 bs=1 seek=33796
exit
exit
adb reboot-bootloader
Thanks for your help.
You indeed have a GPe device. If you want to go back to GPe this thread has all your answers, links and ruu's
https://forum.xda-developers.com/showthread.php?t=2708589
Since your device is a GPe device there is no need to change cid, mid etc. - with s-on you can't change them anyways. Just grab the latest GPe ruu and follow flashing instructions.
Stock recovery is only needed for ota-updates. On sense the updates would fail as this particular recovery is missing. I assume on GPe that would happen as well. It's up to you if you use twrp or stock recovery. GPe won't get updates anymore, same as sense.
I recommend not to mess with this stuff in bootloader. Once you go back to stock (ruu etc), it should fix itself. Besides that to temper with it you need to be s-off anyway.
maultasche said:
You indeed have a GPe device. If you want to go back to GPe this thread has all your answers, links and ruu's
https://forum.xda-developers.com/showthread.php?t=2708589
Click to expand...
Click to collapse
Yes, I had found that exact thread earlier today, thanks to you, and I was just replying to tell you that I have successfully reverted my phone back to stock.
In the spirit of contribution to the site that has helped a novice such as me, I want to share the steps I took so that others might be helped.
The phone, as mentioned earlier, is an HTC One M8 Google Play Edition (Gpe), was s-on, not rooted, bootloader unlocked. I had an old version of TWRP and Resurrection Remix ROM using Android 7.1.2.
Prerequisites
1. Stock GPe ROM: https://androidfilehost.com/?fid=817550096634750828
2. TWRP 3.1.1-0-m8: https://dl.twrp.me/m8/twrp-3.1.1-0-m8.img.html
3. Backup account fix (linked in aforementioned thread): https://www.androidfilehost.com/?fid=24686680535467942
4. ADB and fastboot
5. Unlocked bootloader
**This assumes that you have a Windows computer. I used Windows 10 v1709**
Steps
1. Copy the ROM and TWRP files to the same folder in which fastboot and ADB are located. This makes it easier to run commands.
2. (There might be another way to do this one, but I don't know it) Copy the backup account fix file "MRA58K.H15_backup-account-fix.zip" to a micro SD card and put it in the phone.
3. Open a command prompt or PowerShell window in the folder that contains ADB and fastboot by right-clicking + Shift in an open area and selecting "Open PowerShell/Command Prompt window here."
4. In the PowerShell/Command Prompt window, type "fastboot flash recovery twrp-3.1.1-0-m8.img" and press Enter to install TWRP
5. Reboot into the bootloader and choose "fastboot," then choose "recovery"
6. In TWRP, browse to ADB sideload and then "swipe to start sideload."
7. In your PowerShell/Command Prompt window, type "adb sideload HTC_One_M8_GPe_Marshmallow-6.0_MRA58K.H15_AROMA-Installer-v6-020817.zip" and press Enter to start the installation
8. On the phone's screen, choose the top option, which should be the unrooted, completely stock installation.
9. On my machine, the PowerShell/Command Prompt window showed progress up to 41% and then it finished successfully.
10. After that, do not reboot, but go back into the main TWRP menu and go to Install. Browse to the MRA58K.H15_backup-account-fix.zip file that you previously saved on your SD card and install it.
11. Once that is installed, reboot the phone. My phone took between 5 and 10 minutes to boot the first time.
12. (Optional) I wanted to have a completely reverted phone, so I locked the bootloader again by rebooting the phone into the bootlader and typing "fastboot oem lock" in the PowerShell/Command Prompt window. It then said "relocked" but no warnings or errors.
I hope this helps somebody. All credit goes to maultasche for pointing me in the right direction and to graffixnyc for the other thread.