[Q] HTC ONE V CDMA-Phone reboot/s - HTC One V

Hello,
wanted to ask for help, i have HTC ONE V CDMA version Bootloader Unlocked and Rooted. S-ON
I tried installing PrimoC kernel on stock sense. I install kernel for ICS then i reboot into bootloader flash the boot.img. Phone reboots and keeps rebooting.
I install XPERIA Rom, install stock kernel through bootloader /fastboot phone wont boot up, just keeps restarting.
I install CM10 and install kernel phone boots up and shuts down. Boots up shuts down.
PACMAN ROM same issue.
The point is what am I doing wrong? I went through every phone out there on the market never had any issues. This phone is pain in my ass.
The only way for me to boot up the phone out of boot loops is flashing BOOT.img from my back i made of the stock sense. Even then my WIFI will not work.
I am looking for pointers, instructions, whatever helps i love flashing I love these ROMS on here, but i just cant seem to get the to work.
Appreciate your time and your help.

Sounds like the last OTA update, your phone might have already had it before you bought it.
http://forum.xda-developers.com/showthread.php?t=2013489&highlight=ota

Please ask all questions in Q&A. Thread moved there.

restoring back to pre ota fixed the issue. what a pain it was something so simple yet complicated.

Related

[Q] Cannot boot into Recovery!!

So you probably see these types of threads all the time, but this one is different--
So the phone is a T-Mobile G2, Yes, It is Rooted, and S-OFF.
Long story short, I rooted the phone fine, but I cannot reboot into recovery.
I have the newest CWM flashed. It is version 3.0.0.5. When I try to boot the phone into recovery, it simply gets stuck on the HTC Logo screen. But, it is not bricked, but if I remove the battery, and put it back in, the phone boots and its fine. One more time. The phone is S-OFF and rooted.
The only thing I can do is flash CM 2.5.1.3...... 2.5.1.4+ do not work.
I just want to know WHY its doing this. Its my friends G2 and I have rooted mine the SAME exact way, and its fine. I have tried factory resetting it, but it doesn't work.
PLEASE TELL MY WHY.
EDIT*
I'm trying to do this process in ROM Manager- I also have tried flashing it more than once.
Brazildiogo732 said:
So you probably see these types of threads all the time, but this one is different--
So the phone is a T-Mobile G2, Yes, It is Rooted, and S-OFF.
Long story short, I rooted the phone fine, but I cannot reboot into recovery.
I have the newest CWM flashed. It is version 3.0.0.5. When I try to boot the phone into recovery, it simply gets stuck on the HTC Logo screen. But, it is not bricked, but if I remove the battery, and put it back in, the phone boots and its fine. One more time. The phone is S-OFF and rooted.
The only thing I can do is flash CM 2.5.1.3...... 2.5.1.4+ do not work.
I just want to know WHY its doing this. Its my friends G2 and I have rooted mine the SAME exact way, and its fine. I have tried factory resetting it, but it doesn't work.
PLEASE TELL MY WHY.
Click to expand...
Click to collapse
If you can boot up normally, load rom manager (download from market), and go to install alternate recovery, and install any alternate recovery. Then when that is complete, go back and install the Clockwork recovery version you want on top of the alternate.
What happens is SOMETIMES recovery will get messed up while installing, and you'll get exactly that, loop at the HTC screen.
If you cannot reflash an old, then the proper recovery through Rom Manager, you can do it via fastboot with your computer and USB, there are a few guides on the developer forum on how to do that. If you need i can try to dig up the fastboot recovery method guide later... but really, if you can boot up, Rom Manager is your best/easiest bet.
Yeah, I'm trying to do it using ROM Manager. and It still doesnt work. Ive rooted- unrooted and did everything, idk what I'm doing wrong. I tried flashing the new recovery like 4 times, it doesn't work for me. Thanks for the reply!

[Q] CWM Recovery rom flashes won't boot

Hi everyone, I've come into a strange problem with my G2 and I bet someone here can help me out! I just got a refurbished G2 because my last one had display problems. I tried to root with one with gfree (05) and I ran into a couple of errors so I rebooted my phone and used the rage method. Anyway, I downloaded rom manager and flashed CWM 3.0.2.4 so I could flash that leaked gingerbread build. It wouldn't work for me, so I flashed xborders' version and it's all good. I went to flash the stock rom (to go back) and when it reboots it stays stuck on the HTC splash screen. The same thing happens with CM7, or any other rom I've tried recently. I let CM7 flash when I went to sleep, when I woke up it was still stuck on the HTC screen.
I'll explain what I do:
1. Flash superwipe g2
2. Flash the rom in recovery
I accidently deleted my froyo nandroid but I have one from xborders rom so I at least have a usable phone. Could my sd card be messed up? I've tried it on the two I have.
I had this problem with my other phone too, no matter what I tried I couldn't get CM7 to work. Now it seems like no roms are working.
After I do flash a rom, it doesn't say reboot system like I think it should? I have to hit back to go back into the recovery menu.
Ended up fixing the problem, thanks to anyone who looked at this!
Care to tell us how you fixed in case someone else comes to this thread for reference?
He probably didn't root the phone properly or the partition table has been messed up. To fix something like that just flash a stock ROM that you know works on the phone and from there you can use any root method to get SuperCID, Permanent ROOT, an unlocked HBOOT and ClockWorkMod. Then any rom designed for the G2/DZ should be flashed just fine as long as the requirements are met.

Recovery affected by rom?

