Develop Bugs

[Q] HTC ONE V - Cyanogen 9 RC2 - Help with install

Hi everyone,
I have tried searching but was not able to find what I was looking for.
I would like to install Cyanogen 9 RC2 on my phone. http://forum.xda-developers.com/showthread.php?t=1757323
I currently have an early version of CM10 GSM Jelly Bean on there, which is missing some of the core features (they will come with time!). According to the instructions though, the zip file is supposed to contain a boot.img file to flash it.
Guessing its my newbieness, but, where do I get this file? How do I extract it from the archive to flash with?
Code:
Rom Installation:
Flash boot.img in fastboot
FACTORY Reset
[B]Flash the ROM[/B]
reboot
boot rom
reboot back into recovery
Flash GApps
Reboot into the system (first boot will take several minutes)
Thanks muchly! As well, if someone can point me to a handy user guide for this kind of thing, that would be awesome. As of now I'm only barely able to finger this stuff out. Took me over an hour to unlock my phone haha

:/
U READ THE INSTRUCTIONS WRONG :/
""DONT FLASH THE BOOT.IMG INSIDE THE ZIP""
U can simply use KISS kernel open :
http://www.mediafire.com/?7hq6ikra7w0kt
open the 1 wid cm9 written in it ..rename it to boot.img ...
this kernel has several advantages lik sweep2unlock and usb host <3

