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.
Related
...It's pretty much been over half a year since I needed to root my phone again, but I just received a brand new one from tmob.
SO. I did the root deal, that went super smooth, I have JF1.51 CRB43 ADP to start with.
NOW, I am trying to update the radio, and it does not seem to be working. From what I remember and what I've read, all you do is flash it like you would any rom, rename to update.zip and recov alt+s, right? Well, when I check the radio version it still says the original, not what I flashed. So I re-downloaded and tried again, no luck.
....feel like a real idiot here haha, never had it not work before. Tried searching but I had no luck finding the solution. By all means if you have a link and this was a pointless post just tell me, else I just need some help!
which recovery image do you have installed
maruutah said:
...It's pretty much been over half a year since I needed to root my phone again, but I just received a brand new one from tmob.
SO. I did the root deal, that went super smooth, I have JF1.51 CRB43 ADP to start with.
NOW, I am trying to update the radio, and it does not seem to be working. From what I remember and what I've read, all you do is flash it like you would any rom, rename to update.zip and recov alt+s, right? Well, when I check the radio version it still says the original, not what I flashed. So I re-downloaded and tried again, no luck.
....feel like a real idiot here haha, never had it not work before. Tried searching but I had no luck finding the solution. By all means if you have a link and this was a pointless post just tell me, else I just need some help!
Click to expand...
Click to collapse
If your using Cyanogen's recovery, try to physically press the alt-s, and home + back to reboot
I believe it works like that for flashing the IPL (radio) and SPL
where did you get the radio from?
Sorry I left out the recov info, I know my signature is misleading...didn't change it yet..!
I'm using JF 1.43 recov, I remember that (not sure if it was ever fixed, all I know is that flashing the SPL with CM recov caused 'error at line ___' when flashing new roms) that you cannot flash the new SPL with cyanogen recovery, so I'm using JF's until I get the radio and spl flashed correctly.
I got the radio from where I usually have in the past, as well as the new SPL
http://sapphire-port-dream.googlecode.com/files/
(Of course I will not flash the latest SPL until the newest radio is flashed first!)
I just want my happy CM 3.9.7 back..! With the ability to flash the new hero roms when I get curious..
****I am now attempting to flash the radio with cm recov 1.4, will update on this if it works.
****no luck with cm either, didn't think it would make a difference but thought I would give it a shot. I still have 1.22.12.29 for my radio :/ agh!
So...Still can't update the radio for whatever reason, just does not take, and I still can't find anything in the forums about this either... :/ Anyone have any ideas at all?
get the radio from the htc website maybe you got a bad download. i have flashed radio and new spl with cyanogens recovery so i know it will do it. after flashing the radio press home and back to reboot. do not reboot from the recovery console because i have noticed that it will not write the image.
david1171 said:
get the radio from the htc website maybe you got a bad download. i have flashed radio and new spl with cyanogens recovery so i know it will do it. after flashing the radio press home and back to reboot. do not reboot from the recovery console because i have noticed that it will not write the image.
Click to expand...
Click to collapse
Thanks for the link ^-^ I will give it a shot. Good to her that the CM recov flashes the new SPL alright now..! I will post results...every time I flash it goes through the motions of writing the radio but just never shows that I have the new one..super frustrating.
** I also notice that whenever I have tried to flash the radio on the new phone, when I reboot it goes through the appropriate motions, yes, however it puts me back into recovery every time. I wonder if I should just completely start over (unroot, re-root) hope thats not the case..I just got it all set back up again :/
Nope, no matter where I download from and how many times I flash with different recoveries.. I still have the original radio 1.22.12.29 :/
This has always been so easy! I've never had issues with rooting, then updating the radio, then updating to the new SPL.. :/
maruutah said:
Thanks for the link ^-^ I will give it a shot. Good to her that the CM recov flashes the new SPL alright now..! I will post results...every time I flash it goes through the motions of writing the radio but just never shows that I have the new one..super frustrating.
** I also notice that whenever I have tried to flash the radio on the new phone, when I reboot it goes through the appropriate motions, yes, however it puts me back into recovery every time. I wonder if I should just completely start over (unroot, re-root) hope thats not the case..I just got it all set back up again :/
Click to expand...
Click to collapse
If you can, try rerooting, it will only be a few more steps.
B-man007 said:
If you ca try rerooting, it will only be a few more steps.
Click to expand...
Click to collapse
Yeah, I was hoping to not have to but I will in a bit here if I still can't figure it out. I have root just fine, running CM 3.9.9.1 even, which I usually only run his roms, however I do like to try the Hero roms as well as they come out..
bummer :/
maruutah said:
Yeah, I was hoping to not have to but I will in a bit here if I still can't figure it out. I have root just fine, running CM 3.9.9.1 even, which I usually only run his roms, however I do like to try the Hero roms as well as they come out..
bummer :/
Click to expand...
Click to collapse
I don't know why its not updating your radio, but everything else works fine. You should update the radio before updating to cupcake builds. maybe that will help?
gave up for a while, finally re-rooted
Re-rooted and still cannot update my radio, I have tried updating it after the very first rooting steps, after updating to JF RC33 as well, I still can't get the latest radio to get onto my phone. I have tried with JF recovery, CM recovery, as well as the original recovery image, and nothing. Notta. Zip. No idea why my phone simply will not take the new radio image.. I have re-downloaded it a million times as well, going in circles..don't get why the phone will let me root, unroot, all that jazz, and simply will not let me update the radio... driving me nuts!! I can use CM roms just fine of course but any other roms I am stuck with not trying cause of this annoyance!! Anything anyone can recommend would be great
o man still can't get it to work?
try flashing the official 1.5 OTA update, which contains the updated radio. see if it gives you an error message. if it does, take it to tmobile and tell them to replace your phone.
if it flashes...see if it updated your radio. if it did, you can use the one click root to root your phone
Thanks again buddy, I will try it out ^^
So, I unrooted, and applied the OTA updates from 29 to 30, 30 to 33, 33 to cupcake..and I still don't have the latest radio, still at 1.22.12.29. I got the ota cupcake here:
https://android.clients.google.com/updates/partner/signed-kila-ota-150275.53dde318.zip
i'm going to try flashing the ota radio update without root if it will let me..grr..this is so weird, there is no reason why it shouldn't take a simple radio update..hrm
***attempted the ota radio update, guess you can't without root which is what I figured, but frick, this makes no sense.. >>
so, this is a bit odd, at http://developer.htc.com/adp.html, one of the spots to DL the latest radio, when you hover over the radio link for 1.5 and 1.6, it says "ota-radio-1_22_14_11.zip" rather than "ota-radio-2_22_19_26I.zip", weird, eh? Wonder if it's simply not the right radio, and labeled wrong, I have no idea, but this is getting super old.
I'm actually having the same problem, can't seem to update the radio with the radio image the htc site provides. It's still stuck at 1.22.12.29
Anyone had this before? Any help would be appreciated
I can't get around it, and it's really frustrating, since the only rom I can use is a CM build..aside from a couple others, but CM is the best as far as universal SPL use goes..
So what I've tried so far:
- Updated to HardSPL
- Tried multiple Radio updates, new ones, old ones, even some from the forums.
- Tried a few complete updates that include the radio image
- Tried flashing directly from fastboot, not sure what partition I need to flash though, the radio partition gives me an error that it does not exist.
Still no go. The weird thing is that I come from a stock 1.5 installation updated from 1.0 via t-mobile. And I'm still at the original 1.0 radio image.
My specs:
Sapphire PVT 32B ENG s-off h
HBoot: 1.33.2005
Radio: 2.22.19.261
Ok, so here's my story. I rooted my phone back in november and have had no problems with anything. However, in the last few weeks as i have been trying Froyo roms i keep getting a notification to do a system update to 1.6. Weird i know. I have tried different roms, tried different gapps with all the different roms and the problem keeps persisting. So the only thing i can think is that i messed up when i first flashed it. After i flashed, i flashed the spl i have now.
I have been reading on how to unroot and apparently when some people try to flash the SAMPIMG.nbh file they get an error. I am interested in know if i will run into this problem?
Also, how would i got about flashing AMON 1.7 recovery back to my phone. when i orginally rooted i used cyan's recovery. Do i still have to download and use the flash rec. apk file or can i just use fastboot to flash AMON's after i root. I guess i'm really asking what it the proper way for me to unroot my phone (without using a gold card) and then to reroot it to have Amon's 1.7 recovery?
DO NOT write an nbh file. It will do you NO GOOD.
The RADIO and SPL can have no relation to you getting weird system update notifications at all, and the rest of the system is written by a full update.zip.
Go into fastboot mode and run "fastboot -w system", then a "fastboot flash recovery.img" with your favorite recovery, then boot into recovery and flash your favorite rom.
bkrill said:
However, in the last few weeks as i have been trying Froyo roms i keep getting a notification to do a system update to 1.6. Weird i know. I have tried different roms, tried different gapps with all the different roms and the problem keeps persisting. So the only thing i can think is that i messed up when i first flashed it. After i flashed, i flashed the spl i have now.
Click to expand...
Click to collapse
Um notifications like sms? Or something else?
What carrier, what part of the world?
ezterry said:
Um notifications like sms? Or something else?
What carrier, what part of the world?
Click to expand...
Click to collapse
Robbers tormenting him about his radio version?
I have tmobile.
I don't know how but i've somehow fixed it. It disappeared yesterday after i used Firerats all in one script and hasn't shown up since. i don't know if thats why its not showing up or if one of the other things i was playing with disabled it. Thanks for all the help though.
Hi guys,
Followed the steps in forum.xda-developers.com/showthread.php?t=736271 to root my N1. All worked ok, and had root access. I proceeded to flash a custom recovery and received an error "mtd: not writing bad block at 0x000xxxxx". I redownloaded the recovery again, with the same issue. I rebooted and found that the recovery had loaded, however, after another reboot, was no longer the Amon recovery, but stock?
Second question is how can i unroot and go back to full stock? Tried a method found in another threat but was receiving a "verification failed" error - i assume because the version being flashed was too old for the FRF91 i had.
Any help is appreciated
Update
Hi ended up downloading EPE76 and renaming it to passimg, and letting recovery find/run it to unroot.
I then upgraded to FRF85B by downloading and renaming it to update.zip and running it from recovery.
And finally, i downloaded FRF91 and renamed to update.zip and ran it, again from recovery console, to get back to where i was before the hassles.
Not sure if this was the correct way to unroot, but my radio, rom version etc all matches before i started the rooting. The recovery flash never stuck (even though i did it in manual mode), and so it seems i am stock again.
Any advice on the issues in my first post?
best way to root
http://forum.xda-developers.com/showthread.php?t=710842
had same issue while rooting my latest nexus one, not exactly sure of how it happend but I just did same process and it worked fine. Command error or adb push into wrong place. I just cut and paste commands and it worked out fine.
First nexus one I unlocked bootloader and ended up selling it, thinking of switching to iphone 4, but decided to stay with n1.
Update
Hi there...
The method i used is a copy of that but without the battery mod.
Didn't really think having to trim the battery pack was a great idea...
Update
osugsxr said:
had same issue while rooting my latest nexus one, not exactly sure of how it happend but I just did same process and it worked fine. Command error or adb push into wrong place. I just cut and paste commands and it worked out fine.
First nexus one I unlocked bootloader and ended up selling it, thinking of switching to iphone 4, but decided to stay with n1.
Click to expand...
Click to collapse
Yeah starting to wonder if i should even bother trying again... just not sure if CM will be worth the effort. Was more doing it to check it out, rather than a need.
If i can find out how to unroot properly (i may have done it correctly above), i may give it another go. Just felt my unroot effort was trial and error and not really game to try it again and stuff it completely.
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.
Hi all,
I have been around a long time though i have never had trouble like this before..
i got a Incredible S PG32130 - HBOOT 2.0000.00 - Australian Delivered OPTUS002
I tried to follow the downgrade path so i could get S-OFF found here:
http://forum.xda-developers.com/showthread.php?t=1373697
Everything went fine so i proceeded with the older RUU flash to get back to 1.13 so can then run revoutionary..
Though the older RUU flash failed leaving the device hanging quietly brilliant.
Tried a few methods to get it back online to no avail.
So i htcdev unlocked the bootloader.. worked fine. still couldnt flash anything though. so put on CWM Recovery 5.0.2.0 which also worked fine..
I could then install custom ROMS.. So i tried IceColdSandwich though that wouldnt boot.. flashed the X4 kernel without issue.. so i assume it's cause the radio is still old and from what i gather i cant flash a new radio without S-OFF (i have tried through CWM and via Fastboot and via PG32IMG autoload in the bootloader and all fail.
So i tried an AOSP GB ROM still no luck.. Though neither of these would actually flash. get an communication error.. (could that be because ADB is not working? - am i missing a driver?)
And even tried a of legit WWE and CM7 both fail to install as well.
RUU_VIVO_ICS_35_S_HTC_WWE_4.10.405.1_Radio_20.74.30.0833U_3831.18.00.11_M_release_266013_signed
From my limited knowledge Radio is independent of AOSP/Sense/GB/ICS though Kernel is dependant. Though the only thing i havent been able to flash is the radio.. will the wrong radio stop you booting?
What are my options here to get S-OFF? I cant adb the device no matter what i do though i do have working recovery and fastboot.
Little help would be greatly appreciated.
damn..
http://forum.xda-developers.com/showthread.php?t=1337105
this fixed me.. the manual flashing of the boot.img was the problem..
ffs.. i have spent hours and read so many guides and that one was the only one that mentioned that you had to manually flash boot.img.
thanks all.
Sage said:
damn..
http://forum.xda-developers.com/showthread.php?t=1337105
this fixed me.. the manual flashing of the boot.img was the problem..
ffs.. i have spent hours and read so many guides and that one was the only one that mentioned that you had to manually flash boot.img.
thanks all.
Click to expand...
Click to collapse
Do you still require s-off? What error message did the ruu return when it failed?
the RUU error is simply USB Connection ERROR though this happens after it has erased and sent the package to the phone.
I think it maybe due to not being able to use ADB.. so prob a driver issue. either way i dont really need S-OFF and after the hours i have spent on this i am reluctant to play more
It aint even my phone! Mine is Sensation which is already S-OFF'd
Thanks for the offer though.