Related
Hi,
I have a HTC One M7 WLV (the 4g from Verizon). Recently it had some problems and I had to factory reset it, however I opted for changing to another ROM. It did not go well, and I blame it on not knowing the correct version of recovery/kernel/rom to use on it. So I figured I could ask you guys.
Here is the "getvar all" for my phone:
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4T.21.3218.21
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) product: m7_wlv
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0731000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 3888mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0e82187e
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.062s
And my current recovery is the latest ClockworkMod i could find (6.0.4.8).
Recon that should be enough to figure the correct version.
I am looking to install an as-vanilla-as-possible ROM of Google Play Edition for the latest version of it.
Could someone post the links for downloads of all the files I might need (including bootloader, recovery and kernel if needed)?
Thanks a bunch!
f.
Some links I have found useful after picking up a used vzw m7
flpgdt said:
Hi,
I have a HTC One M7 WLV (the 4g from Verizon). Recently it had some problems and I had to factory reset it, however I opted for changing to another ROM. It did not go well, and I blame it on not knowing the correct version of recovery/kernel/rom to use on it. So I figured I could ask you guys.
[...]
And my current recovery is the latest ClockworkMod i could find (6.0.4.8).
Recon that should be enough to figure the correct version.
I am looking to install an as-vanilla-as-possible ROM of Google Play Edition for the latest version of it.
Could someone post the links for downloads of all the files I might need (including bootloader, recovery and kernel if needed)?
Click to expand...
Click to collapse
I'm relatively new to this phone, so it's fresh in my memory... I can see you've got s-off, so I assume your bootloader is also unlocked? Assuming it is, I would say to first flash the latest of the MDMower build of TWRP found here. I too was in the habit of using CWM, but I found the version you reference is way too slow doing wipes, backups, etc. (and therefore suspicious). Also, most current ROM threads and devs seem to be recommending TWRP for this device. Now that I've used TWRP for a while, I'm happy with it.
Next I would suggest following the advice in the OP of this to thread install the NuSenseSIX ROM. In particular, update your firmware according to this post. Once you've got TWRP, the latest firmware and NuSenseSIX running as a stock-like point of reference, you can backup, try other ROMs, etc. The same excellent developer, santod040, who packaged the latest firmware and NuSenseSIX ROM has also released a couple of nice GPE ROMs (totally stock and "plus").
FWIW, I'm currently running cm11 for the m7vzw with TinyKernel in order to get the "logo2menu" feature.
Finally, prior to getting my phone unlocked and up-to-date, I also found the links in this post quite helpful.
flpgdt said:
Hi,
I have a HTC One M7 WLV (the 4g from Verizon). Recently it had some problems and I had to factory reset it, however I opted for changing to another ROM. It did not go well, and I blame it on not knowing the correct version of recovery/kernel/rom to use on it. So I figured I could ask you guys.
Here is the "getvar all" for my phone:
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4T.21.3218.21
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) product: m7_wlv
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0731000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 3888mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0e82187e
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.062s
And my current recovery is the latest ClockworkMod i could find (6.0.4.8).
Recon that should be enough to figure the correct version.
I am looking to install an as-vanilla-as-possible ROM of Google Play Edition for the latest version of it.
Could someone post the links for downloads of all the files I might need (including bootloader, recovery and kernel if needed)?
Thanks a bunch!
f.
Click to expand...
Click to collapse
You are on an old firmware (hboot is 1.54 when we have hboot 1.57) and your radio is odd, not a Verizon radio. Use the link above to flash the latest Verizon radio and firmware. There is a thread to put your CID back to stock (your getvar all shows all ones and it should be VZW__001 and the Fastboot command is "fastboot oem writecid VZW__001" iirc) as for GPE, there is a couple that are pure port from the m7 GPE in the development section. Almost all devs recommend TWRP for stock (sense) and GPE roms.
Sent from my HTC6500LVW using XDA Free mobile app
Update your firmware like they said, then I recommend this for GPE
http://forum.xda-developers.com/showthread.php?t=2531235
I have had nothing but issues with cwm over the years on different phones. Twrp is the most reliable I have seen. So once you update everything to the latest you should be able to enjoy all the ROMs are have. Be it santod, hawk, and so on
Sent from my Nexus 7 using Tapatalk
Hi guys, thanks for the answers!
For the record, the versions indicated by bmeek all worked. Throughout the process I also found I had a corrupted /data partition and managed to fix it with this tutorial:
http://android-revolution-hd.blogspot.com.br/2013/10/fix-data-htc-one.html
Thanks for the help!
f.
Hey you pros
I am currently a little confused. I just got my HTC ONE m8 (dual boot) a week ago and tried since then to flash a custom rom. I unlocked my phone via htcdev and unlocked is shown. I do not have s off, because I read flashing should also work this way. I tried with twrp 2.8.1.0 on the old firmware (1.45.401.12). I did a full wipe and tried every different way, like booting into recovery via fastboot, flashing the kernel seperately. The newer version of twrp didn't work, and neither did cwm. Then I tried to update the firmware over the normal OTA way and have now version 3.33.401.6. The new twrp is working now, but i again tried all ways known to me and no one worked. Do you guys know what is wrong? I searched over google read different threads, but can't find an answer.
I would really appreciate if you could help me!
Here is the fastboot getvar all:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.22.30306251.27G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.33.401.6
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: ---
(bootloader) imei: ---
(bootloader) imei2: ---
(bootloader) meid: 00000000000000
(bootloader) product: m8_dugl
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B64000
(bootloader) cidnum: HTC__102
(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: 4c3fbd70
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
Oh and by the way I tried to flash the Official Nightlys of CM 11 and "[ROM][5.0.2][OFFICIAL] LiquidSmooth v4.0 | Lollipop | [12-25-14]".
Thanks for your help!
xhdev
So you're saying you fastboot flashed the kernel separately from the ROM itself?
Magnum_Enforcer said:
So you're saying you fastboot flashed the kernel separately from the ROM itself?
Click to expand...
Click to collapse
Yes, I ALSO tried this, because I read somewhere that with s on the recovery can't access /boot. I did this with the command "fastboot flash boot boot.img" if that helps. In this case I used of course the kernel within the rom archive. I tried as well to (again after full wipe) just flash the *.zip archive, which had again the outcome of the bootloader appearing directly on turn on before any logo or animation.
Info for everyone having the same problem: The problem is due to the dual sim model, which is incompatible to the standard custom roms. At the moment there is only maximus hd 2.0 for our model. Im not sure if one can change cid and get other roms to work or if there are other custom roms. If somebody knows more, I'd really appreciate a hint about that.
Sent from my HTC One_M8 dual sim using XDA Free mobile app
devxh said:
Hey you pros
I am currently a little confused. I just got my HTC ONE m8 (dual boot)..
Click to expand...
Click to collapse
I think you are confused
You have a dual sim (although dual boot would be nice). You need to be really careful what you do with it.
Unless stated, any other custom rom on xda (as of today) will not work on your dual sim.
As @devxh says, there are no custom roms apart from MaximusHD (we live in hope though)
Do not try any other roms.
Having said that, I have TWRP 2.8.1 and thats working fine and can recommend MaximusHD as a good replacement for stock rom.
It certainly 'feels' quicker than stock.
If you try it, make sure you update your firmware otherwise you will lose wifi
Soooo....Noob right here :]
I did a really stupid thing, I tried rooting my HTC One M8. I followed the steps, and it worked fine until I flashed and rebooted. After that, the phone was stuck at boot logo, so I decided to just factory reset it, but somehow, after doing that through TWRP, it reboots > went through logo white screen > then stuck at a black screen. I waited for about 20 mins but no luck. What should I do now?
dwerp1234 said:
Soooo....Noob right here :]
I did a really stupid thing, I tried rooting my HTC One M8. I followed the steps
Click to expand...
Click to collapse
What steps?
There are a few different ways to go about rooting, plus if you don't tell us what TWRP version, stock Android version, SuperSU version, etc. we have no way of knowing what you did, much less how to help you.
dwerp1234 said:
so I decided to just factory reset it
Click to expand...
Click to collapse
Why? Did you read somewhere that this was the proper thing to do for the specific situation? Or did someone tell you? If no to both, don't make up your own solutions or try to guess how to fix things. Its a good way to make matters worse than they already are.
There is no reason to think that a factory reset would fix the issue. There is a common misconception of what "factory reset" actually does. All it does is wipe user data, nothing else. It doesn't replace the ROM, or anything like that.
I'm not sure what Android version my phone is right now (I do not know how to check), the TWRP is 2.8.7.0 for M8, the SuperSU just came with the TWRP, so I just followed the TWPR and got the installer, after that, I downloaded the Root pack or sth like that, but it wasn't automatically rebooting into root mode, so I downloaded the pack and then manually reboot it, after that, it froze on boot logo
I read the factory reset thing on a forum too. Besides wiping cache and data, I wiped the system as well, so there is currently no OS right now, and then planned to download the ROM onto an ext SD card then install it through TWRP. But right now, I still haven't find the proper stock ROM in zip file.
Thanks for your reply, I hope this information helps
dwerp1234 said:
I'm not sure what Android version my phone is right now (I do not know how to check), the TWRP is 2.8.7.0 for M8, the SuperSU just came with the TWRP, so I just followed the TWPR and got the installer, after that, I downloaded the Root pack or sth like that, but it wasn't automatically rebooting into root mode, so I downloaded the pack and then manually reboot it, after that, it froze on boot logo
I read the factory reset thing on a forum too. Besides wiping cache and data, I wiped the system as well, so there is currently no OS right now, and then planned to download the ROM onto an ext SD card then install it through TWRP. But right now, I still haven't find the proper stock ROM in zip file.
Thanks for your reply, I hope this information helps
Click to expand...
Click to collapse
No offense, but this sounds WAY out of your league., especially if you don't know how to check your Android version. It's always best to read directions thoroughly first and ask for help before actually attempting to start modifying your device.
You could always try restoring to stock using the specific RUU for your device. I had to do that recently myself in order to get S-OFF.
http://www.htc.com/us/support/rom-downloads.html
dwerp1234 said:
I'm not sure what Android version my phone is right now (I do not know how to check)
Click to expand...
Click to collapse
Do you remember if it was on KitKat, Lollipop, Marshmallow?
You unlocked the bootloader by yourself? Is it currently unlocked?
Connect phone to computer, reboot the phone to bootloader, and select FASTBOOT (if not already highlighted in red) using the vol and power keys. Then open a command prompt on the computer and type command: fastboot getvar all
Post the getvar output (delete IMEI and serial numbers before posting).
The output will help tell us the Android version, as well as other critical info to get your sorted out.
dwerp1234 said:
the SuperSU just came with the TWRP
Click to expand...
Click to collapse
Depending on what Android build you are trying to root, the built-in root on TWRP won't work. Which is why we need to know the Android version.
dwerp1234 said:
I read the factory reset thing on a forum too. Besides wiping cache and data, I wiped the system as well, so there is currently no OS right now, and then planned to download the ROM onto an ext SD card then install it through TWRP. But right now, I still haven't find the proper stock ROM in zip file.
Click to expand...
Click to collapse
Deleting the OS is usually not a good idea; and in your situation not a legitimate solution. Even if you were going to flash a new ROM, that process wipes system partition anyway, so no need to do it manually. And wiping the OS before finding the right ROM to flash was also not a great idea.
It might not have made a difference in your case (since you couldn't boot to OS even before you wiped it). But wiping system shouldn't be done unless you really have a good reason to do it, and you understand what the result will be.
I can't count how many posts I've read (and helped) that stated along the lines of "I wiped system and now my phone won't start, please help".
Hmm, thanks for that link, my Android is 5. Lollipop, I just get so confused with all the numbers on bootloader...How do you get S-OFF though? I've been trying to do that, but found no answer.
My Android is indeed unlocked, I followed the instruction on the internet and got it unlocked.
Oh, here is my getvar output:
(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.19.707.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B11000
(bootloader) cidnum: HTC__059
(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: 3aa067db
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.016s
For the wiped system situation, I followed the instruction on a website on how to install stock ROM, but I'm stuck on finding a stock ROM myself, and I thought deleting the OS wouldn't make any difference.
dwerp1234 said:
My Android is indeed unlocked, I followed the instruction on the internet and got it unlocked.
Oh, here is my getvar output:
(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.19.707.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B11000
(bootloader) cidnum: HTC__059
(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: 3aa067db
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.016s
For the wiped system situation, I followed the instruction on a website on how to install stock ROM, but I'm stuck on finding a stock ROM myself, and I thought deleting the OS wouldn't make any difference.
Click to expand...
Click to collapse
What websites are you going to, and why? Everything you need to know about rooting can be found here.
Download this onto your PC. It's an RUU for your model and firmware version. Also, it's a direct download link, so don't click it on your phone.
After the download is finished, hook your phone up to your PC. Get into fastboot, and enter fastboot oem lock. This will lock your bootloader, which you will need to do since you are S-On.
After that, double click on the download and follow the prompts.
This will get you back to your stock state. Unlock your bootloader again via htcdev.com, use fastboot to flash TWRP2.8.7.0, then use your new recovery to flash the latest SuperSU update.zip, or simply flash a rooted ROM with that same recovery.
That's it. Fixed phone and rooted.
xunholyx said:
What websites are you going to, and why? Everything you need to know about rooting can be found here.
Download this onto your PC. It's an RUU for your model and firmware version. Also, it's a direct download link, so don't click it on your phone.
After the download is finished, hook your phone up to your PC. Get into fastboot, and enter fastboot oem lock. This will lock your bootloader, which you will need to do since you are S-On.
After that, double click on the download and follow the prompts.
This will get you back to your stock state. Unlock your bootloader again via htcdev.com, use fastboot to flash TWRP2.8.7.0, then use your new recovery to flash the latest SuperSU update.zip, or simply flash a rooted ROM with that same recovery.
That's it. Fixed phone and rooted.
Click to expand...
Click to collapse
Thanks for your answer. If you don't mind me asking, but what is the latest stable SuperSU for my version? Is it 2.65?
Edit: After I tried to run the ROM Update .exe, it ended up with an error: ERROR [170]: USB CONNECTION ERROR, although I already connected my phone and it is currently stuck on boot screen as always.
dwerp1234 said:
Thanks for your answer. If you don't mind me asking, but what is the latest stable SuperSU for my version? Is it 2.65?
Click to expand...
Click to collapse
As you are still on Lollipop, any SuperSU version 2.44 or up should be find. I think 2.46 is the latest version still labelled as STABLE.
If you were updated to Marshmallow, you would need 2.62 or higher. Those are labelled as BETA, but folks have been using them with no issues, in my understanding.
dwerp1234 said:
Edit: After I tried to run the ROM Update .exe, it ended up with an error: ERROR [170]: USB CONNECTION ERROR, although I already connected my phone and it is currently stuck on boot screen as always.
Click to expand...
Click to collapse
On boot screen, in fastboot mode (with fastboot highlighted in red)?
You were able to do fastboot getvar all, so I assume "yes" to the that question. So in that case, the RUU can be very finicky. Try re-installing HTC Sync, different USB port, different cable.
You might even need to try another PC. Win7 and USB 2.0 (USB 3.0 is known to cause issues) are your best bet to get the RUU to work.
redpoint73 said:
As you are still on Lollipop, any SuperSU version 2.44 or up should be find. I think 2.46 is the latest version still labelled as STABLE.
If you were updated to Marshmallow, you would need 2.62 or higher. Those are labelled as BETA, but folks have been using them with no issues, in my understanding.
On boot screen, in fastboot mode (with fastboot highlighted in red)?
You were able to do fastboot getvar all, so I assume "yes" to the that question. So in that case, the RUU can be very finicky. Try re-installing HTC Sync, different USB port, different cable.
You might even need to try another PC. Win7 and USB 2.0 (USB 3.0 is known to cause issues) are your best bet to get the RUU to work.
Click to expand...
Click to collapse
Thanks a lot, I changed the port and it runs fine. The ROM is being updated right now. It says it will take 10 mins, but it has been 40 minutes and still 0/6. I'm using win10 btw. I have no win7 around.
dwerp1234 said:
Thanks a lot, I changed the port and it runs fine. The ROM is being updated right now. It says it will take 10 mins, but it has been 40 minutes and still 0/6. I'm using win10 btw. I have no win7 around.
Click to expand...
Click to collapse
You have connection issue .. I'm on Win 10 64-bit and no problem when running RUU.
You need to use USB2.0
Latest HTC USB driver installed - Install HTC Sync Manager - http://www.htc.com/us/support/software/htc-sync-manager.aspx
it will install the needed drivers then uninstall the HTC Sync Manager but leave the drivers.
And I always see many people with USB connection and unable to run RUU ... that's why we have nandroid backup to restore to stock.
Check - http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
These are my getvar all results . Guidance please
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.29.214500021.12G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: SH4BTWM00156
(bootloader) imei: 357336066036366
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: HTC__203
(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: 76df2b54
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
TNTN 997 SU said:
These are my getvar all results . Guidance please
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.29.214500021.12G
(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: 0P6B10000
(bootloader) cidnum: HTC__203
(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: 76df2b54
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
remove your serialno and imei
Then what do you need ?
ahmed.ismael said:
remove your serialno and imei
Then what do you need ?
Click to expand...
Click to collapse
I tried to root my device and it didn't work properly and now it is stuck in the boot logo "that white screen with green hhtc on it". I was runniing on marshmellow and twrp version 3.0.2. I factory reset it but still didn't work. I wanna go back to stock. tried different ways but still didn't work
TNTN 997 SU said:
I tried to root my device and it didn't work probably and now it is stuck in the boot logo "that white screen with green hhtc on it". I was runniing on marshmellow and twrp version 3.0.2. I factory reset it but still didn't work. I wanna go back to stock. tried different ways but still didn't work
Click to expand...
Click to collapse
Here all you need is in this post follow the instruction and you will be back to stock be aware that your internal storage will be wiped
http://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
after that if you want to root your device flash the latest twrp then flash the latest supersu.zip ( 2.78 SR1 )
ahmed.ismael said:
Here all you need is in this post follow the instruction and you will be back to stock be aware that your internal storage will be wiped
http://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
after that if you want to root your device flash the latest twrp then flash the latest supersu.zip ( 2.78 SR1 )
Click to expand...
Click to collapse
Thanks alot
TNTN 997 SU said:
I factory reset it but still didn't work. I wanna go back to stock. tried different ways but still didn't work
Click to expand...
Click to collapse
To be clear, factory reset doesn't revert anything back to stock, aside from (all it does is) wiping user data.
failed to flash anything to my htc one m8
how can i get rid of this error
Code:
target reported max download size of 1826418688 bytes
error: cannot load 'Unlock_code.bin': No error
edwinariko said:
how can i get rid of this error
Code:
target reported max download size of 1826418688 bytes
error: cannot load 'Unlock_code.bin': No error
Click to expand...
Click to collapse
The error message "cannot load" means the file isn't in the right place. You need to put the unlock bin file in the same folder which contains fastboot.exe (and where you are executing the command from).
So this had to happen to me after flashing many phones for others, and when trying to upgrade my own HTC One M8.
I followed a guide on rootingthe M8 (sorry can't post the link) and when trying to flash the TWRP recovery things went wrong. The phone was stuck and it failed to boot. I managed to get it back into flashboot, but after spending too much time after my laptop I accidentally used the command; flashboot flash boot recovery.img
At this point; my phone gives the status unlocked.
I can access fastboot and use commands through the pc.
I can run HBOOT
Recovery won't work; the phone will boot and will not respond
C:\adb>fastboot getvar all | clip
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: [email protected]
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.10.114.11
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8ql_ul
(bootloader) platform: hTCBmsm8939
(bootloader) modelid: 0PKV10000
(bootloader) cidnum: T-MOB003
(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: 8e18db08
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
(bootloader) mfg-name: 0001
At this point I actually don't really care whether I flash it back to stock (not my preference actually) or use a custom ROM. Using it again would be great.
If anyone can point me into the right direction I would be very happy.
Flash TWRP 3.0 again? I tried to root my Sense Marshmallow and was stuck in the HTC boot logo, I was able to fix it by just flashing a random ROM.
Well I didn't manage to flash TWRP 3.0 the newest versions give an error (Bootmagic check fail).
It seems like twrp-2.8.5.0-m8.img flashes well, however when I choose recovery the phone boots and goes black.
The good news for you is that if you can use fastboot, there is still hope. I have saved my phone multiple times from these same situations. Luckily, the fix is fairly simple. I found that by trying different versions of TWRP I eventually found one that worked. I am not exactly sure which one would work for you but eventually you should be able to find one. Also I suggest getting S-Off for your phone if you don't already have it. That way you would be able to install any rom for a previous version of android if needed. Hope this helps!
Thanks for the tip.
I have tried all TWRP versions and all below the 2.8.5 version do write to the phone, however when I try to go to recovery the phone boots shows the HTC startup screen and then goes blank.
I would love to use S-off but, I will need to fix the recovery first :good:
So as the key doesn't seem to tbe the recovery, which for some reason keeps failing.
Would it work if I could obtain an original boot.img ?
You do realize that you have the M8S and not a M8 right ?
http://forum.xda-developers.com/showthread.php?t=3114245
I am not, I'll dig into it.
That's the culprit for not getting it to work. You need different files. Think the easiest way is to RUU it back to stock and start all over.
Just like roms. The M8 roms mainly do not work on the M8s (only when specified in the rom thread OP).
Here is at least a fully working M8s custom recovery
http://forum.xda-developers.com/showthread.php?p=65397339
Mr Hofs said:
That's the culprit for not getting it to work. You need different files. Think the easiest way is to RUU it back to stock and start all over.
Just like roms. The M8 roms mainly do not work on the M8s (only when specified in the rom thread OP).
Here is at least a fully working M8s custom recovery
http://forum.xda-developers.com/showthread.php?p=65397339
Click to expand...
Click to collapse
Awesome, I grabbed the recovery and installed CM12.1
Long story short, I forgot my screen lock and wiped as a last resort. Realizing too late that a factory reset wouldn't complete, I was left with a paperweight. I was able to get a rooted stock ROM from XDA, flashed it and it seems to be working. I want to get back to viper ROM, preferably marshmallow (I'm currently on lollipop) but I am having a lot of trouble. Attempts to get s-off have been thwarted, and flashing viper (5.0.2) has failed. Any help would be appreciated. I can answer any questions.
What stock ROM did you flash, exactly?
How exactly are you trying to s-off, and what step did you get stuck (error messages, or other results?)?
When the ROM failed, did it give you an error message (or list any other outputs or results)?
Your statements on these last 2 points if far too vague, for us to help properly.
Also, do fastboot getvar all, and post the results (delete IMEI and serial number before posting).
Lmy470.h6 is the ROM I flashed. I've been trying to push firewater via adb to get s off. I can't/won't pay for a sunshine. When flashing other stock Roms, the error is no error. It just says install aborted. When trying to flash viper, it says there's a permission error. When trying to run firewater, it gives me the PIE error. Getvar coming later.
Firewater won't work, Period. It had an online component (had to connec to a server), which the devs stopped supporting in Dec 2014. Nothing you do will make it work, and is a complete waste of time.
That said, you don't need s-off to flash ROMs. And whatever is wrong with flashing ROM, s-off is probably not going to fix.
The fact that multiple ROMs work, indicates user error, and you're incorrectly trying to blame the ROMs ("poop ROM").
What TWRP version? Need that info, and getvar data. But I'm guessing you just have an old version of TWRP (or try another slightly different build TWRP).
I'm actually using philz touch recovery. I only call it a poop ROM because I don't like what it came with and how it looks. Also. The ROM I'm using is the only ROM that works thus far. Most other Roms simply abort. Viper ROM tells me it doesn't have to permissions necessary which indicates the need for s off. I attempted getvar, however the command window just sat idle and wouldn't let me type anything. Am I missing something there?
I should also mention I've been using recovery to flash Roms. Perhaps flashing via adb would work better? Or work at all?
One last thing. Flashing the ROM I'm currently using created new 0 directories. I now have 0/0/0. Any safe way to fix that?
enviouss said:
I'm actually using philz touch recovery.
Click to expand...
Click to collapse
That's the problem right there. Philz hasn't been updated in a long time, maybe 2 years. Its almost certainly the cause for the ROM flashes failing.
Use TWRP, but exact version depends on your current firmware version, indicated in getvar. But probably TWRP 2.8.7 since you indicated you were using Lollipop ROMs okay.
enviouss said:
I only call it a poop ROM because I don't like what it came with and how it looks.
Click to expand...
Click to collapse
So its your personal opinion and preference, and I would recommend you not insulting the work of devs that work so hard (usually for no compensation) to post their work here.
---------- Post added at 10:09 AM ---------- Previous post was at 10:06 AM ----------
enviouss said:
I should also mention I've been using recovery to flash Roms. Perhaps flashing via adb would work better? Or work at all?
Click to expand...
Click to collapse
Sideload adb still needs the proper recovery, adb can't flash a ROM by itself. Sideload just adds move points of failure, not less. I don't recommend it, as I've seen it cause more problems than it solves (fails when simply flashing in recovery works).
---------- Post added at 10:11 AM ---------- Previous post was at 10:09 AM ----------
enviouss said:
I attempted getvar, however the command window just sat idle and wouldn't let me type anything. Am I missing something there?
Click to expand...
Click to collapse
Are you in bootloader-fastboot mode when issuing the command?
If so, try another cable, another USB port, or re-install HTC drivers.
I haven't been I boot loader mode. Will try shortly. Also. Will change to twrp. And yes, I'm on lollipop 5.1. I will change recoveries and attempt getvar. Results will be posted.
Getvar results follow.
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.21.21331147A1.19_2G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.28.1540.5
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul_ca
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B12000
(bootloader) cidnum: BS_US001
(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: df77f8b7
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.048s
Getvar results follow.
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.21.21331147A1.19_2G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.28.1540.5
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul_ca
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B12000
(bootloader) cidnum: BS_US001
(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: df77f8b7
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.048s
enviouss said:
Getvar results follow.
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.21.21331147A1.19_2G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.28.1540.5
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul_ca
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B12000
(bootloader) cidnum: BS_US001
(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: df77f8b7
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.048s
Click to expand...
Click to collapse
Also, flashed your recommended version of TRWP recovery. It is up and running. I am ready for the next phase.
enviouss said:
Also, flashed your recommended version of TRWP recovery. It is up and running. I am ready for the next phase.
Click to expand...
Click to collapse
I'm glad I asked for the getvar data. Your firmware (hboot, radio, etc.)is woefully outdated as its still on kitkat firmware, which I can tell from the radio number and version-main 3.28.1540.5. This alone will prevent LP and MM ROMs from working (no boot or broken WiFi).
There are various ways to update the firmware:
- Restore stock TWRP backup for 3.28.1540.5, and corresponding stock recovery, and perform OTA updates which will also update the firmware.
- Relock bootloader, and flash full stock 6.12.1540.4 firmware following the Method 2 here. After flashing firmware, you can then unlock bootloader again, flash TWRP and flash the desire ROM.
I would greatly prefer not to relock my boot loader,as it requires HTC correspondence to unlock. That could take a while. Can you walk me through your first method? Possibly with links to other threads and downloads?
I messed up. big time. So i found and downloaded your recommended recovery image. Downloaded flashify for root, and flashed the image. Now whenever I try to boot, or enter recovery mode, i get the red triangle of death. Please help! I tried reflashing twrp via adb, but adb doesnt recognize my device anymore! I dont know what to do...
update: performed a factory reset. Was able to get device up and running again. Impatiently awaiting further instruction.
enviouss said:
I messed up. big time. So i found and downloaded your recommended recovery image. Downloaded flashify for root, and flashed the image.
Click to expand...
Click to collapse
What did you download, and from where? Its not clear what you were trying to do here, exactly. You don't need root to flash ROMs or TWRP backups; and I personally dislike using apps like Flashify, for things that are easily accomplished with fastboot, TWRP, etc.
I found the stock nandroid backup suggested and flashed it using flashify. I have an idea what needs to be done here, but if an expert like yourself could leave me some detailed instructions as well ad download links it would really help.
enviouss said:
I found the stock nandroid backup suggested and flashed it using flashify. I have an idea what needs to be done here, but if an expert like yourself could leave me some detailed instructions as well ad download links it would really help.
Click to expand...
Click to collapse
He did give you expert advice, and you didn't follow it. Don't use Flashify. Any instructions you get from anyone here will tell you to use ADB/fastboot.
Also, you are going ahead without proper instructions and you can go ahead and do that, but go to where you got those other instructions from to ask for help.
Actually, in reference to the nandroid backup, he (we are assuming here) never said exactly how to use the files. Just what to do. I need precise instructions with links to fix this issue. This is one I've never dealt with before.