Aninomus said:
U can simply use KISS kernel open :
open the 1 wid cm9 written in it ..rename it to boot.img ...
this kernel has several advantages lik sweep2unlock and usb host <3
Click to expand...
Click to collapse
Interesting. So, I take this new boot.img and toss it in my /FastLoader folder, patch it, then fire up my CWM Recovery, load zip from SD and voila?
(I can't check it out now, MediaFire is blocked at work)

:/
read the instructions 1000 times :/
As of now i am out of tim wen free i'll giv u the whole instructions

Aninomus said:
U READ THE INSTRUCTIONS WRONG :/
""DONT FLASH THE BOOT.IMG INSIDE THE ZIP""
Click to expand...
Click to collapse
Sorry, new to this stuff. Please don't hate!
I had just installed CM 10 which did require a boot.img flash, so I was a bit confused with the "Flash the ROM" portion of the install.
So with CM 9, I just plop the zip on my phone's SD, fire up recovery, load, bob's my uncle?

You need to flash a kernel for cm9 go to the KISS kernel thread http://www.mediafire.com/?7hq6ikra7w0kt pick a kernel and flash it via fastboot, just like you did the CM10 kernel, boot into recovery ,wipe data, cache and format system, flash the CM9 ROM and the Gapps, reboot!

rockstar_26 said:
You need to flash a kernel for cm9 go to the KISS kernel thread http://www.mediafire.com/?7hq6ikra7w0kt pick a kernel and flash it via fastboot, just like you did the CM10 kernel, boot into recovery ,wipe data, cache and format system, flash the CM9 ROM and the Gapps, reboot!
Click to expand...
Click to collapse
Yey! Thanks man. Exactly what I needed. I'm installed and up/running.
Having a bit of an issue with the SD card, it won't detect it. Card works fine in my computer; tried another one as well. Tried mounting/unmounting, rebooting, violently protesting in the streets, nothings working.
I'm not even sure where to begin fixing that. Any suggestions? Thanks!

[Q] Flashing a rom...

Extract Rom and grab the boot.img
Make a Full Wipe (Factory Reset,System,Cache,and Davlik Cache)
Install ROM
Fastboot flash boot boot.img
REBOOT
Enjoy!!!
With these instructions *i've never flashed a rom before* I should download the rom, extract the boot.img where I have the fastboot.exe on my computer, do full wipe, put the zip file on my sd card and install in recovery, reboot and go into fastboot mode and flash the image, and then reboot again right? Or am I missing something? Sorry, as I said i've never done this before.

Yeah that's right but flash the kernel (boot.img) first ...because you may get stuck in a bootloop ...so flash kernel first

Ya too bad each step has very specific things you need to do and it takes quite a bit of time sifting through these forums to understand just wtf is going on.
This might help flashing if you've rooted already:
http://www.youtube.com/watch?v=qNR84FST1KQ&feature=plcp

donhashem.dh said:
Yeah that's right but flash the kernel (boot.img) first ...because you may get stuck in a bootloop ...so flash kernel first
Click to expand...
Click to collapse
atonz said:
Ya too bad each step has very specific things you need to do and it takes quite a bit of time sifting through these forums to understand just wtf is going on.
This might help flashing if you've rooted already:
http://www.youtube.com/watch?v=qNR84FST1KQ&feature=plcp
Click to expand...
Click to collapse
Thanks for your help. I actually went ahead and tried mine first, to see because i'm impatient and it worked totally. Thanks everyone!!!

Ok, I'm having issues with this installing ROMs/kernels.
I entered fastboot
I flashed the boot.img for the kernel I want
I toggled to hboot
I went into recovery (twrp 2.2.0)
I did wipe -> Factory Reset, Cache, Dalvik Cache, System
I installed the zip for ROM I want to use [found here]
I flashed the zip for the kernel I want to use (to install the libs) [found here]
wiped dalvik/cache again
reboot system
Now my phone just bootloops. Not sure what I did wrong.
I should mention I did get it to boot once back when I first installed the ROM because I did a normal reboot not a reboot into fastboot (was doing the install the ROM then the boot.img approach at the time) and hadn't installed any boot.img (still had the stock) but ever since I overwrote it all i get is bootloops.
Also, I even tried the same steps using the boot.img included with the ROM as opposed to the other one.
To make things worse, backups are almost useless because with the phone being S-ON even if the boot.img is being backed up, it not getting restored. A point made extremely obvious by the fact that it still bootloops after restoring my backup.
I am currently running the RUU but am hesitant to try and install any ROMs without some idea of what I did wrong.
Any help is appreciated.
-----EDIT------
Ok, I think the problem was the recovery I used. I installed the CDMA TWRP from the OneV tool, and one linked in the cdma development thread and a couple CWM version found there as well. But what seemed to work was getting TWRP straight from the source. After running the RUU I installed version 2.3.1.0 and repeated the steps using the boot.img included in the ROM and it worked. If I'm feeling adventurous later I'll try my luck with the other kernel lol.

[Q] MIUI for V One Help! (What in hells name am I doing wrong?!)

Hey there;
Firstly, thanks for your great efforts on the ports of your roms and consistent, useful forum help.
I appreciate that you probably get a load of these threads but I could really use some help with the installation of the ROM, as I've had a load of problems trying to install it.
I am attempting to install the MIUI rom (http://forum.xda-developers.com/showthread.php?t=1797515), and I am coming from the original software that comes with the device.
I have an unrooted One V, coming from the base OS and kernel. Currently, I can't get past the Jellybean Android screen (getting stuck on starting apps), and usually I can't even get past the MIUI screen at all. Here are the steps I've taken;
- I downloaded this kernel: boot-TK-USB-201302150054 from this thread: http://forum.xda-developers.com/show....php?t=1765687 and flashed it in fastboot, twice.
- Then launch into recovery, follow the instructions on your thread (format all apart from SD), and go ahead and install the .zip.
- Clear Delvik, clear Battery and Fix permissions, then proceed to reboot in an attempt to get in. At this point it hangs on MIUI screen for up to 5 minutes.
- I then try re-flashing the kernel in fastboot again. Still no help.
- I then try and reinstall the .zip from the SD card, and still no improvement.
I imagine I'm doing something very wrong, but I can't work out what it is and it's driving me crazy.
Can you help?!
Thanks in advance, Reasoner.

you are installing an older rom version which has no support..and is old

paarthdesai said:
you are installing an older rom version which has no support..and is old
Click to expand...
Click to collapse
Any chance you good point me in the right direction for an newer version?
Also, am I doing all the steps right?

paarthdesai said:
you are installing an older rom version which has no support..and is old
Click to expand...
Click to collapse
Okay, I have now attempted to install YOUR version of MIUI, and I'm still not having any luck.
I have;
- Flashed the boot.img using the one you suggest on your thread (twice)
- Booted into Recovery, cleared all caches excluding SD
- installed from .zip in CWM Recovery
- Cleared Delvik
On reboot I still get stuck on the MIUI screen.

Reasoner said:
Okay, I have now attempted to install YOUR version of MIUI, and I'm still not having any luck.
I have;
- Flashed the boot.img using the one you suggest on your thread (twice)
- Booted into Recovery, cleared all caches excluding SD
- installed from .zip in CWM Recovery
- Cleared Delvik
On reboot I still get stuck on the MIUI screen.
Click to expand...
Click to collapse
Ignore this, tried again and got through! Thanks a bunch!

Some advice needed!

tl;dr: What happens if I upgrade to CWM 6 after having used Darkside Superwipe on CWM 5?
And now the long explanation of what happened:
I have a Telus T989D, and I had installed the stock Telus JB ROM from this thread: http://forum.xda-developers.com/showthread.php?t=2343748
I previously had CWM, but as per the instructions in the thread I installed TWRP, ran the Infamous Superwipe zip file, and then proceeded to flash the ROM.
Then today I decided to install CM 10.1. The first thing I did was flash CWM 6.x (I forget the exact version, but it was the latest one) from ODIN. Then I downloaded the latest stable build (CM 10.1.2). I then ran the Infamous Superwipe zip file again, and flashed CM 10.1. The result was that the phone would get stuck on the Cyanogenmod circle logo. I did some Googling and found out some people who had bootloops after installing Cyanogenmod, and it was suggested that this was due to a bad wipe, and that using Darkside Superwipe would fix the problem. So I proceeded to give Darkside Superwipe a try... Of course at the time I hadn't realized that 1) What I had was not actually a boot loop (it wasn't rebooting, it was just stuck at the logo), and 2) that Darkside Superwipe should not be used with CWM 6. After flashing the Darkside file, my CWM 6 would load up but would fail to flash ANY zip file that I selected (it would just get stuck on the first line, "Installing xxx.zip"). It would also fail to wipe the /cache partition (would freeze at "wiping /cache partition").
After soft-bricking my phone by trying to flash a different recovery from Heimdall, I ended up following a guide on this forum to flash the stock Gingerbread ROM from Odin. I then flashed CWM 5.0.2.7, did the Darkside Superwipe, installed CM 10.1, and now thankfully the phone works.
My question is... Does anybody know what happened here? And any ideas what will happen if I try to upgrade my CyanogenMod later on? Will I have any issues running CWM 5.x with CM 10.1 or 10.2? I'm a bit afraid of updating to CWM 6 since I have no idea what the result will be.
I later learned that Infamous Wipe is only to be used with TW-based 4.1.2 ROMs, since it adds a preload partition. Did I end up somehow messing up my partitions by using the Infamous & Darkside Superwipe files?
Sorry for the long post... I just figured I should give as much information as possible! I'd really appreciate it if anybody has an explanation for what happened (messed up partitions?) and how to fix it!

