yashsingh1/xdaforums huggingface dataset:
[Eee Pad Transformer Android Development] PeQuEsan:
Hi all,

My current report:

- I rebooted after that 86 hours stable, and I had my first SoD during the night (remember B150, no GAPPS, no APPs, no use at all)... so: It SEEMS that the ROM is stable when first booted... Once you do a reboot, SoDs start happening.

That said... @Timduru... is this info somewhat helpful? :confused:

- Next thing I've done is wipe all again, and then install B150 + GAPPs MIX (no reboot in the middle)... 50 hours after, my tablet is still alive, no SoDs, no RRs. I've restored all of my usual apps with Titanium Backup, I've surfed, I've watched movies and TV using aMPDroid + MX Player, I've done some photos... It's the first time I can really enjoy TeamEOS4 ROM. :)

- Next step I'll do: let me enjoy a little bit more :silly: (may be 2 days), and then I'll reboot in recovery, make a nandroid and reboot... SoDs should start, then I want to restore that nandroid to see if SoDs are there or not. Silly test may be... but I want to do it.

Two more comments I wanna say:

- Last night my tablet hasn't gone to deep sleep. BBS tell me that the culprit is a partial wakelock named "DockObserver". Guess what... it was docked all night. :) During this period of 7h, tablet has eated 15% of dock battery. Not that much anyway. Now I've left it undocked, and I'll review BBS when I come back home this evening.

I've reviewed that setting and I found something odd that may be the cause of the problem... When you first go to see about Daydream, you can't see it "off"... but when you enter inside the setting, there's no screensaver selected... So it's "ON", but with no screensaver selected... Could it be a problem Timduru? Anyway, I've just left it off, as anarox recomends. May be when I reboot I don't have SoD because of this... It's not very consistent to mix different tests, but once you select a screensaver, you can't deselect it anymore, so I couldn't go back.

Thanks all.
[Eee Pad Transformer Android Development] alberteske:
try to update to:

EOS4.2.1-tf101-20130211-B155 - Tim_KatKernel_94_JB4.2_Lidpatch

http://public.timduru.org/Android/tf101/eos4/

:highfive:
[Eee Pad Transformer Android Development] Isham.padron:
I'm running the latest preview version and I have found it runs really nicely. I was having issues with system lagging while I was swiping on the keyboard and just getting in and out of apps would lag using the build 94.

I am still having problems with the sound cutting out and I have to use the kat app to reinitialize the sound. Is there a hardware issue that causes the sound to drop out? Not sure why I have to reinitialized the sound a few times a week.
[Eee Pad Transformer Android Development] timduru:
Even with B155 or is that with 94 ?
[Captivate Q&A, Help & Troubleshooting] TamiTT:
My Aunt had a samsung Captivate She accidently set the Phone in Download Mode. When I connect USB or Power Cable and turn the Phone ON it starts normaly. But When I unplug it and try to start it Boots in to the Download Mode. I got the cell flashed from a repair centre But the Problem is still there Now the repair centre says it is an issue of Hardware.

I want to ask that is that possible that the USB jack can make the phone go into Download Mode?

Captivate was Unlocked, Not Rooted and was on Froyo before the Flashing. Now its on Gingerbread.

Please Guide Me I am confuse what to do?

Thanks
[Captivate Q&A, Help & Troubleshooting] BWolf56:
It's a possibility, I'm thinking it could be from humidity though. You could try to put the phone in a bag of rice for a couple days see if it helps.

If that doesn't work, it could very well be that the volume down button randomly activates. It's not very common but hardware is hardware, never really know what will break or not work properly.
[HTC One V] filoxo:
Any resolution to this problem? This has been reported in several threads (link 1, link 2, link 3, need I give more?)

I'm also experiencing the same problem. I installed Paranoid Android (per instructions here) and am now experiencing the same problem. After flashing, the phone continuously reboots. I am using an HTC One V (CDMA) from the US. I also flashed the JB 4.1.2 gapps with the ROM flash process.

When it boots, I receive two errors: "Unfortunately, android.process.acore has stopped working" and "Unfortunately, Contacts has stopped working". When I lock the screen, it reboots. When I try using it, it reboots after 30 seconds. If I just leave it alone, it reboots.

I have also tried several kernels with this same ROM (kernel that comes with the ROM, SuperSick [found here], and stock CM10) and they all just produced the same behavior.

