Related
I bought a g1 off of craigslist and it already had root. JF 1.4 ....
Around the time cupcake was released I updated it to jf 1.51
Now since there will be no more JF updates I wish to switch to Cyan builds.
I'm unsure of the proper way of doing this?
Should I go back stock .. unroot and then go thru the steps to load cyan?
Or is there a better way? A wipe?
I'm asking to be clear because internet access is strictly from my g1.
Although I can download all the files I need, I do not have constant access.
I'd appreciate any tips or pointing me to the proper thread.
Check the threads in Dream >Dream Android Development look for Cyanogen's thread on his release of 4.1.999, follow the instructions and you will be fine. I'd also suggest at least flashing Cyanogen's v1.4 Recovery Image over JF's, easier to flash any .zip on sdcard. So, new recovery image (use search option in forums, or look in the same thread i mentioned for cyanogen recovery image 1.4) then update to cyanogen's latest rom build
So simply flash a new recovery, then follow the cyan steps?
Cool, easy as pie.
I certainly appreciate it.
Thank you
Yup. just be careful that you dont boot off the htc recovery rom, or the steps to get to cyans rom become much, much harder
B-man007 said:
Yup. just be careful that you dont boot off the htc recovery rom, or the steps to get to cyans rom become much, much harder
Click to expand...
Click to collapse
that is why there is a full update made for it.
haha o right i forgot about that one... no one asked questions about a bad all-in-one flash, only those who messed up while flashing the htc rom
i need sleep lol
B-man007 said:
haha o right i forgot about that one... no one asked questions about a bad all-in-one flash, only those who messed up while flashing the htc rom
i need sleep lol
Click to expand...
Click to collapse
sleep is for the weak. also it is really hard to flash two things while in recovery it causes hemorrhoids and anal fissures.
haha trust me...someone somewhere will make something incredibly easy look like rocketscience
B-man007 said:
haha trust me...someone somewhere will make something incredibly easy look like rocketscience
Click to expand...
Click to collapse
you mean rocketsurgery
david1171 said:
you mean rocketsurgery
Click to expand...
Click to collapse
*sigh*
yes its true.
B-man007 said:
*sigh*
yes its true.
Click to expand...
Click to collapse
lmao me went to smart person learning place
I'd like to chime in here as well since I'm having such a hard time searching for info on the conversion from jf1.51 to the latest build of CM. The amount of posts are staggering!
So, I vaguely remember setting up apps2sd following the guide at the bottom of this page - http://yokohead.com/2009/06/how-to-root-android-g1-with-cupcake-and-appstosd/
Will CM automatically detect this partition?
Also, will I lose the google experience? I'm still confused as to where we are on that.
Thanks for your time! If anyone knows an updated post on this process, please point me to it.
TJ
Well the sticky by fingerlickin at the top of this section is a good place to start....
all you have to do is find the singleflash update in the dev section, backup and clear everything off your ext3, and wipe+flash the single update. you can restore the ext backup then.
also you should upgrade to cyan 1.4 recovery
to do so
su
cd /sdcard
wget http://n0rp.chemlab.org/android/cm-recovery-1.4.img
flash_image recovery /sdcard/cm-recovery-1.4.img
Click to expand...
Click to collapse
you wont lose the google experience
Thanks B-Man007,
After a couple attempts, all is working well. I'm thoroughly impressed with the snappiness of this build. Although it's only my second time updating a ROM, I'm going to blame the amount of posts for my hesitation and confusion. It was easy to just go in and do it.
I actually updated to the latest Amon-Ra(sp?) recovery. At first my Rom was running real slow and the recovery allowed me to update my ext2 to ext3. Loving it now!
The amount of posts does make it quite confusing i agree, especially with the high amount of conflicting posts
Ya ext3 is a must, but you could have upgraded from cyans too haha
cyan usually has the fastest builds out there though at times it can get very slow.
Another noob here. A few months ago I rooted and flashed to xrom 1.5. When I do a reboot, my recovery screen tells me its "CyanogenMod v1.4 + JF".
Since xRom is experiencing some problems w/ updates, I figured I might try the latest build of Cyanogen. I re-booted, went to recovery mode. Wiped. Then flashed the latest Cyan and even found the 1.6 ota on another site. Flashed both zips, then did a re-boot and it hangs now.
I tried it over and over a few times, wiping then flashing again. Wiping, then re-booting, then flashing the rom, etc. Over and over with the same results.
Then as a test, I tried flashing back to xRom... perfectly fine.
As another test, I tried wiping and flashing to another rom, the rooted stock option (the HTC rom version)... and got the same results as when I tried Cyan... just hangs.
Wiped and flashed again back to xRom... works fine.
So at this point, I'm thinking I need a more updated recovery rom? Any other possible problems? Yes, I did a search all over and this was the best thread that matched my problem.
If it helps... I have a T-mo G1, firmware 1.5, JACxROMv1.5, kernel version 2.6.29.6-jac-ski root. And I know many will slap their foreheads when I say this: But the SD is NOT partioned at all (kept trying and trying with zero success, so I eventually gave up).
Please help!!! I started messing with my phone about a week ago and I install the Android 1.6 dev. It will not flash anything, not even an spl. What am I missing. I almost feel bad asking because all of you seem to have such knowledge of this stuff. Thank you very much
I don't wanna bring your hopes down thinking this was help lol but u prolly tried flashing cyanogens new rom and its funny cause i was JUST about to post this same shiet. but anyways. i was thinking about flashing the dream file but i dunno if that owuld brick my phone or not. and just to clarify its the htc 1.6 dev right? i mean if thats the only 1? lol
yup
That is exactly what happened! I don't understand how this isn't a major issue and posted everywhere. If you figure it out make sure you let me know and I will do the same. Take it slow!
Can you explain what the problem problem is? What have you been trying to flash? Do you get errors? What recovery image are you using?
Btw, if you're flashing an SPL or radio with Cyans recovery, you can't use the trackball. It must be an update.zip which you install by pressing alt-s and reboot using home+power. If you don't it wont be installed.
Well, I don'tk now about the original poster, but I've tried flashing the OTA cupcake rom to downgrade. renamed to update, went into recovery but it says its not authorized. and.. im afraid to put the dream.nbh or w/e cause it might brick the phone.
PS: This is 1.6 without root. this is the dev ver. so we have the exclamation point recovery not cyan.
lapalways05 said:
Well, I don'tk now about the original poster, but I've tried flashing the OTA cupcake rom to downgrade. renamed to update, went into recovery but it says its not authorized. and.. im afraid to put the dream.nbh or w/e cause it might brick the phone.
PS: This is 1.6 without root. this is the dev ver. so we have the exclamation point recovery not cyan.
Click to expand...
Click to collapse
okay first you need a app called flashrec it will dl cyan recovery image then you reboot.But you need root first also teh dreaimg.nbh file which is RC29.
1.5 cupcake rc30 or something and up was patched with the one click root, that's why we were trying to downgrade to 1.5..
nothing works
I can't use the flash rec because it won't back up the recovery image! Everything I try to flash just goes to installation aborted! I don't know what to do!
It's b ecause 1.5 rc30+up (including 1.6) patched up the 1 click, but an answer would be nice
flash the dream image and start from scratch. that takes everything back to stock, then you can re-root. This thread can walk you through it
http://forum.xda-developers.com/showthread.php?t=491350
it doesnt work
I already tryed that but it won't let me flash the spl!
i tried that too
I tried flashin the dreaimg too. I have ran jf1.5 before and flashed themes and everything. That's why I don't understand why I can't flash anything. The 1.6 work but the recovery image isn't letting me flash anything at all! Once I installed the 1.6 dev it flashed me from the 1.4 cyanogen image to the exclamation image with a differnt bootloader. Ever since then I can't flash anything.
i think he means using camera + power unroot it.but im guessing we don't flash the SPL since we can't, we just flash the dream.nbh?
After Factory Reset
Guys,
I did factory reset but now I can not work with HTC dream as it is requesting me to cerate a gmail account, and I can not cerate because I do nto have internet in my mobile operator.
Does anyone knwo how to bypass this mesage?
please help meee.
r,
bhowd u do the factory reset?
I did it!!!
I had to download sdk, get it working, fastboot the the cyanogen 1.4 recovery image. After the it let me install all of my updates. YAAAAYYYY!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
could you tell me the steps of what you did?
I'm stuck with ADP1 1.6 ><
Thanks a lot!!
This will work!!!
Trust me this will work because it took me hours to figure out. Install sdk, get it to work. They explain how to use the program on the forum. After you finally get into fastboot flash the cm 1.4 recovery image. After you do that you can bootup into that recovery and it will then read all of your zip files unlike that stupid exclamation recovery.
slightly confused
So you mean you used http://forum.xda-developers.com/showthread.php?t=502010 to figure out how to use the sdk right?
If not, can show me the link to that guide?
Many thanks!!!
yes
Yes, I used the sticky notes at the top of Dream Q&A to figure it out and it wasn't too fun.
I just rooted my g1 and i'm having problems trying to install cms rom.
some info;
DREA100 PVT 32B
HSPL10.95.3000
CPLD-4
RADIO-2.22.19.26I
Oct 20 2008
I installed cm's recover 1.4 img and have access to the recovery screen no problem.
Tired installing AP1.6 but can't confirm it got installed.
I did this..
wipe
flashed signed-dream_devphone_userdebug-ota-14721
wipe
flashed cm 4.2.7.1
goes to the T-mobile screen, then it loads up cm's boot screen then after where it should take me to the setup screen, it turns gray/black and stays there.
please give me some imput on what i'm doing wrong.
Thanks!
You wipe, then you flash the ota update. Reboot and it will go back into recovery by itself. from there you install cm, without wiping. Reboot and you are good.
Ok i've done just that.
wiped
flashed ota, it goes back to recovery image
i flash cm 4.2.7.1
reboot and it does the same thing.
t-mo logo loads up. then cm's android bootscreen loads up.
then it goes gray/black and stays there.
i know im doing something wrong but not sure what... should i install a older cm rom first? since i'm coming from a fresh rooted g1? i was coming from rc29
RegulatorG1 said:
Ok i've done just that.
wiped
flashed ota, it goes back to recovery image
i flash cm 4.2.7.1
reboot and it does the same thing.
t-mo logo loads up. then cm's android bootscreen loads up.
then it goes gray/black and stays there.
i know im doing something wrong but not sure what... should i install a older cm rom first? since i'm coming from a fresh rooted g1? i was coming from rc29
Click to expand...
Click to collapse
it shouldn't make a difference. how much time did you wait? It could take up to 15 minutes for the first initial boot.
i've waited about 10mins. but even if it goes to the gray/black screen i should wait for it longer?
gonna redo this again and wait for a longer time. 20mins max and see where it goes from there.
Upgrade to amon_ra recovery 1.5
Then do this
Wipe
install ADP 1.6
flash cm rom right after flashing ADP without reboot
now reboot and it will go back to recovery mode
now reboot once again and wait my friend
I'm still waiting for about 20mins to see if it reboots good.
If not then i'll be doing the new amon_ra recovery 1.5 way.
should i install a older cm rom if coming from bare root?
or it doesn't matter if i'm flashing 1.6?
you might want to consider upgrading your spl while you're at it. Just a thought. I don't think it's necessary for running Cyanogen, but it'd be nice to have in case you ever want to run a hero rom to upgrade to the danger spl
where can i get the spl? I dont wanna install the danger one since I wont be installing hero on it. I just wanna run cm roms.
no luck still. but have another dumb question for you folks.
the spl i have is this. .. HSPL10.95.3000
is this ok to run cm or should i upgrade it? i know that there is a spl that is used to run hero roms but i'm not gonna be doing that so I thought that maybe there might be another spl out there that is a upgrade from the one i have?
gonna go search the forums for this btw. I dont wanna be a pain about this.
RegulatorG1 said:
no luck still. but have another dumb question for you folks.
the spl i have is this. .. HSPL10.95.3000
is this ok to run cm or should i upgrade it? i know that there is a spl that is used to run hero roms but i'm not gonna be doing that so I thought that maybe there might be another spl out there that is a upgrade from the one i have?
gonna go search the forums for this btw. I dont wanna be a pain about this.
Click to expand...
Click to collapse
I was wondering if it was your spl that could be preventing the rom to boot up. If you don't want to flash the danger spl, you can flash another one, like the HardSPL. I'm sure if you look in one of the sticky's or locked threads at the top of the forums in development you will probably be able to find a download link. It's worth a shot. Since you already have the latest radio, there is no reason to worry about upgrading the radio.
i was checking the forums and i have the hard spl.
or at least this says is the hard one. goes something like this..
hardspl =VER: HSPL10.95.3000
then
Engineering SPL=VER: HBOOT-0.95.3000
and last
G1 Original SPL=VER: HBOOT-0.95.0000
still no luck with installing cm's rom.. gonna look some more.
thanks for all the help guys! please if you think of something else let me know.
ok can't figure this crap out. gonna go bald lol
did a restore on my recovery and i'm back to this.
Model number: Android Dev Phone 1
Firmware version: 1.6
Baseband version: 62.50s.20.1H_2.22.19.26I
Kerner version: 2.6.29-00479-g3c7df37
[email protected] #19
Build number: dream_devphone-userdebug 1.6 DRC83 14721 test-keys
It does show the 1.6ADP
but what the hell lmao. I can't install cm though.
Not gonna touch the g1 right now till hopefully some of you can tell me how or what to do to upgrade my rom to hopefully cm4.2.7.1.
Again i'm really sorry for being soo needy.
oh crap. I think i lost root access again >_< crap
what's the best way to check to see if i still have root?
turned off phone and tried going into recovery but now it just shows the triangle ! and the phone pic. guess root is gone???
The newer Spl rearranges how mem is allocated so more is given to system partition on phone which allows larger roms to be installed(heros).Any SpL is fine for cyanogen/enom/dwang roms.
RegulatorG1 said:
oh crap. I think i lost root access again >_< crap
what's the best way to check to see if i still have root?
turned off phone and tried going into recovery but now it just shows the triangle ! and the phone pic. guess root is gone???
Click to expand...
Click to collapse
The triangle means root is no longer with you,young one.
ok, gonna root it again. i can get it to rc29 no problem but that's where the entire thing went wrong. will post later. wish me luck
ok rooted my g1 once again. gonna install the 1.4 recovery image now.
ok installed 1.4 recovery, now performing a backup for this point.
I think I have a old cm rom around somewhere.. .. its a 3.9.5cm should i update radio first then install this or visa versa?
+ok, installed 1.4 and flashed new radio. now gonna do what your saying and see where it goes. performing backups at each point >< lol
-ok i went to recovery and flashed the new radio and it's still formating cache... its been like 5mins already. should i reboot or wait longer?
i'm still needing to install the 1.6ADP and the rom still.
Don't reboot between the 2 zip files.
Boot to recovery
do a wipe
wipe it again for good measure
install from zip signed dev dream zip
install from zip Cyanogenmod 4.2.7.1
reboot
It will tell you it is writing radio then actually reboot
It will reboot to recovery mode
where it will tell you its writing cache...
wait till it offers reboot option again
Reboot
you shoul dget the G1 screen, than the cyanogen screen...
yes it might take a while on the second screen...I have never had it hang more than about 8 minutes.
Then you should be operational.
I do have a reoccuring issue with poor response after the initial boot to the desktop.
I usually just wait for it to stop all the background shuffling and then it smooths out.
YMMV
ok this is where i am so far...
have root
have hardspl
have recovery 1.4
have Radio Update 2.2.19.26I
now i'm gonna perform backup and do what you just said. hopefully since i did everything brand new there will be no issues.
Phone: HTC Hero, CDMA
Carrier: Sprint
While others have reported of this problem, the solutions that worked for them dont work for me. Im really stuck.
I know, its an old and slow phone, but I was hoping to go to CM7 to get better performance out of it. Well, I must have done something wrong in the process. My current android version is 2.1-update1. I used z4root to root it and used the clockworkmod ROM manager to install a recent nightly after backing-up my current ROM. Installing the nightly failed, something to do with the zip, but my phone had already been wiped and rebooted in default factory mode. I tried doing the install again with the same nightly and a more recent one, but it kept failing due to a problem with the zips. After one of the reboots, the OS just wouldnt load; seems to be looping on the 'HTC quietly brilliant' screen. I am able to boot in recovery mode, but cant figure out how to get past this looping issue.
Ive tried booting using the back-up I created with no luck. Ive even tried going through the RUU process (cant post a link cause Im a new member here), which results in an error message stating that theres an incorrect bootloader.
I did figure out that I was trying to install CM7 using the wrong zip; had the GSM version. Ive tried installing CM7 with the correct zip, but, after reboot, it loops at the animation with the android on the skateboard and the blue arrow around it. Not sure what it means that the two different OSs loop at, what looks like, the same points.
I probably did something wrong, but Im hoping somebody with a better understanding of all thats involved can let me know if there is any way for me to fix this. Thanks in advance for the help.
grins1 said:
Phone: HTC Hero, CDMA
Carrier: Sprint
While others have reported of this problem, the solutions that worked for them dont work for me. Im really stuck.
I know, its an old and slow phone, but I was hoping to go to CM7 to get better performance out of it. Well, I must have done something wrong in the process. My current android version is 2.1-update1. I used z4root to root it and used the clockworkmod ROM manager to install a recent nightly after backing-up my current ROM. Installing the nightly failed, something to do with the zip, but my phone had already been wiped and rebooted in default factory mode. I tried doing the install again with the same nightly and a more recent one, but it kept failing due to a problem with the zips. After one of the reboots, the OS just wouldnt load; seems to be looping on the 'HTC quietly brilliant' screen. I am able to boot in recovery mode, but cant figure out how to get past this looping issue.
Ive tried booting using the back-up I created with no luck. Ive even tried going through the RUU process (cant post a link cause Im a new member here), which results in an error message stating that theres an incorrect bootloader.
I did figure out that I was trying to install CM7 using the wrong zip; had the GSM version. Ive tried installing CM7 with the correct zip, but, after reboot, it loops at the animation with the android on the skateboard and the blue arrow around it. Not sure what it means that the two different OSs loop at, what looks like, the same points.
I probably did something wrong, but Im hoping somebody with a better understanding of all thats involved can let me know if there is any way for me to fix this. Thanks in advance for the help.
Click to expand...
Click to collapse
I *think* your error, in general, was using a bunch of "easy" one click methods and not properly learning (READING) about what the proper steps are. Here is my advice (assuming you are still rooted) -
1.boot into recovery (power off phone, hold home button, press power)
2.wipe data/factory reset
3.mounts/storage - wipe system and boot
4.restore nand backup OR flash ROM/gapps (from the same thread)
5.reboot, and be patient, bootup could take 5-10 minutes.
Good Luck.
You are the man (or woman)! I believe the formatting of system and boot is what did it. Really appreciate the help.
grins1 said:
You are the man (or woman)! I believe the formatting of system and boot is what did it. Really appreciate the help.
Click to expand...
Click to collapse
It is important, as Il Duce said, that you definitely do a good amount of reading when you want to get involved in rooting your phone. You are opening yourself up to some great innovation and fun, but you can also cause yourself a lot of headaches.
Recovery is your friend. If you can get into that, at least you know things are ok. I like to wipe (or format) system, data, cache, and boot 3x just to make sure that clockwork recovery cleaned everything and there are no dingleberries from the last rom I was using.
Flashing the correct type of rom is even more important. Don't flash a gsm rom to a cdma phone and NEVER flash a gsm radio to a cdma phone. Once you delve into the reading aspect of XDA, you will see that is the sure way to brick your phone.
Some roms take longer than others to boot up. Let it run its course. Sometimes it will reboot right after installing. At some point, you might want to make a nandroid of the new rom you are running and go back to your stock (2.1 update 1) and update your PRL, baseband, etc. (if you haven't done an update in a while).
Have fun, that is the most important part and we seem to have a lot of it here in HeroC XDA land.
You know, I put in a fair share of reading about how to update the ROM on my phone and I was under the impression that it would be fairly simple. I figured that since this has been done for quite a while and all these tools have been developed, I wouldnt need to know what happens on the back end during a root or ROM install.
But I did get myself into a bind that I wasnt able to figure out on my own. And with the help of this forum, I was able to get past my problem. Im glad to say I now have a phone that is functioning very smoothly with CM7 and the apps I need.
Next step for me is figuring out how to save my apps to the SD card so that I can install from there if/when I update my ROM in the future.
Thanks again for the help!
Get titanium backup FTW.
BANG! from my shooter...
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.