Related
I have been lurking on these forums since my wife and I received our Heros about one year ago. The information on here as been wonderful and I have yet to really run into any big problems. I generally experiment on my phone first, and then after I find a good stable setup, I reflash and rebuild my wife's phone. Thus far, life has been good
However, I recently had both phones "turned" S-OFF using the unrevoked method, followed by the ENG-SPL. I tested my hero first by flashing a working HERCIMG that flashed the latest CWM, which worked without incident after an RUU. For the life of me, I cannot get my wife's phone to flash a HERCIMG. I have tried my own, downloaded several HERCIMG.zips around these forums. Tried reflashing unrevoked and ENG-SPL again. Nothing!
I've tried searching around for the past two nights to only find possibly one other person who MAY have had a problem (though I have been drinking, therefor no longer focused and cannot find the thread...will look for it in the morning). Both phones use CWM (latest generally, unless updating PRL, etc...), run some variant of CM7 (nightly or stable) and use firerat's (have removed and reflashed recoveries just in case this was conflicting). I cannot get it at all get this phone to flash a HERCIMG, anyone have any suggestions on something I am missing? Thanks!!
I was just told today that some phones that flash the eng-spl won't flash hercimg. Perhaps your wife's is one of them. I'm also told that ruu-ing the phone will remove the eng-spl and you should be able to flash a hercimg through hboot without eng-spl.
Edit: I'll also say that this information is less than 24 hours old for me, I'm no expert.
Drummerboy527 said:
I have been lurking on these forums since my wife and I received our Heros about one year ago. The information on here as been wonderful and I have yet to really run into any big problems. I generally experiment on my phone first, and then after I find a good stable setup, I reflash and rebuild my wife's phone. Thus far, life has been good
However, I recently had both phones "turned" S-OFF using the unrevoked method, followed by the ENG-SPL. I tested my hero first by flashing a working HERCIMG that flashed the latest CWM, which worked without incident after an RUU. For the life of me, I cannot get my wife's phone to flash a HERCIMG. I have tried my own, downloaded several HERCIMG.zips around these forums. Tried reflashing unrevoked and ENG-SPL again. Nothing!
I've tried searching around for the past two nights to only find possibly one other person who MAY have had a problem (though I have been drinking, therefor no longer focused and cannot find the thread...will look for it in the morning). Both phones use CWM (latest generally, unless updating PRL, etc...), run some variant of CM7 (nightly or stable) and use firerat's (have removed and reflashed recoveries just in case this was conflicting). I cannot get it at all get this phone to flash a HERCIMG, anyone have any suggestions on something I am missing? Thanks!!
Click to expand...
Click to collapse
When you say you can't get it to flash, what stage is failing? Does the bootloader not recognize the HERCIMG? Will it not install the .img? A little more detail, pls.
I have ruu-ed to remove ENG-SPL and attempted to flash under 1.47.000...no difference.
The bootloader does not recognize HERCIMG; it boots up the same with the same text output whether the file is there or not.
Drummerboy527 said:
I have ruu-ed to remove ENG-SPL and attempted to flash under 1.47.000...no difference.
The bootloader does not recognize HERCIMG; it boots up the same with the same text output whether the file is there or not.
Click to expand...
Click to collapse
If you ruu'd you took away your ability to flash through the bootloader, unless you used regaw's method to gain s-off. Does your bootloader show s-off at the top?
Another thought . . . you said you ruu'd, did you use 2.27.651.7 to ruu? If so, you may need to use a HERCIMG with an android-info.txt that has version 2.27.xxx in it instead of version 2.31.xxx. Check your HERCIMG and see what version is in there.
Sorry my mistake, I should have clarified that comment Yes, I used Regaw's method originally for S-OFF, which is still S-OFF even after the RUU as it should be.
This was originally how I ran into this problem as the HERCIMG was not flashing even as S-OFF 1.47.0000. So I flashed ENG-SPL to try something different with no change, then RUU-ed and tried again. Still nothing. Had to reroot and restore
Drummerboy527 said:
So I flashed ENG-SPL to try something different with no change . . .
Click to expand...
Click to collapse
Are you saying you still had 1.47.0000 after you ran the eng-spl? If so, I ran into that same problem. I initially had 1.46.xxx after eng-spl. Then I had to ruu to fix a problem and when I came back I flashed eng-spl again and my bootloader stayed at 1.47.0000. I am convinced Sprint figured out a way to muck with eng-spl, but this is just a conspiracy theory.
24601 said:
Another thought . . . you said you ruu'd, did you use 2.27.651.7 to ruu? If so, you may need to use a HERCIMG with an android-info.txt that has version 2.27.xxx in it instead of version 2.31.xxx. Check your HERCIMG and see what version is in there.
Click to expand...
Click to collapse
I used ruu 2.27.651.6. I actually saw this happening in another thread (still cannot find it) and so I tried that also. I have a HERCIMG with both a 2.27.xxx and a 2.31.xxx. Here is what I did with my phone:
Ruu-ed with 2.27.651.6, applied OTA update to 651.7, then applied the next update .2. Flashed the HERCIMG with a 2.27.xxx android-info.txt that was the latest CWM from jasonmaloney's thread (renamed as recovery.img). Worked like a charm!
My wife's phone:
Prior to Ruu (An RUU has actually never been done on this since we originally purchased it), I actually attempted to flash the latest CWM since the current version was 2.5.0.7 thru HERCIMG to test it out. No luck!
Thought that maybe ENG-SPL was causing the problem so I RUU-ed 651.6. Attempted to flash HERCIMG under S-OFF 147.0000 which the bootloader ignored.
I never updated beyond that as I couldn't get some of the newer methods of rooting to work so I rooted .6 and restored the nandroid while I continue the research.
24601 said:
Are you saying you still had 1.47.0000 after you ran the eng-spl? If so, I ran into that same problem. I initially had 1.46.xxx after eng-spl. Then I had to ruu to fix a problem and when I came back I flashed eng-spl again and my bootloader stayed at 1.47.0000. I am convinced Sprint figured out a way to muck with eng-spl, but this is just a conspiracy theory.
Click to expand...
Click to collapse
I actually ran into this problem initially going S-OFF...sort of-ish. I flashed Regaw on the phone with turned it S-OFF but ENG-SPL would not flash to 1.46.xxx. I had to remove firerats to get it to work. Not sure if it was related or not but afterward it worked.
After RUU-ing, Since S-OFF 1.47.xxx didn't work, I reflashed eng-spl and it went back to 1.46.xxx, though I was not using firerats at this point.
Drummerboy527 said:
I actually ran into this problem initially going S-OFF...sort of-ish. I flashed Regaw on the phone with turned it S-OFF but ENG-SPL would not flash to 1.46.xxx. I had to remove firerats to get it to work. Not sure if it was related or not but afterward it worked.
After RUU-ing, Since S-OFF 1.47.xxx didn't work, I reflashed eng-spl and it went back to 1.46.xxx, though I was not using firerats at this point.
Click to expand...
Click to collapse
The member you saw mention this issue is vayman, he has literally the exact same issue having followed the exact same steps a few days ago. I hope you can figure it out.
sent from a series of tubes.
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.
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
what is the best way to get back to stock. as of right now I believe i have S-ON.
I tried firewater but didnt work..
tried this guide but my phone wont get into bootloader mode on its own...
I also can not seem to find the fastboot feature anymore, the roms i have been using dont seem to have that feature, and i need to disable that for the bottom method to work..
http://theunlockr.com/2014/06/08/how-to-unroot-the-htc-one-m8-video/
tried using the RUU method with no luck, i get errors in between.
Any ideas?
Im really trying to get this phone back to stock 100%..
I'm currently having the same problem. I wanted to install the 4.4.3 OTA but I cannot
I've tried numerous sprint HK recoveries and even an RUU but to no avail. Did you ever solve this?
no sorry
[MANDATORY INTRODUCTORY SENTENCE DEPLOYED] Okay so as the title states I have an issue with my Sprint HTC One (m7) [MANDATORY INTRODUCTORY SENTENCE Complete].
The issue in question is lack of GPSability after flashing (you guessed it) Cyanogenmod 11 and currently CM12. I have tried multiple ROMs since then and all of them either don't fix the issue or wont install or work at all. So now I'm back to CM12 and everything works terrifically except for GPS...which I need...alot.
Now of all the research I've done on finding a fix for this infuriating problem has led me to believe that the only real way to fix this is to flash to a stock ROM, get a GPS fix/lock/signal/whathaveyou and then wipe and flash back over to your ROM of choice HOWEVER....heh heh I kinda un-acquired my backup, it somehow got erased during some blunder during the initial rooting process and I was dumb enough to not have saved a backup on my pc...oops.
Now I am aware that there are other ways of restoring my device to stock by other means such as RUU processes but I am not able to perform this process as my internet connection on my pc is dependent on my phone itself via tethering.
I also know that some have had luck by flashing new kernels however I have not been able to find one that worked for me.
So I guess what I'm asking is does anyone know of any other way I could restore my phone to stock using methods that don't require my pc to be connected to the internet, know of a place where I can find a flashable stock ROM or simply just fix my GPS issue outright?
I appreciate any assistance anyone can offer. Thank you in advance.
blink.riddle said:
[MANDATORY INTRODUCTORY SENTENCE DEPLOYED] Okay so as the title states I have an issue with my Sprint HTC One (m7) [MANDATORY INTRODUCTORY SENTENCE Complete].
The issue in question is lack of GPSability after flashing (you guessed it) Cyanogenmod 11 and currently CM12. I have tried multiple ROMs since then and all of them either don't fix the issue or wont install or work at all. So now I'm back to CM12 and everything works terrifically except for GPS...which I need...alot.
Now of all the research I've done on finding a fix for this infuriating problem has led me to believe that the only real way to fix this is to flash to a stock ROM, get a GPS fix/lock/signal/whathaveyou and then wipe and flash back over to your ROM of choice HOWEVER....heh heh I kinda un-acquired my backup, it somehow got erased during some blunder during the initial rooting process and I was dumb enough to not have saved a backup on my pc...oops.
Now I am aware that there are other ways of restoring my device to stock by other means such as RUU processes but I am not able to perform this process as my internet connection on my pc is dependent on my phone itself via tethering.
I also know that some have had luck by flashing new kernels however I have not been able to find one that worked for me.
So I guess what I'm asking is does anyone know of any other way I could restore my phone to stock using methods that don't require my pc to be connected to the internet, know of a place where I can find a flashable stock ROM or simply just fix my GPS issue outright?
I appreciate any assistance anyone can offer. Thank you in advance.
Click to expand...
Click to collapse
The RUU will work just download it and run it from your pc
If your not on 6.x firmware yet use this
Sprint 5.xx RUU
http://forum.xda-developers.com/showthread.php?t=2795856
clsA said:
The RUU will work just download it and run it from your pc
If your not on 6.x firmware yet use this
Sprint 5.xx RUU
http://forum.xda-developers.com/showthread.php?t=2795856
Click to expand...
Click to collapse
I forgot it was Rumrunner that needed internet conection to work, the RUU simply wouldn't work, again this time was no different. But, BUT, BUUUUUT, thanks to that link I WAS able to get access to answers that eventually solved my problem both primary AND secondary. Was able to get back to stock via a Stock Rooted Rom AND achieved GPS lock with CM12. You have my eternal thanks my friend. Your link opened the road to answers that two months of googling couldn't answer.