Develop Bugs

[Q] HTC One V (CDMA) continuously boots after flashing ROM

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.

You may have to flash the old RUU. Look in the General subforum for a thread about phone rebooting after one minute.

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.

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.

...
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?

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.

Awesome!
riggerman0421 said:
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.
Click to expand...
Click to collapse
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
filoxo said:
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.
Click to expand...
Click to collapse
Hey I am having the same problem as you with my htc one v. What did you do exactly to fix this?

lytesson said:
Hey I am having the same problem as you with my htc one v. What did you do exactly to fix this?
Click to expand...
Click to collapse
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.

filoxo said:
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.
Click to expand...
Click to collapse
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?

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.

The OTA update reboots were fixed in the latest 4.2 SickleKernels.
Sent from my One V using Tapatalk 2

bheadrick said:
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.
Click to expand...
Click to collapse
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.

EpicLordPhone said:
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?
Click to expand...
Click to collapse
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?

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.
Sent from my Nexus 7 using xda app-developers app

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!

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.

filoxo said:
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.
Click to expand...
Click to collapse
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.

tallnproud said:
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.
Click to expand...
Click to collapse
Did you flash stock recovery and lock bootloader before running RUU?

Lsesp said:
Did you flash stock recovery and lock bootloader before running RUU?
Click to expand...
Click to collapse
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.

are you rooted already ? (OPPO N1)

hello
I am courious
how many of us are rooted already ?
what method did you use to root your phone ?

nowy57 said:
hello
I am courious
how many of us are rooted already ?
what method did you use to root your phone ?
Click to expand...
Click to collapse
Rooted since long ago... On every build... All the time. :good:
If you're still having trouble with rooting CM or Omni, try the following.
You should be able to flash the SuperSU zip in TWRP after clearing Dalvik and Cache. If that fails, try below.
If you have SuperSU installed already and are failing to get root, you may have to remove your current SuperSU version. Don't just uninstall SuperSU! Go into SuperSU and go to "Settings". Scroll way down to "Full Unroot". Let that run as it needs to, then reboot into TWRP and wipe Cache and Dalvik. Then flash the SuperSU zip. Reboot to system. Test root.

sorry mate
it doesnt work to me
I have tried two times
as you wrote

Harfainx said:
Rooted since long ago... On every build... All the time. :good:
If you're still having trouble with rooting CM or Omni, try the following.
You should be able to flash the SuperSU zip in TWRP after clearing Dalvik and Cache. If that fails, try below.
If you have SuperSU installed already and are failing to get root, you may have to remove your current SuperSU version. Don't just uninstall SuperSU! Go into SuperSU and go to "Settings". Scroll way down to "Full Unroot". Let that run as it needs to, then reboot into TWRP and wipe Cache and Dalvik. Then flash the SuperSU zip. Reboot to system. Test root.
Click to expand...
Click to collapse
I have the same issue too. SuperSU installed 3 times. Did the full unroot like you said and reran the install after wiping both the cache. Still no root access.

I think that magic which found us oppo+CM team is missunderstand couse when I first time heard about cooperation this two companies I was so much happy .
by now when I have it I know that maybe couple of hundred is sold this phones and nobody cares about support it .
1.ROM straight from CM/OPPO site doesnt install propely via TWRP( without ingeration for user-script)
2.no root acces yet
this is sad true .
I v got note3 and I see more future with this phone
AOSP/CM is on a way - a lot of android entusiasts is working for free of charge about better and better ROMs
I am dissapointed - no offens to anybody

I rooted my ColorOS rom as per this post:
http://forum.xda-developers.com/showthread.php?t=2539930

ChodTheWacko said:
I rooted my ColorOS rom as per this post:
http://forum.xda-developers.com/showthread.php?t=2539930
Click to expand...
Click to collapse
it is not installed under CM ROM

It is rooted, as I have done it myself more than once.
Also, I said before that Oppo doesn't update or modify TWRP (nor does CM). I'm sure an updated TWRP build will fix the flashing issue. You can flash CM straight as it is on the stock recovery.
I don't know what's happening that's different from me. I have used that method to get root working on both CM and Omni. Probably about 20 times total now because I keep clean installing due to various changes that I make that I don't want to carry over.
Sent from my N1 using Tapatalk

