Early this AM I got an OTA update to 5.0.2 on my M8 HK which also moved the WiFi calling icon over to the right of the notification bar and did away with the persistent notification. The version is 4.25.654.14 and I think there is a new radio (1.09.20.0209). haven't noticed any other changes yet.
HTC has the RUU posted already here: http://www.htc.com/us/support/htc-one-m8-harman-kardon-edition-sprint/news/
awesome! thanks for the heads up:good::good::good::good:
OTA on M8
I also just did a update check and got the OTA and I have a normal M8
I just got this on my M8 HK version. Installing now... Any ideas as to what it contains outside of the mentioned items?
Legobricke said:
I just got this on my M8 HK version. Installing now... Any ideas as to what it contains outside of the mentioned items?
Click to expand...
Click to collapse
Looks like the stock browser icon has changed. I am not sure if that means the app got an update or the stock overlay did. The version I have installed is 7.1.2514183160. I am not sure what's new if the app itself is, though.
There is also a flashlight app that I don't recall seeing before. Hopefully that means they are going to implement the pull down shortcut for it.
Legobricke said:
I just got this on my M8 HK version. Installing now... Any ideas as to what it contains outside of the mentioned items?
Click to expand...
Click to collapse
dopy25 said:
Looks like the stock browser icon has changed. I am not sure if that means the app got an update or the stock overlay did. The version I have installed is 7.1.2514183160. I am not sure what's new if the app itself is, though.
There is also a flashlight app that I don't recall seeing before. Hopefully that means they are going to implement the pull down shortcut for it.
Click to expand...
Click to collapse
Also, vmail app is updated (fixed) and can now be updated without general failure.
Just upgraded my HTC One M8 H/K. We'll see how it goes.
10 minutes ago...
I have S-OFF, stock ROM, booted into FASTBOOT, copied the stock recovery.img from 4.20.651.10_full_firmware.zip using "fastboot flash recovery recovery.img". Booted into the OS, let the OTA install, phone rebooted and is now stuck at the white "htc one powered by android" screen after it shows the yellow Sprint Spark screen and plays the boot up sound/tune.
I have since flashed the full firmware using the SD card method (4.25.651.14_Full_firmware.zip) and the old firmware (4.20.651.10_full_firmware.zip) and still stuck at that screen. I now have it back with the updated firmware via SD card flash (4.25.651.14_Full_firmware.zip).
Did I do something wrong? How can I fix this without having to wipe the phone?
RChris173 said:
I have S-OFF, stock ROM, booted into FASTBOOT, copied the stock recovery.img from 4.20.651.10_full_firmware.zip using "fastboot flash recovery recovery.img". Booted into the OS, let the OTA install, phone rebooted and is now stuck at the white "htc one powered by android" screen after it shows the yellow Sprint Spark screen and plays the boot up sound/tune.
I have since flashed the full firmware using the SD card method (4.25.651.14_Full_firmware.zip) and the old firmware (4.20.651.10_full_firmware.zip) and still stuck at that screen. I now have it back with the updated firmware via SD card flash (4.25.651.14_Full_firmware.zip).
Did I do something wrong? How can I fix this without having to wipe the phone?
Click to expand...
Click to collapse
I was able to flash TWRP recovery with fastboot then I was able to do a nandroid backup and copy the backup from the phone to my computer. I also backed up the internal SD card while in the TWRP recovery.
Ran the latest RUU, which wiped the phone, but then after it booted and ran the initial setup, I put the TWRP back on and then restored the data partition of the nandroid backup, rebooted, and the phone had all of the apps, content, settings, text messages, etc, (as if I didn't loose anything), along with the latest update from the RUU!
No sense 6.5 or 7...?
Jason021680 said:
No sense 6.5 or 7...?
Click to expand...
Click to collapse
Nope. It's probably coming in the 5.1 matience release.
Looks like HTC wants to degrade M8 to sell more M9s. They didn't change much M9 and all HTC lovers don't want to change the device. Hence, HTC making the M8 worse. Never expected such a cheap behaviour from HTC. With the new update batty life sucks, its worse than which I had in HTC One X. HTC how can you cheat your customers for your selfishness!!! checked everything, its Android engine and kernel eatng up all the battery (non rooted factory firmware). Guys please dont update your phone!
Cashreedhar said:
Looks like HTC wants to degrade M8 to sell more M9s. They didn't change much M9 and all HTC lovers don't want to change the device. Hence, HTC making the M8 worse. Never expected such a cheap behaviour from HTC. With the new update batty life sucks, its worse than which I had in HTC One X. HTC how can you cheat your customers for your selfishness!!! checked everything, its Android engine and kernel eatng up all the battery (non rooted factory firmware). Guys please dont update your phone!
Click to expand...
Click to collapse
Must be your apps I'm non rooted as well at the moment and am getting 17hrs with 4hrs screen time on latest update was a little better on KitKat but not a world of a difference
Sent from my 831C using XDA Free mobile app
joshuadub said:
Must be your apps I'm non rooted as well at the moment and am getting 17hrs with 4hrs screen time on latest update was a little better on KitKat but not a world of a difference
Sent from my 831C using XDA Free mobile app
Click to expand...
Click to collapse
Silly talk... Don't you know it's always HTCs fault... Never ever the users.... Jkjk
Honestly, people should think and try to rule out their own issues before coming and laying down a flat out claim like the OTA is bad... Lol
sgt. slaughter said:
Silly talk... Don't you know it's always HTCs fault... Never ever the users.... Jkjk
Honestly, people should think and try to rule out their own issues before coming and laying down a flat out claim like the OTA is bad... Lol
Click to expand...
Click to collapse
joshuadub said:
Must be your apps I'm non rooted as well at the moment and am getting 17hrs with 4hrs screen time on latest update was a little better on KitKat but not a world of a difference
Sent from my 831C using XDA Free mobile app
Click to expand...
Click to collapse
Maybe you are right. But, so long the phone has been stable and the day phone receives the OTA makes it like a charge addicted and battery drains 50% faster than before. Honestly with normal whatsapp, message, phone call and few minutes of facebook access lasts for roughly 5.5 to 6 hours. Let me see formatting the phone.
I noticed that every time I plug my phone into a charger of any sort (wall, car, solar, PC) WiFi turns on.
I am on stock ROM and Kernel rooted, 2.8.6 twrp installed, S-on. 5.0.2 RUU.
Can anyone else rebut or confirm this?
dopy25 said:
I noticed that every time I plug my phone into a charger of any sort (wall, car, solar, PC) WiFi turns on.
I am on stock ROM and Kernel rooted, 2.8.6 twrp installed, S-on. 5.0.2 RUU.
Can anyone else rebut or confirm this?
Click to expand...
Click to collapse
Check automatic connections under mobile network settings
Sent from my 831C using XDA Free mobile app
joshuadub said:
Check automatic connections under mobile network settings
Sent from my 831C using XDA Free mobile app
Click to expand...
Click to collapse
Interestingly enough that worked. For some reason HTC didn't fully restore my settings after the RUU I guess.
What a ridiculous feature...
Thank you.
dopy25 said:
Interestingly enough that worked. For some reason HTC didn't fully restore my settings after the RUU I guess.
What a ridiculous feature...
Thank you.
Click to expand...
Click to collapse
Yup I always uncheck it during first startup then have to go back into settings and uncheck it there again
Sent from my 831C using XDA Free mobile app
Related
So this is just a question as I was browsing through the rom manager program I noticed the HTC Holiday is now listed in their devices.
As I have been researching this phone I believe the phone was referred to as the HTC Holiday
Basically my question is, Is this the device to select or is it referring to an OEM or pre release handset or is it the same as the AT&T Vivid.
I hope that made sense, if not please let me know and I will do my best to make my question more clear.
Kraizk said:
So this is just a question as I was browsing through the rom manager program I noticed the HTC Holiday is now listed in their devices.
As I have been researching this phone I believe the phone was referred to as the HTC Holiday
Basically my question is, Is this the device to select or is it referring to an OEM or pre release handset or is it the same as the AT&T Vivid.
I hope that made sense, if not please let me know and I will do my best to make my question more clear.
Click to expand...
Click to collapse
It is the same phone but I don't know that anyone has used ROM Manager with it. I never used it on any of my other phones because I found it too buggy.
This is the first I have heard of it being listed on there.
pside15 said:
It is the same phone but I don't know that anyone has used ROM Manager with it. I never used it on any of my other phones because I found it too buggy.
This is the first I have heard of it being listed on there.
Click to expand...
Click to collapse
I believe it is added as of today, I personally have loved rom manager though I understand your reasons for not liking it. I just want to confirm it is comparable with the AT&T device before putting it on and flashing what ever version of clockwork recovery it has to offer.... (I bought my phone at an early upgrade price so $350 makes me quite a bit cautious with it....)
I just loaded the recovery labeled holiday and you get stuck at the HTC boot screen. Going back to the recovery from the sticky. A later update might fix it.
Sent from my HTC PH39100 using XDA App
Apatche69 said:
I just loaded the recovery labeled holiday and you get stuck at the HTC boot screen. Going back to the recovery from the sticky. A later update might fix it.
Sent from my HTC PH39100 using XDA App
Click to expand...
Click to collapse
Thank you for trying and letting me know. I do indeed hope it gets fixed, Rom Manager was always just convenient for me.
I told koush about the issues we are having and he is looking into it.
Sent from my HTC PH39100 using xda premium
I updated to the one from ROM manger and I let my phone die. Now I can not get it to charge and the phone will not boot at all. For some reason the charging light comes on for a few seconds and then turns off. Some one please help me lol.
Sent from my ADR6425LVW using XDA App
Neodous said:
I updated to the one from ROM manger and I let my phone die. Now I can not get it to charge and the phone will not boot at all. For some reason the charging light comes on for a few seconds and then turns off. Some one please help me lol.
Sent from my ADR6425LVW using XDA App
Click to expand...
Click to collapse
boot into HBOOT/Fastboot and Fastboot flash the WORKING recovery found here on our forum. the one in ROM manager DOES NOT work right now.....
Pirateghost said:
boot into HBOOT/Fastboot and Fastboot flash the WORKING recovery found here on our forum. the one in ROM manager DOES NOT work right now.....
Click to expand...
Click to collapse
I can't even get in to hboot to do that. I think the battery is dead and like I said I don't think it's charging
Sent from my ADR6425LVW using XDA App
Neodous said:
I can't even get in to hboot to do that. I think the battery is dead and like I said I don't think it's charging
Sent from my ADR6425LVW using XDA App
Click to expand...
Click to collapse
Its probably obvious but your best bet would be to either get a friends phone to charge your battery or buy an external battery charger....
It's working for me
I have the Vivid and downloaded Rom Manager on a whim. Saw the Holiday, selected it. Tried to backup the Att rom, failed - needed cwm installed. Chose option to let RM flash CWM. The version it put on caused RM to puke when attempting to backup. Flashed CWM v5.0.2.7 from PC. Rebooted and mysteriously lost root. Had to pull the battery a few times during all this.
Rerooted using HTCSupertool, and RM has worked just fine since.
So some flakes, but when ironed out seems OK.
I did a nand backup and a restore just to be sure I could get back and both operations completed without error.
Waiting to get full charge on the phone then will flash first custom rom.
jherbold said:
I have the Vivid and downloaded Rom Manager on a whim. Saw the Holiday, selected it. Tried to backup the Att rom, failed - needed cwm installed. Chose option to let RM flash CWM. The version it put on caused RM to puke when attempting to backup. Flashed CWM v5.0.2.7 from PC. Rebooted and mysteriously lost root. Had to pull the battery a few times during all this.
Rerooted using HTCSupertool, and RM has worked just fine since.
So some flakes, but when ironed out seems OK.
I did a nand backup and a restore just to be sure I could get back and both operations completed without error.
Waiting to get full charge on the phone then will flash first custom rom.
Click to expand...
Click to collapse
can you open ROM manager, click on Download ROM and see if anything shows up?
Yep
Pirateghost
Cerberus
Superuser
ClockworkMod
Google Apps
What do I get if I select your entry?
jherbold said:
Pirateghost
Cerberus
Superuser
ClockworkMod
Google Apps
What do I get if I select your entry?
Click to expand...
Click to collapse
awesome....
click it and see
Oh
I was thinking of a prize for being first
Edit: Too late. Five downloads already.
On a side note, I'm going to try that rom with the Amaze camera first. Just to see if the HORRIBLE audio on videos is impacted.
jherbold said:
I was thinking of a prize for being first
Click to expand...
Click to collapse
lol.
it is a prize. hahaha
So i'm basically a total noob when it comes to this kind of thing.
I recently rooted my new HTC ONE (International) using a method i found on htconeroot.com
After that the phone could not read the SD card. Every time i open storage in the settings menu it closes.
The phone also would reboot at random moments.
I tried to fix it using some other methods and messed it up. I deleted the original OS and i cant access the backups i made because i switched recoveries from TWRP to CWM. Even when i switched back to TWRP, i couldn't find the backups.
I tried installing two roms (Android Revolution and Maximus) but when i did they would not boot completely and would be stuck on the boot logo.
I cannot flash stock RUU because it is not out yet (1.29.401.12)
I tried to use the Nandroid method i found on this link:
http://forum.xda-developers.com/showthread.php?t=2267435
But the installation aborted for some reason and would not work.
PLEASE can anyone help me find a solution or show me how i make the nandroid backup method work?
Andys1994 said:
So i'm basically a total noob when it comes to this kind of thing.
I recently rooted my new HTC ONE (International) using a method i found on htconeroot.com
After that the phone could not read the SD card. Every time i open storage in the settings menu it closes.
The phone also would reboot at random moments.
I tried to fix it using some other methods and messed it up. I deleted the original OS and i cant access the backups i made because i switched recoveries from TWRP to CWM. Even when i switched back to TWRP, i couldn't find the backups.
I tried installing two roms (Android Revolution and Maximus) but when i did they would not boot completely and would be stuck on the boot logo.
I cannot flash stock RUU because it is not out yet (1.29.401.12)
I tried to use the Nandroid method i found on this link:
http://forum.xda-developers.com/showthread.php?t=2267435
But the installation aborted for some reason and would not work.
PLEASE can anyone help me find a solution or show me how i make the nandroid backup method work?
Click to expand...
Click to collapse
Wait so you cannot ruu back did you oem relock and then try the ruu? Sorry I'm on a US variant and not a international one
Sent from my HTCONE using Tapatalk 2
Could you send us a pic of your bootloader? That way we can determine exartcly what state your phone is in.
Also, I just used HTCOneRoot two days ago without a hitch (AT&T variant). The first boot takes a good 2 - 5 minutes so maybe you just didn't wait long enough.
Sent from my HTC One using xda app-developers app
Lekerstein said:
Could you send us a pic of your bootloader? That way we can determine exartcly what state your phone is in.
Also, I just used HTCOneRoot two days ago without a hitch (AT&T variant). The first boot takes a good 2 - 5 minutes so maybe you just didn't wait long enough.
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Ok so i had a friend of mine who's a tech-wizz when it comes to this kind of thing help me out. He explained pretty much everything but i still have a problem.
I basically erased the system by accident (playing with TWRP), so i flashed CWM and restored my phone using a nandroid backup for version 1.29.401.12, which was the original version the phone came in.
The backup worked although it still has the same bugs that i had when i first rooted the damn thing.
Basically, some apps would just restart themselves right when i open them, such as google chrome. They would eventually open after a couple more tries. The phone is a bit laggy, and would also reboot at random moments, which i think normally happen when i do something with the phone such as install a new app or simply post a facebook status. Is it possible that i might've erased an important system file? Cuz the backup should've restored all missing system and data files.
Oh and i also couldn't take a photo of the bootloader because my camera has the same image taking capabilities of a potato.
So i'll just copy down everything on there.
*** TAMPERED ***
*** UNLOCKED ***
M7_U PVT SHIP S-ON RH
HBOOT-1.44.0000
RADIO-4A.14.3250.13
OpenDSP-v26.120.274.0202
eMMC-boot
May 4 2013, 16:21:26:-1
I am running CWM-Touch v6.0.3.1 which was the recovery i found within the nandroid backup
If there's anymore information i can supply that would help please let me know.
Alex1123 said:
Wait so you cannot ruu back did you oem relock and then try the ruu? Sorry I'm on a US variant and not a international one
Sent from my HTCONE using Tapatalk 2
Click to expand...
Click to collapse
I looked everywhere but all the threads i found said that the RUU's for the 1.29 base are not out yet so i had to use the nandroid backup instead.
This phone is killing me
I tried re-rooting and giving the phone 10 mins to stable.
I tried flashing AndroidRevolution rom
I tried several nandroid backups, including the software version that i was initially on (1.29.401.12)
Just now i flashed an odexed rom version 2.17.401.1 and it still keeps on restarting.
I'm starting to believe this phone is fake.
Are flashing the boot.IMG through fastboot after flashing the ROM ?
Sent from my One XL using xda app-developers app
Andys1994 said:
This phone is killing me
I tried re-rooting and giving the phone 10 mins to stable.
I tried flashing AndroidRevolution rom
I tried several nandroid backups, including the software version that i was initially on (1.29.401.12)
Just now i flashed an odexed rom version 2.17.401.1 and it still keeps on restarting.
I'm starting to believe this phone is fake.
Click to expand...
Click to collapse
You may try doing a data factory reset in settings/backup and restore/reset the phone.
henslo said:
Are flashing the boot.IMG through fastboot after flashing the ROM ?
Sent from my One XL using xda app-developers app
Click to expand...
Click to collapse
Not really, i install the rom using the recovery. Is there a way to flash it using fastboot?
Andys1994 said:
This phone is killing me
I tried re-rooting and giving the phone 10 mins to stable.
I tried flashing AndroidRevolution rom
I tried several nandroid backups, including the software version that i was initially on (1.29.401.12)
Just now i flashed an odexed rom version 2.17.401.1 and it still keeps on restarting.
I'm starting to believe this phone is fake.
Click to expand...
Click to collapse
Did it look fake?
MacHackz said:
Did it look fake?
Click to expand...
Click to collapse
No it doesn't, but normally rooting the device shouldn't really do this, right?
Cause i've looked everywhere and no one seems to be having this problem with the HTC ONE.
Is there a way to tell if it's fake or not?
gee2012 said:
You may try doing a data factory reset in settings/backup and restore/reset the phone.
Click to expand...
Click to collapse
Tried that, still keeps restarting
Andys1994 said:
No it doesn't, but normally rooting the device shouldn't really do this, right?
Cause i've looked everywhere and no one seems to be having this problem with the HTC ONE.
Is there a way to tell if it's fake or not?
Click to expand...
Click to collapse
Doubt it will be fake, you'd have to be pretty new to not spot a fake one
MacHackz said:
Doubt it will be fake, you'd have to be pretty new to not spot a fake one
Click to expand...
Click to collapse
Ok, so that means it something i did, which can hopefully be fixed
Okay, so before i go ahead and post this, I'm well aware of where i should be posting it, but i'm apparently a new member and therefore cannot post in the HTC One Development section.
I'm using the T-Mobile HTC One (M7_ul) and i wanted to convert into the Google Play Edition. I took the OTA update from t-mobile that bumped me up to 1.27.531.11, and it took me about an hour to realize that t-mobile decided to block all ways to s-off with that update, and that i would somehow have to get back to .8. My bootloader is unlocked, with TWRP 2.5.0.0. and root. I flashed the Stock Sense 5 1.27.531.8 rom (although rather buggy, i keep getting errors with the phone program abruptly stopping, but its not an issue seeing as im not staying with this rom). Im under the assumption that if i did that, as long as my hboot was still 1.44, i'd be able to use Moonshine or revone to s-off. I tried both, and neither of them were a go. I keep getting an Error-2 with revone, and moonshine gets to Moonshining (10) and then says Error: dont drink and shine. Now i'm not a complete noob when it comes to unlocking and rooting HTC devices, but ive never decided to take that extra step to s-off. everytime i think i have it right, moonshine and revone give me errors. would someone please tell me what im doing wrong, or at least point me in the right direction? please?
Your phone was updated to .11 it's more than just the Rom that was updated, you just gotta wait. I do too my phone came with .11.
Sent from my HTC One using Tapatalk 4
grim489 said:
Your phone was updated to .11 it's more than just the Rom that was updated, you just gotta wait. I do too my phone came with .11.
Sent from my HTC One using Tapatalk 4
Click to expand...
Click to collapse
I see. so if i'm understanding you correctly, I can't just flash the .8 rom and do s-off, T-Mobile patched it and im screwed?
Yeah that's it, I've read that one person has got it to work but idk if they actually took the ota or not. There would be a workaround if we had an RUU for .7 or .8 but we don't. So I guess we just gotta wait for someone to figure something out.
Sent from my HTC One using Tapatalk 4
Oh god I hope that day comes soon. I'm so tired of this menu bar....I'm tired of Sense 5 period. I want my stock android with it's's back
Sent from my HTC One using xda app-developers app
xeyesofthousandx said:
Okay, so before i go ahead and post this, I'm well aware of where i should be posting it, but i'm apparently a new member and therefore cannot post in the HTC One Development section.
Click to expand...
Click to collapse
that's why you can't, you should not have posted in dev section (and not here either but in Q&A) anyway did you try this:
http://forum.xda-developers.com/showthread.php?t=2398717
You could use HTC dev unlock until then though, just reset everything when s-off does come? That's what I've done and I'll just use s-off to make it look like nothing when (hopefully) it comes around again
Sent from my HTC One using Tapatalk 4
This post seems to have eluded me. It doesn't matter at this point, because there's no link in the post for a T-Mobile RUU
Sent from my HTC One using xda app-developers app
I'm unlocked already, I'd just really rather convert completely to the GPE using the mid/cid change method, so if HTC decides to upgrade the One to KLP when its released, I won't have to go back to stock Sense 5 to get the OTA
Sent from my HTC One using xda app-developers app
xeyesofthousandx said:
This post seems to have eluded me. It doesn't matter at this point, because there's no link in the post for a T-Mobile RUU
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
ask (in the thread not via pm)the author of that guide if flasking a firmware package + stock rom would do and what other steps you would need to take
you can find the firmware packages here: http://forum.xda-developers.com/showthread.php?t=2355814
It says in the op that the firmware zips are unsigned, which means I would have to be S-off to flash them.
Sent from my HTC One using xda app-developers app
xeyesofthousandx said:
It says in the op that the firmware zips are unsigned, which means I would have to be S-off to flash them.
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
those firmwares in that thread are official and signed, so that's why I think you could have a chance of getting it working
Ok I see the signed link now. I have a job interview but when I get back I'll give it a shot and post my results. Fingers crossed!
Sent from my HTC One using xda app-developers app
xeyesofthousandx said:
Ok I see the signed link now. I have a job interview but when I get back I'll give it a shot and post my results. Fingers crossed!
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Good luck with the interview
A gentleman, thank you sir!!!
Sent from my HTC One using xda app-developers app
It looks like only the .11 firmware is signed :/
Sent from my HTC One using Tapatalk 4
N/m
grim489 said:
It looks like only the .11 firmware is signed :/
Sent from my HTC One using Tapatalk 4
Click to expand...
Click to collapse
so updating all you fellas, no method i tried worked I managed to find a stable rom for 1.27.531.7. my thought process was to flash to .7, unroot, reflash stock recovery, relock the bootloader, and try to install the .8 OTA. Didnt work. I tried to bypass, got the OTA .zip from my storage, rebootRUU and flash the OTA firmware. Didnt work either. The progress bar hung at about 75%(i tried this 6 times, same result). so i unlocked the bootloader again, reflashed twrp 2.5.0.0 and had planned on just restoring the nan i made. I didnt realize that when you flash a RUU, even if it doesnt finish, it still formats your /sd/data, so backup was gone, by this point i had already done the wipe expecting it to be there, so through all this, i ended up stuck in twrp with no OS, and for some reason the ADB sideload feature didnt work so i couldnt push a .zip to the phone. after an hour and a half of frantically searching, i just decided to run the .11 official RUU, so after 14 hours, im back to where i started. Wayyyyy more trouble than its worth. just gonna flash a stock rooted 4.3 GPE rom, and when HTC and T-Mobile decide to stop screwing around and push the 4.2.2 update, ill just reflash the RUU.
Thanks for all the help, gents.
xeyesofthousandx said:
so updating all you fellas, no method i tried worked I managed to find a stable rom for 1.27.531.7. my thought process was to flash to .7, unroot, reflash stock recovery, relock the bootloader, and try to install the .8 OTA. Didnt work. I tried to bypass, got the OTA .zip from my storage, rebootRUU and flash the OTA firmware. Didnt work either. The progress bar hung at about 75%(i tried this 6 times, same result). so i unlocked the bootloader again, reflashed twrp 2.5.0.0 and had planned on just restoring the nan i made. I didnt realize that when you flash a RUU, even if it doesnt finish, it still formats your /sd/data, so backup was gone, by this point i had already done the wipe expecting it to be there, so through all this, i ended up stuck in twrp with no OS, and for some reason the ADB sideload feature didnt work so i couldnt push a .zip to the phone. after an hour and a half of frantically searching, i just decided to run the .11 official RUU, so after 14 hours, im back to where i started. Wayyyyy more trouble than its worth. just gonna flash a stock rooted 4.3 GPE rom, and when HTC and T-Mobile decide to stop screwing around and push the 4.2.2 update, ill just reflash the RUU.
Thanks for all the help, gents.
Click to expand...
Click to collapse
Dude, you were doing some serious stuff to your phone, you have to slow down a little. I recommend reading as much as you can before you attempt anything you just did. The reason I am saying this is that, when flashing firmware, the progress bar always sticks at about 75%, that is normal, then you reboot and it finishes the install. You probably got that firmware from the OTA you're talking about installed and didn't know it.
dgtiii said:
Dude, you were doing some serious stuff to your phone, you have to slow down a little. I recommend reading as much as you can before you attempt anything you just did. The reason I am saying this is that, when flashing firmware, the progress bar always sticks at about 75%, that is normal, then you reboot and it finishes the install. You probably got that firmware from the OTA you're talking about installed and didn't know it.
Click to expand...
Click to collapse
I let it reboot completely about 5 times, and checked the fw version each time. i promise you i didnt get it. I know the bar hanging on the OTA is normal, i had plenty of learning experience with that on the One V
As the title says, I need to hard brick this HTC One. I offer rooting, repairing and factory unlocking as a part time job and had this customer bring me this phone which he tried rooting himself and now regardless what rom is flashed the phone just reboots and doesn't pickup a cellular connection. I tried to reflash it myself and even tried to flash the ruu but gave up after so many fails and due to the phone just rebooting can't s-off so now the customer wants me to hard brick his phone so that when it boots up it doesn't show the prompt on the splash screen the phone been tampered with so he can just pay the insurance deductible and get a new one. Not sure how to go about Hard bricking since I never hard bricked a HTC device before only a Samsung device. Any help would be appreciated on how to hard brick it or fix it if possible.
I think you could probably try flashing something from a different phone. I hear that screws things up nice and good.
Sent from my HTCONE using xda app-developers app
that would be fraudulent first of all
secondly I assume you are still able to get into recovery if so then the device should be fine
verify that the rom that your customer downloaded was not downloaded from the international htc one, verify if the download was not corrupted.
post what steps you have followed trying to ruu, really this forum is all about helping but at the same time everyone should be aware of the dangers but most of all own up to their own actions if they end up with a brick.
Sent from my HTCONE using Tapatalk 2
Moved to proper section, please read and respect the rules before posting.
Thanks,
im0rtalz said:
that would be fraudulent first of all
secondly I assume you are still able to get into recovery if so then the device should be fine
verify that the rom that your customer downloaded was not downloaded from the international htc one, verify if the download was not corrupted.
post what steps you have followed trying to ruu, really this forum is all about helping but at the same time everyone should be aware of the dangers but most of all own up to their own actions if they end up with a brick.
Sent from my HTCONE using Tapatalk 2
Click to expand...
Click to collapse
When the customer brought me the phone he had installed ViperOne for the Sprint version which what this phone is, what he had installed before that i wouldnt know. What I have tried is flashed the stock firmware thru twrp and cwm and being that its s-on i have to flash the boot image thru fastboot but still reboots and no cellular service. i reflashed the stock recovery and relocked the bootloader and attempted to flash the ruu zip thru the fastboot oem rebootruu and fastboot flash zip rom.zip command and i get a error. I tried to get s-off so that i flash the ruu this way but due to the phone rebooting every few seconds it won't allow Moonshine s-off to finish which ends up giving me a error due to the phone rebooting. So what else can i do to fix this phone or hard brick to where it wont even bootup so an insuarnce claim can be done.
Since it is mentioned that the phone does not get celluar connection, I am assuming that the phone still boots. So when does it actually start rebooting itself?
There are two kernels in the ViperOne thread
- Flashable Kernel Only Zip 1.29.651.10 (LATEST)
- Flashable Kernel Only Zip 1.29.651.7
You do not need to go into fastboot to flash the kernel, unlike previous HTC phones unlocked bootloader on the HTC One allows for kernel/bootimage to be flash from recovery.
I'm just a bit puzzled as to how far the phone boots up too before it reset?
Have you tried a ##786# in dialer and then menu / reset?
Sent from my HTCONE using xda app-developers app
im0rtalz said:
Since it is mentioned that the phone does not get celluar connection, I am assuming that the phone still boots. So when does it actually start rebooting itself?
There are two kernels in the ViperOne thread
- Flashable Kernel Only Zip 1.29.651.10 (LATEST)
- Flashable Kernel Only Zip 1.29.651.7
You do not need to go into fastboot to flash the kernel, unlike previous HTC phones unlocked bootloader on the HTC One allows for kernel/bootimage to be flash from recovery.
I'm just a bit puzzled as to how far the phone boots up too before it reset?
Click to expand...
Click to collapse
After factory reset it will alow you to go thru the setup and then ill get a black screen with just the notification visible and after about 5 minutes the phone will reboot after that it will boot on that same black screen with the notification visible and then after about 2 minutes the phone will reboot and keep doing that until i boot into the bootloader and select power off. does the same regardless if it stock based or aosp based doesn't matter.
Konfuzion said:
Have you tried a ##786# in dialer and then menu / reset?
Sent from my HTCONE using xda app-developers app
Click to expand...
Click to collapse
Cant since i cant get access to the dialer since it never loads.
Is it 1.31 if so have you tried this method to flash the RUU? http://forum.xda-developers.com/showthread.php?p=44243635
It sounds like your customer flashed a non Sprint Rom prior to flashing ViperRom.
Sent from my HTCONE using xda app-developers app
Why not just take it to the Sprint store? Sounds like the phone itself is defective. There was an article on here that Sprint stores frown on root, but they run the RUU and take it back to stock and if it still acts up replaces it. The phone is less than 6 months old, and unless it is beat to heck should be under warrantee services from Sprint.
Plus that would save $150 in deductibles if the phone is defective.
weidnerj said:
Why not just take it to the Sprint store? Sounds like the phone itself is defective. There was an article on here that Sprint stores frown on root, but they run the RUU and take it back to stock and if it still acts up replaces it. The phone is less than 6 months old, and unless it is beat to heck should be under warrantee services from Sprint.
Plus that would save $150 in deductibles if the phone is defective.
Click to expand...
Click to collapse
Sounds to me like they flashed a GSM Rom before flashing a CDMA one.
Sent from my HTCONE using xda app-developers app
Konfuzion said:
Is it 1.31 if so have you tried this method to flash the RUU? http://forum.xda-developers.com/showthread.php?p=44243635
It sounds like your customer flashed a non Sprint Rom prior to flashing ViperRom.
Sent from my HTCONE using xda app-developers app
Click to expand...
Click to collapse
Yes it's 1.31 and I rooted this phone on this firmware without issues so not sure what the hell the dude did. I haven't tried this and will try it out but I found out that he doesn't have insurance with Sprint but with Best Buy so not sure how that will work as another customer of mine told me he's taken phones for exchange and the Best Buy rep don't even look at the phone and just issue out a replacement so he's going to try this. But i'll keep your link bookmarked just in case I come across this again. Thanks to everyone that helped.
asj2583 said:
Yes it's 1.31 and I rooted this phone on this firmware without issues so not sure what the hell the dude did. I haven't tried this and will try it out but I found out that he doesn't have insurance with Sprint but with Best Buy so not sure how that will work as another customer of mine told me he's taken phonse for exchange and the Best Buy rep don't even look at the phone and just issue out a replacement so he's going to try this. But i'll keep your link bookmarked just in case I come across this. Thank to everyone that helped.
Click to expand...
Click to collapse
Based on that info this method will fix the phone unless it is in fact a hardware issue, which I highly doubt.
Sent from my HTCONE using xda app-developers app
My thought (having always bought my phones at Sprint) is that Sprint stores have service support personal at some of their stores that also can do basic repair services. Even if the phone was bought at Best Buy, the service provider is still Sprint and they should be able to run "tests" on the phone.
HTC One should also have a one year warrantee, and since the phone only has been 6 months old, should be covered unless abused.
So shouldn't hurt to take it to the Sprint store. Sprint is all about customer service. Worth the chance to get it fixed or replaced verses having to pay for insurance, etc. But you don't know until you try and worse they can do is tell you no...
what is happening here sounds very similar to what happen to this user http://forum.xda-developers.com/showthread.php?p=45086289
read thru it and see if this is the same problem, also what error do you get when trying the ruu
Sent from my HTCONE using Tapatalk 2
Hey guys I have a Moto bought Nexus 6, running on T-Mobile network Sim card and all. Currently the 6 is on 5.0.1 and has been asking me to bump up to 5.1. My phone is stock and rooted. As we all know I can't use the OTA as a result.
I'm here bugging you all because I know there are different builds for the Nexus 6, and they seem carrier specific. So I went and hunted down an M build which supposedly is for Tmo, as we have some specific tweaking.
I downloaded the LMY47M build and I am currently on the LRX22C 5.0.1 build. What I would like to know is it okay for me to go into TWRP and flash the download? Like the way a person would flash a nightly of CM? Is it the same process? If not what do I gotta do?
(On a bus ride so would be nice to have it update while I'm still riding)
Sent from my Nexus 6 using XDA Free mobile app
If the "download" is an OTA, it cannot be flashed from a custom recovery. ...and it will still fail because you're rooted.
Nope I downloaded online and it's sitting in a download folder now
Sent from my Nexus 6 using XDA Free mobile app
dynamo147 said:
Nope I downloaded online and it's sitting in a download folder now
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
Let me rephrase, if the file you have downloaded is the same file you would get as an ota, then what i said before.
Very likely it's the same but I can't say for sure.,. So where does that leave me in terms of options?
Sent from my Nexus 6 using XDA Free mobile app
dynamo147 said:
Very likely it's the same but I can't say for sure.,. So where does that leave me in terms of options?
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
I don't know much about this "M" build and what version it is supposed to flash from. What I do know is there is no full factory image available.
Of everything else is stock on your phone (Including radio) I think the best action would be:
- download the factory image for the version you are on now.
- extract it and fastboot flash the stock recovery and system.img
- do NOT lock your bootloader
Then you should be able to accept the ota or side load it from stock recovery.
Mmm will try this when I get home thanks! Will be back to update Folks!
Also, will flashing the stock image and recovery wipe any of my data?
Sent from my Nexus 6 using XDA Free mobile app
dynamo147 said:
Mmm will try this when I get home thanks! Will be back to update Folks!
Also, will flashing the stock image and recovery wipe any of my data?
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
Not if you extract it an flash only the system.img
Its flashing the userdata image that wipes data
Yes. I would like to know how to do this also. Is there a difference in flashing the D or E version of 5.1 and then flashing a custom ROM that is built from T-Mobile's update?
Or is there carrier specifics in the different Factory Images?
downloading the img right now, when i get back I will make a little step by step for anyone else curious
dynamo147 said:
downloading the img right now, when i get back I will make a little step by step for anyone else curious
Click to expand...
Click to collapse
Its only 3 steps and I already Gave them earlier in the thread
BossJ said:
Yes. I would like to know how to do this also. Is there a difference in flashing the D or E version of 5.1 and then flashing a custom ROM that is built from T-Mobile's update?
Or is there carrier specifics in the different Factory Images?
Click to expand...
Click to collapse
In my mind in its the radio. you want the radio that comes with the T Mobile version. (if you are on t-mobile obviously) what you flash on top of it for system doesn't matter as long as it supports the radio and is version 5 .1. And as long as what you're flashing doesn't include the radio you are good to go.
So for me as long as I keep the E radio for Verizon I can flash D through M it kind of doesn't matter.
Sent from my Google N6 on VZ
rootSU said:
Its only 3 steps and I already Gave them earlier in the thread
Click to expand...
Click to collapse
Thanks for your replies here. I'm in the same boat as the OP, and have one follow-up question to this thread, if you or anyone could answer --
After doing the steps you mentioned previously -- specifically sideloading/accepting the OTA update, will the bootloader remain unlocked? I'd like to re-root afterwards and keep the user data, though I was under the impression it would actually re-lock the bootloader.
Thanks for any info!
vormund said:
Thanks for your replies here. I'm in the same boat as the OP, and have one follow-up question to this thread, if you or anyone could answer --
After doing the steps you mentioned previously -- specifically sideloading/accepting the OTA update, will the bootloader remain unlocked? I'd like to re-root afterwards and keep the user data, though I was under the impression it would actually re-lock the bootloader.
Thanks for any info!
Click to expand...
Click to collapse
Yes, your bootloader will remain unlocked.
dynamo147 said:
Hey guys I have a Moto bought Nexus 6, running on T-Mobile network Sim card and all. Currently the 6 is on 5.0.1 and has been asking me to bump up to 5.1. My phone is stock and rooted. As we all know I can't use the OTA as a result.
Click to expand...
Click to collapse
Did you ever get this going? I know I procrastinated a bit due to the "unknowns", but finally made it happen (bug off, TMo "5.1 Available" notification!). I ran into a lot of oddities between my phone and computer (running Windows 7) like the phone being an unrecognized device when working with adb sideloads... I ultimately opened the Device Manager and forced the composite ADB driver through for each instance. For me, the rough flow was, starting out with stock but unlocked and rooted,
* flashed stock LRX22C system and recovery images
* used adb to sideload the T-Mobile LMY47M official update
* flashed TWRP
* used adb to sideload SuperSU
* and of course, cleared the dalvik/cache and rebooted
All data in-tact, and my LEDs are still functional (the LEDs are actually the key reason I have it rooted right now... it's insanely stupid that Google blocks these built-in LEDs from being used by those that want them!).
Anyways, if you run into any of those issues, happy to help!
Evolution_Freak said:
Yes, your bootloader will remain unlocked.
Click to expand...
Click to collapse
Thank you...exactly what I needed to know!
Ah yeah I did actually, and I like you, had problems getting the phone recognized with the ADB, also windows 7, which prevented me from slide loading like I wanted to, but nevertheless got all the updates pushed through thnx though!
Sent from my Nexus 6 using XDA Free mobile app