OK so what u need to do first is stop flashing all these recoveries, DL twrp2.6.1.0 and flash that with Odin, stay with this recovery, cwm is OK but not updated frequently enough to keep up with newer flashing scripts, now don't use superwipe/super cache wipes with twrp, they will cause loops, do a full wipe with twrp, mount to USB move all files off SD cards and format them, replace any/all files from SD card that u want, now flash ROM, flash gapps, reboot and let sit ten min, this should fix ur issues, as far as what happens, u used superwipe scripts on 6.x+cwm, those scripts were meant for cwm5x, it'll loop every time...
Sent from my SAMSUNG-SGH-T989 using XDA Premium 4 mobile app

soupysoup said:
OK so what u need to do first is stop flashing all these recoveries, DL twrp2.6.1.0 and flash that with Odin, stay with this recovery, cwm is OK but not updated frequently enough to keep up with newer flashing scripts, now don't use superwipe/super cache wipes with twrp, they will cause loops, do a full wipe with twrp, mount to USB move all files off SD cards and format them, replace any/all files from SD card that u want, now flash ROM, flash gapps, reboot and let sit ten min, this should fix ur issues, as far as what happens, u used superwipe scripts on 6.x+cwm, those scripts were meant for cwm5x, it'll loop every time...
Sent from my SAMSUNG-SGH-T989 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks soupysoup! I will do that the next time I update the phone. And just another quick question: do you know if TWRP is safe to use with CyanogenMod (since it seems that they recommend CWM)?

