Related
Hi everyone! My problem is that if I flash any rom (I've tried ARHD, Viper), the phone gets stuck at the boot screen. I've left it in that state for almost an hour and it hasn't progressed further. Restoring my nandroid backups also yields the same result. My fastboot getvar all:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 1.16.21331831.A15G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HT45
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B65000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: c3d94491
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.163s
The phone is currently unlocked, s-off. I tried flashing with both, philz and twrp, none work. Also, these roms worked before on the same phone with the same recovery so I really have no idea of what went wrong. The firmware on the phone is 1.56.720.6 (Asia-India). I have tried clearing the cache partition multiple times, but it doesn't help.
n1234d said:
Hi everyone! My problem is that if I flash any rom (I've tried ARHD, Viper), the phone gets stuck at the boot screen. I've left it in that state for almost an hour and it hasn't progressed further. Restoring my nandroid backups also yields the same result. My fastboot getvar all:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 1.16.21331831.A15G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HT45
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B65000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: c3d94491
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.163s
The phone is currently unlocked, s-off. I tried flashing with both, philz and twrp, none work. Also, these roms worked before on the same phone with the same recovery so I really have no idea of what went wrong. The firmware on the phone is 1.56.720.6 (Asia-India). I have tried clearing the cache partition multiple times, but it doesn't help.
Click to expand...
Click to collapse
The attached image is where it gets stuck. Adb works
E:\m8\>adb devices
List of devices attached
HT45NWM07703 device
@EddyOS, @nkk71 please see this. I think there's something wrong with my /data partition..
Did you recently do the GPE conversion?
May be you should try to flash the stock rom and stock recovery then flash the ruu.
Sir-Fix-a-Lot said:
Did you recently do the GPE conversion?
Click to expand...
Click to collapse
This, the partitions get altered so you can't just simply flash back
According to the OP's getvar output they've NOT done the GPe conversion as the HBOOT version included in the RUU is 3.18.0.0000 and the OP is still on 3.16.0.0000
OP, I'd follow my guide linked in my signature and you should be good to go
Sir-Fix-a-Lot said:
Did you recently do the GPE conversion?
Click to expand...
Click to collapse
Nope
Jyotirdeb said:
May be you should try to flash the stock rom and stock recovery then flash the ruu.
Click to expand...
Click to collapse
I hadn't touched the firmware, so there shouldn't be any problem related to that. Anyways, a rom and recovery do Not affect an RUU flash.
ashyx said:
This, the partitions get altered so you can't just simply flash back
Click to expand...
Click to collapse
Again, nope, I didn't do gpe
EddyOS said:
According to the OP's getvar output they've NOT done the GPe conversion as the HBOOT version included in the RUU is 3.18.0.0000 and the OP is still on 3.16.0.0000
OP, I'd follow my guide linked in my signature and you should be good to go
Click to expand...
Click to collapse
I flashed the international fw zip, and ARHD, (I had checked the hash of the file) and it still didn't work. Also, when I would reboot, some random artefacts would appear during the boot animation (different each time, sometimes wouldn't appear), such as there would be a random flash of purple across the screen or the boot animation would leave a trail behind it (like the effect you get web you would drag a stuck window in win98) etc. sometimes TWRP would act extremely sluggish while sometimes it would be fast and snappy. Quite a few times, while flashing any rom, the screen would go black and reboot to TWRP at random (even after disabling the display timeout). I tried formatting all the partitions on the internal storage. Still gave me problems. I tried to repair file system of each partition in TWRP. The data partition could never get repaired. All of these random problems lead me to believe that this was 99% the fault of the phone/hardware. Luckily I was within the 14 day replacement period and so I went out today after flashing the faux locked/s-on bootloader (I know I should not mess with firmware unless required, and I hadn't till now but I didn't care anymore since I was getting it replaced anyway. I also had 2 dead pixels and a scratch on my camera glass. Now I just have to sit back and wait for a new phone
We've seen this issue on Viper a few times and it usually happened after someone installed e.g. a VZW recovery to the GSM phone or vice versa.
A wrong recovery would flash stuff into the wrong partitions.
A RUU for your device, really just any, should fix it. You should run a RUU and then factory reset right afterwards from bootloader BEFORE flashing another custom recovery.
There is a cingular (AT&T) RUU out right now from HTC here: http://dl3.htc.com/application/RUU_...G_20.31A.4145.02L_release_368350_signed_2.exe which you could try - it is a GSM RUU. We don't really have WWE 401 RUU yet.
Just make sure you don't grab a SPRINT or Verizon RUU if you find any!!!!!!
Sneakyghost said:
We've seen this issue on Viper a few times and it usually happened after someone installed e.g. a VZW recovery to the GSM phone or vice versa.
A wrong recovery would flash stuff into the wrong partitions.
A RUU for your device, really just any, should fix it. You should run a RUU and then factory reset right afterwards from bootloader BEFORE flashing another custom recovery.
There is a cingular (AT&T) RUU out right now from HTC here: http://dl3.htc.com/application/RUU_...G_20.31A.4145.02L_release_368350_signed_2.exe which you could try - it is a GSM RUU. We don't really have WWE 401 RUU yet.
Just make sure you don't grab a SPRINT or Verizon RUU if you find any!!!!!!
Click to expand...
Click to collapse
Too late for trying a fix , I just want to know what caused it, and I'm 1000% sure I had the right recovery, because as I said, I flashed many other roms in the past with the same recovery, and the problem came after I tried ARHD. And this is the gsm phone.
Yeah well no idea then. Just know I've seen this happen from wrong recoveries. Also not the time to dig into it any further if you've gotten that resolved already I'll leave it as is. Thanks for asking me though. Just keep in mind I've been out of XDA since months and am only slowly reading my way back in so I'm sure there are way more knowledgeable guys around regarding firmware, softbricks and the like.
mobile post... lazy typing...
n1234d said:
Too late for trying a fix , I just want to know what caused it, and I'm 1000% sure I had the right recovery, because as I said, I flashed many other roms in the past with the same recovery, and the problem came after I tried ARHD. And this is the gsm phone.
Click to expand...
Click to collapse
In such a big mess! I have the same problem as the OP - same to the last dot. I am on India version of device, and was just trying to update firmware to 4.4.3 and in that quest i flashed firmware from here http://forum.xda-developers.com/showpost.php?p=54899772&postcount=1392.
Post that camera and wi-fi stopped working - so I thought may be I screwed up with boot.img and reflashing Viper/ADHD would solve it. While on my way to install Viper I cleaned/wiped data in recovery and hit reboot accidentally which got the phone to stuck in bootloop. I pushed in back in recovery however, since then I have not been able to install either Viper or ADHD. I even tried doing a nandroid back-up from here: http://forum.xda-developers.com/showpost.php?p=54940131&postcount=1419, however nothing brings me past the splash screen.
Off-late (few hours) I am not been able to do a back-up (nandroid) as my recovery throws cant mount sdcard or sdcard1 both. Please help!
Here is the "getvar all" log:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.18.0.0000
(bootloader) version-baseband: 1.19.21331147A1.16G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.10.720.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT469WM02625
(bootloader) imei: xxxx
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B65000
(bootloader) cidnum: HTC__038
(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: 42372cde
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
7mojo said:
In such a big mess! I have the same problem as the OP - same to the last dot. I am on India version of device, and was just trying to update firmware to 4.4.3 and in that quest i flashed firmware from here http://forum.xda-developers.com/showpost.php?p=54899772&postcount=1392.
Post that camera and wi-fi stopped working - so I thought may be I screwed up with boot.img and reflashing Viper/ADHD would solve it. While on my way to install Viper I cleaned/wiped data in recovery and hit reboot accidentally which got the phone to stuck in bootloop. I pushed in back in recovery however, since then I have not been able to install either Viper or ADHD. I even tried doing a nandroid back-up from here: http://forum.xda-developers.com/showpost.php?p=54940131&postcount=1419, however nothing brings me past the splash screen.
Off-late (few hours) I am not been able to do a back-up (nandroid) as my recovery throws cant mount sdcard or sdcard1 both. Please help!
Here is the "getvar all" log:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.18.0.0000
(bootloader) version-baseband: 1.19.21331147A1.16G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.10.720.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT469WM02625
(bootloader) imei: xxxx
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B65000
(bootloader) cidnum: HTC__038
(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: 42372cde
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
Did you re-unlock your phone?
Sent from my HTC One_M8 using Tapatalk
n1234d said:
Did you re-unlock your phone?
Sent from my HTC One_M8 using Tapatalk
Click to expand...
Click to collapse
Yes, I did. Using HTCDev.
At the moment, I would be just happy with someway of going back to the clean slate. Is there a way I could go back to original/stock using ADB/Fastboot as recovery also doesnt seem to work.
Thanks
7mojo said:
Yes, I did. Using HTCDev.
At the moment, I would be just happy with someway of going back to the clean slate. Is there a way I could go back to original/stock using ADB/Fastboot as recovery also doesnt seem to work.
Thanks
Click to expand...
Click to collapse
Bump!
Anyone?
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
After Update bootloop ... please help!
Hello everyone!
So im trying to fix this HTC One M8 since yesterday. My gf tried to install the latest update, after she did the phone went into bootloop.
It was rooted, TWRP recovery installed.
Now i tried yesterday to get i back to stock, but strangely nothing seems to work. I downloaded a couple of ruu ZIP files, none of them worked. Only thing worked was the cyanogenmod but well... she wants her phone back to stock
Every Stock-image i could find was for 4.16.401.10, but the phone says its 4.16.401.13.
Please help me! What exactly must i do in order to get i back to stock?
< waiting for device >
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.25.214500021.06G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.16.401.13
(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__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: f063fb42
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.040s
EDIT
strange thing is, even with android SDK and USB drivers my laptop wont execute an RUU.exe... it fails due to not finding the device even though its connected to the laptop and i can acess the phones memory
Khaira said:
So im trying to fix this HTC One M8 since yesterday. My gf tried to install the latest update, after she did the phone went into bootloop.
It was rooted, TWRP recovery installed.
Click to expand...
Click to collapse
In addition to stock 4.16.401.13 ROM, you will also need stock recovery. Since TWRP is on the phone, OTA will cause the phone to boot over and over looking for stock recovery (and not finding it).
Khaira said:
Now i tried yesterday to get i back to stock, but strangely nothing seems to work. I downloaded a couple of ruu ZIP files, none of them worked.
Click to expand...
Click to collapse
Unless the RUU zip is 4.16.401.13, its going to fail CID or version checks.
Khaira said:
Every Stock-image i could find was for 4.16.401.10, but the phone says its 4.16.401.13.
Click to expand...
Click to collapse
You can get .13 stock nandroid and recovery here: http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
Note this is a nandroid, and not a flashable ROM zip. So restore according to the instruction given in the same thread.
Khaira said:
strange thing is, even with android SDK and USB drivers my laptop wont execute an RUU.exe... it fails due to not finding the device even though its connected to the laptop and i can acess the phones memory
Click to expand...
Click to collapse
Did you try with the phone in fastboot mode?
Any response if you type the command: fastboot devices
Response should be the phone's serial number if you have fastboot connectivity.
What Windows version?
Also, as previously stated, unless the RUU is 4.16.401.13, it will fail anyway.
I got it! Thanks a lot! Seems really like I was too stupid to find the thread u posted
Khaira said:
Seems really like I was too stupid to find the thread u posted
Click to expand...
Click to collapse
Its actually a bit hard to find, as its in Q&A. Deserves to be made sticky.
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).
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.