[Q] Cannot update to 4.3 - One (M7) Q&A, Help & Troubleshooting

Hi,
Just a few days ago, HTC has made available the 4.3 update of HTC One developer. And I am having problem with it. I cannot update.
To start with, I actually had a custom recovery. I performed the two previous update by flashing back and forth the custom and stock recovery and just went with OTA update. This time, I am doing the same thing and it doesn't work despite many attempts. I then downloaded the .zip files from HTC dev site with two hopes.
1. I think I might have the problem with the custom recovery. I thought of downloading the zip file and upzipping it for the stock recovery. Sadly, I cannot unzip what I downloaded on HTC dev. It always appear as the archive is corrupted.
2. I then downloaded the PN07IMG_M7_UL_JB43_SENSE50_MR_BrightstarUS_WWE_3.22.1540.1 hoping to perform manual update using CWM touch. Sadly, again, CWM cannot extract/read the zip and the return value was BAD.
I am so frustrated right now having no idea what is wrong with my phone. :crying:
Appreciate your help!

Easiest thing is to download the full RUU that's on HTCDev now (the EXE one), connect the phone in fastboot mode and then run the RUU. If you have a DE phone it'll just update and you're good to go. It'll overwrite the customer recovery and reset the phone to 100% stock so back up your data first as it WILL delete it all!
You cannot unzip the RUU ZIP on HTCDev as HTC have encrypted them but there are ways around it (I don't know how tho!)
If you don't have a DE phone then you'll need S-OFF to flash the RUU

Here are the steps for you to do. Follow link. Since you have CWRM you are rooted.. let me know if you have any questions..
http://forum.xda-developers.com/showthread.php?t=2460035
Sent from my HTC One using xda premium

Related

HTC Vivid Stuck on HTC logo

Ok I tried using this All-in-one software to flash a kernel and it sent it over and wrote it but its stuck on the HTC logo, and yes I can boot into HBOOT and recovery, is there anyway I can restore straight back to everything factory?
Sounds like the wrong kernel for the Rom was flashed.
What rom/kernel were you trying to flash ?
I was trying to flash the holiradar Final rom, but it said I needed the newest kernel so, I didnt flash the rom yet but I went on the AIO program and flashed the holicakes 2.6.35.14 and when it wouldnt boot up after that...
So what do you suggest I do?
So you are going to need to flash the kernel that goes with the holicakes 2.6.35.14 rom.
Should be on the same site.
You can user CMD to fastboot flash boot boot.img and then the rom will boot.
From what I can tell on the rom page there is a kernel download section.
---------------------------------
Looks like he is instructing you to flash the kernel a different way than I have listed above, but both ways will work.
Riomaru said:
Ok I tried using this All-in-one software to flash a kernel and it sent it over and wrote it but its stuck on the HTC logo, and yes I can boot into HBOOT and recovery, is there anyway I can restore straight back to everything factory?
Click to expand...
Click to collapse
DO NOT TRY, FACTORY RESET WILL DO ABSOLUTELY NOTHING AND MIGHT ACTUALLY MAKE THINGS WORSE.
With that out of the way, don't use the AIO software, use fastboot.exe and flash a boot.img to fix the issue.
Riomaru said:
I was trying to flash the holiradar Final rom, but it said I needed the newest kernel so, I didnt flash the rom yet but I went on the AIO program and flashed the holicakes 2.6.35.14 and when it wouldnt boot up after that...
So what do you suggest I do?
Click to expand...
Click to collapse
No need to worry, you haven't had enough experience to know that it is normal. It is normal for the phone to not boot into the rom when the kernel doesn't match. since you have successfully flashed the kernel, you now need to boot into recovery (which I hope you have it installed at this point, if you have not, read how to do it and flash recovery) once in recovery, proceed to flash the HoliRaider rom and you'll be good to go.
in the same boat
Hi All,
I have a similar problem flashing the Kernal with the vivid toolkit (V 2.1) on my Vivid. I think there should be a big warning for that box. I tried flashing the Holicakes Kernal, and flashed it twice as it tells you to, and ended up with the white HTC screen. Then tried flashing back to the stock rom, more than twice now with no luck. In desperation I tried installing the RUU update 3.26.502.56_US but I now get error 150, which indicates a rom mismatch, and yet it is the update for the phone direct from htc.
What should I try next to get past the white screen?
Thanks
newbroman said:
Hi All,
I have a similar problem flashing the Kernal with the vivid toolkit (V 2.1) on my Vivid. I think there should be a big warning for that box. I tried flashing the Holicakes Kernal, and flashed it twice as it tells you to, and ended up with the white HTC screen. Then tried flashing back to the stock rom, more than twice now with no luck. In desperation I tried installing the RUU update 3.26.502.56_US but I now get error 150, which indicates a rom mismatch, and yet it is the update for the phone direct from htc.
What should I try next to get past the white screen?
Thanks
Click to expand...
Click to collapse
Did you install a recovery?
Also, it was not a good idea to try and install all different types of things once you thought it was messed up. Anytime you think you may have messed up, stop right then, read about the issue, and if you can't find the solution, ask a question. I think you can get out of this but some people aren't that fortunate.
vivid white screen
Thanks for the advice I will press on and do some more reading,
I can still get to CWM recovery and have tried restoring the backup image I made, with the same result.
During the kernal flashing process:-
- is the HTC dev lock supposed to be on or off? It is off and unlocked at the moment,
- is double flashing the kernal what is meant by the instruction 'if this is the first time you flash a kernal, make sure to reflash it', or as is suggested in esloan's post on this thread your supposed to flash a matching rom instead?
Thanks
You did the right thing by flashing the kernel twice. That is what those directions said. After you flash the kernel twice the next step would have been to flash a rom. I believe it is better to use the fast boot commands for doing this entire process. It sounds like you are still on the holicakes kernel.
What recovery do you have? 5.5.4 or WCX Recovery? You will have better results with WCX Recovery. Also watch this video:
http://www.youtube.com/watch?v=xEWa_lUd2bY&feature=youtu.be
That is by randog. He did a great video and he shows you how to install everything without a program. Do you have the holiradier rom on your phone?
I was on the CWM recovery.
Thanks for the link to Randog's video, I now have a working phone again.
The major difficulties I had was finding wildchild's webpage with the links shown on the video, mainly because searching for wildchild illuminati took me to a forum with no links to any thing vivid, until you register.
I was also a little worried that I wasn't getting ICS in the ATT_ generic rom, but I needn't have. The key seemed to be locking the phone again and running wildchild's PH39IMG.zip. After that the security warning on the Hboot screen disappeared.
I almost messed the rom flashing part. Randog's vivid does this really quickly, my phone was a good 3 minutes behind and the progress bar was stuck around the 10% way after his phone had finished.
Like Randog says in the video follow the steps and you wont brick and you'll have a working phone.
Thanks megatronisabeast
Glad you got it. Sorry, forgot to give out the link.
Sent from my HTC PH39100 using XDA
Afraid to screw up any further
Htc vivid. 1.2dualcore.ICS.*
unlocked boot loader.
Used all in one vivid *toolkit 2.1
http://forum.xda-developers.com/showthread.php?t=1498003.
There were two choices. After boot loader unlock, which I had already done. Using right reading logic, I went to the "next step". Didn't realize ICS meant ice cream sandwich. Dumbass. I used CWM 5.5.0.4. Then I tried to to update the kernel, to*Holicakes2.6.35.14. For some unknown reason. The result is the white screen of death.
.*
I have access to hboot. As well as the recover menu which has a backup and restore option.
NAND restore clockworkmod backup, is available. I'm not sure how proceed.*
At the bottom of the screen:*
RA Revamped
Build: made for the WCX ILLUMINATE SERIES by GINM
I studied quite a bit. Too dumb to get a clear picture of the necessary steps before I began, I guess. Again, what a Dumbass.
I *need a better understanding of the process.
I didn't know about the super guide until it was too late. Rather, I did not understand I had seen the super guide when I saw it. It was from December, called a Holliday guide, so I didn't read it. There were so many guides, it confused me pretty throughly. Sheesh.
I have the htc white screen, reboots every three minutes or so.
I would really appreciate someone who knows to give me some clarification on these issues.
I understand a lot of these issues have been dealt with in this thread. I'm just really apprehensive.
I hope I posted this in the right place.
Thanks in advance,
Microbot2
Microbot, you have done pretty much what I did. If you follow megatronis a Brady's advice you will have a working phone. In fact I'm using it right now. Use the generic att zip an you will have ICS less the ATT bloatware.
Okay mircobot, I am home and can help you. Here is what you should do:
http://www.youtube.com/watch?v=xEWa_lUd2bY&feature=youtu.be
Watch that video. Shows you what you will need to do to get everything working again.
The next thing, you need to download all of the files you will need for getting your phone working again. I would recommend going here:
http://www.wcxxperia-nce.com/index.php
You will have to register to see the vivid forums.
Next decide if you want to be able to tether (generic build) or if you want stock based rom (ATT vivid ics).
Download the zip file. Follow the instructions in the video and should get you up and running in no time. That would be the easiest way in my opinion.
If you can't get it figured out or need more help just post here and we will try to assist.
Microbot2--vivid
Hey guys, thanks for the prompt reply's and your general bad-assness.
I just woke and will Start on the instructions.
Megatronisabeast, really appreciate it. Newbroman, thank you.
I already feel considerably less worried about this already. I'll let you know how it works out.
microbot2_no PH39img.zip
Note: I updated to ICS from att before I unlocked the bootloader, which is still locked as now the phone can't be seen by the program.
Megatronisabeast, thanks for the link to the video. I am a little closer to understanding now. Unfortunately, I don't have direct access to the internal storage, like the guy in the video did. and I couldn't discern the website URL and he never tells you directly, except for "goto wildchilds site" which i couldn't locate.
I now know that I have access to wildchildes recovery. Unfortunately, I can only see the internal storage if I use WC recovery, ("windows wants to format it") then goto USB-MS. Otherwise the computers don't see it when its plugged up. It says "device not found when I try to do something in AIO_toolkit 1.2 Don't know if that helps.
I did find the wcxrecovery.img
It appears that you have to have access to internal storage to load an image to it. PH39img.zip, which I don't have. I can't seem to find the wildchild ICS image, either. when I start my phone, it looks for the ph39img.zip, doesn't see it, goes to the white screen.
I don't understand how to get the image back,Rather, how to access the internal storage again. is PH39img is the same thing as the ROM? Do I have to load PH39IMG.zip and the wilchild_vivid_ICS.ROM, which, again, I can't seem to find.
This feels like a comedy of errors. I wish I would have studied longer. I usually do. THEN, I find "newbie_proof" all in one toolkit.
I Just wanted it rooted. All I had to do was click "root" instead of "kernel". Man, what was I thinking?
If only I had taken the Red Pill.
Thanks again,
Look at my post above, the link for wild Childs site is there. You have to register to see the vivid forums. That is also where you will download the files needed to set up the ROM, etc. You won't need the Ph39.img since you already have ics. That is for the bootloader. You can actually send a file to your phone in the recovery. since you already have recovery you would need to download the Android sdk tools, so you will have fastboot. You use fastboot to send the boot image to your phone. Then you would go to recovery and send the .zip file to your phone and flash in recovery. Sorry these directions aren't better, I will try to assist more when I get home, Swyping right now.
Sent from my HTC PH39100 using XDA
Microbot,
The wildchild files you need are in the first link Megatronisabeast cites
wcxxperia-nce.com/index.php (I'm a newbie and cant post the full web address). You have to sign up to the forum to access the files. The vivid forum will appear once you have registered.
The PH391IMG.zip is not your normal PH39img.zip you have to use the one contained in the WCX_generic_ATT.zip on the WCX vivid forum page. You also need to relock the phone. You are probably better off using the fastboot and the windows command prompt for this.
Can you boot into recovery at all?
Do you have another phone? you could use that to copy the PH39img.zip over. Thats what I did.
Mcrobot2---
Hi guys,*
Here is what I think I know:
HBOOT is a bootloader, *like a BIOS.
PH39img.zip is the boot file. Like PH39IMG.zip which appears to be a modified version for WC.
Kernel *is the memory and CPU manager.
ROM is an operating system package, or file placed onto the erasable/programmable part of the phones memory. NAND, I think.
S-OFF/ON *is a security check.
.Apk: compressed java file.
.Jar: *java application file.
.odex *files: helper files with most relevant information to compile and run the concerned application as fast as possible, a JIT Kind of thing.
----
I was able to relock bootloader, Yea!
Thanks megatronisabeast and newbroman.
--history--I updated to ICS from AT&T.
I thought I could skip reading for another three weeks because of newbie-proof AIO 2.1. * wrong!
I wanted to root my phone. *I had unlocked the bootloader with htcdev.*
Found hasoons all in one vivid 1.2. Used WC's recovery. I then flashed with hollicakes kernel, twice. Wsod.
--
Megatronisabeast:*
You use fastboot to send the boot image to your phone. Then you would go to recovery and send the .zip file to your phone and flash in recovery.
-I'm not sure the exact boot img,*
- I think the zip file would be the rom?
Getting closer.
Thanks again guys. I'm feeling a little thick lately. Like freshman year of college! Weed out classes.

[Q] Please help me with a brick =)

Basically situation is as follows - I have a phone that bricked after FOTA. I can't flash any RUUs since the version inside is higher. Jtag does not help, after full erase and rebuild of literally everything the phone remains a brick and still wants a firmware version higher than I can give it.
A few things I would like to ask. How do I flash OTA update to this phone?
I can install CWM thus have adb, I do have fastboot, I can change CID (at the moment i ve made it 11111111) I can make S-OFF.
How to perform a clean install of a custom rom only?
I am sure it is a SW brick since I managed to run it after install of a custom rom. BUT I decided to flash stock after that, and I can't repeat procedure. Any help and suggestions are apreciated. Anything will be helpfull.
Download the ROM you want, go into your Recovery and wipe Cache, Data, Davlik Cache (and SDcard if you want to) and then mount the storage via recovery and simply copy the .zip to your SDcard and install it after unmounting it.
Of course know how to flash roms from CWM))).
Sv: [Q] Please help me with a brick =)
Try s-off your phone then install a ruu.exe file that fits your cid.
Sent from my HTC Sensation using xda premium
I did that. It seems there is a problem since the phone once was 2.33 version but the latest ruu I can find is 2.31. I managed somehow flash it 2.31, but that is about it.
I am going to try to flash custom from your signature, and make the phone s-off, again...
Well it must be some strange HW error, since software wise I ve done literally everything.
skas_2002 said:
I did that. It seems there is a problem since the phone once was 2.33 version but the latest ruu I can find is 2.31. I managed somehow flash it 2.31, but that is about it.
I am going to try to flash custom from your signature, and make the phone s-off, again...
Click to expand...
Click to collapse
The fastboot flashables stock zip files i have for 2.33 are:
Runnymede_2.33.415.1_ARA
Runnymede_2.33.707.1_Asia_WWE
Runnymede_2.33.1113.1_Thailand
If you want any of these, i can upload for u
Ty, I found everything. The phone is has some kind of hardware fault i think. Too much work at the moment, I will post result once I get to it.
e-MMC problem. Not software related, even though it looked extremely software related .
if needed do i have : RUNNYMEDE_ICS_35_S_2.37.709.1_hTC_Asia_TW