I've looked all around. Some possibilities are: bad kernel, memory (RAM or otherwise) running out, bad install of ROM, or something no one has yet to define. I don't think its a bad kernel because this happens in 3 different ones. I don't think it's a memory issue because I lowered the CPU clockspeed and the phone has plenty of storage memory, and I've also flashed AOKP with the same results which rules out a bad ROM install.

I've wiped cache, system, data, and dalvik and followed all instructions as given to get a completely fresh installation. No avail. I realize that the One V isn't very popular, and there is only a limited amount of support for it but could anyone shed some light as to what the problem could be?? Perhaps some of the original devs who made the ROMs can help out us lowly fools who can't get it to work? I thank anyone in advance for being awesome and at least trying to help.
[HTC One V] riggerman0421:
You may have to flash the old RUU. Look in the General subforum for a thread about phone rebooting after one minute.
[HTC One V] reID_entify:
sounds like you did the OTA update and have the new radio version, you need to RUU back to stock and dont get the OTA.
[HTC One V] filoxo:
I'll try.

Thanks both of you! I will try flashing the RUU and I'll make sure to not install the OTA update. I'll post later with my results.
[HTC One V] filoxo:
...

So... I flashed the RUU on the phone again. I again carefully followed instructions on how to flash ROMs (AOKP and Paranoid) and it simply doesn't boot. AOKP's ROM only starts up to a black screen. Paranoid boots to the boot screen animation and just hangs... I've used stock kernels, and tried the SuperSick kernel with both. No progress. Any other ideas?
[HTC One V] riggerman0421:
Try the latest version of cm10 with the latest version super sick kennel. That's what I'm running. AOKP has a few versions that boot to a black screen. If you want AOKP use the latest stable version.
[HTC One V] filoxo:
Awesome!

Riggerman0421, thanks a ton for the suggestion!! It worked! Despite not being able to use the other roms, I think I can settle with using CM10.
[HTC One V] lytesson:
htc one v

Hey I am having the same problem as you with my htc one v. What did you do exactly to fix this?
[HTC One V] filoxo:
You have to RUU your device back to the original radio version; it was changed when you accepted the OTA update. That means that you're going to have to flash it to complete stock (no recovery, HTC Sense, booloader relocked, etc.) using the RUU. The forum I found that had all of the different RUUs was deleted unfortunately. You'll have to do careful research for the RUU for your specific device. I only know that Virgin Mobile in the U.S. uses the Sprint towers, so the RUU I used was titled "RUU_PRIMO_C_ICS_40A_Sprint_WWE_VM_1.08.652.6_Radio_1.00.00.0521_2_NV_VM_3.46_0503_PRL61008_release_262414_signed". Just a quick search on XDA and found this forum that has a download link to the RUU you would need for VM [CDMA] phone (read the comments); you can also look around yourself to make sure you have the right one.

You can find specific instructions on how to RUU your device at this awesome forum. It should only take, literally, 15-20 minutes.

After that is done, you will need to unlock your bootloader again and then you're ready to move on to bigger and better ROMs.
[HTC One V] EpicLordPhone:
So, this happend to my htc and I ruu'ed back to stock, after continunously trying to install roms with constant bootloops. I did the ota update again. So if I want to install a custom rom your saying DONT do the ota after ruu'ing then install one after rooting?
[HTC One V] bheadrick:
I've got a similar issue (virgin mobile HTC One V)

I currently have TWRP recovery installed, and I attempted to flash the jellybean CM10 as well as the AOKP rom, and I got as far as the unicorn and I actually manged to get the phone to boot to the main screen with all the icons, but it would constantly reboot after being on for maybe a minute

I tried flashing everything back to stock including restoring a backup I had previously taken with TWRP, but no luck

I also tried flashing the stock rom downloaded somewhere here on XDA and I even flashed the stock recovery, but all I got was constant rebooting.

it would get as far as the startup animation and then reboot indefinitely

I'm at a total loss here. I've seen a few links with some resources that look like they might have been helpful (like on this thread) but the links are dead, and I also read somewhere that HTC was putting the kibosh on a site that had some stock roms.

I'd prefer to get jellybean working on my phone, but ultimately, I just want a working phone.

I've followed the process of installing the rom - some instructions said to flash the boot img before flashing the rom, some say after

I've tried both methods

I went into recovery, mounted the usbmsd and copied the rom, and used recovery to install the rom after having cleared the cache, davlik cache and wiping the data (factory reset)

