Related
Dear Xda's
I Have An DHD, i tried for te first time to Flash/Root/S-OFF/HBOOT and changing ROM. it went not good
Yesterday i have flashed new rom, as it said on multiple thread in here, but today i dared to change kernel on my phone (i like car tuning, so i tryed tuning my phone
But now, i came to the point of no return(for me). My phone will only show HTC logo on the white backround, thats it, no bootloader, no recovery noting... I ave
read every thread abour Rom/Root/S-Off, Eng S-OFF, i'm sure every thing. I can only turn the phone, by taking the battery off... I have formated my SD card, because of i thought that i ave used CMW partition, before the fix...
And now i will be glad with a stock Rom, Kernel a.s.o...
Please help me, some one... i really don't know what to do...
I so sure that i have read twise before starting to change stuff on my phone.
I had HTC HD2 before, and taht was much easier to flash...
Anis2002 said:
Dear Xda's
I Have An DHD, i tried for te first time to Flash/Root/S-OFF/HBOOT and changing ROM. it went not good
Yesterday i have flashed new rom, as it said on multiple thread in here, but today i dared to change kernel on my phone (i like car tuning, so i tryed tuning my phone
But now, i came to the point of no return(for me). My phone will only show HTC logo on the white backround, thats it, no bootloader, no recovery noting... I ave
read every thread abour Rom/Root/S-Off, Eng S-OFF, i'm sure every thing. I can only turn the phone, by taking the battery off... I have formated my SD card, because of i thought that i ave used CMW partition, before the fix...
And now i will be glad with a stock Rom, Kernel a.s.o...
Please help me, some one... i really don't know what to do...
I so sure that i have read twise before starting to change stuff on my phone.
I had HTC HD2 before, and taht was much easier to flash...
Click to expand...
Click to collapse
download full wipe from xda.. google it "full wipe 1.3 xda" put the zip in ur sdcard.. put the rom(watever rom ur using) in sdcard as well ..
now take battery off ur phone.. back in.. press and hold vol down + power key.. u will go into bootloader.. then click on recovery.. ur phone will boot into CMW recovery > install zip fro sdcard.. 1st do a full wipe.. then flash the rom again.. u will be fine
i'll try now, so happy some one can help, i havent sleept for hours
Else if that does not work ( when i try to boot into recovery that way my phone vibrates, shows a green light and does nothing.. )
connect the phone to your computer and in ADB type: " reboot recovery "
I agree with leather face, I haven't tried this method but I have heard this will solve your problem, when I had the same sort of problem I downloaded the ace stock rom the placed the file on my SD card then took my battery out then reinserted it & powered back on while holding down the volume down button then once in bootloader select fastboot then it will ask to load zip, select yes now it will say done, reboot then you should be back at the beginning again with a working phone start again from scratch but this time do a wipe from recovery and make sure you are using the correct clockwork with the correct rom ie clockwork 2.*.*.* with Cyanogen 6 & clockwork 3.*.*.* with Cyanogen 7 & then you should be just fine mate
now i've tried... it says it cant find recovery file? in CWM loader
it says wrong image...
edit: signature is wrong (or some thing like that) should i rename the .zip file?
or sould i generate a Goldcard for MD98IMG.zip?
Anis2002 said:
or sould i generate a Goldcard for MD98IMG.zip?
Click to expand...
Click to collapse
You'll only need a goldcard if your phone is branded.
With something like a T-Mobile Bootscreen or else.
The Filename should be PD98IMG.zip and it should be in the root folder of your SD.
i think i need to change my system recovery? right? please somewone confirm, if you know... i miss many calls, and dont have any back up phone
Anis2002 said:
i think i need to change my system recovery? right? please somewone confirm, if you know... i miss many calls, and dont have any back up phone
Click to expand...
Click to collapse
does anybody know how to flash CWM, not with ROM manager?
i hope some one will help...
Anis2002 said:
does anybody know how to flash CWM, not with ROM manager?
i hope some one will help...
Click to expand...
Click to collapse
Dude,DON'T PANIC!
Download the attached CWM 2.5.1.3 rar and unrar it.
Now,do you have ADB setup on your pc?If not,search for a guide(Google is your friend),there are many.Supposing you have ADB setup,place the downloaded CWM .img file inside the folder where fastboot is.Open CMD in windows(Type cmd in RUN on your start menu) and there type "cd" and navigate to the folder where fastboot is,like "cd C:/YourPc'sName/android/tools" without the quotes.If it changes folder(it will if you type everything correctly) type without the quotes "fastboot flash recovery recovery-clockwork-2.5.1.3-ace.img".The you will be able to boot in recovery through fastboot.
Else,you can use Fastboot commander which is supposed to have a nice GUI and make things easier,but I haven't used it.
Hope I helped!
FIXED,
Fith Fastboot commander (putting my phone in FASTBOOT USB)
Flashing CWM tool, after that I'm da king (Thanks to all, specially mimilover)
Installed Rom, kernel and now nunning 1300Mghz trying it out...
Hello there,
I'm slightly new to the forums, at least posting to them so if I'm in the wrong section or if I'm just not suppose to ask these questions... well... lend some expert advice and help me out!
I'm by no means an expert on rooting and flashing, pretty much every thing i have learned has been on my Optimus V, Nexus 7, and My latest device, HTC One V and i learned it all on these forums!
So my problem is... My HTC One V i have unlocked it and rooted it with a tool kit i found on here called "Hasoon2000's HTC One V All-In-One Kit" and all was well in the world. But now that i have rooted it I've grown bored with the device... after less than 24 hours of running stock rooted. And i've attempted to flash MIUI.us on my device as found on the developers website Now I've flashed many custom roms on my other devices, currently running Paranoid Android Beta 3 on my Nexus and Harmonia 2 (I believe) on my OV. But this phone has become quite the hassle. I'm running TWRP CDMA recovery and i Factory reset, wipe data, cache, dalvic (spelled correctly?) and it boots up to the MIUI boot logo then it goes to the usual Google start screen where you select language and set up your device... but... at that point it fails to do anything then boot loops back out and restarts the phone, and repeats... sometimes it won't even get out of the boot loop and it will just restart the phone... so i have used the RUU and reset the phone multiple times after this has occurred... If anyone could be of assistance or point me towards the correct forum it would be much appreciated!
I'm not totally sure what else could help anyone out there but it says S-OFF and i am unlocked and i have tried multiple roms and none of them have worked yet at all, the AOSP rom actually got to the home screen then restarted... this is getting quite frustrating and slightly irritating so if anyone could lend a helping hand I'd be much appreciative!
If you have a brand new phone it may have the ota already applied, which means none of the custom kernels will work, which means no JB roms.
robaho said:
If you have a brand new phone it may have the ota already applied, which means none of the custom kernels will work, which means no JB roms.
Click to expand...
Click to collapse
Okay but when i do the RUU or even initially it always gives me the option to do system update OTA once i turn it on the first time... and on all the different ROM threads it says you have to extract the "boot.img" and flash in fastbot... so i extract the rom onto the SD card then once i flash the rom I've tried rebooting to bootloader and on my computer with SDK tools running command "fastboot flash boot boot.img" and that never works, i've tried flashing the jellyboot5 kernel i've tried many many options and bricked my phone about 20 times in the first 24 hours of owning my device... Black Friday purchased!
Sorry i'm still getting used to these devices... this is my first HTC and it's been... very much a learning experience but i really wanna try out some new roms on better phones than the OV
the last OTA broke the Radio (-> v.0928) firmware
Basically you need to flash the pre-OTA RUU (radio version: 1.00.00.521_2) first...
Steps (on windoze):
1) Download the correct RUU for your device (available at tinyurl.com/dxrybx9)
2) Run the .exe, wait for it to open the first wizard screen.
3) Open a file explorer in c:\users\yourname\AppData\Local\Temp\New_Directory _With_Some_Hexadecimal_name
4) Locate `rom.zip`, copy to the root directory of your sd card, and rename it to PK76IMG.zip
5) Reboot to bootloader, connect usb, and `fastboot oem lock` in cmd shell, at which point it'll reboot
6) Get back to HBOOT, wait for it to notice PK76IMG, confirm, make a pot of coffee, check back in 5-10 minutes.
7) After reboot, phone should now show a 1.00.00.521_2 radio... re-unlock the bootloader in fastboot, re-flash TWRP or whatever, and you should be good to go.
mkgarrod said:
Okay but when i do the RUU or even initially it always gives me the option to do system update OTA once i turn it on the first time... and on all the different ROM threads it says you have to extract the "boot.img" and flash in fastbot... so i extract the rom onto the SD card then once i flash the rom I've tried rebooting to bootloader and on my computer with SDK tools running command "fastboot flash boot boot.img" and that never works, i've tried flashing the jellyboot5 kernel i've tried many many options and bricked my phone about 20 times in the first 24 hours of owning my device... Black Friday purchased!
Sorry i'm still getting used to these devices... this is my first HTC and it's been... very much a learning experience but i really wanna try out some new roms on better phones than the OV
Click to expand...
Click to collapse
master_c said:
Basically you need to flash the pre-OTA RUU (radio version: 1.00.00.521_2) first...
Steps (on windoze):
1) Download the correct RUU for your device (available at tinyurl.com/dxrybx9)
2) Run the .exe, wait for it to open the first wizard screen.
3) Open a file explorer in c:\users\yourname\AppData\Local\Temp\New_Directory _With_Some_Hexadecimal_name
4) Locate `rom.zip`, copy to the root directory of your sd card, and rename it to PK76IMG.zip
5) Reboot to bootloader, connect usb, and `fastboot oem lock` in cmd shell, at which point it'll reboot
6) Get back to HBOOT, wait for it to notice PK76IMG, confirm, make a pot of coffee, check back in 5-10 minutes.
7) After reboot, phone should now show a 1.00.00.521_2 radio... re-unlock the bootloader in fastboot, re-flash TWRP or whatever, and you should be good to go.
Click to expand...
Click to collapse
Okay so I just wanna make sure i understand all this... I'm basically doing the same thing that the RUU does? What does the RUU do outside of this? and i tried what you said and it never notices it and now when i boot up my phone it has no service and doesn't connect to the network....
master_c said:
Basically you need to flash the pre-OTA RUU (radio version: 1.00.00.521_2) first...
Steps (on windoze):
1) Download the correct RUU for your device (available at tinyurl.com/dxrybx9)
2) Run the .exe, wait for it to open the first wizard screen.
3) Open a file explorer in c:\users\yourname\AppData\Local\Temp\New_Directory _With_Some_Hexadecimal_name
4) Locate `rom.zip`, copy to the root directory of your sd card, and rename it to PK76IMG.zip
5) Reboot to bootloader, connect usb, and `fastboot oem lock` in cmd shell, at which point it'll reboot
6) Get back to HBOOT, wait for it to notice PK76IMG, confirm, make a pot of coffee, check back in 5-10 minutes.
7) After reboot, phone should now show a 1.00.00.521_2 radio... re-unlock the bootloader in fastboot, re-flash TWRP or whatever, and you should be good to go.
Click to expand...
Click to collapse
Oh and when i type the fastboot oem lock command it gives me this
Code:
C:\Fastboot>fastboot oem lock
... INFOLock successfully...
FAILED (status read failed (Too many links))
finished. total time: 0.271s
(Sorry for the awful format, I'm not used to actually taking part in a forum!) but regardless of the FAILED status it still says relocked... I'm not sure if that's a problem or not
You can ignore the error msg, I saw the same thing and the relock worked correctly. The RUU didn't flash the radio correctly when I ran the application, and I couldn't `fastboot flash radio` directly because of S-ON (or install the zip through TWRP), but when I copied the rom zip to PKIMG76 and installed it in hboot, I was able to flash the radio back to 0521_2, at which point I could run sick kernel and AOKP Jellybean without the bootloop (I originally documented it on this thread: tinyurl.com/cf2aq5n)
mkgarrod said:
Oh and when i type the fastboot oem lock command it gives me this
Code:
C:\Fastboot>fastboot oem lock
... INFOLock successfully...
FAILED (status read failed (Too many links))
finished. total time: 0.271s
(Sorry for the awful format, I'm not used to actually taking part in a forum!) but regardless of the FAILED status it still says relocked... I'm not sure if that's a problem or not
Click to expand...
Click to collapse
master_c said:
You can ignore the error msg, I saw the same thing and the relock worked correctly. The RUU didn't flash the radio correctly when I ran the application, and I couldn't `fastboot flash radio` directly because of S-ON (or install the zip through TWRP), but when I copied the rom zip to PKIMG76 and installed it in hboot, I was able to flash the radio back to 0521_2, at which point I could run sick kernel and AOKP Jellybean without the bootloop (I originally documented it on this thread: tinyurl.com/cf2aq5n)
Click to expand...
Click to collapse
Okay so if i put that pk76img.zip into my fastboot folder on my PC then run "fastboot flash pk76img.zip' will it do the same thing? most of my devices when i rooted them and flashed custom images It's never been this difficult and i've never had to actually use CMD which i'm enjoying learning these commands and stuff but it's starting to get on my nerves that i can't get it to work when i boot by phone up into Boot loader here's what is says
Code:
***UNLOCKED***
PRIMOC PVT SHIP S-ON RL
HBOOT-1.53.0000
RADIO-1.00.00.0521_2
eMMC-boot
May 14 2012,20:27:38
I'm not sure if any of that will help at all.. but my Network is fine now but i really don't know what to do next... it says S-ON which i believe might be the problem but i AM rooted..
You wouldn't need to `fastboot flash...`; just copy the file to the root directory of your SD card, make sure it's named "PK76IMG.zip" (possibly case sensitive), and when you enter HBOOT it should say "searching for PK76IMG... blah blah" until it finds the file, at which point you'll see a blue progress bar, and it'll eventually ask you to confirm installation after it verifies the file(s).
All that said, it looks like you already have the correct version of RADIO, so I'm not sure this will help, but it's probably worth a try, unless you're flashing the wrong kernel for MIUI...
mkgarrod said:
Okay so if i put that pk76img.zip into my fastboot folder on my PC then run "fastboot flash pk76img.zip' will it do the same thing? most of my devices when i rooted them and flashed custom images It's never been this difficult and i've never had to actually use CMD which i'm enjoying learning these commands and stuff but it's starting to get on my nerves that i can't get it to work when i boot by phone up into Boot loader here's what is says
Code:
***UNLOCKED***
PRIMOC PVT SHIP S-ON RL
HBOOT-1.53.0000
RADIO-1.00.00.0521_2
eMMC-boot
May 14 2012,20:27:38
I'm not sure if any of that will help at all.. but my Network is fine now but i really don't know what to do next... it says S-ON which i believe might be the problem but i AM rooted..
Click to expand...
Click to collapse
master_c said:
You wouldn't need to `fastboot flash...`; just copy the file to the root directory of your SD card, make sure it's named "PK76IMG.zip" (possibly case sensitive), and when you enter HBOOT it should say "searching for PK76IMG... blah blah" until it finds the file, at which point you'll see a blue progress bar, and it'll eventually ask you to confirm installation after it verifies the file(s).
All that said, it looks like you already have the correct version of RADIO, so I'm not sure this will help, but it's probably worth a try, unless you're flashing the wrong kernel for MIUI...
Click to expand...
Click to collapse
Well I'm not really sure on the rules of forums... about posting links to other things like that... but i think my problem is a kernel issue... I have the JellyBoot5.zip... that everyone was talking about and even someone on that other forum you posted said something about it... but... maybe i'm just doing that wrong... do i go into TWRP recovery... flash the Jellyboot5.zip then reboot to bootloader, and on CMD run "fastboot flash boot boot.img" (which i extract the boot.img from the jellyboot5.zip...) is that correct? I'm really trying to NOT be illiterate on these things but i'm at a total loss... i may just stick with root and stock if i can't figure this out soon.
I would try the v2.0.0 kernel (tinyurl.com/d8xknzb) ... I actually had a (different) bootloop problem after installing the jellyboot5.zip in TWRP, so maybe this kernel will do the trick.
mkgarrod said:
Well I'm not really sure on the rules of forums... about posting links to other things like that... but i think my problem is a kernel issue... I have the JellyBoot5.zip... that everyone was talking about and even someone on that other forum you posted said something about it... but... maybe i'm just doing that wrong... do i go into TWRP recovery... flash the Jellyboot5.zip then reboot to bootloader, and on CMD run "fastboot flash boot boot.img" (which i extract the boot.img from the jellyboot5.zip...) is that correct? I'm really trying to NOT be illiterate on these things but i'm at a total loss... i may just stick with root and stock if i can't figure this out soon.
Click to expand...
Click to collapse
master_c said:
I would try the v2.0.0 kernel (tinyurl.com/d8xknzb) ... I actually had a (different) bootloop problem after installing the jellyboot5.zip in TWRP, so maybe this kernel will do the trick.
Click to expand...
Click to collapse
Okay so i wanna make sure i'm doing this right... I put that zip i just downloaded into my sd card on the root of the drive... then go into recovery... and flash it? do i wipe anything? anything at all? do i need to flash the boot.img? if i DON'T flash a custom rom right now also... will that mess up my phone since stock is running ICS?
It's a JB kernel so it probably won't work with an ICS rom, but I can't say I've tried it. And yeah, you need to flash the boot.img, and also install the zip in recovery, but you shouldn't need to wipe anything if you're just changing kernels (although there isn't much point unless you're installing a JB rom at the same time...)
mkgarrod said:
Okay so i wanna make sure i'm doing this right... I put that zip i just downloaded into my sd card on the root of the drive... then go into recovery... and flash it? do i wipe anything? anything at all? do i need to flash the boot.img? if i DON'T flash a custom rom right now also... will that mess up my phone since stock is running ICS?
Click to expand...
Click to collapse
master_c said:
It's a JB kernel so it probably won't work with an ICS rom, but I can't say I've tried it. And yeah, you need to flash the boot.img, and also install the zip in recovery, but you shouldn't need to wipe anything if you're just changing kernels (although there isn't much point unless you're installing a JB rom at the same time...)
Click to expand...
Click to collapse
Well as soon as i get back to my house I'm going to try this out and try reflashing the MIUI rom which is JB i believe and hope it works! if not... I'll be using that RUU tool again... I think i've been on that more than i have my new phone!
Why did no one report this thread? Obviously I'll see it eventually, but come on guys/gals!
Moved to Q&A.
Hi Guys,
I have a big problem! I forgot to flash the boot.img of "Jelly Bam 7.2.1" - it all ended in total chaos. I will try to describe everything I did, feel free to ask any further on points that seem to be more relevant than I thought.
To let you know: I have knowledge of flashing / custom roms and all that good jazz in general (with other phones before), but I am a total noob concerning all the One X specific stuff...
1.) rooted my One X. No problems so far, stock rom working fine after doing so, HBoot says "UNLOCKED" at the top, so no problems here.
2.) downloaded the custom ROM (JellyBam, endeavoru, 7.2.1), checked MD5, so no problems with the download - copied it to my phone
3.) went into recovery without fastboot, just the way via hboot and did the following in that order: "wipe data/factory reset", "wipe cache partition", formatted "/cache", formatted "/system", formatted "/data", "wipe dalvik cache", flashed the zip "jelly-bam-blabla.zip"
4.) tried to boot, which obviously did not work, because I forgot flashing the boot.img.... but in concrete: the phone first showed the normal "HTC"-Screen, then the JellyBam loading screen came on the screen, then the "Android Welcome Screen" showed up. after 0,5 seconds a pop-up came up saying "Unfortunately, System UI has stopped." and some 0,5 seconds after another pop-up places itself right over the other one. it says "Unfortunately, the process com.android.phone has stopped."... I tried to hit "OK" but it always came up again within 0,5 seconds or shorter.
5.) I went into hboot from there, because my first idea was, that the problem could have been me having forgotten the "fix permissions" after flashing the rom... so i did all the cache / formatting stuff again, flashed the zip again and then fixed permissions.
6.) tried to boot, exactly the same situation as described in "4"
7.) the boot.img-stuff came in my mind. slapped myself in the face several times. the "you should always fastboot flash your recovery if you want to flash anything on your phone"-advise also came in my mind. hurt my face for some more seconds.
8.) went into hboot again, then "fastboot", connected to my MBP and firstly tried to fastboot flash cwm-recovery. but the terminal said that my HOX is too low on battery life...
9.) the part I actually can't remember correctly. tried different advises on how to load the battery without having a rom up and running (from xda devs mainly) - which all did not work but somehow resulted in my HOX not even letting me boot up normally anymore. a (re)boot just kicks me directly into cwm recovery.
10) my battery went totally empty. and now the scary part i really do not understand begins: I connected my HOX via the usb cable to a power adapter. the orange light first started blinking, then it stood on for about 3 hours - I did not touch it. after these about 3 hours the device automatically booted into cwm recovery. i went into hboot which resulted in the normal error messages while connected via usb to a power adapter or a computer, so i unplugged the cable and rebooted recovery. again went in hboot, which now tells me I am too low on battery to flash anything. Because the orange light is only on in cwm recovery I thought that the phone charges there (I also read that, but the people said it would be veeery slow), so I tried to keep it in recovery. the problem is: it automatically shuts down after 20-30 minutes... I tried to avoid that as long as possible, always just hitting volume down once every 20 minutes - but even after doing that for about 6 hours, hboot still told me my battery is too low...
I really do not know what to do. I am never able to stay at home for longer than these 6 hours, so I do not know how I might get the battery high enough in order to flash the boot img or the zip in cwm again...
Please help me you genius people out there!
P.S.: The nerd video at registration is nicely done. I really like it. And I hope I did not overlook a thread that could solve my problem...
I'm not sure this is correct but I'd let it charge then in fastboot erase cache flash the boot then erase fastboot cache again.
A
Htc One X Viper 3.4.2
frontinsomething said:
Please help me you genius people out there!
Click to expand...
Click to collapse
At your service!!
Use this lil script to charge your device. It reboots the handset over and over again causing it to build up voltage. Once it prints out ~3750mV or higher, you should be good to flash.
http://forum.xda-developers.com/showthread.php?t=1658084
http://forum.xda-developers.com/showthread.php?t=1658084
Make this little script and execute it as a batch
Flash this recovery - http://download.clockworkmod.com/recoveries/recovery-clockwork-touch-5.8.4.0-endeavoru.img
Download the stock rom from here - http://forum.xda-developers.com/showthread.php?t=1546970
Fastboot flash the boot.img and `fastboot erase cache`
Wipe data and flash the rom.
You`ll at at least be in a working rom.
P.s you dont have to flash recovery all the time. Flash it once and leave it.
Iceax123 said:
I'm not sure this is correct but I'd let it charge then in fastboot erase cache flash the boot then erase fastboot cache again.
Click to expand...
Click to collapse
Yeah, my plan looked similar. The problem is you forgot the first stept. What I need is to
1.) somehow charge my phone to an adequate degree
2.) fastboot erase cache / flash boot.img / erase cache
3.) flash the zip again (just to make sure)
Can you help me for step one of that?
As described before the charging does not really work. In cwm it charges freakin slow, in hboot it does not seem to at all (I am not quite sure 'bout that)...
come on guys, you are way too fast in answering I knew why I like this place
I guessed people would come up with the script. the point is, that I tried that and failed at it... can somebody exactly tell me how to to that on Mac? I failed at it... (see step 9)
frontinsomething said:
come on guys, you are way too fast in answering I knew why I like this place
I guessed people would come up with the script. the point is, that I tried that and failed at it... can somebody exactly tell me how to to that on Mac? I failed at it... (see step 9)
Click to expand...
Click to collapse
I don't own a mac but it's really similar to Linux, so.....
Name it .sh instead of bat. And mark it executable by going to terminal as root and typing
Code:
chmod a+x [path_for_the_file]
Or use some gui to set it executable.
Then it should work by simply double clicking.
Good luck:good:
EDIT If fastboot commands different on mac, for example "fastboot-mac flash blablah", you need to modify the script accordingly.
TToivanen said:
I don't own a mac but it's really similar to Linux, so.....
Name it .sh instead of bat. And mark it executable by going to terminal as root and typing
Code:
chmod a+x [path_for_the_file]
Or use some gui to set it executable.
Then it should work by simply double clicking.
Good luck:good:
EDIT If fastboot commands different on mac, for example "fastboot-mac flash blablah", you need to modify the script accordingly.
Click to expand...
Click to collapse
Nice! At least the script works! Although it runs since 20:30 now and still only brought me up about 1mV... but let's see where I get. I will try to do all the good jazz if I get over 3680 - I will tell you as soon as it worked or if it did not.
See you later and thanks for the help so far!
frontinsomething said:
Nice! At least the script works! Although it runs since 20:30 now and still only brought me up about 1mV... but let's see where I get. I will try to do all the good jazz if I get over 3680 - I will tell you as soon as it worked or if it did not.
See you later and thanks for the help so far!
Click to expand...
Click to collapse
Nice ! Fingers crossed
Sent from my IceCold One X
TToivanen said:
Nice ! Fingers crossed
Sent from my IceCold One X
Click to expand...
Click to collapse
Just noticed, that I also need/want to flash the zip again - how much mV would I need for that?
Once you have flashed the boot image (fastboot batt warning vanished), you'll be good to flash the zip also.
Sent from my IceCold One X
You Are Epic, Guys!
Thank you for your help, not only, but mainly TToivanen!
Everything worked out fine! ROM is now up and running! yippieh!
Nice !
Enjoy the new ROM
Sent from my IceCold One X
Hello all, for the past few days I have been trying to install android 4.0 ICS on my HTC Wildfire S CDMA phone, currently connected to youtube. on one instance I accidently formatted my backup so at this point im prettty scared.
I have already tried full resets, clearing memory, batttery, cache etc. I am stuck using CWM because TWRP touch screen doesnt seem to work at all. All help will be greatly appreciated. thank you.
I have also tried most of what is on other forums such as kernel update, redownloading.
I also find that if while installing, the phone restarts on its own. at first I thought the installation was done but to my dismay, it wasnt....
I'm not sure I can help but I would suggest you try to clarify what you are asking and trying to do. You state that you're doing an install of ICS 4.0 on your WFSc. I don't think any WFS, gsm or cdma got the ICS update unless you mean as Cyanogen Mod 9 or some other ROM? You also said something about being connected to You Tube now...that doesn't make sense.
That being said, if you meant you were trying to install the ICS theme then you might get a quicker more focused response if you posted in this forum:
http://forum.xda-developers.com/showthread.php?t=1504935
Clarification
I got a second wildfire s from my cousin. exact same model and was bought the exact time as my current one and it successfully installed the cynanogen 9 with the only failure being that the touchscreen is inoperable but I will work on that another time. also when I said connected to youtube, I meant I tried to look on youtube for fixes but never found one. anyway the main problem is that my phone stops midway through the "installin updates" to either freeze or restart to a blank operating system "meaning its stuck on the htc logo". I hope this clarifies what I was trying to convey in the previous post and I promise to keep a closer eye for any other messages. I also thank you for answering.
Instead of potentially aggravating you with 20 questions, I'll just briefly run thru the steps, FWIW. I see you mention CWM.
-So, you probably unlocked the booloader at HTC dev and are S-on.
-Installed CWM, so you have the adb files and htc sync on your computer.
-Rooted, although flashing CM will root.
-Battery charged.
-Downloaded the correct CM9 for your WFS, i.e., gsm or cdma, and moved it to your sd card after extracting the boot.img file and putting it into the folder on your computer with the adb, fastboot, etc. files for later.
-Booted into CWM and wiped the cache, dalvik-cache, and data/factory reset.
-Selected the CM9 file on your zip, and started the install.
I'm a little unsure what you are saying happens next, but normally you would:
-after CM9 is flashed go to fastboot in the bootloader or reboot into recovery>fastboot.
-Attach the USB cable from the computer to the phone and with the command prompt at that folder where you have those adb files type:
fastboot flash boot boot.img and press enter
-Then reboot and CM9 should load...unless now both of us have missed something ::yikes!::
For some reason most guides seem to skip that part about extracting the boot.img file and flashing it after the ROM install, which is needed if the phone is still S-on. Typically seen when stuck on the HTC logo after flashing the ROM and rebooting, and you mentioned being stuck on the HTC logo. If the phone is S-off, the boot.img gets flashed from within the ROM during the install.
Hope I found the missing step and that it installs successfully.
romemo two
MiCeltic said:
Instead of potentially aggravating you with 20 questions, I'll just briefly run thru the steps, FWIW. I see you mention CWM.
-So, you probably unlocked the booloader at HTC dev and are S-on.
-Installed CWM, so you have the adb files and htc sync on your computer.
-Rooted, although flashing CM will root.
-Battery charged.
-Downloaded the correct CM9 for your WFS, i.e., gsm or cdma, and moved it to your sd card after extracting the boot.img file and putting it into the folder on your computer with the adb, fastboot, etc. files for later.
-Booted into CWM and wiped the cache, dalvik-cache, and data/factory reset.
-Selected the CM9 file on your zip, and started the install.
I'm a little unsure what you are saying happens next, but normally you would:
-after CM9 is flashed go to fastboot in the bootloader or reboot into recovery>fastboot.
-Attach the USB cable from the computer to the phone and with the command prompt at that folder where you have those adb files type:
fastboot flash boot boot.img and press enter
-Then reboot and CM9 should load...unless now both of us have missed something ::yikes!::
For some reason most guides seem to skip that part about extracting the boot.img file and flashing it after the ROM install, which is needed if the phone is still S-on. Typically seen when stuck on the HTC logo after flashing the ROM and rebooting, and you mentioned being stuck on the HTC logo. If the phone is S-off, the boot.img gets flashed from within the ROM during the install.
Hope I found the missing step and that it installs successfully.
Click to expand...
Click to collapse
Thanks again for the reply. you have given me quite a lot of information and 90% of it was correct and dead on, but where you misunderstand is that while using CWM and flashing ANY Rom onto the phone, it either freezes at "installing updates" or restats if it ever gets to the next step. The confusing part of this is that the other phone which is the exact same model was able to be flashed with all the roms that I tried on my own phone with no problem.
To make things easier. after this I will adress the phones differently:
My phone (Not working Flash) is Marvelc 1
My cousins phone (working flash) is Marvelc 2
This is particularly challenging because you keep emphasizing that you are doing exactly what (you did?) on the other WFS, and I presume they have identical hboots (which they'd have to if you unlocked using htcdev). You also say that you re-downloaded the different files (recovery, CM9) and double checked that their for the MarvelC, and re-did then, re-tried, re-tried, re-tried...and I'm presuming that when you were re-trying that you didn't skip any steps, like the wipes. Oh, and most of all that everything worked on this phone before you started unlocking - flashing the recovery - and rooting. I thought about htc sync and adb, but the fail point is not when the computer is hooked up.
So all that being re-hashed, I'm looking for something concrete, a clue from what you've said or hinted at and right now I'm curious about your SD card. That is most likely not common to both phones and you did say, "on one instance I accidently formatted my backup..." Did you get everything formatted OK with no errors...that SD especially, as Fat32, shouldn't need an ext partition at this time. It could be corrupted and failing at some point when it's unpacking CM9, or whatever. You might re-do formatting that, including doing it on a computer if you have an adapter or a card reader, if not in CWM. It wouldn't hurt to put it in another phone and see if you can read it there and/or on a computer when that other phone is hooked up as a disk drive. Then put a fresh copy of whichever CM9 your flashing on it and try EVERYTHING one more time (back in your phone of course) ::haha:: be sure to leave the battery out for at least 30 sec. after all this and before trying the flash just to be sure any residual static in the phone has dissipated.
If it fails again, leave on and hook up to the computer and run: "adb logcat" from the prompt where you have your adb files and see if it will show you anything. You can exit logcat with the Ctrl + C keys. What do you think?
Oh, and while you're doing all that, who's CM9 are you trying to install. Do you have a link so I can look at it out of curiosity?
It took me awhile to absorb all that but after trying all.those steps,.there was no progress. Furthermore the microsd card I use is for both of my HTC's. And lastly the adb logcat or any adb script for that matter won't work unless the phone is in debug mode with a working o.s.
Thanks for hanging with me and I look forward to your next suggestion.
Sent from my HTC-PG762 using xda app-developers app
I wasn't sure whether there would be some kind of script running in a buffer of the install that might be captured with something like: logcat -b event > /sdcard/logcat.txt
so it was a shot in the dark and I don't know what's left, but perhaps someone else that is reading the post might have some ideas, or experience with this specific issue and jump in with a solution.
I was writing a macro once and couldn't get it to work and spent too much time over 3 days trying to figure it out. When I finally asked someone else to look at it, I was just missing a semi-colon or some one simple thing. You sound pretty knowledgeable, sorry I couldn't be the second set of eyes to come up with the missing thing. If I can think of anything more, I'm subscribed to this thread and I'll surely suggest it.
Thank you for trying, I hope to find an answer soon enough.
Sent from my HTC-PG762 using xda app-developers app
okay so heres what happened.
I have an international htc one x that is indeed rooted with no roms installed.
I did create a back up and then tried to install the MIUI rom (but I dont really know where that is on my phone. I know I made one with rom manager. I dont have any backups on my computer though)
It worked, however, it didnt have wifi or data signals so i went back to try again.
I opened my bootloader screen. For the record, it is unlocked and hboot is version 1.73 if that helps.
I wiped cashe/data/delvic everything and even factory reset and installed the MIUI RD rom now hoping it would have a difference.
The darn thing got stuck on the MIUI bootloader for hours.
I did the same thing again a few times, sometimes in different orders and then it passed on and another screen came saying 'starting apps'. That got stuck for hours too.
Now I don't have any other roms on my phone, just the MIUI RD. The original miui just vanished too, i dont see it anymore. Also, when I put my USB wire to the phone and connect it to the pc, I cant transfer newer files into it. So this is all I have access to on my phone apparently.
I tried flashing a boot.img and a couple kernels but no luck. I've been trying to do this for all day and this is my first time so I don't know much about it.
I've been googling and somethings say to open cmd and type but i keep getting 'fastboot is not recognized as an internal or external command'
Currently, its not stuck at either the MIUI screen or the Starting Apps. but just the HTC logo screen and not going past.
I don't really want to install any new roms considering i've worked really hard to get this to work and I really want it now more so.
How do i fix this? I want to use this rom.
flash philz recovery (http://forum.xda-developers.com/showthread.php?t=2240646), usb mounting should work on that, then:
steps to install ROM
1. bootloader version should be 1.3x
2. copy ROM to SD Card
3. copy boot.img INCLUDED in the ROM zip to fastboot folder
4. flash the boot.img in fastboot
5. in recovery, wipe system/data/cache/everything
6. flash rom
7. restart
but how exactly do i put it on my phone? my computer isnt detecting my phone when i connect it? im sorry im not exactly an expert on this.
Go to recovery - mounts and storage - hook up the usb cable - tap the last option in the mounts and storage list and wait a few minutes. It won't be mounted instantly
ok i flashed the philtz recovery but when i flash the boot.img it says:
Finding update package
Opening update package
Installing update
installation aborted
for reference: http://forum.xda-developers.com/showthread.php?t=1957490
thats the rom i used and i flashed the boot.img flasher thats right above the download link
edit: also i tried just flashing the rom again and im still stuck on the HTC screen.
its not even going to the miui screen or starting apps anymore. :[
Boot.img must be flashed via fastboot. Not via recovery !
ok, i looked up how to fastboot, downloaded sdk files and i moved the boot.img into the fastboot folder and i opened command prompt there and wrote fastboot flash boot boot.img but i keep getting:
'fastboot is not recognized as an internal or external command'
what did i miss?
EDIT: ok, so the fastboot folder i got from the page didnt work so i used a different fastboot folder, dragged the .boot there and now it worked! finally passed the screen and wifi is connecting!
thank you!
Good, thanks to @tomascus. He summed it up real nice
Cheers