Faruk88 said:
Thanks soupysoup! I will do that the next time I update the phone. And just another quick question: do you know if TWRP is safe to use with CyanogenMod (since it seems that they recommend CWM)?
Click to expand...
Click to collapse
Yes, actually I reccomend twrp to everyone for every ROM, the only way a ROM could be recovery specific would be if the ROM called for specific flashing scripts a certain recovery used/ran but twrp is updated a lot and always uses the newest flashing scripts in there builds, plus the recovery itself is very user friendly, the newest version is 2.6.1.0, go check that out n fully 4.3 compatible
Sent from my SAMSUNG-SGH-T989 using XDA Premium 4 mobile app

soupysoup said:
Yes, actually I reccomend twrp to everyone for every ROM, the only way a ROM could be recovery specific would be if the ROM called for specific flashing scripts a certain recovery used/ran but twrp is updated a lot and always uses the newest flashing scripts in there builds, plus the recovery itself is very user friendly, the newest version is 2.6.1.0, go check that out n fully 4.3 compatible
Sent from my SAMSUNG-SGH-T989 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Perfect, thanks! Just one last question, then: In your previous post you said to flash TWRP through Odin. Does it matter if I flash through Odin or if I just download Goo manager and switch to TWRP from there? Which one of the two options is safer/better?

Faruk88 said:
Perfect, thanks! Just one last question, then: In your previous post you said to flash TWRP through Odin. Does it matter if I flash through Odin or if I just download Goo manager and switch to TWRP from there? Which one of the two options is safer/better?
Click to expand...
Click to collapse
U can use goo manager if u want, but I will say this, sometimes too can cause soft bricks, in which case u would need Odin to recover , so in my professional opinion I would suggest using Odin from scratch
Sent from my SAMSUNG-SGH-T989 using XDA Premium 4 mobile app

[Q] Rom Question

I'm having issues flashing multiple roms of the 4.x.x Roms. The only rom so far I have been able to install and actually run on my phone is TweakWiz V2. I have tried many other roms and they just stay in a boot loop screen. Examples are with the Avatar rom it just stays on the mask an keeps going and going. I have tried CyanogenMod/Cyan Kang an it just stays on the Circle with the bar going around on the inside.
I am running the TWRP Touch Recovery. I also have the latest Radio update and everything else is updated on my phone.
I also let the install itself run for 10+ minutes everytime. But all the roms I try they keep doing the exact same thing and staying in a boot loop.
Can anyone give me any tips or suggestions to maybe something I could do to use another rom or maybe even a suggestion to something I may have overlooked.. Any help is appreciated. Thank you.
An if you need me to give any other information let me know an I will provide.

1. what recovery version not just the name ?? 2.steps you are doing to flash 3. steps you are doing after you flash

krazierokz said:
1. what recovery version not just the name ?? 2.steps you are doing to flash 3. steps you are doing after you flash
Click to expand...
Click to collapse
1.Im using the latest TWRP.
2. Wiping System, Cache, Dvalik or whatever. I wipe everything in the usual instructions. And I make a backup of previous ROM. Flash the ROM then the G-Apps.
3. After I flash I let the ROM run its course an I wait from 15-45 mins for the ROM to load if it doesnt I switch back to TweakWiz or try another.
Sent from my SAMSUNG-SGH-T989 using XDA Premium HD app

try using this recovery since the recovery you are using is the latest one and technically for 4.3 ROMs, give this a shot http://techerrata.com/file/twrp2/hercules/openrecovery-twrp-2.5.0.0-hercules.tar its the same recovery but lower . the steps you clarified seem very proper but your recovery may be at fault crossing fingers try flashing that recovery through odin or download the zip from the same website and report back after trying to flash again

Are you sure you are wiping DATA also?
You will need to do this, if you are flashing a 4.2 or 4.3 ROM, then you will also want to wipe the pre-load. Then flash the rom, and gapps.
Use the newest TWRP 2.6.1.0 to flash anything, don't need an older recovery to flash older ROM's.

idtheftvictim said:
Are you sure you are wiping DATA also?
You will need to do this, if you are flashing a 4.2 or 4.3 ROM, then you will also want to wipe the pre-load. Then flash the rom, and gapps.
Use the newest TWRP 2.6.1.0 to flash anything, don't need an older recovery to flash older ROM's.
Click to expand...
Click to collapse
Is there a option I'm not deleting ?
Because I've been flashing ROMS on different phones an I have never had any issues before. I was using ICS an GB etc before an just recently decided to upgrade an use the JB (I think that's the name.) on my phone.