I also installed the gapps package after the rom, but I don't think that's critical to getting it to just boot.
[HTC One V] BeyondExistence:
The OTA update reboots were fixed in the latest 4.2 SickleKernels.
[HTC One V] maxwech:
I think I'm having the same problem. The phone boots, gets as far as the "this build is for development purposes..." and then hangs for a few minutes and restarts, over and over. The flash with fastboot seemed to work fine and reported no errors.
[HTC One V] filoxo:
Yes. Do NOT install the update if you want to flash another ROM onto your device. Use the RUU to get the device back to factory; this will restore the original radio version. Then go through the steps to unlock the bootloader, root, and flash your ROM as desired. There are other forums which explain the mentioned processes better.

BeyondExistence says that this is fixed with a "4.2 SickleKernel", but as far as I'm aware there are no JB 4.2 ROMs for the HTC One V. Maybe a little more information would be in order?
[HTC One V] filoxo:
Bheadrick:

I'm not quite sure what you mean when you say you flashed the stock recovery. The One V doesn't have a recovery when everything is stock.

You will have to RUU your device back (have you read any of the posts in this and other forums??). The process will reinstall the stock rom, relock your bootloader, remove the recovery, etc.

I recommend that you use Paranoid android's rom with the latest SuperSick kernel. Its been my favorite and most stable build I've used.
[HTC One V] filoxo:
So I found what BeyondExistence might have been talking about (for those of you who care/are currently having the bootloop problem and would rather go with this route). Its called RhythmicRom. This is a 4.2.2 ROM and it has some cool things for users switching from Sense to a more-pure Android [Link here]. Its based off of CM10.1 for the One V and it includes the BeatsAudio app (which most ROMs don't, as far as I know).

The reason I think that this is worth mentioning is because whoever runs into this bootlooping problem can simply SKIP the RUU process and just move onto this ROM. Hit thanks if this helped!
[HTC One V] filoxo:
Newest OTA update.

As some of you may have seen, there's an even newer OTA Update available through the stock ROM. As always, this will cause problems when you try to flash a different kernel, resulting in bootlooping (can anyone who has done the newest update confirm?). Anyway, I've also read that this update also updates your hboot (which, since I haven't and will not apply the update, don't know why it would impede you from flashing any other ROM/kernel but it does) and radio version.

I've looked for additional ROMs who try and make their builds compatible, but so far only RhythmicRom has done anything worthwhile (in my opinion). His latest v 1.3 build will be out soon, and I highly recommend it.

If you flashed both OTA updates, then please be sure to include that when making any post.
[HTC One V] tallnproud:
I got my One V at the end of December and did the OTA update at the beginning of April. Last week, I decided to try messing with loading some different ROMs and have encountered all of the problems you've mentioned (e.g., boot-looping, inability to RUU back to stock). I have successfully gotten RhythmicRom to load using this OTA_support.zip (which has been incorporated into the regular release since I flashed it). I have also gotten the most recent version of PACman v22.1 to run (using the same kernel as RhythmicRom) without boot-looping, but the performance hasn't been great (browser crashes frequently and it seems like the launcher has to restart a lot). User demi_fiend has said that the PACman ROM will work using the CodefireX kernel from user BeyondExistence.

I had also tried to revert back to my stock CWM recovery, but it had the boot-loop problem too. However, demi_fiend has also informed me that you can revert to a stock backup by using the boot.img file that is located in the backup folder. I haven't had the chance to verify this, but I wouldn't be surprised if it were true.

It's a bit of a pickle being unable to revert back to previous radio versions, but there is hope that some of the devs will incorporate this issue into their new builds.
[HTC One V] Lsesp:
Did you flash stock recovery and lock bootloader before running RUU?
[HTC One V] tallnproud:
I had flashed my stock recovery (although it was still boot-looping), and I did re-lock the bootloader before running the RUU.

I used the instructions found here.
[HTC One V] Lsesp:
Can you tell me the version of your Hboot?
[HTC One V] tallnproud:
Hboot: 1.57.0000

Radio: 1.00.00.0928
[HTC One V] Lsesp:
There's the problem, you have the latest hboot version which is not compatible with the RUU. What you can do is run the RUU and go to temporary files by typing %temp% on the file explorer, you are gonna see two folders with long names that are going to have the current time as the date modified, inside one of them you are going to find another folder which will have a rom.zip (approximately 326mb). Copy this zip to your desktop and rename it to PK76.img. Then you will need to place this file to the root of your sd card and then when you are done boot into bootloader and it should automatically look for the file and try to install the stock rom. This will restore the phone to its factory settings. Keep in mind your bootloader has to be locked. This should work, let me know what happens.
[HTC One V] tallnproud:
Just to be clear, this will return the phone to stock, but it will still have the OTA update (e.g., updated radio and hboot)?
[HTC One V] Lsesp:
Nope, it will be just like it came out of the box, no OTAs, it will have Hboot 1.53.0000 and will have the stock radio. :)
[HTC One V] tallnproud:
Wow, that's good news. I'll have to give this a shot when I get home.