Hey mates,
would be cool if you could help me to understand the connection between recovery and flashed rom...
This is why I'm asking: I rooted my desire a couple of weeks ago (by applying the unrevoked method). Since then I flashed a couple of custom roms. I wasnt very happy because the most roms caused my mobile phone to crash. I thought it was because a broken sd card therefore i bought a new one today. Sometimes when my phone crashed I wasnt even able to enter recovery anymore. And sometimes it did just nothing... I couldnt even enter hboot (it just didnt boot - like it was briked - only the charging led was on when i plugged the charger in). In this case I had to remove the battery a couple of times or plug in the charger. Usually I needed to do this many times. This is btw. why I'm fed up with custom roms but maybe its just my mistake. And now finally my question:
Why can I enter recovery sometimes and sometimes not? Does this depend on the rom? Why do I have to remove the battery etc. to make it run?
I know flashed back to the rom I of which I created a backup after root. But it seems that my phone is more unstable since then (even if its just my rooted stock rom)
Thank you for your answers...
What rom are you on? Maybe your recovery is a bit messed, have you tried reflashing it? Btw, s-on right?
If your not able to get to your hboot then there is something wrong with your phone. It will most likely be able to do with your hardware. You can use an ruu to restore everything back to factory default. You could then root again and see if that will help. But it does look like to be a hardware/corruption issue.
Swyped...
Your Desire maybe being one of the new PVT4 new nand would might cause this. I know that the latest version of unrevoked and Clockwork recovery can't be used to root the PVT4 new nand. I had that problem and the fix for me was to use an earlier version of unrevoked and flash Amon Ra recovery instead. There's a thread around the forums regarding this. Check first if your Desire is of the new PVT4 model. Can't post the link but there's a thread that explains how you can check if your Desire is PVT4 new nand. Would post the link but can't yet, but a quick search should take you to it.
hey guys, thank you very much for your fast answers. The desire is s-on. I'll try an official ruu. If I'm brave enough I'll root again . The strange thing is that I can enter recovery but not always. A hardware issue would be awful. I'll let you know how it went. I hope it is ok to just use ruu to update a rooted rom. It flashes a new recovey too, doesnt it?
Ok, i tried to use ruu to unroot my device. It told me that my bootloader was not compatible and canceled flashing. But it also broke my rom. I couldnt boot the system anymore and i couldnt boot into recovery. I dowloaded a ruu image (with my radio) to flash it via hboot. Everything seemed to go fine but after the first restart i'm stucking with an update sign (i guess its the recovery menu) - a mobile with green arrowrs. I think its frozen. Do i need to do anything else?
Hey, just to keep you up to date. I successfully unrooted my device by flashing a stock ruu. Now its booting (but not always) but it often freezes after a few minutes after the boot progress. I guess I'm going to send it back.
Thank you all for your help anyway.
Lovebongo said:
Hey, just to keep you up to date. I successfully unrooted my device by flashing a stock ruu. Now its booting (but not always) but it often freezes after a few minutes after the boot progress. I guess I'm going to send it back.
Thank you all for your help anyway.
Click to expand...
Click to collapse
Yeah best to send it back, it sounds more like a fault with the device

[Q] Flashed incorrect kernel on One M8 no screen response whatsoever

I tried flashing a kernel believed to be ExcaliBur on my HTC One M8, but as soon as i rebooted the screen was black yet still on.
I know it's not bricked completely because i can still hear sounds, feel vibrations and see the LED's work properly. Basically I have a "blind" phone. I have began to look into a way to capture my screen one frame at a time with my computer.
Please help me!
Running Android 4.4.4 Cyanogenmod Snapshot 11
T-Mobile
TWRP 2.8.0.3
Tried getting back to bootloader and flashing back the boot.img you had before flashing new kernel?
If the device still has "some" interaction then you should be able to connect it to PC and use the adb reboot bootloader command to boot it into bootloader.
BerndM14 said:
Tried getting back to bootloader and flashing back the boot.img you had before flashing new kernel?
If the device still has "some" interaction then you should be able to connect it to PC and use the adb reboot bootloader command to boot it into bootloader.
Click to expand...
Click to collapse
I actually DID just get into my bootloader. I had to mess around by pressing the buttons until i finally got it to boot into bootloader. Now I flashed a stock kernel for now, I always keep it in my SD Card.
I found you can use a program called Wondershare MobileGo for Android that can read whatever is on your phone if you happen to be "blind" like me.
P.S. I really need a kernel for CMod that has fast charge. Currently ExcaliBur is off the list.
I haven't heard of Wondershare MobileGo, seems interesting.
I can't help with custom Kernels, I always stick with stock, haven't flashed a custom kernel since way back with my S3. Sorry, can't help there.
Thanks anyways! Notice I got my phone working again! I flashed the stock, and then reflashed CMod and nothing was wiped. Interestingly...
Sent from my One M8 using XDA Free mobile app
That's quite lucky, any other time I've heard of this happening the phone's died completely.

stupid mistake but can't seem to fix

Hi all.
I have been trying to root and load a custom ROM on my friends Chinese htc one m8.
I unlocked the boot loader fine. Then flashed twrp. Here I missed the actual root of the phone which is silly. I then flashed a custom ROM and now stuck in fast boot mode when I reboot.
I know I missed the actual root section. I tried to plug the phone back in computer and use command window to root. But it says device offline now.
Is there anything I can do? Its not rooted. I just think I've wiped the stock HTC software and I didn't make a back up. Please help

Categories

Resources