ChodTheWacko said:
I rooted my ColorOS rom as per this post:
http://forum.xda-developers.com/showthread.php?t=2539930
Click to expand...
Click to collapse
The exploit method was apparently patched in the official CM release. That exploit doesn't work.

Harfainx said:
It is rooted, as I have done it myself more than once.
Also, I said before that Oppo doesn't update or modify TWRP (nor does CM). I'm sure an updated TWRP build will fix the flashing issue. You can flash CM straight as it is on the stock recovery.
I don't know what's happening that's different from me. I have used that method to get root working on both CM and Omni. Probably about 20 times total now because I keep clean installing due to various changes that I make that I don't want to carry over.
Sent from my N1 using Tapatalk
Click to expand...
Click to collapse
i am really confused couse I am pretty sure I am doing good as you said but no succes .

Harfainx said:
It is rooted, as I have done it myself more than once.
Also, I said before that Oppo doesn't update or modify TWRP (nor does CM). I'm sure an updated TWRP build will fix the flashing issue. You can flash CM straight as it is on the stock recovery.
I don't know what's happening that's different from me. I have used that method to get root working on both CM and Omni. Probably about 20 times total now because I keep clean installing due to various changes that I make that I don't want to carry over.
Sent from my N1 using Tapatalk
Click to expand...
Click to collapse
If TWRP doesn't work properly how did you root? With the stock recovery?

it is not true that stock recovery allow to install CM rom straight thru this recovery
I was fight couple of hours to install TWRP (first on my osx than went easier on windows)
and after this I could install CM rom via TWRP of course .

nowy57 said:
it is not true that stock recovery allow to install CM rom straight thru this recovery
I was fight couple of hours to install TWRP (first on my osx than went easier on windows)
and after this I could install CM rom via TWRP of course .
Click to expand...
Click to collapse
You can indeed install straight from stock recovery. I did it last night. You have to use the official rom for the n1. Works nicely. I also had root working on cm. I flashed cm from stock recovery then used fastboot to install twrp. After twrp i flashed supersu zip. After i did the fix root or remove or whatever it is in the ap, reinstalled and tested it in titanium. Said i did have access but then went back to coloros to try and fix my mediascanner issue.
Sent from my N1 using XDA Premium 4 mobile app

nowy57 said:
it is not true that stock recovery allow to install CM rom straight thru this recovery
I was fight couple of hours to install TWRP (first on my osx than went easier on windows)
and after this I could install CM rom via TWRP of course .
Click to expand...
Click to collapse
I mean straight flash CM on the stock recovery, not on TWRP. You would have to be on the stock recovery for it to work straight from the CM download. On the stock recovery though, you will not be able to flash SuperSU on it. I do not believe that Omni can be flashed from there either, but I could be wrong (I haven't tried it).
There's a thread in the dev section that has the stock recovery hosted there. You can always fastboot flash back to that at any time.

Okay, I decided to install Cyanogenmod for the heck of it.
I already had TWRP 2.6.3.1 installed,
I downloaded and modified cm-10.2-WPPH50O-n1-signed.zip as per this page's instructions:
http://forum.xda-developers.com/showthread.php?t=2553165
I also downloaded supersu (current version is 1.86).
I entered TWRP and installed it, following that page's instructions.
After the install, I selected 'reboot'.
When I selected 'reboot', It prompted me with:
install superSU now? this will root your device.
I said no, and then rebooted back into TWRP.
Now back in TWRP, I install SUPERSU.
Now reboot again.
Now in CM.
Now run SuperSU, select 'settings', and unclick 'Respect CM root settings".
Now root works for me.
Two notes:
1) Respect CM root settings implies that in 'developer settings', there is some sort of "allow root" checkbox. I can't find it.
2) If, after the CM install, you answer 'install SuperSU' with YES", then it installs SuperSU, and reboots.
When you go back in, and run SuperSU, it says "gee, you aren't rooted, install SuperSU?"
If you answer THAT with yes, then it downloads some version of SuperSU, reboots into twrp, and installs it.
So it's kinda pointless answering YES in the first place, imho.

Are you serious right now?! I was worried unchecking Respect CM root setting would mess things up. But now I have root access. OMG... I unchecked it and it works! ^_^