BTW, is this a newly discovered method? I haven't seen this mentioned in any of the RUU tutorials. B/c if this works like you say it will, then the tutorials will need an update.
[HTC One V] Lsesp:
Correction, I made a mistake, name the file PK76img.zip not "PK76.IMG" and this is not a nee method, this is the method to restore the phone without ruu.
[HTC One V] tallnproud:
Well, I feel stupid

Wow, now I'm feeling stupid. This method is totally in the tutorial that I was looking at before. If I'm remembering correctly, I didn't try it because my device was boot-looping and I couldn't access the sd card to copy the file over. Of course, after I got it working with a different ROM, I could've accessed the sd card and downgraded, but I had forgotten.

Oh well, thanks anyway, and maybe next time, I'll actually remember what I've read.
[HTC One V] Lsesp:
Haha just ask questions if you're confused, and if you're device decides to bootloop again just stick your sd card into your computer and that way you can copy the file to the sd.
[HTC One V] tallnproud:
You're totally right about putting the card in the laptop. At the time, it was 3:00 in the morning, and I was upset b/c of the boot-looping and wasn't thinking straight. Ah well...

Thanks again.
[HTC One V] Lsesp:
no problem! i have gone through all that with my phone and i know it is pain in the ass when you dont know what to do lol
[HTC One V] MARK-Oz:
im having the same problem ive tried flashing like 4 roms already they all reboot within 1 minute of booting into rom

i am in the process of reading the guide the only thing i have a question on is wich ruu belongs to my device

i think its this one since i have the virgin mobile version

RUU_PRIMO_C_ICS_40A_Sprint_WWE_VM_1.08.652.6_Radio_1.00.00.0521_2_NV_VM_3.46_0503_PRL61008_release_262414_signed.exe

so my question is this my RUU?
[HTC One V] Lsesp:
Yes you have the correct one, good luck.
[HTC One V] qwerty5554:
i tried this on my phone and i get an error that the Hboot version is older just like i did trying it the other way. did this work for anyone else?
[HTC One V] filoxo:
I've done it on three different phones. It works. Which instructions are you following? I used this one and it seems to be best.
[HTC One V] qwerty5554:
will have to try it using that method. hope it works need to get the phone back up and running soon.
[HTC One V] Lsesp:
Hope this helps

In that case try putting the PK76img.zip on your sd card, make sure bootloader is relocked and that you have the stock recovery flashed on your one v.
[HTC One V] filoxo:
This method does not work very often. And also, the One V does not have a stock recovery. It just has a stupid image that doesn't tell you anything.
[HTC One V] qwerty5554:
tried it both methods from that link still fails because Hboot version is older.
[HTC One V] Lsesp:
Is there a way of flashing the hboot alone? the hboot file can be extracted from the stock rom but i wonder if there is a way of just flashing the hboot.
[HTC One V] tallnproud:
I didn't have much time to mess with my phone tonight, so I just reverted back to my RhythmicRom Nandroid backup.

I might try to mess around with everything this weekend when I've got more than just a couple minutes to try things.

But thanks again. I'll post again when I've tried the downgrade.
[HTC One V] filoxo:
Sorry that I missed that. I'm almost sure that you can no longer downgrade hboot, as reported by demi_fiend [here]. Whoever applied this update is stuck :/
[HTC One V] Lsesp:
Well I'm not the one who's stuck lol I'm trying to help tallnproud
[HTC One V] dennisog:
hey guys, I'm obviously new here, but I've been reading these forums forever and found them really helpful for questions on all my devices, you guys are pretty awesome.