[Q] reverting to stock - help needed

i had an issue with my newley purchased one and was advised to try flashing a non stock rom to see if the problem would go. it has not and i now need to put the phone back to standard htc sense 4.1 firmware.
I am ssuming that while the phone has bootloader unlocked still and rooted that i can download 4.1 firmware as a zip and put on the memory then flash from recovery? Once done i will use the tool-kit i used to unlock bootloader and root etc to take these off?
Can anyone link me to the correct firmware i need as there seems to be many listed and im not sure which it is.
At the moment i have Android rev 12 on there.
thanks
Come on a fair bag full of posts, but you haven't given the details of the phone.........
And if you have a nandroid backup of the original rom then restoring that returns the phone to how it was.
Or look here:
youtube.com/watch?v=xgBT0TQnZvM
L0rdNels0n said:
Come on a fair bag full of posts, but you haven't given the details of the phone.........
And if you have a nandroid backup of the original rom then restoring that returns the phone to how it was.
Or look here:
youtube.com/watch?v=xgBT0TQnZvM
Click to expand...
Click to collapse
Can someone please clarify for me....
i used the Hanson - all in one tool kit to unlock bootloader, put on recovery and root the phone. I then installed Android rev 12 to my phone.
I now want to go back to stock and dont have any back up so....
do i just download the stock 4.1 htc rom (this one http://goo.gl/3YQED) then flash this to my phone using the recovery method i used to flash android rev?
do i then just use the Hanson tool kit to remove root and re-lock the bootloader?
Not worried about the phone being completely clean as long as the root has gone and its showing the standard htc firmware in the 'about phone' section....phone is going back to be exchanged due to a hardware fault.
thanks
ive been trying to follow this thread but i seem to get myself lost as i did most of what it says using the toolkit and not adb on computer.

Let's play pretend

Bad boyz current rom
Updated firmware
Super CID
Rooted (obviously)
S-off
adb reboot-works
adb reboot recovery-works
adb reboot bootloader-works
Fastboot reboot- works
fastboot oem rebootRUU- works
RUU-no worky, says usb device not attached even with current htc drivers
Google unable to connect to server after wipe cuz i turned blinkfeed back on and had to push OK a gizzilian times due top FC and did factory reset.
I can go to dropbox thru browser and install app backup/restore and than restore all apps, but it still fails to connect to google servers as i input info from new device (custom rom) and want to start fresh. I dont care if it wipes internal storage (learned long ago how to keep nothing on device that can't be restored off device)
Yes i wiped everything twice (except system and storage, been there done that nightmare)
So.... Bone stock (any version) rom that can be flashed in recovery......
Barebones back to stock is going to require an RUU. Did you make a nandroid of stock before you rooted the phone or is that how you got it?
If you're looking for rooted stock for most recent 5.03.651.3 rom, go here: http://forum.xda-developers.com/showthread.php?t=2766604
MFOsaka said:
Barebones back to stock is going to require an RUU. Did you make a nandroid of stock before you rooted the phone or is that how you got it?
If you're looking for rooted stock for most recent 5.03.651.3 rom, go here: http://forum.xda-developers.com/showthread.php?t=2766604
Click to expand...
Click to collapse
Nope, i'm looking for 100 persent stock RUU bone stock RUU flasable in recovery.
I'm going to go back to roots (and i don't mean ROOTED)
Let's say htc evo. You could take the RUU and extract it in rar, now adays it would be 7zip, take the rom and name it to pmg.3400(example) and put it on sd card, then flash it in bootloader. That no longer exists. I have the vary first bone stock htc one sprint rom, and have extracted rom.zip from it, and it wont flash from recovery. I need to.
Looking for old timers who know what to do with this. I don't want rooted version that will flash in recovery, i have that already and fighting to pull stock OTA update out of it to flash in recovery. There has to be someone here that has had the 1st edition sprint android (hero, or evo 1st edition) that knows what i'm talking about.
Yeah, that's the unfortunate side effect of these phones and no longer have an SD slot. And believe me, I remember the Supersonic days. OG EVO was my first HTC device. EVO LTE after the fact and now this phone. Tinkered with other HTC models for other folks as well.
There is an offchance that having SuperCID not matching for Sprint could be a culprit too. I was checking out a few threads about that after I read your reply. As far as some help from someone that is savvy with the M7... BD619 knows his stuff. PM him.

Question About update (need little help)

Hi Xda members,
a quick question from my side
My htc m7 at&t converted into developer edition
running android lollipop 5.0.2 Stock with software number 7.17.1540.21
with root, unlocked bootloader and custom recovery
so i got a little security update over wifi
and i need ask that can i run the update with above mentioned situation
last time i had same little update and i ran it and my cell was stuck at bootloop
what i need do for a safe update install so i dont have to wipe my cell with a reflash becuz i know maybe am again gona stuck at bootloop or update wont install
ty
this forum always helped me so good
adeel617 said:
Hi Xda members,
a quick question from my side
My htc m7 at&t converted into developer edition
running android lollipop 5.0.2 Stock with software number 7.17.1540.21
with root, unlocked bootloader and custom recovery
so i got a little security update over wifi
and i need ask that can i run the update with above mentioned situation
last time i had same little update and i ran it and my cell was stuck at bootloop
what i need do for a safe update install so i dont have to wipe my cell with a reflash becuz i know maybe am again gona stuck at bootloop or update wont install
ty
this forum always helped me so good
Click to expand...
Click to collapse
Many ppl having issues updating stock rooted rom on this update and the previous one. Better to fully unroot the phone before attempting it. Using the 7.17.1540.21 RUU (see the link in my signature) is a good option imo but will wipe the phone unfortunately. Better to do a nandroid backup before updating (and copy the backup on your PC). Worst case, the update will cause a bootloop and you'll have to flash the 7.17.1540.21 ruu.
Might worth a try to backup your /data partition using twrp (save your backup on your pc), flash the 7.17.1540.21 ruu to unroot and remove any possible modifications, reflash twrp (but do not root), restore your /data backup, reflash the 7.17.1540.21 stock recovery and then try the ota update.
If its possible for you, I would really appreciate if you could share the ota update zip file so I can add the new files in the dev edition collection. To capture the ota zip file, download the ota update but select "install later". once downloaded go to your download folder and you should see a zip file starting with "OTA_M7_UL". Copy it to your computer and upload it (if you can).
u have a point about what u explained to me
i have been playing with android flashing and stuff from long and quite understand things and easy for me
and i didnt understood what happened when last time i got little update and then i had problem and phone went to bootloop
right now i might not be able to flash RUU because of my data in cell and work issues
if there is any solutions without flash let me knw and i cud easily upgrade from ota file
i will try upload and provide u link for it
ty.

Categories

Resources