if there is another thread about this please redirect me as i can't find it.
my problem is i got my 4.16.401.13 update come through a few weeks ago for my htc one m8, and every time i install it i get stuck on the white htc one boot up screen, then have to go back to the previous firmware.
i am not rooted but do have a unlocked boot loader, super cid and s off, I've updated like previously and it hasn't been the problem not sure if this is causing it or not, btw i did use TWRP to restore the previous build.
@iiTz_android
You already have a thread for this topic open here:
http://forum.xda-developers.com/htc-one-m8/help/update-issue-t3200561
Please don't create duplicate threads/posts for the same topic, thread closed.
Related
I performed the update on my brand new HTC Hero and I found out I am stuck in the middle of nowhere with no chance to root until somebody fixes the problem. During my reading, I tried almost everything, and the closest I got was to try and flash an update.zip with the original ROM back onto my device. Yet, at the moment of truth just a stupid white triangle with an exclamation mark appeared instead of the other icon meaning the thingh is working. I can't wait to root for a number of reasons, if I am getting this wrong and there actually IS another solution please help :-((
Ciao!
Vico
Same Boat
Hi mate,
I'm new to the Android OS and just got my hero as well. The first thing I did with it was to update the firmware (as recommended by Orange). Little did I know that this would prevent me from rooting.
I've tried several steps:
1. The One-Step Root Process
2. Flashing an image with the SDK
3. Rolling back to a previous version of the RUU
Nothing works, anyone have any ideas about how to get round this problem or if there's a way to 'un-update' the device, please help!
FYI: I have an HTC Hero on Orange UK running the latest HTC firmware, unrooted http://www.youtube.com/watch?v=9VZHT389eR4
Thanks in advance.
if your phone is NOT CID locked (no clue about orange) you can go here
http://forum.xda-developers.com/showthread.php?t=559622
and download an older RUU (1.76.405.1_R3) and downgrade, then root and upgrade.
problem obviously is that this only works if your phone is not cid locked, or somebody find away to bypass the cid check on the ruu process or finds a way to do this
http://forum.xda-developers.com/showthread.php?t=559806
on updated rom versions......
Thanks
Thanks for the link, I'll take a look into it.
closing this one as currently it can't be solved.
I've started a thread that looks into this here:
http://forum.xda-developers.com/showthread.php?p=4704200
Hi everyone,
Long story short I bricked my phone. After doing more research after the event, I learned that it probably wasn't a good idea yet since there is no stock recovery image posted as of yet. I looked through the posts on this forum to find some information, however so far it has been insufficient.
My question is, is there any update on a Rogers 1.73.631.1 stock recovery.img or does anyone have any information that can help me? My phone used to be stuck on the HTC splash screen however now my phone will only load to bootloader.
Thanks
Lock the bootloader and flash the RUU
to go short start over
Thank you for your reply.
Unfortunately, that list does not have my stock RUU listed as all of those are version 1.26.xxx and my Rogers version is 1.73.xxx. I've tried the disaster recovery thread and I believe because my versions dont match with any RUU listed I can't even load a stock image. Every image I try to load I get a "failed" message, including installing the system.img file from inside of those .exe files.
I desperately need any information anyone has that could help me. I apologize for not posting this in the same thread as the disaster recovery, however I need a minimum of 10 posts to post in that section. Sorry
Am I screwed for a few weeks while I wait and hope someone uploads the proper RUU? I did not get a chance to make a backup as I only got 90% of the way through the rooting process before it crashed and wont load on me. I am using a mac, however I do have access to (and have tried many solutions on) a PC if necessary.
Thanks,
MaidenFan
Hi I am stuck at the same screen
I got the bootloader unlocked and super user installed
I wanted to install Leedroid ROM so downloaded the files and used fasboot to install the version of boot.img that comes with it. Problem is that I forgot to transfer over the rom zip file to the device before doing it so now I'm stuck on this screen. I know, I just got distracted. My fault I know.
(I have successfully rooted my old desire and a wildfire in the past without bother)
I had a nandriod backup done from before flashing boot.img and tried to restore.. It says restore was successful but it it still stuck on this screen. Some help would be mighty appreciated.
EDIT:
The bootloader is now locked again but I think I still have CWM recovery installed however I can't access it anymore. I've tried unlocking the bootloader again but now it says the battery is too low. I keep trying to turn the phone off in fastboot to let it charge but it just starts up again? Any Ideas? Thanks
I've managed to sort out my phone.
For anyone else with the same problem have a look at the following thread to see what I did:
http://forum.xda-developers.com/showthread.php?t=1643483
The Rogers RUU http://www.filefactory.com/file/9qe....09.06_10.81.32.14L_release_254934_signed.zip
---------- Post added at 09:59 AM ---------- Previous post was at 09:58 AM ----------
I'm trying to recover from flashing a Kernel which ultimately sent me in a bootloop.
Hey man, did you end up finding a solution for your phone? I'm in exactly the same situation right now. I'm about to cry.
Why users with Rogers Htc One X posting in the international One X forum ?
For all information on Rogers & AT&T Htc One X are here:
http://forum.xda-developers.com/forumdisplay.php?f=1538
---------- Post added at 11:57 AM ---------- Previous post was at 11:54 AM ----------
achoj said:
Hey man, did you end up finding a solution for your phone? I'm in exactly the same situation right now. I'm about to cry.
Click to expand...
Click to collapse
What is actually your problem, give us more details. Are you on Rogers ?
ckpv5 said:
Why users with Rogers Htc One X posting in the international One X forum ?
For all information on Rogers & AT&T Htc One X are here:
http://forum.xda-developers.com/forumdisplay.php?f=1538
---------- Post added at 11:57 AM ---------- Previous post was at 11:54 AM ----------
What is actually your problem, give us more details. Are you on Rogers ?
Click to expand...
Click to collapse
I finally fixed it. Posted the solution over in the thread that I started. http://forum.xda-developers.com/showthread.php?t=1677034
if there is another thread about this please redirect me as i can't find it.
my problem is i got my 4.16.401.13 update come through a few weeks ago for my htc one m8, and overtime i install it i get stuck on the white htc one boot up screen, then have to go back to the previous firmware.
i am not rooted but do have a unlocked boot loader, super cid and s off, I've updated like previously and it hasn't been the problem not sure if this is causing it or not, btw i did use TWRP to restore the previous build.
Hi,
I'm looking for a stock recovery.img for my HTC One M9. I'm trying to update to Android 7.0 Nougat, but TWRP is preventing me from completing the OTA install. I'm on stock 3.41.651.41 ROM with an unlocked bootloader, TWRP.
Basically I want the whole phone back to stock and able to take the Android 7.0 OTA update has released. I just bought this phone and it has TWRP recovery installed and running stock 3.41.651.41
I tried to update using the RUU exe downloaded from the HTC link above, but i got the error 132 (signature error).
Whenever i try to install the available OTA update it just boots into TWRP and nothing happens. I want the stock recovery image so that i could flash it in TWRP (or any other way) so that i would be able to install the OTA.
at
Info:
Sotware status Official
UNLOCKED
S-OFF
HTC DOWNLOAD MODE
UNLOCKED
(bootloader) product: htc_himaulatt PVT S-OFF
CID: 11111111
LK-1.0.0.0000
RADIO-3 00.C1144084060114
OPENDSP 15-6.1.00522.8994.1026
OS : 3.41.651.41
Nov 2 2016
Please take a look at the ReadMe thread (especially the RUU, the stock recovery and the OTA section). You'll find all needed information and files there.
Sent from my HTC One M9 using XDA Labs
Hello
Thanks for your reply , Please can you help to get the direct link for the tutorial to get a stock recovery on my HTC One m9 and to get the OTA Update.
Thanks
It's not that hard to find. ? I'm sure you'll directly see it if you either visit the General or the Q&A section.
Sent from my HTC One M9 using XDA Labs
Hi
I have tried many Roms updates without any results , Please if you can help me directly i will be soo reconized .
Thanks
Discliamer: Don't get the following message wrong. It neither means that I'm annoyed nor pissed. This is an honest question since I really don't understand it and you're by far not the only person that makes me ask myself the following:
Why does nobody read the ReadMe thread? It's pinned above all normal threads in the General and the Q&A section. In other words it's not hidden at all. Is it due to its naming? If so how do I need to rename it so that people actually read it? Or is it due to the length of its guides? Well, it's not possible to shorten them without deleting important information.
If people would read the ReadMe thread at least 90% of the questions in this section wouldn't get posted since the answers are already covered there*.
* E.g. the RUU section tells you exactly which RUU to use and why RUUs with firmware 4.x (like the ones on HTC's website) can't be used on phones with older firmware versions (version 3.x and below). If people read it they didn't need to "try many roms/RUUS" without success like you did. Then, the OTA section explains that the SuperCID shouldn't be used if you want install OTAs. In addition, the OTA and Stock Recovery sections both explain that simply unrooting and flashing the Stock Recovery isn't enough for being able to install OTAs. And with the explanation of the SKU that can be found above all downloads and with the MID/CID/SKU list in the further reading section you can find out which kind of firmware you're using (branded/unbranded and/or the country/continent that it belongs to). Btw, it's Sprint in your case so be careful with what you're trying to flash on that phone since it's a CDMA device (c.f. the warnings that can be found all over the ReadMe thread).
Hello Back ;
im following this guide :
rename firmware to 0PJAIMG.zip
-copy 0PJAIMG.zip to ext_sd card
-boot into bootloader or download mode
-it will scan your ext_sd card, then ask if you want to start the update
-press volume up & let it do it's thing...
When i press volume up and confirm update i get this error message
HTC ONE M9 fail 22 RU HEADER ERROR
Please help me to solve this issue.
Did you read the post with the most common RUU errors in the ReadMe thread?
Flippy498 said:
Did you read the post with the most common RUU errors in the ReadMe thread?
Click to expand...
Click to collapse
Yes , i have found this guide and i get theses errors
Flippy498 said:
Please take a look at the ReadMe thread (especially the RUU, the stock recovery and the OTA section). You'll find all needed information and files there.
Sent from my HTC One M9 using XDA Labs
Click to expand...
Click to collapse
But aren't the links to all the T-Mobile stock files linked to from the HTC One M9 ReadMe thread are dead, and have been for well over a year (since I got my HTC One M9)?
[Edit: Nevermind, I might be stupid.]
48roses said:
But aren't the links to all the T-Mobile stock files linked to from the HTC One M9 ReadMe thread are dead, and have been for well over a year (since I got my HTC One M9)?
[Edit: Nevermind, I might be stupid.]
Click to expand...
Click to collapse
Are you sure that you're talking about the ReadMe thread? When I checked it the last time all links were working...
Sent from my HTC One M9 using XDA Labs
Try to keep this as short as possible. Got 2 New in box HTC One m9s from ebay.
First one white came with unbranded android 6. It wants to OTA update but always fails. From about info it is a 617 variant. We will lets this ride for a bit...
Second one is the real problem. It came with 5.1 and wanted to OTA update but the update crashed phone, only rebooting to download mode. The only official HTC RUU that worked to restore it was the android 6 ATT Cingular US RUU. It now thinks it is a 502 variant.
I have unlocked the bootloader via htcdev. It reports status: Modified / unlocked / s-on. Not sure why the modified if was the official RUU from HTC download page.
I would like to have a unbranded android 7 as AOSP as possible. But possible due to security KEY changes by htc between versions. I can not get any RUU or zip file on SDcard to install.
I have read and read before posting. The TWRP section here says the info is out of date and could cause a boot loop. The wrong SuperSU can cause a boot loop.
Where/What info can I use to get this phone into shape at this point in time?
Update. I "got some guts" and went ahead with the TWRP install per the READ ME thread and that worked.
I installed a newer (recommended) SuperSU and that boot looped the phone.
So I picked a GSM (ATT) android 7 sense 8 rom and wiped and installed. Almost 20 minutes later the loops stopped and BINGO! working phone.
Installed the SuperSU and that worked.
Current state is unlocked, S-ON any reason to SUNSHINE for S-off at this point?
Do not like the ATT stuff. So the new question is: What is the most AOSP unbranded ROM you might recommend to me?
Thanks!
FYI: I used to hang out here a lot in the HTC fuze days.
The most vanilla rom here would be LOS 15.1 and LOS 16.
The Lineage builds are the offspring of Cyanogenmod.
Both threads are in the original development section, and both are under development.
Take a look.....and happy flashing....g