I have the Virgin Mobile CDMA One V and I used the unrooted stock ROM for the longest, until yesterday I got sick and tired of it being slow and buggy and loaded with bloatware so I decided I'll try my luck with a custom ROM. I applied the April OTA update, so I have the new radio as well as the new hboot. I've tried a couple of different ROMs, but the only one that wouldn't bootcycle itself to death is BeyondExistence's cfx-SR16 build. I've also tried RhythmicROM, but i wouldn't boot. I'm using TWRP2 as recovery. I tried downgrading my hboot in all possible ways described here, but that didn't go anywhere either. I can confirm that the cfx build boots and works quite well on the newest radio/hboot, but I get around 2-3 random reboots per day, which sucks.

my questions are: Is there maybe some other possible way to downgrade the hboot from the April OTA update that I haven't tried? If not, is there a kernel that works with the BeyondExistence's cfx build that is just a little more stable and if not, what would be the best way to start for me to make one?

Thanks for your help!
[HTC One V] qwerty5554:
did you try to do the new manual update with the rythmic rom? you have to get the OTA fix. I didn't realize this and was having reboots every 60 seconds or so. haven't had a single crash or issue with one full days worth of use so far.
[HTC One V] dennisog:
haha... A second after I sent my post I saw that manual update... flashed it, it boots and runs smoothly so far. Awesome! Thanks for your help. I'll post any random reboots or issues if they come up...!
[HTC One V] qwerty5554:
awesome hope you didn't waste two days like i did trying to figure it out. seems a lot smoother for me and i think my battery life has improved a bit. still have over half life after a day, usually had to charge as soon as I got home each day. though phone didn't see a lot of use bit did serf the web a bit on it.
[HTC One V] dennisog:
yeah, it seems to be a nice ROM, unfortunately I can't receive text messages right now, now sure if it's Virgin's fault or the ROM. I'm gonna have to make a backup and test the cfx ROM again. maybe that will work smoother with the Rhythm kernel?
[HTC One V] qwerty5554:
i don't know i was receiving texts fine today. i don't know how that patch would work with another rom. might create a new thread to make sure that will work ok.
[HTC One V] dennisog:
tried every combination between the cfx and rhythmrom kernels and ROMs and I guess it's just my phone. maybe something went wrong while I was trying to do the RUU with the older hboot... It's time for a new thread
[HTC One V] demi_fiend:
I made a rom from the newest hboot for my little sister to revert to, there is a kernel inside that will work, I'll post the link as soon as I upload it. I'm gonna let you know now though, I don't have a very good internet connection so it may take a while on virgin speeds. I'll most likely post it to 4shared anyone have any other ideas for file hosting?

by the way, its deodexed and has init.d its not something I plan on updating or anything, I just wanna help out the community and get a little fix for ya'll and clear some of the clutter and confusion this is all causing.
[HTC One V] filoxo:
Would it be too big to just upload to xda? Other than that, 4shared probably is your best resource. Thanks for doing that!
[HTC One V] demi_fiend:
its about 400 mb, I'll really try and get it up by the end of the day.

okay so I'm uploading to 4shared now, its going painfully slow but I'm gonna sit back and play some Wii. so I'll start a thread and everything when I notice its done.

I really just hope it helps stop some of the ridiculous spamming I've seen in so many threads the past week or so.
[HTC One V] erikerik2013:
Htc one v cdma hboot 1.57.0000 radio 1.00.00.0521_2

Hi, i have the same problem but my hboot is 1.57.0000 and radio 1.00.00.0521_2

i update with OTA_PRIMO_C_ICS_40A_Sprint_WWE_VM_1.10.652.6-1.08.652.11_release_312825wxrvg31mgao07zzy.zip

then don't work anymore..

now i can't drowgrade to RUU_PRIMO_C_ICS_40A_Sprint_WWE_VM_1.08.652.6_Radio_1.00.00.0521_2_NV_VM_3.46_0503_PRL61008_release_262414_signed.exe because OTA-PRIMOC have a HBOOT 1.57 and RUU hboot 1.53.

i try boot with cwm recovery and twrp for the mobile (HTC ONE V CDMA) and nothing work..not boot

appears red text and then reboot..

i try sickkernel

i try with rhytmicRom flashing "boot.img" creating system.img and flashing and not worrk..ç

i search every forum,thread, test and nothing work.....i very stuck ;(

any idea?

thanks for the help
[HTC One V] filoxo:
Have you tried flashing this rom {RhythmicROM}? Its a great, stable and smooth rom and has an update patch to make it compatible with the newest hboot version. That will be your best bet.
[HTC One V] filoxo:
hey [MENTION=4934200]demi_fiend[/MENTION], have you been able to find somewhere to upload your modified, new hboot-compatible version yet? Thanks!