57 43235953
ChodTheWacko said:
...
Two notes:
1) Respect CM root settings implies that in 'developer settings', there is some sort of "allow root" checkbox. I can't find it.
...
Click to expand...
Click to collapse
There is actually a #Superuser control panel just below "{} Developer option" that has lots of useful settings for root user control.
I haven't rooted yet but it seems like handy stuff for supersu to respect? Once you go into #Superuser use the menu button and you can add a profile etc it seems.
It's all kind of oddly done since adding that control panel after activating developer mode doesn't actually add an "su" binary.

hammerandtongs said:
There is actually a #Superuser control panel just below "{} Developer option" that has lots of useful settings for root user control.
I haven't rooted yet but it seems like handy stuff for supersu to respect? Once you go into #Superuser use the menu button and you can add a profile etc it seems.
It's all kind of oddly done since adding that control panel after activating developer mode doesn't actually add an "su" binary.
Click to expand...
Click to collapse
On what version of CM? or did you mean OMNI?
Under 'System' I only have:
Date & time
Accessibility
Developer options
Performance
About phone
Unless you meant 'in {} Developer' but I don't see anything in there either.
- Frank

ChodTheWacko said:
On what version of CM? or did you mean OMNI?
Under 'System' I only have:
Date & time
Accessibility
Developer options
Performance
About phone
Unless you meant 'in {} Developer' but I don't see anything in there either.
- Frank
Click to expand...
Click to collapse
WOW...so it literally disappeared as I was composing this message.
Cyanogenmod "signed" installed with the oppo bootloader (not rooted as supersu doesn't install successfully through bootloader etc).
Some kind of UI refresh after I changed some home screen settings?
It was persistent through 5-10x reboots and now is gone.
Obviously a glitch since I don't have su and I'm not truly rooted but it WAS there :\
I'd say its a bug to be filed if you are rooted and it's not available.

Several Qs: 0 folder under sdcard\download\, soft bricked, counter...etc

My I747 is currently running Carbon Rom nightly 20131102 (4.3.1), it's quite old and I want to upgrade to 4.4.
So last night I nandroid backup , format system, data, flashed Carbon KK on it, then gapps, data, cache, delvik, reboot. But it stayed at the CM alien. I reflashed several times but still stuck at there. But I can nandroid back so I'm kind of fine now. But anyone know why?
Second, I notice my \0\ folder is under sdcard\download\0\ than usual sdcard\0\, I must have done something wrong when I first flash the carbon but I don't know what it is. I usually put my .zip in download, could that be why? Could that cause the bricking I have with KK?
Last, I know there's a flash counter and when I first root/flash last year, I went thru many things to avoid that&IMEI, instead of directly flashing a recovery. I think that could be the source of the problems above??? Now 1 year is up and my warranty is already over so I don't have to worry about the counter anymore. If I want to redo everything, and have to noobiest/simpliest method to flash to KK, what should I do?
Sorry if I lack any essential information. I'd be happy to find it to help.

Did you update to the latest CWM before flashing the ROM? Is your current bootloader supported by the ROM?

Not the latest but 6.0.4.3
I'll update it to 6.0.4.7 and try again.
Unfortunately I don't know if my bootloader is supported. I don't really know how to find mine.

I would update to the latest CWM and then try to flash a 4.4.2 custom ROM. If it doesn't install, it should generate an error message.
Most custom ROMs will look for a particular bootloader. If the bootloader is not found, CWM will give you get prop errors.

audit13 said:
I would update to the latest CWM and then try to flash a 4.4.2 custom ROM. If it doesn't install, it should generate an error message.
Most custom ROMs will look for a particular bootloader. If the bootloader is not found, CWM will give you get prop errors.
Click to expand...
Click to collapse
Thanks, I'll try when I get home.
I installed the ROM fine last night without any error. So I believe the bootloader is supported then.

afyaff said:
Thanks, I'll try when I get home.
I installed the ROM fine last night without any error. So I believe the bootloader is supported then.
Click to expand...
Click to collapse
To be sure, look at the bootloaders mentioned in the ROM's updater script.

[Q] Removing Knox so I can root/install custom recovery

So I've spent the past two hours trying to flash a custom recovery onto my phone so I can root and debloat.
I first tried to root following some instructions on this site and Odin, but that method failed. Then I tried to use towelroot and that method failed. I then googled the problem to find that it had to do with knox and a recent security update released by ATT. Then I flashed a custom recovery onto my phone so I could manually root and that triggered an auto stock recovery. After that I attempted to install cm11. It installed then before the rom could load, it asked me about disabling auto stock recovery and also rooting. I choose to disable it and then root. Then my phone reverted back to stock touchwiz.
How do I get rid of knox so I can root my phone?

Do you want to have a custom ROM on your phone? Root is not required to load a custom ROM.

I originally wanted to get rid of the bloatware on my phone since I don't mind some of the Touchwiz features, but if I can't gain root access due to the phones security features then I'll install something else if I have to. Right now I'm attempting to CM11 install again since I was able to install custom recovery( I had to pull the battery before Touchwiz rebooted though I superSU said it did not have binaries).

If you want TW features, flash a custom ROM based on TW.

Will doing so also give me root access?
I've rooted two devices in the past and they were never this hard so I want to be careful so I don't end up bricking my device.

UPDATE: Just tried to reinstall CM11 just to see what would happen and the same happened: it booted straight into stock touchwiz.
I've been at this for about 5 hours now and I'm at my wits end. Has anyone successfully rooted their phone from 4.4.2 over the past month?

What custom recovery is on your phone?

I had clockwork flashed.

Make sure you have the latest cwm and format the system before installing a ROM.
Before installing a custom ROM, make a nandroid backup of your current tw ROM.

I used the cyanogen installer on the website. I've installed CM before on previous devices so I'm familiar with installing roms. The CM installer is supposed to do that for me so I'm not sure if it's due to Knox and the latest ATT security update that's making it difficult to gain root access to do such as install custom mods. I've gone a google search and people seem to be having the same trouble and I don't know if a fix has been found since the last update that ATT pushed out last week.

Did you try installing a custom using the custom recovery? I have never used the installer so I can't comment, using the cm installer may not allow you to install non-cm roms.

I didn't.
Before I flashed CM11, I checked the Q/A from Cyanogen about the installer:
http://wiki.cyanogenmod.org/w/CyanogenMod_Installer
In it, they state that all you need to do is have your stock rom and software will do the rest for you. Keep in mind, that flashing CM11 was my backup option. My original intent was to simply root my device so I can remove some Samsung and ATT apps.
Here's the article from Android Central about the ATT update. Apparently I'm not the only one who is having issues trying to root:
http://www.androidcentral.com/att-brings-android-os-enhancements-galaxy-note-2-galaxy-s3-galaxy-mega
I might just have to wait out for the S6.

I have never used a CM installer even though I have used CM11 on an s3, Note2, Note3, and a Nexus 4.
I don't trust the installer and always did it the old-fashioned way with a custom recovery.

I'm going to try today since I have some time. Can you give me a link to a custom recovery? I'm going to install using odin and then try it.

Are there no stable builds for CM11?
https://download.cyanogenmod.org/?device=d2att

You should be looking for d2lte builds, not d2att.

I also did that earlier since they're universal and all I see are nightlies and experimentals.
https://download.cyanogenmod.org/?device=d2lte

The unified msm8960 ROMs have been out for a while and even though they are nightlies, they are at the stage where I would consider them stable.

Thank you.
I tried flashing another rom earlier today and it didn't install. I reloaded a backup I made before flashing and now the backup is stuck in a com.google. process. gapps loop.
What are my options?

I recommend flashing the latest Philz Touch tar.md5 recovery from here: https://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2lte/
Try re-flashing the latest CM11.

How do I get this Android10 custom ROM installed on my G960F?

Hey guys, please explain it to me as I would be 5 years old.
For nearly 3 years I used a Android 8.0 version called "lightROM" named "Bodhisattva" from a guy here on the forum.
I've seen about Android 10 and thought, here we gooo.
Sadly it didn't worked this way.
I looked through the Android 10 ROMs and complete overwhelmed, because the forum is complete confusing, I decided to go with this:
https://forum.xda-developers.com/galaxy-s9/development/havoc-os-stable-exynos-t4095221
I downloaded the needed gaps and newest Magisk, flashed newest TWRP 3.3.1-1 and rebooted into TWRP menu.
As with every new ROM, I deleted everything. The data, files, everything except dalvic and external SD.
I then wanted to flash the ROM, but I got a sort of "Android 10 vendor image missing" error.
okay, I then flashed my old Android 8 ROM and here I'm back, luckily.. Stupid Titanium Backup doesn't work too, it just doesn't recognize the files, what a stupid program. Seems like I lost everything.
One of the problems I have are all those suspicious shortcuts everyone is using for everything, I mostly understand just 1/3.
Now I've tried to find a answered all over the forum and Google, what that "Vendor Image" is. It's a sort of second partition to be able to run Android 10.
But where do I get it, how to install and what do I have to do, to get the linked ROM running on my Galaxy S9 SM-G960F Exynos Europe Version.
Please offer me all links needed to download everything I need per click, to be able to install all needed things.
Please talk to me as if I'm 5!!

I think the most simple way to do is to flash the latest stock firmware through Odin which you can download from SamMobile or just use Frija for faster and easier download, and after you flash you can finish the first android setup and flash twrp through odin

B1nz said:
I think the most simple way to do is to flash the latest stock firmware through Odin which you can download from SamMobile or just use Frija for faster and easier download, and after you flash you can finish the first android setup and flash twrp through odin
Click to expand...
Click to collapse
Thanks for your answer.
Why do I have to flash TWRP through Odin? Because it's already on my phone.
And what version of TWRP would I have to flash? I've read about problems with 3.3.1-1 and newest Android 10.
At the point where I've flashed the newest Android 10 firmware for my phone, can I install any ROM I want? Like lineageOS 17.1 for example?
Can you give me a recommendation for a ROM please, I'm pretty lost with this atm.
I need a ROM with a dark theme and mainly to play games. Right now I have a lot of trouble with games, where other people on reddit state "it's working perfectly fine".
For example "DotA Underlords" is a pure 5 fps lag party after 10 rounds.
Is there a ROM what concentrates at issues like this?

Avoka said:
Thanks for your answer.
Why do I have to flash TWRP through Odin? Because it's already on my phone.
And what version of TWRP would I have to flash? I've read about problems with 3.3.1-1 and newest Android 10.
At the point where I've flashed the newest Android 10 firmware for my phone, can I install any ROM I want? Like lineageOS 17.1 for example?
Can you give me a recommendation for a ROM please, I'm pretty lost with this atm.
I need a ROM with a dark theme and mainly to play games. Right now I have a lot of trouble with games, where other people on reddit state "it's working perfectly fine".
For example "DotA Underlords" is a pure 5 fps lag party after 10 rounds.
Is there a ROM what concentrates at issues like this?
Click to expand...
Click to collapse
because after you flash your phone with the stock firmware it will replace all your modification to the default factory settings, that's why you have to flash it again through Odin otherwise if you get into recovery mode it will just showing stock recovery.
hmm, never hear about that problem tho, but I'm using the 3.3.1-1 version of TWRP running EvolutionX Rom Android 10 and got zero problems
yeah, after you flash the latest stock firmware and finish all the first setup (you can just press skip at everything) then you can flash TWRP through Odin. then if you success you can go to TWRP and follow the installation instruction of rom that you prefer
note: In my experience I have to finish the first android setup to be able to flash TWRP, if not then it will fails all the time unless I did finish the setup
I'm not quiet sure about that since what I'm aiming for the rom is for the productivity battery life and I don't really game on my phone, but I can give you a brief summary of the rom that I've tried.
LineageOS 17.1 : is the most simple and stock android experience that I ever tried, don't have alot of features but runs noticeably smooth compared to stock samsung firmware. also it can automatically update your phone, so you don't have to manually download and flash every update
EvolutionX : is LineageOS version but with a tons of great features imo, it's not too much and not lacking of features that I need. It has gaming mode tho, but never tried using it. also it can automatically update the phone
AlexisROM : this is the rom for you if want to have OneUI experience but with features that comes from the latest galaxy s features like OneUI 2.1 etc. this rom also highly debloated which also you can modify in the installation menu since it's using the Aroma installer
If you feeling like the rom needs a little tweak for the performance, you can try to flash custom kernel that has features to tweak the cpu clock performance